Duckling Posted September 9, 2012 Author Posted September 9, 2012 Heres a copy of current cabling file (excel). Allmost up to date :-)HOGBOX_WireSchema_v1.2_temp.zip - - - -
Duckling Posted September 13, 2012 Author Posted September 13, 2012 @Moken.. Was the answer above what you was looking for ? ... - - - -
Duckling Posted December 11, 2012 Author Posted December 11, 2012 Long time since last update... CDU finally made (or rather kinda in draft mode). Buttons and paintjob is worse then bad but it seems to work at least - - - -
Duckling Posted December 11, 2012 Author Posted December 11, 2012 Hehe thanks. But only if not looking to close It's way behind your standard quality ;-b - - - -
Hansolo Posted December 12, 2012 Posted December 12, 2012 Very nice work Duckling. How did you make such nice buttons? Thanks in advance. 132nd Virtual Wing homepage & 132nd Virtual Wing YouTube channel My DCS-BIOS sketches & Cockpit Album
Deadman Posted December 12, 2012 Posted December 12, 2012 Gus it does not look that bad drop me a line some time i sent you a pm but never got a reply I have some things for you :thumbup: https://forum.dcs.world/topic/133818-deadmans-cockpit-base-plans/#comment-133824 CNCs and Laser engravers are great but they can't do squat with out a precise set of plans.
Duckling Posted December 12, 2012 Author Posted December 12, 2012 (edited) Very nice work Duckling. How did you make such nice buttons? Thanks in advance. Thanks HMA, but I didn't ;-) They are OMROM standard with a selfmade adhensive stickers on top Squere ones are 9x9 mm, B32-1210 and round is B32-1600. They are avalible in different colors (last 2 digits on the id). They fit the OMROM Tacticle switches B3F-4050 (think the ID is 1,27N pressured), IF you go for these, be sure to select the more heavier 2,5N instead. Not sure about the iD there though, Gives a more distinct feel when used. Main issue here is the caps is not backlit and the switches has a footprint of 12x12 mm that forces an adjusted layout vs the real CDU. Note also the odd spacing between those that replace the rockers If I'd ever make this trip again I'd go for Multicomps TLL-62BG or likewise. They has a smaller PCB footprint and an integrated micro LED. There are round and squere keycaps in colored backlit versions in aprox the correct size. Hope it is of some help Cheers Gus Edited December 12, 2012 by Duckling - - - -
Duckling Posted December 12, 2012 Author Posted December 12, 2012 Gus it does not look that bad drop me a line some time i sent you a pm but never got a reply I have some things for you :thumbup: Hi DM and thanks. PM inbound. I seems to have f-d up when making the reply last time, sorry :cry: - - - -
Hansolo Posted December 13, 2012 Posted December 13, 2012 (edited) Hi Gus, Thanks a lot for the info. My homemade buttons are 10x10 with a foot print of 13x13 and have same issue as you with adjustment of layout. Secondly I am using prototype PCB with a pitch of 2.54mm which also calls for some adjustment. Anyway many thanks for the info. Will take it into account if trying to redo my CDU :thumbup: cheers Hans Edited December 13, 2012 by Hansolo 132nd Virtual Wing homepage & 132nd Virtual Wing YouTube channel My DCS-BIOS sketches & Cockpit Album
Duckling Posted December 13, 2012 Author Posted December 13, 2012 (edited) Hi Gus, Thanks a lot for the info. My homemade buttons are 10x10 with a foot print of 13x13 and have same issue as you with adjustment of layout. Secondly I am using prototype PCB with a pitch of 2.54mm which also calls for some adjustment. Anyway many thanks for the info. Will take it into account if trying to redo my CDU :thumbup: cheers Hans Hi Hans. I posted (jpeg only) the layout of the baseplate, overlay etc I used for my CDU on my site at http://strandedduckling.com/html/quad_ref.html#QUADRefCDUA10C They are spaced for a labboard with 2,54 mm pitch to provide space for all the switches. (Not a perfect work ;-) . Had'em cut out at a local company and they need some 'manual' adjustment to fit. If you like a copy in Visio or dxf format drop me a PM with your email. Cheers Gus Edited December 13, 2012 by Duckling - - - -
Hansolo Posted December 13, 2012 Posted December 13, 2012 Hi Gus, Many thanks for the offer. I do have a set of drawings in Aspire format since this is the program I use for generating g-code for the cnc. The set have been done so that I am putting the diode needed for Brydling's B256A13 card right on the labboard. Anyway I will take a closer look at the layout you have. Thanks a lot Have a very nice day. Hans 132nd Virtual Wing homepage & 132nd Virtual Wing YouTube channel My DCS-BIOS sketches & Cockpit Album
Duckling Posted March 2, 2013 Author Posted March 2, 2013 (edited) Been stuck in real life for some time but here's some progress at last Landingpanel, AHCP and the gauges on rightside. AoA and SAI remains to be interfaced. Clock is a 3" LCD. The UHF Freq display got an extra button for future use together with some extra digits. http://www.strandedduckling.com/Front_Left_Lower_side_01.jpg Pic of the Landinggear panel showing agrasyuks FlapGauge in place (Great work Anton, thx :thumbup:). http://www.strandedduckling.com/LNDGPNL_5.jpg Backside... http://www.strandedduckling.com/LNDGPNL_6.jpg Edited March 3, 2013 by Duckling - - - -
Hansolo Posted March 2, 2013 Posted March 2, 2013 Very nice indeed.is that a Honeywell magnetic held switch you have incorporated? Looks awesome Cheers Hans 132nd Virtual Wing homepage & 132nd Virtual Wing YouTube channel My DCS-BIOS sketches & Cockpit Album
Duckling Posted March 3, 2013 Author Posted March 3, 2013 Thanks Yes, its a Magswitch and Honeywell as far I know. Funny thing is I haven't give it a second thought until you asked. It's labled 'Microswitch Freeport Illinois USA, 5ET11' but the word 'Honeywell' is nowhere to be found ;-b - - - -
Deadman Posted March 3, 2013 Posted March 3, 2013 Its looking great Gus :thumbup: https://forum.dcs.world/topic/133818-deadmans-cockpit-base-plans/#comment-133824 CNCs and Laser engravers are great but they can't do squat with out a precise set of plans.
Duckling Posted March 26, 2013 Author Posted March 26, 2013 Slow progress (as always) on my Pit. Thought these pics would be interesting even if they not a "Home Cockpit" :-) I joined Västerås Flygmuseum a year back and now part of the team building our "new" Draken (J35-J) simulator. We got an earlier J35-C in action (together with a DC10 and a Convair Metropolitan) and the new pit will join the older to provide ability for either 'combat' or joined missions. Plan is to have new pit ready for display to the annual Roll-Out Airshow in May 26. More info will be posted in the link above including info for fligh-in etc. If you passing by you're welcome for a great day (and hopefullt great weather. If not , the simulators are operational ;-) Cheers Gus - - - -
Duckling Posted March 29, 2013 Author Posted March 29, 2013 The ladder extention button Been searching for a something look-alike or a cap usefull to mimic this 'button' but came up empty. Anyone that can help me out ? Best Gus - - - -
Duckling Posted April 6, 2013 Author Posted April 6, 2013 (edited) So... at last I got TACAN quad to work with SIOC. Credits goes to Oakes and Jockman and several others for building the codes to export data into SIOC Answer been 'here' since 2011 but I didn't grasp the context uptil now. Metal and Gadroc also stated what's needed to be done but I'm a true slow learner ;-) Thx guys :pilotfly: Quiz been how to handle the relative values AND negative inputs to clickabledata.lua via SIOC controlled by an encoder output Been stuck in the first part so long with with try'n errors efforts I'd almost given up hope of ever understand it but here it is if any other have the same issue Some garbage in the code below (as usual, but please ignore) Success came when allowing negative values in the SIOC_parse function AND used native encoder output, i.e toggling 0,1 and 0,-1 depending on CW/CCW rotation [Note: SIOC Version 4.0.1, DCS v1.1.1.1, DCS, Helios and SIOC combined with Oakes scripts.] Export from mainpanel_init.lua of the frequency of each digit + X/Y value to SIOC and parsed into a 7-segment display digit (with top and bottom segment disabled) '4' as 'Y' and an 'H' (digit 8 ) Encoder code to set the values from SiocExport.lua: .. function LuaExportActivityNextEvent(t) local tNext = t tNext = tNext + 0.2 local lSIOC_SendString = "" lSIOC_SendString = lSIOC_SendString..TACAN_window_wheel_hundreds(gTACAN_window_wheel_hundredsSIOCParam) lSIOC_SendString = lSIOC_SendString..TACAN_window_wheel_tens(gTACAN_window_wheel_tensSIOCParam) lSIOC_SendString = lSIOC_SendString..TACAN_window_wheel_ones(gTACAN_window_wheel_onesSIOCParam) lSIOC_SendString = lSIOC_SendString..XYwheel(gXYwheelSIOCParam) ...<snip> function LuaExportStop() local lSIOC_SendString = ResetIndicators(gIndicatorTables) lSIOC_SendString = lSIOC_SendString..ResetSIOCvar(gTACAN_window_wheel_hundredsSIOCParam) lSIOC_SendString = lSIOC_SendString..ResetSIOCvar(gTACAN_window_wheel_tensSIOCParam) lSIOC_SendString = lSIOC_SendString..ResetSIOCvar(gTACAN_window_wheel_onesSIOCParam) lSIOC_SendString = lSIOC_SendString..ResetSIOCvar(gXYwheelSIOCParam) ...<snip> From SiocConfig.lua (subset): ...<snip>.. -- TACAN Indicator IMPORT-- gTACAN_window_wheel_hundredsSIOCParam = 2100 -- 263 TACAN_digit_pos.hundreds gTACAN_window_wheel_tensSIOCParam = 2102 -- 264 TACAN_digit_pos.tens gTACAN_window_wheel_onesSIOCParam = 2104 -- 265 TACAN_digit_pos.ones gXYwheelSIOCParam = 2106 -- 266 ...<snip>.. -- TACAN Divice ID 51 [476] = {Encoder, 51, 1, -0.02}, -- PTR-TACAN-CHANNEL-SELECTOR-1 [479] = {Encoder, 51, 3, 0.1}, -- PTR-TACAN-CHANNEL-SELECTOR-2 [478] = {SimpleRotary, 51, 5, 0}, -- TR-TACAN-XY-BAND_SELECTOR [481] = {TwoPositionSwitch, 51, 6, 1}, -- PTR-TACAN-TEST [482] = {SimplePotentiometer, 51, 7, 0.1}, -- PTR-TACAN-VOL [485] = {SimpleRotary, 51, 8, 0.1}, -- PTR-TACAN-MODE ...<snip> hogbox.ssi ("aka *.ssi" from text export): Var 0474, name TCN_XY_act // PTR-TACAN-XY_BAND Var 0476, Link IOCARD_ENCODER, Device 1, Input 42, Aceleration 1, Type 2 // PTR-TACAN-CHANNEL SELECTOR-1_MHZ Var 0478, name TCN_XY_SEL, Link IOCARD_SW, Device 1, Input 48, Type I // PTR-TACAN-XY_BAND select { IF &TCN_XY_SEL = 0 { &TCN_XY_act = 1 } IF &TCN_XY_SEL = 1 { &TCN_XY_act = 2 } } Var 0479, Link IOCARD_ENCODER, Device 1, Input 46, Aceleration 1, Type 2 // PTR-TACAN-CHANNEL-SELECTOR-2 Var 0480, name TCN_CH2_TMP // Tacan Channel2 reference value for encoder spin direction calc Var 0481, name TCN_TEST, Link IOCARD_SW, Device 1, Input 45, Type I // PTR-TACAN-TEST Var 0482, name TCN_VOL_act, Link IOCARD_ANALOGIC, Device 1, Input 1, PosL 0, PosC 127, PosR 255 // TR-TACAN-VOL Var 0485, name TCN_MODE_act // PTR-TACAN-MODE Var 0486, name TCN_MD_OFF, Link IOCARD_SW, Device 1, Input 49 // TACAN_MODE_OFF { &TCN_MODE_act = 1 } Var 0487, name TCN_MD_REC, Link IOCARD_SW, Device 1, Input 50 // TACAN_MODE_REC { &TCN_MODE_act = 2 } Var 0488, name TCN_MD_TR, Link IOCARD_SW, Device 1, Input 51 // TACAN_MODE_TR { &TCN_MODE_act = 3 } Var 0489, name TCN_MD_AAREC, Link IOCARD_SW, Device 1, Input 52 // TACAN_MODE_AAREC { &TCN_MODE_act = 4 } Var 0490, name TCN_MD_AATR, Link IOCARD_SW, Device 1, Input 53 // TACAN_MODE_AATR { &TCN_MODE_act = 5 } Var 1220, name TCN_DSP_XY, Link IOCARD_DISPLAY, Device 1, Digit 0, Numbers 1 // TACAN_DISPLAY_XYBAND Var 1221, name TCN_DSP_ONE, Link IOCARD_DISPLAY, Device 1, Digit 1, Numbers 1 // TACAN_DISPLAY_DECIMAL Var 1222, name TCN_DSP_TEN, Link IOCARD_DISPLAY, Device 1, Digit 2, Numbers 1 // TACAN_DISPLAY_INTEGER Var 1223, name TCN_DSP_HDR, Link IOCARD_DISPLAY, Device 1, Digit 3, Numbers 1 // TACAN_DISPLAY_INTEGER .. Var 2100, name TACN_HUNDR // gTACAN_window_wheel_hundreds 263 former 3000 { IF &TACN_HUNDR = 10 // DCS exports gives an exported value of '1' in this vers if this digit is '0', Value * 10 in exprt raise it to '10' { &TCN_DSP_HDR = -999999 // blank } IF &TACN_HUNDR = 1 // DCS exports gives an exported value of '0.1' in this vers if this digit is '1', Value * 10 in exprt raise it to '1' { &TCN_DSP_HDR = &TACN_HUNDR } } Var 2102, name TACN_TENS // gTACAN_window_wheel_tens 264 former 3001 { &TCN_DSP_TEN = &TACN_TENS } Var 2104, name TACN_ONES // gTACAN_window_wheel_ones 265 former 3002 { &TCN_DSP_ONE = &TACN_ONES &TCN_CH2_TMP = &TACN_ONES } Var 2106, name TACN_XYWH // gXYwheel 266 former 3003 { IF &TACN_XYWH = 0 { &TCN_DSP_XY = 8 } IF &TACN_XYWH = 1 { &TCN_DSP_XY = 4 } } ExportSupport.lua ..<snip>... -- Used togheter with a for loop to extract Sioc parameters and their value from a string function SIOC_Parse(pSIOC_String) local i = -1 return function () i= string.find(pSIOC_String, ":",i+1) if i ~= nil then return tonumber(string.match(pSIOC_String, ":(%d+)=[+-]?%d+",i)) , tonumber(string.match(pSIOC_String, ":%d+=([+-]?%d+)",i)) end end end ..<snip>... -- TACAN_window_wheel_hundreds function TACAN_window_wheel_hundreds(pTACAN_window_wheel_hundredsSIOCParam) local lMainPanel = GetDevice(0) if type(lMainPanel) ~= "table" then return "" end lMainPanel:update_arguments() local lTACAN_window_wheel_hundreds = lMainPanel:get_argument_value(263) * 10 local lSIOC_SendString = pTACAN_window_wheel_hundredsSIOCParam.."="..round(lTACAN_window_wheel_hundreds)..":" return lSIOC_SendString end -- TACAN_window_wheel_tens DisplayDigit Export TO SIOC function TACAN_window_wheel_tens(pTACAN_window_wheel_tensSIOCParam) local lMainPanel = GetDevice(0) if type(lMainPanel) ~= "table" then return "" end lMainPanel:update_arguments() local lTACAN_window_wheel_tens = lMainPanel:get_argument_value(264)* 10 local lSIOC_SendString = pTACAN_window_wheel_tensSIOCParam.."="..round(lTACAN_window_wheel_tens)..":" return lSIOC_SendString end -- TACAN_window_wheel_ones DisplayDigit Export TO SIOC function TACAN_window_wheel_ones(pTACAN_window_wheel_onesSIOCParam) local lMainPanel = GetDevice(0) if type(lMainPanel) ~= "table" then return "" end lMainPanel:update_arguments() local lTACAN_window_wheel_ones = lMainPanel:get_argument_value(265)* 10 local lSIOC_SendString = pTACAN_window_wheel_onesSIOCParam.."="..round(lTACAN_window_wheel_ones)..":" return lSIOC_SendString end -- XYwheel function XYwheel(pXYwheelSIOCParam) local lMainPanel = GetDevice(0) if type(lMainPanel) ~= "table" then return "" end lMainPanel:update_arguments() local lXYwheel = lMainPanel:get_argument_value(266)* 1 local lSIOC_SendString = pXYwheelSIOCParam.."="..round(lXYwheel)..":" return lSIOC_SendString end Cheers Gus Edited April 7, 2013 by Duckling - - - -
Deadman Posted April 7, 2013 Posted April 7, 2013 Gus what do you need to know about this? PM me The ladder extention button Been searching for a something look-alike or a cap usefull to mimic this 'button' but came up empty. Anyone that can help me out ? Best Gus https://forum.dcs.world/topic/133818-deadmans-cockpit-base-plans/#comment-133824 CNCs and Laser engravers are great but they can't do squat with out a precise set of plans.
Duckling Posted April 7, 2013 Author Posted April 7, 2013 (edited) Started with the outer topmost quads on the the left'n right panels. Those angles are a challange :-) but I managed to get it somewhat near the intended position... still some way to go but rather pleased with the result so far (Should been made with Alu but was out of material and found sheet of Acryl.) Edited April 7, 2013 by Duckling - - - -
Duckling Posted April 8, 2013 Author Posted April 8, 2013 Gus what do you need to know about this? PM me Hi DM. PM sent. Please ping me back if not recieved - - - -
Duckling Posted May 5, 2013 Author Posted May 5, 2013 CMSP panel pieced together and now with an Arduino instead of the earlier OC LCD card. Running Gremlins script and with an VFD 16 digit display. - - - -
Duckling Posted July 2, 2013 Author Posted July 2, 2013 Just made the leap into the World version (v1.2.4) and after a some hours got Helios and SIOC working. Viewports and softTH setup not yet updated and the the few quads I tested so far seems ok. Even all the flightinstrument data exports works as far I can see. Much better then I feared :-) Only issue found so far is indicator output (warning displays etc) is erratic. They don't come on allways and when they do, they're static (non blinking prior master caution switch is clicked). My Sioc/export etc scripts from the earlier v1.1.1.1 not modified so 'something' in the new DCS structure is diffrent Is there anyone that have had same issues or has some ideas where to start the troubleshooting ? All indicators are Opencockpit/SIOC controlled, Helios is used for visual reference of instrument data (no other cards involved) Cheers Gus - - - -
Recommended Posts