kkhylchuk

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Get the number of ACK attempts #32308
    kkhylchuk
    Participant

    Channel Plan: US915
    ADR is enabled
    MultiTech’s Conduit, public network

    Indeed, I see incoming ADR commands:

    
    [DEBUG] ADR Set Redundancy 1
    [DEBUG] ADR DR: 0 PWR: 0 Ctrl: 07 Mask: 0002 NbRep: 1 Stat: 07
    [DEBUG] ADR Set Redundancy 1
    [DEBUG] ADR DR: 0 PWR: 0 Ctrl: 00 Mask: ff00 NbRep: 1 Stat: 07
    

    I tried calling setAck before each send, but no luck. The result is exactly the same.

    • This reply was modified 2 years, 3 months ago by kkhylchuk.
    • This reply was modified 2 years, 3 months ago by kkhylchuk.
    in reply to: Get the number of ACK attempts #32306
    kkhylchuk
    Participant

    Yes, that’s what I expected to see, but instead, I see this:

    
    ...
    [INFO] Preparing frame
    [INFO] Adjust PowerMax to 21
    [INFO] Configure radio for TX
    [INFO] Rx Window 1
    [DEBUG] mDotEvent - MissedAck : retries 0
    [INFO] Rx Window 2
    [DEBUG] mDotEvent - MissedAck : retries 0
    [ERROR] ACK not received
    [ERROR] failed to send data to gateway [-5][Operation Timed Out]
    [INFO] Preparing frame
    [INFO] Adjust PowerMax to 21
    [INFO] Configure radio for TX
    [INFO] Rx Window 1
    [DEBUG] mDotEvent - MissedAck : retries 0
    [INFO] Rx Window 2
    [DEBUG] mDotEvent - MissedAck : retries 0
    [ERROR] ACK not received
    [ERROR] failed to send data to gateway [-5][Operation Timed Out]
    ...
    

    I set the ACK retries to 8 like so dot->setAck(8).
    Calling dot->getAck() returns 8.

    Also, I should note that I’m using libmDot-dev v4.1.2.

    in reply to: Get the number of ACK attempts #32304
    kkhylchuk
    Participant

    Thanks, Jason.

    I implemented mDotEvent::MissedAck, but for some reason “retries” is always 0. I expected it to be equal to dot->getAck(). Or am I understanding this wrong?

    in reply to: mDot wakes up early #32291
    kkhylchuk
    Participant

    I see. Thanks for the quick reply.

    kkhylchuk
    Participant

    It worked. Thanks.

    kkhylchuk
    Participant

    Thanks for the reply, Jason.

    In handleTestModePacket (line 1409) there is a call to setAppPort:

    CommandTerminal::Dot()->setAppPort(224);

    which does not work (returns -1).

    The description for setAppPort says that the valid port value is 1-223. Do I need to do anything else to make it set the port to 224?

    Thanks.

    in reply to: mDot wakeup by RTC and interrupt #30738
    kkhylchuk
    Participant

    I see. Thanks for the reply.
    Where can I find the information about what version of the toolchain to use with a specific version of the library?

Viewing 7 posts - 1 through 7 (of 7 total)