Technical Support | Suprema

Dear Valued Partners,

Release Date: 2024-08-02

A new official Suprema G-SDK V1.7.0 has been released recently with new features.

Please be aware of the new ULRs as follows.

G-SDK online manual: https://supremainc.github.io/g-sdk/ 

G-SDK download: https://github.com/supremainc/g-sdk/releases 

Release Note Link: https://supremainc.github.io/g-sdk/release/release-1.7.0/ 

New features and improvement 

• BioEntry W3 is supported.
• Supports Custom Smart Card.
• Supports setting Anti-Passback on the door.
• Improved to support multi-threading environments.
• Improved to allow activating or deactivating User Status updates.
• Ignore Repeated Signals Duration is added to Trigger & Action API.
• Support for HID Prox and iCLASS cards on the XPass 2 (XP2-MAPB).
• Supports the Display Result from Controller feature for displaying authentication results from a 3rd party controller on the device screen when using Intelligent Slave.
• Added new options in Device Capability.

Note: The device log filtering API GetLogWithFilter has been Deprecated. It is recommended that filtering be performed on the server using GetLog, EnableMonitoring and SubscribeRealtimeLog.

The device log filtering GetLogWithFilter API reviews the device’s logs against the conditions set by the server. This means that the device may invest considerable time in log filtering, and as the number of logs on the device increases, more time will be required.

Also, logs are not permanently stored on the device. If the maximum number of logs that the device can hold is exceeded, the device will overwrite the oldest logs, and logs older than a certain period of time may be automatically deleted. It is recommended that all logs from the device be stored and managed on a server.

It is recommended that logs be received in bulk from the device using the GetLog API, and that logs occurring after the current time be received in real time using the EnableMonitoring and SubscribeRealtimeLog APIs, so that the server stores all logs in an appropriate DBMS and filters the logs from the DBMS.