Nobster

Pete, well, now you made it! Thanks a lot. The values for Engine # 1 (0898) and Engine # 2 (0930) do work just fine. In case I should find some other problems I will let you know. Well, since the DC-3 does have only 2 Engines I am not able to test the values for Engine # 3 and #4 but I will keep my eyes open. Again (and I am sorry if I repeat myself here over and over again and I am sorry in case you are getting sick of reading this over and over again :roll: ): THANKS A LOT for this kind of support which is just assume! Best Regards Nobbi

Pete, you are the hero (at least for engine #1!)!!!! I downloaded and used version 3.618 now and for Engine1 (0898) everything looks just perfect. How ever, offset 0930 shows me complete different values now: Full Throttle: #0898: 15658 #0930: -32628 Idle: #0898: 6580 #0930: 4696 Those datas I got from FSinterrogate and FSUIPC 3.168 while FSLook do show me always the same numbers which are comparible with offset #0898 now. I know where the negative value is coming from, but the numbers itself do look very different to me. The aircraft I used was again the Bar...err DC-3... Again, thanks for your great support! / Nobbi

Sorry Pete, I don't want to bug you on this too much. I am just curious if you had a chance to look into this problem again. Sorry again about the mess with the Baron58. Thanks Nobbi

Pete, ups. Sorry about the Baron. Please have a look at the stock DC-3 which comes with FS9. There you will see the problem. I have no idea why I wrote Baron 58. Sorry! Well, here are the numbers (I produced them with the FS9 stock DC-3): RPM shown by the Gauge: ~1100 (idle) Value by FSinterrogate2std (0898): 3707 Value by FSLook (Engine_N1_RPM): 6590.88 Calculated RPM using 0898: 610,894 Calculated RPM using Engine_N1_RPM: 1086,143 RPM shown by the Gauge: ~2700 (full throttle) Value by FSinterrogate2std (0898): 8995 Value by FSLook (Engine_N1_RPM): 15992.2 Calculated RPM using 0898: 1482,330 Calculated RPM using Engine_N1_RPM: 2635,433 I hope this helps. Sorry again about the Baron58. But as I said, those values are coming from the stock DC-3. Actually I am not writing any application at all. But I am using those instruments from Simkits ans when I face problems with the RPM Gauges I started to have a look at it. Thats how I approached you. Since those Simkits guys do use the offsets 0898 and 08C8 they are provided me the wrong values for my DC-3 but the right values for people who are using a C-172 or a Baron 58 ( :oops: ). I hope those values do help you to chase the problem. thanks Nobbi

Pete, only your support is worth it the money for FSUIPC and WideFS already! This does impress! Thank you! Well, I have checked offset 2400 and I get the same readings like 0898*08C8/65536 which means a "wrong" value for my DC-3 and a right value for the C-172. The interesting thing is that FSLook is getting the right thing. I know, the program is 6 years old already (regarding to the help dialog). You wrote that there is maybe a mismatch between the aircraft and the FS version. What do you mean by this? Thank and best regards Nobbi

Dear Pete, I do face a problem here and I thought maybe you are able to show me the right direction. My problem is getting the right RPM value for some aircrafts. I am talking about the following Offsets: 0898 and 08C8 I use the standard Cessna (172) which comes with FS9 and I use the values provided by FSUIPC (3.6) in order to calculate the RPM (H898*H8C8/65536) I do get the right RPM value. If I use my favorite MAAM DC-3 aircraft and I do the same calculation I do get a value which is much lower. The same happens if you use the standard Baron 58 which comes with FS9. So far the problem. Now my question: With the FSUIPC SDK comes a program called "FSLOOK". If I start FSLook and have a look at the values provided by this program I found the following: There is a variable called "Engine_N1_RPM". If I use the standard 172 Cessna from FS9 the "Engine_N1_RPM" value is equal to 0898 provided by FSUIPC or FSInterrogate2std. If I have a look at the same values but using now my Gooney Bird it starts to get interesting: FSLook is giving me a different value for "Engine_N1_RPM" then FSInterrogate2std or FSUIPC. Using the FSLook value for the calculation (Engine_N1_RPM*H8C8/65536) is giving me the correct RPM value. Now my problem: I have no idea where this value "Engine_N1_RPM" is coming from. The help function from FSLook says "FS2000 Token Varialbe Display" and so I assume the problem is coming from the airplane itsself since it is supposed to compatible to FS2002 and not a FS9 only model. But somehow FSLook is able to provide the right value. My question to you now: Is it possible to get the value provided from "FSLook" through FSUIPC as well? Thank you for your support in advance and thank you for all the hard work to the simmer community. Best Regards Nobbi

Jan, read the word document "FSUIPC for Programmers" provided with the FSUIPC SDK: Offsets 0892, 092A, 09C2 and 0A5A is what you are looking for. Cheers Nobbi

I do pgram an interface for the GR256 from BetaInnovation right now. All you need is a registered version from FSUIPC, the rest will be freeware. For those who are interested, please email me: nobster@gmx.de Cheers Nobbi