The planner is showing the input to the servo and the servo rail is powered because there is no response from the servo. Why is this happening?
What kind of flight controller is it? Some boards don’t power the servo rail so you need to supply voltage for the servos.
Is the plane armed? Have you set safetys?
1 Like
I’m using a Cube Orange and the servo rail is being powered by the BEC circuit of the ESC. I’ve also just started to experience problems where the Throttle in the Servo Output page does not move even when armed (but other control surfaces do give a pwm signal). However the RC does seem to be communicating with the FC as it shows inputs in the radio calibration page of mission planner.
You’ve posted in VTOL so you need to tell us more about the plane. What is the configuration of the plane? Are you using Bdshot? What kind of ESCs? What firmware did you install? Share your param file. How are you testing the throttle outputs? What throttle outputs are you testing, because if it’s a VTOL there’s going to be more than one. In a VTOL, in some configurations the only meaningful way to check the motors is the Mission Planner motor test function. Running the throttle may be fun but it doesn’t tell you anything, and more often just confuses new builders.
1 Like
The VTOL is in a tricopter configuration with two front tilting motors and using vectored yaw. We are using a CubeOrange flight controller with communications to the radio using ELRS. The ESCs we are using are Sequre SQESC 28120 (AM32) connected to XING 4214 2-8S X CLASS FPV Motor 660 KV.
We managed to get the servo output display for the throttle working after setting the Flight Mode to Manual. We also managed to get one of the 3 ESCs show a green light after setting BRD_SAFETY_DEFLT = 0, the other 2 escs are still showing a red light.
After we got one of the ESCs showing a green light, we tried the motor test function in mission planner and only that motor spun up (which makes sense). However, when we are giving throttle inputs through our RC it is not spinning up.
The parameter file, a video of the ESC and motors beeping when powered up and armed, and the wiring diagram of our VTOL is attached. Thank you.
VTOL_26MAR.param (22.5 KB)
To take advantage of AM32 firmware on those ESCs, move them to Aux 1,2,3. Move the servos on those pins to the Main out.
You may need to re-flash the cube with bdshot firmware. This is worth it because if the ESCs are AM32 it will allow you to get a better tune using RPM sensing filters.
Setup the motor outputs for BLheli32/AM32 outputs with Bidirectional Dshot.
https://ardupilot.org/plane/docs/common-blheli32-passthru.html
Use the Mission Planner motor test to check the motors. It will need to be in a VTOL mode for this to work. Q-stab is easiest. Forget arming and testing that way, it’s just screwing you up.
2 Likes