The examination was carried out based on the device logbook analysis as well as a laboratory examination in which the configuration at the customer's site was recreated.It was found that the reported symptoms were caused by differently adjusted baud rates at the icm/digibox input and the perseus.As a result, commands in the perseus are not interpreted correctly.In particular, package end characters are no longer recognized, so that the perseus data buffer grows continuously, and the processor load gradually increases.If due to this other processes are blocked, finally a reset is triggered.This leads to a therapy interruption of maximal 15 seconds.The therapy is then continued with the last valid settings.As initially reported, a slowed display of the real-time curves and a short-term delayed reaction during selection and confirmation of therapy settings could also be observed in the laboratory test in the run-up to the resets.The logbook also contains indications of increased processor workload as well as reboots.After adjusting the baud rate, the problem was fixed.In the already available sw version 2.03, the size of data packets in the medibus buffer is limited to avoid processor overload.In this way, the problem will be prevented in the future even if the baud rates are set differently.The distribution of the sw 2.03 will be carried out with a field safety corrective action.All devices equipped with sw versions 2.01 and 2.02 will be upgraded to sw2.03.
|