-
Notifications
You must be signed in to change notification settings - Fork 67
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
Device rapidly sending port 0 messages #173
Comments
Well, first off, do you know what mac commands they are sending off ? The best thing you can do is to look at the source code and use a ST-Link debugger to see what is going on. |
Debugging is unfortunately not practical, as this only happens to a few devices in the field after a while, haven`t been able to reproduce this in the lab yet. At this point, also the mac commands are not logged and available. Generally the network server is not configured to be sending any. As the first action, a monitor logic will be implemented on a few devices to detect how many messages are transmitted that originate from the stack itself, then we can better understand the case. |
@GrumpyOldPizza managed to get a better debug of the issue. Device keep sending the RXParamSetupReq to which the network server does not respond or send the ack. What triggers this behavior is unknown, device reset resolves it for a while, which can be up to a month and then it may repeat again.
|
Has there been any updates? I believe I am experiencing the same issue. |
The issue has been observed on a few devices deployed in the filed, where they start sending port 0 messages - mac commands at a rapid pace (every few seconds) until they are rebooted. This appears to be some anomaly related to the MAC commands form the network server.
To resolve this issue, it would be good to understand the mechanism what can trigger this @GrumpyOldPizza . Alternatively I need to find a way to safeguard against it.
The text was updated successfully, but these errors were encountered: