Configuring COM Port / Serial Communication for Third-Party Hardware Triggering in EthoVision XT
Last updated: Nov 01, 2026
Problem
A user wants to use the PC's COM (serial) port to trigger or communicate with third-party hardware from EthoVision but cannot find the COM port configuration option or the referenced 'HardwareInterface SerialPort' folder in the documentation.
Details
COM port / serial communication with third-party hardware in EthoVision requires the External Data module (also referred to as DAQ co-acquisition functionality). Without this licensed module, the COM port option is not present in the interface. Users searching for driver or configuration folders based on older documentation may not find these if the module is not licensed or if the installation path has changed. Affected versions: EthoVision XT (multiple versions).
Solution
1. COM port / serial communication for triggering third-party hardware in EthoVision requires the External Data (DAQ co-acquisition) module to be part of your license.
2. Verify whether your license includes this module: go to Help > About in EthoVision and review the listed modules, or check MyNoldus under your license details.
3. If the module is licensed, you will find the DAQ co-acquisition option in the Trial Control or Hardware settings (available during live tracking only — not for post-hoc analysis).
4. Format the appropriate COM port within the EthoVision DAQ configuration interface to establish serial communication with your device.
5. If the External Data module is not part of your license, contact your Noldus account manager to discuss adding it.
6. For simpler triggering needs (on/off TTL pulses), the USB I/O Box (PTIO-0020) with the Trial & Hardware Control module may be a more straightforward alternative — see related articles on TTL output configuration.