Anyone else having problems with this update?
You can add additional ranges and fill in what your missing. I think its just a matter of clicking the “+” under the trash can near the range. I would double check any of the data you use from that though, odds are it didn’t pass an initial QC checkmark. But I’ve had that issue and gone back and added ranges and it checked out with my independent survey shots.
Mel, this is Andrew with the ROCK Support Team, if you would like to discuss this issue in greater detail, please send an email to support@rockrobotic.com and we can work to get a resolution.
Andrew, Sorry for a delayed response on this! I believe the file uploaded from the R3pro was corrupted or incomplete for some reason. I deleted and reloaded the camera file to my hard drive and then reprocessed from the beginning. Had no issues with the trajectories and finished the project. AS ALWAYS, thank you!
Mel, thanks for the update and good news. In the future if you have problems or questions like these, please email support@rockrobotic.com, and I would be happy to help you.
@Mel-northtex (and anyone else that comes across this thread). The most likely cause for this type of issue is that when transferring the data from the usb to your hard drive, the usb was either:
The solution is to do exactly what you did, try to re-transfer from the USB drive to your computer and try processing again.
Hey Alex,
I’ve seen this issue for multiple flights now but I have a 2 TB local drive used only for LiDAR processing that’s got plenty of room to spare. I always watch for the process to complete and transfer the data to two separate locations from the USB for safety. I can compare both those transfers to confirm that all the files are there and the files are the same size. The computer never goes to sleep because it’s configured to never sleep and I’m constantly using it anyway.
I’ve also had times where both transfers don’t show the entire trajectory and are missing the same portion - most often, it’s the take off, IMU configuration, and sometimes the first portion of the flight.
@Melissa can you confirm what version of the firmware you have on your R3 Pro?
We were on 2.00.06 2024.11.15 for the last few flights we encountered the issue on; We’ve updated the unit to 3.01.00 2025.8.26 today.
@Melissa it could also be a usb issue. Are you using the same usb drive that came with the unit? If so, run a full re-format on the usb (not quick reformat). There could have been either some corruption or drive failure on the usb.
Alex,
We have 4 of the recommended Samsung USB drives (Using a new flash drive and formatting it with the R3 Pro) that we do a complete reformat on between every project after data has been copied to two separate locations, processed in Rock Desktop from the local hard drive copy, and then processed into deliverables with TerraScan to confirm data quality.
Usually, I have to confirm with the pilot the area flown to make sure that there’s enough coverage of the flight area to just proceed with what we can get. But having to repeatedly copy the data off the USB, repeatedly process the data to check how much of the trajectory Rock Desktop will show, and then communicate with the field team to confirm what was actually flown is all very time consuming.
@Melissa This is not normal. Can you send in the logs and a dataset where this is occurring to support@rockrobotic.com?
