Is it possible to shape an axis curve in input.map? [-somewhat solved-]

[ADorante]

Hi all!

 

I suspect I have an issue with the limited recognized range of my Simped pedal's left brake. I slave it through a realsimulator.com RUSBA adapter since I no longer use the TM HOTAS Cougar for this purpose. Pedal's left brake range input is limited from ca. 44% to 100% and may be the result of a defective Hall sensor (since I think Simpeds are no longer manufactured I have to live with that, though a repair would be appreciated).

 

This is no problem for me in most cases. Until I started up the Junkers Ju 52 - her brakes are connected to left and right engine throttle. As a result I suspect that constant brake input of 44% lets my left engine always stay close to idle while using these pedals.

 

During my inital search for a solution and after unsuccessfuly re-calibrating inside RUSBA software and Sturmovik settings I stumbled over an entry in [IL-2 directory]\data\input\input.map:

 

Quote

[RPC_WHEEL_BRAKES_LEFT]

data_row0 = -1.000000, -0.980000, -0.960000, -0.940000, -0.920000, -0.900000, -0.880000, -0.860000, -0.840000, -0.820000;
data_row1 = -0.800000, -0.780000, -0.760000, -0.740000, -0.720000, -0.700000, -0.680000, -0.660000, -0.640000, -0.620000;
data_row2 = -0.600000, -0.580000, -0.560000, -0.540000, -0.520000, -0.500000, -0.480000, -0.460000, -0.440000, -0.420000;
data_row3 = -0.400000, -0.380000, -0.360000, -0.340000, -0.320000, -0.300000, -0.280000, -0.260000, -0.240000, -0.220000;
data_row4 = -0.200000, -0.180000, -0.160000, -0.140000, -0.120000, -0.100000, -0.080000, -0.060000, -0.040000, -0.020000;
data_row5 = 0.000000, 0.020000, 0.040000, 0.060000, 0.080000, 0.100000, 0.120000, 0.140000, 0.160000, 0.180000;
data_row6 = 0.200000, 0.220000, 0.240000, 0.260000, 0.280000, 0.300000, 0.320000, 0.340000, 0.360000, 0.380000;
data_row7 = 0.400000, 0.420000, 0.440000, 0.460000, 0.480000, 0.500000, 0.520000, 0.540000, 0.560000, 0.580000;
data_row8 = 0.600000, 0.620000, 0.640000, 0.660000, 0.680000, 0.700000, 0.720000, 0.740000, 0.760000, 0.780000;
data_row9 = 0.800000, 0.820000, 0.840000, 0.860000, 0.880000, 0.900000, 0.920000, 0.940000, 0.960000, 0.980000;
data_endrow = 1.000000

symmetry = 1;
spline = 0;

 

Now I'm wondering if I'll map those data rows (0% = -1,000000 to 100% = 1.000000) to 44% - 100% and into the corresponding values, will this work?

 

I'll report back but in the meantime I'd appreciate any comments. 

Edited August 9, 2019 by ADorante
wrong input.map excerpt corrected

[ADorante]

first conclusion: It really seems to be the malfunction left wheel brake axis on my Simpeds that's responsible for unwanted behaviour in the Ju52. Deleting the axis input from settings/keymapping lets me take off in the aircraft without unwanted braking/throttling.

 

second conclusion: I can't edit the input.map file. I have to try it in the current.map file. input.map stores the default settings and gets restored after program launch when edited.

 

new problem: I deleted the axis but I haven't backed-up my pedal settings in current.map before. Now I have to do a little trial-and-error rediscovering the correct axis name as it has to be defined inside current.map

[[FD]_5_Scarecrow]

For some files it is possible to set them as "Read Only" by right clicking the file and choosing "Properties," in order to preserve your changes. As example, this works for graphics settings in startup.cfg but I've never edited input.map. Could be worth a try?

[ADorante]

thx niner!

yes I tried that with input.map first, but i guess this isn't the right file that has to be changed and then made read-only.

And now I know a little fact more: inside the file current.actions you have to enter the name of your axis, if you want to do it manually. current.map doesn't work for this purpose: I've only successful added an entry for my chosen axis to the visible key mappings when editing current.actions.

[ADorante]

ok, I got it working by editing the curve reponse in current.map and making the file read-only with one remaining issue: Now I get constantly message pop-ups about files unable to write. But at least I can now use a combination of pedal and throttle input to steer the Ju52.

 

As for my pedal behavior mentioned in the first posting (working left brake only from 44% to 100% range) I found this response curve setting in current.map file suitable:

 

Quote

[rpc_wheel_brakes_left]

data_row0 = -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000;
data_row1 = -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000;
data_row2 = -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000;
data_row3 = -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -1.000000;
data_row4 = -1.000000, -1.000000, -1.000000, -1.000000, -1.000000, -0.930000, -0.890000, -0.860000, -0.820000, -0.790000;
data_row5 = -0.750000, -0.720000, -0.680000, -0.650000, -0.610000, -0.580000, -0.540000, -0.510000, -0.470000, -0.440000;
data_row6 = -0.400000, -0.370000, -0.330000, -0.300000, -0.260000, -0.230000, -0.190000, -0.160000, -0.120000, -0.090000;

data_row7 = 0.050000, 0.020000, 0.000000, 0.050000, 0.090000, 0.120000, 0.160000, 0.190000, 0.230000, 0.260000;
data_row8 = 0.300000, 0.330000, 0.370000, 0.400000, 0.440000, 0.470000, 0.510000, 0.540000, 0.580000, 0.610000;
data_row9 = 0.650000, 0.680000, 0.720000, 0.750000, 0.790000, 0.820000, 0.860000, 0.890000, 0.930000, 0.960000;
data_endrow = 1.000000

symmetry = 0;
spline = 0;

[end]

 

I guess I have to ask some testers or the devs about an enhanced solution to my issue. Chances are that there need to be made some changes to the settings algorithms/data.

 

[edit] oh, I see I left out a couple of minuses in data_row7.

Quote

data_row7 = 0.050000, 0.020000, 0.000000, 0.050000, 0.090000, 0.120000, 0.160000, 0.190000, 0.230000, 0.260000;

 

must be:

Quote

data_row7 = -0.050000, -0.020000, 0.000000, 0.050000, 0.090000, 0.120000, 0.160000, 0.190000, 0.230000, 0.260000;

 

Edited August 9, 2019 by ADorante
see edit note above

[Sokol1]

21 hours ago, ADorante said:

44% to 100% and may be the result of a defective Hall sensor (since I think Simpeds are no longer manufactured I have to live with that, though a repair would be appreciated).

 

Since Hall sensor is a electronic circuit is more probable that stop work than work partially.

A possibility is that magnet - use by HALL sensor as reference, became loose and change position, and this reduce the axis reading. If possible give a visual inspection of magnet and sensor of the fault brake.

 

In RoF forum are a topic of guys changing HALL sensor and USB controller of Simped.

Simped electronics is from end of last century, use 4 bits (128 "steeps") USB controller, the (RoF) guys replace original controller with

Leo Bodnar Bu-836A (12 bits - 4096 "steeps") and use Allegro HALL sensor, not sure what model, but A1324EUA is recommended, cost less than $5.

Other good option is Honeywell SS495A1.

 

 

[ADorante]

Thanks sokol, that's valuable information!

 

Nice Johnny Red avatar btw.