July 20, 200619 yr Hi JarkkoFirst test the hardware. Echo test OK in FSADMIN. All the pins of J6-J13 OK?Then goto fsbusroutersw.then rightclick NEW , Digital input switch (do NOT use the Input switch without the word digital in front - it is for the classic boards). Do not use keyboard mouse either (that is for sending a character to another application on the same or on another pc).Then right click in destination and add fligtsim destination - FSstandard-aircraftcontrol-gearcontrol.Enter controller ID and RID (one of thge 64 pins) (use autosense or fsadmin to find the right number).Experiment with the other parameters, they depend of the type of switch you use. Toggle/momentary.good luckNorberthttp://home.wanadoo.nl/norbert.bosch/
July 21, 200619 yr Thanks Norbert.Your post was really helping.in admin ecko test is giving 1 error Why? but otherwise it worksi can light up leds and it regognice every CID ROW i think it works like it shoud!But i
July 21, 200619 yr With me the ECHO test also starts with one fault, then it runs indefenitely without any error, so that should be fine.I use only PM and standard FS variables via FSBUS. I am not familiar with PSSA320. But you should be able to generate keypresses via FSBUS. One for every input , so 64 should be possible with one IO card.About the 1*12 rotary. You can use them as seperate switches. I do that with the autobrake panel. I give the value 0 to OFF position and 5 to MAX ( and so on). In that case you do not have to do anything in fsadmin. It just works as normal momentary/toggle switches.So could you also connect this to F6/F7 ?. How should the hardware notices the difference by turning left or right? If you turn right you would like to generate a F6, and turn left a F7 (or perhaps the other way around). AFAIK that's impossible.I think you should use the rotary selector as a real rotary for this purpose.First you have to define that rotaryswitch into the IC via fsadmin. Suppose you have the rotary connected to the first 8 pins of J6 (pin 1,3,5,7 to the outer side of the rotary and pin 2 or 4 or 6 or 8 to the common, inner pin). Then use the right CID and as keynumber use 0, then select rotary (i do this by head, so perhaps I am wrong, just experiment). Then push apply. If everything is OK then you should see a 1 if you turn the rotary right and a -1 when turning left.(remember to have the jumper 16 set when doing this.) If you use a 1*12 rotary there is another issue, it is documented in the fsbus doc. You have to connect the outer pins of the rotary in a certain way to eachother. Connect pin 1to 5 and 9; 2 to 6 and 10; 3 to 7 and 11; 4 to 8 and 12. If you use these switches it is easier to use 3x4 ones, then you only have to connect the 3 inner pins to eachother.When you saw the 1 and -1 in fsadmin by turning cw and ccw , close fsadmin, remove J16 and open fsbusrouter.Now you should define the switch as an digital rotary in fsbus. Send the signal to the flaps. I do not know what values you should use here. If you do not succeed , use fsinterrogate (in thge fsuipc-sdk package). Set with the mouse a certain flap setting and look in fsinterrogate what the value is. regardsNorberthttp://home.wanadoo.nl/norbert.bosch/
July 21, 200619 yr I use also 9 pins 100 ohm resistor arrays. I even had them (in a few rows) mounted in the wrong way. (there are 8x 100 ohm in the array, the pin without the resistor has to be put at the center side of the pcb, otherwise you will measure 200 ohm at most lines). But this is not critical, everything works with my setup, with the arrays in the wrong way. So the arrays will not be the problem I think.The version thats is on the fsbus site at the moment is the correct one. Pin 3 of IC2 is connected to ground (pin8). If that was NOT the case, J6 would not be recognised either.I do not exactly understand what you are saying. In fsadmin make a short between pin 1 and 2 on J6 (key o ). You should see key 0 = 1 in the display. Do this for all the other 63 keypositions. If that works, your hardware is OK.If I understand you right, everyuthing is OK in fsadmin, but in fsbus you see only what is connected to J6?Did you set "NG only" in FSbus router?norbert
July 21, 200619 yr Thanks Norbert Hardware are ok and working.Now i have some issues whit creating keypress.How i can send key press to fsuipc. like first create key/mouse at routersw lets make G for gear.1. on sequense k+g;k-g2. chooce digit input switch then auto sence klic ok working.3. chooce up event and down event and save 4 open fs 2004 and fsuipc from modules in top of my screen. open keypress page in fsuipc (registered version 3.65) turn switch nothing appears in box in fsuipc i think there should appearss G witch i can assigneg as gear. this i read from finnish cockpit builder forum. i think it was made for classic fsbus key board. shoud this new io board work like earlier version of fsbus.Should i build all so classic key card/board??is it easyer define keypress whit that.Best regards Jarkko
July 22, 200619 yr I experimented (a while ago) with keypresses and remember that it was difficult/ I wanted to send keypresses via the network to another pc.But for gearup. Why so difficult. Just connect it to the standard fs.gearup. Do not use keypress for that. That should work, regardless of what addon you use.Norbert
July 22, 200619 yr Thanks again Norbert Yes, i all ready got working gear systems it really easy part.But the flaps are difficulty i got them working up fully and down fullyBut not by segments, whit on/off/on switch witch has autocenterdefining those as two diffrent switch. common in middle. i think it works now like G in keyboards has push
July 22, 200619 yr For flaps , rebuild the 12 rotary switch as stated above as a real rotary. The hardware should see a difference between turninh left or right. Thats only possible with a real rotary.Norbert
July 24, 200619 yr Thanks Norbert.Now i got it fully working and key commands are working problem was in keyboard/ mouse page controller id it was 1.It should be 0 because, 1 is client computer etc...Best regards Jarkko Nieminen
Create an account or sign in to comment