Forum Home › Forums › Understanding the Software › Line chart versus point graph
Tagged: chart
- This topic has 5 replies, 2 voices, and was last updated 8 years, 10 months ago by
dsjstc.
-
AuthorPosts
-
January 26, 2017 at 6:25 pm #1889
dsjstc
ParticipantMy charts are constructed of dots at 1-minute intervals. This is adequate when zoomed way out, but very difficult to read when zoomed in.
I’d like to show some of the columns graphed as an interpolated curve (or series of line-segments) through the points, rather than just showing the individual data points.
I’ve searched all through the forums and don’t see anything related to this, but I’d be surprised if I’m the only one with this problem. Possibly I am misconfigured?
-
This topic was modified 8 years, 10 months ago by
dsjstc.
January 27, 2017 at 6:51 am #1895
MikhailModeratorYou are the first with this issue. Could you remember what settings of the Webstation app have you changed? Or post a screenshot of http://localhost/Scada/plugins/Config/WebConfig.aspx
January 27, 2017 at 6:52 am #1896
MikhailModeratorI’m mostly interesting in value of the Chart gap parameter.
January 27, 2017 at 4:10 pm #1897dsjstc
ParticipantThanks Mikhail. Problem solved. Chart Gap was 30 sec, and I don’t recall ever having changed it.
The effect of this parameter seems counterintuitive. No change if I decrease it, just dots every minute. At 60 seconds, it interleaves 60-second lines with 60-second gaps. At 120 seconds it creates continuous line-segments.
If that’s not expected behaviour, please let me know if I can help isolate it further.
January 27, 2017 at 5:03 pm #1900
MikhailModeratorThis parameter is very useful for tuning charts. If data are stored every 5 minutes, for example, you need to increase Chart gap to 300 or more to make trend continuous.
On the other hand, if you set it to 300 while data are stored every 1 minute, you can’t recognize when communication with device is unstable.
January 27, 2017 at 5:13 pm #1903dsjstc
ParticipantThat makes sense. I had expected it to infer that information from the poll frequency in the Communicator settings. In my case, the input is Modbus TCP with a delay of 200 (presumably ms), so the 60s chart data period didn’t seem to be related to anything — I assumed it was a glitch in the chart plugin.
Anyhow, all better now. Thanks for your very helpful response. I’m sure this post will help the next person with this problem!
-
This topic was modified 8 years, 10 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.