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

    Topics created by Ralms

    • Ralmsundefined

      Drive standard LEDs. What is the max current rating of IO pins?

      Duet Hardware and wiring
      • • • Ralms
      9
      0
      Votes
      9
      Posts
      256
      Views

      o_lampeundefined

      @Ralms instead of relais and optocoupler you might find a simple inverter/driver chip with optocoupled input in the good'ol 74hcxxx series.

    • Ralmsundefined

      Solved [Solved]Prevent docking/undocking of probe during multiple G30

      Tuning and tweaking
      • • • Ralms
      3
      0
      Votes
      3
      Posts
      113
      Views

      Ralmsundefined

      @jay_s_uk said in Prevent docking and undocking of probe during multiple G30 Pn:

      @Ralms call M401 to undock the probe and then do all your probing routines. That should prevent it docking it between.
      Then M402 at the end

      That did the trick.
      Thank you!

      Need to look into submitting some documentation improvements after finishing coding the printer lol

    • Ralmsundefined

      Using G30 S0 inside homez.g fails

      Tuning and tweaking
      • • • Ralms
      17
      0
      Votes
      17
      Posts
      441
      Views

      droftartsundefined

      @Ralms said in Using G30 S0 inside homez.g fails:

      The issue I'm raising now, is that G30 will execute from the console, even if deployprobe.g fails, it just ignores it and that should never happen.

      G30 works from the console or from within a macro, whether the Z axis is homed or not. The X and Y axes must be homed. When G30 is called, it will run deployprobe.g if the probe type requires it. When and why might deployprobe.g fail, and how would it know if deployprobe.g has failed? If running G30 from the console, it could possibly be too low to fully deploy, eg BLTouch, or off the bed, but I'd say this was operator error rather than the firmware's fault. You could have a check in deployprobe.g for current Z height, if it is below say 2mm, or if the axis is unhomed, move up 5mm. The stock homez.g from the configuration tool moves the Z axis up 5mm before homing to avoid this.

      Ian

    • Ralmsundefined

      Duet 3 Standalone update from 3.3.0 to 3.4.0 failed

      Firmware installation
      • • • Ralms
      7
      0
      Votes
      7
      Posts
      268
      Views

      Ralmsundefined

      @jay_s_uk said in Duet 3 Standalone update from 3.3.0 to 3.4.0 failed:

      @ralms https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
      fallback procedure 2 using bossa

      Well, after delaying this process for a few days, expecting a nightmare and headache knowing what to do, it was actually fairly painless.

      After flashing the board with Bossa its back to working normally.

      Just one suggestion regarding the documentation, the Bossa section is missing a last step just confirming that we are free to reset or disconnect the board from USB and use it normally.

      Thank you.

    • Ralmsundefined

      RepRapFirmware 3.2.2 update question

      Firmware installation
      • • • Ralms
      5
      0
      Votes
      5
      Posts
      262
      Views

      dc42undefined

      @Ralms said in RepRapFirmware 3.2.2 update question:

      've noticed that there is no "Duet3and3Firmware-3.2.2.zip" combined file.

      I have now added that file and announced the 3.2.2 release. The IAP file is unchanged from firmware 3.2.

    • Ralmsundefined

      Duet 3 Extruder control disabled

      General Discussion
      • • • Ralms
      24
      0
      Votes
      24
      Posts
      2.1k
      Views

      droftartsundefined

      @Ralms Thanks for the example. Unfortunately, we are rather limited by the Dozuki software (developed and used by ifixit.com) we use for documentation. There's no drop down selection, tabbed content or even ability to hide sections. It would be good to have documentation specific for each board and RRF version, but that would mean a lot of duplication of pages, so it's a case of putting the most relevant information first, then having notes for other variations. Not ideal, but all that can be done within the current limitations.

      We're always on the look out for alternatives (preferably open source or at least with a low cost of entry), particularly if the existing documentation can be ported easily, so welcome any suggestions.

      Ian

    • Ralmsundefined

      Motech MT-1704HSM168RE shaft without flat section

      General Discussion
      • • • Ralms
      3
      0
      Votes
      3
      Posts
      312
      Views

      Phaedruxundefined

      I've got the same motor and I dremmeled a flat. I clamped it to a table and used electrical tape to protect the innards. Took all of 5 minutes., which was worth it to me to guarantee no slipping on the shaft. Though droftarts makes some points I hadn't considered at all.