Yes we are using on Data controllers but not for common sync method. Dont currently use Siteworks, only Access.
I like getting data off controllers via TSM (you are correct there are some great inbuilt sync functions) however getting design data onto data controllers isn't compatible with my workflow. Also have had some sync issues where the TSM causes a Project duplication in TA which takes time to resolve (you have to copy the ProjectInformation.xml file from the duplicated project back to the original project). TSM can also be very slow when you have multiple users on a large project.
Connect also tracks all changes made to the project via the Activity tab which is invaluable for traceability.
Original Message:
Sent: 10-11-2023 15:54
From: Chay Froggatt
Subject: Feature Request - 12da in Trimble Sync Manager
Hello Both,
Trimble Access does have inbuilt sync functions which are more integrated than Connect Sync.
Edward,
Are you using Connect Sync on the data controllers to ensure a common sync method for both Siteworks and Trimble Access devices or is there something missing from the Trimble Access feature set?
------------------------------
Chay Froggatt
Original Message:
Sent: 10-11-2023 14:13
From: Edward George
Subject: Feature Request - 12da in Trimble Sync Manager
Ah ok. That does make it hard to track as staked info.
I have been moving away from the TSM and to Trimble connect. Has been more stable and much faster on large projects. I have found it behaves more like one drive in that you can nominate a one-way sync so that field crews can't delete or change the field files required - Just log in in to Trimble connect sync on the TSC7 and automatically get all office changes (download only has to be selected in Trimble Connect Sync).

------------------------------
Edward George
Original Message:
Sent: 10-10-2023 20:30
From: Peter Batson
Subject: Feature Request - 12da in Trimble Sync Manager
thanks Edward,
I've been using this for exporting 3d shapes like structures and pits and pipe. the only thing I don't like is it renames all entities to TRB0000 as you select in TA and shows on the as-staked info. so its hard to look back at what was actual staked out. i was looking for the automation from using TSM with the cappabilites of the 12da (which is already handled in TA).
thanks
------------------------------
Peter Batson
Original Message:
Sent: 10-10-2023 16:58
From: Edward George
Subject: Feature Request - 12da in Trimble Sync Manager
Hi Peter,
Have you tried the .trb (Trimble BIM) export from TBC? Its hidden under the Export → Construction Tab → Site Vision AR Exporter.

Seem to work well getting 12d and TBC attributes back into Access. We have been using this for the purpose of getting asbuilt attributes back out into the field for stakeout:

Seems to work well for line names / layers / arcs / circles however doesn't seem to work for surfaces / alignments yet (try .xml / .ttm / 12da for that).
Dont think you will ever get a 12da as a reference file. Reference file command is for sharing between TBC (.vce) files - similar to how Terramodel works.
Alternatively, you can just drag and drop a 12da/12daz directly into TBC very easily!
Hope this helps.
Ed
------------------------------
Edward George
Original Message:
Sent: 10-09-2023 19:40
From: Peter Batson
Subject: Feature Request - 12da in Trimble Sync Manager
Could someone please look at adding 12da files to the referenced project files.
And is there any reason why Trimble Access Doesn't use a Trimble native file like VCL? It would be good to have one file that supports lines, circle, alignments, surfaces, points, attributes but retains name and layering.
thanks, in advance.
------------------------------
Peter Batson
------------------------------