FSBUS NG / CDK Dig out

[Guest o2drink]

What would the FSBUS NG IO Port A Bit 7 translate to as a CID/RID if I wanted to define a control? (It works in FSADMIN.)C, CLOuterMark, DOUT, CID, RID ,, 0, 0Thank you in advance.Eric

[Guest o2drink]

Too quick to post... I got it by using this:C, CLOouterMark, DO, 8, 7,,0 ,0 in the dabI have found that after too many changes, a restart of CDK makes the difference to get things working. I, however, can't seem to get the VC LEDs to work - at least for this. Happy building to all!Eric

[npbosch]

Hi EricI had this question also on my TO DO list.The same is with the 8 analog (potmeters) input.(what cid/rid should they get?) Recently I was experimenting with my IOcard with CID=1.I had the throttle connected to the first pin. I still am not able to get the pots to work, but I noticed something else.The code was OK (in the virtual cockpit I could change the slider and the throttles moved)but my real hardware did nothing,I used CID RID 1 , 0 (the first pin on CID 1 port A). But when I turned my com1 rotary the throttle moved. That specific rotary had also cid/rid 1/0. Because the potiline came later in the code then the rotary code I suppose it gets priority.So my question to you:The 8 will be your cid I assume? But how do you call your key in pin 8 of J6? That also will be a 7.Are you able to use those 2 simultaneously?There is a little bug I think in the leds of the vc. If you assign the cid/rid of your outermarker led to the first VC led, the second led will lit. Thats also with the second (third will lit), third (fourth will lit) and fourth (nothing will lit). I emailed this to Dirk, so he is aware of it.regards NorbertPSWith reagrds to my resetting problem. I am making my flatcable as short as possible now. 2/3 of al the cables is finished by now, there is no resetiing anymore till now. Will add the last 1/3 one by one and check after every cable wheter it stays stable.

[Guest o2drink]

Yes, I am using the i/o board at CID 8. As far as I can tell (within CDK) the keys have their own identity and the digouts have their own as well. I have moved down to the Digital B port now for more permanent placing. So, Discrete 8-7 is different than Digital out 8-7. I haven't tested that in FS though as I have a hard time getting the outermark triggered by strictly keyboard flying, which is my fsbus test PC. As for the VC led, now that I've moved to dig port B, I do see if I assign LED0 as 8-0, LED1 will light. However, If I assign LED0 as 8-8, LED1 will not light. Hope that might help.I'm still building out the circuit to Mike Powell's air-core airspeed indicator and I hope to have that at least somewhat working in the next week or two. Still guessing at how that will hook up to the pc, but one step at a time I suppose.(luckily my homebrew is easier to make)Cheers,Eric

[Guest o2drink]

Norbert,Since you're schooled on the CDK, is more correct to have many ini files (Led.ini, radio.ini,...etc) or is it more efficient for processing to have only one? I starting placing more code in the .dab and now it takes 5-10secs to run and I have 5 ini's.Eric

[npbosch]

Hi Eric,Best is to put all the F variables in one ini.file.Use the one from www.rvdijk.nl. That one is already very extensive and saves a lott of work with regards from the offset.One can shares each other F-object.ini files , bacause the things in it have to do with only the offsets.Then put the C/A/R objects in another ini. This will be different for every builder.For simplicity split things up:I have a pedestal.ini and a overhead.ini (or even more if you like).In the dab file it is important that the ini with th F objects is loaded first. (I noticed all kind of error mesagges when the f.ini file loaded last)regardsNorbert