EasyManua.ls Logo

Philips IntelliVue MX800 - Alarms;INOPs from External Devices; Language Conflict with External Device Drivers

Philips IntelliVue MX800
460 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
28 IntelliBridge EC10 Module
345
Alarms/INOPs from External Devices
The IntelliBridge module itself generates INOPs, but does not generate alarms. If the external device's
alarms are on, the module transmits these to the monitor. A message in the External Device Data
window tells you either
Device Alarms Ignored or Device Alarms Accepted or No Alarms Available.
External device alarms status symbols precede some, but not all, measurement labels.
Alarms from external devices are transmitted to the monitor. For all numerics configured in the setup
menu, an alarm condition is announced at the monitor. For one or more measurements not configured
in the setup menu, an alarm is announced as a text message for the highest priority alarm. Priority is
determined at the external device.
Refer to the documentation supplied with the IntelliBridge module for details of how alarms are
announced on the monitor and the Information Center.
INOPs from the IntelliBridge Module
Language Conflict with External Device Drivers
You should avoid language conflicts between the IntelliBridge module device driver and the monitor.
Be aware that if you connect an IntelliBridge module with a different operating language to the
monitor, the monitor will show:
measurement labels in the monitor language
alarm and INOP texts in the IntelliBridge module device driver language.
the monitor is configured to accept external device alarms, but the alarms are
switched off at the external device.
INOP Text INOP Condition
!!NO DEVICE DATA
!!!NO DEVICE DATA
Communication has been lost to a connected device when
!! a medium priority INOP or patient alarm was present
!!! a high priority INOP or patient alarm was present
NO DEVICE DATA Communication has been lost to a connected device with no (or
only low priority) INOPs/physical alarms.
DEVICE UNSUPPORTED Device identification completed but no appropriate device driver
installed
DEVICE CHECK CONF. Device identification completed but communication could not be
established due to errors
DEVICE CHECK SETUP Device identification completed but communication could not be
established due to timeout

Table of Contents

Related product manuals