Telemetry OK but Torqeedo Cruise 3.0 TL not spin

Hi everyone,

ArduRover 4.6 introduced the very nice feature of controlling two Torqeedo motors, so I decided to give it a try. Unfortunately I can arm the vehicle, but the motors do not respond to RC throttle at all.

Hardware
Holybro Pixhawk 6X (Standard)
2 × Torqeedo Cruise 3.0
Torqeedo 24 V 3500 Wh

I plug the Tiller connector of each Cruise motor into a Japan Drones RS-485 converter board. The converter’s UART is connected to the Pixhawk TELEM port.
![IMG_4720|375x500, 50%]


(upload://ysvPaX4KIRqZmdUfvxkyweyKn6P.jpeg)

Pixhawk arms without any error messages. When I raise the RC throttle stick, neither motor reacts. ESC / RPM / current values in ESC_TELEMETRY_1_TO_4 dont change.

Addition photo
Screenshot of the Mission-Planner status messages


A short .bin log captured while arming and moving the throttle

Screenshot of all parameters I have set

Can anyone spot what I am doing wrong, or suggest things to check next?

Thank you in advance for any help!

1 Like

Hi @anhong4685,

Thanks very much for the report.

I guess a single motor does work but two does not?

Thank you for your reply.
Even when I try to operate it with just one motor, it arms, but the motor doesn’t spin.

One more thing I’m curious about — does the calibration of the Torqeedo affect motor operation when using it with the Pixhawk?

Hello,

I am attempting to restart my project using ArduPilot Rover to connect two Torqeedo Cruise 3.0 Tiller motors.
I am currently experiencing a similar but different issue and would like to ask for some help.

Problem


Communication is functioning correctly, but the motors are not working.
As shown in the picture, communication appears to be normal, and it seems that throttle commands are being sent via the RC. However, the dspd value does not change even when I increase the throttle.

Questions

Why isn’t the dspd value changing?

Are my parameters configured incorrectly?

Is my hardware configured incorrectly?


My current system is configured as shown in the attached diagram. Could this hardware configuration be causing the problem?

Thank you for your help.