Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Sensor Service Methods

DCE web services API

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure IT Help Center
  • EcoStruxure IT Help Center Categories
  • Data Center Expert
  • DCE web services API
  • Sensor Service Methods
Options
  • Mark as New
  • Mark as Read
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close

Related Forums

  • EcoStruxure IT forum

  • APC UPS Data Center & Enterprise Solutions Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

EcoStruxure IT Support

Submit a support request for additional assistance with EcoStruxure IT software.

Request Support
Back to DCE web services API
Options
  • Mark as New
  • Mark as Read
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
1313 Views

Link copied. Please paste this link to share this article on your social media post.

Trying to translate this page to your language?
Select your language from the translate dropdown in the upper right. arrow
Translate to: English
  • (Français) French
  • (Deutsche) German
  • (Italiano) Italian
  • (Português) Portuguese
  • (Русский) Russian
  • (Español) Spanish

Sensor Service Methods

Picard EcoStruxureIT
‎2019-11-20 06:14 AM

Sensor Service WSDL

A sensor represents any measurable value or state within a device or probe. It is easy to confuse the terms sensors and probes. In the Data Center Expert domain, a probe is a physical entity for measuring an aspect of the physical environment, while a sensor is a conceptual entity which simply references any device or probe value or state.

Sensors themselves have an associated state value. This value indicates whether the sensor is connected or not (for sensors associated with probes) and whether there is an alarm condition associated with the value of the sensor. Alarms are generally triggered when a sensor’s value exceeds a threshold defined by the user on the device or on Data Center Expert.

Sensors are organized by a pre-defined set of sensor types. Most devices support a DEVICE_STATUS sensor.

Some devices will support multiple instances of a particular sensor type such as the BREAKER_CURRENT sensor on a PDU. When a device does have multiple instances of a sensor, each instance will be identified by a sequential index number.

Some devices consist of modules or sub-systems and sometimes these modules have multiple instances of a certain type of sensor. In these cases, the sensor instances are double-indexed; once for the module instance and once for the sensor instance.

When referencing a NetBotz probe sensor, the sensor index often represents the port that the probe is plugged into.

The following methods are available through the Sensor web service.

initializeSensorService

This optional method serves two purposes. First, it allows the sensor web service to be customized using a string of parameter values (NYI). Secondly, it provides a mechanism for isolating the 2-3 second set up time required for the first (and only the first) invocation of the sensor service; otherwise, a client has to endure that set up time during the processing of that first sensor service request. Returns true if successful.

Service: ISXCentralSensorService

Parameter Type Description
initialParameters  String Ignored

getSensorByID

Returns an ISXCSensor object that represents a sensor being monitored by the Data Center Expert server and is identified by the specified ID. 

Service: ISXCentralSensorService

Parameter Type Description
ISXCElementID  String

The unique identifier of a sensor being monitored by the Data Center Expert server.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getSensorsByIDs

Returns a list of ISXCSensor objects that represent sensors being monitored by the Data Center Expert server and are identified by the specified IDs. 

Service: ISXCentralSensorService

Parameter Type Description
ISXCElementID list  String

A list of unique identifiers of sensors being monitored by the Data Center Expert server.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getSensorsByType

Returns a list of ISXCSensor objects that represent sensors being monitored by the Data Center Expert server and are of the specified type. 

Service: ISXCentralSensorService

Parameter Type Description
sensorType ISXCSensorType

The specific type of the sensors to return.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getSensorsForDevice

 Returns a list of ISXCSensor objects that represent sensors connected to the DCE-server-monitored device that is identified by the specified ID. 

Service: ISXCentralSensorService

Parameter Type Description
ISXCElementID  String

The unique ID of the device to return sensors for.

sensorType (optional) ISXCSensorType

The sensor type to filter the results on.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getDeviceForSensor

Returns an ISXCDevice object that represents the DCE-server-monitored device that the sensor with the specified ID is connected to.

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID  String

The unique ID of the sensor to return the device for.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getSensorData

Returns an ISXCSensorData object that represents the current value data for the sensor with the specified ID.

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID  String

The unique ID of the sensor to return the data for.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

 

For the getMultiple<X> methods, it is important to realize that specifying large sensor ID lists or “wide” date ranges can cause excessive CPU and/or memory utilization resulting in overall performance degradation. To prevent this, specify as few sensors and/or as narrow a date range as is reasonable for your application.

