3D finder, crashed on auto Z calibration

[bergstar]

So I got brand new, shiny 3D finder from https://www.sorotec.de/shop/3D-Finde...nsor-6411.html
Connected it, spent some time getting it perfectly calibrated. A few fun hours in a workshop. I followed instructions, set all the parameters. So far so good.

Then I triggered "Calibrate Z" under Calibrate Probe Z Height - it worked just as expected. In 3D finder manual, it recommended to run it several times - so without doing or touching anything, I triggered "Calibrate Z" again. It worked as expected as well.

But after that it followed by a full speed negative Z plunge of about 10-15 mm straight into the ball bearing.

As a result, I no longer have a 3D finder.


I understand that somehow I should have known that triggering auto calibration will result in this crash, I just don't what I have missed.

Similar Threads:

• Cnc auto tool calibration
• Auto workpiece finder DSP57
• Auto labeling and auto feeding CNC machine for wood panel cabinet furniture
• Marlin delta auto calibration issues
• Mach 3 auto calibration problem

[ger21]

Are you using a Chinese motion controller?

[bergstar]

Are you using a Chinese motion controller?

No, I'm using CSMIO/IP-M from https://en.cs-lab.eu

[ger21]

CSMIO uses custom probing macros, and I've heard of a lot of users having trouble with probing with their controllers.

[bergstar]

CSMIO uses custom probing macros, and I've heard of a lot of users having trouble with probing with their controllers.

I did not use the custom probing macros, just the Mach4 interface. Also this is a calibration process, no the probing it self.

[ger21]

I don't know how the CS Labs Mach4 plugin works, but my guess is that it caused the problem.

[bergstar]

I don't know how the CS Labs Mach4 plugin works, but my guess is that it caused the problem.

Well this is highly unlikely - this is just a bug in Mach4. Sending regular gcode to the controller works just fine - its when you actually use Mach4 software you get into all kinds of problems due to horribly written software.

[dazp1976]

Well this is highly unlikely - this is just a bug in Mach4. Sending regular gcode to the controller works just fine - its when you actually use Mach4 software you get into all kinds of problems due to horribly written software.

Definately moving over to UCCNC when I get tired of Mach3.
Mach4 sounds like a buggy pos everywhere I look.

[bergstar]

Definately moving over to UCCNC when I get tired of Mach3.
Mach4 sounds like a buggy pos everywhere I look.

Yes indeed. Especially after watching this video:


I feel like step by step I had all the issues he experienced.

I will be moving to LinuxCNC.