Skip to content

Encoding conversion via configuration

When a reader reads a number from a card and transmits it to the host system, this number's encoding is converted in 2 steps.

From card-specific to ASCII decimal encoding

The encoding of the number on the card depends on the card type. Since there may be different card types with different encodings in the same project, all numbers need to be converted to a standardized encoding before they can be processed further. The standardized encoding used by BALTECH readers is ASCII decimal.

This conversion step is covered by the RFID interface component.

From ASCII decimal to host-specific encoding

The host system may expect to receive the number in yet another encoding. In this case, the reader converts the number accordingly before transmitting it to the host.

If you need this conversion step, you need a custom host interface component that you can order from us.

ConfigEditor and ID-engine Explorer show the number after the 1st conversion step

When testing the RFID interface configuration in BALTECH ConfigEditor or ID-engine Explorer, you'll see the number in ASCII decimal encoding. Thus, this output may differ from the output you'll later see in your host system. This can be very helpful when troubleshooting: If e.g. the output in ConfigEditor or ID-engine Explorer looks good, you know that the bug is in the host interface component.

Diagram: Encoding conversion via RFID interface and host interface components in the configuration of a BALTECH reader