Hm. I may need do write a new extension tonight to go ahead and grab all of the details to help troubleshoot these reports . In the meantime, here is a semi-quick guide for debugging the thrusters. Please let me know if this helps in isolating what is going wrong.
Primer on the motor telemetry values
In the telemetry screen, there is one setting: Motor(1500,1500,1500) and another Mtarg(1500,1500,1500). Where the numbers inside represent the value being sent to the thruster (Port,Vertical,Starboard). Motor is the actual value that has been sent, Mtarg is the value the browser has sent to it. The values for the motors are between 1000-2000 where 1500 is neutral (stopped). Technically these values are the PWM pulse widths in ms.
There are two things that will cause a difference between Mtarg and Motor.
- Is software smoothing is enabled, the Mtarg will be ramped up to over time.
- If the motor is reversed your see the the opposite value. (instead of 1700 which is 1500(neutral)+200, you will see 1300( which is 1500(neutral-200).
Given your description I am curious what the motor values are when you are using the software.
If the MTARG value is still 1500 on the port thruster when thrusting forward it indicates the command never made it to the micro controller which may mean the message was corrupted and rejected.
If the MTARG value seems to be changing on both motors and the port motor is not spinning I would then check the MOTOR value. If it is still neutral (1500) then the firmware failed to send the command to the servo at which point I would check the value of the MTRMOD value in telemetry.
Primer on MTRMOD telemetry data
MTRMOD stands for Motor Modification Value. It is a floating point number that is multiplied to the target PWM value being sent to the motor. When you reverse a motor in the UI it causes the MTRMOD value for the motor to be multiplied by -1, essentially flipping the direction.
MTRMOD(1,2,1,2,1,2) where the values are (Port Forward, Vertical Forward, Starboard Forward, Port Reverse, Vertical Reverse, Starboard Reverse).
I would basically be checking to ensure none of the values are zero.
If the MOTOR values seem correct and the thruster is still not turning… well then we have a bigger mystery as we are properly sending the right signal to the ESC. We can tackle that problem if and when it happens.