Gecko driver g320x series#
The GUI could then handle other canned cycles such as G76 by converting the G76 command into a series of G01, G00, and G33 commands that GRBL takes care of. Or implement a G33 within GRBL that is simply the same as a G01 except that using it tells GRBL to convert M3/M4 SXXX commands into syncronized motion. Maybe a simple binary variable that grbl uses to know if the intent at the time is syncronized motion or not. The only thing I am not sure of is how you would keep the spindle turning say for non-threading commands. For this example you would have to provide a thread relief cut at the end of the travel since the spindle would stop at the end of the cut in this example. I used G33 because it is simple to illustrate. GRBL would just see a G1 F302 Z-2 Y16.8 where Y is the spindle servo. To get 300 rpm out of the spindle if set up for 1 unit=1revolution, the feedrate sent to GRBL would have to take into account the Z axis travel. The gui could easily calculate that the Z axis has to move a total of 2.1 inches and with a K value of 0.125, there would need to be 2.1/0.125=16.8 revolutions of the spindle. G0 X1.25 (rapid move tool away from work) G33 Z-2 K0.125 (move Z axis to -2 at a rate to equal 0.125 per revolution) The gui could then convert any type of canned threading cycle into a series of G1 coordinated motion commands. I think it should be possible to have the GUI interface handle most of the heavy work with GRBL just keeping track of the spindle position by keeping track of the number of step pulses sent to the driver. The servo drive on the spindle would adjust to keep up rather than having to have GRBL adjust the other axes due to spindle speed fluctuation. I think the use of a servo for the spindle drive could provide a way to incorporate spindle synchronization in a fashion that is possibly easier than having an encoder and index pulse mounted to the spindle that GRBL would have to monitor and adjust the other axes for. This could also be applied to mill spindle synchronization in a similar fashion allowing rigid tapping but would require a fourth "axis". But this isn't the way that lathe threading is normally programmed and doesn't account for non-threading use where you would want the spindle to run continuous at a set rpm. A G91 command of G1 z-1 y10 would give a 10 thread per inch type of move.
Gecko driver g320x how to#
The issue is how to implement this within GRBL.įor example for a lathe, lets say you set up the spindle as the Y-axis with a distance of 1 inch corresponding to one revolution of the spindle. Since the motor would be seen as just another axis, then coordinated motion would be possible, allowing lathe threading. Since GRBL is 3-axis only, the normal lathe X and Z axes would take up two of the available axes, leaving the third available to control the spindle motor through the Gecko driver. The motor could then be hooked to the spindle with a timing belt drive so that the motor position could be related to spindle position. All of the encoder and servo feedback control would be internal to the Gecko driver.
Gecko driver g320x driver#
If I were to add an encoder to the motor and drive it using a servo driver such as the Gecko G320X, GRBL would see the motor as simply another step/direction motor like a stepper. I have a 9 x 20 lathe that I also have a surplus DC motor that I intend to use for a spindle drive. Posted in: All Tutorials, Config & Tweaks | Tagged: 3 Axes DMM DYN4 AC 750W Servo Kit, 3 axis cnc control, 3 axis cnc mill, 3 axis cotroller, 4 Axes DMM DYN4 AC 1.I have been thinking about the issue of lack of spindle synchronization as it relates to lathe operation and I think I have an idea for smaller lathes t least. It is also very Important that you set proper units to Millimeters or Inches before you run a G-code. Then you must set the steps per unit for your machine, this may cause your motors to go slower, if so you can adjust velocity and acceleration in Motor Tuning. You must also verify the directions your motors are running and make any changes if necessary. It is very common that the Y axis uses two motors, therefore usually the A axis is slaved to Y axis. You must first determine if you are using any slaved axis. In this video we explain the steps you need to follow once you have your CBX 1.7 controller by CNC Basis connected to your machine.