I am trying to create a chart that show gaps when the data is bad quality. This seems to work fine in Vision, but I can’t get it to work in Perspective. The breakLine property sounds like it should enable this functionality, but I don’t see a difference when turning this on or off.
There is a breakLine property that is enabled by default per pen. It functions differently than Vision’s Easy Chart, though. It breaks on missing/absent values vs a 0 value like the Easy Chart:
Are you sure the Easy Chart is reacting to zero? Instead of the recorded quality? (I always inject nulls into Vision datasets to deliberately break lines.)
@pturmel is correct. The screenshot in my original post is showing values with bad quality, not good quality zero values. Although it may be sending a zero value to the database? The breakLine property doesn’t seem to do anything.
My fault; thanks guys. Yes, the Vision table is reacting to the quality. On the Perspective side, we are reacting to only the data right now. I’m going to open a feature request to have the Power Chart respond to the quality code that it gets back in the data payload.
Thanks @jball! Is this a bug or is there another purpose for the breakLine property that I’m not seeing? Either way, I’m happy this is getting some attention because I’ve been getting complaints from customers about this.
Alongside this discussion, how do we turn off interpolation from Power Chart? We want to be able to see when comms go down or data is missing as well. Power chart interpolates between values so when a comm is down, we end up getting a slowly decreasing line when really it should’ve nulled out. Any updates? Ideas?
I saw in another ticket that there will be changes to the powerchart in the next sprint, is this ticket included? I definitely hope, Users are complaining as some of our old sensors give 32000 as bad sensor value.
Quick follow-up This will be available in the 8.1.17 release. The changes were merged, and it should be available in the next nightly release for testing.
In 8.1.19 it still happens. I was wondering where I got all those changing values until I came across with posts about interpolation.
You are right. I was reading this post a while ago.
I'm not sure how it supposed to work because an analog sensor is not discrete and it also doesn't have the behavior that the power chart is drawing by default. I wonder why there aren't more posts about it