hexagon logo

TP20 6-port probe changer issues

Running 2023 R2.
I'm trying to put a new probe into our TP20 6-port probe rack, but for some reason it's the only one that won't load automatically. Ports 1-5 work normally, but when loading or unloading the new probe positioned in port 6, it asks me to manually remove the new probe before loading another probe or when trying to load the new probe. I checked port assignments, and the correct probe is specified for the port.
  • Thank you for showing all the ports. This is a tricky area for many people and an incorrect definition can get confusing, but not the case here.

    As also noted, make sure it is the correct rack type. HR-X1 and MCR20 (or TP20) are very different. Can you send a picture of the rack?

    Also yesterday it was a 5x100 in port 6 and today that one is hot shown anywhere. With the current list of slot contents, what is the name of the one in your PRG that is trying to load? Can you show that command?


    The first screenshot is from my rack not JimCMS's rack. I was only trying to help with his setup. Sorry for the confussion.
  • A couple of things spring to mind.

    1) are you 100% sure it's the same probe file (I've seen systems where they have say a 1 x40mm and a 1x40mm (one with a space in the name and one without) and it's the wrong one selected in the rack

    2) double check in set search paths under probes if you've got the 'look in program directory' option ticked, you may have inadvertently created a duplicate probe file

    3) from probe utilities, click setup, is that probe specified in the 'use for probe unload'?

    I'm posting from my phone, so the exact wording of the options mentioned might be different but you should figure out what I mean.


    1 - probe file name in probe directory matches
    2 - set search path points to appropriate probe directory
    3 - probe not specified in "use for probe unload" - that field is blank

    Attached Files
  • Ok two things:
    1: I am pretty sure this isn't your problem, but make 100% certain you have a probe build that doesn't contain a SPACE at the end of the probe name.

    2: PDCMIS thinks it's smarter than you are. I had this happen with trying to use TP200 modules on a MCR20 (not possible).
    --Hexagon has some backend validation that makes certain that you can't use a TP200 on a TP20 rack, even though it's physically possible.
    --I noticed your probe #6 in the picture is the only probe using a TESASTAR branded module.
    --Try rebuilding that probe, reference a TP20 module in the build instead of the TESASTAR.

    It will likely work then.

    PCDMIS is probably programmed to prohibit any probe BUT TP20's from being mounted on a MCR20 rack.


    Will try rebuilding probe later this morning - lots of projects going. Thanks for everyone's input!
  • Ok two things:
    1: I am pretty sure this isn't your problem, but make 100% certain you have a probe build that doesn't contain a SPACE at the end of the probe name.

    2: PDCMIS thinks it's smarter than you are. I had this happen with trying to use TP200 modules on a MCR20 (not possible).
    --Hexagon has some backend validation that makes certain that you can't use a TP200 on a TP20 rack, even though it's physically possible.
    --I noticed your probe #6 in the picture is the only probe using a TESASTAR branded module.
    --Try rebuilding that probe, reference a TP20 module in the build instead of the TESASTAR.

    It will likely work then.

    PCDMIS is probably programmed to prohibit any probe BUT TP20's from being mounted on a MCR20 rack.


    Rebuilding the probe referencing a TP20 in place of the Tesastar worked!

    Again - thanks to all for the input!
  • Glad it worked, and thank you for following up with the solution.

    Good catch Is that not also the case for the port in the #4 slot ?