Program will not start back until I click the continue button

[ToadC]

I have 1 program that will not start running until we click the continue button in the execute window. All other programs will start running as soon as I switch back to DCC mode. I do not know how to change it to start running as soon as I am back into DCC mode.

[jtrofatter]

Are you manually toggling between manual and DCC mode? Could you possibly share the code where the stop happens forcing you to click the continue button?

[Matthew D. Hoedeman]

what is the prompt in the execute window? There has to be a prompt.

[Schlag]

Betting 1 $ on 2 theories....You have a breakpoint in the program or an operator comment that has no text in it.

[jigars]

most possible scenario

[ToadC]

It doesn’t matter where I am in the program. If I have to switch to manual mode to take hits and then return back to DCC mode, I have to click the continue button for the program to run again.

[UKCMM]

Silly question but you are pressing the done button on the jog box after taking the manual hits.

[Schlag]

Thats what DCC mode is. The CMM is running the program. What do you mean " no matter where you are at in the program ? Are you saying the CMM is taking a bad hit or missing a feature ? Then it stops and you manually measure a feature ? Then you hit continue and the CMM takes over because DCC is still " on ". This is the way...

[ToadC]

Yes, the CMM is taking a bad hit or missing the feature. I put it in manual mode to take hits. I then put it back into auto. On my other programs the CMM will begin running the program once I put it back into auto. For some reason the program I am referring, I put it back into auto and then I have to hit continue before the program will continue to run.
What I mean by "no matter where you are in the program", it doesn't stop in the same place. It only stops if its a bad hit or missing a feature. The program was written for us.

-UKCMM, if I push the done button on the jog box it will ask me if I want to save feature with new target so I have been instructed to take the manual hits then put the program back in auto.

Thank you

[Schlag]

AUTO features will always ask that. You may be able to answer no and then check the DO NOT ASK ME AGAIN box on that. I personally hated that dialog box.

[ToadC]

First off I just want to say Thank You to everyone for taking the time to read and/or respond to the issue I am having.
I can not attach the program to help explain what is happening. We can't figure out why this program has this issue but our other programs do not. I start the program with control Q, the program runs fine until it gets to a stud or hole that is off location. I put it in manual mode to take hits. I put it back into auto. All our other programs start back at that moment. With this program I put it back in auto but I then have to hit continue. It's really not an issue other than I just like to learn everything I can.

[Matthew D. Hoedeman]

holes and/or studs. Use READ POS if you expect it to be off location beyond the prehit/retract values.

[ToadC]

Will do, thank you

[BKulpa]

What are you using for prehit / retract distances and check distance? maybe you can adjust them to find the features that are off location. Or put those auto features in remeasure mode.

[ToadC]

We use the default prehit/retract for the most part.
What we are trying to understand is why the program doesn't start back after putting it in auto. The other programs we use will.