Hi Developers, I use NI sbRIO-9651 SOM with our product, that acts as a server and accepts TCP/IP connections over Ethernet. I noticed one strange behavior with keeping connections alive. What I do: 1. The device boots up, loads FPGA bitfile and starts listening for connections, it is a Server 2. I establish a TCP/IP connection from a Client (PC) side 3. Then I communicate with the device, perform some actions 4. Then I ask my device through a TCP/IP command to load another bitfile to FPGA. And then something interesting happens: 5. If I have a direct cable connection (1-to-1), the TCP/IP connection on the Client side is terminated with the code Error 66 (The network connection was closed by the peer). The Server side doesn't detect the problem right away, and only after 20 seconds or so it closes the broken connection as well. 5. If I have an ethernet switch between my device and my PC, then nothing bad happens, the connection is alive. Have you guys seen something like this before? Do you know why this happens? What would you do to workaround this difference for an end user? Thank you in advance!

Hardware Developers Community - NI sbRIO & SOM

Author

Hi Nathan,

We will take this USB option into consideration when designing a new carry board.

I hope we find a software workaround to this problem with the current design.

Thank you!

Nikita Prorekhin
CLA

Message 11 of 11

(875 Views)