Feature Request

snowgoer540 wrote:

phillc54 wrote: That is the same as the X/Y "jiggle", you are jogging back up to the soft limit. I purposely dodn't disable the offsets on Z like I did with X/Y to see if this would appear. I am surprised that it took so long to find. I will do the same with Z, disable offsets unless they are being used.

Oh, testing me to see if I would notice are you?!

I was interested to see if it would happen, as it has not been reported before. (that I can remember)

What do I win now??

You get to keep your job. :laugh:

I may not have noticed had I not accidentally started a probe with the torch lowered. Normally I don't jog the Z axis much after a failure.

Now I know why I said somewhere in the docs to not jog the Z axis.

Regarding the offset, I think we said this was a bug in the LinuxCNC core? If so, did it ever get reported?

It is not a bug, it is the way external offsets works. It is mentioned in the external offsets docs to stay away from the soft limits while offsets are active.

phillc54 wrote: I was interested to see if it would happen, as it has not been reported before. (that I can remember)

I do remember trying to get it to happen with the Z axis, but I never could. *shrug* guess I had a stroke of brilliance today? lol

You get to keep your job. :laugh:

Sweet! I enjoy it.

Now I know why I said somewhere in the docs to not jog the Z axis.

haha, I did say it was an accident :laugh: at least when someone else makes the mistake it wont do a springy maneuver haha.

Regarding the offset, I think we said this was a bug in the LinuxCNC core? If so, did it ever get reported?

It is not a bug, it is the way external offsets works. It is mentioned in the external offsets docs to stay away from the soft limits while offsets are active.[/quote]
OHH, I missed that part. Ok sounds good then. Just making sure.

All these issues "should" be fixed now in 2.8, master and the test branch.

phillc54 wrote: All these issues "should" be fixed now in 2.8, master and the test branch.

Thanks Phill, much appreciated as always! I am planning to mess with my THC this evening so I'll report back if something is amiss

One thing I noticed tonight: If you're on the MDI screen and the machine pauses during a cut, it will let you type in and send MDI commands, even though they do nothing. After a failed cut I kept trying to G0X0Y0 so I could bump the torch over and try again. It kept getting me that the machine was paused. It's be cool if the MDI box or the GO button (or both) greyed out during a pause, so you cant try to send commands and get confused why it's not moving like a goon

That is a problem of trying to integrate into existing GUIs. I could possibly do it with Axis but I doubt it I could do it with Gmoccapy.