@hana Pallet 3 is already a networked device. The pallet can even be sent some commands over the web already. Give us a web API for the Pallet 3, and the open-source community can make plugins for Octoprint/Fluidd/Mainsail compatible with the P3 instead of trying to run everything from the P3. That should take less work than trying to re-implement existing features. Adding a web API would also open doors for people who run anything other than Marlin. The market for multi-material printing is full of people who enjoy tailoring their equipment to their specific needs, and are willing to invest the time and energy to optimize how it operates. Mosaic has made a pretty neat piece of hardware, give us the tools to LET US USE IT.
Some initial questions in the klipper discord suggest this would not be difficult to implement. Klipper already supports several web interfaces that could communicate. Let us know what you're expecting for a ping, and we'll add the feature. I mean it could even be something as simple as a literal network ping sent by the klipper host. guy@Spicy:~$ ping [hostename].local -c 1 Klipper wouldn't even need any modifications, the kiauh extension already allows for shell commands, which can be executed from a macro that is called from the gcode. P2PP would just add a SEND_PING macro at regular intervals through the print, instead of trying to modify pauses into the purge tower.
Huzza! First large print with Super Slicer, P2PP, and P3P. Was running into issues with printing too fast, and running out of buffer! Took me longer than I care to admit to track down. KVP ABS, 8,3,-2. 0.1mm layer height, 20h print Room for improvement? Sure! Threshold for success in my book? Yes. Purge tower took substantially longer to print than the part itself, digging into purge speed settings. Seems to be buggy in Super Slicer
Test results!! Everyone likes data right?: TLDR for your average user: 0.4mm nozzle shouldn’t print faster than 150mm/s with “typical” settings printing PLA. See results for the proper volumetric machine limit I measured. Set up:: Printing a large cylinder in vase mode. 0.2mm layers, 0.45mm extrusion width, constant tool head speed of 60mm/s. Goal is constant and controllable extrusion speed. Multi-spool mode KVP PLA spliced with 2,2,0 Method:: I increased the feed rate multiplier until the P3P ran out of buffer and caused the extruder to skip. Got up to 250% feed rate, 270% caused skipping. Even showed the P3P do a ‘worst case’ filament run-out at a pong event at 250% feed rate which looked very tight to the end of the buffer, but didn’t skip. Worth noting I do have a very long output tube ~120mm, shorter output tubes may have slightly less forgiveness. Results:: Machine limit is about 13.5mm^3/s, or 5.6mm/s filament speed. Phew! I got worried in my previous answer that I was going to need to slow WAY...
I’ll take a WAG at this. Offer a wrong answer and someone will correct it right? Measured data/assumptions: Filament provided during the compression step is negligible. P3P max drive speed: 200mm in 5s, or 40mm/s (raw 1.75mm filament speed) P3P USABLE buffer length: ~70mm- Measured available filament in buffer from when splice core starts heating. 0,0,0 P3P splice time: 28s Printer is continuously consuming filament, AKA no travel moves, no features that vary the flow rate. 1: Single splice: Buffer length and splice time- The thought here, if there is a single splice with a constant (maximal) rate of filament used, there is a maximum filament the buffer can make up while the filament is paused. Bonus points if someone else factors in the filament fed while compression is happening gets accounted for. This would just be the usable buffer(mm)/splice time(sec), or about 2.5mm/s. or about 4.4mm^3/s This should be a lowerbound given the buffer will be fed during the compression and cooling steps. 2: Infinite...
I’m running into something very similar, sometimes the Pallet is missing pings entirely. I’m using P2PP to generate the commands for my P3P in accessory mode, my next steps is to try using a linear ping length. I’m not sure how Canvas spaces out pings, or where those ping settings are managed. What model are you trying to print on what printer?
Katy, If I understand the question, the splice settings are configured in Canvas under the material profiles, then you select the material in each drive. Often you have to define both directions of splicing as say ABS->PETG might not be the same settings as PETG->ABS. The splice tuning guides cover a lot of this with slight variation between Pallet devices For ‘custom’ print modes (Multi-spool, random, etc) you just define the splice parameters once at the start of the print on P3P assuming it all runs on the same material, not sure about the other models. It’s a royal shame they can’t save the splice settings to Canvas after tuning. As kindly as I’m able to say it- I’m looking forward to all the promises of this next major update. Cheers
I’ve had luck on the P3 Pro with:
KVP ABS <-> KVP ABS with 8, 3, -2
KVP ABS <-> KVP 3DSolve with 8, 4, 0
Is there a place to collect and share user splice values?