TPControl devices may fail to connect to an AMX (Netlinx) Controller due to a range of configuration or network issues. Use the following checklist to verify that the TPControl device, the AMX controller, and the network are properly configured.

1. TPControl License

  • Confirm that the device is registered with a valid TPControl license.

2. iOS-Specific Requirements

  • For devices running iOS 14 or later, ensure the 'Local Network' permission is enabled in the device’s Settings for TPControl.

3. Wi-Fi and Network Access

  • Ensure Wi-Fi is enabled on the TPControl device.

  • Confirm the device is connected to the same network as the Netlinx Controller.

4. TPControl Profile Settings

To verify the profile settings:

  • Navigate to TPControl Settings > Manage Profiles > Profile1.

  • Confirm the following:

    • Host IP: This should be the IP address of the Netlinx Controller.

    • iCSP Port: Set to 1319, unless the controller uses a different port.

      • Note: NX Controller Secure iCSP is not currently supported.

    • Device ID:

      • Ensure the correct Netlinx Device ID is entered. This ID is assigned by the AMX programmer.

      • The Device ID must be unique. If two TPControl devices use the same ID, the connection will fail.

    • Encryption:

      • If encryption is enabled on the controller, ensure the correct username and password are configured in the profile.

5. Network Connectivity

  • Ensure the Netlinx Controller is online and reachable from the TPControl device:

    • Open a browser on the device and enter the controller’s IP address. Confirm that the controller’s web interface loads.

    • Alternatively, use the Telnet service on the controller to ping the device.

6. Static IP Configuration

If the TPControl device is configured with a static IP address:

  • Make sure a DNS and Gateway address are also configured.

  • In some environments, setting the controller’s IP address as the DNS/Gateway can help resolve connectivity issues.

7. iCSP Port (1319) Accessibility

If all settings appear to be correct and the controller is reachable:

  • The issue may be related to network-level blocking of the iCSP port (1319).

  • Further investigation may be required to determine whether the network is allowing communication on this port.

Additional Notes

If you are unsure about the Netlinx Device ID or controller settings, please contact your AMX programmer. You may also reach out to TPControl support for further troubleshooting assistance.