Best posts made by devleon

The one thing I miss the most from OctoPrint is the ability to cancel a specific object while printing. There's a plugin for this.

Say I'm printing a lot of parts and one of those fail, I don't need to stop the whole print or waste a lot of plastic spaghetti, but I can just cancel that object and it will stop printing that object.

Most popular slicers (Cura, Slic3r and S3D) support labeling individual objects in g-code, and the readme of the plugin explains how.

I heard there's a gcode viewer in the works for DWC, but even without it, it would be nice to include this functionality in DWC 2. It's basically just a matter of using a couple of regex patterns to detect when a section of gcode for an object starts and stops and then displaying buttons to skip those sections.

I'm a software developer myself, so I might just go down the rabbit hole of the DWC code and give this a try.
Is it already possible to read out the gcode in DWC somehow? And how would I be able to tell the printer what sections to ignore? After all GCode is not streamed like in octoprint, but read from the SD-Card. Guess this would require support in both the firmware and DWC?

It's called Exclude Region (https://plugins.octoprint.org/plugins/excluderegion/).
This actually could be a first, quick and easy way to realize this, no need to parse the gcode and detect processes/objects.
But I would require having a G-Code viewer, while canceling individual objects/processes would just require a list and buttons to cancel specific objects/processes.

But isn't a G-Code Viewer planned for DWC 2 anyways?

See here: https://duet3d.dozuki.com/Wiki/Gcode#Section_G31_Set_or_Report_Current_Probe_status

Just tried the DWC2 again, not bad. However I think the blue (#1976d2) is quite hard to read against the gray background in the dark mode. I think a lighter blue like #0091ea is much more readable. Also, I found two bugs. I built the latest Duet Web Control 2.0.0-RC6+3 from github.

1. If i click on Extra, any clicks on Tools will simply not do anything. I have no possibility to go back to Tools, other than to reload the page.
2. For some reason, in the Tool page, all the Current temperatures just read as n/a. The graph next to it shows all temperatures fine though.

For 2), the console shows this:

app.806a5f0e.js:19 TypeError: Cannot read property 'current' of undefined
    at app.806a5f0e.js:32
    at s.Ve [as _l] (app.806a5f0e.js:19)
    at sp (app.806a5f0e.js:32)
    at s.t._render (app.806a5f0e.js:19)
    at s.i (app.806a5f0e.js:19)
    at ni.get (app.806a5f0e.js:19)
    at ni.run (app.806a5f0e.js:19)
    at Jn (app.806a5f0e.js:19)
    at Array.<anonymous> (app.806a5f0e.js:19)
    at ce (app.806a5f0e.js:19)

Hey everyone!

My Ender 3 conversion is pretty much done, just needs some final touches. It features a magnetic hotswap tool mount and currently has a E3D V6 with a MaPa nozzle and all-metal heatbreak as well as a 500mW laser. It also has a Y-Splitter for Dual Material printing.

Anyways, I got a chance to make my first test print, and while it looks good, there are some weird ripples on the y-axis. For X and Y I'm running identical JK42HM40-1684 0.9 degree steppers.

This is my first print, and there are some wide spaced ripples:

I then tightened my y-axis belt so you can string it like a base guitar string, and the rippels got closer together... How can that be? Maybe a bent motor shaft?

I just finished printing my XYZ cube as well, but I'm honestly baffled, and I really don't know how to interpret these results. I have never seen a texture like this before... I mean, it looks cool, but not perfect the way I want it, and I knew my printer could do better.

Not really sure what to make of this? I have calibrated e-steps as well as flow rate. It's the same filament I have always been using. I'm doing 4mm retraction, maybe that's too high for my all metal hotend?

Also, my hotend temperature is everything but stable, maybe this has to do with it.

I'm running a E3D V6 with a 40W cartridge, already PID tuned (with M303 H1 S240) . The thermistor is a ATC Semitec 104GT-2, and the config for it is like this:

; Hotend
M305 P1 T100000 B4725 C7.06e-8 R4700
M143 H1 S280
M307 H1 A662.5 C243.2 D8.7 S1.00 V24.0 B0

Maybe the wierd texture has to do with the temperature fluctuations?

... And finally, some before and after comparisons. Left is before conversion, right is after.


Atleast the ringing is gone!

Well, after lots of attempts, clogs because of the all-metal hotend, heater faults because the part cooling fan would cool the hotend too much, weird babystep offset issues during tool changes, where after a toolchange the offset would just be ignored and the nozzle would bury itself in the print, I finally got a complete dual color print

@dc42 Thanks!

For my first print, I had my z-height slightly too low, so when the printer started printing, the nozzle was too close to the bed. I used babystepping in DWC to make it higher, and that worked for the first layer until a toolchange happened.
After the toolchange, the nozzle was too low again (I guess the babystepping was reset, even though it stayed the same in DWC), dug itself in the already printed layer and ultimately caused a clog in my heatbreak. My first guess was that it was caused by a "G1 R1" in my purge_bucket.g macro that was called after purging and cleaning from a toolchange, so I removed it.

However, even with it removed, I still had the issue that if there was babystepping before a toolchange, it would not get applied correctly after the toolchange. If I had babystepped during the first layer of the first tool, the nozzle would always be too high or too low after a toolchange (causing some clogs in the all metal hotend). I'm also running grid mesh compensation, so maybe the combination of babystepping, grid bed leveling and a toolchange didn't work well together. Or maybe the baystepping get's reset after a toolchange? It stays the same in DWC. The actual offsets (G10) are the same for both tools, as it's the same nozzle anyways.

I ultimately fixed it by carefully tuning the z-height before the print so I wouldn't need babystepping. This finally produced the cone above.

Im running the latest beta3 btw.

@dc42 Just confirmed that the offset it reset when changing tools. I checked by baby stepping up by 4mm, then running a toolchange. The nozzle goes back down 4mm, but it still says 4mm in DWC. I also have a M451 in my tpre0.g and tpre1.g to make sure the printer is in FFF mode, because I have a M452 in my tpre2.g for my laser. Maybe that's the reason?