We use cookies to personalize content, interact with our analytics companies, advertising networks and cooperatives, and demographic companies, provide social media features, and to analyze our traffic. Our social media, advertising and analytics partners may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. Learn more.
I had an issue where Easel stopped asking me to probe the work during the carve stage.
I set up the machine again and reminded it that I had a Z probe, and that seemed to work. I ran it again, homed the machine, jogged it to the spot where I wanted to cut, got the probe questions and successfully probed the work.
Once.
Now it goes through the process, asks if I want to probe, shows contact when I touch the bit to it, and looks for all the world like it’s about to probe, but when I tell it to “Start Probing”… nothing. The screen looks like it’s probing, even SAYS it’s probing, but it’s not.
These two instances were less than 5 minutes apart. Worked perfectly, five minutes later, after doing nothing but jogging and homing the machine, it won’t respond to a probe command. The Z works perfectly in the home command and in jogging, but for some reason ignores the probe command.
Tried this in Opera, Chrome and IE with identical results.
checked my wiring, but the probe wiring wouldn’t keep it from moving down to try and touch the plate would it? The spindle isn’t moving when I hit “probe”
If you use the Inventables Z probe socket, then yes it could. The socket is a normally closed socket so it would appear as an immediate trigger of the probe. Doesn’t explain why it gets stuck though.
Yes, soft limits enabled. I thought about that and went into Machine Inspector and tried to disable them but it wouldn’t change them. Could that be because of the alarm that was evidently being sent constantly? (That is what I’m seeing with the continuous rolling screen of alarm messages, right?)
I agree but, I’ll tell you why Inventables won’t change anything.
The Z probe command they send has a potential max travel of the entire Z axis. The reason for that is they are coding so that it works no matter who does it or where it starts. A lot of users will move the Z close to the probe prior to starting the probe, as that makes sense to do. However, there will be a decent amount who expect to be able to launch the Z probe immediately after homing which means they start from the top of the axis. With no real knowledge of where the Z is (hence the probing), they are coding for the absolute worst case of probing, starting right around Z=0 instead of like a 0.25" on top of the probe.
Is this smart? No. But unfortunately, it’s probably needed. That is unless you have training material available that will show best practice is to jog the spindle close to the probe prior to probing.
