Plane 4.3 stable release


I’ve just released plane 4.3.1beta1. This is a minor update with some useful enhancements and fixes:

  • fixed build with gcc 11.3
  • fixed random number generator in lua core
  • scale VTOL angle P with airspeed in quadplane back-transiton
  • added support for implementing AUX functions in lua scripts
  • fixed BMI085 accel scaling
  • fixed KSXT NMEA parsing affecting position resolution
  • fixed race condition in TECS control leading to ‘nod’ in forward transition
  • allow for expansion of notch filters to fix notch of fwd motors in quadplanes
  • added logging of TECS target alt

In case you are not familar with loading beta releases, this is how to do it with MissionPlanner:

Please test and report back!

1 Like

Sterling work as all ways Tridge,thank you

What board is this on?

@andyp1per it is Matek F405wing

Ok, here is a build with tramp debug turned on for Plane 4.3. Unzip it and upload the apj to your board using mission planner:

arduplane.zip (651.8 KB)

To see the debug you will need to use mavproxy - MAVProxy — MAVProxy documentation - please try it and show me the console output.

4.3 No problem so far. Thanks.

I am sorry I don’t how to use mavproxy. here is what I get.

MAV> Traceback (most recent call last):
File “site-packages\mavproxy-1.8.6-py3.5.egg\MAVProxy\modules\lib\wxconsole_ui.py”, line 52, in on_menu
File “site-packages\mavproxy-1.8.6-py3.5.egg\MAVProxy\modules\lib\mp_menu.py”, line 66, in call_handler
File “site-packages\mavproxy-1.8.6-py3.5.egg\MAVProxy\modules\lib\mp_menu.py”, line 280, in call
TypeError: object of type ‘map’ has no len()

Are you on windows? Did you use the .exe installer?

yes mine os is windows 10. installed under program files X86. run Mavproxy. while 405wing connected to Mission planner. run Mavproxy, the white window pops then click Mavexplorer then click Open. then I got info on the black window.

You need to do “add link”:

when I click Mavproxy. here is what the blackwindow showes,

Auto-detected serial ports are:
COM3 : ArduPilot (COM3) : USB VID:PID=1209:5741 SER=45003D0008504D4254393920 LOCATION=1-1
Connecting to COM3 : ArduPilot (COM3) : USB VID:PID=1209:5741 SER=45003D0008504D4254393920 LOCATION=1-1
Connect COM3 source_system=255
Running script (C:\Users\Jazzplane\AppData\Local\MAVProxy\mavinit.scr)
Running script C:\Users\Jazzplane\AppData\Local\MAVProxy\mavinit.scr
→ set moddebug 2
→ module load help
Loaded module help
Unknown command ‘graph timespan 30’
Log Directory:
Telemetry log: mav.tlog
Waiting for heartbeat from COM3
MAV> online system 1
RTL> Mode RTL
APM: ArduPlane V4.3.0beta1 (219ad27d)
APM: ChibiOS: 75a01029
APM: MatekF405-Win 003D0045 424D5008 2039395
APM: RCOut: DS150:1-2 PWM:3-10
APM: IMU0: fast sampling enabled 8.0kHz/1.0kHz
Flight battery 100 percent
APM: PreArm: 3D Accel calibration needed
APM: PreArm: Compass not healthy
APM: PreArm: GPS: waiting for home
APM: PreArm: Radio failsafe on
Received 1108 parameters
Saved 1108 parameters to mav.parm

Ok, can you try doing this immediately after the board boots to see if there is any tramp output?

OK,this is what i got

Auto-detected serial ports are:
COM3 : ArduPilot (COM3) : USB VID:PID=1209:5741 SER=45003D0008504D4254393920 LOCATION=1-1
Connecting to COM3 : ArduPilot (COM3) : USB VID:PID=1209:5741 SER=45003D0008504D4254393920 LOCATION=1-1
Connect COM3 source_system=255
Loaded module graph
Loaded module console
Loaded module map
Running script (C:\Users\Jazzplane\AppData\Local.mavproxy\mavinit.scr)
Loaded module help
Log Directory:
Telemetry log: mav.tlog
Waiting for heartbeat from COM3
Detected vehicle 1:1 on link 0
Received 1108 parameters (ftp)
Saved 1108 parameters to mav.parm
Saved 1108 defaults to defaults.parm

Can you post your full parameter set

yes sure. please check it.

There is no tramp setup in those parameters

sorry,I did not do param restore after the firmware flashed you sent to me. I have done it check it pls

Ok, please now do the mavproxy test again

Do i need to power the FC with the battery or only USB cable power. is VTX needs to be connected if it is battery powered?

VTX needs to be powered. Most VTX’s require battery power to work - but not sure whether yours does