Set RX2 parameters
-
@kersing I'm also interested in this. Have you found a solution?
-
No. For the time being I've put my pycom devices to the side. I'm using other LoRaWAN devices where questions about basic usage are answered...
-
Does this mistery network send the correct RX2 data rate in the DLsettings section of the OTAA join accept response?
If so I believe the LoPy will pick it up automatically.
-
@jmarcelino Yes it does. However the response is send in RX2 at SF9 so the LoPy is not able to receive it and adapt the parameters of the stack.
-
@kersing
That sounds like a bug on the network server side and deviation from the LoRaWAN standard... and I remember someone with your name posting a fix for it ;-)https://github.com/kersing/ttn/commit/915bb5e22dd1e78859b35f00b16edcf528cfec58
If you can't fix the network server the only workaround I know is to force it on the C code, as it's also done for Semtech's own broken server
-
@jmarcelino Actually as LoPy is a development board we would like to have under control all parameters and RX window is the one which is mostly customized by guys who want to play with LoRa. I'm currently trying to get downlink data in Lopy and as no examples worked for me wanted to try different options with RX windows.
-
@jmarcelino said in Set RX2 parameters:
That sounds like a bug on the network server side and deviation from the LoRaWAN standard
In this case it is an choice of the network operator for their development network. Checking the LoRaWAN specification (regional parameters document) it states: "The default parameters are 869.525 MHz / DR0 (SF12, 125 kHz)".
I'm not sure whether "default" implies mandatory. If not the operator is free to choose other settings... -
@kersing
My interpretation of "default" means until/unless a different parameter has been selected via the DLsettings mechanism.One major goal of LoRaWAN and the LoRa Alliance is to guarantee interoperability so (public) networks and certified devices shouldn't really be using different core settings that break that interoperability.
-
Hey, have you found a solution for this?
-
@prashanth I have seen that TTN uses SF9 @ 869.525 MHz for the RX2 response. There is a rational that a gateways can send with higher power at that frequency, and therefore cover the same distance, while having shorter transmission times. That works, if the node has been connected with OTAA. In that case the RX2 parameters are sent to the node.
I was a little bit surprised when I stumbled over that.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login