Mission Planner has an interpreter built in. There’s no need to have a Python (or IronPython) environment specifically installed separately on the machine.
Run scripts from here:
Recommend also updating to latest beta Mission Planner from the Help page by clicking the “Check for BETA Updates” button here (also do this somewhat frequently):
Beta updates often contain bug fixes and minor updates for recent firmware compatibility. Official releases tend to lag that timeline significantly.
I’m barely qualified to answer MP script questions, even if I wrote it…
They have fallen out of vogue since Lua scripting has largely supplanted the need, and pymavlink works pretty well for custom ground-based Python development.
Full disclosure, I haven’t used the Hall effect tuner in quite some time. It was an afternoon diversion that became a bit entertaining and slightly useful. It could still be quite useful for you, but don’t waste too much time on the Python stuff before just driving around and eyeballing things as best you can with a little help from the data provided by the onboard sensors that you have through the ESP32.
My mower doesn’t even use direct SERVO1 and SERVO3 output anymore. I have a Lua script that resides in-between what amounts to synthetic autopilot throttle commands and actual servo output, manipulating the values based on scaling, offsets, and backlash compensation to get very close to linear output at my desired engine throttle setting. However, that’s VERY experimental and honestly quite painful to configure. It’s not worth the time at this moment to enable (nor do I have time to explain it anytime soon…it really is that bad…).
Instead, don’t agonize too much over straight line tracking. The Hall effect setup will get you close, even if you’re manually manipulating the RC controls to get the required data.