The communications health shows under 50%. It’s possible there is a problem with the cabling, perhaps some of the RS485 hardware is damaged, or GNDing crossed up between devices. If you have another T3-TB unit around you can try swapping hardware.
Check the T3 RS485 hardware using your PC and a USB to 485 converter. Use T3000 and connect from your PC directly to the T3 over RS485, just the one single device and your PC. If you dont see 100% good packets try swapping with a known good T3 controller.
If you can provide a sketch the network that would help us understand better.
Also I don’t think it’s the cables because I tried using a brand new cable layed on the floor between one TSTAT10 and the T3 controller. Despite having a new cable and only two devices plugged I still had the same problem. I think the RS485 port has been damaged.
I can feel the frustration and we’ll get you there. I assume that 100% you have checked out that RS485/power cable. One single device with 24vac (I assume) crossed up will cause exactly the issues we’ve been discussing.
You can test any single device on its own, direct to your PC and see if the hardware is OK or not. Get a known good connection going and move on from there.
Hi Maurice, I have to say that yes i’m frustrated right now, but I have nothing against you or your team. I really appreciate the time and effort you’ve been giving me and I got to thanks everybody at Temco.
So this evening something happened and I don’t know why. I did basically no change since my last post and two of the TSTAT 10 have showed up on the tree but the symbol is not the one of the TSTAT 10 and I’m unable to connect to it.
Here’s screenshot
I’ve tried to push the firmware to both TSTAT and it changed nothing.
It’s getting late and tommorrow I’ll check with wireshark to see what’s going on.
I think we need to connect with you over a remote connection and help out in person. We use anydesk and also the open source rustdesk for remote connections.
My guess at the root cause is the poor communication quality on the RS485 MSTP bus, too many lost packets.
You can send an email to me, fandu@our company suffix.
Or send to sales email and we will set this up.
As Fandu mentioned, we’re available to help via remote connection. Looking at the screenshots there you have a lot of packet errors. They way to diagnose that quickly is on the bench, connect direct, one by one to the devices and add more in steps. Monitor the network health as you go. Then do the same on the actual RS485 cable.
The other tool is the scope, rather than those two plots you showed earlier you can plot the A - B channel and make sure the waveforms are nice and square. Any single device in the network with 24VAC crossed over or poor grounding will cause problems.
And wireshark as you tried already, with a bit of sleuthing there should be some clues there.
Well I found something.
My 24VAC source was definitely a big part of the problem. As soon as I use it every single problems listed here happens. So I bought a 24 VDC powersupply with a filter integrated. Now I got a way better communication and way less packet issues, but I still got some problems listed above, like the devices won’t show in the tree and I got ghost devices showing up. I emailed Fandu last week and I think it might have ended in it’s junk box.
Well most of our gear does indeed get installed in a 24VAC environment. If you are having trouble with communications when powering with 24VAC, that most likely will be due to 24VAC being crossed up somewhere in the system. Any single device with the AC hot and the neutral crossed over with respect to the other devices will have a big impact on communications.
If you are STILL getting communications issues with your new DC supply Fandu will work with you to get to the bottom of it. Our usual tools for debugging at this point are still the wireshark and scope whcih you are familiar with by now. We dont stop till we get to the root cause.
