Help parsing UDP Packet

[nathand · Accepted solution]

Almost there! But there's no need for all the indicators and local variables. Make a copy of the MY_UDP indicator, change to a control, and wire it to the "type" input of Type Cast. Or, slightly better, make a constant instead from the MY_UDP indicator and use that for the type. It will be a large constant, but you can move it outside the loop if you don't want the loop to blow up.

Also, eventually you should make that cluster into a Type Definition (see the help) so that if it changes, you only need to update the type definition and it all the instances of it will be updated to match.

[joe5213]

Thank you very, very much for all your help.

[A_LI]

hi  nathand,

I have used UDP write and read in the LabVIEW palletes for my testing. It gives the data only, can i get the complete UDP Frame (Raw Data).

I have gone through this link https://forums.ni.com/t5/Example-Code/Ethernet-Packet-Sniffer-Utility-Using-WinPcap-Functions/ta-p/3... but in this example is the receiving the data , i also have to send in the same way .

Do we have any other way using the winpcap in LabVIEW.

inputs :

 1. Data rate is 100 kbps.

 will this be helpfull for me please help me.

Thanks in Advance

Thanks

Ikram

[nathand]

The built-in UDP functions provide only the data, which is by far the most common use case. I do not know of a library that allows you to manipulate raw packets, you'll have to do some searching to see what your options are. Why do you need raw access to the packets?

[nathand]

Also, you should start a new thread, since you're responding to a post that was marked as solved over a year ago.