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

Calibrating Multiple Tips

MrCMM
I have calibrated multiple tip angles to work together with the calibration sphere in the same position for all the tips. There is one tip angle (A90B180) that is out .005" in the Y axis from all the other tips. I've tried recalibrating them several times but I still get the same results. Does anyone have a solution for this? Thanks!
  • Tips in PC DMIS work off of a MASTER/SLAVE relationship

    That said..

    You need to qualify one tip angle as your MASTER and all subsequent tips & their angles as SLAVES

    To do this in PC DMIS:

    -Pick astubby/fat probe..people usually use 4X20 or something similar. We'll use 4X20 for this example. Qualify A0B0 of 4X20 by saying YES the sphere has moved. This makes A0B0 of your 4X20 your MASTER
    -Qualify all OTHER tip angles of your 4X20 by saying NO sphere has not moved. This makes these angles slaves to the master
    -Qualify all other tip angles of all other probe builds by saying NO sphere has not moved. This makes these tips & their angles slaves to the master

    If this doesn't solve your problem, check back & we'll dig further. You may have to edit some touchspeeds, play with your F5 settings (display absolute speeds)...or may have a flat on your ball and/or sphere
  • Have you tried 'Reset Tips to Theo'? Sometimes you have to clear the old data to eliminate those offsets. (shouldn't have to, but happens)
  • Are you using collision detection during calibration?

    There is a known issue with this and I'm still waiting on a fix.

    If you calibrate a probe saying yes sphere has moved (with multiple tips selected) then you will get incorrect offsets for the second tip calibrated.

    If you want to use collision detection, then calibrate Master probe-tip (typically A0B0) first saying Yes sphere has moved (Don't use collision detection here - there's no need anyway).

    Then select all your other tips and say No Sphere has not moved - you should now be able to use the collision detection.



  • Are you using collision detection during calibration?

    There is a known issue with this and I'm still waiting on a fix.

    If you calibrate a probe saying yes sphere has moved (with multiple tips selected) then you will get incorrect offsets for the second tip calibrated.

    If you want to use collision detection, then calibrate Master probe-tip (typically A0B0) first saying Yes sphere has moved (Don't use collision detection here - there's no need anyway).

    Then select all your other tips and say No Sphere has not moved - you should now be able to use the collision detection.





    link to said know issue please. all of our parameter sets use collision detection and we calibrate probes daily.


  • link to said know issue please. all of our parameter sets use collision detection and we calibrate probes daily.

    I don't think I can link to is as such - it's on our internal system.

    However AFAIK my description of the issue is valid, as is the workaround (calibrate Master probe-tip on it's own so PC-Dmis knows where the reference sphere is) then it can do the collision detection and generate the correct offsets.

    A lot of people don't see this issue as this is the workflow they employ anyway.



  • I don't think I can link to is as such - it's on our internal system.

    However AFAIK my description of the issue is valid, as is the workaround (calibrate Master probe-tip on it's own so PC-Dmis knows where the reference sphere is) then it can do the collision detection and generate the correct offsets.

    A lot of people don't see this issue as this is the workflow they employ anyway.



    All of our parameter sets have collision detection on. We use collision detection because we have a 7-10-7 and there is a risk of the probes striking the leg during angle rotation while calibrating. Probes have been broken in the past due to the styli striking the leg and this is why we now have it defaulted to on. Do we need to run the master probe every time we calibrate to avoid any issues?



  • All of our parameter sets have collision detection on. We use collision detection because we have a 7-10-7 and there is a risk of the probes striking the leg during angle rotation while calibrating. Probes have been broken in the past due to the styli striking the leg and this is why we now have it defaulted to on. Do we need to run the master probe every time we calibrate to avoid any issues?

    {"data-align":"none","data-size":"full","data-attachmentid":536657}

    If you select "User defined calibration order" and save it as a Parameter Set, you can probably avoid this. My Parameter sets start with greatest -B angle and rotate around to greatest +B angle.


  • If you select "User defined calibration order" and save it as a Parameter Set, you can probably avoid this. My Parameter sets start with greatest -B angle and rotate around to greatest +B angle.

    We have different sized cmms across 3 states so programs run on the 1st open CMM that has the volume for the part. using the user defined command is just not feasible since collision detection makes the necessary changes. kind of frustrating that this is a know issue and is not made public with a bulletin, makes you wonder what else is going on that we as users are not being made aware of.


  • All of our parameter sets have collision detection on. We use collision detection because we have a 7-10-7 and there is a risk of the probes striking the leg during angle rotation while calibrating. Probes have been broken in the past due to the styli striking the leg and this is why we now have it defaulted to on. Do we need to run the master probe every time we calibrate to avoid any issues?

    {"data-align":"none","data-size":"full","data-attachmentid":536657}

    This should be fine, the issue only happens when the master probe-tip is calibrated at the same time as other tip angles (of the master probe) - like literally selecting several angles at one time.

    From your parameter set names I see you're just doing A0B0 of the master probe on it's own, then doing other probes, so you should be fine.

  • in reply to DAN_M

    I love finding an answer to my question without asking it. Thank you, Dan.

© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement