Tools

EVAL Log Extract

Drop an HTML test log exported from EVAL and get every APDU exchange back in two formats: a readable trace with command names, timestamps and status words, and a raw list with one APDU per line, ready to paste into another tool.

Your log stays on your device. The file is read and processed in your browser; nothing is uploaded. EVAL is a product of FIME; this tool is independent and not affiliated with FIME.

Drop an EVAL HTML log here or Choose a file No file loaded.

Or paste the HTML source of the log

Readable trace

Command name, C-APDU and R-APDU with timestamps, status word and its meaning, grouped by transaction.

One APDU per line

Commands and responses alternate, in order. Each response ends with its status word. A <tap> line marks each SELECT PPSE (contactless), an <insert> line each SELECT PSE (contact), and a <mute> line replaces the response to a command the card never answered. The file starts with the terminal's dynamic data for each transaction (9A, 9F21, 9F37, 9F6A, DF8301), read from the commands along the card's DOLs; a tag is written alone when its value was not found.

How it works

What it reads

EVAL HTML logs list each event in a table row with a level, a name, a value and a timestamp. The tool keeps the rows of level CAPDU and RAPDU, pairs each command with the response that follows it, and keeps the transaction markers (for example "Transaction : (1/2)") and the test header.

Commands that get no response

A command the card never answered is written as a <mute> line in the one-per-line format. A SELECT PPSE logged during the test preamble is paired with the response logged right after the transaction starts. A "no APDU received" timeout is kept in the readable trace as a note.

What to do next

Paste any response into the TLV parser to decode it, or take a SELECT PPSE response and the reader configuration to the Entry Point simulator.