Lost Connection

[English Rebel]

I keep losing connection between my Server computer running FSX and my client computer running my avionics. Can someone please look at the logs and let me know where the problem lies so I can fix it. I just noticed the IP Address and it to connects over my WiFi network and not my LAN. Let me troubleshoot this first.

Thanks

Alan

WideServer log

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

Blocksize guide = 8192 (double allowed)

Date (dmy): 04/05/13, Time 11:52:30.947: Server name is FSX

15897 Initialising TCP/IP server

15897 Initialising UDP/IP server

16115 Broadcasting service every 1000 mSecs

28626 Incoming connection Accepted ok (skt=7336) TCP

28626 Restarting service due to zero reception!

32870 Incoming connection Accepted ok (skt=4204) TCP

37113 Incoming connection Accepted ok (skt=3720) TCP

41356 Incoming connection Accepted ok (skt=7336) TCP

86706 Incoming connection Accepted ok (skt=4600) TCP

86799 Connected to computer "AVIONICS" running WideClient version 6.991 (skt=4600) TCP

1545081 **** ERROR! Sumcheck or length fails on received block (skt=4600), len=351 (time=0)

1548950 Send ok but needed 5 attempts! (496 of 496 sent) (skt=4600) TCP

2257257 Send ok but needed 6 attempts! (564 of 564 sent) (skt=4600) TCP

ClientServer Log

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

Date (dmy): 04/05/13, Time 11:53:37.560: Client name is AVIONICS

94 LUA: "C:\Program Files (x86)\WideFS\Initial.LUA": not found

156 Attempting to connect now

156 Trying to locate server: Need details from Server Broadcast

156 Failed to connect: waiting to try again

2216 Attempting to connect now

4275 Server = FSX

4368 Trying TCP/IP host "FSX" port 8002 ...

4368 ... Okay, IP Address = 10.0.0.18

4665 Connection made okay!

9969 New Client Application: "LJ45_ASI" (Id=4264)

14321 New Client Application: "lj45_Altimeter" (Id=4752)

16178 New Client Application: "LJ45_ADI" (Id=3700)

22901 New Client Application: "Jet45_MFD DU3" (Id=2276)

26739 New Client Application: "Jet45_RMU FO" (Id=4500)

28673 New Client Application: "Jet45_RMU PILOT" (Id=5088)

30265 New Client Application: "Jet45_MFD DU2" (Id=2896)

32215 New Client Application: "Jet45_PFD" (Id=4756)

37020 New Client Application: "interfaceIT" (Id=4252)

133678 New Client Application: "PokeysRMUNoGear" (Id=4956)

1371936 New Client Application: "Jet45_CWP_Driver" (Id=2252)

1453821 WARNING! Send() request depth is over 100!

1456426 ERROR!! Send() request depth is over 250! Queue flushed!

1460357 WARNING! Send() request depth is over 100!

1471012 New Client Application: "FSInterrogate2std" (Id=4000)

[Pete Dowson]

I keep losing connection between my Server computer running FSX and my client computer running my avionics. Can someone please look at the logs and let me know where the problem lies so I can fix it. I just noticed the IP Address and it to connects over my WiFi network and not my LAN.

Best never to use Wifi for what you need to be an almost continuous flow of data in both directions.

Also, it would be much more efficient to use the UDP protocol instead of TCP. It is more prone to lost blocks, however.

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

Date (dmy): 04/05/13, Time 11:53:37.560: Client name is AVIONICS

94 LUA: "C:\Program Files (x86)\WideFS\Initial.LUA": not found

156 Attempting to connect now

156 Trying to locate server: Need details from Server Broadcast

Set the correct (non-WiFi) IP address explicitly in the WideClient.INI, and also set the protocol (whether TCP ot UDP).

Regards

Pete

[English Rebel]

Pete

Okay let me try that as I added the ServerIPAddr=192.168.0.1 to my WideClient.ini file and it appears that the connection was made over the LAN. However I still had a loss of communications. Here is the new ini file.

Thanks

Alan

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

Blocksize guide = 8192 (double allowed)

Date (dmy): 04/05/13, Time 13:17:04.105: Server name is FSX

15959 Initialising TCP/IP server

15959 Initialising UDP/IP server

16100 Broadcasting service every 1000 mSecs

49858 Incoming connection Accepted ok (skt=4212) TCP

49905 Restarting service due to zero reception!

54101 Incoming connection Accepted ok (skt=6964) TCP

58345 Incoming connection Accepted ok (skt=7348) TCP

62588 Incoming connection Accepted ok (skt=4444) TCP

67065 Incoming connection Accepted ok (skt=7348) TCP

67221 Connected to computer "AVIONICS" running WideClient version 6.991 (skt=7348) TCP

558874 **** ERROR! Sumcheck or length fails on received block (skt=7348), len=948 (time=29)

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

[English Rebel]

It was running TCP so was wondering what the last section meant.

Thanks

Alan

67221 Connected to computer "AVIONICS" running WideClient version 6.991 (skt=7348) TCP

558874 **** ERROR! Sumcheck or length fails on received block (skt=7348), len=948 (time=29)

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

After changing to UDP protocol, I still lost communication and this is the latest WideServer log.

Thanks

Alan

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

Blocksize guide = 8192 (double allowed)

Date (dmy): 04/05/13, Time 13:40:43.414: Server name is FSX

