I ordered a T-balancer from MCubed in early May, and it still hasn't arrived. I thought I'd try it out 'side by side' with the TMS-200. But the TMS-200 is actually here, whereas the T-balancer is in shipping limbo.
There are a few North American-based companies that may have the T-balancer, though, if that is something you want to look into. If I realized that at the time I wouldn't have ordered direct from MCubed.
As an aside, I didn't reconnect the ATX pass through power switch to my TMS-200 after I disconnected during my Indigo Extreme reflow process, because it wouldn't even boot (no power to pump = no boot, for safety, I suppose.) I haven't bothered to test it now that my system is operational, but I think they may have resolved part of the problem with certain settings.
For instance, if you use a flow meter, you can set it to shutdown the system of the flow < a set amount. But in the first few seconds of the software initializing it reads the flow as 0, and this initiaties a shutdown. However, at some point they added a delay option, so if you use the default 60 second delay for your system, that gives the software enough time to initialize, get the flow reading correctly, and it automatically abandons the shutdown (assuming no other shutdown conditions are fulfilled.) After using it, it only takes 5 seconds or so to get the flow reading and cancel the shut down - no input from the user is required. You just get a quick flash of a window saying 'shutdown because flow < X' and then it goes away.
What they should do is just not activate any shutdown rules until 10 seconds after the software connects with the com port.
I think without this delay option I could see users having problems. But I don't see why it wouldn't work better now. But my TMS-200 is in a tight spot, and I'm semi-lazy, and don't really want to connect my ATX power pass through cable unless I have to go in there for something else.
Bookmarks