1 / 42

i-Vu Open Systems IP & MS/TP Networks & Open Controllers on 3rd Party Systems

i-Vu Open Systems IP & MS/TP Networks & Open Controllers on 3rd Party Systems. What will we cover?. We will cover i -Vu Open System: MS/TP Networks TCP/IP Networks Addressing i -Vu Open Controllers & 3 rd Party systems – special considerations. MS/TP Network. MS/TP Network.

chidi
Download Presentation

i-Vu Open Systems IP & MS/TP Networks & Open Controllers on 3rd Party Systems

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. i-Vu Open Systems IP & MS/TP Networks & Open Controllers on 3rd Party Systems

  2. What will we cover? We will cover i-Vu Open System: • MS/TP Networks • TCP/IP Networks • Addressing • i-Vu Open Controllers & 3rd Party • systems – special considerations

  3. MS/TP Network • MS/TP Network

  4. MS/TP Network MS/TP Network MS  Master-Slave TP  Token-Passing MS/TP devices are either Masters or Slaves Masters – can initiate communication • and will respond to broadcasts Slaves – only respond to direct • requests for information i-Vu Open controllers are Master devices

  5. MS/TP Network On any given MS/TP bus, each MS/TP device must have a unique MS/TP address (commonly called MAC address) Master devices can have a MAC address between 0 and 127. Slave devices can have a MAC address between 0 and 254. i-Vu Open device MAC address is set using rotary switches. Max address is 99.

  6. MS/TP Network In order for a device to initiate communication it must have the token. Lowest addressed device creates token following power up or collision. Master device passes token to next master device when done. Max Info Frame setting determines how many requests can be made before having to pass token.

  7. MS/TP Network To determine next master recipient, master does a Poll for Master. i-Vu Open controllers will do a Poll for Master every 50 times they get the token if there is a gap in addressing. Polls one address each time it gets token

  8. MS/TP Network A simple i-Vu Open VVT System VVT Zone Rotary Address 15 RTU Rotary Address 02 Bypass Rotary Address 14 VVT Zone Rotary Address 09

  9. MS/TP Network A review of a BACScope capture shows the token being passed between the 4 controllers on the network (addresses are in HEX format).

  10. MS/TP Network Since there are gaps in the addressing, the BACScope capture will also show periodic Poll for Master messages.

  11. MS/TP Network • Questions?

  12. TCP/IP Network • TCP/ IP Network

  13. TCP/IP Network Open Routers and Open Links are BACnet/IP to MS/TP Routers Internal router of an i-Vu Open server is also a router when the USB Open Adapter is used. Adding Open Routers or Open Links allows you to: • Access i-Vu Open devices from the IP side • Expand systems beyond the 60 device limit of an MS/TP bus running at 76.8k.

  14. TCP/IP Network Open routers have an IP address and a MAC address. The MS/TP MAC address of an i-Vu Open router will always be 0 and cannot be changed. On a system with multiple i-Vu routers that does not have a front end, one router should have rotary switches set to 01 to make him the ‘master’ router. The master will synch time and collect color status from other routers.

  15. TCP/IP Network IP Router BACnet/IP Network i-Vu Router i-Vu Link i-Vu Open server Standard or Plus MS/TP Networks USB Router MS/TP Network MAC Address 3 MAC Address 3 MAC Address 3 MAC Address 7 MAC Address 7 MAC Address 7

  16. TCP/IP Network • BBMDs BBMDs: BACnet Broadcast Management Devices Used to manage BACnet Broadcasts across routers BACnet uses broadcasts for everything from discovering nodes to sending trend and alarm data to the server

  17. TCP/IP Network • BBMDs Only one router per subnet needs to be configured as a BBMD Use the BBMD Tool to configure your routers. For an i-Vu server, the internal router must have a valid IP address in order to configure it as a BBMD BBMDs must be configured in order for i-Vu or FA to be able to fully discover an entire system spread across multiple subnets

  18. TCP/IP Network • BBMDs IP Router i-Vu Open server IP Router IP Router IP: 141.61.92.87 Subnet: 255.255.255.0 i-Vu Link i-Vu Router USB Router IP: 41.4.22.54 Subnet: 255.255.255.0 IP: 141.61.92.88 Subnet: 255.255.255.0 IP: 16.128.12.22 Subnet: 255.255.255.0 USB Router MS/TP Network MS/TP Networks

  19. TCP/IP Network • BBMDs The network on the previous slide would require each router to be a BBMD The BBMD table loaded would contain the IP address of each of the three routers so would look as follows:

  20. TCP/IP Network • Questions?

  21. Controller Addressing in i-Vu Open • Addressing Controllers

  22. Addressing An i-Vu Open controller has two addresses: It’s MS/TP Network Address It’s BACnet System Address MS/TP Network Address The BACnet MS/TP network address is set using the rotary switches on the device This address must be unique only on the local MS/TP network where the controller is installed This is referred to as the MAC address of the controller

  23. Addressing IP Router i-Vu Link i-Vu Open server i-Vu Router MS/TP Networks MS/TP Network MAC Address 3 MAC Address 3 MAC Address 3 MAC Address 7 MAC Address 7 MAC Address 7

  24. Addressing • BACnet System Address • Referred to as the DeviceID or Device Instance of the controller • This can be generated automatically (default) or set manually • Automatically, it is set as a combination of the Network Number that the device resides on and the device MAC address (Auto Generation) • Manually, it is set via software (using BACView, Field Assistant or i-Vu), to any valid BACnet Device ID

  25. Addressing Default Controller Configuration Dip Switches Default Settings Rotary Address = 0 Dip Switches set Baud Rate = 76.8K Internal Configuration Network number =16101 Device Instance is not set Address

  26. Addressing Default Router Configuration Default Settings Rotary Address = 0 Dip Switches set Baud Rate = 76.8K IP Address = 192.168.168.1 Internal Configuration BACnet/IP Network Number 1600 MS/TP Network number is not set Device Instance is not set Dip Switches Address

  27. Addressing • Auto-generating Scheme Standalone controllers or systems that do not have i-Vu Open routers will always have a default MS/TP network number of 16101 When controllers are connected to a i-Vu Open router then it’s setting will determine the automatic BACnet addressing scheme for the connected Controllers (see below). i-Vu Open Router or Link • IP Network Number = 1600 • Device Instance Number = 1600xx • MS/TP Network Number = 161xx • MS/TP MAC Address = 0 (fixed) i-Vu Open Controllers: • Device Instance Number = 161xxyy • MS/TP MAC Address = yy • MS/TP Network Number = 161xx (actually learned from the router; defaults to 16101 if no i-Vu Open router is present) NOTE: USB Adapter Network # is randomly generated by default Legend 16 = Carrier's BACnet Vendor ID xx = Router's rotary address (Router Address) yy = Open controller's rotary address (MS/TP MAC Address)

  28. Addressing Router Setup – IP Addressing Routers or Links can be set to an Assigned IP address or allowed to obtain an IP address using DHCP. To Assign an IP address: Use BACView Use PC and HyperTerminal: Turn Dip Switch 1 and 2 ON. Cycle power. Connect to the Router or Link with a PC running HyperTerminal using a USB-L cable or connect through the S2 port. Note: Turn Switch 1 OFF and cycle power when done.

  29. Addressing Examples • Auto-generating with External Routers BACnet/IP Network number 1600 Rotary Address 01 Router Device Instance 160001 MS/TP Network Number 16101 Rotary Address 03 Device Instance 1610103 Rotary Address 07 Device Instance 1610107 16 = Carrier’s BACnet Vendor ID

  30. Addressing Examples Autogenerating with i-Vu Open Server Server Device Instance 169999 i-Vu Open Standard or Plus MS/TP Network Number is Autogenerated. 16593 Rotary Address 03 Device Instance 1659303 Rotary Address 07 Device Instance 1659307 16 = Carrier’s BACnet Vendor ID

  31. Addressing Examples • Autogenerating with External Routers IP Router i-Vu Open Standard or Plus BACnet/IP Network number 1600 Server Device Instance Number 169999 Rotary Address 01 Router Device Instance 160001 MS/TP Network Number 16593 16101 Rotary Address 03 Rotary Address 03 Device Instance 1659303 Device Instance 1610103 Rotary Address 07 Rotary Address 07 Device Instance 1659307 Device Instance 1610107 16 = Carrier’s BACnet Vendor ID

  32. Addressing Manual Addressing - Routers At the site level/Discovery, the Advanced tab allows for manual addressing of the routers When using manual addressing make sure that each network number and device instance is unique or the NETWORK WILL HAVE PROBLEMS!!

  33. Addressing Manual Addressing - Controllers At the Router level/Discovery, the Advanced tab allows for manual addressing of the Controllers When using manual addressing make sure that each device instance is unique or the NETWORK WILL HAVE PROBLEMS!!

  34. Addressing • Manual Addressing Manually defining network numbers The maximum device instance number is 4,194,302. Network numbers greater than 40,000 would potentially cause errors in the system because it will cause device instance numbers to be greater than 4,194,302. i-Vu will automatically subtract 40,000 and assign a device instance minus 40,000 to the controller. Example Network number = 50000 50000 – 40000 = 10000 Controller MAC address = 22 22 appends to 10000 Device Instance = 1000022

  35. Addressing Auto Vs. Manual Addressing Auto Addressing Automatically configures Routers to have unique Network numbers Automatically configures the controllers to have unique device instance numbers Manual Addressing Manual process to give unique network numbers Manual process to give unique device instance numbers Recommended only if it is specified for a certain network numbering scheme!

  36. Addressing • Multiple i-Vu systems on same LAN • You must have unique Device IDs and MS/TP Network numbers • By default, every i-Vu Open server has a Device ID of 169999 • Two or more i-Vu Open servers on the same LAN would result in duplicate server Device IDs • Every i-Vu Open system, by default, uses the same addressing scheme which means that great care needs to be taken • MS/TP network numbers must be manually set or care needs to be taken to ensure that the rotary switches on all routers are unique. • If the network number is manually set then the router Device ID will most likely also need to be manually set.

  37. Addressing • Multiple i-Vu systems on same LAN • If two or more i-Vu servers reside on the same LAN and they can be found by BACnet a common problem is that alarm and trend data may periodically be lost. • Problem most likely to be seen with Internal router since a device binds with the last device that responds to its request.

  38. Addressing • Questions?

  39. i-Vu Open Controllers & 3rd Party Systems • Special Considerations

  40. 3rd Party BMS Considerations Default Network Number All Open controllers, by default, have an internal network number of 16101. Thus, the BMS system CANNOT have their own network (of any kind) with a network number of 16101. Only way to change default network number in an i-Vu Open controller is to connect controller to an i-Vu router configured withthe desired MS/TP network number.

  41. 3rd Party BMS Considerations Auto Generated Device IDs Third party routers will NOT send the MS/TP network number to Open controllers. ALC and other OEM customers routers will send it. Open controllers use the network number to generate a unique Device ID as part of the i-Vu Open system. If you have Open controllers on more than one 3rd party MS/TP network serious consideration should be given to using user defined Device IDs set using BACView or Field Assistant.

  42. Thank You!

More Related