Writing IPU plugins for non ip enabled technologies (Zwave, ZigBee) [message #1733140] |
Tue, 24 May 2016 17:49 |
Klemen Petrovcic Messages: 34 Registered: November 2015 |
Member |
|
|
Hi,
I was wondering if anybody could tell me, how should we write IPU plugins for non IP enabled devices like Zwave or ZigBee.
One of the problems I see is that these technologies have shorter frames, so (at least ZigBee) has to use packet fragmentation to deliver the whole message. This means, we cant use the same XML bodies like at the HTTP protocol.
I'm thinking of defining my own protocol with shorter messages, which will convey the important parts of the message to the gateway so it knows which operation is being executed and what variables to use (for example, at ZigBee I could pass: "op=1; X-M2M-Origin: admin:admin;X-M2M-NM: MY_SENSOR" to create an AE entity).
What if I have a closed Zwave device? I can't change it's program logic, but I can include it in the network and receive its supported command classes. Is there a correct way to map those classes and the devices info to the OM2M platform?
Thanks in advance for your help, as always!
[Updated on: Tue, 24 May 2016 17:50] Report message to a moderator
|
|
|
|
|
|
|
Re: Writing IPU plugins for non ip enabled technologies (Zwave, ZigBee) [message #1742906 is a reply to message #1742644] |
Thu, 08 September 2016 14:13 |
Klemen Petrovcic Messages: 34 Registered: November 2015 |
Member |
|
|
Hi Son Duong,
I used two xbee pro modules. The two modules have to be configured, before writing the IPU plugin, appropriately with the X-CTU tool (you have to set at least the role, destination address, I/O configuration, serial connection parameters, API mode 2). You have to set one module as an end node or a routing node, and the other as a network coordinator. You will find a few beginner tutorials on the Sparkfun page.
[Updated on: Thu, 08 September 2016 14:16] Report message to a moderator
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04731 seconds