Make instruments
part of the same process.

Device Configuration holds a name, category, role, description, brand/model information and connection settings for each instrument. A sequence refers to the configured device, so the station can contain several meters, supplies or interfaces with distinct responsibilities.

Device configuration Inside the software

Enlarge

Enable or disable devices deliberately and use connection feedback when commissioning. Entering a brand and model identifies the equipment; it does not install a driver or establish compatibility by itself.

Custom command formats and response handling help adapt supported connections to the documented instrument protocol. Confirm the exact brand, model, adapter and driver version with the team; an interface family is not a universal driver for every instrument.

Windows may assign a new COM number after an adapter is reconnected. Supported USB identity matching uses available VID/PID, serial number and hardware information to locate the device’s current port. The saved port can be a fallback.

1. Capture the intended adapter

   Select the connected serial device and save its available identity with the communication settings.

2. Check reconnection

   Reconnect the adapter and confirm that the intended instrument is found at its current COM port.

3. Resolve ambiguous identities

   Review adapters that share an identity or have no unique serial number before depending on automatic selection.

A stable USB identity solves port discovery. Baud rate, protocol, cable wiring and whether another program holds the port still affect communication.

Supported DAQ integrations, including NI-DAQmx and Advantech paths, connect channel configuration with acquisition and output operations. Discovering hardware is followed by an explicit binding to the channels required by the station.

Commanded output state and measured feedback answer different questions. Where confirmation matters, read a suitable feedback channel rather than assuming a successful command proves the physical output.

NI-DAQmx integration requires the matching native NI driver on the station. Ordinary relay and DAQ operation is separate from the specialist UDAQ firmware programming capability.

The Virtual Machine workspace manages simulation profiles that can be launched, stopped or disabled. Launched profiles participate in the normal device workflow with simulated responses, allowing engineers to exercise configured logic while physical equipment is unavailable.

1. Install and identify

   Prepare vendor drivers, the correct physical interface and the device’s documented settings.

2. Connect and inspect

   Use Test Connection and Communication Studio to inspect a supported identification query or other appropriate command.

3. Verify the measurement

   Check framing, decoded values, units, scale and response timing against a known condition.

4. Validate the production use

   Map the device into the sequence and test normal, disconnected and unexpected-response behaviour.