Sensor Access has many different existing integrated systems for a global solution.
Here's the list of the different products that have been integrated with Sensor
Access Control solution:
Biometric readers: Suprema, Identitech
Lift control system: Mitsubishi
Wireless door lock systems: Aperio, Salto
CCTV: Many different manufacturers
Alarm panel: Galaxy
Broad-based ID document authentication: Keesing
Intelligent key cabinets and locker systems: TRAKA
Automatic License Plate Recognition: LPR / ANPR Module
Visitor Tracking software: Telemaque
INTEGRABILITY OF THE SENSOR ACCESS PRODUCTS
Sensor Access products may be integrated with Third Party software.
Here's the list of the different ways of integration with Sensor Access products:
Currently there are 9 different ways of integrations, categorized in 4 types.
The first 3 types are based on GuardPointPro and thus requires GuardPointPro to be up and running to let the integration work, and the 4th is for projects that should communicate directly with the controllers.
Type 1
- I/O status reading
- Actions & processes activation
- GuardPointPro screens opening
- Cardholders creating & deleting
- Event history
The integration methods for this type are as follows:
DB API (or Database API)
The Third Party software writes commands in a table of the GuardPoint Pro database.
The events may be read from the database directly.
XML-API where the Third Party software sends XML commands to the Spread like a standard Workstation.
acAPI.dll which is a DLL file written by Sensor Access and used by the Third Party software to send specific XML commands to the Spread like a standard Workstation.
The method of acAPI.dll is less recommended today for new projects because:
(a) it has less options and less flexibility than the other 2 methods.
(b) The other 2 methods are cross platform whilst acAPI.dll is only compatible with Microsoft environment.
Type 2
- Actions & processes activation
- GuardPointPro screens opening
- Cardholders creating & deleting.
The integration methods for this type are as follows:
SpreadCmd.exe which is a EXE file written by Sensor Access (located in the Application folder) and used by the Third Party for sending XML command lines to GuardPointPro via the Spread
Am5www.dll which is a DLL file written by Sensor Access and used by the Third Party for sending HTTP commands to GuardPointPro via the Spread (by using the Internet Information Services of Windows).
Type 3
- - I/O status reading,
- - Actions & processes activation,
- - GuardPointPro screens opening,
- - By using a world-wide known protocol.
The integration methods for this type are as follows:
Wizcon where the Third Party software uses a Wizcon client for reading/writing OPC Tags published by GuardPointPro.
Note: this requires the installation of the 'Wizcon Supervisor' application.
OPC where the Third Party software uses a OPC client for reading/writing OPC Tags published by GuardPointPro.
MODBUS-TCP where the Third Party software uses the Modbus-TCP protocol for reading/writing 16-bit Words published by GuardPointPro (each controller is virtualized as a MODBUS slave).
Type 4
- I/O status reading
- Cardholders creating & deleting
- Event history
- All the controller commands supported by the selected method (of the following two)
- By communicating directly with the Sensor Access controllers
The integration methods for this type are as follows:
DDSCOM
ActiveX/DLL containing tools to communicate with Sensor Access controllers)
Full protocol:
Basic level communication protocol with all commands supported by the controller (this method gives the maximum flexibility, but on the other hand it is the most demanding for a programmer as it requires writing the whole communication layer from scratch.
It's recommended for companies that wish to achieve full control on all the aspects of the communication without using any Sensor Access files).
Comments
0 comments
Please sign in to leave a comment.