Object reference not set to an instance of an object

Problem

When exporting an MX7 mission to Trimble MX, Mapillary or TopoDOT, you get this error: "Error exporting TMI database (...).tridb: Object reference not set to an instance of an object."

Solution

• Try to increase the duration of the sbet by initializing from VNAV in POSPac.

  

• Import the database with no SBET. In this case it will use the realtime solution (.nav) and precision will suffer. You can see the realtime position error in the POSPac plots

  

• Remove the sync file lines for which the time is not covered by the SBET, and remove the corresponding frames in the PGR by re-exporting only the frames covered by the SBET. Use LadybugCapPro to open the PGR and export the desired range of frames into a new stream (PGR) file.

Problem Details

Typically this error means that the image time interval (contained in the sync files) is not fully covered by the sbet time interval, at the beginning and/or the end because of an insufficient navigation system initialization. You can confirm this by comparing the start and end time in the sbet and sync files. For the sbet you can for example look at the SBET latitude plot in POSPac

Zoom at the very beginning to see the start time (here 154 426 seconds):

Zoom at the very end to see the end time (here 155 907 seconds):

For the image time, open the first sync file of the camera and look at the first GpsWeekSeconds value to get the start time:

And open the last sync file and look at the last GpsWeekSeconds value to get the end time:

In this example you can see that the sbet started at 154426s, before the start of the first sync file (155393s), and ended at 155970s, after the end of the last sync file (155538s). Therefore the sbet covers entirely the sync time and the error will not occur.

Related Products

Trimble Business Center (TBC)

Support Reference

SYMM-1710, 00350695, 00505124

Last modified

7 May 2021