Setting up a LonIp channel with a third-party Config Server
This setup method applies when the host is installed on a network that includes a configured third-party Config Server and
CEA-852 routers.
Prerequisites: The station is open in
- Before adding the ChannelMember for the CEA-852 router, connect to the remote controller station, right-click the ChannelMember and click .This step ensures that a discovery job will find the Lon router.
- Open the lonIp palette and drag or copy a LonIpNetwork component to the station’s container.
- Double–click the LonIpNetwork component (opens the Device Manager), then double-click the network’s Local Lon Device (or select the Local Lon Device and click Edit).The local Lon device Edit window opens.
- Configure the device’s
Channel Id,SubnetandNodeto be consistent with the LonIp channel, which the station will join as a member, then click OK.The third-party Config Server/CEA–852 router interface provides theChannel IdandSubnet. Choose aNodethat is not already in use on the subnet. - Expand the and double-click the Network Config container.The Network Config Property Sheet opens.
- Set Is Config Server to
false, click OK and click Refresh.TheConfig Server Ipproperty appears in the Property Sheet.
- Configure these properties and click Save:
- For
Config Server Ip, enter the server IP address of the third-party Config Server. - If the host is behind a NAT router, set
Use Extended Nattotrue, and enter theNat Ip Address(the Internet side of the NAT router).
The driver automatically forcesUser Extended Nattotrueif it detects extended NAT messages. - For
- Double-click on Ip Channel.The Member Manager view opens.
- Right–click the channel member (row) that represents this station and click .
- At the third-party Config Server, add a member to the IP channel for the station.To complete this step, refer to the vendor’s documentation for the Config Server.Unlike the situation where the station functions as the Config Server, you do not need to edit or add any members in this view. Once the third-party Config Server is configured, it makes contact with the station. Then, the LonIp driver in the station dynamically populates the Member Table under the network’s Ip Channel container. From this point forward, other Lonworks functions perform as if directly connected to a Lon trunk, that is, as if using a standard Lon network.
The next logical step may be to commission a Lon router. It is likely that at least one Lon router needs to be added.