uCNC Error 2
uCNCErrorPosition is kept
A number in the line is missing or badly written (like X1.2.3 or a letter with no value).
Position is kept. An error means the controller refused that one line or command, so nothing moved for it. (Hamrun's reading)
What to do
- Look at the line it stopped on and fix the number after the letter.
- If your file uses commas as decimal points, change them to dots.
Name in the uCNC source:
STATUS_BAD_NUMBER_FORMAT. The meaning above is in Hamrun's words; uCNC's own message text isn't copied here. sourceGot a different message?
Paste it into the decoder. Hamrun's editor checks your G-code before you run it, so a toolpath that leaves the machine's travel or a missing feed rate is caught before the machine stops. Have the whole file? Check it here, free: it finds the line that triggers this, and the file never leaves your computer.
Related codes
- GRBL 1.1 Error 2: A number in the line is missing or badly written (like X1.2.3 or a letter with no value).
- grblHAL Error 2: A number in the line is missing or badly written (like X1.2.3 or a letter with no value).
- FluidNC Error 2: A number in the line is missing or badly written (like X1.2.3 or a letter with no value).
- Grbl_Esp32 Error 2: A number in the line is missing or badly written (like X1.2.3 or a letter with no value).
Code name taken from the uCNC source on 2026-11-10; the meaning is in Hamrun's words and uCNC's message text isn't copied. Steps and the position answer are Hamrun's reading unless marked “firmware says”. User reports are labelled CLAIMED.