Badge Formats

Badge formats are not pre-programmed into the Continental access control
panels. The formats are created in the Badge Formats screen of the
CardAccess software, and then downloaded (as serial data) to the panels.
Once the formats are stored at the panels, the panels will be programmed to
recognize the badge format types.
Accessing Badge Formats Screen

Click on Administration menu in CardAccess main menu bar.

Click on Badge Formats menu item in the list.
Upon clicking, the Badge Formats screen will be displayed as below.

Fig. 60.1. The Badge Formats screen.

A few standard formats are preprogrammed into the Badge Formats screen
(see the records in upper half of figure 60.1 above). These formats can be used
without the need to create badge formats from scratch.

On the other hand, the CardAccess system designer can design and implement
a completely unique badge format as well. The system will allow you to design
badge formats from scratch, program these formats onto cards, and have the
access panels recognize the proprietary formats.
A general discussion on Badge Formats follows below.
What is a Badge Format?

In order to understand badge formats, we must first look at what actually

happens when the system reads a badge. An access control system typically,
has some kind of card reader connected through wires to an access control
panel, and that panel is in turn connected through wires to a computer.
In the case of Continental Instruments designed access control systems, the
panel is programmed with local intelligence. It is the panel that locally makes
all of the decisions on who will gain access through a given door. The PC
connection mostly exists to receive history and status messages from the panel
about what access attempts have taken place.
The access scenario most often seen at an entry door is, a cardholder steps
up to a reader with an access card, and presents that card to a card reader.
But what is actually happening at the reader? How does the reader get data
from the badge? (For the purpose of this discussion, we assume that the card
type used is designed to match the reader type used. That is, we get a
successful read each time).
Every access card is encoded with some kind of data string. Essentially,
some information is programmed into the card, and that information is
dumped to the reader when the card is presented to the appropriate reader
type.
The reader (somehow) activates the card (the technology used to activate the
card varies with the reader and card design) and the data content of that card
is dumped to the reader memory (the card activates, dumps its data contents,
then shuts off). The reader then forwards that data stream to the panel,
which evaluates it.

The data that is actually sent from the card to the reader is an unintelligible
string of data bits that looks like figure 60.2 below.

Fig. 60.1A.

101110111000111110000111110101
Fig. 60.2. A typical string of card data bits from a 36 bit
format.
It is the badge format that gives description to this meaningless string of data
bits. The badge format tells the panel how to divide the data bits into several
logical (sub) groups of bits. Each sub- group of data bits is assigned a
meaning, which is defined by the badge format.
At this point, its helpful to look at the type of information that gets conveyed
from the badge to the access control panel. What things might we want to
know about a badge holder from the data stream on his access card? The
answer to that question will define a badge format. The total number of bits
needed on the badge will depend on how many data fields are needed on that
badge.
As an example, let us examine the (standard) 36-bit format. Embedded in this
format are a Facility Code (16 bits), a Badge Number (16 bits) and an Issue
Level (2 bits).
Notice that we have not accounted for two bits out of the 36 total bits
(16 badge number bits+ 16 facility code bits+ 2 issue level bits= 34 bits only).
The first bit and the last bit of this format are part of a checking calculation.
We will discuss how this calculation is performed later in the manual section.
P FFFFFFFFFFFFFFFF BBBBBBBBBBBBBBBB I
Fig. 60.3. 36 Bit (Weigand) Format.

In figure 60.3 above, the 36-bit format graphic shown is divided into five
subsections. The system knows to parse the bit stream into the subsections
shown above, because that information is programmed into the Badge
Formats screen (see figure 60.4 below).
The 36 bit example we have been discussing is taken from the actual badge
Format 1 which is one of the predefined badge formats that Continental has
created for you. Figure 60.4 is a picture of the definition for Format 1, from
the Badge Formats screen.

Fig. 60.4. 36- bit format.

The controls seen in figure 60.4 are explained below.
Format No
The Format No control will show the number assigned to the badge format
in question.

Fig. 60.5. The Format No field.

Note: A maximum of 10 badge formats are allowed in the screen.
Name
The Name field is used to enter a descriptive text label you wish to give to
the badge format in question.

