Below is a list of errors the user may receive if they attempt to upload problematic data.
- Warning: “The captured images cannot be processed. Please press the calibration button and scan again without changing any of the camera settings.
Solution: This error means that some of the images were captured with a zoom lens instead of a wide lens. During calibration, the CaptureApp sets the camera lens to be “Wide” but it can be changed to zoom by clicking the zoom button on the Camera View Screen. Please recalibrate and scan again ensuring this button is not touched.
- Warning: Some or all of the images were taken without an RTK fix. This could lead to a less accurate verification and longer processing times. Would you like to proceed with the process?
Solution: This error means that some of the images were captured without an RTK fix (The RTK icon wasn’t white). Siteaware can process these images but it may impact the accuracy of the solution. Siteaware recommends re-scanning if possible but still uploading this dataset so processing can begin.
- Warning: Some or all of the images are missing parameters that are required by Siteaware. This could lead to less accurate verification and longer than usual processing times. Would you like to upload them anyway?
Solution: This error means that after calibration, some of the camera settings were changed which can affect the quality of the digital twin. Siteaware recommends re-scanning if possible but still uploading this dataset so processing can begin.
- Warning: A minimum of 10GB of free space on the remote control is required to complete the upload. Please clear space in the local storage and try again.
Solution: This error means that there’s not enough memory remaining on the controller to complete the upload process. Please delete some files to ensure that there are at least 10GB of free space on the controller.
- Warning: An error occurred while picking the file.
Solution: This error means that there’s an issue accessing the files on the device. Exiting the app and re-entering should solve this issue.