FlightGear wiki - User contributions [en]

Cessna 150

2021-05-22T15:49:20Z

Puffergas: /* Startup */ Add some items to the checklist.

{{WIP|The C150 is now (20160504) under maintenance by HJ}}

{{:{{PAGENAME}}/info}}
The '''Cessna 150''' is a two-seat tricycle gear general aviation [[aircraft]], that was designed for flight training, touring and personal use.

The Cessna 150 is the third most produced civilian plane ever, with 23,839 aircraft produced. The Cessna 150 was offered for sale in the 150 basic model, Commuter, Commuter II, Patroller and the aerobatic Aerobat models.

== Normal Operating Procedures ==

=== Airspeeds for normal flight operation ===

{| class="wikitable"
! !! Vias
|-
| '''NORMAL / OPTIMUM''' || kts|| MPH
|-
| Best angle of climb '''V'''X || 56 || 64
|-
| Best rate of climb '''V'''Y || 68 || 78
|-
| Normal rotation speed '''V'''R || 50 || 58
|-
| Normal climb speed || 65-75 || 75-85
|-
| Normal landing (no flaps) || 60-70 || 70-80
|-
| Normal landing (full flaps) || 50-60 || 57-69
|-
| Powered landing (no flaps) || 65 || 75
|-
| Powered landing (full flaps) || 55 || 63
|-
| Maximum performance approach || 52 || 60
|-
| Optimum glide speed || 60 || 69
|}

{| class="wikitable"
! !! Vias
|-
| '''LIMITS''' || kts|| MPH
|-
| Never Exceed Speed '''V'''NE Do not exceed this speed in any operation || 141 || 162
|-
| Max structural speed '''V'''NO Do no exceed this speed except in smooth air and then only with caution || 107 || 123
|-
| Maneuvering speed '''V'''A || ||
|-
| 1,600 pounds || 67 || 111
|-
| 1,450 pounds || 93 || 107
|-
| 1,300 pounds || 88 || 101
|-
| Maximum flap extended speed '''V'''FE || 85 || 97
|-
| Stall speed VS || 47 || 54
|-
| Stall speed (10° Flaps) '''V'''S1 || 45 || 52
|-
| Stall speed in landing configuration '''V'''S0 || 42 || 49
|-
| Optimum glide speed || 60 || 69
|}

=== Checklist ===

==== Startup ====
# Seat - Lock
# Avionics -Off
# Carburetor Heat - Cold
# Mixture - Full Rich
# Primer - As Required
# Brakes
# Master - On
# Beacon - On
# Mags - Both
# Throttle - Open 1/4 inch
# Propeller Area - Clear
# Starter - On
# Oil Pressure
# Lights - As Required
# Mixture - As Required

==== Takeoff ====
# Wing flaps - Up
# Carburetor Heat - Cold
# Throttle - Full "Open"
# Elevator Control - Lift nose wheel at 50 mph
# Climb Speed - 72 MPH until all obstacles are cleared

==== Climb ====
# Air Speed - 75 to 80 MPH
# Power - Full throttle
# Mixture - Rich (unless engine is rough)

==== Cruise ====
# Power - 2000 to 2750 RPM
# Elevator Trim - Adjust
# Mixture - Lean to maximum RPM

==== Approach ====
# Mixture - Rich
# Carburetor Heat - Apply full heat before closing throttle
# Airspeed - 65 to 75 MPH
# Wing Flaps - As desired below 100 MPH
# Airspeed - 60 to 70 MPH with flaps extended

==== Landing ====
# Touch down - Main wheels first
# Landing Roll - Lower nose wheel gently
# Braking - Minimum required

=== Keyboard reminder ===
{| class="keytable"
!Key
!Function
|-
|{{Key press|d}}/{{Key press|Shift|d}}
|Door select
|-
|{{Key press|Ctrl|d}}
|Open/close selected door
|-
|{{Key press|Shift|O}}
|Operate priming pump
|-
|{{Key press|<nowiki>=</nowiki>}}
|Open configuration dialog
|}

== Gallery ==

