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

  • Upload
    chidi

  • View
    42

  • Download
    1

Embed Size (px)

DESCRIPTION

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. - PowerPoint PPT Presentation

Citation preview

Page 1: 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

Page 2: 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 NetworksTCP/IP NetworksAddressingi-Vu Open Controllers & 3rd Party

systems – special considerations

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

MS/TP Network

MS/TP Network

3

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

4

MS/TP NetworkMS Master-SlaveTP Token-Passing

MS/TP devices are either Masters or SlavesMasters – can initiate communication

and will respond to broadcastsSlaves – only respond to direct

requests for information

i-Vu Open controllers are Master devices

MS/TP Network

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

5

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.

MS/TP Network

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

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.

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

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

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

8

MS/TP Network

A simple i-Vu Open VVT System

RTURotary

Address 02

VVT ZoneRotary

Address 09

BypassRotary

Address 14

VVT ZoneRotary

Address 15

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

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).

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

10

MS/TP Network

Since there are gaps in the addressing, the BACScope capture will also show periodic Poll for Master messages.

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

MS/TP Network

Questions?

11

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

TCP/ IP Network

TCP/IP Network

12

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

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.

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

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.

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

BACnet/IP Network

MAC Address 7

MAC Address 3

MS/TP Networks

i-Vu Router

TCP/IP Network

15MAC Address 7

MAC Address 3

MAC Address 7

MAC Address 3

IP Router

USB RouterMS/TP Network

i-Vu Linki-Vu Open server Standard or Plus

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

16

TCP/IP Network

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

BBMDs

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

TCP/IP Network

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 17

BBMDs

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

MS/TP Networks

i-Vu Router

TCP/IP Network

18

IP Router

USB RouterMS/TP Network

i-Vu Link

i-Vu Open serverIP

RouterIP

RouterIP: 141.61.92.87Subnet: 255.255.255.0

IP: 16.128.12.22Subnet: 255.255.255.0

IP: 41.4.22.54Subnet: 255.255.255.0

BBMDs

USB RouterIP: 141.61.92.88Subnet: 255.255.255.0

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

TCP/IP Network

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:

19

BBMDs

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

TCP/IP Network

Questions?

20

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

Addressing Controllers

Controller Addressing in i-Vu Open

21

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

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 controller22

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

MAC Address 7

MAC Address 3

MS/TP Networks

i-Vu Router

Addressing

23MAC Address 7

MAC Address 3

MAC Address 7

MAC Address 3

IP Router

MS/TP Network

i-Vu Linki-Vu Open server

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

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

24

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

25

Default SettingsRotary Address = 0Dip Switches set

Baud Rate = 76.8K

Internal ConfigurationNetwork number =16101Device Instance is not set

AddressingDefault Controller Configuration

Address

Dip Switches

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

26

Default SettingsRotary Address = 0Dip Switches set

Baud Rate = 76.8KIP Address = 192.168.168.1Internal ConfigurationBACnet/IP Network Number

1600MS/TP Network number is

not setDevice Instance is not set

AddressingDefault Router Configuration

AddressDip Switches

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

Standalone controllers or systems that do not have i-Vu Open routers will always have a default MS/TP network number of 16101When 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).

Legend 16 = Carrier's BACnet Vendor ID xx = Router's rotary address (Router Address)yy = Open controller's rotary address (MS/TP MAC Address)

i-Vu Open Router or LinkIP 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)

Auto-generating Scheme

Addressing

27

NOTE: USB Adapter Network # is randomly generated by default

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

28

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 BACViewUse 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.

AddressingRouter Setup – IP Addressing

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

BACnet/IP Network number 1600

Device Instance 1610103

16 = Carrier’s BACnet Vendor ID

Device Instance1610107

Rotary Address 07

16101

Rotary Address 03

Router Device Instance160001

Auto-generating with External Routers

Rotary Address 01

Addressing Examples

29

MS/TP Network Number

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

30

Addressing ExamplesAutogenerating with i-Vu Open Server

Device Instance 1659303

i-Vu Open Standard or Plus

16 = Carrier’s BACnet Vendor ID

Device Instance1659307

Rotary Address 07

16593

Rotary Address 03

MS/TP Network Number is

Autogenerated.

Server Device Instance169999

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

BACnet/IP Network number 1600

Device Instance 1610103

i-Vu Open Standard or Plus

IPRouter

Server Device Instance Number 169999

16 = Carrier’s BACnet Vendor ID

Device Instance1610107

Rotary Address 07

16101

Rotary Address 03

MS/TP Network Number

Router Device Instance160001

Autogenerating with External Routers

Rotary Address 01

Addressing Examples

31

Device Instance 1659303

Device Instance1659307

Rotary Address 07

16593

Rotary Address 03

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

32

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!!

AddressingManual Addressing - Routers

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

33

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!!

AddressingManual Addressing - Controllers

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

Manual AddressingAddressing

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.

ExampleNetwork number = 50000 50000 – 40000 = 10000Controller MAC address = 22 22 appends to 10000

Device Instance = 1000022

34

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

35

Auto AddressingAutomatically configures

Routers to have unique Network numbers

Automatically configures the controllers to have unique device instance numbers

Manual AddressingManual process to give

unique network numbersManual process to give

unique device instance numbers

Recommended only if it is specified for a certain network numbering scheme!

AddressingAuto Vs. Manual Addressing

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

Multiple i-Vu systems on same LANAddressing

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.

36

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

Multiple i-Vu systems on same LANAddressing

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.

37

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

Addressing

Questions?

38

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

39

i-Vu Open Controllers & 3rd Party Systems

Special Considerations

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

40

3rd Party BMS Considerations

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 with the desired MS/TP network number.

Default Network Number

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

41

3rd Party BMS Considerations

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.

Auto Generated Device IDs

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

Thank You!

42