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

LSP X1h + 2015.0 / 2015.1 = no go?

vpt.se
For anyone out there with an LSP X1h and are using 2015.0 or 2015.1:
Experienced any problems with calibrating your probes?

Example:

For the first two probes below, I have answered YES to the question if the tool has moved (only way in order to get values that matches the THEOs): 
T1A-5B-15      TEO X  -1.5046 Y  -5.6152 Z 284.6301 D 5.0000
T1A-5B-15      SNABB X  -1.4635 Y  -5.5247 Z 284.6052 D 5.0000 PrbRdv 0.0035
T1A-5B-15      MÄTT X  -1.4635 Y  -5.5248 Z 284.6044 D 5.0000 PrbRdv-0.0012 StdDev 0.0004

T1A0B0         TEO X   0.0000 Y  12.0000 Z 284.3600 D 5.0000
T1A0B0         SNABB X   0.0016 Y  11.9994 Z 284.3585 D 5.0000 PrbRdv 0.0031
T1A0B0         MÄTT X   0.0014 Y  11.9994 Z 284.3579 D 5.0000 PrbRdv-0.0017 StdDev 0.0004

T1A-90B-90     TEO X-203.8600 Y  -0.0000 Z  92.5000 D 5.0000
T1A-90B-90     SNABB X-203.0024 Y   0.0033 Z  93.3571 D 5.0000 PrbRdv 0.0027
T1A-90B-90     MÄTT X-203.0017 Y   0.0032 Z  93.3571 D 5.0000 PrbRdv-0.0015 StdDev 0.0005

T1A-90B90      TEO X 203.8600 Y  -0.0000 Z  92.5000 D 5.0000
T1A-90B90      SNABB X 202.5958 Y   0.4775 Z  93.2956 D 5.0000 PrbRdv 0.0034
T1A-90B90      MÄTT X 202.5957 Y   0.4776 Z  93.2956 D 5.0000 PrbRdv-0.0009 StdDev 0.0004

T1A90B-180     TEO X   0.0000 Y-203.8600 Z  68.5000 D 5.0000
T1A90B-180     SNABB X  -0.3890 Y-202.5555 Z  69.5875 D 5.0000 PrbRdv 0.0026
T1A90B-180     MÄTT X  -0.3891 Y-202.5557 Z  69.5873 D 5.0000 PrbRdv-0.0015 StdDev 0.0004

T1A90B0        TEO X   0.0000 Y 203.8600 Z  68.5000 D 5.0000
T1A90B0        SNABB X  -0.0159 Y 203.0495 Z  69.6721 D 5.0000 PrbRdv 0.0033
T1A90B0        MÄTT X  -0.0159 Y 203.0492 Z  69.6725 D 5.0000 PrbRdv-0.0015 StdDev 0.0005


The machine can't complete a DCC calibration of the angles, only A0B0... It either touches the calibration sphere or errors out giving me the "Invalid reading of measured point".

Hexagon tech tested the calibration using 2013 MR1 which passed, ie. PC-DMIS could calibrate the angles as expected so it seems that the issue is related to 2015.0 AND 2015.1. I have tried with deleting the probe files, creating new ones, creating new tool, hit/retract values, analog probe values etc., to no avail. Needless to say, machine is not fit for use in it's current state - if used together with 2015.*

Why not downgrade? Because with our CMM programs collection, backsaving is out of the question - that's why.

Anyone else seen this?
  • All credit for this finding (which was true Sherlock Holmes-style) goes to AndersI (and any additional crew he needed for it).

    I know the EULA states that you are not responsible (yada, yada...) but for the love of God...
    Looks like we have to take the fall with this one - if this error has affected our measuring results...

    Maybe I should start authoring our official "We're sorry, but..." letter to our suppliers?

    It shouldn't do, once calibrated it knows where the tip centre is.

    If you got it to qual it would be be okay, if not you wouldn't have run parts anyway.
  • It shouldn't do, once calibrated it knows where the tip centre is.

    If you got it to qual it would be be okay, if not you wouldn't have run parts anyway.

    Increasing the prehit value can make the probe pass calibration... (did not run a qualification)
  • Increasing the prehit value can make the probe pass calibration... (did not run a qualification)


    calibration and qualification are the same thing - well not really, we refer to it as probe calibration but it's technically a probe qualification.
  • This is quite odd, because we are having no length problems with 2015.0, 2015.1 and LSPX1h over here.

    However - in the past we have had problems with the incorrect Z-ram-to-Wrist adapter plate being put into the virtual probe build, which throws the lengths off.

    This is quite possible, but irrespective of which length is correct, LSPX1 H, S and M should have the same (C is different), and the change in PROBE.DAT in version 2015 only modified LSPX1H.

    If the calibration of (<0,0>, <90, 0>, <90, 180>Wink is done with the tips reset to theo, MAN+DCC, "Yes, the ball has moved", then one would suspect that the variant that actually works is the correct one (the older, longer, value in this case), wouldn't you?

    What's the story on "the incorrect Z-ram-to-Wrist adapter"? Is this another part in PROBE.DAT that has changed size? And if so, when? And what value should it have?
  • Since the issue has been found, I hope that AndersI can chime in with what to change in the PROBE.DAT in order to rectify it?

    I assume that the order is to install PC-DMIS 2015.x and then (prior to doing anything else) edit the PROBE.DAT - but to what (tech did it for us)?
  • This was only with NEW probe builds correct? I shouldn't have any problems with existing probes should I?
  • This was only with NEW probe builds correct? I shouldn't have any problems with existing probes should I?

    You shouldn't, because all offsets are known in the actual probe.
    If you select "reset to theo values", maybe you could have the problem.
  • I won't give any instructions for changing anything until I've talked to the tech that was on site, and the issue is completely sorted by Wilcox. We've made changes to probe files and probe.dat to get vpt:s system running smoothly, but that is a temporary solution - the important bit remains: to do the *correct* change(s) at the *correct* place(s).

    So far, this is what happened with unmodified PC-DMIS at this installation:

    Probe files created with PC-DMIS versions < 2015.0 work OK.
    Probe files created with PC-DMIS version 2015.0 and later give problems.
  • I won't give any instructions for changing anything until I've talked to the tech that was on site, and the issue is completely sorted by Wilcox. We've made changes to probe files and probe.dat to get vpt:s system running smoothly, but that is a temporary solution - the important bit remains: to do the *correct* change(s) at the *correct* place(s).

    So far, this is what happened with unmodified PC-DMIS at this installation:

    Probe files created with PC-DMIS versions < 2015.0 work OK.
    Probe files created with PC-DMIS version 2015.0 and later give problems.


    Thank you
  • Well, well, well.
    It is the PROBE.DAT

    Everyone reading this: to reinforce Ander's point: don't modify PROBE.DAT unless you know you have a problem and you know what you are doing.

    JIRA #PCD-95436 by Anders
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement