I forgot to mention the main thing, servos are moving weird only when GPS lock is established.
Servos are connected direct to pwm rail. I have also tried different brand servos with the same result.
GPS, there are 2 Here in a custom casing.
I think this is fairly common, its just the gps signal bouncing about a bit, should stop one you move forward at any-speed.
i.e. if the gps lock is accurate to 1m or even tens on cementers when the aircraft is stationary this is seen as rapid changing direction of the velocity vector. Once you move forward a bit the inaccuracies are much smaller than the velocity vector and hence no twitchy servos. You should see it smooth out even at walking pace
I was thinking the same way, but till now on smaller (and lighter) VTOLS I have never seen servos moving so much. This one is much bigger (4m w-span and 30 kg) with a lot of carbon also…
I will try at walking speed first and some additional shielding under gnss and i will also enable logging at start without arming.
Just one another question not related to this topic.
Is there any difference in FW (on ChibiOS) between CubeBlack and fmuv3 for PH2.1?
Hello friends. I’m having the same problem, my traditional VTOL quad plus the rear engine airplane. The servos quit on and on when I connected the battery, I tested another servo and the same problem. The strange thing is that they stop picking when I take the quad motors off the PWM rail. I already tested without connecting the escs of the quad and tremble alike, it is not an ineference of ESC. I thought of mapping the channel 1 and 2 ports to auxiliary ports 10, 11. My impression is that the channels connected to the servos respond as if they had motors there. Any idea how to solve it? I’m with firmeware arduopilot 3.7.1