Posted this part in the RatRig discord server. But it has a limited Duet3D fan base. So posting here too.

https://www.printables.com/model/967347-eva3-back-plate-tension-less-duet3d-tool-board

@kipk
I have reserved one at
https://www.dold-mechatronik.de/

They expect it to be in stock next week.

@jay_s_uk Great tip, thank you. i will look into that.

Both that wiki and the GCode Dictionary explains thing with the term "Z leadscrews" which is correct in some hardware configurations. But it fooled me, maybe reading too quickly and not fully comprehending tings.

I propose a change to the use of "pivot point" or equivalent to make things a bit less likely to misunderstand.

@droftarts I have limited knowledge in this area, but would it be possible by using an arduino converting it to an analog signal and use that signal as a temp sensor on the Duet?

One would then get a curve plotted in the web interface and a neat way to control an extraction fan with "temp" levels in the M106 command.

Final settings (for future use by anyone interested):

config.g
-----------------------------------------
; Drives
M584 X0:3 Y1:4 Z2 U3 V4 P3; Three axis visible

; Tools
M563 P0 D0 

; Drive direction
M569 P0 S1                       ; Drive 0 goes forwards
M569 P1 S1                       ; Drive 1 goes forwards
M569 P2 S1                       ; Drive 2 goes forwards
M569 P3 S1
M569 P4 S1

; Steps and Speed
M92 X80.00 Y80.00 U80.00 V80.00 Z4000.00 ; Set steps per mm
M566 X900.00 Y900.00 U900.00 V900.00 Z12.00; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 U6000.00 V6000.00; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 U500.00 V500.00; Set accelerations (mm/s^2)
M906 X800.00 Y800.00 Z800.00 U800.00 V800.00 I30; motor currents (mA) and motor idle factor
M84 S30  ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U0 V0 S1                 ; Set axis minima
M208 X600 Y400 Z100 U600 V600 S0           ; Set axis maxima

; Endstops
M574 X1 Y1 U1 V1 S0               ; Set active low and disabled endstops

homex.g
----------------------------------------
M584 X0 U3 P5; split steppers, 5 axis visible
G91 ; relative moves
G1 X-650 U-650  F450 S1 ; fast homing X and U in parallell
;G92 X0 U0 ; Make adjustments to square axis here
M584 X0:3 P3; join steppers, 3 axis visible
G90

dsmudger

I would say these are major steps

• Homing switches (I use a microswitch for X and an old dc42 IR sensor for Z and Y)
• Make adapters or get new cables to stepper motors
• Make adapter or new cable for hot end
• Power supply (I am using the original Cetus power supply)
• Configure the Duet3d (steps/mm and heater values you can see above, the rest I think may vary in your case)

Original connectors can be forced into the Duet board, but I ended up making adapters both for the steppers and the hot end. Pictures below show before the adapters during "proof of concept phase". On the hotend it self I made a new board using experimental circuit board and matching connectors. There was too much interference in the ribbon cable for the signal from the IR board so I added an ethernet (twisted pair) cable for that.

If there are any questions I would be happy to help.

Never used them, can not reach them with my fingers when mounted on my printer.

I got no voltage at those points. Not with or without an object within range.

I made several tests to be sure sonce i did net get any readots at all.

As a last test I was thinking of trying to shine some IR light on the sensor using the old ormerod sensor or a tv remote.

Settimg this up it started working again!!?? I did not get to the point using another IR source.

I have disconnected it several times and kept working then it stopped working again.

I have upgraded my duet-controlled Cetud3d with a Hemera extruder. I have been testing how fast it can print and still have not reached its limits.

Peak speed in the PLA print below is about 250 mm/s , reported by DWC.

• Lauyerheight 0.20 mm
• Print time 40 minutes.
• Acceleration set to 2500 mm/sec^2 (M201)
• Allowable instantaneous speed change 800 (M566)

This is unnecessary and so much FUN
https://youtu.be/gCN8IdGvwas

@fotomas
Did a test, first layer transparent PLA layed down in a concentric pattern. On top of that black and red PLA and lastlt a black layer. All layers printed with a .4 mm nozzle and layerheight .4 mm. The coaster has a diameter of 80 mm.

There some moiré effects so there are things to improve. But as a first test I think it worked out fine.

(The text translates to "transmission interruption")

After finding and adressing several issues I belive it is working fine now.

I have:
Lowered the jerk value for Z to 15
Let the bed soak properly before do bed mesh (temp 80 )
Replaced lost screw, one of three holding the hotend to the heatsink. This was hidden by the silicon sock on my Phaetus Rapido hotend.

