PowerFlex 700S: HIM CopyCat Is a Backup, Not Proof

After the replacement is restored and independently verified, the new PowerFlex 700S can reproduce the parameter image saved in the HIM. The transfer alone does not prove that embedded logic or every port-associated setting moved with it.

Transfer boundary

The term HIM here means the drive’s human interface module. Its CopyCat function can hold a saved parameter image. Moving the HIM from a damaged drive to a replacement does not, by itself, copy the damaged drive’s current configuration; the required image must already have been written to the HIM.

Memory Storage > HIM CopyCat > Device to HIM identifies the save direction: the device is the source and the HIM is the destination. That operation must occur while the source drive remains operational enough to expose its configuration. If the drive failed before the save, installing its HIM on another drive does not create a current backup retroactively.

Check 1: Existing HIM image

Read the HIM’s memory inventory before connecting it to the replacement. The deciding reading is the presence of a CopyCat image intentionally created from the failed drive.

1. Image present: expect the HIM to list a stored drive image that can be selected for restoration. Continue to Check 2.
2. No image present: the HIM contains no demonstrated backup to restore. Recover the configuration from another documented backup, an engineering record, or the damaged drive if it can still communicate.
3. Image identity uncertain: do not write it into the replacement. Compare its stored description and configuration details with maintenance records before proceeding.

A readable display is not proof that a parameter image exists. Normal operator screens and a CopyCat memory image are different resources. Likewise, a previous save can be older than the configuration active at the time of failure. Record the image identity before using it.

Check 2: Replacement configuration

Compare the failed and replacement assemblies before restoring anything. Read the product labels and installed-option inventory rather than relying on cabinet position or appearance. The expected result is a replacement configuration compatible with the saved parameter set.

1. Matching base drive and installed options: continue to Check 3.
2. Different base drive: stop the bulk restore. Determine parameter compatibility from the applicable product documentation.
3. Different option or port population: document every difference and continue only after deciding how the missing, added, or relocated device will be configured.

A parameter image is interpreted by the destination device. A setting that addresses unavailable hardware can be rejected, ignored, or left ineffective. Conversely, a newly installed option can retain defaults because no corresponding data existed in the saved image. A completed copy therefore confirms data movement, not configuration equivalence.

Check 3: Logic ownership

Determine what “logic control” means in this installation. Drive functions assembled from parameter selections, references, limits, and digital-I/O assignments are parameterized behavior. They move only to the extent that their defining parameters are present in the CopyCat image.

A separately developed control program is different. Compiled logic, source code, retained application data, and parameter values can occupy different memory objects even when they execute in the same drive assembly. Identify the logic by inspecting the project records and the drive’s application or programming interface.

1. No separate program is listed: treat the function as parameter-based, then continue to Check 4.
2. A separate program is listed: locate its independent backup and download procedure. Do not use a successful parameter restore as evidence that the program transferred.
3. Ownership remains unclear: trace one distinctive sequence from its input through the drive configuration. If the sequence depends on instructions rather than parameter assignments, recover the program separately.

The practical test is storage ownership: determine which component owns the executable object. The HIM image can be trusted only for objects that its inventory explicitly contains.

Check 4: Port and option scope

Do not interpret “device” as “every device reachable through every port.” A drive assembly can expose the base drive, the HIM, and attached option devices as separate parameter owners. The CopyCat menu path proves the selected transfer direction, but it does not identify the scope of every stored object.

1. Inventory the base drive and each populated port on the failed assembly using the saved records or any remaining diagnostics.
2. Open the HIM image inventory and identify the devices or parameter groups represented there.
3. Compare that inventory with the replacement assembly port by port.
4. For every device absent from the image, use that device’s documented backup or configure it separately.

Check 4 expects a one-to-one accounting: every required parameter owner must map either to an object in the HIM image or to a separate restoration action. If an attached device has no mapped source, its configuration remains unresolved even when the base-drive copy reports success.

Restore procedure and acceptance checks

Perform the restore only after the four checks identify a valid image, a compatible destination, the location of any separate logic, and the scope of port-owned parameters.

1. Record the replacement drive’s initial identity, option inventory, and parameter state.
2. Install or connect the HIM according to the equipment procedure.
3. Select the verified CopyCat image and invoke the operation that writes the stored HIM image to the replacement device. Confirm the displayed source and destination before accepting the command.
4. Record every rejection, skipped item, or transfer message. Resolve each item rather than repeating the copy blindly.
5. Restore any separately stored logic and any option-device configuration not represented in the HIM image.
6. Apply the required restart or initialization action indicated by the device after the write.

Use numbered acceptance checks before returning the machine to automatic control:

1. Check 1: expect the replacement identity and installed-option inventory to match the approved replacement configuration.
2. Check 2: expect the CopyCat operation to finish without unresolved transfer errors or skipped required objects.
3. Check 3: expect recorded critical parameters—command source, references, limits, I/O assignments, protective settings, and communication configuration—to equal the approved backup values.
4. Check 4: expect each populated port and option device to appear in the intended location and report its intended configuration.
5. Check 5: with motion inhibited, expect input status, output status, permissives, interlocks, and commanded references to change according to the control design.
6. Check 6: during a controlled functional test, expect direction, reference tracking, stopping behavior, interlocks, and any drive-resident sequence to match the documented machine operation.

Frequently asked questions