Bosch Rexroth Motion Control

An internal software error occurred during the generation of the stack for the IdleTask. This is a serious system error, indicating a fundamental issue with the system's software components. No error recovery is possible for this fault.

This is a SERCOS state class 1 error indicating an overload condition on the specified axis, leading to a cut-off. The drive attempts the best possible response with a subsequent torque release. This fault points to an issue within the servo loop or the drive itself.

This SERCOS state class 1 error signals an overtemperature condition in the amplifier of the specified axis, resulting in a cut-off. The drive will attempt to respond appropriately with a torque release. This fault is categorized as a servo loop or drive fault.

A SERCOS state class 1 error indicating that the motor on the specified axis has exceeded its safe operating temperature, triggering a cut-off. The drive will attempt a controlled response with a torque release. This is classified as a servo loop or drive fault.

This SERCOS state class 1 error indicates a cooling system malfunction for the specified axis, leading to a system cut-off. The drive attempts a best-effort response with torque release. This fault affects the servo loop or the drive's cooling system.

A SERCOS state class 1 error reporting a fault in the control voltage for the specified axis. The drive will attempt the best possible response with a subsequent torque release. This issue impacts the servo loop or the drive's control power supply.

This SERCOS state class 1 error signifies an issue with the encoder on the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault can lead to inaccurate position feedback and affects the servo loop or drive operation.

A SERCOS state class 1 error indicating a problem within the electronic commutation system of the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault affects the servo loop or drive's ability to properly control the motor.

This SERCOS state class 1 error reports an overcurrent condition on the specified axis. The drive attempts the best possible response with a subsequent torque release to protect the system. This fault is indicative of an issue in the servo loop or the drive's power stage.

A SERCOS state class 1 error indicating an over-voltage condition on the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault typically originates from an issue within the servo loop or the drive's power supply.

This SERCOS state class 1 error reports an under-voltage condition on the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault is typically related to the servo loop or an issue with the drive's power supply.

A SERCOS state class 1 error indicating a phase fault in the power supply for the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault points to an imbalance or loss in the incoming power supply or within the drive's power section.

This SERCOS state class 1 error indicates a general servo error on the specified axis. The drive attempts the best possible response with a subsequent torque release. This is a broad category for issues within the servo loop or the drive, requiring further investigation.

A SERCOS state class 1 error reporting an interface error on the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault indicates a communication or hardware problem at the interface level between the control and the drive.

This SERCOS state class 1 error indicates that the physical or software-defined position limit of the specified axis has been exceeded. The drive attempts the best possible response with a subsequent torque release. This fault suggests a runaway condition, incorrect limit settings, or a control issue.

A SERCOS state class 1 error indicating an unspecified error on the specified axis. The drive attempts the best possible response with a subsequent torque release. This is a generic fault, requiring deeper diagnostic analysis to identify the root cause within the servo loop or drive.

This SERCOS state class 1 error reports a manufacturer-specific error on the specified axis. The drive attempts the best possible response with a subsequent torque release. This fault indicates an issue requiring specialized knowledge from the manufacturer for diagnosis and resolution.

The system attempted to activate a specific MACODA parameter (identified by %d) without performing the required control startup of the NC. This is a core system warning, indicating a procedural error in parameter transfer.

An internal software error occurred during the processing of ICL-data at specific code lines (%d %d). This is a serious MMI (Man-Machine Interface) error, indicating a critical software malfunction with no error recovery possible.

An internal software error occurred during the initialization of the VGA system. This is a serious system error, indicating a fundamental problem with the system's display or graphics handling, with no error recovery possible.

A programming error at a CPL command was detected because the required zero offset table could not be found. This indicates an issue within the part program, potentially affecting positioning accuracy.

The PLC program has been intentionally set into the STOP state by an operator using the programming device. This is a PLC error, requiring manual intervention to resume operation.

The PLC user program is prevented from starting because the physical switch on the SM module is currently set to position '1'. This is a PLC error that requires a change in the module's switch setting or a software override.

The system encountered an error while attempting to open the specified SCS-file. This is a servo loop or drive fault, indicating that a critical configuration or group file is inaccessible.

A syntax error was detected in the axis list within a local group of the SCS-file, specifically at the indicated line. This is a servo loop or drive fault, preventing proper axis configuration.

A 'FOR' instruction is missing within the main group of the SCS-file at the specified line. This is a servo loop or drive fault, indicating an incomplete or incorrect control script.

An invalid file name was specified for a local group within the SCS-file at the indicated line. This is a servo loop or drive fault, hindering the system's ability to identify and use group configurations.

A 'USE' instruction is missing within the main group of the SCS-file at the specified line. This is a servo loop or drive fault, indicating an incomplete or incorrect control script that prevents the use of necessary resources.

A variable within a 'USE' statement in a local group of the SCS-file is missing its specified value at the indicated line. This is a servo loop or drive fault, preventing the proper assignment of parameters or resources.

The drive does not accept the identification number provided in the SCS-file for the specified axis. This is a servo loop or drive fault, indicating a mismatch between the configured identification number and what the drive expects or supports.

A part program selection error occurred because the chosen item ('%s') is identified as a file directory rather than an actual program file. This is a part program error, preventing the execution of the intended program.

