Issue
Problems adding i2 or b3 controllers to systems and causing the network to go down or devices to not learn on.
Product Line
Andover Continuum
Environment
- i2 Controller
- b3 Controller
Cause
Duplicate ID's, incorrect baud rates or faulty controller
Resolution
Infinet and BACnet field controllers have the capability to autobaud and auto correct duplicate ID's on a network.
They do this by listening to the network on powerup and determining what Baud Rate and currently operating controller ID's are on the network. If an existing controller is on the network and the newly added controller has the same ID assigned, the new controller will zero out its own ID so as not to cause a network problem with duplicate ID's. Then learning or manually commissioning the controller will give it a unique ID.
It is therefore critical that when adding a controller to a network, that the controller is connected to the network before the controller is powered up. Failure to do so could cause network problems such as duplicate ID's or conflicting baud rates which could bring the network down.
If the new controller causes these types of problems it is recommended to power down the suspect controller(s) and re-power them to eliminate these issues. Run acctrace when the learn is being done and there will be an indication of what is happening. Send a controller error log to PSS.
If nothing else works even with a clean database then replace the Master and if that works send the controller in to repair.
