The original code uses a timer which runs every 500ms and this timer manages the state machine which uses the serial protocol to control the uTracer 3.
Debug was added to the protocol state machine which revealed that the timer continues to fire after the state machine reaches the full idle state. This is inefficient so add functions to control the creation and destruction of the timer object. This means the timer object only exists when the protocol state machine is running.
In addition, focus the various operation requests through a single function so that the GUI requests can be isolated from the protocol state machine.
The original code uses a timer which runs every 500ms and this timer manages the state machine which uses the serial protocol to control the uTracer 3.
Debug was added to the protocol state machine which revealed that the timer continues to fire after the state machine reaches the full idle state. This is inefficient so add functions to control the creation and destruction of the timer object. This means the timer object only exists when the protocol state machine is running.
In addition, focus the various operation requests through a single function so that the GUI requests can be isolated from the protocol state machine.