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

    dek

    @dek

    0
    Reputation
    1
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Website www.thingiverse.com/dekem/ Location Sweden

    dek Unfollow Follow

    Latest posts made by dek

    • Conditional logic documentation

      Is there any documentation regarding this? I've seen the homing if-statement macro so it has to be somewhere?

      I wanted to make a if statement that exit my stop-macro if the Auto-sleep is checked and run the sleep macro instead.

      posted in Tuning and tweaking
      dekundefined
      dek
    • RE: Turning off ATX (M81) makes me lose homes

      Ok thanks! Good to know! Thought I could shave off a few seconds on my prints.

      posted in Tuning and tweaking
      dekundefined
      dek
    • Turning off ATX (M81) makes me lose homes

      I have my printer run M81 with a stop macro after each print and I'm wondering if it's possible to do without losing your homes. I still have 5V to run the duet board so it shouldn't happen? Or have I set up something wrong?

      posted in Tuning and tweaking
      dekundefined
      dek
    • RE: Problem with powering on with M80

      @dc42 said in Problem with powering on with M80:

      @dek said in Problem with powering on with M80:

      I have the start script stored on the duet and referencing it in the slicer with "M98 P/macros/Scripts/start.g"

      And start.g starts with:
      M80 ; Power On
      G4 S5 ; Dwell for 5 seconds

      But the printer doesn't even power up. However, sending the M80 command in the G-code console works.

      Is the M98 command right at the start of the GCode file generated by the slicer? I have a suspicion that if you look, you will find there there are some heating commands before it.

      Have you tried putting the M80 command in file /sys/start.g file instead? That script is run automatically when you start a print from SD card, unless you are using old firmware.

      Yes, this worked! Thank you!

      As Veti said I think the problem was that Cura generated the commands in the wrong order. By a start.g in the sys directory I can still keep it simple in the slicer. This will make switching between different slicers easier.

      posted in Tuning and tweaking
      dekundefined
      dek
    • RE: Problem with powering on with M80

      I have the start script stored on the duet and referencing it in the slicer with "M98 P/macros/Scripts/start.g"

      And start.g starts with:
      M80 ; Power On
      G4 S5 ; Dwell for 5 seconds

      But the printer doesn't even power up. However, sending the M80 command in the G-code console works.

      posted in Tuning and tweaking
      dekundefined
      dek
    • Problem with powering on with M80

      I'm trying to have the printer power on when I send it a file to print from Cura with the DuetRRF plugin. I'm sending the M80 in the start script but this doesn't work because I'm guessing it needs to power on earlier than this in the printing process. Is there any way of trigger the M80 when the printer receives a print command?

      posted in Tuning and tweaking
      dekundefined
      dek