I guess where I would start:
1. Remove and disassemble thruster, check out whether some sand or something bad got into the motor assembly.
2. On your arduino, set up serial output so that you can see the PWM signal being sent out in real time. This will tell you whether the arduino is still trying to run the thruster, but the thruster is stopped.
If the arduino is not sending out a good PWM signal (something between 1550-1900 ms) then the issue is in the program or arduino.
If the arduino is sending out a good PWM signal but the thruster is not running, and you checked out your thruster hardware already then the issue is in the power infrastructure (power supply, ESC). You could troubleshoot that by looking at the current draw of the power supply to see if it seems right, check signal coming to and from the ESC to the motor.
Totally possible that the code might be allowing the system to get into a stopped state and not out of it. Weird that it would take so long to expose itself, but definitely possible. The serial output view will show that. To do it just plug into your arduino with a USB cable and your computer and run the program with the serial output window open and check it out.
Good luck!
1. Remove and disassemble thruster, check out whether some sand or something bad got into the motor assembly.
2. On your arduino, set up serial output so that you can see the PWM signal being sent out in real time. This will tell you whether the arduino is still trying to run the thruster, but the thruster is stopped.
If the arduino is not sending out a good PWM signal (something between 1550-1900 ms) then the issue is in the program or arduino.
If the arduino is sending out a good PWM signal but the thruster is not running, and you checked out your thruster hardware already then the issue is in the power infrastructure (power supply, ESC). You could troubleshoot that by looking at the current draw of the power supply to see if it seems right, check signal coming to and from the ESC to the motor.
Totally possible that the code might be allowing the system to get into a stopped state and not out of it. Weird that it would take so long to expose itself, but definitely possible. The serial output view will show that. To do it just plug into your arduino with a USB cable and your computer and run the program with the serial output window open and check it out.
Good luck!

