lora-network-server whitelist and mote personalisation not working

Home Forums Conduit: mLinux Model lora-network-server whitelist and mote personalisation not working

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #22786
    Pramod Mynampati
    Participant

    Hello all,

    Summary of my problem – Hoping for any insights

    Hardware:
    Multitech Conduit 210L MTCDT
    MTAC-LORA-868

    Software:
    mLinux: 3.3.22
    lora-network-server: 2.0.16-r2.0

    Background:
    1. I am currently playing with the conduit mLinux model (210L) and testing with an mbed SX1276 lora mote. I am running the mbed demo example (number 76)

    2. Rather than doing the OTAA, I am doing ABP

    I have added the mote deveui, appeui, appKey to the whitelist section of the config file in the server (lora-network-server.conf).

    Issue:

    1. I can see the packets being rxvd but I get the error of Message rejected due to unknown device.

    Tried:

    1. Added the mote devAddr as mentioned in the below link
    http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/conduit-mlinux-lora-use-third-party-devices/

    But when I do the node add command – I am getting a syntax error

    So,
    Have anyone tried ABP with a thrid party device before.

    Any help would be appreciated

    Kind Regards

    #22787
    Jason Reiss
    Keymaster

    To see all options for network server commands`
    # lora-query -x help`

    For ABP device registration first a device record is added then a session created for the device. The appeui will be attached to uplinks, the joineui is for recording purposes, it would have been sent in an OTA join.

    
    # lora-query -x device add '{"deveui":"00-80-00-00-00-00-e1-9c","class":"C"}'
    
    # lora-query -x session add 
    '{"deveui":"00-80-00-00-00-00-1-9c","dev_addr":"00112233",
    "appeui":"00-88-88-88-00-00-e1-9c","joineui":"00-99-99-99-00-00-e1-9c",
    "net_id":"000017",
    "app_senc_key":"531bd9c5ec5d8ba5ef3b262cebfb3e66",
    "fnwk_sint_key":"531bd9c5ec5d8ba5ef3b262cebfb3e66"}'

    The whitelist is for OTA devices, records in the list should be as follows:

    
    { "deveui": "", "appeui": "", "appkey": "", "class": "A" }
    • This reply was modified 6 years, 1 month ago by Jason Reiss.
    • This reply was modified 6 years, 1 month ago by Jason Reiss.
    • This reply was modified 6 years, 1 month ago by Jason Reiss.
    • This reply was modified 6 years, 1 month ago by Jason Reiss.
    #22792
    Pramod Mynampati
    Participant

    Thank you for your message.

    I am able to add the device successfully, but whenever I try to add the session I fail.

    I am getting ‘Failed to create session’

    I tried restarting the server but I still get the same error.

    #22799
    Jason Reiss
    Keymaster

    Is the dev_addr being used by another device?

    The lora-network-server log may have more details.

    #22802
    Pramod Mynampati
    Participant

    Hello Jason,

    Thank you for your message.

    I found the issue in the sense that my app eui was being set to 0.

    Having fixed that – I can get the server working.

    Many thanks for your patience and help

    Kind Regards

    #22803
    Jason Reiss
    Keymaster

    Good to hear you are successfully working with the new server code.

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