had a former assistant who just started. corners were measured dist-button, then rec-button at the corner. He forgot the dist button the whole day. Only angles were recorded. The boss wasn't too happy
surveydawg, post: 414529, member: 12073 wrote: I would like too see your setup for locking the robot, if you have a pic handy!
Me too!
christ lambrecht, post: 414537, member: 284 wrote: Really?
I don't know that feature ... you're not speaking about points with the same nr or name?
Christof.
It's under the duplicate point tolerance screen under survey styles. At the bottom there's an area where you can check the box for proximity check of points with different point names and specify a horizontal and vertical distance. With this turned on, a series of shots to a stationery rod should give a warning.
Thanks a lot.
not possible on our TSC2's with Access 2012.10
Will check the new TSC3's for that option.
Christof.
Jim Frame, post: 414484, member: 10 wrote: This afternoon I was working on a topo survey with my robot when a crew from an out-of-town company parked nearby to eat lunch. One of their guys wandered over to see what I was up to, and we chatted for awhile about business, equipment, the weather and other matters of mutual interest. After a bit I allowed as how I ought to get back to work, and resumed picking up points. Maybe 20 minutes later I glanced at my robot and it didn't seem to be pointing at me. I looked in the general direction it was aiming and saw that the other crew had leaned their prism pole against their truck. So I checked the map on my data collector and saw that I had 41 shots to their 360 prism. That's when I decided to call it a day.
Jim I really appreciate your candor. I also have suffered that fate. In fact, I was briefly blacklisted for it (i did it only once). My name still hasn't cleared (it was like 8 years ago). It's kinda like going to jail - you get the reputation or at least it gets thrown back at you from time to time.
I never liked standing all day behind the gun anyway. It ruins my back.
Thing about the active prism is it will not lock on when selected to a prism.
We are surveying a boundary in Magalia. I have the boundary calc'd from record data. We set laths on my calc'd line as we go. Eventually I'll go back and correct the laths to line between found monuments, will be less than a foot in most cases. I think the Camp Chief wants carsonite line posts. It's a Cal.C.C. camp so we'll probably be able to recruit some of those Cal.C.C. troops to help with that.
So there I am in the brush 30' from the S7...find a hole I joystick it over...I can see it looking at me...won't lock...what the heck? Dan goes down there and points it, still won't lock...I've done smaller holes further away. OH Forgot to change to the active target. Locked right on.
The first time I used the robot I took 30 shots to the backsight. It grabbed the backsight when I walked by. Like Kris said, that's when I learned to watch for it changing before storing the shot. The active target largely cured that although sometimes it'll say target locked when it's not locked. When staking out don't believe it, make sure the numbers are floating especially in brush.
Hate to point this out to you Jim, but it appears you assumed your robot was monogamous. It cheated on you with another rod. Right in broad daylight when you weren't looking.
Scott Ellis, post: 414567, member: 7154 wrote: How do you process your field to finish? We use Carlson and they have an option to split mult codes.
I rolled my own. It does have a mechanism for adding a second code, but it's by means of a note rather than part of the description and that makes it cumbersome enough that I found it easier in most instances to take a second shot. I chose that route originally because I often include supplementary info in the description after the F2F code, and it seemed simpler that way. But I may revisit that, probably identifying additional codes by means of a unique character (e.g. |).
Jim Frame, post: 414601, member: 10 wrote: I rolled my own. It does have a mechanism for adding a second code, but it's by means of a note rather than part of the description and that makes it cumbersome enough that I found it easier in most instances to take a second shot. I chose that route originally because I often include supplementary info in the description after the F2F code, and it seemed simpler that way. But I may revisit that, probably identifying additional codes by means of a unique character (e.g. |).
We when started field to finish we took separate shots on everything then cleaned up the drawing in CAD, it tooks a while to do this in CAD, when you have Edge of Asphalt, Gravel Road, Top of Ditch, seemed like a waste of time to do the field to finish then have to clean up all of the line work. The multi codes shots really do make it easier and cleaner, and faster.
surveydawg, post: 414529, member: 12073 wrote: I would like too see your setup for locking the robot, if you have a pic handy!
I have a photo somewhere, but finding it would take more time than it's worth. There's nothing fancy about my method, it boils down to this:
1. Run the tribrach latch screw all the way in to the secured position.
2. Take a bit of rubber -- I cut a piece from an old thorn-resistant bicycle inner tube -- and push it into the screw hole, then trim flush with a sharp knife.
3. Get a suitable length (10' or so) of stainless steel wire rope -- I use 7/32", but you can go a little larger if you like -- and create a loop in each end. You'll need some sleeves and a crimping tool, or find a shop that has them.
4. Thread one end of the wire rope through the tribrach, and run the other end through the protruding loop.
5. Lock the free end of the wire rope to a stationary object. I like to set my control points near light poles, chain link fences, or fire hydrants (I keep length of chain handy for hydrants).
This method won't stop a determined thief, but it'll slow down the grab-and-go guys enough to discourage them, and will give you time to see what's going on and put a stop to it.
Jim Frame, post: 414484, member: 10 wrote: This afternoon I was working on a topo survey with my robot when a crew from an out-of-town company parked nearby to eat lunch. One of their guys wandered over to see what I was up to, and we chatted for awhile about business, equipment, the weather and other matters of mutual interest. After a bit I allowed as how I ought to get back to work, and resumed picking up points. Maybe 20 minutes later I glanced at my robot and it didn't seem to be pointing at me. I looked in the general direction it was aiming and saw that the other crew had leaned their prism pole against their truck. So I checked the map on my data collector and saw that I had 41 shots to their 360 prism. That's when I decided to call it a day.
That is the oldest trick in the book! LOL, that happens more than you think. You can change your settings to a different frequency. Or maybe retire.
christ lambrecht, post: 414591, member: 284 wrote: Thanks a lot.
not possible on our TSC2's with Access 2012.10
Will check the new TSC3's for that option.
Christof.
I'm on 2016.12 but I think it was on mine when I first got it which would have been a late 2014 or early 2015 version.
James Fleming, post: 414502, member: 136 wrote: When your robot repeated returns to the wrong target: recidiprism.
Boo!
Dan England, post: 414607, member: 12510 wrote: That is the oldest trick in the book! LOL, that happens more than you think. You can change your settings to a different frequency. Or maybe retire.
Am I missing something here? Do you mean the "other" surveyor purposely laid his prism against his truck to disrupt Jim's shots?
I could suggest a few repercussions, but the end result would probably involve the judiciary system.
FL/GA PLS., post: 414746, member: 379 wrote: Do you mean the "other" surveyor purposely laid his prism against his truck to disrupt Jim's shots?
No, it was completely innocent. He stopped for lunch at the dead end of the street I was cross-sectioning, a couple hundred feet from where I was at the time, and leaned his prism pole against his truck while he ate his sandwich. As I worked my way toward him, he walked over to chat. Sometime after I moved on I crossed over past his prism, and that's when my robot decided that it liked that target better than mine.
Jim Frame, post: 414753, member: 10 wrote: No, it was completely innocent.
Thanks. It's nice to know they were innocent. 🙂
I certainly hope no surveyor would purposely interfere with another comrades data collection.
[USER=379]@FL/GA PLS.[/USER]
When finding a tripod, tribrach, and prism target, unatended, beside the road, i have been known to stick my business card in the front of the prism, blocking a return from it....
FL/GA PLS., post: 414757, member: 379 wrote: I certainly hope no surveyor would purposely interfere with another comrades data collection.
Nate The Surveyor, post: 414770, member: 291 wrote: When finding a tripod, tribrach, and prism target, unatended, beside the road, i have been known to stick my business card in the front of the prism, blocking a return from it....
Buddy, you better start praying vigorously or get used to some high temperatures. 😉
Jim Frame, post: 414601, member: 10 wrote: But I may revisit that, probably identifying additional codes by means of a unique character (e.g. |).
I revised my code to accommodate multiple F2F codes per point, separated by a backslash. (I already use the pipe symbol to flag "no DTM" shots and remarks in the raw data. On my Surveyor+ the pipe is on the Y key and the backslash is next door on the Z key, so it was a convenient choice. ) I haven't tried it in the field yet, but in testing it works well.
Thanks for the kick in the butt -- this is something I probably should have done a long time ago, but allowed complacency to hold me back.