Quit while scanning

[PowerJunkie]

I'm doing a scan on a part and the machine keeps going offline (Machine Start light goes out and the lights on the Probe Head Controller go out).

The program scans the part in 8 sections on 2 dia's to acquire total runout. Friday I started the program and it would run through the first 2 sections then it kept going out as described above. This morning I fired up the CMM and program and it ran through 6 sections of the scan before quitting.

To get everything running again, I have to restart both the CMM at the control box and PCDMIS.

Is there anything I can do to fix this? Should I get a service person out here?

-Global Image 7107 / SP600 / PCDMIS 4.2 MR1

[JamesMannes]

I'm doing a scan on a part and the machine keeps going offline (Machine Start light goes out and the lights on the Probe Head Controller go out).

The program scans the part in 8 sections on 2 dia's to acquire total runout. Friday I started the program and it would run through the first 2 sections then it kept going out as described above. This morning I fired up the CMM and program and it ran through 6 sections of the scan before quitting.

To get everything running again, I have to restart both the CMM at the control box and PCDMIS.

Is there anything I can do to fix this? Should I get a service person out here?

-Global Image 7107 / SP600 / PCDMIS 4.2 MR1

That is not a service type thing. I think it is a settings type of problem. The settings for scanning are numerous. To brainstorm the issue will be a hard via the forum but I'll try. Can you post your code? Also post an example of your settings (PARAMETERS>OPTIONAL PROBE SETTINGS).

As a side note this could be caused by parts that are not real close to nominal.

[PowerJunkie]

Thanks, any help will be very much appreciated!! Files attached.

[JamesMannes]

Try theses settings once and see what kind results you get. These area stock default settings frommthe scanning handbook.

GO HERE for the scanning powerpoint.

[PowerJunkie]

James, thank you for your suggestion. I changed the Opt.Probe settings but still no dice.
The only thing I can think of that has 'changed' is an upgrade from 3.7 to 4.2 since the parts have last been run and it's always run fine. Now it just quits in random areas.

[JamesMannes]

James, thank you for your suggestion. I changed the Opt.Probe settings but still no dice.
The only thing I can think of that has 'changed' is an upgrade from 3.7 to 4.2 since the parts have last been run and it's always run fine. Now it just quits in random areas.

Sorry, didn't see the 4.2 thing(or maybe I did?). Have you F9'd the scan and regenerated it at all? That might do it. It's hard to pin down a scanning problem via a text type of format.