unwanted movement after macrostop reset

[girogiri]

Hello,
we have the following issue: if we stop a macro during the execution of a G53 movement, when the macrostopped is reset as soon as we set a Feedrate the machines moves by itself.
here is a short version of the code:

Code: Select all

exec.Code("G53 G1 F 2000 X 1000");   
while(exec.IsMoving()){}

if(exec.Ismacrostopped()){
    exec.Codesync("");
    exec.Code("F 1000");
//    exec.Codesync("F 1000");
   while(exec.IsMoving()){}
}


thanks ini advance
Giorgio

[Battwell]

you have while(exec.IsMoving()){} after the g53 line so that line will complete before the rest of the code is read.
does it still move if you rem out that line -

[girogiri]

Hello Battwell,
tanks for you kind reply.
For an easier understandig of the problem I just posted few lines of a much longer macro.
You can immagine it as part of a probing macro or an ATC macro.
We do the followig: we save the actual feedrate, set it to a lower value to do a generic movement G53, and then wait for the movement to end (I presume we should keep the While is moving instruction or the macro will execute next instruction too early)
If for some reason somebody press a software stop then we want to reset the previous feedrate. The problem is that as soon as we set the old feedrate, the machine moves at max speed in unknown directions (in our case a 300kg head rapids at 20000mm/min )
This is scaring, can you immagine if somebody gets hit by that unexpected movement by such a machine?
rgds Giorgio

[DanStory]

Sounds similar to viewtopic.php?f=3&t=3644

[girogiri]

Hi DanStory,

it is exactly the same issue but we do not use button 783.
I don't understand why you say that if you call the M6 macro from MDI it does not happen. Would you please post your M6 macro if this is not a problem for you?
We can repeat the issue every time we push STOP during a G53 as soon as we reset the "MACROSTOP" variable.
What is funny is that as soon as we reset the MACROSTOP variable with exec.codesync("") some lines of code previously skipped are then executed.
It would be usefull to have a feedback and a workaround from Csaba or Balazs

rgds Giorgio

[cncdrive]

We just debugged and fixed this issue, it will be fine in the next release.
We working hard now on finalising the release if all will go well then it will be out before Xmas, if not then in the beginning of the new Year, we will see soon.