Howto:Build and run FlightGear on Raspberry Pi 4: Difference between revisions

Jump to navigation Jump to search
m
add syntax highlighting
m (add syntax highlighting)
Line 4: Line 4:
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.
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
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.
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
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.
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.
Line 88: Line 93:
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'>.
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'>.


<syntaxhighlight lang="xml">
   <axis>
   <axis>
     <desc type="string">Mixture All Engines</desc>
     <desc type="string">Mixture All Engines</desc>
Line 115: Line 121:
     </binding>
     </binding>
   </axis>
   </axis>
</syntaxhighlight>


<big>'''Thrustmaster Flight Rudder Pedals'''</big>
<big>'''Thrustmaster Flight Rudder Pedals'''</big>
Line 133: Line 141:


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:
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>
   <name type="string">Thrustmaster T-Rudder</name>
Line 162: Line 172:
     </binding>
     </binding>
   </axis>
   </axis>
 
</syntaxhighlight>
 
[[User:Puffergas|Puffergas]] ([[User talk:Puffergas|talk]]) 16:26, 20 February 2020 (EST)


==Compiling ==
==Compiling ==
Line 181: Line 189:


[[File:Cooling fan Raspberry Pi4.jpg|thumb|Noctua cooling fan used to cool the Raspberry Pi4 while running FlightGear.]]
[[File:Cooling fan Raspberry Pi4.jpg|thumb|Noctua cooling fan used to cool the Raspberry Pi4 while running FlightGear.]]
[[User:Puffergas|Puffergas]] ([[User talk:Puffergas|talk]]) 12:50, 21 February 2020 (EST)

Navigation menu