Duckling

Great mod and thanks Overpro. My old joystick card died on me and your mod and a Mega saved me. Pedals back in business again. only issue I had was that I initially used a 32 bit win7 for the configuration . Config and firmwareload was successful but my win7 -32 refused to find the downloadble driver for the Mega. After plugging it into the simPC (64bit), all works great. Cheers Gus

might be wrong but try shorten the name "OXY_Sys_FL_IND" to "OXY_IND" or likewise. Yes, sorry for that /Gus

Hi Torrorvogel Here is a .zip with stripped set of my current files. There are three files in total for Oakes scripts Note also SIOC Var numbers within has not been changed to reflect the thread above. (my installed path to the export folder is: "C:\FLIGHTSIM\DCS World\Config\Export") Within Export folder: "ExportSupport.lua" "SiocExport.lua" Folder: "SIOCConfig" with containing file "siocConfig.lua" # siocConfig.lua: -- list of exports of mainpanel.lua values gOxygenVolumeSIOCParam = 2002 -- 274 for example inputsTable = { [sIOC VAR] = {function, DeviceID, Arg, ...} -- [35] = {TwoPositionSwitch, 58, 20, 1}, -- PTR-INTERCOM-CALL ... ... myIndicators = { -- snippet of my indicatorconfig below -- [sIOC VAR] = {0, Arg} -- defined warning indicators in mainpanel.lua -- [1000] = {0,509}, -- WR_L_WNG_PMP 11 -- [1001] = {0,480}, -- WR_ENG_STRT_C -- [1002] = {0,513}, -- WR_L_MAIN_LO -- [1003] = {0,484}, -- WR_ANTISKID } gIndicatorTables = {myIndicators} # ExportSupport.lua: Functions called by the scriptfiles. # SiocExport.lua note the lines under -- HIGH important data such as: lSIOC_SendString = lSIOC_SendString..BreathFlowMeter(gBreathFlowMeterSIOCParam) corresponds with the lines under function LuaExportStop() such as: lSIOC_SendString = lSIOC_SendString..ResetSIOCvar(gBreathFlowMeterSIOCParam) In "C:\Users\<UserName>\Saved Games\DCS\Scripts\Export.lua: only lines within my one are: dofile ("./Config/Export/SiocExport.lua") dofile(lfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) -- you can omit this if not using DCS-BIOS Hope these will be of some help. Remember to make a backup of your files before start editing. Can't tell how many times it saved me from a disaster editing these :) Cheers Gus Edit: some spaces been added by the forum tools in text above so plese check the attached files Export.zip

Hi Terrorvogel I failed to export the oxypanel supply switch position (Device ID 40, button 1, 603) "SupplyOn". I'm off for several weeks but will be back to this when possible. I need the same type of function on some other panels You currently need a physical two pos switch to set the oxy Supply to On, for moving the data into SIOC. As far I can tell, it wount interfare with HELIOS setting, setting Physical switch to On will be reflected into Helios but not the other way around. Toggle the physical OXY switch again will set the Cockpit info to the desire state with the 'bad' to have to cycle the position to update the value if it's already in the desired position due to Helios update. There's also a 'Failure = OXYGEN_FAILURE_TOTAL' info from OXY system that could save the day but no idea how to access that if possible. In the real craft, not sure either how and if the OXY system works at all without power from the bus that powers the diluter system. Oxy kicks in somewhere around 10k if I recall correct and OXY mixture is dependent on air pressure/flightlevel from there upwards For a simple circuit/config, assuming you got your warningquad OXY_LOW Warning indicator already under "my indicators"/gIndicatorTables within siocConfig.lua say as [1035] = {0,487}, -- flag_OXY_LOW 1035 is SIOC Var named OXY_LOW for mainpanel.lua Arg 487 Below are some info that might be usefull meanwhile (i sincerily hope I got everything correct in all places ; -) . It's DCS:A10C export of the OXY Volume, OXY Pressure and 'Breathflow' gauge into SIOC VARs The last is the black&white flip/flopp indicator, nice but not suitable to drive you airpump. I'll incuded it if you like it for other handling. It cycle the SIOC VAR between 0 & 1 Connect your pump to Var 9605, name Oxy_Power, Link IOCARD_OUT, device 3, Output 0 // Opencockpits-USB-Outputscard Power-Relay (12V-to-220V) ON/OFF (Make a backup copy of your files just in case before starting but I suspect you had a bad impact earlier) --> EDIT: theres some spaces added into the text when pasted into the "spoils" sections below. They needs to be deleted to get it working) <--- Examples SIOC VARs can by used to as part of building some logic to controll the output port for the relay to the breathing machine. In ExportSupport.lua. paste the following: In SiocExport.lua Under function LuaExportAfterNextFrame() local lSIOC_SendString = "" Paste the following and under function LuaExportStop() paste the following: In siocConfig.lua paste the following above your "inputstable": In your SIOC .ssi file add/edit VAR: In siocConfig.lua (I havent checked that switch, omit last ",1" if not working ): [9601] = {TwoPositionSwitch, 40, 1, 1}, -- PTR-OXYGENCP-SUPPLY (Oxygen Supply On/Off)

