Trend Log showing many Off/On items

I have some variable that I know are Off/On at some point in time, but the Trend Log always show them at the same value.

As you can see here

the D (Boiler) should be up (Value = true) when 8 (Pump) is up, and when 8 goes down, B and D should be down (false). In the screenshot you can see that CH_MA is No and the Log show it UP.

Create a new trend log with just the two items of interest on it, sampling them every 10 seconds or so. Keep the T3000 trend log screen open during the test. Manually toggle the inputs and outputs on and off for a few on -off cycles. Hopefully you see the trend log behaving. If not try setting different ranges like off-on instead of on-off.

Once you are done the test you can set everything back to auto and report back here. Also you could send your prog file by email, best not to send it here on the forum in order to keep your files private.

Will keep doing test, but realize that if you have too many Digital variable, they don’t all display


In this screenshot you can see that D (Boiler) don’t show up, and C (R_FO) is outside the box


If I uncheck a couple of Digital, then the missing one show up

Thanks for the feedback, we will make a note to improve the display with lots of digital IO.

Have you sorted out the initial issue about trend logs not behaving?

Just tested with 2 digital and 1 analog…
The 2 digital doesn’t even seem to be logging

We’re on it. Thanks for good feedback.

1 Like

Can you send me your prog file?
my email is chelsea(at)temcocontrols(dot)com

The new code supports access to modbus sub-devices using VAR, IN, and OUT.

The following is a demo about programming


About trendlog, I had to explain that it’s best to map remote points to local points, just like in the demo. Since all remote points are considered analog, we haven’t checked the ana_dig attribute of each remote point, and there are many cases where we can’t get this information.

In addition, we support two ways to access remote modbus points, one is the old 1.2.MB_REGXX, the other is the newly added 2VARx,2INx,2OUTx, maybe the second way is more convenient.

1 Like

I have tested according to your prog and connected two Tstat10s ID16 & ID12.
MAP remote modbus points to local vars in program code.