I am about to make the plunge into building a simpit with FSX and 737NGX. And I have some simple but fundamental questions.I'm a software developer with years of coding in most languages and I'm an experienced hardware builder. I'm also a pilot (just not current). So I know how to write software and build things. I just don't know the best ways of hooking things together. And how well they work in practice.So question 1: How does the SDK work? Will the 737 SDK allow me to "get" to all the events and devices displayed on screen. Does the SDK work on a polling or event system? (I've seen some sim SDKs that use some very old-fashioned methods like polling offsets.) Will the PMDG SDK give access to FSX stuff or will I have to get that separately? And since the SDK isn't out yet I'm asking for best guesses based on how PMDG's other SDKs work.Question 2: Connecting PC's: Should I use sockets, UDP, HTTP, or some form of client-server configuration. I guess that depends on the hardware. But any tips like: "don't use IP for displays--it's too slow" would be helpful.Question 3: Is it likely that the SDK will have connectivity to FSUIPC or will the connectivity be something else? Will I be able to write code that can connect directly to the SDK??Switches, lights, levers, I assume can be put on separate PCs because a little latency with those is OK. But is it wise to put things like PFD & ND on networked PCs or better to keep them on the master PC.Finally I'd appreciate if anyone can point me to a web site that discusses networked pros and cons and tips and tricks. There is a lot on the web about home-built sims but not too much detail about the fundamentals. I don't want to get down the road with one methodology and find out that it doesn't work well.I'm asking a lot but I want to have a pretty good picture of the forest before I plunge into the trees. (Bad metaphore for a flying forum!)Thanks for any help.

Ned,Since no-one replied yet, I'll try to give what I know and have experienced.I used to build level-6 stationary sims in a company for private training institutes and some airlines, but what I will try to suggest (from memory and from what I'm allowed to share) may be too expensive for you.I spend a good portion of time working on 738 panels (active project during the time I was there) and cockpit interior. I guess I can give you a brief overview of how you may be able to construct panels, wiring them and fitting them, though not sure how useful this is to you. If you have the budget, it's probably more useful to just buy a premade panel.We use to connect the displays and buttons and dials using phidget board, which is a USB IO device that connects directly to the computer. Very straight forward to program. Panel plates are made from aluminum, and we use to paint them first, laser cut the panel element outline and then machine cut or drill them out. After then, using illustrated parts catalogue to find the right parts, get them from parts stoker or electronics stores (ebay is your best friend). Otherwise you could try to use plywood.In terms of connecting to FS, we used to use FSUIPC for FS9 as that was our engine. But I believe you have FSUIPC for FSX and also SimConnect. But assuming NGX's SDK would be somewhat similar to the one of the project that I've told you about, it should have some good level of access to the product's manipulatable or displayable parameters like the FSUIPC has on FS9.I won't go on too much about how to create the flap control, autothrottle etc, it's probably not something you'd want to do at home (needs machinery).Sorry if this isn't what you want, but thought I throw my knowledge out there just in case you or anyone might find it useful.

I would suggest you have a look at some dedicated Cockpit builder forums.All of the answers to your questions are there.I hope that I am allowed to do this, here are a few that I have gleaned an enormous amount of info from:www.cockpitbuilders.comwww.mycockpit.orghttp://forum.avsim.net/forum/142-the-home-cockpit-support-forum/I'm sure there are a lot more, but this should get you started. Hope this helps,Frank Cooper

Ned,I will mirror what Frank has said about the above cockpit builders sites.I too am embarking on the B738 route using the NGX as a base. Whilst I have the MCP, CDU, EFIS, and radios, I am eagerly awaiting to get them to run with the NGX.Cockpit building absorbs a lot of time and money but it is very satisfying - even when things don't work first time.Good luck.

I was doing some reading for a friend, and found that connecting computers together seems to use SimConnect. You might find this answer to be correct or incorrect though, check those literature above as suggested by the previous two would be your best bet.

