Centroid Community CNC Support Forum

Is there an issue if I wire the machine so the one switch triggers both HomeAll and LimitAll at the same time? Will that interfere with the homing cycle?

I get that but if you follow the proper procedure and home the machine FIRST as the software expects then you reduce the consequences of making a mistake to ZERO. :mrgreen:


You're using a different definition of "mistake" than I am if you rely on the operator to always follow any procedure ...

After you power up the machine and press the reset button on the VCP the first thing you do is HOME the machine. Why are you jogging it around?


I understand that if I do everything properly in the right sequence, I won't crash the machine. I'm trying to understand if I can set it up to protect ...

Is it possible to make the home switches stop the machine movement when jogging prior to homing?

I have a slaved dual-drive gantry machine set up with three homing switches (-X, -Y master, +Z) configured on a HomeAll input, a slave axis homing switch (-A) configured as SlavedHomeInput, and limit ...

One thing to be forewarned about. The Centroid autosquaring routine clears the soft limits at the start of the routine and then restores them at the end.

If something happens that prevents the autosquare routine from finishing, your soft limits will remain cleared and you will need to manually re ...

Thanks for the responses. This is what I suspected, but thought I'd ask.

I write software for a living, so I can certainly code a macro, but I also see the value in walking the well-worn path when there's no benefit to doing otherwise. When I was planning the build, I had enough inputs, so I went ...

Is it possible to use auto-homing and auto-squaring on a gantry machine with dual drive Y axes and separate home switch inputs for each axis?

I'm running with software pairing, with separate home switches on each of the X, Y, Z, and A (slave) axes, with the inputs defined as FirstAxisHomeOK ...

Yeah, agreed. The USB worked, but it's going to have more latency and jitter, even if it continues working long-term. Plus, the USB-C connector is going to be much more susceptible to pulling out at a bad time on a real working machine.

I edited the first post in the thread and added a link to the solution. I don't know if there's a better way.

Good troubleshooting work!
In your packet sniffer, you should see a UDP broadcast when the software tries to detect ETH1616. Now that you fixed it, you should see that UDP broadcast, not just the ARP broadcasts.


And in fact, this is exactly what I see. The ETH1616_RESPOND message goes out to ...