How do I setup field to finish in the field with the tsc3?
I’m trying to get my boss to upgrade to at least a tsc5 or tsc7.
You will need to set up a feature library (FXL) and reference that in your job properties
It details point symbols, colours, linetypes etc to say how you want to draw
Trimble provide a sample one, GlobalFeatures.FXL, that you can modify to suit
There is a free tool, Feature Definition Manager (FDM) tool that comes with TBC or that can be downloaded from https://help.fieldsystems.trimble.com/tbc/downloads-software.htm
There are a good number of Youtube videos around Feature Libraries that you may wish to explore
I'm thinking that your time would be better spent setting up F2f in C3d or Carlson or whatever office CAD software your company uses.
jimcox has the right idea. Field coding is extremely helpful for crews to keep track of what they've located and fill in any gaps. Many PLSs and PMs myopically think of F2F only as a way to decrease CAD time. It's possible that the version of Trimble Access on your TSC3 will allow you to manually create field codes, but ten years ago when I was using the TSC3 you did not have that option.
1. Download a copy of Trimble's Feature Definition Manager (free) https://help.fieldsystems.trimble.com/tbc/downloads-software.htm
2. Create point codes and field codes. How you code is largely a function of how big your company is. A small firm can have more flexibility than a large firm. Make sure you involve the CAD department as they'll need to create Description Keys within C3D.
3. Verify your Line Control Codes - B = Begin; CLO = Close; BSC = Begin Smooth Curve; PC = Begin Tangential Curve etc..
4. Transfer the resulting .fxl to the TSC3. Place it in the same folder as your Geoid: Trimble Data>>System Files
Having created feature codes for older field hands who refused to learn anything about computers and were generally pessimistic about the whole process, I learned that in a medium to small sized firm there's no reason not to create multiple codes for the same feature. Instead of fighting the guy that keeps coding utility poles as PP (power pole), just make two codes, UP and PP. Similar on the back end. You can have enter thousands of Description Keys reflecting nearly all variations of your codes. I'm in the business of preventing blunders and one way to do this with field coding is to note codes that are commonly transposed such as IPF (iron pipe found). After seeing it listed as IFP a few times, I added a IFP to the Description Keys but made the marker obnoxiously large so I'd notice it and correct it. Obviously, this is not to replace any other QA/QC but it's an example of something free and easy that can be done to increase your chances of not missing something. Expect human fallibility and you'll avoid disappointment.
@murphy Having multiple codes for the same item is genius. That will solve so many problems of people entering the intuitive code instead of the legitimate one. Just make them all legitimate as long as they aren't already used for some thing else. Thanks Murphy.
I don't know why but we were stuck on one code for 1 item when that is nothing but a self imposed restriction.
Many PLSs and PMs myopically think of F2F only as a way to decrease CAD time.
I think of F2f as primarily quality control. CAD speed is a side benefit. Nevertheless, I believe that dealing with drawing elements on a 3 1/2" screen is a tough way to go.
How do I setup field to finish in the field with the tsc3?
The same way you would for any TA device, creating a FXL file. I exported my civil 3d description key for a place to begin creating the FXL. Though it will probably slow down the device operation since the TSC3 CPU is so slow and the device has been discontinued 9 years ago and product was launched 15 years ago. Who would buy or use a 15 year old mobile computer? That's what the TSC3 is.