... to all the Duet 3D programmers. I just updated the Duet and the PanelDue to 3.4.0 - and especially the latter part shows how far you have come with simplifying the task: upload, right-click, choose "install" and that's it.
This is light years away from the old process with Bossa. Congratulations for making this so effortless!
@Phaedrux:
Thanks again - it works perfectly. I removed the second step however - this is handled by the gcode of the print itself:
M307 xxxxx ; PID values for quick heating
G10 P0 S180 ; set temp of tool to 180°C
M116 ; wait for temp
M307 yyyyy ; PID values for stable temps during print
; final temp is supplied by part gcode
@dc42:
sure, I played a lot with autotune but for some reason did not get any satisfying results with the Duet that combined a quick heat-up and a stable print temperature. I do not remember though if I changed D that much - I will try that.
Interestingly, the autotune of the old Printrboard had yielded a better result, which is why I fell back to setting the PID values with M301 for a while and simply used what the Printrboard autotune had told me on the Duet as well, but I had to resort to setting an M307 setting to define a maximum PWM since the duet does not seem to provide another way to set this - and then overwrite this setting partly with M301. (On the Printrboard I could define the max. PID drive in the firmware eeprom.)
This did not work perfectly though (unsure why - maybe due to different response times of Duet vs. Printrboard?). But for now and with Phaedrux' trick I finally have a setting I feel comfortable with.
By the way - thanks a lot for including the german translation I had sent you into the PanelDue firmware 
Just in case anyone is interested, here is the working solution:
; XY calibration in a cavity that is normally covered by the print plate
; Variables
; print plate thickness in variable "global.Druckplattendicke" needs to be defined before running the macro, e.g. in config.g
var Eintauchtiefe = 1 ; how deep the nozzle shall dive into the cavity
var Referenzwert_X = 0
var Referenzwert_Y = 0
var Hotend2_X = 0
var Hotend2_Y = 0
G28 ; Home
; prepare printer - insert whatever you need here...
; heat up hotends and bed
M140 S60 ; heat up bed
T0 P0
M568 P0 S220 R220 ; heat up Hotend 1
T1 P0
M568 P1 S220 R220 ; heat up Hotend 2 auf 220°C
T-1 P0
M116 ; wait
; let the user clean the nozzles
G1 H2 X{move.axes[0].min+50} F3000
G1 H2 U{move.axes[3].max-50} F3000
M400 ; wait
; Message
M291 "Please clean the nozzles" R"Notice" S3
; Move print heads back to their parking position
G1 H2 X{move.axes[0].min} F3000
G1 H2 U{move.axes[3].max} F3000
; lift bed close to measuring level
G1 H2 Z5 F6000
; move hotend 1 to cavity and dive in
G1 H2 X0 Y0 F6000
M400
G1 H2 Z{-global.Druckplattendicke - var.Eintauchtiefe} F3000
; begin reference measurement
T0 P0 ; activate tool 0
while iterations < 8 ; measure 8 times in X
M675 X R1 P0 F100
M400
set var.Referenzwert_X = var.Referenzwert_X + move.axes[0].machinePosition ; save value
set var.Referenzwert_X = var.Referenzwert_X / 8 ; calculate final reference value
while iterations < 8 ; measure 8 times in Y
M675 Y R1 P0 F100
M400
set var.Referenzwert_Y = var.Referenzwert_Y + move.axes[1].machinePosition save value
set var.Referenzwert_Y = var.Referenzwert_Y / 8 ; calculate final reference value
; move back hotend 1
G1 H2 Z2 F6000
M400
G1 H2 X{move.axes[0].min} F6000
; delete old offset from hotend 2:
G10 P1 U0 Y0
; move hotend 1 to cavity and dive in
G1 H2 U0 Y0 F6000
M400
G1 H2 Z{-global.Druckplattendicke - var.Eintauchtiefe} F3000
; measure with hotend 2
T1 P0 ; activate tool 1
while iterations < 8 ; measure 8 times in U
M675 U R1 P1 F100
M400
set var.Hotend2_X = var.Hotend2_X + move.axes[3].machinePosition ; save data
set var.Hotend2_X = var.Hotend2_X / 8 ; ... and calculate final value
while iterations < 8 ; measure 8 times in Y
M675 Y R1 P1 F100
M400
set var.Hotend2_Y = var.Hotend2_Y + move.axes[1].machinePosition ; save data
set var.Hotend2_Y = var.Hotend2_Y / 8 ; ... and calculate final value
; define new offset and save it to a file that is read from config.g:
G10 P1 U{var.Referenzwert_X - var.Hotend2_X} Y{var.Referenzwert_Y - var.Hotend2_Y}
echo >"Korrekturwert_xy_offset_tool1.g" "G10 P1 U"^{var.Referenzwert_X - var.Hotend2_X}^" Y"^{var.Referenzwert_Y - var.Hotend2_Y}^""
; bring printer back to idle state
T0 P0
G1 H2 Z5 F6000
G1 H2 U{move.axes[3].max} Y{move.axes[1].min} F3000
G1 Z120 F6000
M568 P0 S0 R0
M568 P1 S0 R0
M140 S0
; notify user
M291 S2 P"XY-Offset of right Hotend is has been saved!"
(edit: added remark, removed unused variables)
@oliof said in IDEX XY calibration by electrical nozzle contact:
@NeoDue great stuff! You should consider some way to filter out outliers in your 8 runs (use median or just track lowest/highest and reject runs where the difference is greater than some value you deem an acceptable range).
@oliof Now I finally had the time to dust off and actually use a bit of my old statistics knowledge... Got it - here is a test macro that removes outliers from a given array based on their z-score:
; constraints out of experience:
; - electrical nozzle contact never gets activated too soon (=> too low values will never happen and are not taken into account here)
; if that does not apply, a lower acceptance limit for the z-score needs to be defined as well
; - values that are too high are usually at least 0.15...0.2mm off
var Referenzwert = {1,1.02,1.05,1.2,1.22,1.3,1.01,} ; test values - the three values that are too high need to be detected and removed from the mean value
var Referenzmittelwert = 0.0
var Referenzstandardabw = 0.0
var ReferenzZScore = vector(#var.Referenzwert,null)
var ZScoregrenze = 0.5
var Anzahlgueltig = 0
; calculate mean value
while iterations < #var.Referenzwert
set var.Referenzmittelwert = var.Referenzmittelwert + var.Referenzwert[iterations]
set var.Referenzmittelwert = var.Referenzmittelwert / #var.Referenzwert
; calculate standard deviation
while iterations < #var.Referenzwert
set var.Referenzstandardabw = var.Referenzstandardabw + (var.Referenzwert[iterations] - var.Referenzmittelwert) * (var.Referenzwert[iterations] - var.Referenzmittelwert)
set var.Referenzstandardabw = sqrt(var.Referenzstandardabw / (#var.Referenzwert - 1))
; calculate z-score of each measurement value
while iterations < #var.Referenzwert
set var.ReferenzZScore[iterations] = (var.Referenzwert[iterations] - var.Referenzmittelwert) / var.Referenzstandardabw
; re-calculate mean value without detected outliers
set var.Referenzmittelwert = 0
while iterations < #var.Referenzwert
if var.ReferenzZScore[iterations] < var.ZScoregrenze
set var.Referenzmittelwert = var.Referenzmittelwert + var.Referenzwert[iterations]
set var.Anzahlgueltig = var.Anzahlgueltig + 1
set var.Referenzmittelwert = var.Referenzmittelwert / var.Anzahlgueltig
echo var.Referenzmittelwert
While I do not use that for XY calibration (at least yet - that one works perfectly well as it is so far...), I did add it to the two macros I wrote for z calibration and z-leveling of the U axis relative to the X axis. It definitely makes sense there since slight drops of filament coming out of the nozzle can cause errors.
Just in case somebody stumbles over this thread and has the same problem:
In the meantime I got the second amplifier and included it in my bed sensors.
Dividing the three piezo bed sensors on two different amplifiers - both (digital) outputs being connected in parallel to the input of the Duet - worked perfectly for me. All problems I had with the bed sensors are gone and contact sensing works great even with the slow z axis of my printer.
Thus, I can recommend this method whenever there is a crosstalk problem with piezo sensors.
@droftarts Thanks!
A suggestion though, if I may: In order to keep others from running in the wrong direction, I would like to suggest to clarify the M950 documentation a little by changing the text for the "E" parameter from "LED strip number" to "DotStar/Neopixel LED strip number (for standard LEDs or LED strips use the "P" parameter together with M42)"
Same here: I upgraded my Duet Wifi (v1.02) from 3.2.0 (my first v3 firmware) to 3.2.2 and the printer got stuck and required additional help to get WiFi running again. I had used the new update procedure for the PanelDue (5" v3.0) just before that, just to mention that in case it helps. SD card seems fine though, if I can trust Windows...
@dc42 While searching on how to do this, I found your wiki help section "Installing and Updating Firmware" seems a bit outdated. It is still talking about iape4e/iap4s.bin being needed. Thankfully the M997 command complained about the missing Duet2_SDiap... file instead of showing me obscure error codes as some other systems might do.
(thanks @T3P3Tony for getting my account running again btw, the Akismet spam tool drove me nuts... now I can at least post something again even if it still bugs me now and then...)
Hello together,
ever since I finally threw out the old Printrboard on my GRR Neo and replaced it with a Duet Wifi (which I should have done much sooner btw...), I have been fussing around with two things:
By now it seems I have finally solved both problems - the motor issue thanks to several hints here and thanks to the new firmware (in case someone needs it - "M569 ... T1:1:0.5:6 C65974" yields the best results so far), and the hotend oscillation after dozens of unsuccessful attempts by rather severely decreasing the max PWM value by using the M307 S... parameter, and this brings me to my question:
By reducing the max. PWM to 0.25, I managed to reduce the temperature swing from ±3...4°C (which was the best I could get out of both automatic as well as manual tweaking PID parameters) to ±0,7...1°C.
The drawback is that it takes now some 8...10 minutes for the Neo to heat up.
So here is my question: is it somehow possible to configure the Duet in such a way that you e.g. use a max. PWM of 0.5 for up to 180°C and then go on with a PWM of 0.25?
(I am aware that I somewhat contradict the idea behind the PID management of the hotend with this question, but as mentioned above I miserably failed getting it to work like that - regardless what I do, PID always either fires too hard when it recognizes a temperature drop or it reacts too slow when temperature is reached)
Best regards
Florian
@arhi I had already posted the setup I used
You can see it here: https://forum.duet3d.com/topic/14477/piezo-board-with-4-sensors/29
The bed screw holes of the original bed support (a shaped sheet metal plate) were drilled open to let the bed springs through, and I added additional screw holes to hold the added aluminium profiles in place and stiffen the original bed support.
The basic "mount" for each sensor is a more or less L-shaped aluminium profile I had lying around (a rest of the cable channel for our TV). You can replace it with any aluminium L profile that has at least the following dimensions: material thickness 1,2mm, long "leg" of L profile 24mm, short "leg" of L profile 8mm.
I cut fitting holes into the material as needed (two screws for the Andromeda, one larger for the bed spring, another screw hole for screwing the whole thing onto the original part and making the assembly stiffer than it was before and two M2 threaded holes for some sensor covers I printed from PETG) and used clinch nuts to get stable threads for mounting the Andromeda sensors. Since I mounted these aluminium plates on top of the original sheet metal bed support so save some millimeters (as noted in the other thread, there is not much available space in my printer), I used DIN 988 adjusting washers to even out the heights when I screwed on the sensors.
In order to catch the tolerances, I mounted everything loosely first, then added the bed and only then tightened all screws with a little bit of Loctite (be careful not to let that stuff get onto the epoxy material of the PCB, in some cases this causes trouble some years later).
That's it, basically... sadly nothing another user could use 1:1 I am afraid - but It's a concept. If I can help you (or anyone else) with details please feel free to ask or send me a message
@dc42 The first start today did not take four minutes but ten.
I tried switching back to the new firmware but that did not change anything. Then I tried resetting the module by deleting the saved networks and then handling as if it was new (flash firmware once again, start module, add network etc) - but this time I waited 10min, rebooted and waited 10min more between each step to let the module finish whatever it liked whenever it liked. That did not help in the least. Again, the first start was great, but any boot with the module active took ages.
After several more fruitless attempts some gut feeling made me change the config.g to this:
; Enable network except WLAN module
M550 P"Duplimatix" ; Machine name
M552 I0 S1 ; Ethernet active
M586 P0 S1 ; HTTP server active
M586 P1 S0 ; FTP off
M586 P2 S0 ; Telnet off
; Enable PanelDue
M575 P1 S1 B115200
; Enable WLAN module
G4 P5000 ; wait a bit...
M552 I1 S1 ; WLAN module active
... and suddenly the module started like a charm! 
Doublechecking by switching back to the previous config.g order confirmed this.
This means it is some kind of timing or startup order issue. From what I can see maybe the PanelDue start command causes the hiccup if executed while the module is still initialising, or the module might be started too early to be recognised correctly by the CPU which then triggers the formatting procedure you mentioned or such...?
Edit: it's definitely those five seconds that make the difference. As soon as you delete that line the module starts in slow motion.
What I do get though with the new firmware is a weird WiFi Server information in DWC:
2nd Edit - offtopic, just in case someone else wants to do this as well: keep the WiFi antenna away from the PanelDue. I intended to put it into or onto the same housing, in a horizontal position below/above oder behind the PanelDue, but that turned out to be a really bad idea in terms of connection stability.
Just in case someone else follows this: I just saw a new Wifi module firmware (2.1beta6) has been released that addresses some Wifi connection issues if I understand the release notes correctly. I am currently giving it a try and will report what happens here.
Hm. Reading through all this what your effort yielded, I wonder if whatever @dc42 might find here could also affect the (much smaller) issues I have on my Duet 3 6HC with wifi module
I blamed the latter two on the web server and the firmware being beta in general - but who knows...?
@Exerqtor out of curiosity since you did not mention it (I have to admit I did not read through that huge other thread): The fact that - if I understand you correctly - you say the Mini worked first but started to show issues after a while makes me wonder a bit.
Therefore, just to have asked and based on my rusty electronics knowledge - did you check the following two things:
@Jimborr Ah, yes, that seems to be something else that affects Delta printers.
@janjoh @Jimborr @PCR thanks, that is reassuring that I am not the only one with that issue.
I wonder if we could do something to support the devs here to narrow down that issue. Could you each post your config.g that ran when you had that issue and the gcode of the part layer where layer shifting occurred and of some layers below that? I will try to dig through that and see if I see any similarities.
What I expect to find would be an increase of motion steps per length, motor steps or time, since that was a very obvious difference in my case. Layers with a relatively low amount of acelerations and decelerations per length unit printed fine, but as soon as a layer with many of those was printed (in my case probably caused by Prusaslicer varying the extrusion width since I did not really care about the nozzle width when desingning my part), I observed layer shifts when input shaping was active.
I do not know if this might yield a result that actually helps since we would need a dev here telling us what to do, but it is at least a try.
@oliof said in IDEX XY calibration by electrical nozzle contact:
@NeoDue great stuff! You should consider some way to filter out outliers in your 8 runs (use median or just track lowest/highest and reject runs where the difference is greater than some value you deem an acceptable range).
@oliof Now I finally had the time to dust off and actually use a bit of my old statistics knowledge... Got it - here is a test macro that removes outliers from a given array based on their z-score:
; constraints out of experience:
; - electrical nozzle contact never gets activated too soon (=> too low values will never happen and are not taken into account here)
; if that does not apply, a lower acceptance limit for the z-score needs to be defined as well
; - values that are too high are usually at least 0.15...0.2mm off
var Referenzwert = {1,1.02,1.05,1.2,1.22,1.3,1.01,} ; test values - the three values that are too high need to be detected and removed from the mean value
var Referenzmittelwert = 0.0
var Referenzstandardabw = 0.0
var ReferenzZScore = vector(#var.Referenzwert,null)
var ZScoregrenze = 0.5
var Anzahlgueltig = 0
; calculate mean value
while iterations < #var.Referenzwert
set var.Referenzmittelwert = var.Referenzmittelwert + var.Referenzwert[iterations]
set var.Referenzmittelwert = var.Referenzmittelwert / #var.Referenzwert
; calculate standard deviation
while iterations < #var.Referenzwert
set var.Referenzstandardabw = var.Referenzstandardabw + (var.Referenzwert[iterations] - var.Referenzmittelwert) * (var.Referenzwert[iterations] - var.Referenzmittelwert)
set var.Referenzstandardabw = sqrt(var.Referenzstandardabw / (#var.Referenzwert - 1))
; calculate z-score of each measurement value
while iterations < #var.Referenzwert
set var.ReferenzZScore[iterations] = (var.Referenzwert[iterations] - var.Referenzmittelwert) / var.Referenzstandardabw
; re-calculate mean value without detected outliers
set var.Referenzmittelwert = 0
while iterations < #var.Referenzwert
if var.ReferenzZScore[iterations] < var.ZScoregrenze
set var.Referenzmittelwert = var.Referenzmittelwert + var.Referenzwert[iterations]
set var.Anzahlgueltig = var.Anzahlgueltig + 1
set var.Referenzmittelwert = var.Referenzmittelwert / var.Anzahlgueltig
echo var.Referenzmittelwert
While I do not use that for XY calibration (at least yet - that one works perfectly well as it is so far...), I did add it to the two macros I wrote for z calibration and z-leveling of the U axis relative to the X axis. It definitely makes sense there since slight drops of filament coming out of the nozzle can cause errors.
@oliof thanks for the explanation!
@oliof No, I do not use mesh bed leveling.
The j1 has just three measurement points for z - each one above a bed adjustment screw - that are only used with a calibration macro I wrote for the Duet: at the first point the macro redefines the upper limit of the z axis by sending an M208 command, then the printer moves on to the next point and measures every second or so while telling the user to twist the knob left or right (ASCII Art rules 
) until the bed is level. That will be repeated on the last point - simple assisted bed leveling which is does its job by far well enough with the (coated) glass plate the J1 has.
Since that recalibration macro has to be started by the user and its only lasting effect is the M208 command saved in a separate file that is called by config.g during boot, I do not expect that to have any influence.
But if mesh bed leveling also may cause this, I am am quite tempted to see this as another indicator for some internal communications timing issue - at least I assume mesh bed leveling to be rather calculation intensive as well, just as Input shaping...?
Just for the sake of completeness (the other two issues I posted here are more pressing to me) - I have those reboots as well, running 3.5.0rc1 on a Duet 3 6HC with a Duet 3 wifi module on the latest firmware. In addition to that, I sometimes see connection losses of both the webinterface and the PanelDue that can only be cured by a reset.
Thankfully they did not happen during a print as of now, but rather when the printer has been sitting idle for an extended period of time. That might be caused by the fact that it usually takes the printer about 10+ hours to reset as far as I have noticed by now - all prints I did so far were well finished by then.
When this happens again, I will add an M122 printout here. So far,, the only thing I noticed on previous cases was the recurring note "gcodes spinning" as reset reason in all those cases.
Okay, this is weird: I tried to print this attached gcode file for the last days and kept having "bang" noises and layer shifts on the y axis starting at around 5.5...6mm height:
batteriebox_2x_18650_ut_0.15_T1PLA+T2PLA.gcode.zip.gcode (remark: due to the restrictions in the forum, I zipped the gcode file and had to add a ".gcode" again to the name in order to be able to upload it)
These bangs happened at places where no obstructions could be seen - in somewhere around the middle of a straight line for example.
Since I am running my printer with StealthChop, I first suspected (despite using 1.8° steppers) something like the thing here in the thread https://forum.duet3d.com/topic/22436/missing-steps-cant-print-spreadcycle-stealthchop-tuning-help/ that @dc42 and @droftarts managed to sort out, herefore I followed what was done there:
Due to the thread about input shaping causing stutters and blobs here, I disabled input shaping - and bingo, the printer worked as it should.
Since the code above contains an awful lot of accelerations and decelerations in the area where the layer shifts happened due to... well, whatever Prusaslicer did there..., I suspect there might be some uncaught internal communications delay causing this...?
Here is my config.g (please ask if I should translate something):
; config.g
G4 P2000 ; 2s warten, daß die Duet in Ruhe starten kann - hilft etwas bei einem Reset
; Allgemeine Einstellungen
;
M451 ; FDM-Drucker
M669 K0 S50 ; Kartesischer Drucker, 20ms Mindest-Segmentzeit von Marlin-Sourcen des J1 übernommen
M111 S0 ; Debugging aus
G21 ; Basiseinheit Millimeter
G90 ; Absolute Koordinaten...
M83 ; ... außer beim Extruder
M555 P1 ; Firmware-Kompatibilität wie RepRapFirmware
M200 D1.75
; globale Variablen
;
if !exists(global.Druckplattendicke)
global Druckplattendicke = 5.00 ; Dicke der Druckplatte
if !exists(global.Z_Limit_min)
global Z_Limit_min = 200 ; kleinster zulässiger Max-Wert für Z
if !exists(global.Z_Limit_max)
global Z_Limit_max = 216 ; größter zulässiger Max-Wert für Z
; PanelDue
;
;M575 P1 S1 B115200 ; IO-Port für PanelDue aktivieren
M575 P1 S1 B57600 ; testweise auf 57600 Baud reduziert
; Definition der Sensoren - 2x PT100 mit Vorverstärker am Hotend, 1x 100K-NTC am Bett
;
M308 S0 P"temp0" Y"thermistor" A"T_Heizbett" T100000 B4092 ; Sensor 0 = Heizbett-Temperatursensor
; Hotend-Temperatursensoren:
; die Vorverstärker im Hotend arbeiten nur im Bereich von 120...310°C linear. Daher weichen die Anzeigewerte insbesondere bei Raumtemperatur ca. 10...15° nach unten ab.
M308 S1 P"temp1" Y"linear-analog" A"T_Hotend1" F1 B-116.551 C554.644 ; Sensor 1 = PT100 mit Vorverstärker am Hotend 1 (links). GND und 3,3V kommen vom Filamentsensor, Signal an Pin Temp1 legen!
M308 S2 P"temp2" Y"linear-analog" A"T_Hotend2" F1 B-116.551 C554.644 ; Sensor 2 = PT100 mit Vorverstärker am Hotend 1 (links). GND und 3,3V kommen vom Filamentsensor, Signal an Pin Temp2 legen!
; M308 S3 P"temp3" Y"thermistor" A"Bauraum" T100000 B4092 ; reserviert für Sensor 3 = Sensor für Bauraumheizung
M308 S10 Y"mcu-temp" A"Elektronik" ; Sensor 10 = Prozessortemperatur der Duet für Elektronikraumkühlung - die Stepper haben nur einen dreistufigen Temperatursensor
M308 S11 Y"drivers" A"Steppertreiber" ; Sensor 11 = Steppertreibertemperatur der Duet. 0°C=normal, 100°C=Überhitzungswarnung, 130°C=überhitzt.
; Definition der Anschlüsse
;
M950 H0 C"out0" T0 ; Heizelement 0 (Heizbett mit Temperatursensor 0)
M950 H1 C"out1" T1 ; Heizelement 1 (Extruder-Heizung mit Temperatursensor 1)
M950 H2 C"out2" T2 ; Heizelement 2 (Extruder-Heizung mit Temperatursensor 2)
; H3 (out3) freihalten für Bauraumheizung
M950 F0 C"out4" Q50 ; Lüfter 1 (Bauteilkühlung Hotend 1) PWM-Frequenz 50 Hz (sonst schwankt die Drehzhl)
M950 F1 C"out5" Q50 ; Lüfter 2 (Bauteilkühlung Hotend 2) PWM-Frequenz 50 Hz (sonst schwankt die Drehzahl)
M950 F2 C"out7" Q500 ; Lüfter 3 (Hotendkühlung Hotend 1)
M950 F3 C"out8" Q500 ; Lüfter 4 (Hotendkühlung Hotend 2)
M950 F4 C"out6" Q50 ; Lüfter 5 (Elektronikraumlüfter) PWM-Frequenz 50 Hz (sonst schwankt die Drehzahl)
M950 P9 C"out9" Q100 ; LED-Streifen an Ausgang 9
; Definition der Antriebe
M569 P0.0 S0 F4 Y1:2 D3 H5 V25 ; Antrieb an DRIVER_0 (X) läuft rückwärts mit StealthChop2, thigh klein, tpwmhrs auf 375mm/s eingestellt,
M915 P0.0 T1 ; ... und tcoolthrs extrem niedrig, so daß CoolStep immer aus ist
M569 P0.1 S1 F4 Y1:2 D3 H5 V25 ; Antrieb an DRIVER_1 (U) läuft vorwärts mit StealthChop2, thigh klein, tpwmhrs auf 375mm/s eingestellt
M915 P0.1 T1 ; ... und tcoolthrs extrem niedrig, so daß CoolStep immer aus ist
M569 P0.2 S1 D2 ; Antrieb an DRIVER_2 (Z) läuft vorwärts mit Spreadcycle
; M569 P0.3 S0 D2 ; testweise auf Spreadcycle umgestellt. Nutzt nix.
M569 P0.3 S0 F4 Y1:2 D3 H5 V25 ; Antrieb an DRIVER_3 (Y) läuft rückwärts mit StealthChop2, thigh klein, tpwmhrs auf 375mm/s eingestellt
M915 P0.3 T1 ; ... und tcoolthrs extrem niedrig, so daß CoolStep immer aus ist
M569 P0.4 S0 D2 ; Antrieb an DRIVER_2 (E1) läuft rückwärts mit Spreadcycle
M569 P0.5 S1 D2 ; Antrieb an DRIVER_3 (E2) läuft vorwärts mit Spreadcycle
; Definition der Achsen und Extruder
;
M584 X0.0 U0.1 Y0.3 Z0.2 E0.5:0.4 ; Antriebe zu Achsen zuweisen
M350 E64:64 Z16 I0 ; Mikrostepping ohne Interpolation für Z (mit der 2mm-Steigung der Schraube entspricht ein Vollschritt exakt 0,01mm) und E
M350 X16 U16 Y16 I1 ; Mikrostepping mit Interpolation für X, U, Y entspricht 0,0125mm pro Mikroschritt
M92 X80 U80 Y80 Z1600 E138.58:138.58 S16 ; (Mikro-)Schritte pro mm
; M566 X600 U600 Y600 Z100 E300:300 ; testweise erhöht wg. Layer Shifts. Nutzt nix.
M566 X342 U342 Y342 Z100 E300:300 ; Maximale sofortige Geschwindigkeitsänderungen (mm/min). E-Wert aus Marlin, XYUZ-Werte aus Junction Deviation 0,013 errechnet (vgl. https://blog.kyneticcnc.com/2018/10/computing-junction-deviation-for-marlin.html). Für XYU möglichst klein halten (Input Shaping)
M203 X21000 U21000 Y21000 Z600 E4800:4800 ; Maximalgeschwindigkeiten (mm/min)
M201 X1000 U1000 Y1000 Z500 E5000:5000 ; Maximalbeschleunigungen je Achse (mm/s²) (Z aus J1-Cura-Profil) - Snapmaker-Daten X,U,Y=10000 sind wegen des Werts in M204 völliger Humbug! (Gesamtbeschleunigung max 1000, daher können die XY-Komponenten nicht höher sein)
M204 P900 T900 ; höchste erlaubte Gesamtbeschleunigung für Druck und Bewegung (Originalwert Snapmaker: 1000, da fängt aber der Tisch an zu wackeln...)
M906 X1000 U1000 Y1400 Z1000 E800:800 I95 ; Motorströme (mA) und Faktor des Ruhestroms in Prozent TODO höhere Ruhestromabsenkung möglich?
M84 S30 ; Timeout für Ruhestrom (s)
; M915 X U Y S20 F1 R2 ; Stallguard für X, U und Y TODO Wert festlegen: Snapmaker definiert den Wert als 8 bei einer Bandbreite von 0...255 beim TMC2209; der TMC2160 der Duet hat aber -64...63
; Beispielwerte für F von X und Y in mm/s:
; F200 --> 100mm in 30s
; F1000 --> 100mm in 6,5s
; F2000 --> 100mm in 3,1s
; F3000 --> 100mm in 2,1s
; Koordinatendefinition
; Nullpunkt = Mittelpunkt des Druckbetts = Zentrum der XY-Korrekturöffnung
;
M208 X-175.5 Y-101 Z0 U-151 S1 ; Achsen-Minima
M208 X151 Y101 Z209 U175.5 S0 ; Achsen-Maxima - nur grobe Vorgabe für Z, korrekter Wert wird beim Bedleveling ermittelt und in der Datei z_max.g gespeichert
; Definition der I/O-Ports
;
; Endstops
M574 X1 S1 P"io1.in" ; X-Endstop: aktiv für Signal auf "High-Level"
M574 U2 S1 P"io2.in" ; U-Endstop: aktiv am oberen Ende für Signal auf "High-Level"
M574 Y1 S1 P"io3.in" ; Y-Endstop: aktiv für Signal auf "High-Level"
M574 Z2 S1 P"io4.in" ; Z-Endstop: aktiv am oberen Ende für Signal auf "High-Level"
;
; Filamentsensoren
M591 D0 P7 C"io5.in" L4.2 R50:150 E12.5 S0 ; Filamentsensor für Extruder 0, Impulssignal, an "io5.in", 4mm/Impuls, Toleranz 50...150%, erste 3 Pulse = 12,5mm verwerfen
M591 D1 P7 C"io6.in" L4.2 R50:150 E12.5 S0 ; Filamentsensor für Extruder 1, Impulssignal, an "io6.in", 4mm/Impuls, Toleranz 50...150%, erste 3 Pulse = 12,5mm verwerfen
; gemessene Werte: TODO - nach einigen Drucken mit M591 D0 bzw. M591 D1 auslesen und anpassen!
;
; Druckdüsen als Z-Sensoren
; Achtung, diese Werte werden von den drei Kalibriermakros temporär überschrieben!
M558 P8 C"^!io7.in" H2 F150 R0.2 T720 K0 B0 ; Z-Sensor Hotend 1=binär ohne Entprellfilter, 2mm Antasthöhe, invertiert (active low)&Pulldownwiderstand aktiv, 300mm/min Meßgeschwindigkeit, 0,5s Recoveryzeit, XY-Bewegung zwischen Messungen 1800mm/min, Heizelemente an
G31 K0 P500 X0 Y0 Z{-global.Druckplattendicke-2} ; Z-Sensor Hotend 1: Triggerwert, Offset und Auslösehöhe
M558 P8 C"^!io8.in" H2 F150 R0.2 T720 K1 B0 ; Z-Sensor Hotend 2=binär ohne Entprellfilter, 2mm Antasthöhe, invertiert (active low)&Pulldownwiderstand aktiv, 300mm/min Meßgeschwindigkeit, 0,5s Recoveryzeit, XY-Bewegung zwischen Messungen 1800mm/min, Heizelemente an
G31 K1 P500 U0 Y0 Z{-global.Druckplattendicke-2} ; Z-Sensor Hotend 2: Triggerwert, Offset und Auslösehöhe
; Hinweis: es darf nur an den Schrauben gemessen werden. Muß in bed.g definiert werden - M557 nicht verwenden!
; Bettleveling
;
M671 X0:-114.5:114.5 Y86:-93:-93 S3.0 P0.5 ; Position der Einstellschrauben
; Einstellungen Heizbett (H0)
; auf PID umgestellt, Bang-Bang macht man auch beim Bett nicht mehr, produziert Z-Banding...
M140 H0 ; Heizelement 0 initialisieren
M307 H0 R0.155 K0.140:0.000 D5.68 E1.35 S1.00 B0 ; Heizelement 0 (Heizbett) Kalibrierungsdaten
M143 H0 S110 ; Temperaturlimit für Heizelement 0 (Heizbett) = 110°C
; Einstellungen Heizelemente Hotends (H1 und H2)
;
; M307 H1 R2.186 K0.17:0.11 D5.67 S1.00 V24.0 ; Heizelement 1 (Hotend 1) alte Kalibrierungsdaten aus Marlin umgerechnet
M307 H1 R2.461 K0.335:0.144 D6.09 E1.35 S1.00 B0 V23.9 ; Heizelement 1 (Hotend 1) Kalibrierungsdaten, kalibriert mit 250°C und F0.55
M143 H1 S320 ; Temperaturlimit für Heizelement 1 = 320°C
M570 H1 P5 T16 ; erlaubte Temperaturabweichung erhöhen, um die bei Raumtemperatur krumme Verstärkerkennlinie abzufangen (sonst Heater Fault)
; M307 H2 R2.186 K0.17:0.11 D5.67 S1.00 V24.0 ; Heizelement 2 (Hotend 2) alte Kalibrierungsdaten aus Marlin umgerechnet
M307 H2 R2.476 K0.347:0.131 D5.52 E1.35 S1.00 B0 V23.9 ; ; Heizelement 2 (Hotend 2) Kalibrierungsdaten, kalibriert mit 250°C und F0.55
M143 H2 S320 ; Temperaturlimit für Heizelement 2 = 320°C
M570 H2 P5 T16 ; erlaubte Temperaturabweichung erhöhen, um die bei Raumtemperatur krumme Verstärkerkennlinie abzufangen (sonst Heater Fault)
M302 P0 S160 R120 ; Limit für Extruderbewegungen: extrudieren nur ab 160°, zurückziehen nur ab 120°
; Einstellungen Lüfter
;
M106 P0 S0 H-1 B0.2 L0.17 X1.0 C"Werkzeuglüfter 1" ; Lüfter 0: Startwert 0%, Steuerung via Thermosensor nicht aktiv, Blip-Dauer 0,2s, Geschwindigkeit von 17%-100%
M106 P1 S0 H-1 B0.2 L0.17 X1.0 C"Werkzeuglüfter 2" ; Lüfter 1: Startwert 0%, Steuerung via Thermosensor nicht aktiv, Blip-Dauer 0,2s, Geschwindigkeit von 17%-100%
M106 P2 S1.0 H1 T45 C"Hotendlüfter 1" ; Lüfter 2: Startwert 100%, Aktiviert, wenn Heizelement 1 > 45°C
M106 P3 S1.0 H2 T45 C"Hotendlüfter 2" ; Lüfter 3: Startwert 100%, Aktiviert, wenn Heizelement 2 > 45°C
M106 P4 H10:11 T40:60 B0.2 L0.17 X1.0 C"Elektroniklüfter" ; Lüfter 4: Aktiviert, wenn Prozessortemperatur > 40°C, läuft bei 70°C oder wenn Steppertreiber eine Überhitzungswarung ausgibt mit 100%.
; Werkzeuge (Tools)
;
M563 S"Hotend 1" P0 D0 H1 F0 ; Werkzeug 0 = Extruder 0 + Heizelement 1
G10 P0 X0 Y0 Z0 ; Achsenoffsets für Werkzeug 0
M568 P0 R0 S0 ; Defaulttemperaturen Werkzeug 0 0°C (=aus)
M563 S"Hotend 2" P1 D1 H2 F1 X3 ; Werkzeug 1 = Extruder 1 + Heizelement 2, X auf U gemappt
G10 P1 X0 Y0 Z0 ; Achsenoffsets für Werkzeug 1
M568 P1 R0 S0 ; Defaulttemperaturen Werkzeug 1 0°C (=aus)
; M563 S"Duplizieren" P2 D0:1 H1:2 X0:3 ; Werkzeug 2 = beide Extruder, 150mm versetzt
; G10 P2 X75 U-75 Y0 Z0 ; Achsenoffsets für Werkzeug 2
; M567 P2 E1:1 ; Extrusionsverhältnis für beide Hotends gleich
; M563 S"Spiegeln" P3 D0:1 H1:2 X0:3 ; Werkzeug 3 = Extruder 1 + Heizelement 2, X auf U gemappt und 300mm versetzt. U mit M579 U-1 invertieren, wenn das Tool aktiv ist! Homing anpassen!
; G10 P3 X75 U-75 Y0 Z0 ; Achsenoffsets für Werkzeug 3
; M567 P3 E1:1 ; Extrusionsverhältnis für beide Hotends gleich
; LEDs
;
M42 P9 S0.5 ; LED-Streifen auf 50%
; Geschwindigkeitsverbesserndes Voodoo (Input Shaping, Pressure Advance etc.)
; Empfehlung: erst Input shaping justieren, dann Pressure Advance, dann Retraction!
;
; testweise Input Shaping deaktiviert
; M593 P"zvddd" F58 D0.1 L30 ; Input Shaping bei 58Hz, Dämpfungsfaktor 0,1
M572 D0:1 S0.05 ; Pressure Advance
M309 P0 S0.035 ; Hotend 1 Feedforward-Wert
M309 P1 S0.035 ; Hotend 2 Feedforward-Wert
; Retractwerte (M207) siehe Filamente!
; Netzwerk - WLAN-Modul ans Ende setzen wegen Timing-Bug...
;
M550 P"Duplimatix" ; Maschinenname
M552 I0 S0 ; Ethernetanschluß deaktiviert
M586 P0 S1 ; HTTP-Server aktiv
M586 P1 S0 ; FTP deaktiviert
M586 P2 S0 ; Telnet deaktiviert
G4 P10000 ; 10s warten, daß das WLAN-Modul in Ruhe starten kann
M552 I1 S1 ; WLAN-Modul aktiv
; Sonstiges
;
T0 ; Erstes Werkzeug bei Start ausgewählt
M42 P9 S0.25 ; LED-Streifen dimmen
M98 P"Korrekturwert_z_max.g" ; korrigiertes Z_Max einlesen
M98 P"Korrekturwert_xy_offset_tool1.g" ; XY-Offset Hotend 2 einlesen
M207 P0 S1.5 R0 F2400 T2400 ; Default-Retractwerte Hotend 1: 1,5mm und 40mm/s
M207 P1 S1.5 R0 F2400 T2400 ; Default-Retractwerte Hotend 2; 1,5mm und 40mm/s
This is an M122 report after a layer shift (I used spreadcycle in that attempt):
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.1 (2023-08-31 16:19:24) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6JTDL-3SN6L-998UU
Used output buffers: 12 of 40 (32 max)
=== RTOS ===
Static ram: 154852
Dynamic ram: 123592 of which 0 recycled
Never used RAM 63780, free system stack 136 words
Tasks: NETWORK(2,nWait,15.8%,187) HEAT(3,nWait,0.0%,323) Move(4,nWait,2.5%,214) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,343) TMC(4,nWait,9.6%,61) MAIN(1,running,71.6%,137) IDLE(0,ready,0.4%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 01:05:47 ago, cause: software
Last software reset at 2023-10-21 12:39, reason: User, Gcodes spinning, available RAM 63596, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 42.4, current 47.0, max 47.3
Supply voltage: min 23.6, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.3, max 12.6, under voltage events: 0
Heap OK, handles allocated/used 99/3, heap memory allocated/used/recyclable 2048/2012/1960, gc cycles 11
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 216, reads 9996, writes 28 timeouts 0
Driver 1: standstill, SG min 0, mspos 264, reads 9996, writes 28 timeouts 0
Driver 2: standstill, SG min 0, mspos 584, reads 10001, writes 23 timeouts 0
Driver 3: standstill, SG min 0, mspos 792, reads 10001, writes 23 timeouts 0
Driver 4: standstill, SG min 0, mspos 582, reads 10006, writes 19 timeouts 0
Driver 5: standstill, SG min 0, mspos 398, reads 10006, writes 19 timeouts 0
Date/time: 2023-10-21 13:45:42
Slowest loop: 211.72ms; fastest: 0.05ms
=== Storage ===
Free file entries: 17
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 4.1ms, write time 2.8ms, max retries 0
=== Move ===
DMs created 125, segments created 38, maxWait 129179ms, bed compensation in use: none, height map offset 0.000, ebfmin -1.00, ebfmax 1.00
no step interrupt scheduled
Moves shaped first try 15, on retry 893, too short 13236, wrong shape 57285, maybepossible 6813
=== DDARing 0 ===
Scheduled moves 117289, completed 117289, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
SBC is idle in state(s) 0
Daemon is doing "G4 S1" in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x8000000f
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
Extruder 0 sensor: ok
Extruder 1 sensor: ok
=== CAN ===
Messages queued 35520, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 19739/0/0
Tx timeouts 0,0,19738,0,0,15780 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 204.56ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(2) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: disabled
Error counts: 0 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta4
MAC address 70:04:1d:be:ad:b8
Module reset reason: Power up, Vcc 0.00, flash size 4194304, free heap 217116
WiFi IP address 192.168.178.31
Signal strength -61dBm, channel 2, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 5 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0
And here is what an M569.2 R0...4 command set spit out (unsure if it helps, but since that was requested in the thread I mentioned above...):
M569.2 P0.3 R4
Register 0x04 value 0x30000042
M569.2 P0.3 R3
Register 0x03 value 0x00000000
M569.2 P0.3 R2
Register 0x02 value 0x00000000
M569.2 P0.3 R1
Register 0x01 value 0x00000005
M569.2 P0.3 R0
Register 0x00 value 0x00001089
It might be worth noting that - if I interpret the M122 command correctly - my Duet also shows a lot of CAN tx timeouts, which is something that was also mentioned in the "Missing Steps - Cant Print SpreadCycle StealthChop tuning help" thread that I linked above. I do not know what the figure means, but I suspect this might be related to the issue I have with the Duet 3 wifi module...?
The question is now: what can I do to get the printer running with input shaping...?