Multiple issues with Duet Ethernet since 2 weeks
-
I have let the printer switched off a couple of hours
I have upgraded to firmware 2.01 (last stable release) with DWC in order to check if the problem was linked to the firmware.
I've done a new test print with the L.
Dimensions are good.
No sign of under or over extrusion.I got significant pattern on X and Y, like before.
So the issue is not linked to the firmware.
Attached the new M122
0_1544811139548_M122 131218.txt -
I have reprinted the same test print in a row.
I have a good first layer for the skirt and perimeter.
Then the ticking noise from the extruder and over extrusion and then under extrusion.The problem is due to improper retraction at a certain point.
I've stopped the print with severe grinding and the E3D V6 jammed with the filament retracted very high after the heatbreak.
So the extruder is not properly controlled by the driver / board when having used.
It confirms the board is faulty.
I need to replace it.
-
I have well received my new Duet 2 Ethernet.
I have replaced it very easily as it is the same layout.
The old one had some oil on it on the side with the chips.
I don't understand how oil have managed to get on the side which was facing down and no oil at on the other side.
Anyway I will clean the board with isopropyl alcohol.In order to avoid some configuration steps, I took my old USB card and put it in the new board, as it was already with firmware 2.01.
I made a first test print, L shape 10 mm height. Same slicer and parameters.
I got the same issues as weeks ago, when I had the first issues. First layers with a higher layer height than the selected resolutionI've done the test a couple of time with the same issues.
So I switched the usb card with the one supplied with the new Duet board.
I've done the upgrade to firmware 2.02 and copied only the configuration files (config.g, homexxx.g ....).I've done a new test print which was perfect !
All the prints done were good too.
Until today, when I've decided to upload the gcode files from the old usb card to the new one. I've done it using FTP as it's quicker.
The print done just after had the first layers height issue.
So I've removed the gcode files from the usb card and the print were good again.
I have checked the old usb card with fsck, no issues detected.
So the problem is not on the board itself and the culprit is the usb card, more precisely the amount of available disk space.
Is there any memory swap or some temporary system files when running on the usb card, so a minimum available disk space is required ?
That said, cleaning the old board is mandatory, but I believe it would also work.
Thanks for the feedback.
-
What a strange problem! While printing, the firmware writes nothing to the SD card unless you have logging enabled; in which case is will write any error messages to the log, along with a few other messages such as print started and print stopped.
Do you have logging enabled?
Do you have bed compensation enabled; and if so, did you set a taper height?
-
@dc42 said in Multiple issues with Duet Ethernet since 2 weeks:
Do you have logging enabled?
No
Do you have bed compensation enabled; and if so, did you set a taper height?
Yes.
M376 H2 ; Set bed compensation taper -
@v3dprinting said in Multiple issues with Duet Ethernet since 2 weeks:
@dc42 said in Multiple issues with Duet Ethernet since 2 weeks:
Do you have logging enabled?
No
Do you have bed compensation enabled; and if so, did you set a taper height?
Yes.
M376 H2 ; Set bed compensation taperI think the problem is that you are applying a large amount of bed compensation and you have set a small taper height. So:
-
Check that your height map doesn't have a significant offset. It should have close to zero height error (green in DWC) close to the centre of the bed.
-
Use a larger taper height, e.g. 10mm, or no taper at all.
-
-
Thanks Dave
I'll have a look as soon as my printer is free. -
Just an update on that old topic.
I had many issues with that printer, always the same type of steps not being consistent.
I changed many things on the printer :
- PSU (400W 24V TDK) replaced
- Duet 2 Ethernet replaced
- Probe (capacitive sensor) replaced by an IR Sensor
- Opto coupling board for the capacitive sensor removed
- Duet 2 grounded to the casing
- Casing grounded
Stepper motors were checked for each wiring impedance, but not replaced.
It had changed nothing to my issues, after a certain time (couple of days) being switched on, the steppers were not having consistent steps.
Until two weeks ago, were I've discovered that the ground provided by the mains in my building (I'm in a business center) was faulty with a constant 105V - 30 microA AC current....
It has been fixed this week. I hope it was the root cause.
-
@V3DPrinting said in Multiple issues with Duet Ethernet since 2 weeks:
I've discovered that the ground provided by the mains in my building (I'm in a business center) was faulty with a constant 105V - 30 microA AC current....
Curious how you even discovered that.
-
Touching it would tell you pretty quickly.
-
I Have come across this as well in a telecoms environment where the ground for our cabin wasn't tied to the ground of the Mast/Tower causing a rise in Earth Potential and this in turn caused error's induced into a Microwave Data cct looks a long time to diagnose but the fix was simple. Tie the earths/Grounds together.
-
@V3DPrinting said in Multiple issues with Duet Ethernet since 2 weeks:
discovered that the ground provided by the mains in my building (I'm in a business center) was faulty with a constant 105V - 30 microA AC current....
Wow. Thanks for the update. That would be a slippery one to track down.
-
@Phaedrux said in Multiple issues with Duet Ethernet since 2 weeks:
@V3DPrinting said in Multiple issues with Duet Ethernet since 2 weeks:
I've discovered that the ground provided by the mains in my building (I'm in a business center) was faulty with a constant 105V - 30 microA AC current....
Curious how you even discovered that.
I've discovered it touching the casing and the central heating tubes, which are grounded else where.
The current is not strong enough (30 micro Amps) to be detected just touching the casing, because the shoe soles's are not conductive or not enough.