I did end up getting it work. Diffs from stock FT-5 firmware posted in the comments section of the video.
[youtu.be]
[youtu.be]
↧
Re: Trouble getting dual Z end stops + steppers to work
↧
Re: Z axis will not respond to homing command (Mendel90)
What factors determine the step/mm?
I ask this because mine don't seem to do that.
So I'm wondering why?
thanks
I ask this because mine don't seem to do that.
So I'm wondering why?
thanks
↧
↧
LCD works, but encoder is not working, help?
He guys, need help. I'm using the REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER and the LCD works, but the encoder wheel doesn't work at all.
Did I miss something? Do I need to enable the encoder?
Thanks guys
Did I miss something? Do I need to enable the encoder?
Thanks guys
↧
Re: too much extrusion - what to modify in configuration.h ?
Thank you ! Last time i assembled a printer was some years ago. First time i see a bowden extruder..
Yes, seller confirmed 0.4mm nozzle.
And i actually had to increase the 89 because extrusion of 200mm only lead to 188mm :-/
I guess it is something mechanical. The Extruder lever moves up and down when the gear-wheel rotates.
And the clicking noise does not come from the filament slipping back but the gear-wheel is pushed back :-(
Tried with less tension in the spring (that pushes the lever and increases the pressure onto the filament) and it seems to reduce the slipping of the gear-wheel.
Uploaded a short video: [youtu.be]
In the very beginning you can see (and hear) the gear-wheel clicking/slipping back three times :-/
Ideas welcome :-)
P.S. first i could not load the hot hotend with the filament. Had to unscrew the nozzle and push the filament by hand (pressing the lever on the extruder) by hand through the hotend. Then a 3cm long PTFE tube appeared and i manually inserted the 1.75mm PLA filament into it. Then i could print. Later i extruded backwards to remove the filament and then forward extruding worked. So i guess this little PTFE tube is okay now.
Yes, seller confirmed 0.4mm nozzle.
And i actually had to increase the 89 because extrusion of 200mm only lead to 188mm :-/
I guess it is something mechanical. The Extruder lever moves up and down when the gear-wheel rotates.
And the clicking noise does not come from the filament slipping back but the gear-wheel is pushed back :-(
Tried with less tension in the spring (that pushes the lever and increases the pressure onto the filament) and it seems to reduce the slipping of the gear-wheel.
Uploaded a short video: [youtu.be]
In the very beginning you can see (and hear) the gear-wheel clicking/slipping back three times :-/
Ideas welcome :-)
P.S. first i could not load the hot hotend with the filament. Had to unscrew the nozzle and push the filament by hand (pressing the lever on the extruder) by hand through the hotend. Then a 3cm long PTFE tube appeared and i manually inserted the 1.75mm PLA filament into it. Then i could print. Later i extruded backwards to remove the filament and then forward extruding worked. So i guess this little PTFE tube is okay now.
↧
Cartesian Bed Levelling Solved
Hi,
Does anyone have an up to date set-up procedure for bed levelling on the current Marlin.
I have been going around in circles for days now (insane :))....
I have followed Thomas Sanderer's video on YouTube, but when I get to the final calibration part I cannot for the life of me get the probe to go below the sensor trigger point.
Sorry if this a simple question....
Mark
Was using Repetier Host works in Ponterface...:)
Does anyone have an up to date set-up procedure for bed levelling on the current Marlin.
I have been going around in circles for days now (insane :))....
I have followed Thomas Sanderer's video on YouTube, but when I get to the final calibration part I cannot for the life of me get the probe to go below the sensor trigger point.
Sorry if this a simple question....
Mark
Was using Repetier Host works in Ponterface...:)
↧
↧
Re: Cartesian Bed Levelling Solved
You need to have your Z_PROBE_OFFSET_FROM_EXTRUDER set accurately. And... It may help to turn off the software endstops:
#define min_software_endstops true // If true, axis won't move to coordinates less than HOME_POS.
#define max_software_endstops true // If true, axis won't move to coordinates greater than the defined lengths below.
It sounds like you are using Grid leveling. In all of the Mesh leveling schemes (including UBL at [github.com]), going below 0.000mm is assumed to be necessary.
If you bring up the UBL system, I'll spend the time to help get over any problems you run into.
#define min_software_endstops true // If true, axis won't move to coordinates less than HOME_POS.
#define max_software_endstops true // If true, axis won't move to coordinates greater than the defined lengths below.
It sounds like you are using Grid leveling. In all of the Mesh leveling schemes (including UBL at [github.com]), going below 0.000mm is assumed to be necessary.
If you bring up the UBL system, I'll spend the time to help get over any problems you run into.
↧
Re: Cartesian Bed Levelling Solved
Since the probe is stopping early and wont move right down then
mostly likely you need to issue a G92 Z10. That tricks the controller into
thinking the z-min endstop is 10mm lower, or at least below the bed.
Must admit I used the Sanderer videos myself. Very nice productions.
mostly likely you need to issue a G92 Z10. That tricks the controller into
thinking the z-min endstop is 10mm lower, or at least below the bed.
Must admit I used the Sanderer videos myself. Very nice productions.
↧
Question about using marlin in laser cutting applications
hello
I found a plugin for inkscape that enables the user from generating a code for laser cutter that can be read by repetier. I drew a square and I generated this simple code:
M452
M3 S255
G90
G21
G0 F1500
G0 X47.5746 Y229.8095
G0 F100.000000
G1 X157.2381 Y229.8095
G1 X157.2381 Y133.0476
G1 X47.5746 Y133.0476
G1 X47.5746 Y229.8095
G0 F1500
G91
G90
M5 S0
G0 X0 Y0
M18
my question is, if I am using marlin with ramps 1.4, how the output will go to laser head to make it on or off ?? if I understand correctly, I will have to deactivate z axis in marlin firmware, but will the on-off signal of the laser head go to the extruder0 output in ramps?
and if this is the case, can I modify in marlin code to make the output is just a pin that goes high for on and low for off? if yes, where I need to modify this into marlin?
many thanks
I found a plugin for inkscape that enables the user from generating a code for laser cutter that can be read by repetier. I drew a square and I generated this simple code:
M452
M3 S255
G90
G21
G0 F1500
G0 X47.5746 Y229.8095
G0 F100.000000
G1 X157.2381 Y229.8095
G1 X157.2381 Y133.0476
G1 X47.5746 Y133.0476
G1 X47.5746 Y229.8095
G0 F1500
G91
G90
M5 S0
G0 X0 Y0
M18
my question is, if I am using marlin with ramps 1.4, how the output will go to laser head to make it on or off ?? if I understand correctly, I will have to deactivate z axis in marlin firmware, but will the on-off signal of the laser head go to the extruder0 output in ramps?
and if this is the case, can I modify in marlin code to make the output is just a pin that goes high for on and low for off? if yes, where I need to modify this into marlin?
many thanks
↧
Re: Question about using marlin in laser cutting applications
NB this is generating code for Repetier firmware M452 is only in that firmware (at least as far as teh g-code wiki is concerned)
Your code is using spindle commands to turn the laser power on/off, but it also has an enable pin (see below)
M3: Spindle On, Clockwise (CNC specific)
M5: Spindle Off (CNC specific)
see [github.com]
In the current firmware "Here G1/G2/G3 moves have laser enabled and G0 moves have it disables."
ie you need to find and update
#define SUPPORT_LASER 0 // set 1 to enable laser support
#define LASER_PIN -1 // set to pin enabling laser
#define LASER_ON_HIGH 1 // Set 0 if low signal enables laser
So if your just turning your laser on and off (because it doesn’t have a digital enable pin) use the enable pin to turn it off/on.
Hint, if your laser needs lots of power or a weird voltage use D8 on the ramps, as you can feed in any required voltage into the 11amp normally 12v supply, and it only goes to the heated bed. Don't just try and run it from an IO pin, that will probably draw to much power and kill the IO pin.
You don't lose z, you need that for focusing, you just set it to the correct height manually then hit print and it stays at that height.
Marlin doesn’t support this. (as far as im aware) you need something else, normally I've see them use a fan output and it explicitly turns the laser on and off as needed. No magic G0/G1 stuff
What plug in are you using ? this [jtechphotonics.com] ?
Your code is using spindle commands to turn the laser power on/off, but it also has an enable pin (see below)
M3: Spindle On, Clockwise (CNC specific)
M5: Spindle Off (CNC specific)
see [github.com]
In the current firmware "Here G1/G2/G3 moves have laser enabled and G0 moves have it disables."
ie you need to find and update
#define SUPPORT_LASER 0 // set 1 to enable laser support
#define LASER_PIN -1 // set to pin enabling laser
#define LASER_ON_HIGH 1 // Set 0 if low signal enables laser
So if your just turning your laser on and off (because it doesn’t have a digital enable pin) use the enable pin to turn it off/on.
Hint, if your laser needs lots of power or a weird voltage use D8 on the ramps, as you can feed in any required voltage into the 11amp normally 12v supply, and it only goes to the heated bed. Don't just try and run it from an IO pin, that will probably draw to much power and kill the IO pin.
You don't lose z, you need that for focusing, you just set it to the correct height manually then hit print and it stays at that height.
Marlin doesn’t support this. (as far as im aware) you need something else, normally I've see them use a fan output and it explicitly turns the laser on and off as needed. No magic G0/G1 stuff
What plug in are you using ? this [jtechphotonics.com] ?
↧
↧
Re: Question about using marlin in laser cutting applications
I do not remember from where I downloaded the plugin, but it seems that what I have in an older version of the plugin that you sent me of jtechphotonics. the plugin that I have does not have "Laser On Command", and "Laser Off Command" text area.
so if I understand well now, I will need to connect the laser head to fan output, and in th plugin I will make the on command is M106 S255 and off command is M106 S00 ? This will give on-off signal during moves when needed to the laser?
so if I understand well now, I will need to connect the laser head to fan output, and in th plugin I will make the on command is M106 S255 and off command is M106 S00 ? This will give on-off signal during moves when needed to the laser?
↧
Re: Question about using marlin in laser cutting applications
another point. I remembered why I was using the old plug in. It was dedicated for generating G code that can be read with repetier. I tried the laser plugin that you sent me, and I generated a simple output of 3 squares drawing:
M107 S0
G90
G21
G1 F3000
G1 X45.9619 Y81.4413
G4 P0
M106 S255
G4 P0
G1 F100.000000
G1 X105.6317 Y81.4413
G1 X105.6317 Y41.1238
G1 X45.9619 Y41.1238
G1 X45.9619 Y81.4413
G4 P0
M107 S0
G1 F3000
G1 X80.6349 Y178.2032
G4 P0
M106 S255
G4 P0
G1 F100.000000
G1 X152.4 Y178.2032
G1 X152.4 Y129.8222
G1 X80.6349 Y129.8222
G1 X80.6349 Y178.2032
G4 P0
M107 S0
G1 F3000
G1 X49.9936 Y266.0952
G4 P0
M106 S255
G4 P0
G1 F100.000000
G1 X99.181 Y266.0952
G1 X99.181 Y227.3905
G1 X49.9936 Y227.3905
G1 X49.9936 Y266.0952
G4 P0
M107 S0
G1 F3000
G1 X0 Y0
M18
but when I copy and past this now in repetier, the visualization does not show anything, as if it does not recognize the code!
but when I added manually in the beginning of the code :
M452
M3 S255
then repetier could darw visualization of the the code.
why is this happening? ae not there any way that the plugin put these 2 lines automatically?
M107 S0
G90
G21
G1 F3000
G1 X45.9619 Y81.4413
G4 P0
M106 S255
G4 P0
G1 F100.000000
G1 X105.6317 Y81.4413
G1 X105.6317 Y41.1238
G1 X45.9619 Y41.1238
G1 X45.9619 Y81.4413
G4 P0
M107 S0
G1 F3000
G1 X80.6349 Y178.2032
G4 P0
M106 S255
G4 P0
G1 F100.000000
G1 X152.4 Y178.2032
G1 X152.4 Y129.8222
G1 X80.6349 Y129.8222
G1 X80.6349 Y178.2032
G4 P0
M107 S0
G1 F3000
G1 X49.9936 Y266.0952
G4 P0
M106 S255
G4 P0
G1 F100.000000
G1 X99.181 Y266.0952
G1 X99.181 Y227.3905
G1 X49.9936 Y227.3905
G1 X49.9936 Y266.0952
G4 P0
M107 S0
G1 F3000
G1 X0 Y0
M18
but when I copy and past this now in repetier, the visualization does not show anything, as if it does not recognize the code!
but when I added manually in the beginning of the code :
M452
M3 S255
then repetier could darw visualization of the the code.
why is this happening? ae not there any way that the plugin put these 2 lines automatically?
↧
Re: Question about using marlin in laser cutting applications
No idea why repetier is being brain dead... you would have to ask the developers.
The plugin is just python code.. you can edit it in a text editor, so is easy to add in the two lines
open up laser.py
find the section:
replace with:
NB this is just a educated guess... but should work.
Yes this is now using fan gcode command to turn the laser on and off
eg
M106 S255 laser on full
G4 P0 pause a moment
G1 F100.000000 set the feed rate (speed of move, but also how dark/deap the cut)
G1 X105.6317 Y81.4413 move
G1 X105.6317 Y41.1238 move
G1 X45.9619 Y41.1238 move
G1 X45.9619 Y81.4413 move
G4 P0 pause a moment
M107 S0 laser off
It will use what ever IO pin you have defined as the fan PIN. This is controlled by what motherboard name you give it in your firmware
egs
#define BOARD_RAMPS_14_EFB 43 // RAMPS 1.4 (Power outputs: Hotend, Fan, Bed)
#define BOARD_RAMPS_14_EEB 44 // RAMPS 1.4 (Power outputs: Hotend0, Hotend1, Bed)
#define BOARD_RAMPS_14_EFF 45 // RAMPS 1.4 (Power outputs: Hotend, Fan0, Fan1)
#define BOARD_RAMPS_14_EEF 46 // RAMPS 1.4 (Power outputs: Hotend0, Hotend1, Fan)
#define BOARD_RAMPS_14_SF 48 // RAMPS 1.4 (Power outputs: Spindle, Controller Fan)
Remember that D8 is what ever voltage you apply to the 11amp 12v power pins
But D9 and D10 are what ever voltage you apply to the 5amp 12v power pins, and will be 12v on normal systems. (needed by stepper driver)
I don’t know what your laser takes to power, but if this was me I would use BOARD_RAMPS_14_EEF so the laser is on D8 and you can set what ever supply it needs to the 11amp 12v power plug
If your doing something totally custom, you can edit what pin is being used for the fan by editing pins_RAMPS.h and compiling a custom firmware
NB if you get this working, please post results
The plugin is just python code.. you can edit it in a text editor, so is easy to add in the two lines
open up laser.py
find the section:
'header': """ G90 """,
replace with:
'header': """ G90 M452 M3 S255 """,
NB this is just a educated guess... but should work.
Quote
Quote:
so if I understand well now, I will need to connect the laser head to fan output, and in the plugin I will make the on command is M106 S255 and off command is M106 S00 ? This will give on-off signal during moves when needed to the laser?
Yes this is now using fan gcode command to turn the laser on and off
eg
M106 S255 laser on full
G4 P0 pause a moment
G1 F100.000000 set the feed rate (speed of move, but also how dark/deap the cut)
G1 X105.6317 Y81.4413 move
G1 X105.6317 Y41.1238 move
G1 X45.9619 Y41.1238 move
G1 X45.9619 Y81.4413 move
G4 P0 pause a moment
M107 S0 laser off
It will use what ever IO pin you have defined as the fan PIN. This is controlled by what motherboard name you give it in your firmware
egs
#define BOARD_RAMPS_14_EFB 43 // RAMPS 1.4 (Power outputs: Hotend, Fan, Bed)
#define BOARD_RAMPS_14_EEB 44 // RAMPS 1.4 (Power outputs: Hotend0, Hotend1, Bed)
#define BOARD_RAMPS_14_EFF 45 // RAMPS 1.4 (Power outputs: Hotend, Fan0, Fan1)
#define BOARD_RAMPS_14_EEF 46 // RAMPS 1.4 (Power outputs: Hotend0, Hotend1, Fan)
#define BOARD_RAMPS_14_SF 48 // RAMPS 1.4 (Power outputs: Spindle, Controller Fan)
Remember that D8 is what ever voltage you apply to the 11amp 12v power pins
But D9 and D10 are what ever voltage you apply to the 5amp 12v power pins, and will be 12v on normal systems. (needed by stepper driver)
I don’t know what your laser takes to power, but if this was me I would use BOARD_RAMPS_14_EEF so the laser is on D8 and you can set what ever supply it needs to the 11amp 12v power plug
If your doing something totally custom, you can edit what pin is being used for the fan by editing pins_RAMPS.h and compiling a custom firmware
NB if you get this working, please post results
↧
Re: Induction Z Probe on Z Max, NOT Z Min
Quote
obewan
connect the probe to zmin and remove the mechanical switch, you the use the probe for zmin homeing and bed levelling.
However, i have had more consistant results useing a z max mechanical switch and probe on z min for levelling (useing repetier firmware tho atm)
OH I got it now. It is Z probe OR Zmin mechanical switch, not both.
Makes sense.
Thanks!
↧
↧
Re: Any Experience for SD Card Logging
Quote
Roxy
I think we could be a little more elegant about it. Ignoring the SD-Memory card case, we could have the host computer keep track of how far it got. And it could do some clever things to recover and start from where it left off. Probably, it would have to do things like re-align the nozzle and purge some filament.
Is there any software exist for this aim?
Best Regards
↧
Bed Leveling RC8
Hi again,
Thanks for the help telling me to use ZMin end stop for my inductive z probe.
Now, I try to get the bed leveling setup in configuration.h.
With Z_SAFE_HOMING enabled I get the following message:
"Z_SAFE_HOMING_X_POINT can't be reached by the Z probe."
If I disable Z_SAFE_HOMING new error says -
"The given LEFT_PROBE_BED_POSITION can't be reached by the Z probe."
SanityCheck.h says -
//Make sure probing points are reachable.
#if LEFT_PROBE_BED_POSITION < MIN_PROBE_X
#error "The given LEFT_PROBE_BED_POSITION can't be reached by the Z probe."
I cannot find where MIN_PROBE_X and MAX_PROBE_X is defined.
I read another post that sounded close to the configuration I had, Home is X Max and Y Max. Something about the bed being oriented differently then what logic says. However, I got lost in the text.
Is this my issue, too? is 0,0 really Back and not the front? or was it saying the opposite?
Print bed is 120 x 120. (ToyRep!)
Z probe in on the "left" of the hot end,
Here is a picture of my printer that I am currently working on - [www.thingiverse.com]
Help me again please.
Thanks for the help telling me to use ZMin end stop for my inductive z probe.
Now, I try to get the bed leveling setup in configuration.h.
With Z_SAFE_HOMING enabled I get the following message:
"Z_SAFE_HOMING_X_POINT can't be reached by the Z probe."
If I disable Z_SAFE_HOMING new error says -
"The given LEFT_PROBE_BED_POSITION can't be reached by the Z probe."
SanityCheck.h says -
//Make sure probing points are reachable.
#if LEFT_PROBE_BED_POSITION < MIN_PROBE_X
#error "The given LEFT_PROBE_BED_POSITION can't be reached by the Z probe."
I cannot find where MIN_PROBE_X and MAX_PROBE_X is defined.
I read another post that sounded close to the configuration I had, Home is X Max and Y Max. Something about the bed being oriented differently then what logic says. However, I got lost in the text.
Is this my issue, too? is 0,0 really Back and not the front? or was it saying the opposite?
Print bed is 120 x 120. (ToyRep!)
Z probe in on the "left" of the hot end,
Here is a picture of my printer that I am currently working on - [www.thingiverse.com]
Help me again please.
↧
Re: Bed Leveling RC8
In configuration.h
#define X_PROBE_OFFSET_FROM_EXTRUDER -22 // X offset: -left +right [of the nozzle]
#define Y_PROBE_OFFSET_FROM_EXTRUDER 0 // Y offset: -front +behind [the nozzle]
#define Z_PROBE_OFFSET_FROM_EXTRUDER 1.5 // Z offset: -below +above [the nozzle] (how far nozzle is above bed when probe triggers)
#define X_PROBE_OFFSET_FROM_EXTRUDER -22 // X offset: -left +right [of the nozzle]
#define Y_PROBE_OFFSET_FROM_EXTRUDER 0 // Y offset: -front +behind [the nozzle]
#define Z_PROBE_OFFSET_FROM_EXTRUDER 1.5 // Z offset: -below +above [the nozzle] (how far nozzle is above bed when probe triggers)
↧
Re: Bed Leveling RC8
Quote
Eddiie
I cannot find where MIN_PROBE_X and MAX_PROBE_X is defined.
Those are setup in Conditionals.h to assist and make various other checks easy. Focus on gettting these #defines correct and you will be close:
In RCBugFix's Configuration.h at about line 720:
// Travel limits after homing (units are in mm)
#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 200
#define Y_MAX_POS 200
#define Z_MAX_POS 200
and at about Line 800:
// Set the number of grid points per dimension.
#define ABL_GRID_MAX_POINTS_X 3
#define ABL_GRID_MAX_POINTS_Y ABL_GRID_MAX_POINTS_X
// Set the boundaries for probing (where the probe can reach).
#define LEFT_PROBE_BED_POSITION 15
#define RIGHT_PROBE_BED_POSITION 170
#define FRONT_PROBE_BED_POSITION 20
#define BACK_PROBE_BED_POSITION 170
// The Z probe minimum outer margin (to validate G29 parameters).
#define MIN_PROBE_EDGE 10
// Probe along the Y axis, advancing X after each column
//#define PROBE_Y_FIRST
↧
↧
Re: Any Experience for SD Card Logging
Quote
yuzmemak
Is there any software exist for this aim?
Best Regards
I'm not sure how to answer that. I'm thinking hard about it. I've had a couple of difficult prints fail after 12 or 15 hours. And I was able to get them restarted successfully. I was manually issuing GCode commands. And I needed to home in a corner instead of in the center of the bed because the part (a big skull!!!!) was in the center of the bed.
I've got a couple of ideas how to do this. But no software has been written yet.
↧
Re: Induction Z Probe on Z Max, NOT Z Min
Eddie: You can configure your machine however you want. But really... If you have a Z-Probe, you probably don't need a Z-Min limit switch. It will just add complexity. And most likely, things will be simpler if you put the Z-Probe on the Z-Min connector of your electronics board.
↧
Re: Bed Leveling RC8
Great! So RCBugfix is newer than RC8? Is RCBugfix always newer? Seems there was a RC6 bug fix too.
So, the front is the front and the back is the back?
My current values are:
// Travel limits after homing (units are in mm)
#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 120
#define Y_MAX_POS 120
#define Z_MAX_POS 120
// Set the number of grid points per dimension.
#define ABL_GRID_POINTS_X 3
#define ABL_GRID_POINTS_Y ABL_GRID_POINTS_X
// Set the boundaries for probing (where the probe can reach).
#define LEFT_PROBE_BED_POSITION 0
#define RIGHT_PROBE_BED_POSITION 90
#define FRONT_PROBE_BED_POSITION 0
#define BACK_PROBE_BED_POSITION 90
// The Z probe minimum outer margin (to validate G29 parameters).
#define MIN_PROBE_EDGE 10
does not compile in RC8, errors are mentioned in the OP.
Will try RCBugfix.
Thanks!!
So, the front is the front and the back is the back?
My current values are:
// Travel limits after homing (units are in mm)
#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 120
#define Y_MAX_POS 120
#define Z_MAX_POS 120
// Set the number of grid points per dimension.
#define ABL_GRID_POINTS_X 3
#define ABL_GRID_POINTS_Y ABL_GRID_POINTS_X
// Set the boundaries for probing (where the probe can reach).
#define LEFT_PROBE_BED_POSITION 0
#define RIGHT_PROBE_BED_POSITION 90
#define FRONT_PROBE_BED_POSITION 0
#define BACK_PROBE_BED_POSITION 90
// The Z probe minimum outer margin (to validate G29 parameters).
#define MIN_PROBE_EDGE 10
does not compile in RC8, errors are mentioned in the OP.
Will try RCBugfix.
Thanks!!
↧