|
|
This page reports the current state of the implementation.
|
|
This page reports the current state of the implementation.
|
|
|
|
|
|
|
|
|
There were various way to do this implementation. I chose to copy the code from the Texas Instruments dongle implementation and apply fixes to make it work. I thought that this method was faster and produced code more familiar for the zigbee4java contributors community. On the other hand there are some parts of the library that were not very clear or that could be written in a more efficient way and now may be worse. Moreover I changed the OpCodes of the packets without changing their names (to avoid having to look for names and change them all over the package) with the result that it is not so easy to find the correspondence between the name used in the ZToolCMD class and the BlackBox reference. Also in some points the documentation comments are in the wrong place. I addressed all these problems in the long term plans.
|
|
|
|
|
|
|
My point of reference is the zigbee-gateway-server of the zigbee4java library. This is a program given with the library as an example application that lets you test the functionality of the implementation. I modified it a little bit in order to use the NXP dongle instead of the Texas Instruments' one. By now I can start the program and register the default end-points. As for the TI dongle there are problems at shutdown: the applications stops responding but doesn't finish, so you have to terminate it, but doing so will corrupt the simple-network.json file so you have to delete it before starting the getaway again. You can also enable the permit joining. I did not test other functionalities.
|
|
My point of reference is the zigbee-gateway-server of the zigbee4java library. This is a program given with the library as an example application that lets you test the functionality of the implementation. I modified it a little bit in order to use the NXP dongle instead of the Texas Instruments' one. By now I can start the program and register the default end-points. As for the TI dongle there are problems at shutdown: the applications stops responding but doesn't finish, so you have to terminate it, but doing so will corrupt the simple-network.json file so you have to delete it before starting the getaway again. You can also enable the permit joining. I did not test other functionalities.
|
|
|
|
|
|
|
|
With the Freescale dongle you will get a lot of warning messages in the console because the dongle starts in a sort of debug mode that reports a lot of messages from the lower levels that aren't recognized by the program.
|
|
With the Freescale dongle you will get a lot of warning messages in the console because the dongle starts in a sort of debug mode that reports a lot of messages from the lower levels that aren't recognized by the program. You can change the mod through a packet of the ZTC.
|
|
|
|
|
|
|
|
There still some work to do to have a working network discovery. From the tests I've done with the dongle and the FlexPlug I could get the simple descriptor response, but sent the IEEEAddressRequest with no response. |
|
There still some work to do to have a working network discovery. From the tests I've done with the dongle and the FlexPlug I could get the simple descriptor response, but sent the IEEEAddressRequest with no response. |
|
|
|
\ No newline at end of file |
