Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. holco62
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 49
    • Best 4
    • Controversial 0
    • Groups 0

    holco62

    @holco62

    4
    Reputation
    1
    Profile views
    49
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location Nederland Age 62

    holco62 Unfollow Follow

    Best posts made by holco62

    • RE: Can't get part cooling fans running :(

      I see it now 😊 line 4 and 5 is for the hotend fan that triggers on 45 degree, I only have to put the connector on the FAN1 output which is now connected on a always on output 🙄

      Have a lot to learn about G-code 😀

      posted in General Discussion
      holco62undefined
      holco62
    • RE: Can't get part cooling fans running :(

      Still needed some tuning, but a week ago I did not expect to have a working printer already 😎

      https://youtu.be/CeavMw9Q42I

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      Tomorrow is a new day, I have to go to bed now.

      But thanks for all the help 🙂

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      @holco62 said in when will the new Z-height actually be saved?:

      Ok it starts to get a bit clearer (very small bit 😏 )

      Btw, how can I prevent the printer from homing after G32?

      I would like to have this sequence,

      First manually set bed temp / hotend temp in Duet control

      Load print command> homing axes> G32> start printing, so no homing after G32.

      Removed the start.g file and added G32 in the Cura exstruder start-g code, everything now works exactly as I want 😎

      posted in General Discussion
      holco62undefined
      holco62

    Latest posts made by holco62

    • RE: when will the new Z-height actually be saved?

      @Phaedrux said in when will the new Z-height actually be saved?:

      @holco62 said in when will the new Z-height actually be saved?:

      What did the line "G1 Z15.0 F1000; short move" that has now been removed?

      Nothing useful.

      Haha, oké

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      Another question 😊

      If the printer runs the G32 calibration, the nozzle leaves a little filament on each calibration spot, now I wondered if it is possible that after each print job, for example, 50mm retraction takes place so that the hotend is always free of filament, and that after the G32 calibration the 50mm (or more) is immediately re-fed.

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      Works perfectly now 👍 👍 👍

      https://youtu.be/tdl2iDNiC9Q

      What did the line "G1 Z15.0 F1000; short move" that has now been removed?

      Btw, I think it's really remarkable that you can remember all those codes 👌

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      The G32 is in the Extruder Start G-code.

      Extruder Start G-code.png

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      four_square_retrac.8mm.gcode

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      homedelta (1).g bed (1).g config (1).g

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      Cura doesn't let me copy the start G-code, so I took 2 pictures

      Start G-code-1.png

      Start G-code-2.png

      I'll post the rest in a moment

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      G32 works well in Cura (Extruder Start Gcode), but with the start of a print when all temps have been reached the effector first slowly approaches the bed, just before the nozzle hits the bed, it's homing and then starts the G32 calibration and goes printing.

      Is there any way to skip that initial slowly going to the bed?

      I am also curious if other changes / settings are needed with regard to Cura 4.8 which I have now set as a standard Anycubic Predator, especially stringing (PLA) gives me a hard time to get it right with a Mosquito hotend.

      I shot a short video of it

      https://youtu.be/cFRNCrjWwww

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      @Phaedrux said in when will the new Z-height actually be saved?:

      Post your Cura start gcode. That's where it would be defined.

      Technically you don't need to use start.g at all. You could do it all in Cura.

      M116; Wait
      G28 ; home printer
      G32 ; bed.g for leveling

      Or just use Start.g to preheat. Since it's a progression you can split it up however it makes sense. If you want you can even call a macro file in your slicer start gcode section.

      Sorry for quotting myself yesterday 😊 I was supposed to quote you in my penultimate post, but better late than never, you nailed it again so thank you 👍

      posted in General Discussion
      holco62undefined
      holco62
    • RE: when will the new Z-height actually be saved?

      @holco62 said in when will the new Z-height actually be saved?:

      Ok it starts to get a bit clearer (very small bit 😏 )

      Btw, how can I prevent the printer from homing after G32?

      I would like to have this sequence,

      First manually set bed temp / hotend temp in Duet control

      Load print command> homing axes> G32> start printing, so no homing after G32.

      Removed the start.g file and added G32 in the Cura exstruder start-g code, everything now works exactly as I want 😎

      posted in General Discussion
      holco62undefined
      holco62