Jump to content
The simFlight Network Forums

GPSout problem


Recommended Posts

Hi!

I'm having troubles with the GPSout function via WideView. I've searched a bit around the forum but didn't find the answer yet. I've just purchased FSUICP and WideFS7 a few hours ago.

I'm trying to have my Flightsim PC send an GPGGA sentence to a WideClient on another PC. I've followed the instructions from the manual. In FSX's 'add-on' menu, I enabled the GPSout to WideFS.

I've checked the settings on the FSUIPC4.ini file on the FS computer:

[GPSout]

GPSoutEnabled=No

Port=COM1

Speed=4800

Interval=2000

PosTo6Decimal=Yes

Sentences=GGA

So that seems okay to me. On the client-computer, I've added the following lines in the WideClient.ini file:

[GPSout]

Port=1

Speed=4800

When I launch the WideClient application, it waits for a connection from the hosts PC. When I fire up flightsimulator, the client says 'Connected', so that seems okay.

However, there is no serial data coming out of the serial port. I'm using 'Virtual Serial Port Emulator' to create a COM-instance which can be opened by 2 applications at the same time, and 'RealTerm' as the terminal program. I know my way around serial ports as I do a lot of engineering for my job, so I'm prety sure that my serial port setup is correct. However there's nothing coming through.

This is the WideServer.log file:

********* WideServer.DLL Log [version 7.80] *********

Blocksize guide = 8192 (double allowed)

Date (dmy): 18/02/12, Time 21:40:43.140: Server name is YOUR-BC081B8812

15546 Initialising TCP/IP server

15546 Initialising UDP/IP server

16046 Broadcasting service every 1000 mSecs

17671 Incoming connection Accepted ok (skt=3824) TCP

17875 Connected to computer "LAPTOPJVH" running WideClient version 6.940 (skt=3824) TCP

17875 Client capabilities: 04 (GPSout) (skt=3824) TCP

103671 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP

110312 Close signalled to clients

111421 Closing down now ...

Memory managed: Offset records: 68 alloc, 67 free

Read buffer usage: 39 alloc, 39 free, max in session: 1

Write buffer usage: 2671 alloc, 2671 free, max in session: 1

Throughput maximum achieved: 20 frames/sec, 603 bytes/sec

Throughput average achieved for complete session: 5 frames/sec, 170 bytes/sec

Average receive rate from "LAPTOPJVH": 0 frames/sec, 17 bytes/sec

********* Log file closed *********

So I guess it has something to do with the 'Error 10013'.

However, I'm not a network specialist.

Any help would be greatly appreciated!

Thanks a lot!

Jens

Link to comment
Share on other sites

I've checked the settings on the FSUIPC4.ini file on the FS computer:

[GPSout]

GPSoutEnabled=No

Port=COM1

Speed=4800

Interval=2000

PosTo6Decimal=Yes

Sentences=GGA

So that seems okay to me.

Why do you say that? You haven't even enabled the GPSout function to start with (can't you see that, above?), and you've left it sending to serial port COM1. Please go to the GPSout settings in FSUIPC Options in FSX, and read the FSUIPC4 User Guide chapter on how to set it up!

[GPSout]

Port=1

Speed=4800

What's "Port 1"? Serial ports have names, like "COM1"! Just as documented!!!

Seems you are not actually referring to any documentation before you start?

BTW WidevieW is a totally different program by a different author!

:-(

Pete

Link to comment
Share on other sites

Hi Pete,

Thanks for the quick reply.

Seems I made a copy/paste error refering to the FSUICP.ini file, actually just before I posted the question on the forum, I tried if I was having the same problem with the 2nd GPSout output, so I disabled the first one (just in case). I had actually enabled it before and changed the port to 'WideFS' :)

I guess the problem was that I, as you say, refered to the COM port as '1' instead of 'COM1'. Haven't tried it out yet, but this seems logic. It would have made more sense for me if there had been an example in the user manual instead of just giving the syntax as 'COMn' though.

I can assure you that I've spend a whole amount of time reading the user guides.

Thanks a lot for the quick response!

Jens

Link to comment
Share on other sites

I guess the problem was that I, as you say, refered to the COM port as '1' instead of 'COM1'. Haven't tried it out yet, but this seems logic. It would have made more sense for me if there had been an example in the user manual instead of just giving the syntax as 'COMn' though.

Oh dear. look: it's actually better than an "example", it is the correct format and it tells you to add it as it is, i.e.


[GPSout]
Port=COMn
Speed=n
[/CODE]

All you needed to do was copy it and just change the values to suit your setup! Surely that's explanation enough, and better than a specific example which might not be at all applicable and need changing in any case?

It's certainly not scuppered anyone before to my knowledge!

Pete

Link to comment
Share on other sites

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.