CO2 Bacnet TCP/IP status showing offline intermittently

#1

T3000 offten show that devices are not connected. Usually there are some CO2 sensors unavailable, but sometimes T3 controllers are offline too. Some times devices start responding if you try to connect. I use Bacnet TCP/IP. Have anyone experienced similar problems? May be this is bad network wiring/cables? Any ideas how to troubleshoot that, there to start?

(upload://blYE3Mfc9DcXBTRFFSZEQy8T7jb.png)

p.s.Firmware and software is up to date

1 Like

#2

I will try to repeat this problem , and will reply you ASAP.
I think there is something wrong with the scanning command , It is using UDP broadcast to detect each device status .
Thanks!

1 Like

#3

Additional info:
Looks like *.27 and *.28 are offline, and this may be because they are powered off, but other devices replies sometimes.

Ping statistics for 192.168.30.85:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 44ms, Average = 37ms

C:\Users\AB>ping 192.168.30.86

Pinging 192.168.30.86 with 32 bytes of data:
Reply from 192.168.30.86: bytes=32 time=68ms TTL=126
Reply from 192.168.30.86: bytes=32 time=36ms TTL=126
Reply from 192.168.30.86: bytes=32 time=40ms TTL=126
Request timed out.

Ping statistics for 192.168.30.86:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 68ms, Average = 48ms

C:\Users\AB>ping 192.168.30.95

Pinging 192.168.30.95 with 32 bytes of data:
Reply from 192.168.30.95: bytes=32 time=48ms TTL=126
Reply from 192.168.30.95: bytes=32 time=53ms TTL=126
Reply from 192.168.30.95: bytes=32 time=21ms TTL=126
Request timed out.

Ping statistics for 192.168.30.95:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 53ms, Average = 40ms

C:\Users\AB>ping 192.168.30.96

Pinging 192.168.30.96 with 32 bytes of data:
Reply from 192.168.30.96: bytes=32 time=54ms TTL=126
Request timed out.
Request timed out.
Reply from 192.168.30.96: bytes=32 time=26ms TTL=126

Ping statistics for 192.168.30.96:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 54ms, Average = 40ms

0 Likes

#4

By the way, now all looks right, only *.27; *.28 are offline, so i think i need to check them on site.

0 Likes

#7

hi, we have fixed a bug which cause a task to write the eeprom too frequently, please update your firmware and see if this can help to solve your problem, The newest firmware version is rev39, it is on our ftp now,
we will connect many devices and do advanced test to try to duplicate your issue, and will show the test result soon.

0 Likes

#8

Great, I will do update and post results.

0 Likes

#9

Updated all CO2 sensors, now list looks better.

0 Likes

#10

System became stable now. All devices are always online, no ping ping timeouts.

0 Likes

#11

Could you please install wireshark and do a capture of the traffic.

0 Likes