Bosch NurseCall Main Unit - RS-232 Interface

NurseCall Main Unit Description | en 13
Bosch Security Systems User Manual F.01U.252.699 | V1.1 | 2012.01
2.2.4 RS-232 interface
A 9-pole SUB-D connector at the rear of the housing can be used for connection to
–a printer
– a paging system
– a DECT phone system
– a PC with Alarm Management Software.
 For the hardware configuration of this interface, see Section 3.2.6 Connecting the RS-232,
page 17.
 For the programming of this interface, see Section 4.3.5 RS-232 output setting, page 27.
 For the wiring of the connector, see Section A.7.3 RS-232 socket (unit rear), page 59.
Connection to a printer
To protocol all events, a printer with serial connection (RS-232 Interface) and endless paper
should be used. Printers with a parallel port can be used together with an intermediate serial
- parallel converter.
Characteristics
– Data rate: 9600 Bauds.
– Transmission: asynchronous
– 10 bit-structure (1 start bit, 8 data bits without parity, 1 stop bit).
The operating status of the printer cannot be tested (switched on/off, paper status).
An RS-232 printer is mandatory.
Connection to a paging system
The NurseCall system uses several protocols: standard ESPA 4.4.4. with RPE670/i-page,
POCSAG, DeTeWe and Medicall 800.
 See Section A.5 Paging systems specifications, page 53 for more information about these
protocols.
Connection to a DECT phone system
The NurseCall system can transfer the received alarms to DECT handsets Multitone CH60 or
CH70.
 See Section A.6 DECT phone system specifications, page 58 for more information about
this system.
Connection to a PC using an Alarm Management Software
At connection / disconnection of a PC using an Alarm Management Software, events are
generated. The loudspeaker is disabled during the connection.
NOTICE!
The paper printout corresponds to the indication at the display of the NurseCall Main Unit.
NOTICE!
Alarms/messages arriving in the alarm buffer are repeated every 3 minutes until
acknowledgement. A technical failure, for example a power outage, is treated as an event. No
acknowledgement is therefore necessary. See Section 5.2 Consulting the alarm or event buffer,
Page 43.