I already did all sensor calibrations.
what other configurations you mean ?
The mission planner is saying “Bad battery” since it is sensing 4 cells even if I have 2 cells
I changed this configuration but doesn’t reflect in the FC.
The configurator has 25 steps. You have completed 5.
ofcourse I did all mandatory hardware configuration (Frame type, Accel, compass, Radio,ESC, flight modes)
what else is missing ?
You only did up-to section 1.6, the rest is missing.
I copyed the instructions here:
1. Quick overview of the entire process
To methodically build, configure and tune ArduPilot vehicles follow this sequence of steps:
1.1 Select the vehicle components
- while choosing an Autopilot and other hardware components avoid these components
- Use ecalc for multirotor to select the propulsion system.
1.2 Install Software
1.3 Input vehicle components and component connections into ArduPilot Methodic Configurator
The software needs this information to automatically pre-select configuration settings relevant to your specific vehicle
- Start the ArduPilot Methodic Configurator and input select a vehicle that resembles yours and input vehicle components and component connections information into the ArduPilot Methodic Configurator component editor window
1.4 Perform IMU temperature calibration before assembling the autopilot into the vehicle (optional)
IMU temperature calibration reduces the probability of Accel inconsistent and Gyro inconsistent errors and reduces the time required to arm the vehicle. IMU temperature calibration requires lowering the temperature of the autopilot (flight controller) to circa -20°C. That is harder to do once the autopilot is assembled inside the vehicle, hence it is done now.
1.5 Assemble all components except the propellers
Assemble and connect all components. Make sure you follow best practices
1.6 Basic mandatory configuration
Again using the ArduPilot Methodic configurator software GUI perform the following steps:
- 04_board_orientation.param flight controller orientation
- 05_remote_controller.param remote controller connections and protocol
- 06_telemetry.param telemetry transceiver connections and protocol (optional)
- 07_esc.param Electronic-Speed-Controller connections and protocol
- 08_batt1.param Battery health and state of charge monitoring
- 10_gnss.param GNSS receiver connection and protocol
- 11_initial_atc.param initial attitude PID gains (vehicle size dependent)
Now use Mission Planner to do:
- 12_mp_setup_mandatory_hardware.param calibrate vehicle sensors
And continue with the ArduPilot Methodic configurator software GUI:
- 13_general_configuration.param general misc configuration
- Test if the hardware diagnostics are OK
- 14_logging.param configure Dataflash/SDCard logging (black box data)
- 15_motor.param motor order and direction tests. ESC linearization.
- 16_pid_adjustment.parm attitude PID gains (vehicle size dependent)
- 17_remote_id.param required by law in many countries
- 18_notch_filter_setup.param to remove motor noise, reduce power consumption and increase flight stability
1.7 Assemble propellers and perform the first flight
Now that all mandatory configuration steps are done you can perform the first flight
1.8 Minimalistic mandatory tuning
These are the very minimum tuning steps required for a stable flight:
- Load the
.binlog file from the first flight into Notch filter webtool - 19_notch_filter_results.param use the webtool information to configure the notch filter(s)
- 20_throttle_controller.param the altitude controller depends on the power-to-thrust ratio found in the first flight
- 21_ekf_config.param sometimes the EKF3 needs a tune to maintain altitude
- 22_quick_tune_setup.param and 23_quick_tune_results.param You need lua scripting support to do this if not available you can tune manually.
That is it, if you are impatient and do not want an optimized vehicle you can skip to everyday use.
1.9 Standard tuning (optional)
These are the standard tuning steps required for an optimized flight:
- 24_inflight_magnetometer_fit_setup.param Use lua scripted flight path or fly manually and 25_inflight_magnetometer_fit_results.param Use the magfit webtool to calculate a file that the ardupilot methodic configurator can use
- 26_quick_tune_setup.param and 27_quick_tune_results.param Redo quick-tune now that the compass magnetic interference is fully calibrated
- 28_evaluate_the_aircraft_tune_ff_disable.param and 29_evaluate_the_aircraft_tune_ff_enable.param
- 30_autotune_roll_setup.param and 31_autotune_roll_results.param tune roll axis rate and angle PIDs
- 32_autotune_pitch_setup.param and 33_autotune_pitch_results.param tune pitch axis rate and angle PIDs
- 34_autotune_yaw_setup.param and 35_autotune_yaw_results.param tune yaw axis rate and angle PIDs
- 36_autotune_yawd_setup.param and 37_autotune_yawd_results.param tune yawd axis rate and angle PIDs
- 38_autotune_roll_pitch_retune_setup.param and 39_autotune_roll_pitch_retune_results.param re-tune roll and pitch pitch axis rate and angle PIDs
Now the standard tuning is complete you can skip to everyday use
Sections 1.7, 1.8 and 1.9
I see you are not following any of the advice being given.
1 Like
i am stuck in step 1.7 no value to check 1.8 and 1.9 → my quad doesn’t even fly!
can you please confirm based on the video I uploaded if the motors rotate in correct direction and the order is also correct?
You’re still stuck at 1.6 - item 15.
Read this:
https://ardupilot.org/copter/docs/connect-escs-and-motors.html#testing-motor-spin-directions
So than your configuration is still not correct. Don’t ignore any step if it is not working as you expected.
Show your actual PARAMs
Videos show nothing as nobody can see what you are doing on Mission Planner or your Transmitter.
2 Likes
Thx for the answer.
The last video, I run on mission planner a test of motors in sequence. there was no RC transmitter used.
I will upload full parameter list when I go back home.
We need the parameter files created by the ArduPilot Methodic Configurator
Those files include all the necessary information to do informed decision when supporting you.
And you should add a vehicle.jpg file to it 
Honestly, please remove the propellers or at least loosen the nuts by 2 turns until you confirmed the correct rotation of each motor. It is highly dangerous to do this indoors with a copter.
2 Likes
If you have not done so already you may want to check the ESC Calibration. It looks like the motors were at quite different speeds during the motor test.
@mr_byte31 the more steps you skip or perform incorrectly, the faster the drone will crash.
2 Likes
I always do ESC calibration before flight.
I follow this video steps.
Here is a user that did it correctly and got it working
2 Likes
I reflashed my firmware and I also did all calibrations → I start from scratch to avoid any wrong parameters that I may configured.
this is my full parameter list.
full_parameters.param (17.5 KB)
I need to spend time on how to get ArduPilot Methodic Configurator to work for me.
I installed the tool and I am stuck with the template for my FC.
I can’t find any template that uses Pixhawk 2.4.8.
is there any template that I can use?
here is a picture of the configuration that the tool collected when it started running
Think a second about this… ArduPilot supports over 100 different FC boards. Do you think we need 100 different templates? Those 100 different templates can use different ESCs. And different telemetry modules and different rc protocols … etc. The number of combinations explode.
But we are in luck, you can pick any template. Just pick the one closest to your vehicle.
I understand your point.
The RC receiver is connected via SBUS with FC and the template is asking about the SERIAL port number and I have no clue for such things.
I am googling now for answers.