20 minutes ago, kmanstudios said:Having had to abort a print so that I can clean out the feeder, I can say that the prints are now going into the recent history. Dunno why it missed that first print, but it is starting to work now as expected.
Curious; why are you having to clean the feeder?
For your information; my S5 stopped a print twice stating that it was out of material when the PVA filament became bound on the spool and could no longer be pushed through the Bowden tube so preemptively I opened the feeder after the print expecting all sorts of dust and chips but it was clean.
By the way; have you loaded the new firmware?
Edited by Shadowman
Spelling
Recommended Posts
Top Posters In This Topic
89
40
38
36
Popular Days
Apr 23
76
Apr 19
32
Nov 2
31
Apr 26
30
Top Posters In This Topic
kmanstudios 89 posts
SandervG 40 posts
Shadowman 38 posts
uncle_bob 36 posts
Popular Days
Apr 23 2018
76 posts
Apr 19 2018
32 posts
Nov 2 2018
31 posts
Apr 26 2018
30 posts
Popular Posts
Daid
Problem was that dilithium was very difficult with legislation, being an accidental space-time warp risk. So we removed that feature last second.
foehnsturm
As for the flow sensor. We (the Mark2 crowd ) almost finished development for an external flow sensor for the UM2+ including firmware integration. Mechanically it fits to the UM3, but connecting to e
Daid
It's bigger. 330x245x315mm to be exact. And that volume can be used by BOTH nozzles. No more less volume for dual extrusion prints. It has a flow sensor, that works for jam detection as we
Posted Images
kmanstudios 1,100
But it is still "aborting" a print when it detects difference in nozzle heights. This means going back into the history, reloading, repositioning the print order and restarting the process. This is a pain to deal with, especially since this is not behaviour on the UM3 side of things.
Link to post
Share on other sites