Anybody having issues with COWS Diamond DA42 Controls on MSFS 2020?

[pilotjohn]

I'm using FSUIPC exclusively for control setup with "Send direct to FSUIPC Calibration". This has been working great for all planes (and I have custom profiles for the few that are "special"), except I can't seem to get it to work on the COWS DA42.

Rudder control partially works. It appears to move in the cockpit view, but if there's no constant input change they "recenter".

Elevator and aileron controls don't work at all, and the stick in the cockpit doesn't move.

Throttles work fine.

Ultimately I can't rotate to take off.

 

[John Dowson]

I don't have the COWS DA42, so it is difficult for me to advise. You need to use logging to determine what is being used.
First, load the aircraft onto the runway and open the FSUIPC logging window (Log->Open Console) and set logging for Events.  If you see many events logged without touching anything, these events are just noise and can be ignored. When you need do is exit FSUIPC7, then add the DontLogThese ini parameter to your DA42 profile section to stop thse events being logged. Once that is done, restart FSUIPC7 and also set logging for Axes Controls. Then move the axes (rudder, elevator, aileron) in the VC and see if any events are logged. If so, you can try assigning to that.

If no standard controls/events are logged or work, look for Input Events instead. Try logging for Input Events and again move the axes (rudder, elevator, aileron) in the VC and see if any input events are logged. If so, I can show you how to assign to use those.

If no Input Events are available. try looking for lvars. List the lvars (Add-ons->WASM->List Lvars)  to see if any look applicable. If some look like they might control the main axes, you can log those lvars (see Advanced User guide on how to do this) and again move the axes on the VC to see the value range of the lvars. If it looks like you can use lvars to control the axes, I can help you assign to those.

The last step would be to inspect the code of the aircraft to see how the axes work. See the following article on how to do this: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/

Note there are a few presets currently available (45) for the COWS DA42, but none for the main flight axes.

15 hours ago, pilotjohn said:

I'm using FSUIPC exclusively for control setup with "Send direct to FSUIPC Calibration". This has been working great for all planes (and have custom profiles the few that are "special"), except I can't seem to get it work on the COWS DA42.

Actually, before trying the above, try assigning with "Send to FS as normal axis" and try the various different axes control there, including the *_EX1 ones.
You can (possibly) still calibrate when assigning this way, if allowed by the aircraft.

John

[pilotjohn]

So some interesting observations:

1. Before making any changes, I tried to use an Xbox controller on default settings/mappings in MSFS. This works in the aircraft (stick moves).

2. If I turn on logging (Events, Input Events, Axes Control) it shows AXIS_AILERON_SET when moving the controller.

3. If I change FSUIPC set up to "Send to FS as normal axis" as AXIS_AILERON_SET for my Yoko+, it doesn't work and the Xbox controller also stops working.

4. As soon as I go back to "Send direct to FSUIPC", the Xbox controller starts working again.

5. The rudders seem to work with FSUIPC, but start "resetting 0 position" above a certain speed, and Xbox controller rudders do not work.

 

[John Dowson]

17 hours ago, pilotjohn said:

1. Before making any changes, I tried to use an Xbox controller on default settings/mappings in MSFS. This works in the aircraft (stick moves).

2. If I turn on logging (Events, Input Events, Axes Control) it shows AXIS_AILERON_SET when moving the controller.

Are any other controls/events logged for this, or just the Aileron Set?

17 hours ago, pilotjohn said:

3. If I change FSUIPC set up to "Send to FS as normal axis" as AXIS_AILERON_SET for my Yoko+, it doesn't work and the Xbox controller also stops working.

4. As soon as I go back to "Send direct to FSUIPC", the Xbox controller starts working again.

That is very strange...assigning in FSUIPC should not affect assignments any where else, although calibration can affect controls assigned outside of FSUIPC. Ate you sure that this was not for other reasons, such as the window focus not being with MSFS (with the xbox controller being an XINPUT device, MSFS needs the focus to receive the xbox controls)?

