Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:release_note_250 [2021/01/18 14:52] yjjung |
en:release_note_250 [2023/08/17 13:36] (current) |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| <callout type="warning" icon="true"> | <callout type="warning" icon="true"> | ||
| - | <wrap em>CAUTION</wrap> \\ | + | **CAUTION** \\ |
| You need to re-build SDK to SDK version upgrade as BioStar 2 Device SDK structure has been changed. | You need to re-build SDK to SDK version upgrade as BioStar 2 Device SDK structure has been changed. | ||
| </callout> | </callout> | ||
| Line 18: | Line 18: | ||
| <text size="x-large">1.</text> SEOS Card(Including Elite Key, RF performance improvement) feature supports iClass SEOS card configuration via Smart card layout.\\ | <text size="x-large">1.</text> SEOS Card(Including Elite Key, RF performance improvement) feature supports iClass SEOS card configuration via Smart card layout.\\ | ||
| - | * API [[BS2_GetCardConfigEx]] has been added | ||
| - | * API [[BS2_SetCardConfigEx]] has been added | ||
| - | * Structure [[Configuration API#BS2CardConfigEx]] has been added | ||
| - | <text size="x-large">2.</text> CoreStation feature supports CoreStation which is the new Suprema device. CoreStation, which works as a controller of the master, performs overall functions along with Slave devices. The difference from other devices is CoreStation can't get credential input such as card or fingerprint since it works only as a controller. Also, CoreStation configuration and control setting is supported via BioStar because it doesn't have a separate UI. | + | * Add API [[BS2_GetCardConfigEx]] |
| + | * Add API [[BS2_SetCardConfigEx]] | ||
| + | * Add structure [[Configuration API#BS2CardConfigEx]] | ||
| - | * API [[BS2_GetSlaveExDevice]] has been added | + | <text size="x-large">2.</text> CoreStation feature supports CoreStation which is the new Suprema device. CoreStation, which works as a controller of the master, performs overall functions along with Slave devices. The difference from other devices is CoreStation can't get credential input such as card or fingerprint since it works only as a controller. Also, CoreStation configuration and control setting is supported via BioStar because it doesn't have a separate UI.\\ |
| - | * API [[BS2_SetSlaveExDevice]] has been added | + | |
| - | * Structure [[Configuration API#BS2Rs485SlaveDeviceEX]] has been added | + | |
| + | * Add API [[BS2_GetSlaveExDevice]] | ||
| + | * Add API [[BS2_SetSlaveExDevice]] | ||
| + | * Add structure [[Configuration API#BS2Rs485SlaveDeviceEX]] | ||
| <text size="x-large">3.</text>Intrusion Alarm Zone supports following features. Normally Intrusion detection system sends signals when the installed sensor on the security facility detected intrusion or abnormal signals and it has two different ways - unmanned and local. In the Unmanned Intrusion detection system, security guards from the control center which is the remote location perform tasks when the an abnormal situation. On the other hand, in the Local Intrusion detection system, resident security guards from its own control center perform the overall task. BioStar targets users who feel pressured by the cost of an Unmanned intrusion system or whose local security guards based on their own Intrusion detection system. Currently, a normal Intrusion Alarm Zone(biostar1.X) is provided, and 3rd party alarm system intrusion detection | <text size="x-large">3.</text>Intrusion Alarm Zone supports following features. Normally Intrusion detection system sends signals when the installed sensor on the security facility detected intrusion or abnormal signals and it has two different ways - unmanned and local. In the Unmanned Intrusion detection system, security guards from the control center which is the remote location perform tasks when the an abnormal situation. On the other hand, in the Local Intrusion detection system, resident security guards from its own control center perform the overall task. BioStar targets users who feel pressured by the cost of an Unmanned intrusion system or whose local security guards based on their own Intrusion detection system. Currently, a normal Intrusion Alarm Zone(biostar1.X) is provided, and 3rd party alarm system intrusion detection | ||
| - | On/Off device integration will be provided in the near future. In the long term, a professional local control system that can be applied to Video and Visual map features is a goal. | + | On/Off device integration will be provided in the near future. In the long term, a professional local control system that can be applied to Video and Visual map features is a goal.\\ |
| - | + | ||
| - | + | ||
| - | * API [[BS2_GetIntrusionAlarmZone]] has been added | + | |
| - | * API [[BS2_GetIntrusionAlarmZoneStatus]] has been added | + | |
| - | * API [[BS2_SetIntrusionAlarmZone]] has been added | + | |
| - | * API [[BS2_SetIntrusionAlarmZoneAlarm]] has been added | + | |
| - | * API [[BS2_RemoveIntrusionAlarmZone]] has been added | + | |
| - | * API [[BS2_SetIntrusionAlarmZoneArm]] has been added | + | |
| - | * Structure [[Configuration API#BS2IntrusionAlarmZoneBlob]] has been added | + | |
| - | <text size="x-large">4.</text>Ethernet Zone is the feature that a specific device(Not BioStar V2.x) performs as Zone Master using Ethernet TCP communication method between devices(Master <-> Member). Currently, it supports corresponding features to the existing 1.x Entrance Limit, Fire Alarm Zone. | + | * Add API [[BS2_GetIntrusionAlarmZone]] |
| + | * Add API [[BS2_GetIntrusionAlarmZoneStatus]] | ||
| + | * Add API [[BS2_SetIntrusionAlarmZone]] | ||
| + | * Add API [[BS2_SetIntrusionAlarmZoneAlarm]] | ||
| + | * Add API [[BS2_RemoveIntrusionAlarmZone]] | ||
| + | * Add API [[BS2_SetIntrusionAlarmZoneArm]] | ||
| + | * Add structure [[Configuration API#BS2IntrusionAlarmZoneBlob]] | ||
| - | * API [[BS2_GetDeviceZone]] has been added | + | <text size="x-large">4.</text>Ethernet Zone is the feature that a specific device(Not BioStar V2.x) performs as Zone Master using Ethernet TCP communication method between devices(Master <-> Member). Currently, it supports corresponding features to the existing 1.x Entrance Limit, Fire Alarm Zone.\\ |
| - | * API [[BS2_SetDeviceZone]] has been added | + | |
| - | * API [[BS2_RemoveDeviceZone]] has been added | + | |
| - | * API [[BS2_SetDeviceZoneAlarm]] has been added | + | |
| - | * Structure [[Configuration API#BS2DeviceZoneConfig]] has been added | + | |
| - | <text size="x-large">5.</text>USB log and User export support following features. It is used as T&A using Export/Import user & log data via USB at site where network connection is unavailable. (Usage Scenario) Users are registered at the head office where BioStar server is installed and USB memory which includes registered users is sent to the site, and T&A result is generated with log of the previous month at the beginning of every month. Practically it should be supported as a file type so that it can be handled via USB copy even when this USB data is re-forwarded. | + | * Add API [[BS2_GetDeviceZone]] |
| + | * Add API [[BS2_SetDeviceZone]] | ||
| + | * Add API [[BS2_RemoveDeviceZone]] | ||
| + | * Add API [[BS2_SetDeviceZoneAlarm]] | ||
| + | * Add structure [[Configuration API#BS2DeviceZoneConfig]] | ||
| - | * API [[BS2_GetUserListFromDir]] has been added | + | <text size="x-large">5.</text>USB log and User export support following features. It is used as T&A using Export/Import user & log data via USB at site where network connection is unavailable. (Usage Scenario) Users are registered at the head office where BioStar server is installed and USB memory which includes registered users is sent to the site, and T&A result is generated with log of the previous month at the beginning of every month. Practically it should be supported as a file type so that it can be handled via USB copy even when this USB data is re-forwarded.\\ |
| - | * API [[BS2_GetUserInfosFromDir]] has been added | + | |
| - | * API [[BS2_GetLogFromDir]] has been added | + | |
| - | <text size="x-large">5.</text>Filtering log from device feature is improve the status of no response from the system when the log is filtered and showed from the device via SDK or when the device gets log. | + | * Add API [[BS2_GetUserListFromDir]] |
| + | * Add API [[BS2_GetUserInfosFromDir]] | ||
| + | * Add API [[BS2_GetLogFromDir]] | ||
| + | <text size="x-large">6.</text>Filtering log from device feature is improve the status of no response from the system when the log is filtered and showed from the device via SDK or when the device gets log.\\ | ||
| - | * API [[BS2_GetFilteredLogSinceEventId]] has been added | + | * Add API [[BS2_GetFilteredLogSinceEventId]] |
| ==== Modified features ==== | ==== Modified features ==== | ||