[Roman Ploskon]

and another question:

5. Referring to the LoRaWAN spec. 4.3.1.5, lines 20, 21: How the gateway is resetting the frame counter in case of personalized end-device (manual configuration)?

Thank you

[Roman Ploskon]

Hi,

Would you please be able to provide any update on this? I am unable to reproduce the issue seen at customer site:
1. Nodes successfully join the network.
2. Messages are being received by gateway and forwarded to our server.
3. Gateway is power cycled.
4. Several nodes seems to be no longer sending any messages (or at least our server is no longer getting forwarded messages from those nodes).

Re-joining the network seems to help.
Could you please give us any information how re-joining the network could help? This should not be related to “lease time”.

Thank you!

[Roman Ploskon]

Jason,
thank you for your reply. I looked into the Semtech’s reference implementation.
The difference is that they have center frequency set to 867.5 MHz unlike yours 869.5 MHz.

Center frequency 867.5 MHz leads to 867.1, 867.3, 867.5, 867.7, 867.9 which all falls under the h1.3 (note 5 – 1% duty cycle).

In your case, can I assume that 869.3 MHz is not going to be used at all or it is actually use under a band h1.3 but with 0.1% duty cycle (if that is permissible)?
And what about 869.7 MHz which is right the edge frequency of h1.7?

[Roman Ploskon]

Mike,
could you be please more specific about which channels falls within which band?
From what I have gathered there are:

h1.3 863-870 MHz; 25 mW e.r.p. (0.1%)
h1.4 868-868.6 MHz; 25 mW e.r.p. (1%)
h1.5 868.7-869.2 MHz; 25 mW e.r.p. (0.1%)
h1.6 869.4-869.65 MHz; 500 mW e.r.p. (10%)
h1.7 869.7-870 MHz; 5 mW e.r.p. (no requirement) / 25 mW e.r.p. (1%)

Thanks,

[Roman Ploskon]

Mike,
thank you. And what about AT+TXW? How the settings (on or off) affects behaviour of mDot expecially when acknowledgment is disabled?

[Roman Ploskon]

Does the command AT+TXN have any meaning for US? Could I use that command to check for expiration of second rx window?
Thanks,

[Roman Ploskon]

There is no such application need. I was just a little bit curious 🙂

[Roman Ploskon]

Mike,
Thank you for your repl.y Is it possible to see which channel has been used for transmission of last packet or is going to be used for next one?
Thanks,

[Roman Ploskon]

Jason,
thank you for your reply. Isn’t that frequency hopping automatically done by mDot for me? Or do I need to manualy change frequencies between packets?

[Roman Ploskon]

Also I would like to hear more on this topic. Presumably mDot is using more then one sub band as I am able to send several messages before starting to receive a response “no free channel”.

[Roman Ploskon]

Brandon,
Purchase order is from 9th of November 2015.
Thanks,
Roman

[Roman Ploskon]

Thank you Brandon,

the file was actually located under /usr/bin folder. For someone else’s benefit, I used a SCP client to copy the file to my machine.

Thanks,
Roman

[Roman Ploskon]

Hi Brandon,

could you please check my data as well? Thank you very much!

Roman

at+ping
-102,7.8

at+rssi
-97, -113, -97, -104

at+ping
-103,8.8

at+rssi
-108, -113, -97, -105

at+ping
-105,8.5

at+rssi
-108, -113, -97, -105

at+ping
-103,6.0

at+rssi
-97, -113, -97, -104

at+ping
-105,8.2

at+rssi
-114, -114, -97, -105

at+ping
-105,8.0

at+rssi
-97, -114, -97, -104

————————————–
Conduit:
Tx Power (dBm): 26

mDot:
Tx Data Rate: SF_7
Tx Power: 20

[Author]

Posts