Reliance 57C413B/57C423 common memory module

The initial installation steps are crucial and orderly:

Cut off the power supply to the rack.

Remove the module from the anti-static bag without touching the back connector.

Activate battery: Remove the battery from the battery holder at the opening on the right side wall of the module, remove the insulation tape, and place it back in the correct polarity ("+" for "+").

Choosing the correct slot for insertion: This is a crucial step.

If used as a system core (bus arbitration), it must be inserted into slot 0. For 57C413b, its adjacent slot on the right (slot 1) must be a processor module or empty (logically occupying 2 slots of space). For 57C423, the three slots on its right (slots 1-3) must be processor modules or empty (logically occupying 4 slots of space).

If used only for data storage, any even numbered slot (2, 4, 6...) can be inserted, and its adjacent slot on the right must be empty (logically occupying 2 slots of space).

Verification after power on: If in slot 0, the processor's power on diagnosis will automatically verify; If in other even numbered slots, the I/O monitoring function of the programming execution software needs to be manually tested for read and write.

The module replacement process is similar to installation, but special attention should be paid: the replacement operation will affect the tasks and variables in the rack. Before operation, it is necessary to refer to the manual appendices (Appendix E for DCS 5000 rack and Appendix F for AutoMax rack) to understand the specific impacts (such as whether application tasks are deleted and how data status changes), and stop all running tasks in advance.

Battery replacement is an important part of preventive maintenance. When the "BAT. OK" light goes out, it should be operated after the power is turned off. The buffering time provided by supercapacitors allows for safe replacement. The designated Reliance Electric M/N 57C385 lithium battery must be used for replacement, and charging, dismantling, high-temperature heating, or incineration of the battery is strictly prohibited. When replacing, ensure that the module has been powered on for at least 8 minutes to fully charge the supercapacitor and maintain memory when the battery is removed.

Programming and Configuration: Variable Control and Storage Strategy

In the AutoMax environment, variables have two control types: common and local. Control "refers to whether a variable is exclusively accessed by a single task (local) or can be read and written by multiple tasks within the rack (common). Declaring variables as public or local is done within the application task.

The storage location of variables is determined by the system hardware configuration:

Local variables: stored on the processing module that runs the task.

Public variables: default stored on the processing module. However, if the universal memory module is installed in slot 0, all common variables are stored on that module, greatly saving processor memory resources. This means that 'public' refers to access control attributes, rather than necessarily physical storage locations.

Universal memory module located in non-zero even slots: The system considers it as two "universal" I/O modules each containing 32K registers. The variables defined on this module belong to I/O variables (the system considers all I/O variables as common), but their physical storage still follows the above rules - stored on the processing module of the single processor rack or on the general-purpose memory module in slot 0 (if any).

The configuration method varies depending on the programming execution software version and module slot:

V3.0 and later versions: Use the "Rack Configurator" menu for graphical configuration, similar to other modules.

V2.1 and earlier versions: require a special configuration task to define, using statements such as MEMDEF (defining volatile common variables), NVMEMDEF (defining non-volatile common variables), or IODEF (defining variables by address when the module is in a non-zero slot) for precise configuration. The configuration task defines all common variables and is a necessary step before running the application task.

Diagnosis and Troubleshooting Guide

Module faults can usually be diagnosed through the front panel LED and processor error codes.

The 'SYSTEM WATCHDOG' light goes off (module in slot 0): At the same time, the processor displays error codes 4.0-4.6, indicating that the module's power on diagnosis has failed. Systematically replacing modules and processors for troubleshooting, or gradually removing other modules to isolate the problem, may ultimately require replacing the backplane.

The "BAT. OK" light goes out: Possible reasons include the battery insulation tape not being torn, incorrect battery orientation, missing or failed battery, and power failure. Check and correct after power outage.

Data error: Output exception. Check if the module slot is correct, if the task referencing the module variable declares it as COMMON, and if multiple tasks are writing to the same variable simultaneously. Use the variable monitor or I/O monitor of the programming execution software to test access. Hardware issues need to be isolated by replacing modules and processors.