I have just completed the first phase prototype of a G1000/GPS500/Audio Panel using the excellent Beta Innovations GammaTron and Simconnect. This is a test bed for a complete G1000 solution using an LCD monitor in the future. I wanted to make sure I have all the pieces in place prior to going further with the project.Simconnect is very nice, Event ID's are easy to use and much less cryptic then offsets. I have currently incorporated Beta Innovations SDK into a C++ program that is both XP and Vista compatible. Currently, assignments are hard coded, however I am working on an interface to allow modification without re-compiling. The device and driver works great. I will be using higher quality rotaries (I am using Bourns PEC11 which create too much noise), and using more eye pleasing tactile switches in the future.The final plans include:GPS500 separated and use a small LCD, with Audio panel using LED's mounted above. The G1000 will use dual concentric rotaries with push buttons, realistic tactile switchs with LED's in the bezel, audio panel in the middle, and the incorporation of LCD's to emulate both the PFD and MDF.Also, all metal construction.img:http://forums.avsim.net/user_files/189576.jpg

>Simconnect is very nice, Event ID's are easy to use and much>less cryptic then offsets.This is because there is a look up table translating the names to internal "cryptic" numbers just like "offsets" (FS control numbers or event numbers). It takes an extra call to establish a link between your chosen ID and the internal one, and an extra look up thereafter on every access. In FSUIPC I actually assign the FS event ID as the chosen ID, though I doubt this makes it any quicker.For FSUIPC it would have been dead easy to make a #define list giving names to all the offsets -- in fact in FS98/FS2000 days many did. But, unlike SimConnect, which is now static until FSXI, for FSUIPC it would always need extending and changing to keep pace with the ever expanding needs of the community. And I do mean always -- at least once a month for the last 10 years.SimConnect was supposed to be like that -- expanding as needed -- but, unfortunately, as always, other priorities overtook it.So, with the only thing "cryptic" about having something like "0E8E" instead of "DEW_POINT" the solution is#define DEW_POINT 0x0E8E(Pardon my C).There are lots of good things about SimConnect and I do hope it will eventually allow me to retire from FSUIPC updates -- in fact when I first discussed SimConnect with Microsoft way back I had high hopes that it would have done by now. Alas, there looks to be no end as yet ...RegardsPete