This alarm occurs when the control receives a G-code command with a numeric value containing more digits than the allowed maximum for that address or parameter. The MOCON control has specific digit limits for each address code (X, Y, Z, F, S, etc.) and exceeding these limits triggers this parsing error. The machine will halt program execution at the offending line and require the operator to acknowledge the alarm before proceeding.
HaasProgram/G-codeBasic5-10 minutes
315
Haas Alarm 315 - Number Exceeds Digit Limit
Too Many Digits
This alarm occurs when the control receives a G-code command with a numeric value containing more digits than the allowed maximum for that address or parameter. The MOCON control has specific digit limits for each address code (X, Y, Z, F, S, etc.) and exceeding these limits triggers this parsing error. The machine will halt program execution at the offending line and require the operator to acknowledge the alarm before proceeding.
Safety
Program cannot execute
Common Causes
Programming error where a decimal point was omitted, causing values like 0.0001 to be entered as 00001 and exceed digit count limits
Post processor configuration issue generating excessive decimal places or improper numeric formatting for feed rates or coordinates
Manual MDI entry mistake where operator typed too many digits in a coordinate value or parameter
Corrupted program file with garbage characters or malformed numeric data being interpreted as extra digits
Macro variable calculation resulting in extremely long numeric string being passed to axis movement or parameter address
Troubleshooting Steps
1Step 1: Note the exact line number displayed with the alarm and review that specific G-code block for any unusually long numeric values
2Step 2: Check for missing decimal points in coordinate values, feed rates, or spindle speeds that would make the number appear much larger than intended
3Step 3: Count the total digits in each address on the problem line and compare to Haas programming manual limits (typically 8 digits including decimal for coordinates, 5-6 for feeds)
4Step 4: If the program was recently post-processed, verify post processor settings for decimal place output and numeric formatting match Haas control requirements
5Step 5: Test the suspected line in MDI mode with corrected formatting to confirm the logic is sound before editing the main program
6Step 6: If alarm persists on a previously working program, perform control software diagnostics and consider reloading the program from verified backup to rule out file corruption
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
Get machine-aware diagnosis
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.