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
Update airtime calculation to track in milliseconds instead of seconds.
a 24 byte packet at SF7->SF9 with a bandwidth of 125kHz will take at most 267ms. This will be rounded down to 0s in the current implementation.
We need better resolution.
Fix is to switch to 32bit counters and track milliseconds instead. This will double the memory requirement, but it would be needed to track usage of faster spreading factors.
Memory usage can be reduced by changing the number of periods we log.
The text was updated successfully, but these errors were encountered:
mc-hamster
added a commit
to mc-hamster/Meshtastic-device
that referenced
this issue
Jan 15, 2021
Update airtime calculation to track in milliseconds instead of seconds.
a 24 byte packet at SF7->SF9 with a bandwidth of 125kHz will take at most 267ms. This will be rounded down to 0s in the current implementation.
We need better resolution.
Fix is to switch to 32bit counters and track milliseconds instead. This will double the memory requirement, but it would be needed to track usage of faster spreading factors.
Memory usage can be reduced by changing the number of periods we log.
The text was updated successfully, but these errors were encountered: