Logitech G940

[Lower&Faster]

Hi everyone,

Just got FG a few days ago, what a great piece of kit!

Could anyone tell me if it is possible to get the Logitech G940 flight control system working with flight gear?
I have done a forum search and found no threads specifically on the G940.

If anyone has the .xml file which works with G940 and could share it that would be great - otherwise I will start reading the wiki :p

In game, Flight gear does pick up that I have a G940 and 3 controllers (Joystick, Throttle & Rudder), but the axes and buttons are not programmed correctly.

Also, does flight gear have support for FreeTrack?

Regards and thanks for your time.

[HHS]

FlightGear supports all inputs and devices like several Joysticks etc...
So theoretically it should possible like with all other ones we already use.

The Logitech G940 is quite new and currently I don't know any user here which owns one, so there is likely no xml yet.
But if you use the seachfunction here, you will get a whole list of how to program a joystick. If there are specific questions left you can ask here and you will get help how to solve this.

We don't support ree Track, but we support FaceTrackNoIR

[Lower&Faster]

Thanks,

I will let you know how I go with it. Probably give it a proper shot on the weekend when I have some time.

[parand]

Hi,
I know its an older Topic, but I have an (incomplete) XML for using the G940. I (copy and paste ) programmed it, Thanks for all the explanations. It includes all three rudders, up to now only one throttle, analogue prop pitch and mixture, analogue trim of all rudders, two coolies (on stick and throttle) for sight elevation and direction. analogue sight direction (left/right) with the mini joy on the stick. Also some buttons are programmed Gear up/ gear down, Flaps up/down) There are now three XML files (one for the rudder pedals, one for the stick one for the throttle).

G940-joystick.xml

Code: Select all

<?xml version="1.0" ?>
<!-- Maintainer: <parand-->
<!--
************************************************************************
* Bindings for Logitech G940 Stick
*
*
* Axis 0: ailerons
* Axis 1: elevator
* Axis 2 (mini Joy): look left/right
* Axes 6&7: view direction
* Axis 3: elevator trim   
* Axis 4: rudder trim     
* Axis 5: ailerons trim   
*
* Buttons
*
* Btn 0 (trigger): Guns               
************************************************************************
$Id$
-->

<PropertyList>

 <name>Logitech Inc. G940 Joystick</name>
 <name>Logitech G940 Joystick</name>

 <axis>
  <desc>Aileron</desc>
  <number>
   <unix>0</unix>
   <mac>0</mac>
   <windows>0</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/flight/aileron</property>
   <squared type="bool">true</squared>
  </binding>
 </axis>

 <axis>
  <desc>Elevator</desc>
  <number>
   <unix>1</unix>
   <mac>1</mac>
   <windows>1</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/flight/elevator</property>
   <factor type="double">-1.0</factor>
   <squared type="bool">true</squared>
  </binding>
 </axis>

<axis n="3">
<desc>Elevator Trim</desc>
<direction>down/forward</direction>
<binding>
<command>property-scale</command>
<property>/controls/flight/elevator-trim</property>
<factor type="double">-1.0</factor>
<power type="int">1</power>
</binding>
</axis>

<axis>
  <desc>Rudder</desc>
  <number>
   <unix>2</unix>
   <mac>2</mac>
   <windows>4</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/flight/rudder-trim</property>
   <factor type="double">1.0</factor>
  </binding>
 </axis>

<axis>
  <desc>Aileron</desc>
  <number>
   <unix>0</unix>
   <mac>0</mac>
   <windows>5</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/flight/aileron-trim</property>
   <squared type="bool">true</squared>
  </binding>
 </axis>

 <axis n="6">
  <desc>View Direction</desc>
  <number>
   <unix>4</unix>
   <mac>4</mac>
   <windows>6</windows>
  </number>
  <low>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-heading-offset-deg</property>
    <step type="double">1.0</step>
   </binding>
  </low>
  <high>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-heading-offset-deg</property>
    <step type="double">-1.0</step>
   </binding>
  </high>
 </axis>

 <axis>
  <desc>View Elevation</desc>
  <number>
   <unix>5</unix>
   <mac>5</mac>
   <windows>7</windows>
  </number>
  <low>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-pitch-offset-deg</property>
    <step type="double">1.0</step>
   </binding>
  </low>
  <high>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-pitch-offset-deg</property>
    <step type="double">-1.0</step>
   </binding>
  </high>
 </axis>

<axis n="2">
  <desc>(twist) View Direction</desc>
  <binding>
   <command>property-scale</command>
     <property>/sim/current-view/goal-heading-offset-deg</property>
   <factor type="double">-180</factor>
  </binding>
</axis>

    <button n="0">
       <desc>guns</desc>
      <binding>
       <command>property-assign</command>
       <property>/controls/armament/trigger</property>
       <value>true</value>
      </binding>
    <mod-up>
       <binding>
        <command>property-assign</command>
        <property>/controls/armament/trigger</property>
        <value>false</value>
       </binding>
      </mod-up>
    </button>
 
</PropertyList>


G940-pedals.xml

Code: Select all

<?xml version="1.0" ?>
<!-- Maintainer: <parand-->
<!--
************************************************************************
* Bindings for Logitech G940 Pedals
*
*
* Axis 0: Brake left
* Axis 1: Brake right
* Axis 3: rudder
************************************************************************
$Id$
-->

<PropertyList>

 <name>Logitech Inc. G940 Pedals</name>
 <name>Logitech G940 Pedals</name>

<axis n="0">
  <desc>Brake left</desc>
  <binding>
   <command>property-scale</command>
   <property>/controls/gear/brake-left</property>
   <offset>-1.0</offset>
   <factor>-0.5</factor>
  </binding>
 </axis>

 <axis n="1">
  <desc>Brake right</desc>
  <binding>
   <command>property-scale</command>
   <property>/controls/gear/brake-right</property>
   <offset>-1.0</offset>
   <factor>-0.5</factor>
  </binding>
 </axis>
 
 <axis>
  <desc>Rudder</desc>
  <number>
   <unix>2</unix>
   <mac>2</mac>
   <windows>3</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/flight/rudder</property>
   <factor type="double">1.0</factor>
  </binding>
 </axis>

 </PropertyList>


G940-throttle.xml

Code: Select all

<?xml version="1.0" ?>
<!-- Maintainer: <parand-->
<!--
************************************************************************
* Bindings for Logitech G940 Throttle
*
*
* Axis 0: Throttle
* Axis 2: mixture
* Axis 3: Prop pitch
* Axis 6: viev direction
* Axis 7: viev elevation
*
* Button 0: increase engine boost
* Button 1: decrease engine boost
* Button 2: elevator trim down
* Button 4: flaps up
* Button 8: flaps down
* Button 5: gear up
* Button 9: gear down
************************************************************************
$Id$
-->

<PropertyList>

 <name>Logitech Inc. G940 Throttle</name>
 <name>Logitech G940 Throttle</name>
 
 <axis>
  <desc>Throttle</desc>
  <number>
   <unix>3</unix>
   <mac>3</mac>
   <windows>0</windows>
  </number>
  <binding>
   <command>nasal</command>
   <script>controls.throttleAxis()</script>
  </binding>
 </axis>
 
<axis>
  <desc>Mixture</desc>
  <number>
    <unix>3</unix>
    <mac>3</mac>
    <windows>2</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/engines/engine[0]/mixture</property>
   <offset type="double">-1.0</offset>
   <factor type="double">-0.5</factor>
  </binding>
  <binding>
   <command>property-scale</command>
   <property>/controls/engines/engine[1]/mixture</property>
   <offset type="double">-1.0</offset>
   <factor type="double">-0.5</factor>
  </binding>
 </axis>

<axis>
  <desc>Propeller</desc>
  <number>
    <unix>4</unix>
    <mac>4</mac>
    <windows>3</windows>
  </number>
  <binding>
   <command>property-scale</command>
   <property>/controls/engines/engine[0]/propeller-pitch</property>
   <offset type="double">-1.0</offset>
   <factor type="double">-0.5</factor>
  </binding>
  <binding>
   <command>property-scale</command>
   <property>/controls/engines/engine[1]/propeller-pitch</property>
   <offset type="double">-1.0</offset>
   <factor type="double">-0.5</factor>
  </binding>
 </axis>

<axis n="6">
  <desc>View Direction</desc>
  <number>
   <unix>4</unix>
   <mac>4</mac>
   <windows>6</windows>
  </number>
  <low>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-heading-offset-deg</property>
    <step type="double">1.0</step>
   </binding>
  </low>
  <high>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-heading-offset-deg</property>
    <step type="double">-1.0</step>
   </binding>
  </high>
 </axis>

 <axis>
  <desc>View Elevation</desc>
  <number>
   <unix>5</unix>
   <mac>5</mac>
   <windows>7</windows>
  </number>
  <low>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-pitch-offset-deg</property>
    <step type="double">1.0</step>
   </binding>
  </low>
  <high>
   <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/sim/current-view/goal-pitch-offset-deg</property>
    <step type="double">-1.0</step>
   </binding>
  </high>
 </axis>

 <button n="0">
  <desc>Increase Engine Boost</desc>
  <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/controls/engines/engine[0]/boost</property>
    <step type="double">+0.01</step>
   </binding>
   <binding>
    <command>property-adjust</command>
    <property>/controls/engines/engine[1]/boost</property>
    <step type="double">+0.01</step>
   </binding>
 </button>

 <button n="1">
  <desc>Decrease Engine Boost</desc>
  <repeatable>true</repeatable>
   <binding>
    <command>property-adjust</command>
    <property>/controls/engines/engine[0]/boost</property>
    <step type="double">-0.01</step>
   </binding>
   <binding>
    <command>property-adjust</command>
    <property>/controls/engines/engine[1]/boost</property>
    <step type="double">-0.01</step>
   </binding>
 </button>



<button n="4"> <!-- Labled as P1 -->
  <desc>Flaps up</desc>
  <repeatable>false</repeatable>
  <binding>
   <command>nasal</command>
   <script>controls.flapsDown(-1)</script>
  </binding>
  <mod-up>
   <binding>
    <command>nasal</command>
    <script>controls.flapsDown(0)</script>
   </binding>
  </mod-up>
 </button>
 
<button n="8"> <!-- Labled as P5 -->
  <desc>Flaps down</desc>
  <repeatable>false</repeatable>
  <binding>
   <command>nasal</command>
   <script>controls.flapsDown(1)</script>
  </binding>
  <mod-up>
   <binding>
    <command>nasal</command>
    <script>controls.flapsDown(0)</script>
   </binding>
  </mod-up>
 </button>

<button n="5"> <!-- Labled as P2 -->
  <desc>Gear up</desc>
  <repeatable>false</repeatable>
  <binding>
   <command>nasal</command>
   <script>controls.gearDown(-1)</script>
  </binding>
  <mod-up>
   <binding>
    <command>nasal</command>
    <script>controls.gearDown(0)</script>
   </binding>
  </mod-up>
 </button>
 
<button n="9"> <!-- Labled as P6 -->
  <desc>Gear down</desc>
  <repeatable>false</repeatable>
  <binding>
   <command>nasal</command>
   <script>controls.gearDown(1)</script>
  </binding>
  <mod-up>
   <binding>
    <command>nasal</command>
    <script>controls.gearDown(0)</script>
   </binding>
  </mod-up>
 </button>


</PropertyList>


cheers, parand

[sgofferj]

Did anybody get any further with the G940?
I've read a lot and e.g. the 8 buttons on the throttle's base can be illuminated red, green, amber or not.
I still didn't get myself a new HOTAS system and the G940 is on sale here ATM ^^.

[mucm]

I have this G940 joystick/throttle/pedal set. I've tried it in both Linux and Windows, and there seems to be a dilemma in how to write the joystick file. Several dilemmas actually...

In Windows it is detected as 3 joysticks (different names) with 8, 6, and 8 axes respectively (not all of which do anything); while in Linux it is detected as 1 joystick (different name again) with 16 or 18 axes depending which test program you believe.

Can anyone tell me if this is possible to adapt to this situation with 1 joystick xml file? or do I need 4 (3 for Windows and 1 for Linux)?

I would like to submit this to Git eventually but the wiki page on joysticks isn't detailed enough to handle this case.

In Windows it shows:

Code: Select all

C:\Program Files\FlightGear\bin\Win32>js_demo.exe
Joystick test program.
~~~~~~~~~~~~~~~~~~~~~~
Joystick 0: "Logitech G940 Joystick"
Joystick 1: "Logitech G940 Pedals"
Joystick 2: "Logitech G940 Throttle"
Joystick 3 not detected
Joystick 4 not detected
Joystick 5 not detected
Joystick 6 not detected
Joystick 7 not detected
+--------------------JS.0----------------------+--------------------JS.1----------------------+--------------------JS.2----------------------+
| Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 Ax:7 | Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5           | Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 Ax:7 |
+----------------------------------------------+----------------------------------------------+----------------------------------------------+
| 0000 -0.0 -0.1 -1.0 ^C.2 +0.1 +0.3 +0.0 +0.0 | 0000 +1.0 +1.0 -1.0 +0.2 -1.0 -1.0   .    .  | 0000 -1.0 -1.0 -0.0 +0.0 -1.0 -1.0 +0.0 +0.0 |
C:\Program Files\FlightGear\bin\Win32>

Whereas in Linux:

Code: Select all

~/Apps/fg/bin $ ./js_demo
Joystick test program.
~~~~~~~~~~~~~~~~~~~~~~
Joystick 0: "G940"
Joystick 1 not detected
Joystick 2 not detected
Joystick 3 not detected
Joystick 4 not detected
Joystick 5 not detected
Joystick 6 not detected
Joystick 7 not detected
+--------------------JS.0----------------------+
| Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 Ax:7 Ax:8 Ax:9 Ax:10 Ax:11 Ax:12 Ax:13 Ax:14 Ax:15 |
+----------------------------------------------+
| 0000 +0.0 -0.1 -0.1 +1.0 +1.0 +0.0 -1.0 -1.0 +1.0 -0.8 +0.1 -0.1 +0.0 +0.0 +0.0 +0.0 |


I have made detailed notes on which axes and buttons (at least according to js_demo) connects to which real-world actions of the joystick, pedals, hat switches, trim wheels, etc. But I don't think I'll clutter this post with all that yet, because there are contradictions and omissions within them. For example on the windows side, there are two controls which affect the same axis in js_demo. On the Linux side, there are no axes that are affected by the first two trim wheels on the joystick base.

I've also noticed some strangeness with what the common Linux program jscal says about this device:

Code: Select all

$ jscal /dev/input/js0
Joystick has 18 axes and 21 buttons.
Correction for axis 0 is broken line, precision is 3.
Coeficients are: 0, 0, 1394469, 1394469
Correction for axis 1 is broken line, precision is 3.
Coeficients are: 0, 0, 1394469, 1394469
Correction for axis 2 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 3 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 4 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 5 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 6 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 7 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 8 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 9 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 10 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 11 is broken line, precision is 0.
Coeficients are: 127, 127, 5534751, 5534751
Correction for axis 12 is broken line, precision is 0.
Coeficients are: 0, 0, 536870912, 536870912
Correction for axis 13 is broken line, precision is 0.
Coeficients are: 0, 0, 536870912, 536870912
Correction for axis 14 is broken line, precision is 0.
Coeficients are: 0, 0, 536870912, 536870912
Correction for axis 15 is broken line, precision is 0.
Coeficients are: 0, 0, 536870912, 536870912
Correction for axis 16 is broken line, precision is 0.
Coeficients are: 0, 0, 536870912, 536870912
Correction for axis 17 is broken line, precision is 0.
Coeficients are: 0, 0, 536870912, 536870912


Though I don't know what would be "normal" output from the above command.

Strangely, the --print-mappings output of that command indeed has 18 buttons, but they're numbered 0 to 21, skipping 12 to 15:

Code: Select all

$ jscal --print-mappings /dev/input/js0
jscal -u 18,0,1,2,3,4,5,6,7,8,9,10,11,16,17,18,19,20,21,21,288,289,290,291,292,293,294,295,296,297,298,299,300,301,302,303,720,721,722,723,724 /dev/input/js0


It seems to be reset to the above after every reboot.

I experimented with rearranging these, or with mapping them only to 0 to 17, and in each case it would give a segmentation fault, but then if I repeated the exact same command a second time it would appear to work (no seg fault), but the behaviour in js_demo output got very strange, such as two different joystick motions (that were previously different axes) affecting the same axis, or some axes being -1 in the middle and +1 at both extremes (instead of the usual, 0 in the middle, -1 at one extreme, and +1 at the other extreme).

Any suggestions for me on how to proceed? Could js_demo be improved to output data for 18 axes instead of the current limit which appears to be 16?

Also I can see that as a general rule, any new joystick files should first control elevator and ailerons with their "main" up-down-left-right controls, then if they have pedals that would naturally control rudder (next most important), and so on. What would be in general the first few most critical things to assign to the first few buttons? or first few most-standard-between-different-joysticks to assign? or most-standard-between-different-aircraft?

[mucm]

Strangely, the --print-mappings output of that command indeed has 18 buttons, but they're numbered 0 to 21, skipping 12 to 15:

Oops, that should have been "...indeed has 18 axes..."

[mucm]

