shishu94
commented
7 months ago Hello,
Thank you for reaching out. Very glad to see that the bridge works as intended.
Now for your problem. A few things. One that you guessed correctly. The slow down being delayed is indeed inherent to how klipper buffers the gcode. Depending on the machine this would be more or less pronounced. But 10s is a bit excessive. Do you mind sharing details about your setup (more like your klipper version, and maybe printer.cfg, to understand the specifics)? The bridge doesn't do anything special about it but I could introduce some logic to prioritize the slow down for splice feature, so it goes directly to the front of the queue. Can't promise any ETA, as I don't have much free time to work on this, but will do my best. Another way to solve this would be to catch via a wire when the palette cuts filament and trigger a slow down on klipper for X seconds.
Second, and the actual reason for your problem, this device has been developed to print at relatively moderate speed (around 100mm/s with .4 nozzle). That gives us a flow rate of 10mm3/s. Your are way to far from this. I also experienced the same problem on my mercury while printing with .6 at 200mm/s. I was almost always drying the buffer. I created an additional buffer that goes after the out port of the P3 which gives me roughly 80cm of additional filament, but this is still in progress as it kinda messes up with the ping/pongs of the Palette.
Sorry if I don't have a clear solution for you immediately, but this is something that I work only on my rare free time and shared it more as proof of concept to show that it works with klipper too. Let me know if you want to test the change I mentioned above. I can probably create the code quickly but will lack time for testing, and I don't want to push something that I don't know if it works. Maybe you can help on that side.
Le mer. 10 avr. 2024, 22:45, 3dprintpittsburgh @.***> a écrit :
We bought a Palette 3 Pro in order to provide automated spool swapping for a large format 3D printer we're working on. This printer uses 1.75 filament, and we normally run it with a 1.2mm nozzle and .8mm layer height at around 40mm/s speed. This translates to around 38.5mm3/s flow rate from the extruder. On first layers, we print slower, at around 20mm3/s or so. I've gotten it hooked up to our machine and started trying to run a connected mode print after following the setup instructions here and making a serial bridge from two USB to serial converters. Everything works fine and the print starts as expected. All the initial splices happen and work as expected, however I find that when the printer actually starts printing, that it seems to outrun the splice rate of the machine.
That said, I did set up the setting to slow down the printer when splices happen, however it doesn't seem to immediately trigger when the splice starts. Rather, the splice seems to start, and then 10-15 seconds later the printer actually slows down. In a lot of instances, this isn't fast enough, and all remaining slack in the buffer zone is pulled out, resulting in the filament breaking and the print failing. Then, 30-40 seconds after the splice is already done and the palette is back up to full speed, the printer speeds back up. It's as if the slow down and speed up are both delayed. I'm guessing this has something to do with the way commands are buffered or sent over USB in connected mode, or maybe something to do with my connection to the machine, but all commands do seem to be running properly, it's just that there's a big delay in the slow down for splicing. Do you have any ideas for me? I feel like I'm so close to being able to use this machine for automated run out splicing for our big machine.
— Reply to this email directly, view it on GitHub https://github.com/shishu94/Klipperotchy/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGTZRJRM3B6SYNG26RN63CTY4WQGXAVCNFSM6AAAAABGBDWVNGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTMMZZHA2DGMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
3dprintpittsburgh
We bought a Palette 3 Pro in order to provide automated spool swapping for a large format 3D printer we're working on. This printer uses 1.75 filament, and we normally run it with a 1.2mm nozzle and .8mm layer height at around 40mm/s speed. This translates to around 38.5mm3/s flow rate from the extruder. On first layers, we print slower, at around 20mm3/s or so. I've gotten it hooked up to our machine and started trying to run a connected mode print after following the setup instructions here and making a serial bridge from two USB to serial converters. Everything works fine and the print starts as expected. All the initial splices happen and work as expected, however I find that when the printer actually starts printing, that it seems to outrun the splice rate of the machine.
That said, I did set up the setting to slow down the printer when splices happen, however it doesn't seem to immediately trigger when the splice starts. Rather, the splice seems to start, and then 10-15 seconds later the printer actually slows down. In a lot of instances, this isn't fast enough, and all remaining slack in the buffer zone is pulled out, resulting in the filament breaking and the print failing. Then, 30-40 seconds after the splice is already done and the palette is back up to full speed, the printer speeds back up. It's as if the slow down and speed up are both delayed. I'm guessing this has something to do with the way commands are buffered or sent over USB in connected mode, or maybe something to do with my connection to the machine, but all commands do seem to be running properly, it's just that there's a big delay in the slow down for splicing. Do you have any ideas for me? I feel like I'm so close to being able to use this machine for automated run out splicing for our big machine.