hexagon logo
Register Sign in
  • Replies 25 replies
  • Subscribers 222 subscribers
  • Views 389 views
  • Users 0 members are here
Options
Related

TP20 6-port probe changer issues

JimCMS
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.
  • So:

    I recalibrated the TP20 - didn't work.
    I removed all port assignments then saved with no probe assignments. Reassigned probes to same ports and still not fixed.
    I swapped the probe to a working port - didn't fix it, but the other probe now in port 6 functions correctly, so it appears to be an issue with the probe?​



    HR-X1 is from post #2. Jims changer is showing TP20. I'm thinking that if you put in the correct rack it should work. My 2c
  • in reply to ogcharliebrown
    MCR20 Probe Change Rack might be the rack your using.
  • 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?
  • 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 rack is an MCR20 (TP 20). Other references to HR-X1 came from DeWain Hodge as an example of his probe rack, not the one I am using.

    Command to load probe uses same probe name as one assigned to port 6:

    ​
    Attached Files
  • in reply to JimCMS
    OK, makes sense, so far, so good. One more question which we've overlooked. Is this the ONLY rack defined in the system?

    And please re-affirm, it is only one single which is having the problem, still? Which one is it now?
  • This is the only rack in the system and only port 6 (with 15BY67MM probe assigned) is having an issue. However, if I put a probe from any other port into port six and update the probe changer port assignment to reflect the change, the Loadprobe command will take the probe from #6. As soon as I reassign port six to the 15BY67MM probe, it asks for a manual probe change when executing Loadprobe command.
  • This is the only rack in the system and only port 6 (with 15BY67MM probe assigned) is having an issue. However, if I put a probe from any other port into port six and update the probe changer port assignment to reflect the change, the Loadprobe command will take the probe from #6. As soon as I reassign port six to the 15BY67MM probe, it asks for a manual probe change when executing Loadprobe command.

    To clarify further, if I assign the 15BY67MM probe to any port 1-5, the Loadprogram asks for a manual change.
  • 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.
  • 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.
  • 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.


    fantastic spot there!

    Almost certainly the root cause!
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement