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