Index error during import or export

Problem

When importing or exporting images in Trimble Business Center, an error occurs:

[project path] The TMI import was unsuccessful, index was out of range.

or

Error exporting TMI database [project path] index was outside the bounds of the array.

Solution

Solution 1:

Open the TRIDB with any SQL explorer and verify that:

  • The MissionInfo table includes all the timestamps of mission start and end.
  • The Run table includes all the timestamps of the runs start and end and covered distance.
  • The Run table includes healthy and long runs. Any run that is shorter than 0.2 kilometers in covered distance can be considered corrupt and removed. Make sure you also remove it from the RunDeviceData table and the RunGraph.
  • Make sure RunIDs and GUIDs are matching and correct.

Solution 2:

The SBET file needs to be reprocessed to make sure it is covering every and all the runs. Proposed workflows in POSPac to ensure the SBET is complete:

  • Modify the POSPac mission so that the SBET starts earlier than the first Event1, e.g.:
    1. Try a different initialization mode in POSPac.
    2. Make sure the lever arms st. dev. Is set to <3 cm.
    3. Make sure that base station data covers the whole mission.
    4. Make sure the DMI lever arms, the scale factor as well as the sign of the scale factor is correctly set.
  • Remove the first images not covered by the SBET:
    1. Identify how many event1 are outside of the SBET.
    2. Open the first *.sync file from Camera_1.
    3. Delete as many lines as there are event1 outside of the SBET.

TIP – To avoid this error in future, make sure that the system operator always logs (static) data for at least 2 minutes after the last run has been finished.

Problem Details

This issue can be caused by some problems in the tridb file. Also it is highly likely that the SBET file being loaded with the mission does not cover all the imported runs.

The mission was stopped (and the system shut down) by the operator only a few seconds after the recording of the last run was stopped. This should be avoided by any means because it can result in the real-time solution stopping a few seconds BEFORE the last run was stopped by the operator.

This is possible because the nav files are downloaded in packages from the Applanix POS memory. If the time interval between the run stop and the mission stop is too short, it can result in the last package of nav files not being completely generated respectively transmitted.

Even if this case would be avoided by the TMI software (which is not the case in the current version 1.4.3), this workflow in the field would most likely anyway cause the same problem later during post-processing, because the resulting SBET is almost always a bit shorter than the real-time solution since a few epochs are truncated at the beginning and at the end of the mission. This is something that the algorithm in POSPac is doing automatically, the user cannot really influence this during the data capture (except for considering the known factors such as using DMI+GAMS, doing a proper mission planning, avoiding bad GNSS environments as much as possible, etc.)

The only way to make such a run usable again would be to cut the last few entries from the .sync file and also delete the last couple of images, so the run is fully covered by the SBET.

Related Products

Trimble Business Center, MX7

Support Reference

None

Last modified

September 2020