General procedure for diagnostics and troubleshooting
BACnet on IP 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.
The following questions can help to troubleshoot communication problems.
Faults | Possible causes & troubleshooting |
---|---|
Is the link signal available on the IP components? With switches, the link signal is indicated by a continuous or flashing LED. In all devices in the Desigo system, the Service LED is continuously ON if no link signal is detected. |
|
Are VLAN switches used on the network? |
|
Diagnostics via wireshark is not possible. | No port mirroring configured on the managed switches
|
Wireshark does not have the proper BACnet services. | Layer 2 switch is used, but without port mirroring Use a hub or configure a corresponding layer 2 switch via the web interface |
No communication between the BACnet client and the various BACnet devices. | Is a firewall available? Consultation with IT, cannot be discovered using the diagnostics tool. Firewall, UDP port configuration is not entered |
The BACnet clients cannot access the different BACnet devices on the various VLANs. | BBMD in multiple IP segments BACnet devices do not have a unique instance number BACnet devices do not have a fixed IP address (if configured as BBMD) BBMD used, but all BACnet networks are the same UDP port? |
Have you considered notes from technical documentation? |
|
Communication, speed on the Desigo network | Compliance with system topology, regarding:
|