I do quite a bit of scanning with the Trimble SX12 and the TSC7 on a mine site, and myself, my cross-shift, and another crew on another site (with SX10) have all experienced the same persistent issue.
About 50% of the time, once the scan is completed, an error prompt is generated saying the saving of the scan has failed, database could not be created (or wording very similar to that anyway), and of course, the scan doesn't save.
We scan some pretty big areas (although small areas can have the same issue), and it's a pain to sit through a 30 or 40 minute scan just to do it all over again.
If a scan does fail to save, shutting down Trimble Access and restarting works 100% of the time, so our field-fix work around is to initially run a quick "burner scan", something in the 10-30 second range,?ÿ so that when it inevitably fails not a lot of time is wasted.
This happens with both older and the newest releases of Access, across two pieces of equipment, on two very different sites. Updating the firmware on the gun (even just reinstalling the most recent) helps for a bit, but isn't a permanent fix.
Anyone else experience this issue regularly? Not sure if it's a common bug, or perhaps there's an issue with our file paths? Would really love to find a solution for this, especially for training purposes. It's a bit cumbersome to explain to a new person how to do the scan, but don't worry it just mysteriously crashes sometimes, just start over no big deal...
?ÿ
I should note that the other crew reports that they do not experience this issue with their TSC5s, which I do not have on hand to try.
Damn, typed out a response and then somehow the webpage reloaded and deleted it. (very apropos, given your issue)
Basically I wanted to suggest using the cable with the 5pin(?) connector, which would assure no data loss during the transmission. If that fixes the issue, your Wi-Fi signal is probably getting stepped on - not sure what to do in that case other than use the cable.
If the cable doesn’t fix it, I’d make quadruple sure that I did a successful firmware update for the SX12 using Trimble Installation Manager on my desktop, and a successful update on the TSC7 using the TSC7’s windows updater.
That said, I’m pretty sure certain updates in the not too distant past actually cause new issues, but our office just did the most recent update last week and aren’t having any issues. (However we aren’t using any of ACCES’s mining utilities)
Big things to do:
On the TSC 7
Disable hibernation. Period.
That will free up as much as 50% of your remaining storage.
also clean the junk Install files from Windows. usually several gigs.
Dont store anything else you scan or take photos on the device. offload to thumb drive and keep it clean.
it's only got a 64G static ram drive that's being used with win10.
it's the only real fatal flaw I found. Had those same scan failures.
these steps fixed it and never saw them again.
Also:
Don't use this for multiple use profiles, aka windows user profiles for network and email. it's a POS as a computer, but a great data collection tool.
Being a former IT Administrator, I was the person who spoke up in the face of the argument that its a potential IT threat...it's on a cell phone connection and never needs to be inside any network ever.
Set it up for one super user (admin) for the updates needed as the software evolution occurs, and a limited access user id to be used in the field and not allowed to add crap like email and TikTok Facebook etc.
let me know what you find.
Prove me wrong.
I do quite a bit of scanning with the Trimble SX12 and the TSC7 on a mine site, and myself, my cross-shift, and another crew on another site (with SX10) have all experienced the same persistent issue.
About 50% of the time, once the scan is completed, an error prompt is generated saying the saving of the scan has failed, database could not be created (or wording very similar to that anyway), and of course, the scan doesn't save.
That sounds like a comms problems to me. Do try using a cable...
Would be good to know the exact text of that error message - will help nail the problem location down.
Is your TSC7 all current with Windows and OS updates?
I've just had a quick chat with some of the techs - they had two comments. Firstly disk space - you need lots. Secondly that error rate is way too high, plus lost data is bad, very bad. Suggest you contact your dealer and get a support case raised.
and just to make sure, when scanning, I just leave the box at the tripod base, with the tsc7 on it. the cable was a persistent issue with one of my coworkers whom didnt understand that both the tsc7 and the sx10/12 in wifi not blue tooth worked well. in fact I refused to use the cable because it's not as fast.
never had an issue.
prove me wrong too.
Thanks everybody! Lots of things to try out, but I suspect it has a lot to due with the amount of files being stored on the data collector. It's maybe not best practice, but it is how the site works.
I use the sx12 quite a bit. We were having a similar issue. What we did where I work to complement the large file size from scanning is we got a 500GB SD card. We had our IT department move trimble access to the sd card. So, now all projects in access are now saved to the SD card in our TSC7. In the file explorer, it comes up as the D drive. After exporting the job files, it asks if you want to eject the sd card or not. We either eject it and put into our computer and download the file or use a portable solid state drive and plug it into the TSC7 and just copy the project and it's files over to it then upload to the computer. Maybe this will help. We found before doing this that we could only do one to two days of scanning and the memory was full on the TSC7 and crashing it. Switching to working from the SD card gave us the ability to do a large scanning projects and not having to download the project until we were done.
It's kind of ridiculous that they thought 64gb was enough. My old machine had 256gb plus an SD card slot.
Did you notice any difference in speed using the SD card? The other bonus would be if the tsc7 fails you are potentially saving a lot of data that could have been lost.
I usually download to the server remotely as soon as I finish a job in fear that the data collector will fail and I'll have to redo something.
Re-install Access fixed that issue for me, along with using cable for data and keeping things clean.
