EVIS

<< Click to Display Table of Contents >>

Navigation:  Components > Manufacturer specific drivers >

EVIS

This driver is used to connect the EVIS system to the EisBaer.

 

Data points of the component:

Name

Type

Function

Export user (file name)

Input

Specifies a file name -> the currently known users are exported to the specified file.

Import user (file name)

Input

Specification of a file name -> users are imported from the specified file (CSV).

Diagnosis [Text]

Output

Error messages are output here. Attention: Diagnostic or debug outputs are only intended for error cases. Please use only with consultation with the support team! If used, these can significantly affect the performance of the service.

Last access denial (user)

Output

The user name of the last access denial is output here (see User Administration).

Last access denied (user ID from card)

Output

see above only output of the corresponding User ID as stored on the card

Last access denied (User ID)

Output

see above only output of the corresponding User-ID, as defined in the user administration.

Last access denial (card ID)

Output

see above only output of the corresponding Unique-ID, as stored on the card

Last access denial (Reader)

Output

see above only output of the name of the reader where the card was used.

Last access (user)

Output

Theuser name of the last access permission is outputhere (see User Administration) .

Last access (user ID from card)

Output

see above only output of the corresponding User-ID, as stored on the card

Last access (User ID internal)

Output

see above only output of the corresponding User-ID, as defined in the user administration.

Last access (card ID)

Output

see above only output of the corresponding Unique-ID, as stored on the card

Last access (reader)

Output

see above only output of the name of the reader where the card was used.

Export log data (All)

Input

All access data (log) are exported to a file.

Export log data (internal user ID)

Input

All access data concerning the specified internal user number are exported to a file.

Export log data (card user ID)

Input

All access data concerning the specified card user number will be exported to a file.

Export log data (card ID)

Input

All access data concerning the given card ID will be exported to a file.

Driver On/Off

Bidirectional

Turns the driver on/off

Access denied Trigger (global)

Output

A TRUE is output here if a card was denied at any reader (See User Management)

Access trigger (global)

Output

A TRUE is output here, if a card was accepted at any reader (see user administration).

 

For each defined reader a subfolder (named after the assigned name of the reader) with reader-specific data points is created.

Name

Type

Function

Cash data da

Output

Flag from Status Byte (contact EVIS for details)

Data carrier present

Output

Flag from status byte (contact EVIS for details)

Data carrier stuck

Output

Flag from Status Byte (contact EVIS for details)

Data carrier move OK

Output

Flag from status byte (contact EVIS for details)

EVIS Passive

Output

Flag from Status Byte (contact EVIS for details)

FW version

Output

FW version of the reader

Valid card inserted

Output

Shows whether a valid (see user administration) card is currently "inserted" for this reader.

Valid card inserted (Last user ID from card)

Output

User ID (stored in card) of the last valid card

Valid card inserted (Last internal user ID)

Output

User ID (internal according to user administration) of the last valid card

Valid card inserted (Last card ID)

Output

Card ID (stored in card) of the last valid card

Valid card inserted (Last internal user name)

Output

User name (internal according to user administration) of the last valid card

Valid card inserted (Trigger)

Output

Triggered with TRUE, if a valid card was detected.

Export log data (all)

Input

All access data (log) (concerning this reader) are exported to a file.

Export log data (for internal user ID)

Inbox

All access data (concerning this reader) regarding the specified internal user number are exported to a file.

Export log data (for internal card user ID)

Inbox

All access data (concerning this reader) regarding the given card user number will be exported to a file.

Export log data (for card ID)

Inbox

All access data (concerning this reader) regarding the given card ID will be exported to a file.

Spec. application da

Output

Flag from Status Byte (contact EVIS for details)

Status Info Byte

Output

Status Info Byte (as value)

Status Info Text

Output

Status Info Byte (evaluated as text)

Synced

Output

Indicates whether the system is synchronized with the reader.

Key pressed

Output

Flag off Status Byte (contact EVIS for details)

Invalid card inserted

Output

Indicates whether an invalid (see user administration) card is currently "inserted" for this reader.

Invalid card inserted (Last user ID from card)

Output

User ID (stored in card) of the last invalid card

Invalid card inserted (Last internal user ID)

Output

User ID (internal according to user administration) of the last invalid card

Invalid card inserted (Last card ID)

Output

Card ID (stored in card) of the last invalid card

Invalid card inserted (Last internal user name)

Output

User name (internal according to user management) of the last invalid card

Invalid card/PIN (Trigger)

Output

Triggered with TRUE, if an invalid card was detected.

Time/Access Data there

Output

Flag from status byte (contact EVIS for details)

 

Properties:

Name

Standard

function

Scanner

0

Here the scanners connected to the system are defined. Here a name can be assigned and the Modbus address of the scanner (DIP switch on the device) can be set.

COM Port

1

Setting for the communication port

BAUD Rate

9600

Setting for the transmission speed

Timeout [ms]

500

Timeout time

Polling Delay [ms]

200

Time offset for data transmission

Protocol

EVIS Frame

transfer protocol

Driver On/Off

 

Turns the driver on or off

 

 

User management:

The users should be able to be managed at runtime. Accordingly, we can not create user-specific data points because they can not be linked at runtime.

Therefore, the access control takes place at the reader level. Thus, there is an SP for each reader which is triggered when a valid card (or PIN entry) has been recognized on the respective reader.

In user administration, users can now be defined and specified for which readers the user has access.

 

e.g. 3 readers defined (R1, R2 and R3), which are e.g. Grant access to 3 different rooms

User 1 - Card Number ABCFEF1111 - Access for Reader 1 and 2

User 2 - card number ABCFEF2222 - access for Reader 2 and 3

If user 1 now holds his card to reader R1, then he gains access - the data entry "valid card inserted" is activated as long as the card is created. In addition, the data points are updated to indicate who has successfully gained access (globally and at the reader level).

If user 1 now holds his card to reader R3, he will not be allowed to enter and the data entry "valid card inserted" from reader 3 will not be set to TRUE (but the data item "invalid card inserted" should also be triggered here)

The user administration can be done with any program that can generate CSV files. Comments are supported (indicated by #). Seperator is the semicolon. A user line looks like this:

<Username>; <card number / PIN>; <internaluser number>; <list of allowed reader addresses separated by comma>

 

Examples:

John Doe; E0051000018178868; 101; 1,2,3 # Allowed for Reader 1, 2 and 3

-> The card with the number E0051000018178868 belongs to Max Mustermann with the internal user number 101 and has access to all 3 readers

 

Moriz man; E0051000018178867; 102; 1 # Allowed for Reader 1

-> The map with the number E0051000018178867 belongs to Moritz Mann with the internal user number 102 has access only to Reader 1

 

Guest; 12345; 500; 1 # Allowed for Reader 1

-> The PIN 12345 can be made available to guests, so that they have access to Reader 1