Undefined Data points in Historical Log

I’m using deadband logging. Trying to get a logging table for a few days to not be 100k+ rows…

image

Any way to get the other items to not say undef? If it’s going to log one value it might as well log the rest, “undef” still takes up space. Heck, it’s more characters than a 3 digit integer anyway.

@tomgiorgio

If there is no data point available for that tag then it will display undefined or Undef. This does not count towards the 1 million historical log data point storage maximum in the eWON’s memory.

If you’d like to log a group of tags when a tag changes in value, you can do that as well but you’ll need to use scripting and be on firmware version 12.2

FW available here: https://websupport.ewon.biz/support/product/manual-firmware-update/manual-firmware-download

You can use the ONCHANGE listener to trigger a logging of a specific group of tags in the eWON (A,B,C,D).

INIT Section
ONCHANGE "mybit", LogGroupIO("A")

For more details on triggering a data log on an event, please see the following topic:

What do you mean by “no data point available”?

@tomgiorgio

You are using deadband logging. This logs the tag that triggered the deadband but does not log all your tags at the same time.

You are seeing undefined because the table is displaying all your possible tags during that moment in time but they weren’t all logging during that instance in time because they were not triggered to log, only the tag that triggered the the deadband will show a data point for that row.

If you want all tags to log at the same time then you can set a logging interval instead of using deadband or use scripting above with the LogGroupIO function.

Hi @tomgiorgio.

Were you able to resolve your logging points table size issue?

Regards,
Chris

3 posts were split to a new topic: LoggroupIO deadband