compilot

That did it Pete! It works perfectly! All is well again..... Thanks Nick P.

I knew you could do it Pete! I'll be waiting to test the new version as soon as I see it. Cheers! Nick P.

Hi Peter, In my last post I uploaded a ZIP file with both Portmon logs and the entire FSUIPC.ini file. Cheers! Nick P.

Hi Peter, That is funny indeed... I know how it feels when you know that it shouldn't be, yet it is.... I've used Portmon to gather the results from simply swapping the FSUIPC.DLL from v4.12 to 4.152. It looks like the Word Length is different between the 2 versions: from 8 to 7 for whatever reason. I hope that helps! Good luck! Nick P. GPSOutBug.zip

Hi Peter, I'm using GPSout with my Garmin 196 and Garmin 296 (COM1, 9600, 1000, AV400). These work very well up to v4.12. Immediately after updating FSUIPC from 4.12 to 4.152, GPSout no longer works. However, if I re-install the 4.12 DLL, it once again works perfectly. I know that there is data being sent since I connected my RS232 tester. The speed looks good but I can't measure it. The .INI corresponds to the settings displayed in the FSUIPC dialog box. Any suggestions? Best regards, Nick P.

Thanks for the hints Pete. I've managed to pinpoint the problem. It was as simple as pushing the ON/OFF button on COM1! By pure chance, I've never encountered this before despite having played with the buttons many times!

I'm using the PFC Cirrus II and Avionics stack with MSFS v9.1. I've installed FSUIPC v353 and PFC v1921. Everything works well except that COM1 and COM2 are switched when controlled within MSFS. That is to say, if I change COM1 in MSFS, COM2 is changed on the avionics stack. Similarly, COM1 on the stack changes COM2 on the screen. I've looked through the options, but can't find the reason. Any clues why? Thank you for your kind attention.

Sorry for the mixup in description. I'll try to be clearer in the future. I agree that diasabling COM1 might do it. I'll have to try that a little later. Thanks

As I mentioned in my post, I had connected my Real GPS (a G196) to COM1. I used the cable that comes with the GPS. That works perfectly! The Lowrance emulator has no docs other than the actual manual. I guess that I'll have to search some more. Thanks just the same.

Thanks for quick reply Pete. I have read several posts. Maybe not all. I have already managed to run my Real Garmin GPS from one PC via WideClient. The Real GPS accepts the data from the PC's COM port. In this case I set WideClient to COM1. However, I've just been experimenting with the Lowrance Emulator on the same non-MSFS PC with WideClient. The emulator is not receiving data. I set WideClient's INI to COM1 which failed. I then installed the COM emulator and setup COM11 & COM12. I then changed WideCLient INI to send the data to COM11, which also failed to get a response from the emulator. Now I'm asking for suggestions.

Just read the posts.... That's excellent info! I would like to know I can have MSFS on one PC, and the emulator work on another PC. Will the COM emulator included in GPSOUT work? If so, how do I set it up? Does the Lowrance emulator expect data from a COM port? Is so which one and can it be changed?

Thanks Pete.... I'll post a message as soon as soon as the WideView Forum is back on line.

I'm using FSIP (FS Instructor's Panel - http://www.fsip200x.com/) with WideFS and WideView. This software allows me to change the Weather as well as many other parameters. When I change the weather, only the server's weather changes. The WideView clients do not change. I tried to send the "Update Remote Weather" command from the WideView server, but it doesn't change. I'm forced to change weather on the server from the MSFS menu. Then I can use the WideView to update the remote clients. Is there something that can be done to get the weather updated to all the WideView clients connected in the network? Do I need to install WideFS on all the PC's?

Thanks Pete..... As always... excellent job! Cheers!

Thanks again Peter... I'll check it out as soon as possible. One other point, I did as you said and pressed the "Predefined Set" button. That caused the drop-down list to restore itself to the same one as the Jet. The "Carb Heat/Anti-Ice" selection appeared for the Prop! I'll try to figure out a pattern if possible. Best regards...

Thanks for the insight Peter. I'll give it try and I'll report back with my findings. Best regards...

Hi Peter, I'm not sure if I have a some other problem, but when I load PFC v1913, it has the "Carb Heat/Anti-Ice" control by default, on both Jets and Props. However, when I load v1.920, the "Carb Heat/Anti-Ice" is simply not there for the Prop (see screen shot). Best Regards....

Hi Peter, Thanks for the reply. Interestingly enough, I did un-install and re-install all the network components and finally removed the network adapter and re-installed it and its driver. I also upgraded the network adapter's driver. No luck. As a further test, I swapped the existing network card with a brand new one of a different brand. I spent the better part of an entire day trying to figure out which component was hanging WideFS up. All this, to report that WideFS Client is still hung up. What I should add is that the log reported that WideFS was connected and running. Even Task Manager showed that it was running. But the "Hour Glass" cursor was still running. My final test was to re-install Win2K, which as you know, fixed it for good. I might add that I have another computer which has the same problem. This computer has a different MB and Net card so I can't say if its really a hardware problem. I haven't re-installed Win2K since I don't need to run WideFS Client on it. I just tried it for testing purposes. The problem still exists on this 2nd PC. Best Regards...

I've spent some time trying to figure this out with limited success. However, I can say that it has nothing to do with the number of screens connected to the PC. That was just a coincidence. The only fix to the problem was to Re-install the operating system (Win2K). It now works properly. I still have one PC with the same problem. I'll just wait for Peter D to get back. He may need some additional info, so I'll hold off Re-installing Windows 2K.

That's very nice work Frank! We've modified the PFC equipment to better reflect a real cockpit. As a commercial pilot with multi-IFR experience, it is very important that any experience picked up in the Sim be easily transfered to the real aircraft. Naturally there are some limititaions such as the main front view which is a BugEye screen, which has to be centered with the pilot. The result is shown in the picture previously posted. We are currently building another Sim which uses a real aircraft fuselage (see http://www.montrealaeroplus.com/images/JS1_Controls.jpg ). In this case we are using SimKits guages and our own Dual Yoke Design which has built-in electric trim. We're hoping to offer this for sale to the public sometime this year. This setup also uses Wideview for a projected set of outside visuals. Keep up the good work! Cheers!

I've just installed WideFS 6.47 for the first time on a Client PC with Win2K and dual screens using an ATI Radeon 9250 dual head AGP card. As a benchmark I've also installed WFS Client on a generic single screen PC which uses Win2k and another on W98 single screen. All are configured with IPX protocol. When I run WFS on the single screen Win2k or Win 98, it connects instantly and the cursor goes from the "Hourglass" to "Pointer" in less than 1 second. When I run WFS on any of the 2 PC's with dual screen Win2k, it connects instantly and the cursor stays on the "Hourglass" until the PC freezes up. I am able to stop WFS via the Task Manager and I noticed that the Log file closes at the same time. It looks like WFS is waiting for something to happen... forever if possible! Does anyone know how to fix this? Cheers!

Thanks for the additional information. The PC is an AM64 with 1Gb RAM and SATA Hdisk using WinXP SP1. Its dedicated to FS so everything has been shut down. However, you've given me inspiration to look even deeper. I may have missed one. I'll check the registry. Sorry about the links. I just noticed that there is an extra character at the end of each link ")". Here they are again: http://www.montrealaeroplus.com/public/ALTair.jpg As you'll see here we have a C2 also.... http://www.montrealaeroplus.com/public/BE1_GPS.jpg Cheers!

Hi Frank, Thanks for the tip. However, the people that own PFC controls are not required to buy FSUIPC so they normally won't have it. The PFC doesn't have a choice for it (see http://www.montrealaeroplus.com/public/ALTair.jpg) I'm assuming that this is something that both Peter D and PFC would like resolved. By-the-way, what kind of setup are you running? We've got 5 screens on 1 PC using BugEye and Parheleia + ATI with twin GPS on a Touch screen http://www.montrealaeroplus.com/public/BE1_GPS.jpg). The only problem is stuttering every 12 sec. I don't know if its the DLL? Regards....

Hi Peter, I just installed the v1.92 of the PFC DLL. I noticed that the carb heat (ALT AIR SWITCH) on my Cirrus II panel no longer functioned. I checked out the settings and noticed that Carb Heat is assigned only to the JET controls. There is no selection for PISTON A/C. Can it be added? Cheers! Best regards, Nick Papadopoli, P.Eng. President / Technical Director Montreal AeroPlus http://www.MontrealAeroPlus.com