WorksManager

When will we be able to upload VCLs directly through the WorksManager interface?

When will we be able to upload VCLs directly through the WorksManager interface?

Let me give a little more context to the need for this. 

We run a fleet of TSC5s and need to use alignments are part of our designs. Up until Siteworks version 1.72, .PRO files weren't supported on Android which forces us to utilize VCL files. We're not spending the money and upgrading the software warranties just to be able to use PRO files. I also haven't been comfortable with the WM integration into TBC, so the only other way to get VCLs onto TSC5s is through the use of TCC. Doing it this way we lose the automatic version tracking and design push out that happens in WM, which has created some issues. 

When will we be able to upload VCLs directly through the WorksManager interface?

When will we be able to upload VCLs directly through the WorksManager interface?

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

Are you talking about the thing it does after loading some VCLs where the Job Setup window won't let you select the design for several minutes?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

This is from what i was told, that not to use the VCL as the machine did not like them.  So i tried it for the field crew data collector.  And somehow the machine tried to pick it up and the job Site would not load.  

Are you talking about the thing it does after loading some VCLs where the Job Setup window won't let you select the design for several minutes?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

This is from what i was told, that not to use the VCL as the machine did not like them.  So i tried it for the field crew data collector.  And somehow the machine tried to pick it up and the job Site would not load.  

Are you talking about the thing it does after loading some VCLs where the Job Setup window won't let you select the design for several minutes?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

We only use VCL files in both SW and WM created from TBC to WM work flow. Look at the cad objects in "advance select" and make sure that you convert or delete any leader lines, ellipses, blocks etc. before export. You may still get a linework error in EW on loading the file but it will still function. The only issue we had recently, is if you have a surface that is dependent on a very large tin model, it will not load in EW. I that case "offset surface"  vertically zero and the dependencies will be detached.

This is from what i was told, that not to use the VCL as the machine did not like them.  So i tried it for the field crew data collector.  And somehow the machine tried to pick it up and the job Site would not load.  

Are you talking about the thing it does after loading some VCLs where the Job Setup window won't let you select the design for several minutes?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

Your warning about too big surfaces can not be made loud enough.  If you happen to include a surface, either directly or by reference, that causes the vcl file to exceed 150 MB and you send that to WorksManager you will instantly brick all the EC520s connected to your network at that time.  The size limit is not exactly 150 MB, but somewhere between 150 and 600 MB.  150MB is what they tell me is safe.  There will be no warning before it happens.  You will have to replace every unit that was connected.  This is a built in flaw that Trimble is aware of, and is one of the many things they claim to be working on fixing.

We only use VCL files in both SW and WM created from TBC to WM work flow. Look at the cad objects in "advance select" and make sure that you convert or delete any leader lines, ellipses, blocks etc. before export. You may still get a linework error in EW on loading the file but it will still function. The only issue we had recently, is if you have a surface that is dependent on a very large tin model, it will not load in EW. I that case "offset surface"  vertically zero and the dependencies will be detached.

This is from what i was told, that not to use the VCL as the machine did not like them.  So i tried it for the field crew data collector.  And somehow the machine tried to pick it up and the job Site would not load.  

Are you talking about the thing it does after loading some VCLs where the Job Setup window won't let you select the design for several minutes?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

Good afternoon,

I've published two VCL designs today, but the LW isn't pushing over-only the surface. I've been pushing VCLs for a while now and can't figure out what's going on.

Is anyone else running into this issue? The LW shows up in the WM viewer, but the tablet only receives the surface!

 

Your warning about too big surfaces can not be made loud enough.  If you happen to include a surface, either directly or by reference, that causes the vcl file to exceed 150 MB and you send that to WorksManager you will instantly brick all the EC520s connected to your network at that time.  The size limit is not exactly 150 MB, but somewhere between 150 and 600 MB.  150MB is what they tell me is safe.  There will be no warning before it happens.  You will have to replace every unit that was connected.  This is a built in flaw that Trimble is aware of, and is one of the many things they claim to be working on fixing.

We only use VCL files in both SW and WM created from TBC to WM work flow. Look at the cad objects in "advance select" and make sure that you convert or delete any leader lines, ellipses, blocks etc. before export. You may still get a linework error in EW on loading the file but it will still function. The only issue we had recently, is if you have a surface that is dependent on a very large tin model, it will not load in EW. I that case "offset surface"  vertically zero and the dependencies will be detached.

This is from what i was told, that not to use the VCL as the machine did not like them.  So i tried it for the field crew data collector.  And somehow the machine tried to pick it up and the job Site would not load.  

Are you talking about the thing it does after loading some VCLs where the Job Setup window won't let you select the design for several minutes?

Has the VCL option been fixed for the machine control?  There has been issue where it will freeze up the Site and not let you open the Site.  I have even run into the issue where I had a VCL for the data collectors and it affect the machine control Site.  We had to remove the design from the TCC files.  

Michael, Wayne is correct. Instead of selecting "surface" on your design export from TBC, use the "User Defined " option, pick your surfaces from the Project explorer tab. All of the surfaces will be in VCL and multiple surfaces will be available on earthworks machines.

Thanks, Tom

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

I so agree!!  Having to load the VCL's manually is ridiculous.

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

We have haven't had any problems unless you have non supported objects in the model. Send me a file and i can let you know if i see something.

Tom

I so agree!!  Having to load the VCL's manually is ridiculous.

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?

We have haven't had any problems unless you have non supported objects in the model. Send me a file and i can let you know if i see something.

Tom

I so agree!!  Having to load the VCL's manually is ridiculous.

I've been getting frustrated with this lately. It's convenient that WM can synchronize devices over the air, but without VCLs it's getting to be rather pointless. We use VCLs for our devices because they can hold more than one surface. An operator running Earthworks can select which surface they are working on within the same design. This helps save the design list from becoming 50 items long, which keeps us sane because we're not getting calls from Dozer operators all day saying they can't find the design they're supposed to be using. WM does not support this multi-surface functionality, but it really needs to. If we have to go out in person to these machines and upload each one anyway, there's not much reason to continue using this service.

When will we be able to upload VCLs directly through the WorksManager interface?