|
__CM0_REV not defined in device header file; using default!
|
V2 This compile-time warning occurs when __CHECK_DEVICE_DEFINES is enabled and the device header file does not define __CM0_REV (the Cortex-M0 revision number). The code provides a default value of 0x0000 but warns that this may not match the actual silicon revision.
|
|
__CM3_REV not defined in device header file; using default!
|
V2 This warning occurs when the Cortex-M3 revision number is not defined in the device header. A default value of 0x0200 (revision 2) is used, which may not match the actual silicon.
|
|
__CM4_REV not defined in device header file; using default!
|
V2 Warning when Cortex-M4 revision number is not defined. Default 0x0000 is used.
|
|
__FPU_PRESENT not defined in device header file; using default!
|
V2 Warning when FPU presence flag is not defined for Cortex-M4. Since M4 can have optional FPU, this is an important configuration parameter. Default of 0 (no FPU) is used.
|
|
__MPU_PRESENT not defined in device header file; using default!
|
V2 This warning occurs when __MPU_PRESENT (Memory Protection Unit presence flag) is not defined. The default value of 0 (no MPU) is used. Some Cortex-M3 variants include an MPU, so this may be incorrect.
|
|
__MPU_PRESENT not defined in device header file; using default!
|
V2 Warning when Memory Protection Unit presence is not defined for Cortex-M4. Default of 0 (no MPU) is used.
|
|
__NVIC_PRIO_BITS not defined in device header file; using default!
|
V2 This warning occurs when the number of NVIC priority bits is not defined. The default of 4 bits (16 priority levels) is used, which is typical for Cortex-M3 but may vary by vendor implementation.
|
|
__NVIC_PRIO_BITS not defined in device header file; using default!
|
V2 Warning when NVIC priority bits count is not defined for Cortex-M4. Default of 4 bits is used.
|
|
__NVIC_PRIO_BITS not defined in device header file; using default!
|
V2 This compile-time warning occurs when __NVIC_PRIO_BITS is not defined in the device header. This constant specifies how many bits are used for interrupt priority levels in the NVIC (Nested Vectored Interrupt Controller). The default value of 2 is used, which may not be correct for all devices.
|
|
__Vendor_SysTickConfig not defined in device header file; using default!
|
V2 This warning occurs when the vendor SysTick configuration flag is not defined. The default of 0 (use standard CMSIS SysTick config) is used instead of vendor-specific implementation.
|
|
__Vendor_SysTickConfig not defined in device header file; using default!
|
V2 Warning when vendor SysTick configuration flag is not defined for Cortex-M4. Default of 0 (standard config) is used.
|
|
__Vendor_SysTickConfig not defined in device header file; using default!
|
V2 This compile-time warning occurs when __Vendor_SysTickConfig is not defined. This flag indicates whether the vendor provides a custom SysTick configuration function (value 1) or if the standard CMSIS function should be used (value 0). The default of 0 is used if not specified.
|
|
- bad filesize\n
|
V1 This error occurs when the SIZE command specifies a filesize of 0 or less, or the size cannot be parsed as a valid integer. The file operation is aborted and the connection returns to the normal command state.
|
|
- delete failed\n
|
V1 This error is returned to the SFTP client when the file deletion operation fails. This can occur if the file doesn't exist, is in use, is read-only, or there are permission issues. The underlying filesystem's remove() function returned a non-zero error code.
|
|
- Error saving file\n
|
V1 This error occurs when writing data to the file fails during an SFTP upload. The fwrite() function returns fewer bytes than requested, indicating a write error such as disk full, filesystem error, or I/O failure. The file is closed and the upload is aborted.
|
|
- Expected size\n
|
V1 This error occurs when the SFTP client sends something other than a SIZE command after a STOR command. The protocol requires the file size to be specified before the file data is sent. If this expected SIZE command is missing or malformed, the file operation is aborted.
|
|
- failed\n
|
V1 This error is returned to the SFTP client when opening a file for writing fails. This can occur if the filesystem is read-only, there's insufficient space, the path is invalid, or there are permission issues. This message appears for both OLD (overwrite) and APP (append) modes.
|
|
- incomplete KILL command\n
|
V1 This error is returned to the SFTP client when a KILL (delete file) command is sent without specifying a filename. The command requires at least 6 characters (KILL + space + filename), and anything shorter is rejected as incomplete.
|
|
- incomplete STOR command\n
|
V1 This error is returned to the SFTP client when a STOR (store file) command is sent without complete parameters. The command requires at least 11 characters (STOR + space + mode + space + filename), and anything shorter is rejected as incomplete.
|
|
- Only OLD|APP supported\n
|
V1 This error is returned to the SFTP client when a STOR command specifies a mode other than OLD (overwrite) or APP (append). The SFTP protocol supports other modes like NEW, but Smoothie's implementation only supports these two modes.
|
|
- Unknown command\n
|
V1 This error is returned to the SFTP client when an unrecognized command is sent. The SFTP daemon only supports USER, KILL, DONE, and STOR commands. Any other command triggers this error response.
|
|
// Failed changing switch state.
|
V1 This error occurs when the temperature switch cannot change the state of its associated switch.
|
|
// Failed to get switch state.
|
V1 This error occurs when the temperature switch cannot retrieve the state of its associated switch, usually because the switch is not configured or not accessible.
|
|
// WARNING: Autopid did not resolve within %d cycles, these results are probably innacurate
|
V2 This warning occurs when PID autotuning doesn't stabilize within the requested number of heating/cooling cycles (default 8). The results may be inaccurate and should be verified.
|
|
//ERROR: Delta calculation fail! Unable to move to:
|
V1 This debug error message is printed when the rotary delta kinematics calculation fails (returns status -1). This occurs when the requested cartesian position cannot be reached by the rotary delta mechanism, typically due to the position being outside the workspace or at a singularity point. The error provides detailed position information for debugging.
|
|
//ERROR: Delta calculation fail! Unable to move to:
|
V2 This error occurs when the rotary delta inverse kinematics calculation fails (returns -1), indicating the requested cartesian position is unreachable by the delta mechanism. This happens when a position is outside the robot's working envelope. The system resets actuators to home position (0,0,0) as a fallback. This error only prints when debug_flag is enabled. This indicates the user is trying to move to an impossible position given the delta geometry.
|
|
%c - ERROR: Channel A seems to be unconnected!
|
V1 This error occurs when the TMC26X motor driver detects that channel A appears to be open/unconnected (no load detected). This can indicate a disconnected motor wire or a motor that is not drawing current. Note: The comment indicates these can be false positives during movement.
|
|
%c - ERROR: Channel B seems to be unconnected!
|
V1 This error occurs when the TMC26X motor driver detects that channel B appears to be open/unconnected (no load detected). This can indicate a disconnected motor wire or a motor that is not drawing current. Note: The comment indicates these can be false positives during movement.
|
|
%c - ERROR: Overtemperature Shutdown!
|
V1 This error occurs when the TMC26X motor driver chip is too hot and has shut down to prevent damage. The driver will not work until it cools down. This indicates a serious thermal management issue that must be addressed.
|
|
%c - ERROR: SHORT to ground on channel A!
|
V1 This error occurs when the TMC26X motor driver detects that channel A is shorted to ground. This indicates a wiring problem or motor fault that must be corrected before operation can resume.
|
|
%c - ERROR: SHORT to ground on channel B!
|
V1 This error occurs when the TMC26X motor driver detects that channel B is shorted to ground. This indicates a wiring problem or motor fault that must be corrected before operation can resume.
|
|
%c - WARNING: Overtemperature Prewarning!
|
V1 This warning occurs when the TMC26X motor driver chip detects that it is approaching an overtemperature condition. The chip is still working but some parameters may be degraded. Action should be taken to improve cooling before a full shutdown occurs.
|
|
%c, ERROR: Channel A over current shutdown
|
V1 This error occurs when the DRV8711 motor driver chip detects an overcurrent condition on Channel A and has shut down that channel. This can be caused by a short circuit, wiring issue, or excessive current draw from the motor.
|
|
%c, ERROR: Channel A predriver fault
|
V1 This error occurs when the DRV8711 motor driver chip detects a fault in the Channel A predriver circuitry. This typically indicates a hardware fault in the driver chip or associated circuitry.
|
|
%c, ERROR: Channel B over current shutdown
|
V1 This error occurs when the DRV8711 motor driver chip detects an overcurrent condition on Channel B and has shut down that channel. This can be caused by a short circuit, wiring issue, or excessive current draw from the motor.
|
|
%c, ERROR: Channel B predriver fault
|
V1 This error occurs when the DRV8711 motor driver chip detects a fault in the Channel B predriver circuitry. This typically indicates a hardware fault in the driver chip or associated circuitry.
|
|
%c, ERROR: Overtemperature shutdown
|
V1 This error occurs when the DRV8711 motor driver chip detects an overtemperature condition and has shut down to protect itself. The error is only reported once until the condition clears. This indicates the driver is too hot and cooling is needed.
|
|
%s is not a known switch device
|
V1 This error occurs when attempting to set the state of a switch device that is not recognized or configured. This is reported after attempting to set the switch value and having the operation fail.
|
|
%s is not a known temperature device
|
V1 This error occurs when attempting to get temperature for a device name that is not recognized or not configured. The device name must match a configured temperature control module (e.g., "hotend", "bed").
|
|
%s is not a known temperature device
|
V1 This error occurs when attempting to set temperature for a device name that is not recognized or not configured. The device name must match a configured temperature control module.
|
|
Accessing a corrupted shared library
|
V2 POSIX errno definition for corrupted shared library access. Not relevant in embedded firmware but defined for POSIX compatibility.
|
|
ADC channel %u is outside range available to MBED pins.
|
V1 This error is printed to stderr when attempting to convert an ADC channel number to a pin name, but the channel number is outside the valid range of 0-5. The LPC1768 only has 6 ADC channels available on the mbed pinout (p15-p20). Despite the error, the function still returns a value using a bitmask to prevent array out-of-bounds access.
|
|
ADC channel %u is outside range available to MBED pins.
|
V1 Similar to the previous error, this is displayed when converting ADC channel numbers to pin numbers and the channel is outside the valid range of 0-5. This validation prevents access to non-existent ADC channels.
|
|
ADC pin mapping failed
|
V1 Runtime error when attempting to initialize an ADC on a pin that doesn't support ADC functionality. This occurs when an invalid pin is passed to the analog input initialization.
|
|
ADC Warning: Actual ADC sample rate of %u which is above %u limit
|
V1 This warning is issued when the actual ADC sample rate exceeds the maximum recommended rate (MAX_ADC_CLOCK which is 13MHz, resulting in about 203kHz sample rate). Operating above this rate may result in inaccurate ADC readings. The warning includes both the actual rate and the maximum allowed rate.
|
|
ADC Warning: ADC CCLK clock divider must be 1, 2, 4 or 8. %u supplied.
|
V1 This warning is displayed when the ADC is initialized with an invalid clock divider value. The LPC17xx ADC only supports clock dividers of 1, 2, 4, or 8. If any other value is provided, the system warns the user and defaults to using a divider of 1. This ensures the ADC continues to function even with incorrect configuration.
|
|
ADC Warning: Clock division is %u which is above 255 limit. Re-Setting at limit.
|
V1 This warning occurs when the calculated ADC clock division value exceeds the maximum allowed value of 255 (0xFF). The LPC17xx ADC has an 8-bit clock divider field, so values above 255 cannot be used. The system clamps the value to 255 to prevent overflow and ensures the ADC operates at a valid (though potentially slower than requested) rate.
|
|
ADC Warning: Clock division is 0. Re-Setting to 1.
|
V1 This warning is displayed when the calculated ADC clock divider is 0, which would be invalid (division by zero in the hardware). This can occur if the requested sample rate is extremely high relative to the peripheral clock. The system corrects this by setting the divider to the minimum valid value of 1.
|
|
ADC Warning: Maximum recommended sample rate is %u
|
V1 This is a follow-up to the previous warning, informing the user of the maximum recommended sample rate based on the current clock configuration. This helps users adjust their configuration to stay within safe operating parameters for accurate ADC readings.
|
|
ADC Warning. startmode is %u. Must be 0 for burst mode.
|
V1 This warning is issued when attempting to enable burst mode while the ADC startmode is not set to 0. In burst mode, the ADC continuously samples all enabled channels. However, burst mode is incompatible with other start modes (edge-triggered, etc.). The warning alerts the user to this configuration conflict, though burst mode is still enabled.
|
|
Address in use.
|
V2 This error string corresponds to ERR_USE (-8) error code. It indicates that the requested address (IP and/or port) is already in use by another connection or socket.
|
|
Advertise error
|
V2 POSIX errno definition for RFS (Remote File Sharing) advertise error. Linux-specific error code.
|
|
ALARM: Abort during cycle
|
V1 This error occurs when the user sends a halt command (Ctrl+X, ASCII 0x18) during GRBL mode operation. It indicates that the current machining cycle has been aborted. This is sent to the USB serial port to inform the host that an emergency stop has been triggered.
|
|
ALARM: Abort during cycle
|
V2 This alarm is triggered when the user sends a Ctrl+X (ASCII 24) character, which is the emergency stop command. It halts all motion and operations immediately. This is a safety feature for aborting potentially dangerous operations.
|
|
ALARM: Abort during cycle\r\n
|
V1 This error message is displayed when the user presses CTRL-X in GRBL mode to halt the system. It indicates that an emergency stop has been triggered during a motion cycle. The message follows GRBL-compatible alarm formatting.
|
|
ALARM: Hard limit was hit - $X needed
|
V2 This is the GRBL mode equivalent of the limit switch error. The machine has hit a hard limit and requires the $X command to clear the alarm state.
|
|
ALARM: Homing fail
|
V1 This is the GRBL-mode version of the homing failure error. Same meaning as the previous error but formatted for GRBL compatibility.
|
|
ALARM: Homing fail
|
V2 GRBL mode version of the homing cycle failed error. The system enters alarm state and homing must be restarted.
|
|
ALARM: Kill button pressed - reset, $X or M999 to clear HALT
|
V1 This alarm is triggered when the kill/emergency stop button is pressed. The system immediately halts all motion and requires the user to reset the system or use the $X (unlock) or M999 (reset) commands to clear the halt state and resume operation.
|
|
ALARM: Probe fail
|
V1 This critical error occurs during G38.2 or G38.4 probe operations when the probe is not triggered. These subcodes are "error" versions that halt the system if probing fails. The system enters HALT state and requires reset or M999.
|
|
ALARM: Probe fail
|
V2 This critical alarm occurs when a G38.2 straight probe command completes without triggering the probe. G38.2 is the "with error" variant, so failing to trigger is an error condition. This puts the system into halt/alarm state and requires reset.
|
|
Already connected.
|
V2 This error string corresponds to ERR_ISCONN (-10) error code. It indicates that the socket/connection is already established and the requested operation cannot be performed on an already-connected socket.
|
|
Already connecting.
|
V2 This error string corresponds to ERR_ALREADY (-9) error code. It indicates that a connection is already in progress and cannot be initiated again.
|
|
An error code if there has been an error accepting
|
V2 TCP accept callback parameter documentation. The err parameter indicates if there was an error accepting the new connection. Special note about only returning ERR_ABRT if tcp_abort was called.
|
|
An error code if there has been an error receiving
|
V2 TCP receive callback parameter documentation. The err parameter indicates if there was an error receiving data. Special note about only returning ERR_ABRT if tcp_abort was called.
|
|
Assertion \"%s\" failed at line %d in %s\n
|
V2 This error occurs when a lwIP assertion fails. The macro prints which assertion failed, at what line number, and in which file, then aborts the program. This is a critical error indicating a programming error or internal inconsistency in the network stack.
|
|
Attemt to read beyond end of disk! Read LBA %lu > Disk LBAs %lu
|
V1 This error occurs when the USB Mass Storage Device receives a read request for a Logical Block Address (LBA) that exceeds the total block count of the disk. This typically happens if the host system has incorrect information about the disk size, or if there's a communication error. Note: "Attemt" is a typo for "Attempt".
|
|
authentication failure
|
V2 SNMP generic trap definition for authentication failures. This trap is sent when SNMP authentication fails (wrong community string or credentials).
|
|
Axis must be homed before setting Homing offset
|
V2 This error occurs when attempting to set a homing offset (M306) for an axis that hasn't been homed yet. The axis must be homed first so the system knows its current position.
|
|
Bad address
|
V1 This error indicates a bad memory address or invalid pointer reference in the 9P protocol implementation. It's used when stat buffer operations fail or when pointer arithmetic exceeds expected bounds during message processing.
|
|
Bad address
|
V2 POSIX errno definition for bad memory address. This error occurs when a pointer passed to a function points to invalid memory.
|
|
bad checksums
|
V2 Debug level comment describing the type of warnings that should be logged at the WARNING level, including bad checksums and dropped packets.
|
|
Bad file number
|
V2 POSIX errno definition for invalid file descriptor. This error occurs when operations are performed on an invalid or closed file descriptor or socket.
|
|
Bad font file format
|
V2 POSIX errno definition for bad font file format. Not relevant in embedded firmware context but defined for POSIX compatibility.
|
|
Bad message
|
V1 This error indicates that a malformed or invalid 9P protocol message was received. This can occur when message size is incorrect, required fields are missing, or the message structure doesn't conform to the 9P protocol specification. The CHECK macro throughout the code uses this error for various message validation failures.
|
|
Bad message received %lu
|
V1 This debug message (only shown when DEBUG_PRINTF is enabled) indicates that a 9P protocol message was received with a size larger than the maximum negotiated message size (msize). This is a protocol violation and causes the connection to be closed. This prevents buffer overflows and ensures protocol compliance.
|
|
Bad SPI channel for external SDCard
|
V1 This error occurs when an invalid SPI channel number is specified in the configuration for the external SD card on the panel. The supported SPI channels are 0 or 1. If any other channel is specified, the external SD card feature is disabled and this error is reported.
|
|
because of errors
|
V2 MIB-II statistics documentation describing ifouterrors counter. This tracks outbound packets/frames that could not be transmitted due to errors.
|
|
Board needs to define which UART to use (USE_UART[0|1|2])
|
V2 This is a compile-time error that occurs when the board type and UART selection macros are not properly defined. The code requires both a board type (BOARD_BAMBINO, BOARD_MINIALPHA, or BOARD_PRIMEALPHA) and a UART selection (USE_UART0, USE_UART1, or USE_UART2) to be defined. If none of the conditional compilation branches match, this error is triggered to prevent compilation with an undefined UART configuration.
|
|
Buffer error
|
V2 This is a lwIP error code definition (ERR_BUF = -2) indicating issues with network packet buffers, such as buffer too small, buffer unavailable, or buffer corruption.
|
|
Buffer error.
|
V2 This error string corresponds to ERR_BUF (-2) error code. It indicates a problem with network buffers, such as buffer overflow, underflow, or corruption.
|
|
Button was invalid
|
V2 This error occurs during pin testing when a GPIO pin configured as a button input fails to initialize properly. The pin specification may be incorrect or the hardware may not support the requested configuration.
|
|
calculating baud rate divisors will fail
|
V1 This is a warning/note indicating a limitation of the MRI debugger on LPC176x chips. If the core clock runs faster than 128MHz, the baud rate divisor calculation will fail because the divisor values would overflow or be out of range. The maximum supported baud rate is 3Mbaud.
|
|
Calibration failed to complete, check the initial probe height and/or initial_height settings
|
V1 This error occurs when delta endstop calibration fails. The probe may not be triggering, the initial_height may be wrong, or there are mechanical issues with the delta.
|
|
Calibration failed to complete, check the initial probe height and/or initial_height settings
|
V1 This error occurs when delta radius calibration fails, usually due to probe height issues or mechanical problems.
|
|
Calibration failed to complete, check the initial probe height and/or initial_height settings
|
V1 This error occurs when G29 delta probe point probing fails, indicating probe or configuration issues.
|
|
Called when link failed to setup
|
V2 PPP function comment indicating this callback is invoked when the PPP link establishment fails (LCP negotiation failure, authentication failure, etc.).
|
|
CAN pin mapping failed
|
V1 Runtime error when CAN RD and TD pins cannot be mapped to the same CAN peripheral, or when invalid pins are specified for CAN communication.
|
|
Cannot assign requested address
|
V2 POSIX errno definition for address assignment failures. This error occurs when attempting to bind to an IP address that is not available on any local network interface.
|
|
cannot call any RTOS stuff from this IRQ
|
V2 This is a comment explaining that the I2C interrupt priority is set to 1, which is higher (lower value = higher priority) than the maximum syscall interrupt priority for FreeRTOS. This means RTOS functions (like semaphores, queues, task notifications) cannot be safely called from within this ISR because it can preempt the RTOS itself. It's a warning to developers not to use FreeRTOS API calls in this interrupt handler.
|
|
cannot call any RTOS stuff from this IRQ
|
V2 Similar to the I2C case above, this comment indicates that TIMER0 interrupt has priority 0 (highest priority), which is above the RTOS maximum syscall interrupt priority. Therefore, FreeRTOS API functions cannot be called from the TIMER0 IRQ handler. The commented-out code shows that someone considered using `configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY-1` but chose priority 0 instead, likely for precise timing requirements.
|
|
Cannot exec a shared library directly
|
V2 POSIX errno definition for attempting to execute a shared library directly. Not relevant in embedded firmware.
|
|
cannot set stepticker frequency after it has been started
|
V2 This error occurs when code attempts to change the step ticker frequency after it has already been started. The frequency must be set during initialization only, before the ticker starts running. Attempting to change it after startup is not supported and this error prevents that invalid operation.
|
|
cannot set stepticker unstep delay after it has been started
|
V2 This error occurs when code attempts to change the unstep delay time after the step ticker has already been started. The unstep delay (time between step pulse and unstep pulse) must be configured during initialization before the ticker starts. This prevents runtime changes that could cause timing issues.
|
|
cannot set stepticker unstep delay greater than or equal to step ticker period
|
V2 This error occurs when the unstep delay time is configured to be greater than or equal to the step ticker period. The unstep pulse must occur within the step ticker period, so the delay must be less than the period. This prevents invalid timing configurations that would cause the unstep pulse to occur after the next step pulse.
|
|
CCLKCFG: CCLKSEL must be greater then 1 if PLL0 is used!
|
V1 Compile-time error when PLL0 is enabled but the CPU clock divider (CCLKSEL) is configured incorrectly. When using PLL0, CCLKSEL must be between 1 and 255.
|
|
CCLKCFG: Value out of range!
|
V1 CPU clock divider value must be in the range 0-255.
|
|
Channel A seems to be unconnected
|
V2 This warning occurs when the TMC2660 driver detects an open load (disconnected motor) on channel A while the motor is standing still. This indicates the motor may not be properly connected or has a broken wire. Note: This is only checked when the motor is not moving as it can give false positives during motion.
|
|
Channel B seems to be unconnected
|
V2 This warning occurs when the TMC2660 driver detects an open load (disconnected motor) on channel B while the motor is standing still. This indicates the motor may not be properly connected or has a broken wire. Note: This is only checked when the motor is not moving as it can give false positives during motion.
|
|
Checksum error
|
V2 Statistics counter for network packet checksum errors. This tracks packets that have invalid checksums, indicating corruption during transmission.
|
|
CHIP_LPC18XX is not defined!
|
V2 This is the second part of the error message indicating that CHIP_LPC18XX must be defined when using the LPC18XX chip headers. The developer should add -DCHIP_LPC18XX to their compiler flags.
|
|
CHIP_LPC18XX or CHIP_LPC43XX must be defined
|
V2 This compile-time error occurs when neither CHIP_LPC18XX nor CHIP_LPC43XX preprocessor symbols are defined during compilation. The chip.h header needs to know which specific NXP LPC microcontroller family is being targeted to include the correct chip-specific definitions. This should be defined in the project build configuration or Makefile.
|
|
CHIP_LPC43XX is not defined!
|
V2 This is the second part of the error message requiring CHIP_LPC43XX to be defined. The developer should add -DCHIP_LPC43XX to their compiler flags when building for the LPC43XX chip.
|
|
CLKOUTCFG: Invalid values of reserved bits!
|
V1 Clock output configuration register has invalid reserved bits set.
|
|
CLKSRCSEL: Value out of range!
|
V1 Compile-time error when the clock source selection value is outside the valid range (0-2). This validates the main clock source selection configuration.
|
|
cmsis_18xx.h should not be included directly use cmsis.h instead
|
V2 This compile-time error occurs when user code includes cmsis_18xx.h directly instead of through the generic cmsis.h wrapper. The cmsis.h file handles chip selection and proper configuration before including chip-specific headers. Direct inclusion bypasses these safety checks.
|
|
cmsis_43xx.h should not be included directly use cmsis.h instead
|
V2 Duplicate of the same error from config_43xx/cmsis_43xx.h. This header should not be included directly by user code.
|
|
cmsis_43xx.h should not be included directly use cmsis.h instead
|
V2 This error occurs in the M0 subsystem variant of the CMSIS header. Like the other variants, this header should only be included through cmsis.h, not directly.
|
|
cmsis_43xx.h should not be included directly use cmsis.h instead
|
V2 This error occurs when cmsis_43xx_m0app.h (the M0 application processor variant) is included directly instead of through cmsis.h. The error message says "cmsis_43xx.h" but this applies to all the LPC43XX CMSIS variants including the M0APP variant.
|
|
cmsis_43xx.h should not be included directly use cmsis.h instead
|
V2 This compile-time error occurs when cmsis_43xx.h is included directly in user code instead of through the generic cmsis.h wrapper. The cmsis.h file provides proper chip selection and configuration logic before including the chip-specific header. Direct inclusion bypasses this logic and can cause configuration errors.
|
|
Communication error on send
|
V2 POSIX errno definition for communication errors during send operations. This error occurs when data transmission fails due to communication protocol issues.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V1 Same as LPC1768 but for the LPC11U24 (Cortex-M0) device. The TASKING compiler is configured to generate FPU instructions for a device that doesn't have an FPU.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V1 This is a compile-time error that occurs when the TASKING compiler is configured to generate FPU (Floating Point Unit) instructions but the target device (LPC1768 with Cortex-M3) doesn't have an FPU. The developer needs to check that __FPU_PRESENT is set correctly in their build configuration.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This warning occurs when using IAR Compiler with FPU enabled for Cortex-M3. Same issue as ARM Compiler - M3 has no FPU.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This warning occurs when using Texas Instruments TMS470 compiler with VFP (Vector Floating Point) support enabled for Cortex-M3. The M3 core lacks hardware FPU support.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This warning occurs when using GCC with hardware FPU code generation for Cortex-M3. The check ensures VFP is enabled and software floating point is not explicitly selected.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 These warnings occur in Cortex-M4 headers when FPU code generation is enabled but __FPU_PRESENT is set to 0. Unlike Cortex-M3, the M4 can optionally include an FPU, so this warning alerts when the device configuration indicates no FPU but the compiler is generating FPU instructions. This appears for ARM Compiler (line 112), IAR (line 124), TI (line 136), and GCC (line 148).
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time error occurs when compiling for the Cortex-M3 core with the TASKING compiler configured to generate FPU (Floating Point Unit) instructions, but the target device does not have an FPU. The Cortex-M3 core does not include an FPU, so this configuration is invalid. The developer needs to disable FPU code generation or target a different core (like Cortex-M4 with FPU).
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time error occurs when compiling for Cortex-M4 with the TASKING compiler configured to generate FPU instructions, but __FPU_PRESENT is set to indicate no FPU is available on the target device. This is a configuration mismatch - either the device definition needs to indicate FPU presence, or FPU code generation should be disabled.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time error occurs when compiling for Cortex-M0+ core with the TASKING compiler configured to generate FPU instructions. The Cortex-M0+ core does not have an FPU, so this is an invalid configuration. The compiler's FPU code generation must be disabled for this target.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time error occurs when compiling for SecurCore SC300 core with the TASKING compiler configured to generate FPU instructions. The SC300 core does not include an FPU, so this configuration is invalid. FPU code generation must be disabled.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time warning occurs when using ARM Compiler (armcc) with FPU code generation enabled for a Cortex-M0 device that has no FPU. This is a warning rather than an error for this compiler, allowing the build to continue but alerting the developer to a likely performance issue (software FPU emulation will be used).
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time warning occurs when using IAR Compiler with FPU code generation enabled for a Cortex-M0 device. Like the ARM Compiler variant, this is a warning allowing the build to proceed while alerting to the configuration issue.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time warning occurs when using GCC with hardware FPU code generation (__VFP_FP__ defined and __SOFTFP__ not defined) for a Cortex-M0 device. The condition checks that both hardware FPU is enabled and software floating point is not explicitly requested.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time error (not warning) occurs when using TASKING compiler with FPU code generation for a Cortex-M0. Unlike other compilers which issue warnings, TASKING treats this as a hard error, preventing the build from completing.
|
|
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)
|
V2 This compile-time warning occurs when using ARM Compiler with FPU code generation for a Cortex-M3 device. The Cortex-M3 core does not include an FPU, so this configuration will result in software emulation with performance penalties.
|
|
config setting with value '%s' and checksums[%04X,%04X,%04X] is not a valid int, please see http://smoothieware.org/configuring-smoothie\r\n
|
V1 This error occurs when trying to convert a configuration value to an integer using as_int(), but the value cannot be parsed as a valid integer. The error message includes the invalid value and the checksums identifying the config setting, directing users to the documentation.
|
|
config setting with value '%s' and checksums[%04X,%04X,%04X] is not a valid number, please see http://smoothieware.org/configuring-smoothie\r\n
|
V1 This error occurs when trying to convert a configuration value to a float using as_number(), but the value cannot be parsed as a valid number. The error message includes the invalid value and the checksums identifying the config setting, directing users to the documentation.
|
|
config_tmc2660: no tmc2660 %s entry found
|
V2 This error occurs when the TMC2660 configuration section exists but doesn't contain an entry for the specific actuator being configured (e.g., "alpha", "beta", "gamma"). Each motor axis needs its own TMC2660 configuration subsection.
|
|
config_tmc2660: no tmc2660 section found
|
V2 This error occurs during TMC2660 stepper driver configuration when the configuration file lacks a "tmc2660" section. This prevents the TMC2660 driver from being configured properly and is a critical error for boards using TMC2660 drivers (PrimeAlpha board).
|
|
config_tmc2660: spi cs pin is invalid for: %s
|
V2 This error occurs when the SPI chip select pin specified in the TMC2660 configuration is invalid or cannot be initialized. The chip select pin is required for SPI communication with the TMC2660 driver chip. An invalid pin name or unavailable pin will cause this error.
|
|
config-thermistor: Error in config need 3 Steinhart-Hart coefficients
|
V2 This error occurs when using the coefficients configuration option but not providing exactly 3 Steinhart-Hart coefficients (C1, C2, C3).
|
|
config-thermistor: Error in config need 6 numbers for Steinhart-Hart
|
V2 This error occurs when using the rt_curve configuration option (resistance-temperature curve) but not providing exactly 6 numbers. The format requires three temp/resistance pairs (T1,R1,T2,R2,T3,R3).
|
|
config-thermistor: Error in config need rt_curve, coefficients, beta or a valid predefined thermistor defined
|
V2 This error occurs when thermistor configuration is incomplete - none of the required configuration methods (rt_curve, coefficients, beta values, or predefined thermistor name) were provided.
|
|
config-thermistor: no thermistor pin defined, or invalid ADC pin or bad format
|
V2 This error occurs when the thermistor pin specification in the config is missing, invalid, or in an incorrect format. Valid formats include "ADC0_n" (where n is 0-7) or pin specifications like "P7.5".
|
|
config-thermistor: Thermistor pin not created
|
V2 This error occurs when the ADC pin for the thermistor cannot be created, typically due to ADC initialization failures or system resource limitations.
|
|
config-thermistor: Thermistor pin not initialized
|
V2 This error occurs when the thermistor ADC pin specification was parsed successfully but the pin failed to initialize/connect properly.
|
|
config-zprobe: failed to load %s calibration strategy
|
V2 This error occurs when the delta calibration strategy fails to configure properly. Check the delta calibration strategy configuration requirements.
|
|
config-zprobe: failed to load %s leveling strategy
|
V2 This error occurs when a recognized leveling strategy fails to configure properly. The strategy object was created but its configuration failed. Check the specific strategy's configuration requirements.
|
|
config-zprobe: no pin defined
|
V2 This error occurs when the zprobe section exists but no valid probe pin is defined. A probe pin must be specified for the zprobe to function.
|
|
config-zprobe: Unknown calibration stratagy: %s
|
V2 This error occurs when an unrecognized calibration strategy is specified. Currently only "delta" is supported. Note: typo "stratagy" should be "strategy".
|
|
config-zprobe: Unknown leveling stratagy: %s
|
V2 This error occurs when an unrecognized leveling strategy is specified in the configuration. Valid strategies are "three point", "delta grid", and "cartesian grid". Note: there's a typo in the error message - "stratagy" should be "strategy".
|
|
configure-cart-grid: Invalid config, x_size and y_size must be defined
|
V2 This error occurs when the cartesian grid bed leveling strategy is configured but x_size and y_size parameters are not defined. These parameters define the physical bed dimensions and are required for grid leveling.
|
|
configure-current-control: %s - invalid current
|
V2 This error occurs when a current control channel is configured with an invalid (zero or negative) current value. Current must be a positive number in amps. That channel will be skipped.
|
|
configure-current-control: Failed to set current for %s
|
V2 This error occurs when the system successfully read a valid current setting from configuration but failed to actually set it on the hardware. This could indicate a problem with the PWM pin, the SPI driver, or the actuator not supporting current control.
|
|
configure-delta-grid: no delta grid leveling strategy section found
|
V2 This error occurs when the delta grid leveling strategy section is not found in the configuration file. This happens during configuration loading if the user hasn't defined the delta grid leveling strategy section in their config.
|
|
configure-endstop: no axis defined for %s
|
V2 This error occurs when an endstop configuration doesn't specify which axis it belongs to. The axis parameter is required for each endstop.
|
|
configure-endstop: no common settings found. Using defaults
|
V2 This warning occurs when the endstops configuration section doesn't contain a "common" subsection for shared settings. Default values will be used for debounce time, homing order, trim values, etc.
|
|
configure-endstop: no pin defined for %s
|
V2 This error occurs when an endstop configuration entry doesn't specify a valid pin. That particular endstop will be skipped.
|
|
configure-endstop: no section found
|
V2 This error occurs when the configuration file doesn't contain an "endstops" section. Endstops will not be configured and homing will not work.
|
|
configure-endstop: not a known axis
|
V2 This error occurs when the axis specified for an endstop is not X, Y, Z, A, B, or C. Only these axes are recognized.
|
|
configure-endstop: Too many endstops defined for the number of axis
|
V2 This error occurs when trying to configure an endstop for an axis that doesn't have a corresponding motor configured. The number of endstops cannot exceed the number of configured motors.
|
|
configure-extruder: no extuder section found
|
V2 This error occurs when no extruder sections are found in the configuration file. Note the typo "extuder" in the error message (should be "extruder").
|
|
configure-player: no player section found, defaults used
|
V2 This warning occurs when the configuration file doesn't contain a "player" section. The Player module will use default values for all settings. This is non-fatal.
|
|
configure-switch: failed to configure switch %s
|
V2 This error occurs when a specific switch fails to configure properly, usually due to invalid pin specifications or other configuration errors. The switch is deleted and not loaded.
|
|
configure-switch: no switch section found
|
V2 This error occurs when no switch section is found in the configuration file. This is not necessarily a critical error, as switches are optional modules.
|
|
configure-switch: Selected digital pin invalid - disabled
|
V2 This error occurs when a switch is configured to use a digital output pin that is invalid or not connected. The switch's output is disabled.
|
|
configure-switch: Selected sigmadelta pin invalid - disabled
|
V2 This error occurs when a switch is configured to use a sigmadelta PWM output pin that is invalid or not connected. The switch's output is disabled.
|
|
configure-switch: Selected Switch PWM output pin is not PWM capable - disabled
|
V2 This error occurs when a switch is configured to use hardware PWM on a pin that doesn't support PWM functionality. The switch's output is disabled.
|
|
configure-temperature control: failed to configure temperature control %s
|
V2 This error occurs when a specific temperature controller (like hotend or bed) fails to configure properly. This could be due to invalid sensor configuration, pin errors, or other configuration issues.
|
|
configure-temperature control: no section found
|
V2 This error occurs when no temperature control sections are found in the configuration file. This is not necessarily critical for machines that don't need temperature control (like CNC mills).
|
|
configure-temperature-switch: no temperature switch section found
|
V2 This error occurs when no temperature switch sections are found in the configuration file. Temperature switches are optional modules used to control cooling fans or other temperature-dependent switches.
|
|
configure-temperature-switch: WARNING no switch specified
|
V2 This warning occurs when a temperature switch is configured without specifying which switch to control. The switch_key parameter must reference a defined switch module.
|
|
configure-temperature-switch: WARNING: requires a designator
|
V2 This warning occurs when a temperature switch is configured without a designator. The designator specifies which temperature controller (T for hotend, B for bed, etc.) the switch should monitor.
|
|
configure-temperature: %s sensor %s failed to configure
|
V2 This error occurs when the temperature sensor (thermistor, thermocouple, etc.) fails to configure properly. This is usually due to sensor-specific configuration errors.
|
|
configure-temperature: ERROR Fast Ticker was not set (Too slow?)
|
V2 This error occurs when attempting to attach a heater PWM callback to the FastTicker at a specified frequency fails. This happens when the frequency is too slow for the FastTicker (below its minimum frequency).
|
|
configure-temperature: ERROR Fast Ticker was not set (Too slow?)
|
V2 This error occurs when attaching the laser power update callback to the FastTicker fails because the frequency is too slow for FastTicker.
|
|
configure-temperature: ERROR Slow Ticker was not set (Too fast?)
|
V2 This error occurs when attempting to attach a heater PWM callback to the SlowTicker at a specified frequency fails. This happens when the frequency is too fast for the SlowTicker (above its maximum frequency).
|
|
configure-temperature: ERROR Slow Ticker was not set (Too fast?)
|
V2 This error occurs when attaching the laser power update callback to the SlowTicker fails because the frequency is too fast for SlowTicker.
|
|
configure-temperature: WARNING update frequency is fast enough that ramfunc needs to be used
|
V2 This warning occurs when the laser power update frequency is high enough (>= 1kHz) that the code should be placed in RAM for performance, but currently it's not. This could affect laser power modulation accuracy.
|
|
configure-zprobe: no three point leveling strategy section found
|
V2 This error occurs when the three point leveling strategy section is not found in the configuration file during module initialization.
|
|
configure-zprobe: no zprobe section found
|
V2 This error occurs during configuration when there is no "zprobe" section in the configuration file. Z-probe functionality will not be available. This is a normal condition if the user doesn't have a Z-probe installed.
|
|
Connection aborted.
|
V2 This error string corresponds to ERR_ABRT (-13) error code. It indicates that the connection was aborted, typically by the local application or stack due to an error condition.
|
|
Connection closed.
|
V2 This error string corresponds to ERR_CLSD (-15) error code. It indicates that the connection has been closed, either gracefully by the remote peer or locally.
|
|
Connection reset.
|
V2 This error string corresponds to ERR_RST (-14) error code. It indicates that the connection was reset by the remote peer, typically via a TCP RST packet.
|
|
Connection to server failed
|
V2 SMTP result code indicating that the TCP connection to the mail server could not be established (server unreachable, refused connection, or network down).
|
|
Connection to server failed
|
V2 HTTP client result code indicating TCP connection to the HTTP server failed (server unreachable, refused connection, or network down).
|
|
Copy RAM to Flash command: cannot write to Sector 0.
|
V1 This is a documentation comment describing Code Read Protection (CRP) level 1 limitations on the LPC17xx. When CRP1 is enabled, the Copy RAM to Flash command is restricted and cannot write to Sector 0 of the flash memory. This is a security feature to prevent unauthorized firmware modification.
|
|
CORE_M0 or CORE_M4 must be defined for CHIP_LPC43XX
|
V2 This compile-time error occurs when CHIP_LPC43XX is defined but neither CORE_M0 nor CORE_M4 is specified. The LPC43XX is a multi-core chip with both Cortex-M4 and Cortex-M0 processors, and the compiler needs to know which core is being built for. This should be defined in the project configuration.
|
|
CORE_M3 is not defined for the LPC18xx architecture
|
V2 This compile-time error occurs when compiling code for the LPC18XX chip without defining CORE_M3. The LPC18XX family exclusively uses the Cortex-M3 core, so this symbol must be defined in the build system or compiler flags. This is the first of a two-part error message.
|
|
CORE_M3 should be defined as part of your compiler define list
|
V2 This is the second part of the error message providing guidance on how to fix the missing CORE_M3 definition. The developer should add -DCORE_M3 to their compiler flags or Makefile.
|
|
CORE_M4 or CORE_M0 is not defined for the LPC43xx architecture
|
V2 This compile-time error occurs when compiling for the LPC43XX chip without specifying which core is being targeted. The LPC43XX is a dual-core chip with both Cortex-M4 and Cortex-M0 processors, so either CORE_M4 or CORE_M0 must be defined to indicate which core the code is being compiled for.
|
|
CORE_M4 or CORE_M0 should be defined as part of your compiler define list
|
V2 This is the second part of the error providing guidance on fixing the missing core definition. The developer should add either -DCORE_M4 or -DCORE_M0 to their compiler flags depending on which processor they are targeting.
|
|
could not create directory %s
|
V1 This error occurs when the 'mkdir' command fails to create a directory. This can happen if the directory already exists, the parent path is invalid, there's no write permission, or SD card issues prevent directory creation.
|
|
Could not delete %s
|
V1 This error occurs when the 'rm' command fails to delete a file. This can happen if the file doesn't exist, is write-protected, is currently in use, or there are SD card access issues.
|
|
could not find config setting, please see http://smoothieware.org/configuring-smoothie\r\n
|
V1 This error occurs when a configuration value is marked as required (by calling the required() method) but was not found in the configuration file. The error directs users to the configuration documentation website for help.
|
|
Could not get file size
|
V2 This warning occurs when the system cannot determine the size of the G-code file being played. This prevents progress reporting but doesn't prevent the file from being played. This could indicate filesystem issues.
|
|
Could not open directory %s
|
V1 This error occurs when the 'ls' command attempts to list a directory that cannot be opened. This typically happens when the specified directory path doesn't exist, is invalid, or there are SD card access issues.
|
|
Could not open directory %s
|
V1 This error occurs when the 'cd' command attempts to change to a directory that cannot be opened. This happens when the specified directory doesn't exist or is not accessible.
|
|
could not pinout
|
V1 This fatal error occurs when attempting to configure a pin that is not found in the pinmap table for the requested peripheral function. This means the code is trying to use a pin for a function it doesn't support. The error() macro will print the message via USB serial and halt execution with "blue lights of death".
|
|
Could not rename %s to %s
|
V1 This error occurs when the 'mv' command fails to rename/move a file. This can happen if the source file doesn't exist, the destination already exists, paths are invalid, or there are SD card access issues.
|
|
Couldn't create %s in FATFileSystem::FATFileSystem
|
V1 This error occurs when trying to create a new FAT filesystem instance but all available drive slots (_DRIVES) are already in use. The system supports a limited number of mounted filesystems simultaneously, and this error means that limit has been exceeded.
|
|
Couldn't read csd response from disk
|
V1 This error occurs after successfully sending CMD9 but failing to read the 16-byte CSD data block that should follow. This indicates a communication error during the data transfer phase.
|
|
Couldn't setup requested SPI frequency
|
V1 Runtime error when the requested SPI frequency cannot be configured, typically when hz parameter is 0 or an achievable frequency cannot be generated.
|
|
Currently printing, abort print first
|
V2 This error occurs when a user tries to start a new print while a print is already in progress or suspended. The current print must be aborted before a new one can start.
|
|
DAC pin mapping failed
|
V1 Runtime error when attempting to initialize a DAC on a pin that doesn't support DAC functionality.
|
|
Data check error lead to test abort
|
V2 lwIPerf result code indicating the test was aborted due to data verification errors (received data doesn't match expected pattern).
|
|
Defaulting to 1.
|
V1 This is a continuation of the previous warning, informing the user that after detecting an invalid ADC clock divider, the system is defaulting to a divider value of 1. This allows the ADC to continue operating with safe default settings.
|
|
Didn't get a response from the disk
|
V1 This error occurs when reading the Card Specific Data (CSD) register using CMD9. The CSD contains information about the card's capacity and access parameters. Failure to get a response indicates communication failure or a damaged card.
|
|
Directory not empty
|
V1 This error occurs when attempting to remove a directory that still contains files or subdirectories. The remove() operation in the Tremove handler will fail with this error if the directory is not empty.
|
|
E01
|
V1 This is a GDB protocol error code returned by the MRI (Monitor for Remote Inspection) debugger when it encounters an error parsing command arguments from GDB. This occurs when GDB sends a malformed command or the arguments cannot be parsed correctly.
|
|
E03
|
V1 GDB protocol error code returned when MRI cannot access the requested memory address. This occurs when GDB tries to read or write to an invalid or protected memory location during debugging operations.
|
|
E04
|
V1 GDB protocol error code returned when MRI's internal input or output buffer overflows. This occurs when a command or response exceeds the buffer size allocated for communication between MRI and GDB.
|
|
E05
|
V1 GDB protocol error code returned when there are no free FPB (Flash Patch and Breakpoint) hardware breakpoint comparator slots available. The ARM Cortex-M series has a limited number of hardware breakpoints (typically 6), and this error occurs when trying to set more breakpoints than the hardware supports.
|
|
Entering Alarm/Halt state
|
V1 This message is output immediately after any Gcode error is reported, indicating that the system is entering a halted state for safety. Once in HALT state, most commands are ignored except for specific allowed M-codes and M999 (which clears the halt). This prevents further potentially dangerous operations after an error.
|
|
ERR_BUSY
|
V2 General busy error code (-3) returned when a requested resource is currently busy and cannot be accessed. Used when a peripheral or subsystem is already in use.
|
|
ERR_FAILED
|
V2 General failure error code (-1) returned by Boot ROM drivers and library functions when an operation fails for unspecified reasons. This is the most generic error code in the LPC43xx error system.
|
|
ERR_I2C_LOSS_OF_ARBRITRATION
|
V2 I2C communication error indicating loss of arbitration on a multi-master I2C bus. This occurs when multiple masters try to transmit simultaneously and this master lost the arbitration (another master had a higher priority signal).
|
|
ERR_I2C_NAK
|
V2 I2C communication error indicating a NAK (Not Acknowledge) was received from the slave device. This occurs when the addressed I2C device doesn't respond or can't accept data.
|
|
ERR_ISP_DST_ADDR_ERROR
|
V2 ISP error indicating the destination address is not properly aligned on a word boundary or 256-byte boundary (depending on the operation). Flash programming requires specific alignment.
|
|
ERR_ISP_INVALID_COMMAND
|
V2 ISP (In-System Programming) error indicating an invalid or unrecognized ISP command was sent. This occurs when the bootloader receives a command it doesn't support or that is malformed.
|
|
ERR_ISP_SECTOR_NOT_BLANK
|
V2 ISP error returned during blank check operation when a flash sector contains non-0xFF data. This typically occurs when trying to verify a sector is erased before programming, but it still contains data.
|
|
ERR_ISP_SECTOR_NOT_PREPARED_FOR_WRITE_OPERATION
|
V2 ISP error indicating a flash sector must be prepared before it can be written. The "Prepare sector for write operation" ISP command must be called before programming flash sectors.
|
|
ERR_ISP_SRC_ADDR_ERROR
|
V2 ISP error indicating the source address for a copy/program operation is not aligned on a word boundary (4 bytes). Flash operations require word-aligned addresses for proper operation.
|
|
ERR_TIME_OUT
|
V2 General timeout error code (-2) returned when an operation takes longer than expected to complete. Used across all peripheral subsystems when a timeout condition occurs.
|
|
ERR_USBD_BAD_DESC
|
V2 USB device stack error indicating a malformed or invalid USB descriptor was provided. Descriptors must follow the USB specification format exactly.
|
|
ERR_USBD_INVALID_REQ
|
V2 USB device stack error indicating an invalid request was received from the USB host. This occurs when the host sends a control transfer request that is not supported or is malformed.
|
|
Error
|
V1 This error occurs when the PHY (Physical Layer) reset fails. This happens in two conditions: (1) when the PHY read operation returns a negative value indicating a read error, or (2) when the timeout counter expires waiting for the PHY reset to complete. The function returns -1 to indicate failure.
|
|
Error code to indicate why the pcb has been closed
|
V2 TCP error callback parameter documentation. The err parameter explains why the connection was closed (ERR_ABRT for aborted, ERR_RST for reset).
|
|
error codes predefined by SNMP prot.
|
V2 Comment introducing the SNMP protocol error codes enumeration. These are standard error codes defined by the SNMP protocol specification.
|
|
Error in config need 3 Steinhart-Hart coefficients
|
V1 This configuration error occurs when the thermistor coefficients setting doesn't contain exactly 3 values. Steinhart-Hart requires three coefficients (C1, C2, C3). This indicates a configuration syntax error.
|
|
Error in config need 6 numbers for Steinhart-Hart
|
V1 This configuration error occurs when setting up a thermistor with Steinhart-Hart coefficients from temperature/resistance pairs. The rt_curve configuration must contain exactly 6 numbers (T1,R1,T2,R2,T3,R3). Having a different number indicates a configuration syntax error.
|
|
Error in config need rt_curve, coefficients, beta or a valid predefined thermistor defined
|
V1 This configuration error occurs when a thermistor is configured without any of the required parameters. At least one of rt_curve, coefficients, beta, or a predefined thermistor must be specified for the thermistor to work.
|
|
Error in options
|
V2 Statistics counter for errors in protocol options (e.g., IP options, TCP options). This tracks packets with malformed or invalid option fields.
|
|
error reading input, aborting
|
V1 This error occurs during file upload when there is an error reading input from the stream. A return value of -1 indicates a read error, possibly due to communication timeout or connection loss.
|
|
error writing to file. ignoring all characters until EOF
|
V1 This error occurs during file upload when writing to the destination file fails. This typically indicates the SD card is full, has been removed, or has encountered a write error. The upload continues reading input but discards data until EOF.
|
|
error:
|
V1 This is the error prefix output when a Gcode command has been marked as having an error (gcode->is_error is true). In GRBL mode it outputs "error:" while in normal mode it outputs "Error: ". The actual error message follows this prefix from gcode->txt_after_ok, or "unknown" if no specific error text was set. After reporting the error, the system enters HALT/Alarm state.
|
|
Error:
|
V1 This is the error prefix output in non-GRBL mode when a Gcode command encounters an error. The actual error description follows this prefix. This is part of the same error reporting mechanism as line 388, but for non-GRBL mode systems.
|
|
Error: %s
|
V2 This is a generic error handler that reports any error set in the GCode object. The error message format depends on whether GRBL mode is enabled. After reporting the error, the system enters HALT/Alarm state. If the GCode object has an error but no error message string, it prints "unknown".
|
|
ERROR: ADC failed to setup
|
V2 This error occurs when the ADC (Analog to Digital Converter) system fails to initialize. Without ADC, temperature sensors and other analog inputs cannot be read, preventing temperature control functionality.
|
|
ERROR: Arguments P, X, Y are required
|
V2 This error occurs when using M557 to set probe points without providing all required parameters. The command requires P (point index 0-2), X (x coordinate), and Y (y coordinate) arguments.
|
|
error: axis is out of range
|
V1 This error occurs when the specified axis is beyond the number of motors configured on the robot. For example, specifying axis C when only 3 motors (X, Y, Z) are configured.
|
|
error: axis must be x, y, z, a, b, c
|
V1 This error occurs when an invalid axis is specified for the 'test raw' or 'test acc' command. Only the standard axis identifiers (X, Y, Z, A, B, C) are valid.
|
|
error: Axis X must be homed before setting Homing offset
|
V1 This error occurs when attempting to set X homing offset (M206 X) before the X axis has been homed. Homing must be done first.
|
|
error: Axis Y must be homed before setting Homing offset
|
V1 This error occurs when attempting to set Y homing offset before Y axis has been homed.
|
|
error: Axis Z must be homed before setting Homing offset
|
V1 This error occurs when attempting to set Z homing offset before Z axis has been homed.
|
|
ERROR: calling value after config cache has been cleared
|
V1 This critical error occurs when code attempts to read a configuration value after the config cache has been cleared. The config cache is loaded during initialization and cleared afterward to save memory. Any module trying to access config values after this point will trigger this error and receive a NULL pointer, which will likely cause a crash. This indicates a programming error where config access is happening too late in the initialization sequence.
|
|
ERROR: config file line %s has no value
|
V1 This error occurs when a configuration file line has a key but no value after the whitespace separator. For example, "setting.name " with nothing after it, or if the value position is a comment character '#'. This indicates incomplete configuration entries.
|
|
ERROR: config file line %s is invalid, no key value pair found
|
V1 This error occurs when parsing a configuration file line that doesn't contain a proper key-value pair separated by whitespace. The parser expects format like "key value" but found a line with only a key and no whitespace separator. This happens when a config line is malformed.
|
|
ERROR: config-deltagrid: Not enough memory for grid
|
V2 This error occurs when there's insufficient memory in RAM2 to allocate the grid array for delta leveling. The grid size is determined by the configuration (default 7x7 = 49 points), and if that amount of float memory cannot be allocated from RAM2, this error is triggered.
|
|
ERROR: Configure failed
|
V2 This error message is displayed when configuration fails at any point during startup. The system enters a limited mode where only basic shell commands and SD card access are available, allowing the user to fix the config.ini file.
|
|
ERROR: Configuring robot failed
|
V2 This error occurs when the robot/motion system configuration fails. This is typically due to invalid kinematics settings, missing required parameters, or unsupported arm solution types in the config file.
|
|
ERROR: endstop %d is greater than number of defined motors. Endstops disabled
|
V1 This critical error occurs when an endstop is configured for an axis/motor that doesn't exist. For example, configuring a Z endstop when only X and Y motors are defined. All endstops are disabled when this occurs.
|
|
ERROR: Extruder motor has not been defined in Robot (delta and/or epsilon)
|
V2 This error occurs when the extruder motor has not been defined in the Robot configuration (delta/epsilon axes). The extruder expects the motor to be registered at actuator index A_AXIS+tool_id. This typically means the user forgot to define the appropriate delta/epsilon axis in the config.
|
|
Error: failed to create comms i/o queue
|
V2 This error occurs when the FreeRTOS queue for communication I/O cannot be created, likely due to insufficient memory. This prevents buffering of incoming commands from USB/UART.
|
|
ERROR: failed to create dispatch queue
|
V2 This critical error occurs when the FreeRTOS message queue for dispatching command lines cannot be created, likely due to insufficient memory. The system halts execution as this queue is essential for communication between tasks.
|
|
Error: failed to start ADC
|
V2 This error occurs when the ADC system fails to start its sampling process. Temperature sensors and other analog inputs will not be read.
|
|
Error: failed to start SlowTicker
|
V2 This error occurs when the SlowTicker timer system fails to start after configuration. SlowTicker provides periodic callbacks for modules and is essential for many time-based operations.
|
|
Error: failed to start StepTicker
|
V2 This critical error occurs when the StepTicker (stepper motor pulse generator) fails to start. Without StepTicker, the system cannot generate step pulses for stepper motors, making motion impossible.
|
|
ERROR: Homing cycle failed - check the max_travel settings
|
V1 This error occurs when a homing cycle fails, usually because the endstop was not triggered before reaching max_travel distance. This indicates mechanical issues, disconnected endstops, or incorrect max_travel settings.
|
|
Error: Invalid config, x_size and y_size must be defined
|
V1 This error occurs during CartGridStrategy configuration when x_size or y_size is not defined or is zero. The rectangular grid leveling strategy requires both x_size and y_size to be specified in the configuration.
|
|
Error: is_square has been removed, please use the new rectangular_grid strategy instead
|
V1 This error occurs when the deprecated is_square configuration option is used. Users should migrate to the rectangular_grid strategy instead of using is_square with delta_grid.
|
|
Error: Laser cannot use P%d.%d (P2.0 - P2.5, P1.18, P1.20, P1.21, P1.23, P1.24, P1.26, P3.25, P3.26 only). Laser module disabled.
|
V1 This error occurs when the laser pin is configured to use a pin that doesn't support hardware PWM. The laser requires specific PWM-capable pins. The module disables itself if an invalid pin is configured.
|
|
Error: laser-config: Specified pin is not a valid PWM pin.
|
V2 This error occurs when the laser PWM pin specified in the configuration is not a valid PWM-capable pin. The laser module will not be loaded.
|
|
error: LinearDelta illegal move. HALTED
|
V1 This error occurs when the linear delta kinematics calculation results in NaN (Not a Number) for any actuator position. This happens when trying to move to a position that is mathematically impossible for the delta robot to reach - typically when the requested XYZ position is outside the physical range of the delta arms. The system halts to prevent damage.
|
|
ERROR: MINTEMP or MAXTEMP triggered on %s. Check your temperature sensors!
|
V1 This critical error occurs when the temperature reading is outside the configured min_temp or max_temp range. This indicates a sensor failure, disconnected thermistor, shorted wiring, or actual dangerous temperature condition. The system halts to prevent damage.
|
|
ERROR: MINTEMP or MAXTEMP triggered on %s. Check your temperature sensors!\nHALT asserted - reset or M999 required
|
V2 This critical error occurs when temperature readings fall outside the configured min_temp/max_temp range or return infinity. This indicates sensor failure, disconnection, or actual thermal runaway. The system immediately turns off the heater and enters halt state for safety.
|
|
Error: Motor Driver alarm - reset or M999 required to continue
|
V1 This error occurs when a motor driver chip reports an alarm condition (such as overtemperature, overcurrent, or fault) and the halt_on_alarm configuration option is enabled. The system halts and requires a reset or M999 command to clear the error state.
|
|
Error: mounting: /sd: %d
|
V2 This error occurs when the FAT filesystem on the SD card cannot be mounted. The error code from FatFs is included. This could indicate no card is present, card is not formatted, or filesystem corruption.
|
|
error: Need axis [iterations]
|
V1 This error occurs when the 'test pulse' command is used without specifying an axis. An axis parameter is required, while iterations is optional.
|
|
error: Need axis distance iterations
|
V1 This error occurs when the 'test jog' command is used without all required parameters. The command requires axis, distance, and iteration count parameters to execute the jog test.
|
|
error: Need axis steps steps/sec
|
V1 This error occurs when the 'test raw' or 'test acc' command is used without all required parameters. These commands require axis, number of steps, and steps per second parameters.
|
|
error: Need radius iterations
|
V1 This error occurs when the 'test circle' command is used without required parameters. The command needs radius and iteration count to draw test circles.
|
|
error: Need size iterations
|
V1 This error occurs when the 'test square' command is used without required parameters. The command needs square size and iteration count to draw test squares.
|
|
ERROR: no config file found\r\n
|
V1 This error occurs when the get_config_file() method is called but no valid configuration file has been found. This typically happens during initialization if the expected config file doesn't exist in any of the searched locations.
|
|
ERROR: No valid spindle type defined
|
V1 This error occurs when the configured spindle type is not recognized. Valid spindle types are "pwm", "analog", and "modbus". Any other value in the spindle.type configuration will trigger this error.
|
|
ERROR: No valid spindle type defined
|
V1 This error occurs when no valid spindle type (pwm, analog, modbus, etc.) is defined in the configuration.
|
|
ERROR: No valid spindle VFD type defined
|
V1 This error occurs when the spindle type is configured as "modbus" but the VFD (Variable Frequency Drive) type is not set to a recognized value. Currently, only "huanyang" is supported as a valid VFD type for modbus spindles. The configuration must specify a valid vfd_type.
|
|
ERROR: No valid spindle VFD type defined
|
V1 This error occurs when attempting to create a VFD spindle but no valid VFD type is specified in configuration. Valid types must be defined.
|
|
Error: Not enough memory
|
V1 This error occurs when the system cannot allocate enough memory in the AHB0 memory pool for the grid array. This happens when the grid size is too large for available memory or memory is fragmented.
|
|
Error: Not enough memory
|
V1 This error occurs when the system cannot allocate enough memory in the AHB0 memory pool for the delta grid array. The grid size might be too large for available memory.
|
|
ERROR: only 3 probe points allowed P0-P2
|
V2 This error occurs when trying to set a probe point with an invalid index. The three-point strategy only supports points P0, P1, and P2 (indices 0, 1, 2).
|
|
Error: opening file: /sd/config.ini
|
V2 This critical error occurs when the main configuration file (config.ini) cannot be opened from the SD card. Without this file, the system cannot configure modules and will enter an error state.
|
|
ERROR: opening file: %s
|
V2 This error occurs when the M500 command tries to open the config-override file for writing but fails. This could be due to SD card not mounted, write protection, or filesystem errors.
|
|
error: RotaryDelta illegal move. reset or $X or M999 required
|
V1 This error occurs when a rotary delta move calculation fails and halt_on_error is enabled. The actuator positions are set to zero (safe home position) and the system halts. The user must reset the system or use $X (unlock) or M999 (reset) commands to clear the halt state before continuing.
|
|
Error: setting up sdmmc
|
V2 This error occurs during system startup when the SD/MMC (SD card) hardware interface cannot be initialized. This prevents access to configuration files and other data stored on the SD card.
|
|
Error: Spindle feedback pin has to be on P0 or P2.
|
V1 This error occurs when the spindle feedback pin (used to measure actual RPM via interrupts) is not on port 0 or port 2. Only pins on these ports support the interrupt functionality required for feedback monitoring. The spindle module fails to initialize if an invalid feedback pin is configured.
|
|
Error: Spindle feedback pin has to be on P0 or P2.
|
V1 This error occurs when the configured spindle feedback pin is not on port 0 or port 2. The feedback pin must support external interrupts, which are only available on ports P0 and P2 on the LPC17xx microcontroller. If an invalid port is configured, the module displays this error and deletes itself.
|
|
Error: Spindle PWM pin must be P2.0-2.5 or other PWM pin
|
V1 This error occurs when the configured PWM spindle pin cannot be used for hardware PWM output. The pin must be one of P2.0-2.5 or another pin that supports hardware PWM. If an invalid pin is specified, the spindle module fails to initialize.
|
|
Error: Spindle PWM pin must be P2.0-2.5 or other PWM pin
|
V1 This error occurs when the configured PWM pin for analog spindle control cannot be used for hardware PWM output. The pin must be one of P2.0-2.5 or another pin that supports hardware PWM. This is the same error as in PWMSpindleControl but for the analog spindle variant.
|
|
Error: Spindle PWM pin must be P2.0-2.5 or other PWM pin
|
V1 This error occurs when the configured spindle PWM pin is not a valid hardware PWM pin. The PWM spindle control requires specific pins that support hardware PWM functionality (P2.0-P2.5 or other designated PWM pins). If the configured pin cannot be used for hardware PWM, this error is displayed and the module deletes itself.
|
|
Error: Spindle PWM pin must be P2.0-2.5 or other PWM pin
|
V1 This error occurs in analog spindle control when the configured PWM pin doesn't support hardware PWM. Same requirement as other spindle modules.
|
|
ERROR: Temperature runaway on %s (delta temp %f), HALT asserted, TURN POWER OFF IMMEDIATELY - reset or M999 required
|
V1 This critical thermal runaway error occurs when the temperature drifts too far from the target after initially reaching it. This indicates a serious problem like heater stuck on, thermal sensor failure, or insufficient cooling. System halts immediately for safety.
|
|
ERROR: Temperature runaway on %s (delta temp %f), HALT asserted, TURN POWER OFF IMMEDIATELY - reset or M999 required
|
V2 This critical error occurs when the temperature deviates from the target by more than the configured runaway_range (default 20°C) for more than 8 seconds after reaching target temperature. This indicates thermal runaway or sensor failure. On PrimeAlpha boards, all MOSFETs are turned off as a safety measure.
|
|
ERROR: Temperature took too long to be reached on %s, HALT asserted, TURN POWER OFF IMMEDIATELY - reset or M999 required
|
V1 This critical thermal runaway protection error occurs when the temperature takes too long to reach the target. This indicates a heater failure, insufficient power, or serious configuration error. System halts and power must be turned off immediately.
|
|
ERROR: Temperature took too long to be reached on %s, HALT asserted, TURN POWER OFF IMMEDIATELY - reset or M999 required
|
V2 This critical error occurs when thermal runaway detection determines that the heater is taking too long to reach the target temperature. This could indicate insufficient power, heater failure, or misconfigured PID values. The default timeout is 900 seconds (15 minutes) for heating and can be configured for cooling as well.
|
|
error: tests are not allowed while printing or busy
|
V1 This error occurs when any test command is attempted while the machine is printing or busy executing other operations. Tests require the system to be idle to safely execute movement commands.
|
|
ERROR: UART3/RPI setup failed
|
V2 This error occurs when the UART3 port (typically used for Raspberry Pi communication) fails to initialize. This is only attempted if rpi_port is enabled in configuration.
|
|
error:Alarm lock
|
V1 This error occurs when the system is in HALT state and the user tries to execute a Gcode command that is not in the allowed list of M-codes. In GRBL mode, it returns "error:Alarm lock", otherwise it returns "!!". Only specific M-codes like M105 (get temp), M114 (get pos), M119 (get endstops), M999 (clear halt) are allowed during HALT state.
|
|
error:Alarm lock
|
V2 This error occurs when the system is in HALT/Alarm state and a command is issued that is not in the allowed list. In GRBL mode, this error message is shown. Only specific M-codes (like M999, M105, M114, M119) are allowed while halted. This prevents unsafe operations when the system is in an error state.
|
|
error:at least one of X Y or Z must be specified
|
V2 This error occurs when a G38 probe command is issued without specifying any axis to probe along. At least one of X, Y, or Z parameters must be provided.
|
|
error:at least one of X Y or Z must be specified, and be > or < 0
|
V1 This error occurs during G38 probe command when no axis movement is specified or all movements are zero. At least one axis must have a non-zero movement for the probe to work.
|
|
error:axis out of range %c
|
V1 This error occurs when the jog command specifies an axis that is beyond the number of configured motors. For example, trying to jog axis A when only 3 axes (XYZ) are configured.
|
|
error:bad axis %c
|
V1 This error occurs when the jog command ($J) specifies an invalid axis. Only axes X, Y, Z, A, B, C are valid.
|
|
error:bed dimensions changed read (%f, %f) - config (%f,%f)
|
V2 This error occurs when the bed dimensions in the saved grid file don't match the currently configured bed dimensions. This prevents loading the grid as it was probed for a different bed size.
|
|
ERROR:configure-robot-actuator: no actuator section found
|
V2 This critical error occurs when there is no "actuator" section in the configuration file. Without actuators configured, the robot cannot move. This causes Robot configuration to fail.
|
|
error:Discarding long line
|
V2 This error occurs when an input line exceeds the maximum allowed line length (MAX_LINE_LENGTH). Long lines are discarded to prevent buffer overflows. This typically happens with malformed G-code or excessively long commands.
|
|
Error:error writing to file.
|
V1 This error occurs during file upload (M28/M29 sequence) when writing data to the file fails. This typically happens when the SD card becomes full, is removed during upload, encounters a hardware error, or becomes write-protected. The upload is aborted and the file handle is closed.
|
|
error:Failed to open grid %s
|
V1 This error occurs when attempting to load a delta grid (M375) but the file cannot be opened, usually because it doesn't exist or SD card is not mounted.
|
|
error:Failed to open grid %s
|
V2 This error occurs when the system cannot open the grid file for reading. The file may not exist or there could be SD card issues.
|
|
error:Failed to open grid %s
|
V2 This error occurs when attempting to load a grid file (M375) that doesn't exist or cannot be opened for reading from the SD card.
|
|
error:Failed to open grid file %s
|
V1 This error occurs when the system cannot open the grid file for writing. This is usually due to SD card not being present, not mounted, write-protected, or full.
|
|
error:Failed to open grid file %s
|
V1 This error occurs when the delta grid file cannot be opened for writing, usually due to SD card issues.
|
|
error:Failed to open grid file %s
|
V2 This error occurs when the system cannot open the grid file for writing. This could indicate SD card issues or filesystem problems.
|
|
error:Failed to open grid file %s
|
V2 This error occurs when the system cannot open the grid file (/sd/delta.grid) for writing. This typically happens when the SD card is not mounted, is write-protected, or there's a filesystem error.
|
|
error:Failed to read grid
|
V1 This error occurs when reading grid data from file fails, indicating file corruption or read error while loading the probe grid.
|
|
error:Failed to read grid
|
V2 This error occurs when reading the actual grid height data from the file fails.
|
|
error:Failed to read grid
|
V2 This error occurs when reading grid point data from the saved file fails, typically due to file corruption or incomplete file.
|
|
error:Failed to read grid radius
|
V1 This error occurs when reading the grid radius from file fails, indicating file corruption or read error.
|
|
error:Failed to read grid radius
|
V2 This error occurs when reading the grid radius from the saved file fails, similar to the grid size read error.
|
|
error:Failed to read grid size
|
V1 This error occurs when reading the grid size from file fails, indicating file corruption or read error.
|
|
error:Failed to read grid size
|
V2 This error occurs when reading the grid size from the file fails, indicating file corruption or read error.
|
|
error:Failed to read grid size
|
V2 This error occurs when reading the grid size from the saved file fails, typically due to a corrupted file or SD card read error.
|
|
error:Failed to read grid x size
|
V2 This error occurs when reading the physical bed X dimension from the grid file fails.
|
|
error:Failed to read grid y size
|
V2 This error occurs when reading the physical bed Y dimension from the grid file fails.
|
|
error:Failed to write grid
|
V1 This error occurs when writing grid data to file fails, indicating a disk write error while saving the probe grid.
|
|
error:Failed to write grid
|
V2 This error occurs when writing the actual grid height data to the file fails.
|
|
error:Failed to write grid
|
V2 This error occurs when writing the grid data points to the file fails during the save operation. This happens if any of the grid point values cannot be written to disk.
|
|
error:Failed to write grid radius
|
V1 This error occurs when writing the grid radius to file fails, indicating a disk write error.
|
|
error:Failed to write grid radius
|
V2 This error occurs when writing the grid radius parameter to the file fails, similar to the grid size write error.
|
|
error:Failed to write grid size
|
V1 This error occurs when writing the grid size to file fails, indicating a disk write error.
|
|
error:Failed to write grid size
|
V2 This error occurs when writing the grid size parameter to the file fails. This could happen due to SD card errors, disk full, or hardware issues.
|
|
error:Failed to write grid x size
|
V1 This error occurs when writing the grid X size to the file fails. This indicates a disk write error, possibly due to SD card being full or hardware failure.
|
|
error:Failed to write grid x size
|
V2 This error occurs when writing the grid X size to the file fails, indicating SD card write error or filesystem corruption.
|
|
error:Failed to write grid y size
|
V1 This error occurs when writing the grid Y size to the file fails in the new file format. Indicates a disk write error.
|
|
error:Failed to write grid y size
|
V2 This error occurs when writing the grid Y size to the file fails.
|
|
error:Failed to write x_size
|
V2 This error occurs when writing the physical bed X dimension to the grid file fails.
|
|
error:Failed to write y_size
|
V2 This error occurs when writing the physical bed Y dimension to the grid file fails.
|
|
error:grid size is different read %d - config %d
|
V1 This error occurs when loading a grid file that was created with a different grid size than currently configured. The grid size in the file must match the configured grid size.
|
|
error:grid size is different read %d - config %d
|
V2 This error occurs when the grid size stored in the saved grid file doesn't match the current configuration. For example, if the grid was saved with a 7x7 configuration but the config now specifies 9x9, this error will be triggered.
|
|
error:grid size x is different read %d - config %d
|
V2 This error occurs when the grid X size in the saved file doesn't match the configured grid X size. This prevents loading the grid as it wouldn't match the current configuration.
|
|
error:grid size y is different read %d - config %d
|
V2 This error occurs when the grid Y size in the saved file doesn't match the configured grid Y size.
|
|
error:Illegal combination of probe axis
|
V2 This error occurs when the axis parameter passed to probe_XYZ has an invalid value. This is an internal error that shouldn't occur under normal circumstances as the axis validation happens earlier in the code.
|
|
error:illegal option %c
|
V1 This error occurs when the jog command ($J) is used with an unrecognized option flag. Valid options are -C (continuous mode) and -R (send ok when done).
|
|
error:Invalid statement
|
V1 This error occurs when a GRBL-style $ command is used with an unrecognized command character. Valid $ commands include $G, $I, $X, $#, $H, $S, and $J.
|
|
error:Invalid statement
|
V2 This error is sent when a command starting with '$' (a special system command) is not recognized or cannot be dispatched. This indicates an invalid special command was entered.
|
|
Error:invalid tool: %u
|
V1 This error occurs during M6 tool change when the specified tool number is invalid or the tool is null.
|
|
error:no delta jog specified
|
V1 This error occurs when the jog command is parsed but no actual axis movements were specified. At least one axis must have a non-zero delta value.
|
|
error:no endstop module found
|
V1 This error occurs during M206 command processing when the endstop module cannot be found or accessed. The rotary delta calibration requires the endstop module to retrieve and set homing offsets. If the endstop module is not loaded or accessible via PublicData, this error is returned.
|
|
error:no endstop module found
|
V1 This error occurs during M306 command processing when the endstop module cannot be found or accessed. Similar to the M206 error, the M306 calibration command requires access to the endstop module to retrieve and update homing offsets for rotary delta calibration.
|
|
error:No grid to save
|
V1 This error occurs when attempting to save a grid (M374) that hasn't been created yet. A grid must be generated first using G31/G32 before it can be saved.
|
|
error:No grid to save
|
V1 This error occurs when attempting to save a delta grid (M374) that hasn't been probed yet. A grid must be created using G31 before it can be saved.
|
|
error:No grid to save
|
V2 This error occurs when trying to save grid data but no grid has been probed yet. A grid must be created via G29 before it can be saved.
|
|
error:No grid to save
|
V2 This error occurs when attempting to save a grid (M374) that hasn't been populated with probe data yet. The grid is initialized with very large negative numbers (-1e6F) to indicate unallocated/unprobed points, and if the first element is still negative, it means no probing has been done.
|
|
error:No move detected or too small
|
V1 This error occurs when the requested probe move is too small to execute or cannot be performed. The move distance might be below the minimum threshold for the robot to execute.
|
|
error:Not enough memory to run continuous mode
|
V1 This error occurs when continuous jog mode is requested but there is insufficient memory to allocate the required buffers. Continuous mode requires extra memory to maintain the movement queue.
|
|
error:Nothing set as probe failed or not run
|
V1 This error occurs during M306 L1 command processing when no valid probe position is available. This happens if G30 probe command has not been run yet or if the last probe operation failed. The M306 L1 command requires a successful probe to determine the angle offset.
|
|
error:Only G38.2 and G38.3 are supported
|
V2 This error occurs when a G38 probe command is issued with an unsupported subcode. Only G38.2 (straight probe with error) and G38.3 (straight probe without error) are implemented. Other G38 variants (G38.4, G38.5) are not supported.
|
|
error:Only G38.2 to G38.5 are supported
|
V1 This error occurs when using G38 probe commands with an invalid subcode. Only G38.2, G38.3, G38.4, and G38.5 are supported for probing operations. Other subcodes are not implemented.
|
|
error:Unable to load grid in only_by_two_corners mode
|
V2 This error occurs when trying to load a saved grid while in "only_by_two_corners" mode. Grid loading is not supported in this mode.
|
|
error:Unable to save grid in only_by_two_corners mode
|
V1 This error occurs when attempting to save a grid (M374) while in two-corners mode. Grids cannot be saved in this mode because the grid dimensions and positions vary based on the two-corner parameters.
|
|
error:Unable to save grid in only_by_two_corners mode
|
V2 This error occurs when trying to save the grid data while in "only_by_two_corners" mode. Grid saving is not supported in this mode.
|
|
error:Unable to save grid with size different from configured
|
V1 This error occurs when attempting to save a grid that was created with different dimensions than configured. The current grid size must match the configured grid size for saving.
|
|
error:Unable to save grid with size different from configured
|
V2 This error occurs when the probed grid size doesn't match the configured grid size, indicating a configuration mismatch or corrupted grid data.
|
|
error:unknown option %s
|
V1 This error occurs when the 'get' command is used with an unrecognized option. Valid options include temp, fk, ik, pos, wcs, state, and status. Any other option will trigger this error.
|
|
error:Unsupported command
|
V1 This error occurs when an unsupported M command related to endstops is issued.
|
|
error:Unsupported command - %s
|
V1 This error occurs when a console command is entered that is not recognized by the command parser. The unrecognized command name is displayed in the error message.
|
|
error:Unsupported command - %s
|
V2 This error occurs when a lowercase command (not starting with '$') is not recognized by any registered command handler. The command name is included in the error message to help the user identify the problem.
|
|
error:usage: get [fk|ik] [-m] x[,y,z]
|
V1 This error occurs when the 'get fk' or 'get ik' command is used with incorrect or missing parameters. The command requires at least an x coordinate value and optionally y and z coordinates for forward/inverse kinematics calculations.
|
|
error:Z cannot be probed at the same time as X or Y
|
V2 This error occurs when a G38 probe command tries to probe in Z axis combined with X or Y axes. Z probing must be done separately from XY probing. You can probe XY together, or Z alone, but not Z+X or Z+Y or Z+X+Y.
|
|
error:ZProbe not connected.
|
V1 This error occurs during G38 probe command processing when the ZProbe pin is not configured. The probe must be connected and defined before G38 probing can be used.
|
|
error:ZProbe triggered before move, aborting command.
|
V1 This error occurs in G38 probe operations when the probe is already triggered before the move begins. The command is aborted to prevent errors.
|
|
error:ZProbe triggered before move, aborting command.
|
V2 This is the G38-specific version of the probe-already-triggered error. Occurs when attempting a G38.2 or G38.3 straight probe command but the probe is already triggered at the start.
|
|
ETH: PHY TIMEOUT\n
|
V1 This error occurs during Ethernet MAC initialization when waiting for the PHY chip hardware reset to complete. The code waits for EMAC_PHY_RESP_TOUT iterations for the reset and power-down flags to clear. If the timeout expires, it indicates the PHY chip is not responding to the reset command, suggesting a hardware failure or communication problem.
|
|
Exception
|
V1 Runtime error called when an assertion fails. This is the ARM EABI assertion handler.
|
|
Exception
|
V1 This error is triggered when an unhandled C++ exception occurs in GCC toolchain builds. The `__verbose_terminate_handler` is called by the C++ runtime when terminate() is invoked, typically due to an uncaught exception. This will print "Exception" and halt the system with the error() macro (which displays the message via USB serial and stops execution).
|
|
Exec format error
|
V2 POSIX errno definition for executable format errors. Not typically used in embedded contexts but defined for POSIX compatibility.
|
|
failed
|
V2 This error occurs when disk initialization fails in the low-level disk I/O test. The STA_NOINIT flag indicates the storage device could not be initialized, possibly due to no card present, card not formatted, or hardware issues.
|
|
failed
|
V2 This error occurs when the disk I/O control command to get sector count fails. This indicates the storage device is not responding properly to commands.
|
|
failed
|
V2 This error occurs when the disk I/O control command to get sector size fails. The device may not support this query or is malfunctioning.
|
|
failed
|
V2 This error occurs when the disk I/O control command to get erase block size fails. This is a non-fatal error as block size information may not be available on all devices.
|
|
failed
|
V2 This error occurs when a disk write operation fails during testing. The storage device may be write-protected, full, or experiencing hardware failures. Multiple similar error messages appear throughout the disk I/O test at different return codes (6-24).
|
|
Failed DAD test, not valid
|
V2 IPv6 address state definition indicating the address failed Duplicate Address Detection (DAD) and cannot be used. This occurs when another host on the network is already using the same IPv6 address.
|
|
Failed to allocate pin
|
V2 This error occurs when a GPIO pin cannot be configured as an output during LED testing. This typically happens if the pin is already in use, the pin designation is invalid, or there's a hardware configuration problem.
|
|
Failed to configure Player
|
V2 This warning occurs during system initialization when the Player module fails to configure properly from the configuration file. The Player is responsible for playing G-code files from SD card. Configuration failure is non-fatal but player functionality will not be available.
|
|
failed to create dispatch queue
|
V2 This error occurs during system initialization when the FreeRTOS queue creation for the message dispatch system fails. This is a critical error that indicates the system has run out of memory or heap space to allocate the queue. The queue is used to dispatch commands from multiple sources (USB serial, UART serial, Network, SDCard player thread) to the command processor.
|
|
failed to load configuration override
|
V2 This error message is sent in response to M501 command when the configuration override file cannot be loaded. The file may not exist or may not be readable.
|
|
failed to open file: %s.
|
V1 This error occurs when the 'upload' command cannot open the destination file for writing. This can happen due to invalid filename, write protection, SD card full, or SD card access issues.
|
|
Failed to resolve server hostname
|
V2 SMTP result code indicating DNS resolution failure for the mail server hostname. This occurs when the DNS lookup cannot resolve the mail server name to an IP address.
|
|
Failed to resolve server hostname
|
V2 HTTP client result code indicating DNS resolution failure for the server hostname. This occurs when the DNS lookup cannot resolve the server name to an IP address.
|
|
Failed: Insufficient drive size to test
|
V2 This error occurs when the storage device has fewer than 128 sectors, making it too small to perform comprehensive disk I/O tests.
|
|
Failed: Read data differs from the data written
|
V2 This error occurs when data read back from the storage device doesn't match what was written. This indicates data corruption, faulty storage media, or communication errors with the device.
|
|
FATAL: CDC setup failed
|
V2 This critical error occurs when USB CDC (Communications Device Class) setup fails. The USB communication interface cannot be initialized, preventing USB serial communication with the host computer.
|
|
FATAL: malloc/sbrk out of memory
|
V2 This fatal error is sent directly to UART when the system runs out of heap memory and malloc fails. This is a FreeRTOS hook function that is called when memory allocation fails. The system cannot use printf here as that might allocate memory.
|
|
FATAL: planner failed to initialize, out of memory?
|
V2 This critical error occurs when the motion planner cannot allocate the block queue, typically due to insufficient memory. The system cannot function without the planner and will enter error mode.
|
|
FATAL: UART setup failed
|
V2 This error occurs when the UART (Universal Asynchronous Receiver/Transmitter) hardware setup fails during system initialization in test mode. The system halts with a breakpoint when this critical communication interface cannot be initialized.
|
|
FATAL: UART setup failed
|
V2 This critical error occurs very early in main() when the primary UART hardware initialization fails. This prevents debug output and serial communication, making the system very difficult to diagnose or use.
|
|
FATAL:configure-robot: setup_tmc2660 failed for %s
|
V2 This fatal error occurs when TMC2660 driver configuration fails for an actuator on the PrimeAlpha board. This causes robot configuration to fail completely. Check TMC2660 configuration settings and SPI communication.
|
|
fid already in use
|
V1 This error occurs when attempting to create or assign a file identifier (fid) that is already in use by another file or directory reference in the Plan9 filesystem protocol. Each fid must be unique within a session, and this error prevents duplicate assignments that would cause conflicts.
|
|
fid unknown or out of range
|
V1 This error occurs in the Plan9 network filesystem protocol when a file identifier (fid) being referenced is not known to the system or exceeds the valid range. The fid is used to track open files and directories in the 9P protocol. This error is triggered when operations attempt to use an fid that was never created or has already been closed, or when the fid number exceeds the maximum allowed value.
|
|
Filament Detector has detected a bulge in the filament
|
V1 This message occurs when the bulge detector pin is triggered, indicating that the filament has an abnormal bulge that could cause printing issues. The bulge detector is an optional sensor that monitors filament diameter irregularities.
|
|
Filament Detector has detected a filament jam
|
V1 This message occurs when the filament encoder detects that the extruder has moved but the filament has not moved through the detector (no pulses received). This indicates a filament jam, where the extruder is trying to push filament but it's stuck or jammed.
|
|
File descriptor in bad state
|
V2 POSIX errno definition for file descriptor in bad state. This error occurs when operations are attempted on a file descriptor that is in an invalid state for that operation.
|
|
File exists
|
V1 This error occurs when attempting to create a file or directory that already exists in the filesystem. This is typically returned from the Tcreate operation when mkdir() fails because the target directory name is already taken, or when a file creation is attempted at a path that already exists.
|
|
File not found
|
V2 This error occurs when the play command cannot open the specified G-code file. The file path may be incorrect or the SD card may not be properly mounted.
|
|
File not found: %s
|
V1 This error occurs when the 'cat' command attempts to open a file that doesn't exist or cannot be accessed for reading. The filename parameter is displayed to help identify which file was not found.
|
|
File not found: %s
|
V1 This error occurs when the 'load' command attempts to load a configuration override file that doesn't exist or cannot be opened. The specified filename is displayed in the error message.
|
|
File not found: %s
|
V1 This error occurs when the 'md5sum' command attempts to open a file that doesn't exist or cannot be accessed. The filename is displayed in the error message.
|
|
file.open failed
|
V2 This error occurs when M23 (select file for printing) fails to open the specified file. The file may not exist, may be inaccessible, or the SD card may not be mounted properly.
|
|
Finding bed failed, check the max_travel and initial height settings
|
V2 This error occurs when the initial bed-finding operation fails during grid probing. This typically happens when the probe doesn't trigger within the max_travel distance, indicating either incorrect settings or a malfunctioning probe.
|
|
Finding bed failed, check the maxz and initial height settings
|
V1 This error occurs when the findBed() operation fails, usually because the probe doesn't trigger before reaching max_z distance or the initial_height is set incorrectly.
|
|
first one seems to fail, but works next time
|
V1 This is a comment indicating a known issue where the first disk_initialize() call to the external SD card may fail, but subsequent calls work correctly. This is likely due to timing issues or the SD card needing multiple initialization attempts. The code calls it once knowing it might fail, expecting the next access to succeed.
|
|
FLASHCFG: Invalid values of reserved bits!
|
V1 Flash accelerator configuration register has invalid reserved bits set.
|
|
For packet-oriented interfaces, the number of inbound packets that contained errors
|
V2 MIB-II statistics documentation describing ifinerrors counter. This tracks inbound packets/frames that had errors preventing delivery to higher protocol layers.
|
|
Function not implemented
|
V1 This error is returned when an unsupported or unimplemented 9P protocol operation is requested. It's also used when operations with unsupported permission bits are attempted (such as certain DMDIR flags that aren't supported by the implementation).
|
|
HALTED, M999 or $X to exit HALT state
|
V1 This message is displayed when the system is halted (via Ctrl+X) in non-GRBL mode. It informs the user how to exit the halt state by either sending M999 G-code command or the $X command. The receive buffer is flushed to clear any pending commands.
|
|
HALTED, M999 or $X to exit HALT state\r\n
|
V1 This message is displayed when the user presses CTRL-X in non-GRBL mode to halt the system. It informs the user that the system is halted and provides instructions to exit the halted state using either M999 or $X commands.
|
|
handle_incoming_websocket: base64 encode failed
|
V2 This error occurs during WebSocket handshake when base64 encoding of the accept key fails. This is part of the WebSocket protocol upgrade process and indicates a crypto/encoding issue.
|
|
handle_upload: failed to open file for write
|
V2 This error occurs when the HTTP server receives a file upload but cannot open the destination file for writing. This could be due to SD card issues, permissions, or filesystem problems.
|
|
handle_upload: failed to write to file
|
V2 This error occurs when writing uploaded file data to the filesystem fails. This indicates SD card errors or filesystem corruption.
|
|
handle_upload: state error
|
V2 This error occurs when the upload handler encounters an unexpected state, indicating a protocol or state machine error in the upload process.
|
|
Homing cycle failed
|
V2 This error occurs when the homing cycle is interrupted by a halt condition (kill button, limit trigger, etc.). All homed flags are cleared and homing must be restarted.
|
|
http_server_netconn_serve: badly formatted websocket request
|
V2 This error occurs when a WebSocket upgrade request is malformed or missing required headers (like the WebSocket key).
|
|
http_server_netconn_serve: parse_headers failed with err: %d
|
V2 This error occurs when the HTTP header parsing fails, with the specific error code printed. This is a higher-level indication that the HTTP request could not be processed.
|
|
http_server_thread: netconn_accept received error %d, shutting down
|
V2 This critical error occurs when the HTTP server fails to accept a new connection. This causes the HTTP server thread to shut down, making the web interface unavailable.
|
|
I/O error
|
V2 POSIX errno definition for I/O errors. This error occurs when read/write operations to hardware devices fail due to hardware problems or device unavailability.
|
|
I2C pin mapping failed
|
V1 Runtime error when I2C SDA and SCL pins cannot be mapped to the same I2C peripheral, or invalid pins are specified.
|
|
IAP_ADDR_ERROR
|
V2 IAP status code indicating an address parameter is not aligned on a word boundary. This is similar to SRC_ADDR_ERROR and DST_ADDR_ERROR but for operations with a single address parameter.
|
|
IAP_COMPARE_ERROR
|
V2 IAP status code returned by the Compare command when the source and destination data are not equal. Used to verify flash programming was successful by comparing written data with source data.
|
|
IAP_COUNT_ERROR
|
V2 IAP status code indicating the byte count parameter is invalid - either not a multiple of 4 or exceeds the permitted range for the operation. Flash operations must work with word-aligned sizes.
|
|
IAP_DST_ADDR_ERROR
|
V2 IAP status code indicating the destination address is not on the correct boundary. Different flash operations may require different alignment (word boundary or 256-byte boundary).
|
|
IAP_INVALID_BAUD_RATE
|
V2 IAP status code indicating an invalid baud rate was specified for UART configuration via IAP. The baud rate must be within the supported range for the system clock frequency.
|
|
IAP_INVALID_CODE
|
V2 IAP status code indicating an invalid unlock code was provided. Some IAP operations require a specific unlock code (typically 0x0000ABCD) as a safety mechanism to prevent accidental flash modification.
|
|
IAP_INVALID_COMMAND
|
V2 IAP (In-Application Programming) status code indicating an invalid or unrecognized IAP command was called. This occurs when the IAP command code passed to the IAP entry point is not one of the supported commands.
|
|
IAP_INVALID_SECTOR
|
V2 IAP status code indicating the sector number is out of range or the end sector is less than the start sector. Flash sectors are numbered sequentially and range checks must pass.
|
|
IAP_INVALID_STOP_BIT
|
V2 IAP status code indicating an invalid stop bit setting was specified for UART configuration via IAP. Valid stop bit settings are typically 1 or 2 stop bits.
|
|
IAP_PARAM_ERROR
|
V2 IAP status code indicating insufficient parameters were provided or a parameter value is invalid for the requested IAP command. Note the typo in the comment ("nsufficient" should be "insufficient").
|
|
IAP_SRC_ADDR_ERROR
|
V2 IAP status code indicating the source address provided for a copy or compare operation is not aligned on a word boundary (4 bytes). IAP flash operations require word-aligned addresses.
|
|
ignored while in ALARM state
|
V2 This message occurs when trying to manually fire the laser while the system is in ALARM/HALT state. The command is ignored for safety.
|
|
Illegal argument.
|
V2 This error string corresponds to ERR_ARG (-16) error code. It indicates that an illegal or invalid argument was passed to a function.
|
|
Illegal value
|
V2 This is a lwIP error code definition (ERR_VAL = -6) indicating invalid parameter values passed to network functions. This error occurs when a function receives a parameter that is out of range or inappropriate for the requested operation.
|
|
Illegal value.
|
V2 This error string corresponds to ERR_VAL (-6) error code. It indicates that an illegal or invalid value was passed to a function, such as an out-of-range parameter.
|
|
inbound packets tossed because of error
|
V2 Van Jacobson header compression statistics member tracking packets discarded due to decompression errors or other processing failures.
|
|
inbound packets which were chosen to be discarded even though no errors had
|
V2 MIB-II statistics documentation describing ifindiscards counter. This tracks packets discarded intentionally even when valid, typically due to buffer exhaustion.
|
|
Input/output error
|
V1 This is a general I/O error used when file operations fail. It's returned when file open, read, write, or seek operations fail, or when directory operations encounter errors. This is used extensively throughout the Plan9 code for filesystem operation failures.
|
|
Insufficient work area to run program
|
V2 This error occurs when the disk I/O test program doesn't have enough buffer space allocated to perform the tests. The buffer must be at least FF_MAX_SS + 4 bytes.
|
|
interrupts in FLASH can't fire while we are setting up SPIFI
|
V2 This comment explains why interrupts must be disabled during SPIFI (Serial Peripheral Flash Interface) setup. Since the code itself is running from FLASH via SPIFI, and SPIFI memory mode must be disabled during configuration, any interrupt handlers stored in FLASH cannot execute during this period. If an interrupt fired while SPIFI was being configured, it would cause a hard fault when trying to fetch the interrupt vector or handler code from inaccessible FLASH memory.
|
|
invalid - 5 registers required
|
V2 This error occurs when the setregs command doesn't provide exactly 5 register values. The TMC2660 driver requires 5 register values to be set.
|
|
Invalid argument
|
V2 POSIX errno definition for invalid argument. This is one of the most common errors, occurring when function parameters are invalid, out of range, or inappropriate for the requested operation.
|
|
Invalid exchange
|
V2 POSIX errno definition for invalid exchange. This is a Linux-specific error code not commonly used in embedded systems.
|
|
invalid flags
|
V1 This error occurs when file open flags don't match any valid combination. When OPEN_INVALID is returned, the file open operation fails and returns NULL. This typically happens when unsupported flag combinations are passed to the file open function.
|
|
Invalid frame, ignore it and free buffer.
|
V1 This error condition occurs when an ethernet frame is received with errors or exceeds the MTU size. The RINFO_ERR_MASK checks for multiple error flags including CRC errors, symbol errors, length errors, alignment errors, and receive overrun. When detected, the frame is discarded and the buffer is freed.
|
|
Invalid hostname: %s\n
|
V1 This error occurs when the hostname specified in the configuration for DHCP is invalid. A valid hostname must be 63 characters or less, start with a letter, contain only letters/numbers/hyphens, and not end with a hyphen. The network will still attempt to start but without the hostname.
|
|
invalid ip address: %s
|
V2 This error occurs when the IP address configured in the network section is not a valid IP address format. The `ipaddr_aton` function failed to parse the string.
|
|
Invalid IP address: %s\n
|
V1 This error occurs when the IP address specified in the configuration (network.ip_address) cannot be parsed. A valid IP address must be in dotted-decimal format (e.g., 192.168.1.100). If this error occurs along with other IP configuration errors, network initialization is aborted.
|
|
invalid ip gateway: %s
|
V2 This error occurs when the gateway IP address configured in the network section is not a valid IP address format.
|
|
Invalid IP gateway: %s\n
|
V1 This error occurs when the IP gateway address specified in the configuration (network.ip_gateway) cannot be parsed. A valid gateway must be in dotted-decimal format (e.g., 192.168.1.1). If this error occurs along with other IP configuration errors, network initialization is aborted.
|
|
Invalid IP Mask: %s\n
|
V1 This error occurs when the IP netmask specified in the configuration (network.ip_mask) cannot be parsed. A valid netmask must be in dotted-decimal format (e.g., 255.255.255.0). If this error occurs along with other IP configuration errors, network initialization is aborted.
|
|
invalid ip netmask: %s
|
V2 This error occurs when the network mask configured in the network section is not a valid netmask format. The `ipaddr_aton` function failed to parse the netmask string.
|
|
Invalid length error
|
V2 Statistics counter for packets with invalid length fields. This tracks packets where the length field doesn't match the actual packet size or is out of valid range.
|
|
Invalid MAC address: %s\n
|
V1 This error occurs when the MAC address specified in the configuration file (network.mac_override) is not in the correct format. The MAC address must be exactly 17 characters in the format XX:XX:XX:XX:XX:XX with hexadecimal values. Network initialization is aborted if this error occurs.
|
|
invalid motor number
|
V2 This error occurs when the setregs command is given a motor number that exceeds the number of configured motors. Motor numbers start at 0.
|
|
invalid no registers
|
V2 This error occurs when the setregs command is called without any register values.
|
|
Invalid number of bits (%d) in serial format, should be 5..8
|
V1 Runtime error when serial data bits are configured outside the valid range of 5-8 bits.
|
|
Invalid request code
|
V2 POSIX errno definition for invalid request code. This is a Linux-specific error code.
|
|
Invalid request descriptor
|
V2 POSIX errno definition for invalid request descriptor. This is a Linux-specific error code.
|
|
Invalid serial parity setting
|
V1 Runtime error when an invalid parity setting is specified (not None, Odd, Even, Forced1, or Forced0).
|
|
Invalid slot
|
V2 POSIX errno definition for invalid slot. This is a Linux-specific error code.
|
|
Invalid stop bits specified
|
V1 Runtime error when stop bits are not 1 or 2.
|
|
IPv6 netif zone check failed
|
V2 Assertion macro to verify IPv6 address zone matches the network interface. This check fails if a scoped IPv6 address has a zone that doesn't correspond to the given netif.
|
|
IPv6 zone check failed
|
V2 Assertion macro to verify IPv6 address zone validity. This check fails if a scoped IPv6 address (link-local, site-local) doesn't have a zone identifier when required, or has one when not appropriate.
|
|
LCD_INTMSK_BERIM
|
V2 LCD controller interrupt mask bit for AHB master error interrupts. This enables interrupt generation when the LCD controller's AHB master encounters a bus error.
|
|
Limit switch was hit - reset or M999 required
|
V2 This critical error occurs when a limit switch is triggered during normal movement (not homing). The system enters a halt state and requires a reset or M999 command to clear. This indicates the machine has moved beyond its safe travel limits.
|
|
load config failed
|
V1 This error occurs during unit testing when the TemperatureSwitch module fails to load its configuration. The test expects a valid TemperatureSwitch object after calling load_config(), and if it receives nullptr, the configuration loading has failed.
|
|
load config failed
|
V1 This error occurs in a different test case when the TemperatureSwitch module fails to load its configuration for the edge trigger test. Similar to the previous error, it indicates that the configuration loading returned nullptr instead of a valid object.
|
|
Local error lead to test abort
|
V2 lwIPerf (network performance testing tool) result code indicating the test was aborted due to a local error condition.
|
|
Local memory error
|
V2 HTTP client result code indicating local memory allocation failure during HTTP client operations.
|
|
log an error message and die(1)
|
V2 PPP logging function declaration for fatal errors. This function logs an error message and terminates the PPP connection or process. Used for unrecoverable errors.
|
|
Low-level netif error
|
V2 This is a lwIP error code definition (ERR_IF = -12) indicating low-level network interface errors. This error occurs when there are hardware-level issues with the network interface, such as driver errors or interface not ready.
|
|
Low-level netif error.
|
V2 This error string corresponds to ERR_IF (-12) error code. It indicates a low-level error in the network interface layer, such as hardware failure or driver issues.
|
|
LPC43XX_CORE_M0APP or LPC43XX_CORE_M0SUB must be defined
|
V2 This compile-time error occurs when compiling for the LPC43XX chip with CORE_M0 defined, but neither LPC43XX_CORE_M0APP nor LPC43XX_CORE_M0SUB is specified. The LPC43XX has multiple Cortex-M0 cores (M0APP for application and M0SUB for subsystem), and the build system needs to know which one is being targeted.
|
|
MAINCLKSEL: Invalid values of reserved bits!
|
V1 Main clock source selection register has invalid reserved bits set.
|
|
MAINCLKSEL: WDT Oscillator selected but FREQSEL is undefined!
|
V1 When the watchdog oscillator is selected as main clock source, the frequency selection bits (FREQSEL) must be defined.
|
|
memory allocation failures
|
V2 Debug level comment describing the type of errors that should be logged at the SERIOUS level, primarily memory allocation failures.
|
|
Misc error
|
V2 Statistics counter for miscellaneous errors that don't fit into other categories. This is a catch-all for various error conditions.
|
|
MotorDriverControl %c ERROR: chip select not defined
|
V1 This error occurs when the SPI chip select pin for the motor driver is not defined or is set to "nc" (not connected). A valid chip select pin is required for SPI communication with the motor driver chip.
|
|
MotorDriverControl %c ERROR: chip type not defined
|
V1 This error occurs when the chip type for the motor driver is not specified in the configuration. The chip type (e.g., DRV8711 or TMC2660) must be defined to properly initialize the driver.
|
|
MotorDriverControl %c ERROR: Unknown chip type: %s
|
V1 This error occurs when the specified chip type is not recognized. Currently supported chip types are "DRV8711" and "TMC2660". Any other chip type specified in the configuration will trigger this error.
|
|
MotorDriverControl %c ERROR: Unknown SPI Channel: %d
|
V1 This error occurs when an invalid SPI channel number is specified. Only SPI channels 0 and 1 are supported on the board. The SPI channel determines which pins are used for SPI communication.
|
|
MotorDriverControl ERROR: axis must be one of XYZABC
|
V1 This error occurs when the specified axis is not one of the valid axis identifiers (X, Y, Z, A, B, or C). The axis specification must be a single character from this set.
|
|
MotorDriverControl ERROR: axis not defined
|
V1 This error occurs when configuring a motor driver control instance and neither the 'axis' nor the deprecated 'designator' configuration parameter has been specified. The axis/designator is required to identify which motor axis the driver controls.
|
|
MSD is disabled
|
V1 This is an informational message (though labeled as error in context) indicating that USB Mass Storage Device (MSD) functionality has been disabled either via the DISABLEMSD compile flag or through the msd_disable configuration option. This means the SD card won't be accessible as a USB drive when connected to a computer.
|
|
Net interface failed to initialize
|
V2 This critical error occurs when the network interface fails to initialize. This could be due to hardware failure, driver issues, or LWIP stack problems. Network functionality will not be available.
|
|
Network not started due to errors in config
|
V1 This error is printed when network initialization fails due to invalid configuration. It appears after specific configuration errors (invalid MAC address, IP address, netmask, or gateway). Network functionality will not be available.
|
|
Network not started due to errors in config
|
V1 This error is printed when network initialization fails due to one or more invalid IP configuration parameters (IP address, netmask, or gateway). Network functionality will not be available when this error occurs.
|
|
No CHIP_* definition is defined
|
V2 This compile-time error occurs when no chip family definition (like CHIP_LPC43XX or CHIP_LPC18XX) is provided. The CMSIS header files need to know which NXP microcontroller chip family is being targeted to include the correct peripheral definitions and memory maps. This must be defined in the build system.
|
|
No disk, or could not put SD card in to SPI idle state
|
V1 This error occurs during SD card initialization when the card fails to respond correctly to the CMD0 (GO_IDLE_STATE) command. This could mean no SD card is inserted, the card is damaged, there's a connection problem, or the card doesn't support SPI mode. The firmware was unable to initialize the SD card into SPI idle state.
|
|
No file loaded
|
V2 This error occurs when M26 (reset print) is issued but no file is currently loaded for printing. A file must be selected with M23 before it can be reset.
|
|
No network detected
|
V1 This error occurs when the 'net' command is used but no network interface has been detected or initialized. This typically means the network module is not enabled or has failed to initialize.
|
|
No strategy found to handle G%d
|
V1 This error occurs when a leveling G-code (G29, G31, G32) is issued but no leveling strategy is configured or enabled to handle it. A leveling strategy must be configured in the config file (delta calibration, three-point, delta grid, or cart grid).
|
|
No strategy found to handle G%d
|
V2 This error occurs when a G-code command (G29-G32, except G30) is issued but no configured strategy (leveling or calibration) can handle it. This could mean no strategy is configured or the configured strategy doesn't support that particular G-code.
|
|
No such file or directory
|
V1 This error occurs when attempting to access a file or directory that doesn't exist in the filesystem. This is commonly returned during walk operations when a path component cannot be found, or when operations reference non-existent files.
|
|
Not connected.
|
V2 This error string corresponds to ERR_CONN (-11) error code. It indicates that the socket is not connected and the requested operation requires an active connection.
|
|
Not in idle state after sending CMD8 (not an SD card?)
|
V1 This error occurs when the SD card's response to CMD8 (SEND_IF_COND) is unexpected. CMD8 is used to determine if the card is SD v2.x or v1.x. If the response doesn't match either expected value, it suggests the inserted card may not be a valid SD card or is malfunctioning.
|
|
Not supported compiler type
|
V2 Duplicate of the same error from config_43xx/cmsis_43xx.h. Triggered when using an unsupported compiler.
|
|
Not supported compiler type
|
V2 This error occurs when compiling the M0 subsystem code with an unsupported compiler type.
|
|
Not supported compiler type
|
V2 This error occurs when compiling the M0 application processor code with an unsupported compiler type. Only recognized compilers (ARM, GCC, IAR, etc.) are supported.
|
|
Not supported compiler type
|
V2 This compile-time error occurs when compiling with a compiler that is not recognized by the CMSIS headers for LPC43XX. The supported compilers are checked earlier in the file, and if none match, this error is triggered. The developer needs to use a supported compiler (ARM, GCC, IAR, etc.).
|
|
Not supported compiler type
|
V2 This compile-time error occurs when attempting to compile the LPC18XX CMSIS headers with an unsupported or unrecognized compiler. The supported compilers include ARM Compiler, GCC, IAR, and others checked earlier in the file.
|
|
not_ready_error
|
V2 This counter is incremented when an ADC channel is sampled but the data is not ready (ADC_DR_DONE_STAT not set) or the read operation fails. The comment notes this is primarily meaningful in polled mode (burst mode) rather than interrupt mode, since interrupt mode only fires when data is ready. This error tracking can help debug timing issues or ADC configuration problems.
|
|
NOTE we cannot create these once ADC is running
|
V2 This comment warns that ADC objects cannot be created after the ADC system has started running. The constructor checks both that there's room for more instances (`ninstances < Adc::num_channels`) and that the ADC is not running (`!running`). Creating ADC instances while the ADC is active could cause conflicts or undefined behavior in the interrupt handlers and sampling routines.
|
|
Nothing set NOTE Usage is M143 S0 P300 where <S> is the hotend index and <P> is the maximum temp to set
|
V2 This informational message occurs when using M143 to set maximum temperature without providing the P parameter. It reminds the user of the correct usage.
|
|
NOTICE: This MCU is deprecated, and cannot guarantee proper function
|
V1 This notice occurs when the firmware detects it is running on an LPC1768 MCU (rather than LPC1769). The LPC1768 is deprecated and may not function properly with current firmware versions. Users should upgrade to LPC1769-based boards.
|
|
ok - Invalid G53
|
V1 This error occurs when G53 (machine coordinate mode) command is used but the last modal command was not G0, G1, G2, or G3. G53 makes the next movement command use machine coordinates, but it requires a valid movement command. If the last modal command was greater than G3, it's invalid.
|
|
ok - Invalid G53
|
V1 This error occurs when G53 is followed by a command that is not G0 or G1. G53 must be used with linear movement commands (G0 or G1) to specify machine coordinates. If the following command is not a G0 or G1, or if there is no G command at all, the G53 is considered invalid.
|
|
Only P0 and P1 supported
|
V2 This error occurs when a G-code probe command uses the P parameter to select a strategy, but specifies a value other than 0 (leveling) or 1 (calibration). Only these two strategy indexes are supported.
|
|
open failed, File: %s.
|
V1 This error occurs during M28 (start upload) command when the system fails to open the specified file for writing. This could happen if the SD card is not present, write-protected, the path is invalid, or there's insufficient space. The filename is extracted from the M28 command line.
|
|
OpenDrain not supported on LPC2368
|
V1 Runtime error when trying to configure a pin in OpenDrain mode on the LPC2368, which doesn't support this pin mode.
|
|
Operation in progress.
|
V2 This error string corresponds to ERR_INPROGRESS (-5) error code. It indicates that an asynchronous operation is still in progress and has not yet completed.
|
|
Operation would block.
|
V2 This error string corresponds to ERR_WOULDBLOCK (-7) error code. It indicates that the operation cannot complete immediately and would block waiting for resources or completion. This is typically used in non-blocking socket operations.
|
|
other error will provide a hint what went wrong, but except for assertions, no real error handling is implemented
|
V2 Comment indicating that mutex creation may fail but there is minimal error handling beyond assertions. Programmers should expect crashes on mutex creation failure rather than graceful degradation.
|
|
out of memory
|
V2 This error occurs when there is insufficient memory to initialize the xmodem transfer buffer. This is a critical error that prevents file transfers.
|
|
Out of memory error
|
V2 This is a lwIP error code definition (ERR_MEM = -1) indicating memory allocation failures in the network stack. This error occurs when the network stack runs out of memory for buffers, control blocks, or other network-related structures.
|
|
Out of memory error
|
V2 Statistics counter for memory allocation failures during packet processing. This tracks when the network stack cannot allocate memory for incoming packets or internal structures.
|
|
Out of memory error.
|
V2 This error string is returned by lwip_strerr() when ERR_MEM (-1) error code is encountered. It indicates that the network stack has run out of memory for buffers, packets, or other dynamic allocations.
|
|
Overtemperature Prewarning
|
V2 This warning occurs when the TMC2660 stepper driver chip detects that its temperature is getting too high. This is a pre-warning level indicating the chip is warm but still functional. Action should be taken to reduce current or improve cooling before it reaches shutdown temperature.
|
|
Overtemperature Shutdown
|
V2 This critical warning occurs when the TMC2660 driver chip has reached its thermal shutdown threshold and has shut down to prevent damage. The motor will not operate until the chip cools down. This indicates a serious thermal management problem that must be addressed (reduce current, improve heat sinking, check for shorts).
|
|
PARAM_INVALID_FREQ
|
V1 Error code for power parameter setup when the specified frequency is out of range. Valid range is greater than 0 and up to 50 MHz.
|
|
PARAM_INVALID_MODE
|
V1 Error code when an invalid power parameter mode is specified. Valid modes are PARAM_DEFAULT (0), PARAM_CPU_PERFORMANCE (1), PARAM_EFFICIENCY (2), and PARAM_LOW_CURRENT (3).
|
|
parse_headers: bad header
|
V2 This error occurs when an HTTP header cannot be parsed correctly, indicating malformed HTTP requests from the client.
|
|
parse_headers: hdrbuf pbuf_copy_partial failed
|
V2 This error occurs when copying HTTP headers from the network buffer fails during header parsing.
|
|
parse_headers: methbuf pbuf_copy_partial failed
|
V2 This error occurs when copying the HTTP method (GET, POST, etc.) from the network buffer fails during header parsing.
|
|
parse_headers: reqbuf pbuf_copy_partial failed
|
V2 This error occurs when copying the HTTP request URI from the network buffer fails during header parsing.
|
|
PCLKSEL0: Invalid values of reserved bits!
|
V1 Peripheral clock selection register 0 has invalid reserved bits set.
|
|
PCLKSEL1: Invalid values of reserved bits!
|
V1 Peripheral clock selection register 1 has invalid reserved bits set.
|
|
PCONP: Invalid values of reserved bits!
|
V1 Power control for peripherals register has invalid reserved bits set.
|
|
peer failed to authenticate itself
|
V2 PPP authentication function comment. This callback is invoked when the remote peer fails authentication (wrong username/password).
|
|
PHY reports id %04lX %04lX - not an SMSC 8720A\n
|
V1 This error occurs when the Ethernet PHY chip identification does not match the expected SMSC 8720A chip ID. The firmware reads the PHY ID registers and compares them to the expected value. If they don't match, it means either the wrong PHY chip is installed, there's a hardware problem, or the PHY is not responding correctly.
|
|
pinmap mis-match
|
V1 This fatal error occurs when trying to merge two peripheral pin mappings that are incompatible (neither is NC and they're not equal). This typically happens during peripheral initialization when two conflicting pin assignments are detected. The system will halt after printing this error.
|
|
pinmap not found for peripheral
|
V1 This fatal error occurs when looking up which peripheral corresponds to a given pin, but the pin is not found in the peripheral map table. This indicates an attempt to use a pin with a peripheral it doesn't support, or an invalid pin number. System halts after this error.
|
|
pins on this port cannot generate interrupts\n
|
V1 Runtime error when trying to set up GPIO interrupts on a pin/port that doesn't support external interrupts.
|
|
pins on this port cannot generate interrupts\n
|
V1 This fatal error occurs on LPC1768/LPC2368 when trying to configure a GPIO interrupt on a port other than GPIO0 or GPIO2. The LPC17xx hardware only supports interrupts on these two ports. Attempting to use pins on GPIO1, GPIO3, or GPIO4 for interrupt purposes will trigger this error and halt the system.
|
|
Please use ARM Compiler Toolchain V4.0.677 or later!
|
V1 Same toolchain version check for LPC11U24 device.
|
|
Please use ARM Compiler Toolchain V4.0.677 or later!
|
V1 Another instance of the ARM Compiler version check in the function definitions header.
|
|
Please use ARM Compiler Toolchain V4.0.677 or later!
|
V1 This compile-time error occurs when using an ARM Compiler Toolchain older than version 4.0.677. The CMSIS library requires this minimum version for proper functionality.
|
|
PLL_FREQ_NOT_FOUND
|
V1 Error code returned when the specified frequency cannot be achieved under the specified conditions (mode).
|
|
PLL_INVALID_FREQ
|
V1 Error code returned when the specified PLL frequency is out of the acceptable range. This applies to both input and output frequencies for the main PLL setup.
|
|
PLL_INVALID_MODE
|
V1 Error code returned when an invalid PLL mode is specified. Valid modes are CPU_FREQ_EQU (0), CPU_FREQ_LTE (1), CPU_FREQ_GTE (2), and CPU_FREQ_APPROX (3).
|
|
PLL_NOT_LOCKED
|
V1 Error code returned when the PLL fails to lock. When this occurs, no changes are made to the PLL setup to maintain system stability.
|
|
PLL0CFG: Invalid values of reserved bits!
|
V1 Compile-time validation that PLL0 configuration register doesn't have any reserved bits set. Reserved bits must remain at their default values.
|
|
PLL1CFG: Invalid values of reserved bits!
|
V1 Compile-time validation that PLL1 configuration register doesn't have any reserved bits set.
|
|
ppp_error
|
V2 PPP logging function declaration for error messages. This function is used throughout the PPP stack to log error-level messages.
|
|
ppp_ierrors
|
V2 PPP statistics structure member tracking receive errors. This counter increments for various PPP layer receive errors.
|
|
ppp_oerrors
|
V2 PPP statistics structure member tracking transmit errors. This counter increments for various PPP layer transmission errors.
|
|
Probe failed to complete, check the initial probe height and/or initial_height settings
|
V1 This error occurs when delta grid probing fails to complete successfully. This usually indicates the initial_height setting is too high, the bed is too low, or there are probe connection issues.
|
|
Probe failed to complete, check the initial probe height and/or initial_height settings
|
V2 This error occurs when the G31 probing command fails to complete. This could be due to incorrect initial_height settings, probe not triggering, or the probe hitting the configured max_travel before finding the bed.
|
|
Probe failed to complete, probe not triggered or other error
|
V1 This error occurs during G29 three-point leveling test when probing fails. The probe may not have triggered at one or more points.
|
|
Probe failed to complete, probe not triggered or other error
|
V1 This error occurs during G32 three-point leveling when probing fails at one or more of the three probe points.
|
|
Probe failed to complete, probe not triggered or other error
|
V2 This error occurs when the G29 test probe points command fails. This happens when the probe doesn't trigger at any of the three test points or encounters other errors during the probing process.
|
|
Probe failed to complete, probe not triggered or other error
|
V2 This error occurs when the G32 three-point probing command fails. Similar to the G29 error, this happens when the probe doesn't trigger properly or encounters errors during the three-point leveling calibration.
|
|
programming error in lwIP and the developer should be notified
|
V2 Function documentation warning that negative return values indicate programming errors in lwIP itself, not user code errors. These should be reported to lwIP developers.
|
|
Protocol error
|
V2 POSIX errno definition for protocol errors. This error occurs when there are violations of communication protocol specifications or unexpected protocol states.
|
|
Protocol error
|
V2 Statistics counter for protocol-level errors. This tracks packets with protocol violations or unexpected protocol states.
|
|
Protocol wrong type for socket
|
V2 POSIX errno definition for protocol type mismatch. This error occurs when attempting to use a protocol with a socket type that doesn't support it (e.g., using TCP protocol with a datagram socket).
|
|
PwmOut pin mapping failed
|
V1 Runtime error when attempting to initialize PWM on a pin that doesn't support PWM functionality.
|
|
PwmOut pin mapping failed
|
V1 This fatal error occurs when trying to initialize PWM output on a pin that doesn't support PWM functionality. The pinmap_peripheral() lookup returns NC (Not Connected) when the pin isn't in the PinMap_PWM table, indicating the pin cannot be used for PWM. This will halt the system after printing the error message.
|
|
R1_ADDRESS_ERROR
|
V2 SD/MMC card R1 response status bit indicating an address error. This bit is set when a misaligned address is used for a command (erx = detected during execution, c = cleared by read).
|
|
R1_BLOCK_LEN_ERROR
|
V2 SD/MMC card R1 response status bit indicating a block length error. This occurs when the transferred block length doesn't match the block length set by the SET_BLOCKLEN command (er = detected in response, c = cleared by read).
|
|
R1_CARD_ECC_FAILED
|
V2 SD/MMC card R1 response status bit indicating the card's internal ECC (Error Correction Code) failed to correct a data error. This indicates data corruption that the card's ECC couldn't fix (ex = detected during execution, c = cleared by read).
|
|
R1_CC_ERROR
|
V2 SD/MMC card R1 response status bit indicating a card controller error. This is an internal card error that prevented the command from completing successfully.
|
|
R1_COM_CRC_ERROR
|
V2 SD/MMC card R1 response status bit indicating a CRC check failed on the previous command. This indicates communication errors between the host and card (er = detected in response, b = cleared by next command).
|
|
R1_ERASE_SEQ_ERROR
|
V2 SD/MMC card R1 response status bit indicating an error in the sequence of erase commands. This occurs when an erase command is not part of a valid erase sequence (must set start and end addresses before erase).
|
|
R1_ERROR
|
V2 SD/MMC card R1 response status bit indicating a general error occurred. This is a catch-all error bit for errors that don't fit other specific categories.
|
|
R1_LOCK_UNLOCK_FAILED
|
V2 SD/MMC card R1 response status bit indicating a card lock/unlock operation failed. This occurs when the password provided for card lock/unlock is incorrect or the operation cannot be completed.
|
|
read PHY %lu failed!\n
|
V1 This error occurs when attempting to read from an Ethernet PHY register times out. Similar to the write operation, it waits for EMAC_MII_RD_TOUT iterations for the PHY to become not busy. If the timeout is exceeded, the read operation fails, indicating a hardware communication problem with the Ethernet PHY chip.
|
|
Redlib does not support C++
|
V2 This is a compile-time error that prevents the use of Red Suite's Redlib library with C++ code. Redlib is a lightweight C library that doesn't include C++ support. This error is triggered when both `__cplusplus` (indicating C++ compilation) and `__REDLIB__` (indicating Redlib library usage) are defined. The code enforces the use of Newlib or another C++ compatible library when compiling C++ code.
|
|
Remote I/O error
|
V2 POSIX errno definition for remote I/O errors. This error occurs when I/O operations to remote systems fail.
|
|
RFS specific error
|
V2 POSIX errno definition for Remote File Sharing specific error. Linux-specific error code.
|
|
Routing error
|
V2 Statistics counter for routing errors. This tracks packets that cannot be routed to their destination due to missing routes or routing table issues.
|
|
Routing problem
|
V2 This is a lwIP error code definition (ERR_RTE = -4) indicating network routing failures. This error occurs when the network stack cannot find a route to the destination address or when the routing table is misconfigured.
|
|
Routing problem.
|
V2 This error string corresponds to ERR_RTE (-4) error code. It indicates that the network stack cannot find a route to the destination address.
|
|
rx not allowed while printing or busy
|
V2 This error occurs when trying to initiate an xmodem receive while the system is busy executing commands or printing. The system must be idle to perform file transfers.
|
|
ry not allowed while printing or busy
|
V2 This error occurs when trying to initiate a ymodem receive while the system is busy. File transfers require an idle system.
|
|
SCS: Invalid values of reserved bits!
|
V1 Compile-time validation error that occurs when the SCS (System Control and Status) register configuration has invalid values in reserved bit positions. Reserved bits must be 0 or 1 only.
|
|
SD V1 or V2 card with SDHC descriptor!
|
V1 This error indicates the opposite inconsistency - a card was detected as standard capacity (V1 or V2) but has a CSD structure version 1, which is only valid for SDHC cards. This also suggests a malformed or corrupted card.
|
|
SD_INVALID_APP_CMD
|
V2 SD card enum value indicating an invalid SD application command. SD application commands (ACMD) must be preceded by CMD55, and this value represents an application command that is not recognized or supported.
|
|
SDCard failed to initialize
|
V1 This error message is displayed when the SD card initialization fails. The disk_initialize() function returns non-zero on failure. This can happen if the SD card is not inserted, is damaged, has connection issues, or is improperly formatted. This is a critical error as Smoothieware relies on the SD card for configuration files and G-code.
|
|
SDHC card with regular SD descriptor!
|
V1 This error indicates an inconsistency where a card was detected as SDHC (high capacity) but has a CSD structure version 0, which is only valid for standard capacity cards. This suggests a malformed or corrupted card.
|
|
Serial pinout mapping failed
|
V1 Runtime error when UART TX and RX pins cannot be mapped to the same UART peripheral.
|
|
serial_baud
|
V1 Runtime error when an unsupported baud rate is specified for serial communication. Only predefined baud rates are supported.
|
|
Server responded with an error code
|
V2 HTTP client result code indicating the server returned an HTTP error status code (4xx or 5xx response codes).
|
|
Set 512-byte block timed out
|
V1 This error occurs after successful card initialization when attempting to set the block size to 512 bytes using CMD16. Standard capacity cards require this step, while high capacity cards have a fixed 512-byte block size. A timeout here suggests communication issues with the SD card.
|
|
Set this to 1 to call tcp_abort when tcp_close fails with memory error
|
V2 Configuration option to forcibly abort TCP connections when tcp_close() fails due to memory shortage. This prevents memory exhaustion when the HTTP server has lower priority than other protocols.
|
|
shell_thread: ERROR: Failed to start the timer
|
V2 This error occurs when the shell thread fails to start its timer, which is needed for periodic operations. This indicates a system resource issue.
|
|
shell: accept socket error: %d
|
V2 This error occurs when the network shell fails to accept a new socket connection. The errno value is printed to help diagnose network issues.
|
|
shell: write_back: ERROR magic was bad
|
V2 This error occurs in the network shell when the magic number check fails, indicating corrupted data or protocol error in the shell communication.
|
|
shell: write_back: error writing
|
V2 This error occurs when the network shell fails to write data back to the client, indicating network issues or the client disconnecting.
|
|
SHORT to ground on channel A
|
V2 This critical error occurs when the TMC2660 driver detects a short circuit to ground on motor channel A (one of the two motor coils). This indicates a wiring problem or motor failure. The driver will shut down the affected channel to protect itself.
|
|
SHORT to ground on channel B
|
V2 This critical error occurs when the TMC2660 driver detects a short circuit to ground on motor channel B (the second motor coil). This indicates a wiring problem or motor failure. The driver will shut down the affected channel to protect itself.
|
|
show error pages when parsing a request fails
|
V2 Configuration option to enable error page generation in the HTTP server when request parsing fails. When disabled, the server just closes the connection on parse errors.
|
|
SNMP stack can use only one of the APIs {raw, netconn}
|
V2 Compile-time error check ensuring SNMP is configured to use exactly one API (either raw or netconn, not both). This prevents configuration conflicts.
|
|
SNMP stack needs a receive API and UDP {raw, netconn}
|
V2 Compile-time error check ensuring SNMP has a receive API configured (either raw or netconn). SNMP cannot function without one of these APIs enabled.
|
|
SNMP_ERR_COMMITFAILED
|
V2 SNMP error code indicating commit operation failed. This error occurs during multi-phase SET operations when the commit phase fails.
|
|
SNMP_ERR_GENERROR
|
V2 SNMP general error code (5) for errors that don't fit other categories. This is used when a specific error type cannot be determined.
|
|
SNMP_ERR_NOERROR
|
V2 SNMP error code indicating no error (success). This is the standard success return value for SNMP operations.
|
|
SNMP_ERR_UNDOFAILED
|
V2 SNMP error code indicating undo operation failed. This error occurs during multi-phase SET operations when the undo/rollback phase fails.
|
|
SNMP_ERR_WRONGENCODING
|
V2 SNMP error code indicating wrong encoding. This error occurs when the value encoding doesn't match the expected format for the OID.
|
|
SNMP_ERR_WRONGLENGTH
|
V2 SNMP error code indicating wrong length for the value. This error occurs when SET operations specify a value with incorrect length for the OID.
|
|
SNMP_ERR_WRONGTYPE
|
V2 SNMP error code indicating wrong data type. This error occurs when SET operations specify a value with incorrect data type for the OID.
|
|
SNMP_ERR_WRONGVALUE
|
V2 SNMP error code indicating wrong value. This error occurs when SET operations specify a value that is out of range or inappropriate for the OID.
|
|
Sorry the function/compatibility test failed. (rc=%d)\nFatFs will not work with this disk driver
|
V2 This error is displayed when any of the disk I/O compatibility tests fail. The return code indicates which specific test failed, and the message warns that the FatFs filesystem will not work with the current disk driver.
|
|
SPI format error
|
V1 Runtime error when an invalid SPI format configuration is specified (bits per frame or mode).
|
|
SPI pinout mapping failed
|
V1 Runtime error when SPI pins (MOSI, MISO, SCLK) cannot all be mapped to the same SPI peripheral.
|
|
Srmount error
|
V2 POSIX errno definition for RFS srmount error. Linux-specific error code.
|
|
stepticker is not accurate
|
V2 This warning occurs when the timer setup completes but the actual frequency achieved doesn't match the requested frequency. The `permod` value indicates the deviation. This could affect motion accuracy but is not fatal. The system continues to run but step timing may not be perfectly accurate.
|
|
strategy #%d did not handle G%d
|
V1 This error occurs when a specific leveling strategy (selected with P parameter) exists but doesn't recognize or handle the G-code command. This usually indicates the wrong strategy was selected for the operation.
|
|
strategy #%d did not handle G%d
|
V2 This error occurs when a specific strategy was selected with the P parameter, but that strategy didn't handle the G-code command. The strategy exists but doesn't support that particular operation.
|
|
strategy #%d is not loaded
|
V1 This error occurs when attempting to use a leveling strategy by index (P parameter) that doesn't exist. The index is out of range of the loaded strategies.
|
|
Streams pipe error
|
V2 POSIX errno definition for STREAMS pipe errors. This is for System V STREAMS, not commonly used in embedded systems.
|
|
SYSAHBCLKDIV: Value out of range!
|
V1 System AHB clock divider must be in range 0-255.
|
|
SYSOSCCTRL: Invalid values of reserved bits!
|
V1 System oscillator control register configuration has invalid reserved bits set for LPC11U24.
|
|
SYSPLLCLKSEL: Value out of range!
|
V1 System PLL clock source selection value must be in range 0-3.
|
|
SYSPLLCTRL: Invalid values of reserved bits!
|
V1 System PLL control register has invalid reserved bits set.
|
|
T%d invalid tool
|
V1 This error occurs when attempting to select a tool (T command) that doesn't exist or is invalid. The system halts with this error message.
|
|
tcp_close failed to enqueue the FIN
|
V2 TCP flag definition comment explaining that TF_CLOSEPEND indicates tcp_close() couldn't enqueue the FIN packet and will retry in the TCP timer. This happens when memory is low.
|
|
Telnetd: ERROR Null instance or rport is wrong: %p - %u, %d\n
|
V1 This error occurs when the Telnet daemon receives a callback for a connection but the stored instance pointer is NULL or the remote port doesn't match the expected value. This is a sanity check that indicates corrupted connection state, possibly due to memory corruption or race conditions. The connection is aborted when this occurs.
|
|
Temperature reading is unreliable on %s HALT asserted - reset or M999 required
|
V2 This critical error occurs when temperature readings return infinity values during a heat-and-wait command (M109/M190). This indicates a sensor failure or disconnection, and the system halts to prevent damage.
|
|
TemperatureSwitch: ERROR: named switch %s does not exist
|
V2 This error occurs during runtime when the temperature switch tries to control a switch that doesn't exist. This happens if the referenced switch name in the config doesn't match any loaded switch modules.
|
|
The LPC18XX Chip include path is used for this build, but
|
V2 This is the first part of a two-part compile-time error that occurs when chip_lpc18xx.h is being used (indicating LPC18XX chip selection) but the CHIP_LPC18XX preprocessor symbol is not defined. This indicates a build configuration mismatch.
|
|
The LPC43XX Chip include path is used for this build, but
|
V2 This is the first part of a two-part compile-time error indicating that the LPC43XX chip headers are being used but the CHIP_LPC43XX symbol is not defined. This is a build configuration error.
|
|
The number of outbound packets which were chosen to be discarded even though no errors had
|
V2 MIB-II statistics documentation describing ifoutdiscards counter. This tracks outbound packets discarded intentionally even when valid, typically due to buffer or resource constraints.
|
|
There was a fatal error in the config.ini this must be fixed to continue\nOnly some shell commands are allowed and sdcard access
|
V2 This is the detailed error message stored and displayed to users when configuration fails. It informs users that the config.ini must be fixed and that only limited functionality is available.
|
|
This disk tastes funny! (%d) I only know about type 0 or 1 CSD structures
|
V1 This humorous error message occurs when the CSD structure version is neither 0 nor 1, which are the only two valid values according to the SD specification. The %d placeholder shows the invalid structure version number. This indicates a corrupted or non-compliant SD card.
|
|
Timeout waiting for v1.x card
|
V1 This error occurs when attempting to initialize an SD v1.x card. The ACMD41 (SD_SEND_OP_COND) command is sent repeatedly to initialize the card, but the card never reports as initialized within the timeout period (5000 iterations). This indicates a faulty or incompatible SD v1.x card.
|
|
Timeout waiting for v2.x card
|
V1 Similar to the v1.x timeout, this error occurs when an SD v2.x card fails to initialize within the timeout period. The ACMD41 command with high capacity flag is sent repeatedly, but the card never completes initialization. This suggests a faulty or incompatible SD v2.x/SDHC card.
|
|
Timeout.
|
V2 This error string corresponds to ERR_TIMEOUT (-3) error code. It indicates that a network operation timed out waiting for a response or completion.
|
|
tmr0 setup failed
|
V2 This error occurs when the hardware timer (TMR0) setup fails during StepTicker initialization. This is a critical error that prevents the step generation system from working. Without this timer, the stepper motors cannot be controlled. This could indicate a hardware failure or incorrect timer configuration.
|
|
Too many open files
|
V1 This error is returned when the system has reached its maximum limit for open files or file identifiers. The Plan9 implementation has limits defined as MAXFIDS (32 fids) and MAXENTRIES (32 entries), and this error prevents exceeding these limits to avoid resource exhaustion.
|
|
Transmit error lead to test abort
|
V2 lwIPerf result code indicating the test was aborted due to transmission errors (failure to send data).
|
|
Truncated long line %d in: %s\n
|
V1 This error occurs when reading a configuration file and a line exceeds the buffer size of 132 characters (131 + null terminator). If the line is not a comment (doesn't contain '#'), this warning is printed with the line number and filename. The excess characters are discarded until the next newline or end of file.
|
|
Try to post a message to an mbox - may fail if full
|
V2 Function documentation indicating that sys_mbox_trypost() may fail if the mailbox is full, returning ERR_MEM. This is used for non-blocking message posting.
|
|
Unable to find included config file: %s\n
|
V1 This error occurs when an `include` directive in a configuration file references a file that cannot be found. The system attempts to locate the included file in multiple locations (current path, /sd, /local), and if none succeed, this error message is displayed with the filename that could not be found.
|
|
Unable to properly set sensor settings, make sure you specify all required values
|
V2 This error occurs when using M305 to set sensor-specific optional parameters fails. This happens when not all required parameters for the sensor type are provided, or when invalid parameter combinations are specified.
|
|
unable to set trim, is endstops enabled?
|
V1 This error occurs when attempting to set trim values but the endstops module is not accessible. The endstops module must be enabled for trim adjustment to work.
|
|
unable to set trim, is endstops enabled?
|
V1 This error occurs during SCARA calibration when attempting to set trim but the endstops module is not available.
|
|
Unexpected error occured
|
V1 This error occurs when an unexpected exception is thrown during test execution that is not a standard exception. This is a catch-all handler that captures any exception type not previously caught. The test framework marks the test as having an error and continues execution.
|
|
unknown
|
V1 This error message is output when a Gcode command is marked as having an error (is_error flag set) but no specific error description was provided in the txt_after_ok field. This indicates an error occurred but the handler didn't set a descriptive error message.
|
|
unknown app for port: %d\n
|
V1 This error occurs when a TCP connection is received on a port that doesn't have a registered handler. The firmware supports specific ports (80 for HTTP, 23 for Telnet, 564 for Plan9, 115 for SFTP), and any other port triggers this error message indicating an unexpected connection attempt.
|
|
Unknown compiler
|
V2 This compile-time error occurs when the ARM math library header is compiled with an unsupported compiler. The code checks for specific compiler toolchains (__CC_ARM for ARM Compiler, __GNUC__ for GCC, __ICCARM__ for IAR) and fails if none are detected. This ensures the library is only built with tested, compatible compilers.
|
|
Unknown error
|
V2 SMTP result code for unknown errors during email sending. This is a catch-all error when the specific failure reason cannot be determined.
|
|
Unknown error
|
V2 HTTP client result code for unknown errors. This is a catch-all error when the specific failure reason cannot be determined during HTTP client operations.
|
|
Unknown error.
|
V2 This error occurs when lwip_strerr() is called with an error code that is out of range (positive or beyond the known error codes). It indicates an undefined or unexpected error code.
|
|
Unknown ethernet packet type %04X\n
|
V1 This error occurs when the Ethernet driver receives a frame with an EtherType value that is not IP (0x0800) or ARP (0x0806). The unknown EtherType is printed in hexadecimal format, and the packet is discarded. This could indicate network traffic that Smoothie doesn't support or corrupted frames.
|
|
unknown switch %s.
|
V1 This error occurs when attempting to get or set the state of a switch that is not recognized or configured. The switch name must match a configured switch device.
|
|
upload not allowed while printing or busy
|
V1 This error occurs when the 'upload' command is attempted while the machine is printing or busy executing other operations. File uploads block all operations and must only be done when the system is idle.
|
|
USBCLKCFG: Invalid values of reserved bits!
|
V1 USB clock configuration has invalid reserved bit values.
|
|
USBCLKDIV: Value out of range!
|
V1 USB clock divider must be in range 0-255.
|
|
USBCLKSEL: Value out of range!
|
V1 USB clock source selection must be in range 0-3.
|
|
USBPLLCLKSEL: Value out of range!
|
V1 USB PLL clock source selection must be in range 0-3.
|
|
USBPLLCTRL: Invalid values of reserved bits!
|
V1 USB PLL control register has invalid reserved bits set.
|
|
vjs_errorin
|
V2 Van Jacobson header compression statistics member tracking inbound packets with unknown type. This indicates malformed or corrupted compressed headers.
|
|
Wait on temperature aborted by kill
|
V2 This message occurs when a heat-and-wait operation (M109/M190) is aborted by pressing the kill button or by the system entering halt state.
|
|
Want to handle any errors? Do it here.
|
V2 This is a comment indicating where error handling code should be added in the UART3 interrupt handler. It's not an actual error message but a placeholder for developers to add custom error handling for UART errors (such as overrun, framing errors, parity errors, etc.) before the default ring buffer handler processes the data.
|
|
Want to handle any errors? Do it here.
|
V2 Same as above, but for the main UART (not UART3). This is a comment placeholder in the UART interrupt handler where custom error handling code should be added if needed. The comment appears before the default ring buffer handler is called.
|
|
WARNING Watchdog is disabled
|
V1 This warning is displayed when the watchdog timer is disabled (watchdog_timeout config value is 0.1 or less). The watchdog is a safety feature that resets the system if it becomes unresponsive. Disabling it means the system won't automatically recover from hangs or crashes, which could be dangerous in CNC applications.
|
|
WARNING: actuator %d rate exceeds base_stepping_frequency * ..._steps_per_mm: %f, setting to %f
|
V2 This warning occurs when an actuator's configured maximum rate (feedrate * steps_per_mm) exceeds the base stepping frequency. The max rate is automatically reduced to a safe value. This indicates the user configured too high a max rate for the stepping frequency.
|
|
WARNING: beta cannot be 0
|
V1 This error occurs when the thermistor beta value is configured as zero. Beta is the thermistor coefficient and cannot be zero. This is a configuration error that makes the thermistor unusable.
|
|
WARNING: beta cannot be 0
|
V2 This warning occurs when the beta value for thermistor calculations is 0 or negative, which would cause division by zero. Beta is required for thermistor temperature calculations.
|
|
WARNING: configure-planner: no planner section found. defaults loaded
|
V2 This warning occurs during configuration when the planner section is missing from the configuration file. The system will use default values for junction_deviation, z_junction_deviation, minimum_planner_speed, and planner_queue_size. This is a non-fatal error but indicates incomplete configuration.
|
|
WARNING: could not find axis %c
|
V2 This warning occurs when M906 (set current in mA) is issued with an axis letter that doesn't have a corresponding name mapping. Valid axes are X, Y, Z, A, B, C which map to alpha, beta, gamma, delta, epsilon, zeta.
|
|
WARNING: Discarded ethernet frame that is too big: %08lX, %d - %d\n
|
V1 This warning occurs when an incoming Ethernet frame is larger than the provided receive buffer. The frame information, actual length, and buffer size are printed. The frame is discarded to prevent buffer overflow. This could indicate a configuration mismatch or receipt of jumbo frames when not expected.
|
|
WARNING: duplicate config line replaced
|
V1 This warning occurs when a configuration value with the same checksum (meaning the same configuration key) already exists in the config cache and is being replaced with a new value. This typically happens when the config file contains duplicate entries for the same setting. The old value is freed and replaced with the new one.
|
|
WARNING: ESTOP is still latched, unlatch ESTOP to clear HALT
|
V1 This warning occurs when the emergency stop (ESTOP) button is still being held down after the system has been halted. The system detects that the halt state was cleared (perhaps manually) but the physical ESTOP button is still latched/pressed, so it warns the user to unlatch the ESTOP before attempting to continue.
|
|
WARNING: Failed to create %s voltage monitor
|
V2 This warning occurs when a configured voltage monitor cannot be created, typically due to an invalid pin specification in the configuration. The voltage monitor name is included in the message.
|
|
WARNING: failed to start FastTicker (maybe nothing is using it?)
|
V2 This warning occurs when the FastTicker timer system fails to start. This is usually not critical as it may simply mean no modules have attached to it. FastTicker provides high-frequency periodic callbacks.
|
|
WARNING: G53 with args is not supported
|
V2 This warning occurs when G53 (move in machine coordinate system) is used with arguments directly (like "G53 X10"). The correct usage is "G53" followed by a separate move command like "G1 X10". The direct form is not supported.
|
|
WARNING: GPIO%d[%d] has already been allocated
|
V2 This warning is displayed when attempting to allocate a GPIO pin that has already been allocated to another function. The system uses a bitset to track which GPIO port/pin combinations are in use to prevent conflicts. This occurs when the `set_allocated()` function returns false, indicating the pin is already in use.
|
|
WARNING: load_config_override: this line was not handled: %s
|
V2 This warning occurs when loading the config-override file and a line in the file cannot be processed by any handler. The unhandled line is displayed so the user can identify configuration that isn't being applied.
|
|
WARNING: negative coefficient in calculate_steinhart_hart_coefficients. Something may be wrong with the measurements
|
V1 This warning occurs when calculating Steinhart-Hart coefficients from temperature/resistance pairs results in a negative coefficient. This indicates the measurements or configuration values are incorrect or don't make physical sense for a thermistor.
|
|
WARNING: negative coefficient in calculate_steinhart_hart_coefficients. Something may be wrong with the measurements
|
V2 This warning occurs when calculating Steinhart-Hart coefficients from temperature/resistance pairs results in a negative C coefficient, which is physically incorrect. This usually indicates errors in the input measurements. The code corrects it by using the absolute value.
|
|
WARNING: override will NOT be loaded on boot
|
V2 This warning is displayed after M500 (save settings) when the config_override setting is disabled in the main config. The settings are saved but won't be automatically loaded on next boot unless config_override is enabled.
|
|
WARNING: PLL1 is notr sourced by xtal
|
V2 This warning (note the typo "notr" instead of "not") occurs when PLL1 is not sourced by the crystal oscillator (xtal). The code checks bits 24-28 of the PLL1 register and expects the value to be 0x06, indicating crystal source. If it's not, the function returns 0 and displays this warning. This indicates an unexpected clock configuration.
|
|
WARNING: probe is not within tolerance: %f > %f
|
V2 This warning occurs when the first probe point's Z value is not within the configured tolerance. Ideally, the first point should be at Z=0 (as it's used as the reference), and if it's off by more than the tolerance (default 0.03mm), this warning is issued.
|
|
WARNING: SlowTicker did not start
|
V2 This warning appears when the SlowTicker timer system fails to start during test initialization. SlowTicker is used for lower-frequency periodic tasks. Tests may not function correctly if this system doesn't start.
|
|
WARNING: SPI channel %d, already inited
|
V2 This warning occurs when attempting to initialize an SPI channel that has already been initialized. The code maintains a static boolean array `channel_init[]` to track which SPI channels (0 or 1) have been initialized, and this message is displayed if you try to initialize the same channel twice.
|
|
WARNING: switch config: output pin has no known type: %s
|
V2 This warning occurs when a switch output pin is specified but the output type is not recognized. Valid types are "sigmadeltapwm", "digital", and "hwpwm".
|
|
WARNING: The config is bad for this temperature sensor
|
V1 This warning occurs when attempting to use a thermistor that has been flagged as having a bad configuration. The bad_config flag is set when various configuration errors are detected during initialization.
|
|
WARNING: Using E is deprecated, use A and B for channels 3 and 4
|
V1 This warning occurs when the M907 command is used with the old 'E' parameter format for setting motor currents. The old format mapped E to channel 3 (now A) and A to channel 4 (now B). Users should update their configuration to use the new format.
|
|
WARNING:config-LinearDeltaSolution: No linear delta section found, defaults used
|
V2 This warning occurs when a linear delta arm solution is selected but there's no "linear delta" section in the configuration file. Default values will be used for arm_length (250.0mm), arm_radius (124.0mm), and all tower offsets/angles (0.0). Users must add proper configuration or the delta will not move correctly.
|
|
WARNING:config-RotaryDeltaSolution: No rotary delta section found
|
V2 This warning occurs when a rotary delta arm solution is selected but there's no "rotary delta" section in the configuration file. Default values will be used for all rotary delta parameters (end effector length, base length, carbon rod length, servo horn length, etc.). This is acceptable if defaults are appropriate but users should verify the defaults match their hardware.
|
|
WARNING:configure-robot: %s.microstepping settings needs three numbers 1,1,1 - SET to default
|
V2 This warning occurs when the microstepping configuration for a stepper driver (like A5984) with three microstepping pins is not formatted as three numbers. Default 1/32 microstepping will be used.
|
|
WARNING:configure-robot: %s.microstepping settings needs two numbers 1,1 - SET to default
|
V2 This warning occurs when the microstepping configuration for a stepper driver (like A4988) is not formatted as two numbers. Default microstepping will be used (both pins set high). This is for boards with MS1/MS2 pins.
|
|
Warning:configure-robot: g92_offset config is bad
|
V2 This warning occurs when the g92_offset configuration value cannot be parsed as three numbers (X, Y, Z). The g92_offset setting will not be applied.
|
|
WARNING:configure-robot: no 'motion control' section found, defaults used
|
V2 This warning occurs when the configuration file doesn't contain a "motion control" section. Default values will be used for motion control parameters like acceleration, junction deviation, etc. This is non-fatal but the user should add proper configuration.
|
|
warning:grid radius is different read %f - config %f, overriding config
|
V2 This warning occurs when the saved grid radius differs from the configured radius. Unlike grid size, the system allows this and overrides the configuration with the saved value.
|
|
WDTOSCCTRL: Invalid values of reserved bits!
|
V1 Watchdog oscillator control register has invalid reserved bits set.
|
|
we can't use interrupts in burst mode
|
V2 This comment explains a design decision: due to high IRQ overhead at 70KHz sampling rate, interrupts cannot be used with the ADC in burst mode. Instead, the ADC runs in burst mode (continuously sampling) and the values are polled by a slow timer. This avoids overwhelming the system with interrupt requests while still maintaining adequate sampling for thermistor readings.
|
|
we failed to authenticate ourselves
|
V2 PPP authentication function comment. This callback is invoked when we (the local side) fail to authenticate to the remote peer.
|
|
websocket_read: pbuf_copy_partial failed
|
V2 This error occurs when copying data from the network buffer (pbuf) fails during WebSocket reading. This indicates a buffer management issue in the LWIP stack.
|
|
websocket_read: WARNING FIN bit not set
|
V2 This warning occurs when a WebSocket frame is received without the FIN (final) bit set, indicating fragmented messages. Fragmented WebSocket messages are not currently supported by this implementation.
|
|
websocket_write: error writing: %d
|
V2 This error occurs when writing data to a WebSocket connection fails. The LWIP error code is printed. This could indicate network issues or the client disconnecting.
|
|
When a connection attempt fails, the error callback is currently called!
|
V2 Documentation note indicating that when tcp_connect() fails, the error callback (not connected callback) is invoked. This is important for proper error handling in TCP client code.
|
|
write PHY %lu %04X failed!\n
|
V1 This error occurs when attempting to write to an Ethernet PHY register times out. The operation waits for EMAC_MII_WR_TOUT iterations for the PHY to become not busy, and if this timeout is exceeded, the write operation fails. This indicates a hardware communication problem with the Ethernet PHY chip.
|
|
write_page: Failed to open: %s
|
V2 This error occurs in the HTTP server when it fails to open a file for serving via HTTP. The file path is specified but the file cannot be accessed, possibly due to it not existing, permissions issues, or SD card problems.
|
|
write_page: got write error: %d
|
V2 This error occurs when the HTTP server encounters an error writing data to the network connection. The error code from netconn_write is printed. This could indicate network issues or the client disconnecting.
|
|
xTaskCreate failed
|
V2 This error occurs when FreeRTOS fails to create the player thread due to insufficient memory or system resources. This is a critical error that prevents file playback from starting.
|
|
ZProbe not triggered
|
V1 This error occurs when a G30 probe operation completes without the probe being triggered. This means the probe traveled the maximum allowed distance without detecting the bed surface. Check probe wiring, max_z settings, and initial height.
|
|
ZProbe not triggered
|
V2 This error occurs when a G30 probe command completes but the probe was never triggered. This indicates the probe moved the full travel distance without detecting the bed, which could mean the probe is malfunctioning, not wired correctly, or the bed is too far away.
|
|
ZProbe pin not configured.
|
V1 This error occurs during G29-G32 processing when the ZProbe pin has not been configured or connected. The probe pin must be properly defined in the configuration before any probing operations can be performed.
|
|
ZProbe triggered before move, aborting command.
|
V1 This error occurs when the Z probe is already triggered before starting a probing move. This indicates either the probe is already touching the bed, there's a wiring issue, or the probe logic is inverted. The command is aborted to prevent damage.
|
|
ZProbe triggered before move, aborting command.
|
V2 This error occurs when attempting to execute a probe command (G29-G32) but the probe is already triggered. The probe must not be triggered at the start of a probing operation.
|