-
Notifications
You must be signed in to change notification settings - Fork 64
FAQ
Paciente8159 edited this page Jul 30, 2021
·
19 revisions
These are a few Q&A that I think may be more common while using µCNC.
Jump to section
- Is µCNC safe to use?
- Is µCNC a direct replacement for Grbl?
- µCNC is not recognized by the software I used with Grbl. How can I fix this?
- Ok I've installed µCNC on my board but nothing is happening. What went wrong?
- µCNC is running veeeerrrryyy slooooowwww?
- In terms of collisions I think it's has safe has Grbl. Always wire the ESTOP input and it shuts down everything as soon as you press that button. Limit switches triggered with hard limits enabled also prevent unwanted axis crashes.
- In terms of quality of work v1.2.0 is (I believe) capable of deliver reliable results. In any case safety precautions should be implemented. Run the code in check mode to check for GCODE errors and incompatibilities. If still not confident, do a dry run on a scrap peace or in the air to see if everything looks ok. Then run your real job.
- With minor adaptations yes.
- Pinout yes.
- In terms of settings configuration $0 is max step rate and not step pulse in ms, so for UNO the change is from value 10 to 30000. Everything else should be ok. Eventually $5 and $7 may need adjusting for inverting the limits and controls inputs depending on your wiring.
- If you installed the precompiled version available here then the startup message is with the µCNC name. Some interface software (like Candle, Candle2, and UGS) expect the Grbl startup message instead. If so µCNC needs to be recompiled with option EMULATE_GRBL_STARTUP enabled (cnc_config.h).
- As stated above if you installed the precompiled version available here then the startup message is with the µCNC name. Some interface software (like Candle, Candle2, and UGS) expect the Grbl startup message instead. If so µCNC needs to be recompiled with option EMULATE_GRBL_STARTUP enabled (cnc_config.h). This option actually also forces some of the messages of µCNC to be more Grbl compliant, like the report status message for configurations with less then 3 axis for example. LaserGRBL or OpenCNCPilot for example have no with this.
- If you used a pre-compiled version, as a safety feature all limits and control input pins are pulled high by internal resistors. If µCNC is not wired all limits and control alarms will be active including de Emergency-Stop (ESTOP) input.
- This means that for safety reasons also µCNC will halt. To go around this question short your ESTOP input pin to GND and reconnect your board. µCNC should respond now. If you don't want to use the ESTOP input and want to get rid of the wire, reconfigure setting $7=1 to invert the signal coming from ESTOP, remove the wire and reset your board. µCNC should be running without the wire. At this point other settings may need adjustment.
- Like mentioned above setting $0 is max step rate and not step pulse in ms, so for UNO the change is from value 10 to 30000. Restart µCNC and it should start stepping at a proper rate.
µCNC is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. µCNC is distributed WITHOUT ANY WARRANTY.
Also without the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
µCNC Wiki
- Home
- Basic user guide
- Porting µCNC and adding custom HAL
- Customizing the HAL file
- Adding custom Tools and Modules to µCNC
- FAQ
µCNC for ALL MCU
µCNC for AVR
µCNC for STM32F1 and STM32F4
µCNC for SAMD21
µCNC for ESP8266
µCNC for ESP32
µCNC for NXP LPC176x
µCNC for NXP RP2040