Best posts made by BlueDust

@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!

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.

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

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!

@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...

@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.

@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.

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.

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.

@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.

Hey @Karma
I did "try" to scrap some of the carbon off the pin, but I don't think I was able to do a good job before I put it back together to test (and confirm it was just the wire/crimp). I will be taking it apart again to do a better job at cleaning the pin off.
I will replace the connector , as if I have more problems I don't want this burn mark to confuse me and hinder my troubleshooting in the future.
I am just happy it doesn't look like anything "real" was damaged. I really think this was a reminder that I planned to replace all of the motor wires with custom lengths and neatly hide them in the frame of the printer... Its a custom build, and I really haven't 100% finished it... After a lot of troubleshooting upfront I just wanted to print and prove it worked.... I think it has been almost 2 years now.

@Phaedrux
There is a link on the Sensorless homing wiki page that takes you to another page to talk about motors. This site has a link to download the calculation sheet I shared the screen shot of.

https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors

@Phaedrux

I have made progress. I was able to get ideaMaker to print only on the 2nd tool. Not sure why it works now, but not complaining.
Now trying to figure out how to get IDEX working in copy and mirror mode.
I opened a new thread.
Thanks for the help!

@Phaedrux
From what I could tell, everything was replaced expect for the config.g.bak file.
I restored a full backup I took in March, and know I have tweaked the home files a bit since then...
So far printing OK, but know some things have changed but not impacting me enough to be a noticeable issue right now.
Thanks for the feedback.

@Phaedrux

Currently inside first.

@phaedrux
I changed the settings. Will follow up next time I see the problem.

Thanks!

@jay_s_uk & @dc42

Thanks for the help!
The detailed information to the problems and suggestions on how to wire it up is very helpful!

@chrishamm

Correct. I don't need audio for any reason on the Pi. It is only used to control the Duet3.

No more errors.

Thanks again for the help!

pi@duet3:~ $ sudo apt remove pulseaudio-module-bluetooth bluealsa
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  bluealsa pulseaudio-module-bluetooth
0 upgraded, 0 newly installed, 2 to remove and 5 not upgraded.
After this operation, 460 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 79681 files and directories currently installed.)
Removing bluealsa (0.13) ...
Removing pulseaudio-module-bluetooth (12.2-4+deb10u1) ...
pi@duet3:~ $ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-utils
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,442 kB of archives.
After this operation, 8,192 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://archive.raspberrypi.org/debian buster/main armhf libpulsedsp armhf 12.2-4+deb10u1+rpi3 [45.1 kB]
Get:2 http://archive.raspberrypi.org/debian buster/main armhf pulseaudio-utils armhf 12.2-4+deb10u1+rpi3 [75.5 kB]
Get:3 http://archive.raspberrypi.org/debian buster/main armhf pulseaudio armhf 12.2-4+deb10u1+rpi3 [1,039 kB]
Get:4 http://archive.raspberrypi.org/debian buster/main armhf libpulse-mainloop-glib0 armhf 12.2-4+deb10u1+rpi3 [37.0 kB]
Get:5 http://archive.raspberrypi.org/debian buster/main armhf libpulse0 armhf 12.2-4+deb10u1+rpi3 [246 kB]
Fetched 1,442 kB in 2s (830 kB/s)
Reading changelogs... Done
(Reading database ... 79657 files and directories currently installed.)
Preparing to unpack .../libpulsedsp_12.2-4+deb10u1+rpi3_armhf.deb ...
Unpacking libpulsedsp:armhf (12.2-4+deb10u1+rpi3) over (12.2-4+deb10u1) ...
Preparing to unpack .../pulseaudio-utils_12.2-4+deb10u1+rpi3_armhf.deb ...
Unpacking pulseaudio-utils (12.2-4+deb10u1+rpi3) over (12.2-4+deb10u1) ...
Preparing to unpack .../pulseaudio_12.2-4+deb10u1+rpi3_armhf.deb ...
Unpacking pulseaudio (12.2-4+deb10u1+rpi3) over (12.2-4+deb10u1) ...
Preparing to unpack .../libpulse-mainloop-glib0_12.2-4+deb10u1+rpi3_armhf.deb ...
Unpacking libpulse-mainloop-glib0:armhf (12.2-4+deb10u1+rpi3) over (12.2-4+deb10u1) ...
Preparing to unpack .../libpulse0_12.2-4+deb10u1+rpi3_armhf.deb ...
Unpacking libpulse0:armhf (12.2-4+deb10u1+rpi3) over (12.2-4+deb10u1) ...
Setting up libpulse0:armhf (12.2-4+deb10u1+rpi3) ...
Setting up libpulsedsp:armhf (12.2-4+deb10u1+rpi3) ...
Setting up libpulse-mainloop-glib0:armhf (12.2-4+deb10u1+rpi3) ...
Setting up pulseaudio-utils (12.2-4+deb10u1+rpi3) ...
Setting up pulseaudio (12.2-4+deb10u1+rpi3) ...
Installing new version of config file /etc/pulse/daemon.conf ...
Installing new version of config file /etc/pulse/default.pa ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
pi@duet3:~ $ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Hit:3 https://pkg.duet3d.com stable InRelease
Fetched 15.0 kB in 3s (5,415 B/s)
Reading package lists... Done
pi@duet3:~ $ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@duet3:~ $

@Phaedrux
Made the suggested changes and I haven't seen any more problems with random pausing.

That includes changing the extruder back to x16 microstepping.

Thanks!

@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.