Centroid Community CNC Support Forum

Wizard is set to reverse and pair axis 4 to axis 1 (X axis) but it does not properly set parameter 64 so I changed it to 1 pairing N (4th) axis to X (1st).
All axis jog in the correct directions and X is paired properly.
The mill software shows the pairing per Manual page 14-5
"Special function indicators: These appear, if present, between the axis number and the label. ‘s’ – indicates the axis is the spindle, ‘p$’ – axis is paired with axis ‘$’, ‘*’ – pairing conflict. See Machine Parameters for more information on setting up special functions."

Currently the "RESET HOME" button does basic homing correctly.

How should cnckeith's file cncm.hom above be installed?
Do I just overwrite my current C:/cncm/cncm.hom with it?

Thank You

The ACORN software isn't using parameter 64 for that axis pairing feature. Are you stating that the system wasn't working originally and that by setting parameter 64 then it started working? Or are you just assuming that the settings in the Wizard should have set parameter 64 accordingly and because it didn't, you manually set that parameter?

All you have to do is copy that cncm.hom into your c:\cncm directory and overwrite the existing file.

When we replace the cncm.hom file with the slave homing update version our machine changes the pairing from both x motor paired(axis 1 and 4) to an X motor and the Y motor.

When we don't try to install the updated homing file all was good.

A new more pressing issue occurred yesterday though. During a wizard change and writing to acorn the wizard stopped suddenly and disappeared, bricking the board. It was straight forward enough to fix that though, heat beat restored. Now we cannot get network connectivity, windows says that the cable is disconnected. Swapping with the other network adapter(internet) shows the second network adapter is working fine. I've confirmed the firewall is off. Tried another cable too.

Further tests on the network connection to the computer reveal that the green light on the beaglebone is on. With different computers and different network interfaces I've been unable to get any network activity or lights on the computer end of the cable. I have tested the cable and the network interfaces by connecting to the internet or using the cable elsewhere. I'm beginning to think the original problem with the loss of communication and corruption of the beagle bone firmware was due to a failure of the NIC on the beaglebone itself.

There is a known problem with the Beagle Bone boards (both black and green) with the Texas Instrument's Ethernet PHY chip. A significant portion of the time, the PHY does not initialize on startup and the BBB (or BBG) must be re-started.

More information is available here: https://wp.josh.com/2018/06/04/a-softwa ... phy-issue/

Have other Acorn users experienced Ethernet connection issues? Is Centroid aware of connection issues with the BBG and the Ethernet Chip? I have only got as far as a bench testing with mine and it has worked each time I've powered it up. From reading the linked article on the BBB workaround, it sounds like cycling the power will eventually get the Ethernet chip communicating again.

Oh my. I certainly hope Centroid was aware and did one of the suggested hardware fixes on the Acorn "cape". So far I must have restarted(all power off) the board a dozen time trying things with no luck. So far the only suggestion I've gotten from paid support is to try pinging the acorn.
Thank you tblough for the depressing link Considering the BBG is powered by the header pins that makes for a worst case scenario(16% no LAN on boot).

On the newer hardware I have not had connectivity issues.

Can't understand what you did in the Wizard to "brick" your Acorn.
If the blue heartbeat led is blinking at one blink per second it is not bricked.

Take screen shots of your settings, take a report to USB memory stick, uninstall and reinstall the software.
Make sure no anti virus software is running first.

Hope you figure out what's going on...or can find someone to help you.

Marty

I fixed the bricked condition with ease following the video, heartbeat was restored before the LAN issue arose. I'm not sure why the wizard just closed during the writing either. My hand was not even on the mouse.

The issue was not a software problem, the LAN port was just plain broke! Even before you logged into Windows you could see the LAN lights were not active. On the BBG the ONLY LAN light was a steady, but dim green.

I went onto a site called Amazon and bought a new BBG for a test, LAN issue fixed. Of course now my Pro license does not load.... they are fixing that for me.

With this side trip fixed we can get back to fixing the initial issue, slave axis homing.