|
1
on: October 19, 2017, 07:05:23 PM
|
|
Started by imitheo - Last post by joeaverage
|
|
Hi,
strict diet of chop suey. LOL
Craig
|
|
|
2
on: October 19, 2017, 06:32:03 PM
|
|
Started by chad - Last post by joeaverage
|
|
Hi,
a useful idea for learning is to use some of the simpler Wizards and then observing the Gcode it generates
and trying to understand it. Recommend rectangular bolt pattern, rectangular pocket, circular bolt pattern
wizards.
Craig
|
|
|
3
on: October 19, 2017, 04:27:31 PM
|
|
Started by John40131 - Last post by joeaverage
|
|
Hi,
not sure about the probe problem at the moment.
Try reversing the X and Y axes by checking (or unchecking as the case my be) the active low setting of the
DIR signal of both stepper drivers.
Craig
|
|
|
4
on: October 19, 2017, 04:06:53 PM
|
|
Started by ART - Last post by ART
|
|
Hi:
The waveform doesnt look bad really, it basically shows a jitter of about 10us happening every few cycles of the driver.
Hard to say what it is, some process thats dependent on interrupts by the look of it. Id try tweaking your tuning, the
steppers should be driving OK with that waveform I think.
Art
|
|
|
5
on: October 19, 2017, 03:33:20 PM
|
|
Started by ART - Last post by knitehawk
|
|
Hi, just testing darwin on my system, my motors are choppy and seem to lag a bit.
my old mach3 system died so i had to build another one. it's a 3 axis router table running IM804 stepper drivers 4-6 amp.
i can turn them when the systems off with my fingers and i'm not feeling any binding but when running it just seems slow and you can hear the steppers hesitate at times.
the darwin control and status water fall is showing 2 lines not one. Img attached.
why is that? and could that be causing my issue?
pentium 3ghz with 2g ram
windows xp
using PCI parallel port drivers loaded fine
|
|
|
6
on: October 19, 2017, 03:33:08 PM
|
|
Started by backlashphoenix - Last post by Oto
|
|
Thank you guys for this sources
|
|
|
7
on: October 19, 2017, 03:31:58 PM
|
|
Started by imitheo - Last post by Oto
|
|
I have the same and no problems like that
|
|
|
8
on: October 19, 2017, 02:43:25 PM
|
|
Started by hyildiz - Last post by joeaverage
|
|
Hi Steve,
kool thanks for that explanation. A simple delay will probably work. Thanks again.
Craig
|
|
|
9
on: October 19, 2017, 01:50:58 PM
|
|
Started by hyildiz - Last post by Steve Stallings
|
|
The fault is not necessarily with the G code. It is common to issue an M3 and an S word on
the same line of G code.
Even if the S word is issued in advance, that does not guarantee that the PWM to analog
conversion will happen before the M3 takes effect. That will be dependent on how the
motion device handles the signals. PMDX products will inhibit the analog out until the
M3 is issued. Indeed, Mach3's own parallel port driver will not generate a PWM signal
until the M3 or M4 command is issued.
Using a pause for spin up, or using feedback are valid approaches to the problem.
|
|
|
10
on: October 19, 2017, 01:05:56 PM
|
|
Started by hyildiz - Last post by joeaverage
|
|
Hi,
the fault is your Gcode. It should set the PWM with a Snnnn command, wait for 5-10ms for the PWM to propagate to the VFD THEN issue a start command.
You can cheat to overcome this if you can't be bothered to fix your Gcode by having a delay before calling mcSignalWait so that the glitch has been and gone
before Mach requires it.
Craig
|
|
|