So question 1: How does the SDK work? Will the 737 SDK allow me to "get" to all the events and devices displayed on screen. Does the SDK work on a polling or event system? (I've seen some sim SDKs that use some very old-fashioned methods like polling offsets.)

Polling offsets is not an old fashioned method at all. It depends on the application, what it is doing and how it is doing it as to what method you decide to use for manipulating that data.Assuming the SDK is just the ability to read/send the states of switches,buttons etc then more than likely you will have to put which parts of the cockpit you want to read/control into various timers. Some events will need to be read over short intervals whereas some could be every ten seconds or so.You will also have to create the code to read/send the states from the aircraft via the SDK. ie you will have to create a variable, call the function within the SDK dll to read a particular item in the aircraft which then copys that state into the variable you have created. It is then up to you what you do with that variable! As you are already aware as a programmer YOU are in control of what you want to happen and when.Nico created a software interface for the Level-D 767 SDK which grouped various cockpit items into separate timer groups. I also created a similar interface for my application as I only wanted to read various items at certain times and did not want these constantly polled. I am assuming the 737NG SDK is going to be straightforward dll and .h files.

Will the PMDG SDK give access to FSX stuff or will I have to get that separately?

FS data is already accessible via FSUIPC/Simconnect.

Question 3: Is it likely that the SDK will have connectivity to FSUIPC or will the connectivity be something else? Will I be able to write code that can connect directly to the SDK??

FSUIPC is not required though you can send the cockpit data read via the SDK to FSUIPC offsets if you want to.I have done it this way for the Level-D 767. I read the aircraft data on the FS PC, write to offsets and I can then read them when running my main application on my laptop. It is a good way of 'networking' the data. Spare offsets can be applied for by talking to Pete Dowson (maintainer of FSUIPC) if you are going to release your application to the masses though I just wrote directly to the offsets used by Nicos application for the 767.Again, as a programmer it is your choice where that data is sent, if sent anywhere at all, and what is done with it.

Finally I'd appreciate if anyone can point me to a web site that discusses networked pros and cons and tips and tricks. There is a lot on the web about home-built sims but not too much detail about the fundamentals.

In addition to what is already posted aboveNicos' websitehttp://www.nicokaan.nl/

Edited February 7, 201214 yr by graham3278

Hello Ned,I am a builder (blueskydriver) on the top two listed builder websites in the post above and I'd like to tell you or anyone else ever thinking about building a sim, please go visit someone who has one now. You will figure so much out from just one visit, as seeing is believing, or seeing is learning so to speak. Before I started, I visted a couple of guys and now many years later, I have a B737 Cockpit, with a B727 Cockpit waiting in the wings (pun intended) out sitting on the driveway. My wife has started working towards a F16 just yesterday, yes MY WIFE, so her and I love simulators...Anyway, having the skill sets that you listed is a big plus for building and you might not need to visit someone. However, I've had real pilots see my sim and couldn't believe what they saw. Even an visiting Airforce KC10 pilot was surprised at the level Cockpit Builders are at now and was happy to see mine.I know this does not answer your questions directly, but that is because some builders like doing the "Show and Tell" as opposed to the "Type and Wait"; thus, just ask anyone of them to come visit their sim. More than likely, you will be getting the answers you seek and flying their sim as well. Besides, since the PMDG 737NGX SDK is not out yet, you have plenty of time...John

Edited February 7, 201214 yr by blueskydriver

Ned...If you are good at programming, I think you should look at the Arduino cards. If you are able to write a interface between NGX and the Arduino, those cards will give you total flexibility. I am looking at the Arduino cards myself, but has no clue of how to make the neccessary software interface to NGX. If you also have some electronic skills, you can connect a huge amount of in/outputs on each arduino using shiftin/shiftout IC`s.Regarding PFD/ND and the other screens, I dont think PMDG makes a network version (but I do hope), so you can have them on a different computer, however... My idea is to run all those displays + a FSX top down view in the background, and then running the visuals on a separate computer via the wideview application. This should work.I am looking at the NGX as a base for my next project, but also at the Prosim737. Cant make the decision befor the SDK is released, and hopefully someone has written a software interface for some hardware...Ivar Hestnes

For all those who posted answers, many thanks.More than enough info to get me moving in the right direction. I'm beginning to see in my mind how I will start.But I'm still concerned about how much I can load my PC that's hosting FSX. I plan for that PC to display outside view on two or three monitors. And I want to display PFD, ND, and Upper DU, Lower, F/O displays on multiple monitors. So should I try to have all these monitors on the main PC or can I safely move the PFD, ND, and other DUs to a separate networked computer(s)?I guess what I'm asking is how do folks handle the 6 large displays on the MIP and lower panel?Maybe the answer to that is in the several sites that were suggested.Thanks again. This is a great forum.

For all those who posted answers, many thanks.More than enough info to get me moving in the right direction. I'm beginning to see in my mind how I will start.But I'm still concerned about how much I can load my PC that's hosting FSX. I plan for that PC to display outside view on two or three monitors. And I want to display PFD, ND, and Upper DU, Lower, F/O displays on multiple monitors. So should I try to have all these monitors on the main PC or can I safely move the PFD, ND, and other DUs to a separate networked computer(s)?I guess what I'm asking is how do folks handle the 6 large displays on the MIP and lower panel?Maybe the answer to that is in the several sites that were suggested.Thanks again. This is a great forum.

(1) Read the many forums and Websites about Building a "FSX Sim Cockpit".Every question you have posted so far, has been discussed and dealt with before.Try to get into communication with othere who have already built Sim Cockpits.No point in "re-inventing" the wheel.(2) Learn how to use SIMCONNECT. To do so you will need to be familar with WINDOWS programming. As an experienced programmer, this should not be too difficult to get a handle on. (be aware of other options apart from SimConnect)Wish you every sucess with your project... its will take considersable time and money -- I hope you find it worth it all in the end.

Edited February 7, 201214 yr by FSMP

FDS uses a single monitor for both pfd/nd, so you could get away with only 4 for the instrument displays. As for running them off a second pc, that would definitely be the way to go but we won't know if the ngx sdk will allow for that until its out. Or Robert/Ryan chime in with an answer...