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

    Topics created by taegge

    • taeggeundefined

      Duet 6HC / SBC daughterboard

      Third-party add-ons
      • • • taegge
      5
      5
      Votes
      5
      Posts
      507
      Views

      taeggeundefined

      My vision is almost fully realized! I must have jinxed myself in my last post. No show stoppers, but have hit a couple issues:
      1- you might notice the ethernet jack isn't soldered. It's just dry-fit for show right now. I removed it after realizing that my part didn't match the footprint i used. It was a physical fit, but pins were wrong. I could only find the matching part overseas, so still waiting. I intend to update the schematic/layout to use a more common magjack. In the meantime wireless is working great.
      2- the 12v/24v regulator isn't behaving all the way up to 5A. It's fine up to 3A, but starts cutting out above 4A. I forgot to upgrade the inductor and diode when I moved my target from 3A to 5A. That's probably part of it. I need to take another look at the layout too. Thankfully 5v appears reliable all the way up to 5A. The printer i'm going to test this out on doesn't need the aux supply, so no biggie for now.
      3 - when I added the Molex KK PC style fan header, I mistakenly assumed the Pi5's 4 pin connector followed the same standard. Nope. Easy fix. Happy accident to get to trim the wires down and solder in the correct places. (I guess I could have rearranged the connectors too, but ick)

      Next step is to actually connect to a Duet3 🙂

      IMG_9231.jpg IMG_9232.jpg

    • taeggeundefined

      Duet3 + 3HC: G30 works, but G30 S-1 does not?

      Tuning and tweaking
      • • • taegge
      8
      0
      Votes
      8
      Posts
      241
      Views

      taeggeundefined

      @deckingman That is a good observation. For some reason I was thinking that limitation was resolved in 3.1.0/3.1.1.

      That still doesn't quite explain why I couldn't get the G30 S-1 command to return a valid height when the z-probe was connected to the expansion board, but it's good news that more change is coming in 3.2. Maybe that will resolve my issue.