Hey guys,
Just updated to CC version 460, when I went to send gcode it asked me what post processor to use? Can someone explain the differences between them?
Basic g-code -
grbl -
Nomad 3d -
Shapeoko 3d -
I chose the Shapeoko 3d, just because I didn’t know any of these and it had the word Shapeoko in it.
I ran a project and it worked ok, but did notice 2 things right off the bat.
After zeroing and loading file, then click run usually the spindle would only retract to my set height, this time it went all the way up -which I really don’t mind because the other way I would have to start run and then hit pause where it would then raise up high enough for me to slide the suckit dust boot on.
A lot of times I need to re-set Z on a different area, after setting it and then hit run it would go to the original spot of the initial x,y, which in one case I found out the hard way if you don’t have your retract set high enough -(in this case I was resetting zero on a lower pocketed area) it then scraped across the already done area - (Oh no! ) it wasn’t too bad and I was able to sand it out. Well this time it just stayed and started from the new Z coordinate.
Are these supposed to do this in the new version, or have I picked the wrong processor? But I like these features.
I think I probably was supposed to pick the basic? If I do, will it still have these features as well. I don’t do any 3d----YET.
The Nomad and Shapoko posts will now retract the cutter up to the top of travel before moving to the first plunge. This should be safer since it’s a little less likely to hit any workholding on the table this way.
Basic and GRBL work the old way because they do not assume that users will have homing switches. Basic and GRBL are generally identical at this point except that comments are truncated in the GRBL version to make sure that no serial buffers overflow when sending a line down using a third-party gcode sender.
Bottom line, if you have a Shapeoko, pick the Shapeoko post unless you don’t have homing switches (very unlikely at this point).
Thanks Rob!
There is still a bug in this version as well in the previous ones. Once in a while when trying to move an object it will disappear and be put usually down in the left hand corner,or sometimes way off the screen. Can’t seem to get it to do it all the time, but I think it is either on how the mouse button is pushed or when you zoom in at a certain distance to move object. Just a little frustrating. This is just highlighting the object and then trying to move, not using the move feature. There were a few more I have been dealing with, but have not used this version long enough to see if they are still there.
Once in awhile when resizing and then trying to move the screen it will stick to the object and you have to un-select it and re-select it to resize.
Another one that was very annoying is a ghost image, when you delete a tool path and go back into design, the image of the tool path is still there in grey.
I was also getting quite a few shut downs after trying to open a new file after closing another file.
Like I said these were in the past version,(433) not sure if you had encountered and fixed any of these. Just started using this one yesterday, so not sure if any of the other ones are still there besides the disappearing object one.
If you can provide a file which has repeatable behavior in a current version and step-by-step instructions for eliciting it, please send that in to us at support@carbide3d.com
draw a circle somewhere int he middle of the surface
select it
ctrl-c to copy
try to move the copy, not by dragging a “snap point” on it, but by dragging an inbetween part of the arc
Just a heads up — also the one that I can get to do just about all the time is when you want to resize an object,while it is highlighted and you try to move the screen it sticks, and you have to click off the object and then re click on it again to resize.
Another bug (or something that should be changed) – when in node mode you cant move around without having to go thru the process again, it should just stay in that mode until you click the node button again.
On another note , I did find out that now you can (if running multiple jobs or having to correct something) you don’t have to re-zero or go to the re-zero spot, just hit run job and now it will go and start ,but keeping z up until it gets there, before Z would start to lower before it even got there -pretty dangerous.
it seems less frequent with 461 but I managed to repro it and capture it (I’m not normally doing video capture, had a few false starts)
the glitch happens round 15 seconds in; I did not cut the video down (sorry) in case previous steps matter for the reproduction … 15 seconds shouldn’t be too bad
(btw it “feels” that snap-to-grid is an element to have enabled, but that is not hard data yet)
Was working on a project yesterday and it was happening periodically, not sure what triggers it, very random, most of the time it throws it down to left corner but other times it would throw it way off the screen in upper right corner, had to zoom way out to find it. Were you able to look at the sticking problem when trying to re-size as well? That happens all the time.
just to clarify, what you are seeing, does that match the video I posted above?
(to make sure we’re talking about the same thing and not two separate things)
Yes it is except usually it disappears farther, I suppose that has to do with how far away from the corner you are when trying to move it. I just tried a simple circle and could not get it to do it. Last night it was doing it with letters and whole words.
do you happen to have a design that’s 25 grid elements wide or high?
(kind of wondering if there is a mm/inch mixup somewhere in the snap-to-grid code)
I’ll take a look later when I go out to the shop,I only check this in the morning so that’s why it takes me so long to respond - no internet in the shop.
Did not have any designs that fit that - I tried again on a previous design with just drawing a circle and drew it on the right side and tried and tried all different things and could not get it to do it, then I put the circle on the left side and disabled snap to grid and got it to move over to the right side where I drew it at first, but it only did it a few times and could not get it to do it consecutively. No rhyme, no reason?