Pete Dowson

It isn't important to backup the FSUIPC.zip file -- the latest one is always available from http://www.schiratti.com/dowson in any case (and in fact there's a later DLL in the top Announcemet in this Forum). The more important thing to backup, or keep a hard copy of, is either the FSUIPC.KEY file, which contains your registration details in readable form, or the original email notifying you of same. This is sure to be because you are getting something wrong. I'm always amazed at the number of different ways folks spell their own names, even. All three parts (name, email, Key) must be exactly as originally notified and registered. Regards, Pete

I don't understand, I don't see any mistakes? You seem to have some good ideas. Sorry if I was coming over rather discouraging -- it's just that it is rather easy to underestimate what is involved in creating completely new applications, even if you have an SDK. Please don't let me put you off looking at doing it though. I'd be interested in any progress you make. Regards, Pete

Yes, true, but at least the GPS units come equipped with software and graphics for the application. Yes, just like a PC or PDA. Well, and programming. ;-) Okay. So are you going to take up the challenge? Regards, Pete

If you have the development SDK and you know how to write programs for Linux, then, yes, like any other PC or PDA there's no reason why you cannot write an FS-linkable application, at least for reception of GPSout data via the USB link (used as a COM port on the PC). For linking direct to FSUIPC you'd also need to write a PC application to handle the PC end of the USB link and the interface to FSUIPC. Not sure if it is worth all that trouble -- you are talking about a lot of development/programming work there. What application(s) are you thinking of? Most extensions of FS really demand more screen real estate, not dinky little things like this. Regards, Pete

Tuomas already told them back in 2003. The guy who helped him get me the AV400 format was quite pleased when it all worked. Garmin is a big amorphous company. Telling one guy, even in the right department, obviously doesn't have much effect! ;-) Regards, Pete

No, just re-register with the same details as before. Pete

As you should note from the details in the current Programmer's documentation, you should be writing to 089A instead so that add-ons using Fly-by-Wire or other auto throttle control systems (eg their own autopilot/throttle coding) can intercept and handle the throttles. Is this an aircraft with reverse thrust? It sounds like it isn't. Values from -16384 to 0 represent REVERSE thrust, though the maximum reverse is usually around -4096 (the exact value for the current aircraft is provided at offset 0B00). Anything lower than the minimum implemented for that aircraft will be ignored, of course. Evidently you didn't actually read my documentation for the offsets? Even the one for 088C does state -4096 to +16384. Regards, Pete

Well, in that case, either FSUIPC has never actually been registered, or someone or something has deleted the KEY file. The remedy in either case is to register again. Regards, Pete

Unfortunately the programs are written with their own "ShowWindow" code which overrides the initialisation instructions provided to Windows for their start-up. As you will see from the FSUIPC documentation, the "HIDE" option tries to get the program to hide itself. In fact it does actually say "it isn't very useful for many programs, unfortunately". You should look to see if the programs themselves can be set to minimze or hide. I don't know FSBUS, but if that MCP.EXE is the Project Magenta one you can certainly load that minimised or hidden -- I do myself. Also MCP747.EXE should get hidden with FS's screen over it. But in all three cases I think you'd do better to remove both the "READY" and the "HIDE". The only one I'm not sure of is FSBUS, but the other two can most certainly be started before FS even starts loading without any problems. Regards Pete

There are two possible ways: 1. Yes, a USB serial port adapter works very well. In fact these are more reliable and better performing (with Windows XP at least) than real COM ports are! And you can get them very cheaply if you shop around. 2. If your PCs are Networked together already, or can be for the price of a simply Cat 5 cable connection, then you could use WideFS instead. The current version provides facilities to send GPSout data over the Network, and the serial connection in the target PC is handled by a freebie driver bundled in the GPSout package. for this you need the latest versions of GPSout and WideFS -- see http://www.schiratti.com/dowson, or the top announcement above for even later versions of WideFS. Regards, Pete

Is there an FSUIPC.KEY file there? Have you reinstalled Windows, or rolled back to a previous Restore point? Both of those may destroy the registration. It sounds like all you need to do is re-register, using the same details you originally received. If you have the KEY file they will be in there, or in the backup you made. There's only one version of FSUIPC, not a "registered" and "unregistered" version. They are the same, only you registering makes any difference. Regards, Pete

Yes, that's why I said "And this will allow FSUIPC to identify its correct .INI file, .ini." The part is the value assigned to ControlName, if you check back in the text. Well, of course it cannot be found unless you've added it to your CFG file. Once you've added it then obviously you will know where to "find" it. :-) No it doesn't put those files there. When I tried it /CFG: option caused FS to look in the FS9 folder -- it only creates a new default if it couldn't find the file you specify. If it behaves as you say now, then it must have changed in 9.1 I assume. The way it worked before was most likely an error in any case. Can you tell me what you want different FSUIPC.INI files for please? The original reason folks wanted to do that was for different Joystick calibrations and mappings. Now, with the current FSUIPC versions, you can have aircraft-specific joystick settings (like Buttons and Keys), I am a little puzzled why you still need separate files. Regards, Pete

Yes, of course, though it has 6 positions not 5. If the rotary switch is a rotary encoder, giving pulses on one button in one direction, and on another in the other, then you could program it directly in FS in any case -- FS supports a "DECREASE AUTOBRAKE" and an "INCREASE AUTOBRAKE" control as it stands. You can access these through FS's Button page drop-downs too. If you do really mean a rotary switch with separate wired connections to give different button inputs on each of six positions, then use the added FSUIPC control (also in the drop downs) called "Autobrake set". You use the Parameter field too -- 0 for RTO, 1 for Off, 2-5 for 1,2,3,Max. Just program each position in turn, in the Buttons page. Regards, Pete

What message was that? It doesn't sound familiar. What does FSUIPC on the first options page in FS (ALT M F)? Version number? What does it say about registration? Maybe your FSUIPC.KEY file got deleted? Pete

Okay, good! So it was the "over-accuracy" of the Lat/Lon. Thanks for testing. I'll release this GPSout as 2.61 officially at the beginning of December -- I've a few other updates timed for then, for other modules. Regards, Pete

This is simply because the PMDG 600/700 package was released before the more recent release of FS2004 (version 9.1). The version of FSUIPC.DLL it installs is not able to work with the revised version of FS2004 because it didn't exist when it was written! All you need to do is download and install the latest version of FSUIPC -- get it from http://www.schiratti.com/dowson. Pete

Reading my own TXT file for GPSout I see AV400 was also called ARNAV or KING format. Using Google I did find one short document, though it isn't definitive enough. Here's an extract: Now the output from GPSout, set to AV400 mode, looks like this (this is an actual example with my aircraft stood on the threshold of 24L at EGCC z00265 AN 53 209329 BW 002 165398 C237 D000 QW061 T---------- w01@ The z00265 gives the latitude in feet, AN 53 209329 is the Latitude, N53 degrees 20.9329 minutes BW 002 165398 is the Longitude, W002 degrees 16.5398 minutes C237 is the track in degrees D000 is my speed QW061 is the Mag var 96.1 degrees West) Now, you will note that GPSout is actually providing the latitude/longitude down to 4 decimal places of minutes (i.e. 1/10000ths instead of 1/100ths). Now I don't know now if this is correct according to the original information I received, wherever and whenever that was. However, it doesn't accord with the data I found above, so I'm wondering now if some Garmin devices are programmed more flexibly than others, and yours is restricted to being as per the extract I found. Either that, or I have messed up the AV400 format in recent updates. :oops: Anyway, to check please try the attached test version 2.601, of GPSout. Let me know please. If this works I'll release it generally in due course. Regards, Pete GPSout2601test.zip GPSout2601test.zip

