Jump to content

Geckoas

Member
  • Posts

    24
  • Joined

  • Last visited

Posts posted by Geckoas

  1. 42 minutes ago, Slashee_the_Cow said:

    Have you tried getting a cup of tea and a good book? I've found that some (what seem like pretty simple) prints can just appear to freeze Cura for 5-10+ minutes.

     

    (Mandatory disclaimer: figure of speech. I don't drink tea. Or coffee.)

    I killed the Programm as it didn't respond after more than 30 minutes several times.

  2. On 7/30/2023 at 6:02 PM, GregValiant said:

    Turn off the Bridge settings.  They aren't needed for that model anyway.

     

    But the bridge settings should not be affecting the print like that either.

    Thank you. That's the point. Disabling the Bridge settings provides smooth walls in the 2nd layer. With Bridge settings enabled, it appeared only in the 2nd layer.

    2023-08-02_14h22_48.png

  3. The Post Processing Script "Retract Tower", with mode "Distance", generates false G-code for the retraction, after the tower is finished.

     

    At the end of the Tower, the Extruder is at E104.9.9863

    For retraction of the filament, the extruder moves back 11mm to E93.98630

    Then after switching of the heaters, the Extruder position is set to 1mm (G92 E1)

    After this, the Extruder extrudes 93mm of material (G1 F300 E93.98630), which causes a material blob at the decreasing tower. See included picture

     

    In the "Speed" Mode the Filament retraction is working well

    ;Retract the filament

    G92 E1

    G1 F3000 E-1.00000

     

    Please fix this error.

    Retract-Tower-Distance-Gcode.png

    Retract-Tower-Speed-Gcode.png

    Retract-Tower-Distance.jpg

  4. Cura 5.3.0 - Maschine settings notice box at "Start G-code" & "End G-code" covers input & not scrollable  - Github Issue #14963

     

     

    1.) When you hover with the mouse over the input fields of "Start G-code" & "End G-code" the notice box covers the whole window as long as you move the mouse outside.
    The notice box disappears when the mouse is outside this input fields.

    There's no possibility to push the notice box away to have a reference for the possible input.

    Please make the notice box moveable.

     

    2.) The notice box of "Start G-code" & "End G-code" are not scrollable.
    They contain more information as what can be displayed in the box.
    Please make them scrollable.

    2023-03-19_20h26_33.png

  5. PauseAtHeight script - Layer numbering mismatch between Cura workspace and gcode

     

    While using PauseAtHeight script I was faced with an issue that the layer numbering in Cura 5.3. workspace doesn't match to the produced gcode.

    I used a model with 10 flat layers and 2 layers with numbers on top.

     

    In the PauseAtHeight script I used layer 11 to start the pause for the filament change.

    During printing, the pause started after the first layer of the numbering, which was wrong.

    After this,  I checked the gcode file and found the difference.

     

    Layer numbering in Cura starts at layer 1, whereas in gcode it starts with "Layer:0" 

    As I selected layer 11, as displayed in Cura workspace, the PauseAtHeight script was inserted 1 layer too late.

     

    Please verify.

  6. Printing with different colors on my Anycubic Kobra with PauseAtHeight drove me nuts.

    For testing I used a testcylinder with D=10mm and H= 15mm.

    The PauseAtHeight breaks were programmed for layer 25 and 50 of total 75 layers.

     

    First I tried several setups of the PauseAtHeight script and no one, worked on my Kobra.

    This is, because Anycubic seems to not have proper installed M0 code.

    Finaly I found one setup with manual gcode adjustment that workes for me.

    The printer uses Marlin Gcode.

     

    General: Kobra Printer only stops for longer time, when "Pause"-Button on the display is pressed.

         - When  reaching the pause layer, the printer goes to park position , lift-up and Beep

         - When you press the "Pause"-Button  - printer displays " Paused, waiting for cache command to complete"

     

    1.) Keep Motors enganded (3600s) - not working

        - After pressing "Pause-Button- printer displays " Paused, waiting for cache command to complete"

        - This state last for minimum 1 hour - because of "M84 S3600 ; Keep steppers engaged for 1h"

     

    2.) Disarm Timeout (30s) - not working

         - Printer Goes to park position , lift-up and Beep

         - After pressing "Pause-Button- printer displays " Paused, waiting for cache command to complete"

         - This state last for infinite.

     

    3.) No Motors Enganged, Disarm timeout (0)  - not working

         - Printer Goes to park position , lift-up and Beep

         - After pressing "Pause-Button- printer displays " Paused, waiting for cache command to complete"

         - This state last for infinite.

     

    4.) No Motors Enganged, Disarm timeout (0),  G-code before Pause ((G4 S30) - not working

         - Printer Goes to park position , lift-up and Beep

         - After pressing "Pause-Button- printer displays " Paused, waiting for cache command to complete"

         - This state last for infinite.

     

    5.) No Motors Enganged, Disarm timeout (0),  + manual modification in gcode file ( M0 S30) - Working

         - Printer Goes to park position , lift-up and Beep

         - After pressing "Pause-Button- printer displays " Paused, waiting for cache command to complete" 

         - This state last for 30 seconds

        - Then z-axis lifts for the internal "Pause"- move

        - screen with "Resume"-Button is shown followed be some beeps.

        - After pressing "Resume" the printer primes the extruder and continues the work.

     

        - When you dont press "Pause", within 30 seconds of the first beep, the printer directly continues with extruder priming and printing.

     

    To achive this, I manually modified the generated G-code file as follows.

    **** generated G-Code ****

        M104 S230 ; standby temperature
        M300 S440 P1000 ; Beep
        M0 ; Wait for Pause
        M109 S230 ; WAIT for resume temperature

    *****

     

    ***** modified G-Code ****

       M104 S230 ; standby temperature
       M300 S440 P1000 ; Beep 
       M0 S30 ; Wait for Pause
        M109 S230 ; WAIT for resume temperature

    ****

     

     

    My Question is, if there's a possibility to include  this addition of S30 to the M0 Code in the script.

    Either permanent or with a separate Radio-button in the script parameters. 

    2023-03-12_19h54_31.png

    V3-AK_Testzylinder-10-15-M0-S30.gcode AK_Testzylinder-10-15 v1.3mf

  7. PauseAtHeight script - Layer numbering mismatch between Cura workspace and gcode

     

    While using PauseAtHeight script I was faced with an issue that the layer numbering in Cura 5.3. workspace doesn't match to the produced gcode.

    I used a model with 10 flat layers and 2 layers with numbers on top.

     

    In the PauseAtHeight script I used layer 11 to start the pause for the filament change.

    During printing, the pause started after the first layer of the numbering, which was wrong.

    After this,  I checked the gcode file and found the difference.

     

    Layer numbering in Cura starts at layer 1, whereas in gcode it starts with "Layer:0" 

    As I selected layer 11, as displayed in Cura workspace, the PauseAtHeight script was inserted 1 layer too late.

     

    Please verify.

  8. I think ther's a bug in the "Pause At Height" script when choosing the  "Redo Layer" option.

     

    I used a layer height of 0.2mm.

    When this option is checked, Z-height after the pause script is set for the same layer where the "Pause At Height" script started and not for the layer printed before. 

    In my case, I used a testcylinder with 15mm height and wanted to have "Pause At Height" at Layer 25 and Layer 60 of 75 layers in total.

    For the first instance, after layer 24, Z-axis was moved to 5.2mm before the script and also to 5.2mm after the script to redo layer 24. But 5.2mm would be the height for layer 25. Shouldn't Z be set to 5mm height to redo layer24 ?

     

    ****** Gcode Sample with "Redo Layer" checked

    ;MESH:NOMESH
    G0 F600 X111.336 Y114.781 Z5.2
    G0 F9000 X108.417 Y108.417
    ;TIME_ELAPSED:169.794624
    ;TYPE:CUSTOM
    ;added code by post processing
    ;script: PauseAtHeight.py
    ;current layer: 25
    M83 ; switch to relative E values for any needed retraction
    G1 F2400 E-6
    G1 F300 Z6.2 ; move up a millimeter to get out of the way
    G1 F9000 X30 Y30
    G1 F300 Z15 ; too close to bed--move to at least 15mm
    M104 S230 ; standby temperature
    M117 Click to continue
    M84 S3600 ; Keep steppers engaged for 1h
    M300 S440 P1000 ; Beep
    M0 ; Do the actual pause
    M109 S230 ; WAIT for resume temperature
    G1 F199.998 E5
    G1 F300 Z5.2
    G1 F9000 X113.591 Y113.591
    G1 F300 Z5.2 ; move back down to resume height
    G1 F1444.1 ; restore extrusion feedrate
    M82 ; switch back to absolute E values
    G92 E115.74526
    ;LAYER:24
    M204 S1000
    M205 X8 Y8
    ;TYPE:FILL
    ;MESH:Testzylinder-10-15 v1.stl
    G1 F1444.1 X113.591 Y113.591 E115.74526

     

    For reference, I sliced another file without checking "Redo Layer".

    I this case the same z height 5.2mm was used before  and after the script at layer 25.

     

    ****** GCode Sample with "Redo Layer" unchecked

     

    ;MESH:NOMESH
    G0 F600 X111.336 Y114.781 Z5.2
    G0 F9000 X108.417 Y108.417
    ;TIME_ELAPSED:169.794624
    ;TYPE:CUSTOM
    ;added code by post processing
    ;script: PauseAtHeight.py
    ;current layer: 25
    M83 ; switch to relative E values for any needed retraction
    G1 F2400 E-6
    G1 F300 Z6.2 ; move up a millimeter to get out of the way
    G1 F9000 X30 Y30
    G1 F300 Z15 ; too close to bed--move to at least 15mm
    M104 S230 ; standby temperature
    M117 Click to continue
    M84 S3600 ; Keep steppers engaged for 1h
    M300 S440 P1000 ; Beep
    M0 ; Do the actual pause
    M109 S230 ; WAIT for resume temperature
    G1 F199.998 E5
    G1 F300 Z5.2
    G1 F9000 X108.417 Y108.417
    G1 F300 Z5.2 ; move back down to resume height
    G1 F1444.1 ; restore extrusion feedrate
    M82 ; switch back to absolute E values
    G92 E119.21561
    ;LAYER:25
    M204 S1000
    M205 X8 Y8
    ;TYPE:FILL
    ;MESH:Testzylinder-10-15 v1.stl
    G1 F1444.1 X113.591 Y113.591 E119.45898

     

    Please find enclosed a screenshot, the project file  and both gcode files for investigation.

     

    If I'm wrong, please ignore and delete this post

     

     

    Regards Gerhard

     

     

    2023-03-10_17h00_14.png

     

    AK_Testzylinder-10-15 v1.3mf AK_Testzylinder-10-15 v1.gcode AK_Testzylinder-10-15 v1-noredo.gcode

  9. Hallo Franke66,

     

    Danke für den Link.

     

    Das Script hat vom Ablauf her auf dem Kobra funktioniert, obwohl ich verwundert war, das er nach dem ersten Beep und drücken von Pause zunächst wieder "..waiting for cache process to complete" angezeigt hat. Nach einiger Zeit kam dann aber der "Resume" Button.

    Nach Filamentwechsel und "Resume" hat es dann wieder etwas gedauert, bis er wieder gebeept und dann weiter gedruckt hat. Bei der ersten Lage nach dem Wechsel kam aber fast kein Material. Der Zylinder sah zunächst gut aus. Bei einem leichten seitlichen Druck ist er allerdings an der Nahtstelle der beiden Filamente auseinander gebrochen, was vmtl. an dem wenigen Material nach der Pause liegt.

     

    Frage: Wie kann die Haftung der beiden Teile verbessert werden?

     

  10. Because os the height of 105mm of my vacuum nozzle, decided to use Tab+ to get a better adhesion to the bed.

    In addition, I had chosen 5 Brim Lines.

     

    During printing the first layers I was surprised that the tabs, printed outside the Object didn't have contact to the object as wanted.

    There was a gap of approx 5mm between the outside tabs and the object.

    Thatwhy the tabs have been totaly useless.

    Also this tabs have been printed very thick, which wasn't neither intended nor wanted.

     

    Despite this, the object had enough adhesion to the bed, so the print was finished succcesfully, as you can see in the picture.

     

    I guess, whether I made a mistake with parameters of the Tab+ or if there is an error in the Tab+ extension.

    Comments welcome.

     

    Regards Gerhard

    IMG_20230301_164032.jpg

    2023-03-02_14h11_25.png

  11. On 2/24/2023 at 6:17 PM, Franke66 said:

    Habe jetzt ein Skript gefunden damit es auch den Kopra funktioniert

    Hallo Franke66, ich habe das gleiche Problem und auch diese Information vom Anycubic Support erhalten. Könntest Du bitte das Script veröffentlichen, welches bei Dir funktioniert.

×
×
  • Create New...