richcattell / marlin Goto Github PK

This is tough to explain, but I'll try.

Love the FW btw, it's awesome, just one thing I may be missing here.

After a G28 command, I bring the head down to check the level of the bed, it is closer to the bed towards the front of the machine and further off the bed in the back. After running a G29, I find that it prints too close to the bed in the back and barely touches in the front. Maybe I'm missing something here, but it seems like it's applying the auto level measurements backwards.

I have triple checked my steps per mm and they are spot on. Also triple checked all my delta variables and verified the rods are the same length. My axes are all in the proper directions. The auto level and calibration starts at the proper location in the +X and +Y quadrant. The probe offset is correct.

Any ideas?

Thanks in advance!

When running the G30 A command I notice 4 of the 7 measurement points are well within range after few iterations and 3 (ox, oy and oz) are way off and don't seem to improve much:

c:    0.0016 
z:    0.0017
ox:  -0.0919
x:   -0.0019
oy:  -0.0769
y:    0.0091
oz:   0.1592

The ox, oy and oz are the positions where the opposite arm has to extend the most. With my probe on the side of the x tower oz has to extend the furthest of the three and this is also the position with the highest offset.

Could this be an inaccuracy in some parameter that is not covered by the calibration? Like motor feed rate (88.8889: GT2 / .9 degree motor / 16 microsteps / 36 teeth), carriage has to descend the most for those positions? Or rod length, effect of length error becomes more significant when extending?

After homing, the hotend start heating! If any movement to accomplished, continues to heat up to 250C. When it is stopped for a few minutes, the temperature starts to slow down.

#define Autotemp is disable.

What can I do to disable this procedure?

Hello!

I noticed that this isn't a proper fork of the marlin git repo. As a result, I'm trying to reconcile these changes against the mainline marlin trunk so that I can more easily merge over my own changes. In order to do that effectively, I need to figure out approximately what commit to Marlin that this fork is based on.

If you don't know exactly which commit, then an approximate time period would help narrow the search considerably.

Could someone add g-codes G131 and G132 as can repetier

Hi,

Works Ok with Mechanical switch , but when i use a hall effect, it seems to keep sampling as the probe is retracting for an over sample. This results in ascending values for a single probe point. IE :-1.858 0.130 2.117 4.105 6.092 Any ideas?

I have one issue with this function if you send :

M666 P X... Y... Z...

X and Y work Z return to 0.

In master branch

I do the following and the U, V, W values are wiped out or appear to be.
M666 U1 V2 W3
M500
M666 L // U = 1, V = 2, W = 3
Reset printer
M666 L // U, V, W now all 0

Log from Pronterface

m666 u-1 v-2 w-3
SENDING:M666 U-1 V-2 W-3
m666 l
SENDING:M666 L
Current Delta geometry values:
X (Endstop Adj): -1.663
Y (Endstop Adj): -0.613
Z (Endstop Adj): -1.675
P (Z-Probe Offset): X0.00 Y0.00 Z0.10
A (Tower A Position Correction): 0.000
B (Tower B Position Correction): 0.000
C (Tower C Position Correction): 0.448
I (Tower A Radius Correction): 0.000
J (Tower B Radius Correction): 0.000
K (Tower C Radius Correction): -0.241
U (Tower A Diagional Rod Correction): -1.000
V (Tower B Diagonal Rod Correction): -2.000
W (Tower C Diagonal Rod Correction): -3.000
R (Delta Radius): 182.21
D (Diagonal Rod Length): 287.10
H (Z-Height): 256.83
m500
SENDING:M500
echo:Settings Stored
Reset.
start
echo: External Reset
Marlin RC Testing 2015-01-26
echo: Last Updated: Jan 26 2015 21:19:28 | Author: (David Fruehwald, Ultibots K250VS)
Compiled: Jan 26 2015
echo: Free Memory: 1677 PlannerBufferBytes: 1232
echo:Stored settings retrieved
echo:Steps per unit:
echo: M92 X80.00 Y80.00 Z80.00 E820.00
echo:Maximum feedrates (mm/s):
echo: M203 X200.00 Y200.00 Z200.00 E200.00
echo:Maximum Acceleration (mm/s2):
echo: M201 X4500 Y4500 Z4500 E4500
echo:Acceleration: S=acceleration, T=retract acceleration
echo: M204 S1000.00 T3000.00
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)
echo: M205 S0.00 T0.00 B20000 X2.00 Z2.00 E5.00
echo:Home offset (mm):
echo: M206 X0.00 Y0.00 Z0.00
echo:Delta Geometry adjustment:
echo: M666 A0.000 B0.000 C0.448 I0.000 J0.000 K-0.241 R182.21 D287.10 H256.83
echo:Endstop Offsets:
echo: M666 X-1.66 Y-0.61 Z-1.67
echo:Z-Probe Offset:
echo: M666 P X0.00 Y0.00 Z0.10
echo:PID settings:
echo: M301 P18.62 I1.37 D63.14
echo:SD card ok
m666 l
SENDING:M666 L
Current Delta geometry values:
X (Endstop Adj): -1.663
Y (Endstop Adj): -0.613
Z (Endstop Adj): -1.675
P (Z-Probe Offset): X0.00 Y0.00 Z0.10
A (Tower A Position Correction): 0.000
B (Tower B Position Correction): 0.000
C (Tower C Position Correction): 0.448
I (Tower A Radius Correction): 0.000
J (Tower B Radius Correction): 0.000
K (Tower C Radius Correction): -0.241
U (Tower A Diagional Rod Correction): 0.000
V (Tower B Diagonal Rod Correction): 0.000
W (Tower C Diagonal Rod Correction): 0.000
R (Delta Radius): 182.21
D (Diagonal Rod Length): 287.10
H (Z-Height): 256.83

I was wondering if RichCattell was ever planning on incorporating code to support a bluetooth module. As is, the I can use bluetooth to send data from the serial port to my laptop. Unfortunately, I am unable to send commands to the arduino with the bluetooth module without changes to the code it seems.
Thanks in advance!

Hi Rich,

This firmware is very promising thanks for sharing, been testing it out I am facing a strange problem, when I auto calibrate, the offset probe tip shows good leveled result over the bed. But when I test nozzle tip the leveling is gone. I have set probe offsets properly, how can I get same good level on nozzle with an offset probe? M666L on my machine shows, thanks for any tip.

X (Endstop Adj): -3.315
Y (Endstop Adj): -0.030
Z (Endstop Adj): -1.195
P (Z-Probe Offset): X-0.70 Y22.40 Z-6.00
A (Tower A Position Correction): 0.000
B (Tower B Position Correction): 0.000
C (Tower C Position Correction): 0.000
I (Tower A Radius Correction): -1.125
J (Tower B Radius Correction): -4.125
K (Tower C Radius Correction): -2.531
U (Tower A Diagional Rod Correction): 0.000
V (Tower B Diagonal Rod Correction): 0.000
W (Tower C Diagonal Rod Correction): 0.000
R (Delta Radius): 114.66
D (Diagonal Rod Length): 217.84
H (Z-Height): 216.13

With one extra sample at the center after you determine the plane, you could calculate the horizontal rod radius.

Hi,

I know you're doing some fixes, but just for testing I installed the current development version and I noticed it does not honor the values listed with M666L
P (Z-Probe Offset): X-0.60 Y-17.70 Z-1.30

I just wanted you to know in case it is of use.

Cheers,

Miguel Sanchez

I want to modify the constant that calibrate the high between the extruder and hootbed ( see the picture below).

What's the defined constant to adjust it?

The issue is that I not know how to indicate to the printer the hight between the end of the sensor and the nozzel.

Could you help me? Thx

Hi RichCattell,

On Marlin_main.cpp Line 1619
if (bed_level_z + endstop_adj[2] < l_endstop) l_endstop = bed_level_x + endstop_adj[2];

Is it a bug? Shouldn't it be "bed_level_z" ?

Regards,
Clarence

So, I recently build a delta printer, and am trying to use the FSR's to perform an autocalibration. I'm getting a bizarre behavior that I can't figure out. I'll post the output from pronterface:

Connecting...
start
Printer is now online.
echo: External Reset
Marlin 1.0.0
echo: Last Updated: Mar 1 2015 15:21:32 | Author: (K250VS-MB-FSR-BOM)
Compiled: Mar 1 2015
echo: Free Memory: 2551 PlannerBufferBytes: 1232
echo:Stored settings retrieved
echo:Steps per unit:
echo: M92 X80.00 Y80.00 Z80.00 E800.00
echo:Maximum feedrates (mm/s):
echo: M203 X500.00 Y500.00 Z500.00 E200.00
echo:Maximum Acceleration (mm/s2):
echo: M201 X4500 Y4500 Z4500 E500
echo:Acceleration: S=acceleration, T=retract acceleration
echo: M204 S1500.00 T1000.00
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)
echo: M205 S0.00 T0.00 B20000 X2.00 Z2.00 E2.50
echo:Home offset (mm):
echo: M206 X0.00 Y0.00 Z0.00
echo:Endstop adjustment (mm):
echo: M666 X0.00 Y0.00 Z0.00
echo:Delta Geometry adjustment:
echo: M666 A0.00 B0.00 C0.00 E0.00 F0.00 G0.00 R171.50 D288.00 H233.00 P0.00
echo:PID settings:
echo: M301 P18.62 I1.37 D63.14
echo:SD init fail
SENDING:G28

m502
SENDING:M502
echo:Hardcoded Default Settings Loaded
m500
SENDING:M500
echo:Settings Stored
g28 a d288.0
SENDING:G28 A D288.0
g30 a d288.0
SENDING:G30 A D288.0
Starting Auto Calibration..
Calibration precision: +/-0.040mm
|
-0.4000
-20.0000
-20.0000 Exact Match: -20.0000 Range: 19.6000 mm
|
-9.5875 -6.6000 -3.6125 -0.6250 2.3625 5.3500 8.3375 Mode/Median: -0.6250 Range: 17.9250 mm
|
-19.5500 -16.5625 -13.5750 -10.5875 -7.6000 -4.6125
-19.7750 Mode/Median: -13.5750 Range: 15.1625 mm
|
-20.0000
-20.0000 Exact Match: -20.0000 Range: 0.0000 mm
|
-20.0000
-20.0000 Exact Match: -20.0000 Range: 0.0000 mm
|
-20.0000
-20.0000 Exact Match: -20.0000 Range: 0.0000 mm
|
-18.8375
-18.7875
-18.8000
-18.8250
-18.8250 Exact Match: -18.8250 Range: 0.0500 mm
| Z-Tower Endstop Offsets
| -0.6250 X:0.00 Y:0.00 Z:0.00
| -13.5750 -18.8250 Tower Offsets
| -20.0000 A:0.00 b:0.00 C:0.00
| -20.0000 -20.0000 I:0.00 J:0.00 K:0.00
| -20.0000 Delta Radius: 171.5000
| X-Tower Y-Tower Diagonal Rod: 288.0000
Using diagional rod length: 288.00mm (will not be adjusted)
The position of the endstop switches on this printer are not within limits
Adjust endstop switches so that they are within 3mm Z-height of each other
Current Endstop Positions - X: -20.00 Y: -20.00 Z: -0.62
Autocalibration aborted

The strange behavior starts after the autocalibrate command The printhead comes down and taps the center of the printbed once, the fsr light goes from red to green, and i get the -0.4000 value. The head then moves up about 30 mm, then travels almost halfway to the z column of the printer. It then moves twice back down toward the printbed, but each time it stops short of the printbed, the FSR never triggers (LED stays green the whole time), and it returns -20.0000 twice.
The printhead then proceeds to various spots on the printbed, sometimes tapping the bed, activating the FSR, and returning real values, but most of the time just thrusting down toward the bed without actually contacting it. Whenever it fails to hit the actual bed, it returns -20.000.
At this point I'm just about out of ideas. Any help would be appreciated.
Tim

I'm a little confused about tower names. Could you clarify? My X motor is plugged into my front-left tower, my Y motor is the front-right tower, and the Z motor is the rear center tower. I tried a few manual adjustments and I think what I'm seeing is the A tower is the rear center tower, the B tower is front-left, and the C tower is front-right.

Is that how your firmware is referring to it? Which would be the X, Y, and Z endstop in firmware?

Hi :)

Having spent a couple of days trying to get my delta dialed in makes me appreciate this marlin fork a lot.

I've just run into a wee problem: the hotend heater turns on to full power when I run G30 A and stays on, even after I hit the reset button on the reprapdiscount lcd panel. The result was me wondering what that burning smell was while my jhead goes over the max temp and starts to cook its PEEK holder and PTFE liner.

Is anyone else experiencing this?

Hi,

I was installing the Pibot IR sensor for bedleveling and that works great, however I discovered 2 very odd behaviours in the process.