Fig. 60.6. The Name field.

Badge Format Type

Four badge format types are available for selection in the Badge Formats
screen. Selection can be made by clicking the down arrow to the right of
Badge Format Type control, and then clicking on a desired format type.

Fig. 60.7. The available badge format types in

CardAccess software.
Each of the format types is briefly explained below.
a) ABA ABA is a format type created by the American Banking
Association.
b) Non ABA A format not adhering to the ABA standard.
c) Insertion A bi-directional format designed to be used with swipe or
Insertion type readers.
d) Key - A format designed to be used with Weigand key badges.
Bit/Char Length
Non-ABA badge formats are decoded as bits. Whereas, the ABA formats are
decoded as characters. The Bit/Char Length control is used to specify the
total number bits or characters present in a given badge format.

Fig. 60.8. The Bit/Char Length control.

For non-ABA formats you will enter the number of bits, and for ABA formats,
you will enter the number of characters in this control.
All Types Section
The All Types section provides controls for specifying the string location
(Offset) and the length of the Badge ID, Facility and the Issue that are fixed
for a particular badge format. For information on string Length and Offset,
refer the heading Bit Position, Offset and Length.

Fig. 60.9. The All Types section.

Note: The length of Badge ID, Facility and Issue for non-ABA formats must be
specified as number of bits. Whereas, the length for ABA formats must be
specified as number of characters.
Non ABA Type Section
The Non ABA Type section will be visible when the badge format in question
is of Non-ABA type.

Fig. 60.10. The Non ABA Type section.

This section provides controls for specifying the string location (offset) and the
length for Even and Odd Parity calculations, for a particular Non-ABA type
badge format.
Refer the heading Parity Calculation for more information.
ABA Types Section
The ABA Types section will be visible when the badge format in question is
of ABA type.

Fig. 60.11. The ABA Types section.

This section provides controls for specifying the string location (offset) and the
characters for Start Sentinel, End Sentinel and the Field Separator characters
seen on a particular ABA badge format.
Bit Position, Offset and Length
The terms Bit Position, Offset and Length can be explained with the help of
figures 60.12 and 60.13 below.
Both figures 60.12 and 60.13 below depict the same 36-bit format. Both figures
are identical except for the bit position numbering method used. Figure 60.12
shows the count of bits from left to right numbered sequentially, starting with
the leftmost bit as bit #1.
Figure 60.13 is also numbered sequentially from left to right, but the count
starts at 0. The reason for this is that, in the bit offset method of counting

bits, the leftmost bit (bit 0 location) is used as a reference point to locate the
rest of the bits in the string.
Each bit is counted as being so many places to the right of the first, or zero
bit. So offset means offset to the right of the first bit in the bit string (the
first bit has a zero offset, the second bit is offset one bit to the right of the first
bit, the third bit is offset two bits to the right of the first, etc).

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
Fig. 60.12. Bit Positions 36 Bit Format.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Fig. 60.13. Bit Offsets 36 Bit Format.
When you type in the Offset and Length in the Badge Formats screen
(figure 60.4), what you are really saying to the software is, when you see a bit
stream from a badge, count n bits to the right of the leftmost bit. Then count
off the next n bits, stop counting, and use the bits you have just stored as the
Badge Number (or the Facility Code, etc.).
In the specific case of the standard, Continental supplied 36-bit format, the
first bit is a parity check bit. Then you count one bit to the right of the first
bit, and you are located on the first bit of the Facility Code. You then count 15
more bits to the right and you find the last bit of the Facility code information.
If you then count off the next 16 bits, you will find the Badge Number. The
next two bits are the Reissue number. The last bit is another parity check bit
(see figure 60.14 below).

P
Facility Code
Badge Number
Issue P
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Fig. 60.14. 36 Bit Badge Data Format with Fields Delineated and
Labeled

If we now take a close look at figure 60.4 and compare what you see in each
field of figure 60.4 to figure 60.14, you will see that both figures represent two
different ways to describe the same data structure. Figure 60.4 describes the
badge data string using numeric coordinates. Figure 60.14 is a graphic
representation of the numeric coordinates described in figure 60.4.
The information that is filled into the Offset and Length fields of a badge
format, tells the (panel) software where in the badge data string to look for the
Facility Code, the Badge Number and other data items included in the data
string.
So, when we are creating badge formats (in the Badge Formats screen), we are
actually telling the system how to decode strings of data bits from the readers.
The system does this by counting the bits as they are received and then
parsing those bits into groups of bits. What those groups of bits represent is
described in the Badge Formats screen by the titles on each of the fields
(Badge ID, Facility, Issue, etc.).
When you set up your system, it is imperative that you have a badge format in
the Badge Formats screen that exactly matches the type of badge you intend
to use. If one bit is unaccounted for in your format, the entire system may not
read badges. This means that you must know what type of badge format you
intend to use for your system, and you must be sure it is programmed
correctly.
Fortunately, the CardAccess software already has a few standard, time tested
badge formats pre-programmed into the Badge Formats screen. Lets
examine them in the following section.
Predefined Badge Formats

On opening the Badge Formats screen, you will see a few badge format records in
the upper half of the screen. These are the standard badge formats that are
preprogrammed and shipped with the CardAccess software.

Fig. 60.15. Badge Formats screen view window showing standard

badge formats available by
default in CardAccess software.
A short explanation of each format follows.

Format 1 Insertion 36 Bit Format

On highlighting Format 1 record in the Badge Formats screen view window,
the lower half of the screen will show the following settings.

Fig. 60.16. Settings for format 1 - 36 bit insertion format.

Referring to these settings, the data structure for the format can be constructed
as below.

Odd Parity Calculation

Even Parity Calculation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Facility Code

Badge Number

Fig. 60.17. Data structure for format 1 - 36 bit Weigand/HID.

Specifications for this format are as follows:

The badge format type is set to Insertion.
This data format is 36 bits long.

Issue

The data string starts (read left to right) with an odd parity bit.
The odd parity calculation is performed on the left most eighteen bits.
The next sixteen bits are the facility code.
The next sixteen bits are the badge number.
The next two bits are the issue level.
The data string ends with an even parity bit.
The even parity calculation is performed on the right most eighteen bits.

This 36 bit format can be used with Weigand swipe readers, HID 36 bit proximity
readers and Recognition systems 36 bit Biometric hand and fingerprint readers.
Any device using the 36 bit format will work using this predefined format. A
reader does not have to be an Insertion type to work with this 36 bit format. See
below for more details.
The Insertion badge format type (historically) refers to a type of Weigand
brand reader that has a slot in it, which accepts an access badge. This type of
reader is unique because it is one of several designs of readers that allow the
bit stream from a badge to be read forward and backward (one simply turns
the card around, and inserts it the opposite way around). Note that the
(Weigand) swipe type reader also allows you to read a badge bit stream
forward and backward (swipe in the opposite direction, as opposed to turning
the card around).
Time and Attendance logging is a CardAccess related application where
reading a bit stream backwards would be helpful. When setting up the system
for Time and Attendance logging, you have the option to use two separate
readers, one set up as an IN reader, and one set up as an OUT reader.
However, using one reader to read both the IN and OUT card swipes would
lower the total cost of the access control project. Using one reader for T&A IN
and OUT is permitted by the system.
So, if you were to use a swipe type reader for this application, when clocking
IN you would swipe your badge in a forward motion, when clocking out you
swipe your badge in the opposite direction.
When you create a badge format and set it as Insertion type, the Continental
access control panels become programmed to evaluate the badge bit stream as
swiped in either direction (left to right or right to left).

The ability to evaluate a badge when swiped backward is the primary

difference between the Insertion badge format type and other types. Other
badge format types do not allow backward swiping of badges. That is, if the
badge format stored at the panel is not an Insertion type, the panel will not
attempt to read the bit stream backward. A backward badge read will be
thrown away as an error.
Parity Calculation
In figure 60.16, on the lower right side of the diagram, there are two fields
that concern parity calculations. One is called Odd Parity and the other is
called Even Parity. The entries in these fields tell the software how to check the
incoming badge data string to make sure it has not been corrupted during
transmission.
The parity check digit is a standard method of checking a data string to be
sure that it has not been corrupted during its journey through wires. A parity
check digit or bit is added to a data string (usually at the end) and that digit or
bit is used as a reference to check the integrity of the rest of the data bits.
To create the parity check bits that are used for the 36-bit format, the 36-bit
format is divided into two, 18-bit formats. A calculation is made on each 18bit format individually (figure 60.17).
One bit is added as the first bit in the data string, to cause the first half of the
data string to have an odd number of ones. A second bit is added as the last
bit in the data string. This causes the second half of the data string to have an
even number of ones.
This odd and even parity is checked on every card read to be sure that the
data has not been corrupted between the reader and the panel.
Note
Corrupted badge reads are thrown away by the panel without any other
action, and with no error messages of any kind from the panel to the
PC.

 There are two alternate ways to set the parity calculation for the 36-bit
format. The above-mentioned method suggests dividing the format into
equal halves. This will work with most 36-bit cards. However, if you are
using
Motorola/Indala cards, they will not work with this parity calculation.
They require the parity settings as seen in figure 60.18 below.
If you install your system and all the settings seem to be right, but the system
is not reading cards correctly, try the parity settings as seen in figure 60.18.

Fig. 60.18. Alternate weigand 36 bit format parity settings.

Format 2 ABA 19 Character Format

On highlighting Format 2 record in the Badge Formats screen view window,
the lower half of the screen will show the following settings.

Fig. 60.19. Settings for format 2 19 character ABA format.

Referring to these settings, the data structure for the format can be constructed
as below.
SS Facility FS

Badge ID

Not Used

ES

B 1 2 3 4 5 D 7 8 9 10 11 12 13
14 15 16 17 F
Fig. 60.20. Data structure for format 2 19 character ABA magnetic
stripe format.
Specifications for this format are as follows:
This data format has 19 total characters.
The data string starts with a Start Sentinel, which will always be the letter
B (capital).
The facility code consumes the next 5 digits.
The next character is a Field Separator, which will always be the letter D
(capital).
The next 6 characters are the badge number (note the maximum 6 digit
badge number).
The five characters following the badge number are not used.
The last character is the End Sentinel. This will always be the letter F
(capital).
There is no check character programmed into this format.
The ABA 19-character format is generally used when encoding magnetic
stripe or barcode type cards. The ABA standard was developed for the

American Banking Association for use with ATM and credit cards. In the
access control application, some of the data characters available in this format
are not used.
In this card format, the data structure is expressed in characters instead of
number of bits (as it was above, in Format 1).
Format 3 Non-ABA 26 Bit Format
On highlighting Format 3 record in the Badge Formats screen view window,
the lower half of the screen will show the following settings.

Fig. 60.21. Settings for format 3 - 26 bit non-ABA format.

Referring to these settings, the data structure for the format can be
constructed as below.

Even Parity Calculation

Odd Parity Calculation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Facility Code

Badge Number

Fig. 60.22. Data structure for format 3 26 bit non-ABA format.

Specifications for this format are as follows.

The badge format type is set to Non ABA.

This data format is 26 bits long.
The data string starts (read left to right) with an even parity bit.
The even parity calculation is performed on the left most thirteen bits.
The next eight bits are the facility code.
The next sixteen bits are the badge number.
Issue level field is not used.
The data string ends with an odd parity bit.
The odd parity calculation is performed on the right most thirteen bits.

The 26-bit format is a well-known standard format and is identical in many

ways to the 36-bit format, Format 1. This format has parity bits at the
beginning and ends of the data string and is a Non ABA type (like Format 1).
This format is used by Motorola (Indala) readers. The Recognition Systems
hand and finger type biometric readers and HID proximity readers are also
available with 26-bit output and can use this format with no changes.
Note that the data string is divided into two halves, and parity is calculated
separately on each half (like Format 1). Note that Even parity is calculated on
the left half of the data string and that Odd parity is calculated on the right
half of the string which is opposite of the way it is done in Format 1.
Note that the standard 26-bit format does not provide an Issue Level field.

Format 4 Non-ABA 31 Bit Format

On highlighting Format 4 record in the Badge Formats screen view window,
the lower half of the screen will show the following settings.

Fig. 60.23. Settings for format 4 - 31 bit non-ABA format.

Referring to these settings, the data structure for the format can be constructed
as below.

Odd Parity Calculation

Even Parity Calculation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Issue

Facility

Badge Number

Fig. 60.24. Data structure for format 4 31 bit non-ABA format.

Specifications for this format are as follows.
The badge format type is set to Non ABA.
This data format is 31 bits long.

The data string starts (read left to right) with an even parity bit.
The even parity calculation is performed on the left most seventeen bits.
The next two bits are the issue level.
The next eight bits are the facility code.
The next sixteen bits are the badge number.
The data string ends with an odd parity bit.
The odd parity calculation is performed on the right most seventeen bits.

Note that the parity calculation for this format is different from formats 1 and 3
explained above. Here, there are three bits in the center of the format that are
used for both parity calculations. These three bits overlap both the odd and the
even calculations.

Creating Badge Formats

If you are creating a badge format, there are basically two things to consider.
Are you creating your own custom badge format (for use with barcode or
magnetic stripe cards), or are you creating a format for a card type that you
have purchased from a supplier (a standard format). The approach you take
will be quite different for each method. Essentially, there are only two kinds of
access cards - those that have preprogrammed data, and those that are
programmable by the user.
Preprogrammed Access Cards
Weigand cards, HID proximity cards and Motorola/Indala cards are the
examples of preprogrammed access cards. The badge data string is encoded
into each card by the manufacturer. These cards are well known and the
formats for cards from these manufacturers are already programmed into the
CardAccess software.
Preprogrammed cards have some advantages and disadvantages as listed below.
Preprogrammed Access Card Advantages

 There is no need to get data on these cards. The badge data string will be
encoded into each card by the manufacturer. This proves to be time
saving.
Badge formats are well known and already programmed into the
CardAccess software.
Preprogrammed Access Card Disadvantages
Unit price is higher.
It is much harder to get cards with duplicate badge numbers and higher
issue levels.
Programmable Access Cards
Examples of programmable access cards are magnetic stripe cards and barcode
cards. Magnetic stripe cards are plain PVC plastic cards with an electronically
programmable magnetic stripe embossed on the card. You can encode magnetic
stripes with a special card printer available from Continental Instruments.
Barcode is printed on blank, plain PVC plastic cards using a standard card
printer, also available from Continental Instruments.
Programmable Access Card Advantages
You can exercise complete control on what data gets programmed on the
card.
Initial price per unit is lower.
You can use a standard badge data format or create your own
proprietary format.
Badges can be made to work with multiple manufacturers systems (such
as CardAccess and a Time and Attendance system).
It is easy to reissue cards with the same badge number (reissue levels).

 You can print as many or as few cards as you need, when you need them.
rogrammable Access Card Disadvantages
More time is needed to program these cards.
More technical complexity is involved. The CardAccess administrator
must create badge programming data strings in the badge editor
software. He will be responsible to ensure that the badge format is
entered correctly and is working properly.
Note: There are essentially two kinds of badge data types; ABA and NonABA. Both data types have the same data fields available to them Badge
ID, Facility and Issue. If you are using magnetic stripe cards or barcode
cards, you must include Badge ID (it is a required field) in your badge format.
Facility and Issue are optional.
There are two things you should do before trying to create any kind of badge
format.
If you have purchased access cards from a supplier, ask that supplier to
provide you with a description of the badge format.
Before trying to create a custom or standard badge format in the Badge
Formats screen of CardAccess, draw a diagram of your badge format (see
figure 60.25 below). This will act as your guide and will make it easy to count
characters or bit places as you create the format. Remember that if you
misstate even one bit of the badge format in your description, it is likely that
the system will reject all card reads. The format that you create in the
Badge Formats screen must be exact.

Creating a Standard Format

There are numerous different types of access control cards. Weigand, HID,
Motorola/Indala, 26 bit, 36 bit and more. The place to start is to be sure what
format of card you are buying, since we have to describe that badge format to
the system.
If you purchase all of your supplies from Continental Access, the readers and
cards will be a matched set and the badge format will be well known to
Continental Technical Support Representatives, who can help you set up the
system.
The 36-bit format (Format 1) and the 26-bit format (Format 3) are the most
commonly used because they are widely adopted standards. Format 2 is most
often used with magnetic stripe cards and barcode cards.
Note: If some or all of the CardAccess predefined badge formats are missing
or corrupted, you can restore them quickly by clicking the Default button at
the top of the Badge Formats screen.