Hi Terrorvogel. In current config without a physical switck connected on var 9601 there will be no trigger, oc cards/sioc reacts only on port state change. Workaround is to grab that state from dcs. Got several values parsed fron mainpanel.lua into sioc vars for futher handling but havent touched the oxy panel yet. I test and see if I can get it working. Cant't tell fore sure without checking but gut feeling is that the flow indicator gauge is a "flip/flopp" visual indicator on the oxy panel. In otherwords setting it to "on" will indicate the white area and off, the black causing the relay to constat turn on and off in sequence. Is that what you need ? ( could becwrong here and the "on" just starts the "breathing" on/off sequence) Hopefully have a few hours tomorrow evening to test Edit: disregard bad spelling above ;-) Cheers Gus

Simulated OXY system ? really cool, Not crazy at all. When possible, please elborate on that, need to read up on that type of breathing system. (Not for my rigg but one cold-warbird simpit under restauration) Lua export from mainpanel is a bit messy (for me) but doable but I think using the 'breathing' gauge might not work as expected since if flipping between between on/off so an additional timer is needed in sioc Can the OXY warning indicator be used instead to trigger the relay to drive the 'breathing' machine relay ? (Guess that you have the warning panel running, the OXY warning might fullfill that trigger value ?) i.e. something like this in SIOC stated under the OXY-Warning indicator: if oxy_warning = 0 AND OXY-Switch = 1 and Power_exist = 1 then BreathingMachine = 1 (start) if OXY warning = 1 then BreathingMachine = 0 (stop) edit: above if you need to have the machine air preassure static during usage. I assume you dont want to start/stop if with the 'breathing' sequence. You might want to check for a Oxy regulator system/panel in good condition. These are machanical (at least on Nato standard) and connecting the mask through that panel would likely trigger the on/of indicator also ? Cheers Gus

Extremly nice and clean setup X93355. Very well made /Gus

You're very welcome Think you should go Var 0000 { &LighAnticol_SW = 0 &LighAnticol_L1 = 0 &LighAnticol_L2 = 0 } It's the output ports that goes active by random on fresh start of SIOC (after poweron). On a restart of SIOC the database keeps erlier state of each Var. Pusching both outputports and switchstate to 0 would eliminate that you have the blipper goes active on SIOC Start. Might happen even so just by power on the IOCards ;-)

good to hear it works, always a bit 'scary' to make suggestions when I can't verify it first :) Var420 is the light and 421 the motor ? Why not use a 5V relayboard controlled by the cards ports ? such as http://www.ebay.com/itm/5V-1-2-4-6-8-Channel-Relay-Board-Module-Optocoupler-LED-for-Arduino-PiC-ARM-AVR-/222135332058?var=&hash=item33b84c2cda:m:mgnWPfoXCbjWi3z8ochdzrw just remember the fuse on the 12V line (I didn't first time : -) Trigger it from the regular switch on the panel like Var 0517, name LighAnticol_SW, Link IOCARD_SW, Device 5, Input 56 // SWITCH LIGHT ANTICOLLISION BEACON { IF &LighAnticol_SW = 1 { &LighAnticol_L1 = 1 &LighAnticol_L2 = 1 } IF &LighAnticol_SW = 0 { &LighAnticol_L1 = 0 &LighAnticol_L2 = 0 } } Good idea is also to initilize those outputs as "0" in Var0 so they don't starts automatic when SIOC starts Cheers Gus

