Jump to content

AJS37 & input issues DCS-BIOS - ClickableData


outbaxx
 Share

Recommended Posts

Hi guys

 

I’m having no luck communicating with some of the devices in the AJS37 cockpit.

Usually I use the reference manual to set switches etc to see how they work but there are some things that won’t take inputs, just read outs.

Example:

AUTO_YAW_TRIM, 25, 3732, 211 doesn’t move the trim in the sim.

In clickable data it has instead of 211 a -666.

Can’t figure out what the -666 actually mean but there are more things that have -666 as arg number and they won’t make any input either.

 

So, do we anyone who got the Auto Yaw Trim working?

 

Best Regards

F

Link to comment
Share on other sites

Posted (edited)

The following inputs doesnt work for me:

 

definePotentiometer("AUTO_YAW_TRIM", 22, 3732, 211, {0, 1} --Takes input but not usable

definePushButton("MAX_G_RESET", 25, 3722, 175--No Response, should be Device22 but no joy either

definePushButton("BACK_ADI_CAGE", 25, 3720, 123,

definePushButton("COUNTERMEASURE_FAST_RELEASE", 22, 3001, 184--No Response, should be Device22 but no joy either

definePushButton("ROLL_CENTER", 22, 3305, 212,

defineToggleSwitch("CABIN_AIR_VALVE", 21, 3000, 398--No Response, should be Device18 but no joy either

definePotentiometer("DRYSUIT", 21, 3917, 396, {0, 1}

defineToggleSwitch("IGNITION_COILS", 5, 3918, 395 --{pressing this crashes DCS}

defineToggleSwitch("IFF_POWER", 21, 3000, 308

defineTumb("FR22_GROUP", 31, 3307, 360, 0.1, {0.0, 1.0}, nil, false, 

defineTumb("FR22_BASE", 31, 3230, 492, 0.1, {0.0, 1.0}, nil, false

defineTumb("FR22_MODE_SELECTOR", 31, 3110, 386, 0.1, {0.0, 0.5},  (FR24 actually)

definePotentiometer("TEST_MODE_SELECTOR", 18, 3913, 675, {0, 1} (shoulb be a rotary switch but its not?)

 

defineRotary("MAG_CORRECTION", 22, 3724, 1201 --rotates but doesnt seem to do anything?

 

defineRotary("ALT_SET", 22, 3306, 2005, --Fixed

defineTumb("IFF_CODE", 18, 3000, 309, 0.1, {0.0, 1.0}, nil, false,--Fixed

definePotentiometer("MASTER_VOL", 24, 3006, 399, {0, 1} --Fixed

defineRotary("CLOCK_SET", 22, 3801, 135, --Fixed

definePushButton("STOPWATCH_START_STOP", 22, 3802, 134 --Fixed

defineRotary("HUD_BRIGHT", 22, 3409, 9999, --Fixed

defineRotary("ALT_SET", 22, 3306, 2005, --Fixed

 

Anyone else had any luck with these?

 

Regards

F

 

 


Edited by outbaxx
update sorted
Link to comment
Share on other sites

Hi Outbaxx

You ahead of me here, I've had same issues on a few of the listed above on early testing but most not touched yet.

My environment is Oakes scripts and not DCS:BIOS, even if I use the LUA console for verification of LUA code

 

I'm currently on World O.B. and the device ID or Argument may differ between versions (haven't verified current std World  release yet) but I do found (read) that DCS:BIOS Branch code addresses FR22 as DeviceID 34 (within ajs37.lua latest) instead of 31 as in my version of O.B clickabledata.lua. 

Can't say if that point to the couse in your case but worth checking

 

I have the FR22 running happily on all but the Group and Base 'wheels' controls (those works but currently on on a step up/down basis)

FR22 Device ID 31.  SIOC Code below but almost the same.

(31, 210, 1 -> Sending a "1" to DiviceID31, Argument 3210 for the "knob 0"(code adds the base 3000 to each argument in my case))

LUA function pushes integer "1" to activate the buttons and "0" to release.  

 

(The disclamer is that if an additional "release state" follow the activation of the control, is required of the control I haven't found and verified that yet).
It do activate the selected knob in the virtual cockpit and release when other is pushed just as in the real FR22)

 

-- device ["FR22"]: Device 31
[20] = {TwoPositionSwitch, 31, 210, 1}, -- "Flight 0" needs release command
[21] = {TwoPositionSwitch, 31, 211, 1}, -- "Flight 1"  -- " --
[22] = {TwoPositionSwitch, 31, 212, 1}, -- "Flight 2"   -- " --
[23] = {TwoPositionSwitch, 31, 213, 1}, -- "Flight 3"   -- " --
[24] = {TwoPositionSwitch, 31, 214, 1}, -- "Flight 4"   -- " --
[25] = {TwoPositionSwitch, 31, 215, 1}, -- "Flight 5"   -- " --
[26] = {TwoPositionSwitch, 31, 216, 1}, -- "Flight 6"   -- " --
[27] = {TwoPositionSwitch, 31, 217, 1}, -- "Flight 7"   -- " --
[28] = {TwoPositionSwitch, 31, 218, 1}, -- "Flight 8"   -- " --
[29] = {TwoPositionSwitch, 31, 219, 1}, -- "Flight 9"  -- " --
[30] = {TwoPositionSwitch, 31, 200, 1}, -- "Channel H"   -- " --
[31] = {TwoPositionSwitch, 31, 201, 1}, -- "Special 1"   -- " --
[32] = {TwoPositionSwitch, 31, 202, 1}, -- "Special 2"   -- " --
[33] = {TwoPositionSwitch, 31, 203, 1}, -- "Special 3"   -- " --
[34] = {TwoPositionSwitch, 31, 204, 1}, -- "Minus"   -- " --
[35] = {TwoPositionSwitch, 31, 205, 1}, -- "Channel A/G"   -- " --
[36] = {TwoPositionSwitch, 31, 206, 1}, -- "Channel B"   -- " --
[37] = {TwoPositionSwitch, 31, 207, 1}, -- "Channel C/F"  -- " --
[38] = {TwoPositionSwitch, 31, 208, 1}, -- "Channel C2"  -- " --
[39] = {TwoPositionSwitch, 31, 209, 1}, -- "Channel D/E"  -- " --
[40] = {SUL37_MULTIPOS_SWITCH, 31, 307}, -- "Group Selector"  -- " --
[41] = {SUL37_MULTIPOS_SWITCH, 31, 230}, -- "Base Selector"  -- " --

 

 

Bottom two are currently INOP.

 

Pics on onging work on the real FR22, The panel/knob backlighting is a nightmare ...

 

Cheers

Gus 

 

FR22_1.jpg

FR22_2.jpg


Edited by Duckling

- - - -

Link to comment
Share on other sites

Hi


Hi Duckling

I actually fixed fixed the FR22 buttons earlier today by doing just that, I compared clickabledata.lua and my AJS37.lua and found that they differed.
That fixed some of the inputs above too.

I can get inputs to the Base/Ground selectors but it’s not usable, the inputs doesn’t match any logic steps for the wheels or potentiometers ie if I input a value of 5000 the result can be 15789 or 42543 or whatever :)

Awesome FR22 there, I hope you get the backlighting working, some of the panels use Electroluminescent panels don’t they? Not very user friendly for home cockpits though.

I’ll update the list above later tonight.

Regards
F
Link to comment
Share on other sites

2 hours ago, outbaxx said:

I can get inputs to the Base/Ground selectors but it’s not usable, the inputs doesn’t match any logic steps for the wheels or potentiometers ie if I input a value of 5000 the result can be 15789 or 42543 or whatever 🙂

Thanks

The glory of that goes to SAAB 😉 and the mechanic genius constructor of it. (Freq settings of the actual real thing on the "5-9" knobs setting is actual an individual  16 bit Ochtagol magnectic encoding of each 'embedded shaft'.. (will not be reused) and  the backlight internal cabling (not seen in the Pics) is only reachable by removing all mechanics and I sincerely trying to avoid that. Like opening a pandoras box

   

For the Base and Group commands as far I remember the result of performClickableAction, with an Argument value of "1" or "-1" steps these up/down one at the time, they are reversed to each other (One step up with "1" the other one step down, if I remember correct .

I can (could) force a 'multistep' action by a larger integer. Since the action in both real and virtual panel is a limited (1 <-> Max).

In theory that actually work as a oddie defined workaround (. Place physical contoller in lowest position , stepping down Virtual pit controller all the way to position "1" and a few more and the up again but there is now way to find if the interface missed a step vs DCS or not.

 


Edited by Duckling

- - - -

Link to comment
Share on other sites

On 3/20/2021 at 9:30 PM, BlackLibrary said:

an detailed error report would nice and i show what i can do to fix them.

The fixes above will be integraded in FlightPanel BIOS

 

I will try to show with an example, the Auto Yaw Trim:

 

The AJS37.lua:

definePotentiometer("AUTO_YAW_TRIM", 22, 3732, 211, {0, 1}

 

The clickabledata.lua (AJS37):

elements["PNT_211"] = default_axis_limited(_("Autopilot Yaw Trim"),devices.FLIGHTDATAUNIT, 3732, -666, 0.01, false, false, 1)

 

So when i use the control reference:

I expect to be able to set a value betwen 0-65535 and see the Auto Yaw Trim dial go to that position, but its not.

It rotates, to me, totally random, ie if i set 24500 it can be rotated right or left and if i set the same value again it rotates again.

In clickabledata it has -666 where most of the other has its argument number, dont know what -666 is.

 

Im not sure what else i can add, it just doesnt work as it is.

 

Best Regards

F

 

 

Link to comment
Share on other sites

On 3/21/2021 at 10:43 PM, BlackLibrary said:

i have understand it.

What i mean was:

gime all the names of the not working switches/functions and i will check them

 Ive updated post #2, red ones is the ones that doesnt work for me.

Regards

F

Link to comment
Share on other sites

ah ok must look if i can update this too. 

 

So far:

 

some not possible:

MAX_G_RESET - should work but button is not modeled

COUNTERMEASURE_FAST_RELEASE -not clickable so cant work in BIOS

CABIN_AIR_VALVE - clickable but no action in cockpit with mouse. with BIOS sound is heared

 

 

ROLL_CENTER i cant found were it is in pit. may you can help

 

DRYSUIT; TEST_MODE_SELECTOR - fixed

 

rest WIP


Edited by BlackLibrary
Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...