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

Probe File Noob Help

BassQuality
I've many years of CMM and inspection experience, but I've recently "inherited" running PC-DMIS. For the most part I can figure things out with (relative) ease, but I could use some advice and help regarding probe files.

First off, I have three versions of the software: 2018, 2019, and 2021. Some part programs will no longer run on the 2021 version as they are evidently too old to do so, and therefore I need to close and exit the 2021 version and execute and run the 2018 or 2019 one.

We have a 6-module probe changer rack, and I've figured out how to add and remove modules from the probe changer definitions. I've also figured out how to add/edit/change module/probe/styli definitions, and how to calibrate using a master probe. What I'd like to do is delete all of the old probe definitions from the probe file, so that only the current six (6) modules remain. I remember the former QA inspector doing so, and always complaining that as soon as he loaded up and ran an older program it added all the deleted definitions back into the probe file. So before I invest too much time into futility, I'm hoping I can get some advice.

What is the best way to start from scratch? Tabula rasa with the probe file.
How do I reliably back that up?
How does having multiple versions of PC-DMIS effect the probe file?
Are there precautions to take when running older versions with older part programs so that the probe definitions do not get overwritten or changed?

~Al
Parents
  • Ok so there's a few contributors to your concerns:
    1: make sure you are using one windows login, if not, you need to define the probefile into a universally accessible location like C:/PROBES/
    2: make sure ALL routines exclusively call up one of the SIX currently defined/standardized probes. if routine calls a unique probe name, when you open the edit probe menu, a new probe file will automatically be generated.
    2a: there's an excel file called listfiles.xlsm that someone created, which is a macro-enabled excel file... you define the folder in which all your routines are stored in, and it will populate a list of ALL the probes and probe angles used in each routine. You can use this to audit which routines need probe file names corrected. I've attached it, as i can't find it on the forum anymore. rename the PDF suffix to XLSM for it to work.

    3: as stated above, you'd need to have the probe files and probe calibration results exclusively executed and maintained with your oldest rev software. the probe racks will likely need to be defined and calibrated for each software version, unless i'm mistaken here and you can call up a common directory for probe rack calibration.
    3a: you of course need to have all three software versions point to the one common probe file directory.
Reply
  • Ok so there's a few contributors to your concerns:
    1: make sure you are using one windows login, if not, you need to define the probefile into a universally accessible location like C:/PROBES/
    2: make sure ALL routines exclusively call up one of the SIX currently defined/standardized probes. if routine calls a unique probe name, when you open the edit probe menu, a new probe file will automatically be generated.
    2a: there's an excel file called listfiles.xlsm that someone created, which is a macro-enabled excel file... you define the folder in which all your routines are stored in, and it will populate a list of ALL the probes and probe angles used in each routine. You can use this to audit which routines need probe file names corrected. I've attached it, as i can't find it on the forum anymore. rename the PDF suffix to XLSM for it to work.

    3: as stated above, you'd need to have the probe files and probe calibration results exclusively executed and maintained with your oldest rev software. the probe racks will likely need to be defined and calibrated for each software version, unless i'm mistaken here and you can call up a common directory for probe rack calibration.
    3a: you of course need to have all three software versions point to the one common probe file directory.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement