Page MenuHomeAleph Objects Inc

Layer view showing improper moves and layers
Closed, DuplicatePublic

Description

When slicing a single layer print, CuraLE is reporting that there are 53 layers in the gcode and displays weird travel lines




Sliced on local build of 3.6.3 with freshly cleared cache on hillstar

Event Timeline

logan created this task.Wed, Jan 23, 10:52 AM
karrad changed the edit policy from "All Users" to "Cura LulzBot Edition (Project)".Wed, Jan 23, 11:00 AM
karrad added a subscriber: karrad.

@logan What material and profile were you using? I will try to duplicate here

@karrad polylite PLA High Speed

@logan something is off on your local build. Reslicing the same model I get this:

And when loading in your posted gcode file, I do not see any of those moves:

Did you try printing this and seeing if it moves to the front corner? Looking through the gcode, I am not seeing any X0 Y0 moves

It prints normal.
If something is off with my local build it isn't anything I did.
I built on 1/17 at 7:21am, cleared cache, and have been careful not to run ANY other versions of Cura. It was rebuilt on Thursday because after opening/closing legacy Cura, 3.6.3 that was running would no longer save gcodes reporting "Failed to write because there are no available file types to write with" so I closed 3.6.3 and attempted to restart by running the same terminal command in the same directory which failed. saying there was no cura-lulzbot, despite being able to see it in the folder. It just wouldn't run. So I deleted the "dist" folder, cleared cache, and followed directions for updating local build. Which is the build running now.

@logan Not sure what happened either, let us know if the fresh build fixed it up. But on the bright side, you get to check out the new dark theme.

Can I update without clearing cache? sucks losing settings every time

@logan What settings are you using different each time, are these profile changes we need to include stock?

Clearing cache removes all the old profiles, machine settings, and confusion if multiples have been opened. We have not found a more efficient way to ensure these conflicts do not occur.

If you have a set of settings you like, you can export the profile and re-import it after the new build.

@karrad Quiver I've been sticking with defaults for polylite and just dealing with it while we wait for working profiles. Its the other machines I'm using that just gets old re-configuring them every time.
TAZ 6 Dual v3 start gcode I add wait for idle nozzle to cool to standby temp before beginning first layer so that strings from idle nozzle dont get dragged all over and ruin first layer and reduce all the print speeds because the defaults produce resonance from the tool head being so heavy.
Mini 2 I add the X level to the start gcode
All ABS profiles still require turning the fan off, not sure why it is still on by default.
Auto slicing off
allow connection to wrong printers
specify port for quiver
skirt count 3 distance 5

@logan Can you post the dual v3 start code? We can look at incorporating it.

Mini 2 I add the X level to the start gcode

This we can't put in by default as discussed previously. Support has directions for customers that do want to add it.

All ABS profiles still require turning the fan off, not sure why it is still on by default.

The fan is required for smaller models to give better detail. Catch 22 where we cannot have a single profile for all model sizes for this material. Any changes to this will require extensive testing, which we do not have the bandwidth for atm.

Auto slicing off

This one is legacy, and has how it has been traditionally done. We have directions for customers who like to turn this off, and due to re-education required for customers, QSG, manual etc will not be able to update it

allow connection to wrong printers
specify port for quiver

Will be getting this fixed with T1250

skirt count 3 distance 5

Is this one for checking skirt? We keep the count low and the distance close to avoid lost build volume when customers are first slicing.

logan added a comment.Wed, Jan 23, 1:07 PM

The dual v3 start gcode, there might be an easier way to do it, because which nozzle to specify depends on which one it will print with first.

