Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. BlueDust
    • Profile
    • Following 1
    • Followers 1
    • Topics 80
    • Posts 543
    • Best 24
    • Controversial 0
    • Groups 0

    BlueDust

    @BlueDust

    IT, its not only my day job. It's also my hobby.

    Even though I have been playing with a Monoprice Select v2.1 since December of 2017, I still feel like a noob. Saying that I want to learn more and have a printer that can give me consistent quality prints. As such I built a CoreXY (RatRig v-Core Pro) with a DuetEth and E3d.
    Now on to my next build. In progress of building a Custom IDEX using rails (v-Cast kit from RatRig) on a Duet3.

    "I just built my first bowden printer today. Right now I really like it, but 5 minutes ago "bowden" was a bad word. I think it may become a bad word again soon." - I said that. Just now.

    27
    Reputation
    38
    Profile views
    543
    Posts
    1
    Followers
    1
    Following
    Joined Last Online
    Website twitter.com/wickettsnet

    BlueDust Unfollow Follow

    Best posts made by BlueDust

    • RE: Auto Bed Leveling went bad

      @Phaedrux
      This printer has been causing me a lot of quality problems since Dec of 2019 where I sort of let it rest (small single object TPU/TPE jobs printed fine) for a year after Covid happened before putting more (but random) time in to troubleshooting it.
      Over the last few years replaced all the major parts including this last week replaced the Duet2 with a Duet 3 and 1lc tool board. Once I got everything for the most part working (ie printer could print), I started working on Auto Bed Leveling again, and was again having trouble that reminded me about this post. I reread your question a few times (asking if I run leveling multiple times in a row does it get worse) thinking it was a clue. But as I never reran auto bed leveling more then once in a row, I didn't see this happen when I was testing, as the bed would get so far out of level that the BL Touch would give up or already be triggered when it went to a location to probe for the bed.
      Turns out this was the problem the printer was having after I moved to the Duet 3. Every time I ran it, bed leveling got worse in the same way. Focusing on what could cause this, I realized that the Z motors were not associated with the correct locations.

      I am not sure on what caused the problems with this printer on the Duet 2, but think the board is OK and it was just some calibration that got out of whack when trying to print a handful of different filaments that ended up being bad... And wasn't able to figure out what I did. Going to the Duet 3 forced me to redo everything, gave me an Accelerometer for Input Shaping and all the other goodies I get when using an SBC. So I am not complaining.

      And as always. Thanks for the help!

      posted in IR Height Sensor
      BlueDustundefined
      BlueDust
    • RE: Options for print monitoring

      A long time ago, when I think it was called motion pi??? I used to use this...
      https://github.com/motioneye-project/motioneyeos/wiki

      Or going directly to the main page and using its generic install might work if you want to install on on your Pi OS.
      https://github.com/motioneye-project/motioneye

      I don't remember the details, but believe I had the Duet Web interface connect to the live stream so I could watch the video directly from the Duet.

      posted in Third-party software
      BlueDustundefined
      BlueDust
    • Sharing my Tools

      I used to keep websites book marked or search Google each time I wanted to calibrate my printers. To make life easier, I made my own formula spreadsheet in Google docs.
      Thought I would share it as it might also be useful to others.
      As it is not shared as writable, you will have to copy it to your own Google account to modify. Please let me know if you have other formulas that you find useful as I would like to add them as well.

      https://docs.google.com/spreadsheets/d/16b_Ha3-pXSKHyUNqQK8N4RKqH9bqpy0vR_kGTuBWbVk/edit?usp=sharing

      posted in Tuning and tweaking
      BlueDustundefined
      BlueDust
    • RE: New Random issue

      Removed the set screw, and the needle fell out. It was clean. Looked new. Looked over the BLTouch and found nothing weird. All looked new, and couldn't find any dirt/dust or anything. I played with it a bit (needle up and down with set screw removed) and put it back together (word of warning, the needle can be fired out the set screw hole a few inches and become lost). Now it just works. Ran it in test mode for about 2 minutes and no issues. I have no idea what to make of it but not complaining.

      Thanks @Phaedrux for reminding me about the screw!

      posted in General Discussion
      BlueDustundefined
      BlueDust
    • RE: Baby Stepping stopped working

      @Phaedrux
      Thanks for your help @Phaedrux.
      I may start a new thread later, but you were able to help me make it work better (more accurate) and now if I lower the first layer height a tad, its no longer a big deal. After you mentioned slowing down the speed to find the bed, and I saw it was more accurate, I tightened down the screws/springs on the BLTouch and that seemed to help a small amount too. Not as much as slowing it down but still.... I just need to get back to printing some test prints to test multi color out, to see if it would be good enough for Christmas gifts. Or if I should just print one color and paint...

      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust
    • RE: from e3D Titan (bowden) to bondtech QR3.0 (bowden) Problems

      @as-3d-druck said in from e3D Titan (bowden) to bondtech QR3.0 (bowden) Problems:

      ill just try to print that and tell in what results that T

      Start out with the steps Bondtech or any vendor tells you. But you have to calibrate to make it accurate afterwords. I have both a titan and bondtech... from what I remember, the vendor numbers always had me over extruding (on both extruders). Some people also calibrate with every role of filament. But I don't re calibrate steps unless I see problems.

      posted in Tuning and tweaking
      BlueDustundefined
      BlueDust
    • RE: Duet Stops mid print

      @NitroFreak

      Did you see the M122 you posted shows crazy high Hiccups too?

      Hiccups: 10265739

      Your hiccups may not have been caused by the same reason as mine, but that may be the problem. I only use S3d or Canvas when I paint a model. I don't remember if I tried using Canvas or not and saw this issue...

      I no longer have any Hiccups on my Duet2.

      posted in General Discussion
      BlueDustundefined
      BlueDust
    • RE: Dead Driver or Stepper Motor?

      How much should I worry about other damages at this point?

      I can't see anything wrong with that crimp... Other then the fact its burnt up that is.

      IMG_20200608_210300~2.jpg

      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust
    • RE: Not using X0 Y0 for home

      The skipped lines was actually an empty nozzle.

      On pause, the nozzle pulls back 10mm.

      On resume, it pushes out 10mm.

      The nozzle always extrudes a bit at the 10mm push... which means, when it gets back to to printing, the nozzle is empty.
      I don't know why this was never an issue on resume before, but I ended up have it set the resume for 35 mm to ensure the nozzle will be full enough to properly extrude when it gets back to printing. That seems like alot, and odd I haven't noticed this issue before.
      I did recently complete some upgrades. Upgraded to 3 Z motors to enable actual bed leveling, and swapped out the laser filament monitor for the magnetic one.

      posted in Tuning and tweaking
      BlueDustundefined
      BlueDust
    • RE: Duet3 config Frustration

      @dc42
      Are you saying I could wire in two, DUET 3 TOOLBOARD 1LCs directly into the Duet3 (without a Distribution Board)?
      When reviewing the instructions, it looked like I could only wire one directly to the Duet 3 at a time.

      posted in General Discussion
      BlueDustundefined
      BlueDust

    Latest posts made by BlueDust

    • RE: After update, DWC is out of Sync with board.

      @jay_s_uk

      LMAO!

      That's a fun ending to this story!
      Thanks!

      posted in Firmware installation
      BlueDustundefined
      BlueDust
    • After update, DWC is out of Sync with board.

      I am running a Duet3 connected to an SBC. I completed the update from the Pi console using apt-get update/upgrade like I have done in the past, but DWC apparently didn't update.
      What is the best way to update the DWC out of band (hopefully without having to redo everything)?

      Thanks!

      d3fdfb0f-0447-442e-9d72-cd40e9f20dfc-image.png

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.5.4 (2024-11-24 10:47:10) running on Duet 3 MB6HC v1.02 or 1.02a (SBC mode)
      Board ID: 08DJM-9P63L-DJ3T8-6J9D6-3SN6S-1U7ZB
      Used output buffers: 2 of 40 (40 max)
      === RTOS ===
      Static ram: 155464
      Dynamic ram: 89560 of which 5272 recycled
      Never used RAM 91928, free system stack 112 words
      Tasks: SBC(2,ready,0.9%,807) HEAT(3,nWait 6,0.0%,321) Move(4,nWait 6,0.6%,211) CanReceiv(6,nWait 1,0.0%,771) CanSender(5,nWait 7,0.0%,325) CanClock(7,delaying,0.0%,346) TMC(4,nWait 6,9.3%,53) MAIN(2,running,89.1%,101) IDLE(0,ready,0.0%,29), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 113:05:29 ago, cause: software
      Last software reset at 2025-01-28 21:32, reason: User, Gcodes spinning, available RAM 91928, slot 2
      Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x04
      Aux0 errors 0,2,0
      MCU temperature: min 32.6, current 36.9, max 40.9
      Supply voltage: min 23.8, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.0, current 12.3, max 12.6, under voltage events: 0
      Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/568/568, gc cycles 0
      Events: 1 queued, 1 completed
      Driver 0: standstill, SG min 0, mspos 136, reads 25594, writes 75 timeouts 0
      Driver 1: standstill, SG min 0, mspos 760, reads 25595, writes 75 timeouts 0
      Driver 2: standstill, SG min 0, mspos 744, reads 25595, writes 75 timeouts 0
      Driver 3: standstill, SG min 0, mspos 104, reads 25445, writes 225 timeouts 0
      Driver 4: standstill, SG min 0, mspos 232, reads 25465, writes 205 timeouts 0
      Driver 5: standstill, SG min n/a, mspos 8, reads 25659, writes 11 timeouts 0
      Date/time: 2025-02-02 14:38:08
      Slowest loop: 1001.02ms; fastest: 0.04ms
      === Storage ===
      Free file entries: 20
      SD card 0 not detected, interface speed: 37.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 125, segments created 38, maxWait 78056668ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 115883, on retry 37828, too short 221420, wrong shape 1257363, maybepossible 63368
      === DDARing 0 ===
      Scheduled moves 615600, completed 615600, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 2 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 0 is on, I-accum = 0.0
      Heater 2 is on, I-accum = 0.1
      === GCodes ===
      Movement locks held by null, null
      HTTP* is doing "M122" in state(s) 0
      Telnet is idle in state(s) 0
      File* is idle in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger* is idle in state(s) 0
      Queue* is idle in state(s) 0
      LCD is idle in state(s) 0
      SBC is idle in state(s) 0
      Daemon is idle in state(s) 0
      Aux2 is idle in state(s) 0
      Autopause is idle in state(s) 0
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x80000003
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 5265641, received 8143332, lost 0, errs 16, boc 0
      Longest wait 3ms for reply type 6013, peak Tx sync delay 280, free buffers 50 (min 49), ts 2035646/2035645/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 5, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 11810/11810
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x24c68
      Buffer RX/TX: 0/0-0, open files: 0
      === Duet Control Server ===
      Duet Control Server version 3.5.4 (2024-11-25 17:29:06, 32-bit)
      HTTP+Executed:
      > Executing M122
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 39.15, max time between full transfers: 303.0ms, max pin wait times: 186.1ms/22.8ms
      Codes per second: 4.69
      Maximum length of RX/TX data transfers: 4520/1664
      

      I would also like to thank you for this update as it fixed an odd problem that just recently started. I wasn't having any issues with my printer to really speak of until about 3 weeks ago. I figured it may be a hardware issue because the problem just started without having made any changes to the printer in a long time, but wanted to update before I posted the issue here asking for help. Its hard to explain but generally noticed it when the PanelDue failed to run specific touch screen commands like "resume" after pausing a print. I guess its possible the MicroSD card is starting to die and the update replaced the corrupt files (still being a hw issue) but wanted to share incase it helps someone else and stating just updating the Duet Software may help. (I didn't replace my MicroSD card, only updated via SBC)
      Copied one of the errors here from event logs.

      Error: Pop(): stack underflow on Aux
      
      posted in Firmware installation
      BlueDustundefined
      BlueDust
    • RE: Tool board 1.2a crimp question

      @Exerqtor
      I have never tested stall detection on the extruder but would if I used a Bowden Extruder. I was just trying to have the printer rehome X and Y if the fan shroud or BLtouch got stuck on a part of the print that bent upwards, but never finished dialing it in.

      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust
    • RE: Tool board 1.2a crimp question

      @dc42
      Thanks for the feedback. I will have to play with this...

      M566 X700.00 Y700.00 Z60.00 E2000.00                  ; set maximum instantaneous speed changes (mm/min)
      M203 X8400.00 Y8400.00 Z180.00 E3000.00               ; set maximum speeds (mm/min)
      M201 X1200.00 Y1200.00 Z40.00 E1600.00                ; set accelerations (mm/s^2)
      M906 X1200 Y1200 Z1200 E1000 I30                      ; set motor currents (mA) and motor idle factor in per cent
      
      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust
    • RE: Tool board 1.2a crimp question

      I received the PA-09 crimper and plan to use it soon to try and improve some crimps/connections.
      But I have an ongoing error I want to resolve first to help troubleshoot new problems I may have after I touch the crimps.
      Question...
      Can this error only be caused by bad crimps? Or is there another possible cause? I think I had this same error when I first setup one of my printers years ago, and from what I remember was caused by a physical wiring problem. The problem I have right now making me not want to touch anything, is that everything appears to be working, and was starting to think this was related to some left over stall config from the Duet2 that I never got working 100%... When I enabled stall detection, the printer stops and find homes randomly when not needed during the print (still needs tweaking). Also, when I had the printer still in pieces (but working) during this Duet3 upgrade, it appeared the drivers showing this problem are all on the Z axis.

      3/7/2024, 11:26:44 AM Warning: Driver 4 stalled at Z height 7.86
      3/7/2024, 11:21:43 AM Warning: Driver 4 stalled at Z height 7.62
      3/7/2024, 11:16:12 AM Warning: Driver 4 stalled at Z height 7.38
      3/7/2024, 11:12:46 AM Warning: Driver 4 stalled at Z height 7.14
      3/7/2024, 10:26:45 AM Warning: Driver 4 stalled at Z height 5.22
      3/7/2024, 10:17:37 AM Warning: Driver 4 stalled at Z height 4.74
      3/7/2024, 10:10:56 AM Warning: Driver 4 stalled at Z height 4.50
      3/7/2024, 9:45:10 AM Warning: Driver 4 stalled at Z height 3.30
      3/7/2024, 8:28:31 AM Warning: Driver 4 stalled at Z height 12.28
      3/7/2024, 8:28:31 AM Warning: Driver 4 stalled at Z height 12.28

      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust
    • RE: It was an accident...

      @Phaedrux
      This is the printer I recently swapped out a duet2 for duet3. Still tweaking things and haven't gotten to the point of backing it up yet. But as I am close probably should have backed it up two weeks ago. 😞

      Thanks for the help!

      posted in Off Topic
      BlueDustundefined
      BlueDust
    • RE: It was an accident...

      @Phaedrux
      I didn't know the bak file was updated each time the config was saved... It was last modified early this month and thought I had changed something since then. But also didn't know the file is updated with the main config file.

      Thanks! I will review it and put more confidence in the bak going forward.

      posted in Off Topic
      BlueDustundefined
      BlueDust
    • It was an accident...

      I went to edit the config of a Duet3/SBC printer via DWC, and accidently clicked delete instead.
      Is there a way to export the running config to console? I could then save that to a text file and rebuild it from there.

      posted in Off Topic
      BlueDustundefined
      BlueDust
    • RE: Tool board 1.2a crimp question

      @oozeBot
      I only checked one site and not sure if it was an outlier... But those make expensive look cheap.

      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust
    • RE: Tool board 1.2a crimp question

      @jens55 @oliof @dc42

      Thanks for the feedback.
      The crimper I have crimps both the wire and insulation at the same time, ie I am not able to do one without the other. I get poor/no crimping on the wire itself, and too much on the plastic shielding and it breaks.
      Reading your suggestions makes me believe I just don't have the right tool for these small JST connectors.
      PA09 appears to be the correct one for the job, and appears simply searching for "JST 2.0" connectors on Amazon should help me find the correct replacement connectors I need.

      Thanks for the help!

      posted in Duet Hardware and wiring
      BlueDustundefined
      BlueDust