There are a number of ways to integrate with Reliable Controls systems. In order to view the T3 controllers you will need to have one of their Mach Pro or similar controllers on the network which acts as a gateway to transfer BIP commands to other bacnet devices on the network. Here is a screen shot of the local lan which has a Reliable MachPro as well as a number of Temco products connected, as viewed from the RC Toolkit.
Hello!
This is an old post, but I guess is the best place to post this. If not. I apologize.
Anyone have encountered problems integrating T3-TB with Reliable Controls?
Since a few months ago, the MachPro is been reporting “time out” errors when reading T3-TB points.
Values updated between controllers is incositent.
We’re using plain vanilla bacnet objects in our system so I dont now why it would work before and now not. You could do a firmware update to see if that helps. Next step would be to look at the RS485 signals themselves, use a scope which can plot A - B channels. The signal should show up as nice and square. You could capture some MSTP traffic and perhaps we can spot something from that. Here’s a blog post I did on how to capture MSTP traffic using Wireshark.
Hello Maurice!
Included is the wireshark feed. I simplify the network. There are only 3 devices on it. A MachProWeb, A T3-TB and the BACnet workstation laptop.
I did a little program on the controllers so they are trying to share data periodically. bip_wshrk_6424.pcapng (320.9 KB)
On the wireshark I could not identify any data packages exchange between controllers.
From the T3000, the MachProWeb is not discovered.
From the RC Studio side the T3-TB is shown but no data transfer is done.
Thanks!
As you guys may know, when configuring the MachProWeb, we activate the B/IP network with the #20, and al T3-TB are also configured with the same B/IP 20 network.
From the RC-Studio (Or any other BACnet explorer) I can see/edit all points T3-TB points with no issue.
But the MachProWeb cannot use said points in any program or to write into a local point to the MPW. Also it cannot display the points on the web server.
It looks like the T3-TB and MPW cannot talk to each other directly
192.168.94.17 is T3-TB-17 .
Our controller replied to the packet it was supposed to reply to.
I did not find any data packets sent by MPW to T3-TB, you need to check whether the MPW sent any data packets.
192.168.94.240 sends some who-is commands, and the T3-TB-17 replied . Everything here seems normal and working.