Handling TCP Connection Errors Between a Xilica Controller and a Third-Party Device

When a third-party device can only be controlled by a single controller (such as a native control app, Xilica Designer, or an XTouch controller), the issue typically stems from one of two sources:

1. The secondary controller was not mapped properly in Designer software

2. The third-party device has limitations on simultaneous TCP connections

If your third-party device uses TCP control, it likely allows only one controlling connection at a time. (Check the device's user manual for specific information.) Important to note: a connection to Xilica Designer counts as one connection.

When designing a control system:

• If you place a PJLink power button in your controller design schematic, the controller will automatically establish a TCP connection when the project loads

• If Xilica Designer has a PJLink projector in the project, it will also attempt to establish a TCP connection when going ONLINE

• With limited TCP connections available, these simultaneous attempts can cause conflicts

If your third-party device allows only one TCP connection and you want to control it using an XTouch Control device:

1. Go online with your project in Xilica Designer

2. Exit the Xilica Designer desktop application

3. The XTouch Control device should now be able to control the third-party device without connection conflicts

This approach ensures that only one device (the XTouch Control) is attempting to establish a TCP connection with the third-party device.