Wrong parameters when creating a routine offline

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wrong parameters when creating a routine offline

    Hello everyone

    I have a bit of a strange problem with scanning and I hope maybe one of you guys knows the solution or gets me on the right track.

    I have 3 different machines and an offline station.
    1x Leitz PMM-C
    1x DEA Global Advantage
    1x Tigo SF
    1x Offline

    For each of these machines I have a template routine with their respective parameters saved first thing in the program. Attached you can see the template routine for the Tigo. As you can see I have the “optionprobe” command who sets the relevant offset forces.

    If I create routines on the machines with the respective template everything works fine. The scans run smoothly with the correct offset force.

    The problem appears when I create routines on the offline station. I open the template of the machine I plan to run the routine and create the routine normally. Now when I run the routine on the machine some scans use wrong offset forces. I can visibly see the probe driving too much into the part at the start of the scan and then recovers back a bit. When I evaluate the form of the scanned feature I see a deviation where the scan starts pointing into the material. Which confirms what I see when the scan starts. Going into the scan and recreate doesn’t solve this problem, only when I create the scan from scratch and delete the old one, the scan works fine.

    We use mainly 2 scan types. The basic circle scan and the linear open scan. We don’t use the adaptive scans. The problem only affects the circle scan, the linear open scan works just fine.

    Oh and one more strange thing. The problem only affects the Global and the Tigo. The Leitz machine doesn’t care.

    Do you guys have any idea why this could happen?

    Like this there is not much time saving if I have to recreate most of the scans and then go into every feature to link it to the new scan.

    Thanks in advance for your help guys
    Attached Files

  • #2
    Did you try to set option probe after loading probe ?

    Comment


    • NinjaBadger
      NinjaBadger commented
      Editing a comment
      Yeah this would be considered good practice I believe.

  • #3
    JEFMAN
    Thanks for the input!

    I will try it out once I'm at the machine and let you know.

    I never considered this being the cause. In my mind it's logical to set the option probe before as I want the calibration to use these parameters.
    Also it would be strange why linear open scans use the correct parameters.

    But I will try and let you know. It would be a really easy fix

    Comment


    • #4
      Originally posted by Aaron Baldauf View Post
      JEFMAN
      Thanks for the input!

      I will try it out once I'm at the machine and let you know.

      I never considered this being the cause. In my mind it's logical to set the option probe before as I want the calibration to use these parameters.
      Also it would be strange why linear open scans use the correct parameters.

      But I will try and let you know. It would be a really easy fix
      As I understand the calibration, PC-DMIS reads the probe loaded, then send the right parameters of calibration in the controller (there are more parameters than those in option probe : sp6mtx for each kind of probe).
      An easy way to check if it works fine is create a prog with the routine and just a auto calibration, execute it, then go in the setting editor, and lf the parameters are the right ones, or upload them from the controller.
      Are you sure to have rights enough (read / write on reg edit ?)

      Comment

      Related Topics

      Collapse

      Working...
      X