EnergyWise endpoint with multiple output management.

Document created by cdnadmin on Jan 24, 2014
Version 1Show Document
  • View in full screen mode
This document was generated from CDN thread

Created by: Luigi Borghetti on 13-10-2010 12:38:20 PM
Hi,
we are working on a project composed by a device (called PODIST) which implement an EnergyWise Agent, with 8 power plugs; the device is a rack with plugs in the front of it. At the moment we can:
 
- Read AGGREGATE power consumption of all 8 plugs.
- Set level of the plugs (0 = all plugs OFF, 1 to 10 = all plugs ON).
 
With EW SDK, at the moment, is possible ONLY to manage (read and set) value about one device (one device = one IP address); how we can do for managing, one by one, the plugs of our device?
 
 
Bye.

Subject: RE: EnergyWise endpoint with multiple output management.
Replied by: Brad Schoening on 17-11-2010 07:20:31 PM
Hi,
we are working on a project composed by a device (called PODIST) which implement an EnergyWise Agent, with 8 power plugs; the device is a rack with plugs in the front of it. At the moment we can:
 
- Read AGGREGATE power consumption of all 8 plugs.
- Set level of the plugs (0 = all plugs OFF, 1 to 10 = all plugs ON).
 
With EW SDK, at the moment, is possible ONLY to manage (read and set) value about one device (one device = one IP address); how we can do for managing, one by one, the plugs of our device?
 
 
Bye.


Sorry for the late response.  The new Toolkit SDK 1.2 allows you to manage components inside of an IP managed endpoint.  With this, a PDU can manage and meter each individual outlet.
 
The alpha version of this release is now available for download in binary form from the CDN downloads page.   If you require source code and have an existing licence, I can send you the source code for this alpha release.

Subject: RE: EnergyWise endpoint with multiple output management.
Replied by: Andy Dominey on 21-12-2010 04:10:41 PM


Hi,
we are working on a project composed by a device (called PODIST) which implement an EnergyWise Agent, with 8 power plugs; the device is a rack with plugs in the front of it. At the moment we can:
 
- Read AGGREGATE power consumption of all 8 plugs.
- Set level of the plugs (0 = all plugs OFF, 1 to 10 = all plugs ON).
 
With EW SDK, at the moment, is possible ONLY to manage (read and set) value about one device (one device = one IP address); how we can do for managing, one by one, the plugs of our device?
 
 
Bye.



Sorry for the late response.  The new Toolkit SDK 1.2 allows you to manage components inside of an IP managed endpoint.  With this, a PDU can manage and meter each individual outlet.
 
The alpha version of this release is now available for download in binary form from the CDN downloads page.   If you require source code and have an existing licence, I can send you the source code for this alpha release.

 
Hi there, I have no connection with the orginal poster. 
 
By this do you meant that the SDK now provides the ability to act as a domain member?

Subject: RE: EnergyWise endpoint with multiple output management.
Replied by: Brad Schoening on 21-12-2010 04:19:56 PM



By this do you meant that the SDK now provides the ability to act as a domain member?





No, the SDK is still an endpoint, but we allow the endpoints to have multiple components.  This does make them look more like a domain member, but there are still several important differences between a domain member and an endpoint:
 * only domain members can forward queries
 * only domain members support the MAPI connection
 * the shared secrets used between domain members and endpoints are usually different

 

Subject: RE: EnergyWise endpoint with multiple output management.
Replied by: Andy Dominey on 22-12-2010 06:10:34 PM





By this do you meant that the SDK now provides the ability to act as a domain member?






No, the SDK is still an endpoint, but we allow the endpoints to have multiple components.  This does make them look more like a domain member, but there are still several important differences between a domain member and an endpoint:
 * only domain members can forward queries
 * only domain members support the MAPI connection
 * the shared secrets used between domain members and endpoints are usually different

 

 
Ok, thanks, that's clearer now.

Attachments

    Outcomes