Axis A1601 User Manual page 18

AXIS A1601 Network Door Controller
System configuration
To delete a field map in the Edit card format or Add card format dialog, click
To delete a card format, click
Important
• You can only enable and disable card formats if the door controller has been configured with at least one reader. See
Configure the hardware on page 10 and How to configure readers and REX devices on page 13.
• Two card formats with the same bit length cannot be active the same time. For example, if you have defined two 32-bit
card formats, "Format A" and "Format B", and you have enabled "Format A", you cannot enable "Format B" without
disabling "Format A" first.
• If no card formats have been enabled, you can use the Card raw only and Card raw and PIN identification types to
identify a card and grant access to users. However, we do not recommend this since different reader manufacturers
or reader settings can generate different card raw data.
Card format descriptions
• Name (required) – Enter a descriptive name.
• Description – Enter additional information as desired. This information is only visible in the Edit card format and Add
card format dialogs.
• Bit length (required) – Enter the bit length of the card format. This has to be a number between 1 and 1000000000.
Field maps
• Name (required) – Enter the field map name unspaced, for example OddParity.
Examples of common field maps include:
- Parity – Parity bits are used for error detection. Parity bits are usually added to the beginning or end of a
binary code string and indicate if the number of bits is even or odd.
- EvenParity – Even parity bits make sure that there is an even number of bits in the string. The bits that have
the value 1 are counted. If the count is already even, the parity bit value is set to 0. If the count is odd, the
even parity bit value is set to 1, making the total count an even number.
- OddParity – Odd parity bits make sure that there is an odd number of bits in the string. The bits that have
the value 1 are counted. If the count is already odd, the odd parity bit value is set to 0. If the count is even,
the parity bit value is set to 1, making the total count an odd number.
- FacilityCode – Facility codes are sometimes used for verifying that the token matches the ordered end user
credential batch. In legacy access control systems, the facility code was used for a degraded validation, allowing
entry to every employee in the credential batch that had been encoded with a matching site code. This field map
name, which is case sensitive, is required for the product to validate on facility code.
- CardNr – The card number or user ID is what is most commonly validated in access control systems. This field
map name, which is case sensitive, is required for the product to validate on card number.
- CardNrHex – The card number binary data is encoded as hex-lowercase numbers in the product. It is primarily
used for troubleshooting why you are not getting the expected card number from the reader.
• Range (required) – Enter the bit range of the field map, for example 1, 2–17, 18–33, and 34.
• Encoding (required) – Select the encoding type of each field map.
- BinLE2Int – Binary data is encoded as integer numbers in little endian bit order. Integer means that it needs to
be a whole number (no decimals). Little endian bit order means that the first bit is the smallest (least significant).
- BinBE2Int – Binary data is encoded as integer numbers in big endian bit order. Integer means that it needs to be
a whole number (no decimals). Big endian bit order means that the first bit is the biggest (most significant).
.
18