Typical faults and their solution
BACnet on MS/TP involves the use of a large number of components and this results in a certain degree of complexity and a corresponding vulnerability to errors.
If a problem arises in the system, it must be located in a step-by-step procedure. Always start you analysis at the lowest system. Only continue to the next higher system once you are sure that the system is operating correctly. A sketch of the topology is extremely helpful when attempting to locate problems. Create a sketch if none exists.
BACnet MS/TP devices are introduced to the Desigo system over the BACnet MS/TP IP router to the Ethernet. In other words, you consider topics from the BACnet/IP world and include it in your analysis when troubleshooting problems.
The following questions can help to troubleshoot communication problems.
Faults | Possible causes & troubleshooting |
---|---|
Check cabling prior to commissioning |
|
No communication to the BACnet MS/TP devices. |
|
New BACnet MS/TP devices are not recognized. |
|
The network does not recognize the BACnet MS/TP devices at the end of the trunk. |
|
Communication is not reliable. |
|
Communication is slow. |
|
Communication no longer restarts after a power outage or communication no longer starts after a power outage on the BACnet/IP router. |
|
BACnet networks |
|
Have you considered notes from technical documentation? |
|