There’s a number of settings that have to be set right to get communications going, here’s a few things you can check:
At the start of all debugging sessions you should make sure all devices have the latest firmware and T3000 itself is the latest. Do that at T3000 → help → check for updates.
I assume you are debugging a connection to a device on a bancet MSTP subnetwork as shown at Tab2.
-make sure all devices are set to the same protocol: bacnet in this case, set that at Tab3
-make sure the devices are all set to the same baud rate and leave the parity & stop bit settings at the default as shown at Tab4
-make sure all devices have a unique bacnet MAC id as its called, the network ID as shown at Tab7.
-make sure all devices have a unique ‘Panel ID’ as we call it at Tab9, it’s similar to the bacnet Mac ID but used internally by T3000 to distinguish devices.
-Make sure the Bacnet instance at Tab 6 is unique, its used by Bacnet to route packets
-Make sure the max master is 255 at Tab8, once you have everything working you can reduce this to speed up network polling.
You can check subnet communications health at Tab5
If you are debugging communications of devices on an Ethernet network at Tab1 there’s a few more things you check like the IP settings of your PC network card, temporarily disable VPNS and any wifi or virtual network ports. Let me know and I can elaborate on that here as well.
Standing by to help out more.