Hooray wrote in Thu 4:17 pm:Speaking in general, we do have lots of aircraft with varying quality AP implementations, and some do not even provide a custom GUI dialog or even disable the built-in dialog completely. Another user mentioned it just the other day in a closely related context (running FlightGear nasal scripts from another application using telnet): In addition to that, some aircraft developers have made their autopilots less controllable from the property tree than others. In other words it can differ a lot from aircraft to aircraft, which probably would make for a need to be able to configure an MCP to fit individual aircraft. Most of the things in FlightGear is entirely up to the individual aircraft developer. Are these buttons also exposed in the property tree? Is it possible to control them through Telnet by setting them as properties? For instance, I would want to control the push button that activate the autopilot, change the switch for the banking angle, press the button for APP, LOC, HOLD, etc. Now I would want to be able to control the autopilot push-buttons. It was relatively easy to find and change the properties for heading, speed. I am in reality more a hardware guy (although I like a lot to do C/C++/Android programming whenever is needed). Saul wrote in Wed 9:54 pm:I need some help with the Flightgear internals. I need some help with the Flightgear internals. For now, if someone is interested you can take a look to the raspberry code (Qt C++) at: I plan to release schematics, bill of materials, and PCB gerber files whenever they are available (Everything GPL, so you can use it as you want). You can have a look of how the breadboard prototype works here: There are 3 encoders attached to the heading, air speed, and vertical speed. So far, I have the proof of concept for the B777-300 autopilot working using Telnet (What a good documention for usage of Telnet you have guys!!). With the situation like that, I could as well design my own hardware panels. I started to think about this when I saw that Saitek started to offer panels for Micro$oft FSX and it might take ages before these products can any support for Flightgear. The original idea of my spare-time project is to create an open-source/open-hardware, simple reconfigurable platform that use very cheap components such as the Rapsberry Pi (USD ~ 35) and that can be used as "lego" blocks in order to build cockpit instruments such as the autopilot, radio comm., etc. I bought a Raspberry Pi one month ago and I have been developing my own home-made hardware for the B777-300 autopilot panel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |