hexagon logo
Register Sign in
  • Replies 33 replies
  • Subscribers 30 subscribers
  • Views 778 views
  • Users 0 members are here
Options
Related

How To Force PCDMIS to Save Results Via Automation ?

ECOSSE
Hi All,

I have a strange problem where I have automated the tip selection to be calibrated and select these via automation.

I'm an IT guy and using PCDMIS offline to test and everything works e.g. results file gets updated etc.

When I go live on the cmm, the probe goes through the motions after my .Qualify command and calibrates all the tips, but does not update the XYZ, diameter etc to the probe tip data, or output the ProbeFileName.results file ?

Am I missing something here ?

Do I need to re-interogate some Automation feature to access the results and create my own results file ?

Or do I need to set a particular property to make dmis save the results file ?

I'm not issuing DMIS commands to the program, just using Automation with all the standard objects and properties.

Cheers,

Dougie.
  • I was just looking at the probe object. If I were going to undertake this task, I would have chosen to use .Qualify2(QualificationSettings) - did you try that as well? I'm wondering if pcdmis even knows about your SetTool if you don't use this method. Also, its the only way I see to specify all the necessary parameters (hits, levels, prehit/retract, touchspeed, etc.)

    MyQuals returns a Qualification object which you then fill.

    Set MyQuals = ActiveProbe.QualificationSettings
    MyQuals.Mode = PCD_QUALIFICATION_SETTING_MODE_DCC
    MyQuals.ExecuteMode = CALIBRATE_TIPS
    MyQuals.ToolMoved = TOOL_MOVED_ASK
    MyQuals.SetTool ThisTool
    MyQuals.UserDefinedCalibrationMode = False
    MyQuals.UserDefinedCalibrationOrder = False

    ActiveProbe.Qualify2 MyQuals

    This code only sets the qualification parameters. You then issue :-

    ActiveProbe.Qualify

    And this sets the probe in motion and calibrates all the required tips.

    I've totally bypassed this way of doing what I needed done now.


    Dougie.
  • Isn't that more or less the same as using AUTOCALIBRATE and parameter sets? Perhaps you can go that route instead?

    Parameter sets must first of all be created manually as far as I know.

    The tips are selected depending on their last calibrated date / time. (e.g. tip has not been calibrated for X minutes = add me to the list to be calibrated in this part program)

    I've got my software working now.

    I use Automation for everything bar the very last step when I use windows Api calls to display the probe utilities dialog box, I interrogate the Hwnd of the listbox in that dialog box and issue LB_SETSEL for the tips I need calibrated.

    The operator then presses Measure, Measure as normal and my software is not issuing the command.

    PC-DMIS calibrates the probes, updates the results etc as it should, I don't need to update / mess with the probe files.

    Dougie.


  • ActiveProbe.Qualify2 MyQuals

    This code only sets the qualification parameters. You then issue :-

    ActiveProbe.Qualify

    And this sets the probe in motion and calibrates all the required tips.

    Dougie.

    Ahhh - got it. Thanks.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement