BioStar 1 - BioConnect · This presentation contains information that is confidential and...

BioStar 1.92 November 2016 Kate Yu

1.92v

DISCLAIMER

This presentation contains information that is confidential and proprietary to Suprema Inc. and is solely for the use of Suprema Inc. personnel. No part of it may be used, circulated, quoted, or reproduced for distribution outside Suprema Inc. If you are not the intended recipient of this report, you are hereby notified that the use, circulation, quoting, or reproducing of this report is strictly prohibited and may be unlawful. No representations or warranties, express or implied, are made as to, and no reliance should be placed on, the accuracy, fairness or completeness of the information presented or contained in this presentation. © 2016 Suprema Inc. All rights reserved

Contents

Supported BioStar2 Device, New Feature, Fixed Bug, and Issue

BioStar 1.92 Preview

BioStar 1 & BioStar 1.92

Frequently Asked Questions

Q&A

BioStar 1.92 Introduction

1.92v

BioStar 1 & BioStar 1.92

1.92v

BioStar1 & BioStar 1.92

BioStar 1.92

BioStar 1 : It’s a comprehensive access control and time & attendance management software featuring

TCP/IP-based system architecture with intelligent IP devices and terminals

1.92v


BioStar 1.92

BioStar 1.92 : It is latest version of BioStar 1 launched on October-2016.

Many customers would like to keep the feature of BioStar1 like MSSQL and use BioStar 2

device with BioStar 1 device. To meet the customer’s requirement, we released BioStar 1.91

and then, BioStar 1.92.

1.92v


BioStar 1.92

BioStar 1.92

BioStar 2 devices basically follow the rules and concepts of the BioStar 1 system. BioStar 2

devices have expanded sets of features and more capabilities than BioStar 1 devices. The

features and capabilities of BioStar 2 devices are constrained by the features and capabilities of

the BioStar 1 system to maintain the consistency with the BioStar 1 system.

1.92v


BioStar 1.92

BioStar2 devices don’t support all feature like BioStar1 device even though you use BioStar 1

system.

BioStar 1.92 (Limitation)

1.92v


BioStar 1.92

BioStar 1.92 (Limitation)

Anti-Passback Zone

Muster Zone

Entrance Limit Zone

Interlock Zone

Access Zone

Fire Alarm Zone Wiegand - User ID

Wiegand Legacy Mode

BioStar2 devices don’t support all feature like BioStar1 device even though you use BioStar 1

system.

Only APB and Fire alarm zone can be supported by BioStar2 RS485 Master and Slave device.

Command Card

Unlock Time/Lock Time

[Use Relay] option for T&A key

1.92v

Supported BioStar2 device, New Feature, Fixed Bug, Bug

1.92v

Supported BioStar 2 Devices

BioStar 1.92

BioEntry W2

October 2015 BioStar 1.9

June 2016 BioStar 1.91

October 2016 BioStar 1.92

BioStar 1 Device & BioStar1 FW

BioStation A2 BioStation 2 BioStation L2 Secure IO 2

BioStation A2 BioStation 2 BioStation L2 BioEntry W2 Secure IO 2

1.92v

Supported BioStar 2 Devices : Limitation

BioStar 1.92

BioStar 1.x devices must have BioStar 1.x firmware loaded onto the devices.

BioLite Net, BioEntry W, BioEntry Plus, Xpass, and Xpass S2 with BioStar 2 firmware will not be

compatible with BioStar 1.92.

BioStar 1 Firmware only

1.92v

New Feature & Fixed Bug

BioStar 1.92

New feature Support BioEnty W2 except Multi Wiegand Format

1.92v


BioStar 1.92

New feature Support Output port of BioStar2 device for a log event

- Log event: Auth Success, Auth Fail, Auth Duress, Access Not Granted, Door Opened, Door

Closed

Auth Success

1.92v


BioStar 1.92

Limited New feature Doesn’t support for “Access Granted Input” and “Access Not Granted Input” like BioStar 1

device

1.92v


BioStar 1.92

Bug fix Fixed the connection issue of BioStar 1.91 if there are more than 64 BioStar2 devices

1 2 3 … 63 64

BioStar 1.91

BioStar 2 Devices

1.92v


BioStar 1.92

Bug fix

The server port of BioStar2 device was

not available to use the changed port.

The server port will be 51212 internally

even though you change the port to

another number.

Fixed that the port of Biostar 2.x server of BioStar Server 1.91 was not changed by user setting

1.92v


BioStar 1.92

Bug fix

Fixed that the error of BioStar 1.91 into the report menu

The error occurred during uploading a

log of BioStar2 device.

1.92v

Bug

BioStar 1.92

Bug

- Unstable connection during uploading the image log of BioStation A2.

The client of BioStar1.92 is

stopped if BioStation A2

has an image log more

than 16 k of the image log

size.

1.92v

Bug

BioStar 1.92

Bug

- Stopped BioStar Server if BioStation A2 is ‘device->server’ mode and uses image

log.

The server of BioStar1.92 is stopped if

BioStation A2 has an image log more

than 16 k of the image log size.

Size: 18.9KB Size: 11.5KB

1.92v

Bug

BioStar 1.92

Temporal solution

- Apply the modified BS_SDK_V2.dll to C:\Program Files\BioStar\server.

Download link is as follows. http://webhard.suprema.co.kr//ExFd/13695/29428.dll

http://webhard.suprema.co.kr/ExFd/13695/29428.dll

1.92v

BioStar 1.92 Preview

1.92v

Preview: Who Should Use BIOSTAR 1.92?

BioStar 1.92

1. The expansion of BioStar 1 system If a customer who uses BioStar1 wants to use BioStar 2 devices,

they can use BioStar 1.92.

1.92v

Preview: Who Should Use BIOSTAR 1.92?

BioStar 1.92

2. The limitation of project requirement If one of a project requirement is MS-SQL, MySQL, or Oracle to use Suprema system,

you can choose BioStar 1.92.

1.92v

Preview: Who Should Not Use BIOSTAR 1.92?

BioStar 1.92

1. BioStar 1 device only If the customer wants to use BioStar 1 device only, you should use BioStar 1.9.

2. Performance issue If there is performance issue of BioStar 1.9 or lower version, you don’t need to upgrade

the system. Please contact us first.

1.92v

Preview: When is BioStar 1.92 SDK released?

BioStar 1.92

There is no BioStar 1.92 SDK.

You should use Biostar 1 SDK for V1 devices and use BioStar2 Device SDK for V2 devices.

BioStar 1.9

SDK

Biostar 1.92

+

=

BioStar 2 Device SDK V2.3.0

1.92v

Preview: BioStar Server Config

BioStar 1.92

V1 port: 1480 (Modifiable)

V2 port: 51212 (Modifiable)

1.92v

Preview: Connection Method (Server > Device)

BioStar 1.92

V1 Devices V2 Devices

Direct Mode (Default) Server > Device (Default)

TCP 1480 TCP 1470 or

1471

TCP 1480 TCP 51211

1.92v

BioStar 1.92

V1 Devices V2 Devices

Preview: Connection Method (Device > Server)

Server Mode Device > Server

TCP 1480 TCP 1480

TCP 51212 TCP 1480

1.92v

Remaining pages are about 30 pages..

1.92v

BioStar 1.92 Introduction 1. Device Menu

1 2 3 4 5

1.92v

Device Connection Mode

Device

BioStar 2 devices will be always located on the BioStar

Server tree regardless of the connection mode.

If the connection mode is server-to-device mode,

devices are located under Device tree. If the connection

mode is device-to-server mode, the devices are located

on the BioStar Server tree.

1.92v

RS485 (Master-Slave)

Device

When you configure a Master-Slave configuration through

RS485, you cannot use BioStar 1 devices with BioStar 2

devices. The RS485 protocol between BioStar 1 and 2

devices is different and are not compatible.

The RS485 mode of BioStar 2 devices

have three different values: Default, Host

and Slave.

When the device’s RS485 mode is

“Default”, the device works as a

standalone device or its RS485 mode

changes to “Slave” if it is connected to a

“Host” device through the RS485

interface.

V2 Devices

RS485

1.92v

Template On Card

Device

• Secure credential cards not supported

• Template on Card supported; V2 devices reads both CSN of

a card and template on card as default

• Access on Card issues from BioStar 2 cannot be used in

BioStar 1.92

• Cannot use same Template on Card on V1 and V2 devices

V1 Devices

V2 Devices

Template on Card option

enable/disable feature for

V1 devices

Template on Cared

1.92v

Input/Output (Trigger & Action)

Device

V1 Devices

Input/Output configuration available for

V1 devices

1.92v

Input/Output (Trigger & Action)

Device

V2 devices only has the Input tab,

because the BioStar 2 system has

adopted the Trigger-and-Action

concept

V2 Devices

1.92v

Device

V1 Devices

V2 Devices

T&A

Terminology differences only

V1.x V2.x (Device Menu)

