Technical FAQs

Ask a Question

Graph of state sensor in DCE may not show current value after it has been disconnected and reconnected.

Issue:

Graph of state sensor in DCE may not show current value after it has been disconnected and reconnected.

Product Line:

StruxureWare Data Center Expert (DCE)
NetBotz

Environment:

StruxureWare DCE 7.x graphing
NetBotz any version, with a state sensor connected

Cause:

NetBotz devices only record values for sensors when those values change. This is done to save space. In the case of a door sensor or dry contact sensor for instance, a door closed for a week does not need to record a weeks' worth of data, only the last state. This is done to save space.

Since there is no new state after the reconnection event however, StruxureWare DCE will not graph the state until it again changes to an open / closed state after the reconnection of the sensor.
Here you can see a door sensor that shows a space in the graph in NetBotz Advanced View where the sensor was disconnected and reconnected at about 12:27 to 12:28 or so.




That same report in DCE shows no values after the sensor was reconnected:



This next image was taken almost immediately after the previous graph but also after the door was closed and re-opened to cause a state change:


You can see where this graph captured only a minute later shows about 16 minutes more data.


Resolution:

APC/Schneider is currently looking into this issue and may have an update in a future revision.
A table report will show the current state (closed / open) so you will be able to see the value as well as viewing the sensor's current state on the monitoring perspective of DCE.
 
Was this helpful?
What can we do to improve the information ?