320-0062

Access PLC Configuration

Navigate to MOD function → PLC → Configuration to access the IOC file settings and review operand assignments.

Always backup the current IOC configuration before making changes

Check Operand Data Types

Examine the operand %1 mentioned in the alarm and verify its data type (BYTE, WORD, DWORD) matches the terminal capability shown as %2.

Incorrect data type changes can affect machine safety functions

Correct Size Mapping

Modify the IOC file to use appropriate operand sizes - use B operands for 8-bit, W operands for 16-bit, or D operands for 32-bit terminals.

Reload Configuration

Save changes and perform a PLC restart via MOD → PLC → Reset to reload the corrected IOC configuration.

Identify Mixed Data Types

Review the IOC file for operand %1 to check if logical markers (M, I, O) are mapped to arithmetic terminals or arithmetic operands (B, W, D) to logical terminals.

Separate Logical and Arithmetic Mappings

Ensure logical operands (M0-M4095, I0-I4095, O0-O4095) are only mapped to digital I/O terminals, not analog or counter terminals.

Use systematic operand numbering - reserve M0-M999 for digital I/O, M1000+ for internal logic

Reassign Operand Types

Change arithmetic operands to use B, W, or D prefixes for analog/counter terminals, and M, I, O prefixes only for digital terminals.

Validate Configuration

Use the PLC diagnostic function to verify all operand mappings are consistent before activating the new configuration.

Check Terminal Specifications

Verify the hardware capabilities of terminal %2 in the machine documentation to confirm supported operand types and data formats.

Review I/O Module Configuration

Access MOD → Machine → I/O Configuration to check if the terminal is configured as the correct type (digital, analog, encoder, etc.).

Match Operand to Terminal Capability

Reassign the operand to a compatible terminal type or change the terminal configuration to support the required operand type.

Changing terminal types may affect connected sensors and actuators

Update IOC Mapping

Modify the IOC file to reflect the correct operand-to-terminal assignments and ensure compatibility throughout the system.

Backup and Examine IOC File

Create a backup of the current IOC file and examine it for syntax errors, missing semicolons, or malformed operand definitions.

Validate File Structure

Check that all IOC file sections are properly formatted with correct BEGIN/END statements and proper operand syntax (e.g., M100.0, B200, W300).

Use a text editor with syntax highlighting to spot formatting errors more easily

Restore from Known Good Configuration

If corruption is suspected, restore from a previously working IOC backup or recreate the configuration using the PLC configuration wizard.

Test Configuration Incrementally

Load the corrected IOC file and test operand mappings one section at a time to isolate any remaining issues.