Page 3 of 3

Re: 432 Ethernet Communication Error

Posted: Tue Jan 10, 2023 4:13 pm
by IPGregory
Did you ever get this resolved? On mine I have constantly returning comms issues. I have narrowed it down to a few settings I can change to get them to go away but they come back. I have to turn off AV every time I start the CNC PC even though I have it disabled through the group policy settings. I start the Acorn before I start the PC. Then I start CNC12 and after the homing sequence I run the Comms Stress Test and see if there are comms errors. If there are then I have to go into setup and flip the speed settings for the adaptor. I keep it defaulted to 100Mb/s Half duplex, but I flip it to Auto negotiate, wait for the Acorn to throw a reset, reset in the SW, then set it back to 100Mb/s Half Duplex. I only have to do that say 1 in 5 times I start up. Sometimes that doesn't work, and I have to keep the PC on but cycle the power on the Acorn and that will fix it. After that as long as the PC stays on, the Comms errors will stay away for that session. It's annoying and I am not sure if it's a NIC/Driver issue on the PC or on the Acorn.

Re: 432 Ethernet Communication Error

Posted: Tue Jan 10, 2023 4:24 pm
by vw_chuck
I had the same comms errors on my machine and I had to reload windows to fix it.

Re: 432 Ethernet Communication Error

Posted: Tue Jan 10, 2023 4:35 pm
by IPGregory
It's a fresh cut down install, but I guess that's worth a try. Thx.

Re: 432 Ethernet Communication Error

Posted: Tue Jan 10, 2023 4:58 pm
by Hugo Turn
Sometimes it still appears to me, but it has little effect on the operation of the machine. I have Windows 10 updated in August 2022.

Re: 432 Ethernet Communication Error

Posted: Tue Jan 10, 2023 6:34 pm
by cnckeith
Hugo Turn wrote: Tue Jan 10, 2023 4:58 pm Sometimes it still appears to me, but it has little effect on the operation of the machine. I have Windows 10 updated in August 2022.
try a different PC

Re: 432 Ethernet Communication Error

Posted: Wed Jan 25, 2023 11:44 pm
by RJS100
I looks like turning on Acorn, then turning on the Intel Nuc solved the problem. I have not seen this problem pop up in quite some time now!

Thanks.... Richard