HID OMNIKEY 5427 CK Keyboard Wedge User Guide - Manual (Page 11)

OMNIKEY Keyboard Wedge Configuration, 5x27-902, Rev D.0
November 2013 Page 11 of 23
HID GLOBAL CONFIDENTIAL AND PROPRIETARY INFORMATION. Use and disclosure of this information is strictly
restricted by the terms of a non-disclosure agreement with HID Global Corporation. If you have received this information and
are not an intended recipient or are not subject to or do not agree to be bound by the terms of the non-disclosure agreement,
please immediately return this document to HID Global Corporation, 15370 Barranca Pkwy, Irvine, CA 92618-3106.
For DESFire and DESFire EV1 cards with linear / cyclical record, set LENGTH to one, since
it refers those cards to one record.
2.2.3.3 PACS Custom Data Fields (firmware 02000000 or higher)
HID credential physical access information is a unique bitstream that contains several data
sections like Facility Code or Card Number. The pre-set data PACS function bits provide the
full PACS bits stream. See Section 2.2.3.1 Preset Data Fields, page 10.
In case you are extracting only part of the full PACS bitstream, 5x27 CK readers provide the
function PACS custom:
When activated, define and send separately up to three (3) data sections within the PACS
bitstream over the Keyboard Wedge interface.
This option is available for card types provided with HID PACS bits (HID Prox, HID
iCLASS, MIFARE Classic, MIFARE DESFire EV1) and requires Service Pack 1 or higher.
Definition of PACS data sections is done the same way as custom data fields (pre-/ post-
strokes, Offset, Length). Since PACS data is typically not organized in full bytes, offset and
length input represent bits (and not bytes as with custom data fields).
Furthermore, for each PACS sections, define the output type individually.
EXAMPLE: The configuration below defines two PACS sections:
• FACCODE starting at bit 0 with a length of 4 bits
• CARDNR starting at bit 7 with a length of 10 bits
Figure 4 – Prox Card Custom PACS Card Data Selection Example