Wago Modular I/O System PROFIBUS DP
21 fault codes documented
Insufficient configuration data (Fault code 1, argument 1)
The Fieldbus Coupler has insufficient configuration data for operation. This issue typically arises if the PROFIBUS GSD file is defective or if parameter data was entered improperly during the configuration process, preventing proper initialization of the coupler.
Excessive configuration data (Fault code 1, argument 2)
The Fieldbus Coupler has excessive configuration data. This problem is usually caused by a defective PROFIBUS GSD file or improper entry of configuration data, which can lead to configuration mismatches and operational errors during coupler startup.
Faulty configuration byte n (Fault code 2, argument n)
A specific configuration byte 'n' within the PROFIBUS configuration telegram is faulty. This indicates a problem with the integrity or correctness of the data used to define the Fieldbus Coupler's operational parameters, affecting its proper function.
Insufficient configuration data (Fault code 3, argument 1)
The Fieldbus Coupler has insufficient configuration data, most likely because an I/O module was overlooked during the configuration process. This prevents the coupler from fully recognizing and operating all connected modules, leading to incomplete system functionality.
Excessive configuration data (Fault code 3, argument 2)
The Fieldbus Coupler has excessive configuration data, possibly due to a module being incorrectly configured multiple times or redundant data entries. This can result in configuration mismatches and operational issues, impacting coupler and module functionality.
Configuration byte (module) n is faulty (Fault code 4, argument n)
The nth configuration byte, which corresponds to a specific I/O module in the Fieldbus Coupler's setup, is faulty. This indicates an issue with the definition or data integrity for that particular module within the coupler's configuration.
Maximum input data length exceeded (Fault code 5, argument 1)
The total length of input data configured for the Fieldbus Coupler surpasses the maximum allowed limit (128 bytes, or 244 bytes from SW 03 onwards). This suggests that too many input modules are connected or their input data structures are excessively large, overwhelming the coupler's capacity.
Maximum output data length exceeded (Fault code 5, argument 2)
The total length of output data configured for the Fieldbus Coupler surpasses the maximum allowed limit (128 bytes, or 244 bytes from SW 03 onwards). This suggests that too many output modules are connected or their output data structures are excessively large, exceeding the coupler's capacity.
Compiled buffer overflow for DP process image (Fault code 6, argument 1)
The internal buffer used for compiling the PROFIBUS DP process image within the Fieldbus Coupler has overflowed. This typically indicates an internal memory allocation issue within the coupler, likely due to a complex or overly extensive configuration that exhausts the available buffer space.
Overflow of the internal buffer memory for the inline code (Fault code 1, argument 1)
The internal buffer memory, which stores the inline code within the Fieldbus Coupler, has overflowed. This condition usually points to a significant hardware fault or a firmware issue affecting the coupler's internal processing capabilities.
Unknown data type (Fault code 1, argument 2)
The Fieldbus Coupler has encountered an unknown or unsupported data type during its operation or initialization process. This suggests a fundamental configuration error or a hardware fault preventing proper data interpretation by the coupler's firmware.
EEPROM checksum fault (Fault code 1, argument 3)
A checksum error has been detected in the EEPROM (Electrically Erasable Programmable Read-Only Memory) of the Fieldbus Coupler. This indicates data corruption in the non-volatile memory where crucial configuration or firmware data is stored, likely due to a hardware defect in the EEPROM component.
Fault during writing into the flash memory (Fault code 1, argument 4)
An error occurred while the Fieldbus Coupler was attempting to write data into its internal flash memory. This suggests a defect in the flash memory component itself or a power instability that interrupted the write operation, potentially corrupting stored firmware or configuration.
Fault during reading from the FLASH memory (Fault code 1, argument 5)
An error occurred while the Fieldbus Coupler was attempting to read data from its internal flash memory. This indicates a defect in the flash memory component or a corruption of the stored data, preventing the coupler from accessing essential operational instructions.
Changed I/O module configuration found after AUTORESET (Fault code 1, argument 6)
The Fieldbus Coupler detected a discrepancy between its configured I/O module arrangement and the physically connected modules immediately after an AUTORESET. This means the actual hardware setup of the I/O node does not match the software configuration stored in the coupler.
Reserved (Fault code 1, argument 7)
This fault code indicates an internal issue associated with a reserved function or a protected memory area within the Fieldbus Coupler. It typically points to a low-level hardware defect or an unrecoverable internal system error.
Timeout when writing into the serial EEPROM (Fault code 1, argument 8)
The Fieldbus Coupler experienced a timeout while attempting to write data into its serial EEPROM. This suggests an issue with the serial EEPROM component itself or a timing problem during the write operation, preventing persistent data storage.
I/O module(s) has (have) identified internal bus command as incorrect (Fault code 3, argument 0)
One or more I/O modules connected to the Fieldbus Coupler have reported receiving incorrect internal bus commands. This indicates a critical communication issue on the internal bus, potentially due to a faulty module, corrupted signals, or a defective coupler, leading to unreliable data exchange.
Data fault on internal bus or Internal bus interruption on Coupler (Fault code 4, argument 0)
A data fault or a complete interruption of the internal bus has occurred, originating from or directly at the Fieldbus Coupler itself. This critical issue prevents any communication with all connected I/O modules, rendering the entire node inoperable.
Internal bus interrupted after I/O module n (Fault code 4, argument n)
The internal bus communication is interrupted immediately after the nth I/O module in the node. This means that all modules physically located after module 'n' are not communicating with the Fieldbus Coupler. The specific module 'n' can be identified by the number of blink pulses on the I/O LED.
Internal bus fault during register communication with the I/O module n (Fault code 5, argument n)
An internal bus fault occurred specifically during attempts to communicate with the internal registers of the nth I/O module. This indicates a problem with the module's internal registers or its ability to correctly process and respond to commands over the internal bus, affecting its functionality. The module 'n' is identified by the number of blink pulses.