Someone who had, apparently, done TCP/IP broadcast to Kawasaki robots asked me if it could be done with KRCs. I had no idea. And nothing in the EKI manual even addresses it.
Of course, part of the problem is I'm not a TCP/IP specialist, just someone who's used it a few times.
Based on my experience with EKI, my first thought is that it couldn't work with the robots as clients -- if you configure an EKI channel as a client, then when your KRL program calls EKI_OPEN on that channel, you're essentially stuck until the server handshakes the connection.
But if the robots were using server-configured EKI channels, I'm not entirely sure that would work either. When I've WireShark'd the EKI traffic in the past, the SYN-ACK pattern opening a connection looked exactly the same as when the robot is a client, except in reverse sequence. So I guess the question is, would a server-configured EKI channel respond to multicast traffic?
Based on some quick Googling, it looks like my "transmitter" would need to direct it's traffic to 224.0.0.1, which is the defined IP4 address for "all hosts on this network segment."
Anyone ever tried this, or seen it tried? I'm honestly not certain how to go about creating a test for this -- looks like I have some studying to do.