Pete Dowson

C. I don't know or use C++. My only computer languages are ASM and C (previously BCPL before C was invented). UIPCHello is in C in any case. If you copile it as a C program, not C++, it should be fine. Check you have the name of the LIB correct as well. It has an _ character in it I think, and case is possibly important too. Pete

Okay, easy enough. Actually, there's a GSV option already in there -- has been for a long time. Just seems to have missed mention in the docs. Sorry. Here is what it would have provided: $GPGSV,1,1,04,01,45,000,50,02,45,090,50,03,45,180,50,04,45,270,50 Anyway, I attach test version 2.581 which includes the above values. See if that meets your needs. Regards, Pete GPSout2581test.zip

The P8, T8 and RP48 displays merely consist of 8 LEDs numbered L0 to L7. In the GFdisplay documentation I give full examples for the other modules, which provide more complex cases -- but most of those also have LEDs. It is surely easy enough for you to apply what you can learn from the documentation and many examples to the simpler modules. If there's something you don't understand about the examples, please go ahead and ask specific questions. Then I'll know what improvements to make to the documentation. But I didn't want to try to program everything for everyone. That isn't the purpose. It is a toolkit for folks to do exactly what they want. Regards, Pete

I evidently don't understand VB at all. What is actually setting or changing value in the variable you are writing to 0B7C? What is "8372890"? Where are you reading and using the tank capacity, or are you assuming it is fixed (i.e. doing this for a specific aircraft)? You seem to be updating something AFTER writing something else. It always worries me when I see arithmetic like Val(100) + argNum / 8372890 * (128 * 63556) What is done in what order? Do you know? I always use parentheses to force the order I know I want. In particular, if "argNum" is the +1 or -1 passed as a parameter, then dividing it by 8372890 will surely give zero!? After all, it is declared as a "long" so it isn't capable of storing fractional values is it? Pete

I found the problem. Typo in the code! Thanks for finding and reporting it. I've replaced it by version 3.499a now, see the Announcement. Thanks again! Pete

But filled with what, and why? Well, I can't tell if it is worthy. If you can explain the point of such fixed fictitious data then, yes, of course I will consider it -- if you provide the exact data it will be easy enough. I don't actually need checksums, they are calculated dynamically. Regards, Pete

That sounds like a good idea. But if it also actually Reads the data from FSUIPC (which probably it doesn't, from your description), it would need something like an "FSUIPC_Process" call to actually do the read. We shouldn't encourage the use of lots of separate "Read-Process" pairs, which are grossly inefficient. Maybe a library with calls for popular specific variables, a generic call for others, then a separate "Process" entry which actually does the business, including the conversions of the known (named?) variables. The unknown unnamed ones would still be provided "as is". Thanks for the suggestion, and the potential offer! I look forward to seeing what transpires! :wink: Regards, Pete

An lever, any axis, assigned to spoilers will have a position, somewhere very near fully retracted, which will arm the spoilers. It's a positon on the movement of the spoiler arm -- play with the FS graphic and you'll see what I mean. However, do NOT test this on the ground -- FS will let to arm the spoiler okay but it will then immediately deploy them fully because of the ground situation. Take the aircraft into the sky then find the "arm" position and mark it. No more so than any other calibration. I have considered having a sort-of centre area which could be calibrated for this, but it is a lot of work and on the whole I really don't think it is necessary. The simple axis position method does work -- provided you have some feedback so you can see when it is armed. Regards, Pete

3.499 was only just released yesterday. Were you testing 3.498 before that? It has been on release there for a while. The change from one to the other is only a fix to the PTT via WideFS. Ah, so you presumably hadn't tried 3.498. I expect it was a change somewhere in the 17 test versions since 3.48 then. Oh dear. I'll check this out. Thanks. Pete

Sorry, I know about indications in FS. I use Porject Magenta and have the same indications. I don't need to run FS. All I am saying is that I've never written a program to do what you want to do. You need to do that. I wouldn't have thought the tank capacity would change with altitude. Why should it? The pressures can't be great enough to compress or expand the casings surely? I really don't know in any case. Please use FSInterrogate and observe the levels as you climb or descend with fuel cut off. It shouldn't be complicated, it's just simple arithmetic isn't it? Regards, Pete

Well, I've never done this and it isn't an area I know about, but this is what I would theorise: 0AF4 is the factor for calculating fuel weight given capacity. At different altitudes and therefore different pressures the measured capacity will vary for the same weight, so that figure will change. Use it together with the tank capacities and levels to calculate fuel weight in pounds, per tank, as you say. Regards, Pete

Unless you are using FS2000 there's no need nor point in messing with or even looking at the FS CFG file for these things. That example was necessary in order to configure some things back then. The numbers you are referring to are actually set in FS's dialogues -- go to Options - Settings - Controls - Sensitivities. There are two sliders, one for sensitivity (should be at maximum) and another for null zone (should be at minimum). if those are wrong you'll get less resolution and/or range from your levers. Regards, Pete

Ahthat's not likely to be anything related to registration in any case. BTW doesn't Jose support AIBridge on his own website? Yes -- there is no such thing for user-registered copies as all that part of the checking is thereby bypassed. Sorry I can't help any further. Actually, if it is possibly anything to do with its FSUIPC interface (which is unlikely as Jose knows that well and won't have changed it for that version) then an FSUIPC log with IPC Read/Write logging enabled might help -- but keep it a very short session as it will get very big very quickly. It sounds more likely to be related to the MP interface for FS2004, which will be the new bit in version 3 of AIBridge I should think. Regards, Pete

