@rover83?ÿ
I already figured out that an already existing 503_stk is what caused the software to lose its mind...I still don't understand why it couldn't be bothered to tell me the point already exists.....we deal with this all the time and I would expect it to say "hey dummy this point number is already used, you want to rename it?" Instead of just storing a point 6mm from another point 160m away from me without giving me any indication of this.?ÿ
I am not really liking the whole point number philosophy with Trimble, with a hierarchy of numbers. I'm starting to understand how it works, but I feel like they way overcomplicated it when we could just be prompted to rename, or average or overwrite, like the other softwares I've used in the past. At least then this wouldn't have happened.?ÿ
I've already talked to my pm about this issue and he's aware that now he's going to have to sit and spend a few hours deleting all the old _stk points from every drawing to prevent this in the future.?ÿ
Is there another suggestion for storing in staking besides backing out and measuring like a sideshot? Can we just do a check shot from inside the staking routine so we don't store a new name at all?
@rover83?ÿ
I already figured out that an already existing 503_stk is what caused the software to lose its mind...I still don't understand why it couldn't be bothered to tell me the point already exists.....we deal with this all the time and I would expect it to say "hey dummy this point number is already used, you want to rename it?" Instead of just storing a point 6mm from another point 160m away from me without giving me any indication of this.?ÿ
I am not really liking the whole point number philosophy with Trimble, with a hierarchy of numbers. I'm starting to understand how it works, but I feel like they way overcomplicated it when we could just be prompted to rename, or average or overwrite, like the other softwares I've used in the past. At least then this wouldn't have happened.?ÿ
I've already talked to my pm about this issue and he's aware that now he's going to have to sit and spend a few hours deleting all the old _stk points from every drawing to prevent this in the future.?ÿ
Is there another suggestion for storing in staking besides backing out and measuring like a sideshot? Can we just do a check shot from inside the staking routine so we don't store a new name at all?
I dunno, I've never had this happen to me while on a job, we separate all our staking points to be on different ranges for different applications. Storm on 6000, sanitary on 7000, etc. Everything is prepped in CAD from a master construction drawing file, so we're barred from having duplicate point numbers even before we get to Access.
We don't use points much at all anyways now that the DXF, surface and alignment staking is so much easier than in the past.
I don't see a need to delete anything, or spend more than a few minutes to fix. One could renumber the CSVs that you are linking to stake (a couple minutes in Excel) to avoid overlapping numbers, or even give those numbers a unique suffix for each file (since Trimble supports alphanumeric names).
If there's no way to modify, or split out point ranges for stakeout files, and you want to be absolutely sure that stake points are not stepping on each other, just change the as-staked name to "Auto point name" and the as-staked code to "Design name". This will allow you to reference the point that was staked, but in the description/code rather than the number/name:
Hierarchies exist in pretty much every software program, but Trimble tends to put it front and center. Personally I like it because I can always look at the point manager to see what's going on and why, and if I don't get it the help files are pretty detailed.
The critical thing is to remember that it's not storing those subsequent stake shots incorrectly, it's just displaying the very first stake shot as the location in the map. Importing into TBC will split out those separate observations and confirm that everything's good, and if you run a stakeout report in the collector, both of those observations will show up with the correct deltas to the point that was actually staked out.
We use TSC5s. I like the size, shape and weight of the device. I??m not too fond of the pole clamp. Sometimes the touch screen needs to be convinced I really want to do that, like you need a hammer for a stylus. Android kind of sucks. At first the file transfer was primitive but it worked without hiccups. Then the Android system got updated and I get this thing where I transfer the project folder onto my thumb drive and get 0kb files. Figured out to wait for the progress bar on the bottom. That worked a few times until it didn??t. So now I have to wait an unspecified amount of time after the progress bar finishes to be sure it copied the files.
The TSC3 was the pinnacle in my opinion, Windows Mobile is better, Access was better, the pole clamp was less clunky and stupid. The TSC5 comes with a bag which is tight with the claw installed on it, the claw is hard to get off so I prefer to leave it on there.
Overall it works and the 5? screen is better. All the field operations work for us without bugs.
I loved the TSC3, but now I really don't want to give up that 7" screen. If you set a TSC5 on top of a TSC7, they're darn near the same physical size but the 5's screen doesn't quite do it for me.
The Windows Mobile platform was fine except for processing power and storage space. Well, that and the fact that it got decommissioned by Microsoft.
On that note, the story I heard was that Microsoft had a mobile version of Windows 10 in the works during the TSC7 design period, but then MS scrapped the mobile OS and Trimble had to scramble to work with the standard version, and as a result the TSC7 was not as light or battery-efficient as it was originally envisioned.
@rover83 2 advantages of the 5: 1) weight, it??s lighter than the TSC3 2) battery life is a day plus.
@rover83 2 advantages of the 5: 1) weight, it??s lighter than the TSC3 2) battery life is a day plus.
For sure. Depends on what you're doing. I don't do truly remote work any more, but if I were to go back in the bush I might want the 5. The TSC5 weight is barely less than the 3, so for me it's a wash.
For battery life, in my view things have shifted. I used to stuff a half dozen "camcorder" batteries for the R6 and R8 rovers in my vest at the beginning of the day, knowing that I was going to run through all of them - without worrying about my TSC3 battery. Now I only need one or two R10/R12 batteries, and maybe one or two TSC7 batteries, and the controller batteries are hot swappable to boot. I carry less weight overall, and have to deal with a pound more on the controller, but get more bang for my buck onscreen.
@rover83?ÿ
I did miss the 7" screen from the Panasonic toughpad when I used the tsc5. The Panasonic fits on top of the tsc7 takes up less space than only the top of the tsc7 not including the keyboard and gets 2 day battery life with the extended battery or 1 day with the standard. I really wanted them to get me a radio to use access on the Panasonic but they are sending a new tsc7 and we're returning the tsc5 after that. Until then I'm using the Leica with the Panasonic toughpad again.?ÿ
I will definitely miss the tablet, except when it's raining or snowing. It's faster than the tsc7 and weighs significantly less than the tsc5.?ÿ
Is it safe to buy the tsc5 now ??ÿ just checking in.
If you tilt the tsc7 screen at just the right angle to catch the sun, you can see it is made up of a bunch crosses in the background?ÿ for .. guessing some type of polarized view.?ÿ It's really cool.?ÿ
I would not, at least not for a while. They will be doing updates to fix the glitches, I don't know if it will be 6 months or over a year before a reasonable amount of them are fixed.
Also it depends on how large your typical jobs are. I work mainly in subdivisions and most of my uploads are 3000+ points, sometimes 5000+ and a DXF. The Panasonic fz-m1 and tsc7 can handle it fine but the tsc5 chugs on it. It also takes 20+ seconds to load the point manager in most of them.?ÿ
?ÿ
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.?ÿ
@350rocketmike?ÿ
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!
@350rocketmike?ÿ
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.