Mitsubishi Electric MELSEC iQ-R Motion Controller

This warning occurs when the speed for a synchronous encoder axis exceeds its defined monitor range. This indicates that the input pulse from the synchronous encoder might be too high or the system's monitoring parameters are too sensitive for the actual operating speed, potentially leading to instability.

This minor error occurs when the parameter [Pr.346] Command generation axis length per cycle is set to '0'. This invalid setting prevents the command generation axis from starting its control operation, as a non-zero length per cycle is required for proper functionality.

This minor error indicates that the indirect setting for the positioning address for the command generation axis is outside the acceptable range. The valid range is 0 to (value of [Pr.346] Command generation axis length per cycle - 1). If the address is outside this range, the positioning control will not initiate.

This minor error occurs when attempting to execute a simultaneous start instruction (START) that includes a mix of real axis programs and command generation axis programs. The system does not support mixed program starts, and this action will prevent the control from initiating.

This minor error occurs when the servo input axis number (1 to 64) specified in [Pr.401] for the main shaft is set to the same value as an output axis. This conflict prevents the initiation of synchronous control, as the system cannot distinguish between input and output functions for the same axis identifier.

This minor error occurs when the servo input axis number (1 to 64) specified in [Pr.418] for the auxiliary shaft is set to the same value as an output axis. This conflict prevents the initiation of synchronous control, as the system cannot properly assign input and output roles for the conflicting axis ID.

This minor error occurs when both Speed Change Gear 1 ([Pr.434]) and Speed Change Gear 2 ([Pr.490]) are configured with the same arrangement setting. This duplicate arrangement prevents the synchronous control from starting, as the system cannot unambiguously apply speed change processing for the same section of the shaft.

This minor error occurs when the number of control axes configured per controller exceeds the maximum allowed limit for the current SSCNET operation cycle. It indicates a configuration mismatch that prevents proper system operation.

This moderate error arises when the operating system software version is "25" or earlier, and the MT Developer2 options screen has the number of words used set to "1 word". This incompatibility causes an error upon powering on a Multiple CPU system after installation, as the older OS does not support this 1-word setting.

This fault indicates that the operating system software required for the Motion CPU module is not installed. The module is in an uninitialized state, presenting as installation mode.

This fault indicates an error within the installed operating system software file on the Motion CPU module. The corrupted file prevents the operating system from functioning correctly, leading to operational issues.

This indicates a self-diagnostic error detected by the Motion CPU module, which can range from minor warnings to major faults impacting operation. The 4-digit code () provides specific details, along with a displayed file name and operating mode for continuous errors.

This fault code, displayed on the Motion CPU's dot matrix LED as 'E ', indicates a hardware or software error detected during the module's initialization phase. The '' placeholder represents a specific sub-code that further details the nature of the error. Such errors prevent the Motion CPU from starting up normally, potentially leading to system stoppage.

This error occurs during operating system software installation from an SD memory card, indicating an access failure to the card. The system cannot read the installation files, halting the process.

This error signifies a problem with the operating system install file itself, located on the SD memory card, during the installation process. The file is either corrupted, unsuitable, or an older version (05 or earlier) was attempted on an R64MTCPU module.

This error indicates an access failure to the internal ROM of the Motion CPU module during operating system software installation from an SD memory card. This points to a hardware issue with the module's internal memory, preventing the OS from being written.

This error indicates a problem with the license key file present on the SD memory card during the installation mode. The system cannot validate the license for the operating system, halting the installation.

This error indicates that a problem was detected during the built-in memory clear process on the Motion CPU module. This suggests an issue with the module's memory hardware or the clear operation itself, preventing successful memory initialization.

This error indicates a watchdog timer fault, where the system's watchdog mechanism has not been reset within its expected interval. This typically points to a software malfunction or an unresponsive process within the Motion CPU module, or a hardware error.