Trouble binding

[RcHawks]

I went thru the procedure to bind the neo wirth the N3 and MC3 and finally got it. But when trying to do the same procedure for my Avata 2 with N3 and MC3 I would receive and error that my software is an earlier version and failed. I haven't used my phone to fly with my MA2 in years, I use my mini 5 ipad for that. I'm thinking about trying to update it with my ipad. Anyone else had this issue? I'm not sure why it would work with the neo but not the Avata 2 with the same software in place.
Nope didn't work.

 

[NeoNeo]

From what I understand there are only two ways to update the firmware of the Avata2. The computer based DJI Assistant and phone app DJI Fly. Only have experience using the DJI Fly app. The DJI Assistant is not from an "approved" Apple developer and requires you to go around GateKeeper and ??. Simple process if you have done it before. DJI Fly app is available at the Apple App store. Assuming the same for non-Apple phones.


First you need to make sure you have the latest app firmware downloaded. Then you need to make sure your Avata2, MC3, N3 have the latest firmware. At least with the iPhone DJI Fly App it tells you if there are updates. The Goggles3 needs a hardwire connection to your smartphone. Unsure of the N3. Make sure all your other hardware is powered on. Goggles transmits wirelessly any updates to the quad, controllers. Simple process just following the prompts. Might be a DJI FLY iPad app available allowing you to use your iPad. If not you will need to either download the DJI Assistant to your computer or DJI FLY app to your smartphone.

 

[RcHawks]

Just purchased a new phone and got it setup today. I'm going to download a fresh copy of DJI Fly app and give it another go. Thank you for the tip.

 

[RcHawks]

Got it! I'll install the drivers for the Avata 2 tomorrow. It refuse to installl on the fly app.

 

[RcHawks]

I'm still unable to bind. my Avata 2. I keep getting a message that i'm using a earlier version of the fly app and it will not recognize the avata 2. I did move my app from a old phone to a new phone. Is that my problem. Should I delete my DJI fly app and redownload on my new phone for update? Will this make any difference or cause more issues?

 

[NeoNeo]

Using an older iPhone SE with iOS 18.1.1. IIRC, the last time I updated the DJI Fly App I just went to the apple app store and clicked update.

Just incase missed. Did you activate the Avata2 using the DJI Fly App account page? Should be listed. Open app. Sign in. Click Profile icon. On Profile page click Device Management. Should list your Neo and Avata2. If not, you have not properly activated the Avata2. If activated. Return to home page. Click Connection Guide for instructions. Go back to home page and Click if present the "new firmware available" download box before following the Connection Guide instructions.

One issue that might be missed is. Make sure your Goggles are powered on first before powering up the controller as noted in the Guide. Might make a difference.

 

[RcHawks]

Thank you for your response, I'll try again.

 

[RcHawks]

Not working. I had to sign in to the account though, didn't expect that.
When I click Check for Firmware Update it says connect to device to update. . I went thru the binding procedure and it just keeps running a loop of connecting to aircraft (with avata 2 switch on) and then powering off then back on again by itself and states connecting to aircraft failed and it does this over and over.
Link Failed try to link the goggles to Aircraft or See Menu.
The Avata 2 was listed after your suggestion and I did click on it but it didn't seem to help. I'm considering connecting the N3 Goggles to Assistant 2 to see if there's a update that way.

 

[Kilrah]

When you use Assistant you have to connect the device you want to update to the computer directly, no "going through another" like with the app.

Post screenshots/photos of your setup and what you're doing.

 

[RcHawks]

Considering since it's not activated to just send back for a refund for the drone and refresh, although connecting to the assistant 2 will probably work for this problem.
I did finally get to fly the neo with the n3 and mc3. I was terrible at controlling it. Using the MC3 was very different from using a controller with sticks and I felt very awkward trying to control it. I'm sure I would do much better with the standard controller.

 

[NEO 317]

I did finally get to fly the neo with the n3 and mc3. I was terrible at controlling it. Using the MC3 was very different from using a controller with sticks and I felt very awkward trying to control it. I'm sure I would do much better with the standard controller.

I still haven't made it through the tutorials and find the mc3 with goggles awkward.


I gave up trying and flew with the standard remote which was very satisfying.

I haven't totally given up on the goggles and MC yet, but I prefer the ease of setup with the standard remote, device, and the NEO.

Plus, you don't need a V.O.

.

 

[RcHawks]

