The case in question was reconstructed based on the log analysis.The reported reboot could be confirmed and was caused by a memory overload of a processor on the main processor board.In case of a reset of the processors on the main processor board the therapy is discontinued for maximum 15 seconds.Afterwards, the therapy will resume with the previous valid ventilation mode and settings as is could be confirmed for the current case.The root cause for the high memory allocation could not be identified.No hints were found pointing to a potential hardware failure.As an usb stick was permanently installed it was requested for investigation.The analysis of the usb stick has not revealed any abnormalities.The usb stick was connected to a laboratory device.During operation in different system states and modes no reboot or any log sequences comparable to the complained device arose either.After the device had been in operation for further 6 months, another log evaluation was carried out with regard to reoccurrence of any reboots.The log contained neither reboots nor any indication for an increased memory allocation.Besides this, it was found that the device was kept in standby/ operation for months without switching the device off.Such extended periods bear a risk, as some safety systems can only be checked during the start of the device.The ifu provides a respective warning in chapter "turning on perseus" and recommends at least a monthly restart.Finally, the exact root cause could not be determined.It can be concluded that the device reacted as specified on a detected memory allocation and has triggered a reboot which solved the issue.
|