-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Dismatching device coderate #51
Comments
Update: If using the ChirpStack Gateway OS (which uses the Concentratord instead of the UDP packet-forwarder), the downlinks are working fine with coding-rate "4/5". I did notice that the 2.4 GHz UDP packet-forwarder only accepts "4/8LI" as downlink coding-rate (https://github.com/Lora-net/gateway_2g4_hal/blob/master/packet_forwarder/src/lora_pkt_fwd.c#L1686), however "4/5" is a valid coding-rate in the HAL (https://github.com/Lora-net/gateway_2g4_hal/blob/master/libloragw/inc/loragw_hal.h#L74). Nothing in the ISM2400 proposal states that downlinks must use "4/8LI" as downlink coding-rate. I have asked Semtech if they can confirm the correct downlink coding-rate for ISM2400 and also if they could make this explicit in the ISM2400 document. |
I just got the confirmation that 2.4 GHz must indeed use "4/8LI" as downlink coding-rate. This means that we need to add the LoRa coding-date to each region configuration (or |
The above commit fixes this issue. |
Dear @brocaar, I see in chirpstack v4 chirpstack/chirpstack/src/downlink/helpers.rs, here only
chirpstack_api::gw::CodeRate::Cr45.into()
is used for all devices despite their requested coderate:I believe that’s why I face this warning in my packet-forwarder:
chirpstack forum
and I believe that’s why I face infinite loop of
Join Request
from my deviceISM2400
.P.S.: In my opinion this behaviour is wrong, since device may have different coderates - not only
4/5
The text was updated successfully, but these errors were encountered: