PixelCNC Has Moved: deftware.org

CAM software developed by artists for artists to create unique and original works on a 3-axis CNC router or mill. · By Deftware

Add to collection

tool Community Devlog

PixelCNC Has Moved: deftware.org community

Z Rapid Height not happening - Snapping bits

A topic by Pluto2010 created 10 days ago Views: 34 Replies: 6

Viewing posts 1 to 4

Pluto201010 days ago(+1)

Hi.

Been a while since i last used the machine but i cant get past the first rapid move when it should goto the safe height.

Every time it snaps the bit .

I've tried setting the rapid heigh to 15mm to try and exaggerate the move but it still snaps. It always seem to snap with the bit at max depth of the last cut before moving.

The preview doesn't play the move and skips from last cut to new location so assuming that is whats being output to gcode. no raise then move, just move.

Please help :)

Thanks

DeftwareDeveloper10 days ago

Hi Pluto,

The simulation mode only depicts the actual cutpaths being traversed, and not any retractions to the Rapid Height or the rapids themselves. Only ramping and helical entry cuts are also depicted, but plunge entry cuts are not included. It sounds like a potential CNC controller situation, perhaps a work offset that's being triggered. What post-processor are you using?

Have you looked at the G-code output itself to see what's happening at the end of one operation and the beginning of another? I'd like to take a look at it if you could send it over to support@deftware.org :]

- Charlie

Pluto201010 days ago(+1)

Have sent you over the project file thanks.

Im using the GRBL Metric post processor and running with universal gcode sender.

It does put the gcode in, should it wait for the move to complete before moving on?

X19.51 Y302.47 
G0 Z10.00 
X40.63 Y301.65 
G1 Z1.02 F120 
X40.51 Y301.74 Z1.01

DeftwareDeveloper10 days ago

Hi Pluto,

The project file looks fine, the G-code looks fine. It must be something with your CNC controller. After it reaches the XY coordinate at the end of the cut it should then be rapiding up to Z10, which would be 10mm above the workpiece - assuming that Z0 is the top-surface of the workpiece. If you can manually issue commands to your machine, zero the origin somewhere up in the air and then run a G0Z10, and it should move up 10mm. If it doesn't move 10mm upward from the established machine origin, or moves downward, then the controller probably isn't zeroed out where it's supposed to be for the Z axis.

There does appear to be a toolpath artifact that's resulting in many small individual cuts in two spots in your project:

This is caused by a lack of canvas resolution. Increase your Canvas Resolution to 200ppi to get the proper cuts that I imagine you're going for:

Those cutpaths might've been what caused your cutters to break? Let me know what you find.

- Charlie

Pluto201010 days ago(+1)

Thanks will give it another go.

I can manually jog all axis making it very strange. It all happens so fast, might record the next attempt so i can slow it down if it does it again.

That resolution screenshot looks alot better. I wasnt sure why it was doing that weird bit.

Pluto20109 days ago(+1)

Setup the machine again and recorded it this time.

Think I've found MY mess-up.

The calculator i used on my phone for feed rate doesnt have custom bit sizes. I put in i want 0.1 chipload but just looked and that's for a 3.175mm bit.

Found the calculator i used to use and it should be around 230mmpm not 2000 odd. Whoops!!

Video for fun:

DeftwareDeveloper9 days ago

Hi Pluto,

Ouch! It tried to move so fast that the machine's own inertia kept it from being able to retract - but you can hear it try with that buzz just before rapiding to the next cut. Glad you were able to solve the puzzle :]

- Charlie

itch.io

PixelCNC Has Moved: deftware.org

Z Rapid Height not happening - Snapping bits