Index | Prev | Next

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 Workbench.
  1. Open the lonIp palette in the palette side bar and drag or copy a LonIpNetwork component to the station’s Config > Drivers container.
  2. 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.
    Image
  3. Configure the device’s Channel Id, Subnet and Node to 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 the Channel Id and Subnet. Choose a Node Id for the LonIpNetowrk’s Local Lon Device that is not already in use on the subnet.
  4. Expand the LonIPNetwork > ipChannel and double-click the Network Config container.
    The Network Config Property Sheet opens.
  5. Set Is Config Server to false, click OK and click Refresh.
    The Config Server Ip property appears in the Property Sheet.
    Image
  6. Configure these properties:
    • 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 Nat to true, and enter the Nat Ip Address (the Internet side of the NAT router).
  7. To continue, click Save.
    The driver automatically forces User Extended Nat to true if it detects extended NAT messages.
  8. Double-click on Ip Channel.
    The Member Manager view opens.
    Image
  9. Right-cick the channel member (row) that represents this station and click Actions > Update.
  10. At the third-party Config Server, add a member to the IP channel for the station. Refer to the vendor’s documentation for the Config Server for this step.
    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.

Related Links

  • Lon over IP (Parent Topic)

    • Index | Prev | Next