QuikTune on a Pixhawk 2.4.8?

Can anyone tell me if running QuikTune on a 2.4.8 is a bad idea or not? I have enabled scripting using custom firmware

Thanks!

A response to a previous post which probbaly applies to any F4 based FC:
There was exactly one LUA script memory setting that worked - that was enough memory to run the script, but small enough that the FC had adequate ram for it.

I monkeyed around with a Lua script on a Pixracer (F4) and gave up and replaced the Flight Controller.

Okay… My firmware is about 1.2 MB. Does that mean I get to use the rest for scripting?

I found that other thread, and I guess its a bad idea

Seeing that the blanket statement in the Arducopter Lua Scripts Wiki page says “Scripting is not available in F4 based autopilots”…

I did see that but since I am using a custom firmware and I’m not doing anything else other than quiktune, I thought there was a chance. How can I check available memory (ram) though? The website says 80kb minimum requirement. My chip has a total of 256KB ram

SCR_HEAP_SIZE default value indicates memory available for scripting. It probably says 44k. Cubes are 204k

My experience with that flight controller is it’s not a good idea.

Just use autotune, why would you not?

3 Likes

Yeah right. It says not enough memory

Was planning to get atleast an initial tune done indoors

quick tune needs some amount of turbulence. Doing it indoors is a bad idea.

Autotune on the other hand strives indoors.

1 Like

I see. This was supposed to be an indoor drone, that’s why. I also thought autotune needs gps lock

Not if you run it from Alt Hold. But perform it outside anyway.

2 Likes

Just for your information, I was able to load Quiktune by using a custom firmware with a .apj of 1.05 MB, disabling terrain and bumping up the scripting memory to 60000. The FC still had 4000+ free memory.

Of course, I didn’t perform any test flights and probably never will because my TX doesn’t have a three position switch. I might do it for fun a long time later after I set up telemetry and will post the results here if I ever get to do it

Hello guys, reporting back to say that QuikTune did run. I tried it out of curiosity and it seems to be working. I did this indoors with no GPS.

I used a knob instead of a three position switch

1 Like

Well I am struggling with the same. Out of memory issue using the available stable versions for firmware. How to make a custom firmware?

I am using Pixhawk 2.4.8. I am using camera, compass , osd and some gimbles. I get very less memory free.

How did you do it ? Thanks

You can only do it by removing support for all that is not flight-relevant like camera, gimbal and osd.

Once that is done and the quick tune flight is finished, store the results using AMC and use a FW that has no quicktune but has osd and camera.

Then you’ll have both the quicktune parameters and the features you need to operate.

1 Like

Thanks. I will do it.

There is a qwiktune for VTOL plane included on Arduplane 4.6 FW. Is there any plan to do it for arducopter as well?

ArduCopter already has quicktune for a couple of years now. You really, really need to start using AMC and reading the documentation that it recommends you to.
It will clear all this misconceptions you have.

According to my limited knowledge the quick_tune on copter uses lua script that causes memory issue on F4 processors. However, according to a video for Arduplane 4.6 onwards the FW has built-in quick tune function and hence it does not require to run a lua script and can work perfectly on F4 processors.

I use Arducopter 4.6.3 stable version, in the full parameter list, I cannot find any parameter related to quick tune .