Layer count
-
@(In)Sanity:
FYI, seeing layer count issues with S3D as well. Doing a print that has 251 layers and the DWC is showing 750 layers. Oddly I've seen 750 often, I think it's my max layer count for my setup. Yep it is, says my object is 150mm high. It is showing the two layer heights which is also incorrect as the first layer is set to 100% of 0.20mm. Ok, well not the end of the world I guess, it works on some prints.
Jeff
So was your object actually only 50mm high instead of 150mm, or was the layer height shown by DWC only 1/3 of the real layer height?
-
The object is 0.2mm X 251 layers so yes 50.2 mm high. The printer is showing 150mm and 750 layers. This is a direct slice right from S3D 3.1.1 without any types of edits. Sliced, saved, upload, print. It seams to sometimes work and sometimes not. I see 750 layers often.
Here is the G-Code for your reference: The File
Jeff
-
David,
Sorry did not respond to your request of Jan 13th.
Somehow I am not getting advised when threads I have contributed too are updated.
Where do I reset this?
As you have now released 1.17c with the MH layer fix I assume you no longer need any more gcode examples. -
Merlin, please let us know whether 1.17c fixes the problem. I was not able to test the fix.
-
Any ideas on the S3D layer count issue? I did a print last night with the same 750 layers showing when it shouldn't have been.
Thanks,
Jeff
-
WebControl seems to be displaying inaccurate info while printing.
- The progress Bar is stuck saying "Layer 2 of 440" and not incrementing ; Cura say theres only 100 layers
- Filament usage is also way off; Cura says 11.975m WebControl shows 49.2252
Size:
12.8 MiB
Object Height:
110 mm
Layer Height:
0.25 mm / 0.25 mm
Filament Usage:
49225.2 mm
Generated by:
Cura_SteamEngine 2.5.0–--------------------------------------------------------------
Here's the first part of the code
;FLAVOR:RepRap
;TIME:4651
;Filament used: 11.9751m
;Layer height: 0.2
;Generated with Cura_SteamEngine 2.5.0
M190 S110
M104 S245
M109 S245
;Start of START CodeM561 ; Clear any bed transform
G28 ;Home All Axis
G29 ;Bed Mesh
G90 ; absolute positioning
G92 E0 ; zero extruders
M106 S0 ;Set Cooling Fan to 0
G1 X235 Y3 Z1 F3000 E0.3 ; Position to Wipe
G1 X15 Y3 Z0.3 F3000 E25.00 ; Wipe
G1 E23 F2000
G92 E0 ; zero extruders
;LAYER_COUNT:100
;LAYER:0
M107
G0 F9000 X22 Y15.501 Z0.18
;TYPE:SKIRT -
@Shotfire, can you make that file available to me via Dropbox or similar?
-
Hi shotfire, is your print spiralized? Webcontrol doesn't show the correct info when printing a Cura spiralized model.
-
@burtoogle, No, I'm just printing a a new box for the DuetWif right now. But it happens on every print I do no matter what size or shape
-
That's weird, I'm using Cura 2.5 and the layer stats + time prediction all work as they should.
-
I would also like to take a look at one of your gcode files that are misbehaving. As DC says, can you put it on Dropbox or similar.
-
I have put it on my dropbox but I don't use dropbox very much, I think I need your email address to give you access
-
Using the dropbox website you can make the file public and then copy a link which can be pasted into the forum here.
-
My DWC has been today stuck with 1399 layers. Third print today. Even with different browser sessions. DWC seem to have some problems updating layer counts between different prints if the same session/browser window is used, but now this one happens even with different computers. And I have not had a print with 1399 layers.
-
My DWC has been today stuck with 1399 layers. Third print today. Even with different browser sessions. DWC seem to have some problems updating layer counts between different prints if the same session/browser window is used, but now this one happens even with different computers. And I have not had a print with 1399 layers.
this was explained in David's earlier comment. I had newly created end code section using G1.
-
-
I'll try to make time to look at it tomorrow. Today was taken up with finishing the 1.19alpha firmware release.
-
I have looked at your gcode and it seems to me that it doesn't match the snippet you show in your message of 1st May. The filament used in the file is what DWC reports (49.2252m). Other than that, it doesn't have an M82 to set the extruder into absolute mode (you have that elsewhere, right?). Looking at the Duet code it seems to me that the only way the layer count could not get incremented would be if you had a very small nozzle diameter specified because then the following would never be true:
liveCoordinates[Z_AXIS] < platform->GetNozzleDiameter() * 1.5
So with your layer height of 0.25mm, if the nozzle diameter was smaller than 0.1666 (unlikely), layer changes won't get detected.
One other comment which isn't related to the layer report problem but is related to Cura 2.5 is that Cura now has a new option to expand areas of skin into infill which is useful when you have small areas of infill underneath features such as pillars (which you have in your print). If you are not yet using the expand skin into infill option, I recommend that you do. If your gcode example has been generated with that option enabled then something is wrong and I need to fix it!!
Finally, from the file name I guess you're using PETG. I have found that if I keep combing enabled (Cura feature to avoid retracts and speed up movement) when printing PETG that the nozzle tends to pick up filament and after a while it gets deposited as a hard lump onto the print. So, for PETG, I turn off combing completely.
-
The only issue I can see with that gcode file is the common one, that you have a G1 Z command in your end gcode that is confusing the object height detection. It's this line:
G1 Z110 F1200 ;Move Z Down
The workaround is to start the comment on that line with ;E or ; E for example:
G1 Z110 F1200 ;E Move Z Down
-
Also noticed that if you do a spiral vase print then you get weird layer reporting