17 hours ago, pilotjohn said:

5. The rudders seem to work with FSUIPC, but start "resetting 0 position" above a certain speed, and Xbox controller rudders do not work.

Also strange.

Take a look at the COWS discord server - there are reports there of similar issues. For aileron, rudder and elevator, you need to assign to use the following lvars:

L:INPUT_AILERON, percent; -100 - +100
L:INPUT_RUDDER, percent; -100 - +100
L:INPUT_ELEVATOR, percent; -100 - +100

You can assign an axis to control an lvar by defining your own preset and assigning to that. Take a look at the following FAQ entry on how to do this: 

 

John

Later: found this: DA40 LVAR bindings.txt

Thats for the DA40, but the COWS DA40 will share the same LVARs as the COWS DA42, so also applies.

Edited February 3 by John Dowson
Bindings file attached

[John Dowson]

Here's the DA42 bindings file:  DA42 LVAR bindings.txt

[pilotjohn]

9 hours ago, John Dowson said:

Here's the DA42 bindings file:  DA42 LVAR bindings.txt

Thanks, I'll try this. This will not use the calibration, correct?

[John Dowson]

10 hours ago, pilotjohn said:

This will not use the calibration, correct?

No, axes assigned to presets are not calibrated -  only the standard FS controls go through calibration. You can also reset any calibration entries to stop calibration by FSUIPC if required..

[pilotjohn]

5 hours ago, John Dowson said:

No, axes assigned to presets are not calibrated -  only the standard FS controls go through calibration. You can also reset any calibration entries to stop calibration by FSUIPC if required..

