LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

udp buffer size in RT

Solved!
Go to solution

Hi, I found a couple of good suggestions on how to increase the UDP buffer size in Windows here, but I could not find any such suggestions for RT - does anyone know how to do this for LabVIEW RT?

 Thanks.

0 Kudos
Message 1 of 8
(3,701 Views)

Hi AnthonV

 

I think this should be a good resource for us:

http://digital.ni.com/public.nsf/allkb/45FEF8E4D56D39AF862579FE0053DB93

 

Please note that the above Knowledge Base Article only applies to VxWorks targets though.  Which cRIO are you using?

 

Regards

Joel I.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 8
(3,649 Views)
Thanks for this. But I should have mentioned that I am using a real time desktop target. Do you know of any methods to increase the buffer size when using a RT on a desktop?
0 Kudos
Message 3 of 8
(3,632 Views)
Solution
Accepted by topic author AnthonV

Hi AnthonV,

 

The forum post you linked mentioned this Knowledge Base Article:

http://digital.ni.com/public.nsf/allkb/D5AC7E8AE545322D8625730100604F2D

 

The dll that it mentions, wsock.dll is also present on Pharlap targets.

 

You should be able to find it under ni-rt/system on the RT desktop.

 

Call this DLL using a Call Library Function Node and call the function specified in the Knowledge Base article setsockopt 

and let me know what results from this.  

 

Please make sure to create a backup of any DLLs you work with.

 

Regards,

Joel I.
Applications Engineer
National Instruments
Message 4 of 8
(3,595 Views)
Thanks I was wondering whether this might be an option. That is one of the advantages of Pharlap supporting some Win32 dlls I suppose. I'll give it a go later in the week and report back.
0 Kudos
Message 5 of 8
(3,590 Views)

Thanks this worked well. I wonder how large this buffer can be made?  It was sitting at 65k by default and I tried up to 200k as a test and all went well.

Message 6 of 8
(3,548 Views)

Hi AnthonV,

 

I've looked further into this issue and it seems that the limits will be based on your hardware.

 

 

Also, please note that even though one function worked for the wsock.dll, the other function calls are not necessarily guaranteed to work.

 

Regards,

Joel I.
Applications Engineer
National Instruments
0 Kudos
Message 7 of 8
(3,476 Views)
Noted thanks.
0 Kudos
Message 8 of 8
(3,472 Views)