[FEATURE] Increase usability of the Perspective Power Chart component

[nminchin]

Seems like more of a bug than a usability issue, you should create a new topic for this one

[keith.lyding]

I actually just figured out the issue. My datapath was set to the tagpath, instead of the historical tagpath.

[Ryan_Allen]

@nminchin

SCADA-which-shall-not-be-named

FactoryTalk View or Wonderware lol?

[mdemaris]

Wonderware is such a mess

[josh.schadel]

I'm also having many useability complaints from our customers with the Power cart components.
Or devices typically transmit data at fixed intervals of anywhere from once every 5-seconds to 12-hours, typically in the 5-minute range.

I want a cart of the actual values in the dB but seems the only way to do that is set the pointCount property to -1 which then if you view anything more than a very small time range the graph grinds to a halt.

Is having a basic graph that looks like this possible on a PowerChart?

[nminchin]

I'm a little bit confused by what you're asking for. In your text it seems like you're asking for the power chart to be more performant when showing all data recorded for the pens, but in the image, you're showing the opposite, a very small sample of aggregated points over the time period instead of all of the points recorded. The power chart can certainly show an aggregated sample of points, but it does have some flaws, like that it resamples the data points every time the time advances which causes all of the data points to move around
E.g.

[FEATURE] Increase usability of the Perspective Power Chart component

And this is what I meant about displaying sampled being unusable. (the higher you increase the # samples the more stable it is, but this is at default settings) This is server CPU and memory usage. Notice the ups and down change every second, and sometimes large spikes from 30% to 70% and 80% appear and then disappear the next second for the same point in time.

It's been a while since i've looked at it, and not in the later versions. I really hope that it's improved... I know the time axis has been improved, in that the times are now logical* (hopefully) and track along instead of being fixed in place. That was one of its biggest flaws. But I still hope that things are being done about the realtime/historical modes by getting rid of the distinction which i've documented in many posts in this topic..

[nminchin]

@Vincent_Hallmann

is there a way to disable the second (small) chart that shows up when you switch to historical view vs real-time ?

if you turn on props.interation.panAndZoom.freeRange then this will remove the data preview chart

[josh.schadel]

What I was referring to is say each dot on that graph example is a datapoint in the history db. What I see with the power chart is if we set the pointCount to say 300 the chart "adds" points to the data and the trend takes steps, furthermore if you export the data from the chart you get lots of repeated data with timestamps that do not align with the actual source data.

I'm looking to have the data on the power chart equate to the data that was sent in from our remote devices and have a trend where each "real" datapoint is connected by a line.

[pturmel]

The powerchart is basically using "Wide" history queries under the hood. Wide format is utterly incompatible with point count == -1. AKA "as stored". To get the behavior you are after, you must:

• Do your own queries, which means
• Use a different chart type (TS Chart perhaps, but performance sucks).
• Use "as stored" results with "Tall" format, then
• Post-process the tall result to group by tag path, yielding a dataset per tag with that tag's actual data, then
• Further process that data to deliver to the chosen chart type.

(Example in my Tag Report Utility on the Exchange.)