Forcing Mission Planner to load custom parameter definitions?

I’ve generated a set of ParameterMetaData for a custom branch with a whole load of parameters, that I’d like to display in the units/descriptions columns within the Mission Planner full parameter list. I’ve verified that my new parameters are indeed in the ParameterMetaData.xml file, which has been copied to Documents/Mission Planner/, as well as C:\ProgramData\Mission Planner, which are shown as the two data directories in the Mission planner console when it fires up.

These parameters appear in MP like normal, but there’s nothing in any of the info columns, just the name and value.

Is there a method to force MP to load these params locally?

According to your vehicle type, modify the .apm.pdef.xml file in the ProgramData/MissionPlanner folder then make it read only, so MP will not overwrite it with a downloaded one.

Thanks, the read only flag was the bit I was missing!

is this method also available for MAVLink components ?

No, mavlink component ID descriptions and other mavlink constants are compiled in.