Jump to content

Duckling

Members
  • Posts

    606
  • Joined

  • Last visited

Everything posted by Duckling

  1. Well deserved. Looking great
  2. Thanks. Got it (think I do at least ;-) The "MagHold" possibility is only verified when actually trigger the logical On position and there's no easy way to export that value/state. If (thinking loud now) there's a, say Caution alert state that always occours while the Mag held is failed. It would be a an option to use that to trigger or deactivate the mag coil itself. I.e as long as "that" warning indicator is not stated as active, The Magswitch coil could be set to "hold" ? (physical switch). Quiz if so, if such condition exist and be defiened per each Mag Switch (YAW, AntiSkid, EAC),
  3. Hi Pollock56th. Can't tell the exact figure but to give a hint. Just the left and rightside panels I got have aprox 400 defined electrical inputs (combined numbers of pins of all switches, buttons, rotaries. The Throttle /Stick / CDU not counted). All the 3-position switches also have the mid pos calculated (not physical connected)
  4. Very impressive Gadroc. Question regarding the anti skid MagSwitch. Wouldn't it be possible to control the Off state by some other means ? Haven't digged down far enough to tell if other events is triggerd by a DC bus faliure (and in turn can be used to cut the coil power of the switch) might be an option. Emergency brake and the stick emergency lever will cut the switch and the Aux DC Bus energize it (just theoretical input from the flight manual). Says also that the switch may hold even if condition that causes the anti skid caution light comes on (as Gear down with antiskid in Off position) so that option is out. Got a real issue with my MagSwitches currently, the setup worked great during testing but now can't hold more then one mag at the time :cry:. Got a bigger P/S now with more Amps then in the testrig also. Troubleshooting ongoing. Currently have the MagsSwitches defined as toggled pushbuttons, first "to On" actives, second to "On" decativate ...). Cheers Gus
  5. Looking good Linden. (realy envy on the CNC :-) Gus
  6. Hi Niclas. I'd be in on at least one card (assembly if avaliable). Mail inbound shortly. /Gus
  7. Duckling

    HogBox

    Thanks Tornado.
  8. Great. They will be worth it, and time is not important. Also looked at the lastest pics you posted,. If possible , add a copy of the "fuelgate" lever switchknob Quiz. Would you like the "orders" sent or entered in some way to ease the administration ?
  9. Hi Peter That is a true piece of art. Very well made. You sure earned that "Grog", LOL
  10. Duckling

    HogBox

    Turn it belly-up and remove both plates and peek inside if not already. Easy on the cable connectors inside, they are easily broken. Toggles used by TM are flatpins soldered directly to the boards. Removing these with the crude tools I got is not an option, I'd risk the boards itself. Levers (L/R) are connected to pots in the base and the arm's not easily Modded without rendering the unit inop afterwords. The handles should be somewhat easier modified to fit either the real or an homebuilt base. Think it was Red that already made that and posted some pics of the process here somewhere. Laste part with the TM is a single board with connection to the L/G horn silence button so that easier removed. LASTE PCB connects to mainboard with a patchkabel only. After I "cut" the base and the bottom plate, they need somthing to hold'em together. I used a long M3 bolt here. Hope it can be of some help cheers Gus
  11. Duckling

    HogBox

    Hi Metal. Again. bad description from my side (having the kids run havoc nearby and dogs follow'em at same pace gets things a bit speeded ;-) Gray encoders I use has three pins. Middle goes to grund and the left/right pins connects to two consecutives inputs on the mastercard. Pin 39 & 40 in this case. In below example, SIOC Var "0050" get the encoder input from inputpin 39, and use the rotate function to increment/decr the Var 0049/VHFAM_CH_act by 1. (SIOC uses integer only, hence the conversion within exportsupport.lua) The lines below is to adjust the displayed value of the indicator itself to the Sim. (seen in the mirror, I should ofcouse used "ROTATE 0, 19, L0" instead to avoid the extra lines :doh:to adjust display settings) Var 0049, name VHFAM_CH_act // PTR-ANARC186-VHFAM-PRESET Var 0050, Link IOCARD_ENCODER, Input 39, Aceleration 1, Type 2 // PTR-ANARC186-VHFAM-PRESET_input { L0 = V0050 &VHFAM_CH_act = ROTATE 1 ,20 ,L0 L1 = &VHFAM_CH_act + 1 L2 = ROTATE 1 ,20 ,L1 &VHFAM_DSP_CH = L2 } Var 0049 is in turn feed back into Oakes scriptpack and it's here I hit the "wall". In siocSupport.lua ref is [49] = {SimpleRadioPre, 55, 1, 0.01, -0.01}, -- PTR-ANARC186-VHFAM-PRESET and "SimpleRadioPre" is defined in ExportSupport as: function Simple_radio_Pre(pValue, pDevice, pNumber) GetDevice(pDevice):performClickableAction(pNumber + 3000,(pValue-1)/100) end I got a hunch that the solution whould be to in SIOC test for incr/decr of the encoder, and in ExportSupport.lua grab the inbound string, Use LUA to calc either pos or neg value and push it into the sim. Just haven't got the process on how-to working yet :joystick: but getting closer (hopefully)
  12. Duckling

    HogBox

    Thanks Avi. Thanks. I very far from a C# guy... but longing to be there.. The trick I fail on, is to understand how to define how the value of the encoder in SIOC that define if the value increases or decrease. I'm a copy-cat to the bones, As long as I have a simular path I can follow I seem to get where I want (but make obvoius misstakes down the way, hehe). But you gave me an idea.- Encoder value here is taken only on one of the connected points. I'll try to get the other connection defined as an input and and see if that gets me going (i.e. pushing the negative value into clickabledata.lua (as you see here. i'm for out LOL) My VHF is slightly higher then real world but sure smaller then same shown in the SIM. Sorry for being unclear there. Check the pic attached. Left of comm1, I placed the real Lightpanel of the ARC-186 (partly overlays the IFF lower part)
  13. Duckling

    HogBox

    Thanks Feed ofouse but might missunderstand what you looking for. Is it the Throttle "cut" or the home made Laste panel ? (watch up for Laste plates that I have, these are a notch to "high" vs the real thing, can "remake" it if not found elsewhere)
  14. Duckling

    HogBox

    Hi Guys. Been fiddling with the leftside panel including the VHFs/UHF and got em somewhat operational. http://www.strandedduckling.com/HOGBOX_VHFs_20120310_1.jpg http://www.strandedduckling.com/LeftPanel_20120310.jpg I attach a subpart of the code below. Comments very welcome. I'm far from good at this and most is made by the try-and-error method. Slowly getting the pieces together. I'm sure there are much that can be made better, LOL All freq inputs incl channel select are gray encoders to a mastercard. Remaining is also to code the displays off when the radio is off. Other opt is to include the ability to save each preset channel in a SIOC Var to have it pop up when flipping the channel switch in PRE mode (not an option in the SIM but can be added through SIOC)... VHFs works as predicted as long as I "spin" each knob one way only, then the freq move one step at a time, Turning em the other way, the freq spins to the correct value but take a complete 360 degree first. In short I fail to findout how to code it correct ;-) Happy if someone can point out how to get the "singelstep" to work in bort inc and decr values from a grayencoder. UHF is on the way and needs some rework. Keeping each digit in the range 0-9, it works but going from 9-0 makes it sometimes go to 10,11 etc (within some frequency ranges and affects the "total" frequency) Same goes for the other way around. Not sure how the real UFC/ARC-164 makes this in reality or if it's a SIM issue. ? From siocConfig.lua: From ExportSupport.lua From SOIC.ssi "HOGBOX.ssi" in my case
  15. Hi DM. Just checked your thread and couldn't (allmost :-) belive it.. Can I add a request for just 2 copies of the ARC-186 channel select wheel ? That piece must be one of the hardest to find. Cheers Gus
  16. Hi Towsim. No SDK avaliable and depending on your requirement there are several options, Most based upon what hardware (intetface cards) u plan to use and if you plan to interface other sims outside DCS Check "Helios" from Gadroc for an exellent approach and Oakes script files for a more generic approach. The later is based on opencockpits/IOcard and SIOC database. Welcome to the djungel :-) Edit: sorry, misread your post (was entering a train :-) at the moment. Check PeterPs threads in above subforum and icemakers export utilities for some info. For sim engine interfacing, LUA exports is the only way I know
  17. Allways a struggle between accuracy and function, hehe. The ARC-186 size in 10C is distorted, can't say why but DCS probably had their reasons. The hight is "way" off. True lightpanel size is 122,6 x 53,6 mm. To get place for the compoment at hand I had to use 122,6 x 57,2 instead and it was a pain to get em to fit within that area :). Cant say about the base hight but it shouldn't be more then 1-1,5 mm higher then the lightpanel Will be realy intersting to follow your config/setup. Just started to interface/connect my quads to DCS and the coding stuff sure gives me headace :D
  18. Hi Metal. Can these templates for VHF-AM/FM radios be of any use ? http://www.strandedduckling.com/L10_COMM_All_v0.5.5.pdf I use Gray encoders for the freq selectors (leftmost is standard rotary though) and 7-segm displays. There's been some minor adjustments made (by hand) to get the pieces together but it ended up rather fine and close to the original. Check the "COMMs" under http://www.strandedduckling.com/html/quad_ref.html for a visual Got a matching .dxf files and an eagleCAD PCB file for the 7 segm displays (somewhere) if needed. (haven't yet connected the 7Segm to my pit though). Impressing video, thanks.
  19. A "HogViper" stick or maybe the other way around, hehe.. Great work and result DM ! Whats your plan for the base attachment of the stick, remove the original "fork" and building an adapter for a TM Hog base or make a home made base ? (edit.. or knowing you, you might already have the true "tub" ready... ;-)
  20. Hi Haggart. If you realy in for using LOMAC to control your viperpits (i'd recommend you to to viperpits.org instead for Falcon SW and add-ons).. Check "LoSioc" by Lecreole (sorry if the nick mispelled here). http://losioc.free.fr/ and http://losioc.free.fr/forum/ as a start. It integrate LOMAC, Opencockpits IOCard and SIOC to control your cockpit integration. Via SIOC there are some additional paths that might be very interesting for you. It might be the path you looking for. There is an English version of LoSioc avalible also Cheers Gus
  21. Looking good Strix !
  22. Rotaries and gray encoders (to a mastercard) now working great but I run into a problem connecting a 3 pos rotary that had a "missing" wire (had to cut down to save some ports) For you veterans here using SIOC coding I'm sure this is old news but to ease the task for next one entering the quiz... (same approch should be working also to generate 3 values out of a 3 pos switch On-Off-On switch, where middle position has no connection) Example here is the VHFAM Radio mode select Rotary (dev 55, knob 3): 3 pos rotary, with no connection to pin 1, the "OFF" position of the Mode switch. Pin 2 [Mode TR, input 36, Var 46] and pin 3 [Mode DF. input 37 Var 47]. Var 45 is the one forwarded to siocConfig.lua # In siocConfig.lua: [45] = {SimpleRotary, 55, 3} -- ANARC186-VHFAM-MODE # In sioc.ssi: Var 0045, name VHFAM_MODE_act // PTR-ANARC186-VHFAM-MODE_action Var 0046, name VHFAM_MODE_TR, Link IOCARD_SW, Input 36, Type I // PTR-ANARC186-VHFAM-MODE_TR set { IF &VHFAM_MODE_TR = 0 { IF &VHFAM_MODE_DF = 0 { &VHFAM_MODE_act = 1 } } IF &VHFAM_MODE_TR = 1 { &VHFAM_MODE_act = 2 } } Var 0047, name VHFAM_MODE_DF, Link IOCARD_SW, Input 37, Type I // PTR-ANARC186-VHFAM-MODE_DF set { IF &VHFAM_MODE_DF = 0 { IF &VHFAM_MODE_TR = 0 { &VHFAM_MODE_act = 1 } } IF &VHFAM_MODE_DF = 1 { &VHFAM_MODE_act = 3 } } Hope it can be of some help Cheers Gus
  23. Thanks for posting, Gremmlin. Was looking for Freq handling reference
  24. It woooooorks !!! I can't thank you enough, mate. It's so bleeding beautiful just to see these small LEDs blink. Absolutly wonderbaum I owe you big time my friend, Rep inbound and highly deserved. I finally see a future in my Rig, hehe (only made a preliminary connection soo far, have to rearrange the IOCards and install the P/S in the correct place. Will post the result in near future Cheers (and thanks again) Sorry for being a bit sentimental here but the feeling of getting it to work is super Gus edit: Sorry SuperBus. Unable to add rep to you currently, due to forum rules, will clear that debt in the future, hehe.
  25. :thumbup: Great work R1.
×
×
  • Create New...