Hi,
I’m having an issue with displaying trending graphs when the Y-axis scale is set to Range.
When the Y-axis scale is in Auto mode, I can zoom in/out (mouse scroll wheel) and scroll through the graph (mouse right key) with now issues. However, when I change the Y-axis scale to Range, Cube becomes unresponsive as soon as I scroll / zoom to a part of the graph where data exceed the range. It’s a bit difficult to explain this in writing, so I made a screen recording, please see the link below:
https://drive.google.com/file/d/1r2B7ViKCUxRGOcftFcZlaNmkeVapbeEA/view?usp=sharing
We’re experiencing this issue on Cube 9.6.0.0-9817-CU21 Standalone and via Internet Explorer. On the screen recording I’m looking at NX4600 driver, but I can see the same behaviour on Titan Live driver, so it seems that this is not related to a particular driver.
Happy to arrange screen sharing session do demonstrate the issue.
Hi Adam,
Do these negative values out of the normal range represent exceptions or errors? In that case it is recommended to define them as such in the protocol (see development library), and then these will be displayed separately in the trend UI.
After checking the video it seems very likely you’re running into the limits of how we implemented the scaling due to the huge minimum value that is filled in there.
Is this minimum value expected? If not, maybe it’s worth investigating where it comes from and maybe as a temporary workaround you can set the minimum value to something more realistic in the popup.
Hi Adam,
Thanks for reaching out to us. Would you mind registering this in our Collaboration platform as a task in your ‘maintenance and support’ project? Then you can easily follow up on the progress of the investigation.
More info regarding Collaboration in our training section.
Hi Pieter,
We’ve added this task in the ‘Maintenance and support’ project as you advised.
Hi Toon. We use trending to investigate an ongoing issue resulting in occasional very high / low value of the parameter. At the same time I need to see the shape of the graph between +40 and -40 ppms, so I’m afraid there’s no workaround here. Moreover, I see the same problem with a CPU usage trending graph. In this case the values are fluctuating a lot between 30% and 90%, if I set the Y-axis scale to 45%-50% I experience the same unresponsiveness.