Unless you have multiple LonTunnels (one for each LON port on the JACE), you typically do not need to do any further configuration, apart from defaults (as shown in Figure B.4).
Properties of the LonTunnel are described as follows:
-
Enabled
Boolean slot that must be enabled (true) to permit tunneling.
-
Connections
Read-only slot to indicate the number of tunnel connections, as either 0 (none) or 1 (maximum).
-
Status
Read-only status of the Lon tunnel, typically
ok(unlessfaultfor no supporting LON port). -
Identifier
Read-only “reflection” of the entered Device Name (below), used as the “Tunnel Name” when configuring the client-side Lon Tunneling dialog (Figure B.3).
-
Device Name
String to identify the JACE’s
LONnport used in a LonNetwork. For a LonTunnel copied from the palette, this defaults toLON1. These must match the “Device Name” string in the LonNetwork’s Lon Comm Config container. See Lon Comm Config notes.
In addition, a LonTunnel has an available (right-click) action:
-
Disconnect All
Disconnects any active connection through this LonTunnel (maximum of 1), causing removal of the “TunnelConnection” below it. See About Lon tunnel connections. On the remote (Lon tunnel client) side, a popup message “Connection closed by remote host” is seen.
Any TunnelConnection component also has its own “Disconnect” action, which effectively performs the same function.