Jocman

Update. Currently I'm totally blocked, as after a pause of 1 hour (gone gym, leaving the PC on with the cards connected), when I'm back I realized I was continuosly listening to the Win' sound "USB disconnected" alert...... And it happens every 10 seconds..... If I check the SIOC software, I can see that the card is connected / disconnected / connected / disconnected.... and so on. If I fisically disconnect the USB, the sound stops. What the hell is happening????? My OC card is screwed???? (hope not....) or there's something wrong with the PC's USB drivers ? (I don0t think, because all the pther external devices work fine.... Help....... Jocman

Thanks y2kiah. Unfortunately, I tried to test your suggestion, but it seems that BS doesn't see anymore my inputs. :( I don't understand what's happening: I run SIOC (by testing in SIOC the switches are working), but when I run BS, the cockpit switches don't move. But I didn't make any change to anything. Yesterday (when everything was working) I simply shut off the PC. today it seems as I did no work yesterday. What can I check??? EDIT: I made a test by deleting in ExportSupport.lua the definition for the cover+switch just added. Everything works now.... I don't understand why. I should write in such specific way the new code? I simply added the new string at the bottom of ExportSupport.Lua. Jocman

Ok, I found and error, I forgot the "," at the end of the line BTW, even putting the ",", it doesn't work. So the problem remain: How to make SIOC / LUA perform 2 actions with a single input (switch + cover using only 1 "2 positions" switch). Second...... how to manage "3 positions" or "X positions" switches???? I can't find anywhere something about those issues. Initially I was thinking about to use the function "Rotary Switches", but I don't think it can work. Any idea? Jocman

First problem....:( I'm programming a switch with cover. I wouldn't like to wast 1 input just to set the cover, so I decided to try only with the script for the switch. result: if I toggle the switch, the first time it opens the cover, then I've to toggle it off then on again to make the switch on. Then I tried to assign in SIOC 2nd variable to the cover, but putting as OC input the same as the switch (in my case the input is 0): [1] = {TwoPositionSwitch, 2, 1, 1} [2] = {TwoPositionSwitch, 2, 2, 1} As you can see, in LUA I changed only the second value I tested it, but it doesn't work (nothing happens) How can I tell SIOC / LUA to toggle both (cover and switch) when I toggle only my "real" switch? Thanks all Jocman

Ok guys.... I DID IT!!!!! :thumbup: :thumbup: My first OC card switch in perfectly working on BS!!!! Now it's time to start programming. Thanks Rocketeer for the hint, and thanks Oakes for his tutorial. I'll keep you informed during my "journey" Jocman

Thanks Rocketeer. I'll have a look to that, hoping to find some ideas. I'll keep informed. Cheers Jocman

Hi guys. It's about a week I'm getting brainstormed on how to make the OC cards interact with BS. I got my OC system, I prepared all the sample switches / buttons / rotaries / etc etc, but now I can't find out how to proceed. When I temporarely stopped my project (when I left to Kabul) I had more or less o complete overview on how to proceed. but this long long work-pause has been a disaster. i don't remember anything.... So the current situation is that I'm spendiong the last 3 evenings digging into my HDDs looking for some hint, so as surfing the net, but uselessly... Can anyone help me? I'd need to figure out again how to "build" the system, meaning: - I know that I've to program SIOC to drive the switches connected to OC cards - I know that in BS folder I can find the LUA files I need to get the variables I've to use (as clickabledata.lua) - I know that someway SIOC has to interact with Import/Export to LUA files. Can anyone describe me how to perform the tree points? I think (or better, I hope) I need only such an example (i.e. a simple switch) to study and understand how the system work, then I can proceed on my own. Thankyou guys for the help (I need it :helpsmilie: :helpsmilie:) Jocman

I fixed the problem. Now I can start working with OC cards and programming the switches Hopefully Jocman

Hi all. Well, today I started to program the OC cards. And I stopped... In fact, I planned to check BS about the types of switches inside the cockpit (2 positions, 3 positions, rotary, encoder, etc etc), lights and so on, reporting all those informations on some sketches I made (pratically, I printed out some draws I made for my cockpit). Then start with the programming of the switches, and every time check the results in BS. Problem: I started BS, choosing Mission > Shooting range (the cockpit is "cold and dark", perfect for my tests). Then I wait for the mission to be loaded. and I wait....and I wait....5 minutes...10 minutes....nothing, PC blocked. I press ctrl+alt+del; with the manager window opened, now I can see my desktop too, and I find an alert window: BS isn't responding, look online for a solution or quit the program. I quit, the BS shows me the end screen (as I did the mission). I asked DCS about, I'm waiting for an answer (anyway I'm using a laptop HP Pavilion dv7 - should be powerful enough - win7 home premium 64bit) But in case of problem (meaning I can't running BS), I'd need to ask some of you a big favour: I should send the PDFs of my sketches, then I need some of you to write on those sketches the various type of switches, buttons, etc, then send it back to me (I don't rememeber all the switches....). this way I can start with the programming. Ok, I can't test it, but at least I make all the preliminary work, then when I'll back to Italy (meaning: march) I'll test everything on my monster PC, then fix the problem. Can someone help me this way if DCS can't fix my problem? Thanks in advance to anyone Jocman

Well, guys. Finally, after a log delay (about 2.5 months) I started again with the build. The last 2 days I fixed all the cockpit displays. Well, it means that they light on (just tested with the check software), but I'm quite sure this part of the work is made. Starting from tomorrow, I'll begin with the build of some sample switch (every kind: rotary switch, level switch, button, push button, encoder), then when 'i'll be sure each sample works, I'll start with the programming of the functions. Always hoping that I can use all in BS.... Check six. Jocman

Hi Deadman. Unfortuntely the food isn't the best, but we're in a secondary Camp, so the food contractors use us to rescue the money they MUST use in the main Camp. BTW, we survive. i'm still waiting for an answer from you concerning the F16 belt; maybe it was a problem with my freacking IP, so or you didn't get my message or I didn't get your answer. Anyway can PM me about? Thankyou Jocman

Hi Guys, how is going life? I'm still alive, here in Kabul's Paradise. 2 months since I'm here....I'm triying to keep working on my cockpit (or, better, start working again), but my duty seems never end day by day.... Anyway, I hope next week to set the desk in my room so to put all the electronics concerning the cockpit on it, then start working with programming the functions. BTW, this long pause mined my brain, so now I've to get one more time the full mind-view of my cockpit, as I don't remember what I planned and how it had to work in my mind..... Hard days.... Keep in touch guys Cheers Jocman

Well, for those are interesting in my tales :) as my departure to Afghanistan paradise has been delayed (next week has to be the one, as I got yesterday the full equipment), I decided to drill another panel, before definitevely pack everything to my garage. So here you find the last product of my sick mind, just drilled and tested the switches / switch-guard effects. I'm pretty sure next post will come from Kabul. Cheers Jocman

Ok, here comes the last picture concerning the cockpit. I had to pack all for the long "duty pause". As said, during my staying in Afghanistan I'll try to start programming the OC cards (of course I can't bring with me the cockpit components to work on them). Jocman

Well, guys. Short update. 2 days ago I've been called up to join ISAF in Kabul Paradise. So in the next 10 days (if nothing changes) I'll leave to visit uncle bin laden. It means that my Ka50 cockpit's work has to be stopped untill I back home. Before leave, I hope to post some pics about the current status of making; btw yesterday I tested for the first time the OC system, only for the displays, but it didn't work, Maybe something wrong, I've to test again. Anyway, I think to bring with me some OC cards, some switches and other small stuff, so I'll try to start programming the switches during my staying there. Hopefully, I'll have the possibility to surf on internet, in that case I'll keep you informed. Jocman

Me too, I've a lot of them to run.... Jocman

Thanks all for the suggestions. Usually, I use to drill increasing the drill bit size. The biggest problem is that with small drill bits I use high spee, and the holes are really fine. But with the increasing of the drill bit size, it increases also the possibility for the bit to jam into the plexy, even with lower speed; rather, and paradoxically, with lower speed the bit jam very oft at the end of drilling.... That's the reason why I broke 3 panels. BTW, I have to say that my tools are not so specifics for those kind of works. Nevertheless, I'm getting good results. In the next days I'll post some other pics. Jocman

My Ka50 has been shot down before starting flying ;-) Just some "bugs" while drilling...... It's very hard to manage a thin plexy (2.5 mm) while you drill near the corners.... When you drill with small drill (3 mm) evrything's fine, but use big drills (> 5 mm) it's a big risk. And think that some holes require 12 mm drill (like the plates on the right side).... Jocman

Well, I "fixed" the problems with some epoxy glue...ok, not really an excellent job, but.... I started with assembling some electronics components. I should make some test with the I/O cards. I think I'll do it in this weekend, then 1 week holydays (I've to ...fly some other kind of .... aircraft), then I'll back with working on some other structural design. Plus the collective. Jocman

AAAAAAAARRRRRRRRRGGGGGGGGHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad: And not only those 2 panels......

Ok, I'm back. Lets go with self-critics.... It's not like the original, but I think that build exactly 1:1 it's almost impossible (well, depending on your budget, if I were uncle Bill Gates, I buy a real Ka50....) The original radio switches have been replaced with concentric dual rotary encoders (inner knob for units, outer knob for tens), and consequently I mounted 2 LCD displays. About the shape: the outer lines aren't straight, but I'm not so fine with this kind of work, I prefer the small precision work (I've not many patience to work on big pieces, but the smallers I love them - just have a look to the modded switches some posts up). And this is one of the small boxes, where I spent lot of time by hand sanding. if you see the bigger pieces (and the last pieces I made) you will kill me...I started sanding with the drill.....Yes, I know, it's a crazyness, in fact if you see the result.....:doh: BTW, I finished the boxes (I was very tyred of), even tough not perfects. I'm a little bit upset for that, but it was my decision, so.... Honestly, at this point I burn to fly with my Ka50 (can you belive I NEVER flew with it???), so I want to finish with the electronics, then I have to build the main structure where mount the panels, then work on the controls (I'm studying the collective structure - I have already one self builded - and how to kill and mod a Microsoft Sidewinder II FF joy for cyclic) Ah, I forgot: I'VE TO PROGRAM ALL THE I/O CARDS !!!!!!!:helpsmilie::helpsmilie::helpsmilie:(hoping they will work) I WANNA FLY!!!!!! Jocman

Well, guys, I hurry, so get this one. I'll post something to self-comment later: Jocman

THanks for the suggestions, but....too late. When I cut all the pieces, I planned to do it in about 3 weeks, so to check every piece. But, due some serious family problem, I hade only less than 1 week to cut all (I'm talking about more than 100 pieces), so I made a lot of mistakes. As I didn't have the cutting tools where usually I live, I had to "enjoy" just this little time. The result is that all the pieces have some "error". Well, I think if you check each box very closely, you'll see all the errors. but if you watch the structure in its whole, it seems fine. Honestly, the only cure should be cut the fake pieces (it means ALL) again, but I don't want...... Thw work is still long, I think I'm only at mid way.....maybe.... Jocman

Well, I'm going on. Im finishing the boxes: not really perfects, as I cut all the pieces by hand, so the lines are not so "lines".... Then, I found some errors in my measurements (i.e. some pieces 5 mm shorter), but I'm fixing on the ground (I don't want to cut again, too depressive....) I hope at the beginning of the next week to have all the boxes complete and start with placing the electronic components, and the labels. Then, painting and wiring the components. Then the backlinghting.... Damn, a lot of work still to do...... Jocman

Well, my 1st work disaster... I was trying to assemble the levelers controls (fuel and throttle), and, as they're curve surfaces, I tryed to bend the cover with a thermo gun.... It worked well, untill the first third, then......CRASH!!!! I've to recurse to B plan: metal.... BTW, I made some boxes, the DL panel, the radio panel, and the navigation panel. Ok, not totally made, but at least they start having some .... good look. Jocman