Disconnect the connector to the gShield where the homing/limit switches are connected and try your test again.
If it still fails, disconnect the gShield from the Arduino and do your test again.
Tried the first option but it does nothing. I will try the second option tomorrow but whats the logic?
By disconnecting the switches it isolates the problem to the Arduino/gShield. Since you still have the problem then there is a problem with the gShield or the Arduino. You still may have a problem with the switches, but now you know you have a problem with either the Arduino or the gShield or both.
If you remove the gShield and you still have the problem then the Arduino is at fault, if the problem goes away then it is the gshield that is at fault.
If the Arduino fails without the gShield connected, try reloading grbl into the Arduino and see if that fixes the problem (donât hook the gShield back up until you get the Arduino working correctly by itself).
Thanks for the explanation. I will try that tomorrow and post the results here.
Seems like Arduino is at fault. I disconnected the power and USB, then disconnected the gShield and reconnected Aurduino thru USB and send the ? command. Here is the output, the PIN still shows as 010. Alarm,MPos:0.000,0.000,0.000,WPos:-18.000,-59.000,0.000,Buf:0,RX:1,Pin:010|0|0000
Now as you suggest I will reload Arduino with grbl and see how it goes.
After reloading the grbl the ? output is this.
Alarm|MPos:0.000,0.000,0.000|Bf:15,127|FS:0,0|Pn:Y|WCO:18.000,59.000,0.000
and $$ returns this.
$0=10
$1=97
$2=0
$3=35
$4=0
$5=0
$6=0
$10=255
$11=2147483.648
$12=2147483.648
$13=0
$20=0
$21=0
$22=1
$23=3
$24=25.000
$25=750.000
$26=250
$27=3.000
$30=1
$31=0
$32=0
$100=0.000
$101=40.000
$102=188.976
$110=8000.000
$111=8000.000
$112=500.000
$120=500.000
$121=500.000
$122=50.000
$130=790.000
$131=790.000
$132=100.000
ok
It looks like you loaded in a version of 1.1f that was not specifically built for the Xcarve. Some of the parameters look right for the Xcarve, but many do not.
Here is a listing of the default parameters for a 500mm machine, with homing and soft limits set. The differences for a 1000mm machine are $130, $131and $132, set $130 and $131 to 790 and $132 to 100 if you have the 1000mm
You may also have different values for $3 which controls the direction of motion of the axes.
$0=10 (step pulse, usec)
$1=255 (step idle delay, msec)
$2=0 (step port invert mask:00000000)
$3=3 (dir port invert mask:00000011)
$4=0 (step enable invert, bool)
$5=0 (limit pins invert, bool)
$6=0 (probe pin invert, bool)
$10=115 (status report mask:01110011)
$11=0.020 (junction deviation, mm)
$12=0.002 (arc tolerance, mm)
$13=0 (report inches, bool)
$20=1 (soft limits, bool)
$21=0 (hard limits, bool)
$22=1 (homing cycle, bool)
$23=3 (homing dir invert mask:00000011)
$24=25.000 (homing feed, mm/min)
$25=750.000 (homing seek, mm/min)
$26=250 (homing debounce, msec)
$27=1.000 (homing pull-off, mm)
$30=255. (rpm max)
$31=0. (rpm min)
$32=0 (laser mode, bool)
$100=40.000 (x, step/mm)
$101=40.000 (y, step/mm)
$102=188.947 (z, step/mm)
$110=8000.000 (x max rate, mm/min)
$111=8000.000 (y max rate, mm/min)
$112=500.000 (z max rate, mm/min)
$120=500.000 (x accel, mm/sec^2)
$121=500.000 (y accel, mm/sec^2)
$122=50.000 (z accel, mm/sec^2)
$130=290.000 (x max travel, mm)
$131=290.000 (y max travel, mm)
$132=88.000 (z max travel, mm)
I had just figured that something is wrong with my grbl parameters. For example $100 was zero and I was wondering why my X axis wonât move. Im going into a deep reading session trying to understand what each parameter means at following link Grbl v1.1 Configuration ¡ gnea/grbl Wiki ¡ GitHub
1 Like
I flashed Arduino with Inventable version, removed gShiled and ran ?, the status is as follows.
Alarm,MPos:0.000,0.000,0.000,WPos:6.000,-59.000,0.000,Pin:010
Cant believe that Arduino came like this.
The issue seems to be a faulty Arduino. Get in touch with Inventables.
1 Like