An incorrect implementation of a MACODA parameter has been detected. This indicates a part program error and makes error recovery impossible. The system cannot recover from this fault automatically.

The allocated memory for the link table, defined in MACODA block number 707000010 ('Data areas for CPL programs'), is too small. This results in insufficient memory for the specified program '%s', causing a part program error.

A programming error was detected at a CPL command because the specified subprogram '%s' does not exist. This fault, covering codes 826 to 827, indicates an issue within the part program's structure or dependencies.

The value defined for the stack in MACODA block number 707000010 ('Data areas for CPL programs') is too small. This leads to insufficient runtime memory, resulting in a part program error that prevents proper execution.

An internal software error occurred due to an invalid size of input text for a specific class (identified by %d and %d). This is a minor system error, indicating a data integrity issue within the software, with no error recovery possible.

An internal software error prevented the input text associated with error %d from being written into the database. This is a minor system error, indicating a problem with logging or data storage, with no error recovery possible.

The specified axis ('%s') is not responding to its assigned SERCOS address '%d'. This is a servo loop or drive fault, indicating a communication breakdown or incorrect addressing configuration.

The specified axis ('%s') is not ready for switchover to SERCOS phase 3, due to missing or incorrect identification number S-0-0021. This fault (covering codes 833-834 and 836) indicates the drive rejects the phase change because of parameter validation issues. It is a servo loop or drive fault.

The indicated data record for the specified axis ('%s') is not accepted by the drive. This could be due to the NC data record having an incorrect format, a value outside the drive's allowed range, or the data being write-protected. This is a servo loop or drive fault.

The SERCOS command to reset a class 1 error cannot be set for the specified axis ('%s'). This is a servo loop or drive fault, indicating an inability to clear critical diagnostic errors, with no error recovery possible.

The specified axis ('%s') is not ready for switchover to SERCOS phase 4 due to a missing or incorrect identification number. The fix suggests checking ident number S-0-0022, implying a discrepancy or an issue with the specific ident for phase 4. This is a servo loop or drive fault.

During SERCOS startup, an incorrect communication phase was selected. Only phases 0 to 4 are permissible, and they must be configured in ascending order, incrementing by one step. This is a servo loop or drive fault.

A serious error occurred during SERCOS startup, forcing the NC to revert to SERCOS phase 0. Possible causes include telegram failure, handshake timeout, busy timeout in the service channel, or incorrect transmission time adjustments. This is a servo loop or drive fault, indicating critical communication issues.

An error occurred during the registration of a task as a client within the NCS (Network Communication System). This is a serious system error, indicating a fundamental problem with client registration, with no error recovery possible.

An error occurred during the transition to SERCOS phase 0, preventing the selected SERCOS phase from being successfully implemented. This is a servo loop or drive fault, indicating a critical issue in the SERCOS state machine, with no error recovery possible.

A system error was detected in either the MCA or BMC subsystem at a specific code line. This is a minor system error; however, a precise cause can only be determined after examination by the development department. No error recovery is possible by the technician.

An error occurred during the installation of the SERCOS server. This is a serious system error, indicating a critical failure in setting up SERCOS communication infrastructure, with no error recovery possible.

The bit stream on the SERCOS ring has been interrupted, resulting in a loss of connection to the drives. This is a servo loop or drive fault, severely impacting real-time communication and control.

Two successive drive telegrams from the same address have failed, causing the NC to automatically switch back to SERCOS phase 0. This is a servo loop or drive fault, indicating persistent communication problems on the SERCOS network.

The capacity limit of the internal list that holds NC commands destined for a drive has been exceeded. This error occurs when more than 5 simultaneous active commands are present, representing a serious system error.

The list of active commands is suspected to be inconsistent due to an internal error, leading to its destruction and abortion of access. This is a serious system error, indicating a critical data integrity issue, with no error recovery possible.

The specified axis is configured as a feed axis in MACODA, but the position control interface is not configured in the main operation mode of the drive. This is a servo loop or drive fault, preventing proper position control for the axis.

A communication fault occurred during SERCOS phase 3 while loading the reference point of the drive (identified by %d and IdNo %d). This is a servo loop or drive fault, indicating data corruption or miscommunication during a critical synchronization step.

The SERCOS startup (runup) was aborted due to a simple communication fault that occurred while loading parameters to the drive. This is a servo loop or drive fault, preventing the SERCOS ring from establishing full communication.

The operand address (identified by %d) provided to the APS (Application Processing System) exceeds its corresponding valid operand range (identified by %d) within the ICL (Internal Command Language). This is a PLC error, indicating an incorrect memory or resource address assignment.

An NCS (Network Communication System) function called within the APS (Application Processing System) subsystem returned an error. This is a PLC error, indicating a failure in network communication services within the application, with no error recovery possible.

A request for memory space, specifically for the internal management list, could not be satisfied, preventing the called function (%d) from executing. This is often caused by frequent loading of client modules that are waiting for a response from the NC, leading to resource exhaustion. This is a PLC error with no error recovery possible.

A request for memory space via the dual port (identified by NCB error %d) could not be satisfied. This is a PLC error, indicating a critical memory allocation failure for communication, with no error recovery possible.

An error occurred (identified by NCB error %d) when the system attempted to request the handler structure necessary for copying the NC bit interface. This is a PLC error, indicating a failure in preparing for interface communication, with no error recovery possible.