Does RN WiFly add UDP header info?

Wireless & IoT
1

I’m using a Roving Networks WiFly-GSX to implement an OSC link.

I’ve gotten it to work fine to/from the Processing IDE using the OSCp5 library, but TouchOSC on the iPhone/iPod crashes every time I send it an OSC/UDP packet from the WiFly.

I have been assuming that the WiFly Automatically appends the UDP header info (port numbers, length, & checksum), to the data sent via the UART, since the data is getting to Processing and its OSC/UDP interface.

Anyone know if this is true? Do I need to preface my data with the UDP header info to make it a “real” UDP packet?

2

UPDATE -

I did a little packet sniffing, and it does appear that the WiFly correctly forms UDP Packets.

I also determined that the WiFly does NOT remove the “Match” character from the packet stream - it just appends it as the last byte in the UDP packet, which may be the cause of the TouchOSC problems.

BUT -

Bigger concern is that the WiFly occasionally seems to “drop” the first byte in the stream. Wondering if it drops off long enough when forming/sending a packet to lose an occasional byte.

3

paul.shubert:
Bigger concern is that the WiFly occasionally seems to “drop” the first byte in the stream. Wondering if it drops off long enough when forming/sending a packet to lose an occasional byte.

Remember, there is no error correction/identification in the UDP-Protocoll. My experience is simular. In my setup, there are sometimes errorness submissions, which may be caused by serveral factors. I will use a checksum in my final project.

Hami