cprezzi / grbl-LPC

Multiple compiled versions for different boards & machines (under releases)
Other
56 stars 39 forks source link

Z axis not homing with MKS #32

Closed dansity closed 4 years ago

dansity commented 4 years ago

Hello, I have an issue where the Z axis is not homing using MKS board. I have validated the cabling, the limit switch is recognized when pressed in Putty (Pn:PZ). X and Y axis homing without problem, Z not even moving. When I jog up manually the limit switch clicks but the Z does not stop. It looks like Z axis is not considered at all. I have checked that GRBL is not in laser mode. I have flashed the mks_sbase_firmware.bin from releases. GRBL settings below: $0 = 10 (Step pulse time, microseconds) $1 = 255 (Step idle delay, milliseconds) $2 = 0 (Step pulse invert, mask) $3 = 4 (Step direction invert, mask) $4 = 0 (Invert step enable pin, boolean) $5 = 1 (Invert limit pins, boolean) $6 = 0 (Invert probe pin, boolean) $10 = 19 (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 = 1 (Hard limits enable, boolean) $22 = 1 (Homing cycle enable, boolean) $23 = 3 (Homing direction invert, mask) $24 = 200.000 (Homing locate feed rate, mm/min) $25 = 800.000 (Homing search seek rate, mm/min) $26 = 250 (Homing switch debounce delay, milliseconds) $27 = 2.000 (Homing switch pull-off distance, millimeters) $30 = 1000 (Maximum spindle speed, RPM) $31 = 0 (Minimum spindle speed, RPM) $32 = 0 (Laser-mode enable, boolean) $33 = 5000.000
$34 = 0.000
$35 = 1.000
$36 = 100.000
$100 = 321.000 (X-axis travel resolution, step/mm) $101 = 321.000 (Y-axis travel resolution, step/mm) $102 = 320.000 (Z-axis travel resolution, step/mm) $103 = 160.000
$110 = 800.000 (X-axis maximum rate, mm/min) $111 = 800.000 (Y-axis maximum rate, mm/min) $112 = 400.000 (Z-axis maximum rate, mm/min) $113 = 24000.000
$120 = 2500.000 (X-axis acceleration, mm/sec^2) $121 = 2500.000 (Y-axis acceleration, mm/sec^2) $122 = 2500.000 (Z-axis acceleration, mm/sec^2) $123 = 2500.000
$130 = 800.000 (X-axis maximum travel, millimeters) $131 = 800.000 (Y-axis maximum travel, millimeters) $132 = 300.000 (Z-axis maximum travel, millimeters) $133 = 100.000
$140 = 0.600
$141 = 0.600
$142 = 0.000
$143 = 0.000

cprezzi commented 4 years ago

The precompiled version uses only X and Y homing (because it was made for a laser cutter). If you need a different homing sequence, you would have to define it in config.h (or make an own machine profile in defaults.h) and compile your own binary.

dansity commented 4 years ago

Do you have some little more in-depth description about compiling the files? I did find the lines to uncomment in config.h however i have no idea how to compile this thing and the readme mentions a very brief list of items to have for the compiling.

cprezzi commented 4 years ago

Unfortunately I don't have any more detailed description than this:

dansity commented 4 years ago

Thanks for your answer. I did managed to do this at the end however there was a ton of compiling error reference to the axis "A" in these files when i just simply cloned the repo and tried to build it. I didn't really wanted to go into why that is happening so I just removed every single line from every file that mentioned axis "A" and then the make command worked out and now I have a file that is good for a 3axis CNC machine. Thank you for your support once again.

cprezzi commented 4 years ago

Are you sure these was errors not only warnings? I don't get any errors when I compile it.

dansity commented 4 years ago

i got warnings for redefining the homing sequence but i got errors about 30-40 lines regarding every single A axis reference. I just removed them one-by-one and it compiled fine. It could be my bad, I don't know. I don't know much about Make in general, this is our first met.

cprezzi commented 4 years ago

Did you define the homing sequence in config.h? In my fork, this should not be defined in config.h, but in the corresponding machine profile in defualts.h. Otherwise you get a redifining error.

dansity commented 4 years ago

Well since I had no idea what I'm doing I did it in both location. :)

cprezzi commented 4 years ago

The logic of my fork is, to have all supported board-profiles in cpu-map.h and machine-profiles in defaults.h. This way, I only have to define the board and machine in config.h and everything should be done.

dansity commented 4 years ago

Ok cool. If i do anything next time I'll do like that. Thank you. You can close the issue.