Datasocket server seems to fail after continuous use.

[gold]

The Datasocket server seems to fail after continuous use.  (Labview 7.1 on XP)

I have a data acquistion system that collects data and presents it to the operator.  Then I have from 1-3 remote units that can connect via DS to the acquistion unit to view the data.  As a general rule things work dandy!  I have the data published from the front panel of one VI and subscribed to by the remote VI(s).  However it seems that after some indeterminent time the DS just stops publishing data and my remote units go into alarm indicating that they can no longer get data.  If I shutdown and then restart the DS server then things seem to clear up and work again.

Anyone seen this type of problem?  Unfortunately my app is pretty large and it acquires data from 26 field units so its not real practical to post the code!

I wonder if using the DS VI's would change performance as opposed to the front panel publishing/subscribing that I currently do?  Or can DS just not handle the load, should I change to a TCP/IP handshaking?

Thanks!

~Gold

[JLS]

Hello,

I have not heard of this - I also checked our database of errors and didn't find anything.  Can you post a screenshot of the error message and any other information you may have gathered on the matter since posting?  Could this be a problem with the network connection in general?  Perhaps you could test another network application there which doesn't use datasocket to see if it experiences problems at the same time.

I look forward to your reply, and hope we can find the root cause!

Best Regards,

JLS

[tst]

I have seen something like this in VIs in which FP controls are connected through DS (even if it's on the same PC between seperate executables). This was in an executable and debugging was problematic since it was happening randomly. The client would complain that it stopped working.

What I did was to use a property node getting one of the DS properties for one of the controls (I don't remember which property, but it probably doesn't really matter) and periodically check it for errors. When an error is found, I used some VIs which can be found in the DS LLB in vi.lib which allow you to control the server. I close the server, wait and reopen it. That seemed to solve it, as they haven't complained since.

[gold]

JLS....That is one of the tough things about this issue, there is no error messages!  My remote PC just stops receiving updated data.  When I look at the DS it still seems to be functioning just fine but it will not deliver data until the DS server has been restarted.  I don't believe the network is the problem because I have seen a second system still functioning while the first is having trouble, and they are both on the same network.

Thanks!

[gold]

TST...  Thanks, I will give that a try.  From what I have seen resetting/restarting the DS server couldn't be a bad thing at this point.  Do you recall how long you gave the server before you restarted it?  I'm sure I can come up with some decent interval but I just thought I would ask.

Thanks 

[tst]

Here's the basic piece of code. The outer case structure was used because that program already had some DS related stuff and I wanted to wait before I start checking to avoid disturbing it. I added the array at the bottom for some logging so I could check when it happened, but I haven't been called for it since, so that array has proved unnecessary.