@Phaedrux
Blinking means that I don't get a constant current at the connections for the print head. neither on e01 nor on e02. if i want to heat, the SSR and the LED on the board and also, interestingly enough, the LED lighting flash at regular intervals. icu can rule out the wiring, which sicu hasn't changed in the last year. my system is on 24 volts, the bed heater on 230 volts. I have already replaced the SSR. my next guess is the board, looking for ideas if it can actually be the board before I swap that out.

I've had to overcome a few problems over the years, but here I need some swarm knowledge.

I have the problem that the print head on my Duet2 no longer heats up, but only flashes, flickers or whatever you want to call it. That means I only get a jumping signal on both ports and no longer have a constant voltage. Ergo, the head does not heat either. This goes so far that the LEDs in the printer also flash, as well as the SSR.

My first thought was a defective SSR, so I replaced it, but unfortunately that wasn't the solution either. The second approach was to change the port, but that's not it either. Fuses are all good.

Can anyone give me sound advice on where to start?

A Magnum+ with 2x 50W heater is installed. Has been running flawlessly for 1 year now.

I look forward to hearing from you

@CNCModeller
Hi, you can change the machine Name in config.g with the M550 P“machinename“

This Name ist shown in the Top of the DWC.

@phaedrux
Hello, thank you very much for your help. Soldering the 1K resistor directly in front of the sensor board helped. I have a stable signal. Tested several times, flawless. I also think that the connected shielding also helps.

Thank you again.

@phaedrux
Hello, many thanks for the answer. I'll test that once. can you dare tell me how many watts the resistance must have or is that not important for this purpose?

@phaedrux
Hello,

I'm sending the pictures, I hope that's enough.

I tested a 2nd sensor. Also on another printer with the same result.

With a third printer I get an abort with the message INT1 error.

Verkabelt ist es wie im Bild:

@phaedrux
Hello,

The cable is a USB 3.0 Cable in 1.5 Meter. Also tested with 0.8 Meter. And also testet with unshielded Cable.

The Shield is grounded at GND on the Duet Board an other side GND on the sensor.
——

The Test Prozedure beginn normaly, because stops with the failure an shutown the board.

CSV Files are written with nothing inside an get a parsing failure.

Here is the M122, with no Sensor Connected (the Printer Runs currently)

