What are some tips in getting a corridor imported into Siteworks? Some of the guys at work tried importing a VCL with no luck of seeing the actual corridor.
The corridor has to be Made from instructions not surfaces for it to work like a corridor in Siteworks.
Alignment plus surface or corridor made from surface instructions works the same way- you can get station offset and elevation but no feature staking because the model is slicing the triangles not the features of the road.
Alan
Is there an available emulator for SiteWrork?
How well clean up does the VCL need to be or any at all?
is there a road module to this? just like Trimble Access does.
Francisco, the easiest way I’ve gotten a Corridor exported for either SCS or Siteworks would be to setup a jobsite in TBC.
If you go to RPS-Field Data - Jobsites and create a jobsite. Ensure that you have all of the data needed in the jobsite setup. Here you would Create a new site and select any controllers you would like added to the site. Once you accept this you are taken to the Jobsite Manager. Here is were you need to input the needed information for the Project. Site Calibration ( if you are going to be using GPS for this project this is paramount ) Control points ( this in your DC will be the control points used in the project ) Site map ( this will be the Site map in the DC, IE only for visual reference and not something that can be selected ) as well an any Avoidance Zones for Machine Control.
All of that being followed, your JobSite will be created. Now you can create your Design. Under RPS - Field Date - Create Design under the Design Group. Here you can select what type of 3D date you will be using. You have Surface, Alignment, Road Surface, 3D Linework and Material layer to choose from. For a Corridor you would select Road Surface and select the Corridor surface you want to export to the field. You do have the ability to choose Road Surface and " Mash " together a TTM and an alignment to get a “Dummy” Corridor but without the ability to use the Nodes that are created in an actual Corridor surface. Once you have the 3D portion selected, hit OK and then you can pick any Stakeout Points as well as your Design map. Keep in mind that your Site Map that is created in the Jobsite creation can not be selected for any type of stakeout. This is like a picture where nothing in selectable which can confuse your field techs. Anything in the Design Map that is selected here CAN be selected for staking. Once this is done you need to ensure you have the proper controllers selected for the design to be loaded to.
When these steps are followed, your files will be under the C drive - Trimble Synchronizer Data and under the controllers you created for this project. Keep in mind that a Machine can only be attached to 1 project at a time. The way that I’ve gotten around this in the past is to create a controller for GCS and PCS per Jobsite. For Example if your site is Hillside, you would create a controller for Hillside GCS and Hillside PCS.
All of this being said, you have one place to create a design that will give all controllers the same data with the same name created in one step. No more exporting GCS data for Dozers and Graders, then PCS data for Pavers then a DXF, CSV and TTM Survey crews.
It’s a lot to take in so if you have any questions about this give me a call and I’ll walk you through it.
1 Like
very detailed write-up. these new software are having less and less tools in them. I did the design as mention the other day and how to push some buttons to get the stationing.
which software does everyone prefer - Trimble Access or Sitework?
I thought i still had a loader for this, as I cant find:
https://go2.trimble.com/2020-10-12-CEC-DL-SiteworksEmulator_LandingPage-FormGate.html
If you fill out the form, you will get a link at some point to download. I go to my sitech rep and have them send me the loader. It tends to be quicker.
I am refusing to use vcl’s until end of next year. I spent the fall/winter of 2021 fighting everything about the new work-flow/files. Major stake-out workflows where broke or missing. I still use the scs workflow and push .pro/dxf/csv to the controllers running siteworks. we have been doing this worry free. After Trimble spends some time working out the bugs, we will try vcl’s again.
3 Likes
I was hoping to do the same until we added about four TSC5s to the fleet - they won’t load .pro files :(.
rumor has it that TSC5’s won’t run the roading module due to the android base.
if this is true, good to know now as we may plan on ordering some TSC5 soon. so, will for sure ask this question.
This was relayed to me from my sitech rep. I have done no further investigation - this was deal breaker for me. And I am partial to the TSC7…the TCD600 is also a no-go due to android
As I am new to pushing out design front TBC to Worksmanager. I have found how to push the designs as VCL. As I tried to look at those design in my Siteworks emulator. The emulator did not recognize those VCL design. Fall back was to dump those design into. Empty TBC project. Any use VCL to Sitework? If so, are you able to view those in the Siteworks emulator?
I am not sure as to the work-flow you are using to get the design into the proper folder. But here is this:
When creating a design in the works portion of field data tab, the design goes to: C:\Trimble Synchronizer Data\WorksManager by default. If you navigate to this folder you should find a list of projects and inside those, your Works Files. In the design folder will be a single file with the design name. Copy this to the scs900 folder: C:\Trimble Synchronizer Data\PC\Trimble SCS900 Data. You will need a site and the appropriate folders. In the design folder create another with the design name and paste the file here.
The design will populate under the associated project.
You should be able to copy the entirety of the works project folder and paste it into the scs900 folder but I haven’t played with that. When you create the works project from TBC it saves the uploaded files and designs to the works folder. Legacy workflows go to the scs900 folder but the Controller software looks specifically at the scs900 folder. So if you are wanting to QC the design you have to go hunting
you should get something like this in the emulator(this is user defined model)
as an aside, generally I use the legacy workflow and then upload to Works from the web ui. This keeps all my designs in the same spot. and as prior stated, we are not fully adopting vcl’s quite yet. I would say better than 90% of our designs go out as .pro/dxf still. If I can smash a bunch of material surfaces into a vcl, I will. But mostly run the .pro’s