Below are the steps to create a 36-bit format.

1. Draw a diagram of your badge format.

Odd Parity Calculation

Even Parity Calculation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Facility Code

Badge Number

Issue
Fig. 60.25. Diagram of 36-bit Badge Format.
2. Open the Badge Formats screen by clicking on

Administration Badge Formats menu options in the CardAccess main

screen.
3. Click the New button in Badge Formats screen toolbar.
4. In the Name field, enter a descriptive name for the badge format you are
creating.

Fig. 60.26. The Name field.

5. Click the down arrow to the right of Badge Format Type control and
choose a desired format type. Insertion type is selected in the figure
below.

Fig. 60.27. The available badge format types.

6. In the Bit/Char Length control, set the total bit length of the format equal
to 36.

Fig. 60.28. The Bit/Char Length spin control.

There are two ways to set the number.
o Clicking the white space of Bit/Char Length control and typing in
the number.
o Using the up/down arrows to the right of the spin control to choose
the required number.

7. Click the Offset field for Badge ID, and type in the number 17. Similarly
enter the Length for Badge ID as 16.

Fig. 60.29. Offset and Length fields for Badge ID.

8. Click the Offset field for Facility, and type in the number 1. Similarly
enter the Length for Facility as 16.

Fig. 60.30. Offset and Length fields for Facility code.

9. Click the Offset field for Issue, and type in the number 33. Similarly
enter the Length for Issue as 2.

Fig. 60.31. The Offset and Length fields for Issue.

10.Click the Offset field for Even Parity, and type in the number 18.
Similarly enter the Length for Even Parity as 18.

Fig. 60.32. Offset and Length fields for Even Parity.

11.Click the Offset field for Odd Parity, and type in the number 0. Similarly
enter the Length for Odd Parity as 18.

Fig. 60.33. Offset and Length fields for Odd Parity.

12.Click on Save button in the toolbar to save the settings.

On clicking the Save button, the format will be automatically downloaded to
the concerned panel(s).
Note: You cannot create two very similar badge formats. The system will have
a logical error trying to differentiate which format it should use. The two
formats must be uniquely different enough for the system to recognize. As a
general rule, do not create two formats with the same number of bits or
characters.
Creating a Custom Format

When creating a custom format, you will be limited to using cards that do not
have a preprogrammed format on them. Barcode and magnetic stripe cards
are the only two types of cards that can be considered.
There will be nothing different about the badge format that you create for
magnetic stripe cards vs. barcode cards. Both will use the ABA badge format
type. Within the framework of the ABA type, certain start and stop
characters are required (not optional). Also you must include the badge
number as a required field. However, Badge Number is the only required
field. Facility Code and Issue Level are optional.
Note: The total number of bits read from any badge cannot exceed 255.
Therefore any custom non-ABA format Bit/Char length cannot exceed 255
bits, and any custom ABA format cannot exceed 53 characters (each ABA
character is 5 bits)
You will need to follow the steps below in order to create a custom format.
Make a diagram of your proposed format.
SS Facility FS Badge ID
B

12345 6

7 8 9 10 11 12

Not Used

ES

13 14 15 16 17 18 F

Fig. 60.34. Data structure for the standard 19- character ABA format.

When creating your data structure diagram, bear in mind that there are some
required items and some optional items. You can modify the above standard

data structure for your own use, but consult the requirements lists below
before creating your format.
Custom Format Required Items
The Start Sentinel and the End Sentinel are required. The position of those
fields in the data structure must be at the beginning and at the end of the
data string. However, the characters themselves can be any characters 0-9
or A-F (any hexadecimal character). We will use the standard characters
in these examples.
The Badge ID field is required. The position of this field in the data string
is optional, it can be placed anywhere in between the Start and End
Sentinels.
Note: The system will allow a maximum of 9 badge digits. The Badge field in
ABA formats cannot exceed 9 digits, and the Badge field in non-ABA formats
cannot exceed 27 bits.
Custom Format Optional Items
The order of the data fields does not matter. As long as required fields are
included in the data string, which field appears in the string first is not
important, except for the Start and End Sentinels which must be placed at
the extreme ends of the string.
The Field Separator character is optional. If you wish to adhere to the
ABA standard you will include the field separator character. However, it
can be eliminated without penalty.
The Facility code field and the Issue level field are both optional. They can
be eliminated from the badge format with no penalty.

Fig. 60.35. The standard 19-character ABA Format.

Note: When you set any of the data fields to Offset = 0 and Length = 0, or if
you leave them blank, it means that those fields are not used.
Lets create two example custom formats to illustrate the process.
Custom Badge Format Example 1
The constraints for this badge design are: - we will allow a 5-digit badge
number on the badge and there will be no other data encoded on this badge.
This would represent the simplest badge format the system will allow.
First, lets construct a data diagram.

SS Badge ID ES
B 1234
Fig. 60.36. A custom 7- character badge format.

Now lets construct the above format in the Badge Formats screen.

Fig. 60.37. Custom 7- character badge format created.

Follow the steps below.
Open the Badge Formats screen by clicking on
Administration Badge Formats menu options in the CardAccess main
screen.
Click the New button in Badge Formats screen toolbar.
Copy the values seen in figure 60.37 above into the respective fields.
Give the badge format a descriptive name in the Name field.
Note:
o Observe that the total Bits/Char length is seven characters, not five (see
figure 60.37). The length calculation includes the Start and End
Sentinels. In an ABA format, the count is in number of characters, not
bits.
o Observe that the Start Sentinel begins at offset zero and the End
Sentinel begins at offset six (see figure 60.37). Each Sentinel is one
character wide. Sentinel characters in custom formats are not limited to
B and F. Sentinels can be any character 0-9, or A-F, but the Start
and End Sentinels cannot be the same character

 Click on Save button in the toolbar to save the settings.

Custom Badge Format Example 2
In this format, we will allow a five-digit badge number. We will also allow a onedigit issue level field and an 8-character field for future use. There will be no
facility code for this format.
Again, lets construct a data diagram first.

SS Badge ID

Not Used

IS ES

B 1 2 3 4 5 6 7 8 9 10 11 12
Fig. 60.38. A custom 16- character badge format.

Now lets construct the above format in the Badge Formats screen.

Fig. 60.39. Custom 16- character badge format created.

Follow the steps below.
Open the Badge Formats screen by clicking on
Administration Badge Formats menu options in the CardAccess main
screen.

 Click the New button in Badge Formats screen toolbar.

Copy the values seen in figure 60.39 above into the respective fields.
Give the badge format a descriptive name in the Name field.
Note:
o Observe that the total Bits/Char length is sixteen characters. The length
calculation includes the Start and End Sentinels (see figure 60.39). In an
ABA format, the count is in number of characters, not bits.
o Observe that the Start Sentinel begins at offset zero and the End
Sentinel begins at offset fifteen (see figure 60.39). Each Sentinel is one
character wide. Sentinel characters in custom formats are not limited to
B and F. Sentinels can be any character 0-9, or A-F, but the Start
and End Sentinels cannot be the same character.
o Observe that we have added eight characters to the data string that are
not used by the CardAccess (see figure 60.38). These characters could
potentially be used by another device that can read a bar code or
magnetic stripe.
o Observe that we have limited the Issue level to 1 character (see figure
60.39). That means that we will allow up to 9 total re-issues (1-9). In
case 2 characters were entered, a maximum of 99 re-issues were
possible. Note that when you encode a badge that has never been
reissued, the Issue level is set to 0.
Magnetic stripe and bar code cards make it easy to replace lost cards with
cards that have the same card number. You simply create another identical
card. This is called reissuing the card. Issue level refers to how many times
the card has been reprinted for the user.
Click on Save button in the toolbar to save the settings.

Deleting a Badge Format

Open the Badge Formats screen by clicking on

