Rs232 Interface - Dräger Perseus A500 Instructions For Use Manual

Technical data
Connections between Perseus and the DrägerService computer or the NTP server
Function Protocol
SNMP V3
TCP SNMP V3
(trap)
FTP
(command)
FTP
(command)
FTP
(data)
FTP
(data)
SNTP
DHCP
Typical data volume:
– Update of the device firmware: typically 50 MB
– Help ticket (system log for service purposes):
typically 3 MB
While using the service functions, the device
typically causes an average network load of up to
150 KB/s. During normal use, the bandwidth used
is negligibly low.
Hazardous situations
NOTE
Risk when using the device in an overloaded
network
An overload of the device due to high network
loading (e.g., caused by denial-of-service
attacks) may lead to a shut-down of the device-
side network interface. The interface will not be
available again until the device is restarted. This
function is used to protect the primary functions
of the device against unauthorized intrusion.
254
Perseus
port
UDP 161
UDP >1023
TCP >1023
TCP >1023
TCP >1023
TCP >1023
UDP >1023
UDP 67
Direction Remote port
>1023
162
21
21
>1023
>1023
123
67

RS232 interface

The RS232 interface supports the MEDIBUS.X
protocol. MEDIBUS.X is a communication protocol
for data exchange between Perseus and, e.g., the
following external medical or non-medical
equipment:
– Hemodynamic monitor
– Data management system
– Computer
– RS232 to Ethernet converter
The transferred data include the following
information:
– Settings
– Measured values
– Waveforms
– Text messages
– Alarm status
Take note of the documentation for the following
communication protocols before transferring the
data:
– MEDIBUS.X, Rules and Standards for
Implementation (9052607)
– MEDIBUS.X, Profile Definition for Data
Communication V1.n (9052608)
Instructions for use Perseus A500 SW 2.0n
Remote Connection
partner
SCG
SCG
SCG New, estab-
lished
SCG Established
SCG New, estab-
lished
SCG Established
NTP server
DHCP server