23 miles in the NAS!! All on its own

Views: 189

Comment by Dave Buckley on August 26, 2010 at 3:02am
Stupid Navy. They'll ruin it for all of us!

Comment by Gary Mortimer on August 26, 2010 at 3:07am
Well I wonder if they were readying to shoot it down like they did last with the Reaper, you would think there would be a kill switch, unless all comms failed, even then I guess you would think it would do that for itself. They had to be in touch with it.
Comment by Dave Buckley on August 26, 2010 at 3:10am
There are holes in that story you could fly a 767 through.
Comment by Curt Olson on August 26, 2010 at 4:51am
Tested your lost link code recently?
Comment by Ravi Gaddipati on August 26, 2010 at 5:03am
Of course this happens the day after I was in D.C. working at the naval lab...
Atleast it was able to fly, and didn't just crash.

Comment by Mark Colwell on August 26, 2010 at 6:54am
Maybe it was controlled by non-authorized operator,
Comment by Jack Crossfire on August 26, 2010 at 1:11pm
It could have been over an unpopulated area & flown into a populated area if the RTL code failed. Our main concern with RTL code has always been a motor start on the bench.

3D Robotics
Comment by Chris Anderson on August 26, 2010 at 1:55pm
Sound familiar?

"As Cmdr. Danny Hernandez, a Navy spokesman, put it: “When they lose contact with the Fire Scout, there’s a program that’s supposed to have it immediately return to the airfield to land safely. That did not happen as planned.”
Comment by Chris McNair on August 26, 2010 at 1:58pm
"did not happen as planned" Hmmm that never happens........
Comment by Bill Porter on August 26, 2010 at 5:52pm
@Dave: Hey! I take offense to that! (I'm a Navy engineer in Unmanned Systems, but the watery kind) If anything it's a Northrop Grumman product, I'd blame them first. I've worked with both navy built drones and contractor products, and it's a pain to use contractor products. No access to source, no ability to debug, no understanding of the quarks of the system. I bet all the time it was 'lost' was the time it took the Navy operators to get a Northrop Grumman engineer on the phone to tell them what to do since the craft wasn't responding to it's control GUI program.

This line "The Navy is calling the problem a “software issue” that foiled the drone’s operators. " makes me think it was 'Well, we hit the RTH (return to home) button and it didn't do it. now what? It's not our system'


You need to be a member of DIY Drones to add comments!

Join DIY Drones


Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service