Configure XBee Industrial Gateway
Configure Remote Manager connectivity settings
Digi XBee Industrial Gateway
109
TCP no delay enable
Configures whether use of the TCP no delay option is disabled by default for the Remote Manager
connection between device and server, when configuring the device's TCP socket endpoint for that
connection. The default is disabled. This default reduces the number of packets sent when the
Remote Manager connection is established between device and server. While there is a very slight
penalty in terms of added latency, that penalty is very small compared to the relative high latencies
for cellular network communications. Reducing the packet count reduces the number of bytes
exchanged over the cellular connection, which saves money. The typical start-up data count is reduced
from about 7KB to 4KB by disabling TCP no delay. The ability to turn on the TCP No delay option is
provided for technical support and troubleshooting purposes.
TCP keep alives enable
Enables or disables the ability to send TCP keep-alive packets over the client-initiated connection to
the Remote Manager server, and whether the device waits before dropping the connection. The
default is enabled.
Device Cloud client initiated connection page
You can use the settings on this page to enable Remote Manager and specify reconnect timeout
settings.
Connection enable
Enables or disables the connection from XBee Industrial Gateway to the Remote Manager server.
Disable this feature if you have no use for Remote Manager, and want to eliminate any Remote
Manager-related network traffic.
Connection reconnect timeout (seconds)
These settings control whether to automatically reconnect to Remote Manager after being
disconnected and waiting for the specified amount of time.
If you do not want to automatically reconnect to Remote Manager after a disconnect, choose
Never
reconnect
.
Note
From the web interface, clear the
Reconnection delay
check box.
Device Cloud network type page
Keep-alive Ethernet and Keep-alive Mobile
These settings control how often keep-alive packets are sent over the device-initiated connection to
Remote Manager, and whether the Remote Manager-registered device waits before dropping the
connection. Keep-alives for the Remote Manager connection serve three basic purposes:
1. Keep the Remote Manager connection alive through network infrastructure such as routers,
NATs and firewalls.
2. Inform the other (remote) side of the Remote Manager connection that its peer is still active.