<gallery mode="packed">
C150-064.jpg|Taking off at Winterland (CCC2)
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Cessna_150 Wikipedia]
* [http://www.cessna150-152club.com/ Cessna 150-152 Club]

{{Cessna}}

[[Category:Red Griffin ATC compatible aircraft]]

APionics

2021-04-23T17:25:25Z

Puffergas: /* Instrument Stepper Motors */

{{FlightGearRaspberryPi4 Navigation}}
{{lowercase title}}
'''aPionics''' uses the Raspberry Pi to drive external avionic instruments.
[[File:APionics.jpg|thumb|Cockpit instruments controlled by a Raspberry Pi.]]

==Instrument Needles==
Roof flashing makes a suitable material for making the instrument needles.

==Instrument Housings==
The housings are up-cycled food containers from the local deli. There are a few possible advantages to making stand alone gauges.

Possible Advantage
* Can be used on a desk.
* Later they could be installed into a panel.
* Can be using the ones made while the next instrument is being developed.
* If one instrument is lacking, it can be used while an upgrade instrument is being worked on.

==Instrument Stepper Motors ==
[[File:Size Comparison.jpg|alt=Compare size of automotive stepper motor vs the micro R/C servo |thumb|Instrument Stepper Motor vs Micro R/C Servo]]
[[File:Inside the Instrument Stepper Motor.jpg|alt=Inside of the automotive instrumentation stepper motor.|thumb|Automotive Instrumentation Stepper Motor]]
[[File:Gear-Snubber.jpg|alt=The travel limit snubber.|thumb|Travel Limiter]]
[[File:Snubber Path.jpg|alt=Inside view of the front cover. This is the path of the travel limit snubber.|thumb|Inside Front Cover]]

Automotive instrument stepper motors seem to work with the Pi-Plate Motor Controller. They cost about the same as an imported R/C micro servo or a bit less. They have a travel limit snubber, however that can be removed. Refer to the photos. This is an example of the X27 168 GM instrument cluster stepper motor.
==Fuel Gauge==
[[File:Fuel Gauge DC-3.jpg|thumb|Inside of the fuel gauge, made for the DC-3]]
The inside of the fuel gauge is shown in the photo. The needle movement is accomplished with a hobby servo. The fuel tank selector switch takes advantage of one of the Analog to Digital Converter (ADC) that the TINKERplate has. The resistor, soldered to the rotatory switch is a simple voltage divider. Every used switch position is assigned a voltage level that corresponds to a specific fuel tank.

APionics

2021-04-23T17:21:52Z

Puffergas: /* Instrument Stepper Motors */

{{FlightGearRaspberryPi4 Navigation}}
{{lowercase title}}
'''aPionics''' uses the Raspberry Pi to drive external avionic instruments.
[[File:APionics.jpg|thumb|Cockpit instruments controlled by a Raspberry Pi.]]

==Instrument Needles==
Roof flashing makes a suitable material for making the instrument needles.

==Instrument Housings==
The housings are up-cycled food containers from the local deli. There are a few possible advantages to making stand alone gauges.

Possible Advantage
* Can be used on a desk.
* Later they could be installed into a panel.
* Can be using the ones made while the next instrument is being developed.
* If one instrument is lacking, it can be used while an upgrade instrument is being worked on.

==Instrument Stepper Motors ==
[[File:Size Comparison.jpg|alt=Compare size of automotive stepper motor vs the micro R/C servo |thumb|Instrument Stepper Motor vs Micro R/C Servo]]
[[File:Inside the Instrument Stepper Motor.jpg|alt=Inside of the automotive instrumentation stepper motor.|thumb|Automotive Instrumentation Stepper Motor]]
[[File:Gear-Snubber.jpg|alt=The travel limit snubber.|thumb|Travel Limiter]]
[[File:Snubber Path.jpg|alt=Inside view of the front cover. This is the path of the travel limit snubber.|thumb|Inside Front Cover]]

Automotive instrument stepper motors seem to work with the Pi-Plate Motor Controller. They cost about the same as an imported R/C micro servo or a bit less. They have a travel limit snubber, however that can be removed. Refer to the photos.
==Fuel Gauge==
[[File:Fuel Gauge DC-3.jpg|thumb|Inside of the fuel gauge, made for the DC-3]]
The inside of the fuel gauge is shown in the photo. The needle movement is accomplished with a hobby servo. The fuel tank selector switch takes advantage of one of the Analog to Digital Converter (ADC) that the TINKERplate has. The resistor, soldered to the rotatory switch is a simple voltage divider. Every used switch position is assigned a voltage level that corresponds to a specific fuel tank.

APionics

2021-04-23T17:17:25Z

Puffergas: /* Fuel Gauge */

{{FlightGearRaspberryPi4 Navigation}}
{{lowercase title}}
'''aPionics''' uses the Raspberry Pi to drive external avionic instruments.
[[File:APionics.jpg|thumb|Cockpit instruments controlled by a Raspberry Pi.]]

==Instrument Needles==
Roof flashing makes a suitable material for making the instrument needles.

==Instrument Housings==
The housings are up-cycled food containers from the local deli. There are a few possible advantages to making stand alone gauges.

Possible Advantage
* Can be used on a desk.
* Later they could be installed into a panel.
* Can be using the ones made while the next instrument is being developed.
* If one instrument is lacking, it can be used while an upgrade instrument is being worked on.

==Instrument Stepper Motors ==
[[File:Size Comparison.jpg|alt=Compare size of automotive stepper motor vs the micro R/C servo |thumb|Instrument Stepper Motor vs Micro R/C Servo]]
[[File:Inside the Instrument Stepper Motor.jpg|alt=Inside of the automotive instrumentation stepper motor.|thumb|Automotive Instrumentation Stepper Motor]]
[[File:Gear-Snubber.jpg|alt=The travel limit snubber.|thumb|Travel Limiter]]
[[File:Snubber Path.jpg|alt=Inside view of the front cover. This is the path of the travel limit snubber.|thumb|Inside Front Cover]]

==Fuel Gauge==
[[File:Fuel Gauge DC-3.jpg|thumb|Inside of the fuel gauge, made for the DC-3]]
The inside of the fuel gauge is shown in the photo. The needle movement is accomplished with a hobby servo. The fuel tank selector switch takes advantage of one of the Analog to Digital Converter (ADC) that the TINKERplate has. The resistor, soldered to the rotatory switch is a simple voltage divider. Every used switch position is assigned a voltage level that corresponds to a specific fuel tank.

APionics

2021-04-23T16:57:11Z

Puffergas: /* Instrument Housings */

{{FlightGearRaspberryPi4 Navigation}}
{{lowercase title}}
'''aPionics''' uses the Raspberry Pi to drive external avionic instruments.
[[File:APionics.jpg|thumb|Cockpit instruments controlled by a Raspberry Pi.]]

==Instrument Needles==
Roof flashing makes a suitable material for making the instrument needles.

==Instrument Housings==
The housings are up-cycled food containers from the local deli. There are a few possible advantages to making stand alone gauges.

Possible Advantage
* Can be used on a desk.
* Later they could be installed into a panel.
* Can be using the ones made while the next instrument is being developed.
* If one instrument is lacking, it can be used while an upgrade instrument is being worked on.

==Instrument Stepper Motors ==
[[File:Size Comparison.jpg|alt=Compare size of automotive stepper motor vs the micro R/C servo |thumb|Instrument Stepper Motor vs Micro R/C Servo]]
[[File:Inside the Instrument Stepper Motor.jpg|alt=Inside of the automotive instrumentation stepper motor.|thumb|Automotive Instrumentation Stepper Motor]]
[[File:Gear-Snubber.jpg|alt=The travel limit snubber.|thumb|Travel Limiter]]
[[File:Snubber Path.jpg|alt=Inside view of the front cover. This is the path of the travel limit snubber.|thumb|Inside Front Cover]]

==Fuel Gauge==
[[File:Fuel Gauge DC-3.jpg|thumb|150px|Inside of the fuel gauge, made for the DC-3]]
The inside of the fuel gauge is shown in the photo. The needle movement is accomplished with a hobby servo. The fuel tank selector switch takes advantage of one of the Analog to Digital Converter (ADC) that the TINKERplate has. The resistor, soldered to the rotatory switch is a simple voltage divider. Every used switch position is assigned a voltage level that corresponds to a specific fuel tank.

File:Snubber Path.jpg

2021-04-23T14:58:18Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Inside of the front cover, of the automotive instrument stepper motor, shows the snubber travel path.}}
|date=2021-04-22 15:42:52
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Cockpit building]]
[[Category:Raspberry Pi]]

File:Inside the Instrument Stepper Motor.jpg

2021-04-23T14:58:18Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Inside view of the automotive instrument stepper motor.}}
|date=2021-04-22 15:36:41
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Cockpit building]]
[[Category:Raspberry Pi]]