1. When I initially configured my new Delta I had a super convex bed shape. The difference between the middle of the bed and the point near the tower were 130mm. I uploaded the main branch marlin but could make the autolevel work there so I switched back to RCMarlin and it behaved normally.
2. Now that autolevel works here, the extrusion is completely of. If I give an extrusion command all other motors start slowly creeping upwards. All 3 XYZ at the same time at the same rate, and the extruder motor does nothing.

Hi Rich,

Great work on the code. So far, I have been using your latest released version and tried to update yesterday to your latest development version.

With your v1.04, you had the ability to "lock" the delta_rod_lengths by typing G30 A Dxxx, however, this doesn't seem to work anymore in the new code. Any plans on adding this, or am I using the wrong gcode to get this done?

Thanks,
R

M666 L was updated with U, V, W reporting, but M503 does not report them at this time.

When I attempt to compile there are lots of missing files. I am using win7 64 and Arduino.ide 1.5 and 1.6 to install your marlin on a melzi. Have not been able to load firmware. May I ask what boot loader files and which compiler any one is using. It has been a very frustrating few months. If any one can help I would really appreciate the help and happily supply more details

Hi,

I am doing a few tests on the delta moves using different Marlin distribution (i.e. Zalm, Cattell, Hercek). I encountered a problem when testing manual moves using both Repetier-Host and Pronterface. As discussed here (http://forums.reprap.org/read.php?267,355792) and here (https://groups.google.com/forum/#!topic/deltabot/tUJ1ty6yebg) the main thing that we are testing is the furthest reach of the delta arms using numeric manual moves. (one of the carriages is at 0.00 or close)
The initial problem is that at a certain point (where the delta arm cannot reach according to its length) one of my steppers gets stuck running continuously. It would be better if it stop al together rather than running wild.
M114 in both hosts show that after such point one the carriage is sent to a very low position (negative number) causing it to spin continuously.
http://forums.reprap.org/file.php?267,file=33256
Repetier-Host:
X:0.00Y:0.00Z:0.00E:0.00 Count X: 253.31Y:253.31Z:253.31
X:0.00Y:104.45Z:0.00E:0.00 Count X: 205.79Y:205.79Z:274.00
X:134.30Y:104.45Z:0.00E:0.00 Count X: 3.68Y:220.47Z:238.83
X:134.40Y:104.45Z:0.00E:0.00 Count X: -958.72Y:220.47Z:238.83
Pronterface:
X:0.00Y:0.00Z:0.00E:0.00 Count X: 253.31Y:253.31Z:253.31
X:0.00Y:104.45Z:0.00E:0.00 Count X: 205.79Y:205.79Z:274.00
X:134.30Y:104.45Z:0.00E:0.00 Count X: 3.68Y:220.47Z:238.83
X:134.40Y:104.45Z:0.00E:0.00 Count X: -418.61Y:220.47Z:238.83

Would it be possible to limit the position of the carriage to no less than Z + Vertical effector offset?

This would avoid the carriages to try to reach a position lower than the effector. In addition to changing the software end stops to simulate a triangular region rather than a rectangular or circular one, might even be used as an improved software end stop for the Delta's.

Is there a reason to leave VERSION_STRING as 1.0.0 in Marlin_Main.cpp?

It seems like it should match the release number (currently 1.0.4)

Hi
I built a Rostock/ Kossel hybrid delta.
It prints perfect but wants to get auto bed leveling going
I set everything up and run G29 after g28
The printer probes 2 rows 5 probes each and the lowers the nozzle onto the bed and start hitting the bed erratic as if it wants to move to a point below the bed somewhere
I'm sure it's something I did wrong, maybe a setting but has no idea where to start...
After G29 should the printer zero at the top or will it just wait at the bottom? I assume if it runs a program to print it will go immediately onto the print job but with variable bed?
Hope someone can help?
Theo

Hi,

I had this version working half a year ago and came back to it with my new inductive proximity sensor.

I have configurated everything the same but now as soon as I click home I get some soft motor whining and very slow creeping of the axis.

Has there anything changed in this version or is that another issue?

Cheers

hello, I have a problem with your firmware when I send a signal M119 z-probe returns me always open yet so I plug zmax it works. Is this a bug, or is it that I am doing something wrong?

hi i try to use M43 P63 W (pin 63 to get signal from sensor) if sensor on pin 63 return 1, if not return 0 (pin 63 is unused), how can i do it?

I am using this newest files and would like to measure the Z Endstop offset from the hotend so I enable the three lines of configuration.h; but I got error message and stop the comiling. what should I do? BTW, I disable these three lines tried to measure the offset data, I pull down the hotend above the surface of bed at 0.1mm, then set G92 X0 Y0 Z0, then key in G1 Z10 to try to pull hight Z10mm, I did tried G92 or G91 then but the hotend just went up to more than 15cm height, it wouldn't stop at Z 10mm. What should I change the setting to enable the function?
Regards,
Mark

I have a Geeetech G2S, which has a bit of a funny geometry compared to a kossel. The master branch of your autocalibrate seems to work fine with it though, saving me many hours of work!

I tried calibrating to 0.04 first, but it hit the iteration limit. I was successfully able to get the master branch to calibrate my printer with G30 A0.06, but due to one tower being positioned fairly off, I still have a wave big enough to cause issues. so in order to try to get it closer, I worked on it mechanically a bit, changed the end stop adjustments to make them more repeatable, and manually reset the end stops to where they started when I first tried out the Master branch, as level and flat as I could get without tower and individual tower radius corrections. Right now, after a reset to firmware defaults, it's flat with a slight wave at half the radius of perhaps +-0.05mm aligned with the Z tower (moved in a line between the tower and the furthest part opposite the tower, and about the same aligned with the Y tower. The X tower is way off, so I end up with 0 at the center and 0.6mm off at the tower and off by the same amount and same direction opposite the tower (radius and position error of that tower, I think). then I tried the development branch to get the latest calibration algorithm with A0.05.

I couldn't get the Z probe offset to behave in a sane manner, it seems it's moving diagonally from the z probe deploy point to the first touch point but triggering the probe before it gets there, so I set the printer's z-height much smaller than it is so that it'll at least complete that first point coming straight down.

What happens is the first 6 points touch properly, then the 7th (at the base of the tower with the largest misalignment) drags on the bed as it approaches that location, perhaps 20mm from that location, nearly causing it to crash and skip steps. The iteration completes, the output mentions it's adjusting endstops, and then the 8th point (at the Y axis tower, I guess the first point of the next iteration) starts way high . Then the 9th point (it goes in the direction of opposite the Y tower) crashes near half the radius on the other side of center, jams, and skips a bunch of steps. The testing branch behaves the same.

Any ideas what I could be doing wrong?

Is it possible to add the FSR feature from the bedleveling squence from Johann C. Rocholl (Brand fsr)?

or how could i read from the analog input as endstop and not from the digital one?

hi,

thank you for this marlin, but how to change x and y to z-probe because I can only change the value Z, please ??

I said that I already flasher this marlin with the new value, but it does not change the values

best regards

Greetings I hope you are well, my name is felix and I am super new working with 3D printers. And I currently have a mini rostock, with a proximity sensor and use of the Melzi board. The questions I have: Using this marlin firmware, the automatic calibration after every print and the firmware does everything automatically?
I do not have to point anything, just point the G29 in the print script, to do the autocalibration automatically and then start the impression?

As per my previous issue! My delta does about half of the bed leveling routine and then lowers the nozzle onto the bed and then try to drive it more down, causing steppers to skip steps and erratic pounding of nozzle on table.
I've been through all the setups 100 times now. My configuration.h and configadv.h is the same as in the examples I find here.
Please help?

it's normal i have much vibration on calibration and print ? I have a delta

I'm trying to get autocalibration working, and G30 is causing very nasty head crashes with my machine. Currently, G30 causes this sequence:

Home -> Lower head -> tap once near center -> move positive y -> touch bed multiple times -> move positive y -> smash head into bed and break effector.

I'm pretty sure the endstop switch is working, since it successfully taps the bed multiple times without causing any problems. What is causing these head crashes?

Hey there, I've been using the auto calibration on my delta using FSRs and have had 2 issues. (I'm running everything via Pronterface)