15943 Initialising TCP/IP server

15943 Initialising UDP/IP server

16099 Broadcasting service every 1000 mSecs

19344 Incoming connection Accepted ok (skt=8240) TCP

19469 Connected to computer "AVIONICS" running WideClient version 6.991 (skt=8240) TCP

2657477 **** ERROR! Sumcheck or length fails on received block (skt=8240), len=20781 (time=2)

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

[Pete Dowson]

Okay let me try that as I added the ServerIPAddr=192.168.0.1 to my WideClient.ini file and it appears that the connection was made over the LAN. However I still had a loss of communications.

Sumcheck errors can only possibly occur if there's a [rpb;e on your Network. TCP is supposed to guarantee the frames, so a block arriving in error means either a hardware or driver problem. I've only ever seen them when my LAN adapaterwas faulty -- replacing it fixed it. If it's a motherboard LAN then that's more problematic, maybe disabling it and installing a working one.

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

That's even more indicative of a real problem -- it's the once-per-second broadcast (IP=255.255.255.255 means broadcast) so that other clients can detect the server.

I'd strongly suspect the LAN hardware or driver on your main FS PC.

Pete

[English Rebel]

Pete

Thanks for interpreting that gobbledegook for me. :razz: Fortunately my motherboard has two LAN adapters so I'll try the other one. One question, I have a WideClient.ini on my client PC and a WideClient.ini on my server PC. It was the server PC WideClient.ini that I posted -- my client PC WideClient.ini had no error messages. Could you please explain that.

Thanks

Alan

[Pete Dowson]

One question, I have a WideClient.ini on my client PC and a WideClient.ini on my server PC. It was the server PC WideClient.ini that I posted -- my client PC WideClient.ini had no error messages. Could you please explain that.

You did not post any INI. The INI file is the file containing settings, like the IP address and protocol parameters I mentioned. You posted the WideServer.LOG file most recently, but the more informative original post had both the server and client log fies. They are named accordingly, not all "wideclient.ini" as you seem to refer to them as. Please don't confuse matters by using both wrong filenames and wrong file types.

Errors detected at one end of a connection won't necessarily also be detected at the other end! The two directions have different frames going in different directions! They are not the same frame received by both! That would make no sense! Think of a telphone connection. How often do you get bad reception whilst the other guy says he can hear you perfectly?

In any case the WideClient log you showed certainly had severe errors blocking the connection badly at one point: What do you think these are?

1453821 WARNING! Send() request depth is over 100!

1456426 ERROR!! Send() request depth is over 250! Queue flushed!

1460357 WARNING! Send() request depth is over 100!

Pete

[English Rebel]

Pete

Using the second port made no diiference. I shut everything down and restarted FSX and WideClient but now I cannot establish a connection (server say Waiting for clients). I pinged the server from the client and that ws good. Here are the two ini files to see if you can see a problem.

Thanks

Alan

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

ServerIPAddr=192.168.0.1

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=43,44,886,589

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

serverIPAddr=192.168.0.1

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[sounds]

Path=E:\Program Files (x86)\FSUIPC\WideFS\Sound\

Device1=Primary Sound Driver

Pete

Using the second port made no diiference. I shut everything down and restarted FSX and WideClient but now I cannot establish a connection (server say Waiting for clients). I pinged the server from the client and that ws good. Here are the two ini files that you asked for to see if you can see a problem. I have no idea what those entries mean.

Thanks

Alan

Server

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

ServerIPAddr=192.168.0.1

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

Client

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=43,44,886,589

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

serverIPAddr=192.168.0.1

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[sounds]

Path=E:\Program Files (x86)\FSUIPC\WideFS\Sound\

Device1=Primary Sound Driver

[Pete Dowson]

Using the second port made no diiference. I shut everything down and restarted FSX and WideClient but now I cannot establish a connection (server say Waiting for clients). I pinged the server from the client and that ws good. Here are the two ini files to see if you can see a problem.

Do NOT make any changes to the Server INI! It knows where it is. Only the Client needs to know where it is!!!

Also, in your earlier log the Server's IP address was

4368 ... Okay, IP Address = 10.0.0.18

Now you are trying to use

ServerIPAddr=192.168.0.1

Those two cannot even be in the same Netwrok! LAN IP addresses abide by a Network Mask, almost always 255.255.255.0, which means that the first 3 parts must be the same throught the network!

Additionally, if you specify the ServerIPaddr you must also specify the Protocol. i told you that!

