Layer height runs

Steffen

Why does it do it

wilriker

@steffen We need the GCode file that causes this behavior to say for sure.
But first shot in the dark that comes to my mind is: are you using variable layer height? Also which slicer are you using (but that would be answered by the GCode most probably)?

Steffen

layer 0,200
Simplify3D-4.1.2
It has just come by itself
A print of about 5 min
It's on every print it does

wilriker

@steffen I know that S3D creates some weird GCodes that makes it sometimes hard for RRF to figure out which layer it actually is right now.
Again, uploading the GCode file (or any GCode file where this happens) would be helpful.

Steffen

0_1554986915742_Afstand stykke 7mm 1Stk.gcode

wilriker

@steffen At least there is nothing obviously strange with that GCode at first sight. You have a Z-hop of 0.4mm and it starts at 0.172mm for the first layer and increments in 0.2mm steps from there.

Also relevant: Firmware and DWC versions.

Maybe @dc42 has any idea on this one?

EDIT: I checked the file again. The following command confuses the FileInfoParser:

G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)

can you maybe move your start codes into a macro file and just call M98 Pstart_macro.g?

I commented out this line and now the estimation works as expected.

Phaedrux

G1 Z5 F1800
G90
G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)
G1 X0 Y5 Z0.2 F3000 ; get ready to prime

Any and all of those Z moves will confuse it.

wilriker

@phaedrux said in Layer height runs:

G1 Z5 F1800
G90
G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)
G1 X0 Y5 Z0.2 F3000 ; get ready to prime

Any and all of those Z moves will confuse it.

Actually, the first one will be ignored because it is in relative movement mode. But you are right about the last one (which I did miss because it coincidentally is close enough to the real first layer's Z height so that there is no real confusion).

Steffen

Here's my start script, something that's not necessary

G28 ; home all axes
G91
G1 Z5 F1800
G90
G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)
G1 X0 Y5 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X250 E20 F600 ; prime nozzle

OBELIKS

What do you have in homeall.g ?
Because all of this

G91
G1 Z5 F1800
G90
G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)

should be in there. It gets executed with G28

Steffen

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Tue Jun 06 2017 22:17:43 GMT+0200 (Rom, sommertid)

; Relative positioning
G91

; Lift Z
G1 Z5 F4000 S2

; Course home X and Y
G1 X-305 Y-305 F1800 S1

; Move away from the endstops
G1 X5 Y5 F6000 S2

; Fine home X and Y
G1 X-305 Y-305 F360 S1

; Absolute positioning
G90

G1 Z-275 F800 S1

G91
G1 Z5 F1800 S2
G90

;mowe slowly to z axis endstop once more (secone pass)
G1 Z-275 F360 S1

; Go to first bed probe point and home Z
;G1 X15 Y15 F4000
;G30

; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100

Steffen

One of my friends sent this file and when I print it is okay
I can't see what's wrong

0_1555150796397_infinityheart.gcode

Steffen

By the way, it's a machine similar

Phaedrux

We've explained why it's doing it.

You have homing moves in your start gcode in the slicer that shouldn't be there.

Let's compare the file your friend has to yours.

His

G90
M83
M106 S0
M140 S80
M190 S80
M104 S240 T0
M109 S240 T0
G28 ; home all axes
G1 X0 Y5 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X250 E20 F600 ; prime nozzle

Yours

G90
M82
M106 S255
G4 P500
M106 S128
M140 S80
M190 S80
M104 S247 T0
M109 S247 T0
G28 ; home all axes
G91
G1 Z5 F1800
G90
G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)
G1 X0 Y5 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X250 E20 F600 ; prime nozzle

Do you see the difference?

You need to remove this from your start gcode in the slicer.

G91
G1 Z5 F1800
G90
G1 Z-275 F40 S1; Move slowly to Z axis endstop once more (second pass)

Steffen

Yes it makes sense Thank you