Layer count
-
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
-
Also noticed that if you do a spiral vase print then you get weird layer reporting
You will do. If you think about it, there is either only one layer or an almost infinite number of layers, depending on how you look at it.
-
@dc42 – Layer counts are working properly after making your code change, Thanks.
@burtoogle --
- -- I'm using G90 to set the extruder to absolute, is that OK?
- -- Thanks for the tip on combing, I was experiencing that problem
- -- And also the tip on Expanding the skin
I'm re-printing now and will see how it turns out,
Thanks
-
- – I'm using G90 to set the extruder to absolute, is that OK?
I believe that G90 only affects the x/y/z axis, it doesn't affect the extruder. Your Duet must be in absolute extrusion mode already otherwise you wouldn't be able to print at all. It's still worth adding the M82 into your Cura start code to ensure that it will work even if the Duet isn't already in absolute mode. Cheers, Mark.
-
Mark,
I just checked and I have it in Config.g
; General preferences
T0 ; Select first tool
M111 S0 ; Debugging off
G21 ; Work in millimeters
G90 ; Send absolute coordinates…
M82 ; Absolute Extruder moves (Cura)
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
Thanks
Doug -
I spoke to soon,
Layer Statistics are not working and Layer Count is not updating, its stuck on 2.
Object Height, Total Layer Count and Total Filament Usage are now correct.Link to file that it is printing https://www.dropbox.com/s/wv4ybg55gresa4l/DR2_Doug_duet_wifi_LID_5_May-2017_V1%20v3_With_SuggestedSettings_PetG.gcode?dl=0
-
Which browser are you using, and which versions of RRF and DWC?
-
Windows 10
Firefox Version - 53.0 32 bitFirmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.18.1 (2017-04-09)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.15bI just tried Internet Explorer and it shows the same thing
-
It started working at about layer 10 and is now updating for the moment, I have no idea why. I didn't do any thing, was just watching it and it started working
