Scripted MagFit flightpath generation

Probably because you don’t have an RC function assigned as 300 (scripting).

Follow the instructions carefully.

Honestly I dont understand the ardu documentation. Shall I assigned to some RC channel / trasmitter stick value RCx_OPTION,300 and whith movement of that stick I start script processing?

This is not the ArduPilot docu, it’s from the first post in this topic.

1 Like

Yes, I don’t have this RC function assigned. If I don’t want to use switch (I want use GSC) I don’t need “advance-wp.lua” script, I am right?

I am not sure if I understand correctly to all of the step. I understand that I must enable scripting and upload scripts – I done it. I see all “MAGH_” parameters in Full param list. Then I create on Flight Plan Screen flight plan according to your instruction.

After this step I am not sure what to do. You wrote “Upon execution of the mission, several messages will be displayed via telemetry”. By “upon execution” do you mean after the flight plan is written to the copter (= Flight plan is available on Flight Data Screen)?

Then you wrote “Download the mission to confirm obstacle clearance before proceeding, and then use the GCS to set the indicated waypoint to continue (or use the additional helper script below to use an RC switch for advancing the waypoint).” In this step am I execute “Mission_Start => Do action” command? I understand that after takeoff quad is waiting for either GSC command or for switch input to proceed the first “figure-8” waypoint? I am right?

I am sorry for these stupid questions, but this is my first Ardu quad. Thanks for help.

Just fly some figure 8s in alt hold or loiter mode and use the new online tool to analyze the log.

Come back to these advanced features when you are a little more comfortable with the system.

I just wanted to know if I correctly understand your step-by-step, nothing more :wink:

My point is that it isn’t worth agonizing for days over a feature that isn’t likely to help all that much…and I don’t want to see you crash your hard earned new copter by trying something more advanced than you are prepared for.

I explained things pretty explicitly, and your lack of ability to follow those instructions likely means you aren’t quite ready to use these features.

1 Like

A couple figure 8’s with some throttle changes…
Then use the tool available.

If you have an interest in Lua Scripts in general watch Yuri’s YouTube video. There is no compelling reason to use it for this purpose at this point in your tuning process.

My initial reasoning for making this script was to potentially provide consistent, useful results. But it’s become apparent that you really don’t need to go to this length to tune one Copter.

Now, if you had a fleet to calibrate, I think this script might become quite useful to efficiently tune multiples on the same flight path with reduced operator workload.

On the other hand if you had a fleet to calibrate all at the same location, you could run the sript on one drone, then download the generated mission and reuse just the mission to calibrate the rest. That would even enable F4 autopilots to fly the same calibration path (as long as one F7/H7 drone runs the script to generate the mission).

That’s exactly what I was suggesting.

Oh well, thought you meant to use the script on every drone :see_no_evil:

I successfuly execute the script. You are right that step-by-step was easy to follow, I just dont understand arducopter basics.

One last question in the web magfit tool is “coverage indicator”. Coverage indicator shows low values. My question is how important is bigger coverage regarding to calibration results?