I am also located in Edmonton.
tom3holer said:
Did you have a GoPro camera installed and by any chance was the wifi turned on?
That is a sure way to cause a crash.
Tom
Gopro was not installed at the time. I removed my H3-3D gimbal and GoPro when I noted my unit was having issues. Good idea though..
I didn't originally intend for my question to be a technical one, but more as to whether or not I should purchase another unit based on the 'success' of the new firmware update and just ignore the cause of the issue with my particular unit. When I re-read the question, it does seem pretty retarded the way I wrote it. Sorry about that.
As I can see you fellas are looking to help with the technical side. Here are some notes and anecdotal evidence:
- Controller has been in both Phantom and NAZA mode throughout my testing. Crash occurred in NAZA mode while GPS mode was engaged.
- Unstable descent was a very heavy wobble when bringing the unit down from about 100 feet at about half throttle. It really seems like it could be a symptom of VRS...
- Symptoms only appear in GPS mode. No symptoms in ATTI mode.
- When under GPS lock (indicated by LEDs), the unit will typically drift to the right 6-18 feet upon liftoff and sometimes will show signs of TBE if left to hover. The craziest thing is how far to the right it would pull upon liftoff. It would never pull to the left... Varying levels of correction are required in flight depending on the particular flight.
- Sometimes the symptoms seem to decrease over time as the unit is operated, but sometimes the unit won't descend properly or the 'drift' cannot be corrected unless ATTI mode is enabled. I've had a flyaway issue that I managed to recover (approximately 300 feet away before I was able to recover it).
- When the unit is acting up, the symptoms are most noticeable during yaw and almost require the control stick to be maxxed to one direction or the other to correct the phantom's choice in flight direction immediately after performing a yaw function.
- All symptoms are on a 'per use basis'. If the unit just happens to be stable at the start of the flight, it will continue to be stable throughout it. If I land it, power cycle it and repeat (or don't repeat) the compass calibrations, it may start to have these issues again. I've had to repeat the power cycle and compass calibration 5-10 times to be able to get the unit to hover in one place and not drift or be unpredictable. I can literally tell within 1 second of taking off if the unit is going to be stable for the flight or not. In the case of the crash, I tried to ride it out and see if I could get the unit to be more stable over time in GPS mode.
- All calibrations completed in software (RC sticks and compass)
- Tried performing compass calibration before each flight and also NOT performing the compass calibration after a successful flight and after a power cycle. There is no link between the symptoms are doing too many compass calibrations in my observation.
- All firmware updated (or so it says in the DJI software)
- GPS unit is in correct orientation and top of phantom is attached to phantom in correct orientation.
- Performed deguassing of compass.
- Battery above 75% at time of crash.
I just cannot believe that the symptoms could be so drastic during one flight and nearly gone in another. I've done a lot of my testing in a farmer's field away from anything related to interference. Aside from the terrible crash, I would say that the hooking I would experience is far worse than anything I have seen in videos. It would hook at an angle greater than 45 degrees. Other times it would just fly straight as an arrow.
Maybe I'm doing something incorrectly, but it would have to be so simple that only an idiot could miss it.
Lastly -- for those in Edmonton, can you let me know about the performance of your unit? This will help me determine whether or not I should buy another unit. Thanks.
