Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Lob0426

Pages: 1 [2] 3 4 ... 87
16
The actual controller chip is only like 6 or 7mm square for the SMD version in size if it is a 328p Arduino. I suspect that is what it is. It even could be under the LCD.

17
General Discussion / Re: howto fix laser diode
« on: November 26, 2017, 11:55:23 AM »
The 12mm housing acts as part of the heat sink. The most common sizes are 3.8mm, 5.6mm and 9mm. If it cannot transfer the heat it will burn up.

https://sites.google.com/site/dtrlpf/home/diode-modules

The stock laser 500mw laser module I had had a brass adapter from 3.8 to 5.6mm. I have never seen those for sale. You can get the laser host modules in all these sizes on Ebay and Amazon. They are not expensive. Get one that is the proper size and try to get a copper, rather than brass if you can. Not real important for only 2W.

18
It is a regulator for the low laser then. The older benbox boards had them, but they were manually adjusted. The Laser drivers look very similar. Yeah, might be best to leave it alone unless there is reason to mess with it.

19
Image 0767; looks like the Laser driver is mounted on the bottom of the board. Or is that just a low laser regulator? Make sure you do not adjust that board, it is set to run your laser. You might need to adjust the stepper drivers someday. They are top of the board. Just don't accidently adjust the wrong board. LOL!

20
Mini CNC / Re: Mini mill kerf
« on: November 21, 2017, 10:04:45 AM »
Mine uses LinuxCNC which supports tool diameter and length compensation.

21
Mini CNC / Re: Mini mill kerf
« on: November 20, 2017, 10:10:12 PM »
The most common codes for tool diameter compensation are;
G40 tool compensation off
G41 tool compensation left
G42 tool compensation right

http://cnc-programming-tips.blogspot.com/2014/12/g40-g41-and-g42-cuttercompensation.html

Grbl does not support those gcodes. So the program has to take it into account.

Edit: G40 tool/cutter compensation off is supported by grbl. G41 and G42 are not supported.

22
T2 Engraving / Re: Tablet or Laptop
« on: November 20, 2017, 01:14:53 AM »
I use a 10" tablet to run mine. As long as the software will install it should work. No way to know except try it. If it charges through it's USB  jack you might run out the battery on long jobs. Try to find a tablet that has a separate power port if you can.

Adjust you power settings to shut down the display but not the system. That way your jobs will not stop when it goes to sleep. And having the display off saves power for longer run times.

23
Projects / Re: Cable strain relief
« on: November 17, 2017, 10:14:43 AM »
Looks like a cable chain to me.

24
General Discussion / Re: Stepper motors running hot when in idle
« on: November 13, 2017, 08:20:49 PM »
I run $1=255, Step idle delay, milliseconds. Which leaves the steppers in constant hold. I do not notice any real heat buildup. If you are running them this way two things.
1. Shut off the board when it is not running a job.
2. Make sure you have the stepper current set properly.

If you leave the board on with power to the steppers they will warm up over time. Or you change the setting in $1 so that the steppers are not active after they stop.

25
Mini CNC / Re: Limit vs Home switches
« on: November 09, 2017, 11:04:22 PM »
You have to set it in grbl then recompile. The individual pins are in cpu_map.h

// Define homing/hard limit switch input pins and limit interrupt vectors.
  // NOTE: All limit bit pins must be on the same port, but not on a port with other input pins (CONTROL).
  #define LIMIT_DDR        DDRB
  #define LIMIT_PIN        PINB
  #define LIMIT_PORT       PORTB
  #define X_LIMIT_BIT      1  // Uno Digital Pin 9
  #define Y_LIMIT_BIT      2  // Uno Digital Pin 10
  #ifdef VARIABLE_SPINDLE // Z Limit pin and spindle enabled swapped to access hardware PWM on Pin 11.
    #define Z_LIMIT_BIT      4 // Uno Digital Pin 12
  #else
    #define Z_LIMIT_BIT    3  // Uno Digital Pin 11
  #endif
Different if using a Mega2560. But in same place

config.h notes on homing and homing separate axis, new to me here. description;

// If homing is enabled, homing init lock sets Grbl into an alarm state upon power up. This forces
// the user to perform the homing cycle (or override the locks) before doing anything else. This is
// mainly a safety feature to remind the user to home, since position is unknown to Grbl.
#define HOMING_INIT_LOCK // Comment to disable