File:Gear-Snubber.jpg

2021-04-23T14:58:18Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=The travel limit snubber used for automotive instrument stepper motors.}}
|date=2021-04-22 15:39:05
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Cockpit building]]
[[Category:Raspberry Pi]]

File:Size Comparison.jpg

2021-04-23T14:58:18Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Size of the automotive instrument stepper motor, compared to a micro R/C servo.}}
|date=2021-04-23 10:19:01
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Cockpit building]]
[[Category:Raspberry Pi]]

Joysticks and Raspberry Pi

2021-03-22T23:18:43Z

Puffergas: /* Honeycomb Aeronautical Alpha Flight Controls - Yoke */

{{FlightGearRaspberryPi4 Navigation}}

== Joysticks ==
[[File:Jstest-gtk Joystick Calibration.jpg|thumb|150px|Joystick calibration using jstest-gtk dialog box.]]

You will find that controlling your [[aircraft]], with the official Raspberry Pi keyboard and mouse, too be rather difficult. A [[Input device|joystick]] will solve this problem. The Logitech Extreme 3D PRO is plug and play, for the most part, with [[FlightGear]]. Most modern joysticks should also work. There is a dialog box to assign common joystick controls, in FlightGear. Controls are also properties, however that is for later. This joystick dialog box is found in the top menu bar under 'Files'. Next you will find 'Joystick Configuration' to click on and that will bring up the desired dialog box.

If the joystick’s travel is not being used efficiently or the neutral dead band is not right, the joystick can be calibrated. Install jstest-gtk through the Raspbian software installer or use the terminal and apt-get install command.

<syntaxhighlight lang="bash">
sudo apt-get install jstest-gtk
</syntaxhighlight>

After running jstest-gtk click on your joystick within the jstest-gtk window. Next click on the 'Calibration' button. The calibration can be performed within this dialog box. Consider making note of these values before performing the calibration. Do not forget to cycle the hat switch that is on top of the stick. This is because this switch is considered as a proportional input just like the stick axis. In order to save these new settings, after a reboot or new power up, do not close jstest-gtk at this moment. First open a terminal and enter the below command in order to save the new calibration values. The 'device_name' of the joystick is in the first dialog box of jstest-gtk. It will be something like js0, js1 etc.

<syntaxhighlight lang="bash">
sudo jscal-store /dev/input/js0
</syntaxhighlight>

Some or most Linux distributions will need more work to store these new calibration values, in the way of RULES. However, it seems that Raspbian doesn’t require anymore work.

The above calibration may not adjust for any center dead band. Notice that the calibration values are representing binary numbers in that the maximums are in power of two’s. Except where the maximum value is 1 or -1. It is common to see these values close to 512 or 1024. Consider the values below. To find the maximum value add the RangeMin to the RangeMax. For example; 0 + 1024 = 1024. Since this scheme starts with 0, not 1, 1022 or 510 might be the maximum value. The first pair of numbers, not considering the axis number, should add up to the maximum value.

{| class="wikitable"
|-
! Axis !! CenterMin !! CenterMax !! RangeMin !! RangeMax
|-
| 0 || 511 || 511 || 0 || 1022
|-
| 1 || 511 || 511 || 0 || 1022
|-
| 2 || 127 || 127 || 0 || 254
|-
| 3 || 127 || 127 || 0 || 254
|-
| 4 || 0 || 0 || -1 || 1
|-
| 5 || 0 || 0 || -1 || 1
|}

In order to introduce a dead band consider the values below:

{| class="wikitable"
|-
! Axis !! CenterMin !! CenterMax !! RangeMin !! RangeMax
|-
| 0 || 491 || 531 || 20 || 1002
|-
| 1 || 491 || 531 || 20 || 1002
|-
| 2 || 117 || 137 || 10 || 254
|-
| 3 || 117 || 137 || 10 || 254
|-
| 4 || 0 || 0 || -1 || 1
|-
| 5 || 0 || 0 || -1 || 1
|}

Or the values in the calibration dialog box screenshot, entitled "Joystick calibration using jstest-gtk dialog box".

Axis 4 and 5 are examples of the hat switch.

=== Saitek Saitek Pro Flight Quadrant ===

[[File:Properties tree controls.jpeg|thumb|150px|Properties controls.]]
[[File:Properties tree controls throttle-coupled.jpeg|thumb|150px|Properties tree controls throttle-coupled.]]

This throttle quadrant is now produced by Logitech and works with FG and the Raspberry Pi4. If used with a single engine aircraft or a multi engine aircraft where the engines are controlled with one stick on the quadrant, this will be a plug and play setup. However, there will be a noticeable dead band in the middle of the travel. Furthermore, it is possible that all the usable stick travel is not utilized. Both of these issues can be addressed by calibrating the quadrant as in the joystick example above. Below is the calibration data before calibration and below that is the data after calibration. Notice that the center dead band is removed.

{| class="wikitable"
|-
! Axis !! CenterMin !! CenterMax !! RangeMin !! RangeMax
|-
| 0 || 112 || 124 || 15 || 239
|-
| 1 || 112 || 124 || 15 || 239
|-
| 2 || 112 || 124 || 15 || 239
|}

After calibration below:
{| class="wikitable"
|-
! Axis !! CenterMin !! CenterMax !! RangeMin !! RangeMax
|-
| 0 || 127 || 127 || 0 || 255
|-
| 1 || 127 || 127 || 0 || 255
|-
| 2 || 127 || 127 || 0 || 255
|}

If this quadrant is used with a multi engine aircraft and each engine throttle is controlled by a separate quadrant lever, the levers will only use half of its travel. In order to resolve this, the joystick configuration file will need a small edit. This file is located in homepi/.fgfs/Input, assuming your user name is ‘pi’. Notice that ‘.fgfs’ is a hidden folder in your Home folder. Only edit the joystick configuration files that are in your Home folder. Do not edit the files that are native to FlightGear. In this example we will be editing ‘Saitek-Saitek-Pro-Flight-Quadrant.xml’.

Let us assume that this configuration is for the twin engine DC-3 Dakota and axis-0 will be assigned to ALL engine mixture levers, axis-1 will be assigned to ‘Throttle Engine 0’ and axis-2 is assigned to ‘Throttle Engine 1’. Note that within this .XML configuration file that <axis> is another way to express <axis n=’0’>. The axis-0 doesn’t need the n=’0’. Find <axis n=’1’> and change the ‘offset’ from 0 to -1 also change ‘factor’ from 1 to -0.5. Do the same for <axis n='2'>.

{| class="wikitable"
|-
| Note || For FG version 2019.1.1, axis n="1" and n="2" needed to be change to:
<syntaxhighlight lang="xml">
<factor type="double">.5</factor>
<offset type="double">1</offset>
</syntaxhighlight>
|}

The below worked on FG version 2018.3.2.
<syntaxhighlight lang="xml">
<axis>
<desc type="string">Mixture All Engines</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/mixture-all</property>
<factor type="double">1</factor>
<offset type="double">0</offset>
</binding>
</axis>
<axis n="1">
<desc type="string">Throttle Engine 0</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine[0]/throttle</property>
<offset type="double">-1.0</offset>
<factor type="double">-0.5</factor>
</binding>
</axis>
<axis n="2">
<desc type="string">Throttle Engine 1</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine[1]/throttle</property>
<offset type="double">-1.0</offset>
<factor type="double">-0.5</factor>
</binding>
</axis>
</syntaxhighlight>

Now the Quadrant will move the throttle levers as they should. The levers and props should follow the levers on the Quadrant. However, you might notice that the throttles do not seem to feel like they are independent to each other when taxing or in the air. There is another adjustment to look into and this is the property throttles-coupled='true'(bool).

In this example, the DC-3 Dakota will need a small edit. The file that needs this edit is named ‘controls.xml’ and it's location can be found at /Aircraft/Douglas-Dc3/Systems/controls.xml. The bellow command will be found near the bottom of this file.

<syntaxhighlight lang="bash">
<throttle-coupled type="bool">1</throttle-coupled>
</syntaxhighlight>

The Boolean value 1 needs to be changed to a 0, as in the below example.

<syntaxhighlight lang="bash">
<throttle-coupled type="bool">0</throttle-coupled>
</syntaxhighlight>

Of course the file needs to be saves. Depending where the file is located, permissions might need to be dealt with.

=== Thrustmaster Flight Rudder Pedals ===

There could be two adjustments needed for these rudder pedals. The toe brakes are reversed and delete the toe brake center dead band. Use the same method to delete the dead band as in the above throttle quadrant. Do not delete the dead band for the rudder unless that is what you want to do. Below is a calibration data example:
{| class="wikitable"
|-
! Axis !! CenterMin !! CenterMax !! RangeMin !! RangeMax
|-
| 0 || 511 || 511 || 0 || 1022
|-
| 1 || 511 || 511 || 0 || 1022
|-
| 2 || 448 || 574 || 63 || 959
|}

Reversing the toe brake direction in FlightGear, using it's joystick dialog box, does't work. The easiest method is to reverse them using jstest-gtk and check the invert box for axes 0 and axes 1.

Depending on the version of FlightGear, there could be a bug where one of the toe brakes do not show up in the FlightGear joystick dialog box. If so this is easy to edit in the configuration file. It might also be beneficial to delete controls that are not part of this rudder pedal so not to produce any conflicts. See below:

<syntaxhighlight lang="xml">

<name type="string">Thrustmaster T-Rudder</name>
<axis>
<desc type="string">Brake Right</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/gear/brake-right</property>
<factor type="double">0.5</factor>
<offset type="double">1</offset>
</binding>
</axis>
<axis n="1">
<desc type="string">Brake Left</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/gear/brake-left</property>
<factor type="double">0.5</factor>
<offset type="double">1</offset>
</binding>
</axis>
<axis n="2">
<desc type="string">Rudder</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/flight/rudder</property>
<factor type="double">1</factor>
<offset type="double">0</offset>
</binding>
</axis>
</syntaxhighlight>

A much more in-depth study of joystick programming can be found at the below link:

[[Writing_Joystick_Code:_Part_1|Writing Joystick Code]]

===HID===
Below is an example of how to build FlightGear, using download_and_compile.sh, with standard joystick disabled and HID enabled:
<syntaxhighlight>
FG_CMAKEARGS='-DENABLE_PLIB_JOYSTICK=OFF -DENABLE_HID_INPUT=ON' ../fgmeta/download_and_compile.sh -j3 FGFS
</syntaxhighlight>

Below is an example of FlightGear (as reported in the Terminal) not being able to read a HID device because of a lack of permissions:

<syntaxhighlight>
27.14 [WARN]:input Can't get abs-axes for /dev/input/js0
27.14 [WARN]:input Can't get keys for /dev/input/js0
27.14 [WARN]:input Can't get switches for /dev/input/js0
27.15 [INFO]:input HID event input starting up
27.16 [WARN]:input Honeycomb Aeronautical Alpha Flight Controls_0: HID: Failed to open:/dev/hidraw0
27.16 [WARN]:input note on Linux you may need to adjust permissions of the device using UDev rules.
</syntaxhighlight>

Pass the below command to FlightGear in order to enable the above logging.
<syntaxhighlight lang="bash">--log-level=info</syntaxhighlight>

User rules are located at <code>/etc/udev/rules.d</code> Within the folder rules.d, a file can be created with a new rule. We will name it <code>50-hid.rules</code>. Root will be needed in order to create this file, use your favorite method. This new file <code>50-hid.rules</code> will contain the rule below:
<syntaxhighlight lang="bash">
KERNEL=="hidraw*", GROUP="input", MODE="0660"
</syntaxhighlight>

If the above rule is successful, FlightGear terminal will report something similar to the below:
<syntaxhighlight>
> 155.07 [INFO]:input bytes: 7F 7F 00 00 A0 AA 6A 00
> 155.07 [INFO]:input Honeycomb Aeronautical Alpha Flight Controls
> FGHIDDeivce received input report:0, len=8
</syntaxhighlight>

[[Category:Raspberry Pi]]

Template:Git

2021-03-06T03:11:53Z

Puffergas:

{{sidebar
| name = Git
| title = Git
| contentstyle= text-align: left;

| content1 =
Git is a version control system, used to store all files required to build FlightGear.
* [[Development workflow]]
* [[FlightGear Git|Introduction]]
* [[Howto:Start using git]]
----
* [[Git for Laymen|Users looking for latest version]]
* [[FlightGear Git: data developers|Data developers]]
* [[FlightGear Git: core developers|Core developers]]
----
* [[FlightGear Git: gitiquette|Gitiquette]]
* [[FlightGear Git: tips|Tips and tricks]]
* [[Making a SourceForge Merge Request]]
}}<noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This is a sidebar navigation infobox to add at the top of GIT related pages.

