08-02-2012 10:25 AM
OK so I need to send a 12 byte timestamp along with my data using Labview TCP. I enabled RFC 1323 Timestamps on the windows 7 machine with netsh. And using wireshark I can see that the timestamps options are being sent for seperate functions but the 12byte timestamps not added to the 20 byte header when the labview app sends its data. How can I turn on this function for the labview write data?
08-02-2012 01:51 PM
You will most likely need to do this yourself with calls into the stack. This thread may help to point you in the right direction.
08-02-2012 02:55 PM
So I might be able to enable the timestamp using the GetRawSocketFromConnectionID.vi. But how do I know what to input into the Call Library Function without screwing up the rest of the connection?
08-02-2012 03:35 PM
You will have to lookup Microsoft's documentation on their socket library.
08-03-2012 07:23 AM
I think I've become more confused than when I started. This link doesn't say anything about how to enable the timestamp on a per socket case using setsockopt( ). But how to enable it on the machine. Which I have verified. So why is it that when labview sends data the timestamp isn't included?
08-03-2012 07:27 AM
TCP Wiki this has some info that might help. "Some options may only be sent when SYN is set; they are indicated below as [SYN]. Option-Kind and standard lengths given as (Option-Kind,Option-Length)"
One option being the timestamp. So how can I set the SYN bit to 1?