📌 Problem
LP360 doesn’t recognize a Cycle folder. This can happen when attempting to load directly from the UMS drive or from an archive folder. The Cycle dialog will not show flight information for the Cycle that the user is attempting to select, resulting in the LP360 Error, "The selected folder is not a valid Cycle Folder."
Figure 1: Import Window – Cycle Dialog
âś… Probable Resolutions
-
Review the Cycle folder structure
The file structure requires three basic components to import a Cycle properly in LP360:
- The folder name must have “Cycle_” at the beginning of the name.
- There must be a sub-folder in the cycle folder named “System”
- In the “System” folder there must be a “SystemConfiguration.json” file.
- In the “System folder there should be a “CycleParams.json” file.
Cycle folder format
If the user changes the file structure in a way where these conditions are not met, the Cycle will not be available for import.
L:\Cycle_191212_184916 | +---System | CycleParams.json | SystemConfiguration.json Example of proper file structure
-
Reinsert the USB Storage Device and Retry the Download
This error may occur if the data download from the TrueView payload’s USB storage device was interrupted or incomplete. LP360 may be unable to recognize the Cycle folder if required files were not fully copied.
- Safely eject and reinsert the USB storage device into the system
- Verify the USB drive is fully recognized by the sensor
- On startup the system should copy the entire Cycle folder to the USB
- Confirm that all files and subfolders were copied successfully
After the data has been fully copied, retry importing the Cycle in LP360.
If the dataset still cannot be recognized as a valid Cycle folder, review the other Probable Resolutions in this article.
-
Use the Minimal TrueView Workflow
If the dataset does not contain all standard TrueView Cycle files, LP360 may not recognize the folder as a valid Cycle folder. This can occur if:
- The dataset is incomplete or partially recovered
- Some Cycle files were not generated during collection
- Files were moved, renamed, or copied outside the original structure
- The data did not originate from a native TrueView system
In these cases, the dataset may still be processed using the Minimal TrueView workflow, which allows LP360 to import raw sensor data as long as the minimum required files are present (such as a system configuration file, a trajectory file, and raw LiDAR data).
The Minimal TrueView workflow is intended for recovery and special‑case scenarios where a full TrueView Cycle structure is not available.
Learn more about the Minimal TrueView workflow
If a complete and healthy TrueView dataset is available, the standard TrueView workflow should be used instead.
📬 Need Help?
If you're still stuck, please Contact Support for assistance.
Comments
0 comments
Please sign in to leave a comment.