Mitsubishi Electric MELSEC Q-series MELSECNET/H

The system is in an initial status where the baton pass and data link are not in a normal state. This fault automatically clears when the baton pass and data link recover.

This error indicates an issue with the control or sub-control station's operational status. It could be related to power, cabling, or the CPU module itself.

The network's baton pass mechanism has failed, resulting in a lost baton. This prevents proper communication and data exchange across the network.

A duplicate baton has been detected on the network, indicating a configuration error or physical fault that could lead to communication conflicts and instability. This typically arises from incorrect station numbering or control station settings.

The system is in an initial status during an online test or offline loop test. This state requires the system to be put into online mode or the test to be stopped for normal operation.

This fault indicates that two or more stations on the network have been configured with the same station number. This leads to addressing conflicts and prevents proper communication.

This fault occurs when more than one station is configured as the control station within the same network segment. This creates an unresolvable conflict in network mastership.

The system is currently in an offline status, meaning it is not actively communicating on the network. This state requires the system to be manually set to online mode.

The system has attempted to receive data multiple times but consistently failed, exceeding the allowed number of retries. This suggests a persistent communication issue on the receiving end.

The system has attempted to send data multiple times but consistently failed, exceeding the allowed number of retries. This indicates a persistent communication issue on the sending end.

A communication timeout occurred, meaning a response was not received within the expected timeframe. This is a common network issue that can stem from various physical and logical problems.

An error related to the corresponding station's configuration or operational status has been detected. This includes issues with its parameters or switch settings.

The network loop is in a faulty state, indicating a serious communication problem. This can be caused by physical network issues or incompatible network module types being mixed within the same system.

A general send failure has occurred, and retrying the transmission did not resolve the issue. This indicates a persistent underlying problem in the communication path or station configuration.

A send failure has occurred, and the error recurred even after a retry. This suggests a persistent issue with the physical network or addressing scheme, preventing successful data transmission.

A send failure is detected, pointing towards issues primarily with the physical layer of the network. This includes cabling, hardware integrity, or noise interference.

The system is in an initial state related to baton regeneration. This is a temporary status as the network attempts to restore baton pass and data link functionality.

A send failure occurred because multiplex loop transmission has stopped. This indicates a problem within the loop network that is preventing data from being sent.

The station is reporting a disconnected status, indicating a loss of communication. This can be due to incorrect parameter settings, faulty hardware, or network cabling issues, especially in a remote I/O setup.

The system is in an initial status where no baton is being addressed to the host station. This can be caused by parameter/switch settings or a mix of incompatible network modules.

A send failure has occurred specifically in a bus-based coaxial cable network. This points to issues with the coaxial cable integrity, connections, or terminating resistors.

The receive buffer has no free area, indicating a buffer-full error that prevents further data reception. This can happen due to high communication traffic or issues with the sending CPU's receive processing.

The size of the received data exceeds the system's capacity or configured limit. This typically occurs when a sending station attempts to transmit an excessively large data block.

The logical channel number used for communication is outside the permissible setting range. This is a configuration error that prevents proper channel-based communication.

The channel number used for communication is outside the permissible setting range. This is a configuration error preventing proper channel-based communication.

A SEND instruction was executed with a target network or station number configured for a remote I/O station, which is an invalid operation for a SEND instruction.

This error indicates a problem with the designated station for communication. It can occur if data is sent to station number 0, if a message is received that was not intended for the host, or if the designated control station is down.

The specified send destination station number is out of the valid range or a station number 65 or higher was specified. This is a configuration error preventing proper communication.

The specified send destination group number is out of the valid range or a group number 33 or higher (control data A1H) was specified. This is a configuration error preventing group-based communication.

An error originating from the send destination CPU's hardware has occurred, preventing successful data transmission. This indicates a hardware fault at the receiving end.

The number of relay stations specified for a transmission is outside the permissible range or 8 or more relay destination stations were specified. This is a system configuration error.

The received network number is invalid, causing a communication error. This often points to incorrect network number parameters or a mismatch with other stations' configurations.

A response to a communication request was not received within the expected waiting period, leading to a timeout error. This is a general communication issue.

The host station is attempting to use a channel that is already active or in use by another process. This prevents concurrent use of the same channel.

The target station's communication channel is currently in use, preventing the execution of a SEND instruction. This means the target channel is busy processing other requests.

An arrival monitoring timeout occurred while waiting for a response, and the resend count was set to 0. This can happen with RECV instructions if another station is sending, or if the host is executing the instruction without a response.

Communication failed persistently even after executing the designated number of resends. This indicates a fundamental communication breakdown that retries cannot overcome.

The channel number configured for either the host or target station is outside the permissible setting range of 1 to 64. This prevents proper channel assignment.

The host station's own station number has been specified as the target station number in a communication instruction. This creates a self-targeting loop error.

The execution type for designating all stations or a group of stations is set to "With arrival confirmation," which is not allowed for these designation types.

The configured resend count for communication attempts is outside its permissible setting range. This prevents proper retry logic for failed transmissions.

The configured arrival monitoring time, which dictates how long the system waits for a response, is outside its permissible setting range.

The specified sent data length for a SEND instruction is outside its permissible setting range. This leads to data transmission errors.

An error related to the mode switch setting has occurred, likely indicating a hardware configuration mismatch or an invalid mode selection.

A network number error has been detected, indicating a mismatch or incorrect configuration of the network number for the device.

A group number or station number error has been detected, typically due to incorrect hardware setting switches or parameter configurations. This prevents proper addressing on the network.

An error related to the DIP switch settings has occurred, indicating a mismatch between the hardware configuration and expected or programmed settings.

The contents of the common parameters or parameters specific to a station are corrupted or broken, leading to a link parameter error. This prevents proper network communication and function.

A consistency error has been detected in the parameters, specifically related to parameter size. The word number of specific parameters exceeds that of common parameters, which is an invalid configuration.

A parameter mismatch occurred because the parameters of the control station (which started as a normal station) differ from the parameters received from the sub-control station. This indicates a configuration discrepancy between primary and secondary controllers.

The system has entered a state where automatic return functionality is not active or possible. This requires manual intervention based on specific settings.

The system's "no control station shift" setting has been engaged, preventing a shift in control station functionality. This requires specific corrective action based on this setting.

Startup has been denied because the system is under a condition of "no startup." This often relates to how the data link was previously stopped. If stopped by all station designation, all stations start; otherwise, automatic startup is denied.

A keyword error occurred because a different station from the one that was stopped was initiated for startup. This indicates an incorrect sequence of operations or targeting.

The system has exceeded the allowed number of retries for an operation, indicating a persistent issue that cannot be resolved through automatic retries. This suggests a problem with the control station's operation or stability.

A relevant timer has timed out, indicating an operation did not complete within its allotted time. This points to a delay or fault within the control station's processes.

Communication is impossible because link parameters are not configured or are invalid, specifically indicated by SW0056 being set to 0. This means the station is likely disconnected from the network.

The content of the special register SW0000 is outside its permissible setting range. This is a configuration error that needs correction.

A consistency error has been detected in the low speed link parameters or low speed parameters specific to a station. This is often related to parameter size, where specific parameters exceed common parameters.

An error has been detected within the intermediate CPU module of the system. This indicates a hardware or firmware issue with this specific CPU.