Weird. That's a similar but different problem to the one I had. When I looked in the raw data I could see the target id for every shot up until I used check backsight and then it would immediately turn off the target id and it would be in passive mode when I went in and looked.?ÿ
I've gotten pretty good at keeping an eye on the icon for the prism (along with target height), as even fieldgenius used to switch prism types by itself occasionally when I was using it with the sokkia.?ÿ
Have to watch everything like a hawk.?ÿ
@350rocketmike I do not understand why one would do a check BS routine right after establishing a back-sight station set up routine . ?ÿAll the deltas are in the initial back sight set up. But I know many companies that still require a stake out BS right after they set up. My LS was out in the field and he went back to 1980??s. Doing this. I said stop look read the display. He said oh now I see. I said you require them to write all this down in field book then you require a stake out BS then a stake out a 3rd point check to another point and all required . He said now I see what is going on. ?ÿYou were correct. So i am slowly moving them to do station set up. Write the deltas in field book then turn to ck topo to a third point. This allows for a nice report as part of the the office side qa/qc process. Of course at the end of a set up or during a long time at a station I ask the crews to perform a bs ck store an reorient or store as a ck.?ÿ
hey under the influence of deep fried turkey dressing corn pudding mash tators pies pies pies. ?ÿI did a little reading last night trying to figure out your duplicate points issue in intergrated mode. When you do the video or check try this as well. Go to the options and ck or un ck the precise elevation mode for intergrated survey and see if that changes anything. I will try and read a little more today if the rain comes. Off to check cows and do a bit of honey do??s and try and work off the pounds of turkey and such i had yesterday. Along with a few containers of roleaids and tums. Lol.?ÿ
No I don't see why anyone would check the bs right away either, I just thought maybe he did because that's the only thing that triggered passive mode in my settings until the last update. Personally I shoot the bs in 2 faces and check the deltas before accepting. Then I sometimes wait for it to lock in face 1 again and I look at the Hz angle to make sure it's close enough to 0.?ÿ
@350rocketmike yeah i was just mentioning it for sure. ?ÿAnother option to try on the ck shot. Is instead of typing in the number in measure topo etc is to ctl+k. And then it should take you to the ck shot screen for bs or other. Here it should only give you an option to store another or store as a ck if out of duplicate point tolerances. ?ÿMaybe try that in integrated surveys it might help isolate for the Trimble programmers if and where the bug is. To bad we don??t get paid by them to figure all this out. Lol well i use to.
Also I can try precise elevation also. It's turned off. I thought it was for doing using the ts for elevation and GPS for topo shots or something like that. If I have line of sight though I'm almost always going to use the ts, and gnss possibly just as a check. Unless I was using a questionable TS setup and just wanted it to check my GPS shots.?ÿ
@350rocketmike yes the precise elevation allows you to measure hz position with gnss and elevation from the robot is all. When i trouble shoot something I always try to do a different way to try and isolate where a issue is. Reason for ctl k option. U can also be in map screen and no point seleted tap and hold and check option comes up or select a point use soft key and do ck shot etc.
Okay, we just had this issue happen this morning. What did your raw data say around the initial setup? I can't find where it switched, it just shows a custom prism, prism type number 1 (which has always been the mt1000), prism constant was still +10mm, but it locked onto the truck and I told my helper (summer student) to check if it was active mode and that's when we discovered it. This was in integrated mode again.?ÿ
Raw data shows no sign that my helper changed anything in the prism settings.?ÿ
I was the one in the field that day, i knew i did not change prisms after the station setup, and I was damn sure I set the prism to the MT1000 before shooting the backsight.
This was a brand new TSC7 that I took outside, first job.
After the station setup TA switched prisms itself, hence my assumption that TA remembers the last prismtype used in each survey mode. (If you do a check backsight it knows what prism was used in the station setup and changes accordingly.
We convert our jobs to jxl files before we transfer via memorystick. You can read that jxl just the same as you review the data in TA itself, it??s xml but very good readable if you use the right tools. See my screenshots from some days ago.
Finishing a station setup and starting Measure Topo inserted the extra prism record.
?ÿ
So you have to check and set your prism type when shooting your first point after a station setup.
This was totalstation S6 only, no integrated surveying.
?ÿ
I would really like to take a look at your job or jxl in question - are you able to message it to me please?
Access has only one prism setting - the current one.
When you start up access for the first time, it will select the first one in the list.
Any time you start after that, it will select the last prism used.
For the check backsight routine it reads and selects the same prism as used for the original shot. With the more recent versions of Access, when you escape back to measure topo Access switches back to same prism type as set when you entered the routine. The earlier versions of Access do not revert?ÿ
There are also a couple of caveats here.?ÿPrism type is selected/remembered by the number - edit that prism and those changes are kept for the check backsight.
Also there is a known issue where, if you change the prism type during either the initial level or atmospheric corrections forms, your selection is forgotten and is reset before you get to the station setup page. (There is a fix for this in the pipeline).
Hope this helps
Jim
?ÿ
?ÿ
?ÿ
?ÿ
?ÿ
?ÿ
@jimcox?ÿ
Thanks for the extra information.
I'll add the job and jxl file here, no secrets involved.
There's only 1 stations setup in this job, the other points are all GNSS points.
After the station setup I assumed I was continuing with the MT1000 prism but it switched to the miniprism. that may have been used before on first connection with the S6 in the office. That type of prism must have been in there one way or another.
@rover83?ÿ
Turns out that turning off the e bubble (and/or x fill) was the reason for the reset rtk disappearing. Trimble punishing us for not using it? Sure seems like they are trying to punish us with a lot of things so I wouldn't put it past them.?ÿ
Anyway the menu, measure, rtk initialization, reset is only a couple extra button presses so it's probably worth doing it that way. Although this time I tried it out with the e bubble and it seems to have stayed in calibration since I turned it off several weeks ago. The first time it lasted a couple of days before going out of calibration.?ÿ
I would really like to take a look at your job or jxl in question - are you able to message it to me please?
Access has only one prism setting - the current one.
When you start up access for the first time, it will select the first one in the list.
Any time you start after that, it will select the last prism used.
For the check backsight routine it reads and selects the same prism as used for the original shot. With the more recent versions of Access, when you escape back to measure topo Access switches back to same prism type as set when you entered the routine. The earlier versions of Access do not revert?ÿ
There are also a couple of caveats here.?ÿPrism type is selected/remembered by the number - edit that prism and those changes are kept for the check backsight.
Also there is a known issue where, if you change the prism type during either the initial level or atmospheric corrections forms, your selection is forgotten and is reset before you get to the station setup page. (There is a fix for this in the pipeline).
Hope this helps
Jim
?ÿ
?ÿ
?ÿ
?ÿ
?ÿ
?ÿ
I'm not sure if this was an inadvertent side effect of this change (see screenshot) but in integrated mode it also switches from TS to GNSS and vice versa back and forth every time you hit escape, if you're just trying to close a screen. I don't know if it was like this before the update, but it is somewhat annoying, because it happens constantly.?ÿ
The other thing that happens (sometimes) and in not sure exactly what triggers it, likely a specific way in doing something but if I have something open like an inverse screen or point list and I move to a different area of the map and zoom right in to some points, if hit escape to close the inverse tab or point list, it jumps the map back to where I was when I did that inverse. Then I have to pan back over again. Not sure if this is a bug, but it is another things that been a bit of a pain in my workflow.?ÿ
?ÿ
> every time you hit escape, if you're just trying to close a screen
Mike, What controller - your TSC7?
And do you mean the ESC key on the keypad, or the softkey on the screen - they are not exactly the same thing.
I'll see if can get the same thing going on 🙂
?ÿ
?ÿ
@jimcox?ÿ
Yeah it's the tsc7....Right now it's typically the escape key on the keypad since it's cold and I'm wearing gloves. The glove mode also doesn't work as successfully as the touchscreen only tablet I was using before this tsc7.?ÿ
In the summer time I usually use the touchscreen to save wear and tear on the keyboard.?ÿ
I posted this right after it did it to me, because it reminded me of the problem...but then when I tried to duplicate the problem a second time in a row it didn't do it.?ÿ
I believe all I did was zoom in on a point, to see the number of the check I shot to it, hit my inverse hot key, checked the difference, then zoomed over to the next point I wanted to look at, hit escape to give myself some more screen real estate and keep the memory cleared out and it jumped back to where I was previously zoomed in on.?ÿ
Yeah it's the tsc7....Right now it's typically the escape key on the keypad since it's cold and I'm wearing gloves.
I can't make my TSC7 controller do that swap Integrated modes on the ESC key at all.?ÿ
?ÿ
I posted this right after it did it to me, because it reminded me of the problem...but then when I tried to duplicate the problem a second time in a row it didn't do it.?ÿ
I believe all I did was zoom in on a point, to see the number of the check I shot to it, hit my inverse hot key, checked the difference, then zoomed over to the next point I wanted to look at, hit escape to give myself some more screen real estate and keep the memory cleared out and it jumped back to where I was previously zoomed in on.?ÿ
Closing a side window and returning focus to the map potentially gives a resize and redraw on the map window. There is a new map centrepoint and potentially a new mapscale. And potentially is worse still if we have a third window in the equation. I think what may be happening here is the priority of the redraw message (low) vs user input (high) maybe..
Ideally we would like to find a workflow that generates the trigger condition - but that I know there has been work done around map and window creation, size and positioning - so I'm hoping the problem may have already been addressed in the next software release?ÿ
?ÿ
?ÿ
