Recent content by BudWalker

My apologies. My attempt at brevity seems to have backfired. I didn’t say or mean to imply that tumbling was normal flight. This appears to be the behavior usually seen with simple propulsion loss. A collision followed by thrashing about would have looked different.

But, we do have GPS velocity data. That's the xSpeed and ySpeed data that the GPS receiver obtains from the doppler shift. xSpeed is north speed and ySpeed is east speed. hSpeed combines xSpeed and ySpeed. The direction of flight can be obtained as arctan(xSpeed/ySpeed). These are speeds not...

Is it possible the Air 3S came close to the tree, managed to pick up You're right. The point was that the Air 3S wasn't launched that close to the where the incident occurred. The tumbling that began at 5.85 secs is orderly in the sense that rotation is about all 3 axes. The horizontal speed...

I prefer to base my analysis on numbers. To that end I was able to integrate the horizontal speed to determine the Air 3S travelled 4.6 meters before it started tumbling and then an additional 1.1 meters before the recording stopped. The Air 3S achieved a height of 13.9 meters and started to...

True enough. But, the Air 3S didn't, on average, slow down any. The velocity variations are what is normally seen with the tumbling. Also note that obstacle avoidance was enabled but isAvoidingObstacle is False. I'm still going with, just barely, that the cause was propulsion loss not being...

I can appreciate the conclusion that the Air 3S was flown into the tree. From the description the Air 3S was launched without sufficient GPS, no visual contact, etc. The props shown appear to have had the tips worn off - just what would be expected from being caught in a tree. But I'm still...

Ouch! Looks to me like the right back motor/prop lost propulsion. Either prop or motor loss. At time 5.7 secs the Air 3s begins to rotate in all 3 axes: pitching up, rolling CW and rotating CW about the Z axis (yaw). This is consistent with right back motor/prop lost propulsion. Also plotted is...

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