I kind of "fixed" it by using the translation manager... That's the only way I found to work around unreadable tag names.
2 Likes
Found a couple other things:
- When zooming in quite far, this is all I see in my x-axis. I donât know what date/time this is apart from that it happened at something and ~34/35s. It looks really strange seeing the seconds reported as â:35â as well (at least I think theyâre seconds!).
The axis in my opinion should still have all the information you need. Something like this:
- This has also always been very awkward for me to interpolate values between:
The x-axis increments should be at fixed offset values (e.g. divisible by a fixed number: 2, 5, 10, etc.), not just stay fixed in their positions and change values along with the updates of the plot, going from e.g. 4:51âŚ4:52⌠4:53. This adds so much more mental load in order to constantly try to interpolate the times between points that are constantly changing offsets and particularly changing intervals when zooming in to stupid numbers like 13 17 19. Maybe iâm just âto dumâ
but I very much pity our operators trying to read them!
E.g. this is what I would expect: an x axis whose notches move along with the time:
And if I zoomed in:
2 Likes
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.
2 Likes
I just want to send my support on this topic. Power chart should be better.
Apologies for the ping, but it has been several months since these tickets were created, I looked for and have seen no movement on the nightly change logs, and we have several users breathing down our necks wanting the data to be returned âas storedâ instead of sampled. Could we get an update on where this ticket stands, and if possible, a timeframe? It would be helpful to know if itâs worth pursuing rolling our own charting functionality or using someone elseâs implementation in the meantime, or if Iâve just missed the update, lol.
Thank you very much!
2 Likes
@kirsten.chambers, we just prioritized several power chart tickets for the upcoming development sprint. I also bumped the priority on the âAs Storedâ ticket based on your feedback.
6 Likes
Thank you very much! 
Another thing I would suggest is that when realtime is chosen that trending tags are considered leased or at least make that an option. Last I checked that wasnât the case and we had to use some custom values to make sure they would update at the leased rate.
I added a feature request to also be able to display units for the pens. Right now we do this via a change script but it sure we be nice to have this developed in.
2 Likes
Usually units are displayed in the axes labels, but I can see adding these to the pen labels as being useful as well if you have multiple pens with different units on the one axis
1 Like
Exactly we tend to have several pens on the same chart where the scaling of on axis works out OK but the units of the pens may be a little different.
Kevin,
You can do this by saving the configuration to a DB, but a built in way to do it would be nice.
Sounds like a good idea for an exchange component. That way we can also be in charge of it and modify if we need to without being stuck with what weâre given, so to speak, as one solution doesnât always meet everyoneâs expectations or needs. But at least with an exchange component, everyone isnât starting from scratch each time
1 Like
this is all great info. Id like to add a few that i am trying to overcome to make this tool more useful for my group. When dev is being done and the project is saved it wipes out everyoneâs current charts they have open. we have tried implementing the project update countdown to give time to save what you have open. However, the window pops up right over the save chart controls and i cant for the life of me figure out a workaround. anyone solve this issue?
the other one is our save / Done button is covered by the maximize button on our screens, another one i cant seem to find a fix for.
any help would be very appreciated
Is that using English Alternate translation or another language?
Do you recall the number of samples that worked for you?
I'm getting a weird line from the bottom up when point count is increased from 300 (default) to 400.
The GIF is only showing the line sometimes but on the screen its always there.
I usually at least double the default samples to 600, but it really depends: 1) how often youâre capturing data, 2) how often and how quickly values change, and 3) the time window youâre looking at
Can you link to this please? Iâd like to upvote it
Maybe we can get some empiric formula using those 3 variables 
Right now Iâm using 1800 points as default
English alternate if you want to translate to English, with the real tag name being the key.
Weâre on the fence about switching our process data historian needs to Ignition until the Power Chart is improved. Among the many features we need to see to justify a purchase right now:
- No ability to search for tags in the browser.
- When trending multiple variables with different orders of magnitude of values, the trend is nearly useless unless you put the variables in separate charts which somewhat defeats the purpose.
- Need more options in terms of time retrieval such as custom ranges.