Totally agree. As long as they don't go crazy on the price. It brings great value but gotta keep it reasonable.Good business. I respect them, they showed their value and now they are getting compensated. How many threads include 'what did Healthy Drones' say?
What do you really want to know? (I'm building a log viewer, so I'm curious.)I think that's because the system isn't really telling me anything that I really want to know.
What do you really want to know? (I'm building a log viewer, so I'm curious.)
+1What do you really want to know? (I'm building a log viewer, so I'm curious.)
What do you really want to know? (I'm building a log viewer, so I'm curious.)
Sounds like it would be very useful.No problem - battery voltage in each cell, obviously, in real time. Variations (in real time) between individual cells. Total current draw. The relationship between stick inputs and actions. Motor RPM and load for all four motors. Mod values, ascent and descent rates, horizontal speed. Which mode the craft was in at the time. Satellite count. Battery temperature. IMU temperature. Altitude, both in relation to sea level and take off point.
The things that make assessing what went wrong in the event of a crash useful. IMHO, healthydrones doesn't address these. That said, it's working on the information that is stored in Flight logs in the app - whereas for the 'useful stuff' the .DAT file has to be retrieved. But that's where the real information is. And using budwalker's data converter and dumping the file into luap's dashware is very easy once you have retrieved the .DAT file.
Can you give us some specific examples?I don't agree with their assumptions on their algorithms
We use essential cookies to make this site work, and optional cookies to enhance your experience.