hu-zza / ubot_firmware Goto Github PK

Method: GET
Accept: application/json or /

45° left: http://192.168.11.1/command/DRIVE_K // freezes
45° right: http://192.168.11.1/command/DRIVE_Q // freezes

The processing is same in each case:
ubot_turtle#move resolve the char / int by _moveCharMapping dictionary.
This dict helps converting ints to direction-duration int tuples.
ubot_turtle#move passes this tuple as separate arguments to ubot_motor#move.

The processing is successful, the webserver sends it's reply, but after that it
is not respond, and the motor module also stucks in processing:
motor.isProcessing() is true, _moveList is []
motor.move(0,0), motor.stop() and then motor.resume() helps...

Motor module is autonomous and that's right.
However, if I run a broken turtle program...
...or just want to pause execution for observing...
...then this autonomy is a problem.

ubot_motor#stop, ubot_motor#resume is a good base,
but how can I reach them from one of the UIs?

Wireless: No chance, because it should stop handling
requests until ubot_motor / ubot_future is done.

Buttons: Maybe... Now it's a miracle well of motor freeze cases.