And you have to add a new variable for the turn coordinator (in that same code):
var turn = $.flightIndicator('#turn_coordinator', 'turn_coordinator',options);
And you have to add a new HTML container for the turn coordinator (in the first two lines of the "Flight" template code):
<span id="turn_coordinator"></span>
You have to remember to put the <span> element before the end </div> tag.
And finally, if you want to drive the turn coordinator, you need to add a topic named "turn" (if using the code I pasted above exactly) to the message containing the turn data---e.g., using a Set node configured as below (or using the Injector nodes directly as is done to test all other gauges):
Now as you have done it and written it down, you'll most probably remember it for ever, cos that is most effective way to learn.
I'm happy for both of you, well done.
@gerry, if you get far with the flight gauges and you get them working with a quadcopter (or any other vehicle made with Arduino/Raspberry Pi/etc), please share! I'd be very curious to see, because I'm heading down that path myself.
my ultimate goal is
I have a 7 inch lcd that fits onto a pi and I'm going to get the mpu9250 working with it all and mount it in my jeep for trail riding to see heading , pitch , etc.
If you don't need to explore the libraries every day to figure out how and what to do with them, of course the best practice is to use .min versions of files. In this case here, the files are pretty small and you use them locally most probably so doesn't make much difference but best practices are always good to follow. You should change that other template to load .min files. And you can delete the others if you want to.
Thanks! So the .min files are the ones to keep if I only keep some. Good to know!
How did you get your dynamic gauges to move so smoothly? I think I saw somewhere that you needed to add extra code for that, but maybe I was imagining things, because I can't find that page anymore. My gauges are working great, but they aren't very smooth yet, so I'm wondering if I can improve that...
#Post 11. But not every gauge in every condition can be smoothed so adding them must be done with care. Add one by one and see the result and adjust the times and be prepared to misbehavior
Ahhh. OK, will keep an eye out for unexpected behavior, then. I imagine the problem would be the interpolation between values? What type of interpolation would it be, linear, maybe?
That's why the original does not provide any animations. The gauges are targeted to react to real situation which means fast update so gauges are as smooth as you fly