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

    Topics created by lignumaqua

    • lignumaquaundefined

      Question about diagonal rod length in M665

      Tuning and tweaking
      • • • lignumaqua
      3
      0
      Votes
      3
      Posts
      838
      Views

      lignumaquaundefined

      Thanks David. No, I don’t have a config-override.g file, but changing diagonal rod length still makes no difference. I have no idea why.

      However - M579 worked perfectly! I had thought from the RepRap code help page that it only worked with cartesian printers, and not with delta, but all is good. Thank you. 🙂

    • lignumaquaundefined

      Z speed when probing

      Tuning and tweaking
      • • • lignumaqua
      4
      0
      Votes
      4
      Posts
      840
      Views

      lignumaquaundefined

      It’s very quick so you are probably right that it’s the max Z speed. I’ll try changing that.

    • lignumaquaundefined

      Problem with slow Duet WiFi

      General Discussion
      • • • lignumaqua
      7
      0
      Votes
      7
      Posts
      1.6k
      Views

      lignumaquaundefined

      This gets stranger. Adding in an M117 somewhere in config.g, even one with no text, fixes the problem! The 'Starting up' message comes up for a flash, less than a second, before going to 'Idle'. Comment out that M117 and it goes back to taking 30 seconds.

      I'm guessing that it's always finished booting, it's just that PanelDue doesn't know about it. The addition of the M117 forces a communication with PanelDue that corrects the missed message.

      Anyway, with the blank M117 in there all works fine.

    • lignumaquaundefined

      Heater controls - Duet with PanelDue

      General Discussion
      • • • lignumaqua
      12
      0
      Votes
      12
      Posts
      2.0k
      Views

      dc42undefined

      Thus is fixed in the forthcoming 1.15f release. Meanwhile, you may be able to work around the issue by inserting command G4 P1000 before the T0 command at the end of config.g.

    • lignumaquaundefined

      Microstepping with CoreXY

      General Discussion
      • • • lignumaqua
      7
      0
      Votes
      7
      Posts
      1.9k
      Views

      dc42undefined

      @lignumaqua:

      Ah, thanks. That makes complete sense and I started off thinking that's what I was going to have to do, then I read the Wiki (text below) which suggests that
      I assumed (always dangerous I know) that the steps/mm were based on the default 16x microstepping, and everything else was calculated from there. The Wiki appeared to confirm that assumption, but you always see what you want to see…

      When RRF sees a M92 command it takes that as the number of microsteps/mm at the current microstepping rate. If you subsequently use M350 to change the microstepping, then the steps/mm is recalculated by the firmware to allow for the change. If you then issue another M92 then that will be the number of microsteps/mm at the new microstep setting.

      So if you want to experiment with different microstepping, it's probably easiest to put your M92 command, calculated at x16 microstepping (the default at power up) before the M350 command. Then you can adjust the M350 command without having to adjust the M92 command.