Centroid Community CNC Support Forum

On power up today the control reports "Timeout: MPU not responding". I checked the static IP address and it is 10.168.41.1. I also made sure that there were no firewalls enabled or antivirus software enable. When I open up a command prompt I am able to ping the control without issue and the LED on the OAK reports "1". Any help would be greatly appreciated.

Strippit 2 axis single station punch press
Oak Control

10.192.168.1 is the IP address of the computer. The results of the ping test show that this is correct. What is the result of pinging 10.168.41.2? That is the address of the Centroid control.

Are either of the lights on the control's Ethernet connector lit? Below is a photo of an Acorn's Ethernet jack but Oak's and AllInDC's are similar. Are you sure the Ethernet cable is good? Are you sure the Centroid MPU has power?

TB270 and this post help with com errors.
https://centroidcncforum.com/viewtopic.php?f=61&t=1451

I get the same results with pinging IP address: 10.168.41.2
I am assuming the cable is good by the ping test but I can try another cable and I will test the power connection next. Thank you for your help.

Has Windows recently updated? This can also be caused by Windows Defender blocking communications from CNC12. Turn Windows Firewall off or better yet, make sure cncm.exe or cnct.exe (depending on lathe or mill version) is added as an exception. The latter is the preferred solution as Windows periodically turns the firewall back on when IT feels like it.

This can also happen when the software opens before the MPU11 based control is finished starting up. Does it happen again after restarting the system? If you can restart the Oak itself then open the software manually a minute later, do you get the same result?

I have checked all the voltage inputs and swapped out the network cable. I have tried starting the software separately running as administrator but the problem persists. The LED status window displays 1. I look at the Windows Firewall exception again.

I want to thank you all for your help, it was indeed a firewall setting that needed to be changed.

sbtennessee wrote: ↑Tue Sep 20, 2022 3:39 pm I want to thank you all for your help, it was indeed a firewall setting that needed to be changed.

thanks for reporting back.