[quote]with the old firmware it was the same, but the second time the probe goes down, it was very quick.
Is it possible to get this speed back?
and what are the settings to do this?[/quote]
I haven’t found a feed rate for the probing movements in the config files. The following are in confiaration.h
These look to control the homing feedrate but are the same as the none leveling firmware so I don’t think they will have any effect.
//// MOVEMENT SETTINGS
#define NUM_AXIS 4 // The axis order in all axis related arrays is X, Y, Z, E
#define HOMING_FEEDRATE {50*60, 50*60, 4*60, 0} // set the homing speeds (mm/min)
As your bed is not likley to be far out of level you can reduce the distance the probe is raised to speed things up that way.
[code] #define Z_RAISE_BEFORE_HOMING 4 // (in mm) Raise Z before homing (G28) for Probe Clearance.
// Be sure you have this distance over your Z_MAX_POS in case
#define XY_TRAVEL_SPEED 8000 // X and Y axis travel speed between probes, in mm/min
#define Z_RAISE_BEFORE_PROBING 15 //How much the extruder will be raised before traveling to the first probing point.
#define Z_RAISE_BETWEEN_PROBINGS 5 //How much the extruder will be raised when traveling from between next probing points[/code]
The the actual feedrates are set in the marlin file. If you open it with wordpad you can serch for “feedrate”, some of the Z axis feeds are /60. It’s not something that I have changed.
[quote]#define Z_RAISE_BEFORE_HOMING 4 // (in mm) Raise Z before homing (G28) for Probe Clearance.
// Be sure you have this distance over your Z_MAX_POS in case
#define XY_TRAVEL_SPEED 8000 // X and Y axis travel speed between probes, in mm/min
#define Z_RAISE_BEFORE_PROBING 15 //How much the extruder will be raised before traveling to the first probing point.
#define Z_RAISE_BETWEEN_PROBINGS 5 //How much the extruder will be raised when traveling from between next probing points[/quote]
I have already changed this values many times, but it looks like there is changing nothing.
I have changed all 3 settings to 1mm
Hi dutchronnie, I’ve finaly got my autoleveling reloaded up tonight after getting the lead screw mods fitted and all seems good.
Checked the bed in 4 places (50,50 50,150 150,150 & 150,50) then printed a 150mm square 0.35mm thick 4 perimeters wide.
On checking the thickness it varied from 0.28mm to 0.33mm, I was no where close to that prior to loading. Given that I’m only using baking foil under the glass I think thats quite good. I have a piece of 3mm aluminium on order to replace the foil & then I can scrap the adjusters. I put tape on the leadscrews to check they are moving during the print and they are 
so more printing & time will tell how good it proves to be.
I’m not quite sure what they all mean but this is the return I get from the G29 command.
[code] G29 Auto Bed Leveling
Eqn coefficients: a: 0.00070937 b: -0.00040312 d: 0.03015623
planeNormal x: -0.000709 y: 0.000403 z: 1.000000
Bed Level Correction Matrix:
+1.000000 +0.000000 +0.000709
+0.000000 +1.000000 -0.000403
-0.000709 +0.000403 +1.000000
[/code]
How are you getting on?
Well i think it is oke, but i didn’t see my z axis moving when he is printing.
This are my results of the G29 command:
19:15:53.019 : G29 Auto Bed Leveling
19:16:58.298 : Eqn coefficients: a: 0.00001226 b: 0.00164978 d: 2.95263748
19:16:58.298 : planeNormal x: -0.000012 y: -0.001650 z: 1.000000
19:16:58.298 :
19:16:58.298 : Bed Level Correction Matrix:
19:16:58.298 : 1.000000 0.000000 0.000012
19:16:58.298 : -0.000000 0.999999 0.001650
19:16:58.298 : -0.000012 -0.001650 0.999999
19:16:58.298 : ok
19:16:58.298 : echo:endstops hit: Z:3.29
Before i attached the sensor my heatbed was extremely flat, maybe that is the reason i didn’t see my z axis motor turning
Make sure that your slicer isn’t putting a G28 into the start code after you have your G29.
G28 will cancel auto leveling.
Mine to but it does move very slightly 1/10 of a turn over 100mm.
[quote]Make sure that your slicer isn’t putting a G28 into the start code after you have your G29.
G28 will cancel auto leveling.[/quote]
Thats why i didn’t see the z axis moving, after the G28 i did a G29, and again a G28.
So i removed the second G28 command, but it gave me another problem.
The print starts in the air, and the nozzle didn’t move to 0.2mm above the heatbed.
This is how my start code looks like:
G28 X0 Y0 Z0 ; home all axes
G29 ; Auto bed leveling
G90 ; use absolute coordinates
G21 ; set units to millimeters
G92 E0
G1 E10 F400 ; prime the nozzle
M82 ; use absolute distances for extrusion
M109 S225 ; wait for temperature to be reached
How do i get the nozzel back to the printbed?
I don’t understand why the nozzle goes to 0.2 mm above the bed when i give a second G28, and when i remove the G28 it don’t
I’m on the latest build which has this option (the latest build is very buggy I would not recomend at this time).
#define Z_PROBE_END_SCRIPT "G1 Z5 F12000\nG1 X0 Y0\nG1 Z0.0" //These commands will be executed in the end of G29 routine.========UNCOMMENTED & CHANGED========
I would try
G28 X0 Y0 Z0 ; home all axes
G29 ; Auto bed leveling
G1 Z5
G1 X0 Y0
G1 Z0
G90 ; use absolute coordinates
G21 ; set units to millimeters
G92 E0
G1 E10 F400 ; prime the nozzle
M82 ; use absolute distances for extrusion
M109 S225 ; wait for temperature to be reached
That should take you back to the home postion and be touching the bed.
If the nozzle is still high use an M851, this will return the current offeset.
Then use M851 Z-?.?? to adjust the gap and M500 to save.
Then try again.
I have tried your code, but doesn’t work with my printer.
When the printer has done the G29
then it returns very, very slowly to the x0 and y0
then it stops and and makes no print.
I have set the offset with M206 Z3.35
i will now try with the M851 Z3.35
20:05:40.486 : echo:Steps per unit:
20:05:40.486 : echo: M92 X80.37 Y80.49 Z2560.00 E759.68
20:05:40.487 : echo:Maximum feedrates (mm/s):
20:05:40.487 : echo: M203 X500.00 Y500.00 Z5.00 E500.00
20:05:40.487 : echo:Maximum Acceleration (mm/s2):
20:05:40.487 : echo: M201 X9000 Y9000 Z100 E10000
20:05:40.487 : echo:Accelerations: P=printing, R=retract and T=travel
20:05:40.487 : echo: M204 P1000.00 R1000.00 T1000.00
20:05:40.487 : echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
20:05:40.487 : echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
20:05:40.487 : echo:Home offset (mm):
20:05:40.487 : echo: M206 X0.00 Y0.00 Z0.00
20:05:40.487 : echo:PID settings:
20:05:40.487 : echo: M301 P25.85 I3.06 D54.64
20:05:40.487 : echo:Filament settings: Disabled
20:05:40.487 : echo:Z-Probe Offset (mm):
20:05:40.487 : echo: M851 Z-3.35
20:05:40.487 : ok
This is my result of a M501 command.
the distance i had first was with the M206 command Z3.35.
with M851 it is Z-3.35, so it is now a negative value.
It looks better now, but the distance is now bigger, it is stil to high above the heatbed.
printing with auto bed leveling goes fine now, but now i have an other issue.
i always slice with slic3r, because it gives me the best results. but i want also slice with cura or curaengine.
but when i slice a object with cura, the print starts higer than an object sliced with slic3r.
How is this possible?
i assume the offset values must always be the same.
Hi, can you post both start sections of gcode please. You are correct about the settings should be the same for both, it must be the instructions that are created by the slicer.
Just found the problem, i thought the startcode was the same with both slicers, but it wasn’t
In slic3r i have command G1 Z0,
But it wasn’t in curaengine.
Now i changed and the nozzle is going to the heatbed.
Thanks.
Dutchronnie
I am using the sensor and circuit recommended here thingiverse.com/thing:447719
LJC18A3-H-Z/BY (PNP Capacitive Proximity Switch)
I noticed you are using a one that ends in BX
Any idea what’s different?
The original switch that came with the printer is normally closed
The sensor is normally open. Not sure what difference that makes?
I think I can adjust for that in the software configure.hB
So right now I have printed the holder and attached the sensor to my printer
I have wired up the circuit and powered the sensor from controller board
(I have left old switch and wiring in place and just have it plugged out for now so
I can easily switch between both methods until I get new sensor working)
I have downloaded new marlin firmware and adjusted configure.h
So all looks good so far … Well may not
I having no joy . My z-axis seems to home way up the z axis and I have trouble getting it to come down
When I issues auto bed command sensor moves to four points but about 10cm above the bed.
I’d like to check my circuit behavior first and then check config.h
Could anybody advise how to check circuit behavior with a multimeter
Or have advice on z axis issue
Thanks for help
Noel
Hi, this video explains how to do the mod. https://www.youtube.com/watch?v=EcGFLwj0pnA
That sensor should be fine. Have you change any settings in the confgaration and configaration_adv? If not it will not be able to home correctly and as such it will not move downwards.
Does the fact that he is using an inductive sensors and I am using a capacitive sensor make any difference ?
I had come across this great video but thought as we were using two different sensor types that it was not that relevant
I will watch it again tks
tks
Noel
Hi, no it’s just the type of dark magic that goes off in the sensor, the output from the sensor should be the same (normaly open is the relevent bit).
I am not using an inductive sensor, but a capacitive sensor.
both sensors are the same.
The difference between the sensors is:
Inductive sensor - react on metal.
Capacitive sensor react on more materials, glass, metal enz.
I use a glassplate on the heatbed, so the best choice for me is an capacitve sensor.
I made some good progress but still not working overall.
Thomas Sanladerer video was a great help youtube.com/watch?v=EcGFLwj0pnA
Step 1
I rebuilt the little circuit using the resistor voltage divider and have refitted sensor to the printer.
When the sensor is not activated (LED Off) I have OV on signal and 5v when activated (checked with multimeter)
I did not change firmware yet
So to start I just used the sensor as a replacement for my existing z-endstop switch and all worked fine
Step 2
I configured marlin firmware as advised
As I am using a different sensor to Thomas Sanladerer which triggers opposite way to his
I have left " const bool Z_MIN_ENDSTOP_INVERTING = false;"
I uploaded firmware and used :
G28 which now homes bed so that sensor is over middle of bed
G29 which moves bed so that sensor is over 4 points does its thing
This returns the following
G29
<-Bed x: 50.00 y: 50.00 z: 1.14
<-Bed x: 150.00 y: 50.00 z: 0.76
<-Bed x: 150.00 y: 150.00 z: 0.57
<-Bed x: 50.00 y: 150.00 z: 0.85
<-Eqn coefficients: a: -0.00 b: -0.00 d: 1.40
<-planeNormal x: 0.00 y: 0.00 z: 1.00
<-ok
<-echo:endstops hit: Z:0.85
(BTW I am using Mattercontrol for controlling printer. I have had very poor connection with repetier host on Mac.
I can not find a terminal window on Cura any where)
How ever when I print the bed is not auto levelling
I print the large calibration circle from mattercontrol (which has printed fine pre Auto bed leveling )
However the results are very bad - much worse than what I had pre ABL.
Half the first layer is squashed in to the bed, some of it looks ok and some is like small blobs.
I have tried adjust the z off set but I don’t think thats the issue as I should have a complete hit or miss if this is wrong
Its like the auto-bed levelling is not actually running at all
I have z offset set to -.5 (also tried .62 using Tom Sandler method)
Question
-
in Mattercontrol I am typing G28/G29 into terminal window ,let it do its thing and in Mattercontrol then pressing print
When I put G29 in start GCode it does nothing. Also it does not save (I have emailed mattercontrol re this)
-
The sensor has a small screw on top that lets you adjust the range. I have my sensor very close to the height of my nozzle (just slightly higher)
Any potential issues here
-
After you run G29 does the firmware store the results and use the adjustment or do you need to do something else
Any advice appreciated
Reminder
I am using LJC18A3-H-Z/BY (PNP Capacitive Proximity Switch)
Hi, just on way out so cant give long answer.
Don’t use G28 after G29 it cancels the auto leveling - also check you don’t have a G28 in your start code.
I have loaded the latest firmware from the Marlin site, not the Velleman firmware.
If you use this firmware load it with the latest arduino software, not version 1.0.6, this is for the velleman firmware.
Then set the offset with the M851 command, example M851 Z-0.85
the the M500 command to save to eeprom.
so more printing & time will tell how good it proves to be.