——-
== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9X6JA-JUNSS-6J1FL-3S46R-K9JMV
Used output buffers: 3 of 26 (15 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 70276 of which 240 recycled
Never used RAM 14512, free system stack 110 words
Tasks: NETWORK(ready,98.9%,211) HEAT(notifyWait,0.2%,326) Move(notifyWait,5.2%,304) MAIN(running,310.6%,450) IDLE(ready,0.1%,30), total 414.9%
Owned mutexes:
=== Platform ===
Last reset 01:40:36 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 17632, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 43.4, current 60.7, max 61.3
Supply voltage: min 23.8, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/22/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0
Driver 1: standstill, SG min n/a
Driver 2: ok, SG min 155
Driver 3: ok, SG min 0
Driver 4: ok, SG min 0
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-09-25 19:21:41
Cache data hit count 4294967295
Slowest loop: 213.08ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.4ms, write time 26.0ms, max retries 0
=== Move ===
DMs created 83, segments created 14, maxWait 1960635ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 14620, completed 14603, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X333.724 Y-244.891 E0.1658" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 208.37ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

Hello,
I have a question about input shaping.

I have an Adafruit LIS3DH sensor, wired and configured directly to my Duet 2. The sensor is also recognized (green light).

However, as soon as I want to take a first measurement (via the plugin or console commands). The measurement process aborts with the message "Measurement aborted" and the board restarts completely.

The cable used is a multiple shielded one, the shielding is also grounded.

Duet Firmware is 3.4.1 // Input Shaping Plugin which is 3.4.1 b1

Does someone have an approach for me how I can solve the problem.

@phaedrux
I have tested the Temperatur with a Long and fast extrusion (1000mm) the tempersture falls down 5-7 degrees.

Can this are the Problem what you mean?

Can you explain me, how i have to configure M309?

@phaedrux
Hello, thanks for the approach. This setup, which I am currently using, is already available from the manufacturer (is currently being presented). This works here with speeds of 200mm/sec.

According to Slice, the hotend with the CHT Nozzel performs significantly better than the Supervolcano (but every manufacturer will say that).

Anyway, thanks for the M309 approach, I'd like to pursue that as I can indeed see a steady fall and rise (minimal but present). All of your tests with the tuning macros today also point to your opinion that it is simply a flow break at the corners. With a reduced M204 P260 (instead of P500)

I was able to print cleanly at 160mm/sec. Which is clear as it slows down to 140mm/sec in the corners. Even with a provoked underetrusion (1mm nozzle, with 0.8mm extrusion runs clean) which also suggests that the flow breaks off at the high rates. What I just don't understand is why doesn't he do that on the long straights where he runs fast and has to encourage a lot.

Why in the corners? Doesn't he manage to heat it up as quickly and as much because of the change of direction?

I looked at the rather short documentation for the M309 and unfortunately I can't figure out what values ​​to set here? Unfortunately, Google doesn't really help here either.

@phaedrux
Hello, I heated the nozzle to 260 degrees, extruded 500mm material, and gradually increased the speed until the extruder skipped. This happens at 47 mm/sec. I determined this using a formula. If I have an error, feel free to correct me.

I have a layer height of 0.4mm. The problem occurs at 0.3 as well, just not as severe.

Can you give me a starting point to find the problem. 130mm/sec shouldn't be too fast, because I can also print this speed with the Supervolcano with a 1.2mm nozzle and 0.4 layer height. I can't imagine the Magnum+ being weaker than the Supervolcano.

I discovered your tuning macros and would like to test them further, but I don't currently know what the problem is. (Acc, Jerk, XY or E) ?

@phaedrux

Hello and thank you for the answer. I have attached the files here.
I did some more testing yesterday. I have changed the Printer (same Model) for check. In advance I determined the maximum feed rate and thus the possible volume. E-Steps calibrated fine with 408 steps.

This is at 260 degrees at 111mm3. So the point should be closed.

Single-walled prints brought the result as shown in the picture. 1x pressure test at 130mm/s with 1.0mm extrusion width and 1x pressure test at 130mm/s with 1.2mm extrusion width. The test starts at 100mm/sec and gradually increases to 130mm/sec.

The Wall thickness was nice, 1.05-1.01 / at test 2 1.22 - 1.24mm. The Flow should be correct. Temperature changes didn't help to solve.

I have also done various tests with other values ​​in the M566, but very ignorantly and unsuccessfully. The Body I test ist a Quader with 200x200 / 400x400 / 500x500mm.

Slicer Ideamker as well as S3D are identical results.

I have only changed the Supervolcano in an Bowdensetup against:
• Bondtech LGX ACE with Magnum+
• 2 Heater at 50W (parallel wired), with CHT 1.0 Highflow-Nozzle. Std. Thermistior

I used different Filaments of ASA Formfutura, same Material worked on my other machines fine. The result of my test are the more material is used, the worse the problem become.

M122.txt
M98.txt
config.g

Last Testprint file: Test_200x200_V7.gcode

I have the following setup: Duet2 Board, Magnum+ Hotend with LGX Etruder.

So far everything is going great.

My problem is that I occasionally get sawtooth on straight lines and I have already tried with feedrate etc. I can't get any further here because the approach is missing. The more flow I give, the bigger the problem becomes.

The Printer is Delta with a full-metal Chassis an Carbon arms. The problem is also seen at slow speed 100 mm/sec.

I print the following:
ASA, 170mm/sec, 260 degrees with 1mm CHT Nozzle. Extrusion width 1.20mm

Bevor i change to Magnum+ with LGX directdricre, i have printed with a Bowden with a Supervolcano, without problems 140mm/sec. So I think the problem can found in the Config.
Bowden > Directdrive with Magnum+.

I have attached my current config and a picture of the problem.

Maybe someone can give me a direction.

@o_lampe
Thanks for answer

The problem was simple solved. I have conncted parallel an the fuse are damaged.

The Problem was, that the fuse nit fit exactly in the mount, this was the only fu**ing problem

@engrsky

Ich i have the same config, and i have a question.

I have connected the left wires of the heaters together an the right wires together an connected this on the cables of the original heater (E0)

My problem is, that the fusion damaged at Board Start.

—-
If i wiring the heaters in row, it runs without fusion damage, because to low power.
—

Can you give me a tip, wich mistake i have ?

Thanks a lot

@engikeneer
Thanks for the top tip i will Test it an Reply

@phaedrux
Hello, I will start with a G32 right before doing a mesh bed calibration. The card is loaded with G29 S1.

At the start of printing I start with a G28 followed by a G30 for the Z date = 0 directly before the start of printing.

A height map is attached. The height differences of the map are visible in the first level, so I assume that the map is active, but no height compensation takes place. But I don't know how to check it btw.

bed.g

I have the following problem. I would like to work with the mesh bed compensation (device: Delta with sensor that is placed under the print head). I start it with the following macro:
M561
G28
G1 Z25 F8000; to mount the sensor
G30
M557 R400 S40
G29
G29 S1
G1 Z200 F8000; to remove the sensor

• print -

---

But now it is so that obviously no compensation is carried out. I always have uneven spots in the first layer. In the M122 dialog, the following is under Move:
=== Move ===
Hiccups: 0 (0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: mesh, comp offset 0.000

Shouldn't there be a value under comp offset?