Skip to content
This repository was archived by the owner on Jan 28, 2021. It is now read-only.
This repository was archived by the owner on Jan 28, 2021. It is now read-only.

Unhandled Ack messages #36

Closed
Closed
@matthewgkerr

Description

@matthewgkerr

When calling a command function (e.g setUART1Output) which results in the ublox module sending a response followed immediately by an ACK, I assume it is the intent of the library to process both the response and ACK before returning from the command function.
The function waitForResponse appears to exit as soon as either the expected ACK is received, or if the expected response is received.

I am seeing an issue where specific orders of commands is resulting in commands failing.
In my case, I'm calling setUART1Output then saveConfiguration. The second call is failing.

I'll do more testing tomorrow and add further details when I work out the cause of the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions