Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:fsf2_revision_note_202 [2022/08/24 14:49] mwkim |
en:fsf2_revision_note_202 [2023/11/27 11:55] (current) mashin |
||
---|---|---|---|
Line 16: | Line 16: | ||
<text size="large">5.</text> Improved to check for the duplication of cards registered with users when transmitting user data from the server to devices. \\ | <text size="large">5.</text> Improved to check for the duplication of cards registered with users when transmitting user data from the server to devices. \\ | ||
- | <text size="large">6.</text> Improved Arm/Disarm state to be written directly to the device's memory so that the state persists even if power is lost. \\ | + | <text size="large">6.</text> Improved the Arm/Disarm status is maintained if the device loses power. \\ |
\\ | \\ | ||
==== Bug Fixes ==== | ==== Bug Fixes ==== | ||
Line 29: | Line 29: | ||
<text size="large">3.</text> The device restarted abnormally after scanning some cards on the device (Affects version: v1.0.0). \\ | <text size="large">3.</text> The device restarted abnormally after scanning some cards on the device (Affects version: v1.0.0). \\ | ||
\\ | \\ | ||
- | <text size="large">4.</text> If sending the Output Status Report Request command when the device was communicating with a 3rd party system via OSDP, the relay works, but the Output Status Report does not output (Affects version: v1.1.2). \\ | + | <text size="large">4.</text> When communicating with a 3rd party control panel via OSDP, the device does not respond to the Output Status Report command while the relay reacts to it (Affects version: v1.1.2). \\ |
\\ | \\ | ||
- | <text size="large">5.</text> When the device was communicating with a 3rd party system via OSDP, if the Input Status Request command was sent after the input port was grounded, the output was Inactive (Affects version: v1.1.2). \\ | + | <text size="large">5.</text> When communicating with a 3rd party control panel via OSDP, the device incorrectly responds as 'Inactive' when receiving the Input Status Request command while the input port is grounded (Affects version: v1.1.2). \\ |
\\ | \\ | ||
- | <text size="large">6.</text> When the device was communicating with a 3rd party system via OSDP, no data was output if sending the Device Capabilities command (FSF2-AB, FSF2-DB)(Affects version: v1.0.0). \\ | + | <text size="large">6.</text> When communicating with a 3rd party control panel via OSDP, the device does not respond to the Device Capabilities command (FSF2-DB, FSF2-AB)(Affects version: v1.0.0). \\ |
\\ | \\ | ||
<text size="large">7.</text> The master device restarted abnormally if changing the floor settings after setting up the scheduled unlock zone (Affects version: v1.0.0). \\ | <text size="large">7.</text> The master device restarted abnormally if changing the floor settings after setting up the scheduled unlock zone (Affects version: v1.0.0). \\ | ||
Line 45: | Line 45: | ||
<text size="large">11.</text> When authenticating with a duress fingerprint on a device with the auth mode set to ID+face+fingerprint/PIN, the duress fingerprint log does not leave (Affects version: v1.0.0). \\ | <text size="large">11.</text> When authenticating with a duress fingerprint on a device with the auth mode set to ID+face+fingerprint/PIN, the duress fingerprint log does not leave (Affects version: v1.0.0). \\ | ||
\\ | \\ | ||
- | <text size="large">12.</text> Device does not recognize some HID iCLASS Seos cards (Affects version: v1.0.0). \\ | + | <text size="large">12.</text> Device does not recognize certain HID iCLASS Seos cards (Affects version: v1.0.0). \\ |
\\ | \\ | ||
<text size="large">13.</text> Device does not connect to a 3rd party controller (Software House iSTAR Edge G2) via OSDP (Affects version: v1.0.0). \\ | <text size="large">13.</text> Device does not connect to a 3rd party controller (Software House iSTAR Edge G2) via OSDP (Affects version: v1.0.0). \\ |