Hey Tom,
you are right, I don’t run this controller. I just have it attached to the net in my lab and can access it from any computer, and can run g-code on it, and explore its system, and test modifications.
Also on my own machine, I don’t plan to use this controller for production, just to explore its system.
This does not seem related to the controller, but to the machine itself. Have you ensured accurately that your machine is rectangular (“squared”) (➪ bar gauge) and coplanar (“not twisted”) (➪ fishing line method)? If it is not adjusted, Y movement can block. Coplanarity of the machine is often underestimated (machine not being twisted).
X, Y and Z can block due to issues listed in Troubleshooting: Rail is getting hung, stuck, or out of alignment (x35/x50 machines). This mainly boils down to: The connectors I criticize, the unshielded stepper cables that I criticize which are susceptible to EMI, the lacking strain relief on moving cables I criticize, the Z “curly” cable being not made for permanent motion developing internal cable breaks after a longer while what I criticize, and also having to adjust ball screw end bolt after assembly or temperature change, as well as checking coupler grub screws after assembly or temperature (the last two are nothing unusal). So nothing related to the buildbotics controller.
Did you think of what I posted in another thread of yours, that I would never put the Onefinity PRO/Original into service with 1. unshielded stepper cables 2. these unreliable connectors 3. Lacking strain relief on the entry of Z and X stepper cables on the left end of the gantry 4. with a “curly” Z cable that is by no means made for permanent motion?
The Raspberry Pi 3B inside the controller has no connector for an external WiFi antenna, and the grounded Onefinity controller box is a faraday cage that impacts WiFi radio signals. I would never consider the WiFi on the Onefinity Controller as a way to attach it to your network. It has a nice Ethernet port for this, especially useful in environments with many sources of EMI like workshops with power machines and power hand tools.
What firmware are you running?
I stick with v1.0.9 since all I’ve seen from Onefinity’s own further development were problems.
An issue that I find unnecessary and not understable why it is not fixed, is:
This however seems to be inherited from upstream buildbotics and neither is fixed there.
Stall Homing (=machine bumps the axis carriage to the end of travel until the stepper driver detects it = poor homing repeatability) is a function that Onefinity gets for free from the internal TI stepper driver and is not worth to be considered. I often critized that the machine lacks hardware limit switches and I link to how to retrofit them to the machine.
I can confirm that the fact that the machine looses all positions and offsets in estop mode is understood by nobody. It is simply a stupid thing.
I believe you with your other problems you listed here, since you have the experience. But you mix them with issues that are not related to the controller. Specifically the connectors and unshielded cables problems will remain if you switch to Masso/Elite, and other issues too. I want to prevent that you believe the Masso is perfect and will resolve all problems, since many issues are not controller-related.