Re: UDP problem

I thought of that, but it doesn't matter. That particular define is not used by DC. It's only used by my application to define the number of system communication sockets to open. I even removed opening any UDP sockets except for the one for ID on port 2000, and it didn't make a difference.
 

 Here's another data point I just received. If I use Scott Henion's Ethernet Downloader utility and do a search,  the R6k device responds as it should. But if use our internal utility the R6k never gets the packet. So I used Wireshark and captured both UDP broadcast packets, the one from Scott's utility and the one from ours. I'm looking at them side-by-side, and they are identical except for two differences. The first is the Source Port is different for each application. I don't think that should matter. And I think that's the way Ethernet works. Each application gets its own source port number.  The second difference is that the 8-bytes of data that Scott's utility sends are a 1 and seven zeros, while our utility has some scattered bits set. Again, I don't see how or why the value of the  8-data bytes would affect the packet being received or not. I could see my application getting the packet and after parsing the 8-data bytes decide to throw it away because it had an error. But my app never even gets the packet.
 

 And one more data point. Both utilities, Scott's and ours, work with the R3000 devices. It's only the R6000 that has the problem.
 

 Steve