-
TBC JXL Import Failure
I’m working with a colleague to process some of their Trimble data, but when I try to import the JXL into TBC (my version isn’t current, it’s v5.52 if that matters) I get an error message “Value cannot be null. Parameter name: source” and the import fails.
I’ve attached the file is anyone wants to try it, but you’ll have to change the extension from txt to jxl (the board doesn’t accept jxl as an attachment).
This file was truncated for preview. Please download to view the full file. -
7 Replies
-
There a couple of possibilities for the error given the respective versions of JXL and TBC, but in my experience this is usually related to a prior TBC update not finishing/completing the install of all components…or it could simply be that Access is more up to date than TBC by enough to make them incompatible. There have been a few additional items added to JXLs that newer versions of TBC can read, but older versions cannot.
I would either:
1. Uninstall TBC, run the cleanup tool, (exe is on that link near the bottom) and then reinstall (or preferably upgrade to current version)
or
2. Have your colleague export an earlier version of JXL (probably 6.20 or so) out of Access and see if that imports OK.
“…people will come to love their oppression, to adore the technologies that undo their capacities to think.” -Neil Postman -
It imports no problem into TBC 5.90
I can export into any older version of jxl, let me know what you need.
-
I don’t know what version my copy of TBC can read, but rover83 thinks that 6.20 will work. Shall we give it a try?
-
I did get a v6.20 jxl from my colleague, and it came into my copy of TBC without issue. Unfortunately, it only contains RTK vectors and coordinates. I’d like to get raw observation data (i.e. .dat or .t02) as well going forward. How does he have to set up Access so that it records that?
-
JXLs do not contain static or PPK logging data files – those are always stored in the receiver (or possibly on the controller if someone really likes not being able to use their controller when running static sessions).
When a JXL is exported out of Access, if there are any ancillary files (linked CSVs or DXFs, images tagged to points in the job, scan data from the SX series, etc.) being used, they are exported to a folder with the exact same name as the JXL, in the same location as the JXL. If the operator is actually starting their static sessions with the correct job file open, and downloading them to their controller from the receiver afterwards, those static files will also be in that associated folder.
Then when a JXL is imported to TBC, it will automatically look for that folder, and then pull in associated images and static files if it finds them.
You can always drag and drop T02/T04 files to TBC like usual, but the bottom line is that they are not integrated into the JXL (XML) data format.
(Edit: I should also note that if you are looking for static data from an RTK base receiver, make sure that they know to set their survey style so that the base is on “RTK + Logging” rather than just “RTK”. That will also be logged to the receiver, just like a standard static file, and will be associated with the job too.)
“…people will come to love their oppression, to adore the technologies that undo their capacities to think.” -Neil Postman -
Thanks for that, I’ll pass it along and see what he’s got!
-
File imports into TBC v5.81 without issue
T. Nelson – SAM, LLC
Log in to reply.