Hi,I have ASV installed in a WideFS configuration, that is FS2004/WideServer on PC1, and WideClient/ASV on PC2.I first launch WideClient and ASV. WIdeClient says "not connected" and ASV is started in pause mode and says "FS inactive". I start the data download and click "Refresh". ASV does its job, after what CPU usage continues to go in burst to 100% about halt of the time.I then launch FS2004 on the other PC. WideFS connects, and ASV detects "FS Active".I then quit FS2004. I notice that PC2 CPU usage is stuck at 100% in a nearly permanent way. Looking at the tasks display, I can see that WideClient is actually taking about 90% of those 100%. But if I quit ASV, CPU usage goes idle to 0-2%. I also notice that ASV still says "FS active".I therefore guess that ASV does not detect FS is not active anymore and continues to ask or send data to FSUIPC through WideClient, which is what is using all the CPU.What I would like is to let WideClient and ASV run permanently on the second machine (a server PC in my garage) without having it using all the CPU when FS is actually not running.Do you think it's a problem with ASV (obviously, it does not detect FS is not there anymore, whereas WideClient does detect that)?Eric.

Hi Eric,I am going to ask this, but after that my knowledge is slim. Are you using all the latest versions of ASV, FSUIPC, and WideFS?Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

>Are you using all the latest versions of ASV, FSUIPC, and>WideFS?Yes, of course (ASV with SU2, FSUIPC 3.5 and WideFS 6.5)Eric.

Hi Eric,The start-up stuff looks all normal. Not sure why on FS04 close, WideC is not disconnecting. We would ask that you not run ASV 24/7 because it is still downloading weather every XX minutes and using bandwidth!You may wish to ask Pete for suggestions. Your question could be: Why doesn't WideC disconnect after FS04 shuts down?One more thing I just thought of: when you close FS04 check your processes list and see if the fs9.exe is still running. Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Jim,Read again my initial post: WideClient DOES correctly disconnect (as indicated in its title bar). It is ASV that does not detect the WideClient disconnection (ASV title bar still shows "FS Active").Regarding the bandwith, don't worrry: ASV is setup to work in offline mode. I'm not wasting your bandwidth :-)Eric.

Hi,I have pointed Damian to this!Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi,This may be new to wideFS 6.5, where connection / networking changes were made. We detect FSUIPC connection status every 5 seconds, and possibly wideclient is reporting that the connection is still open even though it's closed. If the connection is reported closed we immediately quit any process. Is this occuring during updates or even when ASV is idle? an FSUIPC.log and wideclient.log would help!Best,

Jim, I think you are right about Wide Client reporting that the connection is open when FS closes. I have written a simple app and part of the process polls at intervals that the connection is still open, and wide client _is_ reporting as still connected after FS closes, and this behaviour has only just started happening. Previous versions did not exhibit this behaviour.Steve

I tested again to report the exact messages displayed by all parties in their title bars:The procedure order is the following:- Start WideClient PC2: "Waiting for connection"- Start ASV on PC2 : "FS Disconnected". In the window: ASV is paused - Refresh to start processing.- Start FS2004 on PC1 : "1 connected", and on PC2 : WideClient "Connected" and ASV "FS Active", and in the window "writing stations xxxx. Offline update completed. Online automatic updated disabled"- Quit FS2004 : WideClient shows "Waiting for connection". ASV shows "FS Active".So I can say WideClient correctly detects FS disconnection. But, it may be that it does not report it correctly when asked programmatically.Eric.

Hi Eric,Yes, the problem does appear that even though Wideclient shows disconnected, it is reporting "connected" because the FSUIPC connection is remaining active (which is how we detect FS9 connection status).Did going back to the earlier FSUIPC/WideFS eliminate the problem?If you can enable and share the wideclient/server and fsuipc logging it may help us to isolate and solve this...Thanks!