Check that the data source is configured correctly and the machine is connected and powered on.

If you are still getting a timeout error, the Run test connection (details below) may be getting blocked by your computer/network firewall. Either try using a different network or contact your IT to make sure the test is not getting blocked.

Direction	Port	Transport protocol	Application protocol
Outbound	443	TCP	WebSocket

If the above is all in order, your machine may not be responding in a timely manner (timeout details below). That may be due to high CPU load or simply outdated hardware.

Hardware/firmware	Timeout
SecureEdge and SecureEdge Pro, firmware 5.0 and up IXrouter3, firmware 3.29 and up	5 seconds
IXrouter3, firmware 3.28 and below	2 seconds

The edge gateway was unable to read one or more variables. These variables have been temporarily blacklisted so that other variables can continue to be read.

The error message may contain a second error, indicating what the problem is. Look up that error below, resolve it, and then reboot the edge gateway.

See error message: No valid tags left after verifying tags.

BACnet communication isn't possible with the machine. Possible causes:

• The machine is expecting a BACnet Device ID, but the data source is not configured as such. Meaning a random BACnet Device ID is selected by the machine and that device does not contain the specified variable. This can happen if you have multiple BACnet devices on the same physical device and the data source is configured for an IP address instead of a BACnet Device ID.
  • The data source's Addressing method determines whether it specifies a BACnet Device ID when trying to communicate with your machine.
  • For help in configuring the BACnet Device ID in your data source, see BACnet/IP data source setup.
  • For help in finding your BACnet Device ID, see How do I find my BACnet Device ID?.
• The machine doesn't support BACnet/IP or does not have its BACnet/IP server enabled.

See error message: Unable to get BACnet RPM response.

BACnet/IP communication is not possible. Possible causes:

• The IP address in the data source is incorrect and does not match the machine.
• The port setting in the data source is incorrect and does not match the port on which the BACnet/IP server on the machine is listening.
• Restarting the BACnet/IP server on the machine or restarting the machine itself may help.

BACnet/IP communication is not possible. Possible causes:

• The IP address in the data source is incorrect and does not match the machine.
• The port setting in the data source is incorrect and does not match the port on which the BACnet/IP server on the machine is listening.
• There is no BACnet/IP server running on the machine.
• Restarting the BACnet/IP server on the machine or restarting the machine itself may help.

BACnet/IP communication is not possible. Possible causes:

• The device ID in the data source is incorrect and does not match the machine.
• The port setting in the data source is incorrect and does not match the port on which the BACnet/IP server on the machine is listening.
• There is no BACnet/IP server running on the machine.
• Restarting the BACnet/IP server on the machine or restarting the machine itself may help.

BACnet/IP communication is not possible. Possible causes:

• The IP address in the data source is incorrect and does not match the machine.
• The port setting in the data source is incorrect and does not match the port on which the BACnet/IP server on the machine is listening.
• There is no BACnet/IP server running on the machine.
• Restarting the BACnet/IP server on the machine or restarting the machine itself may help.

BACnet/IP communication is not possible. Possible causes:

• The device ID in the data source is incorrect and does not match the machine.
• The port setting in the data source is incorrect and does not match the port on which the BACnet/IP server on the machine is listening.
• There is no BACnet/IP server running on the machine.
• Restarting the BACnet/IP server on the machine or restarting the machine itself may help.

The machine cannot find the specified object. Possible causes:

• The machine is expecting a BACnet Device ID, but the data source is not configured as such. Meaning a random BACnet Device ID is selected by the machine and that device does not contain the specified variable. This can happen if you have multiple BACnet devices on the same physical device and the data source is configured for an IP address instead of a BACnet Device ID.
  • The data source's Addressing method determines whether it specifies a BACnet Device ID when trying to communicate with your machine.
  • For help in configuring the BACnet Device ID in your data source, see BACnet/IP data source setup.
  • For help in finding your BACnet Device ID, see How do I find my BACnet Device ID?.
• The variable may be misconfigured.
  • Check the machine for the correct address and verify the settings of your variables in the data source.
  • For help in finding the right addresses, see Find the address of your BACnet/IP variables.