The Sensor Seal is compatible with networking hardware such as routers, switches, access points, stations etc.
In order for a Sensor Seal Gateway to be configured via the web-based Gateway Manager interface, it needs to have an internet connection, but this is not a requirement once the desired configuration has been set. Alternatively, the gateway can be configured via SSGSH Direct without the requirement of an internet conenction.
When powered up, the gateway will try use its currently set network configuration to access its assigned Gateway Manager server over the internet. This is the server that enables the gateway to be configured remotely via the web-based Gateway Manager interface. If it fails to connect to this server using the network configuration, the gateway will still operate as configured and send the measurements it receives using the configured connectivity type. To access the Sensor Seal Gateway Shell (SSGSH), however, SSGSH Direct must be used.
The Sensor Seal Gateway connects to its remote Gateway Manager server using SSGSCP (UDP port 1818). If encountering issues with the gateway showing as offline in the web-based Gateway Manager, ensure the network firewall is not blocking outgoing traffic on UDP port 1818 and the network configuration is correct. If that too fails, try using a different network router, cable, switch etc. or contact us so we can investigate.
Note: The Sensor Seal Gateway does not currently support using IPv6.
Network Hardware Configuration Examples
Example 1
In this configuration, a 4G LTE router is used to supply internet connectivity to a Sensor Seal Gateway. The gateway is configured to send Sensor Seal measurements to a remote SSGSCP server hosted in the cloud.
The gateway is connected to the 4G LTE router via a PoE injector using two network cables. The router has its DHCP server enabled and assigns the gateway a local IP address, subnet mask, default route, and DNS server.
Since it has internet access, the gateway is able to connect to its Gateway Manager server and can therefore be configured via the Gateway Manager web interface.
Example 2
In this configuration, the Sensor Seal Gateway is connected to a PoE switch via a network cable. Another device is also connected to the network switch. Both this device and the Sensor Seal Gateway are configured to use static IPs. The other device is set up to continuously listen for incoming UDP packets on port 2828. The Gateway is configured to use the
UDPUnicast
connectivity type with the ASCII measurement format.
No router is used in this configuration and the Sensor Seal Gateway does not have any internet connection. To update the gateway's configuration, it needs to be connected directly to a computer with a link-local address and accessed using
SSGSH Direct
.
Connection LED Flash Status Codes
Gateway v1.1
- Solid on:Connected to Gateway Manager Server. Gateway can be configured and monitored via the Gateway Manager interface. Also indicates that the gateway has a functioning internet connection.
- 200 ms on, 200 ms off:Default Route Resolved. If usingauto(DHCP) network configuration, and IP address was obtained successfully, and the MAC address of the default route (router) has been resolved. If using amanual(static) configuration, the MAC address of the default route (router) has been resolved. UDPUnicast and UDPBroadcast configurations to devices on the local network should function correctly, however UDPUnicast and SSGSCP configurations to remote servers may not function.
- 150 ms on, 850 ms off:Link Up. The gateway is connected to a networking device via Ethernet, however the default route has not been resolved.
- Solid off:Link Down: The gateway is not connected to any networking device via Ethernet. If configured to do so, measurements will still be output via UART.