hexagon logo
Register Sign in
  • Replies 18 replies
  • Subscribers 223 subscribers
  • Views 375 views
  • Users 0 members are here
Options
Related

Autocailbration losing sphere mid calibration

HxSwartwood
Where I work we have 6 CMM's. We use the same AutoCalibrate program on every machine. It works fine on 5 of them, but on one it will run for about an hour touching the sphere and calibrating the angles we have set. Then randomly it will go out in space and try to take a hit in the air. My boss (my companies actual CMM Programmer, I'm new and still learning Slight smile ) said she has never seen anything like this. We talked with Hexagon support and they us to not reset tips to theo before the calibration and that worked until the next time we calibrated and it lost the sphere mid calibration again. They then advised us to delete all the probe files and recreate them, which I did and the same thing happened. Worked that one time and the next time lost the sphere.

Maybe someone on here has experienced this or something like this because we don't know what else to do with this machine.

The code for this autocalibrate program is just some autocalibrate commands for each tip and move points to move above the sphere to change probes. I can post the code if needed. We are using version 2014.1.
  • Have you cleaned the scales?
    Tried moving the cal sphere to a different location on the table?
    Sounds more like a hardware issue.
  • in reply to BKulpa
    Yes we have done both. We've had a tech out here for another problem with the machine and i happened to run it by him and he said it sounded more like a software/program issue lol.
  • I've seen similar thing happen to me when calibrating steep angles. What's happening to me is the probe is hitting the sphere shank when it's doing initial touches and makes the sphere look bigger than what it is. Than the machine attempts to take a hit on that bigger sphere.
    Orienting the sphere differently (with the shank pointing some other direction) fixes the problem form me after some trial and error. I hope this makes sense.
  • in reply to Nano Vujkovic
    I don't believe we've tried this I'll give it a go.
    Thanks!
  • Someone is not following proper procedure when qualifying tips . If you know the tipname of the one that is going out in left field. Reset just that tip to theo. You may have more to come as you proceed through the program. Might be better to reset them all, and educate everyone on proper procedure.
  • Other than this standard calibration, do you see any information at the faulty workstation that someone is incorrectly qualifing a single or 2 angles? All angles are tethered to a single auto-cal proceedure? As in 1 tool, 1 prompt, all the angles you are trying to qualify? It may not be a bad idea to post the code excerpt... Look in your probe directory for the .results for that particular probe and see if it shows a different date set than the other stored data. Good luck! Rebuilding the probe and angle and parameter sets worked for me when similar happened a few years ago.
  • in reply to R2ah1ze1l
    Have you tried cycling this 'program' in offline mode? You could then go and look at the data for your specific tip and see what stands out different than with any of your angles that run through properly. (Ruby size is off, XYZ position is off,etc...)
  • in reply to DJAMS
    I just reset the tips to theo and i will see how it works out.
    Thanks!
  • Here you go had to remove the summary or it would be way too long. But i ran the program offline and everything looked just fine. The results files are fine as well. 
    STARTUP =ALIGNMENT/START,RECALL:USE_PART_SETUP,LIST=YES
ALIGNMENT/END
MODE/MANUAL
FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
MOVESPEED/ 100
LOADPROBE/S6-3X70MM
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=NO,
Use SPHERE 1
Marked on actual sphere.
Select Sphere 1 from probe utilities box.
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
MODE/DCC
MOVE/POINT,NORMAL,<231.857,410.598,-271.801>
LOADPROBE/S5-4X110MM
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=YES
MOVE/POINT,NORMAL,<231.857,410.598,-271.801>
LOADPROBE/S2-2X70MM
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=YES
MOVE/POINT,NORMAL,<231.857,410.598,-271.801>
  • in reply to DJAMS
    Seems that resetting the tips was the way to go. Hasn't stopped yet and went past the first probe where it usually stops.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement