Hello Guest it is May 23, 2019, 03:23:12 AM

Author Topic: Issue with g3 command incremental  (Read 4953 times)

0 Members and 1 Guest are viewing this topic.

Re: Issue with g3 command incremental
« Reply #10 on: October 15, 2010, 11:38:22 AM »
Just tried this file w/o any issues at the 300mm/min from the file and overuled to 500mm/min. Not any issue.
Im placing the detail in the same area +-1cm where the error occurs, to ensure that it is not caused by a machine error (spindle bent or anything like that...)
Re: Issue with g3 command incremental
« Reply #11 on: October 15, 2010, 11:39:37 AM »
Uupos, forgot attachment

Offline Hood

*
  •  25,811 25,811
  • Carnoustie, Scotland
    • View Profile
Re: Issue with g3 command incremental
« Reply #12 on: October 15, 2010, 01:22:17 PM »
The only real way to see what is going on is to scope the output pulses from the port, as I said I ran your file and I got the pulses so if yours is the same then it would seem to be further out than the port that the problem is.
Can you get hold of a scope?
Hood
Re: Issue with g3 command incremental
« Reply #13 on: October 15, 2010, 04:05:22 PM »
just cut out a few pieces using various files. changed feedrate up and down. Not any issue.
Did the driver test: excellent.
It#s gotta be something with the file(arc)

Offline Hood

*
  •  25,811 25,811
  • Carnoustie, Scotland
    • View Profile
Re: Issue with g3 command incremental
« Reply #14 on: October 15, 2010, 04:19:25 PM »
As said it runs fine here and scopes perfect for me. That is using the same code and your xml so dont see how it can be the code. Fair enough I dont have motors connected but the pulses coming out of the port are present and look to be correct so dont think it would make a difference. Could it possibly be that your drives have an issue with the frequency of the pulses at that point? Does the motor sound like its stalling?
Hood
Re: Issue with g3 command incremental
« Reply #15 on: October 16, 2010, 04:29:25 AM »
I got 2 motors driving the X-axis in parallel.
It feels like they are shivering, they are not locked as if the axis stands still, but they are also not moving.
Will try to reduce acceleration....
Just created another file and will try it out.
If that does not work either, I will connect  scope.
Strange thing is that it always happens at the same command

Offline Hood

*
  •  25,811 25,811
  • Carnoustie, Scotland
    • View Profile
Re: Issue with g3 command incremental
« Reply #16 on: October 16, 2010, 04:32:01 AM »
It could well be that the particular pulserate at that point in time is causing issues, what type of drives do you have?
Will be interesting to see what the scope tells you.
Hood
Re: Issue with g3 command incremental
« Reply #17 on: October 16, 2010, 07:15:22 AM »
These ones: http://www.mechapro.de/hem545.html  ...german... ttl/optocoupler, powerd with 50VDC, good for 5Amps. Powering 1 Stepper each.
! for the y, one for z and 2 for the x. Thru a relais matrix I can switch between 2 mills.
I use those for years now. Never had any issue.

Hope my Multimeterscope is good enough  otherwise I will have to carry my big one down to the basement. will take a while....

Offline RICH

*
  • *
  •  7,331 7,331
    • View Profile
Re: Issue with g3 command incremental
« Reply #18 on: October 16, 2010, 06:46:51 PM »
The files you posted dry run fine here.
RICH