I'm working on a project and in my initial testing I am seeing some problems with running macros repetitively.
Here's what I have,
M90001.m1s
code "G31 z-10 f35"
while IsMoving
wend
code "M3"
code "G0Z1"
M90002.m1s
code "g31 z-10 f35"
while IsMoving
wend
code "M5"
code "G0Z1"
In my tap file I setup this test
M90001
g0y1
M90002
g0y0
m30
Note, the spindle command are controlling a vacuum pickup nozzle. The test is supposed to pick up an object whit the vacuum, move to the y1 location and drop the object.
This whole process runs perfectly each time I hit Cycle Start
BUT, as a test, I set up multipass for 100 repetitions to test my just completed digitize probe. It runs fine for a few iterations. Then the motors start making more and more noise. After about 6 iterations the motors ar grinding and an start to lock up.
If I hit Estop, reset, restart, it repeats this process each time. Runs fine and then starts to grind.
Whats going on? My guess is that the PC is spending more and more resources opening and closing the Macro files robbing time from Mach3.
Anyone seen anything like this before? Would I be better of putting the scripts into buttons where disk access would not be involved?
Any Ideas?
Ted