We use cookies to personalize content, interact with our analytics companies, advertising networks and cooperatives, and demographic companies, provide social media features, and to analyze our traffic. Our social media, advertising and analytics partners may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. Learn more.
I am currently able to step my new XCarve with universal gcode sender and GRBL running on an arduino. My issue is that for a 10mm command, the XCarve moves about 30mm (Which I would like to fix via ugs), and ugs only displays these settings on $$ (Absent are x,y, or z steps/mm):
$0=10 (step pulse, usec)
$1=25 (step idle delay, msec)
$2=0 (step port invert mask:00000000)
$3=0 (dir port invert mask:00000000)
$4=0 (step enable invert, bool)
$5=0 (limit pins invert, bool)
$6=0 (probe pin invert, bool)
$10=3 (status report mask:00000011)
$13=0 (report inches, bool)
$20=0 (soft limits, bool)
$21=0 (hard limits, bool)
$22=0 (homing cycle, bool)
$23=0 (homing dir invert mask:00000000)
$26=250 (homing debounce, msec)
Try changing your G91 (incremental) to a G90 (Absolute) and adding a decimal to the end of the 10. See if that helps. If not, then it’s probably a hardware adjustment…
I had something like that on one of the boards I got from another vendor. For me it was something in the version of GRBL on the board. I ended up reflashing the board with the Inventables GRBL fork, and it fixed things right up.
@BradT, I took your advice and used the inventables fork, and @LarryM it now says that I am on GRBL version 1.0c, and I still have the list of limited commands. @cncrockstar I have no idea where the rest of the $$ readout went haha.
I should probably mention that I’m using third party stepper controllers (TB6560s) with 1/16 microstepping, and now the machine is moving about 5mm for a 10mm command, which would be fixed by setting the default 1/8 microstepping to 1/16 microstepping in GRBL, however the problem seems to be that none of my changes (I’m changing the c code in the background and re-uploading to the arduino) seem to be taking effect. This is probably related to how I’m not seeing those setting on the $$ readout in ugs.
There is something wrong with the firmware you are using. This is what you should see if you have a 500mm X-Carve. If you have the 1000mm the only difference would be $130 and $131.
Unless you have a specific reason for doing so you do not need to change the source code. You may have messed something up in there.
Could it be an issue with the EEPROM on my Arduino?
Here: Frequently Asked Questions · grbl/grbl Wiki · GitHub it says that the GRBL settings list is stored in the EEPROM, that sometimes settings and parameters are funky after flashing GRBL, and that the EEPROM reset could be the fix for that; I’ll try it later tonight when I get home.
