I upgraded the firmware on a TSTAT10 to Tstat10_arm_rev65.8.hex.
I got the message that the firmware load success, but now I can’t communicate with the TSTAT via the jack.
Hi @abarnes-6561, have you found your solution for this? Hi @maurice, can you please help on this? Because I faced the same issue as well after flashing the latest firmware Tstat10_arm_rev65.8.hex to my TSTAT10. I can discover the TSTAT10 using YABE but no object was found.
Is it possible that we have to used older firmware? If that’s the case, How do I identify the particular firmware to be used?
The only way to fix a bricked device is to perform the unbricking procedure. Cycle power and use ISPTool to flash in the first 5-10 seconds after power up. The backlight should be blinking with two quick blips, repeating every second or so in this bootup period. If you dont get the two blips during power on then we’ll need to get the device onto the bench for furher study.
Gnerally speaking you dont need to download firmware mannually, use the T3000 → help → check for updates → download firmware & update. This will make sure to load ONLY the correct firmware for your particular hardware. There’s two types of Tstat10 devices out there now, the orginal version based on the ST cpu and the latest version based on the ESP32. T3000 will check which version you have and load only the appropriate firmware.
You can learn more about the unbrick procedure here:
Yabe can only find bacnet objects which are filled in with a range and engineering units. The default is unused so Yabe will not see them.
The failure to communicate using the jack is not due to a firmware update. I have tested versions 65.8 and above and there is no problem. The jack and the wiring terminal are connected. If there is no communication, please check whether the plug is plugged in tightly or the cable is damaged.
Yes. I downloaded the device using the following procedure:
But after successful flashing of the firmware, we recycled the power and the Modbus or BACnet were not discoverable.
I see that the device has been scanned by YABE. If no object is found and I observe that the log shows “garbage”, it is likely that the communication data was parsed incorrectly. Restarting YABE and trying again can often solve the problem.
We are using this converter purchased from Temco Controls website.
We tested the continuity is ok. We even manage to flash the firmware using this cable. Since that’s the case, I believe the converter & cable is not damaged.
Hi @Lijun, I tried your suggested method with failure
I even tested the Net+ & Net- continuity to the jack with multimeter as well. It is connected with no broken circuit. I’m using 24VDC power supply to power it up. Is there any difference if I’m not using AC power? From What I see, the TSTAT10 is using the REV5 board.
I realized that every time when I need to flash the firmware, I have to wait for the process to reach “Reading device version information!” step, then I have to recycle the power for the TSTAT10 to boot into ISP mode. Lastly only I can see the process of flashing the firmware. Is this normal? I presume that, since I can flash the firmware multiple times already, the connection to Modbus or BACnet connection shall be the same. Please correct me if I’m wrong. Thanks
From the interface you scanned, there is BACnet MSTP data at COM3 115200 baud rate. If you wait patiently, it should appear in the list.
When your protocol is BACnet, you can only update by restarting. At this stage, it will not jump directly to modbus and continue to update. We will add the function of updating under BACnet protocol later.