I’m having an issue with rs-485 communications on a T3-TB-11i. I have a Tstat10 connected to the RS-485 Sub connection. The RX led blinks on the sub RS-485 network and the TX led blinks on the main RS-485 network (nothing connected). I have the correct protocol and baud rate set up in the TB on the sub network. When I perform a search, only the TB is found. I have correct polarity and am able to connect to the Tstat10 via a RS-485 interface. I have tried rebooting and power cycling the TB but nothing seems to work.
Show a few screen shots of the network settins for both devices if you could please. In particular I would like to see the panel ID for both devices, they must be unique on each device. Typically the T3 will be the ‘gateway’ and would be set to panel ID=1. The remaining RS485 devices will be 2 and up.
In this example the T3 controller at Tab1 is set to Bacnet/Modbus ID = 1 at Tab3, the other RS485 subnet devices at Tab2 will be numbered from 2 and onwards.
Make sure all subnet devices have their respective com port setup to match what you see at Tab4 on the T3 controller.
I see that the panel numbers and Bacnet Mac ID are unique, that is good. One suggestion would be to make the MAC ID and Panel ID both the same to make it easier to remember while programming and addressing points.
I see that you are using Bacnet on the subnets. There were some fixes for that not long ago, I would give it a go to update the firmware of all your devices. Since your Tstat10 is not communicating via the T3 controller you can connect direct over RS485 to do the update. If you are having trouble you could switch temporarily to Modbus to do the update. If the device becomes unresponsive you can cycle power and update in the first few seconds after power up.
Let us know how it goes.
Good morning Maurice,
Not sure why, but without reverting back to modbus the Tstat10 device finally showed up on the subnet. Gremlins I guess.
I have one other issue, one that we have discussed in the past… I’m connecting the T3000 devices to a Schneider Electric AS. The AS is somewhat like a JACE. When I perform a Bacnet discovery the T3-TB-11i is discovered (IP) but nothing on the subnet. Any ideas?
Yep, we have some work to do in order to make the devices show up. You can read & write to them but they just dont show up in the usual trees and tools.
Maurice,
I relocated the MSTP from the subnet to the Main and now data from the Tstat10 can be seen on the T3-TB but the Tstat10 does not show up on the system tree. The bacnet tool can see it just fine.
Jim
Maurice,
I don’t know if you saw this or not…
I relocated my Tstat10 devices from the RS485 Sub to the RS485 Main so that I can share information between the TB-3 and the Tstat10 devices. The issue is now that Tstat10 devices do not show up in the system tree. I am communicating with the TB-3 over IP.
Thank you,
Jim
Hi, James. There are many factors that may cause your Tstat10 to not be detected by T3 - TB. Please help troubleshoot them one by one.
- Ensure that the baud rates of the RS485 protocols of TB and TSTAT10 are the same.
- Ensure that TSTAT10 is connected to the correct RS485 interface (T3 - TB has two RS485 interfaces, Main and Sub).
- If you are using Bacnet MSTP to connect to Tstat10, please ensure that the MSTP MAC ID of TSTAT10 is different from that of T3 - TB. It must have a unique MAC ID.
- If you are using Modbus RTU to connect to Tstat10, please ensure that the Modbus ID of TSTAT10 is different from that of T3 - TB. It must have a unique Modbus ID.
- Please ensure that the panel numbers of the two devices are different.
- If there are still problems, you can try to connect T3 - TB via Ethernet and click “Clear subnet datatbase” so that T3 - TB can execute the command to rescan TSTAT10.
And also please try to update the firmware by navigating to T3000 → help → check for updates → update firmware. While you are at it update T3000 itself in the same dialog. Here’s the links to the firmware in case you prefer to do it by direct download:
T3-TB
https://temcocontrols.com/ftp/firmware/T3_BB_LB_TB/mini_arm_rev66.3.hex
TSTAT10
https://temcocontrols.com/ftp/firmware/Tstat10/Tstat10_arm_rev65.8.hex
I’m not getting any answers back on this issue. Once again, when my Tstat10 devices are connected to the MAIN Rs-485 network I can not see them on the system tree.
Sorry for the trouble, sounds like some basic communications issue. You can contact us by email and we can remotely debug with you.
-There are many threads here on the forum dealing with communications troubleshooting.
-Look down at the bottom left of your T3000 screen, there you can see the communicatons health.
My email is chelsea(at)temcocontrols(dot)com