TTS Tooling system

[JAZZCNC]

does probing work correctly as a separate macro? (not in m6)

Yes if using Cslabs macros. The problem is with Mach rather than Cslabs but the workaround is to use Modbus and talk directly to the controller rather than going thru Mach.
Bit fiddly for most but to the man with a DUZZIT Simplizzzz.

[battwell]

Yes if using Cslabs macros. The problem is with Mach rather than Cslabs but the workaround is to use Modbus and talk directly to the controller rather than going thru Mach.
Bit fiddly for most but to the man with a DUZZIT Simplizzzz.

does it capture exact step output the probe was hit on (like mach with parallel port does) and uccnc now does after a bit of nagging?
i presume the problem is with their plugin . are they going to fix it?
i havnt tried a csmio myself but i like to know each ones real life capabilities. (same question i forgot to ask re acorn too)

[Neale]

does it capture exact step output the probe was hit on (like mach with parallel port does) and uccnc now does after a bit of nagging?
i presume the problem is with their plugin . are they going to fix it?
i havnt tried a csmio myself but i like to know each ones real life capabilities. (same question i forgot to ask re acorn too)

I'm using something like Mach3 version .028 and that works fine with the CSLabs macro for touch-off and M6start/end. When I tested the touch-off mechanism, I was getting +-1 microstep repeatability, which is about .03mm on my router. CSLabs say that they are monitoring the probe input in their firmware so there is no Mach3 involvement at that point.

Even when Mach3 and the CSLabs firmware were still in development they just stood and shouted at each other - "It's all your fault!" Nothing is going to happen now. Looks a bit like CSLabs used an undocumented mechanism in Mach3 which Mach3 then changed after about v .028.