Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:fs2_revision_note_140 [2021/05/12 09:16] chloe |
en:fs2_revision_note_140 [2023/08/02 10:49] (current) mwkim |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| <text size="large">7.</text> Supports the thermal camera. \\ | <text size="large">7.</text> Supports the thermal camera. \\ | ||
| <text size="large">8.</text> Supports the Screen Saver. \\ | <text size="large">8.</text> Supports the Screen Saver. \\ | ||
| - | <text size="large">9.</text> Improved the face recognition algorithm for users with glasses. \\ | + | <text size="large">9.</text> Improved the face authentication algorithm for users with glasses. \\ |
| <text size="large">10.</text> Supports the new face template. \\ | <text size="large">10.</text> Supports the new face template. \\ | ||
| + | <callout type="primary" icon="true"> | ||
| * Face templates scanned or enrolled on devices with the firmware version 1.4.0 or later are not compatible with devices with firmware version 1.3.1 or earlier, and authentication may fail due to this incompatibility. | * Face templates scanned or enrolled on devices with the firmware version 1.4.0 or later are not compatible with devices with firmware version 1.3.1 or earlier, and authentication may fail due to this incompatibility. | ||
| - | * If the firmware of the face recognition device connected as a slave is the latest version (FaceStation 2: 1.4.0 or later, FaceLite: 1.2.0), authentication may fail because it is not compatible with the existing template. | + | * If the firmware of the face authentication device connected as a slave is the latest version (FaceStation 2: 1.4.0 or later, FaceLite: 1.2.0), authentication may fail because it is not compatible with the existing template. |
| + | </callout> | ||
| <text size="large">11.</text> Increased maximum number of users (1:N). \\ | <text size="large">11.</text> Increased maximum number of users (1:N). \\ | ||
| * Before: 3,000 | * Before: 3,000 | ||
| Line 37: | Line 37: | ||
| ==== Main Fixes ==== | ==== Main Fixes ==== | ||
| <text size="large">1.</text> When all or user data were exported to a USB and then the user data were imported again after upgrading the device firmware, the event log was deleted. \\ | <text size="large">1.</text> When all or user data were exported to a USB and then the user data were imported again after upgrading the device firmware, the event log was deleted. \\ | ||
| - | <text size="large">2.</text> Logs generated while the device is disconnected are not sent to BioStar 2, even after the device is reconnected. \\ | + | <text size="large">2.</text> Logs generated while the device was disconnected were not sent to BioStar 2, even after the device was reconnected. \\ |
| ==== Bug Fixes ==== | ==== Bug Fixes ==== | ||
| - | <text size="large">1.</text> Modified that the authentication mode of the slave device is set according to the setting of the master device. \\ | + | <text size="large">1.</text> Modified that the authentication mode of the slave device was set according to the setting of the master device. \\ |
| <text size="large">2.</text> Authentication of fingerprints registered as duress fingerprints failed on the BioStation A2 connected as a slave device. \\ | <text size="large">2.</text> Authentication of fingerprints registered as duress fingerprints failed on the BioStation A2 connected as a slave device. \\ | ||
| - | <text size="large">3.</text> Card data is output with wrong BitCount when the device is connected to a 3rd-party system via OSDP. \\ | + | <text size="large">3.</text> Card data were output with wrong BitCount when the device was connected to a 3rd-party system via OSDP. \\ |
| <text size="large">4.</text> The automatic Wi-Fi connection function did not work. \\ | <text size="large">4.</text> The automatic Wi-Fi connection function did not work. \\ | ||
| - | <text size="large">5.</text> Some or all of the image log colors appear garbled. \\ | + | <text size="large">5.</text> Some or all of the image log colors appeared garbled. \\ |
| <text size="large">6.</text> It recognized registered users as unregistered when accessing job codes with assigned cards. \\ | <text size="large">6.</text> It recognized registered users as unregistered when accessing job codes with assigned cards. \\ | ||
| - | <text size="large">7.</text> Device reboots if the face of an existing registered user is changed when the number of registered users is the maximum. \\ | + | <text size="large">7.</text> Device rebooted if the face of an existing registered user was changed when the number of registered users was the maximum. \\ |
| <text size="large">8.</text> An OSDP security session error occurred when connecting OM-120 and XPass D2 as a slave device. \\ | <text size="large">8.</text> An OSDP security session error occurred when connecting OM-120 and XPass D2 as a slave device. \\ | ||
| <text size="large">9.</text> An excess error occurred when registering new user faces or editing registered users even though the number of registered faces did not reach the maximum capacity. \\ | <text size="large">9.</text> An excess error occurred when registering new user faces or editing registered users even though the number of registered faces did not reach the maximum capacity. \\ | ||
| <text size="large">10.</text> The registered user data disappeared and the device rebooted if a user attempted to register a card when the number of registered users was at maximum capacity. \\ | <text size="large">10.</text> The registered user data disappeared and the device rebooted if a user attempted to register a card when the number of registered users was at maximum capacity. \\ | ||
| - | <text size="large">11.</text> An error occurs when matching with groups when there are 5,000 users and 5 user groups are used. \\ | + | <text size="large">11.</text> An error occurred when matching with groups when there were 5,000 users and 5 user groups were used. \\ |
| <text size="large">12.</text> The slave device did not work with group matching even though the group matching was set in the master device. \\ | <text size="large">12.</text> The slave device did not work with group matching even though the group matching was set in the master device. \\ | ||
| - | <text size="large">13.</text> When an administrator is resent from a device with a new firmware applied, it is recognized as an unregistered user and cannot enter the administrator menu. \\ | + | <text size="large">13.</text> When an administrator was resent from a device with a new firmware applied, it was recognized as an unregistered user and could not enter the administrator menu. \\ |
| <text size="large">14.</text> An error in the master-slave connection occurred due to the RS-485 communication key. \\ | <text size="large">14.</text> An error in the master-slave connection occurred due to the RS-485 communication key. \\ | ||
| <text size="large">15.</text> After a global anti-passback violation, an authentication success log occurred twice. \\ | <text size="large">15.</text> After a global anti-passback violation, an authentication success log occurred twice. \\ | ||
| Line 58: | Line 58: | ||
| <text size="large">17.</text> When a locked device was rebooted for an RS-485 connection, the slave device became unlocked. \\ | <text size="large">17.</text> When a locked device was rebooted for an RS-485 connection, the slave device became unlocked. \\ | ||
| <text size="large">18.</text> When Factory Default was performed using SDK, the device resource (logo image) did not initialize. \\ | <text size="large">18.</text> When Factory Default was performed using SDK, the device resource (logo image) did not initialize. \\ | ||
| - | <text size="large">19.</text> Device reboots or a timeout occurs when upgrading firmware or transferring user data during SSL secure communication. \\ | + | <text size="large">19.</text> Device reboots or a timeout occurred when upgrading firmware or transferring user data during SSL secure communication. \\ |
| <text size="large">20.</text> It was unable to edit, delete or add an authentication mode. \\ | <text size="large">20.</text> It was unable to edit, delete or add an authentication mode. \\ | ||
| <text size="large">21.</text> When the delay for the output signal occurred repeatedly, the device did not work properly. \\ | <text size="large">21.</text> When the delay for the output signal occurred repeatedly, the device did not work properly. \\ | ||
| Line 67: | Line 67: | ||
| <text size="large">26.</text> When a user authenticated on the slave device using a smart card or the face, the master device would reboot. \\ | <text size="large">26.</text> When a user authenticated on the slave device using a smart card or the face, the master device would reboot. \\ | ||
| <text size="large">27.</text> When a user authenticated the fingerprint after setting the byte order as LSB and the Wiegand output information as the user ID, the device would reboot. \\ | <text size="large">27.</text> When a user authenticated the fingerprint after setting the byte order as LSB and the Wiegand output information as the user ID, the device would reboot. \\ | ||
| - | <text size="large">28.</text> Device reboots when registering user faces. \\ | + | <text size="large">28.</text> Device rebooted when registering user faces. \\ |
| <text size="large">29.</text> Improved the device to recognize unknown cards by selecting the card type options. \\ | <text size="large">29.</text> Improved the device to recognize unknown cards by selecting the card type options. \\ | ||
| <text size="large">30.</text> Once a card had been registered on the Wiegand output device, the device would not work properly when trying to output data using a fingerprint registered to another user. \\ | <text size="large">30.</text> Once a card had been registered on the Wiegand output device, the device would not work properly when trying to output data using a fingerprint registered to another user. \\ | ||