pmdg overhead

[jonnydaz53]

hi all im wondering if i built a overhead panel for pmdg aircraft how much of it can i get working ie 25% 50% ...

regards john d

[737NGDriver]

Actually with the new FSUIPC it has very easy key mappings to the PMDG overhead panel, and this I mean without having the panel actually open.

[ian@737ng.co.uk]

hi john......
quite correct, using the FSUIPC mouse macro's, you can get everything working. if it's modelled and in there, you can get it operating. and even if there is no macro for a specific switch, it's sooooo easy to record one.
and again correct, you do not have to see the panel to work the switch. the bonus is that you still hear the 'click'.
so the answer is 100% of all modelled controls can be operated.
have a great day...... ian

[kiek]

Yes, you can get all the controls working but that is only one way... You still have the problem how you get the information about the states of lights, leds, annunciators, and so on, ...

So I'd say you can get 50% of the PMDG Overhead working.

If you want to have 95% (!) you better switch to the Level-D 767-300 ;-)
Wth its free SDK and my free lekseecon and lekyoucon programs you have as well all the information about states as all the commands for controls (for the complete cockpit).

lekseecon is for Opencockpits SIOC users and lekyoucon for FSUIPC users.

The two way communication goes digitally (!), no key-commands, no mouseclicks, no emulated mouse clicks, no mouse macro's, :-)

Cheers,
Nico Kaan
www.lekseecon.nl (http://www.lekseecon.nl)

[ADW]

So I guess what is really needed for us B737 drivers is a combination of Petr Dowson's excellent macro feature to activate the switches to satisfy the PMDG logic, and in parallel the use of SIOC to drive the annunciator lights.:)

Just got to figure out how to do it now!

[kiek]

... and in parallel the use of SIOC to drive the annunciator lights.

Yes but that still will not work now, because information about the state of annunciators, leds, and so in, is not available...

[salautom]

Yes Nico, I know you like to promote your excellent lekseecon software, but there are people who like to fly PDMG stuf.....
anyway, I found some solutions for interfacing screen info to SIOC (and I know, there are some difficulties) so you can read the state of the annunciators, etc.

here is one link:

http://www.opencockpits.com/modules.php?op=modload&name=Forums&file=viewtopic&topic=4140&forum=5

and I think when you look around more, you can find more solutions...

[kiek]

Yes Nico, I know you like to promote your excellent lekseecon software, but there are people who like to fly PDMG stuf.....
No, i'm not promoting my leksecon software because that can only be used for the Level-D 767.

I only stress the fact that add-on developers should deliver an SDK together with their add-on (paid or non-paid). That would make life of cockpit builders a lot easier.

[kiek]

http://www.opencockpits.com/modules.php?op=modload&name=Forums&file=viewtopic&topic=4140&forum=5

I'm not impressed... ;-)
Read the comment I have posted in that thread (sometime ago).

[ian@737ng.co.uk]

hi guys....
i agree 100% with nico regarding the SDK. without it there is no way to retrieve data from your add-on. now a lot of us enjoy the PMDG, but in it's current form, there is only so much you can do with it. in the absence of an SDK, i have had to manufacture my own logic system for the overhead annunciators and use the FSUIPC mouse macro's to operate the switches. an 'untidy' solution, but it works. it's the best i can do without access to internal information from the aircraft.
i am reliably informed that there is a 'test' version of the NGX doing the rounds, so let's hope PMDG decide to 'focus on the customer' and make the SDK available when they release it, which i believe is scheduled for 3rd quarter 2009.
but if they do not, i have a cunning plan :o)
so in an ideal world, PMDG would issue an SDK for the NG or better still, why don't LVLD develop a 737. now there's an idea.
happy new year to you all and regards from the welsh borders..... ian

[GSalden]

By using Key2Mouse you can assign keystrokes to mouseclicks.

By putting the overhead on a (hidden) monitor you can "connect" every part of each aircraft to your hardware.

This also works for all other cockpit parts.

Myself I am using this to get everything from the PMDG MD-11 to work.

[737NGDriver]

GSalden, I hate to tell you but Key2Mouse is preety much absolete, with the new Mousetrapping feature of FSUIPC, read this thread from the begginning you'll see what I mean.

[GSalden]

It doesn't matter , the idea was that every aircraft can be used in a cockpit ptoject.

[kiek]

It doesn't matter , the idea was that every aircraft can be used in a cockpit ptoject.

Not really...

With key2mouse, or even better with FSUIPC mouse macro's, you can use about any aircraft if you want to build a "50% cockpit" project (controls only).

If you want to build a "98% cockpit" (controls and state information) you can achieve that with Level-D 767 only... ;-).