@rover83?ÿ
I'm given a combined scale factor which I can use if running TS only, but it fits almost perfect with just selecting our UTM zone, nad 83 and the local geoid. Some jobs are site calibrated instead and some older jobs are scale 1:1, which means I can't use my vrs rover (I don't have a base).?ÿ
This is an area I need to spend more time researching just to have a better understanding.?ÿ
?ÿ
Sorry, just chewed over your response a bit more.?ÿ You can use a VRS rover for a ground sub.?ÿ We do it all the time here in SW ON.?ÿ PM me if you want to exchange cell numbers to shoot the poop on it for a bit.?ÿ I presume you are on Smartnet per the VRS statement??ÿ We are currently using Topnet and Carlson, but the fundamentals are similar.
?ÿ
Some older jobs are scale 1:1, which means I can't use my vrs rover (I don't have a base).?ÿ
I agree with @jaccen, VRS doesn't preclude site calibrations for local coordinate systems. It's just like setting a base up over an arbitrary point and getting a here position, then tying points with the rover for use in the calibration.
Definitely a problem if there aren't enough points to calibrate to, though.
I am deep in VRS-land, and even though it's a great tool there's a ton of misinformation and incorrect procedures floating around...
@jaccen?ÿ
Sorry I meant when site calibrations aren't a good option. We use cannet which is Trimble only.?ÿ
Also these are usually subdivisions that have been around a few years and already have lots of houses in them. In some cases I might be able to consider a site calibration as long as I can get good checks to existing building ties, but often it would take less time to set on some existing control and traverse to where I need to be.?ÿ
@jaccen?ÿ
Yes this mainly all small residential houses in large subdivisions. The houses are usually just ground distances even if the rest of the job is in grid, these are very small houses on small lots. And the better formers can often get the corners of the walls within 0.015m?ÿ
The reason they've been trying to keep all the newer stuff in grid is so we can replace control when it constantly gets destroyed, without spending an hour or 2 doing a site calibration to get set up again.?ÿ
Just finished a backsight and put the mt1000 back in the truck and drove back to where the layout is, "target locked...no target... target locked..." the whole way up the street....so I figure "damn the switching back to passive bug has returned"...back into the settings...what do I find? Still in semi active right where I set it when I went to backsight. So why did it lock onto the truck?
?ÿ
Edit:
I don't think it was actually locking on anything. I discovered shortly after access had slowed down to a crawl... so it was likely about 10-20 seconds behind with its verbal diarrhea as I drove away. It probably lost and gained the target a couple times as I put the prism in the truck so it was just behind.?ÿ
And since I know someone will bring it up...I booted the collector up from completely off when I first got here. I don't leave it on all day or for days like some guys do. It's likely a wonky DXF that's causing the lag here.?ÿ
Normally the speech only lags behind by about 2-4 seconds under normal conditions.?ÿ
So why did it lock onto the truck?
Where was the prism in the truck? Was it in a location where the LEDs could be seen by the instrument? Reflected off something?
When the MT1000 battery is good, it's turned on and set to the correct ID that matches the one in Access, and the diodes are all in good shape, I've never - not once - seen it actually lock onto anything BUT the MT1000.
I've seen it lock onto the prism's reflection in still water before, but never something that is not the prism.
Edit:
I don't think it was actually locking on anything. I discovered shortly after access had slowed down to a crawl... so it was likely about 10-20 seconds behind with its verbal diarrhea as I drove away ...?ÿ
Normally the speech only lags behind by about 2-4 seconds under normal conditions.?ÿ
Are you running speech output ALL THE TIME?
That could be half your problem.?ÿ I know EVERY machine I've ever dealt with using speech output, and I've dealt with alot(my wife is totally blind) runs alot slower. Try turning off the speech, or at least adjusting the verbosity.?ÿ
?ÿ
Point taken. I will turn it off. Only reason I leave it on is sometimes it's useful. Unfortunately Trimble doesn't give any options to adjust it. On/off and adjust the volume. I would like to turn off the broken "Go left!" When you need to go 20 meters out and 0.050 left. Seriously?
Sound on the controllers can be quite delayed, and they can get queued up for ages. Unfortunately it is an operating system thing - Access says 'play this' and the system gets around to it when it can - and sound is usually a low priority system process.
The top line of the display is your best measure of what is going-on right now. It gets updated by Access as high-priority real time. If you don't see that padlock you're not target locked, simple as that.
For me, the only time the sounds are useful is through a set of blue-tooth earmuffs when setting out on noisy construction sites. Then the 'go left' 'go right' mean I can concentrate on the prism bubble, not the controller so much.
I do like having the controller vibrate when it stores a point.?ÿ
@jimcox?ÿ
I definitely pay more attention to the screen than the sound, but I have tripped and fallen in a couple of holes trying to watch the screen (usually with GPS when I'm trying to see if I am headed in the right direction). Why did Trimble leave out the "go in" or go out", it's always left or right, even if it's 200m out.?ÿ
I do like the vibration when the observation is stored though.?ÿ
One of the times I want the sound is if in shooting control or a corner with GPS and I try to do something else while it's shooting.... I'd like to hear "poor pdop" as a heads up when things start to go bad.?ÿ
Back to the original glitch...I confirmed it doesn't happen using TS only or GNSS only at least on my data collector.?ÿ Using the other party chiefs collector the other day, he had the default access tolerance settings 0.000 for the distances, but something like 20" on the angles. And the duplicate point in that case may have been 0.000 from the original shot.?ÿ
So my conclusion is that the glitch is only in integrated mode. If I get a chance I will try to catch it on video today, since I'm sure people think I have my tolerance settings wrong (verified it 3 or 4 times now both in the s5 conventional style and rtk style).?ÿ
Just finished a backsight and put the mt1000 back in the truck and drove back to where the layout is, "target locked...no target... target locked..." the whole way up the street....so I figure "damn the switching back to passive bug has returned"...back into the settings...what do I find? Still in semi active right where I set it when I went to backsight. So why did it lock onto the truck?
?ÿ
I ran into a similar problem where I on first use of a TSC7 I configured the Prism MT1000 to active when I was performing the Backsight measurements. Once the station setup was finished I started Measure Topo, shot my 15 points, checked my backsight with the check backsight routine - everything perfect so I broke down the setup and drove to the office ... later at the office I found out that my 15 points were all shot on a reflector pole along the road. Checking in the TSC7 I saw that my Measure Topo points were all shot with a custom Prism in passive mode !!!
I even checked the map view in the field and had to zoom in very deep but did not realise something was wrong there. All points were in a trench of 2m x 0.30m
So adjusting the prism in the stations setup/Backsight mode works only for your stations shots, AND NOT for your Measure Topo shots. Does this make sense? I think it will since it remembers and switches to the correct prism when you start the check backsight routine.
My 15 shots were pot hole shots on utlity lines - embaressed of course & I felt like a starter that day.
The trench was already filled up again, so no data for that location.
?ÿ
?ÿ
?ÿ
Are you sure you you didn't use "check backsight" before those topo shots? Because that was a bug that was finally fixed in the last update....often when using check backsight it would automatically switch to passive mode immediately and you wouldn't know until it started shooting random signs and stuff.?ÿ
Now I constantly check the prism setting even though it seems to be fixed.?ÿ
As far as changing the settings of whichever prism style to active, i never noticed that it had to be done in measure topo.....it would jump back to a different prism type if that's what you used for the backsight but the settings in the individual prism type shouldn't change. If it did that would be ridiculous but it wouldn't surprise me after some stuff I've seen it do.?ÿ
@350rocketmike?ÿ
I checked the jxl file and did not do a checkshot imediatly after the station setup was finished.
I was on TA 22.00, past september.
after the stationRecord and backbearingRecord is a TargetRecord with Multitrack,
then we have a pointRecord Face1, Face2 and the Stationresiduals followed by a new TargetRecord with a CustomPrism that I never selected.
Before the check shot on my back bearing there's the TargetRecord with the Multitrack again.