:-(

Pete

[English Rebel]

Do NOT make any changes to the Server INI! It knows where it is. Only the Client needs to know where it is!!

I added the server address because it was originally connecting over WiFi (IP Address 10.0.0.18). I originally set the server on my wired LAN to 192.168.0.1

Also, in your earlier log the Server's IP address was

4368 ... Okay, IP Address = 10.0.0.18

Now you are trying to use

ServerIPAddr=192.168.0.1

Those two cannot even be in the same Netwrok! LAN IP addresses abide by a Network Mask, almost always 255.255.255.0, which means that the first 3 parts must be the same throught the network!

Please see comment above .

Additionally, if you specify the ServerIPaddr you must also specify the Protocol. i told you that!

Sorry, my bad.

Went back and added Protocol=TCP to the server and client ini files but still not connected. Client log says

Trying to locate server: Protocol not yet decided.

Do you have any idea what those other error messages mean (e.g. 1456426 ERROR!! Send() request depth is over 250! Queue flushed!)

Thanks

Alan

[Pete Dowson]

I added the server address because it was originally connecting over WiFi (IP Address 10.0.0.18). I originally set the server on my wired LAN to 192.168.0.1

Sorry, but those two addresses can never belong to the same LAN. I really don't know what you are up to.

Went back and added Protocol=TCP to the server and client ini files but still not connected.

I said DO NOT DO ANYTHING IN THE SERVER INI!!!

trying to locate server: Protocol not yet decided.

In that case you got it wrong! The protocol undecided can only occur if you let the Client find the Server automatically.

Do you have any idea what those other error messages mean (e.g. 1456426 ERROR!! Send() request depth is over 250! Queue flushed!)

Yes, it means there are over 250 frames queued waiting to be sent over the network which is obviously just not accepting any of them!

It does actually say that.

Pete

[English Rebel]

Pete

I think you misunderstood what I said. Originally WideFS was using my WiFi network because in one of the client logs I saw the IP Address 10.0.0.18 which is my WiFi network. To stop that from happening (and according to your user guide) I set IPAddr=192.168.0.1 and Protocol=TCP (the IP Address I assigned to my server PC) in the WideClient.ini file. SO they were never on the same network one is WiFi and the other is a wired LAN through a switch that connects the server and client PCs.

I found out why I could not get a connection. When you told me that I probably had a bad network adapter or adapter driver, I switched the cable on the server to a second adapter on my MB. However I forgot to change the IP address of the new adapter. :oops: I just fixed that and now have a connection.

Next step is to remove these lines in the WideFS.ini file as you told me :oops: and see if my network losses have gone.

ServerIPAddr=192.168.0.1

Protocol=TCP

Thanks

Alan

[Ian P]

Alan,

Just checking here, because I'm getting confused, let alone anyone else, but are ALL your connected computers on the same IP range - i.e. 192.168.x.x or (not and) 10.x.x.x?

If one is on 192.168.x.x and the other on 10.x.x.x then that's in all probability the issue. Provided you only have one DHCP server live - or use all fixed IPs - then both your wireless and wired connections should all be on the same subnet, not different ones.

Cheers,

Ian P.

[Pete Dowson]

I think you misunderstood what I said. Originally WideFS was using my WiFi network because in one of the client logs I saw the IP Address 10.0.0.18 which is my WiFi network. To stop that from happening (and according to your user guide) I set IPAddr=192.168.0.1 and Protocol=TCP (the IP Address I assigned to my server PC) in the WideClient.ini file. SO they were never on the same network one is WiFi and the other is a wired LAN through a switch that connects the server and client PCs.

I have never heard of hasving two completely separate networks which cannot talk to each other yet are using the same computers! That's truly a first for me. Why would you set it up like that? Just to have everything wireless or everything wired, no one knowing about the other? No wonder things get confused. I'm amazed that it (almost) works!

If you want a simple life I would change your wireless network to use IP addresses in the same subnet, i.e. 192.168.0.xxx.

Regards

Pete

[English Rebel]

Guys

Sorry if I confused everyone. Its tough for a seventy year old chap to keep up with all this stuff. :mad:

Ian

The client PC and the server PC are on a wired LAN with IP address 192.168.0.1 and 192.168.0.2. The Gigabit LAN adpaters is where I set the addresses for each PC. The WiFi is a completely different adapater and my WiFi router LAN sets those addresses in the format 10.0.0.X. By setting the IPAddr=192.168.0.1 in the client ini file I make sure that its not using the WiFi network to connect -- which it was before (and the mention of 10.0.0.18 is probably where everyone got confused).

Pete

Everything connects oaky but soon after I start to load up the connection by starting the engines, my connection starts to fail. This is the client ini file and clientlog. Hope I have put everything back to the way it should be. :neutral:

Thanks

Alan

CLIENT INI FILE

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=0,0,160,38

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

ServerIPAddr=192.168.0.1

Protocol=TCP

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[sounds]

Path=C:\Program Files (x86)\WideFS\Sound\

Device1=Primary Sound Driver

Device2=Digital Audio (S/PDIF) (High Definition Audio Device)

Device3=Digital Audio (S/PDIF) (High Definition Audio Device)

CLIENT LOG

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

Date (dmy): 05/05/13, Time 11:25:27.250: Client name is AVIONICS

93 LUA: "C:\Program Files (x86)\WideFS\Initial.LUA": not found

93 Attempting to connect now

93 Trying TCP/IP addr 192.168.0.1, port 8002 ...

156 New Client Application: "Jet45_CWP_Driver" (Id=2252)

3822 New Client Application: "FSInterrogate2std" (Id=4000)

21138 Error on client pre-Connection Select() [Error=10060] Connection timed out

21138 Ready to try connection again

22199 Attempting to connect now

23213 Error on client pre-Connection Select() [Error=10061] Connection refused

23213 Ready to try connection again

24242 Attempting to connect now

62665 Trying TCP/IP addr 192.168.0.1, port 8002 ...

188277 Connection made okay!

648434 Received shutdown offset code = ADBC

648434 FS closing down (param=ADBC), disconnecting

648434 ********* Interim performance summary *********

648434 Total time connected so far = 458 seconds

648434 Reception maximum so far: 32 frames/sec, 1061 bytes/sec

648434 Reception average whilst connected so far: 31 frames/sec, 997 bytes/sec

648434 Transmission maximum so far: 286 frames/sec, 18858 bytes/sec

648434 Transmission average whilst connected so far: 277 frames/sec, 8919 bytes/sec

648434 Max receive buffer = 483, Max send depth = 20, Send frames lost = 0

648434 **************** Individual client application activity ****************

648434 Client 2252 requests: 192040 (Ave 419/sec), Data: 38170167 bytes (83340/sec), Average 198 bytes/Process

648434 Client 4000 requests: 258 (Ave 0/sec), Data: 8303 bytes (18/sec), Average 32 bytes/Process

648434 ***********************************************

648543 Received shutdown offset code = ADBC

656187 Connection closed by server!

656187 Attempting to connect now

656187 Trying TCP/IP addr 192.168.0.1, port 8002 ...

677231 Error on client pre-Connection Select() [Error=10060] Connection timed out

677231 Ready to try connection again

678245 Attempting to connect now

722425 Trying TCP/IP addr 192.168.0.1, port 8002 ...

722425 Connection made okay!

722550 Connection closed by server!

722565 Attempting to connect now

722565 Connection made okay!

1130087 New Client Application: "LJ45_ASI" (Id=1948)

1132864 New Client Application: "Jet45_PFD" (Id=6268)

1134455 New Client Application: "Jet45_MFD DU2" (Id=5752)

1136498 New Client Application: "Jet45_RMU PILOT" (Id=4620)

1138012 New Client Application: "Jet45_RMU FO" (Id=7480)

1139057 New Client Application: "Jet45_MFD DU3" (Id=6228)

1148682 New Client Application: "LJ45_ADI" (Id=7024)

1149790 New Client Application: "lj45_Altimeter" (Id=992)

1153159 New Client Application: "interfaceIT" (Id=6748)

1169290 WARNING! Send() request depth is over 100!

1286228 New Client Application: "PokeysRMUNoGear" (Id=1312)

1709006 Received shutdown offset code = ADBC

1709006 FS closing down (param=ADBC), disconnecting

1709006 ********* Interim performance summary *********

1709006 Total time connected so far = 1444 seconds

1709006 Reception maximum so far: 32 frames/sec, 9148 bytes/sec

1709006 Reception average whilst connected so far: 31 frames/sec, 2531 bytes/sec

1709006 Transmission maximum so far: 352 frames/sec, 22059 bytes/sec

1709006 Transmission average whilst connected so far: 235 frames/sec, 390 bytes/sec

1709006 Max receive buffer = 840, Max send depth = 203, Send frames lost = 1

1709006 **************** Individual client application activity ****************

1709006 Client 2252 requests: 489131 (Ave 338/sec), Data: 97489176 bytes (67513/sec), Average 199 bytes/Process

1709006 Client 4000 requests: 476 (Ave 0/sec), Data: 12430 bytes (8/sec), Average 26 bytes/Process

1709006 Client 1948 requests: 5648 (Ave 3/sec), Data: 286760 bytes (198/sec), Average 50 bytes/Process

1709006 Client 6268 requests: 22018 (Ave 15/sec), Data: 6387380 bytes (4423/sec), Average 290 bytes/Process

1709006 Client 5752 requests: 23406 (Ave 16/sec), Data: 6275114 bytes (4345/sec), Average 268 bytes/Process

1709006 Client 4620 requests: 22105 (Ave 15/sec), Data: 13874941 bytes (9608/sec), Average 627 bytes/Process

1709006 Client 7480 requests: 21257 (Ave 14/sec), Data: 13424009 bytes (9296/sec), Average 631 bytes/Process

1709006 Client 6228 requests: 21824 (Ave 15/sec), Data: 6035049 bytes (4179/sec), Average 276 bytes/Process

1709006 Client 7024 requests: 4731 (Ave 3/sec), Data: 462224 bytes (320/sec), Average 97 bytes/Process

1709006 Client 992 requests: 5063 (Ave 3/sec), Data: 599841 bytes (415/sec), Average 118 bytes/Process

1709006 Client 6748 requests: 11861 (Ave 8/sec), Data: 211253 bytes (146/sec), Average 17 bytes/Process

1709006 Client 1312 requests: 12707 (Ave 8/sec), Data: 1829656 bytes (1267/sec), Average 143 bytes/Process

1709006 ***********************************************

1709116 Received shutdown offset code = ADBC

1716775 Connection closed by server!

1716775 Attempting to connect now

1716775 Trying TCP/IP addr 192.168.0.1, port 8002 ...

1782998 Connection made okay!

1793965 New Client Application: "lj45_Altimeter" (Id=6200)

1803356 New Client Application: "Jet45_MFD DU2" (Id=7284)

1804791 New Client Application: "Jet45_PFD" (Id=3936)

1807958 New Client Application: "interfaceIT" (Id=7064)

1835586 ERROR!! Send() request depth is over 250! Queue flushed!

1835617 WARNING! Send() request depth is over 100!

1835664 ERROR!! Send() request depth is over 250! Queue flushed!

1835695 WARNING! Send() request depth is over 100!

1835773 ERROR!! Send() request depth is over 250! Queue flushed!

1835820 WARNING! Send() request depth is over 100!

1835851 ERROR!! Send() request depth is over 250! Queue flushed!

1835882 WARNING! Send() request depth is over 100!

1835960 ERROR!! Send() request depth is over 250! Queue flushed!

1836007 WARNING! Send() request depth is over 100!

1836038 ERROR!! Send() request depth is over 250! Queue flushed!

1836085 WARNING! Send() request depth is over 100!

1838175 ERROR!! Send() request depth is over 250! Queue flushed!

1838206 WARNING! Send() request depth is over 100!

1838284 ERROR!! Send() request depth is over 250! Queue flushed!

1838300 WARNING! Send() request depth is over 100!

1838362 ERROR!! Send() request depth is over 250! Queue flushed!

1838362 WARNING! Send() request depth is over 100!

1838487 ERROR!! Send() request depth is over 250! Queue flushed!

1838487 WARNING! Send() request depth is over 100!

1838550 ERROR!! Send() request depth is over 250! Queue flushed!

1838550 WARNING! Send() request depth is over 100!

SERVER INI FILE

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

SERVER LOG

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

Blocksize guide = 8192 (double allowed)

Date (dmy): 05/05/13, Time 11:54:50.009: Server name is FSX

16053 Initialising TCP/IP server

16053 Initialising UDP/IP server

16115 Broadcasting service every 1000 mSecs

20359 Incoming connection Accepted ok (skt=8244) TCP

20437 Connected to computer "AVIONICS" running WideClient version 6.991 (skt=8244) TCP

[Pete Dowson]

Everything connects oaky but soon after I start to load up the connection by starting the engines, my connection starts to fail.

It looks like the PC you running all this on, and/or the Network link, is simply not up to the task. WideClient is simply not getting to run often enough. Look at all the things presumably soaking it with demands:

1130087 New Client Application: "LJ45_ASI" (Id=1948)

1132864 New Client Application: "Jet45_PFD" (Id=6268)

1134455 New Client Application: "Jet45_MFD DU2" (Id=5752)

1136498 New Client Application: "Jet45_RMU PILOT" (Id=4620)

1138012 New Client Application: "Jet45_RMU FO" (Id=7480)

1139057 New Client Application: "Jet45_MFD DU3" (Id=6228)

1148682 New Client Application: "LJ45_ADI" (Id=7024)

1149790 New Client Application: "lj45_Altimeter" (Id=992)

1153159 New Client Application: "interfaceIT" (Id=6748)

1169290 WARNING! Send() request depth is over 100!

1286228 New Client Application: "PokeysRMUNoGear" (Id=1312)

I've never seen anything like that! You have first 8 then 9 different applications presumably all trying to send their own stuff. Withing 40 seconds that was enough for the backlog of requests waiting to be sent to amount to 100.

But the main "culprit" is identified here, the very first application loaded, before you closed down and restarted:

156 New Client Application: "Jet45_CWP_Driver" (Id=2252)

...

1709006 Client 2252 requests: 489131 (Ave 338/sec), Data: 97489176 bytes (67513/sec), Average 199 bytes/Process

97 megabytes at 67513 per second!? That's 540 kbps all on its own, and with the TCP redtape it's a lot more.

Either the PC itself can't cope, or the speed of your Ethernet connection isn't up to it. The queuing appears to be all at the Client end, otherwise I'd suspect that your FS was overloaded instead. Is perhaps the main load on the client PC doing screen graphics? That can be a problem as things can get held up. Is it a built-in motherboard video card or a good fast add-in one?

Try Protocol=UDP, which is the protocol used by Windows explorer and most other programs. it is more efficient but also less likely to recover erroneous bloakc, so if things are really wrong it will lose data before it clogs up.

Aslo see if any of those programs you are running can be regulated better, especially JET45_CWP.

Please also check with the support folks for the programs you are using. They may be able to give specific advice on using their programs. They may well be designed for use on separate PCs, not all on one client.

Pete

[English Rebel]

Pete

Both my client and server PCs are top of the line home built machines. The server (running FSX) has an ASUS MB, the latest Intel i7 CPU and an nVIDIA GTX670 GPU. The client also has an ASUS MB, an Intel i7 CPU and nVIDIA GTX570 for my DU displays and an NVIDIA 210 for my "instructor station" display. Ethernet is gigabit so it's as fast as is possible over CAT5.

I have sent an email to Eric Tomlin of Flight Level Simulations who provides all of the avionics software including the JET45 CWP program. They recommend running JET45 (all but a couple of the programs on the client PC are JET45) on a client machine and suggest a cheap low power PC as the overhead is very low. I'm very surprised at the amount traffic that program is generating as it's only an interface for the Crew Warning Panel and with the engines running there are no warning lights lit up!

Thanks

Alan

[English Rebel]

Pete

Could you please look at the usages of these programs ( except the JET45 CWP) and let me know if they are reasonable so we can concentrate on the JET45 CWP.

Thanks

Alan

1709006 Client 2252 requests: 489131 (Ave 338/sec), Data: 97489176 bytes (67513/sec), Average 199 bytes/Process CWP

1709006 Client 4000 requests: 476 (Ave 0/sec), Data: 12430 bytes (8/sec), Average 26 bytes/Process FS INTERROGATE

1709006 Client 1948 requests: 5648 (Ave 3/sec), Data: 286760 bytes (198/sec), Average 50 bytes/Process ADI STANDBY GAUGE

1709006 Client 6268 requests: 22018 (Ave 15/sec), Data: 6387380 bytes (4423/sec), Average 290 bytes/Process PFD

1709006 Client 5752 requests: 23406 (Ave 16/sec), Data: 6275114 bytes (4345/sec), Average 268 bytes/Process EICAS

1709006 Client 4620 requests: 22105 (Ave 15/sec), Data: 13874941 bytes (9608/sec), Average 627 bytes/Process PILOT RADIO MANAGEMENT UNIT

1709006 Client 7480 requests: 21257 (Ave 14/sec), Data: 13424009 bytes (9296/sec), Average 631 bytes/Process FO RADIO MANAGEMENT UNIT

1709006 Client 6228 requests: 21824 (Ave 15/sec), Data: 6035049 bytes (4179/sec), Average 276 bytes/Process MFD

1709006 Client 7024 requests: 4731 (Ave 3/sec), Data: 462224 bytes (320/sec), Average 97 bytes/Process ALTIMETER STANDBY GAUGE

1709006 Client 992 requests: 5063 (Ave 3/sec), Data: 599841 bytes (415/sec), Average 118 bytes/Process ASI STANDBY GAUGE

1709006 Client 6748 requests: 11861 (Ave 8/sec), Data: 211253 bytes (146/sec), Average 17 bytes/Process INTERFACEIT

1709006 Client 1312 requests: 12707 (Ave 8/sec), Data: 1829656 bytes (1267/sec), Average 143 bytes/Process POKEYS RMU INTERFACE

[Pete Dowson]

Could you please look at the usages of these programs ( except the JET45 CWP) and let me know if they are reasonable so we can concentrate on the JET45 CWP.

Actually they are all trivial compared to the CWP. But maybe it isn't the demands on WideClient that gives the problem. maybe something is preventing WideClient getting enough processor time, or at least it's Ethernet transmission thread. Possibly a bad video driver or one with bad settings?

One thing you could to it try running the programs manually, one at a time, leaving the system running long enough in between to be sure it is running well. Maybe you'll find the culprit that way -- always assuming, of course, that it really isn't a LAN or LAN driver problem.

Did you try UDP yet? That would be my first test. I use a netwrok of 8 PCs on my cockpit, all using UDP.

Pete

[English Rebel]

Pete

Okay I'll try UDP with just my basic 3 DUs and InterfaceIT running and then add one program at a time to see what happens. In fact I only started using the JET45 CWP program recently and have been having these network issues even since I went with a server and client PC so maybe the issue does reside elsewhere. The developer of JET45 CWP confirmed that the network usage was ridiculous and he's looking into it. There are many Lear45 users who have the same set up as mine without having any network issues -- in fact some use an old low power PC for their client PC. I think I'll try upping the priority for WideClient. The only issue is that you have to do that every time the process runs.

Thanks for working through this with me.

Alan

[Pete Dowson]

I think I'll try upping the priority for WideClient. The only issue is that you have to do that every time the process runs.

There are three priorities WideClient uses for its three threads (receiving, sending and processing application requests and responses) -- please look up the "Priority" parameter in the WideFS Technical document. By default the reception is set at mid-prioriy (#2), below transmission (#1). That has always seemed to work best, but you could try swapping those two, or making them both high.

Pete

[English Rebel]

Pete

I changed the protocol to UDP and ran FSX. I had issues with my displays (same as previous) that pointed toward a network issue again, but in looking at the client log file I dont see anything unusual. Can you please verify that. If this looks okay then my issue must lay somewhere else.

Thanks

Alan

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

Date (dmy): 06/05/13, Time 12:53:32.615: Client name is AVIONICS

78 Attempting to connect now

78 Trying UDP/IP addr 192.168.0.1, port 8002 ...

78 LUA: "C:\Program Files (x86)\WideFS\Initial.LUA": not found

78 UDP connectionless mode set up okay!

15694 Connection made: receiving okay!

21824 New Client Application: "Jet45_PFD" (Id=8940)

22745 New Client Application: "Jet45_MFD DU2" (Id=9432)

24008 New Client Application: "Jet45_RMU PILOT" (Id=6508)

24976 New Client Application: "Jet45_RMU FO" (Id=2748)

25272 New Client Application: "Jet45_MFD DU3" (Id=6348)

26832 New Client Application: "PokeysRMUNoGear" (Id=6412)

28829 New Client Application: "LJ45_ADI" (Id=9536)

29609 New Client Application: "lj45_Altimeter" (Id=6304)

41496 New Client Application: "LJ45_ASI" (Id=7948)

46129 New Client Application: "interfaceIT" (Id=9484)

379035 New Client Application: "interfaceIT" (Id=9972)

846508 New Client Application: "FSInterrogate2std" (Id=4624)

1611287 Received shutdown offset code = ADBC

1611287 FS closing down (param=ADBC), disconnecting

1611287 ********* Interim performance summary *********

1611287 Total time connected so far = 1593 seconds

1611287 Reception maximum so far: 32 frames/sec, 9220 bytes/sec

1611287 Reception average whilst connected so far: 31 frames/sec, 30 bytes/sec

1611287 Transmission maximum so far: 105 frames/sec, 5388 bytes/sec

1611287 Transmission average whilst connected so far: 44 frames/sec, 1830 bytes/sec

1611287 Max receive buffer = 745, Max send depth = 26, Send frames lost = 0

1611287 **************** Individual client application activity ****************

1611287 Client 8940 requests: 106843 (Ave 67/sec), Data: 28527762 bytes (17908/sec), Average 267 bytes/Process

1611287 Client 9432 requests: 117956 (Ave 74/sec), Data: 30376696 bytes (19068/sec), Average 257 bytes/Process

1611287 Client 6508 requests: 102655 (Ave 64/sec), Data: 64500448 bytes (40489/sec), Average 628 bytes/Process

1611287 Client 2748 requests: 95753 (Ave 60/sec), Data: 59492959 bytes (37346/sec), Average 621 bytes/Process

1611287 Client 6348 requests: 123457 (Ave 77/sec), Data: 33464522 bytes (21007/sec), Average 271 bytes/Process

1611287 Client 6412 requests: 21712 (Ave 13/sec), Data: 3125708 bytes (1962/sec), Average 143 bytes/Process

1611287 Client 9536 requests: 17992 (Ave 11/sec), Data: 1969502 bytes (1236/sec), Average 109 bytes/Process

1611287 Client 6304 requests: 20612 (Ave 12/sec), Data: 2712450 bytes (1702/sec), Average 131 bytes/Process

1611287 Client 7948 requests: 21238 (Ave 13/sec), Data: 845259 bytes (530/sec), Average 39 bytes/Process

1611287 Client 9484 requests: 13289 (Ave 8/sec), Data: 237051 bytes (148/sec), Average 17 bytes/Process

1611287 Client 9972 requests: 55827 (Ave 35/sec), Data: 988620 bytes (620/sec), Average 17 bytes/Process

1611287 Client 4624 requests: 144 (Ave 0/sec), Data: 2621 bytes (1/sec), Average 18 bytes/Process

1611287 ***********************************************

1611397 Received shutdown offset code = ADBC

1623861 Timed out UDP reception: connection assumed lost!

1630226 Trying UDP/IP addr 192.168.0.1, port 8002 ...

1630226 UDP connectionless mode set up okay!

1652862 ****** End of session performance summary ******

1652862 Total time connected = 1593 seconds

1652862 Reception maximum: 32 frames/sec, 9220 bytes/sec

1652862 Reception average whilst connected: 31 frames/sec, 30 bytes/sec

1652862 Transmission maximum: 105 frames/sec, 5388 bytes/sec

1652862 Transmission average whilst connected: 44 frames/sec, 1830 bytes/sec

1652862 Max receive buffer = 745, Max send depth = 26, Send frames lost = 0

1652862 **************** Individual client application activity ****************

1652862 Client 8940 requests: 106843 (Ave 67/sec), Data: 28527762 bytes (17908/sec), Average 267 bytes/Process

1652862 Client 9432 requests: 117956 (Ave 74/sec), Data: 30376696 bytes (19068/sec), Average 257 bytes/Process

1652862 Client 6508 requests: 102655 (Ave 64/sec), Data: 64500448 bytes (40489/sec), Average 628 bytes/Process

1652862 Client 2748 requests: 95753 (Ave 60/sec), Data: 59492959 bytes (37346/sec), Average 621 bytes/Process

1652862 Client 6348 requests: 123457 (Ave 77/sec), Data: 33464522 bytes (21007/sec), Average 271 bytes/Process

1652862 Client 6412 requests: 21712 (Ave 13/sec), Data: 3125708 bytes (1962/sec), Average 143 bytes/Process

1652862 Client 9536 requests: 17992 (Ave 11/sec), Data: 1969502 bytes (1236/sec), Average 109 bytes/Process

1652862 Client 6304 requests: 20612 (Ave 12/sec), Data: 2712450 bytes (1702/sec), Average 131 bytes/Process

1652862 Client 7948 requests: 21238 (Ave 13/sec), Data: 845259 bytes (530/sec), Average 39 bytes/Process

1652862 Client 9484 requests: 13292 (Ave 8/sec), Data: 237778 bytes (149/sec), Average 17 bytes/Process

1652862 Client 9972 requests: 57171 (Ave 35/sec), Data: 1012420 bytes (635/sec), Average 17 bytes/Process

1652862 Client 4624 requests: 160 (Ave 0/sec), Data: 3025 bytes (1/sec), Average 18 bytes/Process

1652862 ********* Log file closed (Buffers: MaxUsed 33, Alloc 750069 Freed 750049 Refused 0) *********

[Pete Dowson]

I changed the protocol to UDP and ran FSX. I had issues with my displays (same as previous) that pointed toward a network issue again, but in looking at the client log file I dont see anything unusual. Can you please verify that. If this looks okay then my issue must lay somewhere else.

That looks perfect. But where's that "Jet45_CWP_Driver" program?

You seem to be not running that now but several others not listed before!

46129 New Client Application: "interfaceIT" (Id=9484)

379035 New Client Application: "interfaceIT" (Id=9972)

Was that 2 copies of "interfaceIT", or did you restart it after about 5 minutes?

1652862 Reception maximum: 32 frames/sec, 9220 bytes/sec

1652862 Reception average whilst connected: 31 frames/sec, 30 bytes/sec

1652862 Transmission maximum: 105 frames/sec, 5388 bytes/sec

1652862 Transmission average whilst connected: 44 frames/sec, 1830 bytes/sec

1652862 Max receive buffer = 745, Max send depth = 26, Send frames lost = 0

That's pretty impressive performance. What is your average FS frame rate?

Interesting if most of those applications are instrumentation, not control, that the transmission of data TO FS is so much higher than reception from it. Why is that? Are those not just display instruments after all?

Pete

[English Rebel]

Pete

I did not run the Jet45_CWP_Driver program as the developer is checking into why I got such high data rates before so I wanted to eliminate that. Yes I did restart InterfaceIT (which is the Flight Deck Solutions connection board interface program). I'm not really running FS at speed right now (and those frame rates are for the client PC with the nVIDIA GTX580 GPU) -- the Lear45 is just sitting on the tarmac with the engines running to see if I can eliminate the issues I'm having -- which brings me to those issues. I can start a new thread if you wish as I think we may have eliminated connection issues.

Okay here goes.

All of these programs run various displays on my MIP monitors. I'm not sure exactly how they communicate with FSX but I assume they read mostly (FROM FS) so they can display the values and flight parameters on the MIP displays. All of the hardware is connected through InterfaceIT using standard offsets so that communication would mainly be TO FS.

JET45_PFD -- my primary flight display (DU1)

JET45_DU2 -- my EICAS

JET45_DU3 -- my multi function display

JET45_ RMU_PILOT -- the pilots radio management unit (static graphics display only)

JET45_RMU-FO -- the first officers radio management unit (static graphics display only)

PokeysRMUNoGear -- the program that runs the RMUs for the COM and NAV etc. values and buttons and encoder functions

LJ45_ADI -- the program that displays the Standby ADI

LJ45_ASI -- the program that displays the Standby ASI

LJ45_Altimeter -- the program that displays the Standby altimeter.

Now to my problem. I can start my simulator and all is fine until about 10 - 15 minutes in when all of the standby gauges start flashing 'Not Connected" (that's normal if not connected) on and off and I get the messages in the FSX window saying for instance LJ45 ADI Connected (presumably because it disconnected and then reconnected). Shortly thereafter (or sometimes at the same time) I start getting strange values for fuel flow and fuel capacities in the EICAS display. Starts off small then goes to hundreds of thousands of pounds per hour (the values over run the flow rate display areas -- obviously).

It seems as if the EICAS is reading (or interpreting) wrong values from FSX -- more likely the latter. If it was a simple matter of a lost connection then I would have thought that the current values would just freeze.

Now that doesn't seem to be the case for the standby gauges -- not sure what's going on there.

Hope this sheds some light on my issues that you may be able to pinpoint a solution (fingers crossed). :???:

Thanks

Alan

[Pete Dowson]

All of these programs run various displays on my MIP monitors. I'm not sure exactly how they communicate with FSX but I assume they read mostly (FROM FS) so they can display the values and flight parameters on the MIP displays. All of the hardware is connected through InterfaceIT using standard offsets so that communication would mainly be TO FS.

JET45_PFD -- my primary flight display (DU1)

JET45_DU2 -- my EICAS

JET45_DU3 -- my multi function display

JET45_ RMU_PILOT -- the pilots radio management unit (static graphics display only)

JET45_RMU-FO -- the first officers radio management unit (static graphics display only)

PokeysRMUNoGear -- the program that runs the RMUs for the COM and NAV etc. values and buttons and encoder functions

LJ45_ADI -- the program that displays the Standby ADI

LJ45_ASI -- the program that displays the Standby ASI

LJ45_Altimeter -- the program that displays the Standby altimeter.

Ok. There doesn't look to be anything there which would be sending much data TO FS, it's all requiring just updates FROM FS. The two highest data SENDING applications are the PIOT and FO displays, which I suppose is what you'd expect if they want to be smooth:

1652862 Client 6508 requests: 102655 (Ave 64/sec), Data: 64500448 bytes (40489/sec), Average 628 bytes/Process

1652862 Client 2748 requests: 95753 (Ave 60/sec), Data: 59492959 bytes (37346/sec), Average 621 bytes/Process

Now to my problem. I can start my simulator and all is fine until about 10 - 15 minutes in when all of the standby gauges start flashing 'Not Connected" (that's normal if not connected) on and off and I get the messages in the FSX window saying for instance LJ45 ADI Connected (presumably because it disconnected and then reconnected). Shortly thereafter (or sometimes at the same time) I start getting strange values for fuel flow and fuel capacities in the EICAS display. Starts off small then goes to hundreds of thousands of pounds per hour (the values over run the flow rate display areas -- obviously).

It seems as if the EICAS is reading (or interpreting) wrong values from FSX -- more likely the latter. If it was a simple matter of a lost connection then I would have thought that the current values would just freeze.

Well, there are no errors logged, but remember, I did say that UDP has no error detection. It can lose or corrpt blocks without any attempt to correct them and no notifications. HOWEVER, the WideFS protocol does check the lengths, sequence numbers and sumchecks on each received frame, so it should be okay in any case. I've been using UDP for ages and the only times I've ever had any problems (which is hardly ever) the log has been showing the errors, things like sequence errors and sum checks.

There's lots of logging available, right down to all the data and every single exchange both with the programs and with the network, but if we enable that it will be many many megabytes, and honstly I wouldn't have time to pore through it even if you could get it to me.

I think your first step must be to ask the JET45 folks what they think, What causes those symptoms in their programs?

BTW didn't you ever try TCP protocol without that CWP program running?

Pete