Pete Dowson

What was wrong? Was it a manually entered key, listed in the documentation? Regards, Pete

Have you checked with PortMon as I suggested? Is perhaps Windows doing some unwanted power management on the USB subsystem -- I have heard that can cause problems. Also, the first time I tried a USB serial adapter on a PC with Windows XP, the exchange of data dried up and stopped after a number of minutes. This wasn't with GPSout, but my PFC equipment driven by my FS PFC driver. It worked fine under Win98. It turned out, eventually, to be the drivers supplied with the serial port USB adapter. Although they purported to be suitable for WinXP it seems they were designed and tested in WinNT4 days and obviously didn't work properly in XP. I found later drivers which then worked fine and have done ever since. In fact, once you get a good adapter with properly working drivers they are better than a "real" serial port! Even stranger that in over six years of GPSout's availability no one has had this problem before, or at least no one has mentioned it. No, please check things out with PortMon and investigate your drivers. All the code used in GPSout for driving serial ports is rock solid basic Windows API stuff which has seen good use in at least a dozen of my programs over more years than I like to count, including Fax software which is very testing of serial port usage. Regards, Pete

GPSout relies only on being woken up by Windows at the intervals you set. It's always worked fine for many years with no changes to this. that sounds more like something queuing or blocking on your serial port. Are you using a true serial port or a USB with serial adapter? The only changes which have been made to GPSout over the years have been to add additional sentence options (such as the AV400 format) and to correct the course from the bearing when it was found that the GPS course from FS was suspect. Nothing has been changed in either the way the timing is set nor in the actual serial port handling for about six years -- ever since it was written, in fact. It really does sound like there's either something wonky with the serial port you are using or with the receiving end. Try checking the GPSout activity on the port with PortMon (a free utility from http://www.systeminternals.com) and also try port another if you have one. If the output from GPSout looks okay with PortMon (and it is easy to see it all with that utility), then you will need to investigate your receiver. What's "Error 34"? What reports that? Doesn't it say anything else? Having the original disks isn't as important as having an original installation. The update doesn't look at your disks. Regards, Pete

It's actually Enrico Schiratti's site. I just downloaded and checked, and you are correct -- although Enrico has written it up as 1.90, he hasn't actually changed the ZIP for the new onle I sent him in July!!! I'm sure it used to be okay. I think he must have slipped up when he trasferred all the Schiratti sites to new Servers. I'll write to him and get it sorted. Thanks! Pete

I think ActiveSky controls most of those options. including wind smoothing, in any case, when it is running. Have you checked the ActiveSky documentation? Regards, Pete

Hold it there first. What does that mean? "loading the information on the flight yoke ..."? Have you calibrated your flight yoke in Windows, or in the CH driver? Get it working reasonably well in FS before even attempting to do anything in FSUIPC. All FSUIPC offers is more accurate end and centre points with possibilities of null zones, response curves and filtering. But the input values need to be reasonable to start with, otherwise you will have problems. Delete your FSUIPC.INI file, or at least the section for Joystick Calibrations. Calibrate your yoke properly in Windows. Load up FS and make sure the assignments are correct and the sensitivity is high and null zone low. Test it all to make sure it works. If you cannot get this far you need help from CH, not me. THEN try calibrating in FSUIPC, following the steps in the documentation. If you come back for more support please always state the version of FS and the version of FSUIPC you are using. Regards, Pete

Well, there's no attempt whatsoever by the program to provide a Key. Please re-check the documentation. Possibly the author intended users to enter the Key manually. Else, either it is the wrong version (possibly an FS2002 version?) or a mistake has been made by either the suppliers or author. Please feel free to cut and paste this entire message and send it to them in your request for assistance. If I can find the author's email, I will point him to this thread as well, Regards, Pete

Good, glad you resolved it. Regards, Pete

It is easy to prove. Delete the FSUIPC.KEY file. Now see if those programs run okay. None of them need a user-registered FSUIPC in any case, they are all accredited aircraft. You only need to pay for FSUIPC is you want to use the additional facilities. But you paid for ATR Flight 1, PMDG 737 NG, PSS A320 Phoenix? Or are all those stolen too? You think FSUIPC is an easy program to write and maintain, despite it being a full time job for five years? You think I should give it up and do something else for a living? :cry: Pete

What's a "replied" key please? Do you mean you are illegally using someone else's key? :cry: And you even expected support? Hmm. :x To register FSUIPC (or WideFS) correctly and legally as a full user you need to purchase the key from one of the suppliers. The easiest way is to go to SimMarket. Check http://secure.simmarket.com/product_info.php?products_id=538. Regards, Pete

I think you should be able to include pictures actually in your message, probably by using the "Img" button instead the the "URL" button. But your way does at least keep the message size down, and is better for those who don't want to look at the pictures. This is tremendous. I am very jealous of your practical abilities, for I have none. I can just about wield a soldering iron and build circuits -- provided I have good clear instructions, but when it comes to making anything solid that works or looks good, count me out. I have to stick to programming! :wink: Thanks for showing us, Regards, Pete

Hmm, those are certainly the correct details for the program as notified to me, so the Key should work -- if it is built into the program, as it should be. In order for me to determine whether it is writing the key correctly, could you repeat this test, exactly as above, only before loading FlightTracker go into the FSUIPC options (ALT M F), find the Logging page, and enable IPC read and IPC write logging. Keep the session short again. Remember to turn off the extra logging next time you load FS or it may make rather large files. If the Key is not built into the program then I can only assume either that it is an older version, or that the author intended that user's should manually enter the key. But then the latter would be published with the documentation. Since the Key was issued way back in July 2003 and this is the first such inquiry I've had, I can only assume something is wrong with the specific package you have. However, let me see the fuller log, then we will know and you can be more specific when you request support from the suppliers. Regards, Pete

Sorry, you misunderstood me. I currently use is Visual Studio .NET 2003, but of all the stuff they forced me to pay for, all I use is C and the excellent debugger (the latter being the main reason I moved up from Version 6). The Visual C++ system handles C or C++. It's one of the arcane ritualistic properties, somewhere deep in the menus. If you find your compiler and linker properties and show me them I'll compare them to mine and tell you what's different, if you like. Regards, Pete

FlightTracker was granted an FSUIPC access code in July 2003. As far as I know it uses this to gain automatic access to FSUIPC, with no special action needed by you. Please let me see the FSUIPC log file. Regards, Pete

I only use C. Possibly you need to put some sort of C wrapper around the declarations so that it doesn't mangle C names like I think it does with C++? I'm afraid all those Microsoft C/C+ compiler settings are a rather an obscure black magic art to me. I just do the simplest things, like add the library to the list of libraries it says it wants, and to make sure the LIB file is in my project folder where it can find it. Surprisingly, I've not had this sort of question in all 5 years since I supplied this stuff, so there must be a lot of folks who know what to do, precisely, for C++. I hope one of them can jump in and help. Regards, Pete

Run any one of those which has a problem, close FS, ZIP up the FSUIPC.LOG and FSUIPC.KEY files you will find in the FS modules folder, and send them to me at petedowson@btconnect.com. It sounds very much like a user registration problem. I very much doubt that it is a problem in 3.411, but so far out of several reports no one has sent me the files I need to resolve this. Regards, Pete

Version 3.xxx registrations cover ALL version 3.xxx issues. If it is a legitimate access key you should have no problems. I am concerned by this. Please Zip up a complete FSUIPC.LOG (after FS is closed) together with your FSUIPC.KEY file and send them to petedowson@btconnect.com. Regards, Pete

That's part of FSUIPC's heading data. It is always there. Have you enabled IPC read/write logging? Please show the file, not one line. Oh, that. Just add 'FS2004' to the end of the list and change the array size to 7. As you saw, FS2004 is #7. That's why I asked to see the FSUIPC log with the IPC logging enabled. Hmmit sounds rather like something may be wrong with your registration. What happens if you temporarily remove the FSUIPC.KEY file from the FS modules folder? Let's start againPlease do as I said to start with, i.e. ... enable IPC read/write logging in FSUIPC's logging page, run it, get the error, then close FS down, the Log file (FSUIPC.LOG) produced in the FS Modules folder will tell me what is going on. Regards, Pete

I'd really much rather understand WHAT in the manuals you don't understand. This is the only way they'll get improved so that I don't get asked the same questions over and over. I told you exactly what to do in FSUIPC. Did you manage that? Please clarify exactly what it is you are asking and why things are so obscure in the documentation. :cry: Regards, Pete

The source code shows where it checks these things, so as you are an expert in Delphi you would be in a better position to tell me what is going on. (I don't know Delphi at all). However, if you enable IPC read/write logging in FSUIPC's logging page, run it, get the error, then close FS down, the Log file (FSUIPC.LOG) produced in the FS Modules folder will tell me what is going on. Are you using a user-registered version of FSUIPC? Hmmm. The file "FPCuserIntf.INC contains this: // Supported Sims SIM_ANY = 0; SIM_FS98 = 1; SIM_FS2K = 2; SIM_CFS2 = 3; SIM_CFS1 = 4; SIM_FS2K2 = 6; SIM_FS2K4 = 7; The last one is for FS2004. What makes you think is isn't supported? Are you by any chance using a very old version of the SDK? Regards, Pete

This is WeatherSet.exe? (Not WeatherSet2.exe, which is only for FS2004). Correct? What version of WeatherSet (right clock the EXE and check Properties-Version). What version of FSUIPC? Run it, run WeatherSet, get the error, then close FS and show me the FSUIPC.LOG file (from the FS Modules folder) please. Regards, Pete

Neither FSUIPC nor WideFS send keystrokes or buttons over the connection to Clients. There is a mechanism in WideFS caled "KeySend", which sends an arbirary reference number across, 1-255. All you do it program a key or button in FSUIPC to operate the KeySend command, with a parameter 1-255 to identify it. Then in your selected WideClient.ini file you declare the key Press you want that KeySend number to create. This is covered in the WideFS documentation, and the KeySend is also mentioned in FSUIPC documentation. Please do have a look sometime. WideServer.ini doesn't come into it any more. That method, designed for ISA Epic cards, has not been the best method for several years. Regards, Pete

No, neither. The only thing that can stop it working is the one documented in the FSUIPC User guide: Sounds like you've changed that option or reinstalled video drivers or something, making that Windows option come back on. BTW, version 4 of FSUIPC isn't available for quite a while yet. You mean 3.411. Regards, Pete

Hey, how on Earth did you work that out? That's brilliant! I must give that a try when I get time. Incidentally, the GPSout.INI parameter is "Port" not "Ports". Thank you very much! Looks like I should add this to the GPSout files -- shall I credit you? If so would you rather a different name entered than "FunkyMunky"? :wink: Regards, Pete

Oh, what they used to be called the EFIS display -- there were things for that in FS98 and FS2000. Check the FSUIPC SDK Programmer's Guide, offsets 0E5A through to 0E68. I've no idea whether any of that still applies in FS2002 or FS2004. It looks like no one has ever tried it. If it does then you try setting an on/off control by using the Offset Word Togglebits control (in FSUIPC) with offset x0E5A and parameter 1. Try the FS2004 Forum, not far from here. Or else experiment with some of the assorted Pan and Eyepoint controls available. Sorry -- I haven't an answer. I would have to experiment to find one in any case, same as you. Regards, Pete