AEP 3rd party Private

Home Forums Conduit: AEP Model AEP 3rd party Private

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #10181
    Lawrence Griffiths
    Participant

    This page describes OATA but uses a Public preamble/syn word?
    http://www.multitech.net/developer/software/lora/conduit-aep-lora-communication/aep-lora-use-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	
    
    #10194
    Brandon Bayer
    Blocked

    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

    #10201
    Lawrence Griffiths
    Participant

    Brandon thanks

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.