Hello, I have now found out that I have to adjust my Config.g etc. etc. significantly. Because without adjustments when updating from 3.4.0 to 3.5.4 the print head moves in the bed and the heights probably don't match the firmware.
Because I don't know what I have to adjust (I tried), the topic can be closed and I will stay on 3.4.0 and live with the not so optimal or non-functioning mesh bed compensation during printing.
Many thanks to everyone who wanted to help me 
@dc42 Hello,
the plugin has started.
@Phaedrux
Under 3.4.0 it is not possible to compensate for these height differences with the mesh bed compensation or it is useless. Open perimeters and sometimes too deep areas without compensation. So I hope that the update will bring a significant improvement. I print on 15mm GAL cast pure aluminum, so I cannot manually correct anything on the print bed.
Altes Druckbett:
@MichaelKallner my config.g
#4;Magnum+ Config
M111 S0 ;Debug Modus S0=aus
M550 PTractus3D #4 -T2300 ;Maschinenname (DNS Name)
M98 P"_UserSettings.g" ;Macro laden
M552 S1 ;Netzwerk starten
M555 P1 ;Emulationstyp 1= Reprap
G21 ;Einheiten auf mm
G90 ;Koordinaten auf absolut relativ gesetzt
M83 ;Extruder auf auf relativ gesetzt
M400 ;Alles beenden, Puffer löschen
M569 P0 S0 ;E0 ; Laufrichtung Stepper (0=rückwärts 1=vorwärts)
M569 P1 S1 ;E1 ; Laufrichtung Stepper (0=rückwärts 1=vorwärts)
M569 P4 S0 ;Y ; Laufrichtung Stepper (0=rückwärts 1=vorwärts)
M569 P2 S0 ;X ; Laufrichtung Stepper (0=rückwärts 1=vorwärts)
M569 P3 S0 ;Z ; Laufrichtung Stepper (0=rückwärts 1=vorwärts)
M575 P1 B115200 S0 ; Paneldue P=Seriennummer, B=Baudrate, S0= ohne Prüfsumme
M584 X2 Y4 Z3 E0 ; Laufwerksnummer Stepper
M92 X80 Y80 Z80 ; E-Steps XYZ
M906 X1700 Y1700 Z1700 E700 I40 ; Motorstrom in mA (I=Leerlaufstrom)
M201 X1000 Y1000 Z1000 E6000 ; Maximalbeschleunigung mm/sec
M204 P400 T1000 ; Druckbeschleunigung (P=Druck + T=Travel)
M203 X18000 Y18000 Z18000 E18000 ; Maximaler Vorschub mm/min
M566 X300 Y300 Z300 E600 P1 ; Max Geschwindigkeitsänderung (Ruckgeschwindigkeit)
M665 R494.50 L1063 B500 H879 X0 Y0 Z0 ; Delta Konfig: R=Radius:2 // L=Armlänge // B=Druckradius:2 // H= Düsenhöhe über Bett im Homeing
M666 X0 Y0 Z0 A0 B0 ; Achsen Endstop Korrektur (Position Endstop)
M574 X2 S1 P"xstop" ; Endstopkonfig: X2=Highend S1=aktiver High-End-Stop-Eingang P=Pin
M574 Y2 S1 P"ystop" ; Endstopkonfig: X2=Highend S1=aktiver High-End-Stop-Eingang P=Pin
M574 Z2 S1 P"zstop" ; Endstopkonfig: X2=Highend S1=aktiver High-End-Stop-Eingang P=Pin
M308 S0 A"Bed" Y"thermistor" P"bedtemp" T100000 B4400 R4700 ; Thermistor Druckbett
M308 S1 A"Magnum +" P"e0temp" Y"thermistor" T100000 B4680 C6.455513e-8 ; Thermistor Hotend
M950 H0 C"bedheat" T0 ; Heizung Pinvergabe
if sensors.analog[1].lastReading<0
M575 P1 B57600 S1 ; Paneldue P=Seriennummer, B=Baudrate, S1= mit Prüfsumme
G4 P200 ; Maschinenstillstand für P200 Millisekunden
M291 P{"Please check your print head / connection! Try again?"} R"No print head detected!" S3 ; Nachricht anzeigen
M999 ; Neustart
M92 E408 ; E-Steps Extruder
M308 S6 A"MCU" Y"mcu-temp" ; Sensor 6 MCU Temp
M575 P1 B115200 S0 ; Paneldue P=Seriennummer, B=Baudrate, S0= ohne Prüfsumme
M950 P0 C"exp.heater3" ; Heizung Pinvergabe
M950 H1 C"e1_heat" T1 ; Heizung Pinvergabe
M950 F1 C"fan0" ; Lüfter Pinvergabe
M950 F0 C"fan1" ; Lüfter Pinvergabe
M950 F2 C"fan2" ; Lüfter Pinvergabe
M950 J1 C"!e1stop" ; Einganspin Pinvergabe estop1
M950 J2 C"exp.e2stop" ; Einganspin Pinvergabe estop2
M106 P1 S0 H-1 C"Part cooling" ; P=Lüfter T=Temperatur H=Aktivieren Thermostat S=255 Drehzahl
;M106 P1 T50 H1 S255 ; P=Lüfter T=Temperatur H=Aktivieren Thermostat S=255 Drehzahl
;M106 P2 T40:60 H6 L0.50 X1.0 ; P=Lüfter T=Temperatur H=Aktivieren Thermostat S=255 Drehzahl
M570 H0 P2000 T20 ; Heizung Fehlererkennung H=Heizung P=Zeit in Sekunden des Fehlers T=Erlaubte Abweichung in Grad
M570 H1 P15 T20 ; Heizung Fehlererkennung H=Heizung P=Zeit in Sekunden des Fehlers T=Erlaubte Abweichung C
M563 P0 D0 H1 F0 S"Hotend 1" ; Definition Werkzeug /Druckopf
G10 P0 S0 R0 ; Setze Werte Druckkopf S=Aktive R=Standby
M140 H0 ; Bettemperatur einstellen
M307 H0 R0.500 K0.170:0.000 D13.78 E1.35 S1.00 B1
; M307 H0 R0.500 K0.566:0.000 D20.56 E1.35 S1.00 B1 ;PID Einstellungen Druckbett
M307 H1 R2.003 K0.197:0.000 D8.22 E1.35 S1.00 B0 V24.0 ;PID Einstellungen Druckkopf
M558 P5 C"e0stop" X0 Y0 Z0 F100 T10000 ; Z-Sonde P=Typ C=Contakt XYZ=Auslösehöhe F=Vorschub Z mm/min T=Travel zwischen den Punkten
G31 X0 Y0 Z18.48 P500 ; XY= Sondenoffset // Z=Z-Triggerhöhe. // P=Triggerwert
M557 R400 S40 ; Sondierungsraster R=Radius/2 // S=Abstand
M208 S1 Z-2.5 ; Achsbegrenzung
M911 S20.5 R22.0 P"G91 M83 G1 Z3 E-3 F3000 M929 S0" ; Druckabbruch bei Unterspannung
M579 X0.9952 Y0.9983 ; Skalierung der Achsen (Bei Abweichungen der Form)
M912 P6 S1 ; Ãœberwachung der Elektronik Temperatur (MCU)
M143 H0 P0 S110 A2 ; Maximaltemperatur mit Abschaltschwelle
M143 H0 P1 S130 A0 ; Maximaltemperatur mit Abschaltschwelle
M143 H1 P0 S300 A2 ; Maximaltemperatur mit Abschaltschwelle
M143 H1 P1 S320 A0 ; Maximaltemperatur mit Abschaltschwelle
M42 P0 S255 ; IO Pin P=Pin nummer S=Wert
M42 P1 S255 ; IO Pin P=Pin nummer S=Wert
M581 P1 T2 S0 R1 ; Externen Pin Schalten
M23 "0:/sys/config-override.g" ; Macro "...laden"
if result == 0 ; wenn erfolgreich dann...
M501 ; lade
else ; sonst...
M575 P1 B57600 S0 ;
M400 ;
M98 P"stpwzd.g" ;
M29 ;
M23 "0:/sys/firstuse.g" ; Macro "...laden"
if result == 0 ; wenn erfolgreich dann...
M23 "0:/sys/bed.g" ; lade
M575 P1 B57600 S0 ;
M400 ;
M98 P"stpwzd.g" ;
M400 ;
M575 P1 B57600 S1 ; Paneldue P=Seriennummer, B=Baudrate, S1= mit Prüfsumme
M929 P"0:/sys/printerlog2.txt" S1 ; Printerlog S1= ein // S0= aus
G28 ; Homeing
M309 P0 S0.00 ; Feedvorward Heizung
;M955 P0 C"spi.cs4+spi.cs3" ; Accelerometer
;M593 P"mzv" F20.5
I'm not at the printer today. I'll try it tomorrow. Shouldn't the G29 S4 command output something and what does the new plugin look like? I only know the old height map from 3.4.0 (top left in the navigation). Or does the new plugin and the G29 S4 command only work when a new map has been created?
.
I did the update in the hope that the bed compensation for large beds (1m diameter) works better than in version 3.4.0
Today I did a FW and DWC update on my Duet2 from 3.4.0 to 3.5.4. The height map module is now set up as an extra plugin. The updates have been installed properly, but my saved map is not displayed, the G29 S4 command also ends in a "not supported" command and I can't see any visual changes. What's wrong here? Can someone help me? I only did the updates, no changes to the config or anything like that. I tested different browsers and deleted caches.
@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) ?
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.
