We are using a T3-LB for lighting control and have connected it via ethernet to our process network. The IT department gets alarms regarding port dropouts and reconnecting. We have updated to the latest firmware and still it drops out. It is now disconnected until we can fix the issue. Any ideas for us to try? Thanks.
Hard to say what might be going on from the description so far. I know that the ping task on the T3 series is a lower priority task, you could set the IT department master to give the ping a couple retries before geenrating the alarm. If you can change your setup to poll a modbus or bacnet packet that will run as a higher priority task.
Have a look through the modbus register list, there is one register dedicated to monotiring network connectivity, it increments slowly then wraps around to zero and restarts. Also there’s the number of seconds since reboot, I believe there’s a register for that as well. You can see the modbus register list under T3000 → tools → modbus register list.
Been an ongoing issue for years. Cannot understand why stable networking has not been resolved. Many people have brought it forward. Whether it is IP or rs-485, this has been a lacking problem. Single panel installation seems to be the fit.
All sites I have installed have networking issues. Firmware updates fix some things but break others. The QA process needs some help.
We spend a huge amount of time making sure our gear is reliable in hundreds of environments. If you are experiencing communications issues the first step would be to update the firmware of your device, and also T3000 while you are at it. If you’re still expeiencing issues we’ll work closely with you till its solved. We dont stop till you are 100% satisfied.
Maurice