Product

Component

Firmware running DRS below version 2.34 (all existing firmware as of 14 July 2005)

Symptoms

If the drum stop command is the first command issued after a reset or a safety loop break, this can produce unexpected drum oscillations. If the drum stop command is followed by a drum move, the oscillations will become even worse.

How to reproduce:

• After a reset, type drum stop (or drum stop followed by drum move) before any other drum command is issued.
  OR
• Immediately after the safety loop has been broken and closed, type drum stop (or drum stop followed by drum move) before any other drum command is issued.

Expect to see one of two things:

• Drum does not do anything obvious, but you may be able to hear an unusual pitch or hum. Try to move the drum by hand; it should be able to move within a small range. (To see how the drum should behave normally, enter command drum init, followed by drum stop, and then try to move the drum by hand.)
  OR
• Drum starts oscillating very quickly around a small range.

Cause

Solution

This problem is fixed in DRS version 2.34, but as of 14 July 2005, no firmware releases include DRS v2.34. The commands for checking the DRS version are:

access dev
list version version

In the meantime, be aware that this problem exists, and avoid entering the drum stop command (or drum stop followed by drum move) after a reset or safety loop break, as the resulting symptoms could be mistakenly diagnosed as a hardware failure.

Also note that even if you don’t enter these commands under these circumstances, it doesn't necessarily mean that this firmware problem is not is to blame for the drum oscillation problem. In certain situations involving safety loop breaks or media fly-offs, the MCE firmware itself can issue these commands and trigger the problem automatically.

Technical contact(s)

Cedric Galere

Submitted by

Cedric Galere

Date submitted