Random Mode buffer ran out

Comments

35 comments

  • Avatar
    Kurt Skauen

    I don't know what to say.

    You have not responded to ANY of my questions AT ALL. Ok, maybe some of the unimportant ones. I don't think you have, but I'm not going to waste my time reading over them again to check.

    But none of the important questions have been answered.

    You have simply ignored everything I have written.

    You have constantly attempted to derail all conversation with irrelevant nonsense in an attempt to draw attention away from the questions. Like listing printers that don't support USB control when discussing octoprint on a Pi Zero. And an almost infinite supply of other examples.

    You have not disputed any of the accusations against you about lying. You have simply attacked back and demanded examples. Which has been provided and that you again are ignoring. And then attempted to smokescreen everything away.

    You have never ever backed any of your arguments with any kind of real data. It is all just "because I say so".

    Every time you write something you are confirming most of the accusations against you. You must have the poorest reading comprehension of any person I know. You again and again and again and again and again come back replying with things that are not even remotely relevant to the questions being asked.

    Until you show at least the slightest ability to understand event the most simple things that are being told to you, I'm not going to waste my time talking to you in private. You have displayed such an incredible level of dishonesty and disrespect that it is really hard to comprehend. And for the second time to ask me to take the discussion offline just add to that. You should really be ashamed of yourself, and so should Mosaic as a company for supporting you.

    I just don't get how you can come here now and say that you have responded to my questions. I'm almost attempted to distill out some of the most important again and list them here. But it would of course also just be a huge waste of time as you no doubt would simply ignore them again and come with your regular random ramblings.

    What a joke.

    0
    Comment actions Permalink
  • Avatar
    Donovan Meyers

    Just finished a 14-hour print in multi-spool mode on firmware 4.2.3, and it rolled through two almost-empty spools and onto a third brand-new one with no problems. Woohoo!! This is a big reason I bought the P2P -- to finish up spools (and not just on tiny prints).

    It sure does pong a lot now. I didn't really pay attention with old firmware, but in the beginning of this print, I counted just 14 of the tiny little advances of the outgoing drive before it let the buffer drain until the switch tripped. I watched it do this several times! 14 grunts, pong, 14 grunts, pong. I have to say it was really nice to see the buffer fill back up every time the switch lit up. I do worry about a spool running out in the middle of a pong, though. Seems like there's a risk of having an empty buffer when suddenly a splice is required -- and the Palette has no way of knowing when it will need to splice in this mode. But this is all theoretical -- it worked just fine this print.

    0
    Comment actions Permalink
  • Avatar
    Kurt Skauen

    Yes, most prints that is ran slow enough that about 50% (the normal fill percentage) of the buffer is enough will succeed.

    Since it spend more time not ponging than it do in ponging there is a <50% chance of having a failure.

    It still comes down to luck though. And no serious company would release a product where whether it's intended operation will succeed or if it will cause damage to the customers property (the model being printed, and potentially the printer) comes down to luck with as poor odds as this device have.

    With the new slow-down-when-splicing feature it should be possible to eliminate the element of luck though. Make it run at less than 24.8mm/s during splices, and the 32mm that it push into the buffer to get the filament from the cutter to the splicer will be enough to sustain the printer.

    In theory at least. Unfortunately I don't think it will work in practice when the margins are this small.

    The firmware in the printer pre-process and buffer a few gcode commands and thus will not react instantly on the speed change command. Especially when it is doing 100% infill of large areas there is very few gcode commands per mm^3 of plastic. And then this is likely to become an issue and we are right back to depending on luck.

    And then you have the one-way-valve design in the filament inputs that makes it unsafe to let the palette run out at any speed. That is a catch-all for making multi-spool unusable in any safe manner.

    -2
    Comment actions Permalink
  • Avatar
    Donovan Meyers

    Jonny,

    I don't think we're quite out of the woods.

    I upgraded the firmware a few days ago, and started using Multi-Spool mode to print a few large single-color models. I just left the Palette running and it performed like a champ through 2 or 3 prints, from 2 partial spools and a full one.

    Last night I reloaded so I could print another big model. I pressed stop, cleared output and pulled from Bowden, and went back in to multi-spool mode. I loaded the ~2m scrap that was leftover in the tubes, a partial roll, and a full roll. Note that I did not power cycle.

    This morning I woke up to find that very early in the print it failed. The buffer was drained, the buffer switch light was on, and the printer was air-printing. The filament was actually ground down and split at the extruder gear, with little black marks on it (white filament).

    So, I turned it off, cleared everything out, and let it sit for a minute. Then I turned it on, selected multi-spool, and loaded the partial and full rolls (inputs 2 and 3).

    I noticed that the buffer was running very lean. It even did what I think was a pong, but still didn't fill the buffer back up very much.

    I canceled the print, cleared the Palette, and started everything back up, and it's doing the same thing. I'm letting it print but I'm worried, especially for the time when it needs to splice to the next roll.

    It's as if it doesn't know how big the buffer is. I have the loading process on video, and I see that at the very beginning after loading, when I've clipped in and I start extruding down the bowden tube, the buffer drains quite a bit before it starts advancing filament. And it never fills it back up more. I'm quite certain there is less in the buffer than during my earlier successful prints right after firmware upgrade.

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Hey Donovan, I'm sorry to hear that. Let me chat with the team about this and I'll respond shortly. What was your print speed when these issues occurred? Also, would you happen to have a video of what is happening in the buffer when you first start the print?

    0
    Comment actions Permalink

Please sign in to leave a comment.