Recent content by GrettirTheStrong

I wasn't going to assume anyone else would be willing to look at it, but if you'd be willing I'd sure appreciate it: FLY027.DAT. My question is really around what happened in the final 10 seconds or so- why did it keep going forward, and did it perform a RTH or something similar at the very...

Attached I've zipped a few seconds as it goes into the trees. It's still totally in waypoint autonomous mode. You can *see* it stop, think, and then start "nudging" itself into the branches.

I have the .DAT from where DJIA2 allowed me to see the directory of .DAT files. But I don't know what to do with it now that I have it. The doc you sent suggests using CsvView, and in fact I was able to install CsvView and load my .DAT. Now I am at the limit of my competance. Any good guides on...

Well... crap. Thanks. What's the best way for me to try to read my .DAT file to figure out what happened at the end? Can you point me towards the right self-help?

Flying and adjusting a waypoint route. First four times, worked fine, came in about a meter under a branch. Fifth time, came in about a meter high. Why did I not stop when I saw that? Pilot error. Thought it would interpolate height down to the next waypoint. When Litchi saw that the MP was...

Lolo, thank you for recommending I watch the short video. I had seen it before, and moved onto his detailed video (since I had to flash FW twice) but watching the short video made me realize I had missed the enabling parameter in his long video. I wish I could drop like a stone on the descent...

Thank you. I try to do a 20% out, 20% back test flight on my first battery in any given situation, then the second and third batts are for two "summit attempts". Then I try to always turn around at 60% (or sooner if flying with a tailwind).

Found my problem. Pilot error. I fixed three parameters, but there was a fourth I had missed in the video- an enable that needs to be something other than "1". Just flew two 1000+m climbs on neighboring Cascade mountains.

Maybe if I switch to Sport Mode...?

I flew this weekend at (47.4185, -121.1747) after making the changes shown above with DJI GO 4, and the MP stopped at 500m. DJI GO 4 has its own setting for max altitude and you can only set it between 20m and 500m. Ditto Litchi.

Yes. And I did that. See my earlier reply. I'm quite confident my bird is willing to go more than 500m up. But DJI GO 4 and Litchi will not. That's the problem.

I flashed FW 03.0700, updated the params, and then flashed a special version of 04.0300 that doesn't update the parameters. See attached. But my problem is that the vehicle is fine w/ more than 500m, but DJI GO 4 and Litchi are not.

I fly in the Cascade mountains. There are many line of sight <122mAGL flight opportunities that would result in going more than 500m above my starting point. I have done all the FW shenanigans to remove the 500m limit from my Mavic Pro, but DJI Go 4 is hard coded to 500m, as is Litchi. Are there...

All this worked like a charm- I rolled back to FW 3.700, updated my height parameters to 10000, rolled forward to the special 4.300, verified that the parameters were still set to 10000, and flew today. But I must be missing some critical element of doing this right. I run DJI Go on an iPhone...

I want to fly up a mountain. Head 234degN from a 487mASL launch. 120m above a 1200m ground waypoint is 833m above and 642m horizontally is still LOS from home, so there shouldn't be a transmitter issue. It should take me a little under 5 minutes at 3 m/s climb. (Yes, I know I can do 5 m/s in...