hexagon logo
Register Sign in
  • Replies 56 replies
  • Subscribers 222 subscribers
  • Views 546 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?
Parents
  • Is the "invalid reading of measured point" a PCDMIS error or a controller error? What controller are you using?

    PC-DMIS gives the error message, I assume the controller tells it that it can't calculate the measured point. It's an FDC.

    Can you explain what you mean here?

    Calibrating the A0B0 (and telling it that the tool has moved) gives me measured values that is close to the THEO probe values.
    Calibrating ANY angle after this (answer NO to the question that the tool has moved) will result in MEAS values pretty far off compared to the THEO's.
    Calibrating ANY angle after A0B0 AND telling that the tool has moved, will yield MEAS results close to THEO's, but I lose the relationship to A0B0.

    Have you compared the probe parameters at the controller and registry settings between the two versions?

    This is over my head. The webinterface to the controller is password-protected. The Hexagon tech has transferred the working settings from 2013 MR1 to 2015.x but it still doesn't work. Using a different computer (Hexagon techs) with 2015.x yields the same results, but works fine with 2013 MR1.

    This case is now being actively pursued by the nordic branch support, but I wanted to try all venues since we can't trust the results in it's current state.
Reply
  • Is the "invalid reading of measured point" a PCDMIS error or a controller error? What controller are you using?

    PC-DMIS gives the error message, I assume the controller tells it that it can't calculate the measured point. It's an FDC.

    Can you explain what you mean here?

    Calibrating the A0B0 (and telling it that the tool has moved) gives me measured values that is close to the THEO probe values.
    Calibrating ANY angle after this (answer NO to the question that the tool has moved) will result in MEAS values pretty far off compared to the THEO's.
    Calibrating ANY angle after A0B0 AND telling that the tool has moved, will yield MEAS results close to THEO's, but I lose the relationship to A0B0.

    Have you compared the probe parameters at the controller and registry settings between the two versions?

    This is over my head. The webinterface to the controller is password-protected. The Hexagon tech has transferred the working settings from 2013 MR1 to 2015.x but it still doesn't work. Using a different computer (Hexagon techs) with 2015.x yields the same results, but works fine with 2013 MR1.

    This case is now being actively pursued by the nordic branch support, but I wanted to try all venues since we can't trust the results in it's current state.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement