tomvandeneede / p2pp

Palette2/3 Post Processing tool for Prusa Slicer
143 stars 39 forks source link

p2pp not working any more #193

Open pertoft opened 3 months ago

pertoft commented 3 months ago

Hi,

I have been using p2pp for a very long time - and it just works! Great job!

Lately, I have experience a problem with my Palette2s running in connected mode with klipper.

I slice using prusa slicer and p2pp, uploading it to moonraker and starts print. The palette starts making filament and gets ready asks for me to insert the filament into the extruder.

When I pull filament from the palette it will NOT make new filament, and when the buffer is empty i cant pull out anymore. Initially I thought it was an hardware problem and contacted palette support. After some troubleshooting, a hardware problem is ruled out.

We discovered that the problem only occurs when the gcode is sliced with p2pp and prusa slicer. If the same settings and printer profile is sliced in canvas3d, everything works.

There seem to be something in the gcode produced by p2pp which makes the palette2 not feeding filament correct.

Video of the problem: https://photos.app.goo.gl/KDTP1US9gGorCBbi7

Attached gcode: working-print.gcode.txt faulty-print.gcode.txt

Any suggestion what to change? Bug?

tomvandeneede commented 3 months ago

Did you mane any changes tot the process (new versions of Prusa Slicer e.g.)

On 11 Apr 2024, at 11:30, Per Abildgaard Toft @.***> wrote:

Hi,

I have been using p2pp for a very long time - and it just works! Great job!

Lately, I have experience a problem with my Palette2s running in connected mode with klipper.

I slice using prusa slicer and p2pp, uploading it to moonraker and starts print. The palette starts making filament and gets ready asks for me to insert the filament into the extruder.

When I pull filament from the palette it will NOT make new filament, and when the buffer is empty i cant pull out anymore. Initially I thought it was an hardware problem and contacted palette support. After some troubleshooting, a hardware problem is ruled out.

We discovered that the problem only occurs when the gcode is sliced with p2pp and prusa slicer. If the same settings and printer profile is sliced in canvas3d, everything works.

There seem to be something in the gcode produced by p2pp which makes the palette2 not feeding filament correct.

Video of the problem: https://photos.app.goo.gl/KDTP1US9gGorCBbi7

Attached gcode: working-print.gcode.txt https://github.com/tomvandeneede/p2pp/files/14944238/working-print.gcode.txt faulty-print.gcode.txt https://github.com/tomvandeneede/p2pp/files/14944240/faulty-print.gcode.txt Any suggestion what to change? Bug?

— Reply to this email directly, view it on GitHub https://github.com/tomvandeneede/p2pp/issues/193, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK6CHJJAPWJYEEZ6NCBIOL3Y4ZJ33AVCNFSM6AAAAABGB6IDQCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTOMRZG44DQMY. You are receiving this because you are subscribed to this thread.

pertoft commented 3 months ago

I have not used my setup for a long time. I have updated Prusa slicer to latest 2.7.4 and single color prints works flawlessly. I upgraded to the latest release on p2pp before last print. The slicing looks find and everything seems good.

The only problem is that the palette2 crashes / are slow / cpu overload and do not produce filament when its pulled from the buffer.

tomvandeneede commented 3 months ago

can you please send me the unprocessed file Will have a look

On 12 Apr 2024, at 13:50, Per Abildgaard Toft @.***> wrote:

I have not used my setup for a long time. I have updated Prusa slicer to latest 2.7.4 and single color prints works flawlessly. I upgraded to the latest release on p2pp before last print. The slicing looks find and everything seems good.

The only problem is that the palette2 crashes / are slow / cpu overload and do not produce filament when its pulled from the buffer.

— Reply to this email directly, view it on GitHub https://github.com/tomvandeneede/p2pp/issues/193#issuecomment-2051609556, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK6CHJMDKOYBNJZWRKWTVOTY47C77AVCNFSM6AAAAABGB6IDQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGYYDSNJVGY. You are receiving this because you commented.

pertoft commented 3 months ago

Do you mean the gcode after p2pp or the STL? The faulty-print.gcode.txt is the file from p2pp

tomvandeneede commented 3 months ago

Code file without the p2pp processing (temp disable the p2pp plugin but keep all the other settings the same)

On 13 Apr 2024, at 09:03, Per Abildgaard Toft @.***> wrote:

Do you mean the gcode after p2pp or the STL?

— Reply to this email directly, view it on GitHub https://github.com/tomvandeneede/p2pp/issues/193#issuecomment-2053547839, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK6CHJOLDSXOGMJ23VKWIG3Y5DKFLAVCNFSM6AAAAABGB6IDQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJTGU2DOOBTHE. You are receiving this because you commented.

pertoft commented 3 months ago

Sliced with prusa slicer and output to p2pp: 201901MosaicKeychain1_0.2mm_PLA_CR10S_51m.mcf.p2pp.gcode.txt Sliced with prusa slicer and no output script: 201901MosaicKeychain1_0.2mm_PLA_CR10S_51m.mcf.plain.gcode.txt