Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 66753

LabVIEW 2013 TCP timing lose message

$
0
0

Dear,

 

my be anyone of you hase faces the same difficulties.

Open a TCP connection, creating some smal messages and sending these to the target.

Doing this within a none times loop will case lose messages.

Anyone faced this problem too?

In my case I first send three messages within a timed loop.

Everythin ist OK as shown in the wireshark protokoll.

Now the consumer goes to the next case and sends another message.

This message starts the target mesurement data streaming.

It should allways be transmitted - within the right mode - but it has not be trandmitted.

As one can see within the wireshark protocol.

In this case my app waits a little bit of time closes the Ethernet vonnevtion and tries to do the same again to start the data streaming on the client.

 

By unsing a delay structure of 5ms the problem disapears-

 

My questions are:

   - Has anyone seen this too?

   - Can this problem be solved with TCP_nodelay in the ethernet card configuration?

   - Is it a windows 7 problem?

   - Is it a LabVIEW problem?

   - How can I bee sture that the problem is solved?

 

The missing command can be found in message number 88 and 89 of the wireshark protocol.

Than the client starts streaming data as wanted before.

 

Now that I have "solved" the problem or build a workaround I like to know how reliable it is.

 

Any other Ideas are wellcome.

 

Best regards

 

Martin

 


Viewing all articles
Browse latest Browse all 66753

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>