[luis santos]

Don’t exist one command that removes the packet queue of all devices?

[luis santos]

How can i remove all the queue msg?

[luis santos]

I didn’t change the default value of 16.

The commands don’t produce any result:

admin@AbrantesTorrePT:~# lora-query -x packet queue
admin@AbrantesTorrePT:~# lora-query -x packet queue json

But I have another gw that return results.

https://pastebin.com/1tPX1vEZ

https://pastebin.com/VfjmR8kb

cumps,

• This reply was modified 6 years, 10 months ago by luis santos.
• This reply was modified 6 years, 10 months ago by luis santos.
• This reply was modified 6 years, 10 months ago by luis santos.
• This reply was modified 6 years, 10 months ago by luis santos.

[luis santos]

Multitech have plans to include this packages in a near future? 🙂

Cumps,

[luis santos]

Tks Jason. You help a lot.

Edit:
One last question :).
the gw band 0 tx 1% dutycycle if for all end devices?

cheers,

• This reply was modified 7 years, 2 months ago by luis santos.

[luis santos]

Tks for all the support.
But now a notice another thing. I’m receiving a lot off “|WARNING| Duty cycle limit met – Band: 0 time-on-air available: 1044 ms” on the lora-network-server.

Can anyone explain me this warning? and ways to mitigate.

cumps,

[luis santos]

About the downlink queue. When a clear is sent to a specific EUI. It cleans only the queue msg for this EUI?

[luis santos]

Yes, both conduits have the same APPEUI and AppKey.
Yes, the End-devices got the same AppEUI and APPKey.
On the end-devices the only way to change the appEUI or appKey, is locally reprogramming the firmware.

[luis santos]

Hi,

Yes I’m using the built in network server on both gateways.
Changing the AppEUIs is not a option.

Before the new release of AEP. I try to use the whitelist, but some nodes continue jump between gateways when doing otaa join.

cumps,

[luis santos]

After read the documentation. I found that this options:
Address Range Start
Address Range End.

Buy i not sure how can a put single address. Must be range of address?

[luis santos]

No.
I’m very happy with the conduit gateway.

Cheers,

[luis santos]

For me the better solution, is to change the Laird lora module that i’m using now, for a new one that don’t need to make a lora join every time e wakeup from a deep sleep.

tks,

[luis santos]

To stop the network server from sending the first downlink, clear the queue on joined event or when the first uplink is received. Then queue your downlink packet.

Send MQTT message with topic
lora/<DEV-EUI>/clear

Your tip help. Now the lora node receive the first dowwlink.
But I not happy with this kind of solution. But for now, this must do.

Tks,

• This reply was modified 7 years, 5 months ago by luis santos.

[luis santos]

Cool, for the next project I will suggest the xDot.
I have one question about the xDot. Is possible used the xDot as class C lora?

[luis santos]

Hi,

After talking with Laird. They respond this.

“Unfortunately because all communication is terminated when the module goes into deep sleep to conserve power, you will always need to rejoin when the module wakes. The only way to prevent needing a new join request would be to keep your module in standby doze mode rather than deep sleep.”

[luis santos]

Well. The device do ota join, send data, receive data, deep sleep 6h, wake-up do ota join, …, sleep 6h.
The reason i do a ota join every time the device wake-up is because i put the laird rm186 in deep sleep, and from what i’m aware this module when go in deep sleep lose the session info.

• This reply was modified 7 years, 5 months ago by Jason Reiss.

[luis santos]

Ok, I was not aware of that. So after doing a join, the node need to send 2 packets (uplink) before received the first gateway payload?
For a battery powered device this kinda sucks.

tks,

[luis santos]

Tks for the quick response. So it’s not possible to send data on the first downlink?

[Author]

Posts