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
I was seeing hangs and an eventual stack overflow randomly when testing this function. After testing several dozen tags in various stacks.
All the tags I have tested have UIDs that start with the same 3 bytes. Most have the same 4th byte. Out of 3 dozen or so tags only 3 cause the problem if they are within range of the sensor. And all of the tags that cause the issue have UIDs ending in 0.
The hang also happens when a tag with a UID ending 0 is the only tag in range of the sensor.
My suspicion is that this is caused by a bug in the implementation of the collision avoidance algorithm.
The text was updated successfully, but these errors were encountered:
I was seeing hangs and an eventual stack overflow randomly when testing this function. After testing several dozen tags in various stacks.
All the tags I have tested have UIDs that start with the same 3 bytes. Most have the same 4th byte. Out of 3 dozen or so tags only 3 cause the problem if they are within range of the sensor. And all of the tags that cause the issue have UIDs ending in 0.
The hang also happens when a tag with a UID ending 0 is the only tag in range of the sensor.
My suspicion is that this is caused by a bug in the implementation of the collision avoidance algorithm.
The text was updated successfully, but these errors were encountered: