T3 OEM - T3 TB Bacnet communication issues

Single T3-OEM is connected to T3-TB (Bacnet RS485). TB(master) have program:

10 VAR50 = 30033AV10
20 VAR51 = 30033AV11
30 VAR52 = 30033AV12
40 VAR53 = 30033AV13
50 VAR54 = 30033AV14
60 VAR55 = 30033AV15
70 VAR56 = 30033AV16
80 VAR57 = 30033AV17
90 VAR58 = 30033AV19
100 VAR59 = 30033AV20
110 VAR60 = 30033AV22
120 VAR61 = 30033AV23
130 30033AV25 = VAR62
140 30033AV26 = VAR63

All works fine for some time, but after a while Notwork points disappear, and communication with OEM is lost.

If program is off network works without any issues.

Give it a try with a firmware update. There were some communication bugs worked out recently.

Same issues after update, t3-oem no connection:

Our recommendation is to update the T3’s firmware, latest firmware is rev62.2, I did a similar test before and it still works fine after running a few days of operation. I will test it again.

I updated t3tb to rev62.2 before testing.

I did a similar test, and it has been running for a few days without any problems, so can you help me find the version number of the T3-OEM firmware, the problem now is that the communication between the T3-OEM and the T3 is broken.

When there is a problem, check the status of the network health, clear first and then look at the RX and TX.or can we access your PC to help, it is easy for us to check what happened. chelsea@temcocontrols.com you can send me email also.


I’m having trouble communicating via BACnet MSTP between T3 controllers.
I have connected T3-Nano → T3-TB, communication via BACnet MSTP is good.
When adding a new controller, T3-Nano → T3-TB → T3-TB, communication stops.
This is done in a workbench.

Any ideas what is going on?

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.