tigert

Um, can you clarify a bit? The "Knitter" and "Alps" encoders do work, yeah, since those have the rotation direction split to different pins depending on which direction you turn.Do you mean you can use the phase-shifted ones without using the "redec" circuit? Which ones? Model number? Screenshot of your config? Photo of the wiring? More info! :)//Tuomas

Conrad.de has them. Well, not encoders, but 12-position rotary switches with a 3mm hole through the 6mm shaft. See the flightxpress.de forum (linked from www.fsbus.de) and look for the thread called "Radioknopf".//Tuomas

To make a button emit keypress "a" you need to do this:K+A;d50;K-AThat's: Press down A (needs to be capital), delay of 50ms, release A.Use the FSFinder to figure out more complex strokes and special key names. FSFinder.exe is where your FSBUS is installed.For something like a PTT switch, leave out the delay, and put "K+VK_CONTROL" on "up event" and "K-VK_CONTROL" on "down event" - this way a key "Ctrl" is pressed down as long as your switch is connected.For the ND range thing you want just up events, and ideally you need to have each range value have their own keycode, which you can bind to that button in FSBUS. And then you need to put the whole thing wiht delay to the "up" event.It depends on what you need, I hope this helps you a bit further? Unfortunately I havent looked into the mouse button events at all, so I cannot help with those. See if the fsfinder shows you something that helps?//Tuomas

FlightGear is truly Free, not just "Free" ;-) But I guess that's what you meant too. Nice simulator!I need to check it back again - how does one interface to it? Is there a network interface like on x-plane or something else?It's been a while since I last looked into it - I just dropped it last time since Linux 3d drivers were in a sorry state back then.. and they sort of still are thouhg.. :-///Tuomas

Good morning indeed :)I am impressed by your panel quality and the general project, very good looking stuff and well constructed parts! While I am not personally very fond of flying the "nintendo" I do enjoy your GA flying pictures a lot! Keep up posting them :)Here's my gallery if you want to waste time looking at pics:http://tigert.gimp.org/gallery/aviation//Tuomas

>Hi Joachim,>>Would you post some pictures of operating your 295 with MSFS?>Does Pete Dowson's GPSOut.dll work perfectly with the 295? or>to 195 only? Would you tell us what functions will be disable>by using simulator mode?Hi Alkit :)I can only speak for my 196 - basically FS tells the GPS where we are, what altitude and where we are moving and how fast.It does not integrate with the autopilot on FS - the communication is strictly one way (it's called GPS*OUT* after all :)) - but no portable GPS does that on real planes anyway.It does not load your flightplans if you create one from the simulator, but then again, at least I am practicing the GPS use, so I am using it to do the route planning.I think it works pretty much like a portable GPS does in a real plane.One thing I think that does not work is the "breadcrumbs" track log the GPS makes - it doesnt plot and store the flown route in simulator mode. But that's pretty much the only thing I know that doesnt work.It probably works with all Garmin aviation gps'es, I think I heard a GPS III Pilot works, my GPS196 does and now we know a 295 does. Basically Pete Dowson added the AV400 support after I mailed him a protocol doc I got from Garmin - it is not supported by Garmin, it just is on one of their technical manuals, Pete just formatted the GPSOut lines according to the doc, and it worked. We had to debug a bit to get heading output work correctly, but it does seem to work sweet now. If you find issues, let Pete know of course - it is a hack, but a really slick hack that rules :-)Non-garmin units may work - the protocol is also called "King" and something else, which indicates it might be something used by other brands too, but no idea. I dont have other GPS'es to test with. If someone uses gpsout with another GPS unit, let us know, it'd be interesting to know. It does not work with Garmin's "non-aviation" gps units like the street pilot or eTrex etc.. since those dont have the aviation protocol option.//Tuomas

>12 pos rotary should be connected this way:>common to one of the fskey commons>first connect together pins>1,5,9>2,6,10>3,7,11>4,8,12>>then connect these four groups, to four inputs in sequence on>the fskey card.Yes, but he does not want this. What you described gives a rotary encoder -like switch that increments a value when turned clockwise etc.In this case one needs N-position switch that outputs a different value or keystroke when moved to each position.The switch usually has a metal "tab" that you can adjust to limit the number of steps the switch can move. So if you want 4 positions, put it so that it moves 1-2-3-4 and then the tab stops it from moving further.Then wire the center wire to a common ground signal (the fsbus KEY card has the "ground" pins common for each "row" (8 pin pairs) - you can see this from the back of the key module - the ground pins are the ones that are *away* from the diodes.So wire it like this:G-o-o-o-o-o-o-o-o-o-o... < key card row1-2-3-4-o-o-o-o-o-o-o.... . . . . . . . . . . ! ! ! ! ! ! ! ! ! ! !... < diodes. . . . . . . . . . .1-2-3-4 are connected to those pins that the switch uses. This gives you basically 4 momentary switches of which one just "stays" on at once.You want to *uncheck* the "down event" checkboxes and just check "up event"'s so that when you move the switch to position 2, the switch "2" turns "ON" and emits a key sequence (for example "K+A;d50;K-A" for "Up" event. Nothing for down event as we dont want to mess with those - when you turn the switch to another position, you dont care where it *was* (down event) but rather where it *goes* (up event).Do this for each switch and define suitable key events that the freefd uses to switch the range stuff..I hope this helps, ask more if I wasnt clear, it is pretty late and I must sleep now :-)//Tuomas

>Power USB ports/hubs are able to provide 500ma.>Much more then a com port, but i doubt they are sufficient for>a gps.>Don't know for sure though...>My Garmin has a special cable which has actually two cables going to the Garmin connector that plugs into the GPS unit. There's one cable for COM-port with a 9 pin serial port connector, and then another cable with a +12V car cigarette lighter plug. The COM-cable does not provide you with *power* - it is just for connecting the unit to the computer.I'd get a real cable, it is not that expensive compared to a fried GPS.. :)Our simulator just has a car cigarette lighter socket on the panel - it is powered by the +12V from the AT power supply that powers FSBUS and simkits. Just do *not* use the lighter from it - it draws too much current and could burn the fuse on the AT psu..//Tuomas

>Not bad at all...>>About CH products. It takes quite a lot time and effort to>build a decent yoke and pedals so honestly it is quite good>choice until you have time to build better ones.Yep, agreed. They are the only reasonable choice if you dont want to spend $1000 to yoke + pedals or cannot do them yourself (or dont have the time to do it)//Tuomas

Search the forum for "PCI" and "multiple monitors on one PC"//Tuomas

Neat!Waiting to see the inside..But why CH? My feeling has been that they, while better than your ordinary PC joystick, are still rather inprecise and too "plastic" for a real simulator..Of course it all depends on the resources and time available, which is understandable.//Tuomas

Mail them and ask where they got theirs, and how they work?//Tuomas

>Pitch and roll you maybe mean an "attitude indicator" ?>They are not gravity piloted, no instrument on any plane is>left to only phisical forces a part from the ones using air>pressure (airspeed indicator, altimeter).>All the attitude indicators are mechanical, gyroscope driven.>There are two ways to replicate them in a homecockpit:>RC servo (see simkits)>Stepper (for full 360

>Interesting - is that gauge in your simpit the same as the one>in your real Cessna? The 172 I fly is a 1972, and the flaps>switch is a flat lever that comes down a 'stairstep' slot to>select each flaps position, and has no indicator to show where>the flaps actually are.Yes, there are different models. The new ones have the "stairstep" too - and our 152 has that as well - the stairstep has the "stick" indicator next to the stairstep. The 172 has a round gauge just like on the sim - and a (on)-off-(on) switch to add/remove flaps (it is non-proportional - you hold the switch down to get more flaps, and you get as much as you hold, the gauge shows how much you have (or you can watch from the flaps themselves of course))Here's a pic:http://tigert.gimp.org/tigert-albums/c172dim/abc.sized.jpgThe gauge is there above the right side yoke, just above the measuring tape, and the switch is right of the mixture lever.(if you do a cessna cockpit, the whole gallery might be useful: http://tigert.gimp.org/gallery/c172dim )The 152 has the more common flaps "stairstep" lever:http://www.mik.fi/gallery/albums/koneet/p1010134.sized.jpg//Tuomas

>I don't have a flaps actual position indicator in the real>172 I fly. The flaps switch is a multi-position switch who's>position shows the position of the flaps. Checking it's right>means looking out the window :-)>>For the elevator trim indicator, you could indeed use a servo>or stepper. The value for the actual trim position in FSUIPC>is at 0BC2.>>You can see a non-gauge trim indicator in my FSPanel app in>the library.>>RichardOur club cessnas have an indicator - the 152 has a small "stick" that moves next to the lever - you move the flaps lever down, and the stick moves along as the flaps extend.The 172 has a round gauge on the instrument panel since it has just a 3-position switch to extend and retract flaps.We did our indicator to the simulator from the simkits "small gauge" instrument - just wired the servo to FSBUS since Simkits would require to have a whole flap switch thing together with the indicator and we didnt do that since we have the simple switch for operating flaps.http://tigert.gimp.org/tigert-albums/simu_...e/aab.sized.jpgYou can see the whole panel here:http://tigert.gimp.org/tigert-albums/MIK/aah.sized.jpgQuite a challenge to stuff the instruments of a C172 into a C150 panel space - the thing is built into a C150 fuselage..//Tuomas

>I too was hoping to use PSS A320 as my airplane in my>homebuilt but once I started to build out with Project>Magenta, it appeared needless in that I never ever open up a>cockpit view! I have a pyhusical cockpit in fromt of me! So,>since all of the systems in the A320 are working form PM ABGC>- the only thing I really need is a pretty airplance anf I get>that from IFDG or Project Opensky.What do you need the outside model for? :-) You are sitting inside... All those things become irrelevant once you start flying in the cockpit - you dont really want to see *the plane you are flying* through the cockpit windows, it looks way bizarre :-)//Tuomas

Dont modify fsif.ini, do a file called "myfsif.ini" and you can start the id's from one as far as I remember.This has the added safety that it doesnt get overwritten when you upgrade fsbus later.Then we can circulate the master "myfsif.ini" and it doesnt conflict if dirk releases a new one wiht more stuff - we get those plus our own.//Tuomas

>I haven't tried them out yet since I don't have any of my>hardware from FDS yet. >>What ones would you be interested in trying? If you let me>know I'll see if I can find them and give them to you so you>can try them out. As long as you report back and let me know>if it works or not of course. :-)>>For example, on the Captain's EFIS panel, the VOR1 switch. >It's a three position switch. Here is what I found out:>>Capt VOR1 Switch>----------------> Address: 6204>VOR1 Value: 256>ADF1 Value: 512> Off Value: 0 >>Let me know if those worked for ya. :-) We should make a>list or something so others can use them too. I'll try>putting something together as I gather the data.>>-AllistahYou can try them out if you have a registered FSUIPC - for example get the FSBUS 1.3 software - it has a "test button" and you can define the offset and bit sizes etc in the UI - good for testing. Pressing the test button lets you toggle values in fsuipc even without real hardware. FSBUS2 has a config file where one defines those, so it is a bit less useful for just trying out things, but the 1.3 version is still available from www.fsbus.de and should be a useful thing to play with.//Tuomas

>So where do I get FS Interrogate from anyways? I looked in>the library but couldn't find it.>>-AllistahIt's in the FSUIPC SDK if I remember correctly. From Dowson's page on www.schiratti.com/dowson.html//Tuomas

Sigh, silly people :)If it is so easy to figure out with FSInterrogate, are they so naive that they think the competitors havent done that already? Sigh. Classic case of "security through obscurity"..Thanks for the tip anyway.//Tuomas

>while I'm very sure that most people actually have checked the>manual. Dude, most people do *Not* read manuals. Believe me. Try doing some tech support work sometime and you dont even doubt it anymore :-)//Tuomas

>I have a Radeon 9800, is it better to run the second monitor>off that card, or get a seperate PCI card to run the panel??Well try it, it if works, fine.My PCI card doesnt eat any frames, actually I get a few FPS more because the panel is off the main window - most panels are quite slow because of the complex "hole mask" on the window shape - a full screen panel means FS doesnt need to mask the panel over the 3d view, so things are faster.//Tuomas

>That would be neat indeed. To fly with someone together. >Only problem is .. I don't see my dad flying with me more than>10 minutes. Neither would my friends.>>Only when someone from FSCB would come over or some HC builder>friends .. who knows.>>Either way, my sim will look MUCH better as a 2 seater. >Obvious cuz that's how it is in real as well. If you make>2/3ds of a cockpit it will always look cripled. (or however>you write that)A friend of mine has done some "757PIC" flying (767PIC mod with a 757 flight model and performance data etc) with a friend - they are planning a full cockpit, but so far it has been in a multimonitor setup wiht panels scattered accross - he said it is a whole new world of simming to get into the cockpit resource management and pilot/copilot arrangement - who does what and such - you need to find the Fokker operations manual somewhere to see how the stuff is done for real. It's a whole new thing - combine this with a flight planning session, real paper IFR charts and weather briefing etc (www.pmfp.com) - with a friend or friends who are sharing the interest it's a good way to spend a weekend or a night socializing and flying.. add VATSIM and it gets pretty intense.All this in a cockpit is so much more than just sitting around the PC.//Tuomas

>Rip it off.... Write it down as control failure, squawk 7600>and issue a mayday before you hit the deck ;)Sir, it's 7700, 7600 is for radio failure =)"Seven five - man with a knife,Seven six - radio nix,Seven seven - going to heaven."so, 7500 is hijacking code, 7600 is for communication failure like mentioned, and 7700 is the emergency code.For Philip, SHORT's idea is good - the car or washing machine suspension thing is a good way to add the heavy feeling - and make it out of metal, use inline skate bearings or such like he has, to make it *sturdy* - the rest of the cockpit can shake a bit, but the yoke and pedals - they need to be strong and feel heavy if you want to feel like flying something that weighs several tons. CH yoke and pedals are mere toys if you think of this that way. Better than nothing of course, but just too light, and too inaccurate for serious flying. Make the movement of the yoke be about 20cm in elevator axis (easy wiht the long pole) and 180 degrees for the aileron, and use the "MiniME" controller for that if possible - or your joystick pots. Something that does not shake like gameport. This gives you a more realistic control where you can adjust the plane with just very small movements of the yoke and thus combined with the heavy feel, it should be pretty cool. You probably need centering force to the yoke though - it works without, but it is very hard to trim the plane for approach as if you poke the yoke accidentally then you have it all messed up again..//Tuomas

> Don't take this a gospel, but I was under the impression>that you could only have one AGP and one PCI video card per>machine. Again not 100% sure.>> MiltSomeone said months ago that he had 5 monitors on one computer - 1 agp and 4 PCI matroxes.Some pci card brands dont like to work with multiple cards, but matroxes do work generally.With win2000 / XP it should be OK.Just try adding an extra one and see if it works - better to try before buying of course.//Tuomas