EnergyWise for reduced IPV6 Devices

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: Paul Bertrand on 17-03-2011 05:43:58 AM
Hi all,
 
I'm very new to energywise solution, so do not hesitate to redirect me to the right place(s) if these subjects have already been dicussed somewhere.
 
Has anyone allready thought about making small devices (8/16 bits MCU, low RAM/low Flash, RF PLC or any) acting endpoints for energywise systems ?
I can imagine two solutions:
- Port the EnergyWise SDK solution on one of the various reduced OS for small Sensors/actuators Nodes.
- Making an endpoint (Linux or Windows) with multiple components linked to.
 
Energywise endpoints use Ethernet MAC address for identification (discovering) is it possible to use an other id (IPV6 address or any ...) ?
 
Regards

Subject: RE: EnergyWise for reduced IPV6 Devices
Replied by: Brock Miller on 21-03-2011 08:09:27 PM
Hi Paul,

We have several partners currently running/scoping the SDK on embedded lightweight systems.  For these partners we can supply the source code (pending legal etc.) for compilation purposes since we only pre-compile for 32-bit Win and Linux.  The determining factor here would be how lightweight the system is and what effort is required (if any) to get the SDK service up and functional.

Your second suggestion would also be an option if the first isn't feasible due to system constraints.  I assume that you mean this Linux/Windows machine will "proxy" for the attached sensor nodes etc?

EnergyWise endpoints use a completely unique EnergyWise ID for identification purposes.  We provide several helper utility functions to help facilitate generating this.  It can be generated randomly by the OS, or be seeded with MAC address and/or other device-specific attributes like product id, hw version, etc.

Hope this helps!

-Brock

Subject: RE: EnergyWise for reduced IPV6 Devices
Replied by: Paul Bertrand on 22-03-2011 11:05:08 AM

We have several partners currently running/scoping
the SDK on embedded lightweight systems.  For these partners we can
supply the source code (pending legal etc.) for compilation purposes
since we only pre-compile for 32-bit Win and Linux.  The determining
factor here would be how lightweight the system is and what effort is
required (if any) to get the SDK service up and functional.

Indeed,
we are minding about the volume of such an implementation. If
necessary, maybe a reduced set of functionnalities could be implemented ?
So we would really be interested in getting source code/doc to evaluate
the complexity .



Could we get in touch with your partners that are running/scoping the SDK on lightweight systems ?


Your
second suggestion would also be an option if the first isn't feasible
due to system constraints.  I assume that you mean this Linux/Windows
machine will "proxy" for the attached sensor nodes etc?

I
saw that proxy could be a solution, but, in that case, we also need the
sources, as our gateway to is a small device running an openembed linux
on a Cortex A8 MCU.
By the way looking at the documentation, isn't
there an other way than "proxy" to do that, by using the multiple
components capability of an endpoint that seems to be available since your SDK V1.2 ? How many
components can be binded to  an endpoint ?




EnergyWise endpoints use a completely unique EnergyWise ID
for identification purposes.  We provide several helper utility
functions to help facilitate generating this.  It can be generated
randomly by the OS, or be seeded with MAC address and/or other
device-specific attributes like product id, hw version, etc.

Is the unicity, controlled with CDP protocol ?



Which is the entry point to get the specificfications of the implemented
protocols. If possible not SNMP that could be quite heavy for a
lightweight device ...

Many thanks for your answers
 

Subject: RE: EnergyWise for reduced IPV6 Devices
Replied by: Paul Bertrand on 31-03-2011 03:44:44 AM
Hi Brock,

We are really minding about the recompiling of the SDK on embedded lightweight systems.
That's why, we need evaluate the complexity, either for a small MCU with limited capabilities, or for an Linux OS but not based on X86 architecture (ie Cortex A8 / Openembed).

Please tell us the right way to obtain source codes under any licence agreement (NDA ?) ?

In advance, thanks for your next answers.

Subject: RE: EnergyWise for reduced IPV6 Devices
Replied by: Luis Suau on 31-03-2011 08:29:18 AM
Hi Paul,

The EnergyWise Source Code is governed under its own TLA addendum and is handled directly through the EnergyWise Business Development Manager (Amir Raz). I will forward your request to him.

Best Regards,

Luis

Attachments

    Outcomes