|
Post by yusuke620 on Apr 29, 2019 2:35:48 GMT
I bought my M3 2.5 years ago and am just now able to use it again after sitting in a closet for 2 years.
That being said i am learning all over again and having some difficulty.
I designed something very basic in easel and exported the g code file, opened it in UGS platform and when i run it all of the axis go to max and try to keep going until i stop it.
Another problem i have is that the yellow arrow in UGS does not accurately portay where my spindle is, it just sits there as if im nit moving anything around.
i do have control of X, Y and Z manually.
When building the file in easel i set the size of the work piece to 10" square and i run the toolpath in easel and it works fine.
Since i hadn't used this thing in a couple years i did make a mistake this morning and fried the uno, i ordered full new electronics from Millright today but i had another uno laying around and put GRBL on it and got it running after i realized what i did wrong, i plugged the 24v into the uno.
Anyone have any suggestions? A lot of this stuff doesn't make sense to me but im catching up quickly.
|
|
|
Post by Bruce on Apr 29, 2019 3:11:19 GMT
Yep 24V to the Arduino Uno will fry it. Make sure you have your machine set to inches and not millimeters which is the default.
|
|
|
Post by yusuke620 on Apr 29, 2019 14:42:19 GMT
Setting to inches does not fix it.
Do you know why the yellow arrow in UGS is nto accurate to the placement of the spindle?
No matter what file i use the z axis goes to the top and then the y goes all the way forward (front of the machine) and the x goes all the way to the right and all axis bind up until i stop them.
|
|
rowiac
Full Member
Posts: 230
Location: California
Machine: M3
|
Post by rowiac on Apr 29, 2019 15:21:38 GMT
Does your M3 have limit switches? If so, have you tried homing it in UGS using the Home button in the Common Actions window? It might also be labeled $H or you can just type in that command. That will set your machine zero position. From there you can jog the X,Y and Z to the zero position on your workpiece and hit reset zero to set your work coordinate origin. (Hopefully I got the terminology right.)
|
|
|
Post by yusuke620 on Apr 29, 2019 20:35:27 GMT
My machine does have limit switches but they do not work either, this may be due to interference.
When I run verbose and push the switches I don't get the feedback.
When I push the homing button I get an error saying homing is disabled.
|
|
|
Post by joebob296 on Apr 29, 2019 22:19:42 GMT
Can you type $$ into the console and paste the output here.
|
|
|
Post by yusuke620 on Apr 29, 2019 23:26:51 GMT
Here is the ouput.
For my test cut i am trying to cut the mushroom from Easel if you're familiar with that, i have it set 4.5" inside the front left corner of the bed.
When i start the file my z maxes out at the top and then my x and y very quickly move to the back right corner and do nothing but bind up.
Grbl 0.9j ['$' for help]
>>> $$
$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)
$11 = 0.010 (junction deviation, mm)
$12 = 0.002 (arc tolerance, mm)
$13 = 1 (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)
$24 = 25.000 (homing feed, mm/min)
$25 = 500.000 (homing seek, mm/min)
$26 = 250 (homing debounce, msec)
$27 = 1.000 (homing pull-off, mm)
$100 = 250.000 (x, step/mm)
$101 = 250.000 (y, step/mm)
$102 = 250.000 (z, step/mm)
$110 = 500.000 (x max rate, mm/min)
$111 = 500.000 (y max rate, mm/min)
$112 = 500.000 (z max rate, mm/min)
$120 = 10.000 (x accel, mm/sec^2)
$121 = 10.000 (y accel, mm/sec^2)
$122 = 10.000 (z accel, mm/sec^2)
$130 = 200.000 (x max travel, mm)
$131 = 200.000 (y max travel, mm)
$132 = 200.000 (z max travel, mm)
|
|
|
Post by yusuke620 on Apr 30, 2019 0:08:46 GMT
Based on what is going on it seems as though the machine thinks that it is bigger than it is.
When trying to run a file it goes to the back right corner, opposite of where i have home at.
It then tries to keep going, what i noticed is that the yellow arrow is moving but much slower than the x and y are.
I have made multiple files where the work area size is between 6 and 10".
Is there somewhere that i can tell the machine what the maximum size of the work area is? i thought this was done inside of the g code, you design something in the space given and the g code tells the machine to stay within this space, am i thinking about that correctly?
My 3d printer has a setting where yo u tell if the max x, y and z. Can i not do that with this?
EDIT- I let something run and it does all of its movement in the back right corner, this is what it does for everything i try to run.
|
|
|
Post by Bruce on Apr 30, 2019 2:17:56 GMT
You are right, there are a few settings that are off. Check the default settings for the M3
M3 GRBL settings:
$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=0 (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 = 0 (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 yusuke620 on Apr 30, 2019 2:22:09 GMT
I tried these settings earlier and it did all sorts of bad things. X, y and z would only move about 10mm very slowly and my z motor would make a whining noise and got pretty hot. It would only stop when disconnecting the 24v power. I was able to stop it by reverting to the settings I posted. I'll try again tomorrow though. You are right, there are a few settings that are off. Check the default settings for the M3 M3 GRBL settings: $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=0 (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 = 0 (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 Bruce on Apr 30, 2019 2:42:06 GMT
Based on what is going on it seems as though the machine thinks that it is bigger than it is. When trying to run a file it goes to the back right corner, opposite of where i have home at. It then tries to keep going, what i noticed is that the yellow arrow is moving but much slower than the x and y are. I have made multiple files where the work area size is between 6 and 10". Is there somewhere that i can tell the machine what the maximum size of the work area is? i thought this was done inside of the g code, you design something in the space given and the g code tells the machine to stay within this space, am i thinking about that correctly? My 3d printer has a setting where yo u tell if the max x, y and z. Can i not do that with this? EDIT- I let something run and it does all of its movement in the back right corner, this is what it does for everything i try to run. The back right corner is the default homing location. The Steps/mm are very high at: $100 = 250.000 (x, step/mm) $101 = 250.000 (y, step/mm) $102 = 250.000 (z, step/mm) Should be: $100=40.000 (x, step/mm) $101=40.000 (y, step/mm) $102=80.000 (z, step/mm) Check the jumpers on the CNC Shield to make sure you have the right settings. (page 29 of the M3 manual.)
|
|
|
Post by Derek the Admin on Apr 30, 2019 4:16:32 GMT
I agree with Bruce that you should take a look at your jumpers and make sure they are vertical as pictured in the assembly instructions versus horizontal.
|
|
|
Post by yusuke620 on Apr 30, 2019 10:20:00 GMT
Ill make the changes and check the jumpers after work today and get back to you.
|
|
rowiac
Full Member
Posts: 230
Location: California
Machine: M3
|
Post by rowiac on Apr 30, 2019 15:27:08 GMT
It seems weird that your GRBL firmware settings were messed up. Did you by chance connect to the machine with Easel? If so, I believe Easel can rewrite your firmware settings, thinking it is an Xcarve. You should only use Easel to generate gcode, and then connect to your machine and run the gcode using UGS or another dedicated gcode sender app.
|
|
|
Post by yusuke620 on Apr 30, 2019 22:51:41 GMT
It seems weird that your GRBL firmware settings were messed up. Did you by chance connect to the machine with Easel? If so, I believe Easel can rewrite your firmware settings, thinking it is an Xcarve. You should only use Easel to generate gcode, and then connect to your machine and run the gcode using UGS or another dedicated gcode sender app. I did use Easel but i generated the g code. I did not let Easel make any changes.
|
|