The rotaflow drive was investigated from an emtec technician with the service order report# (b)(4) on the 2019-07-24: during the in-house inspection, the drive made noise and head alarm occurred.When "head alarm" occurred, the output data from rs-232c was checked and noticed that the rotation speed on the console side and the rotation speed on the drive side were different.The rotation speed on the drive side was displayed low.Therefore the failure could be on the drive side.The error described by the customer could not be traced.In goods receipt it was noticed that the knurled nut on the mast holder is missing.After further testing it was noticed that the deep groove ball bearings are no longer 100% in order.Action: knurled nut attached.Replacing deep groove ball bearing.Rfd has passed all tests.Possible root cause: aging the device was also investigated from the getinge service technician with the maquet service order report# (b)(4) and customer order no: rma id (b)(4) on the 2019-07-26: additional work performed: investigation performed: missing knurled nut on must holder mounted (confirmed).Defective ball bearings replaced (confirmed).Burn in, calibration and final check.System test performed according to service protocol for this head error an nc was opened and investigated: in the course of the investigation of nc-17-06-011 all complaints were analyzed individually to look for patterns and causes.After evaluation of the complaints, the following defects are the most common: hot plug, sig error followed by head error, error message due to shaking / error message due to sensitivity, connection problems and hardware-error.The increase in complaints with the error "head error" is due to a user / application error.The actions have been addressed in the past to prevent application errors.Furthermore, the instructions for use of the rotaflow system see rotaflow system user manual, mcv-ga-10000703-de-11, contain detailed descriptions to prevent an "error head".In addition, the instruction manual describes how the user has to react in case of an error message so that the application can be continued if possible.Since there are several causes of errors that result in an error head (error head) message, no final root cause could be determined.It is noticeable that the evaluated error is largely due to a user error.Warning in the ifu regarding "hotplug" and label with the "hotplug" warning on the rfc have already been implemented in the past.
|