AEP 3rd party Private

[Lawrence Griffiths]

This page describes OATA but uses a Public preamble/syn word?

Conduit AEP: LoRa Use With Third-Party Devices

Why does the syn have to be public?
It’s my understanding that the Network Server should ignore all Public packets when configured for Private which is what I want.

Also there is a real confusion in TERMS which I think were used with the best of intent but wreck your head when reading LoRaWAN docs!! Can I confirm if I’ve got this RIGHT?

       AEP LoRa Server UI	| mDot AT		| LoRaWAN
------------------------------------------------------------------
Network ID:   testloRaWAN   	| at+NI=testloRaWAN   	| AppEUI
Network Key:  testO-0 		| at+NL=testO-0		| AppEUI	

• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.
• This topic was modified 9 years, 4 months ago by Lawrence Griffiths.

[Brandon Bayer]

Lawrence,

Most third-party LoRa devices use the public sync word. If you have third-party device configured to use the private sync word, then sure, you can use private on the lora server.

Here’s the terminology mapping:

Network ID  |  AT+NI  |  AppEUI
Network Key |  AT+NK  |  AppKEY

-Brandon

[Lawrence Griffiths]

Brandon thanks

[Author]

Posts