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_296 [2024/02/21 11:08] mwkim |
en:release_note_296 [2024/02/22 12:59] (current) kkshin [Modification function] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * Added feature to ignore repetitive input signals when using third-party controllers connected via Wiegand. | * Added feature to ignore repetitive input signals when using third-party controllers connected via Wiegand. | ||
| * Supports displaying authentication success/failure results from third-party controllers on Suprema devices. | * Supports displaying authentication success/failure results from third-party controllers on Suprema devices. | ||
| - | * Added feature to set the baud rate of the slave device in the RS485 network. | ||
| * Added function to initialize by selecting a network. | * Added function to initialize by selecting a network. | ||
| Line 24: | Line 23: | ||
| * Refer to structure [[face_api#BS2FaceEx]] | * Refer to structure [[face_api#BS2FaceEx]] | ||
| - | <text size="x-large">3.</text> In environments where Suprema devices are connected to third-party controllers via Wiegand, if the same input signal is repetitively input from a specific model of the controller to the Suprema device, a feature has been added to ignore this. \\ | + | <text size="x-large">3.</text> In environments where Suprema devices are connected to third-party controllers via Wiegand, if the feedback for authentication is repetitively input to the Suprema device from a specific model of the controller, a feature has been added to ignore this. \\ |
| * Refer to structure [[configuration_api#BS2Trigger]] | * Refer to structure [[configuration_api#BS2Trigger]] | ||
| Line 34: | Line 33: | ||
| * Refer to structure [[device_api#BS2DeviceCapabilities]] | * Refer to structure [[device_api#BS2DeviceCapabilities]] | ||
| - | <text size="x-large">5.</text> Added feature to set the baud rate of the slave device in the RS485 network. \\ | + | <text size="x-large">5.</text> Added function to initialize by selecting a network. \\ |
| - | + | ||
| - | * Add API [[BS2_SetSlaveBaudrate]] | + | |
| - | + | ||
| - | <text size="x-large">6.</text> Added function to initialize by selecting a network. \\ | + | |
| When connected to multiple networks, specifying a particular network for initialization allows for searching for devices on that sub-network after performing initialization. \\ | When connected to multiple networks, specifying a particular network for initialization allows for searching for devices on that sub-network after performing initialization. \\ | ||
| Line 54: | Line 49: | ||
| * Refer to structure [[configuration_api#BS2FaceConfig]] | * Refer to structure [[configuration_api#BS2FaceConfig]] | ||
| - | <text size="x-large">2.</text> The device log filtering API [[BS2_GetFilteredLogSinceEventId]] has been ''Deprecated''. \\ | + | <text size="x-large">2.</text> The device log filtering API [[BS2_GetFilteredLog]], [[BS2_GetFilteredLogSinceEventId]] has been ''Deprecated''. \\ |
| It is recommended that filtering be performed on the server using [[BS2_GetLog]] and [[BS2_StartMonitoringLog]]. \\ | It is recommended that filtering be performed on the server using [[BS2_GetLog]] and [[BS2_StartMonitoringLog]]. \\ | ||
| + | * Refer to API [[BS2_GetFilteredLog]] | ||
| * Refer to API [[BS2_GetFilteredLogSinceEventId]] | * Refer to API [[BS2_GetFilteredLogSinceEventId]] | ||
| * Refer to API [[BS2_GetLog]] | * Refer to API [[BS2_GetLog]] | ||