User's Manual
Table Of Contents
- 1 About this manual
- 2 Grouped safety messages
- 3 Product description
- 4 Design and Function
- 5 Installation
- 6 Start-up
- 6.1.1 Service switch
- 6.1.2 Cold start
- 6.1.3 Starting the service mode
- 6.1.4 Starting the service mode and setting the service IP address
- 6.1.5 Starting the terminal software / warm start
- 6.2.1 Communication
- 6.2.2 Comparing finger templates
- 6.2.3 1-click installation
- 6.2.4 Configuration
- 6.3.1 Start-up procedure
- 6.5.1 Ethernet settings
- 6.5.2 Host interface
- 6.5.3 Reader settings
- 6.1.1 Service switch
- 7 Operation
- 8 Maintenance
- 9 Packaging / returns
- 10 Disposal
- 11 Index
Design and Function Manual
24 04043988 - 02/2014 B-eco
4.2 System connection
4.2.1 Communication principle
Communication between the terminal and a higher-level host computer usually
takes place via an Ethernet network.
Terminal software
B-Client PDC6
Communication
software
B-COMM
Customer
application
LAN
B-eco Host computer
Data exchange between the B-Client PDC6 terminal software and the customer
application takes place by means of the B-COMM communication software.
The communication software transfers the data recorded by the terminals to files or
sends it to the customer application via a defined interface.
4.2.2 Parameterization
The various terminal functions mainly depend on the set parameters. Parameter
setting allows extensive adaptation to a wide range of applications. A parameter
setting changes the currently valid parameters and stores the new ones in the
memory of the terminal. The required parameters are provided by the customer
application and transferred to the terminal in form of parameter records.
4.2.3 User rights
Information required for authorizations is provided by the customer application in
the form of personnel master records.
All the information on a specific badge number or group is stored in the master
record. The master record contains information on authorizations, time profiles,
person-related display texts and the PIN number.
Master records can be saved in the terminal. This allows the terminal itself to decide
whether a booking is authorized. Master records can be transmitted to the terminal
at any time. The currently valid master record is then overwritten. Individual master
records can be deleted from the host. Likewise, master records can be requested
from the host. The number of master records that can be loaded in the terminal
depends on the licensed memory configuration.
Whether a booking is authorized can also be requested by contacting the host in
"online" mode. In this case, no master records are required in the terminal.