📌 Problem
In LP360 Job Manager, a TGO (SLAM) or Sensor Processing Extension (SPX) job fails, completes with warnings, or leaves an expected output missing or incomplete. The job message or log may show:
- TGO (SLAM):
ERROR_BASE_POSITION_ERROR,ERROR_POS_SOLVE_FAILED,ERROR_SLAM_DATA_COPY_ERROR, or an available-memory warning or reminder. - SPX: “Unable to start picture processing,” “Unable to start point-cloud processing,” or a picture or point-cloud stage that did not produce the expected output.
- Either job type: A task-folder or temporary-folder operation failed, or the job reported a warning or diagnostic you do not recognize.
🔍 Root Cause
There is no single cause. Depending on the diagnostic, processing may be affected by incorrect base coordinates, incomplete base observations or collection data, low available system memory, an inaccessible or locked folder, insufficient disk space, a processing component that cannot start, or a graphics hardware or driver limitation.
A generic solver failure, missing output, or unfamiliar identifier does not establish a root cause. Use the named processing stage, the exact message, and the job log to narrow down what happened.
🧠 What is a job diagnostic?
A job diagnostic records what a worker reported during processing. TGO diagnostics relate to SLAM processing, while SPX diagnostics may identify the picture or point-cloud stage. A warning can remain visible after a job completes; it does not necessarily mean processing failed. Inspect the affected outputs before using them.
✅ Probable Resolutions
In Job Manager, open the job message details and select View Log. For SPX jobs, use File Explorer to find additional logs. Choose the resolution that matches the exact diagnostic.
TGO: Base position error
For ERROR_BASE_POSITION_ERROR, verify that you selected the intended base station, that its coordinates and coordinate reference system are correct, and that its observations cover the collection period. Correct the base inputs and retry. If the error repeats, include the solver log and base setup when contacting Support.
TGO: Position solve failed
For ERROR_POS_SOLVE_FAILED or a generic SLAM failure, look in the solver output for a more specific diagnostic. If it reports a base position error, follow the base position checks. If no cause is clear, send Support the full job log and the processing mode.
TGO: Available system memory warning
For WARNING_SLAM_AVAILABLE_MEMORY_BELOW_15GB, PROMPT_SLAM_AVAILABLE_MEMORY_REMIND, or a message about low available system memory, close memory-heavy applications and avoid running multiple processing jobs at once. If processing completed, check the point cloud for coverage gaps. If you retry, keep the first output and log for comparison.
TGO: Incomplete input data
For ERROR_SLAM_DATA_COPY_ERROR or a message saying downloaded data may be incomplete, verify that the original collection is intact, copy the complete collection again, and reimport it. Keep the original data until you verify the replacement import and output.
TGO or SPX: Processing could not start
If the job says it was unable to start SLAM, picture, or point-cloud processing, check the Windows error and path in the job details. Verify that the working folder is accessible and writable and that the required processing component is installed. If the message identifies a missing or blocked component, send the exact error to Support.
TGO or SPX: A task folder, temporary folder, or previous LAS output could not be updated
For a task-folder replacement failure, a temporary processing folder error, or an SPX message saying previous LAS output could not be removed, check the reported path for free space, write access, and file locks. Close applications using the affected output and restore access to any disconnected drive before retrying. Preserve retained inputs, prior outputs, and the job log.
Graphics hardware, driver, or graphics memory
Compare your GPU and driver with the LP360 GPU guidance.
- For
0x1112(outdated driver), update the driver. - For
0x1113(insufficient graphics memory), close GPU-intensive applications before retrying. - For
0x1111(unsupported GPU) or0x1114(insufficient compute capability), check whether the hardware meets the requirements. Graphics memory is separate from system memory.
SPX: Picture or point-cloud processing failed or expected output is missing
Use the stage named in the message to identify which input and output folders to check. Verify that the folders are accessible and that the expected photos or LAS files exist before using partial results. If the log does not identify a fix, send Support the stage, any reported worker status, and the additional logs from the job folder.
TGO or SPX: The job completed with warnings or reported an unfamiliar diagnostic
Copy the exact identifier and accompanying detail, review the affected stage, and inspect its output. If the warning repeats or the output is incomplete, send Support the job log, the diagnostic, the LP360 version, and the Sensor Extension version if applicable.
📚 Additional Notes
For help with processing settings, see SLAM Processing.
If geocoding succeeded and the only issue is a lower-than-expected point count, see Troubleshooting Geocoding Issues.
📬 Need Help?
If you're still stuck, please Contact Support for assistance. Include the job type, exact diagnostic, processing stage, software version, and relevant logs.
Comments
0 comments
Please sign in to leave a comment.