I  recently pefformed a large area scan at 300 feet elevation. i noticed a few passes on the stockpile did not register together correctly and are about 500mm apart in elevation.  I am wondering if it has to do with the gaps in the lidar on top of the mound?    i flew at a consistant height of 300feet but the big stockpile was about 150-200ft tall which meant the lidar didnt have enough overlap as it only would have been 100+- feet above the large pile.   Please see attached photos.  RTK is good

What kind of base station are you using?

WELL, that brings me to my next question. I used a Trimble R12 base that i have used many times before with no issues. However this time i was getting this error shown on the photo.  i shouldnt be getting this error as i had full RTK connection the entire flight which is proven by the green line in DJI terra showing excellent RTK.          I could not get it to process so i downloaded a 1 second interval file from the nearest CORs station about 10km away. The files processed sucessfully with that other than this anomoly.

i have never had any issues with this setup but of course i did all of the software updates and now i am running into issues.

with RTK i didnt think you needed overlap in the lidar, however that is the only difference in this flight to others is that there is some missing overlap

RTK during all the flight does not mean the correction is good. From what i can see there is a potential antenna reposition.

djiuser_D8RutBwjfjta Posted at 11-1 07:09
WELL, that brings me to my next question. I used a Trimble R12 base that i have used many times before with no issues. However this time i was getting this error shown on the photo.  i shouldnt be getting this error as i had full RTK connection the entire flight which is proven by the green line in DJI terra showing excellent RTK.          I could not get it to process so i downloaded a 1 second interval file from the nearest CORs station about 10km away. The files processed sucessfully with that other than this anomoly.

i have never had any issues with this setup but of course i did all of the software updates and now i am running into issues.

Is the rinex file in the right format ? Covering the whole flight duration? Not farther than 25 km ?

LV_Forestry Posted at 11-1 07:18
Is the rinex file in the right format ? Covering the whole flight duration? Not farther than 25 km ?

Distance is 19KM to reference station.  i used version 2.11 but here are the options.

djiuser_D8RutBwjfjta Posted at 11-1 07:21
Distance is 19KM to reference station.  i used version 2.11 but here are the options.[view_image]

Terra is theoretically able to read all. Choose 3.04 i use that and it works.
19km is ok.
Think about deleting the RTB file and replace rinex file extension by OBS.

going back to my R12 base perhaps it is not working as i may have the wrong RTCM version.   Should i be using 3 legacy?

djiuser_D8RutBwjfjta Posted at 11-1 07:28
going back to my R12 base perhaps it is not working as i may have the wrong RTCM version.   Should i be using 3 legacy?

MSM must work as well.

LV_Forestry Posted at 11-1 07:29
MSM must work as well.

turns out, i went back to 3.0 legacy on my trimble base and am no longer getting processing errors

djiuser_D8RutBwjfjta Posted at 11-1 08:20
turns out, i went back to 3.0 legacy on my trimble base and am no longer getting processing errors

good to know

LV_Forestry Posted at 11-1 08:38
good to know

it would be nice if DJI Pilot 2 would give you a warning that something wasnt right if Terra doesnt like it. Luckily i pay for a CORS service so i had backup however that would have been an entire day of flying wasted when the controller was showing everything was perfectly fine....

djiuser_D8RutBwjfjta Posted at 11-1 11:53
it would be nice if DJI Pilot 2 would give you a warning that something wasnt right if Terra doesnt like it. Luckily i pay for a CORS service so i had backup however that would have been an entire day of flying wasted when the controller was showing everything was perfectly fine....

Pilot can’t see if something is wrong with base station coordinates. They are provided by the base station itself as a message. If the message doesn’t exist it will display 0000 as coordinates but that’s it.