I'm using a 2 axis diy machine with a blackbox. I flashed to the 2-axis using the Firmware Flashing Tool. The Z is still showing in the interface jogging, set zero etc. Should I expect them to be gone? Is there a macro to hide them? Also I can't use the gotozero XYZ button, it does not work, it tells me I am exceeding my soft limits. I can go to the x and y separately and tell them to go to work zero and it works. I do have limit switches installed and enabled and it will home correctly. Thanks!
No you should not. The 2axes firmware just fixes Grbl so ot doesn't try to home a non-existent Z axis (or it would hang on homing) : see Frequently Asked Questions · gnea/grbl Wiki (We just did that compile for you that's all) You still want to home XY as your machine has those axes. You can still Setzero, as your nonexistent Z axis will still accept Z moves and other Z commands. Disable Soft Limits it does not support 2-axes machines: Soft Limits applies to all three axes, building a machine with only two, means it is to be left disabled.
@Peter Van Der Walt Can you please provide me the source files of your 2 axis firmware? I have some issues with homing but your 2 axis fw works well so I want to understand the differences to learn! Thanks in advance Pa_blo
As per above, the only thing we apply to the 2-axes firmware, is setting the Homing Sequence as described in the Grbl FAQ (linked) If you elaborate, we can advise. What controller? (BlackBox 4X?), what machine? and issues experienced
Hmm.....the FAQs home 2 axis in separate cycles, your fw does it simultaneously..... Ok, so then my other changes are the reason why homing is not working.. My setup: Laser engraver, so no z axis Arduino uno with zyltech cnc shield and drv8825 drivers ( because all of these comonents were lying around). My additional changes are a second motor for y ( clone from y) but I want it with a searate endstop for squaring. But then I have to share endstop pins to achieve second y homing.... I enabled all necessary options for dual axis. I am not sure how to "share" pins by sw, only share them by use them with multiple cables in hw...
It does not: see control-grbl-buildall/config.h at 7282759221e655c6c784fb5780b6681128ad384b · OpenBuilds/control-grbl-buildall See the config.h comments around autosquare. Y2 is shared with Z
Done! THX a lot, it was a type mistake...... "For Grbl on the Arduino Uno, the cloned axis limit switch must to be shared with and wired with z-axis limit pin due to the lack of available pins. " I understand this, so x axis to x axis limit switch, y1 axis to y limit switch, y2 axis to z limit switch Connected BUT: y2 does not recognize the limit switch on z (switch is ok, i swapped with y1 to test)
grbl/config.h at master · gnea/grbl says it should (Defined in the map here grbl/cpu_map.h at bfb67f0c7963fe3ce4aaf8a97f9009ea5a8db36e · gnea/grbl and that map pulls into config.h here grbl/config.h at bfb67f0c7963fe3ce4aaf8a97f9009ea5a8db36e · gnea/grbl) -- unless you changed that config to use a different map Note it will only do so during homing (Y2 is not reported in feedback when you press it by hand during testing)
Clear, I know this! To test i "unsquared" the machine manually with y2 closer to the limit switch, then pressed homing. x axis --> no problem y axis --> Y2 went in hard limit and motor y2 went on until y1 hit the limit switch....so the belt on y2 got stressed a bit... Now I will try to swap y1 limit and y2 limit, then y1 should crash and y2 should work fine.....just to get sure I didn't made a connection mistake
