Why does the tag engine take upwards of 3 minutes to shut down?

[West Chester]

The time between programatically shutting down the tag engine and when it actually turns off varies. LV 6.1 Sometimes immediately sometimes 4 minutes. (I have been careful not to be reading or writing tags when shutting down.)

[Khalid]

________________________________________

What Server are you using? There was an issue with the DataSocket server.. for details of this, please see the following:

ftp://ftp.ni.com/support/labview/labviewdsc/fixes/6.1/readme.txt

Regards,

Khalid

________________________________________

[Philip McDermott]

I'm getting the same problem as well. I haven't tried the patch but the only servers I'm using are VI's. I thought it was a slow memory leak since I'm running 12 VI servers of the same design. They should all shut down when the engine closes since I have the loop condition terminal wired to the shutdown terminal.

The shutdown problem only occurs after an hour or so. I haven't done much research on the problem but what I have seen is the tag engnie running at about 85% processor usage (up from about 10% at the start) and when I instruct the system to shutdown I get 98-99% usage and the system takes about 20-25 minutes to shut down.

The design of the servers is to only transmit data on changes. They definitly do not throw out data unless a valu
e on its front panel is changed or a value is written to it, so It shouldn't be a queing problem. It's most probable down to citadel as I have only notice the probelm after leaving the system doing nothing for a long period of time. Maybe citadel doesn't like no changes at all over a long period. It might also be a problem with the shutsown order of the server. If the server tires to destroy its refrences to the server VI's ad they refuse to stop running for whatever reason they two programms will hold themselves open.

I'm not using the VI servers for the full application. They will be replaced my fieldpoint. However it would be nice to get an answer for the problem. I'm happy to send you my code Khalid but I don't really want to put it on the web as I have spent a Very long time doing some pretty low level programming (don't want to give away my secrets).

Let me know if you have any more questions.

Later

Philip McDermott

[Khalid]

Here's a few things which I would try:

1. To eliminate or otherwise narrow-down, try not logging any data. See if this changes the behavior.

2. Are you able to stop the Citadel services after a period of time?

3. Debug by placing indicators on your Server VIs and check if the Shutdown output from your SRVR Get Status VI goes high as soon as you exit the Engine.

4. If you're using the Shutdown info' from SRVR Write Input Queue VIs, make sure you have a True wired to the Return Status input. Without this the Shutdown info' is not returned.

If you can narrow this down further maybe we will get some ideas as to what's happening. I will be happy to take a look at your VIs.. though not sure when!! Email them or a simplifie
d version of 'em to me at: mki_ansari@iee.org

Hope this helps,

Rgds,

Khalid