@bg_86 I'm tired of the whole "I know better than you" "you shouldn't want what your asking for" condescending elitism that's infused tech communities. You don't know what my situation is, what gives you the right to tell me that the reasons I chose the path I did are invalid? I literally told you I don't want to hear about another tool yet you forced the issue anyway. Either help me do what I'm trying to do, or stop wasting my time.

I have some force sensitive resistors, and a y axis with two solid parallel contact surfaces that are effectively a hard stop. I've been wondering if I could use one of said resistors for the end stop to accomplish something like the analog z-probe does with it's trigger point and trigger the stop when the axis is pressed hard enough against the hard stop. I'm imagining behavior much like sensor-less homing but more (?) reliable/accurate.

@bg_86 I'm tired of the whole "I know better than you" "you shouldn't want what your asking for" condescending elitism that's infused tech communities. You don't know what my situation is, what gives you the right to tell me that the reasons I chose the path I did are invalid? I literally told you I don't want to hear about another tool yet you forced the issue anyway. Either help me do what I'm trying to do, or stop wasting my time.

@bg_86 What did I say?

@richardmckenna As for the WorkBee, that is where I started with my machine but I've found them to be quite restrictive and inflexible (there was a customer service interaction where they insisted on getting on a phone call to resolve it, but wouldn't budge from a 2 hour window their time despite me being 9 time-zones out from them and having to get up in the middle of the night for their required window but I digress). They have the touch probe system that works great when working the way they envisioned but I'm trying to do things like locating the inside corner of a pocket and their built in interface is hard coded and won't accommodate that use case. They may do something with macros behind the scenes, but that's not visible to me.

@bg_86 How does this help me write a macro. If your answer is "Just buy this other program and you won't have to." then don't bother, that's not helping me write my macro.

@richardmckenna @Phaedrux Ah, that sucks.

I'm necroing this because while it's an edge case it's still a problem.

There's a bug report on git hub that was closed because no one replied in time and it says to open an issue in the forum if it's still a problem, but I'd rather keep a discussion going rather than clutter things with new issues on the same topic. Needless to say generally having a move command not respect what type of move you're commanding and moving unexpectedly is a problem, moreso in the CNC world than the printer one, and my post on the bug details exactly how this has impacted me (my own experience is quite similar to @Max3D 's but I was lucky enough to notice why sooner). I would request that we get some attention to this soonish.

@Danal , I know it's been a bit, but would you be willing to post an example macro? I've been having some trouble figuring out how to compensate for tool width and an example of how you did it would be a great starting point.

@T3P3Tony , might want to add this to your documentation, there's no mention of this in either the new or old docs.

Fun Fact:

The v1.2 STEP file doesn't match the v1.2 specs.

In fact, it seems to match the v0.6 specs.