Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

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.


Introduced in Terminal firmware version 20220106.


Remote

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

Onsite

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

The Diagnostics Key is disabled (empty) by default.

  • It must be set to enable the onsite diagnostic function.

  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.

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.

  • No labels