For anyone considering this joystick, throttle, pedals set, it is construction-wise pretty good. The force feedback I have only felt during the Windows calibration screens, where it goes haywire as you press certain buttons, but is certainly powerful... it could easily break a fogey's wrist.

I can confirm it has what on many reviews and youtube videos is called the "reversal bug", and which Logitech calls hysteresis and is no doubt a "feature". E.g. http://www.youtube.com/watch?v=SZlUWwOJUN0

So it is, at a high level, pretty good for what most people will notice, and this may be the source of the good reviews. However if you try to precisely adjust any axis (like a trim wheel with the heads-up-display enabled) you will see it is nice and precise when going one direction (pixel-level precision) but if you go too far and start to go back, the hysteresis kicks in and considers your input "noise" until it has passed a certain threshold, so you end up jumping say 10 or 20 pixels back. This is very annoying and is certainly noticeable when flying, even on joystick and pedals, not just trim wheels. Not that it prevents you from flying, it just throws unwanted jumps into your input.

My particular hardware version information is:

M/N: J-U0001
P/N: 842-000004
PID: LZ122M1

Here is what I've sent to Logitech support:

We have tested this product in a flight simulator application and found it more or less worked adequately.

However on closer testing, we have since discovered that the "hysteresis" problem (what others in many internet reviews of the product are calling the "reversal bug") is not just a calibration or application (our flight simulator) issue as we first believed (thus believing we could address it in the application), but is in fact coming from the joystick hardware itself or firmware or driver (thus we cannot work around it).

We have this issue on all axes. We have this in the pedals, in the throttles, in all 5 trim wheels.

Our versions are:

5.10.127 according to the Logitech Profiler Help... About... screen.
lgs509_x64 according to downloaded file name.

I have run G940_Updater which changed the firmware from 1.37 to 1.41, and rebooted; the issue persists.

I believe from internet reviews that this previously affected the first two main joystick axes more and was "improved" with a firmware update, however it still affects those axes the same in my tests too.

I have gone to the Profiler... Device menu... Game Controllers... Properties... Settings... Hysteresis, and it does not let me adjust this below 10. Why can this not be set to zero, and let the application handle whether it is jitter noise or a real input from the user?

I have also tried setting all of these hysteresis values to a higher number (65) to verify that this is the issue (expecting it to be worse with this change, 65 out of 255 should mean about 1/4 of the whole axis' travel should be masked by the hysteresis), yet it was the same, so I am not convinced this setting is even being used anywhere.

We absolutely need this fixed.

I didn't bother raising it in the Logitech support ticket but the hysteresis is about the same in FlightGear under Linux as it is under Windows. This suggests to me it is not in the Windows driver but indeed in the firmware. I will let all a youse know how they respond.

[Qwseyvnd]

Do you still have the issue? Or is it fixed? I still have this issue in linux if I am using FlightGear 2.1.2

[ak-vinge]

Hi.
Just got my hands on a used G940 set. Have downloaded the driver, calibrated and all is responding in the Logitech profiler program. I am NOT used to programming. So joystick, throttle and pedals more or less do the same it looks like. Used 4 hours trying and 2 hours reading here.

So my goal is training soaring first. So I need tow release.

How do I install the xlm file(s) for operating the G940 controls in Windows 10?
lenovo thinkpad laptop. SSD , Intel i5, and grafikkcard intel HD Graphics 4600

[sim]

ak-vinge, The Logitech G940 has aged 8 years since this topic opened in 2010 !

So about time working xml files were around for stick pedals and throttle.
You will need to ensure FG recognises all three devices, (or two if throttle
is just an extension of the joystick).

mucm says three show in js_demo
Joystick 0: "Logitech G940 Joystick"
Joystick 1: "Logitech G940 Pedals"
Joystick 2: "Logitech G940 Throttle"

Sounds like an interesting piece of kit. Does it require three USB sockets?
Three separate xml's required too. (3 in windows although Linux seems conflicted about that)

Never tried aero-tow in FG myself. In FG the Winch launch always seemed easier.
Best of all and smoothest is a hill facing into wind and bungee launch which FG doesn't
seem to do yet. Although if the wind's strong enough and you attach a rope to nose hook
(Rope staked further downhill) Then just heave back on the stick until fully airbourne,
lower the nose and pull the bung!

[dutchman]

I use3 xml files named g940-joystick.xml g940-pedals.xml and g940-throttle.xml.
They are located in /flightgear/data/Input/Joysticks/Logitech/