Sorry mate …
If DJI don’t come through with a refresh, I’d be happy to donate to a fund raiser … I want to see a >122mph record next !
Sorry mate …
If DJI don’t come through with a refresh, I’d be happy to donate to a fund raiser … I want to see a >122mph record next !
Really sorry the Mini 2 doesn’t want to be found but sort of feel it has to be. Even if it’s damaged beyond repair, it’s the Flying Scotsman of the drone world. Incredible feat, even more so without a power hack.
It’s also fantastic to see people coming together to help, be it dragging their boots through muddy fields to hours of watching videos.
Anymore footage or stills for us all to scan through Chris?
Just copying them off the SD cards now
Dave arrived on site not long before me, and we were searched different areas today. So the updated search area map (below) may be inaccurate. Searched area is in red.
I took lots of photos and a video of this area below, the ‘woods’ (red) and the ‘bush’ (blue).
The Woods:
About 250m long and have been searched at least half a dozen times now. There is lots of plastic and debris littered within it. I have included 26 photos of this area in the link below.
The Bush:
Just below the woods is a large, tall bushy area, full of brambles. I have also taken 7 photos and a video of that area too.
Downloaded and looking through carefully
So disappointing.
As intimated above, I took a totally different approach, today. Not that any of the ideas above are flawed … but the bugger hadn’t been found by following them through.
So - I thought - what haven’t we considered?
That would fall to the ground completely differently to the “Descend on disconnect” theory that had been used so far. Basically free-fall, and even taken upwind if a big bird took it out of the air.
So - with that in mind, I’d prepped a few Litchi missions to box-search three of the fields and take Hi-Res images every 0.25secs.
I’d set this up for the field beneath the disconnect …
… hugging the ground contours at 15ft height.
I’d prepped ones for the next field north, and the field to the NE of the strip of trees where Chris had brief reconnects.
It was nice and sunny, ideal for a short exposure times … but Litchi only works with the MP in P mode, not S … and the wind was blowing a hooley pretty much until we left.
So - a foot slog it was.
First, a very slow detailed search of the hedge along the north side of the field beneath the last good position (red), then a careful box-search (blue) of the area beneath the last good location (yellow) … in case it fell quickly or was taken upwind by a buzzard (or similar).
So - whilst nothing more than a whim to look at it this way, I can guarantee that it’s nowhere there abouts.
I followed that with a slow walk along the east of the trees - near where the reconnects happened. Nice brightish sun and a clear sky meant the trees were superbly silhouetted, and I took time to look every branch and twig up and down (even with binoculars) looking for the regular shape of a Mini amongst the abstract twiggery. No joy.
Yet another walk back down in amongst the trees, looking up and scouring the ground. No joy.
Another walk up along the west of the trees - again carefully looking the branches and twigs up and down in the excellent light, and scanning carefully all the way to the ground in case it had just been taken into them by the wind. No joy.
As I was doing this I did some calcs … again assuming free-fall.
From 65m, the time for an object to fall is ~3.5 secs, let’s assume that air resistance extends that to 10 secs (at a max, I’d reckon).
Let’s also assume a wind speed at the time, at that level, of ~50mph = 22 meters per sec (sorry about the mixes imperial/metric … I’m old enough I do both and swap depending on what it is. )
Anyway - that means a max 220m that it would have been blown …so, in the field to the north of the “last known position field” I walked back and forward in arcs about 10/15m apart - to a total of 275m from the last known position (roughly - not pissed - just checking things as I walked).
I repeat - so disappointing. All the effort Chis has put into searching, let alone my two afternoons, and not a sign of it. 10km/15ksteps (not bad, one week after being under the surgeon’s knife - his work has been tested and confirmed a success - I couldn’t have walked that far 1 week ago today! )
The farmer has Chris’ contact details should they find the drone. The field of my last searching has about 25 heifer roaming about it. Hopefully one of them hasn’t swallowed it. … because the vets bills for removing a drone from one of their stomachs …
And this is Dave performing a similar search on the East side. Definitely good weather for searching today.
That’s all the zig zagging you were doing! I only did 13,700 steps today, but over 60,000 since the search began. I had to cover my right knee in Voltorol a few minutes ago.
Great effort guys, You and Dave have really covered some ground again Having a good scan of all the photos and vid at the moment
I spy with my little eye:
I don’t see anything I would say is a MINI 2. Please can we have more eyes looking through the images and videos…
Maybe clutching at straws, but running out of ideas
I noticed this in the West Woods when reviewing the 26 aerial images.
This would put the object about here …
I used Gigapixel AI to up the resolution to 67MP.
Original and upscaled images below.
I think the only way to find out is to go and look.
Just replaying the screen recorder footage, specifically the last 10 seconds. I can’t see anything that looks like there was any impact. I see that transmission bars were cutting in and out for the second half of the flight … first being at 0:34, last at 1:11, where it dropped from 3 bars to 2 bars - before disconnecting from the RC at 1:16.
Further analysis of the flight data:
1m 48.6s - Confirms that the “MC.failSafeAction” did indeed switch from “Go Home” to “Land”
The downlink was pretty hit and miss for the last half of the flight:
Back to the drawing board … fields …
Also the data suggests that the motors were off on the last row, with “Motor Fail Reason” showing “ESC stalled near ground”.
OSD.gpsNum | OSD.gpsLevel | OSD.isGPSUsed | OSD.isOnGround | OSD.isMotorOn | OSD.isMotorBlocked | OSD.motorFailReason | RC.downlinkSignal | RC.uplinkSignal | BATTERY.chargeLevel | MC.failSafeAction |
---|---|---|---|---|---|---|---|---|---|---|
6 | 2 | FALSE | FALSE | FALSE | FALSE | ESC stalled near ground | 0 | 18 | 83 | Land |
A Drone has been handed in at Chippenham police station a few days ago.
Funnily (har-har) I was also re-examining the logs.
A missing 11.19 secs … almost no change in position (5ft), even though ~32mph (both with 18 satellites).
The time is GPS time … and with 18 satellites we can trust that there is a missing 11.19secs.
OK - now for the more puzzling info …
The final line (if one believes it) shows it wasn’t moving in any axis …
Also - the final line does indeed suggest it’s upside-down …
BUT … it cannot have climbed 45ft.
Those last three items suggest to me that it’s rebooted … upside-down … somewhere.
Oh - and it had changed from Sport to P-GPS for that final line.
They do always start in p mode regardless of switch position.