hexagon logo
Register Sign in
  • Replies 18 replies
  • Subscribers 223 subscribers
  • Views 399 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.
  • Do you have a parameter set for your master probe? Do you calibrate/locate the sphere with your master probe first?

    My cal programs calibrate/locate the sphere first with the master probe in a parameter set (qualtool_moved=Yes DCC, then runs the rest of the probes using qualtool_moved=NO.

    Unless your ran the master probe before running the auto cal program.

    Maybe your probes and tip angles are referencing more than 1 master probe?
  • in reply to DJAMS
    Just be sure everyone using the machine understands the qualification process so that it doesn't happen again. Slight smile
  • in reply to HxSwartwood
    Make a real parameter set, not just 'all-tips-with-defaults' . You can have 'Reset to Theo' selected and enforce which tool (Sphere 1 as seen above) will ALWAYS be used. As and others on this forum will suggest, use a 'master probe' to define ALL tool locations in 1 shot if possible, then run the rest with qualtool_moved=no. Good luck, glad your 'reset to theo' worked! (this round)
  • do you have a parameter set for your master probe? Do you calibrate/locate the sphere with your master probe first?

    my cal programs calibrate/locate the sphere first with the master probe in a parameter set (qualtool_moved=yes dcc, then runs the rest of the probes using qualtool_moved=no.

    unless your ran the master probe before running the auto cal program.

    Maybe your probes and tip angles are referencing more than 1 master probe?

    this ^--Master Probe is not in program so this is going to go back to last time someone answered "yes" to probe has moved prompt ; the first probe /angles calibrated is master, is everyone using the same probe. We use something short 20mm and 3 or 4 mm Ruby at A0B0
  • +1 on 'Master Probe' parameter missing. I saw similar things happen in my earlier days, a fellow app eng schooled me many moons ago and have not seen any problems since. Here's a snipet of an old autocal program: 
    $$ NO,
            ====================
            SLOT 1
            ====================
            LOADPROBE/LSPX1_5X20
            TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
            AUTOCALIBRATE/PROBE, PARAMETER_SET=MASTER, QUALTOOL_MOVED=YES_DCC,
                          SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
$$ NO,
            ====================
            SLOT 2
            ====================
            LOADPROBE/LSPX1_3X50
            TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
            MOVE/POINT,NORMAL,<20.4985,15.4721,>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=3X50_TACTILE_SET updated, QUALTOOL_MOVED=NO,
                          SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
$$ NO,
            ====================
            SLOT 3
            ====================
            LOADPROBE/LSPX1_1PNT5X40
            TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
            MOVE/POINT,NORMAL,<20.4985,15.4721,>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=1PNT5X40, QUALTOOL_MOVED=NO,
                          SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO


    All probe tips are selected in order that will rotate B axis in a clockwise direction to avoid crashing into carriage beams.

    "Slot" represents garage port on probe rack.
  • in reply to Rich P
    This is exactly what we use. I accidentally grabbed a weird version of the program (old outdated one that we don't use). We do use a 4x20 probe as our master probe.
  • Yep yep.
    Sounds like it's incorrectly programmed.
    When I created our AutoCal program, I had to make sure I studied up on what the hell I was doing for a few days.
    It took some time, but quite frankly I understand the calibration procedures much better now, to the point I was able to make a program to do it automatically.
    Make sure you understand exactly the process that is needed for calibration, then take a look at your program and make sure it is programmed to do exactly that.
  • you can also add comments and if/end commands for when a probe tip exceeds the standard deviation

    I currently have the autocal repeat itself if the first run didn't pass my requirements. if it fails again, it goes to a operator commnets saying to seek help from myself or foreman to continue. Usually need the putty to clean the probe modules.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement