Strange problem: goes exact mode after mdi

[lfleiva]

Hi!
I have this really strange problem that I've never noticed before.
I am running a code. I stop the run by either by pressing single step or hold buttons.  Make a G00 move in MDI.  Resume the program with Cycle Start and ....
the program resumes moving as if it was in Exact Stop mode!!  Status shows G64 (CV) but movement is as it would be in Exact Stop mode.

If I change to G61 and back again to G64 everything stays the same. I would need to rewind the program and rerun to get to CV movement again.

Right now I have every CV option in General config unchecked: (plasma mode, distance and angle options)

Any ideas of what could be happening ?
Thanks,
Luis

[Hood]

If you use Single block then I think it will go to ES but using feedhold only should not do that. Can you attach your xml and some code that it happens with and I will see if I can see a problem.
Hood

[lfleiva]

This is the code and the xml.
To be clear on what I am doing is the following:
1. Start the program (runs in CV mode)
2. Press hold and stop or single step to stop movement.
3. Go to MDI and run G0 X0Y0Z0
4. Hit Cycle Start again
5. The movement resumes but moves as in Exact Stop mode.

I am noticing now also that I am not getting the preparational move screen. Shouldn't I?

Luis

[Hood]

Think you will only get the prep move box if you do a RFH.
Will go look see if I can at least replicate with your xml.
Hood

[Hood]

Sorry, can you also attach the brain or macropump that you use for the oemtriggers.
Hood

[Hood]

You also have a very funny setup for soft limits, you have huge Home Off values,
why do you have them and why so big?
What size is the machines axis travels?
You seem to have the jogging keys (keyboard) configured the opposite of normal, this may be intentional but just wondering?
Hood

[derekbpcnc]

I occasionally get drop outs from CV into exact stop (ES).

I was running a small batch of parts, program ended and rewinds everything normal.
Load the next part and press start, etc.
But sometimes when pressing start, Mach is in ES, so I have to stop the prog and edit the prog header to add G64.

It tends only to happen to progs that I dont have G64 written into the start lines.

ATB
Derek

[lfleiva]

Hood,
I have answer for all your questions but I do think none of those issues have to do with what's happening.
- Limit offsets are just used to coincide Mach DROs to a mechanical dial in the machine axis.
- It is a Bridgeport mill with 18x12x5" axis travels,
"You seem to have the jogging keys (keyboard) configured the opposite of normal, this may be intentional but just wondering?" // Just changed them to have right key move table to the right (and not the tool).
- Macropump is just for forcing softlimit on. Already disabled macropump in general conf and restarted with same results.
- I also have a macro but it's used only when ref homing.

BTW, the exact stop mode entering doesn't happen if I just jog away instead of giving mdi command.

Derek, same thing even if G64 explicit is in the program.

Luis

[Hood]

I think I may have seen it happening when I tested with your xml but had to head home so will do some more testing in a bit.
Hood

[Hood]

Ok I am not sure why its happening but I do see it. The CV LED is staying lit but the feedrate DRO definitely shows a slow down.
Doing a RFH after the hold, stop, MDI seems to make it ok and I suppose really thats the way you should do it but I will see if I can get a hold of Brian and see what he has to say.
Hood