Not use = Not use

Manual = By User

Manual Fix = Last Choice

Auto change = By Schedule

Event Fix = Fixed

1.92v

Wiegand

Device

• V2 devices support Extended mode only

• V2 devices support Card ID In/Out only

1.92v

BioStar 1.92 Introduction 2.User Menu

1 2 3 4 5

1.92v

User Information

User

You should transfer user information to RS485host and RS485 slave devices

V1 Devices

V2 Devices

You should transfer user information to RS485host only

RS485 Host RS485 Slave

RS485 Host RS485 Slave

BioStar Client

BioStar Client

TCP

TCP

RS485

RS485

1.92v

User Information

User

V2 Devices

• Department: All BioStar 2 devices do not store department information on the devices.

(BioStation and BioStation T2 only store department information)

1.92v

User Information

User

V2 Devices

• PIN: BioStar 2 devices encrypt PIN data whereas BioStar 1 devices do not. When you transfer users

from BioStar to BioStar 2 devices, the PIN data is encrypted and transferred, allowing users to use

PIN authentication on BioStar 2 devices. However, if you retrieve users with PIN from BioStar 2

devices, the PIN data is not usable because it is one-way encrypted.

Transfer

1

2

3

ID 1

PIN

ID 1

PIN

Transfer ID 1

1.92v

User Information

User

V2 Devices

1

ID 1

PIN ID 1

PIN

Transfer

ID 1

PIN

1.92v

User Information

User

V2 Devices

• Enrolling a user on slave devices: With BioStar 2 devices, you cannot enroll users on the slave

devices. On the BioStar 2 system, a slave device works as a dummy device and does not have users

on the device.

1.92v

User Profile

User

• BioStation, BioStation T2, X-Station

supported

V1 Devices

V2 Devices

• BioStation A2 supported only

• BioStation 2, BioStation L2 is not supported

• Transfer user image only

• Other features such as private Message,

Display Count, Display Duration are not

supported

1.92v

Private Authentication Mode

User

• Not supported in V2 devices

V1 Devices

V2 Devices

• Normal User / Admin User

V1 Devices

V2 Devices

• Admin User = Device Administrator

• Unable to assign device

administrator per device

• Supported in V1 devices only

1.92v

Bypass Card

User

• Bypass Card feature not supported in V2

devices

• When card is issued with “Bypass Card”, it

will trigger private authentication mode to

turn on “Card Only” mode

V1 Devices

V2 Devices

• Supported in V1 devices only

1.92v

Mifare Card Reading Mode (MSB/LSB)

MIFARE card only

• The byte order of a MIFARE card on BioStar 2 devices is opposite to the one on BioStar 1

devices. If the byte order of BioStar 1 devices is set to MSB, you need to set the byte order of

BioStar 2 devices to LSB and vice versa.

User

V1 Devices

V2 Devices

1.92v

Mifare Card Reading Mode (MSB/LSB)

User

3829120554 11100100 00111011 10111110 00101010

MSB of BioStation Byte Order

3829120554 11100100 00111011 10111110 00101010

LSB of BioStation2 Byte Order

717110244 0010101 010111110 00111011 11100100

MSB of BioStation2 Byte Order

717110244 0010101 010111110 00111011 11100100

LSB of BioStation Byte Order

1.92v

Find User

User

• All features supported

V1 Devices

V2 Devices

• Read Card not supported

1.92v

BioStar 1.92 Introduction 3.Access Group

1 2 3 4 5

1.92v

Default Access Group

Access Group

V2 Devices

With BioStar 2 devices, users are allowed to gain access when

there are no door assigned to the device. It is working just like

“Full Access”.

However, as soon as the device is assigned to a door, then it

will work like “No Access” and block users without access

groups.

1.92v

Default Access Group

Access Group

V1 Devices

V2 Devices

With V1 devices, if the device’s default access group is set to Full

Access, whether the user can gain access depends on the

matching access group. If the time when the authentication takes

place is not within the time schedule of the matching access

group, the user will not gain access. If the time when the

authentication takes place is within the time schedule, the user will

gain access.

With BioStar 2 devices, if the device’s default access group is

Full Access, the device does not use access group information

to determine if the user is allowed to gain access. This means

that the user will always gain access if the credential matching

(e.g. fingerprint, card) succeeds.

Skip

1.92v

BioStar 1.92 Introduction 4. Door & Zone

1 2 3 4 5

1.92v

Dual Authentication (Double Mode)

Door

Double Mode: Configure a

device to open only when

authenticating credentials of

two persons

V1 Devices

1.92v

Dual Authentication (Double Mode)

Door

V2 Devices

Dual Authentication = Double Mode

* Configure a door to open only when

authenticating credentials of two persons (an

ordinary user and an administrator).

1.92v

Door / Zone Configuration

Door

• Cannot use BioStar 1 devices with BioStar 2 devices for a door.

• For example, if you’ve specified a BioStar 1 device as an entry device on

the door configuration, you can choose BioStar 1 devices only as an exit

device

• Cannot use BioStar 1 devices with BioStar 2 device for a zone.

• For example, if you’ve specified BioStar 1 devices in an Anti-

passback zone as member devices, you cannot add BioStar 2

devices to the zone.

• BioStar 2 devices are only support Local Zone.

• BioStar 2 devices are supported in Anti-passback zone and Fire

Alarm zone only.

1.92v

Door / Zone Configuration

Door

Global Zone : TCP/IP and RS485 based, BioStar Server is zone master

Local Zone : RS485 based, RS485 master device is zone master * zone master : makes logical decisions and controls functionality

RS-485

TCP/IP

Local Zone Global Zone

BioStar 2 Server

M S

Global Zone Master

Zone of Biostar 2 device

1.92v

Unlock Time / Lock Time

Door


V1 Devices

V2 Devices

• Unlock Time / Lock Time not

supported

• Driven By, Unlock Trigger not

supported

1.92v

Held Open / Forced Open Alarm

Door

V1 Devices

V2 Devices

Held Open will be OFF when the door is closed

• Held Open / Forced Open alarm will NOT be OFF when the door is closed

• Administrators must click [Release alarm] from Monitoring tab

1.92v

BioStar 1.92 Introduction 5.Monitoring

1 2 3 4 5

1.92v

Monitoring

Monitoring


V1 Devices

V2 Devices

• Upload log > USB not supported

1.92v

Demonstration

1.92v


1.92v

1. What firmware versions are compatible with BS1.92? (For 1.x 2.x) -> All firmware for V1 devices -> BS2: V1.3.1_20160921 / BS A2 : V1.2.1_20160921 / BS L2 : V1.1.1_20160921 / BEW2: V1.0.1_20160920 or higher versions 2. Can we integrate the database from 1.8 to 1.92? -> The database structure is almost the same between BioStar 1.8 and BioStar 1.92-> You can upgrade your BioStar from old version to the latest version without issue. 3. Will the USB memory be supported in future updates? -> We do not have any plan for USB support yet. 4. Will Ver2 Readers be compatible for Server matching? -> Yes


1.92v

5. Is DM20 supported in Bx.1? -> Unfortunately, no 6. How many cards per user can we issue for BioStar 2 devices? -> Only 1 7. In 1.92 , how many access groups per user in V2 devices? -> Same as V1 devices, 4. 8. Will there be a tool to import BioStar 2 DB to BioStar 1.92? -> Unfortunately, no. 9. Is Biomini compatible with BioStar 1.92? -> Yes, Biomini and Biomini plus are compatible with BioStar 1.92. Biomini slim and BioMini 2 are not compatible.


Effective way to integrate with 3rd party card and RF reader

Device will verify the validity of card ID received from the RF reader and will react

upon the user information stored in device. (Unabled to distinguish the RF reader

generating the authentication event)

Wiegand Input (Legacy - 1)

Wiegand Legacy mode

Door

Door lock

Door sensor

Exit Button

Out In

Wiegand

Wiegand Input (Legacy – 2)

Wiegand Legacy mode

Card : 12345

11000000111001

User ID Card Info Template Password

BypassOption

1 12345 Yes 1111 No

Wiegand

RF Reader

Leave log information with own device IDs. APB-zone configurable.

RF Reader will be treated as an independent device. No extra verification is

necessary

Wiegand Input (Extended Mode - 1)

Wiegand Extended mode

Door 1

Door lock

Door sensor

Out In

Wiegand

Door 2

Door lock

Door sensor

Out

Door 3

Door lock

Door sensor

Wiegand

RS485

Out

Wiegand Input (Extended Mode – 3)


RF Reader

Card : 1234

5

11000000111001

User ID Card Info Template Password

BypassOption

1 12345 Yes 1111 No

243

0

(Device log)

Wiegand

Wiegand Input (Extended Mode – 2)


243

0

BioStar 1 - BioConnect · This presentation contains information that is confidential and...

Documents

Transcript of BioStar 1 - BioConnect · This presentation contains information that is confidential and...