It might be helpful if you explained what went wrong with your machine earlier when you first posted about this problem. You "forced" your y-axis to home? What was the initial problem that caused you to "force" anything? What did you do to try to fix it? I'm think you may have fried something, because Grbl's settings should not be randomly resetting itself. Also, make sure you are using the most recent release, Grbl v1.1f
Cool, thanks. Now I have to figure out how to compile the source... Is there a way to dump or extract the settings on an existing install to a new default.h file (or other file)? MG
Hi Sonny, Forced is maybe not the right word, I only gave the machine the grbl command. That had been the same issue....grbl lost my inputs and showed some kind of standard settings, not the ones, I programmed to fit my machine. By the way...is there a grbl command to lock the stepper motors? The ox seems to be very wobbly, when powered up. I could easily move the axis by hand, I think that is not very beneficial, when it comes to accuracy.
Yes. It's in the Wiki page that explains the configuration of Grbl. Setting $1=255 will keep the steppers enabled.
By the way...Sonny, you mentioned the cnc x pro could be accidently been fried? What could be reasons for that? I can't imagine to do something unusual at the assembly or first runs.
I built the c-beam machine from the kit and marks video on youtube. Im now at the point where i need to setup grbl and mark keeps referencing "software" folder in the viideo and an image with the grbl settings but I never got any of that in the pack. Can you point me in the right direction? Martin
Martin: Go to the Openbuilds "Builds" page, and select "CNC Router builds" at the top. Scroll down until you find the C-Beam Machine router build. Go to the "Files" section, and download the C-Beam software zip file. This should have everything you need. Note that the versions of software here are quite old, you should go to GitHub and get the latest versions of GRBL, GRBL Panel, etc. MG
Now that I've finish my testing with my 'Uno' to get my Ox up and running, which all went okay apart from a few hiccups on my part, I thought I'd like to use my 'Uno' for another project when it comes up as I've now got a dedicated board running GRBL. So I plugged in my board which had 'GRBL' on, found the com port it was on, started up the IDE, set the relevant port and tried to upload 'blink' to clear 'GRBL' off, and things didn't happen as they should have, no flashing lights on TX/RX, tried a couple of times no joy. I then thought lets check on UGS to see if it connects, sure enough it connected and was still able to check settings and everything, now when I checked on the 'GRBL' wiki it said this wouldn't happen. So what gives, do I need to get the boot-loader burnt back on again from a good Arduino or not.
make sure there is nothing connected to the Uno that might prevent it resettting when the IDE tries to program it. or, press the reset button just after you press 'upload'.
Hey, anybody have problems installing the FTDI chip drivers in Windows 8? I have a client that can't seem to get the Arduino Nano talking to Win8. We've installed the FTDI chip drivers, tried installing the Arduino IDE, nothing seems to work. Win8 recognizes the chip is there, but wont talk to it and won't assign a COM port... MG
Bit of a 'brain fart' moment again, I also had problems connecting my 3D printer as well and it wasn't until this morning when I was having my morning smoke that I realised it could be the hub I've got, sure enough not long ago uploaded 'blink' and its merrily flashing away like a mad thing. Needless to say I've now got an 'arduino boot-loader chip' on it's way to me at this moment, that'll be waiting for a project when the time arises. Ho hum. So the moral of the story, when something is cheap it doesn't mean its gonna be good.
Pulling my hair out at the moment, can someone here save me from death by alcohol?. My Ox is built, has taken 6 weeks on and off, I found the mechanical build ok with not too many slip ups due to Marks excellent video. I have limit switches installed with Hard limits and Homing set on 1. The machine homes lovely with no bashing into side rails etc, it homes nicely to X,Y and Z in the positive position. I also have the Max travels set up slghtly smaller than I need to just to be safe. My problem arrives when I zero on a work piece which I put in the middle of the table, I reset the work area to zero and then I home it then I send the gcode at it, the ox fires up then will try and do its business nowhere near the zero location even though I know that this is roughly where it is meant to start its cut, then it will hit the limit switch and disable. Obviously I am air cutting atm but I have spent nearly 2 weeks playing with Universal gcode sender and I cannot figure it out what the issue is. I have looked on this forum for answers time and time again taking the advice of anything that relates to my problem but with no luck. The gcode I am sending it only represents a small area (aproximately 110mm x 250 mm safe area) done in Sketchucam, but the ox acts as if it is handling something much larger. I have checked my wiring again and again but everything runs in the correct direction so it is not that. I have played with the gcode and used different settings, defaulted the values and starting over again and again. It is driving me crazy as I am desperate to cut and produce but I am thwarted. Any good samaritan out there have the answers?
Hi. I am seeking a little help from the group around the commissioning of my recently completed c beam xl I am looking for support in the grbl settings ( they are a mystery to me!) for this build Also the setting of the microswitches and the whole area of homing. Any help would be really appreciated P
When you reset zero, does UGS show you are at zero? Also, does UGS send a G92 or a G10 web seeing zero?
Hmmm, but it goes back to home switches when you send it to your new zero? Maybe you're mixing work coordinate systems?
Sorry, I may be confusing you, it will home to the correct position and it will return to zero wherever I set it, but once I have set Zero (where my workpiece is), when I run the Grbl file it starts its cut elsewhere no where near and gets stopped by hard limits otherwise it would be crashing into the side rails. The size coordinates of the file I'm sending are only small so there is no need for it to be going outa bounds.
http://www.openbuilds.com/members/saint-billy.60317/ Have you run your g-code through Camotics or some other simulator to see if your g-code origin is where you think it is? If you are homing at y+ max and x+ max, your origin on your g-code needs to be in the upper right corner of your code, All of your X and Y moves will be negative. Most g-code has its default origin in the lower left corner, and all moves are positive. Also, open up your g-code file in a text editor and manually look at the G1 X,Y co-ordinates and see if they look reasonable.
I have just looked at gcode parameters and it is showing (G54:-6.000,--6.000,-1.000), is this correct as all the other G commands are 0.?
G54 should be all zeros as well. Are you working in inches? Have you checked to make sure your g-code is in inches as well? And your UGS is set up for inches?
Hi, I am working in metric. to be fair I mainly use the basic Universal Gcode sender which is in Metric but I didnt realise Ugs was in inches. is the G54 values messing me up? if so how do I return these to zeros. cheers
The G54 values show your work coordinate offsets. They should not be zero if you changed your work zero. Can you share your Gcode?
Thanks for the time guys, appreciated! This is the gcode I am sending: % (Generated by SketchUcam V1.4d-80c0152) (File: cncdustcollector.skp) (Bit diameter: 8.000mm) (Feed rate: 8.000mm/min) (Plunge Feed rate: 80.000mm/min) (Material Thickness: 15.000mm) (Material length: 250.000mm X width: 110.000mm) (Overhead Gantry: true) (Plunge Depth first) (Optimization is ON) (www.PhlatBoyz.com) (Loaded profile DustCollectorTestCut) G90 G21 G49 G17 F80 M3 S5000 G00 Z10.000 X38.123 Y33.654 G00 Z0.500 G01 Z-15.300 F80 X34.405 Y38.500 F7 X32.067 Y44.144 X31.270 Y50.200 Z-7.500 X31.466 Y51.687 Z-15.300 F80 X32.067 Y56.256 F7 X34.405 Y61.899 X38.123 Y66.745 X42.969 Y70.464 X48.613 Y72.801 X54.669 Y73.598 X60.725 Y72.801 X66.368 Y70.464 X71.214 Y66.745 X74.933 Y61.899 X77.270 Y56.256 X77.872 Y51.687 Z-7.500 X78.068 Y50.200 Z-15.300 F80 X77.270 Y44.144 F7 X74.933 Y38.500 X71.214 Y33.654 X66.368 Y29.936 X60.725 Y27.598 X54.669 Y26.801 X48.613 Y27.598 X42.969 Y29.936 X38.123 Y33.654 G00 Z10.000 X24.617 Y11.006 G00 Z0.500 G01 Z-15.300 F80 X68.175 F7 Z-7.500 X71.175 Z-15.300 F80 X84.721 F7 X87.487 Y11.187 X90.257 Y11.738 X92.931 Y12.646 X95.464 Y13.895 X97.813 Y15.464 X99.936 Y17.326 X101.798 Y19.450 X103.367 Y21.798 X104.616 Y24.331 X105.524 Y27.005 X106.075 Y29.775 X106.256 Y32.541 Y54.667 Z-7.500 Y57.667 Z-15.300 F80 Y191.307 F7 Z-7.500 Y194.307 Z-15.300 F80 Y210.593 F7 Y214.595 X106.079 Y216.285 X105.332 Y219.142 X104.163 Y221.854 X102.598 Y224.358 X100.674 Y226.598 X98.434 Y228.522 X95.929 Y230.087 X93.218 Y231.256 X90.361 Y232.004 X87.424 Y232.312 X84.632 Y232.181 X65.256 Y244.181 X56.081 Y215.889 X60.811 Y215.561 X68.440 Y212.940 X75.129 Y208.433 X80.425 Y202.348 X83.965 Y195.101 Z-7.500 X84.252 Y193.628 Z-15.300 F80 X85.509 Y187.184 F7 X84.951 Y179.137 X82.329 Y171.508 X77.823 Y164.819 X71.738 Y159.523 X64.490 Y155.983 X56.573 Y154.439 X48.526 Y154.997 X40.898 Y157.619 X34.208 Y162.125 X28.913 Y168.210 X25.373 Y175.458 X23.829 Y183.375 X24.283 Y189.925 Z-7.500 X24.387 Y191.422 Z-15.300 F80 X27.008 Y199.050 F7 X31.515 Y205.740 X37.600 Y211.035 X44.847 Y214.575 X53.256 Y216.215 Y244.181 X44.081 Y232.181 X36.669 Z-7.500 X33.669 Z-15.300 F80 X24.720 F7 X21.925 Y232.362 X18.962 Y232.095 X16.075 Y231.374 X13.334 Y230.218 X10.803 Y228.654 X8.543 Y226.719 X6.608 Y224.459 X5.044 Y221.928 X3.888 Y219.187 X3.168 Y216.300 X3.081 Y215.343 Y210.593 Y191.256 Z-7.500 Y188.256 Z-15.300 F80 Y52.233 F7 Z-7.500 Y49.233 Z-15.300 F80 Y32.541 F7 X3.263 Y29.775 X3.814 Y27.005 X4.721 Y24.331 X5.971 Y21.798 X7.540 Y19.450 X9.402 Y17.326 X11.525 Y15.464 X13.873 Y13.895 X16.406 Y12.646 X19.081 Y11.738 X21.851 Y11.187 X24.617 Y11.006 G00 Z10.000 (EndPosition) X0.000 Y0.000 Z15.000 M05 M30 %
Yes, that g-code is in metric. If your machine or UGS is set to inches, as it looks like with the G54 values you sent, it will try to go to (the first instruction) X34.405 Y38.500 inches, which will be way off your table. Also, these g-code moves are all positive, which will not work if your Home position is in the upper right corner. All moves should be negative if this is the case. By the way, if you are running in metric, a feed speed of F7, or even F80, is glacially slow. it should be more like F500-F1500, depending on material, bit speed, etc. SketchUCam defaults to the very low speeds, you need to crank it up. Did you download Camotics and preview your code? This is an absolutely necessary step. I never found a need to use G54, I set it to 0. I use GRBL Panel, and there is a zero button right beside G54 to clear it. I always set my work zero and machine zero by disconnecting and reconnecting after positioning the machine to my g-code origin using GRBL panel. This sets everything including machine position to 0 at the origin of my g-code, and I never have problems. I don't understand why GRBL insists on homing to the upper right and having all moves into negative space in quadrant 3. This makes no sense to me, despite the explanation of why Chamnit does this on the GRBL WIKI. Almost all g-code generating software defaults to the origin in the lower left hand corner, with all moves positive in quadrant 1, which makes a whole lot more sense to me. MG
