I have a Mitutoyo BN1015 with PH20 and UCC T5. Running 2018R1. Will change to angle in DCC program but before it measures drops back to A0B0. Just getting started with programming with this setup. All works fine with A0B0.
Something I'm not understanding is why your tip commands have "_T5" at the end of each. It makes me wonder if that Tip selection isn't understood and so it defaults to A0B0?
Your first angle command has a dash T5: TIP/T1A0B0-T5 and your second angle command has an underscore T5: TIP/T1A15B0_T5
If you're trying to use a variable in your probe change, then that underscore needs to be a minus to be a math function. If both instances are in error, then remove both from the angle command.
I have six probe assemblies showing in server. T5 is the main one I use. So if I use the same angle with assembly T4 I want to be able to differentiate.
Does this identification work else where? I would imagine that since the software is built to differentiate already, your redundancy is causing the issue.
I++ uses a direct naming convention. So for example all probes are built and calibrated in Renishaw UCC software, then you assign a nickname in Renishaw software, then in PC-DMIS you assign than nickname through the probe edit window. It's a whole different beast unfortunately. Tool names can be pretty much what ever you want them to be and tend to be incredibly goofy looking to someone not aware.
