New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing Gcode #10
Comments
Checking! |
Okay, commented out a thing I added recently: 870cd96 Each entity is a list of vertices in an array. I want to add Ramp plunges (urgently need that man (: ) so the logic here was to find the longest segment in the array, and circularly rotate the array, so we start at the longest segment (enough space to do a ramp) - but it seems to break and drop a segment - will fix it later, but for now, removed that (: |
in SketchUcam the ramp code does this: the bit-diam/2 is a 'this generally works' but it does depend on specific bit geometry. it is based on the geometry of my collection of 2 flute carbide router bits (-: it will not work on a large diameter shell mill where your ramp length will need to be > bit_diam. I did not make this 'yet another option' because there are already too many options for most people to absorb. |
1 - optimiser: we don't have one (yet) - but on the todo Doing a slightly different style of ramp (I guess born from personal preference) - we (although its temporarily disabled now) resort the vectices to place the longest vertex first (helps with the automated Tabs and with plunges) - then inside the first segment, i do a back and forth plunge like this - (to half the depth, and then back down to full depth) - this was born from trial and error - works really well with plain old wood cutting router bits (builders warehouse style for R60ish) I have two things to do here:
|
that looks good. I need to work on the ramp length in SketchUcam, at the moment it uses the whole segment but it should be limited to a multiple of the tool diameter AND the given angle limit and then cut the rest of the segment at the set depth. |
…irst point logic needed fixing
Fixed the bug with the rotation. Was pretty simple once i looked at it. Say we have this geometry to draw a box:
After a circular rotation it became, for example
The 0,0 is the problem now, as we can't go back to where the vertice started, and instead have two points with same geometry in the middle. Lol. So fix was easy, splice off the last coordinate (as i know our cam ALWAYS has last=first) Now yea yea I know, someday i'll need to support open vectors too. but for now (: I dont have to. |
Hi again
I loaded the 'Hello World' example and created Gcode but the Gcode is missing some edges, particularly across the top of the "HELLO" word.
I then regenerated the code with different bits sizes, and also scaled the entire thing to 75mm wide (to fit my bit of foam for an actual test cut) and redid all the cut paths and still got the same missing edges.
Right now I have just opened the cam site (Firefox) and loaded the default Gcode in CAMotics and it shows the missing edges....
the outside cut on WORLD fairs better but is missing the vertical part of the internal cut on the R
The text was updated successfully, but these errors were encountered: