HI All -

Can't seem to find info on this. I just got the aquaero 5 up and running. I'm using aquasuite 2012 and am just playing around with it at this point to learn how it works - I'm not actually trying to do anything serious.

So I went and I set up a virtual sensor. I choose absolute temp difference mode. I dropped two temp sensors into the data sources box. These temp sensor were maybe 2 degrees apart. But the output from the virtual sensor said something like 30 degrees. I've tried both absolute and non absolute, tried different temp sensors as data sources, changed the order in which I enter the sensors in to the drop boxes, and I always get some really wrong looking number. A few times the difference was close to being correct, but was off by 6 or so degrees. Usually the number I see is saying the difference is 30, 40, or 50 degrees. I thought there might be some sort of offset for the virtual sensors, but I can't seem to find one. And besides, I haven't seen a real clear pattern in the temp differences that would make me think they're being effected by a constant offset.

The other virtual sensor modes (avg, max, min) all work. Any ideas anyone?

Maybe I should say how expect this to work, because maybe I've got the wrong idea. I'd expect that if I drop two sensors, sensor X and sensor Y, into a virtual sensor, and set it to absolute temp difference mode, the output of the virtual sensor should = |X - Y|. For the non-absolute difference mode, I'd just expect it to be X - Y or Y - X maybe depending on the order you placed the sensors into the drop boxes.

Thanks!

Thanks Larry! I am indeed using F - I almost wondered if that was the problem but instead of switching to C I said, naw, can't be.

I read the link you posted. That's.... incredible. Maybe something was lost in translation, but it's two lines of code to take the number aquasuite is going to display to the screen, check a flag to see if it should be F or C, and then run it through the conversion formula. In other words, they could just do the conversion right before the user sees it if they feel it's too complicated to put it into the code that does the temp delta calculation. Just wow. I must be missing part of their explanation.

Thanks for explaining. I'm well aware of the prevalance of C over F in scientific and engineering calculations and devices (and that's how it should be, the C scale is easier to work with). I use it myself for that sort of thing. It's just I grew up with F, so I don't have an intuitive feel for just how warm a value in C is. When I'm just looking at a temp. like CPU temps or water temps, I like to see it in F so I can say, wow, that's really warm!

So maybe I've missed what you're saying, and I did oversimplify things in my previous post (my apologies), but it sounds like what AS has is the delta T in C, regardless of what the display units are set to, and that temps are converted to F only at the point of display. Thus, in the case of detla T values, once AS has calculated the delta in degrees C, couldn't it just multiply that value by 9/5 to get the delta T in F?

For example, delta T of 50 C (122 F) and 40 C (104 F) is 10 C (18 F). Well, if one multiplies 10 by 9/5, one gets 18....

I'd like to understand if I'm missing something, but it seems to work. It's no different than the C to F conversion you do for the straight temp readings except that you don't have to add or subtract the 32 degree offset, since it's a difference, not an absolute value.

Thanks again!

Larry, well put! I don't mean to be nit-picky and I agree with what you said about it working or not being there. It won't kill me to get used to looking at C temps, that's for sure. And the aquaero seems to be a pretty nice piece of hardware.

Sebastian, thanks for explaining more. I'm still not sure I see the why this change would be impossible- all the info is floating around in aquasuite, from the original sensor readings, to which sensor readings go into making a virtual sensor reading. That said, I understand that based on the software architecture and how the virtual sensors are implemented (which is what you were speaking about in your last post), that the change would be difficult - or at least difficult to do in an elegant way w/o resorting to a hack - and therefore due to ROI reasons, AC doesn't want make the change, which is understandable, if unfortunate for us pesky Americans.

There's plenty of other threads on this forum dealing with issues that need real help (including another from me! ), so please don't worry about this anymore, with the exception of taking the knowledge forward when planning future releases that there is at least some interest in the user base at seeing virtual sensors display in F.