Microcontroller seems to hang and get reset if GOTO az 360degrees is given.

[Short-bus]

'pulsar' reported this in the discord group.
360Degrees is the movement limit for the azimuth motor. It's range is set to 0-360degrees, by default it will not move beyond 360 degrees unless the OptimiseMoves parameter is enabled.
It is likely that the telescope stops at or before the limit, or that it is wrapping round to 0Degrees - so the program never considers the move is complete.
Will test to see if the problem can be identified properly.

[Short-bus]

Test results confirmed when the azimuth moves to 360Degrees the microcontroller reports 0Degrees position, which triggers a fresh restart and a new move command to correct the situation. It will loop until the maximum number of resets has been reached, then it will declare failure. Program checking needs to handle the 360 = 0 azimuth result.