Replies: 5 comments 10 replies
-
|
It is not possible to add this to grblHAL. However, it can be added to ioSender. What feedrate do you define as "slow-ish"? |
Beta Was this translation helpful? Give feedback.
-
|
3-500mm/min or something like that. so one can actually see that one doesn't crash into anything :-) |
Beta Was this translation helpful? Give feedback.
-
|
I presume this feature is for checking the program without actually cutting? If it was to be added to ioSender, maybe add a Z-limit function enable button and a Z-limit value field. That way when the function is enabled ioSender could limit the Z value sent to the value in Z-Limit field? As to the Z feedrate, the feedrate override function could be used to slow down the movement. Cheers, Peter |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it's just to see visually on the machine that your toolpath is clear of clamps etc. Imho Z can just stay exactly where you are - i.e. you jog to the z-height you want, and hit the button, and it does a little walk around the edge (X and Y), and one can quickly see if the path is clear or something is uncomfortably close. just ran into another clamp today while doing a job, because i mistaenly thought it was far enough away. :-/ (endmill survived luckily). Also a rookie question - what's the easiest Gcode to go to a coordinate with full feedrate? - ie. move fast to x + 100mm ? (machine coordinate) |
Beta Was this translation helpful? Give feedback.
-
G91G0X100 |
Beta Was this translation helpful? Give feedback.
-
|
thanks :-) |
Beta Was this translation helpful? Give feedback.
-
|
If the intent is to make sure that your gcode and workpiece are co-incident, then Program Limits in the 3D view is pretty helpful. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, but to really see if i'm clear or not, i usually need to jog to the positions - that's where it would be handy to have the machine do a little walk around for me :-) |
Beta Was this translation helpful? Give feedback.
-
|
Added as a flyout to the latest edge version. Note that this has changes to Tool length offset probing that I hope is ok, please be careful when using this and report any issues! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you again Terjeio! then i make sure my bit is lifted well above anything (in this case i just left it at it's home position). open the outline: I hit go, and get an alarm 2. so i somehow exceeded my machines workable area. I'm not sure what gives. |
Beta Was this translation helpful? Give feedback.
-
|
when i look at the program there is something that doesn't add up... look at this: It does go a bit across 0 on the x axis, but Y should be all positives. below is the NC, it's not horribly long. (Face-Rough) (Face1 - smoothing) |
Beta Was this translation helpful? Give feedback.
-
|
It seems like a bug in my gcode parser - I guess due to plane changes (G17/G18). Will look into this later - I am off for some shopping. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like it is due to incorrect handling of G28 moves, new edge version uploaded that should work. |
Beta Was this translation helpful? Give feedback.
-
|
I'll check that out shortly. I've just redone my fixture plate with a million holes with threading it took quite a while. But everything was very stable throughout this 2.5h job. I'm very pleased with that. |
Beta Was this translation helpful? Give feedback.
-
|
and it works like a charm! Thanks! that feature is going to save me quite a few clamps and endmills :-) |
Beta Was this translation helpful? Give feedback.
-
I was wondering if it would be possible to do a "sizing". Currently in 3d view i can see the program limits, and I can manually jog to the X and Y limit, at a safe Z height, to see that i'm clear of clamps and such before starting a job. Would it be possible to make a small feature that does a slow-ish walk around the edge of the program loaded (without changing Z-height)?
Beta Was this translation helpful? Give feedback.
All reactions