Quote:
Originally Posted by jhersh
Does this occur only if you open a socket on that port and never read, or also if you never open the socket at all?
BTW, the DS to cRIO port is only for crossing the field network. You should use ports outside the FRC range (as defined in the rules) for on-robot traffic.
-Joe
|
Hi Joe,
This is Mike Anderson. We've met several times at ESC. I'm the software mentor for Team 116. In any case, I've been able to duplicate the failure from Linux as well. I'm attaching the wireshark output, the code for the cRio that fails and the code under Linux that causes the failure. It generally fails within 70 packets or so causing the cRio to die.
So, compile the UDPtest and load it to the cRio.
Start the client on linux (set to talk to 10.1.16.2 at port 1929).
Within 70 or so packets, the cRio will die a horrible death. No diagnostic output on the net console. It just dies.
To compile the client code under Linux, use "gcc -o client client.c"
The client.bin.txt is the compiled Linux IA32 binary.
TIA,
Mike