GPSOut across a wired network

[John Fee]

I am running FSXSE in a Win10 PC. I use Sky Demon for navigation - undocked to a second monitor.

I explained the method here https://forum.simflight.com/topic/76431-gpsout-for-sky-demon-in-fs9/#comment-465701 (read down to my second post).

Now, to reduce the CPU load I would like to install Sky Demon on a second W10 PC.  So I need to find a way of taking GPS output from the flying PC.

I cannot figure out a way of doing this - maybe it is not possible?

I would be grateful for advice.

 

[John Dowson]

T

1 hour ago, John Fee said:

So I need to find a way of taking GPS output from the flying PC.

There are two ways - either via a cable or using WideFS.  From the FSUIPC4 User guide (GPSout section):

Quote

You will need to connect your flying PC to your moving map PC with a serial “null modem” cable (i.e. send and receive crossed over), and configure your map program accordingly. Alternatively, if you use WideFS you can tell GPSout to send the GPS data to the Client PCs. You will need to configure those in the WideClient.ini files. A virtual serial port program (freeware) from MixW is available from my Support Forum. You can use this to generate a pair of linked virtual serial ports to connect between GPSout and a receiving program on the same PC, or between WideClient and the receiving program on a client PC. Either way, no cables are needed with this method.

John

[John Fee]

Thanks! This is a good help. I will try the WideClient method first.

I have WideFS but not WideClient.  Should WideClient be installed on the flying PC, or the client PC, or both? 

 

[John Dowson]

WideFS is WideServer + WideClient. WideServer runs on the FS PC and is built into FSUIPC4 (and later versions - previous to FSUIPC4 it ran as a separate application). WideClient runs on the client PC.

[John Fee]

Sorry, yes, of course.

As you can see I'm pretty rusty.

If/when I get Sky Demon working using WideClient, I will update this post with details.

[John Fee]

I've not been able to get this working.

Relevant logs and .ini files are attached. Also a screenshot of the Virtual port driver.

Firewalls are all off.  All relevant folders are shared with Full Access - files are easily moved from one PC to the other.

I am running FSX-SE in Windows 10. Perhaps STEAM software is causing some problem?

Or maybe I missed something obvious.

I'd be grateful for help. 

FSUIPC4.ini WideClient.log FSUIPC4.log WideClient.ini

[John Dowson]

WideClient isn't connecting to WideServer/FSUIPC.  You need to sort this out before anything else. Please see the WideFS documentation on connection issues (check your Workgroup name!), as well as other forum posts. Do you see '...wth WideServer waiting for clients' in the titlebar of FSX? If so, WideServer is running but WideClient is not connecting - you need to correct this before anything else.

14 hours ago, John Fee said:

Firewalls are all off.

All firewalls - client, server and routers?

Your FSUIPC4.log file shows that this was attached while FSUIPC was still running - please ALWAYS exit FSX/FSUIPC before attaching files. And also please attach your WideServer.log file the next time.

 

[John Fee]

On 10/3/2024 at 12:05 PM, John Dowson said:

Do you see '...wth WideServer waiting for clients' in the titlebar of FSX?

Yes.

All firewalls - client, server and routers?

I have a 24 port Cisco switch. I have disabled the client and server firewalls but I am not keen to disable the Virgin modem/router firewall.

 

The Workgroups are the same.

When I attempt to run Sky Demon, I get a banner message across the map 'Waiting for data'.

I've attached files again as requested.

Thanks!

WideClient.log WideClient.ini FSUIPC4.log FSUIPC4.ini WideServer.log

[John Fee]

Update

I have just discovered that the client laptop (Dell) reverts to WORKGROUP instead of the correct name - OSBORNE.

I have no idea how or why, it is not in a domain.

This may explain at least part of the problem.

Edit

I'm detecting other problems with the LAN. Up till recently I had no problems. These all started with a second-hard A rated Dell laptop. 😢

[John Dowson]

2 hours ago, John Fee said:

I have just discovered that the client laptop (Dell) reverts to WORKGROUP instead of the correct name - OSBORNE.

Ok, although i don't know why you previously said 'The Workgroups are the same'!

Once that is corrected, try again. If you still have issues, try setting the ServerName (or ServerIPAddr) and the Protocol - see the WideFS User guide, and also the WideFS Technical guide for troubleshooting network issues.

2 hours ago, John Fee said:

I'm detecting other problems with the LAN. Up till recently I had no problems. These all started with a second-hard A rated Dell laptop. 😢

Ok, but you need to sort this out - I can;t help with this...

John

[John Fee]

The WORKGROUP names were the same when I posted, i.e. OSBORNE.

Problem was when I rebooted the laptop, it made an uncommanded name change to WORKGROUP, unbeknownst to me! 

The explanation (in case others have a similar problem) were incompatibilities between Windows 10 Home (PC server), and Windows 10 Pro (cllent).

I appear to have these fixed now so that the Workgroups are the same (hopefully permanently) and the sharing of files and folders is permitted.

 

Quote

try setting the ServerName (or ServerIPAddr) and the Protocol

That's for tomorrow. Thanks again!

[John Fee]

John

Success! 😀

Setting ServerName=Belladonna;  Protocol=TCP in  WideClient [config] worked some magic.

I do not know if I did correctly, but I set Port=8002 (was 0) and Port2=9002 (was 0). I realise from the documents that 9002 is for folders.

If wrong it seems to have done no harm. 

If you think it would be of interest I can write a full version of how we did this for posting in User Contributions. Setting up GPSOut for Sky Demon in FSX-SE is clearly not always straightforward.

I posted how to do this for FS9 and FSX in User Contributions many years ago. Since then the Sky Demon set up has changed somewhat. I didn't bother you with that!

Thanks again for all your advice and interest.

[John Dowson]

2 minutes ago, John Fee said:

Success! 😀

Great!

3 minutes ago, John Fee said:

If you think it would be of interest I can write a full version of how we did this for posting in User Contributions. Setting up GPSOut for Sky Demon in FSX-SE is clearly not always straightforward.

Yes, I am sure that would be helpful for others.

Regards,

John