Testing the new ArduIMU Viewer with FLEXIPILOT from Krzysztof Bosak on Vimeo.
Unfortunately ArduIMU Viewer is not accepting the protocol that ArduStation likes.The demonstration shows the look of both viewers,where to click on order to configure COM port and alsohow to setup the protocol with FLEXIPILOT.Observe a bug in the viewer making possible multiple creation of 3D cube.You need to be a member of diydrones to add comments!
Comments
Happy,
The actual status is, I am mimicking the output of what YOU use so far.
Examples:
www.aerialrobotics.eu/flexipilot/flexipilot1.2-osd-en.pdf
So I am already compatible to some extent.
Besides those protocols, I have my own BEACON protocol which is about to be published very soon (must improve comments).
Beacon is a unidirectional protocol.
I use my modems the following way: one is sending unidirectional porotocols,
the other is a bi-directional access to the console,
therefore if you want to make ACTIVE groundstation,
it would be best to allow assigning sending a custom string upon button press.
This can be @@@PARA for parachute opening, @@@RETHOME for mission abort, @@@THRDISABLE and so on, @@@WPTGO5 for selecting wpt #5, or any other command including waypoint redefinition.
If you can do something with buttons that can send any string that is terminated with CR or (best) CRLF or LF,
many ppl would be able to affect the most-resembling action to that button.
Or maybe even a script that affects color/label/actionstring - this would be a total solution.
BTW what is missing most in the new imu viewer is the lack of graphical pitch display,
and crazy scales on all axes. Plus the fact that the parser that cannot live with regular ArduStation data
from the same 'racing team'.
But I am so very impressed at how Chris can make Flexipilot talk to so many different GCSes. It is the chameleon of autopilots.