DGK737

Hitried to aproach the www.fs2crew.com homepage but the browser says: "Can't find the Server"!!!!Does anybody else have this issue?

... and how are you looking after several beers....

Hi Vincent,many thanks for this hint. I never recognized Prosim737 before. Looks quite interesting.(reminds me a bit to the Project Magenta stuff I already have for GA and RJ and planned to purchase for 737)Will definitely look more closer to it since from the first view it looks like an alternative to PM for me.But since I have the PMDG 737NGX I am not 100% sure if I really need it.PMDG allows to drop out the PFD, ND, FMS CDU, engine displays to other monitors.(Have 2 graphic cards with 3 monitors)The performance of my PC does manage it with acceptable FpM.Also all (not only some) buttons and switches etc. could already be managed via Lua vars.Missing is a way to control the >100 annunciators and the gauges in the OVHD.Hope the SDK will cover it, if not than I'll go the other route....I totally agree that for somebody, who have the space to build a 1:1 shell + cockpitand can use beamers for the outside world, the Prosim737 approach is much better.Unfortunately I do not have that space in my room but I'm keen to have a complex simulationwithout the need of a mouse ....... at the moment I guess this could only be reached by building a "scale cockpit" - like my RC models ;-)

Do you really believe that the majority of cockpit builders, who know what PMDG 737NGX means, does not know what a SDK is?Have you ever tried to make GoFlight or OC or Leo Bodnar stuff working with PMDG 737NGX ?Maybe I have missed something but I could NOT make it working without writing FSUIPC macros and writing or using LUA scrips from other. (not even spoken about CPflight, Flyengravity, ITRA ,....)My request was truly made due to a misleading language in the manual that has said:"Our goal is to allow hardware manufacturers to create their own drivers so that the hardware can be made compatible with our software,...."This sounded for me that only commercial suppliers, who sign a SDK license agreement or something like this, will get access.But in the meantim people have routed me to posts, where PMDG have already stated that the SDK will be available for all.So I am (and I'm sure a lot of other guys too) will be happy and looking forward what we will get.

Great Idea! I am curiouse too!Hoepfully this comment will not lead in a further delay since now the lawyers who scratch their heads about the SDK EULA needs to consider a paragraph that ensures that the post secret will not be violated ... :(

Have you recognized it,the GoFlight webpage is back and looks not that bad....good move...

I hope they have the wisdom to make things as sophisticated as possible for the skilled developers of further SW products and as easiest as possible for people who pay their bills by purchasing this great 737NGX but being not neccessarily IT experts with the wish to create their own home cockpit......

Hi Paul,you might be right in some cases, but my request was really in front of the awareness that some programming skills are required.If you have ever used SIOC or LUA (even if you rework LUA scripts on LINDA) you would not be able to do it without any SW knowledge.To be honest the last time that I wrote some codes in my professional live was at the end of 's in "TURBOPASCAL", then I moved from SW development to business development.But with some help of other friends of this forum I learned relatively quick how to write LUA and SIOC scrips and I am sure a lot of other guys are in a similar situation. I am really excited to get the info how the SDK from PMDG will be structured and how it works.All inputs (switches, knobs, selectors, etc) could already be controlled via LUA var's - so no problem on this side.Some of the FSUIPC standard offsets are also be used by PMDG (e.g. flap position, speed, on air, .....)What I am looking for (and I know also some other guys who wants to know the same) is how to requestthe status of all annunciators and the gauges/displays in the overhead display.One hint I would like to have for the PMDG folks: As I was guided to a thread that already run in August last year, therePMDG has announced that the SDK will be available to all 737NGX customers, why do they still have this missleadinglanguage in the manual by end of the year (when I purchased it).I am sure a little change on the language would avoid any similar requests in future.... but I know how much developers like to update manuals and therefore please understand this only as a hint and in no way as a criticism...

Many Thanks Dennis,this is very much appreciated!I surved a lot but have not seen this - only discussions around timing, EULA and FS2Crew....probably have not looked enought back, since this was from summer last year.....

Hello PMDG folks,I asked the question already but unfortunately got no answer until now!Will this SDK made available to all end customers who have purchased the PMDG 737NGXor will it be made available only to commercial suppliers of Ad-Ons or hardware(as you mention it in the manual "PMDG 737 Introduction" on page 0.00.20)?I ask this questions since I am in a process of building my own cockpit usingBU0836X boards for inputs (which work already for a lot of functions of the glair and OVHD)and now I intend to use LED- and Servo control boards from open cockpit for annunciators and gauges.These boards require own scripts based on SIOC. It already works on my setup fore.g. flap indicator and gear control since for this you use the standard FSUIP offsets.But for a working OVHD or glairshild annunciators I would need the SDK.Therefore I like to ask if I "as an endcustomer" will get access to the SDK and can start purchasingthe control boards from Open Cockpit, or is it recommended to wait for an supplier whoprovides a plug and play solution like the OVHD from VRi.Any hint are very much appreciated.(If I have overseen a post that already have answered this question, please forgive me and guide me to it. I surved a lot but could not find a statement around this topic)ThanksDietmar

Hello Robert,In your post you made a clear commitment to the consumer market which is very much appreciated.In the manual "PMDG 737NGX Introduction and Use" I found following statement:"Our goal is to allow hardware manufacturers to create their own drivers sothat the hardware can be made compatible with our software, however sowith the PMDG 737NGX we are going to be releasing to them an SDKthat will allow hardware manufacturers to independently create drivers toensure the highest degree of compatibility.The only restriction that we place on hardware developers is that thesedrivers must be provided at no cost to their customers. This SDK may notbe available at release time but it will be made available a short time laterto interested, known hardware developers!"So here my question:Will this SDK also be available for your customers, who purchased the 737 NGXor will this only be available for commercial suppliers of hardware like GoFlight, CPFlight, VRi, OC, Flyengravity, etc.... ?Do I need to wait until these suppliers provide me a gateway / driver .....or will I become able to write my own scripts based on Lua or SIOC so that I can complete my own cockpit?Dietmar

Hi Francesco,could you get some success? Here is a further hint.I found a page with a brilliant Lua Tutorial.Looke at: http://www.anadrac.com/FSUIPC-Lua-Tutorial/index.htmlIt describes Lua and also the integration into FSUIPC that simplethat even me ( an old guy who wrote last time his own SW during BASIC and TurboPascal times 25 years ago.....)could understand it. In the meantime I'm also a bit familar with SIOC. I have the OC USB-Servo and LED output board and I alreadycan control the Flaps indicator gauge incl. the LED's. Unfortunately SIOC does not read Lvar's. Therefore some times you needto set an FSX offset via a Lua script, that NGX does not use and then read it via SIOC to control a LED. Not that straight forward but a solution until PMDG will publish an SDK.good luckDietmar

Hello Guenter,many thanks for that great help. I tested it and it works.In the meantime I also found a brilliant Lua Tutorial.http://www.anadrac.com/FSUIPC-Lua-Tutorial/index.htmlNo I start to understand how all that works. ... also what UB, UD and UW means......Great stuff and I guess via this it should be possible to control some more of the LED's in the PMDG 737 NGXalso without an SDK from PMDG (simply follow the logics described in the flight manual.....)Thanks again,Dietmar

Hi Artem,Great Job with LINDA v.1.11!I have one question:Via the LINDA Tracer you can set an FSUIPC offset to a value.e.g.: X2F80 to 0 or 1 or ... 5 ... this is autobrake to RTO, Off, 1, ....Is there any command for the LUA scribt available to set this value tothe FSUIPC offset via LUA?I use PMDG 737 NGX and control the autobrake via LINDA LUA commands.It works perfect. But my LED's will be controlled via OC LED-Output-Card and SIOC.Via SIOC I can only request FSUIPC offsets but 737 NGX does not use theFSUIPC offset x2F80. (only LVar's)I would like to add a command in the "737 NGX action.lua" after the LVar was set like: ipc.control(xxxxxx, yyyy) ' set offset x2F80 to z'Is this possible?ThanksDietmar

Oh I thought your routines are from an already existing LUA file....To be honest - I don't know at the moment how to setup a standalone LUA.I did what you proposed to write something for my GoFlight modules by trying to copy routinesfrom Steve but it has not worked. I could not trigger the buttons....Then I put each of my routine in a separate LUA with the name-methodology "function.LUA" and activated it in the FSUIP.INIAfter this I could see it as a button function in the FSUIPC button assignment.But I did not follow this method since it would have required to write dozents of LUA's.....Therefore I used my GoFlight moduls only for ON/OFF functions (e.g. Lights and AES).I wrote one macro with all the LVar's and then I assigned the buttons via FSUIPC.Let me check SIOC and may be in some days I know more ... or I am desperate as you .. ;-)But at least, test what you mentioned and tell me if it has worked.good luck,Dietmar