EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 10:37 PM . Last Modified: 2024-04-05 05:08 AM
Hi Team,
Asking on behalf of jared reed.
DCE is running v7.4.1.5.
They tried to upgrade to 7.4.3 but are experiencing issues during upgrade (separaete post on this here: )
Jared asked me the following question could you please assist:
__________
I have a tricky problem to do with trend data received from DCE following a query.
See below we run the trend request, however the data returned is from June…. Is there something were missing here?
We would expect the returned data to be most recent, I have check times on devices and server they are correct.
“
Request:
Response:
http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
“
(CID:124523221)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 10:37 PM . Last Modified: 2024-04-05 05:08 AM
Hey Luke, just on the SOAP part,
-Hi all, do correct me if i misunderstood this particular getHistoriclaSensorData request.
I'd recommend you to indicate the startDate and endDate, if you want historical data on specific date, as the number of data returned is <1000, see the max data points description.
To get historical data until the last available data, indicate 'null' as endDate, but ensure you have start date, and estimate so the total data points returned is less than 1000.
For example if the sensor is polled every 5 minutes, in a day you'll have 24 x 60 / 5 or 288 entries.
(plus additional entries when the device has alarm, and DCE polled it)
Netbotz will have more, as some of them have entries every minute, so that's 1,440 data points daily.
Some alternatives, depending on what user wants to achieve use:
getAverageSensorDataReturns an ISXCSensorData object that represents the average value of recorded data for a sensor with the specified ID.
getSensorData
Returns an ISXCSensorData object that represents the current value data for the sensor with the specified ID.
See explanation below on getHistoricalSensorData
As comparison,below is a similar response:
(CID:124523233)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 10:37 PM . Last Modified: 2024-04-05 05:08 AM
Hey Luke, just on the SOAP part,
-Hi all, do correct me if i misunderstood this particular getHistoriclaSensorData request.
I'd recommend you to indicate the startDate and endDate, if you want historical data on specific date, as the number of data returned is <1000, see the max data points description.
To get historical data until the last available data, indicate 'null' as endDate, but ensure you have start date, and estimate so the total data points returned is less than 1000.
For example if the sensor is polled every 5 minutes, in a day you'll have 24 x 60 / 5 or 288 entries.
(plus additional entries when the device has alarm, and DCE polled it)
Netbotz will have more, as some of them have entries every minute, so that's 1,440 data points daily.
Some alternatives, depending on what user wants to achieve use:
getAverageSensorDataReturns an ISXCSensorData object that represents the average value of recorded data for a sensor with the specified ID.
getSensorData
Returns an ISXCSensorData object that represents the current value data for the sensor with the specified ID.
See explanation below on getHistoricalSensorData
As comparison,below is a similar response:
(CID:124523233)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 10:37 PM . Last Modified: 2024-04-05 05:08 AM
Thanks Chris,
I will get Jared to review ans he can come back to you with additional questions.
(CID:124523269)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 10:37 PM . Last Modified: 2024-04-05 05:08 AM
Chris, Lukaz,
This is great, we have simply limited our start time parameter to 24hr prior to origin(current time).
This is providing the last 1000 records from the last 24hrs.
ANSWERED thank you
(CID:124524165)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 10:37 PM . Last Modified: 2023-10-22 01:28 AM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.