Replies: 1 comment 2 replies
-
Bearing in mind that RadioLib can be used for LoRa point to point as well, the LoRaWAN layers over the top like So all LW config needs to do act on the node, in this case you to use the node.setDatarate() function. You can ask @StevenCellist when you meet him why it's DR for LW and SF for the radio. DR6 aka SF7 BW250 isn't in common use with TTN, hence it being greyed out in the calculator. The TxPower works in steps of two from 16 down in the EU. The TTS algorithm works to reduce the DR first to reduce airtime. the precious resource, and the LoRa Alliance expect providers to restrict the use of SF11 & 12 due to the time on air - which is also far more susceptible to interference from other transmissions due to the duration. So if you want to try the TxPower, do it on DR5. All that said, RF antennas a couple of inches above the ground are pretty poor radiators, so by the time you've got to DR5 it won't be working so well and reducing the power will only make it worse. In context for the vast majority of LW devices, ADR is on and the LNS just sorts this out - hence the suggestion to start at the very beginning, it's a great place for nuns teaching you to sing as well as many layered radio systems. Another approach to tracking which does work nicely is LoRa point to point which I use for High Altitude Balloon projects with schools - far more flexibility for small bursts of info and 433MHz has much better range. |
Beta Was this translation helpful? Give feedback.
-
Following discussion #1169, I noticed something else that confused me regarding the radio controls in RadioLib.
Summarizing that other discussion, I was able to connect my device to the things network and upload data. Right now I would really like to test the performance under different radio settings and see how often I can transmit under those settings according to law and FUP.
Following discussion #1170, where I asked this same question, I am reposting my question here with the parameters adjusted to fall within legal norms, according to suggestions by @StevenCellist and @HeadBoffin.
I have the following program:
As you can see, I am using node.setADR(false) to free myself from ADR, and then I try to set the spreading factor to 8. However, when I observe my uplinks on the TTN console, I see the following:
The spreading factor observed by TTN seems to still be 10. This is also confirmed by the duration of my uplink as reported by RadioLib:
Last uplink: 371
371 ms of airtime; which corresponds pretty clearly to an SF of 10 as per this airtime calculator
I have also tried an SF of 7, with a high bandwidth of 250 as specified by that airtime calculator, but I get the same result in the TTN console, including the lower bandwidth.
How do I change these settings? It doesn't seem like this is working right now, judging by the values reported by TTN and even RadioLib itself.
Beta Was this translation helpful? Give feedback.
All reactions