LordoftheFlies
lvl.4
Offline
|
Okay so I get to be the aviation jerk: FAA states NOT flying over people for a reason...
But to be an engineer again. If I were coding this drone: I would tell active track to use a "continuous update" on the tapfly function. So, if the SUBJECT moves, the software will automate the new position automatically throughout the internal coding. rather reprogramming a whole new MODE. It looks like the programmer did not include a "stop signal" to the "TAPFLY-listener" if the track is lost or fails in this new firmware, thus resulting in the last tapfly input to approach your freaking mug. Which is pretty freaking awesome, i may add.
So in active track its:
Tracking -> update tapfly input -> tracking -> update tapfly input -> tracking failed -> use last tapfly input.
This makes the most sense to me, yes it is a shortcut in code, and a rather easy one to fix. They just need to create a gate that outputs a "0" to the last message received from the tapfly "listener".
BUT THE FAILSAFE SHOULD BE THE PAUSE BUTTON! PLEASE MONITOR YOUR DRONE'S BEHAVIOR at all times in these shooting modes and have a thumb over the BREAK at all times.
The only to prove this wrong would be the drone flying WHILE the OPTICALS COLLISION SENSORS were active/working, then everything I said was a lie. Not really, bc even if the track fails the MA will use the last TRACK input as a TAPFLY input. SO, KEEP AN EYE ON YOUR AIRCRAFT ALL TIMES WHILE USING THESE SHOOTING MODES! |
|