Two BACnet MS/TP devices with the same MAC address can make a building automation network behave unpredictably. A controller may appear to come online and then disappear, devices may fail discovery, or traffic on the trunk may deteriorate. But a missing BACnet device does not automatically prove an address conflict.
This practical guide explains how to recognize a possible duplicate, separate it from wiring problems, and plan a verified correction. If you have a supported seven-switch address bank, our BACnet MS/TP DIP Switch Address Calculator can show the binary pattern after you confirm the exact device profile.
What Is a Duplicate MS/TP MAC Address?
An MS/TP MAC address identifies a device on a particular BACnet serial data-link segment. Two devices on the same segment should not share that address. Johnson Controls warns that duplicate addresses can lead to severe communication problems, including devices staying offline or communication stopping altogether.
A MAC address is not the same thing as a BACnet device instance. The device instance is a separate object identifier used in BACnet communications and must also be managed for uniqueness within the BACnet internetwork. Changing only a physical MAC switch does not necessarily solve a duplicate device-instance problem.
The correct address range depends on equipment. Some controllers accept 0 through 127, while other specific products reserve values or use 1 through 127. The seven-bit binary calculation does not replace a model-specific installation chart.
Common Symptoms of an Address Conflict
One symptom is that one of two devices appears in the network supervisor while another expected controller does not. On some installations, the visible device at that address may change intermittently, leading technicians to believe a controller has an unstable power supply.
Other symptoms can include intermittent BACnet communications, timeouts, discovery failures, token-passing issues, or all communications on a branch becoming unreliable. These symptoms are not exclusive to address collisions; a reversed pair, bad termination, or incorrect baud rate can create a similar experience.
Because the symptoms overlap, collect evidence from the supervisory interface, controller LEDs, and installation records before changing addresses. A systematic sequence is safer than repeatedly flipping DIP switches until the network appears stable.
- A newly commissioned controller does not appear.
- A familiar address appears online inconsistently.
- Multiple controllers drop offline after adding a device.
- A controller reports one MAC address while the plan shows another.
- BAS diagnostics show duplicate device identifiers or repeated communication errors.
Check the Device Address Plan First
Start with the documented list of devices on the physical MS/TP trunk. Record each controller’s label, model number, intended MAC address, actual MAC address, and location. Include routers or supervisory devices when they occupy a MAC address on that segment.
Compare the list for repeated values. Be cautious with address 0 and other reserved ranges because individual devices or vendor systems may have special commissioning rules. Johnson Controls’ Verasys documentation, for example, specifies system-specific address reservations that differ from a generic seven-bit representation.
If the network uses both wired and wireless segments, follow the product guide for any mode-select switches. An eighth physical switch may enable wireless operation, select a protocol, or control another feature rather than encode the MAC value.
Inspect the DIP Switch Bank Carefully
Before touching a field controller, identify its exact model and download its current official installation instructions. Document the existing positions with a clear photo that includes switch numbering and the ON marker, then compare the actual pattern with the manufacturer’s binary weighting.
On a straightforward seven-bit LSB-first address bank, SW1 contributes 1, SW2 contributes 2, SW3 contributes 4, SW4 contributes 8, SW5 contributes 16, SW6 contributes 32, and SW7 contributes 64. For example, 37 uses 32 + 4 + 1. But physical numbering and valid address ranges are device-specific.
Do not change a spare or eighth switch without knowing its function. On the Johnson Controls SC-Connect product family, the manufacturer documents using the first seven switches for MAC address 1 through 127. That statement should not be generalized to every Johnson Controls device.
How Technicians Confirm a Suspected Duplicate
Johnson Controls’ Verasys troubleshooting documentation recommends checking whether an address remains online after a suspect device is removed from the bus under an appropriate service procedure. If the address is still present, another device may be using it. This is a diagnostic step for qualified personnel, not a reason to disconnect arbitrary live controls.
When the entire trunk is unstable, authorized technicians may isolate sections of the bus and test progressively. The product manual and building maintenance plan should determine the sequence so that access, life-safety, and operational systems are not disrupted unexpectedly.
Record each change and observation. If a duplicate is confirmed, assign a permitted, unused MAC address according to the network plan and the specific product’s settings, then recheck communications after the manufacturer-prescribed application procedure.
Rule Out Physical-Layer Problems
An MS/TP network uses physical cabling whose integrity is just as important as its addresses. Reversed polarity, disconnected conductors, ground-reference issues, inappropriate branches, signal interference, or incorrect end termination can prevent normal communication.
On a conventional linear trunk, correctly matched termination normally belongs at the physical endpoints. If each intermediate controller has a selectable 120-ohm resistor enabled, the combined load may affect performance. Read our RS-485 Termination DIP Switch Guide for a separate explanation of this electrical setting.
Check each device’s power status and communication LEDs according to the vendor instructions. Also verify the actual configured baud rate and protocol settings, not just the values shown in an old wiring schedule.
Duplicate MAC Address vs Duplicate BACnet Device Instance
A MAC collision occurs locally on an MS/TP segment and affects data-link communication. A duplicate BACnet device instance can affect device discovery and identification across the BACnet internetwork even when the devices are reached through different physical segments.
Johnson Controls’ BACnet integration troubleshooting guidance describes inspecting duplicate device identifiers from supervisory diagnostics. Therefore, a controller might have a unique MS/TP MAC address yet still be involved in a separate device-instance conflict.
Do not fix a device instance duplicate by randomly changing DIP switches unless the product explicitly maps those switches to the device instance. Check whether the instance is set in software, generated from a formula, or managed by a supervisory configuration interface.
Example: Two VAV Controllers at Address 21
Suppose two VAV controllers were mistakenly commissioned with MS/TP MAC address 21 on the same trunk. In a simple binary scheme, address 21 corresponds to weights 16 + 4 + 1. Both controllers would therefore share the same address bits even if their names and physical locations were different.
The address plan should identify a free, valid replacement MAC value for one controller. The selected value must be permitted by that model and by the site’s addressing conventions. Do not assume that 22 is free merely because it is the next number.
After an authorized change, recheck controller communication, supervisory discovery, and the address inventory. Also confirm the BACnet device-instance identifiers and any associated graphics or points whose mapping may require validation.
Preventing Duplicates During Future Commissioning
Use a central register that includes the trunk name, controller model, physical location, MAC address, BACnet device instance, and installer notes. Update it whenever a module is replaced. An outdated spreadsheet is one of the easiest ways to repeat an address inadvertently.
Commission a new device with its addressing verified before connecting it to an established trunk, as directed by the manufacturer’s field procedure. Johnson Controls’ Verasys integration guide specifically calls for assigning a unique MS/TP address before connecting the controller to its system bus.
Make sure replacement components do not arrive with the same factory default address as existing nodes. Provide future technicians with both the as-built wiring diagram and the equipment-specific switch diagram rather than only an address number.
Related Resources
Use the BACnet MS/TP DIP Switch Address Calculator to visualize binary patterns for its documented profiles. For more general switch orientation, see How to Read DIP Switch Positions Correctly.
For communication-layer background, our RS-485 primer explains the bus technology. Note that Modbus and BACnet use different addressing conventions even if both share RS-485 electrical principles.
Frequently Asked Questions
Can two BACnet devices share the same MS/TP MAC address?
Not on the same active MS/TP segment. Each participating device requires a unique local data-link address as supported by its equipment profile.
Will a duplicate MAC address always stop the whole network?
No. The symptoms vary with device behavior and network conditions. It can cause intermittent visibility, communication degradation, or a severe outage.
Does BACnet device instance equal MAC address?
No. They are distinct identifiers. Some devices relate them through a manufacturer formula, but that cannot be assumed for all equipment.
Can an RS-485 termination fault look like a MAC conflict?
Yes. Poor cabling, reversed connections, bad termination, and serial configuration mismatches may also make controllers appear offline.
Does a seven-bit calculator identify duplicate addresses automatically?
No. It converts an entered value into switch positions. Duplicate detection requires an accurate device inventory or appropriate network diagnostics.
Sources and Further Reading
- Johnson Controls Verasys: setting a device address
- Johnson Controls SC-Connect: MAC address settings
- Johnson Controls: BACnet System Integration Troubleshooting
- Johnson Controls Verasys: connecting BACnet devices
Editorial note: This guide is educational, not a substitute for an equipment service manual. Review electrical safety requirements for the specific device.