Omron SYSMAC CJ Series PLC

This fault indicates that the pulse output operation was stopped due to a CW limit signal input. This typically occurs during an origin search function, signifying that the machine has reached its positive travel limit, preventing further movement in the CW direction.

This fault indicates that the pulse output operation was stopped due to a CCW limit signal input. This typically occurs during an origin search function, signifying that the machine has reached its negative travel limit, preventing further movement in the CCW direction.

This fault occurs during an origin search when the 'Origin Detected after Prox Input' parameter is set to 0 (Turns ON and then OFF), but no origin proximity input signal was received. This indicates the machine failed to detect the initial proximity sensor before the final origin, preventing the origin search from completing.

This fault occurs during an origin search when the main origin input signal was not received. This prevents the system from precisely determining its home position, indicating a failure to detect the final origin marker.

This fault occurs during an origin search in operation mode 0, specifically when the origin input signal is received during the deceleration phase after the origin proximity input signal has already been detected. This indicates that the origin input signal was detected too early, before deceleration to a stop was completed.

This fault indicates that an origin search cannot be initiated because both CW and CCW limit signals are being input simultaneously. This suggests a conflicting state where the system believes it's at both ends of its travel range at once, preventing any movement.

This fault occurs during an origin search when the origin proximity input signal and the limit input signal in the search direction are being input simultaneously. This indicates a contradiction where a proximity signal is detected at the same time as a hard limit in the direction of travel, potentially causing an emergency stop.

This fault indicates one of two conditions: either the limit input signal is already active in the origin search direction when a search is attempted, or during a search without proximity input, both the Origin Input Signal and the Limit Input Signal in the opposite direction from the search were ON simultaneously. This prevents the origin search from starting or proceeding correctly due to an initial, conflicting limit condition, resulting in an emergency stop.

This flag indicates that the Pulse Value (PV) for pulse output 0 has either exceeded its maximum positive limit (overflow: incremented beyond 7FFF FFFF hex) or fallen below its minimum negative limit (underflow: decremented below 8000 0000 hex). This signifies that the cumulative pulse count for output 0 has gone out of its defined 32-bit range, wrapping around to the opposite extreme, and can no longer accurately represent the total number of pulses.

This flag activates if the Pulse Value (PV) for pulse output 0 experiences an overflow or underflow while an interrupt input is received, or during the execution of the IFEED(892) instruction when a specified number of pulses is being moved and the origin is defined. This indicates a data integrity issue within the pulse counter, specifically during interrupt-driven feeding operations where the PV limits are exceeded.

This flag indicates that the Pulse Value (PV) for pulse output 1 has either exceeded its maximum positive limit (overflow: incremented beyond 7FFF FFFF hex) or fallen below its minimum negative limit (underflow: decremented below 8000 0000 hex). This signifies that the cumulative pulse count for output 1 has gone out of its defined 32-bit range, wrapping around to the opposite extreme, and can no longer accurately represent the total number of pulses.

This flag activates if the Pulse Value (PV) for pulse output 1 experiences an overflow or underflow while an interrupt input is received, or during the execution of the IFEED(892) instruction when a specified number of pulses is being moved and the origin is defined. This indicates a data integrity issue within the pulse counter, specifically during interrupt-driven feeding operations where the PV limits are exceeded.

This flag indicates that the Pulse Value (PV) for pulse output 2 has either exceeded its maximum positive limit (overflow: incremented beyond 7FFF FFFF hex) or fallen below its minimum negative limit (underflow: decremented below 8000 0000 hex). This signifies that the cumulative pulse count for output 2 has gone out of its defined 32-bit range, wrapping around to the opposite extreme, and can no longer accurately represent the total number of pulses.

This flag activates if the Pulse Value (PV) for pulse output 2 experiences an overflow or underflow while an interrupt input is received, or during the execution of the IFEED(892) instruction when a specified number of pulses is being moved and the origin is defined. This indicates a data integrity issue within the pulse counter, specifically during interrupt-driven feeding operations where the PV limits are exceeded.

This flag indicates that the Pulse Value (PV) for pulse output 3 has either exceeded its maximum positive limit (overflow: incremented beyond 7FFF FFFF hex) or fallen below its minimum negative limit (underflow: decremented below 8000 0000 hex). This signifies that the cumulative pulse count for output 3 has gone out of its defined 32-bit range, wrapping around to the opposite extreme, and can no longer accurately represent the total number of pulses.

This flag activates if the Pulse Value (PV) for pulse output 3 experiences an overflow or underflow while an interrupt input is received, or during the execution of the IFEED(892) instruction when a specified number of pulses is being moved and the origin is defined. This indicates a data integrity issue within the pulse counter, specifically during interrupt-driven feeding operations where the PV limits are exceeded.

This word stores a specific error code if a fatal pulse output error occurs for pulse output 2. It also stores a code if pulse output 2 is stopped due to a limit input (CW or CCW) when the limit input function is set to be always enabled in the PLC Setup. The value stored in A438 provides specific information about the cause of the pulse output stop, requiring further interpretation.

This word stores a specific error code if a fatal pulse output error occurs for pulse output 3. It also stores a code if pulse output 3 is stopped due to a limit input (CW or CCW) when the limit input function is set to be always enabled in the PLC Setup. The value stored in A439 provides specific information about the cause of the pulse output stop, requiring further interpretation.

This word stores a specific error code if a fatal pulse output error occurs for pulse output 0. It also stores a code if pulse output 0 is stopped due to a limit input (CW or CCW) when the limit input function is set to be always enabled in the PLC Setup. The value stored in A444 provides specific information about the cause of the pulse output stop, requiring further interpretation.

This word stores a specific error code if a fatal pulse output error occurs for pulse output 1. It also stores a code if pulse output 1 is stopped due to a limit input (CW or CCW) when the limit input function is set to be always enabled in the PLC Setup. The value stored in A445 provides specific information about the cause of the pulse output stop, requiring further interpretation.