Troubleshoot Incorrect CEMAT V8.0 Manual-Mode Options in Runtime

Troubleshoot Incorrect CEMAT V8.0 Manual-Mode Options in Runtime

When CEMAT runtime offers reduced-interlock manual operation instead of the required interlocked mode, inspect the drive's effective feature/permission configuration and the AS system chart together. CEMAT V8.0 documents a required system chart per AS and separate mode-enable settings. One reported recovery replaced SYSPLCxx and downloaded the CFC program, but that outcome does not establish a universal repair. Diagnose the actual chart and preserve its project-specific settings before considering replacement.

Table of Contents

Reported Configuration and Symptoms

The reported multiproject uses PCS 7 V8.1 and CEMAT V8.0. Drives and valves offer only the undesired reduced-interlock manual state, although its feature and OS-permission bits were reportedly not enabled. The C_Group faceplate also hides manual-mode selection.

These observations do not prove that a single individual block input is wrong. Record the actual installed library and faceplate versions, affected instances and online state before changing permissions.

Documented Drive Permissions

The Engineering Cemat Minerals V8.0 drive-functions table, printed page 6-24, distinguishes:

Drive commandFeature bitOS_PermissionLog bitSwitch to manual mode131Manual, non-interlocked165Manual, only protection177Manual, reduced interlocks186

Compare those fields for the applicable drive types with the intended engineering design. Do not enable a less-interlocked mode to make a selection visible. The table does not, by itself, diagnose the separate C_Group display. See the CEMAT engineering manual.

Inspect and Reconcile the System Chart

The manufacturer's new-project sequence on printed page 3-42 requires the system chart once in each AS:

  1. In Plant View, create the intended hierarchy folder for the system chart.
  2. Copy SYSPLC00 from the project library into that folder.
  3. Rename it for the AS number, for example SYSPLC02.

For an existing project, treat this as a reference configuration, not permission to delete its chart. Compare the actual SYSPLCxx with the matching library chart in an engineering copy. The manual's checklist also calls for checking hierarchy assignment and system-block runtime positions.

The reported recovery used a chart copied from another project and a complete CFC download. Its source-project settings and the precise defect were not identified. Prefer a traceable comparison against the matching library before planning a supported correction.

Verification

Check the effective drive-mode permissions and visible choices after an approved change. Confirm that the intended interlocked manual operation is available and undesired alternatives remain excluded. Investigate the group faceplate separately if its selector is still hidden.

Verify the system chart's AS identity, hierarchy placement and runtime-order requirements against the CEMAT configuration. Successful downloading alone is insufficient; observe the intended runtime behavior and check affected group/drive functions.

Limitations and Operational Precautions

The root cause of the reported symptoms is unresolved. The manufacturer's chart-placement instructions do not establish that replacing any SYSPLCxx fixes manual-mode faults or that another project's chart is interchangeable.

Preserve the original chart, parameters, interconnections and online operating state. Compare project-specific settings before accepting a replacement. A complete CFC download must be planned against the actual CPU and running-process requirements, including rollback and any required outage.

Do not bypass interlocks or broaden permissions as a diagnostic shortcut. Compatibility of the reported PCS 7 V8.1/CEMAT V8.0 pairing is not independently established by the opened engineering manual.

Engineer FAQ

Should reduced-interlock mode be enabled to fix a hidden selector? That changes the permitted operation and is not a justified repair.

Is chart replacement a confirmed general solution? It is a reported recovery with an unidentified cause.

Must the group and drive symptoms share a cause? Their common timing is evidence to investigate, not proof.

Technical References

Related Articles

Related Tags

20 respuestas