m if Are Encoding Badge Creator

8/12/2019 m if Are Encoding Badge Creator

1/34


2/34

Page 2of 34

Contents

Contents .................................................................................................................................................. 2

Introduction to Mifare ............................................................................................................................. 3

New Mifare Layout Wizard ...................................................................................................................... 4

Mifare Encoding in BadgeCreator ........................................................................................................... 7

Mifare Encode Layout Toolbar ............................................................................................................ 7

Open an Existing Mifare Layout .......................................................................................................... 8

Mifare Menu .......................................................................................................................................... 10

Add Field ........................................................................................................................................ 10

Add Function ................................................................................................................................. 13

Add Binary Item... .......................................................................................................................... 15

Edit Item ........................................................................................................................................ 17

Add Database Update ................................................................................................................... 18

MM10 Integration ......................................................................................................................... 19

QE Integration ............................................................................................................................... 20

Remove Item ................................................................................................................................. 22

Remove DB Update Item ............................................................................................................... 22

Overview ........................................................................................................................................ 22

Edit MAD ........................................................................................................................................ 23

Options Menu ........................................................................................................................................ 31

Encode Settings... .......................................................................................................................... 31

Settings .......................................................................................................................................... 32

Viewing Mifare in BadgeMaker. ......................................................................................................... 34

View or Hide Encode Data ................................................................................................................. 34


3/34

Page 3of 34

Introduction to Mifare

MIFARE is based on the International Standard ISO/IEC 14443 Type A.

MIFARE is used for contactless smart card systems. MIFARE typically has a maximum read and write distance of

10cm. It is highly secure and reliable as there are no moving parts and no battery involved in the operation of

MIFARE.

MIFARE 1k features

MIFARE 1k has a storing capacity of 1 KB of information (768 Bytes). Unique serial number of 4 Bytes 2 x 48 bit keys per sector for key hierarchy. Data Retention is around 10 years. 16 sectors (or tracks), each sector contains 4 blocks, 3 user blocks (block 0 to 2) and one key block (block 3) Sector 0 block 0 cannot be used (contains manufactory data) Sector 0 block 1 and 2 can be used for the MAD. Each block contains 16 bytes.

MIFARE 4k features

MIFARE 4k has a storing capacity of 4 KB of information (3480 Bytes). Unique serial number of 4 Bytes. 2 x 48 bit keys per sector for key hierarchy. Data Retention is around 10 years. 40 sectors (or tracks). The first 32 sectors contain 4 blocks, 3 user blocks (block 0 to 2) and one key block (block 3) Sector 0 block 0 cannot be used (contains manufactory data) Sector 0 block 1 and 2 can be used for the MAD for sector 1 to 15. In case MAD is used, sector 16 block 0 to 2 contain the MAD information for sector 16 to 39. The last 8 sectors contain 16 blocks, 15 user blocks (block 0 to 14) and one key block (block 15). Block 0 key is for block 0 to 4 Block 1 key is for block 5 to 9 Block 2 key is for block 10 to 14 Block 3 key is for block 15, which is the key block. Each block contains 16 bytes.


4/34

Page 4of 34

New Mifare Layout Wizard

Select File Menuand click New Layout Wizardto open the wizard, the following screen is presented.

Click from the BadgeCreator Toolbar.

The Welcome screen can be skipped in future by selecting Don't display this screen in the future.

Click Nextto proceed to the next screen and begin configuring a New Layout.


5/34

Page 5of 34

Select Contactless Chipto create and click Nextto proceed.

In this dialog choose the type of contactless chip to use.

Select Mifareand click Nextto continue.

Select which type of Mifare chip to use.

For this example Mifare 1Kis selected.

Allow multitrack database items (non-binary): Select this option to scan a field across multiple tracks (for large

segments of information).


6/34

Page 6of 34

Enable MAD Section: Enable MAD(Mifare Application Directory) to define common data structures for multi

application directory entries.

Once all settings have been defined and configured the final dialog is presented. Click Finishto complete the

Wizard or click Backto change settings. When you click Finisha new layout is presented in BadgeCreator.

Form the BadgeMaker Toolbar click , this will open BadgeCreator and start the New Layout Wizard.


7/34

Page 7of 34

