Tech Bulletin 270 (Rev7) - Solving CNCPC To MPU Communication Errors
Tech Bulletin 270 (Rev7) - Solving CNCPC To MPU Communication Errors
Centroid CNC controls communicate with the CNCPC via Ethernet connection. This communication
method is very reliable and fast. Setup and Installation details are critical for good, reliable CNC
control performance. These details are simple and easy to get right and should not be overlooked.
1.) Complete shut down of communication between the MPU (Centroid CNC control card such as the
Acorn, Oak, Allin1DC or MPU11) and the CNCPC
This type of error results in Error Message “452 Ethernet Communication Error, CNCPC to controller.
See Tech Bulletin 270" which appears in the main screen message box. This error message can also
be seen in the error log found in the Utility menu and same information can be found in a report.zip
urf folder.
The 452 com error is the most obvious and easiest to solve.
When these types of Ethernet communication errors happen they are recorded in the error log but not
displayed on the CNC12 main screen dialog box. (Note: Starting with CNC12 version v4.66 (Acorn)
and v4.22 (Oak/Allin1DC/MPU11) when a certain number of these types of errors are recorded within
an hour this message will be pushed to the CNC12 main screen dialog box).
“Communication Errors Detected, See TB 270”
Depending on the frequency of communication errors 944,945,946,947,948 and how the CNC control
is being used they can result in puzzling hesitations in operation of the CNC control or be completely
unnoticeable by the operator. In either case these errors should be eliminated for good CNC control
operation.
Causes of CNC control to CNCPC communication errors fall into two main categories.
2.) CNC system noise related. Cables, routing, missing quench arcs (aka snubbers)
1.) Not performing the Centroid CNC controller communications Bench Test.
https://youtu.be/W7cP7jwuGno
2.) Not properly setting up Windows for CNC control use. https://youtu.be/W7cP7jwuGno
6.) Ethernet adapter drivers on the CNC PC haven't been updated (always use manufacture drivers
when possible)
7.) ANY type of anti virus software installed, you can't just simply turn it off you have to uninstall it
9.) Windows or Laptop bios power saving feature turning off the Ethernet adapter, Windows resetting
the ip address automatically.
11.) The shielded Ethernet cable is bad, try another shielded cable as a test.
13.) Windows Updates or any other auto updaters are active hogging up PC resources
14.) Using the dedicated DC logic power supply for the Centroid CNC controller card (Acorn, Oak,
Allin1DC, MPU11) to power other components.
Solve CNC control to CNCPC communication errors by getting these details right.
1.) Setup Windows for CNC control use. Be sure to follow the details on how to properly setup
Windows 10/11 for use with a CNC control. Settings that control sleep and Ethernet ip address
settings along with others settings are critical for good cnc control operation.
- How to Setup Windows for CNC control use Videos are found on the Centroid Tech Support
YouTube channel, the Centroid Tech Support Forum and The Centroid DIY web page.
- The most common cause of PC Data Receive Errors are firewalls and anti-virus programs. These
programs intercept and delay the real-time data exchange between the CNC Control and the
CNCPC. These delays can accumulate to the point that it triggers this fault. If you are seeing PC Data
Receive Errors, completely disable all firewalls and uninstall all anti-virus programs. Remove any Anti
Virus software*. you can't just simply turn it off, it must be uninstalled.
- If the Windows Firewall is ON the first time you run CNC12, the Windows firewall will typically ask
you to “allow” CNC12 to run be sure to check both the Public and Private check boxes when asked. If
for some reason Windows doesn’t ask or you would simply like to check the Windows Firewall
permission status of CNC12 navigate to Windows Firewall Advanced settings panel and make sure
cncm/t/r/p is set to Private,Public, Enabled and Allow.
A good firewall test is to simply disable the entire Windows firewall temporarily.
2.) Connect the Centroid CNC control board directly to the CNCPC Ethernet port with a Shielded
cable. Do not use an RJ45 bulkhead connector* or a regular non-shielded cable or a USB Ethernet
adapter or any other type of adapter. We have seen a few bad Ethernet cables so its always a good
idea to have a spare shielded cable to test with as well.
3.) Run Windows Update and be sure to install the latest Ethernet adapter drivers directly from the
manufacturer’s website.
4.) Windows (or Laptop* bios power saving feature) is turning off the Ethernet adapter and/or
Windows resetting the ip address automatically. Unselect “Obtain an IP address automatically” in
Windows Ethernet adapter settings and select “ Use the following IP address”
5.) Remove any other network devices* from the CNCPC. Network traffic from other network devices
can cause a dramatic decrease in PC and network performance. Remove all other network devices
and connections to the PC, uninstall any hardware drivers or network utilities associated with network
hardware not associated with the network adapter connected to the CNC controller. Wireless network
devices that are searching for a connection can be extremely resource intensive and interfere with
CNCPC to CNC control communication.
6.) Other applications running on the CNCPC. The minimum hardware requirements specified by
Centroid take into account running only the CNC12 software. If receiving PC Data Receive Errors,
please terminate any other programs that may be running hogging up the PC resources.
7.) Windows, Adobe, anti-virus etc.. auto updaters can bring a PC to it's knees while checking for,
downloading and/or installing updates,
CNC system noise related communication errors: Cables, routing, missing quench arcs (aka
snubbers)
1.) Run the shielded Ethernet communications cable directly from the Centroid controller card to the
CNCPC. The cable running between the MPU and CNCPC should be a single shielded cable that
does not connect to any switches, hubs or butt connectors*. Any of these things can effectively defeat
the shielding and introduce noise. They may also likely introduce propagation delays which will cause
this error as well.
2.) Do not run the shielded Ethernet cable next to any three phase or power cables. The Ethernet
cable should never be run alongside any three phase or other power cables. Route the Ethernet
cable well away from spindle and servo motors and any other cables with inductive loads such as
coolant and lube pumps, and especially solenoids and their related cables.
3.) All the inductive loads in the cnc system are required to have Quench Arcs (aka snubbers)
installed on them. Quench arcs are very important and must be installed across the coils of all relays,
solenoids and motors. Quench arcs should be installed as close as physically possible to the load
(coil) itself. See TB206 Noise Suppression
4.) Use a CNCPC that at least meets the Centroid minimum CNCPC hardware specs. Found here on
this page. https://www.centroidcnc.com/centroid_diy/acorn_quick_start_guide.html
Do use a CPU with a single core benchmark performance rating above 1500. (this does not mean
you have to use a single core CPU (which is impossible to find these days anyways). The single core
bench mark rating of 1500 or higher is the performance rating is for ONE of the cores of the PC’s
CPU, NOT the overall score (combined core performance). Check a CPU’s single core performance
rating here.
https://www.cpubenchmark.net/singleThread.html
It is cheap and easy these days to find a PC that exceeds the minimum Centroid Hardware
requirements so there is no savings in trying to use a PC that doesn’t.
5.) Dedicate a Logic power supply to the Centroid CNC control card. Do not use the CNC control
card logic power supply to power anything else but the Centroid CNC control card. Common
mistakes are using the control card logic power supply to power relays, contactors, solenoids etc. Do
not do this. Use a separate power supply to run all the other items in the CNC control system.
6.) Check power supply connections. Verify that the connections between the logic power supply and
Centroid CNC control card are crimped properly. We have seen in the past that a poor crimp in these
wires can cause random 452 errors.
Discussions.
The Windows Ping Test is a great test to confirm basic Ethernet connection from the CNCPC to the
Centroid CNC controller card. It helps you quickly determine if there are any “big” connections issues
between the CNCPC and the controller card. It however is not a definitive test. Just because the ping
test reports good results does not mean the CNC system is free of communication errors. The ping
test really just confirms at that moment that the two Ethernet ports are connected and communicating.
CNCPC Communication errors can and do sometimes only occur when noise (electromagnetic
energy) is introduced into the system or some software decides to interrupt the communication for
some reason.
Intermittent communication errors often show themselves when the CNCPC is being heavily taxed,
one such scenario is when there is a very short vector G-code program being run with Centroid CNC
G code Smoothing active. While the Centroid system does NOT rely on the Windows PC CPU for
Motion control (commands going to the axes motors) when the Centroid G code smoothing feature is
active the Windows PC CPU is utilized to Pre-process the G code program on the fly, it loft arcs thru
all the short vectors of the G code program to produce significantly smoother machine tool motion.
The G code smoothing feature passes a lot of data back and forth from from the CNCPC to the
Centroid CNC controller card while running the job so all the details in this document need to be right
for the best CNC machine tool performance when using this feature.
*All of these items can be used in conjunction with the Centroid CNC Controller but add an additional
layer of complexity by introducing a number of possible communication issues. Avoid adding
complications to the system when first setting up the CNC system OR when solving communications
errors. Eliminate these items to get to the point where there is good solid communication between the
CNCPC and the Centroid controller. Then and only then, if you really want to, reintroduce these items
into the system one at a time.