== Usage ==
<pre>
{{Git}}
</pre>

[[Category:Navigation templates]]
[[Category:Git templates]]
}}</noinclude>

File:SourceForge Request Merge Form.png

2021-03-05T23:17:58Z

Puffergas:

The form that needs to be completed in order to make a Request Merge.

File:SourceForge Request Merge.png

2021-03-05T22:08:45Z

Puffergas:

A SourceForge request merge after your changes have been pushed.

File:SourceForge Fork Completed.png

2021-03-04T23:23:47Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=The SourceForge fork has been completed.}}
|date=2021-03-04
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Git]]

File:SourceForge Fork.png

2021-03-04T23:23:47Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Starting the forking process on SourceForge.}}
|date=2021-03-04
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Git]]

File:SSH public keys for SourceForge.png

2021-03-04T21:49:54Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Creating and adding public SSH keys to SourceForge.}}
|date=2021-03-04
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Git]]

USB Controller Boards

2021-02-14T00:55:59Z

Puffergas: /* GEEEKPI */

{{FlightGearRaspberryPi4 Navigation}}

[[File:QuadrantDC3.jpg|thumb|150px|Throttle quadrant for the DC-3. Uses a GearFalcon general purpose joystick controller board.]]

The objective of '''USB Controller Boards''' is to discuss some of the board available that will allow building flight controls.
 
== GEEEKPI ==
[[File:Geeekpi.jpg|thumb|150px|GeeekPi joystick controller board.]]

The GEEEKPI board has six (6) analog inputs. These work for aircraft control surfaces but not as well for throttles, prop pitch, mixture and etc. The reason, for this comment, is that there is a dead spot hard programmed into the analog inputs. This will be reflected into the controls that do not need dead spots, in the center of their travel. It is possible that some versions of this board do not have this issue.

The analog inputs tend to have jitters. A few item to help to reduce this is listed below:
* A bypass capacitor placed across the input to ground.
* Ground the case of the potentiometer.

== GearFalcon General Purpose Joystick Controller ==
[[File:Gearfalcon.jpg|thumb|150px|GearFalcon general purpose joystick controller.]]

The GearFalcon board has eight (8) analog inputs and thirty six (36) digital. 
 
This board uses programming to reduce/remove jitter. Of course, proper wiring and grounding the potentiometer case is good practice.

Template:FlightGearRaspberryPi4 Navigation

2021-02-09T19:34:23Z

Puffergas:

{{sidebar
| name = Raspberry Pi 4 and FlightGear Navigation
| title = Raspbery Pi
| contentstyle= text-align: left;

| heading1 = Intro
| content1 = [[Howto:Build and run FlightGear on Raspberry Pi 4]]
| heading2 = Contents
| content2 =
* [[Updating Raspberry Pi OS]]
* [[Graphic Issues Raspberry Pi 4]]
* [[Joysticks and Raspberry Pi]]
* [[Compiling FlightGear for Raspberry Pi - Scripted Compilation]]
* [[Backtrace using gdb & Download and Compile.sh]]
* [[64bit OS - Raspberry Pi]]
* [[Interfacing - Raspberry Pi]]
* [[Memory Raspberry Pi]]
* [[Cooling - Raspberry Pi]]
* [[Feature Scaling - Raspberry Pi OS]]
* [[Feature Scaling - FlightGear]]
* [[Osgviewer - Raspberry Pi]]
* [[aPionics]]
* [[PiStack]]
* [[Network Bridge]]
* [[USB Controller Boards]]

}}

<noinclude>{{-}}

[[Category:Navigation templates]]</noinclude>

USB Controller Boards

2021-02-09T19:32:44Z

Puffergas: Created page with "{{FlightGearRaspberryPi4 Navigation}} Throttle quadrant for the DC-3. Uses a GearFalcon general purpose joystick controller board. The o..."

{{FlightGearRaspberryPi4 Navigation}}

[[File:QuadrantDC3.jpg|thumb|150px|Throttle quadrant for the DC-3. Uses a GearFalcon general purpose joystick controller board.]]

The objective of '''USB Controller Boards''' is to discuss some of the board available that will allow building flight controls.
 
== GEEEKPI ==
[[File:Geeekpi.jpg|thumb|150px|GeeekPi joystick controller board.]]

The GEEEKPI board has six (6) analog inputs. These work for aircraft control surfaces but not as well for throttles, prop pitch, mixture and etc. The reason, for this comment, is that there is a dead spot hard programmed into the analog inputs. This will be reflected into the controls that do not need dead spots, in the center of their travel. It is possible that some versions of this board do not have this issue.

The analog inputs tend to have jitters. A few item to help to reduce this is listed below:
* A bypass capacitor placed across the input to ground.
* Ground the case of the potentiometer.
* The use of twisted paired wiring.

== GearFalcon General Purpose Joystick Controller ==
[[File:Gearfalcon.jpg|thumb|150px|GearFalcon general purpose joystick controller.]]

The GearFalcon board has eight (8) analog inputs and thirty six (36) digital. 
 
This board uses programming to reduce/remove jitter. Of course, proper wiring and grounding the potentiometer case is good practice.

File:QuadrantDC3.jpg

2021-02-09T03:03:23Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Throttle quadrant for the DC-3. Uses a GearFalcon general purpose joystick controller board.}}
|date=2021-02-06 14:58:40
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Cockpit building]]

File:Geeekpi.jpg

2021-02-09T03:03:23Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=GeeekPi joystick controller board.}}
|date=2021-02-07 22:02:13
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Joysticks and Yokes]]

File:Gearfalcon.jpg

2021-02-09T03:03:23Z

Puffergas: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=GearFalcon general purpose joystick controller.}}
|date=2021-01-28 10:02:16
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Joysticks and Yokes]]

Network Bridge

2021-01-23T01:12:26Z

Puffergas: /* Barrier */

{{FlightGearRaspberryPi4 Navigation}}

It is possible that there will be an increasing number of Raspberries being added to your FlightGear simulator. It is also possible that the location of said simulator only has a WiFi connection, to the home network. Furthermore, the home network might be saturated by other family menbers. It also might be possible that this cluster of devices is using Barrier, to share a common keyboard and mouse. One solution is to use a common WiFi router as a LAN/WLAN Bridge. Now, all the Raspberries can be connected to the fast switch that is part of the Bridge Router and still have a internet connection.