Mifare Encoding in BadgeCreator

Select the File Menu, click Mode, and then click Mifare Encode Layout to open Mifare Encode Layout Mode.

Click from the BadgeCreator Toolbar and select Mifare Mode from the drop down menu.

Main Screen

Mifare Encode Layout Toolbar

In Mifare Encode Layout mode, mifare layouts are created and edited.

The Toolbarin Mifare Layout Mode can be used to quickly start a function by clicking on the desired button.

Back to Main Screen

Click on this button to return to the BadgeMaker main screen.

Badge Layout Mode

Click on this button to enter the badge layout mode to configure/create badge layouts.

Magnetic Layout Mode


8/34

Page 8of 34

Click on this button to enter the magnetic layout mode to configure/create magnetic encode layouts.

Chip Mode

Click on this button to the chip layout mode to configure/create chip encode layouts.

Mifare Mode

Click on this button to enter the Mifare Layout Mode to configure/create Mifare Layouts.

Open Layout

Click on this button to open an existing Mifare layout linked to the current project (*.BM) file.

New Layout

Click on this button to start the New layout Wizard.

Save Layout

Click on this button to save the current layout.

Add Field

Click on this button, to add a field to the current track.

Add Function

Click on this button, to add a function to the current track.

Add Binary Item

Click on this button, to add a binary field to the Mifare Layout.

Add DB Field

Click on this button, to store a constant, counted value or card serial in a database.

Remove Item

Click on this button, to remove a field from the layout.

Preview

Click on this button, to preview a layout.

Open an Existing Mifare Layout

Select File Menu and click Open Layout or use from the toolbar.

The following screen is presented. Configured Mifare Layouts are listed here.


9/34

Page 9of 34

Select Mifare Demo.

The layout is presented in the BadgeCreator main screen.

Mifare DEMO


10/34

Page 10of 34

Mifare Menu

The MM10 and QE Integration cannot be activated together. You must select either MM10 integration or

QE integration. Both are payment systems facilitated by BadgeCreator.

Add Field

This option is used to add fields from the database to a track.

A 1K Mifare card has 16 tracks; track 0 is used to store the Mifare Application Directoryinformation in track 1

until 15 can be used to write data in. Each track has 4 blocks of 16 bytes of which 3 can be used to enter data.

In the fourth block the keys and access information are stored.

When you add a (non-binary) field it must fit into one track, so the size cannot be larger than 48 bytes. Binary

items which do not fit into one track can be added by using the option Add Binary Itemfrom the Fieldsmenu.

If you work with 4K Mifare cards instead of 16 tracks there are 39 tracks available.

On track 1 -31 there are 3 blocks available for storing data (Zone A); the 4th block is for the keys of the track.

On track 32-39 there are 15 blocks available for data (Zone B), the 16th block is for the keys. To go to zone B,

click the Zone Bbutton.

Select Mifare Menu and click Add Field or use from the toolbar.

The following dialog is displayed.


11/34

Page 11of 34

Select a field to add to your current mifare layout.

When creating a New Mifare Layout the operator will have the option to enable Allow multitrack

database items (non-binary): Select this option to span a field across multiple tracks (for larger segments of

information).

Add to

Track: Select which track to write the field to.Block: Select a block to write a field to.

Begin Byte: Select a Begin Byte to write the field to.

No. of bytes: Select the number of bytes needed for a field.

Options are dependent on field type.

Encode As

Encode As: Select the method to encode information onto the card. Select an option from the following.

Character

String: (field type character, numeric and date)


Decimal: (field type numeric)

Binary coded decimal: (field type numeric and date)

Date

Numeric


12/34

Page 12of 34


Motorola decimal: (field type numeric)

Intel decimal: (field type numeric)

Binary coded decimal: (field type numeric and date)

The contents of a date field can be encoded in different orders. Select a set from the drop down list.

In case you encode as a string every character is represented by its ASCII value (every character is encoded into

one byte).

Motorola and Intel decimal encoding work with hexadecimal values. Special hexadecimal encoding is a mixture

(hexadecimal notation without decimal to hexadecimal conversion of the value).

Example

Suppose the database has a numeric field with 4 positions named ID number. The value

is 1500(=05DC hex).

The following ways of encoding are possible.

In the case the largest value of the field ID number would be 9999999 (98967F hex),

there would be 7 bytes needed to encode it as a string, 3 bytes to encode it as Motorola

or Intel decimal and 4 bytes to encode it as special hex.

The following example shows how unused bytes are fil led when the number of bytes

assigned for the field is more than needed.

Number of bytes assigned is 6, the value is 1500.

When you encode character fields it is possible to concatenate multiple fields. This can be done by pressing the

CTRLkey (on the keyboard) and clicking on the lines with the fields which have to be joined. The text box

Fields: will display the joined fields (field1 + field2 etc.). By joining fields space can be saved. E.g. in the


13/34

Page 13of 34

database for the field Firstnameand for the field Surname35 characters are reserved. Each character will take

one byte. The chance that both the surname and the first name will have 35 characters is smaller than that the

surname or the first name will have 35 characters. For that reason the unused positions behind each field will

be removed. A space will be added between the fields. The unused positions between the last character of the

joined fields and the last byte on the card will be filled with zeros (encoding as a string). In the example two

tracks would be needed to encode the surname and first name separately. Combined it would be acceptable to

use one track of 48 bytes. If the first name is equal or smaller than 12 characters, the full 35 characters are

available for the surname (48-(12+1)) and vice versa.

At the bottom an overview summary is shown illustrating the fields positioned on the current layout. It is

possible to scroll down and view the entire layout structure of the mifare encode layout

Summary

Numbers running across are the number of bytes in each Block. Number running down the left hand side are

the number of Blocks to a Track.

Select OK to add the newly created field.

Add Function

Select Mifare Menu and click Add Function or use from the toolbar.


Add functions


14/34

Page 14of 34

Except for the card serial number, functions occupy one byte.

Function

Constant: Select a value between 0 and 255. This value will be encoded into the selected byte. If more thanone byte is selected, same value will be encoded to every byte. The value can also be read from the database.

Select Field listed in the Function Properties, the value from the field will be encoded onto the chip layout.

Count: The counter function can read a value from the database and increment it with

a defined value (e.g. the number of times a new card is issued for the same individual can be stored in the

database), or an array with incremental values can be encoded.

Function Properties

In Function Properties you can select if the value must be incremented after it is written to the card.

Value: Select a value between 0 and 255.

Card Serial Number: The card serial number (encoded by the manufacturer in track 0) can be read from the

card. A card serial number that was written in the card by the manufacturer can be stored into the database in

BadgeMaker when the card is encoded. That way it is possible to check the database which card number was

assigned to a certain person. This number can be stored as a decimal or hexadecimal value.

Checksum: A checksum can be calculated over a number of bytes. Select the way the checksum is calculated,

select where the checksum should be stored and select the bytes where the checksum should be calculated

over. The checksum is one byte, if more than one byte is selected for the checksum, the value of the checksum

will be repeated in every byte.

Function Properties

In Function Properties you can select the way a checksum is calculated.

XOR

I 0 0 I I 0 0 I

0 I I 0 0 I I 0

0 0 I I 0 0 0 I

I I I 0 I I I 0

0 I I I I 0 I 0

Result: 0 I 0 I I 0 I 0

Selecting XOR will always result in a value that fits into one byte.

When ADD is selected the low byte value will be written to the card.

ADD

I 0 0 I I 0 0 I

0 I I 0 0 I I 0

0 0 I I 0 0 0 I

I I I 0 I I I 0

0 I I I I 0 I 0

Result: I 0 I 0 0 I I 0 0 0

Parity


15/34

Page 15of 34

A parity check can be selected, since encoding is done in minimal parts of one byte, it will occupy one byte

only.

Polynomial CRC is the most reliable way to calculate a checksum.

At the bottom an overview summary is shown illustrating the fields positioned on the current layout. It ispossible to scroll down and view the entire layout structure of the mifare encode layout.

Polynomial CRC

Use a polynomial to calculate the checksum. When you use a polynomial fill in the polynomial you would like

to use.

Example: The polynomial to use is x8+x5+x4+x2+1. This is represented by the binary value 100110101 (309 in

decimal). In the PolyOne text box a decimal value must be specified. This decimal value must be between 257

and 511 (between 100000001 and 111111111 binary).

Start Value: Select a value between 0 and 255 and fill it in, in the box.

Summary

Numbers running across are the number of bytes in each Block. Number running down the left hand side are

the number of Blocks to a Track.

Add Binary Item...

Select Mifare Menu and click Add Binary Item or use from the toolbar.



16/34

Page 16of 34

Add binary fields

Add a binary field to the Mifare Layout.

Select an Image Type stored as a BLOB (Binary Large Objects). Below as an example Photo is chosen.

Add Binary item

Select the range on the card where it should be encoded.


17/34

Page 17of 34

Most images (photos, signatures or fingerprint images) are too big to encode on a card. Biometric data

such as fingerprint or hand palm characteristics are in general small enough to store on the card.

Track: Select a Begin & End Track to write the field to.

Block: Select a Begin & End Block to write a field to.Byte: Select a Begin & End Byte to write the field to.

Select Apply to insert the new binary field. Click OK to exit.

Edit Item

Select Mifare Menu and click Edit Item.


Add field dialog

Select a field to edit in your current mifare layout.

Fields

Track: Select which track to write the field to.

Block: Select a block to write a field to.

Begin Byte: Select a Begin Byte to write the field to.

No. of bytes: Select the number of bytes needed for a field


18/34

Page 18of 34

When creating a New Mifare Layout the operator will have the option to enable Allow multitrack

database items (non-binary): Select this option to scan a field across multiple tracks (for larger segments of

information).

At the bottom an overview summary is shown illustrating the field and where it is positioned on the currentlayout. It is possible to scroll down and view the entire layout structure of the mifare encode layout.

Add Database Update

Select Mifare Menu and click Add Database Update or use from the toolbar.


Select a field from the database which will be updated automatically from information and a card when the

Mifare card is read.

Constant: A constant value can be stored in the selected field. When the card is encoded, the value will bewritten in the field. (Fixed Text)

Count: A counted value can be stored in the selected field. It will be incremented for every card encoded. The

start value can be given in or can be read from another (or the same) field.

Card Serial No: The card serial number that was written in the card by the manufacturer can be stored in the

database when the card is encoded.

Example

A card serial number that was written in the card by the manufacturer can be stored in the database when the

card is encoded. That way it is possible to check the database which card number was assigned to a certain

person. This number can be stored as a decimal or hexadecimal value.

The database update functions are displayed in the lower half of the main screen.


19/34

Page 19of 34

DB Update field

MM10 Integration

Select Mifare Menu and click MM10 Integration.

If you wish to make a link with MM10 Integration (MagnaCarta payment system) you can link fields fromBadgeMaker to fields in the MM10 Integration.



20/34

Page 20of 34

Select Enable Carthago Section and set the Begin Track for MM10 on the Mifare chip and the Nr of Tracks used

by MM10 Integration.

Select an MM-10 Field and map a BM Field to it.

The following fields are mandatory to use MM10.

CostAccount CardNumber Surname

If these fields are not mapped to a corresponding BM field encoding will fail.

Select OK to apply changes or Cancel to undo any changes made.

QE Integration

QE Integration (Quality Equpiment payment system), you can link fields from BadgeMaker to fields in the QE

Integration.

Select Mifare Menu and click QE Integration.

The following dialog is presented.


21/34

Page 21of 34

QE Settings

Select Enable QE Section to encode Mifare cards for use in QA10/QV10 environments payment systems.

Select which tracks will be used. QE Integration requires 3 tracks to encode.

Map a QE Field to a BM Field from your database to set up.


22/34

Page 22of 34

Select OK to save the QE configuration or Cancel to undo any changes made.

Remove Item

First you must select a field and then select Mifare Menu and click Remove Item or use from the toolbar.


Select Yes to remove the selected field or No to cancel removal.

Remove DB Update Item

First you must select a field and then select Mifare Menu and click Remove DB Update Item or use from thetoolbar.


Select Yes to remove the selected DB Update field or No to cancel removal.

Overview

Select Mifare Menu and click Overview.



23/34

Page 23of 34

Mifare Summary overview

The overview display's a preview of the data that will be encoded onto the current layout.

Full Screen: Display the Overview full screen (enlarged).

Print: To print the Overview select this option.

Edit MADSelect Mifare Menu and click Edit MAD.

MIFARE Application Directory (MAD) defines common data structures for card application directory entries,

allowing terminals to identify the right card (and the right memory sector within the card) without the need to

perform a comprehensive search through all of the cards memories until the appropriate application is found.

The following dialog is presented.


24/34

Page 24of 34

Mifare Application Directory

MAD (Mifare Application Directory) can be used to assign different applications to different tracks

To administrate free tracks

To register card holder info

To register card publisher infoTo protect tracks against writing new data

Select Use Mifare Application Directory to enable.


25/34

Page 25of 34

MAD

Select New to assign an application to tracks.

MAD

Select the MAD tab, the following dialog is presented.


26/34

Page 26of 34

Application info

Specify a Function cluster. Specify an Application code.

Show as either Decimal or Hexadecimal.

Select Save + exit to return to the main MAD dialog box.

Select which tracks are to be assigned to the Mifare Application.

Select OK to close.

Admin

Select the Admin tab, the following dialog is presented.


27/34

Page 27of 34

Select which of the tracks not yet populated in the layout will remain free.

Selected tracks will be highlighted in blue.

Select OK to close.

Card Holder Info

Select the Card Holder Info tab, the following dialog is presented.


28/34

Page 28of 34

Card holder info

Select Enable Card Holder Info to select the appropriate database fields for the individual.

Use the drop down lists to select a field from your database.

Select OK to close.

Card Publisher Info


29/34

Page 29of 34

Select the Card Publisher Info tab, the following dialog is presented.

Card Publisher Info

Select Enable Card Publisher Info to enter Card Publisher Info and assign a track to write the information to.

Protection


30/34

Page 30of 34

Select the Protection tab, the following dialog is presented.

Protection

Select the tracks to be protected against a failure occurring during the write process.

Selected tracks are shown highlighted.

When you have completed your Mifare layout, close and save the layout. The layout is stored as a *.MIFfile.


31/34

Page 31of 34

Options Menu

When an encoding layout has been created and saved, it is added to a list of available encode layouts already

stored in BadgeCreator.

The current badge layout can now be linked together with a saved encode layout. The Badge will then be

printed and encoded in a single process when sent to the printer.

Encode Settings...

Select Options Menu and click Encode Settings. The following dialog is presented.

Connect encodes

In the Connect Encodes dialog link an encode layout to a badge layout. Check the right badge is selected. On

the left-hand side of the window, the available configured encode layouts are displayed.

Select one and click the transfer right button.

Now the encode layout will be displayed on the right-hand side of the window.


32/34

Page 32of 34

Click Apply to save.

A combination of one chip encode layout and one magstripe layout is possible. Only one contact or

contactless chip encode layout can be connected at a time. If you try to connect them both to a layout the

following warning message is displayed.

To disconnect an encode layout, select the layout on the right side and click the transfer left button.

Click OK.

To disconnect an encode layout, select the layout on the right side and click the transfer left button.

Click OK to close and save settings.

Settings

Select Options Menu and click Settings.



33/34

Page 33of 34

Settings

Mifare Version

Select the type of Mifare Chip being used.

Mifare 1K classic: Select a Mifare 1K classic type.

Mifare 4K classic: Select a Mifare 4K classic type.

Allow multitrack database items (non-binary): Select this option to scan a field across multiple tracks.

Binary items will not be affected by this setting.


34/34

Viewing Mifare in BadgeMaker.

In BadgeMaker, there is not much visible evidence for Mifare support. Mifare is treated like any other contact

or contactless chip encode encoder.

In the preview of BadgeMakers main screen the chip encode information is visible.

View or Hide Encode Data

To show encodedinformation configured on the card select from the Toolbar.

This button located on the Toolbar is for viewing or hiding the encoded badge information.

Click View Chipto view chip encode information (magstripe information is not displayed).

When a print command is given the encode information will be send to the printer and the chip move and the

encode dll will be called.

Apart from the encoding in the printer also a manual encode option available in the BadgeMaker toolbar .

This option will send the encode data to the encoder.

Documents

m if Are Encoding Badge Creator