Jump to content

CARNAGE!


---
 Share

Recommended Posts

Edit: I put this in the wrong forum...

No. The probe is no miss loaded. It's not an illusion. That is an integrated cube stylus system so the styli should be in line with the machine axes....

This is how damaged an XXT head got today at our facility. The internals of the head are rotated that much.

Nobody knows what happened. They swear it wasn't crashed or man handled...

I was called because it wouldn't pick up probes from the rack.....

PXL_20230301_213823395.MP.jpg

Link to comment
Share on other sites

I've heard this many times:
....Nobody knows what happened. They swear it wasn't crashed or man-handled...

Here's a tip to find out if the problem was natural or if aliens landed....

Tip for the alien hunters
What was the very last measurement plan that was started with which settings?
Check the setting:
Extras/Settings/Environment/Paths/Default path for measurement plans
Go to this folder:
Example:
C:\Users\Public\Documents\Zeiss\CALYPSO 7.x\Workspace\Inspections\
Look for the file "startfile"
Open "startfile" with an editor
Then you can see all the details of the very last measurement plan:

Example: That was my very last measurement plan
operid ==> natural or aliens?


activeTechnology ***
baseSystemRealName Lagerbock_RevD 5
baseSystemType baseSystem
calExport false
clearOldRes true
compactProtocol false
displayPlots true
equatorMode masterMode
featureListName All Characteristics
measForASE false
meMode cf
motionPlanning false
naviMode automatic
pdfExport false
presProtocol false
printer false
printPlots false
protNumbers 1
protocolDefinition default_PR1
protocolHead true
psExport false
ptxExport false
recheckMode false
recheckModeInspection nil
runMode slowToFirst
selection complete
skipExecuteCFs false
speed 300
subSeqEval false
creationdate February 28, 2023 11:58:16 AM
creationdme PRISMO_USS2
creationswi 7.5.0042
creationTimestamp 3855038296
date 2023-2-28
dateandtime February 28, 2023 12:02:46 PM
datedayofmonth 28
datemonthindex 2
datesecondclock 3855034966
datestring February 28, 2023
dateyear 2023
devicegroup Simulation
dmeid PRISMO_USS2
dmesn 000000
nameOfFile C:\Users\Public\Documents\Zeiss\CALYPSO 7.6\workarea\inspections\Lagerbock_RevD 5
operid G.Haas
partnbinc 1
partnbpre 1
planid Lagerbock_RevD 5
produceoper Master
runswv 7.5.0042
time 12:02:46 PM
Link to comment
Share on other sites

Reminds me of an incident years ago. The following pic shows a probe mounted in a freshly exchanged VAST XT head. It's only one of ~50 probes and all of them looked the same. The angle meter is lying on a magnetic chuck that is perfectly aligned to the machine axes.
The tech guy who installed the head tried to imply our probes may be twisted. I asked him, do you really think that all 50 probes can be twisted by exactly 1.5 degrees?
No, the only thing twisted here was the head. No natural cause, no aliens. It had just been delivered this way - and TWICE. Because the next replacement head had the same issue.
127_acb083e1d3419c04d38d965e46cd7b9c.jpg
Link to comment
Share on other sites

Please sign in to view this quote.

.
Mike, that looks extremely frustrating. Hang in there, buddy.

I'm not sure if you're aware, but there is a utility that hardware techs access that shows all collision activity, no matter how minor. It tracks impact force, vector of the machine during the crash, time and date and other goodies. The graph that this utility generates is useful.

Also, consider the human element. Keep in mind that someone may feel scared shitless right now that they're going to lose their job if someone finds out. I try to communicate with my coworkers that if a collision occurs on their watch, they have total safety to communicate openly about it. I also mention that they don't have to disclose this information in front of the group but that they can do so confidentially.
.
Link to comment
Share on other sites

Open communication is always good. Something can always happen at work

The program for real-time monitoring and analysis of important data
can be found here:
https://www.zeiss.de/messtechnik/servic ... itaet.html

If you want to check when the collision could have happened without the Smart Service app:
As described, search for the last measurement run. Check whether the measured values are in the reporting database. If no, something happened during the CNC run. If so, something happened after the last CNC run

But as I said: something can always happen when working. (I've already smashed a VAST probe head myself while programming...)
Link to comment
Share on other sites

Please sign in to view this quote.

Yes that software has been fantastic in showing problems and helping us slowly find the causes and fix them. CMMs are treated like gauges here training is "The CMM is over there, go load your part, there's a photo that will tell you how"....

In this case it was actually some of our more experienced inspectors trying to calibrate the machine... something went very wrong.
Link to comment
Share on other sites

Please sign in to view this quote.

I am currently trying to get out IT to allow PowerShell so I can finish the installation of the free version of that software on this very machine so we can see how it works and hopefully buy it for other machines. It looks VERY handy.
Link to comment
Share on other sites

Hi Michael,

Yes, I hope Smart service will provide you all necessary data.

I try do get it run but it seemed to need an extra activation of a menue at your "Zeiss Portal" account. Second you need a certificate generated by Zeiss. At the moment I do not know where to get it.
Technical description ( great detailed 😃 ) you can find here:
https://portal.zeiss.com/download-cente ... tware/9597

Best regards
Karsten
Link to comment
Share on other sites

Please sign in to view this quote.

I'm pretty sure I have everything I need from Zeiss, I went through that process to get 2 machines setup.

I'm just waiting for IT on my end to enable Powershell as it's apparently required for the install.
Link to comment
Share on other sites

This is great, but the functionality per machine has already existed for years. Zeiss refined and packaged it as an add-on product.
Link to comment
Share on other sites

  • 4 weeks later...

Please sign in to view this quote.

Yeah, it is pretty frustrating something as basic as collision history is hidden behind a paywall. I just want to be able to see collision history on my machines for troubleshooting purposes and to occasionally make sure I don't have bigger problems but there does not appear to be a simple/free way to do that.
Link to comment
Share on other sites

 Share

×
×
  • Create New...