Hi, I recently bought an OX CNC KIT and I tried to get it work. My issue with the machine is that when I do a toolpath it doesn't seem that GRBL (2.0) accepts it wright or maybe I doing it wrong. The feed rates and the plunge rates seem to hige when the job starts. I do the toolpaths in the Vetric Aspire software and the setting for the end mill are set quite conservative at feed rate being 10mm/min and plunge rate also at 10mm/min. The toolpath are postprocessed as the GRBL G-CODE or X-CARVE G-CODE the problem is the same. In the GRBL there are some settings about XY step, feed rate and Z feed rate, Which setting do control the movement of the machine? Are the GRBL settings only for Jogging the machine? The material is MDF and the end mill is D=6mm. The cut depth is also set to no more than 3mm. Can anyone please suggest or has any experience on how to set it wright. Thanks. MotGor
Need more info, are you using UGS? do a $$ command and post here what you see for your settings that's the first place to start and yes this needs to be set correctly for your machine. we need to know your setup. what belt are you using (GT3?) how many teeth your pulleys are(20?), micro step settings on the drivers you are using, are you using the TR8*8 screw for Z? All the settings are described in the GRBL wiki page.... I don't think GRBL goes to 2.0?
10mm/min is TOO SLOW for GRBL, it just cannot reliably pulse that slow 0.9i - Min feedrate appears to be around 40-45mm/min · Issue #742 · grbl/grbl · GitHub that is also way too slow to cut properly in wood, you want more like 1000 to 4000mm/min, the cutter must make chips not dust. 3 to 5 thou per tooth. Use one of the many online feedrate calculators! Materials - ShapeOko the settings in GRBL set the homing feed rate, and maximum travel rates, the cutting feedrate is always set by the Gcode. (unless you are still running GRBL v0.8, which is many versions too old, upgrade to v1.1 as soon as you can!)
Hi, Thanks for the help fom both of you. In the picture you can see the parameters in USG. Sorry the version 2.0 I ment it for USG not GRBL. I will tray something like you sugested. I have a GT3 belts I thin that the pulleys have 20 teeth. Hope that helps. Regards, MotGor
MotGor, Looks like you set GRBL up fine, I can't see the acceleration but everything else should be ok. Make sure your drivers are set for 1/8 step, to match the steps per mm listed. The issue is probably what David said about the slow feed-rate. Gary
Hi, It's seem that I can't get it to work right. Now when I try to send the G-code trough USG the CNC start and soon (about 4seconds) stops at an point on the material and it doesn't move anymore. It goes from running to Idle. The settings are the same as in the previous post that I posted the screen shoot but now in this screen shoot it states an Error .... What I'm doing wrong? Is there any option to reset the whole thing (CNC xPro) or is this not a goog idea? I realy not know what to do any moore.
what are you using to make you G-code (and the drawing)? try uploading the file here and we can look at it, you might have an incompatible command or something. As for the microstep, the cnc xPro has jumper settings for x8 its "1-1-0" see the pic
Hi, to make the G-code I'm using Vetric Aspire. I tried to save it in grbl(G-code) and also X-Carve (G-code) but it's no difference the CNC stil stops after a few lines of G-code and as I said goes from run to idle. The files are attached.
Hi, I once again tried to run the CNC. I sent the G-code trougout the USG and once again the machine stoped in the middle of the jobe (you can see on the USG screen shoot) with the lights lit on the xPro board as you can see on the picture. Please can anyone help me to solve this issue. I'm allready desperate. Sorry for my english! Thanks!
I ran the Celtic file no problem even engraved some MDF. so it's not the gcode. I do not have a CNC xPro, I use Arduino Uno and UGS platform. Sorry maybe somebody with xPro experience can help from here.
What Uno do you have? is it a genuine Arduino or is it a cheap copy ? you can tell them apart, the genuine has a Atmel 16u2 chip next to the USB socket, the cheap copies have a CH340 chip there. The CH340 is the problem, if you have one. They simply die when you send a lot of data through the USB port. The only fix s to get a real UNO with a 16u2 chip. (and even that might need a software update if it is very old) I have some of these at home and the USB dies even when I am not using them for GRBL, often just during programming from the Arduino IDE. They really are not worth the money saved.