What is the symptom? AI bridge was designed to work with Squawkbox 2. I don't think it is at all needed with the current on-line flying programs. Also, is the gauge working without multiplayer, with normal AI traffic, but not with MP traffic? If so it may be the way it was programmed. The MP traffic have distinguishing IDs, so this can be done. Regards, Pete

Three problems there: 1. Version 3.1 is not supported. It is very old -- 2 years old next month in fact. Please see the Announcements at the top of this page. 2. The data at 6xxx was not even added till after that version. 3. You will not get reliable access to FSUIPc unless you register FSUIPC as a user (i.e. purchase it). Regards, Pete

What's the problem? Just go to the Buttons tab in the options, press the button, and set it to send the F9 key. That's all. Please tell me why you cannot figure this out from the documentation. Is it a language thing? Pete

That "darn button" isn't there because a User Registered FSUIPC does not need any application keys whatsoever -- in the user registered version ALL applications get free access. This is actually mentioned in the documentation as one of the advantages of registering. It's this paragreph in the "What you get if you pay" section: Pete

You need to calibrate with the minimum set whilst your levers are ABOVE the minimum, and the maximum set whilst your levers are BELOW the maximum. Always leave a little "dead" zone (unused part) at either extreme. If you are calibrating in FSUIPC just follow the steps one by one. If you are using CH's control manager then I don't know -- see Bob Church's help over on http://www.ch-hangar.com. He has prepared some documentation on setting up the CH quadrant. If you are mixing the two I think it may get rather complicated, but hopefully Bob's details will help. Why is that? Is English not your first tongue? Sorry if so, but the Manual has stood the test of time -- those step-by-step instructions for calibrating have been pretty much the same for five years with very few complaints. If you can point out exactly what "confuses" you maybe I can improve them, but you'll have to be very specific. Regards, Pete

I don't know, you'd need t check aircraft manuals for that. But you can alter the fuel levels up or down. Pete

Did you search for "fuel" rather than "refuel", or even "tank"? There are up to 11 fuel tanks and there are two offsets for each -- one giving the capacity (fixed per aircraft) and the other the current level (as a proportion of capacity). You can write to the latter to set the fuel levels. Note that the fuel tanks are in two groups -- one of 7 and the other of 4. This is historical, the 4 separate ones were new in FS2002 whilst the other 7 date back to FS98 or before. Pete

Yes, but that also is the GROUND altitude, NOT the height of the aircraft. The ground altitude is NOT displayed in FS!!! You seem very confused as to what you actually want to read! When you have decided, THEN look it up in the documentation, please. AND please please PLEASE use FSInterrogate to actually look at all these things, live, and see how they read and convert there. It is supplied as a tool explicitly to help you sort these things out for yourself! Regards, Pete

Where is this * (65536# * 65536#) * 360# from? What does # mean in Visual Basic? In FSInterrogate # is used to mark "the value". But I din't know what you mean by it. Please check the documentation again. It says that the heading at 0580 is multiplied by 360 and DIVIDED by (65536*65536) to get degrees TRUE. You seem to have three multiplications. I don't understand where you are getting your incorrect information from? Or is it just a simple typo? Regards, Pete

The FS window Shift+Z does NOT show the GROUND altitude, it shows the AIRCRAFT altitude -- of course these will almost never be the same! Not only that but you are reading a 2 bytes value into a 32-bit (4-byte) variable, I think (forgive me if I'm wrong -- I don't know VB). You need to zero that beforehand to avoid getting rubbish. Hmm. Please think about things a bit longer and decide whether what "height" it is you want (aircraft, ground, VOR, NDB, Eiffel Tower? ;=)), then go find the correct offset and conversion in the documentation. Please also use FSInterrogate to investigate these things. It is provided for a reason. Regards, Pete

Ah, "BT = Blue Tooth", not "British Telecom"! . I should have guessed. However, everything else seems okay so I won't remove it. Thanks, Pete