Knowledge Base
cancel
Showing results for 
Search instead for 
Did you mean: 

Steps for replacing a BACnet B3 controller and things to consider.

Issue

Steps for replacing a BACnet B3 controller and things to consider.

Environment

Continuum Site

Cause

Steps for replacing a BACnet B3 controller and things to consider.

Resolution

Steps for replacing a B3 controller and things to consider.

Use these steps when replacing a B3 controller from brand new stock, it is relatively straight forward.

  1. Physically disconnect power and MS/TP data cables from existing B3 Controller.
  2. Remove existing B3 Controller.
  3. Install replacement B3 Controller.
  4. Pull the battery tab on replacement B3.
  5. Connect MS/TP data cable to the replacement B3 controller.
  6. Connect power to the replacement B3 controller.
  7. Edit the B3 controller object in Continuum on the infinity side.
  8. On the Runtime tab enter the Serial Number of the new replacement B3 controller and click Apply.
  9. Click refresh until B3 controller returns Online.
  10. Reload the B3 Controller.
  11. Verify existing points and programs are running correctly.
  12. Perform a “Backup to Flash” operation on the B3 controller.
  13. Perform “Send to Database” operation on B3 controller from BACnet view.

One scenario for example is the Replacement B3 controller came from a different job that has previously been programmed and has a valid flash backed up onto it. If installed on the new network, when powered up will start trying to communicate with
controllers it has routing tables for. Could potentially cause issues on the new network. It is suggested that if you are replacing with a previously used controller from an old site with a valid flash backed up is to flush the controller out before applying to the new network. From a test machine with a test DB bring the controller online, this will require a BCX to do as well. Once the B3 is learned in and online, perform a reload to the controller and then a backup to flash. The only thing that will be reloaded will be the system variables.

Another thing to think about, is lets say you've already replaced the B3 and sent it off to repair. You've gotten it back and now want to put it back to its original location. That one is very simple and following the replacement steps above will suffice. Just remember that step 8 above you would make sure the Bacnet Device ID and the serial number match for the original unit integration. But if you wanted to add a new B3 controller to the same site and use the repaired B3 as a new installed controller, just remember that the previously replaced B3 will have
the Bacnet Device ID of the repaired B3 and you'll have to make sure that when manually creating a new B3 with the repaired B3 you'll have to make a new Bacnet Device ID that is unique.

Rules to remember:

  1. Flush out used B3 controllers before adding to an existing mstp network or replacing a defective B3
  2. Bacnet Device ID's must be unique for each given bacnet network


 

Tags (1)
Labels (1)
Version history
Revision #:
1 of 1
Last update:
2 weeks ago
Updated by: