LoPy Lora - randomly goes offline/unable to sent messages for few hours
-
What region are you in? What frequencies are you using? What data rate(s)? Are you using ADR? What are the observed RSSIs and SNRs? What's the distance? Are you indoors or outdoors? What antennas are you using (both on the LoPys and on the gateway)? Are the 15 seconds randomised?
-
Thanks for responding!
What region are you in?
EuropeWhat frequencies are you using?
686.1What data rate(s)?
Min = 0 max = 5Are you using ADR?
NoWhat are the observed RSSIs and SNRs?
RSSI Between 60-76 dBm
SNR Between 8-10.8 dBWhat's the distance?
Between 6 and 20 metersAre you indoors or outdoors?
IndoorWhat antennas are you using (both on the LoPys and on the gateway)?
On the gateway standard external antenna
In our nodes, an PC81 Taoglas antanna (internal)
https://www.taoglas.com/wp-content/uploads/2015/06/PC81.07.0100A.dB_.pdf

Are the 15 seconds randomised?
No -
Hi @mronday
I'm not saying it's the cause of the problem but unless it was tested and really as intended sticking an antenna, especially one of that type, to any metal surface - even worse to the metal RF shield of the LoPy - is a bad idea.
-
Screenshot gateway RX messages

Our Lora channels in LoPy
lora.add_channel(0, frequency=config.LORA_FREQUENCY, dr_min=0, dr_max=5)
lora.add_channel(1, frequency=config.LORA_FREQUENCY, dr_min=0, dr_max=5)
lora.add_channel(2, frequency=config.LORA_FREQUENCY, dr_min=0, dr_max=5) -
Hi Marcelino,
We've also some old test models with an external antenna (like the one on the gateway). Those nodes also having this strange problem of going offline for a few hours randomly.
Thanks for reply anway, we'll change the position of the antanna's within the case.
-
@jcaron said in LoPy Lora - randomly goes offline/unable to sent messages for few hours:
Are the 15 seconds randomised?
Very interesting. That is indeed a valid & good question, that could explain the beat character of the effect.
-
Hi Robert,
Could you explain the beat character? Do you mean that because we didn't randomize the 15 seconds, it explainable that an node is offline for a few hours?
-
@mronday Yes, because then two nodes may try to send at the same time and interfere. Since the clocks of the node are not exactly the same, that situation will disappear after a while, and come back. For that, the difference of the crystals can be in the order of 10^-6, which is totally reasonable. A randomize send timing would avoid longer periods of collisions.
-
@mronday A few comments:
-
If you keep the 15 second interval and go beyond SF8, you'll be in breach of the duty cycle regulations. Remember they are not imposed by the networks, but by national/transnational regulations. Those bands are shared, they imply limits on power and duty cycle (or LBT-AFA, but that's another topic).
-
Even at SF7, on a single channel, 10 nodes emitting every 15 seconds implies an average collision rate of over 5%. If you get to 40 nodes, the collision rate will get to 25%. If you increase the SF, well, you'll quickly get to 100% collisions...
-
The fact that your interval is fixed (but not 100% exactly) means that two nodes that emit very close one after another can drift into colliding every time, then back into being slightly apart, and so on. If you randomise the interval, you would more likely see collisions spread a bit randomly rather than concentrated on a single node (it should actually be two, isn't that the case?).
-
If you check your logs, you probably have another node emitting at nearly exactly the same times, don't you? And it should also fail during approximately the same periods.
My advice:
-
Forget about sending every 15 seconds. This is definitely not what LoRa was intended for, and you'll run afoul of regulations quite quickly (not to mention power issues if you're running on batteries...).
-
Use more frequencies to reduce the risk of collisions.
-
Add a random element to your interval. You'll have collisions, but they won't be a long series affecting the same two nodes for a while, it'll be more random and probably more manageable.
-
-
Hi Jcaron,
Thanks for your explaination.
-
We'll make te intervals longer so that we don't breach the regulations.
-
I understand what your saying, but could you describe how you calcluate the collision rate?
-
The strange thing is, that almost every time it is a single node who is not recieved well by the gateway. Not always two nodes at the same time. They are indeed close to each other, but we're now testing it with one node, to see how that works.
-
We'll add a random interval.
I'll post if this changes solved our problem.
-
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