Hello, All
New member. Came across this site looking for information. Been poking around, lots of good stuff most of it over my head. Current project (First Arduino project of any kind) is CNC control the tower and an X table on my fiber/ galvo laser. Already had automated the tower with a stepper and up/ down buttons, DRO, but wanted CNC control and also X table to accurately move workpiece when/ if larger then the boundary of the work area.
So what I have so far, one week in, Uno R3/ Shield, IDE, and UGS. Have the X working and homing, have the Z working, but not reading the limit switch. Probably pretty easy to sort that out.
First changed the config.h file for 1 axis, got it working, then added the Z. That's where I am at as of last night.
All hobby stuff, haven't quit my day job.
Just wanted to pop up and say hi!
I'm sure I will have some questions, is there a CNC Shield area to post in?
Thanks--
Al
The Motors, Mechanic, Power and CNC and section is probably the best.
That's a surprise. Compared to the work You tell You've done it's a surprise.
The next surprise is how You think forum can make any suggestion without seing the code.
To feel safe seing the schematics for the powering is interesting.
Ha!
Just introducing myself, but when/if I ask for help I will be sure to include the code.
And even maybe a schematic!
Appreciate the heads up and desire to jump in and help.
Al
Smoked the little guy. For a week I have been powering the UNO R3 through the barrel, messing around yesterday and smoke started pourin out!
Cause:
Used a power supply that I had previously used on a 24V board
Forgot to change to 12V
PS had a 5.5x2.5 plug, remember now iit was an tough size to get but a 5.5X2.1 would not fit. Spaced out on the UNO taking a 5.5x2.1, spaced out on the 24V
So apparently the 5.5x2.5 @ 24V went a week without actually making contact with the center pin and the UNO was being powered by the USB during testing. Then it decided to make contact last night.
Fortunately only a $20.00 board, but need to be more careful in the future.
Here is the code I changed in config.h
// NOTE: Defaults are set for a traditional 3-axis CNC machine. Z-axis first to clear, followed by X & Y.
#define HOMING_CYCLE_0 (1<<X_AXIS) // REQUIRED: First move Z (X) to clear workspace.
#define HOMING_CYCLE_1 (1<<Z_AXIS) // AF 8.2.23
// #define HOMING_CYCLE_1 ((1<<X_AXIS)|(1<<Y_AXIS)) // OPTIONAL: Then move X,Y at the same time.
// #define HOMING_CYCLE_2 // OPTIONAL: Uncomment and add axes mask to enable
// NOTE: The following are two examples to setup homing for 2-axis machines.
// #define HOMING_CYCLE_0 ((1<<X_AXIS)|(1<<Y_AXIS)) // NOT COMPATIBLE WITH COREXY: Homes both X-Y in one cycle.
// #define HOMING_CYCLE_0 (1<<X_AXIS) // COREXY COMPATIBLE: First home X
// #define HOMING_CYCLE_1 (1<<Y_AXIS) // COREXY COMPATIBLE: Then home Y
// Number of homing cycles performed after when the machine initially jogs to limit switches.
// This help in preventing overshoot and should improve repeatability. This value should be one or
// greater.
#define N_HOMING_LOCATE_CYCLE 1 // Integer (1-128)
// Enables single axis homing commands. $HX, $HY, and $HZ for X, Y, and Z-axis homing. The full homing
// cycle is still invoked by the $H command. This is disabled by default. It's here only to address
// users that need to switch between a two-axis and three-axis machine. This is actually very rare.
// If you have a two-axis machine, DON'T USE THIS. Instead, just alter the homing cycle for two-axes.
// AF 8.2.23
#define HOMING_SINGLE_AXIS_COMMANDS // Default disabled. Uncomment to enable.
// After homing, Grbl will set by default the entire machine space into negative space, as is typical
// for professional CNC machines, regardless of where the limit switches are located. Uncomment this
// define to force Grbl to always set the machine origin at the homed location despite switch orientation.
#define HOMING_FORCE_SET_ORIGIN // Uncomment to enable. AF 8.2.23
My attempt at a schematic. Excuse the poor penmanship, lack of standards, etc.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.