Greetings,

I turn on the router, then I start the g-code from Mach 3.

The Z axis moves, then the whole rig trips offline.

If, I start the g-code, then let the z axis run, and THEN turn on the router, the program runs fine.

I am assuming that the router being "ON" has an impact on the program running.

HElp

th

Is there an error message on the screen?

You mention "rig trips offline" - is it the control box that stops? The servos on my KG3925 'tick' when the control box is running, so it's easy to hear when it's stopped.

I have found the control box can be a little flaky at times, and it does occasionally trip out when I turn on either my router or dust extractor.

Does it stop if you have the router on, then move the axes around using the cursor and pg up/pg down keys? (i.e. without starting the g-code program).

Good idea, I will try simulating the problem by manually moving the axis around.

I have Gecko drives, maybe I need to read up on them.

Would the torque of the router spinning have an effect?

I currently believe it is a noise issue, or, the Gecko drives need to be tweaked.

I guess another approach would be to really slow down the accelleration and max speed on the z axis.

I will give it a go this week and post what I find.

Would the torque of the router spinning have an effect?

I wouldn't have thought so. There will be a gyroscopic effect, but I think that only causes an issue if you try to rotate the axis of the gyro (i.e. turn the router over). My physics is a bit rusty though!

I currently believe it is a noise issue, or, the Gecko drives need to be tweaked.

I guess another approach would be to really slow down the accelleration and max speed on the z axis.

Could be. I had a lot of problems getting my machine setup. K2 didn't provide xml files for Mach 3 at the time, and I only really got going once I found a suitable file posted on a Mach forum.

The control box does seem to be a bit flaky, in the sense that tweaking the settings usually seems to make it cut out really quickly, or just produce no movement at all. It's one of the things that's stopped me experimenting with the settings more, as it doesn't really get you anywhere.

I did find that the acceleration, and max velocity, settings can cause the box to cut out very quickly. I did manage to get the machine doing rapids at an impressive speed once, but it doesn't take long for it to trip.

Apparently, Quantum (the next 'version') of Mach has the capability to do smooth acceleration curves, so the machine doesn't jerk around so much. I've not tried it yet though, partly because I've got things working, and they tend to stop when I start fiddling!

I've attached the xml files I've been using for my machine, in the hope it might assist. Note that they are for an earlier revision of Mach 3. I think the newer versions have a different format, but it might convert them on first use.