hexagon logo
Register Sign in
  • Replies 56 replies
  • Subscribers 222 subscribers
  • Views 553 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?
  • I should've added I am using 2015.0 SP2.

    Are you using parameter sets? What cal settings are you using? Have you performed a lower matrix?

    I saw, when I tried a few hours 2015.1 that parameter set disappear...

    @ VPT.SE : maybe you could try to say that you have a LSPX1-S, and configure it whit H values ? There are not too different...
    You could also choose (I'm not at the cmm to check it) that you have a HP-S-X1H (it's only a new name, but in a traduction, it could become a bug !!!!!)
  • I should've added I am using 2015.0 SP2.

    Are you using parameter sets? What cal settings are you using? Have you performed a lower matrix?

    No.
    "Standard" settings (ie. default, I believe).
    No. Sounds dangerous.


    IF you're saying the sphere has moved then the MEAS should be exactly the same as the THEO, or should not change from the previous offsets at any rate.

    I'm assuming from looking at the results you previously qualified this probe answering 'No' to the 'Has Sphere moved' question (after defining the reference sphere position with a different (master) probe)?

    I have answered YES to the tool has been moved for the A0B0 and then calibrated other angles (same probe). When I noticed that the A15B0 differed that much, I answered YES to the tool has been moved for that one as well, then calibrating the other angles trying to find why it differed. New tool.dat, new probefiles...

    I saw, when I tried a few hours 2015.1 that parameter set disappear...

    @ VPT.SE : maybe you could try to say that you have a LSPX1-S, and configure it whit H values ? There are not too different...
    You could also choose (I'm not at the cmm to check it) that you have a HP-S-X1H (it's only a new name, but in a traduction, it could become a bug !!!!!)

    Possibly!

    Regardless, this is a new machine, the only versions that has been installed are 2015.0 + SP1 and 2015.1 + SP1. It is equipped with two proberacks, one for the CWS/CMM-V/X1h and one for the hard styluses. I suspect that the machine has been this way all along, I noticed it by chance. I presume that the tech has gone through whatever they suspect in order to remedy the problem. From a laymans point of view, it seems to boil down to either a 2015.* error OR something in the controller/machine.
  • I think I'd perform a lower matrix and then re-cal.

    Have you checked your master probe to see if the glue has come loose? Everything is tight? This has happened
  • I think I'd perform a lower matrix and then re-cal.

    Have you checked your master probe to see if the glue has come loose? Everything is tight? This has happened

    Checked all probes, LSP discs...
  • Install 2013 and try that - if it works it's a 2015 issue, if not then it's hardware or a setting.
  • Ninja> Why wouldn't you attempt a lower matrix first?

    I run the same set-up and I am not seeing any issues at all. I perform Lower Matrix after software changes / updates and hard crashes IF they were to occur (knocking on wood)
  • Ninja> Why wouldn't you attempt a lower matrix first?

    I run the same set-up and I am not seeing any issues at all. I perform Lower Matrix after software changes / updates and hard crashes IF they were to occur (knocking on wood)


    Lower matrix is stored in the controller - if a tech has performed successful qual using different PC nd 2013 it suggest to me it's not the lower matrix.
  • Lower matrix is stored in the controller - if a tech has performed successful qual using different PC nd 2013 it suggest to me it's not the lower matrix.


    That I can agree on


    However....

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



    So if a lower was performed using 2013 and cal was successful using 2013 why not lower matrix 2015 and cal using 2015?
    IMO it's worth a shot.
  • That I can agree on


    However....




    So if a lower was performed using 2013 and cal was successful using 2013 why not lower matrix 2015 and cal using 2015?


    From what he said the lower matrix wasn't performed in 2013 either (i.e the one existing on the controller worked for 2013).

    I'm not suggesting 2013 as a solution, but a trouble shooting step.
  • He also stated downgrading is not an option. I'm not afraid of lower matrix and have been performing them since my Sp600 days, didn't need 'em with the SP25 but now that I am on a machine with a LSPX1H I am back to using them. I don't do lower matrix frequently but if something is turning out awry on my cal results it's on the very top of my trouble shooting list. It only takes a few minutes, it's worth a shot IMO
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement