npbosch

You should study the info off those addon programs. If they need to talk directly to FSX you can use them on another PC in the network. But then you have to use wideserver/wideclient (from Pete Dowson). Then the networked programs "thinks" it talks to FSX but infact it talks to wideclient on the second PC. Wideclient and wideserver (a dll that goes in to the dll directory of FS) do the real communicutaion on the network.Norbert

Is the unit stll available? I do not see the pic?RegardsNorbert

If that lever is comparable to the steering tiller used in the larger aircraft, then you could use the special tiller function that has been incorporated in fsuipc.norbert

Very nice project. I was interested how you did get these white characters on the knobs.regards Norbert

Thats correct. I can assure you that the new boards work. With every board I made I had hours and hours to find shorts and cold solders ( I have 4 io cards). Check also your cables. (I once had a faulty connection in one of the cables). Leds and capacitators in the right direction? The symptoms you describe seem to e like there are shorts. Use a magnifying glass or a multieter to check every connection. A lot of work, but it is the only way to succes.I know it is frustating, but keep trying, the design of the boards has been built by many and they work.good luck Norbert Bosch

download fsadmin from here:http://www.rvdijk.nl/download/fsadmin.exe

For C++ you will need the files under FSBUS 2008. (nothing from 2007 is needed)If the fsadmin does not work, download the fsbus cdk (it contains the fsadmin functionality)I will notify the webmaster for the error you mentioned when downloading the fsadmin tool about the missing file.Norbert

dl fromhttp://www.fsbus.de/3.htmlthe 2007 version is the "old" version. Quite simpel for non programmers (like me). Most things have to be put in ini files, see the docs for good info. You can even add basic code to get almost everything done what you can imagine.The 2008 version has to be used together with visual C++ and the dll. In this version you will get a exe file after programming and compiling. The biggest advance is a gain in speed.I use the 2007 version with fs9 and a quite old PC. It works very good to me. So I am not going to invest in C++ programming. For me thats a step too far.regardsNorberthttp://home.wanadoo.nl/norbert.bosch/

Fs9 or FSX.When talking about cockpitbuilding, it really does not matter which one you choose. All the IO cards talk/read to/from the sim via FSUIPC. Which sim you use depends more on the computerhardware you have. Many builders still use FS9.Before you start building read these 2 websites:http://www.mikesflightdeck.com/http://www.fscockpit.com/regardsNorberthttp://home.wanadoo.nl/norbert.bosch/

I just rebuild mine fire handles. Have a look athttp://home.wanadoo.nl/norbert.bosch/panel.htmlscroll down and click on the pics for a larger view.I adjusted an idea I saw at the flightsim convention at the Aviodrome at Lelystad.But because that idea is AFAIK not documented on the web, I think it is good to show it in this thread.The original manufacturer even made a locking device so the handle could not be pulled when there was no fire.When there was a fire a selonoid took the locking pin out, then you could pull the handle. When the selonoid was deactivated the locking came back to place by a spring.It was a beautiful design, but a lot of work for something you normally do not notice.What pilot pulls the handle when there is no fire?RegardsNorbert

Congratulations, looks very sturdy and very simple. Well done.I have one question, with what technique do you get those white 1 and 2 on the red plexiplate? regardsNorberthttp://home.wanadoo.nl/norbert.bosch/

Sorry, I was wrong. A long time ago I made my boards. 6pin is for flashing, 10 pins for setting CID.Did you set the jumper on pin 16 when setting the cid? Only one board must be connected to the com board when setting a cid.In fact when I made my boards I had a lot of trouble too. I found a wrong connection in my 10 pin cable. One of the connectors was not correctly connected to the metal of the flatcable. I only discovered that after using a multimeter on every line of the cable.Good luckNorbert

http://www.fscockpit.com/http://www.mikesflightdeck.com/good sites to start with.Lots of IO cards possible.If you can make them your own I suggest fsbus. Otherwise buy the assembled cards from http://www.opencockpits.com/ redardsnorbert

AFAIK you can only set the CID with the 6 pin ISP cable, not with the 10 pinscable. Thats what the ISP cable is for. By deafault CID is set to 31. Remember to remove all other cards when setting a CID. On some cards you have to set a jumper to change the CID. Just proceed exactly by the docs.Norbert

You will get your registration. The owner of the site is very busy at the moment, so it can take a few days.Norbert

If you install the fsbuscdk package , you will find a sunfolder with all the hex files.Yes I made one servo board, I think it is analogue indeed. The servo works, but now it stays on the todo list for a while.I will use it for the brake pressure gauge in the future.regardsNorbert

After a lot of work I got fsbus working and running.I remember that I saw 'Device missing or unkown device (-24)' too.I thinks there IS something wrong with your hardware. Check and recheck every cable and component and line on your pcb.I had a few cold solders o my board, and the last error was on my connectors that were pressed on my flatcable. One pin did not make contact with the copper, I found it after measuring every line of the connectors between the flatcables.The solution is almost always in these sort of things. The layout of the boards is OK and they do work.The way you solder the 3 pin resonator is unimportant.Norbert

Hi Rob,I put all my code (FSBUS-CDK) on the Dutch cockpitbuilders forum.You have to register firsthttp://www.flightdeckbuilder.nl/modules.ph...=viewforum&f=34I split the code in small parts.So one part for transponder, a part for radios etc etc.You can put it together by yourself to larger files.Or download the code from www.rvdijk.nlYou will find there the code of his 737 pit.But that is everything together in a few files and a bit difficult to see what belongs to what.RegardsNorbert

Just download the package from fsbus.de.Install and look in the subfolders in the programfolder for docs.layout etcNorbert

All the docs I have are in "normal" English. Only the general document explaining the concept and the different parts is in German.If you mail me on norbert dot bosch at wanadoo dot nl , I will send them to you.Did you download the latest fsbus package? After installing you will get a folder with the docs.Norbert

I build, 1 com board, 4 IO boards and 2 sixpackdisplay boards. None worked from the beginning. Now everything is working. check and recheck for:cold soldersshortcutscapacitators/leds in the wrong direction.The design of the boards are OK , they work. Have patience, check and recheck.Norbert

If you install the fsbus cdk package, then you will see subdirectories that contain the layout files and the document files that explain everything.Norbert

You have mail. I think the download section of fsbus.de is not complete anymore. I brought it to the attention of the one that manages the site.Norbert

I still do not understand. I use rotaries for radios, heading selector, altitude selct etc.The fsbus software links the hardware input to the fsuipc offset you want to change. That worked perfectly with the old fsbus and the new NG package.You can also send keycommandos to FS or other software on the same pc or a pc in the network. But you do not use rotaries for that but pushbuttons or switches or rotaryselectors.Norbert

I do not see them on www.fsbus.de anymore. Only the CDK software, layout of the IO and servo board, but the com and display boards are missing.Give me a PM (norbert dot bosch at wanadoo dot nl) , and I will send it to you.Norbert