I just noticed a weird behaviour with my new Neo. I've successfully connected it to the RC2 of my Mini 4 and to my Avata 2's Goggles3 with the MC3 and the FPV2. I've just flown indoors so far and with RC2 and FPV2 everything is fine and controllable, but with the MC3 sometimes the NEO all of a sudden starts to accelerate during normal flying and can't be stopped until it crashes f.e. in a wall. It always seems to happen after I've just got the message  "Vorsichtig fliegen (keine Satelliten-/---". Anybody else can confirm that?
To be sure, that this is a problem of the NEO, I've just flown the same area with the Avata2 and the MC3 and didn't have any problems at all.


Other than that, I really like the NEO, but what I'm missing is a 'turtle-mode' and a change to fly lower than 0.4cm. Always when trying to go lower (f.e. when trying to fly underneath a chair), the NEO wants to land :-(

Hi there, thank you for reaching out and we are sorry to hear about what happened with the drone. In a situation like this, the best course of action would be to submit an online repair request here:  DJI REPAIR

If you need assistance with creating a ticket, you may contact DJI support at https://www.dji.com/support.

Oh, sorry - maybe just a misunderstanding: I don't need to open a repair request, because despite the NEO accelererating and flying (crashing) 3 times straight into a wall whilst using the MC3 indoors, no obvious damage at the NEO! It seems to be a tough little thing, so far!
Beside the message regarding the satellites, there is another thing to remeber - the 'N'-symbol for normal mode was covered in red - maybe that can help you to fix this issue.
Or is to open a 'repair request' neccessary, so that I then can send you f.e. a video stream from the crash and log data?

I've noticed the same issue.  I have the Avata2 and just got the Neo as a mess about drone.  Using the RC3 seems fine so far but with the MC3 it randomly accelerates into the nearest wall etc.   I've only seen this indoors but it has been raining a lot so haven't yet flown it outside.

Observation.  Drone took off with N in WHITE.  Number of sats was between 0-5 fluctuating.  During flight indoors the N went RED and sat went to Zero.  At the exact moment the N went Red the drone  accelerated full speed forward until crashing.

Hopefully its a simple bug to iron out

Kinda makes turtle mode more useful if its going to just keep crashing all by itself ;-)

ralf-djiforum Posted at 9-11 02:23
Oh, sorry - maybe just a misunderstanding: I don't need to open a repair request, because despite the NEO accelererating and flying (crashing) 3 times straight into a wall whilst using the MC3 indoors, no obvious damage at the NEO! It seems to be a tough little thing, so far!
Beside the message regarding the satellites, there is another thing to remeber - the 'N'-symbol for normal mode was covered in red - maybe that can help you to fix this issue.
Or is to open a 'repair request' neccessary, so that I then can send you f.e. a video stream from the crash and log data?

Thank You for keeping us posted. Could you try fly outdoor or in another location and confirm if issue still persist? If issue still persist and you need an analysis for this issue, kindly sent us flight log for us to check this with the relevant department. We are looking forward to your response for further assistance. Thank You

@numpty99: completely the same! TX, that you posted here!
@Gamorra: Due to the bad weather here, outdoor flying at the moment is not possible. But I really would like to have this issue analyzed, because even if I could try to confirm this issue by flying outdoors - who does know where the NEO would fly to or into? I was not able to stop it indoors until it crashed.... So, how can I get the log and where do you want me to send it to? I had 3 of these crashes indoors in my flat but as I've tested directly afterwards with the Avata2 with MC3 (and nothing happened), this seems only to be a issue with the NEO and MC3.

I think this is ATTI mode by not having GPS or Vision of the ground due to low light.  I haven't experienced it with the Avata2 as never flown it indoors.  Not too much of an issue with the Remote Controller as it'll be similar to Manual mode or i'll already be in manual mode but for the Motion Controller its a different ball game.  It feels like if using the motion controller and it goes into this mode that it should just drop or attempt to get lower to the ground rather than full pelt away in any given direction.

I won't fly it in low light again (even though it was a fully lit room, especially with the MC.  Sensors obvs not as good as the Avata at this price point.

Fun toy though :-)

