I am about with this disaster of a company. Another print failed after 10 hours because the %#*@ thing froze. My success rate is under 205 (I know, some folks here would love that rate!).They are off trying to make their element and array customers happy, while we are abandoned; they even admitted this in another thread. It has now been over 5 months without a firmware update, when there are definite known issues. As an aside, can you imagine giving these guys 10s of thousands of dollars for a commercial product? I am starting to think that Mosaic is what happens when some engineers with a cool idea try and build a business. In a way it is a shame, because the hardware is not that bad, but the slicer and firmware and company are a real mess. I have been working in tech for more than 30 years, and from the outside they look like a company that needs a good middle manager flushing. In a private message I told them they are missing their chance. They have a community here that wants the thing to work, they...
Thanks for the response, but let me paraphrase it for you so you know what most people on this forum will hear: 'Sorry we have been ignoring the Palette while we work on brining other products to market, even though the Canvas and P3Pro is still not market ready, and still do not offer all the functionality claimed on the product page' :-(
This thread is almost a year old, has there been any progress in figuring out the problem? I just froze 40 hours into a 50 hour print :-( Everything was going great, the pings were spot on, the color changes were as good as they get, then I heard my extruder clicking and the P3 was frozen. I sent my log files to support@mosaicmfg.com
Just a thought, but what if it is just not possible with the physical design of the Palette3? A lot of people are still failing with basic PLA, and firmware fix will make flexibles work? We keep hearing that they are working on a firmware fix, I would like to understand what more can be done beyond the current control of temperature, compression, and cooling? Can Mosaic at least give us a hint what the biggest hurdle is and how they are trying to get around it? Is it the splices? Is it the path through the palette? Can they give us anything? The ability to do materials other than PLA has been part of the Palette 3 advertising from day 1, and the ability to handle flexibles is still on their marketing page. Think of how long they have had to work this out. Now think of their track record and lack of transparency and ask yourself what they would do if they had determined it is just not possible. Would they admit it? They just raised the price $100, it would be hard to admit that such a key feature will never...
I have had the same thing happen several times. I have an 800mm tube and 50mm offset. It happens when I have a lot of short splices to start things off. As near as I can tell it happens if I have a splice between 1600mm and 1700mm, and that splice is made a short time before the palette is trying to push the filament out of the tube. It looks like there is a zone just after the core where the splice can’t sit, so it pushes the splice out of that zone and as a result it pushes too much filament out of the tube. I have to go add a skirt etc., to change the splice locations a little bit.
I don’t think that Palette cares about nozzle size. I can slice and print with a .25 mm nozzle (I don’t because it generally leads to more splices). You do have to set the nozzle size for the printer in Canvas and use appropriate line widths and heights. Palette generates filament for consumption, and that consumption is defined by the g-code, which in turn is generated by the slicer which takes things like nozzle size, line width and height into account. I don’t think there is anything special about a .4mm nozzle when it comes to the Palette, as long as the slicer knows the size.
But what if I am in accesory mode and want to send the mafx file to the palette? Right now I have to download to usb and insert into palette, why can't I just transfer the mafx to the palette from Canvas? If you take the time to read the original post I am pretty sure that is the question.
If the Palette uses a raspberry pi (or something similar), then how about running klipper and fluidd right on the Palette? Too bad things are not a little more open.