Last time I tested, it does not remote other surfaces. I did a really detailed post on the Cleanup VCL Exporter. I'll try to find it.
Original Message:
Sent: 06-19-2023 09:02
From: Ed Levandoski
Subject: VCL file to machine control
If using the "Job SIte" method for exporting design files, there is an option to "Cleanup VCL file". By default it is set to no, but if you change it to yes, it says it will remove dependent objects included in the VCL file (See picture).
It is my understanding that this will remove the dependent surfaces that are unwanted in the final VCL going out to devices. I have not tested this, but I believe this was implemented when there were reports of very large VCL files that were being exported out of TBC using Export > VCL Project Link exporter
------------------------------
Ed Levandoski
Original Message:
Sent: 06-19-2023 04:23
From: Adam Bower
Subject: VCL file to machine control
This is a good tip. I used to do this but I don't like the idea of there being a locked surface in one of our files. I want the only surface to be live and change when we change anything. A big reason for this is that we use a collaborative approach to building models so multiple guys' can be in one model throughout its lifetime. This isn't normal though. Yeah, I could do the 0' offset before every time I need to export, that would probably be easier
------------------------------
Adam Bower
Original Message:
Sent: 06-19-2023 00:18
From: Matthew Pitt
Subject: VCL file to machine control
Little life hack I use.
TBC brings in dependant entities for surfaces (eg. if your surface is made of multiple other surfaces all of those will be exported to earthworks.) Offset your surface by 0.000mm and all of a sudden you have a surface with no dependant entities that can be exported to Earthworks by itself.
Matt
------------------------------
Matthew Pitt
Original Message:
Sent: 06-17-2023 12:57
From: Adam Bower
Subject: VCL file to machine control
Another HUGE concern is that when you publish a surface that has for example, a surface tie to OG, it will bring both surfaces in which is not good with how large OG surfaces can be. Also, if you're like us and you add multiple surfaces to one big surface with boundaries, it will bring every surface in that is referenced to the main one. I don't like the built in exporters at all.
------------------------------
Adam Bower
Original Message:
Sent: 06-15-2023 05:02
From: Lasse Hanberg
Subject: VCL file to machine control
You can push the VCL directly to Trimble WorksManager using the Construction Tab - you just need to create the project on worksmanager.com first.
Then in TBC hit "WorksManager-project" and "Create WorksManager-design".
Swap the model-type to "User defined" and simply select all the linework, including multiple surfaces, and push "Publish". This will generate both VCL for Earthworks/Siteworks, and SVD+SVL for GCS900 machines and upload them to WorksManager where they get pushed to the machines.
Only issues we are coming across is missing CAD-text in Earthworks, but surfaces and layers come through just fine.
------------------------------
Lasse Hanberg
Original Message:
Sent: 06-08-2023 05:05
From: Tom Silicato
Subject: VCL file to machine control
Adam, thanks for getting back. Since I am using TBC V5.80, I do see the construction Data tab which has a sub tab called Works Manager. In that tab there is button "Field Data to USB". I will gives this a try. Thanks
------------------------------
Tom Silicato
Corrado Construction
New Castle, Delaware
tsilicato@corrado.com
www.corradoconstruction.com
Original Message:
Sent: 06-07-2023 06:21
From: Adam Bower
Subject: VCL file to machine control
So Trimble has a built in method to create the VCLs for Siteworks and Earthworks. It doesn't work with the method of how we build models so I don't use it. The problem you're going to run into is that when you use that method in your project file, it's going to grab a bunch of objects that aren't supported by Siteworks or Earthworks. Let me save you a headache with using VCLs. I wish Trimble would create a command that utilizes the same methods I do to create the Siteworks/Earthworks VCL.
If you're not using the Field Data tab to create your project/design in TBC, you need to learn that and start using it. It's pretty straightforward once you do it a few times. Create your designs as you normally would in Field Data. Then open a blank TBC file and drag in the DXF/TTM/CSV file into that blank TBC file. Run "Convert to Linestring" on all the linework. Then turn everything on including the surface/surfaces (VCL supports multiple surfaces) and then run your normal export to VCL like you show in the screenshot.
That is the best foolproof way of exporting a VCL. When we build subdivisions for example, we add multiple corridor surfaces and lines to the finish design surface in TBC. If you do any of the VCL exports, including the one Trimble created specifically for the machine file VCLs, it will bring in every other surface used to create the finish design surface which we don't want in the machines. That's why you have to use your TTM in a blank file to create that VCL. I wish Trimble would come up with a way to do this in TBC. It's a simple work around but annoying to do.
------------------------------
Adam Bower
Original Message:
Sent: 06-06-2023 08:36
From: Tom Silicato
Subject: VCL file to machine control
I am trying to find a way to create a file for our machine control that allows an operator to turn layers on and off. I was told some time ago that a VCL file exported out of Business Center (highlighted in pic below) will allow an machine operator to do that. I do see in the export command that there is a way to export to a VCL but what should I select to export? Do I include the surface as well? How about calibration? Right now I export to GCS900 file and then use file flipper to create an Earthworks file in a ProjectLibrary folder.
------------------------------
Tom Silicato
Corrado Construction
New Castle, Delaware
tsilicato@corrado.com
www.corradoconstruction.com
------------------------------