When integrated into an Axium SmartPOS device, the SDK writes local log files on the host mobile device that can be retrieved to help integration support diagnose issues.

Log File Location

The SmartPOS logs sit under a fixed subdirectory of the host application's file storage. Use the path component below to construct the full path:

String chipDNASmartPosLogPathComponent =
    "NMI" + File.separator + "ChipDNA" + File.separator + "smartpos_logs" + File.separator;

This resolves to NMI/ChipDNA/smartpos_logs/ within the host application's file storage.

📘
These logs are written by the SDK on the host mobile device, not on the Axium itself. If you need diagnostics from the Axium device, contact NMI integration support — they have separate tooling for retrieving device-side logs.

When to Collect Logs

Collect and forward the SmartPOS logs to NMI integration support when:

A transaction returns an unexpected TransactionResult or error code that you cannot reproduce.
The SDK fails to connect to an Axium device that is otherwise reachable on Bluetooth.
The AttemptingToReconnect event fires repeatedly without recovery — see Device disconnection.
An OTA update fails or hangs — see OTA updates.

Include the timestamp range relevant to the issue, the device's BluetoothDeviceId and Bluetooth name, and the transaction's UserReference if applicable, so support can match the log entries to the events you're investigating.