[Faustin Empis]

Hi Jason,

Your explanation is very clear, however I have the following situation :

3 LoRaWAN devices connected to a single gateway (AEP conduit with lorawan network server).
1 of the device has some trouble to communicate with the gateway (not because of distance but obstacles), with about 18% frames lost. This ratio can be improved/solved with better antenna (UFL antenna is connected to the LoRaWAN device, classic 3dbi antenna to the gateway)

Now my wondering is about the ADR management of the network server (ADR is enabled on device side).
I have a weird behaviour of my device with periods up to 12 hours with no frame lost, and other periods with about 1 on 3 frames lost. Maybe this is due to the environment (multiple walls, disturbance ?), but the device is static.
The device is started by default with SF9, but most of the time the ADR is down to SF7 even when the device has trouble to communicate. SF can be set at 8, then 9, 10, 11 by network server, and finally set at 7 for no specific reason (still transmitting the same frame)
Low Spreading Factor and lost frames do not coincide, I have cases where communication is good with SF7 for a long period, sometimes it is not.

The LoRaWAN device is class C, and sending unconfirmed frames (1 time, no ack required) with 58 bytes of payload most of the time (every 5 minutes), and sometimes 70 (3 times a day), 47 (1 time a day), and 80 (1 time a month).

Thank you

• This reply was modified 8 years, 3 months ago by Faustin Empis.

[Faustin Empis]

Hi mike,

Thank you for googling this for me 😉

The TTN link is very interesting, I’ll look into it in details, and see if I can test compatible USB dongles.

What I want is not to connect the gateway to a wi-fi network, but the gateway to have a wi-fi network reachable with a tablet for example (I have a use case where I will not have an access to a wifi network). But the video tutorial is nice and I may collect some elements.

Now I know that what i want to do is possible

Best regards,

Faustin.

[Faustin Empis]

Any suggestions someone ? 🙂

[Faustin Empis]

Hi Jeff,

Thank you for the answer, I’ll have to dig how to do it.
I already watched Node-RED a bit to see the possibilities, for now I was able to save the received frames on a file, about MQTT, I do not have a broker for now so I will try it later.

There is something I wonder, when I said :
“- 1 hour of transmission with no 3G, so packets are received on the Network Server but not sent to the Application Server.
– After 1 hour, up the PPP connection, and send every frames received in the hour at the same time, then cut the PPP connection.”

I meant send every frames in one block (like a file with the frames recorded on it), and not send frames one by one to unstack the buffer.

The real question here is about 3G data consumption between, for example :
– 12 frames sent in one hour every 5 minutes
and
– a single file containing the 12 frames after 1 hour of transmission

I think the issue is also about how a LoRa server is working :
– Here the frames are received on the Network Server of the gateway, fine.
– The Network Server has the information on which Application Server it has to send the frame
– So if a file with frames is to be sent from a Network Server to an Application Server, this is not the usual LoRa network process, so can it work anyway ? Maybe with a post-treatment of the file on the AS side after reception.

[Faustin Empis]

Ok thank you Jason.
Using the IMST LoRaWAN stack, so if I can send 51@SF12 that’s because their stack authorize it, but so this is not LoRaWAN compliant ?

[Author]

Posts