Weird Remote ID issue

[kenjancef]

I just had a weird Remote ID issue with my Air 2s. I 've been using the $300 DJI RC as the controller for about a year and a half. I've been having minor signal issues since I've been using the RC, but still kept using it, as the issues weren't too bad. But here are the steps I did to lead up to the Remote ID error...

Saturday 9/28:
Morning: I flew in the morning with someone. I wasn't too far away, but I was getting a lot of video feed freezing issues. I was talking to my friend about it, and I decided to swap back to the RC-N1 that came with the Air 2S.

Afternoon: Swapped out the DJI RC with the RC-N1. I unbound the RC, and bound the N1, all was good.

Evening: Flew with another friend, using the RC-N1. Went through 2 packs with no issues.

Wednesday 10/2:
Took everything out to try to get a sunset. I fired everything up, and then I saw the red box saying "Remote ID Error". I couldn't take off of course. But I've never had a Remote ID issue ever, and I've had this 2S for almost 2 years. So I unbound the RC-N1 and re-bound (if that's a word...) the DJI RC, and everything worked.

Why would the RC-N1 work once on Saturday for 2 packs, then I get an error yesterday, then switching back to the RC the error goes away? As I said, I never had ANY issues with my 2S, nevermind Remote ID errors.

Sorry this is so long, but I wanted to get as much info in as I could...

 

[mavic3usa]

Perhaps it has something to do with the "unbound" process, not exactly sure what that is?

 

[kenjancef]

Perhaps it has something to do with the "unbound" process, not exactly sure what that is?

To use another controller, you have to remove, or unbind, the old one before binding the new one.

 

[Capt KO]

Did you use the DJI RC for the A2s RID firmware update? Might need to update the RC-N1. Maybe it took a couple uses to get the error message.

 

[Explorer1]

Did you check the the battery charge of the N1 ?

 

[MS Coast]

I fired everything up, and then I saw the red box saying "Remote ID Error". I couldn't take off of course.

I frequently see "RID Error" messages in a red box during startup, but they close as the drone and controller come on line.

Are you seeing an error message that persists until startup is completed? Are you prevented from starting the motors or are you choosing not to fly because of the error message?

 

[kenjancef]

Did you use the DJI RC for the A2s RID firmware update? Might need to update the RC-N1. Maybe it took a couple uses to get the error message.

You know what, I'm not sure... I've been using the RC for about a year and a half. Didn't the RID update come out before that?

 

[kenjancef]

Did you check the the battery charge of the N1 ?

Yea. I made sure I charged it up first before I made the swap.

 

[kenjancef]

I frequently see "RID Error" messages in a red box during startup, but they close as the drone and controller come on line.

Are you seeing an error message that persists until startup is completed? Are you prevented from starting the motors or are you choosing not to fly because of the error message?

I got the error a few seconds after the controller finds the drone. I did wait until the drone got all it's satellite locks and stuff, but the error didn't go away. Maybe I still didn't wait long enough? It's just weird because I've had this Air 2S for just about 2 years and never had any issues/error at all since I've had it.

 

[MS Coast]

I got the error a few seconds after the controller finds the drone. I did wait until the drone got all it's satellite locks and stuff, but the error didn't go away. Maybe I still didn't wait long enough? It's just weird because I've had this Air 2S for just about 2 years and never had any issues/error at all since I've had it.

Did the satellite icon color change to white to indicate a gps lock? Did you hear the message about the home point being set? If not, you might not have waited long enough.

It does sound a bit unusual. I see the RID error message closing soon after strart-up and long before the gps lock happens.

 

[kenjancef]

Did the satellite icon color change to white to indicate a gps lock? Did you hear the message about the home point being set? If not, you might not have waited long enough.

It does sound a bit unusual. I see the RID error message closing soon after start-up and long before the gps lock happens.

Funny, I don't even remember... maybe I was just so concerned about the error that I didn't wait. The weather is crap today, so maybe tomorrow I'll try it again.

 

[MS Coast]

Funny, I don't even remember... maybe I was just so concerned about the error that I didn't wait. The weather is crap today, so maybe tomorrow I'll try it again.

Have a look and see. No need to fly; you can start it up in any weather.

 

[lukedow54]

Ive had this issue numerous times over the past few months with my DJI Mavic 3 (that I bought a few years ago). All firmware and everything else is up to date, I go to fly and I get that error code, even after the satelites are locked on and the number/symbol becomes white. I usually have to shut down everything and restart it again and then after doing that once or twice the error goes away.
Unfortunately this awesome sunrise, that I was scrambling to capture, didnt want to wait for this annoying problem to pass.

Any idea what the issue might be?

 

[Fader McG]

Chiming in to share that I've been experiencing the same with my 2nd-hand Air 2S. Everything had been functioning well for the last five months that I've owned it, but starting last month I began experiencing the Remote ID error at random times with the standard RC-N1 controller, even in near-ideal conditions. The only way I've been able to correct it consistently is to reboot the drone, and I'm still not sure if removing the battery entirely or shutting down and restarting the Fly app has any effect as I've tried different a different order and nothing is consistent.