Trimble Business Center

Is anyone having issues with importing point clouds from the SX10 in TBC5.32? 

Importing the jxl into TBC it takes the same normal amount of time to import then collourize but there is nothing visable in TBC. Under the project manager you can enquire on the seperate scans and it says there are points within the point cloud but nothing shown. I got the same data and brought it into TBC 5.31 on another computer with no problems at all.

I have been in contact with the local Trimble reps in my area and they have the same issues. They were sighting that it might be something to do with the version of Access I am using (2020.01). I have updated this to 2020.10 but am yet to trial this with another scan.

Regards

Bevan

Hi Bevan,

since we just updated our Pointcloud Computer to V5.32 this morning we had a quick test in the office. We updated Access to the latest version first.

Dragging the JOB file into TBC we get an error that it can't convert the Job file. Obviously they forgot to update the conversion library of TBC.

So, we exported a JobXML out of Access and that one works in TBC V5.32 and we can see the point cloud.

Hi!

We have the same problem. When we import a job-file with scans included, all previously imported pointclouds disappears from the project. 

So, should we dowgrade to 5.3 again?? 

Im getting kind o tired of this. The update before this was a mess with the plotting so we had to downgrade and now we cant use pointclouds, ALL our projects contains pointclouds.

4 guys in the office putting hours in things that does not work, you do the math.....

All new versions have something better but they are half cooked. After 5.31 we decided only to upgrade on full number updates every six months because like this we are like test rats and my phone is constantly ringing.

Yep, Just did a scan with a SX10 today and exact same thing has happened. Brought the same data into another PC running 5.30 and no probs.

@Bevan Macdonald and all

I tired importing an SX10 point cloud job file from TA 2020.10 in TBC v5.32 (before and after running check for update in TBC to get the latest job file converters) and I am able to see my point cloud data with no problems. See image below.

Data below is the data I used for testing.

TBC 532 TEST.zip - Google Drive 

So far this seems to be data specific. However it is odd that multiple users are seeing the same issue. Please ensure that you have ran check for updates in TBC v5.32 to get the latest job file converters. If you are still seeing issue, can you please share your data so that our development team can investigate this issue?

Hi!

Here is a scan to test if you want. Transfer - Dropbox 

When we import this it seems to be working but there is no pointcloud visible after import, only points. All 4 guys in the office has the same problem. 

Also, when importing a new scan from the SX10 into a project with previous scans makes also those scans dissapear. Only .LAS file can be imported and working. 

Because we had huge problem with the plotting in 5.31 should we downgrade to 5.3?

The scan that I did was done from two different setups and did resections off known control points whereas the sample above seems to be have done from the one station using an arbitrary setup . Maybe an issue with multiple setups and/or resections.

Another one of surveyors did a regular feature survey earlier in the week with a S5 total station and TSC7 running Access with multiple resection setups and had a similar issue with no data appearing in 5.32.

TBC 5.32 seems to be having an issue with the station setup. So maybe it's not a scan thing, but just a total station setup/resection issue.

I've had issues with Resection data too from Access 2020.10 (all appears good in Access and Sync Mamager - Coordinates and data there) but then on import into TBC 5.32 it seems to be that is the problem (Resections),

I'm downgrading to 5.31 and will try that - as you say VERY frustrating

Yes it's a TBC 5.32 issue with Resections - I've just downgraded to TBC 5.31 (and using Access 2020.10) and imported this Survey through Sync Manager - Data uploads and processes OK.

I have raised the issue with product management on the Geospatial side of things as this is an issue for them to look at as it relates to the SX10 - I dont have any data for SX10 to test against unfortunately so I cannot validate either way - if you have an Access file set please share so I can test this for you to see what is happening.

Alan

Here is data that does not work. It looks like its importing it correctly But after import its just the measured points and no pointcloud. And If i try to import this data into a old project with earlier scans they will dissapear. 

Dropbox - 200904 - Simplify your life 

All

A bug has been entered regarding the issue and is currently being investigated. for a work around if you set the resection to 'Helmert Resection' for each station, the data will appear again (see image below).

Hey All.

Upgraded to Access 2020.10. Performed 4 resection setups for scan done this monring. Will try and bring it in normally and then with the above suggestions. Will keep you posted.

Cheers 

Bevan

Hey Adam.

I can right click on the setup and change to Helmert but it doesnt seem to change in the project explorer? You can close the properties pane then right click and view properties again and it comes up as Helmert but still shows resection in the project explorer. Any ideas?

Regards

Bevan

Hi Bevan, did you recompute the project after you change the setup type?

Hello TBC users,

Trimble Business Center v5.32 users are currently experiencing difficulties when importing all total station data in which a Standard Resection is used as a Station Setup. Data such as point clouds and total station vectors do not appear after import. Please review the attached Support Bulletin for more details. Apologies for any inconvenience this may have caused. 

Standard Resection Issues in v5.32 - Support bulletin.pdf - Google Drive 

It seems that 5.32 users are also experiencing trouble exporting as well.  At least I am... and we have a resection setup.

When I exported my surface, it disappeared from my vce drawing.  

When I tried to export my points to a CSV, only the Point Number and Description exported.  The N,E,Z columns were blank in my csv

Hi Katy,

I believe this is direct result of observations disappearing with standard resections. Unfortunately, I would suggest going back to 5.31 until we can provide a patch in the coming days. I want to send my most sincere apologies for the difficulties this has caused everyone. I share the same frustrations, and I'm optimistic we will have a solution for you and others soon. 

Thank you for your patience! 

Where can I get a copy of 5.31

If you are using drafting in TBC i would recommend 5.3 instead. In our office We have downgraded to 5.3. 

Hi Fredrik,

What's prohibiting you from drafting in more recent versions?

When we upgraded to 5.31 4 guys (all) in the Office  could not use drafting. Pointtables did not show and not imported pictures was some of the bugs. I think its a thread here in the forum about that. Last time TBC was running smoothly for us was 5.3 and the 2 updates after that have just made a mess for us. We are running 5.3 again. 

Hi Fredrik,

Sounds like there are several issues going on with drafting. Would you mind collecting some screenshots or descriptions for us to troubleshoot the issues? 

Thank you.

Rui

I think that is fixed already with the the update to 5.32 but then pointclouds from SX10 and some other stuff stopped working so we have all downgraded to 5.3 again. 

HUGE DRAFTING PROBLEM AFTER UPDATE TO 5.31 

We have just released a patch 5.32.1 to fix the SX10 point cloud issue. You may download it from Check for Updates, or from our home page: http://go2.trimble.com/downloadTBC.html 

Thanks, but i think we will wait with updates for some time to see that it works before we install it. This last 2 updates has been taking a lot of hours from us in the office and we dont have the time to work with problems and downgrading. I will use 5.3 and reading in the forum for a couple of weeks before updating