// Define the homing cycle patterns with bitmasks. The homing cycle first performs a search mode
// to quickly engage the limit switches, followed by a slower locate mode, and finished by a short
// pull-off motion to disengage the limit switches. The following HOMING_CYCLE_x defines are executed
// in order starting with suffix 0 and completes the homing routine for the specified-axes only. If
// an axis is omitted from the defines, it will not home, nor will the system update its position.
// Meaning that this allows for users with non-standard cartesian machines, such as a lathe (x then z,
// with no y), to configure the homing cycle behavior to their needs.
// NOTE: The homing cycle is designed to allow sharing of limit pins, if the axes are not in the same
// cycle, but this requires some pin settings changes in cpu_map.h file. For example, the default homing
// cycle can share the Z limit pin with either X or Y limit pins, since they are on different cycles.
// By sharing a pin, this frees up a precious IO pin for other purposes. In theory, all axes limit pins
// may be reduced to one pin, if all axes are homed with seperate cycles, or vice versa, all three axes
// on separate pin, but homed in one cycle. Also, it should be noted that the function of hard limits
// will not be affected by pin sharing.
// 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<<Z_AXIS)                // REQUIRED: First move Z to clear workspace.
#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.
// #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.

$5 sets limits/home NC or NO
$6 sets "probe" switch NC or NO
$21 sets hard limits =switches

https://github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration

"
$21 - Hard limits, boolean
Hard limit work basically the same as soft limits, but use physical switches instead. Basically you wire up some switches (mechanical, magnetic, or optical) near the end of travel of each axes, or where ever you feel that there might be trouble if your program moves too far to where it shouldn't. When the switch triggers, it will immediately halt all motion, shutdown the coolant and spindle (if connected), and go into alarm mode, which forces you to check your machine and reset everything.
To use hard limits with Grbl, the limit pins are held high with an internal pull-up resistor, so all you have to do is wire in a normally-open switch with the pin and ground and enable hard limits with $21=1. (Disable with $21=0.) We strongly advise taking electric interference prevention measures. If you want a limit for both ends of travel of one axes, just wire in two switches in parallel with the pin and ground, so if either one of them trips, it triggers the hard limit.
Keep in mind, that a hard limit event is considered to be critical event, where steppers immediately stop and will have likely have lost steps. Grbl doesn't have any feedback on position, so it can't guarantee it has any idea where it is. So, if a hard limit is triggered, Grbl will go into an infinite loop ALARM mode, giving you a chance to check your machine and forcing you to reset Grbl. Remember it's a purely a safety feature."

Richard

26
Mini CNC / Re: Limit vs Home switches
« on: November 09, 2017, 04:20:37 PM »
$h initiates a script that runs the steppers towards the settings in home direction until the switches are activated. The difference in home and limit is how they react to a switch activation. Limits are initiated by the switches and end in an alarm state. Any switch can be used as a home and/or limit. Sounds weird but it works. Use $h and it is a home switch, dependent on the settings for home direction. If any switch is hit without a $h they halt the machine as a limit.

Your number 1. Since you did not use $h it just goes to the switches and stops, being activated as a limit. If it does tis with a $h used your homing seek speed is too high.

Your #2 $x as Nottingham stated. System alert is the default at start if you setup firmware for switches. I think you can change that in the firmware, not in eeprom. $h or $x cancels the alarm.

Your #3 . You can use Z limit to change the tool. Then lower down the work taking into account tool lengths

You could raise Z to the limit for the tool change, automatically stops all movement of steppers, motors and lasers (anything controlled as spindle). Then use the grbl "probe" function to lower to work height. Use an adjustable probe that can be adjusted to each tools length or have all tools the same length (I know, I'm dreaming).

Your #4 if you use $h the switch is a homing switch (. If the switch is activated without $h it is a limit.

"probe" has to be set in firmware not in eeprom.

I hope this helps.

27
Custom Size Frames / Re: core-xy
« on: October 26, 2017, 12:28:49 AM »
There is a couple of settings in the grbl firmware for CoreXY did you set everything to CoreXY?

28
Assembly Help / Re: Wiring home switches
« on: October 19, 2017, 05:04:17 PM »
Once you get all moving in the right directions you can adjust those settings up a bit.

You can set the homing seek 4000. And the homing feed is safe at 400 to 500. Those will keep your accuracy while speeding up the homing.

I use even higher settings than those with no problems.

29
General Discussion / Re: mega 2560 problem motor
« on: October 19, 2017, 04:22:49 PM »
We need to know what board you are using. There is no standard wiring set for these boards. The firmware may have to be compiled specifically for your board.

30
Congratulations!

Pages: 1 [2] 3 4 ... 87