Some thoughts and some findings using PlasmaC

More
6 years 1 week ago #187031 by snowgoer540
Ignored how? Like Rod had described?

Please Log in or Create an account to join the conversation.

More
6 years 1 week ago #187039 by tommylight
Nope, it just moved fast at setup speed, not slowing down.

ASUS ROG Crosshair VIII Impact - AMD X570

Please Log in or Create an account to join the conversation.

More
6 years 1 week ago #187043 by phillc54
Tom is it possible that the material buckled up enough so the the top of the material was above the Probe Height. Remember that Probe Height is measured from the MIN_LIMIT rather than the material.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
6 years 1 week ago #187071 by tommylight
When cutting square tubing i set the probe height much higher, but yesterday i was cutting only 3mm and i did set the probe heigh just to make sure, but still it would just run full speed down.
Doing more cutting today so i will see if i can reproduce that and report back.

ASUS ROG Crosshair VIII Impact - AMD X570

Please Log in or Create an account to join the conversation.

More
6 years 2 hours ago #188035 by DenkBrettl

Franklin wrote: One more note for pierce/cut mode. When in the Gcode is present the spotting function and turn on the "Pierce only" mode the plasmac makes piercing instead of spotting.
It would be great to ignore spotting when "Pierce only" mode.


I had exactly the same problem today. So I fixed it :-)

My fork can be found here: github.com/DenkBrettl/linuxcnc - I've opened a pull request as well.

Klaus
The following user(s) said Thank You: phillc54

Please Log in or Create an account to join the conversation.

More
5 years 11 months ago #188057 by tommylight

tommylight wrote: When cutting square tubing i set the probe height much higher, but yesterday i was cutting only 3mm and i did set the probe heigh just to make sure, but still it would just run full speed down.
Doing more cutting today so i will see if i can reproduce that and report back.

Warning : Do not take any of this as de facto as i have two very fast machines that are set in many ways differently from what is normal setup.
This got to be more complicated than i thought, so here is some more:
As far as i could gather the ignoring probe height was happening as i had my heights set differently, i had the Z axis set as min at 0 and max at 180 or 200 on both machines and rarely had the issue of Z axis moving to far up and hitting the limit switch, but when i updated to 0.177 and later to 0.180 it got to the point of being unusable, so i set the Z axis as 0 max and -180 and -200 on both machines and that issue was gone .... until i started cutting some square tubing so the cut height was in the upper 50 to 80 mm of travel even when the safe travel height and probe height are set properly and both functioning it will still overrun and hit the switch.
Overruns will happen occasionally during normal work when everything is working properly and will not trigger the switch but will move past soft limit so resuming will not be possible without stopping the program execution and running from line after that it will run normally for quite some time or not repeat that again at all.
Checking the Z axis position in World and Joint mode shows the soft limit has been passed.
Writing this got me thinking, i must lower the setup speed as i did that before for testing and all these issues disappeared, but i like speed ! :) I have them set at a meagrely 4800mm/m!
Overall it is working magnificently and i am really enjoying using it all day every day, just the fact that i have not gone back to using "my" config should be enough proof that all of the issues i am having are mostly self caused. :blush:

ASUS ROG Crosshair VIII Impact - AMD X570
The following user(s) said Thank You: phillc54

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.470 seconds
Powered by Kunena Forum