I'd suggest you this procedure: Find a wall/column and mark a spot where you can shoot reflectorless with your scope more or less horizontally about 20'(6m) away and take a?ÿ horizontal distance shot. Hold your mini prism with the back tip right on the mark and take a shot in robotic mode using the mini +17.5mm constant. The difference between the 2 measurements should be added to 17.5 and the result would be your new prism offset for this particular application. Of course, you can take a few shots in each face in both reflectorless and IR mode for a better result. I believe you can get a true offset within 1mm or less using this method. The mini prism tilt in any direction, horizontally or vertically, will have a great effect on the distance measurement. That is why it is important that the mini be perfectly oriented toward the instrument. You have to remember that the instrument's ATR will focus on the prism center, not on the back tip. I have done that type of "as-built" survey shown in the video above, but I never used a prism. I always went reflectorless in 2 faces. I believe that the prism would induce additional errors due to it not facing perfectly the instrument. This is just my opinion, please correct me if I'm wrong.
Thank you ALL for the great help.?ÿ VERY much appreciated!
As @john-putnam stated, and using all the other's advice to verify, for the GMP111 (+17.5mm constant) PLUS the 20mm offset distance from the reference plane (the pivot point) to the pointed tip I was able to make a custom user target of 37.5mm for "just" the peanut prism when removed from holder.
.
?ÿ
I am getting error in latest Fieldgenius also after creating new user target.
As far as the FieldGenius error I was getting with their demo when trying to create a user target, I figured it out.?ÿ Just a simple settings.xml edit. (ProgramDataMicroSurveyFieldGenius11)
Just FIND the user target made (i.e. test) change 0 to 1:
<Target Name="test" Manufacturer="1">
VOILA!
?ÿ
?ÿ
This "fix" is not working for those who run into this.?ÿ It let's you create a new user target, BUT...?ÿ the custom user CONSTANT is NOT sticking.?ÿ So it's useless.
This pertains to a older Leica TCRA1103 PLUS using the Leica "Robotic" GEOCOM driver.?ÿ Seems to be a driver issue.
It does work though if using the Leica "TPS Series (GSI)" driver though.?ÿ But extra functions such as turning laser on/off are removed.?ÿ 2 steps forward, 10 steps back. : /
?ÿ
I would suggest sticking with standard GMP111 prism with a 17.5 mm constant.?ÿ Then apply a 20 mm offset to the shot itself.?ÿ I'm not familiar with FieldGenuis, I suspect you have the ability to add offsets to single or multiple shots.?ÿ Adding the 20 mm to the prism constant seems like an accident waiting to happen.?ÿ
I am getting error in latest Fieldgenius also after creating new user target.
As far as the FieldGenius error I was getting with their demo when trying to create a user target, I figured it out.?ÿ Just a simple settings.xml edit. (ProgramDataMicroSurveyFieldGenius11)
Just FIND the user target made (i.e. test) change 0 to 1:
<Target Name="test" Manufacturer="1">
VOILA!
?ÿ
?ÿ
This "fix" is not working for those who run into this.?ÿ It let's you create a new user target, BUT...?ÿ the custom user CONSTANT is NOT sticking.?ÿ So it's useless.
This pertains to a older Leica TCRA1103 PLUS using the Leica "Robotic" GEOCOM driver.?ÿ Seems to be a driver issue.
It does work though if using the Leica "TPS Series (GSI)" driver though.?ÿ But extra functions such as turning laser on/off are removed.?ÿ 2 steps forward, 10 steps back. : /
?ÿ
?ÿ
OK.?ÿ "FINALLY" figured out a workaround for this problem.?ÿ MicroSurvey FieldGenius (FG) DEMO (latest version at writing 11.4.0.524 (2022-10-06)) does not seem to be able to SET the EDM settings to the instrument when using a CUSTOM USER TARGET from FG.
PREREQUISITE:?ÿ Create a CUSTOM USER DEFINED TARGET on the instrument.?ÿ via DEF 1 etc.
If you try to create a custom user target in FG using a new target or copying a PRISM it doesn't seem to work.?ÿ FG sends back error.
If you COPY the ONE built-in "RL (Reflectorless) target", it seems to work.?ÿ You can still make it a PRISM target and use your own Constant value. (fyi, before all of this, tried making the custom user target NAME on the instrument the same as in FG and still did not work).
The catch is since FG is NOT setting the EDM you MUST make sure to do this on the INSTRUMENT.?ÿ But at least the custom user target IS working with the correct Constant value.
?ÿ
The catch is since FG is NOT setting the EDM you MUST make sure to do this on the INSTRUMENT.?ÿ But at least the custom user target IS working with the correct Constant value.
?ÿ
Ok, after further tinkering, and determined to get the Leica TCRA1103 Plus EDM settings via FG, here is "hopefully" the "FINAL" work-around solution:
Using the Leica "Robotic" driver.
Goto the Settings.xml file where the TARGET settings are stored:
(Windows 10 Pro) ProgramDataMicroSurveyFieldGenius11
Open with Notepad.
Using FIND, search using the keyword "user".
There will be (3) entries in the file specified with "Leica User1" that apparently relates to the first DEF 1 user target you have created on the instrument itself and so forth for the other (2) user targets out of (3) total that can be created.
?ÿ
</Target>
<Target Name="Leica User1" Manufacturer="5">
<Type>0</Type>
<Height>0.000000</Height>
<PrismConstant>0.000000</PrismConstant>
<PrismAperture>0.000000</PrismAperture>
<Icon>4</Icon>
<Define>4</Define>
<EdmMode>-1</EdmMode>
</Target>
COPY ALL OF THIS.
Then search using keyword "TargetCollection"
INSERT by PASTING the text you copied right above </TargetCollection>
</Target>
<Target Name="Leica User1" Manufacturer="1">
<Type>0</Type>
<Height>0.000000</Height>
<PrismConstant>37.500000</PrismConstant>
<PrismAperture>0.000000</PrismAperture>
<Icon>4</Icon>
<Define>4</Define>
<EdmMode>0</EdmMode>
</Target>
*MAKE SURE TAB SPACINGS ARE CORRECT.
THE KEY HERE IS TO CHANGE THE (2) RED VALUES TO MATCH AS SHOWN.
Apparently <Target Name="Leica User1" Manufacturer="1"> specifies that the target is a MANUFACTURER target.?ÿ If you leave it at "0", it will send back an error in FG even though 0 tells it is a USER target.?ÿ Go figure.
The <Define>4</Define> apparently sets the EDM on the instrument to match up with your first USER TARGET created on the instrument (DEF 1).?ÿ Have not tested, but would assume the same for the next (2) user created targets on the instrument.?ÿ i.e. 5 for DEF 2 (instrument) and 6 for DEF 3 (instrument).
If all of this is done correctly, FieldGenius will NOW correctly set the USER TARGET created first on the instrument (DEF 1) without having to MANUALLY also set it on the instrument.?ÿ So can now switch TARGETS freely using FieldGenius completely.
HOPE THIS HELPS ANYONE WITH THIS SAME SITUATION! ; )
GeoCom v1.05 (I have v1.07 which may have more options)
PAGE 94
For newer FlexLine instruments, but PAGE 37 shows the PRISM TYPE DEFINITIONS that seem to work with older TCRA1103 Plus (TPS1100 series)
?ÿ
GeoCOM v1.10
PAGE 68