Datasocket bug in Win2K - constantly updated


I have a simple Datasocket system which produces a very strange problem on Win2K

After a variable duration (from 30 seconds to 30 minutes), the player datasocket simply stop receiving updates of the writer.

The system features a base Writer DS and DS player that communicate over the DS server localhost. I've included the reader and the writer screws for your tests. In addition, it seems to be easier to reproduce if the screws are compiled into executable files. I've included the executables for the tests. The problem is reproducible when the 'reader' is actually a C++ (using Measurement Studio) program which is integrated into an OCX component (not included).

NOTE: This bug doesn't seem to be reproducible under WinNT.

I spent a lot of time this system... with no luck debugging. I've narrowed it down so that it is very reproducible. Just run the Datasocket server and the two clips EXEs on Win2K (Professional) and wait a while... eventually, you will see the Player stops to get updates.


The writer of the DS to connect to the DS server in 'write' mode and sends an array of doubles. An "attribute" property is specified as another array of doubles. The writer then updates the connection. The two paintings are supposed to represent the values and timestamps.

The DS drive connects in mode 'reading-auto-update. He is waiting for an update and then reads the table and its "table of attributes.

Take a look at the examples attached... they are very simple.


The problem is reproducible on Win2K machines.

After a variable period of time (usually no more than 10 minutes) the single drive ceases to receive updates. The DS connection is reported as "Active: connected" and the status is 'ConnectionActive '.

= NOTE =.

I use LV6.02 and the latest version of Datasockets 4.0 (370).

2 screws are in the same delivery system: the User Interface.

On the PC power management is set to "always on" and the power to save them all, functions of sleep, screensavers, etc are disabled.

I use the 'old' datasockets screw (open connection. read/write double vector, close, etc.). I realize that the "bug" I'm reports could in fact be fixed if I used the new Datasocket screws that come with LV6i, but we really don't want to use these screws we find the old screws better because:

1. the older screws seem to be faster to the writing of the major vectors. We discovered this through tests.

2. reliability of maintaining connections. The older screw seem to be more to the maintenance of the connections.

3. the new screws have difficulties getting the items appear (and with the appropriate icon) in the window "Browse measurement data.

No other significant network activity is seen when this bug occurs. It seems to happen randomly.


Tags: NI Software

Similar Questions

Maybe you are looking for

  • Re: Satellite U500 - can I install Windows XP?

    Have recently bought a Toshiba Satellite U500 laptop. It came with Windows 7. It is very unstable. Programs that don't crash XP, crash regularly in Windows 7. Including Windows Internet Explorer and Windows Explorer (especially painful if you have ru

  • Windows 7 and Deskjet printer 722C

    I tried to install my office 722 C on my Windows 7 32-bit system.  Windows has detected the hardware & after you download the driver, said "your device is ready to use.  However, he said also "no installed printer.  Could not print because there is n

  • What benefit comes from an external hardrive? It will allow my Skype video calls be better quality >

    My web cam sends a photo of feverishness to the correspondent. I was told that this is due to the lack of memory and that another HDD would fix it.

  • I don't n no sound at all

    Well I accidentally delete my audio device so now I haveno sound at all on my pc where can I get this program? I know that what I'm looking for is volume control 5.1 version but I can't find it anywhere Thank you

  • Communication I/O Stream socket operations

    Hello! I want to build a mechanism that opens a socket on a server connection and then independently send and receive messages to and from the server on this connection. My approach is like this: main thread I run a wire (ignition wire) which opens a