Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I've tried a bunch of times to get my Garmin 196 working with FSX as I did with FS9. I have a clean connection to the FSX computer. I've tried using the Port=WideFS as well as using the virtual serial port through my laptop.

I get this from the WideClient log:

********* WideClient Log [version 6.70] Class=FS98MAIN *********
Date (dmy): 14/11/06, Time 20:27:25.531: Client name is PT13547
      250 Opening GPSout port WideFS, speed=9600 -- FAILED!

Anyone know what is causing this to fail? My firewall is off.

From FSUIPC4.ini (registered):

[GPSout]
Port=WideFS
Speed=9600
Interval=1000
PosTo6Decimal=Yes
Sentences=AV400
GPSoutEnabled=Yes

And from WideClient.ini

[User]
Log=Errors+

[GPSout]
Port=WideFS
Sentences=AV400
Interval=1000
Speed=9600

Thanks in advance for any thoughts.

iniFiles.zip

ClientAndServerLogs.zip

post-14283-128689478154_thumb.jpg

Posted
I've tried a bunch of times to get my Garmin 196 working with FSX as I did with FS9. I have a clean connection to the FSX computer. I've tried using the Port=WideFS as well as using the virtual serial port through my laptop.

I get this from the WideClient log:

********* WideClient Log [version 6.70] Class=FS98MAIN *********
Date (dmy): 14/11/06, Time 20:27:25.531: Client name is PT13547
      250 Opening GPSout port WideFS, speed=9600 -- FAILED!

Anyone know what is causing this to fail?

Since nothing whatsoever has changed in the Client end of things, the above error must surely also occur on the same PC with the same WideClient and the same INI settings whether ot not you run FS9 or FSX. In fact WideClient doesn't even know whether you are going to be using FS9 or FSX or even FS98 at the the time it tries to open the COM port.

In this particular example "Port=WideFS" on the Client could never have possibly worked on FS9 either. In the Client INI you must tell it which COM port to send the data to. It cannot open a port called "WideFS"! The WideFS setting is for GPSout, to tell it to send it to Wideclient instead of a COM port. What WideClient are you expecting WideClient to send it to?

If you had it all working on FS9 why did you change the Client end at all?

Regards

Pete

Posted
That was just my latest iteration. I've tried Com1 on the laptop as well.

But you showed no log of that. What does it show then?

Why are you changing anything at the Client end in any case? That doesn't know or care whether you have FSX or FS9 at the Server.

I'm sorry, I really can't help without information to go on.

There was certainly a bug in the GPSout facilities in FSUIPC4.03 but it is fixed in FSUIPC4.04.

Regards

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.