==LAN/WLAN Bridge==

An excellent guide on how to set up a bridge can be found at [https://www.nerd-quickies.net/2019/08/20/setup-lan-wlan-bridge-with-openwrt-luci/ Nerd Quickies].
It requires flashing the router with OpenWrite software.

===Raspberry bridging hints===

The <code>ifconfig</code> command is helpful to find information and the address of eth0.
After making changes to the Raspberry network settings, use the below commands to activate the modified settings. After making the changes, take the Ethernet down. After a bit of time, use the up command to restart the Ethernet. This is when your changes go into effect.
<syntaxhighlight>
sudo ifconfig eth0 up #Ethernet
sudo ifconfig eth0 down #Ethernet
</syntaxhighlight>

[[File:Raspberry Bridge Router setting.png|thumb|150px|Location of the DHCP check box and Raspberry IP address.]]
The screenshot of the Network Preferences dialog box, shows where the DHCP check box is and the Raspberry address. Right click on the network icon, upper right of the Desktop, next to the speaker icon. Click on Wireless & Wired Network Settings, in order to bring up this dialog box.

==Barrier==
Barrier allows sharing a common keyboard and mouse between many computers and works with different operating systems. It also allows sharing the clip board. Barrier is in the Raspberry software repository. In order to have a Raspberry boot with Barrier running edit the following file. At the end of the file <code>/home/pi/.profile</code>, place the command <code>barrier &</code>. This will only work if the Raspberry is configured auto login, which is it's default setting. Barrier is not a component of the network bridge, however Barrier's performance will benefit from a network bridge.

APionics

2021-01-23T01:07:26Z

Puffergas:

File:Fuel Gauge DC-3.jpg

2021-01-23T00:42:54Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Inside of the fuel gauge, made for the DC-3}}
|date=2021-01-04 09:07:56
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]

Network Bridge

2021-01-20T00:45:22Z

Puffergas: /* Raspberry bridging hints */

Network Bridge

2021-01-20T00:42:20Z

Puffergas: /* Raspberry bridging hints */

{{FlightGearRaspberryPi4 Navigation}}

It is possible that there will be an increasing number of Raspberries being added to your FlightGear simulator. It is also possible that the location of said simulator only has a WiFi connection, to the home network. Furthermore, the home network might be saturated by other family menbers. It also might be possible that this cluster of devices is using Barrier, to share a common keyboard and mouse. One solution is to use a common WiFi router as a LAN/WLAN Bridge. Now, all the Raspberries can be connected to the fast switch that is part of the Bridge Router and still have a internet connection.

==LAN/WLAN Bridge==

An excellent guide on how to set up a bridge can be found at [https://www.nerd-quickies.net/2019/08/20/setup-lan-wlan-bridge-with-openwrt-luci/ Nerd Quickies].
It requires flashing the router with OpenWrite software.

===Raspberry bridging hints===

The <code>ifconfig</code> command is helpful to find information and the address of eth0.
After making changes to the Raspberry network settings, use the below commands to activate the modified settings. After making the changes, take the Ethernet down. After a bit of time, use the up command to restart the Ethernet. This is when your changes go into effect.
<syntaxhighlight>
sudo ifconfig eth0 up #Ethernet
sudo ifconfig eth0 down #Ethernet
</syntaxhighlight>

[[File:Raspberry Bridge Router setting.png|thumb|150px|Location of the DHCP check box and Raspberry IP address.]]
The screenshot of the Network Preferences dialog box, shows where the DHCP check box is and the Raspberry address. Right click on the network icon, upper right of the Desktop, next to the speaker icon. Click on Wireless & Wired Network Settings.

==Barrier==
Barrier allows sharing a common keyboard and mouse between many computers and works with different operating systems. It also allows sharing the clip board. Barrier is in the Raspberry software repository. In order to have a Raspberry boot with Barrier running edit the following file. At the end of the file <code>/home/pi/.profile</code>, place the command <code>barrier &</code>. This will only work if the Raspberry is configured auto login, which is it's default setting.

Network Bridge

2021-01-20T00:39:34Z

Puffergas: /* Raspberry bridging hints */

{{FlightGearRaspberryPi4 Navigation}}

It is possible that there will be an increasing number of Raspberries being added to your FlightGear simulator. It is also possible that the location of said simulator only has a WiFi connection, to the home network. Furthermore, the home network might be saturated by other family menbers. It also might be possible that this cluster of devices is using Barrier, to share a common keyboard and mouse. One solution is to use a common WiFi router as a LAN/WLAN Bridge. Now, all the Raspberries can be connected to the fast switch that is part of the Bridge Router and still have a internet connection.

==LAN/WLAN Bridge==

An excellent guide on how to set up a bridge can be found at [https://www.nerd-quickies.net/2019/08/20/setup-lan-wlan-bridge-with-openwrt-luci/ Nerd Quickies].
It requires flashing the router with OpenWrite software.

===Raspberry bridging hints===

The <code>ifconfig</code> command is helpful for find information and the address of eth0.
After making changes to the Raspberry network settings, use the below commands to activate the modified settings. After making the changes, take the Ethernet down. After a bit of time, use the up command to restart the Ethernet. This is when your changes go into effect.
<syntaxhighlight>
sudo ifconfig eth0 up #Ethernet
sudo ifconfig eth0 down #Ethernet
</syntaxhighlight>

[[File:Raspberry Bridge Router setting.png|thumb|150px|Location of the DHCP check box and Raspberry IP address.]]
The screenshot of the Network Preferences dialog box, shows where the DHCP check box is and the Raspberry address. Right click on the network icon, upper right of the Desktop, next to the speaker icon. Click on Wireless & Wired Network Settings.

==Barrier==
Barrier allows sharing a common keyboard and mouse between many computers and works with different operating systems. It also allows sharing the clip board. Barrier is in the Raspberry software repository. In order to have a Raspberry boot with Barrier running edit the following file. At the end of the file <code>/home/pi/.profile</code>, place the command <code>barrier &</code>. This will only work if the Raspberry is configured auto login, which is it's default setting.

File:Raspberry Bridge Router setting.png

2021-01-20T00:15:16Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Location of the DHCP check box and Raspberry IP address.}}
|date=2021-01-19
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]

Network Bridge

2021-01-20T00:03:22Z

Puffergas: /* Raspberry bridging hints */

Network Bridge

2021-01-20T00:00:09Z

Puffergas: /* LAN/WLAN Bridge */

Network Bridge

