Hi all,
lately I’ve been working on a version of my script for the Horus X10/X12 radio series
It’s implemented as a one time script, so when it runs all other scripts are stopped.
I choose this over a widget implementation because the latter does not allow for user interaction (by design).
My script had menus and a couple more features requiring user input such as min/max values, voltage source cycling and single to dual battery toggle so I needed a way for the user to interact with the script.
It’s an early version, performance of the HUD it’s not optimal, mostly because of the very large display, I’ll try to improve it later.
The event engine is the same as my other script so all features of the X9D version are present.
I really have to thank @Touchthebitum for beta testing out my scripts, I do not own an Horus radio so it’s only thank to him that I could verify my code on a real radio, thank you Franck!
If anybody is interested in beta testing it out please PM me, all I want in turn is some feedback
I would be interested in beta testing for you. I have a Horus X10S and run a pixhawk. I have used FlightDeck and a few others as well. I used to be a manager for software development group so I believe that my feedback would be valuable.
I just wanted to say thank you for the awesome work you did with this script. I did not try it at first, because the ardupilot wiki does not make it really obvious that anything else than a premade cable for 20$ can be used. Today I had the time to do a little bit more research. I found an unused Frsky FUL-1 adapter as mentioned in the ardupilot wiki somewhere. The wiki says you will also need a FrSky SPC cable for a complete DIY solution.
The SPC cable is nothing more than a diode on a PCB, so I thought, why not just solder a diode to the TX/RX pins of the FUL-1 and it works! Now I am going to order some MAX232 converter PCBs and diodes and try the same with them, so I can use your script with all of my vehicles.
I received a request from Craft&Theory to change the way the altitude and vertical speed hud boxes looked in the Taranis versions of the script, the fix was kind of trivial and I must say I like it better the way it is now.
The look of the Taranis versions is now more in line with the look of the Horus version,
[N] I added gps coordinates because when the script is running it’s not possible to switch to another telemetry page
[Q]: is the actual time next to the label flighttime misleading? Since you cannot exit from the script I imagined that it would be useful to display it
Consider using “TimeFlying” or “TimeInAir.” The global time should be elsewhere - maybe at the top center so that it’s not confused.
This is my opinion, but I would like to see a larger HUD - it’s the “primary” instrument referenced for errors. If C&T thinks you’re infringing on their rights, use a “russian” HUD where the lines move instead of the horizon. I also use the “hash” marks on the top of most HUD’s to get a fairly accurate measurement of bank angle - so if it’s easy to add them, they make it look nice.
I also don’t see a need for the frame type to be displayed - It shouldn’t be changing in flight, right?
Excellent work though! I’m excited to begin trying this out soon!
