M0 in VR Milling 5

[blatter]

Hi I am making a component on a Triac PC using VR Milling 5 that has a total of 11 tool changes and 6000+ lines.

I have to add extra clamps half way through the cycle so am using a M0 program stop. This works fine untill i want to do a restart from a point that is after the M0. if i try this it always selects the tool that was in use prior to the M0 program stop which in my case is a floating M8 tap and then trys to continue the program with the tap! if i remove the M0 all is well.
is this a Bug in VR Milling?

Paul

[Martin]

What is the version of VRMilling 5?
It may be worth updating to 5.35 if it's a older one.

https://www.website.denford.ltd.uk/suppo ... -downloads

[Denford Admin]

Yes some improvements have been made to M00 and M01 (optional stop added)
The block restart also works better in later versions

[blatter]

Hi,
i am currently using version 5.34.0.514, will upgrade to the latest and let you know the result.

i will also try using "M00" instead of "M0" to see if it makes any difference

Paul

[Denford Admin]

I'm not sure M00 will have changed from 5.34 to 5.35.
I've just tested 5.35 here: put a T2 M06 at the beginning of the program and an M00 half way through.
If I have Tool 1 currently active, then block search to a line after the M0, the first thing Block Search asks me to do is change the tool to tool 2, so this appears to be working.

Can you upload / paste the program and tell us which line you are trying to restart from...

[blatter]

Hi,

i have stripped nearly all the moves from the program leaving just the tool changes and a couple of rapids after each change. the program runs through all the moves ok

the M00 is located in line 69
if i restart at any point after it will always select T04 as that was the last tool used prior to the M00

if i restart at line 89 it loads T04 and moves to the last position prior to the M00, X90.0 Y100.0 Z30
and then on the "do you wish to run the Program" message moves straight to X23.96 Y26.14 without selecting T07

regards

Paul

[Denford Admin]

Ok, we've found the problem and it's fixed in the next version due out soon - look out for 5.37

The block search processor was reading the M00 and pausing itself, so no tools were read past the M00.

[blatter]

thanks for getting to the bottom of the problem, i did wonder if i was going slightly mad

just a thought, i had the same result when using substituting M00 with a M01. Will the release cover both

Paul

[Denford Admin]

Yes it'll fix it with M01 as well. Thanks for your patience

[Jim Reeves]

Did the M00 & M01 issue get resolved?
I am having trouble with it failing to continue, I click the green play button but it just halts.
This is in V5 5.53 running a vmc 1300.
Program has no tool changes.

[Denford Admin]

Just tried an M00 on a test-rig setup as a VMC1300 and it worked ok on my v5.54 (no related changes have been made from 5.53)
Do you get the red Program Paused status indicator at the bottom of VR Milling5 ?

Does it work if you press start straight away ? ie without opening the guard or changing mode etc..

[Jim Reeves]

Hello,
This was in the VR window, start program, it runs up to M00 & pauses, red "program paused" message appears, I click on the green start button again, green button goes grey & red pause message dissapears but program is dead. I can run it by selecting "start from line " after the M00.
I did not want this problem on real machine so I am running another job that has no M00 s. THis will run all day this week, then i'll try the job with the m00 in real.

The machine came with version 5.27 & m00 worked but real machine would not link to my pc so i upgraded to 5.53 & used the machine up grade files as well.
jim