2021-01-19T23:58:06Z

Puffergas:

Network Bridge

2021-01-19T23:56:53Z

Puffergas:

Network Bridge

2021-01-19T23:55:41Z

Puffergas:

Network Bridge

2021-01-19T22:16:43Z

Puffergas:

{{FlightGearRaspberryPi4 Navigation}}

It is possible that there will be an increasing number of Raspberries being added to the FlightGear simulator. It is also possible that the location of said simulator only has a WiFi connection, to the home network. Furthermore, the home network might be saturated by other family menbers. It also might be possible that this cluster of devices is using Barrier, to share a common keyboard and mouse. One solution is to use a common WiFi router as a LAN/WLAN Bridge. Now, all the Raspberries can be connected to switch that is part of the Bridge Router and still have a internet connection.

==LAN/WLAN Bridge==

An excellent guide on how to set up a bridge can be found at [https://www.nerd-quickies.net/2019/08/20/setup-lan-wlan-bridge-with-openwrt-luci/ Nerd Quickies].

===Raspberry bridging hints===

The <code>ifconfig</code> command is helpful to find information and addresses of eth0.
After making changes to the Raspberry network setting, use the below commands to activate the modified settings. After making the changes, take the Ethernet down. After a bit of time, use the up command to restart the Ethernet. That is when your changes go into effect.
<syntaxhighlight>
sudo ifconfig eth0 up #Ethernet
sudo ifconfig eth0 down #Ethernet
</syntaxhighlight>

Template:FlightGearRaspberryPi4 Navigation

2021-01-19T16:19:07Z

Puffergas:

{{sidebar
| name = Raspberry Pi 4 and FlightGear Navigation
| title = Raspbery Pi
| contentstyle= text-align: left;

| heading1 = Intro
| content1 = [[Howto:Build and run FlightGear on Raspberry Pi 4]]
| heading2 = Contents
| content2 =
* [[Updating Raspberry Pi OS]]
* [[Graphic Issues Raspberry Pi 4]]
* [[Joysticks and Raspberry Pi]]
* [[Compiling FlightGear for Raspberry Pi - Scripted Compilation]]
* [[Backtrace using gdb & Download and Compile.sh]]
* [[64bit OS - Raspberry Pi]]
* [[Interfacing - Raspberry Pi]]
* [[Memory Raspberry Pi]]
* [[Cooling - Raspberry Pi]]
* [[Feature Scaling - Raspberry Pi OS]]
* [[Feature Scaling - FlightGear]]
* [[Osgviewer - Raspberry Pi]]
* [[aPionics]]
* [[PiStack]]
* [[Network Bridge]]

}}

<noinclude>{{-}}

[[Category:Navigation templates]]</noinclude>

Network Bridge

2021-01-19T16:17:48Z

Puffergas: Created page with "{{FlightGearRaspberryPi4 Navigation}} It is possible the there will be an increasing number of Raspberries being added to the FlightGear simulator. It is also possible that t..."

{{FlightGearRaspberryPi4 Navigation}}

It is possible the there will be an increasing number of Raspberries being added to the FlightGear simulator. It is also possible that the location of said simulator only has a WiFi connection, to the home network. Furthermore, the home network might be saturated by other family menbers. It also might be possible that this cluster of devices is using Barrier, to share a common keyboard and mouse. One solution is to use a common WiFi router as a LAN/WLAN Bridge. Now, all the Raspberries can be connected to switch that is part of the Bridge Router and still have a internet connection.

Howto:Build and run FlightGear on Raspberry Pi 4

2021-01-19T03:04:29Z

Puffergas: /* Possible Paths */

{{FlightGearRaspberryPi4 Navigation}}

It is now possible to run FlightGear on a Raspberry Pi, starting with the model Pi 4. The objective of [[Howto:Build and run FlightGear on Raspberry Pi 4]] is to introduce Pi users to FlightGear and possibly FlightGear users to the Raspberry Pi family. One of the main objectives of the Raspberry Pi is education. Hopefully this marriage will introduce some young programmers to FlightGear. Although this will mainly deal with the Pi 4, other models may find applications in the area of flight panels and instruments.

== Gallery ==

<gallery mode=packed widths=230px heights=230px>
Pi4 ADW-ERI 1.png|Raspberry Pi4
Pi4 ADW-ERI 2.png|Raspberry Pi4
Pi4 ADW-ERI 4.png|Raspberry Pi4
Pi4 ADW-ERI 5.png|Raspberry Pi4
Pi4 ADW-ERI 7.png|Raspberry Pi4
Pi4 ADW-ERI 13.png|Raspberry Pi4
Pi4 ADW-ERI 15.png|Raspberry Pi4
Pi4 ADW-ERI 16.png|Raspberry Pi4
Pi4 Desk.jpg|Raspberry Pi4 running flightGear. One touchscreen and Raspberry P3 A+ with Phi PFD and a second with Phi radio stack.
</gallery>

== Possible Paths ==

[[File:FlightGear System.jpg|FlightGear and the Raspberry Pi family.]]

The Raspberry Pi can run FlightGear or perform other duties. Creating avionics steam gauges to more modern touch screen avionics devices. These ancillary Raspberries can serve a standard desktop computer running FlightGear or another Raspberry running FlightGear with most of the settings set to low.

== Did You Know ==

===Sun, tree and other textures===
[[File:Rendering.png|thumb|How to fix some texture issues with the Raspberry Pi4.]]
Did you know that the sun, tree and other textures can be fixed by enabling the "Cache graphics for faster loading" option, that is found in the launcher? This works for version 2020.3.5.

[[Category:Raspberry Pi]]
[[Category:Building from source‎]]

File:Rendering.png

2021-01-19T02:57:21Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=How to fix some texture issues with the Raspberry Pi4.}}
|date=2021-01-18
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]

PiStack

2021-01-13T01:11:53Z

Puffergas:

{{FlightGearRaspberryPi4 Navigation}}

== Introduction ==
'''PiStack''' is a remote radio stack interface, written for the Raspberry Pi and the official touchscreen, to be used with the DC-3.

[[File:PiStack GUI.png|thumb|The main GUI for PiStack]]

[[File:PiStack Keyboard.png|thumb|The frequency input keyboard for PiStack]]

== Software Repository ==

