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

qual. tool locations not updating (v3.7 MR3)

probetip
I'm using v3.7 mr3. I qualify on a 1" sphere, "yes" to has it moved. This updates that spheres XYZ definition.
I switch probe configurations, select the same sphere, "no" it hasn't moved. The spheres' definition is not the same as after the first qualify, so the probe heads for an old location. This is a new trick, hasn't given me any trouble before. I tried adding a new "tool". This fixes the problem, but only once. For now,
I have to add a new tool (deleting some old ones) each time I start. What up?
  • This is happening b/c PC-DMIS attaches the position of the Qualification Tool to the probe you are calibrating. Whenever you make a new probe assembly you have to update the qualification tools position manually. This works the same way when qualifying probes that you have already made, when you update the position of one manually, it does not update the others.
  • Thanks. Where do I access the qual tool position that is stored? The only place I see it is in the measure window
    where you select the tool to be used. Its XYZ values are grayed out.
  • I don't believe what cappy said to be true unless I've misunderstood him.

    The qual tool position is stored in the tool.dat file (you can't open it to view it however)

    You can use assignments and expressions to get the xyz location of the tool (look up QUALTOOLDATA in the help)

    If your probe's going to the wrong place it would appear as if the xyz offsets for the tips are incorrect - when you create a new probe file the xyz offset for each tip are to nominal - after qualification they will be updated with the measured values.

    so if I built a probe up 4by40 (in pc-dmis) but actually built it up to 4by50 then qualified it manually, it wouldn't matter it was 10mm out it know where the centre of the tip was.

    It sounds as if your probe file's getting corrupted, or you don't have user rights to the directories for either your probe(s) or the tool.dat file.


    So...

    1) Check where the system thinks the qual tool is using the qualtooldata functions and see if this agrees with the tools position on your CMM

    2) Check what measured offsets you are getting for your tips (click on a tip-angle in the probe utilities window and click the edit button)
  • are you sure ninjabadger?

    I'm almost positive that it doesn't update the tool position for all probes. I've Calibrated a probe, changed to another and hit "no, it has not moved" and it went to the old qualification tool position
  • If you have more than one calibration tool stored pcdmis will default to the last one used by that probe.
    You have to change the tool to be used in the probe file.
    You cannot edit a defined calibration tool or you loose all the results relative to that tool.
    The calibration tool data is common across all probes that use that tool.
  • are you sure ninjabadger?

    I'm almost positive that it doesn't update the tool position for all probes. I've Calibrated a probe, changed to another and hit "no, it has not moved" and it went to the old qualification tool position

    Cappy,
    They are correct.

    Everybody,
    Name your qual sphere tools with obviously unique names (letters, numbers, underscores only)

    Then when you go to calibrate, make sure the correct tool is selected.

    Also, if you're running Windows 7 make double extra sure you've got full admin rights and are running PC-DMIS As Administrator. Otherwise it won't save diddly-squat.
  • Also, if you're running Windows 7 make double extra sure you've got full admin rights and are running PC-DMIS As Administrator. Otherwise it won't save diddly-squat.

    You don't need to be an administrator to run PC-DMIS on Windows 7, and you don't need "Run as Administrator". Tool.dat is stored in C:\ProgramData\WAI\PC-DMIS\2011, so check your permissions in that folder (and have an administrator give you permissions there if you don't have it).
  • Thanks to everyone for your answers. Here I go into "shoulda" land. When you say that a given tool has moved, the system uses the current
    probe offset lengths as is, and updates the tool.xyz in the stored file. When you switch probes, and try to qualify on the "just established"
    tool, that tools location SHOULD BE being read from the file and used to update the probe offsets of the new probe.
    It SHOULDNT matter how many tools you have, or what you named them, they are all stored in tool.dat to be accessed or updated
    depending on whether you select YES tool has moved or NO tool has not moved.
    Or am I getting signals thru my tin foil hat?
  • Thanks to everyone for your answers. Here I go into "shoulda" land. When you say that a given tool has moved, the system uses the current
    probe offset lengths as is, and updates the tool.xyz in the stored file. When you switch probes, and try to qualify on the "just established"
    tool, that tools location SHOULD BE being read from the file and used to update the probe offsets of the new probe.
    It SHOULDNT matter how many tools you have, or what you named them, they are all stored in tool.dat to be accessed or updated
    depending on whether you select YES tool has moved or NO tool has not moved.
    Or am I getting signals thru my tin foil hat?

    Signals are correct.

    Although files do go corrupt...
  • Probetip in Michigan
    What version of Windows are you running this 3.7 on?


    You don't need to be an administrator to run PC-DMIS on Windows 7, and you don't need "Run as Administrator". Tool.dat is stored in C:\ProgramData\WAI\PC-DMIS\2011, so check your permissions in that folder (and have an administrator give you permissions there if you don't have it).

    True, but as you posted in an earlier thread it depends upon "if PC-DMIS is properly installed", which entails right-click-Run-As-Administrator the first time you run it on Windows 7.

    If that didn't happen, the user must right-click-Run-As-Administrator every time they run PC-DMIS on Windows 7.

    Working with a customer right now who is having a similiar issue, but with 2011 MR1.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement