Your Products have been synced, click here to refresh
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?
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.
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |