RS-232 and IR Connections

Troubleshooting RS-232 and IR Connections

RS-232 Connections

If there is an issue with an RS-232 connection, ensure that all of the devices in the communication path (both DisplayNet devices and peripherals) are using the same settings: Baud Rate, Data Bit, Stop Bit and Parity. These settings are found in the Device Settings Rollup window for each device. Also, ensure that any serial cables used are properly wired. RS-232 communication can be bidirectional, so it is normally necessary to join each device twice, both as a sender and as a listener. In DisplayNet Server software, when two devices are paired, these two pathways are set up automatically; however, when using a third party controller, these switches must be set up individually via the API.

IR Connections

If there is an issue with an IR connection, ensure that the IR Transmitters are connected to the IR Out ports and that the IR Receivers are connected to the IR In ports on the DisplayNet devices. Also, ensure that any peripheral devices (e.g. IR remotes, Blu-ray Players, etc.) are within range and correctly oriented toward the IR Transmitters and Receivers. As with RS-232, the communication can be bidirectional. If bidirectional communication is used, it is necessary to switch each DisplayNet device twice, as both a sender and as a listener. In practice, however, IR communication is usually unidirectional. In DisplayNet Server, when two devices are paired, these two pathways are set up automatically; however, when using a third-party controller, these connections must be set up individually via the API.

 

There are global RS-232 settings that apply universally to all devices, as well as individual RS-232 settings that can be configured separately for each device in each device's device setting rollup.