Jump to content
The simFlight Network Forums

Simconnect/WideFS


Recommended Posts

Hello Pete,

I hope this has not been addressed already and I missed it.

It took a the better part of a week to properly config the Simconnect function. It all now works fine with all programs that need it.

Afterwords I noticed that the WideFS no does not function correctly. The indication I get is on the client machine and it only shows for a brief moment that there is a connection then goes away. This happens all the time.

The windows firewalls have been disabled on both the server and client machines and the linksys router have the ports open for the 8002 9002.

FSX, SP1 then SP2 installed

SDK SP1a

XPPro SP2 .net framework 3.5

Below are copies of all the files that you might need. If I missed any please let me know.

Thanks,

Steve

FSUIPC

------------

********* FSUIPC4, Version 4.30 by Pete Dowson *********

Reading options from "G:\FSX\Modules\FSUIPC4.ini"

User Name="Steve Reinard"

User Addr="skyhawk8@comcast.net"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX (SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

62 System time = 14:26:56

62 FLT UNC path = "\\HOMESERVE\Steve\My Documents\Flight Simulator X Files\"

62 FS UNC path = "G:\FSX\"

1594 LogOptions=00000001

1594 SimConnect_Open succeeded: waiting to check version okay

3656 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

3656 Initialising SimConnect data requests now

3656 FSUIPC Menu entry added

3719 C:\Documents and Settings\Steve\My Documents\Flight Simulator X Files\default.FLT

3719 G:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR

43156 System time = 14:27:39, FSX time = 14:27:01 (19:27Z)

43547 Aircraft="Cessna Skyhawk 172SP Paint1"

44750 Advanced Weather Interface Enabled

89500 Sim stopped: average frame rate for last 47 secs = 23.1 fps

96359 System time = 14:28:33, FSX time = 14:27:46 (19:27Z)

96359 *** FSUIPC log file being closed

Average frame rate for running time of 47 secs = 23.1 fps

Memory managed: 24 Allocs, 24 Freed

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

WideServer (this is the log that goes with the wideclient log below for the same session)

---------------------------------------------------------------------------------------

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 23/07/08, Time 14:27:39.468: Server name is HOMESERVE

15141 Initialising TCP/IP server

15156 Initialising IPX/SPX server

15156 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

15156 Failed to start IPX/SPX Server

15156 Initialising UDP/IP server

16031 Broadcasting service every 1000 mSecs

53344 Closing down now ...

Memory managed: Offset records: 24 alloc, 23 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

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

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

WdieClient

---------------

********* WideClient Log [version 6.75] Class=FS98MAIN *********

Date (dmy): 23/07/08, Time 14:28:20.578: Client name is HOMESUPPORT

610 Attempting to connect now

797 Server = HOMESERVE

797 Trying TCP/IP host "HOMESERVE" port 8002 ...

797Okay, IP Address = 192.168.1.100

813 Connection made okay!

1125 Connection closed by server!

1125 Attempting to connect now

1125 Trying to locate server: Need details from Server Broadcast

5797 Server = HOMESERVE

5797 Trying TCP/IP host "HOMESERVE" port 8002 ...

5797Okay, IP Address = 192.168.1.100

5797 Connection made okay!

6125 Connection closed by server!

6125 Attempting to connect now

8797 Server = HOMESERVE

8797 Trying TCP/IP host "HOMESERVE" port 8002 ...

8797Okay, IP Address = 192.168.1.100

8797 Connection made okay!

8938 Connection closed by server!

8938 Attempting to connect now

13797 Server = HOMESERVE

13797 Trying TCP/IP host "HOMESERVE" port 8002 ...

13797Okay, IP Address = 192.168.1.100

13797 Connection made okay!

13938 Connection closed by server!

13938 Attempting to connect now

15781 ****** End of session performance summary ******

15781 Total time connected = 2 seconds

15781 Reception maximum: 0 frames/sec, 0 bytes/sec

15781 Reception average whilst connected: 0 frames/sec, 0 bytes/sec

15781 Transmission maximum: 0 frames/sec, 0 bytes/sec

15781 Transmission average whilst connected: 1 frames/sec, 338 bytes/sec

15781 Max receive buffer = 0, Max send depth = 1, Send frames lost = 0

15781 ********* Log file closed (Buffers: MaxUsed 1, Alloc 4 Freed 4 Refused 0) *********

Link to comment
Share on other sites

It took a the better part of a week to properly config the Simconnect function. It all now works fine with all programs that need it.

It shouldn't need any "configuring". What on Earth were you doing for a week?

Afterwords I noticed that the WideFS no does not function correctly.

There is no relationship between SimConnect and WideFS, excepting that they both use TCP/IP and FSUIPC4 uses SimConnect and that has to be working for WideFS to work.

... and the linksys router have the ports open for the 8002 9002.

I've never had to tell a router to open specific ports. Does that mean all the others are closed? Possibly you've told SimConnect to use the ports needed by WideFS? That would most certainly clobber WideFS as SimConnect will grab them for exclusive use first.

Pete

Link to comment
Share on other sites

Pete,

I looked at what you said and went back and realized that I was working way to close to the problem. In trying to get it to work I was just throwing ideas at the problem. That's not usually the way I do things. That was out of frustration.

I had FUSIPC with WideFS running through the default port that is set and also set Active Sky X to run through the same port. I feel that's what was causing the problem. I changed the Active Sky X connection back to the recommended port and wouldn't you know it everything worked. I also had some other issues from having FSX installed for over 2 years and shared my computer with the wife. Not blaming anything on her but sometimes things are installed that conflict with what I have set up. Now she has her own machine.

In the end I ended by doing a complete uninstall and cleared all directories and registry entries to ensure a good clean install of the FS. Tested along the way and have not installed any 3rd party app's except yours and the SDK until all was good.

Thanks for the input and steering me in the right direction.

Steve

Link to comment
Share on other sites

I had FUSIPC with WideFS running through the default port that is set and also set Active Sky X to run through the same port. I feel that's what was causing the problem.

ASX uses SimConnect. If you give the Port which WideFS is using to SimConnect, it gets it first (because it runs before FSUIPC, of course). So when WideClinet sends to that port, SimConnect receives what is to it a complete load of rubbish, and sensibly closes WideClient's connection.

There's no shortage of ports. ASX suggest 500 to be well clear of others in common use!

Regards

Pete

Link to comment
Share on other sites

  • 2 weeks later...

I have more or less the same problem

If I include the 8002 port in the SimConnect xml file , WideClient connects Ok but after some minutes begins to log the following messages (in the Wide

nnnnn Sending Computer name and requesting base data ...

nnnnn Button Thread Started

nnnnn Button Thread Terminated

and continue to log this 3 messages forever

if, in the meanwhile I try to use for instance FS Commander 8.3 (Connect to FS), I receive the following message

Unable to Connect to Flight Simulator #14

If I remove the 8002 port in the SimConnect xml file, the the wideclient never connects OK

any idea of what is happening ?

regards

Jorge

Link to comment
Share on other sites

If I include the 8002 port in the SimConnect xml file , WideClient connects Ok but after some minutes begins to log the following messages (in the Wide

Do NOT tell SimConnect to use the ports WideFS wants tyo use, otherwise you are asking for WideFS to fail. Why on Earth would you deliberately choose the same port? :-(

If I remove the 8002 port in the SimConnect xml file, the the wideclient never connects OK

It isn't only the port in the SimConnect.xml file which may be fouling things up, but the one in the client's Simconnect.cfg file. I assume you've set that to 8002 as well?

any idea of what is happening ?

Whatever is going wrong with WideFS, it isn't going to be fixed by messing around with SimConnect files because it doesn't use SimConnect. If you aren't getting a WideFS connection the reasons should be shown in the WideFS files -- look in the WideServer and WideClient Log files!

Pete

Link to comment
Share on other sites

Pete

thenks for your support

I removed port 8002 from SimConnect xml and again wideclient is unable to connect with the wideserver

looking at the network activity I see requests that came from the wide client PC to the wideserver PC but the wideserver never answer the request

I was unable to see the wideserver log to if it is receiving something

the fsuipc.ini file is:

[General]

History=19ZVKPE3IM6AOEIGX81M2

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

WeatherReadFactor=2

WeatherRewriteSeconds=1

SimConnectStallTime=1

CustomWeatherModify=No

Console=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

ZapSound=firework

ShortAircraftNameOk=No

LogReads=Yes

LogExtras=Yes

[WideServer]

WideFSenabled=Yes

AdvertiseService=Yes

ProtocolPreferred=TCP

MaximumBlock=4096

Port=8002

Port2=9002

Log=Errors+

[GPSout]

Port=

Speed=4800

Interval=1000

PosTo6Decimal=Yes

Sentences=

GPSoutEnabled=No

[AutoSave]

AutoSaveEnabled=No

there is something wrong here ?

thank you very much

Link to comment
Share on other sites

I removed port 8002 from SimConnect xml and again wideclient is unable to connect with the wideserver

Probably because WideServer isn't running. WideClient only thinks it can connect to SimConnect when you used the same Port number, but of course it cannot talk to SimConnect -- they use entirely different protocols.

I was unable to see the wideserver log to if it is receiving something

If there is no WideServer log in the Modules folder, then WideServer is not active. Have you even registered it by entering your WideFS7 key when you installed FSUIPC4? Check the FSUIPC4.LOG. What does it say near the top about your FSUIPC4 and WideFS7 keys? What does the "About" tab in the FSUIPC4 options show (look to the bottom right-hand)?

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.