OTA join mdot fails (better tracing mdot)

Home Forums Conduit: mLinux Model OTA join mdot fails (better tracing mdot)

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #10999
    Andre Broers
    Participant

    Hello,

    I’m trying to write my own network server that handles the OTA join of an mdot. Everything works fine, I get the join request, i send the join accept and I see in the log on the gateway that the join accept message is send.

    ##### 2016-01-09 20:11:35 GMT #####
    ### [UPSTREAM] ###
    # RF packets received by concentrator: 0
    # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
    # RF packets forwarded: 0 (0 bytes)
    # PUSH_DATA datagrams sent: 0 (0 bytes)
    # PUSH_DATA acknowledged: 0.00%
    ### [DOWNSTREAM] ###
    # PULL_DATA sent: 1 (100.00% acknowledged)
    # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    # RF packets sent to concentrator: 0 (0 bytes)
    # TX errors: 0
    ##### END #####
    INFO: [up] PUSH_ACK received in 13 ms
    INFO: [up] PUSH_ACK received in 12 ms
    INFO: [down] PULL_RESP received 🙂
    INFO: [down] a packet will be sent on timestamp value 244744644
    INFO: [down] PULL_ACK received in 12 ms
    INFO: [down] PULL_ACK received in 12 ms

    ##### 2016-01-09 20:11:55 GMT #####
    ### [UPSTREAM] ###
    # RF packets received by concentrator: 2
    # CRC_OK: 50.00%, CRC_FAIL: 50.00%, NO_CRC: 0.00%
    # RF packets forwarded: 2 (184 bytes)
    # PUSH_DATA datagrams sent: 2 (674 bytes)
    # PUSH_DATA acknowledged: 100.00%
    ### [DOWNSTREAM] ###
    # PULL_DATA sent: 2 (100.00% acknowledged)
    # PULL_RESP(onse) datagrams received: 1 (205 bytes)
    # RF packets sent to concentrator: 1 (37 bytes)
    # TX errors: 0
    ##### END #####

    This is the output on the mdot.

    atz

    OK
    at+ni=0,0000000000000000
    Set Network ID: 00.00.00.00.00.00.00.00

    OK
    at+njm=1

    OK
    at+join
    Join Error – Failed to join network

    ERROR

    Is there a better way to see more specific (verbose) logs on what is going wrong on the mdot? Is there a way to snif all the packets that it receives so that I can see that it at least gets my join accept message and that it maybe doesnt validate the MIC or something?

    Kind regards.

    #11000
    Jason Reiss
    Keymaster

    The mDot will print debug on the mbed debug pins on the back of the module. This is available through the USB of the UDK.

    AT+LOG=6 will set the log level to max.

    If you are using 5/6 s join windows set AT+PN=1
    Since you received the JoinRequest I assume you have done this, unless you gateway is set for Private Network sync word 0x12.
    In that case the AT+PN=0 would match the sync word by the expected JoinAccept message will be at 1/2s on the mDot.

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