Re: Hardware cockpit instruments with round displays.
David Hudach <[email protected]> Sun, 26 Jul 2026 11:10:27 -0400
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <CAJeoFa+yS9aPvFWcB902q2t0iC30uuwosihPVrNmP3QdLT=CqA@mail.gmail.com> |
--===============1363580205619064370== Content-Type: multipart/alternative; boundary="0000000000002e31b90657850271" --0000000000002e31b90657850271 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable At some point I would like to implement "real instruments" using either small stepper motors on Raspberry Pi. But until then I'm almost at the finish line building an instrument animation program from scratch in C and SDL2 that would essentially be similar to fgpanel. The problem with fgpanel is that from what I've seen and what I've tried, building it on Pi is a challenge. So I've done all of my development on Pi. I'm able to run FG on my laptop and send the output to Pi over WiFi and things so far work ok. I'm running about 13 instruments sending 42 properties across to the C program. Naturally Pi isn't going to be super robust, but it was an easy way to test the ability. As for proper instrument animation, I've kind of had to reverse engineer some of the animation/condition/transformation settings in the instrument xml files. But so far so good. Eventually I'll connect the PC to the Pi via ethernet. On Sun, Jul 26, 2026 at 10:38=E2=80=AFAM Patrick Callahan <pat.callahan1@gm= ail.com> wrote: > Has anyone done any cockpit instruments using Flightgear source materials > driving 2.8" round TFT displays from raspberry pi zeros? I'm thinking i= n > terms of a FGFS instance with no scenery, no airport, just a single > instrument, driven not from the FDM, but from input fed from the main FGF= S > instance over USB or UDP, perhaps running independently on a Raspberry Pi > Zero. Outputs for adjusting knobs back to the main fgfs via the same > channel. > > -Pat > > > https://www.aliexpress.us/item/3256805001903002.html?spm=3Da2g0o.cart.0.0= .491f38daKYclES&mp=3D1&pdp_npi=3D6%40dis%21USD%21USD+31.27%21USD+31.27%21%2= 1USD+31.27%21%21%21%402103138417850754067242788e0eb6%2112000032031307056%21= ct%21US%21798636471%21%211%210%21&gatewayAdapt=3Dglo2usa > > Heading Instrument example > 1 raspberry pi zero > 1 2.8" display with hdmi board > 2 magnetic rotary encoders for Heading Bug and Card Adjust > > Is there a simpler way to drive the display than to have a full instance > of flightgear running on the Pi? > _______________________________________________ > Flightgear-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > --0000000000002e31b90657850271 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">At = some point I would like to implement "real instruments" using eit= her small stepper motors on Raspberry Pi. But until then I'm almost at = the finish line building an instrument animation program from scratch in C = and SDL2 that would essentially be similar to fgpanel. The problem with fgp= anel is that from what I've seen and what I've tried, building it o= n Pi is a challenge. So I've done all of my development on Pi. I'm = able to run FG on my laptop and send the output to Pi over WiFi and things = so far work ok. I'm running about 13 instruments sending 42 properties = across to the C program. Naturally Pi isn't going to be super robust, b= ut it was an easy way to test the ability. As for proper instrument animati= on, I've kind of had to reverse engineer some of the animation/conditio= n/transformation settings in the instrument xml files. But so far so good. = Eventually I'll connect the PC to the Pi via ethernet.</div></div><br><= div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"g= mail_attr">On Sun, Jul 26, 2026 at 10:38=E2=80=AFAM Patrick Callahan <<a= href=3D"mailto:[email protected]">[email protected]</a>> wr= ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px= 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D= "ltr"><div>Has anyone done any cockpit instruments using Flightgear source = materials driving=C2=A0 2.8" round TFT displays from raspberry pi zero= s?=C2=A0 I'm thinking in terms of a FGFS instance with no scenery, no a= irport, just a single instrument, driven not from the FDM, but from input f= ed from the main FGFS instance over USB or UDP, perhaps running independent= ly on a Raspberry Pi Zero.=C2=A0 Outputs for adjusting knobs back to the ma= in fgfs via the same channel.</div><div><br></div><div>-Pat</div><div><br><= /div><a href=3D"https://www.aliexpress.us/item/3256805001903002.html?spm=3D= a2g0o.cart.0.0.491f38daKYclES&mp=3D1&pdp_npi=3D6%40dis%21USD%21USD+= 31.27%21USD+31.27%21%21USD+31.27%21%21%21%402103138417850754067242788e0eb6%= 2112000032031307056%21ct%21US%21798636471%21%211%210%21&gatewayAdapt=3D= glo2usa" target=3D"_blank">https://www.aliexpress.us/item/3256805001903002.= html?spm=3Da2g0o.cart.0.0.491f38daKYclES&mp=3D1&pdp_npi=3D6%40dis%2= 1USD%21USD+31.27%21USD+31.27%21%21USD+31.27%21%21%21%4021031384178507540672= 42788e0eb6%2112000032031307056%21ct%21US%21798636471%21%211%210%21&gate= wayAdapt=3Dglo2usa</a><div><br></div><div>Heading Instrument example=C2=A0<= /div><div>1 raspberry pi zero</div><div>1 2.8" display with hdmi board= </div><div>2 magnetic rotary encoders for Heading Bug and Card Adjust</div>= <div><br></div><div>Is there a simpler way to drive the display than to hav= e a full instance of flightgear running on the Pi?</div></div> _______________________________________________<br> Flightgear-devel mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/flightgear-devel" r= el=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/lis= tinfo/flightgear-devel</a><br> </blockquote></div> --0000000000002e31b90657850271-- --===============1363580205619064370== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1363580205619064370== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel --===============1363580205619064370==--