1 / 25

Chapter 7

Chapter 7. LonWorks Network Programming. LonWorks Network Programming • Network Variable Bindings • Device Commissioning. LonWorks network programming involves making the software bindings that represent the interactions between the physical nodes.

kaylee
Download Presentation

Chapter 7

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 7 LonWorks Network Programming LonWorks Network Programming • Network Variable Bindings • Device Commissioning

  2. LonWorks network programming involves making the software bindings that represent the interactions between the physical nodes.

  3. Network management tools may use a variety of interfaces for programming and configuring LonWorks networks.

  4. Ad hoc program design requires the network management tool to be connected to the nodes because they are commissioned as they are added to the network program.

  5. Engineered program design allows the network program to be created without the network management tool being attached, which is useful for planning an automation system while a building is under construction.

  6. Like a virtual wire, network variable bindings allow control information to be shared between function blocks or nodes.

  7. Unicast bindings include one sender and one receiver, though they may be within the same function block.

  8. Multicast bindings include fan-out and fan-in bindings, which are used to share the same control information among several function blocks.

  9. The network variable configuration table includes the Selector IDs that are associated with a node’s network variables.

  10. Alias network variables allow multicast bindings to avoid Selector ID conflicts.

  11. LonWorks network domains include one or more subnets that include one or more nodes. The numerical identification of the domain, subnet, and node are used to precisely address message packets to individual nodes.

  12. Each node includes an address table that specifies the destination address for the network variable updates it transmits onto the network.

  13. Subnet broadcasts are isolated to a certain subnet by routers, but domain broadcasts are forwarded by routers to all nodes in the network domain.

  14. Acknowledged message service requires a return response from the receiving node, confirming that a network variable update was received.

  15. Unacknowledged message service is a one-way transaction where no response is expected from the receiving nodes.

  16. Authenticated message service provides a high-security method of sending network variable data by requiring nodes to prove that they share the same authentication key.

  17. The use of a network channel can be divided into time slots for nodes to transmit message packets onto the network. Assigning a priority time slot to a node guarantees that it can communicate reliably without packet collisions.

  18. Configuration properties can be changed to customize node behavior and the control functions.

  19. Plug-ins from node or network device manufacturers provide a user-friendly way to adjust configuration properties.

  20. Heartbeat configuration properties define how often a network variable update is transmitted from a sending node.

  21. With the configuration property SCPTmaxRcvTime, a receiving node can be set to lock out if a heartbeat is not received from a sending node within a certain period.

  22. SCPTdebounce sets a delay period before a digital network variable is updated to avoid transmitting the pulses of a set of physical contacts that are changing state.

  23. For commissioning, the Neuron ID of a LonWorks node or network device can be obtained by any of three methods.

  24. The Wink command confirms that the tool can communicate with a node by causing the node to exhibit a physical response, such as flashing an LED.

  25. Routers must be commissioned and on-line in order for the tool to communicate with nodes on their other side.

More Related