ROMFS/px4fmu_common/init.d/airframes/4500_clover4

#!/bin/sh
#
# @name COEX Clover 4
#
# @type Quadrotor x
# @class Copter
#
# @maintainer Oleg Kalachev <okalachev@gmail.com>
#
# @board px4_fmu-v2 exclude
# @board intel_aerofc-v1 exclude
# @board bitcraze_crazyflie exclude
#

. /etc/init.d/rc.mc_defaults

set MIXER quad_x
set PWM_OUT 1234

if [ $AUTOCNF = yes ]
then
	param set MC_PITCHRATE_P 0.087
	param set MC_PITCHRATE_I 0.037
	param set MC_PITCHRATE_D 0.0044
	param set MC_PITCH_P 8.5
	param set MC_ROLLRATE_P 0.087
	param set MC_ROLLRATE_I 0.037
	param set MC_ROLLRATE_D 0.0044
	param set MC_ROLL_P 8.5
	param set MPC_XY_VEL_P_ACC 2.2
	param set MPC_XY_VEL_D_ACC 0.26
	param set MPC_XY_P 1.1
	param set MPC_Z_VEL_P_ACC 4.8
	param set MPC_Z_P 1.2
fi
Add COEX Clover 4 airframe 2019-11-12 02:17:29 +03:00			`#!/bin/sh`
			`#`
			`# @name COEX Clover 4`
			`#`
			`# @type Quadrotor x`
			`# @class Copter`
			`#`
			`# @maintainer Oleg Kalachev <okalachev@gmail.com>`
			`#`
ROMFS: Exclude uncommon board configs (Clover4) 2020-03-16 13:52:00 +01:00			`# @board px4_fmu-v2 exclude`
			`# @board intel_aerofc-v1 exclude`
			`# @board bitcraze_crazyflie exclude`
			`#`
Add COEX Clover 4 airframe 2019-11-12 02:17:29 +03:00
nsh scripting:source (.) cmd supported 2020-06-22 13:53:01 -07:00			`. /etc/init.d/rc.mc_defaults`
Add COEX Clover 4 airframe 2019-11-12 02:17:29 +03:00
			`set MIXER quad_x`
			`set PWM_OUT 1234`

			`if [ $AUTOCNF = yes ]`
			`then`
			`param set MC_PITCHRATE_P 0.087`
			`param set MC_PITCHRATE_I 0.037`
			`param set MC_PITCHRATE_D 0.0044`
			`param set MC_PITCH_P 8.5`
			`param set MC_ROLLRATE_P 0.087`
			`param set MC_ROLLRATE_I 0.037`
			`param set MC_ROLLRATE_D 0.0044`
			`param set MC_ROLL_P 8.5`
mc_pos_control: migrate MPC__VEL_ parameter to acceleration scaling Before #14212 the velocity control gains used in the multicopter position controller were defined as a scale between velocity error in one axis (or it's integral and derivative respectively) and the unit thrust vector. The problem with this is that the normalization of the unit thrust vector changes per vehicle or even vehicle configuration as 0 and 100% thrust get a different physical response. That's why the gains are now defined as scale between velocity error (integral/derivative) and the output acceleration in m/s². 2020-04-27 15:44:40 +02:00			`param set MPC_XY_VEL_P_ACC 2.2`
			`param set MPC_XY_VEL_D_ACC 0.26`
Add COEX Clover 4 airframe 2019-11-12 02:17:29 +03:00			`param set MPC_XY_P 1.1`
mc_pos_control: migrate MPC__VEL_ parameter to acceleration scaling Before #14212 the velocity control gains used in the multicopter position controller were defined as a scale between velocity error in one axis (or it's integral and derivative respectively) and the unit thrust vector. The problem with this is that the normalization of the unit thrust vector changes per vehicle or even vehicle configuration as 0 and 100% thrust get a different physical response. That's why the gains are now defined as scale between velocity error (integral/derivative) and the output acceleration in m/s². 2020-04-27 15:44:40 +02:00			`param set MPC_Z_VEL_P_ACC 4.8`
Add COEX Clover 4 airframe 2019-11-12 02:17:29 +03:00			`param set MPC_Z_P 1.2`
			`fi`