PiStack is located at GitHub.
[https://github.com/puffergas/PiStack PiStack Program]

Howto:Build and run FlightGear on Raspberry Pi 4

2021-01-13T00:59:49Z

Puffergas:

{{FlightGearRaspberryPi4 Navigation}}

It is now possible to run FlightGear on a Raspberry Pi, starting with the model Pi 4. The objective of [[Howto:Build and run FlightGear on Raspberry Pi 4]] is to introduce Pi users to FlightGear and possibly FlightGear users to the Raspberry Pi family. One of the main objectives of the Raspberry Pi is education. Hopefully this marriage will introduce some young programmers to FlightGear. Although this will mainly deal with the Pi 4, other models may find applications in the area of flight panels and instruments.

== Gallery ==

<gallery mode=packed widths=230px heights=230px>
Pi4 ADW-ERI 1.png|Raspberry Pi4
Pi4 ADW-ERI 2.png|Raspberry Pi4
Pi4 ADW-ERI 4.png|Raspberry Pi4
Pi4 ADW-ERI 5.png|Raspberry Pi4
Pi4 ADW-ERI 7.png|Raspberry Pi4
Pi4 ADW-ERI 13.png|Raspberry Pi4
Pi4 ADW-ERI 15.png|Raspberry Pi4
Pi4 ADW-ERI 16.png|Raspberry Pi4
Pi4 Desk.jpg|Raspberry Pi4 running flightGear. One touchscreen and Raspberry P3 A+ with Phi PFD and a second with Phi radio stack.
</gallery>

== Possible Paths ==

[[File:FlightGear System.jpg|FlightGear and the Raspberry Pi family.]]

The Raspberry Pi can run FlightGear or perform other duties. Creating avionics steam gauges to more modern touch screen avionics devices. These ancillary Raspberries can serve a standard desktop computer running FlightGear or another Raspberry running FlightGear with most of the settings set to low.

[[Category:Raspberry Pi]]
[[Category:Building from source‎]]

File:FlightGear System.jpg

2021-01-13T00:46:32Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=FlightGear and the Raspberry Pi family.}}
|date=2021-01-10 10:04:17
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]
[[Category:Cockpit building]]

APionics

2021-01-08T04:11:22Z

Puffergas:

{{FlightGearRaspberryPi4 Navigation}}
{{lowercase title}}
'''aPionics''' Uses the Raspberry Pi to drive external avionic instruments.
[[File:APionics.jpg|thumb|Cockpit instruments controlled by a Raspberry Pi.]]

Template:FlightGearRaspberryPi4 Navigation

2021-01-08T04:10:06Z

Puffergas:

{{sidebar
| name = Raspberry Pi 4 and FlightGear Navigation
| title = Raspbery Pi
| contentstyle= text-align: left;

| heading1 = Intro
| content1 = [[Howto:Build and run FlightGear on Raspberry Pi 4]]
| heading2 = Contents
| content2 =
* [[Updating Raspberry Pi OS]]
* [[Graphic Issues Raspberry Pi 4]]
* [[Joysticks and Raspberry Pi]]
* [[Compiling FlightGear for Raspberry Pi - Scripted Compilation]]
* [[Backtrace using gdb & Download and Compile.sh]]
* [[64bit OS - Raspberry Pi]]
* [[Interfacing - Raspberry Pi]]
* [[Memory Raspberry Pi]]
* [[Cooling - Raspberry Pi]]
* [[Feature Scaling - Raspberry Pi OS]]
* [[Feature Scaling - FlightGear]]
* [[Osgviewer - Raspberry Pi]]
* [[aPionics]]
* [[PiStack]]

}}

<noinclude>{{-}}

[[Category:Navigation templates]]</noinclude>

PiStack

2021-01-08T04:09:08Z

Puffergas: Created page with "{{FlightGearRaspberryPi4 Navigation}} '''PiStack''' is a remote radio stack interface, written for the Raspberry Pi and the official touchscreen, to be used with the DC-3. [..."

{{FlightGearRaspberryPi4 Navigation}}

'''PiStack''' is a remote radio stack interface, written for the Raspberry Pi and the official touchscreen, to be used with the DC-3.

[[File:PiStack GUI.png|thumb|The main GUI for PiStack]]

[[File:PiStack Keyboard.png|thumb|The frequency input keyboard for PiStack]]

File:PiStack GUI.png

2021-01-08T03:46:23Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=The main GUI for PiStack}}
|date=2021-01-07
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]

File:PiStack Keyboard.png

2021-01-08T03:46:23Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=The frequency input keyboard for PiStack}}
|date=2021-01-07
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]

Template:FlightGearRaspberryPi4 Navigation

2021-01-07T17:52:22Z

Puffergas:

{{sidebar
| name = Raspberry Pi 4 and FlightGear Navigation
| title = Raspbery Pi
| contentstyle= text-align: left;

| heading1 = Intro
| content1 = [[Howto:Build and run FlightGear on Raspberry Pi 4]]
| heading2 = Contents
| content2 =
* [[Updating Raspberry Pi OS]]
* [[Graphic Issues Raspberry Pi 4]]
* [[Joysticks and Raspberry Pi]]
* [[Compiling FlightGear for Raspberry Pi - Scripted Compilation]]
* [[Backtrace using gdb & Download and Compile.sh]]
* [[64bit OS - Raspberry Pi]]
* [[Interfacing - Raspberry Pi]]
* [[Memory Raspberry Pi]]
* [[Cooling - Raspberry Pi]]
* [[Feature Scaling - Raspberry Pi OS]]
* [[Feature Scaling - FlightGear]]
* [[Osgviewer - Raspberry Pi]]
* [[aPionics]]

}}

<noinclude>{{-}}

[[Category:Navigation templates]]</noinclude>

APionics

2021-01-07T17:44:59Z

Puffergas: Created page with "{{FlightGearRaspberryPi4 Navigation}} {{lowercase title}} '''aPionics''' Uses the Raspberry Pi to drive external avionic instruments. File:APionics.jpg|thumb|150|Cockpit ins..."

{{FlightGearRaspberryPi4 Navigation}}
{{lowercase title}}
'''aPionics''' Uses the Raspberry Pi to drive external avionic instruments.
[[File:APionics.jpg|thumb|150|Cockpit instruments controlled by a Raspberry Pi.]]

File:APionics.jpg

2021-01-07T17:36:15Z

Puffergas: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Cockpit instruments controlled by a Raspberry Pi.}}
|date=2021-01-07 10:10:23
|source={{own}}
|author=[[User:Puffergas|Puffergas]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Raspberry Pi]]
[[Category:Cockpit building]]