C6_Hellfrog

information transmitted diffused... you will become very well known !!!!! :music_whistling::thumbup: link in cockpit section here :http://forums.eagle.ru/showthread.php?t=46582

@ toge : look this one just new from today : http://forums.eagle.ru/showthread.php?t=46579 :music_whistling::(:doh::mad::thumbup::megalol::helpsmilie::lol::huh: select the good item...

I think you didn't try it under Win 7, with 7 you can span your monitors with different resolutions and place one under the others. like in Oakes pit. / FPS are low although you have a very good rig with latests graphics cards and good OVC... EDIT : OK , I passed the NON Windowed mode, sorry... in that case you are right

any news ?

négatif Marc download en cours ... ftp://ftp2.files.eagle.ru/dcs/patche..._1.0.1c_FR.exe ftp://ftp3.files.eagle.ru/dcs/patche..._1.0.1c_FR.exe

bonjour , patche s: un nouveau choix en download : 101 C c'est quoi ce nouvel opus c après b (http://forums.eagle.ru/showthread.php?t=45407) ? :music_whistling:

Personnaly I never start with AC or DC, batt is enough, so it's just levers and RPM, more simple... a rutine in SIOC could do the job I think. And for reparation, levers down and RPMs down... or complete shutoff.

can you use -- Engines RPM from main panel LeftEngineRPM = 135 RightEngineRPM = 136 to test the electrical power : it appears to be sufficient to light many systems only above a certain value of engines RPMs no ? (to determine I didn't do that, just a suggestion...) /Hellfrog

no pb : mouses just dig holes in CP to make the pit ! :lol:

well, I'll develop weapons script this week and will post it, but I still haven't received SIOC card so I can't test it myself... and would be pleased if you could verify it and add it to your work. but with no card connected, I will have to let ouput values blank in SIOC...

no you should take by exemple, for SIOCCOnfig.lua EnginesIndicators = { [0011] = {0,163} } gIndicatorTables = {EnginesIndicators} for SIOC : if you connect like : The one of the Led pins will go to the #11 you should have : Var 0011, name L_EngStartValv, Link IOCARD_OUT, Output 11

for code in SIOCConfig look at Oakes answer here http://forums.eagle.ru/showpost.php?p=767589&postcount=21 about masterwarning lamp

sont regroupés dans cette discussion que j'essaie de maintenir à jour sur C6 ici http://www.checksix-forums.com/showthread.php?t=155723 / Hellfrog

For FRENCH USERS As not so many french users look at good stuffs here, I made a specific thread on C6 forums who linked usefull informations for SIOC , Oakes magnificient work, and so on, here : http://www.checksix-forums.com/showthread.php?t=155723 If you disagree with that, let me know... I advised people on 3rdwing who developed LSIOC Server and so on... but few or no feedback at this time... :( Pour les français, j'essaie de maintenir sur C6 http://www.checksix-forums.com une page qui recense les liens les plus utiles pour le developpement SIOC et LUA pour les cockpits BS http://www.checksix-forums.com/showthread.php?t=155723

because I'm french user and many people are interested in Touchbuddy, I Linked to your google code page on french forum C6 : http://www.checksix-forums.com/showpost.php?p=967907&postcount=34 If you disagree with that let me know, I'll remove.

fantastic continue the good work :thumbup: if you make a fully functionnal software to emulate gauges on second panels, you maybe will have as much celebrity as utilities for LO which made the same thing because many simmers don't have time or knowledge to achieve such a software... it will be very appreciated by the community I think !!! /Hellfrog

many thanks again, - I've found myself some infos since my last posts ::music_whistling: Rotary programmation in SIOC just like you answered with one Var linked to BS via InputTables and other linked to IOCARD_SW for calculations and logics - I've just understood :smartass: the logic behind your siocConfig.lua, thanks to your answer : I knew where to find infos, but did'nt realized relation between SIOCConfig.lua and these ones I understand SIOCConfig receive Inputs and Outputs adresses tables to link SIOC and BS and vice versa. I understand export.lua script is to create / concatenate strings before sending to, or after receiving from, SIOC I understand that with this birlliant work any process with the ability to communicate over TCP or UDP may exploit these strings. :thumbup::joystick::book: - For rotaries I wasn't sure about values : because of [color=black]GetDevice([/color][color=black]pDevice):performClickableAction([/color][color=black]pNumber + 3000,[/color][color=Blue][b](pValue - 1)/10[/b][/color]) values in SIOC ssi file are in units, (SIOC = integers only) and in decimals in lua files right ? With the same logic about values (integers / decimals) did you find this an absolute valid rule for ALL BS values in clickabledata.lua for arg_value eg arg_value = {[color=Blue]0.2[/color]}or is there exceptions ? :huh: For MasterWarning : - I understand you use One SIOC Var for lamp , linked to your OutputTable named gIndicatorTable, and now mixed in SIOCConfig.lua and another SIOC Var for the pushbutton, linked to InputTable in SIOCConfig again - No need to use other SIOC var in that case : :huh: - status of lamp is sent by BS via gIndicatorTable to SIOC and light the LED in pit - pushbutton pressed in pit is sent to BS by SIOC via InputTable like any button press - BS will synchronize lamp and button, no need to program that in SIOC : is this correct ?:huh: HOT Start vs COLD Start ? :doh: - did you have reflexion about a good way to know if you launch BS in cold pit or hot pit or inflight or at ground ? - how to know that with consistency form BS ? - what about the delay between launching mission and time everything is OK ? - and therefore it should be usefull to develop a Var 0 Value 0 SIOC script for initiating cockpit status on startup of BS mission... to have not to resynchronize - there is also the 'quick start' and 'quick shutoff' 'cheats' which may cause problem ? :megalol: Joke of the day : If Shakespeare had a cockpit project, he should have writen : headache or not Headache... that is the cockpit !

ballistics data settings selector + MastterWarning + SIOC code How to input this one ? I think it is the selector on back right panel, so like a rotary... If you stay with the below Inputtables.lua code // ("Unguided rocket and gun pods ballistics data settings selector") elements["PPK-NRAKS-PTR"] // [1223] = {TwoPositionSwitch, 12, 23, 1}, how do you implement it in SIOC ? Why not rotary as viewed ingame? / because of class_type.Tumb (see below clickabledate.lua extract) ? // {class_type.TUMB, class_type.TUMB} // action = {device_commands.Button_23, device_commands.Button_23}, // arg = {484, 484}, // arg_value = {-direction*0.1, direction*0.1}, // cycle = false, // arg_lim = {{0, 1.0}, {0, 1.0}} Will this SIOC code be correct for Weapons ? it's my very first attempt for weapons controls and I'm novice with ssi files // WEAPONS // // ("Master Arm") elements["MASTER-ARM-PTR"] // InputsTable.lua // [1201] = {TwoPositionSwitch, 12, 1, 1}, Var 1201, name MasterArmPushed, Link IOCARD_SW, Input XX, TYPE I // // ("External stores jettison") elements["PUI800-AVARCHOP-PTR"] // [1203] = {TwoPositionSwitch, 12, 3, 1}, Var 1203, name ExternalJettison, Link IOCARD_SW, Input XX, TYPE P // // "Weapon mode switch - Burst Length") elements["SR-PTR"] // values 0 0.1 0.2 // InputsTable // [1204] = {SimpleRotary, 12, 4}, Var 1204, name BurstLen, Value 1 Var 9991, name BurstLenShort, Link IOCARD_SW, Input XX, Type I { IF &BurstLenShort = 1 { &BurstLen = 1 } IF &BurstLenShort = 0 { &BurstLen = 2 } } // BurstLenMedium is (NOT (BurstLenShort AND BurstLenLong)) so no need for a Var Var 9992, name BurstLenLong, Link IOCARD_SW, Input XX, TYPE I { IF &BurstLenLong = 1 { &BurstLen = 3 } IF &BurstLenLong = 0 { &BurstLen = 2 } } // // ("Manual/Auto weapon system control switch") elements["PUI800-AUTO-PTR"] // [1205] = {TwoPositionSwitch, 12, 5, 1, 1}, Var 1205, name WeaponAuto, Link IOCARD_SW, Input XX, TYPE I // // ("Cannon round selector switch HE/AP") ["PUI800-OFBR-PTR"] // [1206] = {TwoPositionSwitch, 12, 6, 1, 1}, Var 1206, name GunAmmoTypeHE-AP, Link IOCARD_SW, Input XX, TYPE I // // ("Weapons Control system") elements["SUO-PTR"] // [1218] = {TwoPositionSwitch, 12, 18, 1}, Var 1218, name WCS_On, Link IOCARD_SW, Input XX, TYPE I // ("Weapons Control system Cover") elements["SUO-PTR"] // [1219] = {TwoPositionSwitch, 12, 19, 1}, Var 1219, name WCS_Cover, Link IOCARD_SW, Input XX, TYPE I // // ("Cannon rate of fire setting") elements["MT-PTR"] // [1220] = {TwoPositionSwitch, 12, 20, 1, 1}, Var 1220, name GunROF, Link IOCARD_SW, Input XX, TYPE I // // ("Expedite emergency ATGM launch") elements["MASTER-UNLOAD-PTR"] // [1221] = {TwoPositionSwitch, 12, 21, 1}, Var 1221, name ATGMJettison, Link IOCARD_SW, Input XX, TYPE P // // ("Jettison arm mode - arm fuse/disarm fuse") elements["MASTER-EXPLODE-PTR"] // [1222] = {TwoPositionSwitch, 12, 22, 1}, Var 1222, name FusingJettison, Link IOCARD_SW, Input XX, TYPE I // What to do more from this start about MasterWarning SIOC script ? ("Master Warning") Values for multipos switches and lights (MasterWarnings in lua) are | Button is | Pushed | Not Pushed | | .... On ...| .. 0,3 .. | ... 0,1 ......| | .... Off ...| .. 0,2 ..| ... 0,0 ......| InputsTable.lua is or may be // [1201] = {TwoPositionSwitch, 12, 1, 1}, // [1201] = {SimpleRotary, 12, 1}, <-- which one is better ? Your opinion please about below code => Var XXXX, name MasterWarning_ArgValue // read from BS { IF &MasterWarning_argValue = 0 { &MasterWarningPushed = 0 &lamp_MasterWarning = 0 } IF &MasterWarning_argValue = 1 { &MasterWarningPushed = 0 &lamp_MasterWarning = 1 } IF &MasterWarning_argValue = 2 { &MasterWarningPushed = 1 &lamp_MasterWarning = 0 } IF &MasterWarning_argValue = 3 { &MasterWarningPushed = 1 &lamp_MasterWarning = 1 } //[indent] [i][color=Navy] // Or we can consider // &MasterWarningPushed is 2d bit of &MasterWarning_ArgValue and // &lamp_MasterWarning is 1st bit of &MasterWarning_ArgValue // is this exact or not ? // is there a more efficient way of coding working on bit ? [/color][/i][/indent] // } [indent][color=Navy][i]// below Vars are numbered with device arg and param arg values : 1201 = device(12) element(01)[/i][/color] [/indent] Var 1201, name MasterWarningPushed, Link IOCARD_SW, Input XX, TYPE P // Input from Pit, MonOff pushbutton, sent to BS Var 0044, name lamp_MasterWarning, Link IOCARD_OUT, Output XX // output from BS device(0).parameter(44) and Outpout From SIOC to LED in Pit / Hellfrog

you're a prince Mister ;) for beginners, a modified mainpanel_init.lua file somehow shortened to find easily and quickly values and names for BS main panel lamps, controls and so on... _BS_mainpanel_vars.zip

Hi, from Hellfrog to Oakes 1st question : I don't understand your files here : - in weaponsInterfaceIndicators.lua : why don't you have Device ID = 12 for Weapons panel ? so that : "[330] = {12,437}," ? - in dataLinkIndicators.lua why don't you have Device ID = 25 for DTL panel ? so that : "[344] = {25,17}," ? why 0 ? 2d question : What are the differences and how to adapt inputtables.lua and sioc code for these three different buttons : type = TUMB action = {device_commands.Button_1, device_commands.Button_1}, I suppose : (pushed, then on, then off only if released ?) type = TUMB action = {device_commands.Button_1), stop_action = {device_commands.Button_1}, I suppose : (pushed, then on, then push again then off) type = TUMB action = {device_commands.Button_1, device_commands.Button_1}, stop_action = {}, I suppose : (pushed and released once at a time ? even if maintened ?) How to input this button ? ("LWS self-test button") elements["L140-CNOB"] -- {class_type.BTN} -- action = {device_commands.Button_3}, -- stop_action = {device_commands.Button_4}, ? I suppose creation of 2 interrupts for SIOC : -- [3603] = {TwoPositionSwitch, 36, 3, 1} -- [3604] = {TwoPositionSwitch, 36, 4, 1} How to input this button ? ("CMD Select Left/Both/Right board flares dispensers") elements["UV26-BOARD-PTR"] -- {class_type.TUMB, class_type.TUMB} -- action = {device_commands.Button_1, device_commands.Button_2}, -- arg_lim = {{0, 0.2}, {0, 0.2}}, ? I suppose create 2 interrupts for SIOC : -- [2201] = {TwoPositionSwitch, 22, 1, ???} -- [2202] = {TwoPositionSwitch, 22, 2, ???}

look at that page if you are interested on the motion subject : http://www.rogerdodger.net/motion/maacs/maacs_home.html and explore the links on it :smilewink:

natural field of view before 3D => 3 screens 2D:pilotfly:

my two cents http://forums.eagle.ru/showpost.php?p=764486&postcount=30

I made a compilation between devices.lua and clickbledata.lua to help developping for SIOC -- A file intended to help programming SIOC interface to build cockpit for DCS-BS -- in stock BS folders you find -- \scripts\aircrafts\ka-50\cockpit\devices.lua which is sorted by devices index -- \scripts\aircrafts\ka-50\cockpit\clikabledata.lua which is sorted by panels organisation in cockpit -- to build a cockpit using OpenCockpit interface cards and SIOC software you need to know devices index for each button -- I was bored searching in clickable data.lua and devices.lua so I made this compilation -- This file is a compilation from \scripts\aircrafts\ka-50\cockpit\devices.lua and clickabledata.lua -- in which each button is sorted by is index number, all buttons are grouped by device index number. -- type of button and arguments are copied also to help programing SIOC -- I hope forgot nothing but fastidious to verify... so if anyone find errors ... feel free to post a comment for edition and correction -- IMPORTANT : don't paste this file "as is" in BS folders... it ain't work that way ... -- I named it ".lua" because of syntax color in Notepad++ the editor I use, it's easier to read and edit ! -- Hellfrog @ C6 french forums SIOC_BS_help.zip

thank you very much, :) in the name of all SIOC non pro users, your work is very time saving for us, and your explanations very clear. :thumbup: