Remote ID error on Goggles 2 & Mini 4 Pro w Plus Battery

I am getting seemingly random remote ID errors when using the Goggles 2, motion controller 2 and the Mini 4 Pro and Plus battery… It stops me from even starting the motors, despite having GPS lock and
Anyone else getting this? I can clear it by re-pairing it to the RC2, then pairing it back to the Motion Controller 2 and Goggles 2 whilst the Mini 4 Pro remains on with a GPS lock. Only then can I use the Plus battery.
This seems a crazy routine, although in fairness the Plus battery is not officially supported in the UK, but once the drone has full GPS and it knows it’s not in the USA, it should remove the Remote ID error without having to tether your Goggles to your phone and Fly App.
Anyone else getting this?
Ian

1 Like

I don’t suppose many have the Goggles2, motion and the plus battery :thinking:

but I suspect this is an error with the RID setup and can happen with the Avata as well

because there is no GPS in the goggles it doesn’t know where the operator is and throws the error stopping the takeoff

This is why many in the USA are now using the Goggles integra as they have built-in GPS and they don’t have to connect their phone whilst flying

Try connecting your phone with the fly app open

1 Like

@ianinlondon if Wayne’s solution works and you do a quick video don’t forget where you got the solution :wink:

1 Like

Yeah, I’m painfully aware of the cause and solution, but I am struggling to work out why it’s random.
Once I pair it to the Goggles 2 & MC2, outside with GPS lock and the Plus battery, I don’t get the RID error. But a day or two later, if it’s not used, I turn everything on and the error is back.
It’s like the initial pairing outside tells it that it’s not in the USA, then after a day or two, it forgets, and throws the error up again. I’ve had people complain about the error even using a standard battery as well, which really confuses me…

LOL… I already had the solution and already filmed that part :rofl: :rofl: But you know I never miss a chance to mention this forum :wink:

1 Like

This is why RID is a pile of :poop:

I’ve had similar issues and I suspect it to be down to the bugs in the firmware and the way it uses the geo-location at the startup

What have DJI said?

They’re still working on my flight logs… They say it should only happen in the USA so they’re not sure why this is happening.