Broken Probe Tip Mystery

[angerji]

Good Morning,

I sat down at our CMM today for the first time after having a few days off of work, only to find the shaft on the 0.5mm ruby tip probe had been snapped off. Does anyone know of a creative way to be able to tell when this might of happened? Does pc-dmis have any kind of log it keeps showing when the machine physically crashes?

[A-machine-insp]

Was the probe loaded on the machine when you came in? If it was, I'd safely assume it happened on the last program ran. I don't know of a log that DMIS keeps of crashes although it would be nice to have.

[Mike Ruff]

I'm honestly not sure, I only have it on the desktop of one CMM computer, so I can just double-click it from there. I was trying to get it on the other CMMs a while back to help track down crashes, but I couldn't figure out where to get it from. Someone else hopefully knows where to get it

[Mike Ruff]

UPDATE:

On my computer, the FDCPanelApp is located in the C:\FDCPanel folder. It is in the same location on the other CMM computer but it only seems to be working on my CMM, not both. Within this folder there are 4 files: FdcDriver.dll, FDCPanel.dll, FDCPanelApp.config, and FDCPanelApp.exe. I don't have time today, but I'm guessing the config is the key to getting it to work on the other CMM.

[angerji]

I have an H3C Panel app on my CMM PC, no idea what thats for or if its the same thing?

[angerji]

Was the probe loaded on the machine when you came in? If it was, I'd safely assume it happened on the last program ran. I don't know of a log that DMIS keeps of crashes although it would be nice to have.

No the probe was on the rack. The strange thing is the last program that was run does not even use that probe.

[Paperback Rocker]

Look at the last program run with that tip. If the data is good, it got broken afterward.

If the data goes bad part way through the run, the tip broke then.