Recent content by BudWalker

Did you submit the correct .txt? There was no lateral movement during the few intervals where the sticks were neutral. Yaw varied only 1° when the rudder was held neutral (most of the flight).

@slup @msinger good observations about yawUnWrapped. CsvView computes yawUnwrapped differently than Mike’s algorithm. I like his method better and will use that in the next version of CsvView. Both methods have the same fundamental limitation due to a low sample rate. I noticed that that...

At least for these 2 flights there is no difference in performance; lateral thrust is the same. Any difference in prop effectiveness (if it exists) is compensated. We need to see a difference in performance before we can ask is it due to the props.

Looking at motor RPMs hurts my head. And it's hard to infer thrust values. So, I took the easy way::) If we can assume that the 2 MA1s weigh the same and they have identical drag, then the tilt angle can be used to determine thrust. Using tilt/thrust allows us to ignore differences in ground...

Why haven't you provided the .DAT logs for both MA1s? Looking at the .DATs is the most likely way to answer your question.

I believe that's reversed. ySpeed is along East/West (longitudinal) axis. And xSpeed is along North/South (latitudinal) axis

"and then restarts" How do you know it restarts? When found on the ground is it in the powered up state? Next time this happens could you get the Fly App to reconnect with the MA2? The resulting .DAT will have the info necessary to determine when the MA2 powered up even though that was before...

Is there a FLY042? The FC may have crashed and rebooted.

"Hmmm I can't find motor rpms in the DAT !" It's there. CsvView/DatCon isn't smart enough to recognize it. Make sure that All Signal Croups is selected. The motor data is found in esc_data

That's my expectation.

I agree 100%. Unfortunately, that’s not going help much. You might try posting this over on the DJI forum. At least there will be the possibility that DJI will read it before ignoring it.:(

I think this was a deliberate choice made by DJI engineering. So, I don’t see much chance of a successful warranty claim. But, you won’t know if you don’t try. Which is a greater probability; 1) ground is moving, or 2) location solution isn’t correct. I would choose 2. Aren’t there explicit...

It looks to me like the pitch forward had the proper effect. At 200 secs the Mini4 started to gain NE speed because VIO started tracking the water flow and there were no control inputs. I.e, the Mini 4 thought it was hovering but was actually moving with the water. Full pitch forward wasn't...

For anybody wanting to look at this here are the log files 2024-09-17_15-27-13_FLY234.DAT DJIFlightRecord_2024-09-17_[15-27-59].txt

I learned a lot with this one. With just the .txt and sketchy GPS data I assumed that it was the GPS doppler velocities that caused the problem. But, then @djules75 provided the .DAT and it was clear that it was the VIO velocities that were incorrect. We’ve seen a lot of incidents were only the...