Inspire 2 Slave Remote Disconnected After I2 Firmware Upgrade

[InterMurph]

My main remote is a Cendence with CrystalSky. I had a hard time upgrading the I2 aircraft firmware with this combination, and ended up having to use the DJI Assistant 2 app:

How do I update my Inspire 2 aircraft/camera firmware with my Cendence/Crystalsky remote?

The craft is now upgraded, and the Cendence remote is connected fine. But now my slave/camera remote, which is a standard I2 remote, is not connected:



Further, when I Enter Device anyway and navigate to the RC settings, where I would expect to be given the choice of Master/Slave, I see no choice:



And when I back out to the opening screen, long-press the three-line menu, and try to update the RC's firmware, I am not given the option:



Any idea of how I can revive this remote?

Thanks.

 

[InterMurph]

Well, that's weird.

The batteries on my I2 were running down, so I powered off, replaced them, and powered on. And now everything is working.

Even though I had power-cycled my craft several times trying to get this to work.

DJI's continued software-reliability issues, after all these years, do not inspire confidence.

 

[Advexure]

Glad things are working. Wanted to chime in on your below statement as we see this every so often on the CS as well.

Further, when I Enter Device anyway and navigate to the RC settings, where I would expect to be given the choice of Master/Slave, I see no choice:
View attachment 19620

We've found that this settings option for master/slave does not show when the CrystalSky is not recognizing the RC it's plugged into or doesn't have the USB accessory authorization in Android (message that comes up asking you if you want to allow an app, either GO, GO4 or Pilot, to use the USB accessory "just once" or "always"). With the RC powered on, re-seat the CrystalSky on its bracket and navigate back into that menu, or even re-seat it while in the RC settings menu. The option to set master/slave will disappear when it doesn't have communication with the RC. Very common occurrence we run into when setting up M200s with slave and master Cendences and every so often on the Inspire 2.

 

[InterMurph]

My primary remote is a Cendence/CrystalSky combo. I had no problems with that.

My second/camera remote is a standard I2/iPad combo. That's the one that wouldn't connect.

 

[Advexure]

Gotcha, usually the stock RC/iPad route is pretty smooth.

In other news for CrystalSky, DJI just released a new CS firmware yesterday (See Release Notes Here) and it mentions "Fixed an issue where the remote control became disconnected when switching between built-in apps."

 

[InterMurph]

Coincidentally, I got myself into this same situation again.

This time, restarting the aircraft had no effect. It was an attempt to restart the unlinked camera RC that did it. I tried the patented DJI press-release-press-hold, and instead of powering off, it linked. The RC status light, which had previously been dark, came on, and it worked.

I marvel at how difficult it is to get a DJI drone flying, and then how easy it is to fly once you figure out all of the button-presses needed.