Duet Wifi Print Status - Collected Data & Estimations Issue
-
I've not compared the additional information output between the two slicers, but can fully understand why some fields might not be able to be populated. (And the "spiralized" issues makes sense based on that, although I'd expect the layer time estimate to still be able to be implemented)
The issue where none of the Cura stats are updated until you disconnect / reconnect however is something that should be able to be resolved. Do we need to add a comment at the bottom of the header that Cura generates to signify the start of a print ?
-
The issue where none of the Cura stats are updated until you disconnect / reconnect however is something that should be able to be resolved. Do we need to add a comment at the bottom of the header that Cura generates to signify the start of a print ?
I get updated stats without having to disconnect/reconnect. What version of Cura are you using?
-
The issue where none of the Cura stats are updated until you disconnect / reconnect however is something that should be able to be resolved. Do we need to add a comment at the bottom of the header that Cura generates to signify the start of a print ?
I agree. It's possibly a bug in RRF or DWC triggered by the particular workflow you are using, nothing to do with Cura. Are you starting the print from DWC or by some other means? If from DWC, are you using Upload & Print, or uploading and printing separately?
-
I'm starting from DWC, uploading separately before printing. This same workflow works correctly when using a G-Code file produced by Slic3r so I'll compare the two when I get home.
When using Cura, disconnecting from / reconnecting to DWC during the warm-up phase does not resolve the issue, but reconnecting once the print has actually started does resolve the issue - Which is why I'm assuming that it is related to something that happens within or just after the header G-Code.
-
Looking at it Cura actually gives a bit more information between each layer, Slic3r gives a load more details in the header but there's little to separate the header from the main G-Code:
https://objects-us-west-1.dream.io/yngndrw/3D%20Printer/PI_groot_calibratie%20-%20Cura.gcode
https://objects-us-west-1.dream.io/yngndrw/3D%20Printer/PI_groot_calibratie%20-%20Slic3r.gcode -
OK, well you're using cura 2.3.1 and that doesn't include in the gcode the comments that RRF requires to do estimates. They should look like these examples and be positioned very near the top of the file.
;Filament used: 5.57459m
;Layer height: 0.2Cura 2.4 probably does include those comments, I can't remember when the change was made, quite a while ago.
Cura 2.5 gcode will definitely have them.
-
Thanks, I didn't realise there was a new version of Cura out. 2.4 does indeed output those lines:
[c];Filament used: 0.586407m
;Layer height: 0.2[/c]I'll give it a try with DWC tomorrow.
PS: Why does this forum unsubscribe me every time I reply ?
-
I have no idea why you are getting unsubscribed on each reply. It doesn't happen to me as far as I can tell, although I am subscribed to all the forums.
Does anyone else notice this?
-
i noticed this behavior too. sometimes i get stats and sometime they are just partial. i am using cura but since my pc died, i am temporarily using an old pc so am running an older 32 bit version. I downloaded some stls from thingy verse and some of them report great but others are partial or not at all so am guessing it has something to do with the files as well. I am a newbie so take it with a grain of salt please
-
I've just tried with Cura 2.4 and it all worked correctly.
I wouldn't think the STL file would cause the issue unless DWC was unable to pull out the layer information - Do you have some examples of the files you were using ?
