I decided to try some cheaper controller than my pixhawk 6c, I bought a speedybee f405 v3. When I decided to transfer my scripts to a new controller, I encountered the problem that there is no “SCR_ENABLE” parameter in the parameter tree. I know that it’s a memory issue, but is there a way to around this limitation? If it’s not, please explain why. (I plugged in a 64gb SD card).
F4-series autopilots lack the hardware resources for scripting.
This makes no difference.
It’s about the integrated flash memory, not the SD card capacity. You can build a custom firmware with other unused features disabled and scripting enabled, but it’s still an F4 CPU and I have my doubts that it can handle it.
Get an H7 FC instead. They start at 60€ (40 if you’re lucky and order from China).
That can sometimes work (rather poorly) on the F7-based boards. F405-based boards will almost certainly fail at scripting, even with a custom build.
I was able to use your “MinFixType” LUA script on my Pixhawk 2.4.8 while running Ardupilot 4.2.3
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.
Just enough.
And that was for a rather non-complicated script.
MavFTP stopped working as a consequence of my settings.
So, possible, but of limited utility.
I don’t think scripting of any sort will be possible on 4.5 with the limitations of the old Pixhawk.
I may finally have to upgrade.
In very crappy, nerdy, slightly anachronistic analogies:
When that autopilot was released, installing ArduPilot on it was already a bit like installing Windows 7 on a machine built for XP (the F4 series was already half a decade old). Now you’re essentially trying to run Windows 11 on that old Pentium desktop.
2 Likes