1. when the probe repeatedly probes the edge of the bed often times the FSR directly opposite will activate when the probe lifts. I think it is related to how FSRs are tared (how the code determines a baseline resistance, then looks for changes over a certain % of baseline resistance). After repeated probing it seems like opposite FSRs are tared, so that the weight of the bed activates them. This leads to the probe repeatedly reading as "activated" and calculating a giant range.

2. if I can get the FSRs to behave (although they usually have the error above at least once an autocalibration) the autocalibraiton continues even after the correct precision appears to be reached, although looking through the code I couldnt quickly figure out how precision is defined. It works fine for looser precision, IE A0.1 or 0.08, but once I get down to around 0.05 it just keeps going.

For instance, I ran G30 D288.04 A0.05

and got this (the calibration continued until iteration 99, then gave the normal successful calibration message:

Iteration: 52
Adjusting Z-Height to: 221.34 mm..
|
-7.1250
-7.1250 Exact Match: -7.1250 Range: 0.0000 mm
|
-7.0250
-7.0250 Exact Match: -7.0250 Range: 0.0000 mm
|
-7.0875
-7.0750
-7.0625
-7.0625 Exact Match: -7.0625 Range: 0.0250 mm
|
-7.0625
-7.0625 Exact Match: -7.0625 Range: 0.0000 mm
|
-7.3750
-7.3750 Exact Match: -7.3750 Range: 0.0000 mm
|
-7.2500
-7.2625
-7.2500
-7.2500 Exact Match: -7.2500 Range: 0.0125 mm
|
-7.3375
-7.3375 Exact Match: -7.3375 Range: 0.0000 mm
| Z-Tower Endstop Offsets
| -7.0250 X:-6.25 Y:-5.44 Z:-4.86
| -7.0625 -7.3375 Tower Offsets
| -7.1250 A:-0.04 b:-0.21 C:0.25
| -7.0625 -7.2500 I:0.00 J:0.00 K:-0.25
| -7.3750 Delta Radius: 171.8750
| X-Tower Y-Tower Diagonal Rod: 288.0400

then, after it reaches the 99th iteration:

Iteration: 99
Adjusting Z-Height to: 221.34 mm..
|
-7.1000
-7.0875
-7.1125
-7.1125 Exact Match: -7.1125 Range: 0.0250 mm
|
-6.9750
-7.0000
-7.0125
-7.0250
-7.0250 Exact Match: -7.0250 Range: 0.0500 mm
|
-7.0000
-7.0000 Exact Match: -7.0000 Range: 0.0000 mm
|
-7.0375
-7.0375 Exact Match: -7.0375 Range: 0.0000 mm
|
-7.3750
-7.3875
-7.3625
-7.3750
-7.3625
-7.3625 Exact Match: -7.3625 Range: 0.0250 mm
|
-7.2625
-7.2625 Exact Match: -7.2625 Range: 0.0000 mm
|
-7.3000
-7.3125
-7.3250
-7.3250 Exact Match: -7.3250 Range: 0.0250 mm
| Z-Tower Endstop Offsets
| -7.0250 X:-6.25 Y:-5.44 Z:-4.86
| -7.0000 -7.3250 Tower Offsets
| -7.1125 A:-0.04 b:-0.21 C:0.25
| -7.0375 -7.2625 I:0.00 J:0.00 K:-0.25
| -7.3625 Delta Radius: 171.8750
| X-Tower Y-Tower Diagonal Rod: 288.0400
Auto Calibration Complete
Issue M500 Command to save calibration settings to EPROM (if enabled)

Thanks for the help!

I don't know if this issue are on the Marlin Master 1.04 or the u8glib 1.17 (http://code.google.com/p/u8glib/wiki/u8glib)
HW: Arduino-compatible Mega2560+ RAMPS 1.4 + 12864 Discount Full Graphic Smart Controller. All Chinese import.
I have installed the u8glib according to instructions.
Enabled the display in Configuration.h
(#define REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER)
Now when I print, the printer stalls maybe 0.1-0.3 sec every time the display updates - leaving ugly dots in the surface on the prints. (Both on print from PC and from SD-Card).

Any suggestions ?
Best regards
Lars.

I used G30 A command to start auto calibration, but it seems that it's never going to stop...
I'm now running more than 30 iterations, but still not stopping. What could be the reason for that?

Steps I used:

1. M502 to load default value,
2. M500 to save value,
3. G30 A to start calibration,
   4..My step 30 is never ending.. so I don't know what to do here yet.

In the programme, you can see this :

// Set E direction (Depends on E direction + advance)
for(unsigned char i=0; i<4;i++) {

why we don't use "step_loops" instead of "4" ?
Some lines before, you would see similar code that use "step_loops".

Hi,

Great project, I can't wait to get it working on my 2020 Kossel. I've set everything up according to the settings described in the configuration.h file, but when my printer is going through the G30 command, it drags the Z-probe (Spring Loaded allen key) on the bed. Where can I add the z_raise_between_probing setting so that doesn't happen?

Thank you,

Robert

If you forget to make these caps it will at best ignore them and in some cases I've seen other the end stop offsets get wiped out.