Jump to content

WideFs 6.0.2.0 MSG Auto restart after delayed stoppage!


Recommended Posts

Hi Pete,

I have problem with WideFS server registred version 6.0.2.0

For each request to FSUIPC msg Auto restart after delayed stoppage!

is issued.

Used FSinterrogate.

TCP/IP connection over 10Mb ethernet.

FS2004 was runnig on the server.

Please find following the ini files and log files

Server Side

; PLEASE SEE the documentation for parameter details

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

[Config]

UseTCPIP=Yes

SeverIPAddr=10.70.1.110

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

[user]

Log=Errors+

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

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

Using blocksize guide of 4096 bytes

Date (dmy): 01/08/03, Time 18:17:14.734: Server name is P500

67728 Initialising service now

67728 Initialising server socket now

89459 Incoming connection Accepted ok (skt=2040)

89599 Connected to computer "P700" (skt=2040)

105081 Auto restart after delayed stoppage!

105081 Initialising server socket now

105102 Incoming connection Accepted ok (skt=2004)

105322 Connected to computer "P700" (skt=2004)

123318 Auto restart after delayed stoppage!

123318 Initialising server socket now

123318 Incoming connection Accepted ok (skt=2024)

123568 Connected to computer "P700" (skt=2024)

141624 Auto restart after delayed stoppage!

141624 Initialising server socket now

141914 Incoming connection Accepted ok (skt=2016)

141924 Connected to computer "P700" (skt=2016)

156375 Closing down now ...

Memory managed: Offset records: 579 alloc, 579 free

Throughput maximum achieved: 11 frames/sec, 3449 bytes/sec

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

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

Client Side

; PLEASE SEE WideFS documentation for parameter details

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

[Config]

UseTCPIP=Yes

ServerIPAddr=10.70.1.120

Window=32000,32000,160,34

Visible=Yes

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

[user]

Log=Errors+

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

********* WideClient.DLL Log [version 6.02] Class=FS98MAIN *********

Date (dmy): 01/08/03, Time 18:18:55.687: Client name is P700

63 Attempting to connect now

63 Connection made okay!

15750 Connection closed by server!

15766 Ready to try connection again

15781 Attempting to connect now

15781 Connection made okay!

22188 New Client Application: "FSinterrogate" (Id=3184)

34000 Connection closed by server!

34000 Ready to try connection again

34016 Attempting to connect now

34016 Connection made okay!

52391 Connection closed by server!

52391 Ready to try connection again

52391 Attempting to connect now

52391 Connection made okay!

62375 Reception maximum achieved: 12 frames/sec, 4078 bytes/sec

62375 Reception average achieved whilst connected: 4 frames/sec, 620 bytes/sec

62375 Max receive buffer = 4078, Max send depth = 0

62375 ********* Log file closed (Buffers: MaxUsed 2, Alloc 278 Freed 278 Refused 0) *********

The program works correctly.

Time to time I can see on the top of FS2004 screen

the text changing

from

: 1 connected

to

: Waiting for clients

Hope all necessary information are here.

Regards

Michel

Link to comment
Share on other sites

I have problem with WideFS server registred version 6.0.2.0. For each request to FSUIPC msg Auto restart after delayed stoppage! is issued.

All this means is hat something was going on in FS which prevented WideServer accessing variables in FS for a number of seconds (I cannot remember how many). In order to make sure all the clients are updated when it gets access back again, it restarts its service. This is actually quite quick, but it may result in a jerk in instrumentation.

You say this occurred after "reach request to FSUIPC", but you were using FSinterrogate. Can you tell me what you were asking FSInterrogate to do? Something is causing the Server's access to FS to be dirupted.

TCP/IP connection over 10Mb ethernet.

Ouch! That is truly an awful combination. 100Mbps Ethernet is now almost universal, and just as cheap, so why still use 10Mbps? And especialy with TCP/IP which is very inefficient. If you intend to stick to 10Mbps I'd recommend trying IPX/SPX instead.

Hope all necessary information are here.

Well the only thing missing is an explanation of what you were asking FSInterrogate to do. By itself it does nothing, not even talk to FS. And what starte was FS2004 itself in, flying, parked, in menus or options, minimised, .. what?

Pete

Link to comment
Share on other sites

Hi Pete,

Thank you for your prompt reply.

I found what is happening...

Fs2004 was running on a old PIII 0.5 Ghz processor.

I reverse the connection PIV 1.8 Ghz 1Gb memmory running FS2004

and PIII 500 Mhz the FSIinterrogate program.

No more msg "Auto restart after delayed stoppage!"

PS. Could find a maximum of the new "state code" in TCAS section

from 0x81 to 0x92.

Missed 0x8B.

Where can i find this information ??

Regards

Michel

Link to comment
Share on other sites

Fs2004 was running on a old PIII 0.5 Ghz processor.

I reverse the connection PIV 1.8 Ghz 1Gb memmory running FS2004

and PIII 500 Mhz the FSIinterrogate program.

No more msg "Auto restart after delayed stoppage!"

AhWideServer was simply not getting to run for some periods because of FS2004's need for the processor?

Could find a maximum of the new "state code" in TCAS section

from 0x81 to 0x92.Missed 0x8B.

Where can i find this information ??

Here's a list of the AI states which I report. This is from the forthcoming SDK update:

0x80 128 Initialising

0x81 129 Sleeping

0x82 130 Filing flight plan

0x83 131 Obtaining clearance

0x84 132 Pushback (back?)

0x85 133 Pushback (turn?)

0x86 134 Starting up

0x87 135 Preparing to taxi

0x88 136 Taxiing out

0x89 137 Take off (prep/wait?)

0x8A 138 Taking off

0x8B 139 Departing

0x8C 140 Enroute

0x8D 141 In the pattern

0x8E 142 Landing

0x8F 143 Rolling out

0x90 144 Going around

0x91 145 Taxiing in

0x92 146 Shutting down

Mind you, I'm not sure you will actually ever see all of them happen. I never have so far. I suspect some of them are transitional and only valid for a very short time.

When this is 00 it isn't valid -- this will be true in FS2002, for example.

Regards,

Pete

Link to comment
Share on other sites

Thanks for the information.

Is there a possibility to have in a future version

of FSUIPC the from/to ICAO information, as we can see

in the AIMAP.gau by Rodolfo Arata for FS2002 ???

I am working on a program "Airport Traffic Viewer & Recorder" and

this info would be nice.

Have a nice week end.

Michel

Link to comment
Share on other sites

Is there a possibility to have in a future version

of FSUIPC the from/to ICAO information, as we can see

in the AIMAP.gau by Rodolfo Arata for FS2002 ???

At present I don't know where to find that information, but I will have a look when I get time. I don't think Rudolfo will want to share his findings.

The problem then will be to find room to add extra information without (a) reducing severely the number of entries in the table, and (b) rendering many programs unusable by a change in format. Although I do provide structure size and so forth, I'm sure a number of programs do not use this in calculating access.

Maybe a separate table elsewhere for additional information would work, but designing something easy to access is difficult. Anyway, I shall add it to my list of things to look at.

Regards,

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
 Share

×
×
  • 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.