hexagon logo
Register Sign in
  • Replies 2 replies
  • Subscribers 15 subscribers
  • Views 102 views
  • Users 0 members are here
Options
Related

DMEError_485

dsmith8532
Hello, all. I am having an issue on a Global HTA when there is a probe check on the calibration sphere, the machine stops and throws a DMEError_485. This happens at both calibration and also when it does a probe check on the sphere about every 6th part. I'm not sure what this is and the QuindosErrorLog states:

DMEXeEngine-485 S%7 DMEError_485 Specific DME error message not found - "Failed to approach start point or unsupported ScanMode : 0"

I tried to re-learn the probes but it doesn't seem to have helped. Has anyone come across this problem?
Parents
  • Thank you for the reply, I think I may have discovered and solved the issue.

    When the SR0 probe scans the calibration sphere during probe checks between parts and/or calibration, it makes two passes around the sphere for all four probes. On the second pass for SR0, it moves in front of the sphere and then makes a short move in the +X direction before moving -X again to approach the sphere for scanning. It was at this point the probe would stop and the error would trigger.

    I ended up rotating the calibration sphere slightly clockwise to allow for more travel in the +X direction because that axis was very close to being maxed out and I think it occasionally was maxing out it's travel during the second scan pass when approaching the sphere. Since making this adjustment, we have had no further issues with this error. Fingers crossed.
Reply
  • Thank you for the reply, I think I may have discovered and solved the issue.

    When the SR0 probe scans the calibration sphere during probe checks between parts and/or calibration, it makes two passes around the sphere for all four probes. On the second pass for SR0, it moves in front of the sphere and then makes a short move in the +X direction before moving -X again to approach the sphere for scanning. It was at this point the probe would stop and the error would trigger.

    I ended up rotating the calibration sphere slightly clockwise to allow for more travel in the +X direction because that axis was very close to being maxed out and I think it occasionally was maxing out it's travel during the second scan pass when approaching the sphere. Since making this adjustment, we have had no further issues with this error. Fingers crossed.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement