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
When disabling the EU868 Duty cycle limit using the latest commit 'v3.2.2-23' the channel count sometimes degrades after each transmission.
When using previous commit 'v3.2.2-22' the channel count remains at 12 after each transmission.
The 'getNextTxMs()' routine always returns 0 but even after waiting 10 minutes of no channel activity the channel count is still 0.
This is weird because i can't repeat it 100% each time but it's happened a few times during testing and the channel count doesn't match the different library versions.
I'm using the MultiTech gateway's internal network server and i've tested on multiple gateways with gateway v5 and v1.7.2.
Transmission interval is 10 seconds (just for range testing purposes)
With 'v3.2.2-22' [TRACE] Number of available channels: 12
Join is ok with the default 3 channels.
First TX 'v3.2.2-23' [TRACE] Number of available channels: 8
Second TX 'v3.2.2-23' [TRACE] Number of available channels: 6
Third TX 'v3.2.2-23' [TRACE] Number of available channels: 0
Fourth TX and beyond 'v3.2.2-23' [TRACE] Number of available channels: 0
..
The text was updated successfully, but these errors were encountered:
Hi,
When disabling the EU868 Duty cycle limit using the latest commit 'v3.2.2-23' the channel count sometimes degrades after each transmission.
When using previous commit 'v3.2.2-22' the channel count remains at 12 after each transmission.
The 'getNextTxMs()' routine always returns 0 but even after waiting 10 minutes of no channel activity the channel count is still 0.
This is weird because i can't repeat it 100% each time but it's happened a few times during testing and the channel count doesn't match the different library versions.
I'm using the MultiTech gateway's internal network server and i've tested on multiple gateways with gateway v5 and v1.7.2.
Transmission interval is 10 seconds (just for range testing purposes)
With 'v3.2.2-22' [TRACE] Number of available channels: 12
..
The text was updated successfully, but these errors were encountered: