You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite packets having to pass CRC, somehow packets are sometimes received which are completely invalid. For an example, see below:
[2024-09-04 17:29:31] [Debug] Received invalid announce for <aa94e097d2d22b2b23343f746104f01c>: Invalid signature.
[2024-09-04 17:29:31] [Debug] Received invalid announce for <aa94e097d2d22b2b23343f746104f01c>: Invalid signature.
This happens intermittently. It should be noted that this was a double announce on two RNode interfaces at the same time. It may be this is some kind of race condition or something. I've caught the raw packet from one of these before and literally 1 or 2 bytes will be incorrect, making me think it could also be some kind of memory issue.
Currently I have no clue what causes it, but it happens rarely enough for it to not be a problem most of the time.
The text was updated successfully, but these errors were encountered:
A large issue with the SX1280 is the sheer number of interrupts that it generates when operating at 203kbps (~550 per second). Currently I can't think of a great solution for this as I can't just sit polling the modem for ages since the firmware needs to be doing other stuff. For now, I'll leave this issue open until I think I can tackle it properly.
Commit 51afd31 has temporarily addressed this by capping the data rate. The data rate can be increased again once this issue has been resolved, but for now this allows for greater reliability.
Despite packets having to pass CRC, somehow packets are sometimes received which are completely invalid. For an example, see below:
This happens intermittently. It should be noted that this was a double announce on two RNode interfaces at the same time. It may be this is some kind of race condition or something. I've caught the raw packet from one of these before and literally 1 or 2 bytes will be incorrect, making me think it could also be some kind of memory issue.
Currently I have no clue what causes it, but it happens rarely enough for it to not be a problem most of the time.
The text was updated successfully, but these errors were encountered: