You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your task is to investigate a bug in the stepper motor functionality. When the stepper motor receives too many commands in quick succession, the device is not able to move any more. In my experience, the blue light on the module core continues to blink, but others have said the device disconnects from the network.
I do not believe this issue exists in the servo motors, as I have made a patch where the servo points in a random direction every 75 milliseconds and the device could keep up.
Some ideas (from Luke Geortzen) to get started include:
Test if this happens in AP mode, Client mode, or both
Try seeing if relay commands cause the same behavior (just set it to hook to pin 13, the LED), for testing purposes
Send servo commands without servo module instantiated (to verify it's not just the rate or processing something in the command)
What is the state of the device upon disconnect? Run it with the serial monitor and see what it prints. Does the device disconnect gracefully and try to reconnect, just carry on as if there's no connection, hang, etc.
When debugging the code on the arduino side, I would also recommend checking the dependencies. To me this seems like this might be some sort of safe gaurding behavior someone else implemented.
The text was updated successfully, but these errors were encountered:
Hello future URSA Researcher!
Your task is to investigate a bug in the stepper motor functionality. When the stepper motor receives too many commands in quick succession, the device is not able to move any more. In my experience, the blue light on the module core continues to blink, but others have said the device disconnects from the network.
I do not believe this issue exists in the servo motors, as I have made a patch where the servo points in a random direction every 75 milliseconds and the device could keep up.
Some ideas (from Luke Geortzen) to get started include:
When debugging the code on the arduino side, I would also recommend checking the dependencies. To me this seems like this might be some sort of safe gaurding behavior someone else implemented.
The text was updated successfully, but these errors were encountered: