Guest
Show Posts
1
VB and the development of wizards / M6Start macro problem
« on: March 22, 2022, 09:30:00 AM »
Hi guys,
I see here many of us have some sort of problems with ATC macro. Well, I am not exception neither.
We are now finishing retrofit on Hurco MB1 CNC mill that has 18 tool changer powered by "geneva" mechanism.
My ATC VB code raised a bit by now but I have strange behavior on bare beginning of my macro where it stuck when I call code "G53 G0 Z-104". Z axe do not move at all and macro stuck in While IsMoving loop.
This happens only after referencing axes. If I do E-stop reset after referencing, macro will work errorless but if I reference again for eg. only Z axe macro stuck at the same place.
At the same time if I type "G53 G0 Z-104" on MDI line Z axe moves no matter of referencing nor E-stop. It's a strange and it looks like referencing leave some variable or some motion mode active so it interrupt motion call from M6 macro.
If I do E-stop after ref., machine is capable of doing relatively complex G code including multiple tool changes without any problem.
I do not have my macro code here yet to share, but its beginning is fairly simple down to the point where it usually stuck. I can share it later.
Is there any idea what can cause this like problem.
Regards and thanks in advance.
I see here many of us have some sort of problems with ATC macro. Well, I am not exception neither.
We are now finishing retrofit on Hurco MB1 CNC mill that has 18 tool changer powered by "geneva" mechanism.
My ATC VB code raised a bit by now but I have strange behavior on bare beginning of my macro where it stuck when I call code "G53 G0 Z-104". Z axe do not move at all and macro stuck in While IsMoving loop.
This happens only after referencing axes. If I do E-stop reset after referencing, macro will work errorless but if I reference again for eg. only Z axe macro stuck at the same place.
At the same time if I type "G53 G0 Z-104" on MDI line Z axe moves no matter of referencing nor E-stop. It's a strange and it looks like referencing leave some variable or some motion mode active so it interrupt motion call from M6 macro.
If I do E-stop after ref., machine is capable of doing relatively complex G code including multiple tool changes without any problem.
I do not have my macro code here yet to share, but its beginning is fairly simple down to the point where it usually stuck. I can share it later.
Is there any idea what can cause this like problem.
Regards and thanks in advance.