I have a Pixfalcon setup as shown in the build thread.
I have completed the setup and everything works on the bench as expected in both multi rotor and fixed wing- except, the left motor does not run in any case. (Testing in ACRO flight mode)
Problem is an apparent lack of signal on MAIN 2 servo pin connector.
Left motor will run if I move the signal to MAIN 1 or MAIN 3.
Continuity is confirmed from back of connector on PCB to the signal pin on the servo header and the solder joints look clean.
Iāve looked through parameters but Iām not seeing anything that would resemble disabling port MAIN 2.
ItĀ“s very important to do the compass cal with closed canopy cause only then the magnetic situation is the same as in flight. Both magnets connected reduce the magnetic interference to the fc. even better would be to remove this magnets completely ā¦ I had the same behaviour with the magnetometer calibrated without canopy.
The current version 1.7 rc 0 and 1 doesnĀ“t support my tilt mixer mentioned above anymore. I was able to fly it successful a few months with the 1.6 master from august.
The tilt mechanism mixer still works perfect while the elevon outputs are completely dead as soon as 3 or more sources are used by the tilt mixer.
Concerning the PX4 vtol mixer I have an additional basic question: I would like to add vectored thrust into the mixer that only adds stabilised roll and pitch to the tilt mechanism while in FW mode. Being able to do all this with only one PixFalcon ā¦ without the need of a second fc.
(a bit like the original Horizonhobby controller does it for roll)
Currently I experienced that such additions are present in all modes.
Where can I find the mixer that is active in FW mode only?
Which mixer does the differential thrust part in FW mode?
@taileron the differential thrust is handled by the vtol controller (tiltrotor.cpp), but should be done with a mixer.
If thereās been a regression since 1.6 please open a github issue with details to help track it down.
@dagar much thx I see itĀ“s documented inside the code ā¦ will try it. An issue is already in process #8312 the Z mixer of ch 4 can be changed in 1.7 without affecting the other mixers while in 1.6 all following mixers were shifted by one. The PWM limit of 2150us can be changed in drv_pwm_output.h
device: /dev/pwm_output0
channel 1: 900 us (alternative rate: 400 Hz failsafe: 900, min: 1080 us, max: 1943 us)
channel 2: 900 us (alternative rate: 400 Hz failsafe: 900, min: 1080 us, max: 1943 us)
channel 3: 900 us (alternative rate: 400 Hz failsafe: 900, min: 1080 us, max: 1943 us)
channel 4: 1500 us (alternative rate: 400 Hz failsafe: 2000, min: 995 us, max: 2005 us)
channel 5: 2449 us (default rate: 50 Hz failsafe: 1985, min: 701 us, max: 2450 us)
channel 6: 701 us (default rate: 50 Hz failsafe: 1030, min: 701 us, max: 2450 us)
channel 7: 1521 us (default rate: 50 Hz failsafe: 1522, min: 722 us, max: 2322 us)
channel 8: 1522 us (default rate: 50 Hz failsafe: 1522, min: 722 us, max: 2322 us)
@dagar now it might be that iĀ“m running into a small problem the 1.6.5 standard release crashes the plane sometimes.
The version currently on my plane that flies absolutely stable (master from beginning of september flashed by QGC) rejects very often rtl and missions.
1.7 doesnĀ“t support my tilt mixer anymore.
Is there a chance to get a master code version prior to 1.7 probably without the mixer issue for doing the real flight tests with increased pwm limits and retune the mixer
The first two flights of our Convergence after installation of Pixfalcon were failures. It flew ok in multirotor mode, but it didnāt do well in airplane mode.
Control surfaces deflected correctly on the ground prior to flight in stabilize mode in multirotor and both stabilize and manual modes in airplane mode.
I had a first pass at the log and what is very obvious is that the roll angle gets quickly out of hand. Interesting the set point stops in fixed wing mode, which might be according to configuration or the real issue - weāre checking that.
Hi, maybee IĀ“m wrong in this topic. I have build a convergence with pixfalcon. It flies in stabilized setup but I have very heavy uncontrolled yaw movements to the right and left side. How can I suppress theese unwanted movements?
sometimes I get an error āekf internal checksā especially when itĀ“s very cold outside. https://logs.px4.io/plot_app?log=7cfbc241-2751-4e95-910a-61fd803140ac
ThatĀ“s a log with the chinese PixRacer, now (after it got bricked - U304 burned, MPU gets very hot and doesnĀ“t boot anymore) I changed to an AUAV one.
But still āekf internal checksā sometimes (master feb.14th) . Sensors now are much more accurate with more reliable temperature readouts and no sensors inconsistent errors anymore.
Tried it, but got no reliable temperature readouts from the fc (listener sensor_mag / baro) and while a cooling fan blows into the electronics without cases, after few minutes the temperatures are showed way to high but almost stable.
Finally the āekf internal checksā donĀ“t really block arming, flying missions or rtl anymore. Is there a way to get more detailed information which sensors data is the source of this notification GYRO, ACC or MAG? ACC calibration I have to do out of the plane in the housing to make sure fc is aligned rectangular now temperatures rise much faster as builtin to the plane.
Log of a similar flight with new PixRacer (AUAV): https://logs.px4.io/plot_app?log=70945461-9ce3-477b-8c0f-e63fa5c5f55e
by disabling mag1 it was nearly possible to get rid of this error (only 1 time in 5 flights).
Currently two issues are left:
1 - IĀ“m using a second fc (for mixing vectored thrust in fw) in V1.6.5 it was possible to neutralise the yaw set value in stabilized mode by switching to acro for a short moment.
In vers above 1.7 the set value jumps back to the old heading when switching back to stabilized while the plane has to fly an extremely sharp corner.
Mostly I do transitions back to mc within gliding to the landing point without any yaw authority cause motors off / no builtin rudder the yaw set value changes a lot in this moment while gliding.
And gliding only works when the tiltrotors are swept upward to cause less drag. Another thing is when yaw isnĀ“t neutral one of the motors swivels into the airflow and begins to circulate and generates assymetric drag in the opposite direction of the yaw function and has to be corrected immediately by manual stick movement ā¦ very dangerous
Is there a parameter to reset the yaw set value to neutral before enabling stabilized mode?
2 - In mission mode there are massive yaw (roll) oscillations (mc) when there is heavy wind. It can only be corrected with a static tilt value e.g. 20 ā¦ 35 degree to result about 0 degree pitch relative to horizon (a bit nose up while fighting against the wind).
VT_WV_LND_EN 1
VT_WV_LTR_EN 1
VT_WV_TKO_EN 1
this parameters improved it only a bit
Does it make sense to lower VT_WV_YAWR_SCL to zero ?
WouldnĀ“t it make sense to try to stabilize pitch to horizon and add a tilt value to hover forward in missions?
For position mode I added some mixers into the tx and that works perfect even in very heavy wind (mixing an amount of tilt into pitch) https://review.px4.io/plot_app?log=3f05910f-a588-440c-80f2-f1a9cee1f6d7
this log contains a few transitions via zero throttle and gliding and a bit yaw oscillation in mission afterwards.
ā¦ with 1.8.0 rc0 from 10Ā“th of june my manual tilt mixer starts to work again
Which control group should be used for mixing into fw tilt to have elevons in mc (for gliding rotors up)
And roll pitch mixed into tilt only when rotors down fw
Currently roll/pitch is mixed allways into tilt and disturbs mc mode yaw:
