Maintain Axium software and collect diagnostics
Handle required updates and distinguish host SDK logs from terminal-side diagnostics.
Complete first-boot setup
Use the device setup application for network connectivity, Bluetooth where required, and registration/software installation. Match charging and power instructions to RX, EX or DX hardware. A reachable host connection does not establish terminal-to-gateway connectivity.
Surface required and deferrable updates
The Device Agent surfaces OTA notifications and the SDK emits FirmwareUpdate. Required updates block further processing; deferrable updates eventually become required. Triggering through the SDK hands the foreground to Device Agent and returns to the integrating app afterward.
Do not fabricate update progress
Large updates can take five to ten minutes. Axium firmware controls download/install and does not report granular progress through the SDK. Show an updating state rather than an invented percentage. Device Agent owns the retry screen when the update fails.
Collect the correct logs
Host SDK logs are under NMI/ChipDNA/smartpos_logs/ inside the host app storage. These are not Axium terminal logs; terminal diagnostics require integration support. Correlate the relevant time range with BluetoothDeviceId, device name and UserReference. Apply your secure support process before sharing logs.