The lonIp module became available starting with AX-3.2, and contains a palette with a modified LonNetwork— the default name is “LonIpNetwork”. Figure C.1 shows it expanded in the palette.
The modified LonNetwork communicates on an IP Lonworks channel as defined in CEA-852. In this document, this CEA-852 channel is referred to as the “LonIp channel”. When using the LonIp driver, the station presents itself as an “IP channel node” member (as opposed to a Lon/IP router member).
CEA-852 specifies a “Configuration Server” (Config Server) that handles the distribution of routing information to all members of a LonIp channel.
-
Prior to AX-3.5, the LonIp driver required a pre-configured, third-party Config Server already installed, along with one or more CEA-852 routers on the Lon Ip channel. The driver would not work otherwise.
-
Alternatively, starting in AX-3.5, you can configure the JACE station to operate as the Config Server on the network of configured CEA-852 routers (Lon Ip channel). Or, you can use the previous method of referencing a pre-configured, third-party Config Server.
In either case, the LonIp channel must be properly configured—that is, all channel members must be recognized by the Config Server, and have up-to-date routing tables. Each channel member
must be assigned a unique subnet/node address, but use the same channel ID. Note LonIp channel setup is outside the scope
of normal NiagaraAX Lonworks station configuration, with the sole exception of the subnet/node address assigned to the station
for use as an IP channel node. For example, setup of Lon/IP router members typically requires proprietary, vendor-specific
configuration. Consult each device’s documentation for details on how to set its Lonworks subnet/node address, etc.
Once the IP channel is properly configured, and the station has been added as an IP channel node, all other Lonworks functions will perform the same as if the JACE was connected directly to a LON trunk.
Also see LonIp licensing, LonIp architecture, and LonIp FAQs.