Trying to import a .jxl to TBC. The .jxl contains traverse data and scan data. Currently on TBC v5.52.
Things I've tried:
Installed TBC updates
Imported file to blank TBC project
Find/Replace ALL 'PointRecord' instances from file that DOES import
Turned on "all symbols" in Notepad++ and did a visual search for anomalies
Used the .job to create a "fresh" .jxl
I get the same error from the .job and .jxl. The PC included a .dc file which imports without issue but doesn't bring in the scan data.
Any help is appreciated! Thanks!
TN
Also tried opening the same file on a newer version of TBC (v5.7) with the same result.
If you're on v5.52, the crew may be running with a later version of Access that is not compatible. Usually the major updates of TBC coincide with an Access update so you might be a few versions behind.
I'd get the crew to export an earlier JXL version, maybe 6.20, and see if that imports correctly.
Just remembered something I have seen only once before.
Somehow a crew managed to record a GNSS observation that has no ECEFDeltas or ECEF records in the PointRecord entity. Which means that it is impossible to compute that point.
It was a while back but the error message sounds familiar.
You might want to make another sweep of the PointRecords and check if any are missing that critical info.
I have no idea how it happened, because it should have thrown an error in Access as well.
This is EXACTLY what happened! The file now imports without issue.
Wow...Hadn't seen that one before!
@rover83 I have seen issues when a crew is in a scale 1.0000 only job and launch the vrs survey style get no coords and then realize something is wrong and get frustrated and just set robot up in that same scale job. Has a random vector from vrs base took me a minute to figure that on out Another reason to keep everything grid on datum as they swap everything all the time at a previous company.
I'm having the same issue, but am not very familiar with Trimble data to determine if I'm missing the ECEF info. Would someone mind analyzing a piece of the .jxl code to tell me if it looks like anything is missing? Here's a sample of the PointRecord info from my .jxl file:
<PointRecord ID="000001a2" TimeStamp="2023-11-13T11:46:52">
<Name>111301</Name>
<C.o.d.e.>MAG</C.o.d.e.>
<Method>GpsStaticObservation</Method>
<SurveyMethod>RTK</SurveyMethod>
<Classification>Normal</Classification>
<Deleted>false</Deleted>
<ComputedGrid>
<North>64637.298015368</North>
<East>86760.632446507</East>
<Elevation>419.55127843729</Elevation>
</ComputedGrid>
<Precision>
<Horizontal>0.00734204296562</Horizontal>
<Vertical>0.01195278484374</Vertical>
</Precision>
<QualityControl1>
<NumberOfSatellites>20</NumberOfSatellites>
<RelativeDOPs>false</RelativeDOPs>
<PDOP>1.4637444019318</PDOP>
<GDOP>2.13862271373</GDOP>
<HDOP>0.6438227891922</HDOP>
<VDOP>1.3145493268967</VDOP>
<NumberOfPositionsUsed>20</NumberOfPositionsUsed>
<HorizontalStandardDeviation/>
<VerticalStandardDeviation/>
<StartTime>
<GPSWeek>2288</GPSWeek>
<Seconds>157610</Seconds>
</StartTime>
<EndTime>
<GPSWeek>2288</GPSWeek>
<Seconds>157629</Seconds>
</EndTime>
<MonitorStatus>NotMonitored</MonitorStatus>
<RTCMAge>1.7999999523163</RTCMAge>
<Warnings>
<ExcessTiltWarning>NotCalibrated</ExcessTiltWarning>
<ExcessTiltAtStorage>NotCalibrated</ExcessTiltAtStorage>
<ExcessMovementWarning>No</ExcessMovementWarning>
<ExcessMovementAtStorage>No</ExcessMovementAtStorage>
<PoorPrecisionsWarning>No</PoorPrecisionsWarning>
<PoorPrecisionsAtStorage>No</PoorPrecisionsAtStorage>
</Warnings>
</QualityControl1>
<QualityControl2>
<NumberOfSatellites>20</NumberOfSatellites>
<ErrorScale/>
<VCVxx>0.00003773673961</VCVxx>
<VCVxy>0.00002885392314</VCVxy>
<VCVxz>-0.00002699793367</VCVxz>
<VCVyy>0.00006399014819</VCVyy>
<VCVyz>-0.00004789939339</VCVyz>
<VCVzz>0.00009504777699</VCVzz>
<UnitVariance>1</UnitVariance>
</QualityControl2>
</PointRecord>
I have minimal experience with JXL files, but I looked at one I dealt with recently for comparison, and I see that the typical PointRecord in my file has the following between the Deleted record and the ComputedGrid record:
<Deleted>false</Deleted>
<Source>Search Pts Epoch 2017-50.job</Source>
<ECEFDeltas>
<DeltaX>8959.5936727142</DeltaX>
<DeltaY>-8874.7327793888</DeltaY>
<DeltaZ>-2950.7649638909</DeltaZ>
</ECEFDeltas>
<ReferenceRecordID>00000069</ReferenceRecordID>
<RTK_Base>RTCM0476</RTK_Base>
<AntennaID>00000071</AntennaID>
<ComputedGrid>
FWIW.
Thanks Mr. Frame! Now I just have to figure out why that part is missing and how to get it...
This usually happens on export to JXL.
You can either export to an earlier JXL version (try something like 6.20) and try importing that, or you can simply import the JOB file, which usually works when the JXL does not.
Thanks Rover83, that did the trick. I picked a different jxl version and all was fine, no more error.
