My step loop logic will iterate through this abbreviated list, making the device connection per the COM Port identified in the connections object list and the connection parameters specified in the Tulip Table.
I’ve run into a potential snag - the triggers within the app currently “communicate” with these devices by Static Value | Text “Identifier” parameters in the Run Device Function and Device Output triggers:
I’m thinking I need to make this dynamic based on the device type connected…and maybe just leverage the first device of a type (i.e. Serial Barcode Scanner, Printer) as the default input/output and let the user know that if they prefer to use the second device instead, to disconnect the first of the device type and re-run the connection steps.
This worked - basically storing whatever is the last connected Identifier containing “Printer” or “Scanner” (reminded me that Contains is case sensitive in this context, unlike table filters):