Sodex Mobile 1.1.3 improves Help Center access, upload workflows, SDX-PocketScan status feedback, and NTRIP connection handling. It also moves the Sign Out button and makes ARKit scan processing more stable.
Summary
Sodex Mobile version 1.1.3 was released on February 02, 2026. This release focuses on easier access to help content, smoother upload handling, clearer device information in the app, and more reliable NTRIP and ARKit behavior during scanning workflows.
Key highlights
Open Help Center articles directly in the app
You can now open Help Center content from inside Sodex Mobile. The new Help button is available in the Settings and Scanning screens and opens the documentation in an in-app WebView.
Manage uploads more easily
Cloud ZIP exports are now saved in CloudExports/, which makes them accessible in the iOS Files app. The 3D scan viewer also now includes an Upload button, so you can start an upload directly from the viewer.
See clearer device and debugging information in Settings
Sodex Mobile now shows the serial number of the connected SDX-PocketScan. The app also adds Show Upload Debug Info to the main Settings area, which makes it easier to review upload details when you need to troubleshoot or verify behavior.
Keep ARKit processing more stable
ARKit now pauses during scan processing and restarts with fresh tracking after export completes. This reduces the risk of unstable tracking behavior during processing-heavy steps.
Fixes and improvements
- Settings layout: The Sign Out button now appears at the bottom of the Settings list.
- NTRIP connection setup: Sodex Mobile no longer requires a GPS position before it can connect to NTRIP.
- NMEA time handling: GGA messages now use UTC time instead of local time, which aligns better with NTRIP server expectations.
-
NTRIP request format: The app now uses
NTRIP SDX-PocketScan/1.0as theUser-Agent, removes theNtrip-Versionheader, and adds aHostheader to the source-table request. - GGA timing: GGA messages are now sent on a timer after the connection is established instead of being sent immediately after the mountpoint request.
- Retry behavior: Retry attempts now continue even when GPS is not available, and the retry delay increases from 0.5 seconds to 3.0 seconds to reduce the risk of server rate limiting.
Comments
0 comments
Please sign in to leave a comment.