All information and data contained in this document are the exclusive property of SKIPLY SAS and may neither be used nor disclosed
without its prior written consent.
~ 26 ~
16.4.
Running Mode 9: CODE
In this section acknowledgement means activation of the Hall effect sensor with a magnetic badge.
The purposes, among others, of this running mode is:
•
to allow an individual to be identified (with his personal code)
•
to allow the proof of presence
•
to enter and transmit a code
•
to enter and transmit an acknowledged code
•
to detect the use of the magnetic badge
In this mode the buttons 1,2,3,4 and 5 do
n’t increment their respective counters, but allow to create the
user code by shift to the left at each push (maximum 6 digits, if there are more digits only the first 6 digits
are stored). Under normal conditions, as soon as the first push is detected, a countdown is started. The
value in seconds of this countdown is
equal to “TPB”. The user enters his identification code (maximum
6 digits). If the user does
n’t activate the magnetic sensor before the end of the countdown, the code isn’t
acknowledged, otherwise the code is acknowledged.
At the of the countdown equal to “TPB” LEDs lights
green fix to inform user that it is possible to compose a new code.
For an acknowledged code, the header of the uplink
payload starts with “3”.
For an unacknowledged code, the header of the uplink payload starts with “1”.
To address an issue of duty cycle, this running mode embeds a buffer containing up to 4 uplink payloads.
If all duty cycle is completely consumed and more than 4 codes are entered before the duty cycle
becomes available again, the oldest codes are lost.
16.4.1. Code Data Frame format
The uplink payload contains the last two codes entered. The uplink payload is formatted as follows:
Xa
Xb
TT YYYY
BBBBBB
AAAAAA
Xa: Acknowledgement flag for the first code A (1 => unacknowledged, 3 => acknowledged)
Xb: Acknowledgement flag for the previous code B (1 => unacknowledged, 3 => acknowledged)
YYYY: hexadecimal value. Time in minutes since the last transmitted code.
TT: hexadecimal value. Time in minutes between the end of the entering code (=
end of “TPB”
countdown) and the transmission of the uplink payload (duty cycle management). Maximum FF or 255
minutes. In most cases, the duty cycle management does not exceed 3 minutes.
BBBBBB: Second last code entered and sent
AAAAAA: Last code entered and sent
After each sent frame, the YYYY and TT counters are reset in anticipation of the next code entry and
frame sending.
