OK, never had this issue.. Zero-ing to center (because it's a round item, and helps me keep tool paths aligned) Openbuilds Blackbox, all up to date Fusion360 for model/tool paths Adaptive clearing- everything's fine. Parallel Tool Path- ECK! starts from Zero but dives down and direct to start location.!! No rise- move to start point like others. Not sure if it's something in Fusion or some button I can't find (I looked, I looked a lot!) Does it at the end also!! Isn't there a "Start & End" G-code script or something that should prevent this? Coming from 3D Printing, all the slicers have a start code that is auto attached to all code generated to prevent this kinda thing.,.... What am I missing? Image and parallel's g-code uploaded if that helps Thanks!
There is, but you have to remember to Home the machine so it knows where Machine Coordinates are Step 1) Home machine to set Machine Coordinates (Any time it was off, crashed, or otherwise lost machine coordinate locations) Step 2) Zero (Tells it where the stock is, by setting the Work Coordinates) Step 3) Run jobs (Because Fusion, and other advanced CAMs, move in both Machine Coordinates and Work Coordinates - you need to home and zero both) You can view Machine coordinates by hovering over the DROs
Never had to Home it before,Think I've homed the system like 3 times total, and to make it worse after homing the end stops freak and pull up an error the 1st time you go to move after. and yes, It's backed off 5mm after homing. Also can't home it after a tool change or is screws up the zero location? I "zero-ed" it.. always do- normally it lifts the tool.. moves to start location then drops down into the material.. this time it just buzzed over and down..
Those other times you were lucky that Z was high when you powered down. Now you weren't - get in the Habit of homing to ensure a consistent experience
You do not have to home between tool changes. You just have to rezero the z axis. Another thing I do for a long cut like a 3d carve is I home, then I jog to my zero point. I write down those numbers before zeroing the x and y. That way if you are hours into a long carve and something happens, you know exactly how far to jog to get back to your zero point after homing. Then you can reset the zero point there again
Which specifically, screenshot the error. Grbl had many different alarm and error codes. Depending on which you got, we could offer more insight
just said "grbl err all stop" on the interface thingy.. didn't see any code.. I'll pay more attention if it happens again.
Interface always shows the code. PS: please read gnea/grbl - the errors, configs, homing, etc are all discussed in the Grbl wiki - its a must read to ease your learning curve.
OK, stopped at the exact same point in the cut- "error 33 Invalid Motion Target" what ever the hell that means.. OK, I get it's an arc error, but how to fix? been googling now and the issue comes up, but no one seems to have a fix..?
you have the fix (-: , there is an option in the fusion post for linearizing small arcs.... turn it on and regenerate your gcode. The issue is that fusion automatically calculates some arcs from the bit diameter (entry and exit arcs), and if the bit is small the arcs are even smaller and then fusion generates tiny arcs with slightly different radiusii, different enough for GRBL to flag an error..
"Linearize Small Arcs" in the Post options: You also need to make sure you have the right version, see the Changelog: OpenBuilds/OpenBuilds-Fusion360-Postprocessor (v1.0.23 or later of the post - latest is 1.0.25)
OK, Fusion looks NOTHING like that on my computer- but guessing in the Post Processing - this thing? I'll give it a try.. thanks.
Well, you have a Mac, not Windows? Might be the difference in how they render the dialiog. That is it though...
OK, ticked it on.. running it without spindle or vac on,.. cuz.. NOISE!! LOL. (yes, I took the bit out) stupid question..... shouldn't it be on by default? anything else you guys see off hand in that list I should have on/off/change for default settings?
Makes you wonder whether Fusion is worth bothering with sometimes, For a home shop CNC, Sketchup does it all for me and machining problems are a rarity.
Oh god no... I had WAY more issues doing simple modeling with Sketchup, and the files that came out of it were horrible and near impossible to fix , that was for 3d Printing. went to Fusion and haven't looked at Sketchup since it changed hands the last time... it doesn't even do machining as far as I know. ..?
You struggled with Sketchup? Oh well No, Sketchup is just for CAD - you can then choose whatever CAM program you like, to do the toolpathing.
I switched from sketch up to Fusion as well. Fusion is way easier and more intuitive in my opinion (and probably the OP's). I would not say I "struggled" with it, it was just clunky (IMO). That being said, I have not used the CAM portion of Fusion for years. I started using Estlcam before OpenBuilds put out Control and CAM. I found it to be the fastest and easiest way for me to make parts and generate tool paths . For 2.5D stuff, I don't even need to waste my modeling in 3D. I just draw the part up as a .dxf.
I, well, beg to differ.... swarfer/sketchucam https://www.youtube.com/playlist?list=PLm728rLHCWOw-vRvTJwS_5MmKG1fs4sZ0
You don't have to do that, the offsets are stored in EEPROM when you set them, and will survive a power cycle. I have often stopped a job between files, turn off, gone to sleep, wake up, turn on, run next file (maybe a bit change and Z re-zero) without losing the part zero. This is the point of a stable home, GRBL stores the offsets in non-volatile memory, so that homing is an instant fix for a crash or power out. My machine doe snot have limit switches, I have always used the 'fake the home' method.
I do (well trying to do, lol ) “true 3d” not just 2.5 CNC which is why i started with Fusion. That and been using it for yrs in 3D Printing. I used Sketchup for yrs as well as Solidworks back in the day. If i were to go back to architecture again, id probably use Sketchip for it, but it didnt handle round faces and chamfers correctly, pretty much anything beyond simple block building it struggled with.
