Hi, this is my 1st post on this forum and would like to thank you for the hard work on arduplane. I started with Arduplane around newyear 2021. Arduplane was the only OS that supported the Matek H743-wing that I had bought. It is installed in a AR wing pro with the Matek CAN gps and TBS Tracer as Rx and controlled by a TX16S transmitter. Furthermore a VTX. I installed arduplane v4.1.0dev and is still using this version after a huge amount of flights. It took a while for me to setup arduplane and gain full telemetry, but the award is a very well flying wing! On the 2nd flight I used autolaunch with success and have used it in every flight since. I really enjoy flying in the area where I live. My goal is now to upgrade to the 4.2.0 release. Furthermore, I would like to be able to see the live flight in missionplanner so a little more investigation is required from my side on how to do that . Thank you for the work!
ESCs do not get signals from Pixhawk Cube Orange. Motor signals are not visible in Mission Planner Servo Output. Board Arms fine, and all servos work ok. The flight controller operates the ESCs perfectly using ArduPlane 4.7.1 Official. So there is a problem with this beta version.
Does anyone have any suggestions how to get this beta version to work with the Pixhawk Cube Orange?
The flaperon function does not work in v4.2.0(BETA 2). On a F765-WING with version v4.1.7 they work almost perfectly (FLAP_SLEWRATE never worked for me). I update to v4.2.0(BETA 2) and the flaperons don’t work, I go back to v4.1.7 and everything works again; Obviously without changing anything in the configuration.
That is why I suppose that there is some problem or some change in the way of configuring it in v4.2.0 (BETA 2)
@Lano can you please send me a log file (from which I can extract your parameters).
I’d also like to know how you are testing (ie. how you are setting flaps).
The only significant change with 4.2 is that FLAP_SLEWRATE now allows for much slower slew rates. I’ve just tested flaperons in SITL for 4.2 and it is working fine for me.
I have performed a series of experiments below that will provide insite to the problem:
flashed Copter Official
flashed Plane 4.2.Beta
Turn on TX - Connect 4S bat - motors not tilt in responce to connection to flight controller - Connected MP via Mavlink Ant - MP not Arm - can see on params that things are not right
downloaded full scale param.file - MP arms
restarted system: tx on - Conn 4S bat - motors still not tilt in responce to connection to FC - wheel servos work - can see in Servo Outputs tilt servos not connected (no green bars) - see motors working!
connected battery to ESC and
*ESCs now working in Plane 4.2 Beta!!!
can see Q parameters have changed and some missing - Changed Q_Tilt_Enable=0 to =1 and reloaded full scale 001 param file - this fixed the missing Q params (before this it MP planner complained that 10 Q param missing, and gave a list!)
restarted system: TX on - 4S bat connect (now get correct tilt motor responce as FC connects) - MP Arms ok - can tilt front motors using rudder stick and TX right finger control
*But ESCs stoped working!!! - MP shows in Servo Output that there are no motor signals (no green bars)
These tests were interesting! We got the ESCs to work in Plane 4.2 Beta by changing Firmware from Copter to Plane. But the ESCs stoped working when we loaded the parameter file for the 2nd time after I set Q_tilt_enable=1 (note ESCs worked when I loaded the full scale 001 parameter file the 1st time). The problem seems to be one of the 10 tilting parameters that were missing and had to be activated using q_tilt_enable=1: the missing params included: q_tilt_type, q_tilt_max, q_tilt_yaw_angle, q_tilt_fix_angle, q_tilt_rate_up and dn …
We found the problem and have Plane 4.2 Beta now working well with my Pixhawk Cube Orange. The problem was that the pwm max/min parameters were set to zero. Once we set them to 2000/1000 respectively, the motor signals began to work properly and the ESCs started working.
The v4.2 log shows it is working fine. You have FLAP_SLEWRATE=1, which means the flaps move extremely slowly. A value of 1 means maximum of 1% per second, so it takes 100 seconds for your flaps to move through the full range. Try using FLAP_SLEWRATE=50 for a more reasonable value.
Thank you very much for the quick response. It’s clear that the FLAP_SLEWRATE parameter is set to a ridiculous value. I guess as in v4.1.7 it was never satisfactory and the flaperons worked (fast but they worked) I forgot about it and when I used v4.2.0(BETA 2) FLAP_SLEWRATE did its job.
Now I don’t have the possibility to reinstall v4.2.0(BETA 2) but when I can I will try it and confirm to you that it works correctly.
Pitch PID not working. Nav_Pitch signal tracks Pitch when motors off, But when motors turned on, Nav_Pitch signal rails to zero and does not track Pitch signal anymore. I am using the same PID values I used before using Arduplane 4.2 Beta. Here is a log file of the test:
I’m the guy building the F-35B.
I am running a YouTube channel.
Q_FRAME_TYPE = 0, Q_FRAME_TYPE = 16
There is no reaction of TailTilt Servo (Function 39).
I would really appreciate it if you could put a forced reaction option.
Is this only possible with a tricopter?