I think the jerk value was the thing but the other two brought a fair amount of inconcistency too.

So i will end this thread/question here. Thank you for all the help and a little extra to Phaedrux.

Reading about E3D's new PZ Probe https://e3d-online.com/products/pz-probe

I wonder if it would be possible to connect to Duet3D's Toolboard. The wireing instructions states that it should be connected to the PanelDue port.

Also, the stand-alone version of PZ Probe should/can it be connected between the hotend heatsink and toolhead. Looking at the Voron version, it seems to be "inside" the heatsink somehow.

@timschneider There is no M207 in config.g or print code.

I have done more testing.

• Starting out with a 0.2 mm baybystepping does NOT make it change more between prints.
• I happens even without any initial baby stepping.
• "Print Again" on PanelDue or sending new G-Code file makes no difference.
• Homing Z makes it OK again

So it does not seem to relate to babystepping. I started thinking in terms of loosing steps on Z-Axis, below is my motor settings, start and end GCode (if any Z-moves messes things up)

... I am running out of ideas here, does any one hava any ideas for some controlled approach to narrow down the possibilities?

speed settings

M566 X600.00 Y600.00 Z500.00 E120.00 P1      ; set maximum instantaneous speed changes (mm/min) and jerk policy
M203 X30000.00 Y30000.00 Z1200.00 E6000.00 ; set maximum speeds (mm/min)
M201 X20000.00 Y20000.00 Z300.00 E5000						; set accelerations (mm/s^2)
M204 P10000 T20000

Start of print code

M140 S80 ; set bed temp and continue
M109 S245 ; set nozzle temp and wait
M190 S80 ; set bed temp and wait

M150 R255 U255 B255 W255 P255 S120 F0 ; Print lights

G1 X100 Y4 Z5 F5000
M73 P1 R1
G1 Z0.6
M73 P2 R1
G1 X200 Y4 E30 F1500

End of print code

M106 S0
M400 G91; relative positioning
G1 H2 Z25 F12000 ; lift Z relative to current position
G90 ; absolute positioning
G1 Y270 X10 F5000; move head back
M150 U255 P255 S120 F0 ; Print done lights, green
M0

I start my printer with bed.g G32 (code borrowed and tweaked) from someone at this forum:

M290 R0 S0      ; clear baby stepping
M561            ; clear any bed transform
M400            ; finish all moves, clear the buffer

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
	G28             ; home all

M201 X1000 Y1000  ; reduce acceleration

; calibrate bed
while true
  if iterations = 5
    abort "Auto calibration repeated attempts ended, final deviation", move.calibration.final.deviation ^ "mm"
  G30 P0 X5 Y10 Z-99999 ; probe near a leadscrew
  if result != 0
    continue
  G30 P1 X150 Y275 Z-99999 ; probe near a leadscrew
  if result != 0
    continue
  G30 P2 X270 Y10 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
  if result != 0
    continue
  if move.calibration.initial.deviation <= 0.05
    break
  echo "Repeating calibration because deviation is too high (" ^ move.calibration.initial.deviation ^ "mm)"
; end loop
echo "Auto calibration successful, deviation", move.calibration.final.deviation ^ "mm"
G0 X150 Y150 F12000

G28 Z                     ; rehome Z as the absolute height of the z plane may have shifted
G29 S1                    ; load saved mesh
M98 P"0:/sys/setspeeds.g" ; set speed and acceleration

@oliof No the value on PanelDue and DWC remains at 0.1

@gloomyandy That is a good question. I will test that ASAP

@oliof I set babystepping via PanelDue, see OP.

After som testeing I have drawn the conclusion that babystep settings accumulates between each print.

These are three consecutive prints (sorry for the green light, LED strip signaling finished print).
Baystep is set to 0.1 mm "higher" and as can be seen it prints higher and higher for each print.

Babystep is set by PanelDue FW 3.5.0
RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode)

config.g and g-code for the print attached, sliced with Orca Slicer.

What can be the cause of this?

config.g
Cube_0.2mm_PETG_1m2s.gcode

Posted this part in the RatRig discord server. But it has a limited Duet3D fan base. So posting here too.

https://www.printables.com/model/967347-eva3-back-plate-tension-less-duet3d-tool-board

@jay_s_uk
Is it ok to connect to LED strip in parallel? Would it work and both behave the same, as a mirror image of eachother?

@jay_s_uk I do not want to argue but then then power to the LED strip is just one lead. It will only join on the AC side. I do not understand... ahhh negative to negative between the PSU's

But I have an answer how to connect things, thank you!