|
Post by brianarnold on Oct 13, 2019 20:55:10 GMT
Can this also deal with the z axis. whe i move 1 mm i am actuall moving close to 3mm
|
|
|
Post by Bruce on Oct 13, 2019 21:37:23 GMT
Hi Brian, You should check the settings for the machine by going to the Universal G-code Sender and look in the Machine|Firmware settings or go to the console and type $$ <enter> This will display the GRBL machine settings. Copy the list here. Tell us which machine you have also?
You can also check the jumper settings on the CNC Shield. The Z axis may be set wrong.
|
|
|
Post by brianarnold on Oct 14, 2019 1:17:20 GMT
$0 = 10 (Step pulse time, microseconds) $1 = 255 (Step idle delay, milliseconds) $2 = 0 (Step pulse invert, mask) $3 = 0 (Step direction invert, mask) $4 = 0 (Invert step enable pin, boolean) $5 = 0 (Invert limit pins, boolean) $6 = 0 (Invert probe pin, boolean) $10 = 1 (Status report options, mask) $11 = 0.010 (Junction deviation, millimeters) $12 = 0.002 (Arc tolerance, millimeters) $13 = 0 (Report in inches, boolean) $20 = 0 (Soft limits enable, boolean) $21 = 0 (Hard limits enable, boolean) $22 = 1 (Homing cycle enable, boolean) $23 = 0 (Homing direction invert, mask) $24 = 25.000 (Homing locate feed rate, mm/min) $25 = 1000.000 (Homing search seek rate, mm/min) $26 = 44 (Homing switch debounce delay, milliseconds) $27 = 4.000 (Homing switch pull-off distance, millimeters) $30 = 1 (Maximum spindle speed, RPM) $31 = 0 (Minimum spindle speed, RPM) $32 = 0 (Laser-mode enable, boolean) $100 = 40.000 (X-axis travel resolution, step/mm) $101 = 40.000 (Y-axis travel resolution, step/mm) $102 = 45.000 (Z-axis travel resolution, step/mm) $110 = 8000.000 (X-axis maximum rate, mm/min) $111 = 8000.000 (Y-axis maximum rate, mm/min) $112 = 3000.000 (Z-axis maximum rate, mm/min) $120 = 250.000 (X-axis acceleration, mm/sec^2) $121 = 250.000 (Y-axis acceleration, mm/sec^2) $122 = 250.000 (Z-axis acceleration, mm/sec^2) $130 = 250.000 (X-axis maximum travel, millimeters) $131 = 250.000 (Y-axis maximum travel, millimeters) $132 = 69.000 (Z-axis maximum travel, millimeters)
I have a M3
I did change $102 to 45 i did not write down the default valut....i know that was stupid. always create a back up
|
|
|
Post by brianarnold on Oct 14, 2019 1:27:58 GMT
and i did double check i had the m0 and m1 jumpers in the correct place
|
|
|
Post by Bruce on Oct 14, 2019 15:38:10 GMT
Yeah, looks like Z axis setting is off, should be $102=80.000 (z, step/mm) rather than 45. There are a couple other settings that should be adjusted too. Make these changes and you should be good to go.
M3: Initial Setup parameters $0=10 (step pulse, usec) $1=255 (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) $11=0.010 (junction deviation, mm) $12=0.002 (arc tolerance, mm) $13=0 (report inches, bool) $20=0 (soft limits, bool) $21=0 (hard limits, bool) $22=1 (homing cycle, bool) $23=0 (homing dir invert mask:00000000) $24=25.000 (homing feed, mm/min) $25=600.000 (homing seek, mm/min) $26=244 (homing debounce, msec) $27=4.000 (homing pull-off, mm) $30 = 12000 (Maximum spindle speed, RPM) $31 = 0 (Minimum spindle speed, RPM) $32 = 1 (Laser-mode enable, boolean) $100=40.000 (x, step/mm) $101=40.000 (y, step/mm) $102=80.000 (z, step/mm) $110=8000.000 (x max rate, mm/min) $111=8000.000 (y max rate, mm/min) $112=3000.000 (z max rate, mm/min) $120=250.000 (x accel, mm/sec^2) $121=250.000 (y accel, mm/sec^2) $122=250.000 (z accel, mm/sec^2)
$130=264.000 (x max travel, mm) $131=264.000 (y max travel, mm) $132=69.000 (z max travel, mm)
|
|
|
Post by Derek the Admin on Oct 16, 2019 13:30:12 GMT
You can also return to defaults by typing $RST=* in the command line.
|
|
|
Post by Bruce on Oct 26, 2019 3:21:39 GMT
You can also return to defaults by typing $RST=* in the command line. Well that's a new one on me. Now that I look it up... $RST=$ : Erases and restores the $$ Grbl settings back to defaults. $RST=# : Erases and zeros all G54-G59 work coordinate offsets and G28/30 positions stored in EEPROM. ($# parameters) $RST=* : This clears and restores all of the EEPROM data used by Grbl. This includes $$ settings, $# parameters, $N startup lines, and $I build info string. That's why I hang around here, learn something new everyday.
|
|
k
New Member
Posts: 8
|
Post by k on Feb 22, 2020 2:03:16 GMT
Hello!
I have the Mega V 19x19. Great and speedy machine. I'm really enjoying learning how to use this beast.
I just ran the 100mm x 100mm square calibration file that I've created in Fusion360. I measured the Height and Width. The width is 98.3mm and followed the .xls provided by Derek. It calculated that I should use $100=40.68. Would this work for my Mega V?
I went into my UGS Firmware setting, the current setting are: $100=57.288 $101=57.288
Appreciate the help and thank you. -K
|
|
|
Post by Bruce on Feb 22, 2020 5:22:22 GMT
Make sure to enter the Mega V steps/mm in the spreadsheet.
Example: X Expected Distance 100.00
X Actual Distance 98.30
Programmed X steps/mm 57.29
X Percent Error -1.70%
Corrected X steps/mm 58.262 Type in $100=58.262 in the command line to set this
|
|
k
New Member
Posts: 8
|
Post by k on Feb 22, 2020 22:41:54 GMT
Make sure to enter the Mega V steps/mm in the spreadsheet. Example: X Expected Distance 100.00 X Actual Distance 98.30 Programmed X steps/mm 57.29 X Percent Error -1.70% Corrected X steps/mm 58.262 Type in $100=58.262 in the command line to set this Thank you Bruce! Your explanation is great!
|
|
|
Post by btreichel on Mar 7, 2020 2:49:07 GMT
Well, I didn't use any of the tools for this. Just no need. I cmd'ed a 700mm jog, and engraved a 700 mm line. Told it 28"'s, same story.same for x & z. it's perfectly dialed in. FYI, I used 700 mm, because the longer the move, the bigger error to be seen.
|
|
|
Post by Derek the Admin on Mar 9, 2020 2:35:01 GMT
Can't beat perfect!
Cheers
|
|
|
Post by paul061513 on Apr 19, 2020 14:27:54 GMT
HELP!!! I have the Mega V 35x35 OK, so I'm not sure this is where I need to ask this or not. I am a complete novice at this and have been viewing tutorial after tutorial. I have my machine built and after days of not being able to get V-Carve to mesh with g-sender or whatever it's called, I found that i actually have V-Transfer to talk to the machine. I connected and am able to jog the machine, send the unit to home position and back. I started out like a goober, using standard units of measure and couldn't figure out why it was making a 5.5"x10" carving to fit on a pencil eraser, 3" above the surface. Once i found that V-transfer was in metric, i converted everything over and re-ran...same thing. I started a new file in metric, and was able to get the machine to show carving the correct size, now if i could just get it to carve on the wood and not 3" above the wood, I'd be happy. My brother came over and helped me adjust a couple things, I was then able to make a pocket cut. It started lettering, made it through 6 letters and froze. I shut everything down and unplugged so it would reset. When i started back up, i reset all my zeros and without a bit in place pushed cut; it appeared to work perfectly, so i restarted once the first pass was complete with the bit in place. The machine bottomed out in the board at 0,0 and shot left, snapping my bit and stopping outside the work area and plunged back into the board and sat there. I had not been using the homing plate, and thought this may be the reason for my troubles on getting this to work correctly. I set the homing plate on my project (now just scrap, but still usable) and reset my zeros. I ran a dry run, everything looked good. When I installed the bit, it went outside the work area again, dropped down and ran an angle cut up and across the work area and stooped at the other end and sat there. Attachments:
|
|
|
Post by btreichel on Apr 20, 2020 4:23:07 GMT
Use vcarve and save the file to the grbl selection at file save time. Don't try to run directly. When you go to run, have UGS load and run that file. But first, use UGS to home / job the machine around.
|
|
|
Post by paul061513 on Apr 21, 2020 17:24:42 GMT
Use vcarve and save the file to the grbl selection at file save time. Don't try to run directly. When you go to run, have UGS load and run that file. But first, use UGS to home / job the machine around. I did this, and it still runs through at about an inch above the material. Cant get a photo from the mobile to show you, but it’s doing just like v-transfer.
|
|