Event Log

A Terminal’s Event Log contains a record of every conversation between the BATM and CAS. Some of this information is not displayed, but can be located by downloading the CSV log. The codes are “bitwise” - each represents a single on/off state, which means that multiple states may be represented by an aggregation of codes (i.e. error code 2 + error code 16 = 18; representing both error states. “18” itself isn’t an error code.). Thus, you may see codes that aren’t listed (but can still be derived).

The Log is informational only, and provides a wealth of data. Don’t overreact to ominous tones! In some cases, an error is expected & routine, yet must still be logged (and reported here).

The Event Log is routinely requested by the Support team, as it contains vital information needed to diagnose the most common problems.

See: Send Logs to Support

Select the appropriate Date Range, or leave it blank for all recorded events.

Non-cash events are displayed (default).

Show only cash handling events.

TERMINAL STATUS BITS IN DB:

Code	Message	Description

Code	Message	Description
1	SERVER IS NOT REACHABLE	The BATM is unable to open a connection to CAS. See: OOO: Server is not Reachable
2	ACCEPTOR STACKER OUT	Reinsert the stacker/cashbox.
4	ACCEPTOR STACKER FULL	Grab your cash! Check that the cashbox is not packed full and that there is room for more banknotes.
8	ACCEPTOR UNKNOWN ERROR	Check you BATM’s acceptor connections.
16	NO CAMERA	Verify the USB plug is connected. Also see: Symptom: QR codes ignored at BATM
32	PAPER MISSING	Refill the printer paper. Also see: Printer Troubleshooting
64	ACCEPTOR JAM ERROR	Clear your acceptor/stacker/cashbox jam.
128	NFC CARD MISSING	Refill the NFC cards.
256	CONNECTION REJECTED ERROR	Pairing error. See: OOO: Client Certificate Mismatch
512	CONNECTION TIMEOUT ERROR	Internet error.
1024	UNKNOWN NETWORK ERROR	Internet error.
2048	SERVER CERTIFICATE MISMATCH	See: OOO: Client Certificate Mismatch
4096	TLS ERROR	See: OOO: Client Certificate Mismatch
8192	PAPER LOW	Refill the printer paper. Also see: Printer Troubleshooting
16384	NFC COLLECT BIN FULL	Check the NFC card dispenser.
32768	LAST NFC DISPENSE ERROR	Check the NFC card dispenser.
65536	NFC CARDS RUNNING LOW	Refill the NFC cards.
131072	PRINTER DISCONNECTED	See: Printer Troubleshooting
262144	ACCEPTOR IS NOT DETECTED	Check you BATM’s acceptor connections.
524288	PRINTER DISCONNECTED	See: Printer Troubleshooting
1048576	ACCEPTOR STACKER FULL	Grab your cash! Check that the cashbox has freeplay.
2097152	ERROR MACHINE MAINTENANCE	Terminal “Active” has been unchecked in settings.
4194304	ERROR ACCEPTOR SERIAL NUMBER MISMATCH	The acceptor head’s serial number is unrecognized. Enter the BATM ADMINISTRATION screen, then exit.
8388608	TERMINAL PAUSED	CAS is preparing to restart, transactions not allowed.
	DOOR SENSOR STATUS	A door sensor was triggered (opened or closed).
	TRANSACTION ATTEMPTS REACHED	This event is logged when a user reaches the “insert cash” point level of a transaction, but fails to insert cash - 3 times in a row. This feature is intended to notify you of repeated abandonment of transactions.
	TRANSACTION LIMIT REACHED	Your customer has exceeded your AML/KYC limit(s). SOLUTION: Register them, or grant them VIP limits (if appropriate). Check that their documents haven’t expired.

Cash Manipulation:

These events are limited to cash in/out only. This log is useful when determining cash receipt/dispensing problems.

REMOTE events occur at the BATM.

REMOTE events are then shared with CAS, which acknowledges them in a “LOCAL” event.

Send the Event Log to Support:

Support may ask for your Event Log for a specific Terminal. Find the download icon on this page.

Save it as a CSV (comma-separated values) file.
Do not convert it to any other format.
Logs sent in other formats will be rejected; they are a security risk.