APM 2.5 startup/connection with disconnected compass

So after upgrading to the latest firmware/software it seems to be a new requirement that the compass is connected in order to boot it up and connect to it from mission planner. Whilst this is fine for out in the field, it’s a real pita when your compass is mounted out on a wing and you want to power up the APM at home to retrieve log files or whatever.

Can I ask what prompted this change and if there is any way around it or a chance that it might be rolled back or become configurable?

Chris

So I pulled the latest source and a quick scan of ‘system.cpp’ looks like it should startup with no compass attached…

void Plane::init_ardupilot()
{
...
    if (g.compass_enabled==true) {
        if (!compass.init() || !compass.read()) {
            cliSerial->println_P(PSTR("Compass initialisation failed!"));
            g.compass_enabled = false;
        } else {
            ahrs.set_compass(&compass);
        }
    }
...

So before I raise this as an issue on github, is this a bug or something else?

Chris