Well, this is a bit hard to judge for someone who doesn't have the same piece of hardware.
Let's rule out the easiest thing first:
Is DeviceLink putting out values for turn/slip yes or no?
This can be answered first by taking a look into IL-2's code where it's plain to see that in online sessions this output will be suppressed.
You should fly offline for your tests though.
Next we can give it a try with a sample client app.
I've made one for Android to check what I get back from DeviceLink and this is what I see flying offline:
Slip Deg. and Turn Ind. show valid values which means "it works".
Now we see these lines in your G-Step functions maintenance window:
Code:
030, Slip, Position, Gauge, , 04, 034, 000, 0, 1, 1
031, turn, Position, Gauge, , 04, 036, 000, 0, 1, 1
Whether or not "turn" should have a capital "T" is debateable.
The DeviceLink query parameters (34, 36) seem fine.
Comparing this to other DeviceLink Parameters configured there, we see that these two lines have a "000" behind the DeviceLink Parameter, whereas others have "001" at that place.
Can it be that there's a mistake here?
Furthermore you once mentioned that the default config for turn gauge has value ranges of -1000 to +1000.
How about applying a multiplier of 1000 to that gauge?
In my book the line should look like this:
Code:
031, turn, Position, Gauge, , 04, 036, 001, 0, 1000, 1
Best regards - Mike