Add project settings to your configuration
In the project settings, you define which data is read from the project card and how it is converted. You can create project settings once you've collected the project information.
Supported card types
In most cases, you'll have 1 configuration file and add 1 project settings component to it as described below. In more complex scenarios, however, you may need multiple project settings, e.g. when dealing with various card types or exchanging an encryption key (learn more here).
Add a project settings component
Open BALTECH ConfigEditor.
If you haven't installed it yet, you can download it herecall_made as part of BALTECH ToolSuite.
In the popup window, click Open and select the BALCFG file of your existing configuration.
If you don't have a configuration file yet, create a new one.
Click Extend Configuration.
- Navigate to the card type you want to add.
- Select the appropriate Autoread form and fill it out as described in the next chapter.
Select and fill out project settings form
Depending on your card type, one or several forms are available. Below, you get an overview of when to use which form and how to fill it out.
125 kHz cards
Default form to read the card's UID.
- If the UID returned by the card matches the expected number, you don't have to fill out anything. Just save the empty form as part of your configuration.
- If the numbers don't match, enter the UID returned by the card in the Sample UID field and use the UID Transformation Rules to convert it into the expected number.
Autoread UID in Wiegand Format
Use this form if the data on the card is encoded in Wiegand format. You'll get Wiegand-specific UID transformation rules to obtain the expected number.
13.56 MHz cards
Read the card's UID.
- If the UID matches the expected number, you don't have to fill out anything. Just save the empty form as part of your configuration.
- If the numbers don't match, use the UID Conversion Rules to convert the UID into the expected number.
Autoread UID with Authentication
Read the UID of a card that returns a random ID by default.
- In the Card Parameters section, specify any encryption key for reading the card's UID.
- If the card's real UID doesn't match the expected number, use the UID Conversion Rules to convert the UID.
There's a standard and an advanced form. Please always start with the standard form. Only use the advanced form if the standard form doesn't produce the expected result.
- This form covers standard HID bit lengths. If you can rule out certain bit lengths for your project card, select Restrict card formats to disable them.
- Convert the PCN into the expected number. To do so, use the options in the Cut PCN section (learn more about these options here).
- If the form doesn't return the expected number when you test it in ID-engine Explorer, your card uses an uncommon bit format. In this case, use the advanced form.
- Open the advanced form. Without making any changes, test it in ID-engine Explorer.
- Take the number returned by ID-engine Explorer and enter it in the Data in hex field of the form. The first byte is the bit length, the following bytes are the card number.
- Convert this number into the expected number. To do so, use the options in the Facility Code and ID Code sections (learn more about these options here). By default, the options in the IC Code section are applied to the entire data stream. To convert the facility code individually, select Activate Facility Code.
- If you want to use HID configuration cards to deploy HID Elite Keys to the reader, select Enable HID ConfigCards.
All other card types
Read a PCN stored in the card's memory.
Autoread ID of NFC ID App
Use this form if you use an NFC ID app instead of a card.
- Specify the number to read and its byte length.
When you're done, you can test your project settings.