|
|
This page explains how zigbee4java works in relation with the hardware used to perform the communication in the ZigBee network.
|
|
|
This page explains how zigbee4java works referring to the hardware used to perform the communication in the ZigBee network.
|
|
|
|
|
|
ZigBee Alliance defines some packets in their format. In particular it specifies anything regarding the ZigBee Cluster Library (ZCL) and some packets of the ZigBee Device Object (ZDO, Zigbee Device Profile for BeeStack) (at least in main contents).
|
|
|
The ZigBee Alliance defines some packets in their format. In particular it specifies anything regarding the ZigBee Cluster Library (ZCL) and some packets of the ZigBee Device Object (ZDO, Zigbee Device Profile for BeeStack) (at least in main contents).
|
|
|
The dongle vendor adds to these primitives the Test Library (ZigBee Test Client, ZTC, for BeeStack).
|
|
|
|
|
|
The library uses the Test Client to perform some actions on the dongle, like CPU reset or set/get channel, PAN-ID, and so.
|
|
|
The library uses the Test Client to perform some actions on the dongle, like CPU reset or set/get channel, PAN-ID, and so. This is strongly dependent on hardware.
|
|
|
The ZDO is used to perform actions mainly related to network management.
|
|
|
The packets defined by the ZigBee Alliance are defined in the *zigbee-common* package that is the higher level, hardware independent part of the library.
|
|
|
|
... | ... | |