Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
en:xp2_revision_note_123 [2021/06/01 13:40] chloe created |
en:xp2_revision_note_123 [2021/06/01 14:15] (current) chloe |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| <text size="large">1.</text> Upgraded to the 1.1.1i version of OpenSSL. \\ | <text size="large">1.</text> Upgraded to the 1.1.1i version of OpenSSL. \\ | ||
| - | |||
| <text size="large">2.</text> Intelligent Slave Support \\ | <text size="large">2.</text> Intelligent Slave Support \\ | ||
| * Intelligent Slave: A function that enables 1:1 or 1:N matching directly from the Suprema device and transmits the authentication result as OSDP card data to the third-party controller. | * Intelligent Slave: A function that enables 1:1 or 1:N matching directly from the Suprema device and transmits the authentication result as OSDP card data to the third-party controller. | ||
| - | |||
| <text size="large">3.</text> The transmission power level for Bluetooth Low Energy (BLE) has been adjusted. \\ | <text size="large">3.</text> The transmission power level for Bluetooth Low Energy (BLE) has been adjusted. \\ | ||
| Line 16: | Line 14: | ||
| ==== Bug Fixes ==== | ==== Bug Fixes ==== | ||
| <text size="large">1.</text> If 31 slave devices were connected and one of the devices got disconnected, the master device rebooted. (Affects version: v1.0.0) \\ | <text size="large">1.</text> If 31 slave devices were connected and one of the devices got disconnected, the master device rebooted. (Affects version: v1.0.0) \\ | ||
| - | |||
| - | |||
| <text size="large">2.</text> Incorrect BitCount was sent if a user authenticated with AoC when the device was connected to a 3rd-party system via OSDP. (Affects version: v1.0.0) \\ | <text size="large">2.</text> Incorrect BitCount was sent if a user authenticated with AoC when the device was connected to a 3rd-party system via OSDP. (Affects version: v1.0.0) \\ | ||
| - | |||
| <text size="large">3.</text> When using a static IP while the DNS server address was configured, a reboot on the device caused communication problems between the server and the device. (Affects version: v1.0.0) \\ | <text size="large">3.</text> When using a static IP while the DNS server address was configured, a reboot on the device caused communication problems between the server and the device. (Affects version: v1.0.0) \\ | ||
| - | |||
| <text size="large">4.</text> It failed to reconnect to the slave device after downgrading its firmware version to 1.1.0. (Affects version: v1.0.0) \\ | <text size="large">4.</text> It failed to reconnect to the slave device after downgrading its firmware version to 1.1.0. (Affects version: v1.0.0) \\ | ||
| - | |||
| <text size="large">5.</text> Device responded that it supported transparent mode by OSDP_PDCAP when connecting as a slave while it did not support it. (Affects version: v1.0.0) \\ | <text size="large">5.</text> Device responded that it supported transparent mode by OSDP_PDCAP when connecting as a slave while it did not support it. (Affects version: v1.0.0) \\ | ||
| - | |||
| <text size="large">6.</text> When calling the BS2_ResetConfigExceptNetInfo API from the BioStar 2 Device SDK, a ‘Timeout’ error occurred. (Affects version: v1.0.0) \\ | <text size="large">6.</text> When calling the BS2_ResetConfigExceptNetInfo API from the BioStar 2 Device SDK, a ‘Timeout’ error occurred. (Affects version: v1.0.0) \\ | ||
| <text size="large">7.</text> The OSDP LED Temporary command did not work properly. (Affects version: v1.0.0) \\ | <text size="large">7.</text> The OSDP LED Temporary command did not work properly. (Affects version: v1.0.0) \\ | ||
| <text size="large">8.</text> The network reset on the first use was needed to use OSDP default keys to communicate. (for devices released with the firmware version 1.2.0 or later) (Affects version: v1.2.0) \\ | <text size="large">8.</text> The network reset on the first use was needed to use OSDP default keys to communicate. (for devices released with the firmware version 1.2.0 or later) (Affects version: v1.2.0) \\ | ||
| <text size="large">9.</text> It was able to communicate using default keys after changing the key settings when the device was connected to a 3rd-party device via OSDP. (Affects version: v1.0.0) \\ | <text size="large">9.</text> It was able to communicate using default keys after changing the key settings when the device was connected to a 3rd-party device via OSDP. (Affects version: v1.0.0) \\ | ||
| - | <text size="large">10.</text> Secure communication was not available by using the default key after downgrading firmware to version 1.1.0 or below which does not support encryption. (Affects version: v1.2.0) \\ | + | <text size="large">10.</text> Secure communication was not available by using the default key after downgrading firmware to version 1.1.0 or below which does not support encryption. (Affects version: v1.2.0) |
| + | \\ | ||