Corrupt clips error during import

Problem

When importing a tridb file in Trimble Business Center, an error occurs:

Importing TMI contains corrupted clips. Some stations may be not imported.

Solution 1:

Try one of the following and see if it works

Try to increase the SBET length, for example by using GAMS and/or changing the initialization mode.
Remove the sync entries and .pgr frames that are not covered by the SBET.
Import without SBET.

Solution 2:

Look at the GPS time in the .tridb or the sync file to identify the last run before midnight (let’s say it’s run 10).
Make a tridb containing all the runs before this run (for example, runs 0–9).
Make a separate .tridb containing only the midnight run (for example, run 10).
Make a separate .tridb containing all the runs after this run (for example, runs 11–20).
Use Trimble Business Center 5.21 or later to import these .tridb separately as different missions.

Solution 3:

Make sure all the PGR files are in the camera folder.
Make sure the PGR stream contains the same number of frames than the associated sync files.

To see the number of frames in a PGR stream, you can open any pgr of the clip with LadybugCapPro. In the bottom you will see "Current Image : 0 / x" where x + 1 is the number of frames in the stream (e.g. if x = 100, there are 101 frames in the stream). To see the number of frames in a sync file, open it with a text editor and go to the last line. The first number of the last line + 1 is the number of frames (e.g. if the first number of the last line is 100, there are 101 frames in the sync file).

The SBET does not cover the whole mission. Or, the mission may span midnight GPS time, which is an issue with Trimble Business Center 5.20.

In addition, there could be fewer frames in the .pgr than in the .sync file.

Trimble Business Center, MX7

410965, SYMM-2310

September 2020