Terminal Self Test

Terminals have a diagnostic self-test mode for checking connected components.

The self-test can be executed using:

1. a special diagnostic QR code at the BATM, or

2. triggered remotely via the “Terminal Self Test” action.

Self Test results are immediately recorded in the Event Log.

Access a historical diagnostics table via:

• Terminal Details > ACTIONS > Monitor > Diagnostic History

• Terminals > Analytics > Diagnostic History

Remote Diagnostics

Navigate to the Terminal of interest and click on ACTIONS: Terminal Self Test

Open

Onsite

Set a Diagnostics Key on the Terminal Details page for the BATM being tested.

1. Create a “Diagnostic Key” of any arbitrary string of characters (maximum 255).

2. Use the same new “key” to generate the QR code, see: https://generalbytes.atlassian.net/l/cp/CKX0V3QX.

3. Enter the key in the relevant Terminal’s Details to enable the onsite self-test function.

4. Save the Terminal settings.

The BATM will now download the key, and it should be effective within minutes.

Open

When onsite, trigger the test by attempting:

1. a transaction using a QR code created from the Key, or

2. entering an administration mode (pressing the “!” icon) and presenting the diagnostics QR.