On the Action tab:

• The 'Run command' allows you to use command line interfaces or scripts that are dependent on the card ID which has been read. There is a Run command example.

• The 'Launch URL' option lets you create a similar action for your website. There is a Launch URL when a card is presented example.

Both of these actions allow multiple parameters to be used, such as the reader serial number (if available), card type, or time stamp, as well as the card ID.

On the Format tab you can create an advanced template for the keyboard buffer to use. This greatly increases the range of the Default - Keyboard wedge functionality by allowing you to insert special characters or keyboard commands, to direct the information you want to where it is needed. The Insert RFID card ID into Word or Excel example uses this facility.

On the Web Server tab you can enable a web server from which your web site or application can receive card data obtained through Read‑a‑Card. There is more about this under Using the Read‑a‑Card web server.

On the Lock tab you can lock the Read‑a‑Card user interface to prevent end‑users from accidentally modifying the settings after an application has been set up.

On the Logging tab you can easily create folder structures and logs with names based on information gathered by Read‑a‑Card, such as which reader detected the card or the current date. The Log contactless card information example demonstrates this facility. The Read‑a‑Card logs that are created can be used by your software and read back in real time.

Some plug‑ins only require that Read‑a‑Card is licensed for the plug‑in to function; others require specific configuration data. If a plug‑in appears in the dropdown list but is 'greyed out', it is unable to work for one of these reasons.

Clicking on the next to the format dropdown box will pop-up an information window showing the currently selected plug‑in format name, version, and other features. This window also contains a link to edit the .ini configuration file for the plug‑in and a link to help in this online help.

Read‑a‑Card currently includes:

• NFC Decoder for decoding certain types of text NDEF records stored in NFC tags;

• Paxton Net2 Compatible Decoder for converting card IDs to the format used by Paxton systems;

• DESFire Decoder for reading secure application DESFire files;

• MIFARE Sector Decoder for decoding data stored in MIFARE Classic sectors, including those protected by specific access keys; and a

• Custom Format Decoder to extract specific data in particular formats.

If you require something else, or have any other requirements for decoding and returning contactless card ID information, please contact us via support@read-a-card.com to discuss how we can help.