New computer, new problems

[neilw20]

SATA drives should be no problem.
Disconnect any IDE stuff. CD/DVD rom.

Or disable in the BIOS, at least.

[Claytonc]

SATA drives should be no problem.
Disconnect any IDE stuff. CD/DVD rom.

Or disable in the BIOS, at least.

I unpluged the IDE CD ROM drive.. tested and got the same results... Starts out fine then starts stuttering after 30 or so seconds...

[neilw20]

In Mach3 config increase lookahead to say 100 or 200.
The low level queue might be running out of data.
You can monitor queue depth on the diagnostics page.

I assume you are using Mach3 above version 3?

[Claytonc]

In Mach3 config increase lookahead to say 100 or 200.
The low level queue might be running out of data.
You can monitor queue depth on the diagnostics page.

I assume you are using Mach3 above version 3?

Im not sure if the look ahead is relevant seeing how I'm using the Xbox 360 controller controlling movement for testing.

Yes. Im using above v3.

[neilw20]

Mach3 feeds data to the driver via a queue.
Mach3 upper level program gets a look in about 10 times a second, and if the low level queue is depleted while moving move stops instantly. - The jerk.
Are you running 25KHZ?
You might be running it too fast. The queue empties too quickly.
Only run just fast enough so that you get the required speeds.

[Claytonc]

Mach3 feeds data to the driver via a queue.
Mach3 upper level program gets a look in about 10 times a second, and if the low level queue is depleted while moving move stops instantly. - The jerk.
Are you running 25KHZ?
You might be running it too fast. The queue empties too quickly.
Only run just fast enough so that you get the required speeds.

Im running it at 35000 as it was when I was using the much slower, much less ram, much less video card, etc and it ran great.. So strange... I've tried it at 25,000 before I started posting here. It didn't help either. Its got to be one little setting somewhere...

It does act like some sort of a buffer is filling up because if I stop movement for a while and start again the problem is gone for another 20 30 seconds...

I will try setting the read ahead buffer when I get home tonight.

[neilw20]

Study the Mach3 mysteries PDF. The clues are in there somewhere.
My machine still has the jerks, and I just lowered the max feed rate so the steppers can stop instantly and not lose position.

I will fix or upgrade one day. I just ignore the clunk. The 2000 hours running the machine was more important, as was not losing steps.

Yep, I fixed it the 'other' way.

If you change the KHz you need to restart Mach3 for it to take affect. See Mach3 manual and read details on clock rate setting.

[Claytonc]

But see, this was running great on a much older machine. it just don't make sense. Maybe ill put xp on another partition and see if its the OS that is the problem.

[neilw20]

You can do that.
Might be easier to plug in another drive that already has XP on it from another computer.

At least it will prove whether it is the OS or the motherboard.
Try some bios setting that don't use the interrupts on the the parallel card. It is polled anyway by the driver.

Interrupts will only screw it up (IMHO)

The clu is it starts doing it 30 seconds later. Watch the diagnostics screen in Mach3 for clues.

Does it do it in a program or just from the keyboard?
Make sure sticky keys is disabled. That steals Mach3 keyboard focus. Quite dangerous.

start button, type sticky and select change how your keyboard works.

Are you using a wireless keyboard? Latency can be there.

[Claytonc]

What exactly will I be looking for on the diagnostic screen?

[neilw20]

Queue depth, buffer load, Time in int. Look ahead.
Any of above getting to a limit, or zero might give a hint.
Slow the feed. and watch.
Double the feed and watch.
Below a certain speed the jerks might smooth out.

You don't by any chance have exact stop turned on do you?
That might appear like jerks. It will stop start at all speeds.

[Claytonc]

Queue depth, buffer load, Time in int. Look ahead.
Any of above getting to a limit, or zero might give a hint.
Slow the feed. and watch.
Double the feed and watch.
Below a certain speed the jerks might smooth out.

You don't by any chance have exact stop turned on do you?
That might appear like jerks. It will stop start at all speeds.

Ok... man this sucks... Here is what I've found.
Queue depth stayed 0
buffer load stayed 0
time in int was 4 to 6 with peaks of ~15 or less
Set Look ahead to 200

Same numbers at various speeds.

I'm not sure where the 'exact stop' setting is but i'm sure i'm not looking at this as being the problem as it never was before.

I'm getting pretty frustrated at this point...

ill post a video if needed.