BadgeMaker Encode
Creating a MIFARE Classic Template using the CCI Editor
Launch the CCI Editor, which will open to a blank window. Choose “File” → “New” → “Mifare Classic (1k)” or “Mifare Classic (4k)” depending on your project requirements.
The Card Settings are displayed on top of the screen (A). You are able to define whether the card should use MAD Sectors or not. Enabling this setting will have an impact on specific sectors and their contents. It will also automatically generate Key A for sector 0 (and sector 16 for 4K cards).
On the left of the screen (F), a list of sectors is displayed, 16 for 1K cards, 40 for 4K cards. Depending on the settings, each of the sectors can contain information that will be encoded onto the card through BadgeMaker Identity.
The center of the screen (B,C,D and E) allows you to configure the information for the currently selected sector. You are able to define keys, determine read and write settings for each of the four data blocks and create data segments to fill the available space. The CCI Editor visualizes any data that will be encoded onto the Smart Card in order to give the user a better view of the amount of used and available space in each sector.
#SCREENSHOT#
Certain blocks (such as Block 0 on Sector 0, and the Trailer Block on all sectors) are reserved for manufacturer information and storing keys. These are not available to the user, and are displayed as hatched.
Each square represents one byte of information. When adding sector data, the length of the data is visualized on the right. Each item in the list is given a slightly different color to make it easier to understand how the data is transferred to the card.
• Dynamic Data
This is information that will be added to the card by your BadgeMaker project. Similar to adding card desings, when you add a CCI file to your project, a pop-up will allow you to bind columns in your project to each of these items. You must always ensure that the data in your project corresponds with the settings you have chosen in terms of length and data type. The following data types are available.
| ASCII | All standard ASCII characters are allowed. |
| Numeric | 0 … 9 |
| Alphabetic | A … Z and a … z |
| Alpha-numeric | A … Z, a … z and 0 … 9 |
| Alphabetic and special | A … Z, a … z and Punctuation marks |
| Alpha-numeric and special | A … Z, a … z, 0 … 9 and Punctuation marks |
| Binary-coded decimal (5) | 0 … 9, two digits in one byte, maximum 5 bytes |
| Binary-coded decimal | 0 … 9, two digits in one byte |
| Binary-coded decimal date | YYYYMMDD each two digits in one byte |
| Decimal | 0.00 (Fixed point) |
| Wiegand-26 | Facility and card codes with parity |
| Hexadecimal | 0123456789ABCDEF |
| Octal | 012345678 |
| Binary | 01 |
In addition, you are able to add a description of the sector data to remind you of certain agreements.
• Constant Data
Constant or Static data is data that is manually entered in the CCI file and will never change. The format of this piece of information can be of any of the types mentioned in the Dynamic Data section.
• Empty Space
This item can be used to indicate a specific part of a sector that will never be used.
• Card serialnumber
This is a 10-byte, right aligned numeric data section which will automatically contain the card serialnumber when the card is being encoded.
Using these options, you can create any type of CCI file. Once completed, you are able to save your work in either an unencrypted file (XML) or an encrypted CCI file. If you choose the latter option, you will be required to enter a password that will also be required when adding the CCI file to your BadgeMaker Identity project.