Probe test problem

phillc54 wrote:

So when you home, Z is about 4.5" above the slats.

You press Probe Test and Z moves down at the rapid rate, hits the sheet then gives the "float switch detected while moving to probe height" error

Yes, exactly that.

Also, I tried running some g-code. It does something similar, goes to probe and then errors out because it hit the float switch.

Can you post your .ini, .hal and your <machine>_config.cfg files

phillc54 wrote:

Can you post your .ini, .hal and your <machine>_config.cfg files

Absolutely. See attached. .cfg changed to .txt because of rules

Before I take a good look, Probe Height is the distance above the minimum limit, so the top of your material needs to be at least Probe Height higher than than the bottom limit.

phillc54 wrote:

Before I take a good look, Probe Height is the distance above the minimum limit, so the top of your material needs to be at least Probe Height higher than than the bottom limit.

I'm more of a visual guy, to be honest, so these min and max limits havent really clicked yet, but as it stands right now after I home the machine with Z all the way at the top, I can jog down until the torch is about 1.5" under water. My machine travels such that movements from the top of the Z axis, toward the work piece are negative. So where the top of travel is 0, the bottom of travel would be -4.7". Similar to my milling machine.

I tried setting the Probe Height to the smallest value (.1") and it still does the same thing. I'm mostly at a loss as to why it doesnt just Work.

OK, jog your torch down to the bottom limit then measure from there to about 1/2" above to top of the material.

This value needs to be your probe height, unless you are cutting material that would be above this height.

Edit: remember to jog Z back to where you started or re home your machine.

Ok, awesome. I was definitely thinking about this backward (or something). I set it to 3.25" and it probes slightly from above the surface. Kind of makes sense now, but most importantly, I MADE MY FIRST CUTS!

Thanks a bunch for the help!

One more thing, should I be able to edit the config values by clicking on them and typing with the keyboard? Because I cannot.

Yes you should. I am running your config here at the moment and it does work.

You have a couple of issues with homing.
HOME_SEQUENCE is negative only for joints that need to home in sync.

For a xyyz config it would normally be something like:
So Z would home first then X and Y would home together both both Y joints syncronised.


[JOINT_3] seems to missing:or do you manually set it to height before homing.

phillc54 wrote:

Yes you should. I am running your config here at the moment and it does work.

hmm, for some reason it does not currently work that way, I can only use the up and down arrows which takes foreverrrr (unless I modify the config directly). Any ideas on what to look at?

Thanks for the heads up on the homing sequence. I am not sure why I did that. Z currently doesnt have the limit switch hooked up, as I want to redesign the axis at some point. So home in place works. Otherwise I was going for Z, X, YY. So I changed them to 0, 1, -2 -2.

hmm, for some reason it does not currently work that way, I can only use the up and down arrows which takes foreverrrr (unless I modify the config directly). Any ideas on what to look at?

Not really, I don't normally use Gmoccapy. It definitely works here in both Gmoccapy and Axis.

Does it show that behaviour in both the Run and Config Panels?