Dear Andy,
1 : yes, we only use the default ethernet port.
2, 3 : Unfortunately, it’s not possible to run our application on one of your standard carrier board, because our VF50 board must run with a second processor based on our specific carrier board.
This specific carrier board doesn’t output any UART, so we can’t see any boot log output …
4 - 5 : When not working, the VF50 doesn’t boot after a reset if the ethernet cable is plugged. If no ethernet cable is plugged, the VF50 seems to run correctly (use of Cerhost on the USB OK, exchanges correct with our 2nd processor based on the specific carrier board, …) except the ethernet link (no communication possible, no ping)
6 : Yes, we try to connect the Colibri to different ethernet router/switch (MOXA, Dlink, TPlink). It seems to be independent from the router/switch.
7 : Difficult to say, because not often (hopely, but too enough for a 24h/24h installation which can be reseted. perhaps 1% ???)
8 : When we see the problem, the ethernet link was constantly charged with UDP frames transmitted by other controllers (around 6 UDP frames/second). But, after that, disconnecting the other controllers from the network doesn’t help the faulty controller to restart correctly after a hardware reset.
In that case only switching off (min 5s) / switching on make the controller restart as it should do.
Thanks for your help.
Regards.