; This profile is designed specifically for LulzBot TAZ6 3D Printer with the Yellowfin Dual
M73 P0                       ; clear GLCD progress bar
M75			                 ; start GLCD timer
G26                          ; clear potential 'probe fail' condition
G21                          ; set units to Millimetres
M107                         ; disable fans
M420 S0                      ; disable leveling matrix
G90                          ; absolute positioning
M104 S{material_soften_temperature_0} T0               ; soften filament
M104 S{material_soften_temperature_1} T1               ; soften filament
M140 S{material_bed_temperature}; get bed heating up
G28 X Y                      ; home X and Y
G1 X-17 F3000                ; clear X endstop
G1 Y258 F3000                ; move over the Z_MIN switch
G1 X-19 F3000                ; move left as far as possible
M117 Heating...              ; LCD status message
M109 R{material_soften_temperature_0} T0               ; wait for temp
M109 R{material_soften_temperature_1} T1               ; wait for temp
T0                           ; return to first extruder
G28 Z                        ; home Z
T0                           ; select this extruder first
M82                          ; set extruder to absolute mode
G92 E0                       ; set extruder to zero
G1  E-15 F100                ; suck up XXmm of filament
T1                           ; switch extruders
M82                          ; set extruder to absolute mode
G92 E0                       ; set extruder to zero
G1  E-15 F100                ; suck up XXmm of filament
M104 S{material_wipe_temperature_0} T0                 ; set to wipe temp
M104 S{material_wipe_temperature_1} T1                 ; set to wipe temp
M106                         ; Turn on fans to speed cooling
G1 X-17 Y100 F3000           ; move above wiper pad
M104
M117 Cooling...              ; LCD status message
M109 R{material_wipe_temperature_0} T0                 ; wait for T0 to reach temp
M109 R{material_wipe_temperature_1} T1                 ; wait for T1 to reach temp
M107                         ; Turn off fan
T0                           ; switch extruders
G1 Z1                        ; push nozzle into wiper
G1 X -18 Y95 F1000                   ; slow wipe
G1 X -18 Y90 F1000                   ; slow wipe
G1 X -18 Y85 F1000                   ; slow wipe
G1 X -17 Y90 F1000                   ; slow wipe
G1 X -18 Y80 F1000                   ; slow wipe
G1 X -17 Y95 F1000                   ; slow wipe
G1 X -18 Y75 F2000                   ; fast wipe
G1 X -17 Y65 F2000                   ; fast wipe
G1 X -18 Y70 F2000                   ; fast wipe
G1 X -17 Y60 F2000                   ; fast wipe
G1 X -18 Y55 F2000                   ; fast wipe
G1 X -17 Y50 F2000                   ; fast wipe
G1 X -18 Y40 F2000                   ; fast wipe
G1 X -17 Y45 F2000                   ; fast wipe
G1 X -18 Y35 F2000                   ; fast wipe
G1 X -17 Y40 F2000                   ; fast wipe
G1 X -18 Y70 F2000                   ; fast wipe
G1 X -17 Y30 Z2 F2000                ; fast wipe
G1 X -18 Y35 F2000                   ; fast wipe
G1 X -17 Y25 F2000                   ; fast wipe
G1 X -18 Y30 F2000                   ; fast wipe
G1 X -17 Y25 Z1.5 F1000              ; slow wipe
G1 X -18 Y23 F1000                   ; slow wipe
G1 X -17 Z15                         ; raise extruder
M109 R{material_probe_temperature_0}                   ; heat to probe temp
M204 S100                    ; set accel for probing
G29                          ; probe sequence (for auto-leveling)
M420 S1                      ; enable leveling matrix
M425 Z			     ; use measured Z backlash for compensation
M425 Z F0		     ; turn off measured Z backlash compensation. (if activated in the quality settings, this command will automatically be ignored)
M204 S500                    ; set accel back to normal
M104 S{material_print_temperature_0} T0 ; set extruder temp
M104 S{material_print_temperature_1} T1; set extruder temp
G1 X100 Y-25 Z0.5 F3000      ; move to open space
M400                         ; clear buffer
M117 Heating...              ; LCD status message
M109 R{material_print_temperature_0} T0 ; set extruder temp and wait
M109 R{material_print_temperature_1} T1; set extruder temp and wait
M117 Purging...              ; LCD status message
T0                           ; select this extruder first
G1  E0 F100                  ; undo retraction
G92 E-15                     ; set extruder negative amount to purge
G1  E0 F100                  ; purge XXmm of filament
T1                           ; switch to second extruder
G92 E-15                     ; set extruder negative amount to purge
G1  E0 F100                  ; undo retraction
G92 E-15                     ; set extruder negative amount to purge
G1  E0 F100                  ; purge XXmm of filament
G1 Z0.5                      ; clear bed (barely)
G1 X100 Y0 F5000             ; move above bed to shear off filament
T0                           ; switch to first extruder
M190 S{material_bed_temperature_layer_0}; get bed temping up during first layer
G1 Z2 E0 F75
M109 R170 T1       ; wait for 2nd nozzle to cool to standby temp before starting first layer with nozzle 1
M400                         ; clear buffer
M117 TAZ Printing...         ; LCD status message

Skirt is probably a personal preference, little extra purging.
I know most of these are personal preference or use case scenarios, I just wanted to clarify what I was setting up after each update/cache clear.

logan added a comment.Wed, Jan 23, 4:16 PM

@karrad
Followed instructions for updating local build including clearing cache, same result. Doesn't happen when slicing for TAZ 6 Aero

@logan Did you check the gcode for the moves or does this one print normally as well?

@karrad Nothing weird in the gcode that I could see, printer behavior normal.

karrad triaged this task as Low priority.Thu, Jan 24, 12:13 PM

@logan Okay, going to tag this one as low priority until it can be duplicated or reported elsewhere.

karrad renamed this task from One layer print reports as 53 layers to Layer view showing improper moves and layers.Thu, Jan 24, 12:13 PM
jebba added a subscriber: jebba.Tue, Feb 5, 11:59 AM

I get a different view from both of you. You have checkboxes for each extruder and mine says "Compatibilty mode" at the top of mine. Not sure what is up. This is with official 3.6.3 build. See attached screenshot.

