@engikeneer Thanks for the tip with G53, that is indeed what I was looking for. I id implemented "my way" in the meantime which simply sets the offset to x0y0 in the tool files. But that is a ugly hack indeed.
I had a look at the e3d's git repo to get some ideas how they did it. And they do not use they do not use the G53 there, which is a bit surprising. The command may be to new for their retired product.

Anyway, I will work on the calibration for now and will play with the G53 later.

I might be onto something:

I cut off the pins that I don't need on the 2209 from the J3 column (pins 2, 3 & 5). 40239395-a074-42b3-ad22-2af4380e8002-image.png

After declaring the drivers in the board.txt file this is the status of the drivers from m122:
7760f99d-d9ea-4a64-af31-332f66a85791-image.png
(I think my driver 1 socked is broken, no matter what I put in there it sais that there is no driver, I will look into it some other time)

Now I need to reconnect the cables to the board as before so that I can go on with testing.

Update:
Succes! All axis moving as they should.

@dc42 - thanks for the clarification.

Layer segmentation working pretty well.

I set things up so layers are segmented into 4 - other than the top and bottom layers, plus every 4th layer.

Results look pretty good in Bambu Studio Preview - with segmented parts joining back together ok.

Before Join
40355914-D7E5-484F-A080-3899DF92CB33.png

After segments joined - inner wall only illustrated
4B1D9729-BAE3-45C8-80E8-75C0D9794D4D.png

Showing the Gcode now for 4 segments
First segment - for motion system queue1
175D26B1-E793-45A1-BBE3-F61EB3C8D118_1_201_a.jpeg

Bambu Studio showing that segment completed - by the time it gets to the gcode for queue0
CA54FB18-8957-47D7-A60B-E28EEDD94A66_1_201_a.jpeg

Gcode now showing wait - for both queue1 and 0 to complete, and then on to 2nd segment for queue 1
3286F9A0-5B04-4E6E-80F2-7CE475C1F7D3_1_201_a.jpeg

End of both queues - and then moving on to a full non parallel layer
834A6253-BF47-4D3C-85A6-898F14A8FAC7_1_201_a.jpeg

@droftarts hi, sorry it took so long and many thanks for help.

First, answering your questions:

same with beta2 no, the pause is not in the middle of a particularly long move. My feeling is that this happens at every pause. I could not find any segmentation settings in OrcaSlicer (which I am using) from what i see in gcode, the slicer is using relative extrusion attaching the gcode of a cube 20x20x20 with 2 walls and some simple infil, that is used in the video youtube link at youtu be: c0CzmD-DGdg?si=Dh9AtsguJKMDB1lt to see the phenomenon in action. an overextrusion is clearly heard at 00:26

Here goes config.g:

===================================================
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"M1 Magrethea"

; Emergency stop at E6 - to be replaced with power cut
M950 J6 C"duex.e6stop"
M581 P6 T0 S1 R0

; Network
M552 S1 ; connect wifi to internally stored ssid
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; FTP

; Drives
M569 P0 S1 ; X ; physical drive 0 goes forwards
M569 P1 S1 ; C
M569 P2 S1 ; this is the dual channel connected to right Z motors
M569 P3 S1
M569 P4 S0 ; E
M569 P5 S0 ;
M569 P6 S0 ;
M569 P7 S0 ; right Y
M569 P8 S1 ; left Y
M584 X0 Y7:8 Z2:5:6 E4 C1 P3 ; set drive mapping; P4=visible axes. right Z motors are on the dual channel driver. 5 is back left, 6 front left
M350 X16 Y16:16 Z16:16:16 E16 C16 I1 ; configure microstepping with interpolation
M92 X80.00 Y100:100 Z1600:1600:1600 E783 C80 ; these are the correct theoretical model. measured with orca calibration
M566 X300 Y300:300 Z10:10:10 E320.00 ;120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X10000.00 Y10000:10000 Z600:600:600 E1200.00 ; set maximum speeds (mm/min)
M201 X6000.00 Y4000:4000 Z100💯100 E450.00 ; set accelerations (mm/s^2)
M906 X1200 Y900:900 Z1800:900:900 E900 C80 I15 ; set motor currents (mA) and motor idle factor in %. My extruder is rated for 1A
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X652 Y430 Z690 S0 ; set axis maxima. z could be 701. X has about 1mm spare, to enlarge, relocate X probe.

; Endstops
M574 X2 S1 P"!xstop" ; x stop, sorry for using NO stop. better to reconfigure as NC
M574 Y2 S1 P"ystop+e1stop" ; configured as NC, which is a good thing to do