Low light ability is a 'must have' for me as I'm often flying indoors in the equipment room of a gym, which is really a lot of fun! I wanted to use the NEO there instead of my 'old' analog FPV-whoops.... And as I'm also really a big, big fan of the MC3 controller, I would prefer to use the MC3 instead of the FPV3 or RC2. So, please DJI - clear up this bug!

Does anybody know whether the issue with the MC3 indoors is fixed with the new fw release? Do not want to test it indoors and have the NEO crash again into a wall :-(

ralf-djiforum Posted at 9-17 07:59
Does anybody know whether the issue with the MC3 indoors is fixed with the new fw release? Do not want to test it indoors and have the NEO crash again into a wall :-(

I've had just the same problem. I have the updated firmware so it hasn't been corrected within this latest update.

I've been flying indoors and with plenty of light and I'm getting exactly the same problem you have. I do hope they correct this issue because it's one of the main reasons for getting this little drone. Something to fly round indoors when the weather is crap.

Interesting. Ordered the Neo a few days ago primarily for indoors winter season flying or the occasional in the outdoors just around the yard on very light wind day sessions.  Only have the Avata2 Fly More Combo kit. FPV RC3 was at the top of the "DJI List" until that funding was spent on the Neo.  Guessing and incentive to put in an order for FPV RC3.

I really would like to stay with the MC3 instead of the FPV3, because I like the way of flying with the MC3 (even indoors with the Avata2). I had hoped that DJI would see this issue as a priority one and fix it with the last update. That probably was a wish a little too soon :-((((((

Crashed inside as well. Have 2 other DJI drones have never seen a glitch like this. Are we meant to fly in S mode inside? When will this issue be resolved?

Same here, I just bought the Avata 2 combo to get the goggles 3 and the motion controller 3 for the Neo. Updated the firmware and crashed 2 times indoor into a wall. The Neo suddenly accelerated and could not be stopped! Now I know that others have the same problem

Count me in--same issue indoors even though in a VERY well-lit environment. The drone just takes on its own ideas and ignores my inputs. After that happened on 10/1, I've flown only outdoors the past two days. I was doing OK using RC2 but crashed once today (10/3) due to similar behavior in a tight space and I believe I flew that time without waiting for GPS. These little guys are tough. No harm after a hard crash on concrete that dislodged the battery and sounded bad.

I flew a few more times with Goggles and MC3 after waiting for confirmed GPS and had no problems except some high winds when I flew too high and exposed. Clearly I need to be more careful to lock in GPS outdoors but the indoors problem is troubling. I also have an FPV controller 3 but I'm not skilled enough to fly manually with any confidence. That's a learning curve that's going to take a while. Still crashing repeatedly in Liftoff and struggling to hit even the biggest gates or openings. I agree with the previous poster who prefers MC3 as I've had very good luck with it, given my minimal FPV skills.

Today (10/4) I made a concerted effort to fly indoors. This house is VERY well-lit but it does have some dark wood and paint colors in certain spots. I can now replicate the behavior on demand after crashing at least four times.

It goes into suicide mode so quickly that you can't react with the pause (orange) button on the MC3. In the goggles, the N "Normal" mode indicator switches to red (for Nuts? ... because the drone goes insane until it crashes).  A "CAUTION: No satellites/vision ..." warning also appears but, by then, it's already too late.  I tried once to pause it when it clearly got confused and gave me just a moment to react, but that didn't work. After trying to pause multiple times I guess I'd hit the orange button four times and the motors just stopped, dropping the drone hard on a tile floor. I checked in the Goggles 3 and the "4-time press to emergency stop" option is disabled. C'mon DJI!

Obviously, this firmware version is lacking and an immature work-in-progress. Until they fix these issues, I think the drone is not suitable for indoor use unless you're skilled enough to fly manual mode with the FPV controller. I haven't verified this but it's the only method by which I've seen others successfully fly indoors even though I've scoured the U of Tube. I am quite disappointed as my use case for this tiny drone was mostly indoors and confined spaces. I'm going to have to rethink that.

In another note, this environment is MUCH brighter than could be delivered by any flashlight that the Neo can carry.  I have the OriginalDobo light mount for the Avata 2 which works well, but that's not going to be the solution for Neo. I believe you'd have to illuminate both the camera's FOV and the area below for the downward sensors. I agree with another comment I saw earlier that DJI should allow us to exert complete manual control by turning off the clearly inadequate position sensing (in its current state). Hoping that a solution is forthcoming.

Maybe manual FPV control is the only way I'm going to be able to use this as I'd intended?

Yep. Exactly the same thing happened to me today. Indoors, goggles 3, motion controller 3, no satellite lock (only 3 or 4) Flying slowly passed over a couch sudden acceleration straight into a wall. Not ideal
Hopefully this can be fixed with a firmware update.

Irrespective of the camera and low-light limitations, the thing that MUST BE FIXED is this consistent behavior: "Neo confused, so Neo accelerate and crash now."

That's just inexcusable. Also, I keep hoping someone will weigh in on whether Manual mode FPV control eliminates this issue.

DJI, please get this issue fixed ASAP!! Indoor season for me is going to start soon and I really wanted to present my new NEO there at the first meeting and show what it's capable for! But with this issue still well known in public and not fixed yet, I think my mates just will start to laugh if I show them the NEO. DJI - your reputation is going down the drain.....  

Similar experience during first indoors test flight. N mode at factory set gains. Don't remember if flying with RC3 or MC3. All was fine until I reached the top of the well natural lighted open stairs to the loft.  Big shadow thrown by the sofa which has a dark quilt draped over it.  Image went dark and sort of grainy. Neo by itself seemed to have accelerated at least once straight into the quilt.

Not being the brightest bulb in the room tried another indoors test flight couple days ago. Well natural lighted great room.  No issues.  The brains dimmer switch must have been turned way down.  Decided to fly under the dining room table.  Need speed at low altitude or auto landing kicks in.  Too late to change my slow mind.  Luckily no issues flying in the shadow of the underside of the table. Wondering if the camera sensor system is part of the position feed back system? What the camera captured flying under the table was a bright image vs. the quilt's dark image.

If it is the stabilization system that is getting confused by what it is "seeing".  Wondering if DJI can update the firmware with a option to shut the system off.  N and S mode would then become like conventional Angle mode which is fine for indoors flying in small spaces.

Guessing DJI's main market for the Neo is the person interested in  outdoors autonomous image capturing.  Hope was the Neo would make for a nice flying indoors quad.  Right now I think I'm reserving it more for a manual mode, immersive flying, windless conditions outdoors quad.

I just experienced something similar. There as a bit of wind but I did a few helix shots with no issues. I started flying the drone manually with my iPhone when the drone suddenly went wild. I tried to land it as quickly as possible but it still went into my neighbours backyard.

ralf-djiforum Posted at 9-19 08:55
I really would like to stay with the MC3 instead of the FPV3, because I like the way of flying with the MC3 (even indoors with the Avata2). I had hoped that DJI would see this issue as a priority one and fix it with the last update. That probably was a wish a little too soon :-((((((

I have been experiencing the same issue with the fpv3 as well as with the manual controller.  Guessing the issue is with the satellite link as mine seems to do it every time i go through the interior hallways of our home.

I have also been experiencing this issue but am seeing it with both the motion controller and the controller 3.  At first I figured it must be a low light issue, so I turned all the lights on in each room, but the Neo keeps doing this every time I go through an interior hallway and I am guessing it is due to the drone losing satellite contact as I always get the red satellite warning just before the drone takes off at full speed.  Kind of annoying as I specifically bought the Neo to capture interior video footage of properties at the request of a local Realtor.  That and because of the fact that it is light enough to be safe to fly over people at indoor functions.  Turns out to not be so safe if the drone suddenly decides to tear off at full speed on its own every time it drops a satellite link.

The Neo is one TOUGH little drone.  Tones of fun to fly FPV with but it does take some getting used to since its tiny size make it behave somewhat differently than the Avata 2, so be prepared for several wrecks early on.  The good news is that it is so light that even bouncing off things at full speed seems to be right up its alley.  Perfect starter drone so I sure hope DJI can work out things with our government here in the US, since none of the approved drone manufacturers here currently make anything nearly as versatile anywhere near the price point DJI offers.

Same issue here

djiuser_WInTCzzNR6yE Posted at 10-18 18:45
Same issue here

Hi djiuser_WInTCzzNR6yE,

Thank you for reaching out. As mentioned on the 6# thread comment, kindly sent us flight log for us to check this with the relevant department. We are looking forward to your response for further assistance. Thank You

Today we started our winter season flying at the gym. Besides other toys I took the NEO with me (because that's what I bought it for) and also the AVATA 2 for comparison. Flying with the NEO was a DESASTER! Every few minutes it crashed because of suddenly accelerating and being uncontrollable. It didn't matter which controller I used - MC3, FPV3 or RC-2. It even didn't matter whether the floor was without pattern or whether the floor had a pattern on it with clear and colorful lines for badminton, basketball etc.. Also lighting conditions seemed to have no influence. Flying in a well lit corridor - crash, flying in a badly lit equipment room - crash. I even installed a power LED underneatch to lit the ground - didn't matter. Sometimes I got the 'N'-mode icon turning red and the message 'no satellites' before it started, sometimes not. The only positive thing to say is, that the NEO is really, really sturdy - it took all these crashes without any damage. If turtle mode would be an option, I even would have been able to keep staying at my seat and mostly restart it without having to walk.  
But at the moment the NEO with the latest Fw release for me is not usuable for Indoor flying at all, doesn't matter whether you use the Goggles3 for FPV-feeling or whether you use the RC-2 just for fun flying. Please DJI fix that!!!!!!! Otherwise me (and probably many others) will return the NEO. With this bug I also would really not recommend to use the NEO for one ot its advertised advantages - to use it indoor as a small and light-weight drone for real-estate exposes. Think of the consequences when NEO crashes uncontrollable in some really expensive interior.
No unexpected crashes with the Avata at all (flying the same course and spots in the gym). Only when the Avata went out of 'N' mode because of no satellites and into ATTi-Mode, I sometimes was not able to control it because of flying with the MC3 (the FPV 3 is a better option then). Having turtle mode then really was nice :-)

issue since it was connected to no satellites plus low light bottom vision sensors didn't respond well.

Low light ,not enough satellites, definitely flying in ATTI mode.

Funn 1 Posted at 10-20 09:03
Low light ,not enough satellites, definitely flying in ATTI mode.

Yes, but ATTI-mode normally doesn't mean to go uncontrollable with full speed into the next wall. I'm experienced enough to fly ATTI or even full manual mode, but here no control was possible.

ralf-djiforum Posted at 10-20 11:19
Yes, but ATTI-mode normally doesn't mean to go uncontrollable with full speed into the next wall. I'm experienced enough to fly ATTI or even full manual mode, but here no control was possible.

Agreed 100%. I flew again today with GPS and Goggles3/MC3. Flew underneath a house during daylight but it was as dark as you'd expect a crawl space to be. Full speed, straight line until head-on crash with stationary 4x4 post and no control whatsoever. There has to be a firmware fix for this.
When switching the Neo from Sport to Manual mode with the FPV controller, there's even a programmed transition where DJI asks you to zero-out the throttle stick. This sudden "ATTI" transition gives no warning or any chance for us to retain control.

What I'm wondering about at the moment is, whether really low light conditions have to do something with this. F.e. at one time my flat was well lit when it happened and also the main area of the gym was well lit and it happened in this area, too.

i have the same issue I bought this drone for inside the house, so far just accelerated out of control and hit my 3000.00 tv.  

Probably it won't be long til somebody claims a case against DJI because the drone has destroyed something really expensive whilst going wild (or, even worse, hits a person)

Bad form here, but something that is a serious flaw that needs to be fixed if possible. Duplicate post from other threads regarding this issue.  

If the sensor hardware limits.  Need to have a manual engaged and disengaged ATTI mode option in N and S modes for all controllers.  Right now we are limited to FPV RC3 manual mode to fly this drone in poor lighting, sat lock environments.  You can lock in or out of ATTI.  People of my skill level find it very challenging to fly in tight areas indoors under M mode. Assuming the rates and gains, PID settings are mellower in N and S mode.  Might allow for most of us to fly indoors in ATTI mode. The other option is a bit cumbersome.  After trial and error in finding your ideal indoors gain, rate, and center sensitivity.  Change back and forth those settings for indoors and outdoors flying.

Atti mode itself won't be a problem, if it would function properly. ATTI mode (as IMHO DJI understands it) would mean that the NEO would keep it's height above ground stable whilst using barometric data and without stick inpout it just would drift around. But with this issue, even if it is ATTI mode which the drone jumps into, NEO accelarates without stick input and you no longer can control. So this so-called Atti mode also is faulty (IMHO) .   


And - sorry to ask that - to what do you refer as 'bad form' here? I'm not a native english speaker and depending on some online translation help - is 'bad form' something like bad or inapropriate behavior? If I have insulted someone with a post, I feel sorry for that and please excuse me! That I'm feeling a little impatient with DJI should be understandible, shouldn't it?

ralf-djiforum Posted at 10-21 07:01
Atti mode itself won't be a problem, if it would function properly. ATTI mode (as IMHO DJI understands it) would mean that the NEO would keep it's height above ground stable whilst using barometric data and without stick inpout it just would drift around. But with this issue, even if it is ATTI mode which the drone jumps into, NEO accelarates without stick input and you no longer can control. So this so-called Atti mode also is faulty (IMHO) .   

Bad form is me basically restating the same comments in different threads.
  
The loss of control. Literally no response to  user input resulting in no control issue has been noted in a number of threads here at the Neo page.  Obviously an issue for flying the Neo in marginal lighted and/or poor satellite lock environments.

ATTI mode shuts off the stability control, but puts limits on the degrees of movement.  Think angle mode in a non-DJI quad.  The FPV RC3 when set up for manual mode has a toggle to disengage or activate ATTI mode.  Right now its how I've been flying the Neo in M mode.  So no rolls, loops, and real sharp maneuvers.  DJI manual mode with ATTI engaged is sort of a manual training mode. Something between S mode and M mode.  IMHO, it allows the Neo to be a nice manual mode trainer.   

Same here. I can fly it in a hallway and certain rooms in my house all day long and it doesn't do that, but in certain areas in some rooms it just takes off forward out of control with that warning message. I'm using the Goggles 3 and the RC MC 3 and everything is on the latest firmware. It should just hover in place instead of blasting off. Come on DJI stop asking for flight logs and acknowledge there's a problem and fix it. There are enough people on this thread to show there's an issue.

deckt Doch mal alle drei bereiche, imgesammten ab unter der drohne

I have the same issue.

I have the DJI NEO with the RC-N3 controller. With the RC-N3 there are no issues whatsoever (either outdoor or indoor).

With the G3/MC3, in indoor flying I have the flying straight unable to stop issue even when I let go of the MC3 throttle or went into reverse. The neo is in beginner mode. This has now happened 4 times in the last 7 minutes. It is not a sometimes issue, it always happens.

I have not had a chance to fly outdoors yet with the Neo/G3/MC3.

It is not a low light or GPS condition since the RC-N3 controller had no issues. It is likely a firmware issue with the Neo/G3/MC3 combo.

Unfortunately I could not make a Neo/G3/RC-N3 pairing for further testing. The only controller choices that show up with the G3 is the MC3 and FPVC.

-----

Update 1:

It just happened with the RC-N3 as well (indoor, RC in C-Mode for slowest speed). Drone kept going forward even when I let go of the throttle or go in reverse before hitting the wall. The odd thing is it never happened with the RC-N3 before I paired the Neo with the G3 and MC3 for the first time (just lucky?). Now I don't know what it is.

Another observation. When I had the lighting in the house at 50% (daytime but very cloudy outside) the issue cropped up (RC-N3). When I switched on all the lights in the house it seems ok. But I've only tried 1 cycle of lights 50% (issue) and lights 100% (no issue). It is odd though, why would lighting (or GPS) affect how the drone ignores throttle position on the RC.

I will run more tests.

---

Update 2:


Happened again with RC-N3 C-mode (Indoors in well lit area).