Jocman

Hi guys. I made some try. The hardware is fine (the classic arduino blinking sketch works perfectly). Tried to change led (using the gear nose down) and even the switch (gear lever): The lever gear works, the led doesn't. Tried even the Interactive reference (my first time). after watching the video and started socat then DCS, I don't see any sign of life as in the video (the metadata flux....). Anyway, by toggling the refernce switch for the master caution, i can see the sim master caution working, but, as before, no sign of life from the linked led. For the sake of honesty, I'm starting with the BIOS test on my laptop running DSC World 1.2 (it cannot run higher versions), as the "monster" PC is still not available (i don't know how long it will take). I hope this won't be the issue, but in case: it can be?

Hi Han. Changing the pins as you suggested worked but partially. Once again, 50%, only the Button is working, the led doesn't. I tried by swapping the led polarity, but nothing. Even the onboard led gives no sign of life. It can be possible the led address is wrong in dcsbios reference? cause I tried by pressing the front panel's lamp test button, but no response. (BTW, when wiring arduino I've been using the "easy" scheme iI found in the forum, but allegedly is clearly wrong (see attachment) . I'll provide a custom scheme from the official Nano one.)

Hi. Han First of all thanks for your support. Attached you find couple of pics: the wirings (sorry, I quickly remade it today in my office - and I tested again in DCS, with no good results....), and a screenshot where you can see socat stucked (sorry, the system is italian Language) /* Tell DCS-BIOS to use a serial connection and use interrupt-driven communication. The main program will be interrupted to prioritize processing incoming data. This should work on any Arduino that has an ATMega328 controller (Uno, Pro Mini, many others). */ #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" /* paste code snippets from the reference documentation here */ DcsBios::Switch2Pos scMasterCautionBtn("SC_MASTER_CAUTION_BTN", 15); DcsBios::LED scMasterCautionLed(0x1814, 0x0800, 16); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } The code is the standard master caution example, just updated to match Ka-50

Hi all. After reading all the posts concerning the general discussion, and the documentation, yesterday evening I did my first attempt with the classic MasterCaution sketch loaded on my arduino NANO (chinese). As I'm interesting in Ka-50, I modified the command lines to match the aircraft, with the following: DcsBios::Switch2Pos scMasterCautionBtn("SC_MASTER_CAUTION_BTN", 15); //use pin D12 DcsBios::LED scMasterCautionLed(0x1814, 0x0800, 16); //use pin D13 Started SOCAT, then DCS and started an instant mission Well, the button works (I can see in the cockpit the button moving, and in socat I get the messages about the command), but the led doesn't..... Damn.... well, 50% is better than nothing. Today, I modified the circuit, in order to use only the built in led (pin D13) so to be sure no issue about the polairy (in other words, I justy took away led and resistor...), but this time nothing works at all, the button neither... I tried several time to recompile and load the ino file, changing pin over pin, deleting the line concerning the led and keeping only the one for the button... Again, if maybe the button got faulty, I simply shortcut gnd and the pin directly.... Nothing, nothing, nothing..... I've seen now SOCAT keep being in such an....idle state (waiting since 2-1-0 second. press a key to continue), but DCS does'n give any sign of life.... Help?

Kyrmy, I don't know how to give you an answer (maybe out of my range of electric/C++ knowledges), but I've seen something similar to your layout here: http://www.instructables.com/id/FSX-Boeing-737NG-Lights-overhead-panel-Italian-ver/ (I think there's an english version of the post) Have a look, maybe you find something usefull to you (and if you will share I appreciate) Andrea

Hi all. Following my dream to build my cockpit, and thank to Ian for his outstanding creation (btw, by now good luck for your forthcoming issues, waiting for you back), and assuming that: - I'm not a programmer - I'm not an electronic engineer I'm keeping learning DCS-BIOS to manage such....building strategy. As my knowledges aren't enough to let me manage a...perfect system as the most of you, and as (unfortunately) there's no a "dummies guide to the cool cockpit" (but if I success maybe I can think about write one....), reading the Tekk's post about the use of matrix to drive btn, enc, etc etc, I made some math about the devices (switche, btns, etc) to drive, and I got the total of 359 pins needed (hope my maths are right) - I'm not considering LEDs or displays. By considering the "matrix theory", and using a Mega, using a matrix 21x21 will give me 441 "pins" to connect switches, buttons and encoders. Manage more boards via RS485 is (by now and for long time away) out of my science, even if I suppose it's the best (and right) way to build the system (otherwise none of you will "waste" time on that issue) But in my sick mind, this way a mega could drive all the inputs (even the pots), a nano with max7221 could drive all the LEDs, a second nano (or a third one) with Max7221 could drive the 7seg displays for autopilot, radio, etc. This means use 3 usb devices, plus the joysticks My question is: It can be done? not considering the "wiring" issue (I know, it would be a mess...), but the system designed this way could work? I know it's a stupid question, otherwise I should have found some post about (I'm still reading the DCSBIOS discussion - 40 pages on 85 red...), but I didn't find none using this kind of approach. Thanks Andrea.

Ops you'right I was keeping looking for it at the top..... It was very frustating Thanks... Andrea

Hi all. I started studying dcs-bios' objects (don't know if it's the right denomination). I noticed something i can't understand. Considering the upper left side of the overhead,the 2 4-ways switches for the lights and wiper The 4 positions are OFF-10-30-100 and OFF-LOW-MED-HIGH So i'd use a 4 positions (allegedly a rotary one) and 3 pins(if none is switched,the only possibility is the off position,right?),but the reference report a 5pos and 5 pins used. There's a specific reason for that? Thanks Andrea

Maybe a stupid question, but.... It's about 10 days the forum interface switched from english to russian Language...... How can I switch it back to english? I can't find the setting..... Thanks

Well BaD,not really double post. Here i asked some info about dcs-bios, and there for the monitor. Actually,there's already my post about the making of my cockpit,but it's very old,don't know if it is allowed to reopen (or better keep writing) the old one. Most forum don't like to rescue old post, but if not a problem to the community,i'll keep writing the old one (so i continue the story....)

Hi BaD. Honestly? indeed it's YOUR the guilt of my madness!!!! I started with my intention of build the cockpit when I red your posts ...yes about 10 years ago. Long time is past, lot of unexpected life issues, and so on, to delay my wishes. You and your work will remain one of my pillars in this tale. Unfortunately simulatoregp seems to me not active since months, and his posts on BS cockpit have been decimated. So, right now (I'm sorry for that) I note you use a TV in the front panel for the gauges (I've been always sure they were 2 monitors.......): what dimension is it? About the VR: yes I'm pretty sure the immersion is really awesome, but the feel to see and touch your switches is priceless. Maybe in the next future VR will implements even such touch-devices..... By now I'll keep the idea of a phisical pit.

Hi all. I started thinkering about the dimension of the monitors to reproduce (helios or similar) the gauges-abris-shkval At the end (if I'll get to the end....) I would like to have 3 monitors for the scenaries + the ones I need for gauges etc About the last issue, I'm considering 2 possibilities: 1) 3 monitors (2*22" for the gauges+abris and 1*8" touch for the SHKVAL), so in total I should manage a total of 6 video out 2) Somewhere (I don't remember where) time ago I red about the fact that the TV LED could be the best solution for the gamer, because the new generation of TV could support the graphic needs of the modern videogames. Thus, I'm considering to use a TV 40" to cover the full area of the front panel and all the gauges-abris-shkval (but I'll lose the touch screen-not a big issue btw). The pro is to manage only 4 video out As I've to re-design the front panel structure (I've realized I made some mistakes in calculating) it could be very helpfull to me to choose the right (or the best) solution What do you think about? Thanks Andrea

Hi all. After long (long long....) time, I'm back working on my Ka50 cockpit. When I stopped my work, I was working on programming via LUA and SIOC my OpenCockpit cards (the software side was at 90 %) In these last years, DCS BIOS is born, and as I red it has lot of possibility more than the OC system, so I'm quite tempted to restart (sigh) with it. Maybe I'll keep only the LED management with the OC card. It worths to switch to DCS BIOS? There should be a little bit difficult to someone without programming skills due the need to implement devices (such segment display and so on) and build a working RS487 network. At the time of my last work on DCS, I was using the vers. 1 patched. BTW, even if I left the project and the simulation for so long time, I got BS2 (but never installed) when it was in pre-order. Now, considering that the vers 2 must have lot of better features (or not?), I don't know if the core structure is changed so to defeat all my past efforts to understand LUA and program the OC cards: will they work with BS2? If not, the obvious answer to the first question could be YES (as I should restart all) Andrea

Ciao a tutti. Dopo un "po'" di tempo di assenza (che non quantifico per decenza) dal forum e dall'attività simulativa, mi ha fatto piacere vedere una sezione in italiano (Se non altro perché a volte è difficile spiegarsi per bene nella lingua d'albione). Comunque, a parte questo, mi sono deciso a ritornare perché dopo la pausa mi sono detto "Cacchio, cerchiamo di completare quello che abbiamo iniziato!". Quello che mi interessava (e tutt'ora mi interessa) è il Ka50, con tanto di cockpit (o almeno l'idea all'epoca era quella). I mezzi sono aumentati, all'epoca arduino era solo un promettente possibilità, mentre adesso DCS-BIOS apre molte porte (ma anche finestre, portoni, etc). Alla luce di ciò mi sembra obsoleta la soluzione che avevo all'epoca, cioè usare delle schede OpenCockpit per gestire tutti gli switch e i led. Alcuni mesi passati a capire la logica della programmazione, l'interazione tra LUA e SIOC, e alla fine il 90% di quelli che erano gli interruttori (o riconducibili ad essi) funzionante. Rimaneva la struttura (pannelli e quant'altro), di cui feci solo qualche (striminzito) prototipo. Fino al momnento in cui tutto, per una serie di circostanze, finì nel dimenticatoio. Fino a qualche settimana fa..... Dopo questo sproloquio, veniamo al dunque. Dovendo....ricominciare, avrei bisogno di alcune informazioni per colmare le lacune accumulate. 1) Tutto ciò che avevo programmato per le interfacce era basato su BS1, anche se avevo acquistato anche BS2 quando uscì. dovendo riprendere tutto in mano (purtroppo oserei dire da zero) mi conviene resettare tutto e cominciare direttamente da BS2? sembra una domanda stupida, ma in realtà la problematica riguarda la struttura delle due versioni: le mie schede erano programmate su BS1, e non so BS2 in cosa differisca a livello di programmazione. Sapere di poter eventualmente riciclare almeno il controllo dei LED sarebbe cosa non da poco) 2) Poiché DCS-BIOS sembra un gran sistema (anche perché mi permetterebbe di fare ciò che le OC non mi consentivano) tendenzialmente tenderei a "ricominciare" con questo. Ma a differenza delle OC (che era un sistema commerciale apposito) DCS-BIOS richiede una buona conoscenza se si vuole fare qualcosa di buono (tipo gestire la comunicazione RS-485, programmazione, etc etc). E in questo non sono ferrato. Per cui mi sarebbe molto utile una mano, ma anche 2 (ebbene si, è una richiesta di supporto tipo cane guida per ciechi.....) Oltre questo, domande ce ne sarebbero tante, ma eventualmente ci sarà tempo. Grazie a tutti Andrea PS: se qualcuno è curioso, questo è il mio post dell'epoca: http://forums.eagle.ru/showthread.php?t=50071

Yep

Guys,the reason is almost easy: i've win7 64,why to buy another os to use it?

Well, still having trouble with migration to SSD.... I put win 7 64 on it, so to finally use all my ram (12 Gb - till today I had 32bit OS). No way to make the audio work.... I know, my system is quite....old: I own a Asus P5A board with AMD Phenom The audio is provided by a SupremFX X-Fi board (such "embedded" with the MB). I got the system in 2009 and I'm still happy how it works. If I mount my old HDD with 32bit OS everything work fine; that's meaning the hardware is working. So the problem MUST be such a driver issue with 64bit OS. "Obviously" Creative discontinued the board and with it the support (their solution is such "it's your problem, not my") I found several 64bit audio drivers (Realtek, ausus....), installed all of them but nothing.... Audio's still dead..... Among thousand of curses, I'm also thinking about upgrade the system (ok, it's euphemism: upgrade my system means get ALL - well maybe not the SSD - and that means lot of money). But before access to my wallet, i would like to fix the problem. Any help / suggestion / similar ? Thanks Andrea

Yep,i'm talking about black shark I know is...dead since v2 has been released My only doubt was not wich one is better (ofcourse v2 must have.improvement);i was just wondering about the developing of a home cockpit,as the cards programming with bs1 has been quite...challenging to me,and start eventually from the beginning with bs2 won't make me happi

Well, I could install both versions, then see what happens BTW, honestly I don't see such difference between HDD and SSD, right now. On HDD there's 32bit system, software installed and so on, and it starts in about 25 - 30 seconds, boot included (really, is very fast) Now on the SSD there's 64bit system and nothing else.... and it starts in 15-20 seconds, boot included.... (I've installed a disk rack so to change hard disk and switch between my old system - I still use some software - and the new SSD) Well, not really a big difference....... Thanks guys Andrea

Hi all. Finally after long time of thinking (and more long time of no flying at all....) I decided to switch my PC to a SSD disk But now I'm deciding what to do with BS. I own both versions, but currently the one installed is still the V1. I would like to switch to V2, but I'm having some doubt about the home cockpit issue. Few years ago I've been programming my open cockpit boards in order to work with BS V1, and even if the cockpit didn't see the life, all the panel prototypes I made worked fine. My doubt now is: the V2 has been changed someway so to invalidate all my job, or V2 will work exactly like V1? It's worth to install V2? Thank for your opinion and suggestion Andrea

Hi all. Here comes an update: I'M FLYING!!!!!!!!:pilotfly::pilotfly::pilotfly: It's almost 14 days I'm in Florida for heli training. I'm flying R22. The beginning has been very traumatic, it seemed a crazy machine. But now everithing is going better, mostly the hover (wow, guys, it's really a challange hover and manoeuvring while hovering, but when you start manage it, you feel really....I don't know how to describe). BTW, I'm going hon with even more specialized manoeuvres, thing are going hard, but I love this challange. Maybe R22 is not a Ka50, but believe me it deserves the maximum respect. I'm sorry to say, but heli simulation cannot be compared with real world, aero simulation can. Why? Well, about 8 years ago I went to a friend whom own a Piper; it was the period I was flying Flight Simulator. Well, with no real experience, I made everithing alone (ok, my friend was ready to rescue in case of error): startup, taxy, take off, flight, landing, shut down. But believe me, flying an helicopter, a real one, cannot be done just with "simulator experience". And I'm happy being do it. Short anecdote: The most of the guys here study for airplane (we're only 4 heli pilots on about 40 students), and they always tell me "fly airplane, not heli!!!". Well, once the instructor, after a training, flying back to the airport, asked me "did you ever seen alligators?" "No, why?" then he took the controls and sayd "Here we go!!!" then fastly went down from 500 to 50 on a small river, following the river turning with 90° of bank (wow it seemed to me like Apocalipse Now, just missing the sound track...), and hovering on the alligators (when we spotted some). Then, back to airport, I told the "airplane guys" about the flight, and they stand silent. "Do it with an airplane!". Stay tuned. Jocman

Thanks, brother. See you soon (as I'll need surely your help again). Jocman

Update..... Ok, I wired some cables.....then stopped!!! Even because I need more hardware to complete the wiring, and I've to order it..... Many the reasons: stress on workplace (it was better to survive in afghanistan than work at home), stress on relational life (I think at this point is gone screwed....), and so on. BTW, my CNC project is going on, as in those last days I'm dealing for the machine and working on adapting the cad files I used to hand make my current panels. Then, in more or less 20 days I'll leave to USA to attend flight course (try to guess: fixed or rotary wing ?), and then when I'll come back (in 2 months) I hope to be moved to a new (hopefully better) workplace, meaning I'll be busy with the movement, looking for home (bigger, better, etc etc), and so on. Thus, my "Ka50 dream" has to be put on stby for a while..... Well, by now that's it, guys, maybe I'll keep you informed about my flight course (if interesting in). Jocman

Update. Just started wiring the switches. Ok, I started working on the cockpit since really long time, but at least I started again. BTW, I've still some switches to program.....Well, I'll do it, don't know when, but I'll do it. I must do it. In the meanwhile, I'm going on with the CNC project: next week I'll meet some guys in order to get some info about it, then I hope for Easter to get a CNC. Then it will be time make my project become real. Damn, I think I'm flying to high with my fantasy... Jocman

Well, back home. I still didn't start working again on my cockpit, as those last 10 days have been very busy because of the work and all the luggages to make up. Anyway, starting from monday I'll have some holydays (3 weeks) and I'll start working on cards and panels (finally I'll see again my beloved panels). In the meanwhile, during the last 2 weeks, I started to look for some craziness: a CNC mill machine. I'd like to remake the panels in a more realistic apparel. Of course, I'll build my cockpit prototype with the panels I built, but among all the missions, my proposal is to make new and better look panels. In the next days I'll go to see some machine, and is highly possible I'll get it. Stay tuned Jocman