ACK received and not received at the same time?

Home › Forums › mDot/xDot › ACK received and not received at the same time?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • August 2, 2018 at 4:34 pm #25873
    Adam Haun
    Participant

    I’m talking to a custom Things Network server installation using an xDot. The data gets through just fine, but I seem to get a false error message on the ACKs. I’m using the latest development version (3.1.0-rc6-3). Here’s the trace output I see after calling dot->send():

    [DEBUG] Send with tx timeout 20000
    [INFO] Preparing frame
    [TRACE] NA: 26000296
    [TRACE] NSK: ed89f457d61d429faef01c4fe03b6244
    [TRACE] DSK: 85a4d624c77b09c6ebc49f438083ec3a
    [TRACE] Adding MIC to frame
    [TRACE] Sending 219 bytes
    [TRACE] Number of available channels: 8
    [DEBUG] Using channel 7 : 903700000
    [INFO] Configure radio for TX
    [DEBUG] Session pwr: 20 ant: 3 max: 21
    [DEBUG] Radio Power index: 20 output: 19 total: 22
    [DEBUG] TX PWR: 20 DR: 3 SF: 7 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0
    [INFO] Configure radio for TX
    [DEBUG] Session pwr: 20 ant: 3 max: 21
    [DEBUG] Radio Power index: 20 output: 19 total: 22
    [DEBUG] TX PWR: 20 DR: 3 SF: 7 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0
    [INFO] Rx Window 1
    [INFO] RxDone 12 bytes RSSI: -93 dB SNR: 57 cB
    [TRACE] Payload: 6096020026201000df62839c
    [INFO] Packet for 26000296
    [TRACE] Check downlink counter 00000010
    [TRACE] Ack received
    [TRACE] Empty payload
    [INFO] Packet Received : Port: 0 FCnt: 00000010 Size: 0 ACK: 1 DUP: 0
    [INFO] Packet RSSI: -93 dB SNR: 57 cB
    [ERROR] ACK not received

    Despite the error message, the missed ACK callback is not called, and there are no retry attempts. (Those things do happen if I turn off the packet forwarder. For some reason the missed ACK callback is called twice after the final retry attempt, once for RX1 and once for RX2.) The return value from dot->send() is -5 (MDOT_TIMEOUT). Am I configuring something wrong, or could this be a bug in the library?

    Thanks,
    -Adam

    September 6, 2018 at 4:34 pm #26283
    Adam Haun
    Participant

    I’ve updated to the latest stable release of libxDot and I still have this problem. Does anyone have any idea what’s going on?

    September 6, 2018 at 4:43 pm #26284
    Ryan Klaassen
    Blocked

    It may be due to the time it takes to process a packet or when the packet was recv. The timer will keep running until the packet is verified for that device. Once the packet is verified the ack timer gets killed. It may be the device verifies the packet just after the timer expires, where the print happens but the callback doesn’t.

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