Hi, When we download tag history from PowerChart data, I noticed there is duplicated timestamps with two different values.
Can someone help why this happens.
Your time column is not showing the seconds.
It looks like you have converted the t_stamp but left off the seconds and milliseconds portion.
@lrose Thanks for quick response.
Though I activate ss and SSS the data is same. Duplicated.
Iâm running 8.1.2. And this export is from powerchart component.
I just noticed that when we add new Pen, by default the aggregation mode is set to âdefaultâ. I suspect default aggregation mode is MinMax. Hence there is two data on every timestamp interval.
Is there anyway to set aggregate mode to Average when we âAdd Selected Tagâ?
Undoubtedly
When you add or edit a tag there is an option to set the Aggregation Mode, I don't know if there is a way to change it's default to a different type of aggregate.
@cmallonee Perhaps you have some insight?
No, there is not a way to configure the default aggregation mode when tags are brought into the Power Chart. Dev seems to believe it wouldnât be difficult to expose a new property to allow for this. Iâll open a feature request for now and weâll see what happens.
1 Like
Has there been any update? We are still seeing this same behavior in csv export version 8.1.25.
No progress at this time. There have been a few notes left on the ticket which mention various interested parties, but we've not started any development work on this feature.
The problem seems to exist. I have version 8.1.30. Is there a work around that you suggest?
Thank you
I also have the same issue with the PowerChart and I cant figure out how to get the csv export file to only show 1 row per data point. Has this been figure out?
You can write script in Excel to average each two rows.
Hi Anthony,
I'm not sure if that will work in my case where timestamps duplicate only a couple of times. Has anyone else figured this out by chance? I have an assumption that it might have to do with clock delay if the Ignition Gateway is experiencing heavy load.
Hi @cmallonee, has work continued to fix this issue?
No, it has not. The ticket is still awaiting development. The ticket does have multiple interested parties listed and is of a higher relative priority, but it has no estimated/target release version. Iâll add your interest to the ticket.
We also submitted a request to Ignition support for the same issue and they replied saying it's likely caused by the Minmax aggregation but no real solution on it currently. Also hopefully it gains enough interest to get some attention.