There was another reason to abandon the initial design. I also learned a lot from writing the software. I learned a lot from these initial designs, but I my IO Cards needed not just a microprocessor but also additional hardware (transistors and diodes, power drivers etc.). One of the things I disliked more than the Centronics interface was the complexity of the wiring for a MCP build with IO Cards. I had looked at other MCP’s build with Open Cockpit Cards. A single display card for the digits and one input/LED card for the indicators, switches and rotary encoders. For the MCP I needed 2 IO Cards of my own design. I wrote the microcode, and additional software to connect USB to FS2004. So, I started to design my own ‘OC like’ IO Cards, but entirely based on microprocessors directly connected to the USB ports.Īs the interface between SIOC and the OC hardware is not published, I had to design my own. However, parallel interfaces were disappearing from the PCs and USB was the way to go. At the time the OC hardware was designed, it was a perfect, cheap and simple solution. One of the reasons I did not make/copy or adapt the open cockpit IO cards was the fact that they connect to the Centronics (parallel interface). Read it to better understand the different programs and their differences. I wanted to create enough panels that it would allow me to fly PMDG 737 without having to use the mouse to click to operate switches etc.īelow I will briefly touch the history of the design and the reasoning behind it all. I do not have the place for it, nor the time. My goal has never been to make a full blown cockpit. Support engineering, project management, marketing managers, software architect…. I’m an electronics engineer and worked in the computer industry for many years in various functions. It’s mainly about the electronics and software that allows you to build your own panel hardware and interface these with FSX/PMDG. This site is not a complete guide how to build a cockpit. On this BLOG-site I write about my efforts to design hard- and software to enable me to build a cockpit and/or cockpit elements for MS Flight Simulator. You find PMDGDataEventServers and virtual CDU programs for this version (as all other programs) via the tapatalk forum. The SDK is (stil) the same as the previous released 737NGXu for P3D. PMDG recently released their 737NG3 for MSFS2020. PMDGDataEventServer for PMDG 737 NGX (Simconnect data values) You will find these values at the end of the PMDG SDK data. On request I decided to include some data from MSFS SDK (Simconnect) in PMDGDataEventServer. As PMDGDataEventServer only dealt with PMDG SDK data, consequently PMDGDataEventServer did not provide these data values. Users were missing the display values of COM’s, NAV and Transponder. ![]() The PMDG SDK is almost complete to build a full cockpit. Until then, be patient.Ī new version of PMSGDataEventServer for NGX and NG3 (NGXu). As soon as I get correct SDK I will make a new version of the PMDGDataEventServer for the NG3. PMDGDataEventServer for MSFS NG3 no longer works.Īs of the latest update from PMDG 737NG3 for MSFS, the legacy SDK I use for the DataEventServer is no longer vallid and produces unexpected results. Future update from PMDG could change things. NOTE: This is based on a preliminary version of the SDK. This is an initial version for SIOC, yet to be verified. This version is verified to work with the latest update from PMDG. Version 3.12.A.MS -> Arduino/Serial version.I got the prelininairy SDK for MSFS NG3 from PMDG. New version of PMDGDataEventServer for PMDG 737 NG3 for MSFS. PMDGDataEventServer for MSFS and PMDG has been veriefied to work correct using the latest/current relaese of the SDK. If you are new to this site skip to ‘Dear Visitor’ some block below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |