|
During a monarch bronchoscopy procedure a 500-29-0-310 idm torque mismatch fault was reported.The physician was at the target, and was readjusting to place a fiducial, when the fault occurred.The account manager powered down the system and attempted to restart, however, the fault persisted when the arms were un-stowed.The physician swapped to a second scope the issue continued.The physician elected to abort the case, which is to be rescheduled.There were no reported adverse effects to the patient because of the system issues.
|
|
Auris failure analysis engineering reviewed the logs and confirmed the reported fault 500-29-0-310 ¿idm torque mismatch¿.This was reported by robotic arm 1 (id29), idm output shaft 0 (index0).This fault is reported when the torque value mismatch with the torque approximation from the current of more than 0.5 nm.The arm was tested in-house on a system level, and during arm deployment, the arm reported the same fault.The telemetry logs shows the current was not proportional to the torque, specially that fault is being triggered during arm deployment when the output shaft is not used beside while driving the system.The subject arm was returned to the original equipment manufacturer (oem) kinova, for further investigation.Upon their testing, the issue was reproduced, and root cause determined to be due to a chip failure on the driver board (u5), where the reference voltage supplied by the chip u5 is wrong.Reviewing the complaint investigations history for this failure, it revealed this is the first failure for this u5 chip reporting the torque mis-match fault and therefore considered an isolated event and random component failure.Reported issue was confirmed and cause was traced to driver board u5 chip failure.Component code: g02013.Medical device problem code: a07.Type of investigation: b24, b01, b11.Investigation finding: c0201.Investigation conclusions: d02.
|