jebba added a comment.Tue, Feb 5, 12:12 PM

I do see an option that is off by default: "Force layer view compatibility mode (restart required)". On my workstation I can enable the new viewer by running this:

MESA_GL_VERSION_OVERRIDE=4.2 MESA_GLSL_VERSION_OVERRIDE=420 cura-lulzbot

jebba added a comment.Tue, Feb 5, 12:14 PM

Using the new layer viewer, I don't see the bug when importing the STL.

logan added a comment.Tue, Feb 5, 12:14 PM

I cannot seem recreate this on fresh build of 3.6.4 for quiver or any other machine/tool head configurations I tried.

jebba added a comment.Tue, Feb 5, 12:15 PM

Looks ok when I import the gcode, see screenshot.

logan added a comment.EditedTue, Feb 5, 12:19 PM


In this screenshot you can see a few odd travel lines but nothing like above, this is from Q_wiggletest.gcode from above
Quiver/Dual
CuraLE 3.6.4

jebba added a comment.Tue, Feb 5, 12:26 PM

@logan When I import a gcode file, the object is blue (cyan) and is just one color. Your screenshot has different colors for travel and infill, for example. It usually doesn't show this when importing a gcode file. @karrad what do you get?

jebba added a comment.Tue, Feb 5, 12:27 PM

Logan has "line type" selected under "Color Scheme" not "Material Color".

jebba added a comment.Tue, Feb 5, 12:29 PM

When I do "Line Type" for Color Scheme, I don't get the lines, fwiw. See screenshot.

jebba added a comment.Tue, Feb 5, 12:31 PM

Ah, if I do "Show Travels" I can see it.

jebba added a comment.Tue, Feb 5, 12:32 PM

The travel line on the far right looks like the wiper pad. The one in the center is when the print is done. I'm not sure what the two shorter ones to the left of the part are.

logan added a comment.Tue, Feb 5, 12:34 PM

I think those are in the gcode and not displayed by error vs the original report had weird lines displayed without any corresponding moves present in the gcode

jebba added a comment.Tue, Feb 5, 12:35 PM

I don't see the lines when using wiggletest.stl, probably because we don't display the gcode start lines. See attached pic.

I do see the lines when I import the gcode I generated from wiggletest.stl.

jebba added a comment.Tue, Feb 5, 12:37 PM

@karrad The reason you didn't see moves is you didn't have "Show Travels" checked.

When viewing the STL, the lines aren't there. When viewing the gcode, in "Line Type" and "Show Travels" checked, it shows the lines. They may be real travels, fwiw.

logan added a comment.Tue, Feb 5, 12:41 PM

@jebba I didn't have "Show Travels" checked in the original report either. Which made it even more odd.

Everything is working normally on 3.6.4 and others couldn't recreate on 3.6.3 elsewhere so it seems reasonable to me to leave this ticket closed until the issue crops up again.

jebba added a comment.Tue, Feb 5, 12:42 PM

You can also see these travels in the "Compatibilty Mode", so it isn't just in the new viewer. This is a screenshot of Q_wiggletest.gcode in compatibility mode with "Show Travels" checked.

jebba added a comment.Tue, Feb 5, 12:43 PM

I don't think this is a bug, I think it is rendering the correct travels and those travel lines are in the gcode.

logan added a comment.Tue, Feb 5, 12:45 PM

Agreed, nothing like the original report.

jebba added a comment.Tue, Feb 5, 12:54 PM

Ok, the first line on the left of the part is the wipe sequence for the left extruder. I'm not sure why it doesn't put in in the back left (probably because it hasn't homed Z yet ?), but that line is actual gcode. The small line to left of the part is right before it starts the print. So that is a legit gcode move as well.

I think all the rendering lines it generates are actual moves.

As for the first screencap you have where it says 53 layers, are you still able to reproduce it? I can't reproduce it. I'm assuming that 53 layers, is 1 layer of print, then when the print ends, the extruder moves up in Z to the cooldown position.

logan added a comment.Tue, Feb 5, 12:59 PM

No sir, not able to reproduce on 3.6.4.
It would only display that way from slicing the stl, if I were to save, clear build plate and import the gcode I saved, the issue wouldn't appear. So when I would load in the saved gcode it would report 1 layer again.

jebba added a comment.Tue, Feb 5, 1:03 PM

"It would only display that way from slicing the stl, if I were to save, clear build plate and import the gcode I saved, the issue wouldn't appear. So when I would load in the saved gcode it would report 1 layer again."

So that's how you would get it to show 1 layer? What would be the process you used to show 53 layers?

logan added a comment.Tue, Feb 5, 1:05 PM

To get the initial error just loading the wiggletest.stl from above and slicing it with any material/profile on quiver

jebba added a comment.Tue, Feb 5, 1:13 PM

Loading wiggletest.stl on 3.6.3 using Quiver with PLA 0.25mm default settings gives me 1 layer.