Trend Line type for stale values

Find and share HowTos to various installations / configurations!
Search

Post Reply
2 posts • Page 1 of 1
MattPaulissen
Posts: 26
Joined: Fri Feb 19, 2016 9:27 pm

Trend Line type for stale values

Post by MattPaulissen »

The trend object seems to automatically change the trend line to dash dot dot when the current timestamp on a DPE is less than the current time. This normally doesn't bother me at all, but I'm trying to make a trend with two extra curves that show a high and low setpoint. If I directly connect these to the DPEs that are coming from the PLC then they change to dash dot dot and then don't fill since the setpoints are very seldomly changed. It actually does the same thing if I set the curve to static and then use a dpConnect on the setpoints to change the static value. Is there any way to disable this behavior on a per curve basis or am I stuck with a config entry?

I'd like the setpoints to ignore this behavior, but keep it for the actual PV. Attached to the real PLC perhaps it won't matter if I can't ignore it per curve since the PV will always be updating anyway.

User avatar
mkoller
Posts: 741
Joined: Fri Sep 17, 2010 9:03 am

Re: Trend Line type for stale values

Post by mkoller »

The TrendCurve reflects the invalid bit being set on the DPEs value, therefore you'll see a changing line type.
First I would make sure that this does not happen, e.g. this DPE always receives value changes with increasing timestamps.
Since this seems not the case here, I have the feeling there is something broken.

If you still don't like this, you need to change the "trendStatusPattern" config entry so that the invalid bit does not change the line type.
What I see is that the default in the UI is to display invalid curves with a dotted line, not "dash dot dot" - did you already change this configuration ?

To your "per curve" question: you can configure the line type per curve, however the global config "trendStatusPattern" has precedence.
You could define some "trendStatusPattern" in the config which will never match, then you have full control over the curve, however
without any automatic check for the status pattern of a value.

Post Reply
2 posts • Page 1 of 1