ActiveBridge Network Testing
Initialization Self Test
The network self-test is only available for bridges running version 2.22.0 or newer.
When initializing an ActiveBridge or after losing communication with our services, it will run a self-test to identify any network issues. Once the test is completed, if a problem is detected, one of the error codes shown in the table below will appear on the splash screen while the red LED remains on and solid.
Error Codes
Error Code | Triggered by | Resolution |
|---|---|---|
NO NETWORK | Not having an IP address | Check the network cable, router, and DHCP assignments. |
NO DNS | Failure to resolve the necessary DNS records | Check the gateway (i.e., cable modem) to ensure there isn’t content filtering/ISP domain resolvers. |
TCP BLOCK | Not being able to get to the comms service (timeout) | Check console/comms website (for outage). Check for firewall rules blocking outgoing port 443 to |
If any error code condition is present, the bridge will check for recovery every 5 seconds. If it succeeds, it will automatically reconnect.
UDP Test
The network self-test is only available for bridges running version 2.24.0 or newer.
ActiveComms utilizes UDP ports for its transmissions. To ensure it is working properly a test can be run on demand:
Hold down the back button for 3 seconds; the T screen/splash screen goes away, and a complete self-test is performed.
If the self-test fails to ping one or more UDP ports in the range 10000-10029, it should report 'UDP BLOCK' on the screen and in the log.
If all the ports successfully ping and all other tests succeed, it should display
SUCCESS (average latency) mson the screen for 30 seconds and then reboot the bridge, exiting self-test mode.