Rightso that's presumably where I got the AV400 format from? This will be the document I can't find at present. But this was about two years ago -- the files (and emails) will be long deleted, maybe archived (I get about 2000 emails per week so I cannot keep them all on-line!). Regards Pete

Yes, of course. You calibrate the two throttles on page three of the Joysticks tab ("Separate throttles per engine"), and check the option which says "Map 1->12, 2->34" You can also fly a three engined aircraft by an option to map 1->12, 2->3 (for symmetry only the centre engine is then separated). >> Of course I realize that operating single engines would not be possible then (only seeing two engines as one). << Yes, it will be -- just use the throttle assigned to engine 1. This is actually covered, albeit perhaps a little briefly, in the FSUIPC user documentation. It's in the Joysticks section, in paragraphs starting with "There are four special cases you may want to deal with". Take a look. Regards, Pete

Test it on a default aircraft. If it is something peculiar to the Dreamfleet 727 then you really need to ask them. All the reverser is doing in FSUIPC is sending appropriate negative thrust values to all engine throttles. The usual problem is that the normal throttle(s) is/are not quite in idle, but that stops you going into reverse, it doesn't stop you coming out. Does the 727 go into reverse using the F2 key to keep decrementing thrust? If you do this till it gets to maximum reverse, does it come back out gradually on pressing F3? Regards, Pete

Use the electric trim on the yoke, as real pilots do. Never use the trims on the console except for initial setting up: they are "trim pots" not aircraft trim wheels. My test rig is still using a Jetliner console, but there really is no more development I can do for it. Everything works as needed, and you can re-program pretty much anything you want through FSUIPC. Regards, Pete

No, not at all. That, as I said in my last reply, is Garmin's protocol for transferring routes, fixes, track logs and so on. It is nothing whatsoever to do with making the GPS into a mere moving map for another GPS position source. Did Tuomas send me something? I am at a loss to know what you are talking about I'm afraid. Can you give me a reference? I implemented the AV400 facility in GPSout years ago. I cannot even find the original specification now. But check in the "Interface Settings" section of your Garmin manual. You'll see some definitions, like: * Aviation In -- allows the unit to commiunicate with a Garmin panel-mounted GPS ... * Garmin -- the proprietary format used to exchange waypoint, route, track log data ... * NMEA -- supports the input/output of standard NMEA 0183 data ... Of these GPSout supports the first and third. The second has absolutely no provision for driving the GPS unit as a moving map! Regards, Pete

FSUIPC doesn't use its own terms. All the FS controls use the formal names Microsoft defined for them, as defined in its "CONTROLS.DLL" (which is where FSUIPC reads them from), and listed in the List of FS2004 Controls which is included in the FSUIPC ZIP for your convenience. The "CRS" value is known as the "OBI" (probably for Omnidirectional Bearing Indicator, but I'm not sure). There are these FS controls: Vor1 obi dec Vor1 obi inc Vor2 obi dec Vor2 obi inc The NAV1 radio is linked to the left CRS, OBI1, and the NAV2 radio to the right CRS, OBI2. I think the term OBI is used on light aircraft, CRS (course) on airliners. Regards, Pete

I've seen all that stuff before. It's for transferring tracks, waypoints, routes and stuff like that. I don't think you will find anything in there about GPS data input, which is what you are wanting. Fixes (i.e. waypoints) are to do with plans you download to your GPS so it can follow them. All that stuff is to do with using your GPS for the purpose it was designed -- i.e. a GPS. With FS and GPSout you are only wanting to use it as a moving map, not a GPS at all. I prefer using a PC for that as the screen is bigger and clearer and there is a wider choice of maps. but some folks do want to use the GPS instead. However, this uses that GPS in "simulation" mode, wher its own GPS hardware is switched off and all you are really using is its display. Regards, Pete

No idea, sorry. But your cable must be fine if you get some good data. Pete