The TDC600 is the bomb. Light, almost nothing on the pole, fast, I thought I would miss the hard keys, but I don't. Often I don't even clamp it on the pole, simply carry it in one hand as I take a shot. It's fast and way better in sunlight than the TSC3
The only downside to that is i was told it's about 25% slower than the tsc5 which makes it a no go for my work. It would be great for legal jobs fighting your way through the bush thought.?ÿ
My Panasonic toughpad fits in a vest pocket while going through the bush plus has a lot of processing power.?ÿ
I'd seen the sluggishness with the tsc5 Android system.?ÿ Has to be a way to parse that dxf into a few separate layers e.g. - Building Lines,?ÿ Lot Boundaries, Street ROWs - what ever makes sense to you - and then pull them in or out when needed.
Select points by area or radius from an overall .csv in your project folder.
I could not tell what you were trying to illustrate in your videos, but if you are new to Trimble your frustration might not be glitches. And about this time of year Trimble rolls out the new year??s TA version, if you have a license in a valid warranty.?ÿ
and contrary to your experience, when I used a demo Leica robot unit for a few days doing basic topo survey I found their software incomplete and a generation behind Trimble. Their technical support guy (US not an individual vendor) could not tell me how to reset 0 on my back sight. He had me reset my north angle skewing everything about 90 degrees!
I haven't used captivate with Leica, I tried their emulator and I thought it seemed way more user friendly than access, but until you actually use it in the real world and run into things you didn't think about until you need to (like resetting zero).?ÿ
Fieldgenius isn't perfect either that's for sure, but I just wanted to illustrate what I think should happen when you want to check a backsight (the last video I posted - not on the first page).?ÿ
The first video, you can see I stored a point I was staking out in the the staking operation and then immediately staked out the stored point. It for stored 160 meters away where that point number had already been used. It didn't prompt me that the point was already used like it normally would. Even if I knew those point numbers were used, I would still have continued on and expected it to prompt me to call it it _stk1 like fieldgenius would, otherwise I have to mess about in the settings and change the staking naming behavior just for this specific job.?ÿ
?ÿ
The Survce map cad program is far superior from the bullshit cad of the Trimble access!
I'd seen the sluggishness with the tsc5 Android system.?ÿ Has to be a way to parse that dxf into a few separate layers e.g. - Building Lines,?ÿ Lot Boundaries, Street ROWs - what ever makes sense to you - and then pull them in or out when needed.
Select points by area or radius from an overall .csv in your project folder.
I split out everything anyways, no matter what collection software I'm using, but Access does allow for individual layer selection.
Given a set of engineering drawings, I'll crunch everything down to a handful of layers, clean up the labels (keep only the ones I want to see in the field), generate somewhere between 5 and 10 CSVs, some alignments, maybe a finished grade surface, and push it all out to the cloud through Sync Manager. Pull into the DC and turn on or off whatever I am staking.
Water line staking? I'll turn on only the water layer of the DXF, check the "create nodes" box in my settings to generate nodes at the vertices, then turn on the FG surface so I can give them final grades when I lay out the lines and tees/bends. Sometimes I'll have points, but I might not even turn them on.
If the contractor wants a stake where the laterals cross the curb line, fine. Turn on the curb layer, pick the lateral and the curb line, tap and hold to select compute intersection, then stake it out.
Access, like most other software programs, benefits from proper setup of base files. Without solid office support and setup it won't really reach its potential.
?ÿ
The Survce map cad program is far superior from the bullshit cad of the Trimble access!
You've made your preference clear in other threads, without actually explaining why. Are you just randomly entering threads now to throw out one-liners without contributing?
@rover83 I was Leica user for several years. Before some months I have Upgraded to Trimble r12i rovers that is the best gps receiver that I have worked so far and Trimble s5 robotic 3''.
My problem is that I was used to work with survce program for many years and now that I switch to trimble GPS receivers as trimble can not works with other programs I found that cad program (trimble access)?ÿ in TSC5 has minor cad tools comparing with survce map!
That's just poor dealer support not poor software. Captive is every bit as good as access just all about which you are most familiar with.
Won't run a robot though (without that awkward additional module anyway).
@rover83?ÿ
If I was responsible for (and had time to) keep track of all my own control and give myself my own uploads that would be fine but I have to count on the office to give me uploads and if they try to cut down on points something always ends up missing so I would rather just have all of it.?ÿ
The most of ever have to adjust with the DXF is to turn off contour lines and some unneeded text. There is hardware that will run these uploads just fine like the tsc7 and the Panasonic I've been using.?ÿ
I haven't used captivate with Leica, I tried their emulator and I thought it seemed way more user friendly than access, but until you actually use it in the real world and run into things you didn't think about until you need to (like resetting zero).?ÿ
Fieldgenius isn't perfect either that's for sure, but I just wanted to illustrate what I think should happen when you want to check a backsight (the last video I posted - not on the first page).?ÿ
The first video, you can see I stored a point I was staking out in the the staking operation and then immediately staked out the stored point. It for stored 160 meters away where that point number had already been used. It didn't prompt me that the point was already used like it normally would. Even if I knew those point numbers were used, I would still have continued on and expected it to prompt me to call it it _stk1 like fieldgenius would, otherwise I have to mess about in the settings and change the staking naming behavior just for this specific job.?ÿ
?ÿ
Are you sure you didn??t have that 503_stk in there twice? The staked code when stored was rebar, but when you staked out another point called 503_stk the code was different. And you can customize the as staked point name in settings.?ÿ
That's just poor dealer support not poor software. Captive is every bit as good as access just all about which you are most familiar with.
Like I wrote, that wasn??t a dealer. That was Leica geosystems US tech support. It was a salesman working directly for their US company. Not sure which software, but it was 8 years ago now.