I think I've discovered what I did wrong and it's embarrassing but if it helps anyone else so be it. I haven't followed thru on it because I still have the option to return as it's not activated. My wife keeps telling me to keep it. I'm undecided at this point. When I scanned to inside lid of the box the first time the app didn't do anything and I thought I was good. Not so, apparently because of the frustration of not getting it to work I tried scanning it again and the activation agreement came up. Duh that's got to be it.
Trying to weigh to pros and cons of keeping it.
I think if I do I'll add a m3 controller.

 

[NeoNeo]

Good to hear you were able to activate the quad. R/C can sometimes be a frustrating hobby. Usually it is one overlooked or clicking the incorrect choice that makes life beyond interesting.

When I first flew the Avata2 with the MC3 the initial impression was not very positive. Totally different way of flying. Lacked agility, responsiveness. Having a pre-use bias against (lame, for those who need a crutch to fly....blah...) didn't help. Took a few flights to get a feel. Sort of like it for flying slow than slow in real tight settings. Still trying to improve skill level when trying to coordinate smooth transitions from using motion and trigger to joy stick. Need the joystick sometimes to pop up or down through real tight openings. Or sometimes just to slide a few cm port or starboard to squeeze through an opening.

Plan this winter indoors season on well light days is to use the Neo and MC3 to practice those transitional moves on a set "track".

 

[Droning on and on...]

I post the following video for demonstration purposes only; I do not have a monetized YT channel, watching my videos gains me nothing other than a little pride. I feel I must include this disclaimer because I have had a video removed before on this site being admonished not to use the forum to "promote my channel".

The following (long) video was flown entirely with the MC3, in Sport mode on the Neo, full-throttle most of the time.

@NeoNeo, once you get a more reflexive feel for the MC and are less skittish, you'll find it a blast.

 

[RcHawks]

Good video. I see what you mean. It looks similar to flying a plane. I've been missing that feeling lately and this type of flying should fit the bill. I was debating on whether to spend another 200 dollars on a rc 3 or to simply develop the skills to do this kind of flying with the MC3. I think I'll stick with the MC3 as I have plenty of other drones and controllers.

 

[NeoNeo]

MC3 is not skittish IMHO. The opposite. Sluggish. Or for some "smooth". It feels like the tuning is biased to reduce newbies from over reacting when compensating for a less than ideal maneuver. Good move by DJI for introducing people to FPV. Bit of a traditionalist and find that even after +10 hours of flying with the MC3. Sticks are "better". Plus the MC3 limits you to only stabilized N or S mode. Great for video recording and gentle flying. Definitely great for preventing crashes. Did crash couple times over the first couple hours of flying the Avata2. Finally got use to the "sluggish" and limited angle of attack. Zero crashes after that. Then I went manual mode with the FPV RC3. Don't remember a session where I haven't had to either bailout of M mode or end up crashing. Good thing the Neo is a tough little quad. Avata2 would be in the trash bin. Only fly that quad in M mode with significant altitude to allow time for recovery. Plus nothing to run into at altitude.

Regarding the FPV RC3. JMHO, it is a bit pricey for what you get relative to the rest of the FPV Tx market. But the only option for Manual mode flying 04 gen quads. Outside of gimbal sticks. No other parts from DJI are available for repair. Sort of a throw a way controller. Checked eBay for replacement parts. One seller had used gimbals at $59 each. Crazy price, but I guess that's the state of the current market. Don't drop your RC3. Store with gimbal stick guards or remove the sticks before storage. Don't cross thread the inserting gimbal sticks.

 

[NEO 317]

.... Sticks are "better".

Agreed.

.

 

[RcHawks]

Now I've got to find a cheap RC 3 controller, lol. Yeah I was afraid of that, the MC3 - RC3, and which I'd like better. No customer service parts huh? Good to know. I've always used Sticks, just what I'm used to, but I think I'll like the MC3 given the chance, just not as much and that's alright.

 

[RcHawks]

I'm buying a RC 3 to go with the neo and Avata 2 as well while I can. It says I will receive it by Christmas Eve. I have a N3 goggles case that's supposed to arrive the same day. I guess I'll ask my wife to wrap it for my Christmas presents the next day, ( I'll probably act like a kid and open on Christmas eve before midnight when she's not looking)

 

[RcHawks]

I found the solution to the problem. I downloaded Assistant 2 and plugged into the port on the side of the drone. It automatically called up Avata 2 and after 2 or 3 simple steps it was activated and done. Now to see if pairs ok.
I had some more trouble but kept at it and was just about to give up and send it back, really I was about done with it, but I reconnected the drone to the software it picked it up again an I did the update again and voila no more aircraft vesion too early error. After that when pairing the drone and N3 goggles it simply connected with a camera view and the whole thing was complete. Finally.
Assistant 2