Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added destination address to 0x8701 #231

Open
wants to merge 1 commit into
base: v3.1b
Choose a base branch
from

Conversation

ISO-B
Copy link
Collaborator

@ISO-B ISO-B commented Aug 22, 2019

Fixes #215

@pipiche38
Copy link

Tested with the pre-firmware version.
I indeed get a value, but the short address given doesn't correspond to any of my devices short address !

@pipiche38
Copy link

Here is a payload I'm geting

d000ae27

ae27 is unknown in my Devices list !

And as already reported:
The first by which are expected to be u8NwkStatus seems to u8NwkStatus;;
the 2nd byte which is expected to be u8NwkStatus is u8NwkStatus;

So I wonder if the ZPS_tsAfNwkRouteDiscoveryConfEvent is correct !

@pipiche38
Copy link

I might have a clue. In case NwkStatus & Status are not equal to 0x00, u16DstAddress seems to be invalid.

@ISO-B
Copy link
Collaborator Author

ISO-B commented Aug 27, 2019

Expected structure is:

<Status: uint8_t>
<NwkStatus: uint8_t>
<DstAddress: uint16_t>

NXP documentation doesn't have any notes about u16DstAddress being invalid in some cases, but that doesn't mean it cant be so. Should we discard address when statuses aren't both 0?

@pipiche38
Copy link

NXP documentation doesn't have any notes about u16DstAddress being invalid in some cases, but that doesn't mean it cant be so. Should we discard address when statuses aren't both 0?

For me it is up to the above layer to decide based on the Status, no ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants