Ojmar Nexo NLX1 Instruction Manual page 77

Nexo NLX 1
Card
approaching
Action
performance
+ card writting
To decide if the lock has access or not the 3rd party software should use its own
means to keep tracks of the card UUID recorded to each user and the access rights
provided to him. The API will act as a mere intermediary in this case.
6.2.1.1 Nexo NLX1 limitations
Following limitations are defined during the usage of the Nexo NLX1 system.
Communication limitations:
•
Up to 252 bytes can be sent by TCP/IP communication.
Up to 768 bytes can be sent by USB communication.
Functionalities limitations:
•
Online operations:
- Up to 36 different profiles can be uploaded per lock
- Last 10 events can be viewed per communication.
- Just one information request can be asked per communication.
Offline operations:
- Automatic opening is not available.
- DST is not available.
- Time zones and expiry dates for user cards are not available.
- Up to 125 UUIDs can be uploaded on the lock for white/black list for the
offline operation.
6_API INTRODUCTION
Petition (Bytes)
Action performance +
Configuration/information
petition (Bytes)
Last event + information
(Opt.) (Bytes)
Figure 6-2. System workflow.
API
Petition (JSON)
Action performance +
Configuration/information
petition (Opt.) (JSON)
Last event + information
(Opt.) (JSON)
rd
3 party SW
Checks
permissions
OJMAR 77