Skywalker 1900 Crash

BlueFlyer · April 03, 2016, 08:20:15 PM

Witness the end of my Skywalker 1900... not the Vector's fault... it actually did what it was told to do... unfortunately the failsafe was telling it to do the wrong thing lol. Some time between the last flight and today's flight, the EzUHF failsafe had been set to "centre all channels", which put the vector into 3D heading hold mode with 50% throttle lol... thank goodness it was pointed to the ground not the sky lol :)

FPVSteve · April 03, 2016, 08:56:01 PM

Wow something not quite right there /obvious.

Western · April 03, 2016, 08:58:29 PM

Sorry to see that happen Blue.

Jameskibler · April 03, 2016, 09:00:39 PM

If that sheep had any pants they would have definitely been soiled

BlueFlyer · April 03, 2016, 09:03:12 PM

haha, the sheep didn't move... just not phased by the event at all...

In fact, when I went to retrieve the plane from the hedge (front end was proper jammed in there) the sheep wouldn't leave me alone... must have thought it was feeding time or something.

wgt40w · April 03, 2016, 09:13:49 PM

Quote from: BlueFlyer on April 03, 2016, 09:03:12 PM
haha, the sheep didn't move... just not phased by the event at all...

In fact, when I went to retrieve the plane from the hedge (front end was proper jammed in there) the sheep wouldn't leave me alone... must have thought it was feeding time or something.

They were probably wondering whether to attack you - as they thought you had just tried to kill them!

Really sorry to hear your sad flight news. Are you going to transfer what you can over to your 'other' Skywalker??

BlueFlyer · April 03, 2016, 09:22:54 PM

Quote from: wgt40w on April 03, 2016, 09:13:49 PMAre you going to transfer what you can over to your 'other' Skywalker??

Yes mate, that was the ultimate aim eventually... I guess it's been brought forward lol

Dillwhacker · April 03, 2016, 10:51:59 PM

That's a boo Blue - so you had a perfect storm of RX link broken on the same flight as RTH had been screwed up - bad luck but I guess these things happen.
Hope the new SW is awesome mate.
Happy flights!
;D

dogzilla · April 04, 2016, 12:10:46 PM

Sorry you stuffed it mate. I want to know how you get into FS when you seem to be within pissing range?

BlueFlyer · April 04, 2016, 12:22:32 PM

I know, very disconcerting

FPVSteve · April 04, 2016, 01:14:02 PM

Not sure what's worse, you binning it or if RTH had worked it'd have been circling overhead for an hour with you unable to take back control - imagine the stress!

Maybe you got off lightly given the circumstances, like you say it could have been miles away lol

BlueFlyer · April 04, 2016, 01:33:10 PM

that would have been so funny steve... waiting for it to just drop out of the sky when the LiPo ran out lol...

AdamG · April 04, 2016, 02:17:00 PM

Quote from: BlueFlyer on April 04, 2016, 01:33:10 PM
that would have been so funny steve... waiting for it to just drop out of the sky when the LiPo ran out lol...

There was a video of this happening to someone with a Skywalker... i'm sure it was on this forum somewhere...

I think Blue sabotaged this SW. He hadn't told the mrs about the new Skywalker and needed a good reason :laugh: :laugh: "I need a new one as this one broke :D" lol

Bad news about the crash, at least you were able to find the reason and sisnt lose anything.

How was the AAT?

BlueFlyer · April 04, 2016, 02:33:23 PM

AAT was hit and miss... it did track, to an extent but wasn't receiving a continuous GPS data stream... damn thing kept beeping and it would intermittently stop tracking

Then when the walker crashed into that hedge, the tail must have popped up because the prop had sliced through the GPS cable (which I had put on the shelf on the tail)... so it wouldn't shut up beeping then lol

I'm hoping that with the MFD AP and the V5 driver I'll get a better track

BlueFlyer · April 04, 2016, 03:25:17 PM

I just plugged both the RX and TX into the computer, they were bound OK, RSSI was 1dbm within 1m and -100dbm with the tx switched off.

Both were on 430-450 Extreme hopping, and both were on the same version firmware (v1.52) which is the latest one.

I've just re-flashed them both anyway, then I've re-bound the receiver to the JR module. I can't see anything wrong from here... I'll just have to see how the next flight goes and make sure I test/set failsafe properly before launching.