SP500X Software FAQ

Below you will find the most frequently asked software questions about the Handheld SP500X ScanPrinter.

1. Security: Is the device secure?
   The device is a terminal and only accepts the incoming connection it is looking for. Commands are parsed by the user application code, and the underlying system is not available remotely. Additionally, the WiFi module firmware is separate from the device firmware and can be updated separately as security patches are released by the module vendor.
2. OS (Operating System) setup: What is the OS and is it separate from the user firmware?
   Yes, the OS is MircoPython and is built into the API layer. It is stored in a separate partition on the device memory and is read-only (except specifically during an upgrade).
3. OS updates: How are OS updates distributed?
   OS updates will be available on the Handheld website and can be pushed to the unit either via USB or via Wifi (if the customer has the system set up for this). Note that the firmware and core MircoPython environment are very stable and is only updated for extended functionality, bug fixes, or customer customization needs.
4. Database: What type of database can the device operate?
   The device natively supports a .ini file as the primary data store. Also, the device can support any remote database through the customer’s remote API.
   
   There is no native support for local SQL. However, there are libraries that support SQLite you can download and test.
5. Storage: How much storage does the OS occupy as standard and what is available for custom applications and data?
   There is 7GB of available storage accessible to the user/application on the mmc partition. There is 195kb of storage on the internal partition for APP code. The DEMO APP only uses 70KB of storage, leaving plenty of space for expanded functionality.
6. MDM (Mobile Device Management): Is this device compatible with MaxGo or any MDM tools?
   No, this device is not compatible with MaxGo. However, the APP can be customized to integrate with custom MDM tools.
7. Device status: How do you know the status of devices on your system?
   The APP can be customized to send the desired device status to your backend system; or do a check to see what is connected to your AP.
8. Logging: Does the device log usage information?
   Yes, the unit logs information. How much, and what kind is completely controlled by the customer via API updates. Depending on the customers protocol, the device can also send information to a server application for logging on that side. The duration the unit stores the logs are customizable by the customer, default is 10 files of 1KB each, files are replaced in a FIFO manner.
9. Communication Protocol: What communication protocols does the device support?
   The device currently supports UDP and Bluetooth SPP (Serial Port Profile) protocols.