First flight prep with AMC on a JIS EV410

ArduCopter Copter 4.6
1

Hello everyone,

I am preparing for the first maiden hover test on a new custom build. I have meticulously gone through the ArduPilot Methodic Configurator (AMC) software to ensure all vehicle component selections, mandatory calibrations, and baseline parameters match my hardware exactly.

Build Specs (Stripped Down for Initial Hover/Tune):

  • Frame: JIS EV410 Quadcopter

  • PDB: Dumb PDB (standard copper board, no current measuring capability at the moment)

  • Flight Controller: Cube Orange

  • Power Plant: Hobbywing X8 Motor System (ESC + Motor + Props Combo)

  • Telemetry: 100 mW SiK Radio

  • Firmware: ArduCopter 4.5.x

The AMC software has generated my final pre-flight parameter files cleanly. Before I put the propellers on and take it out for the first hover test, I want to proactively ensure I haven’t missed any edge cases or specific safety checks unique to this frame layout using AMC parameters.

I am tracking my build closely. What specific telemetry feedback or behavior should I look out for during the first 10-second off-the-ground hover to confirm the AMC baseline is solid before proceeding to minimalistic tuning?

Thanks

Ag_Drone_June_27_2026.zip (233.0 KB)

2

Thanks for taking the time to configure it correctly and prevent issues, instead of crashing the vehicle and asking us for help after the damage is done.

It’s all described in Section 7 of the AMC tunning guide

3

You are using an outdated version of AMC. Please update to AMC 4.3.0

Why are you using MavLink1 protocol on the telemetry link instead of Mavlink2 ?

You are not supposed to upload the file 24_throttle_controller.param until after the first flight, but you did it already.

I’m guessing you did not do the IMU temperature calibration correctly, because there are no .png files in the .zip file

You posted that you are using ArduPilot 4.5 but the file reports you are using ArduCopter 4.6.3 beta.

No, you did not add powerplant and telemetry information in the AMC. Why are you not using ESC telemetry?

4

Hello Amilcar,

First of all, thank you so much for your amazing software, your incredible support, and for such a prompt answer! I am quite new to this, and your expert guidance is invaluable to me.

I am actually leaving for a trip to Mexico in a few days, so I will not be doing any flights yet. When I return, I plan to completely update to AMC 4.3.0 and run through the steps fresh to clean these items up.

To answer your questions as best as I can right now:

  • MAVLink 1: To be honest, I am not sure why it is set to MAVLink 1. I likely missed a setting or it was a default, but I will absolutely change the telemetry link to MAVLink 2 when I do the fresh run.
  • ATC_ANG_YAW_P: I honestly do not remember changing this to 1.5. I will make sure it is reverted or correctly calculated by AMC on the next pass.
  • The throttle file / IMU temperature calibration: You are entirely correct (my bad!). I actually didn’t discover the Methodic Configurator until after the drone was fully assembled, so I missed the temperature calibration. I will ensure the IMU temp calibration is done correctly next time, and I will wait on the throttle controller parameter until after the maiden flight.

Thank you again for looking at my files and catching these edge cases before I ever put props on. I look forward to updating everything when I get back!