getMultipleSensorData

Returns a list of ISXCSensorDataSet objects that represent the current value data for a list of sensors with the specified IDs. Recommended when querying for data for 4 or more sensors. For 3 or less sensors, it may be more efficient to use the getSensorData method.

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID list String

The unique IDs of the sensors to return the data for.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getMultiplePeakSensorData

Returns a list of ISXCSensorDataSet objects that represent the peak value data for a list of sensors with the specified IDs. Recommended when querying for data for 4 or more sensors. For 3 or less sensors, it may be more efficient to use the getSensorDataRange method.

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID list String

The unique IDs of the sensors to return the data for.

startDateTime (optional) xsd:datetime

The start date-time of the range to return data for, or null to return data from start of recorded data.

endDateTime (optional) xsd:datetime

The end date-time of the range to return data for, or null to return data until the end of recorded data.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getMultipleAverageSensorData

Returns a list of ISXCSensorDataSet objects that represent the average value data for a list of sensors with the specified IDs. Recommended when querying for data for 4 or more sensors. For 3 or less sensors, it may be more efficient to use the getAverageSensorData method.

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID list String

The unique IDs of the sensors to return the data for.

startDateTime (optional) xsd:datetime

The start date-time of the range to return data for, or null to return data from start of recorded data.

endDateTime (optional) xsd:datetime

The end date-time of the range to return data for, or null to return data until the end of recorded data.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

getHistoricalSensorData

Returns a list of ISXCSensorData objects that represent the recorded value data for a sensor with the specified ID. 

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID String

The unique ID of the sensor to return the data for.

startDateTime (optional) xsd:datetime

The start date-time of the range to return data for, or null to return data from start of recorded data.

endDateTime (optional) xsd:datetime

The end date-time of the range to return data for, or null to return data until the end of recorded data.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

maxDataPoints (optional) integer

The max number of data points to return in the request. Value cannot exceed 1000.

Note: ISXCSensorData objects contain timestamps corresponding to when the sensor data was captured. Since these timestamps can be used to determine/enforce sample order, there is no guarantee of any order in the returned list of samples.

getAverageSensorData

Returns an ISXCSensorData object that represents the average value of recorded data for a sensor with the specified ID. 

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID String

The unique ID of the sensor to return the data for.

startDateTime (optional) xsd:datetime

The start date-time of the range to return data for, or null to return data from start of recorded data.

endDateTime (optional) xsd:datetime

The end date-time of the range to return data for, or null to return data until the end of recorded data.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

 

getAverageSensorRange

Returns the ISXCSensorData objects that represent the highest and lowest values of recorded data for a sensor with the specified ID. 

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID String

The unique ID of the sensor to return the data for.

startDateTime (optional) xsd:datetime

The start date-time of the range to return data for, or null to return data from start of recorded data.

endDateTime (optional) xsd:datetime

The end date-time of the range to return data for, or null to return data until the end of recorded data.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

Note: Normally ISXCSensorData objects contain timestamps corresponding to when the sensor data was captured. In the case of min/max sensor data, the timestamps are set to the user-specified EndDateTime. Because each min/max value could appear multiple times within a given date range, it is not possible to ascribe a specific collection date to either of the two returned min/max values.

getSensorEnumerations

Returns a list of localized strings that correspond to possible values for a sensor that returns an enumeration index as its current data value and is identified by the specified ID. 

Service: ISXCentralSensorService

Parameter Type Description
 ISXCElementID String

The unique ID of the sensor to return the enumerations for.

locale (optional) String

Specifies the locale results are translated into before being returned. The default value is the locale configured in the Data Center Expert server.

Note: For sensors with enumerated value-types, the enumerated value definitions can vary from device model to device model. For example, an enumerated value of “0” for BATTERY_STATUS may mean “OK” on one UPS but may represent “Unknown” on another. Data Center Expert strives to normalize these values so they are consistent across devices. The number of supported devices makes this difficult to guarantee.

Verify sensor enumerations for all device models your application supports.

Attachments
ISXCentralSensorService_v2_0_360039289353.wsdl
Was this article helpful? Yes No
No ratings

Link copied. Please paste this link to share this article on your social media post.

Didn't find what you are looking for? Ask our Experts
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

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.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of