Second layer jump
-
The ;Layer 1, Z = 0.300 is not something that I'm doing intentionally, It is what ever is built into Simplify3D version 4.1.2. I can see if I can change that somehow and I'll report back with my findings.
-
@Phaedrux said in Second layer jump:
For the ending script you can put
M0
in the slicer end gcode and then put all of the commands instop.g
. M0 will call stop.g when present.I do like the sounds of that. Thanks.
-
So I have tested a new print with the start up macros rather than using the starting script I previously had.
It appears that the issue with the layers not showing up has been partially resolved. rather than showing layer 8 for the second layer, it now shows layer 2 and it show that layer 2 and 3 take about the same amount of time (But there should actually be 4 layers for the bottom). So it looks like layer 1 and 2 are missing and layer 2 is layer 3 and so on.
Having said all of that it still appears that I have the baby stepping issue. Any baby steps that get applied to the first layer seem to get doubled up or re-applied on the second layer.
Here is a screen capture of the layer time plot
-
Can you share one of your newly sliced gcode files after your changes?
-
@Phaedrux Of course Drag chain mount.gcode This one still has the Babystep reset at Layer 2 and it appears that I still need to do that.
-
Sorry, can you show again what's in start1, 2, 3.g? I know you've moved your commands over, but I'd still like to see exactly how everything is getting executed.
Also, if you disable Z hop, does the problem change?
Do you have anything in tool change files?
-
@baird1fa said in Second layer jump:
G1 H2 Z-5 F600 ; back off of limit for second pass
Probably unrelated, but in your homez you should remove the H2 from the back off move.
-
@Phaedrux
Start1.g;Call this Gcode after the chamber heaters are set G28 Z G28 X Y ; Home all G1 Z10 F1000 ; Bring up Z G1 X-55 Y-48 F12000 ; Offset for z probe M18 E0:1 ; Disable extruder stepper motors as they ca
start2.g
; Call this after the bed is warmed up G30 ; Probe bed single point and set offset of Z G29 ; Bed mesh probe G1 Z10 F400 ; Lower bed while heating G1 X-30 Y165 F12000 ; move head over purge bucket while heating G1 Z-1 F200 ; Lower head down to purge bucket
Start3.g
; Call This after the bed has been probed G92 E0 ; Set extruder to 0 G1 E10 F120 ; Extrude 10mm of filament into purge G92 E0 ; Reset Extruder count to 0 G1 E-0.5 F500 ; Retract 0.5mm of filament G1 Z0.5 F900 ; Raise nozzle to .5mm over bed
I just copy and pasted these out of my original start script in simplify3D.
-
I think it would be a good idea to specify G91 relative moves for the Z moves in your macros, unless the intention is really to move to that absolute location.
Also, if you disable Z hop, does the problem change?
Do you have anything in tool change files?
-
@Phaedrux my intention is to actually move 1mm below the bed surface as there is a purge bucket there which is why I'm in absolute mode.
I have not tried to disable the Z-hop but that would be a good next step.
I do not have anything in my tool change files.
-
@baird1fa said in Second layer jump:
G1 H1 Z585 F1000 ; move Z up until the endstop is triggered
When you home with the z endstop, where is the nozzle in relation to the bed? I see your M208 minima is -10, so when it goes that move it will set the position as -10.
I guess it doesn't really matter since you're doing a G30 in start2 anyway.
Another random thing to try, is that if you have empty tool change files present, just delete them entirely.
-
@Phaedrux The Z actually zeros at the maximum so there is a very large space between the print head and the bed. I will look at deleting those files. I'm out of the office now for the holidays so I'll pick this up again in week or two.
-
@Phaedrux Sorry it has been awhile, I don't think I ever did delete those tool change files, but the second layer jump seems to have been resolved.
-
I'm having this same issue with my printer. The second layer is definitely printing well above were it is suppose to.
-
@warbunnies Please start a new thread if you'd like to trouble shoot it.