I have a TB-8i with a Neptronic HROB20 humidity controller on MSTP MAC 20, with an instance ID of 120, and a Contemporary Controls BAST-221C-B2 Thermostat on MSTP MAC 15 and a instance ID of 15. Port is at 38400 on all devices, comms are good:
The Thermostat on the other hand will NOT show up under the device tree in T3000, and while I can send and poll using YABE launched from the T3000 application, But the YABE on my laptop on the same subnet (Windows 11, YABE version 2.10) can SEE the devices, but the WhoIS fails every time. Also, the variables do not update reliably.
So, two questions: 1.) Did I miss a step with the thermostats? 2.) How the hell do I write to the variables? I can read AI’s, AO’s, BI’s, BV’s, and MSV’s, but cannot write to them from the T3000 interface, whether it is in auto or Manual mode. I am assuming that I am doing something wrong. I have just ordered two TB tiny’s to use as BACnet routers as opposed to the Contemporary Controls BASRT-B’s that I normally use, as I have a location that we want to add 100+ TB tiny’s as routers. For an HMI, we use both a Weintek HMI as well as BASView 3.
If the firmware is not up to date, please update it to the latest version first.
For the thermostat, its MAC address 15 and Device Instance 15 are the same. This can sometimes cause unexpected issues in BACnet networks. Please change one of them so that the MAC address and Device Instance are different, then try again.
Under normal conditions, the variables should be writable. The TB will forward the BACnet write commands to the MS/TP device.
Hi Lijun, thanks for the quick reply! I did update the firmware, but I was already quite up to date. The thermostat is quicker to respond now, but unfortunately, when I try to discover anything from YABE on the network, the mstp devices do show up, but will not acknowledge or return points:
I hope that you get it figured out - I too really wanted to be able to use the TB as a BACnet router, but after a lot of effort and wireshark samples, I just came to the conclusion that this wasn’t ready for a commercial deployment - too much risk. I never heard back from the team since I brought this up to them in March, so I moved on.
So I have updated all of my devices, by adding a 1 in front of its MAC address, so ID 15 has a bacnet id of 115. I have updates of all network points within a few seconds of modifying the point on the device. When I try to update the setpont from the variable screen, by putting the mode to manual, and setting the SP to a different value, it does not update that value on the device. When I set it via YABE in the T3000 tool, it does update the value on the controller, but tells me it has not:
Any Thoughts? I am trying to cover alll of the possible issues here, and am using two different BACnet certified devices in order to keep all of this BACnet compliant.
Ok, so I have two new T3-Nanos, both on the latest firmware, I cam map my variables through from my Contemporary Controls TSTAT, and I can poll those over BACnet to other management platforms no problem. However, when I write to those values, it does not work. I have connected to the TSTAT with the RS-485 to USB adapter that I bought from Temco as well, and I can read and write to the TSTAT with the exact same serial setup as on the Nano, but I still have no ability to write to values THROUGH the Nano. Is there something to be modified?
Lijun will study your report here and get back to us shortly.
Our usual tool for debugging these sort of unexplained communications problems is wireshark for bacnet and modbus over ip, also it can be used for mstp over rs485. For modbus rtu we use mbpoll and docklight.
Heres a detailed blog I did for debugging Bacnet MSTP using wireshark:
We usually use Yabe for the basic tests, and everything goes smoothly. The following is the result of my test using the software from Contemporary Controls, and it can indeed be written to normally. Are you writing about AV or another object? Not all parameters can be written. Could you provide me with more details?
