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

Doc: cmd 8000, understanding status code #371

Open
tcharp38 opened this issue Jun 26, 2021 · 0 comments
Open

Doc: cmd 8000, understanding status code #371

tcharp38 opened this issue Jun 26, 2021 · 0 comments

Comments

@tcharp38
Copy link

Sorry guys.
This is an old subjects but never really answered.

What is to procedure to understand 8000 cmd status code WITHOUT being forced to enter in Zigate FW ?

As an new example I'm getting a status 14 following 0100 cmds.

[2021-06-26 15:14:03] Abeille1, Type=8000/Status, Status=00/Success, SQN=B2, PacketType=0100
[2021-06-26 15:14:03] Abeille1, Type=8000/Status, Status=00/Success, SQN=B3, PacketType=0100
[2021-06-26 15:14:03] Abeille1, Type=8000/Status, Status=14/Status 14 inconnu, SQN=00, PacketType=0100
[2021-06-26 15:14:04] Abeille1, Type=8000/Status, Status=14/Status 14 inconnu, SQN=00, PacketType=0100
[2021-06-26 15:14:05] Abeille1, Type=8000/Status, Status=14/Status 14 inconnu, SQN=00, PacketType=0100

I'm guessing that this is a flow control issue (by the way, describing this somewhere would be good for zigate experience), but could not be sure since unexplained error.

If there is no way to clearly list & explain all possible codes, can we at least have the procedure to find it ?
Thanks

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

No branches or pull requests

1 participant