top of page

CM500 Err06 During Deceleration: Validate the Stop, Not Just the Fault Reset

Nov 7
5 min read

A drive that runs normally but trips while slowing needs a stopping-duty investigation. Repeatedly resetting it or changing the ramp until the fault disappears does not establish that the machine now stops acceptably. Preserve the fault evidence, identify the exact stopping requirement and validate the physical result after any authorised change.


This guide uses the Coolmay CM500 manual linked from the ProSense catalogue, dated 10 March 2023. Confirm that its fault definitions and instructions match the installed drive and firmware. Electrical investigation, braking-system design and commissioning belong with competent people under the applicable current requirements; this is an evidence-gathering guide, not live-work instructions.


Original conceptual illustration of CM500 Err06 During Deceleration: Validate the Stop, Not Just the Fault Reset. Unbranded engineering concept, not a specific product or customer installation.

Original ProSense illustration. Equipment forms and signal paths are conceptual; use the supplied product documentation for actual specifications.


Key takeaways


A cleared Err06 and an acceptable stop are separate findings. Keep fault diagnosis, the required stopped state and measured stopping performance in the same acceptance record.


Err06 is a clue, not a complete diagnosis


The referenced CM500 manual identifies Err06 as deceleration overvoltage. Its cause list includes high input voltage, an externally driven motor during deceleration, a short deceleration time and absent braking equipment. That list gives several investigation paths; the fault code alone does not prove which one applies.


A stopping load can return energy towards the drive. Schneider Electric’s explanation of its ATV58 over-braking fault illustrates the resulting DC-bus voltage rise and describes how braking behaviour can affect actual stopping duration. Those product-specific settings and fault names must not be transferred to a CM500. The useful general lesson is to assess energy handling and observed motion together.


Grey Coolmay variable speed drive with front digital display, rotary control, keypad and lower terminal cover
Coolmay CM500-family drive shown in the ProSense 7.5 kW / 11 kW catalogue listing - product photograph, not a customer installation or a verified braking configuration.


Record the stop that actually failed


Before an authorised investigation changes anything, retain the displayed fault code and available history. Identify the drive model, motor, load, operating speed, stop-command source and the conditions when the event occurred. Note whether it followed a normal process stop, a speed reduction or another command. Do not assume that every stopping command uses the same configured behaviour.


Record what the machine did after the fault: whether it continued moving, how that was observed and whether the process entered its intended state. A fault indicator and a stopped-load observation answer different questions. Use existing approved monitoring where possible. Do not open energised equipment or approach moving parts simply to improve a diagnostic record.


Agree on an acceptance boundary


Define the time origin and the required end state with the responsible engineer. For example, is the process requirement measured from the PLC issuing a normal stop, from the drive receiving it, or from the start of deceleration? Is completion defined by an approved speed-feedback threshold, a process condition or another validated observation? Write down the measurement method and its limitations.


Keep normal process stopping separate from machinery safety functions. A configurable ramp, a zero-frequency display or the absence of a drive fault does not by itself demonstrate safe standstill or a certified safety function. Emergency-stop design, guarding and access conditions need their own competent assessment and validation.


Review ramp and braking duty as a system


Have the integrator review the required stopping time alongside load inertia, operating speed, repeated-stop duty and any external forces driving the load. Longer deceleration may be a permitted option for some processes; for others it would breach the requirement. Treat any proposed change as an engineering decision with an agreed test and recovery plan.


If braking equipment is proposed, its suitability must be confirmed for the exact drive and duty. The CM500 manual distinguishes drive sizes and braking arrangements and warns about resistor voltage and temperature hazards. A resistor’s presence, a matching kilowatt label or a catalogue photograph is insufficient evidence of correct selection, installation, protection or thermal performance.


A hypothetical acceptance result


Suppose a machine’s approved normal-stop requirement is no more than eight seconds under a defined production condition. After an authorised investigation, a proposed longer ramp prevents the previously observed overvoltage trip, but the recorded time to the agreed end state is twelve seconds. That result fails the eight-second requirement even though the drive no longer reports the same fault.


The next action is to review the stopping solution with the responsible engineer, not silently relax the requirement or defeat protection. These illustrative times are not recommended settings. Real acceptance conditions must cover the machine’s relevant operating envelope, including the loads and repeated stops specified by its designer.


No fault is not stop acceptance. Retain the original Err06 evidence. Define the required stopping state. Review actual drive and load duty. Measure the authorised test stop. Compare result with the requirement. Original explanatory infographic; examples are hypothetical.

Original explanatory diagram. It summarises the checks described in this article; it is not a wiring drawing, product screenshot or customer test result.


Close the investigation with evidence


Retain the original fault record, approved configuration change, tested conditions, timing method and observed outcome. Include any untested conditions explicitly. If the fault remains, provide the technical support team with the exact model, applicable manual revision, load description and sanitised history. Do not share passwords or access credentials.


For procurement, request a review of the complete stopping duty rather than a replacement drive chosen only by motor power. Confirm which braking components and documentation are required before ordering. Keep final installation, application suitability and acceptance with the responsible qualified people.


Source documents





Diagnostic comparison


Observation

Acceptance question

Err06 appears while slowing

What were the load, supply and commanded stop conditions?

Fault no longer appears

Does the measured stop meet the defined application requirement?

Timing requirement is missed

Which approved design change and retest are required?


Recommended equipment / related solutions


Equipment starting point: CM500 catalogue drive variant. Confirm the supplied variant, current documentation and application conditions before selection.


For selection and integration scope, review ProSense technical services and project support. Provide the exact model and the evidence described above; scope and compatibility require confirmation.



Frequently asked question


Does a successful normal stop establish a safety function?


No. The normal-stop evidence in this guide does not establish a certified safety function. Application-specific safety design and validation remain with competent people.


Send the model and diagnostic record through ProSense Instruments technical enquiries to discuss equipment selection and the appropriate next step.


Need help with your application?

For instruments and product selection, visit ProSense Instruments, email sales@prosenseinstruments.com.au or call 1800 560 854.


For monitoring and automation projects, visit ProSense Solutions or email sales@prosense.com.au.


For software enquiries, visit ProSight Software or email info@prosightsoftware.com. Confirm integration requirements for the exact instruments and system.

Recent Posts

See All

Comments


bottom of page