If I call Socket.Close() method on a possibly non-functional socket (like, for example, when the other side crashes), the whole G400 locks up for quite a lengthy amount of time — sometimes for a minute. This shouldn’t be considered a normal behaviour?
Blocking the whole program for a minute is already a bad thing by itself, but for me it is even worse. CAN bus routines are still working somewhere at the firmware level, quickly overruning all the buffers and breaking something inside so G400 doesn’t recover at all, if Socket.Close() takes too long…
Any ideas?..