Recent content by BudWalker

I've tried using the stylus with just the RC 2 only. Still a little difficult to use but much better than my fingers. Just to be clear the stylus I'm referring to is not the Apple Magic Pencil you mentioned.

A stylus like this https://www.amazon.com/dp/B09CDCN7VS?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_2&th=1 helps a lot. Might be easier to use in the field. I just now tried the mouse approach. I'd have to say that it's a game changer. Yikes!! The mouse scroll wheel works to zoom in/out on map...

My theory is that the leftBack came into contact with the chimney which caused the CW roll and pitch down attitude. Depending on how it's measured the distance to the chimney can be as little as 0.5m. That's well within the margin of error. Why did the rightFront speed decrease instead of going...

The gyro data shows that the CW roll occurs just slightly ahead of the rightFront being commanded to 100%. That probably means something caused the CW roll and the FC responded by commanding the rightFront to 100%

If installed on Widows is a requirement try FlightReader It accepts .txt logs

@Ce226uk I assume you are asking about the .DAT for the Mini2? Unfortunately, both the the onboard .DAT and the controller .DAT are encrypted. So DatCon is unable to process these .DATs.

The .DAT log file on the Mavic itself will have higher speed data that will show if the battery disconnected. Can you retrieve that FLY143.DAT and provide it via Dropbox or similar? Take a look here How to retrieve a V3 .DAT File from the AC to see how to retrieve it. The motor voltage data in...

Regarding using DatCon/CsvView to process a .DAT log file. It depends on which DJI platform you're interested in. The more recent platforms will have encrypted .DAT log files and can't be processed by DatCon/CsvView. AFAIK these platforms and before will have non-encrypted (i.e. useable) .DATs...

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...