Hi Terravogel. (hope this is correct, other are welcome to chime in o.c.) Each position of the 3pos switch above has an unique button ID (11-13) Activating position 1 (ButtonID 11), the sim expect an argument value = "0.1" and "0"when release Pos 2 (ButtonID 12) "0.2" and "0" on release Pos 3 (ButtonID 13) "0.3" and "0" on release the 'SimpleRotary' function (if it's same as I posted above) only parse the value (and neglect the ButtonID) [edit: the ButtonID is supplied from SiocConfig] If the switch in the sim always has to return to middle pos to be able to select another position, the following should work (if you can flip directly between 1-2-3 without going center it needs some additional SIOC code to set each VAR to '0' prior setting the new position) [Assuming DeviceID 40 on the your panel] Define three Vars (say 1331-1333, I nicked your earlier 1327) Var 1331, name TFSsensG1 // TFS Sensor Mon G1-G2-G3 selector G1 Var 1332, name TFSsensG2 // TFS Sensor Mon G1-G2-G3 selector G2 Var 1333, name TFSsensG3 // TFS Sensor Mon G1-G2-G3 selector G3 in SiocConfig: SiocConfig [1331] = {SimpleRotary, 40, 11}, -- EXTING-GROUPS-CTRL-01 [1332] = {SimpleRotary, 40, 12}, -- EXTING-GROUPS-CTRL-02 [1333] = {SimpleRotary, 40, 13}, -- EXTING-GROUPS-CTRL-03 In your .ssi/SIOC Var 1328, name TFS_GR1, Link IOCARD_SW, Device 5, Input 69 // TFS Sensor Mon GR1 EXTING-GROUPS-CTRL-01 { IF &TFS_GR1 = 1 { &TFSsensG1 = 2 } IF &TFS_GR1 = 0 { &TFSsensG1 = 1 } } Var 1329, name TFS_GR2, Link IOCARD_SW, Device 5, Input 66 // TFS Sensor Mon GR2 EXTING-GROUPS-CTRL-02 { IF &TFS_GR2 = 1 { &TFSsensG2 = 3 } IF &TFS_GR2 = 0 { &TFSsensG2 = 1 } } Var 1330, name TFS_GR3, Link IOCARD_SW, Device 5, Input 70 // TFS Sensor Mon GR3 EXTING-GROUPS-CTRL-03 { IF &TFS_GR3 = 1 { &TFSsensG3 = 4 } IF &TFS_GR3 = 0 { &TFSsensG3 = 1 } } Let me know the results. Allways fun to joggle my remaining gray.. Cheers Gus

Hi Terravogel. Looks like a three pos switch with a release value thats missing but can't say for sure. Possible eqv to the 10Cs "tempcontrol" switch. Below is for the 10C 3-pos switch on the env panel (working) but it's been a while since I made that. Check or post your switch function within your clickabledata.lua for some insight of the switch Var 0532, name ENV_CON_OPR, Link IOCARD_SW, Device 1, Input 121 // ENV_CON_OPR_AUTO { IF &ENV_CON_OPR = 0 { &ENV_CON_A_act = 1 } IF &ENV_CON_OPR = 1 { &ENV_CON_A_act = 2 } } Var 0533, name ENV_CON_HOT, Link IOCARD_SW, Device 1, Input 122 // PTR-ENV_CON_HOT { IF &ENV_CON_HOT = 0 { &ENV_CON_H_act = 1 } IF &ENV_CON_HOT = 1 { &ENV_CON_H_act = 4 } } Var 0534, name ENV_CON_COL, Link IOCARD_SW, Device 1, Input 123 // PTR-ENV_CON_COL { IF &ENV_CON_COL = 0 { &ENV_CON_C_act = 1 } IF &ENV_CON_COL = 1 { &ENV_CON_C_act = 3 } } Var 0538, name ENV_CON_A_act // ENV_CON_OPR_AUTO activate Var 0539, name ENV_CON_C_act // ENV_CON_OPR_COLD activate Var 0540, name ENV_CON_H_act // ENV_CON_OPR_HOT activate # within Clickabledata.lua (10C) elements["PTR-ENVCP-CABIN-AIR-COND-OPER"] = {class = {class_type.TUMB,class_type.TUMB}, hint = _("Air Conditioner MAN/AUTO"), device = devices.ENVIRONMENT_SYSTEM, action = {device_commands.Button_10,device_commands.Button_10}, arg = {285,285}, arg_value = {0.1,-0.1}, arg_lim = {{0.0, 0.1},{0.0, 0.1}}} elements["PTR-ENVCP-CABIN-AIR-COND-OPER-COLD"] = default_button(_("Air Conditioner to COLD"),devices.ENVIRONMENT_SYSTEM,device_commands.Button_11,285,0.2,{0,0.2}) elements["PTR-ENVCP-CABIN-AIR-COND-OPER-HOT"] = default_button(_("Air Conditioner to HOT") ,devices.ENVIRONMENT_SYSTEM,device_commands.Button_12,285,0.3,{0,0.3}) #SiocConfig.lua [538] = {SimpleRotary, 41, 10, 0.1}, -- PTR-ENVCP-CABIN-AIR-COND-OPER [539] = {SimpleRotary, 41, 11, 0.2}, -- PTR-ENVCP-CABIN-AIR-COND-Cold [540] = {SimpleRotary, 41, 12, 0.3}, -- PTR-ENVCP-CABIN-AIR-COND-Hot #Exportsupport.lua for reference function SimpleRotary(pValue, pDevice, pNumber) GetDevice(pDevice):performClickableAction(pNumber + 3000,(pValue - 1)/10) end Code above a bit rough but it works im my case. Hope it could be some help Cheers Gus

Hi Hans. Correct, sorry to say (allmost like rest of my RL currently ;- ) Working on a rebuild of my infra currently but timeline has expanded beyond plan Cheers B-O

Ooops, must have stepped on some toes there by posting a "wishlist" about viggen in the viggen thread.. My appologies.

@Mattebubben. Surströmming bombs still fall under highly classified material and should not be exposed in a public forum. i advice caution in here. Never know when Must interfere. Repricautions could me monumental (myself still struggling of the effect with close encounter with an old can years back....) And some more solid request.. @Letherneck: when (hopfully soon) presenting your 37 Module. Please make the Args for the module public avalible. No bigger issues if these get adjusted/edited during progress and version updates as long info is updated. Interfacing the module on either a homebrewed pit or in one of the few real pits we have here in sweden would be awesome. Same goes for defined viewports of instruments, avionics, rdr etc Cheers Gus

No correction from me but some caution. Using a surplus g-suit/pants is workable. I tried it ones in a sim and it sure adds to its purpose. A compressor with a subtank controlled vent working on g-force suit. But (and a big such).. these things aren't toys regardless in what form a suit or 'device' acting on produce pressure to the humen body, often on a non-so-well-trained-as-a-fighter-pilot and out of the real environment they are constructed for. I don't say not to use such, just be very carefull and keep the levels used at a minimum There's been at least one fatal injury with this kind of sim-setup.

You seen http://forums.eagle.ru/showthread.php?t=107733 ? Must be other threads here within also..

Good to review these "older" threads. Think i edited my files due to your post and it works great. Thanks vitabutch (2 years late though :- ) (Did a rep post but forum rules prohibited it)

Nice, looking forward to upcomming posts. Holding my thumbs that the "warpers" responds anytime soon. Both companies seems to have high regards for their fast and quality fixed support departments.

My guess, thrustmaster will be there. Availibility of tmwh set a few years up ahead will never be guaranteed If a statement of such is not issued by TM. If you aim for the tmwh, if not availible some will be on the second hand market but cost will be comparable with current judging from the cougar history. Despite the compititors, its the best cost/performance device on the market (my opinion). No need to feberish if you not having the funds for it anyway

Thanks Burnsy. True, and have had same feeling from time to time through the years but somehow can't get rid of it either the pit, urge or the bug so to speak. Slow pace and randow activities ;-) though. must be getting old. A good malt or a stout don't help either in the long term, tried that alredy Hang in there (here)

Looks great. After the tweaks are made and verified, any chance to buy a printed copy or 'lic' to make the print over here ?

ehurrmm, thanks Stelios. Now you make my blush (in true green NVIS light) @Ian: Thanks, can't beat that time to resolve, missed that totaly Cheers Gus

@Hans: Thanks. Good to now. Probably copy your setup or close to when time allow, ping you for some extra details then. (rearrange my MIP is first prio and will take some time). For the "second" version of the throttle as wrote, I just assumed that KLaFaille pics was just that. If that is DIY mod, it's a masterpiece.

Now that is real sweat ! Thanks Order inboud shortly. /Gus

Trying with best effort to read up on all the threads and found your throttle mod. Looks great. (made another approach but didn't work out as expected so I used my TMWH instead). Does your config and the linkage works ok ? Any issues found ? Looks a great bit more solid than what I did and a lot closer to the the newer version of the throttle