Packet loss in Lorawan

[jcaron]

@rpct In the general case, changing the frequencies after the join (and a few packet exchanges) could be different as the gateway can give instructions to the node about which channels to use.

Not sure if the nano-gateway code does anything like that...

[bmarkus]

@jcaron said in Packet loss in Lorawan:

@rpct In the general case, changing the frequencies after the join (and a few packet exchanges) could be different as the gateway can give instructions to the node about which channels to use.

Not sure if the nano-gateway code does anything like that...

Gateways never give instructions (more precisely MAC commands) to devices, it is up to the Network Server. Gateways do not have encryption keys nor any knowledge on devices.

[chumelnicu]

@jcaron The node is to close to gateway ...

[hajermet]

@rpct how did you import the network module please? I'm new to pycom and I'm having problems with that . Can you help?

[rpct]

@chumelnicu could you be more precise about mechanisms causing packet loss when gw is too close from node? How can we calculate minimum distance? How can we check a node is too close?

[robert-hh]

@rpct try to delete all channels but one after joining. That solved it for me

[chumelnicu]

@rpct To much power could bring lora module in supra-saturation ...For that is important to have a minimum distance between node and gateway .... Just try to put the gateway in other room

[jmarcelino]

@robert-hh

That’s only true for single channel gateways (using a Lopy as a nano-gateway). When using a real, full, LoRaWAN gateway you should keep all the channels.

Real gateways also have more sensitivity it’s recommended that nodes are least 2 meters away to avoid overloading the RX amplifiers.

[robert-hh]

@jmarcelino as far as OI read it, that's the case here.

[jmarcelino]

Yes thanks @robert-hh,

Just wanted to make it clear to anyone looking this answer up for the more generic node - gateway separation concern that was being discussed