| ... | ... | @@ -4,3 +4,5 @@ The first one is that lots of packets in ZStack are sent as synchronous packets |
|
|
|
|
|
|
|
To complain with the ZStack, the library contains a function called waitAndLock3WayConversation, where 3Way means the request, the synchronous response and the callback. That function uses a map to avoid that more request of the same type are sent so that the system doesn't know which request the response is for. Actually the function never checks that the conversation is performed that way, so it could be used also for the message exchange as it is done through the NXP dongle. I should have fixed all places where the library was waiting for a synchronous response over the asynchronous one but, obviously, I could have missed someone.
|
|
|
|
|
|
|
|
Some incoming packets (Asynchronous responses) from ZStack reports the source address in their contents where the equivalent packet from BeeStack does not. Maybe there are still some methods that expect to found this field. They should be modified to avoid run-time exceptions.
|
|
|
|
|
