Issue
The built in logs for troubleshooting communications from SmartStruxure ES/AS to SmartStruxure ES/AS remove the need for network captures for SmartStruxure communications. However, SmartStruxure to BACnet continues to be ideal for traditional means of network captures. The most common capture method is Wireshark when dealing with BACnet device to BACnet device communication.
Product Line
EcoStruxure Building Operation
Environment
- SmartStruxure
- BACnet
- ES
- AS
Cause
The need to troubleshoot communications issues from device to device whether this is ES to AS or vice versa. The need to troubleshoot BACnet communications
Resolution
Network captures are beneficial in troubleshooting the following cases:
- Connection issues between SmartStruxure client and AS/ES.
- If customers complain their client cannot connect to an AS/ES, a capture run from the client PC can be very useful. However, SmartStruxure uses TCP/HTTP and the payload is not easy to decode. There are no Wireshark decoders to help out, but the good news is that there is in communication logging built in to SmartStruxure that can replace the need for network captures. (See Error logs from the Enterprise Server for ES and see Error logs from an Automation Server and Enterprise Server for AS)
- Communication Status problems between servers and controllers (for example BACnet controllers).
- The location of where the captures is taken can be very important. The best place to capture is at a switch directly connected to the controller. This may be difficult because it will require putting a “dumb” hub between the switch and the controller or finding a port mirroring switch.
- When you are not receiving BACnet alarms when expected.
- When you are not receiving COV notifications when expected
- When a trendlog is trending external point
- To evaluate the health of a network.
- ARP broadcast traffic can flood networks and can create connectivity problems on BACnet/IP networks. If this is the case then a customer can take action by segmenting their BMS to a VLAN.
- Performance problems on graphics where a large number of the point displayed are BACnet
- MS/TP bus performance is poor or MS/TP device is offline
- Using a USB RS-485 adapter can permit the capture of packets on an MS/TP bus. Wireshark can then be used to decode the packet captures. This can show token passing problems as well as traffic loads.
Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.
