My Octo pre-flight checklist is exhaustive, but still there are things that my moderately comprehensive setup cannot tell me:
Because we don't (and neither do our flight controllers) fully know the status of all onboard systems.
Until we do we're flying blind and so are our Wookong-Ms etc.
Flew a new craft 8 times recently, then went out again and it was bucking all over the sky - I'd changed nothing. In an ideal world I'd log in to my DJI log and diagnostics data and find out what it was.
OSD will be nice but how about data logs, diagnostics (If I know how I controlled it but it behaved like this then I can infer what might be wrong). How about a proper monitored power supply?
I could go on. Before the bells and whistles there has to be a solid foundation based on data. That's partly why Droidworx went off and hid in the lab - they've had to go rethink it all - end to end.
Wake up DJI - we are all out there potentially collecting data for you to use to improve and evolve your products, come get it from us!!!!!
- ESC temp
- ESC PWM in
- Attitude
- Vibration
- Rotor RPM
- Power Loom status
Because we don't (and neither do our flight controllers) fully know the status of all onboard systems.
Until we do we're flying blind and so are our Wookong-Ms etc.
Flew a new craft 8 times recently, then went out again and it was bucking all over the sky - I'd changed nothing. In an ideal world I'd log in to my DJI log and diagnostics data and find out what it was.
OSD will be nice but how about data logs, diagnostics (If I know how I controlled it but it behaved like this then I can infer what might be wrong). How about a proper monitored power supply?
I could go on. Before the bells and whistles there has to be a solid foundation based on data. That's partly why Droidworx went off and hid in the lab - they've had to go rethink it all - end to end.
Wake up DJI - we are all out there potentially collecting data for you to use to improve and evolve your products, come get it from us!!!!!