Cube Black and MethodicConfigurator (MC), Part 2

While progress in configuration there are some items in parameter files mark with N/A that means not available. But after upload, these parameters are suddenly available!! So I’ve done it by this way the whole process!

I THINK THAT’S A VERY BAD BEHAVIOR. THE SOFTWARE SHOULD NEVER UPLOAD N/A-PARAMETERS TO THE FC

After I finished the configuration process, I try to start Mission Planner and the nightmare begins with error messages in the HUD.

  1. failed to initialize MAVFTP
  2. PreArm: Scripting: out of memory
  3. Starting messages

    grafik

The FC isn’t more operable. Every try failed .

your trying to enable more than your cube black can handle so your getting out of memory errors. the cube black cant do lua anymore.

1 Like

The unavailable parameters become available once their respective *_ENABLE parameter gets set.

It does not upload N/A parameters, not the you you think at least, it’s not a bug. It’s just that you do not understand the ArduPilot firmware yet.