Guest
Show Posts
321
General Mach Discussion / Re: Pulse Frequency
« on: June 01, 2009, 08:20:58 PM »
at work right now.. will post my settings in my evening.. (+-7hrs from now)
pretty sure my step and dir pulses are set at 2 each..
the error does not present in Y.. what happens as best as i can guess is that there is some "lag" and the first thing that moves after my A has rotated is my Y to bring it back over the centre of my model.. i think in this time mach is playing catch up or summing and the loss of steps to A carries thru to Y.. by the time i start cutting X its sorted. (but A angle is out as well as Y.) (the cut itself then carries on cutting properly in X and Y but just in wrong position)
peculiar error.. goes away if i switch off toolpath display.. and only on big paths.. think its more related to processor speed perhaps. i have not had time to test it at a changed kernel speed, but if all the previous posts are anything to go by then upping kernel speed will make this problem worse not better as higher kernel speed puts more load on processor.
notable here too..
pure rotary jobs, (which are typically my heaviest gcode jobs) cut fine, with toolpath display on.. very strangle.. it seems like it only does it when i instruct rotary to turn from a0 to a180 in one movement at 600mm/min..
will post xml in later
pretty sure my step and dir pulses are set at 2 each..
the error does not present in Y.. what happens as best as i can guess is that there is some "lag" and the first thing that moves after my A has rotated is my Y to bring it back over the centre of my model.. i think in this time mach is playing catch up or summing and the loss of steps to A carries thru to Y.. by the time i start cutting X its sorted. (but A angle is out as well as Y.) (the cut itself then carries on cutting properly in X and Y but just in wrong position)
peculiar error.. goes away if i switch off toolpath display.. and only on big paths.. think its more related to processor speed perhaps. i have not had time to test it at a changed kernel speed, but if all the previous posts are anything to go by then upping kernel speed will make this problem worse not better as higher kernel speed puts more load on processor.
notable here too..
pure rotary jobs, (which are typically my heaviest gcode jobs) cut fine, with toolpath display on.. very strangle.. it seems like it only does it when i instruct rotary to turn from a0 to a180 in one movement at 600mm/min..
will post xml in later