Administration Badge Formats menu options in the CardAccess main
screen.
In the upper half of the screen, locate the badge format you wish to delete
and click on it.
Note: Deleting a Badge Format could disable all badges in the system! Select
only unused badge formats for deleting.
Click on Delete button in the toolbar. Upon clicking, the following message
box will be displayed.

Fig. 60.40. Message box displayed before deleting a badge format.

After confirmation, click on Yes button in the message box.
Click on Close button in the toolbar to close Badge Formats screen.

Badge Formats Screen Navigation Bar

Fig. 60.41. The Badge Formats screen navigation

bar.
The Badge Formats screen navigation bar can be found in the middle of the
screen. The arrows of the bar can be used for viewing
older/newer/bookmarked badge format records in the screen. In figure 60.41,
we have numbered the arrow buttons of the bar to provide simpler
explanation. The functions of the arrow buttons are as follows:
Arrow 1: Placing the mouse cursor over arrow 1 will display the
message First record. Accordingly, clicking on this arrow will highlight
the very first badge format record in the screen.
Arrow 2: Placing the mouse cursor over arrow 2 will display the
message Prior page. Accordingly, clicking on this arrow will highlight
the last record in the page previous to the current page, containing the
highlighted badge format record.
Arrow 3: Placing the mouse cursor over arrow 3 will display the
message Prior record. Accordingly, clicking on this arrow will
highlight the record previous to the currently highlighted badge
format record.
Arrow 4: Placing the mouse cursor over arrow 4 will display the
message Next record. Accordingly, clicking on this arrow will highlight
the record appearing after the currently highlighted badge format
record.
Arrow 5: Placing the mouse cursor over arrow 5 will display the
message Next page. Accordingly, clicking on this arrow will highlight

the first record in the page appearing after the current page,
containing the highlighted badge format record.
Arrow 6: Placing the mouse cursor over arrow 6 will display the
message Last record. Accordingly, clicking on this arrow will highlight
the last badge format record in the screen.
Arrow 7: Placing the mouse cursor over arrow 7 will display the
message Save Bookmark. Clicking on this arrow will bookmark the
highlighted badge format record.
Arrow 8: Placing the mouse cursor over arrow 8 will display the
message Goto Bookmark. Clicking on this arrow will highlight the
previously bookmarked badge format record.
Restoring Default Badge Formats

If you accidentally delete one or all of the default badge formats that are
available in CardAccess, you can restore them by following the steps below.
Note: The steps below will delete all of the existing formats in the screen, and
restore only the default formats that are available in the software.
Open the Badge Formats screen by clicking on
Administration Badge Formats menu options in the CardAccess main
screen.
Click on Default button in the toolbar.

Fig. 60.42. The Default button.

On clicking the following message box will be displayed.

Fig. 60.43. Message box displayed on clicking the Default button.

Click on Yes button in the message box.
Click on Close button in the toolbar to close the Badge Formats screen.
The default formats will be automatically downloaded to all panels after
restoration.
Downloading Badge Formats to Panels

If you are having problems reading badges, you may need to download the
badge formats to the concerned panel(s) manually. The following steps will be
involved.
Open the Panels screen by clicking on ConfigurationPanels menu options
in the CardAccess main screen.
Click on Download button in the Panels screen toolbar.

Fig. 60.44. The Download button.

Upon clicking, the Download Categories screen will be displayed as below.

Fig. 60.45. The Download Categories screen.

In the Download Categories screen, click on Badge Formats check box.

Fig. 60.46. Badge Formats checkbox selected.

On checkbox selection, the Download Panel and the All Panel buttons
will be enabled (see figure 60.47 below).

 Click on Download Panel button if you are downloading badge formats to

only a particular panel or click on All Panels button if you are
downloading badge formats to all panels in the system.

Fig. 60.47. The Download Panel and All Panels buttons.

Note: These buttons will be enabled only after the Badge Format
checkbox is selected (see figure 60.46 above).
On clicking one of the buttons, the following message box will be displayed.

Fig. 60.48. Message box displayed before downloading badge

formats to panel(s).
After confirmation, click on Yes button in the message box to start the
download.
At this point, badge format downloading would have begun if communications to
the panel is operating.
Click on Close button in the toolbar to close the Panels screen.