Koolance TMS-200 testing results / review

[Kibbler]

Should work fine, make sure youve checked the box corresponding to tje pump channel in the settings page

[Waterlogged]

I finally got my rig done and I hooked up my MCP-655 "bling bling" pump to it and it won't report the pump RPM, is it me or does it just not work?

Is that a Vario or a "B" model? If it's a Vario, there's no tach output at all and RPM's are not readable. If it's a "B" something is either not connected right or the tach circuitry may not be working.

[Ketzer7]

If you are missing the RPM tach lead on your pump, and are feeling adventurous, you can try adding one yourself.

Scroll down this thread and take a look at the instructions in there for adding the RPM lead to the circuit board.

http://www.xtremesystems.org/Forums/...=234698&page=2

I believe his was a Vario in that thread FWIW. If not, he also mentions that Laing could do it for you if you send the pump in..

[ohms]

I'm pretty sure its not a vario because i don't have the red dial on the backside and I do have the RPM lead plugged in.

[Grinder]

So its "safe" to get this now?

Just wondering

I am wondering the same thing.

Another thanks to dsumanik for the thorough review. And to Tim for keeping us updated. Just ordered the TMS-200 to give it a whirl.

I have an Aquaero for temp and fan monitoring/control, but it's impossible to get a new one in the US right now, so wanted something different. The Alphacool looked interesting, but couldn't find much info on it, and as far as I could see, the manual is only in German (maybe that's only the online version? ). So, due to the info in this thread, went with the TMS-200.

How did you make out? What is your personal impression compared to the Aquaero?

Thanks in advance

[ABalthazor]

I recently installed a TMS-200, about a week ago. Previously I was using a Koolance RP-1000 to control my primary 4 x 120mm fan / radiator, with sensors to my CPU, one of my GPUs, and one for ambient. I'm using the latest TMS-200 software, 2.1.26, and my board revision was 2.5 or something like that.

When I installed the TMS-200 I added a flowmeter, added an in-line water temp sensor, and had four other sensors going to CPU, one for each of my two GPUs, and one for RAM.

My impression so far is fairly positive, although I haven't used any of the other options currently on the market. I went for the TMS-200 as my initial choice because, of the competing offerings, it seemed to have gotten the most recent support. The T-balancer software, for instance, hasn't been updated since 2008, and that is labeled an 'alpha' version.

There are definitely a few areas for improvement. Starting up the TMS-200 software requires an admin prompt if using UAC on Vista or Windows 7, even if the program starts up at logon. I worked around this by making it a scheduled task set to run with highest priveleges; I found I had to give it a 30 second delay to start after logging on, otherwise the program would start but the tray icon would be missing. The 30 second delay fixes that.

I set the TMS-200 to control my pump speed based on water temp, and maybe 90% of the time upon reboot and logon the pump is controlled correctly. The other 10% of the time the pump starts at max power and remains there until manually set back to 'Auto', which sort of defeats the purpose of 'Auto.' Fortunately reboots are fairly infrequent with Vista / Windows 7, so this issue rarely presents itself.

One option the TMS-200 lacks when compared to the T-balancer is the ability to control a fan through a group of sensors. The TMS-200 limits you to controlling a fan header by one sensor only. You can use the same sensor for all three fans, or three different sensors for each of the three fan headers, or any combination; but you can't, say, have a fan controlled by the highest temp sensor between CPU and GPUs.

I installed the TMS-200 in a 5.25 bay using an internal USB header, and haven't had any com port issues; apparently this is an issue with some users on earlier versions of the software. I did have an issue with the ATX pass-through power switch and the TMS-200, particularly during my Indigo Extreme reflow session. I ended up just removing that. The TMS-200 software does have an 'OS shutdown' option when defined alarm conditions are met (as opposed to the hard-off provided by the ATX passthrough power switch.)

One minor annoyance with the com port interface is that when the software initiatizes after a reboot, it has to do a 10 second 'com port scan' before it becomes operational. During this time you can't move or minimize the window, preventing my scheduled task from starting minimized. Just a minor issue, but something I noted.

I sent in feedback regarding this to Koolance. I also suggested LCD keyboard and Windows Gadget support, as well as the ability to read temps from third party programs like RealTemp. I wouldn't hold my breath though; Koolance replied to some of my suggestions by stating that they had limited programming support but that their software code was on the website if users wanted to modify it.

Hopefully this doesn't mean that software support for the TMS-200 has ended.

So far, though, I'm happy with the interface, and it lets me run my system a lot quieter than previously. I particularly like the ability to control my pump speed based on a sensor, and to customize the fan profiles to my liking. Now my computer is so much quieter I'm noticing my hard drive noise more... I'll have to figure out a way to silence them better.

[astrodanco]

So far as I know, nothing has changed with the TMS-200 for many months now. I was going to suggest visiting the Koolance support forums and reading up on it, but I see that they're down for some reason.

I have a TMS-200 + EB200 here on my system. It works okay. It's actually a fairly good piece of hardware. It appears to me that it's just the software that lacks. I have it driving two D5 pumps, seven fans (some w/splitters), an FM17 flow meter, a water temperature probe and two air temperature probes.

Some motherboards have USB problems such that they don't consistently communicate with the board. Using a separate pci usb card can solve that problem.

I get the impression that Koolance have abandoned the TMS-200. They don't appear interested in doing anything further with it. Anyone wanting to do anything to support it themselves will either have to dig up an ancient VB6 compiler or start more or less from scratch.

[Grinder]

I recently installed a TMS-200, about a week ago. Previously I was using a Koolance RP-1000 to control my primary 4 x 120mm fan / radiator, with sensors to my CPU, one of my GPUs, and one for ambient. I'm using the latest TMS-200 software, 2.1.26, and my board revision was 2.5 or something like that.

..snip..

So far, though, I'm happy with the interface, and it lets me run my system a lot quieter than previously. I particularly like the ability to control my pump speed based on a sensor, and to customize the fan profiles to my liking. Now my computer is so much quieter I'm noticing my hard drive noise more... I'll have to figure out a way to silence them better.

Thanks for the detailed comments It sounds like there is still trouble with the hardware based emergency shutdown (part of the reason I want it).

So far as I know, nothing has changed with the TMS-200 for many months now. I was going to suggest visiting the Koolance support forums and reading up on it, but I see that they're down for some reason.

..snip..

I get the impression that Koolance have abandoned the TMS-200. They don't appear interested in doing anything further with it. Anyone wanting to do anything to support it themselves will either have to dig up an ancient VB6 compiler or start more or less from scratch.

Yes, I tried the forum before posting here. Sounds like another potential BigNG. I'm almost tempted to go BigNG and see if I can work out the software issues. However the Koolance is available from NCIX in Canada, while I'd have to order an Aquaero from Europe or a BigNG from US or Europe.



Thanks for the info!

[rambler358]

I'll concur that it's working pretty good for me as well. But it looks like further software updates won't be coming, despite what Koolance said in their forums a while back. ABalthazor seems to pretty much confirm that above.

Also, the TMS-200 seems to only support certain fans. When not at 100% my Coolermaster R4 fans would not work at all. When my Corsair RAM fan is not at 100%, RPMs are not displayed but the fan is still controlled. No issues with Koolance fans however.

[astrodanco]

I'm using Gentle Typhoons with mine. They work well.

The TMS-200 uses PCM to control fans. Not all fans like that. Some make annoying clicking noises when PCM driven. I had some Panaflo fans that didn't like PCM at all.

[ABalthazor]

Also, the TMS-200 seems to only support certain fans. When not at 100% my Coolermaster R4 fans would not work at all. When my Corsair RAM fan is not at 100%, RPMs are not displayed but the fan is still controlled. No issues with Koolance fans however.

And I'll concur with this. I have a Kinston HyperX RAM fan that does the same thing; it only shows RPMs at 100% speed. It can be controlled and run as low as 50%, but just displays no RPMs at anything less than 100%.

I'm running 4 x Koolance 12025HBK on one header (1.12A total), and one 12025HBK on a second header, and those have no issues displaying RPMs, even running at 10%.

I hope Koolance continues to support the product, but I'm not optimistic. There is certainly room in the market for currently supported software controlled fan/pump controller.

[ABalthazor]

Thanks for the detailed comments It sounds like there is still trouble with the hardware based emergency shutdown (part of the reason I want it).

Yes, I tried the forum before posting here. Sounds like another potential BigNG. I'm almost tempted to go BigNG and see if I can work out the software issues. However the Koolance is available from NCIX in Canada, while I'd have to order an Aquaero from Europe or a BigNG from US or Europe.

Thanks for the info!

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.

[ABalthazor]

Koolance has had some issues with their website since the beginning of the month, including their forums. The community activity there is small, but they do have users that discuss the TMS-200. No power users releasing software updates, unfortunately.

[rambler358]

I have the ATX power pass-through connected on my TMS-200, and Koolance seems to have worked out that previous issue now.

[rambler358]

Koolance has had some issues with their website since the beginning of the month, including their forums. The community activity there is small, but they do have users that discuss the TMS-200. No power users releasing software updates, unfortunately.

That's because Koolance used out-dated VB6, and there doesn't seem to be anyone using that anymore.

But I also heard rumor that Koolance is working on some other form of TMS, and that could be the reason they've stopped TMS-200 development.

[ABalthazor]

That's because Koolance used out-dated VB6, and there doesn't seem to be anyone using that anymore.

But I also heard rumor that Koolance is working on some other form of TMS, and that could be the reason they've stopped TMS-200 development.

Well, it would be great if they allow any new products' software be backwards compatabile with the TMS-200, but I wouldn't hold my breath.

Would be nice to see a supported product on the market, in any event.

[Grinder]

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.

Sorry to hear it's taking so long, and thanks for the tip! I double checked NCIX, the only Canadian source I could find for the TMS-200, and it isn't in stock, saying 3-6 weeks...

When yours finally arrives and you have had time to evaluate, you can send me the loser

I like the relative price, availability, and capabilities of the Koolance, but it sounds like they still haven't got an OS independant shutdown mechanism. i.e. the software needs to be running on the pc.

[astrodanco]

it sounds like they still haven't got an OS independant shutdown mechanism. i.e. the software needs to be running on the pc.

It WILL do a hardware power button style shutdown of my machine. It takes it's time about it, but it does do it. What it will NOT do for me is a proper Windows (e.g., OS level) shutdown. Not just when the software isn't running properly of course, but even when it is running properly. The OS level shutdown feature just doesn't do anything here -- other than cause some extra added delay as it eventually reverts to a hardware power button style shutdown.

You can tell they didn't put much thought or effort into the software. It's very light weight demo quality, if that.

One of my main beefs with the software is "auto-startup." The software is written as a monolithic program that is started only once someone logs into the machine. It should be written so that it has a core service that communicates with the board and a separate user interface that communicates with the service. Then the service would be made to start when windows starts. It is as if they thought the software was used only for bells and whistles pretty picture type monitoring and forgot all about the need to be able to do an OS level shutdown when no one is actually logged in at the time...

The USB interface is also problematic for some people. It's done using a prolific driver and a USB to serial converter. When I first got this board the software and the hardware would not communicate at all until I totally re-installed Windows from scratch. I never did find out what was getting in the way. Also, whenever I plug a USB thumbdrive into my machine, the instant I remove it, the TMS-200 software looses contact with the TMS-200 board. Only a reboot gets the two back in communication again.

I hate to bash the thing because it really does work well overall most of the time.

[ABalthazor]

You could schedule it as a task to start at boot (as opposed to logon), but the tray icon won't be there.

I agree that they need to revamp it to a service-style model, which would also resolve UAC issues if done properly.

I don't think the software has to be running for it to cutoff the system using the ATX pass-through switch. If this were the case it couldn't have prevented my computer from booting up when the pump was disabled, but it did. I don't know what parameters it uses when the software isnt' loaded, but there are some.

Ideally the user could select options and have them saved to the firmware of the board instead of relying on the software interface.

[rambler358]

Ideally the user could select options and have them saved to the firmware of the board instead of relying on the software interface.

That's actually what's done when you're system starts up and the software isn't running. The last time you saved settings they're written to firmware, and the TMS will use those settings at next startup until they're changed again.

[Grinder]

It could stop you from booting if it was confused :

Actually, I think the comment made by the OP was that it couldn't do a flow based shutdown, but I'm too lazy to check right now.

The scenario I'm being anal about is Windows hangs while unattended and a problem occurs. Is the shutdown mechanism dependant on the software running for certain things?

Sorry for playing devil's advocate It seems like all of these solutions have their flaws. Time to google some more, and see where I can find one of these three (tms-200, aquaero, bigng) in stock and at what cost!

[rambler358]

It could stop you from booting if it was confused :

Early versions of the software had this very issue!

[D749]

I'm waiting for Everest support before I pick one up. A dev on the Everest forums mentioned they were looking into it and that they had ordered a TMS-200. But there has been no update for months.

[ABalthazor]

When yours finally arrives and you have had time to evaluate, you can send me the loser

The T-Balancer finally arrived from Austria. Looking at it ... boy does it have a lot of sensors, way more than anyone would practically need. And the fact that I need to install the base unit and the analog sensor hub in order to get flowmeter support is offputting. Right now the TMS-200 can do what I need in one unit: flowmeter, sufficient temp sensors, and three fans, and all in one device. I suppose I could use another couple of fan headers, but I don't need them enough to install either the TMS-200 expansion board (which won't fit where the TMS-200 is currently installed) or to install the T-balancer.

My TMS-200 is installed in a really cramped place in my case, and taking it out to reroute the cables to the T-balancer is going to be more work than it is worth right now. The TMS-200 is working fine for the time being, so I'll probably store the T-balancer as a backup system.

The T-balancer's software version was labeled 2006. That isn't confidence building.

[Grinder]

The T-balancer's software version was labeled 2006. That isn't confidence building.

Yeah, that's the thing I like the least about it. No support to speak of in terms of fixes or new features. I wonder if it is limited to 2 flow input? Unless you could hook up more than one analog hub... It sounds like the tms-200 has the same status, but at least the software is a lot more recent.

Do you have any thoughts about the aquaero? And let me know if you decide to sell your mcubed gear for a loss