Is there any way to apply the calibration (which is helpful for idle detent and the slopes I'm used to)?

[John Dowson]

10 minutes ago, pilotjohn said:

Is there any way to apply the calibration (which is helpful for idle detent and the slopes I'm used to)?

No. If you want to calibrate, you would have to do this yourself before sending the value to the sim. You can do this in the RPN/preset code if you know advanced RPN, Otherwise, you would need to write the axis value to an FSUIPC offset and have a lua script that monitored the offset, calibrates the value to the lvar range (plus any further calibration you want to apply) and then send the new lvar value to the sim. Calibration for null zones is straightforward, but adding a slope more complicated (you need to determine the function to use).

John

[pilotjohn]

4 hours ago, John Dowson said:

No. If you want to calibrate, you would have to do this yourself before sending the value to the sim. You can do this in the RPN/preset code if you know advanced RPN, Otherwise, you would need to write the axis value to an FSUIPC offset and have a lua script that monitored the offset, calibrates the value to the lvar range (plus any further calibration you want to apply) and then send the new lvar value to the sim. Calibration for null zones is straightforward, but adding a slope more complicated (you need to determine the function to use).

John

Can I use the values at offset 0x3328 etc.? Are these the calibrated values that FSUIPC would be sending for elevator etc. control?

[pilotjohn]

On 2/3/2025 at 7:44 AM, John Dowson said:

Here's the DA42 bindings file:  DA42 LVAR bindings.txt

EDITED: It works!

So I have the following in myevents.txt:

COWS_DA42_Aileron#$Param -163.84 / -100 max 100 min (>L:INPUT_AILERON, Percent)
COWS_DA42_Elevator#$Param -163.84 / -100 max 100 min (>L:INPUT_ELEVATOR, Percent)
COWS_DA42_Rudder#$Param -163.84 / -100 max 100 min (>L:INPUT_RUDDER, Percent)

I then assigned controls as follows:

This now works.

[John Dowson]

13 hours ago, pilotjohn said:

Can I use the values at offset 0x3328 etc.? Are these the calibrated values that FSUIPC would be sending for elevator etc. control?

But as the standard controls are not used, they will be empty. Have you tried logging those?

12 hours ago, pilotjohn said:

This now works.

Great!

[pilotjohn]

I came across a weird situation with this aircraft (cleaning up configuration based on other threads that we shouldn't have calibration if we're assigning to a preset).

The DA42 seems to use L:INPUT_RUDDER (send to preset) only above 10kts or so ground speed. Below that, it has no effect.

However, if I have "calibration" set up for rudder, the rudders work below that speed. If I reset the calibration, they don't.

What does FSUIPC send to MSFS when "calibration" is set up for rudder, but I'm sending to a preset otherwise (not send to calibration)?

[John Dowson]

14 hours ago, pilotjohn said:

cleaning up configuration based on other threads that we shouldn't have calibration if we're assigning to a preset)

You can have it but it won't do anything because, as I said, it is the FS axis events that are calibrated, and this can be done before sending to the FS (done when using 'Send direct to FSUIPC calibration') or when the event is received by FSUIPC (and this event can be generated by FSUIPC when assigned with 'Send to FS as normal axis', or can be generated by the FS or other software, depending in the priority level it is sent at).

14 hours ago, pilotjohn said:

The DA42 seems to use L:INPUT_RUDDER (send to preset) only above 10kts or so ground speed. Below that, it has no effect.

So what does it use below 10kts?

14 hours ago, pilotjohn said:

However, if I have "calibration" set up for rudder, the rudders work below that speed. If I reset the calibration, they don't.

If you are using a preset for rudder and have calibration set up on rudder and this is having an effect, then what must be happening is that the preset is being executed and this is generating the FS rudder control/event (in the FS) which is then being received by FSUIPC, is being masked (i.e. blocked), but the value received is calibrated and then resent back to the FS (using the same event).
But this surprises me, as I thought that the standard FS rudder controls don't work...if they do, why don't you just assign to those?

When the aircraft is static, do you see the rudder move (external view) when you use the preset? If so, the preset must be working at all speeds, no?
And if you activate logging for Axes Controls, do you see any rudder events when using the preset, and if so which one?
Do you see any movement when assigned to Axis Rudder Set or Rudder Set (under 'Send to FS as normal axis')? And when assigned like this, can you set up monitoring for the lvar L:INPUT_RUDDER (see documentation on how to do this via the ini file) and see how that changes?

 

[pilotjohn]

Ok, here's what I see:

Axis Config	Joystick Calibration	Taxi <10kts	Taxi >= 10kts	L:INPUT_RUDDER	RUDDER_SET	AXIS_RUDDER_SET
Send to FS	No	No	No	None	Constant	None
Send to FS	Yes	No	No	None	None	None
Send to Calibration	Yes	Yes	No	None	Constant	Variable
Send to Preset	Yes	Yes	Yes	Variable	Variable	None
Send to Preset	No	No	Yes	Variable	Constant/Variable	None

Axis Unassigned (send to fs as normal, joystick calibration for rudder reset):

• No changes to L:INPUT_RUDDER logged (via LvarsLogged)
• RUDDER_SET logged for axis with the same constant value (-154)
• No AXIS_RUDDER_SET logged
• Joystick calibration unset
• Aircraft can't be at taxied at any speed, no changes to any visuals (inside or outside)

Axis Unassigned (send to fs as normal, joystick calibration for rudder "calibrated"):

• No changes to L:INPUT_RUDDER logged
• No RUDDER_SET logged for axis
• No AXIS_RUDDER_SET logged
• Joystick calibration rudder view doesn't show any changes when moving joystick
• Aircraft can't be at taxied at any speed, no changes to any visuals

Axis Assigned (send to calibration rudder, joystick calibration for rudder "calibrated"):

• No changes to L:INPUT_RUDDER logged (via LvarsLogged)
• RUDDER_SET logged for axis with the same constant value
• AXIS_RUDDER_SET logged for axis with changing value (based on joystick input)
• Joystick calibration rudder view shows changes as joystick is moved
• Aircraft can be taxied below 10 knots, rudder begins to flap above 10 knots, resets to "center" unless joystick is constantly "moved"

686750 ***  AXIS: Cntrl= 65764 (0x000100e4), Param= -8467 (0xffffdeed) AXIS_RUDDER_SET
686750 ***  AXIS: Cntrl= 65764 (0x000100e4), Param= -8876 (0xffffdd54) AXIS_RUDDER_SET
686750 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -154 (0xffffff66) RUDDER_SET
686766 ***  AXIS: Cntrl= 65764 (0x000100e4), Param= -9171 (0xffffdc2d) AXIS_RUDDER_SET

Axis Assigned (send to preset, joystick calibration for rudder "calibrated"):

• Changes to L:INPUT_RUDDER logged (based on joystick input)
• RUDDER_SET logged for axis with the different values
• No AXIS_RUDDER_SET logged for axis
• Joystick calibration rudder view shows changes as joystick is moved
• Aircraft can be taxied at all speeds, no flapping observed on rudder visuals

1209969 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 1671 (0x00000687) RUDDER_SET
1210000 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 1062 (0x00000426) RUDDER_SET
1210000 Lvar updated: INPUT_RUDDER = -13.793945
1210016 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 0 (0x00000000) RUDDER_SET
1210047 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -882 (0xfffffc8e) RUDDER_SET
1210078 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -1645 (0xfffff993) RUDDER_SET
1210141 Lvar updated: INPUT_RUDDER = 43.243408
1210328 Lvar updated: INPUT_RUDDER = 46.295166

Axis Assigned (send to preset, joystick calibration reset):

• Changes to L:INPUT_RUDDER logged (based on joystick input)
• RUDDER_SET logged for axis with the different values above 10kts, constant value below 10kts 
• No AXIS_RUDDER_SET logged for axis
• Joystick calibration rudder view unset
• Aircraft can be taxied at >10 kts, no visual changes below 10kts (rudder stuck at last position)

1930016 Lvar updated: INPUT_RUDDER = 48.474121
1930047 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -3572 (0xfffff20c) RUDDER_SET
1930063 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -2929 (0xfffff48f) RUDDER_SET
1930172 Lvar updated: INPUT_RUDDER = 2.667236
--- Below 10 knots ---
1930547 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 7079 (0x00001ba7) RUDDER_SET
1930563 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 7079 (0x00001ba7) RUDDER_SET

So I'm trying to figure out why Send to Preset + Calibration results in a perfectly functioning plane, but all others do not.

 

[John Dowson]

 

7 minutes ago, pilotjohn said:

So I'm trying to figure out why Send to Preset + Calibration results in a perfectly functioning plane, but all others do not.

I have no idea - try the aircraft support...but if you have a working solution, I would just be happy with that...

Sorry but most of that doesn't make much sense to me (I would need to see log and ini files for each test to make sense of this), I don't have this aircraft and I really cannot spend any more time on this as I have far to much to do at the moment....these forums are shutting down at some point this year and I need to move everything across to www.fsuipc.com and set up a discord server for support. I therefore have no time to look into this, especially as you have a working solution..

 

[pilotjohn]

It turned out to be another addon. I should have eliminated more variables. Good luck, I do hope you manage to archive all this valuable information.

[John Dowson]

19 minutes ago, pilotjohn said:

It turned out to be another addon.

That is interesting - which one? And how did this cause this steering/rudder issue?

20 minutes ago, pilotjohn said:

Good luck, I do hope you manage to archive all this valuable information.

Thanks - its going to be a slow process.... hopefully I will be able to keep these forums read-only for quite a while so I can transfer the information over an extended period and after the new discord support is active.

John

[pilotjohn]

10 hours ago, John Dowson said:

That is interesting - which one? And how did this cause this steering/rudder issue?

10 hours ago, pilotjohn said:

FSRealistic's prop wash effect apparently. But somehow the interaction between it, and FSUIPC's rudder calibration (without assignment to it), negated it. If I disabled FSR prop wash, INPUT_RUDDER works at all speeds.