03.03.2021, 07:13
New "ekey FSX app" v.20210228 is available for download:
http://www.ekey.lv/logicmachine/ekey-app...210228.ipk
User manual:
http://www.ekey.lv/logicmachine/ekey-app...manual.pdf
Changes from previous v.20201108:
+ Now Is possible to do the more scenarios with ekey FSX app software, like
Scanner #1 activates door A and door C, 'unknown finger' activate object D
Scanner #2 activates door B and door C , user with 'no rights' activate the object E, binary-input of the scanner activate the door B from inside
Each scanner can respond on multiple event types , like positive access events ('enter') , negative access events ('no-rights'), wrong user identification ('bad-finger') and
the 'binary-input' (available on scanners with the built-in relays). For positive access events the are available 9 different Keys.
To realize this function each scanner has new configuration records to assign those event types to specific predefined Tasks
"Tasks" also are the new terms implemented in the app. Tasks are defined as the combination of Objects (KNX data groups) and predefined Actions (none, on/off short, ... , toggle)
The app has the new tab "Tasks" and this new tab replace the tab "Action" from the older app version
For example, Tasks are: 'Door 1 - open 3 sec'; 'Door 2 - toggle on/off', 'Alarm - On', etc.
the User credentials (fingerprints & rfid cards) is attracted to Keys numbered from 1 .. 9 (visually in same way as previous with Actions).
By assigning multiple Keys to different User credentials now it is possible for each scanner positive access event execute different Tasks based on Keys assigned to User fingerprints.
* This is similar method in the "ekey multi" system where user finger keys make logic to switch different relays from the one scanner.
When you update the "ekey FSX app" from v.20201108 to v.20210221 then
all required Tasks are created automatically according to previous configuration
all Actions previous assigned to User credentials (fingerprints and RFID cards) now are the Keys
all Tasks are assigned to Keys for each scanner
so you don't need to make additional changes to your existing configuration
+ scanner: switch OFF the scanner status LED light (to make it invisible at night)
+ scanner: locate scanner function (start/stop flashing function LED lights)
+ scanner: existing service commands available to execute from the app:
Restart - restart the scanner
Clean - delete all credential (fingerprint and RFID card) information from the scanner
SyncToDB - copy all credentials from scanner to internal database
SyncFromDB - copy all credentials from internal database to scanner
+ you can create a new resident script to control the ekey daemon status using internal function:
- check if ekey daemon is already running using predefined 1 bit KNX data object for this purpose, like '8/2/6' in this example:
-----------------------------------------------------------
require('custom.ekey.lib')
ekeylib.check_ekey_daemon ( '8/2/6' )
-----------------------------------------------------------
+ if you are using in parallel the old scada-version then this version is not fully compatible with this app:
User fingerprints there are as previous assigned to Actions. But actually they are used as Keys.
The scanner field Object is not more functional due to new method of assigning multiple Tasks to scanner
* Don't forget after the update to restart the LM device and clear the browser cache (Ctrl+F5)!
http://www.ekey.lv/logicmachine/ekey-app...210228.ipk
User manual:
http://www.ekey.lv/logicmachine/ekey-app...manual.pdf
Changes from previous v.20201108:
+ Now Is possible to do the more scenarios with ekey FSX app software, like
Scanner #1 activates door A and door C, 'unknown finger' activate object D
Scanner #2 activates door B and door C , user with 'no rights' activate the object E, binary-input of the scanner activate the door B from inside
Each scanner can respond on multiple event types , like positive access events ('enter') , negative access events ('no-rights'), wrong user identification ('bad-finger') and
the 'binary-input' (available on scanners with the built-in relays). For positive access events the are available 9 different Keys.
To realize this function each scanner has new configuration records to assign those event types to specific predefined Tasks
"Tasks" also are the new terms implemented in the app. Tasks are defined as the combination of Objects (KNX data groups) and predefined Actions (none, on/off short, ... , toggle)
The app has the new tab "Tasks" and this new tab replace the tab "Action" from the older app version
For example, Tasks are: 'Door 1 - open 3 sec'; 'Door 2 - toggle on/off', 'Alarm - On', etc.
the User credentials (fingerprints & rfid cards) is attracted to Keys numbered from 1 .. 9 (visually in same way as previous with Actions).
By assigning multiple Keys to different User credentials now it is possible for each scanner positive access event execute different Tasks based on Keys assigned to User fingerprints.
* This is similar method in the "ekey multi" system where user finger keys make logic to switch different relays from the one scanner.
When you update the "ekey FSX app" from v.20201108 to v.20210221 then
all required Tasks are created automatically according to previous configuration
all Actions previous assigned to User credentials (fingerprints and RFID cards) now are the Keys
all Tasks are assigned to Keys for each scanner
so you don't need to make additional changes to your existing configuration
+ scanner: switch OFF the scanner status LED light (to make it invisible at night)
+ scanner: locate scanner function (start/stop flashing function LED lights)
+ scanner: existing service commands available to execute from the app:
Restart - restart the scanner
Clean - delete all credential (fingerprint and RFID card) information from the scanner
SyncToDB - copy all credentials from scanner to internal database
SyncFromDB - copy all credentials from internal database to scanner
+ you can create a new resident script to control the ekey daemon status using internal function:
- check if ekey daemon is already running using predefined 1 bit KNX data object for this purpose, like '8/2/6' in this example:
-----------------------------------------------------------
require('custom.ekey.lib')
ekeylib.check_ekey_daemon ( '8/2/6' )
-----------------------------------------------------------
+ if you are using in parallel the old scada-version then this version is not fully compatible with this app:
User fingerprints there are as previous assigned to Actions. But actually they are used as Keys.
The scanner field Object is not more functional due to new method of assigning multiple Tasks to scanner
* Don't forget after the update to restart the LM device and clear the browser cache (Ctrl+F5)!