; Filament sensors
;M591 D0 P3 C"e0_stop" S1 ; drive 0, magnetic filament monitor, plug, enable
M591 D0 P1 C"!^e0stop" S1 ; microswitch sensor drive 0, active low, pin, enable

; Z-Probe
;M307 H3 A-1 C-1 D-1 ; H7 means E6 (Duex /Expansion). Disable heater so this pin can be used; probably not needed coz it says heater not found
; "You can no longer disable a heater using M307 A-1 C-1 D-1. To use the pin for something else, don't create a heater on that pin."
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.i^H^H^H^Hn" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P20 X-31 Y1 Z1.12 ; set Z probe trigger value, offset and trigger height; lower Z means print higher. NOZZLE: 0.5 HF
M375 ; load height map

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp. Tnnn (for thermistor sensors) Thermistor resistance at 25C, Steinhart-Hart thermistor model B coefficient
M950 H0 C"!exp.heater4" T0 ; Q0
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0

M308 S1 P"e1temp" Y"thermistor" T100000 B3950 ; configure sensor 1 as thermistor on pin e1temp
M950 H1 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1
M307 H1 R3.004 K0.380:0.000 D11.29 E1.35 S1.00 B0 V23.9
M570 H1 P20 T20 ; temperature excursion 20, time 20s - abit too long but the PID is annoying
M143 H1 S270 ; set temperature limit for heater 1 to 270C

; Fans
M950 F1 C"duex.fan4" Q10 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"duex.fan3" Q10
M106 P2 S0 L250 X255 B0.1 H-1 ; set fan 0 value. Thermostatic control is turned off

; Tools
M563 P1 D0 H1 F2 S"Right" ; define tool 1, extruder 0, heater 1, fan 2
G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

M309 P1 S0.03 ; this is flow/heater power compensation

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B115200 ; enable support for PanelDue, UART at 115200 baud
M564 H0 ; H1 = forbid movement of axes that have not been homed, H0 = allow movement of axes that have not been homed
M302 P1 ; allow cold extrusion

G92 C0 ; nevermind this axis for now

T1 ; default tool is 1
======================================================end of config.g

Cube_PLA_6m41s.gcode

@droftarts, I am waiting for your response.

Please check my config.g file:

M558 K0 P11 C"100.i2c.ldc1612" F36000 T36000 ; configure SZP as probe 1, type 11, on CAN address 120 M308 A"SZP coil" S10 Y"thermistor" P"100.temp0" ; thermistor on SZP coil G31 P500 K0 Z3 Y-17 H10 ; define probe 1 offsets and trigger height M558.2 K0 S23 R164530 M558.1 K0 S2

Let me know if I am doing something wrong.

At some points, I get trigger heights like 3.00, -2.55, or -2.99.

In DWC, my Z-probe value is not steady; it fluctuates between 0, 9097, and 999999.

Additionally, I am using a proximity sensor for homing the Z-axis.

provide me solution for that.

@droftarts Thanks, I'll wait then.

@mitch Lots of places to shift electronics (ebay, craigslist, offerup marketplace), I'm in agreement about saving it from a landfill. But seems really disrespectful to come here to do it. Just my 2c.

@T3P3Tony

I will be able to check that in January, once I'm back from holidays

@droftarts

Same, will test it out in January once I'm back. The wiring I've done per the guide you've shown. I had missed the driver enable polarity jumper, so that's quite likely the issue there.

With re-sending the commands we were able to get the printer up and running, and the printer has completed a successful print, though hopefully we won't need to use the driver_enable.g file I used before with the fixes recommended.

Thanks both for the help, I'll enjoy the Christmas break for now and get back to it in Jan

@droftarts thanks for replying.
This model you mentioned, from aliexpress, theoretically doesn't need any changes to the wiring, right?

@martinv what is the chamber heater controller actually controlling? How many heaters, fans, temperature sensors etc?

@RodrigoRMaraujo said in Duet maestro - Diag led does not turn off:

I've been buying Duets on AliExpress since 2019

Just curious, since you’ve benefited so much from their work without buying genuine hardware, have you offered to contribute to the Duet development team?

@Aurimas Do you have a daemon.g file in /sys?
I think the logging (M111) should show the Gcode sent if you turn it on, which might give a clue where it's coming from. Send M111 P3 S1 and connect a serial monitor (eg YAT) via USB.

Ian

@droftarts

My mistake... I'm sorry for mixing up the firmware numbers. I thought I had the latest firmware on both boards but I don't. I updated the firmware on the 6HC and it's now working.

Thanks so much for your help!

@Arminas said in PT1000 thermistor configuration:

erature is stable all the time, expect at a

you probably have season changes and thus your PID tuning is out the window.
rerun the tune and you will probably find that it works fine now

@LindsayC which firmware version? SBC or standalone mode?