So today I made quite a few experiments chasing my problem with moving of the U carriage during printing with X. A few days ago I tried to put both Y motors on ZA and ZB conectors , just to find that one of my Z connectors is not energizing the motor. I ordered a new Duet wifi and while waiting today decided to try to move 3 Z motors on wifi and x,y,u on DUEX board. So I put 3Z motors on P1,2,3 and the motor on 2 is not energized, then moved the motors to 0,1,2 and it is working , but center motor is inverted (2), So I make it to move in the right direction with inverted motor, but when G32 it is corecting wrong direction, I do not know why then tried on 234 and 2 is not working, then defined this: ; Drives M569 P2 S1 ; X physical drive 0 goes backwards M569 P3 S1; Z ;M569 P3 S0 M569 P4 S0 ;M569 P1 S0 ; Y right physical drive 1 goes backwards ;M569 P2 S1 ; Y left physical drive 2 goes forwards ;M569 P3 S1 ; U physical drive 3 goes forwards M569 P1 S1 ; E1 physical drive 4 goes backwards M569 P5 S0 ; X M569 P6 S1 ; Y right M569 P7 S0 ; Y left ;M569 P5 S1 ; Z left physical drive 5 goes backwards ;M569 P6 S1 ; Z center physical drive 6 goes backwards ;M569 P7 S0 ; Z right physical drive 7 goes forwards M569 P8 S1 ; E2 physical drive 8 goes forwards M569 P9 S1 ; U M584 X5 Y6:7 Z0:3:4 U9 E1:8 ; set drive mapping and it is working like a charm . Ther is some kind of short on this board ,period. Now the movement of U with dial indicator when changin gY direction is 0.04 and X is 0.05

I was looking into this for the past week and unfortunately I have to report failure to get it done. The problem is that we just have way to few RAM available on PanelDue. Maybe in future version of PanelDue with much more RAM this could be done for but for now it is technically impossible.

Done in standalone mode:

Well, the issue has come back. Same symptoms. I get really bad motor movement with the gcode files while printing, but I can pause and extrude just fine with DWC. Any idea what I should be looking at next? I have swapped the motor to a much more powerful one that I just had lying around, and it can really crank out the extrudes in DWC, but when I go to print, it just stutters and skips steps. I have dropped the acceleration and jerk to 500, and I still have the issue. I do not think it is the settings, as I can extrude with those settings in DWC with no issue. When printing, I do not think the toolboard driver is giving good commands, but I have no idea why that would be. ; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode G4 S1 ;wait for expansion boards to start ; Drives M569 P121.0 S1 ; physical drive 121.0 goes forwards M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S0 ; physical drive 0.2 goes forwards M569 P0.4 S0 ; physical drive 0.2 goes forwards M569 P0.5 S1 ; physical drive 0.2 goes forwards M584 X0.1 Y0.0 Z0.2:0.3:0.5:0.4 E121.0 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X98.00 Y98.00 Z400.00 E426.00 ; set steps per mm M566 X2500.00 Y2500.00 Z200.00 E200.00 ; set maximum instantaneous speed changes (mm/min) M203 X10000.00 Y10000.00 Z8000.00 E3000.00 ; set maximum speeds (mm/min) M201 X3000.00 Y3000.00 Z200.00 E200.00 ; set accelerations (mm/s^2) M906 X1100 Y1100 Z1000 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-200 Y-200 Z-1 S1 ; set axis minima M208 X200 Y200 Z400 S0 ; set axis maxima ; Leadscrew Locations M671 X-322.5:-322.5:262.5:262.5 Y-250:300:300:-250 S20 F1.2 ; Z leadscrew positions ; Endstops M574 X2 S1 P"io0.in" ; X min active low endstop switch M574 Y2 S1 P"io1.in" ; Y min active low endstop switch M574 Z1 S2 ; Z-Probe M558 P8 C"^!121.io0.in" H5 F300 T16000 ; set Z probe type to unfiltered switch and the dive height + speeds M558 H15 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X0 Y0 Z1 ; set Z probe trigger value, offset and trigger height M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters M557 X-200:200 Y-200:200 S100 ; define mesh grid ; Heaters M308 S0 P"temp3" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp3 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S0.50 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S150 ; set temperature limit for heater 0 to 120C M308 S1 P"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 121.temp0 M950 H1 C"nil" M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H1 B0 S0.5 ; disable bang-bang mode for heater and set PWM limit M143 H1 S350 ; set temperature limit for heater 1 to 350C ; Fans M950 F0 C"nil" M950 F0 C"121.out2" Q500 ; create fan 0 on pin 121.out1 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"121.out1" Q500 ; create fan 1 on pin 121.out2 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory T0 ; select first tool m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S8-6JTDL-3SD6J-1S3YF Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 148196 Dynamic ram: 61484 of which 500 recycled Never used RAM 140492, free system stack 121 words Tasks: Linux(ready,143) HEAT(delaying,302) CanReceiv(notifyWait,799) CanSender(notifyWait,359) CanClock(delaying,349) TMC(notifyWait,18) MAIN(running,616) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:13:58 ago, cause: power up Last software reset at 2021-03-05 23:49, reason: User, none spinning, available RAM 140492, slot 0 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 28.9, current 51.2, max 51.3 Supply voltage: min 27.9, current 30.0, max 30.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.1, under voltage events: 0 Driver 0: position 0, standstill, reads 48788, writes 31 timeouts 0, SG min/max 0/271 Driver 1: position 0, standstill, reads 48788, writes 31 timeouts 0, SG min/max 0/505 Driver 2: position 22080, standstill, reads 48784, writes 35 timeouts 0, SG min/max 0/263 Driver 3: position 0, standstill, reads 48784, writes 35 timeouts 0, SG min/max 0/277 Driver 4: position 0, standstill, reads 48785, writes 35 timeouts 0, SG min/max 0/259 Driver 5: position 0, standstill, reads 48785, writes 35 timeouts 0, SG min/max 0/201 Date/time: 2021-03-08 15:16:32 Slowest loop: 171.53ms; fastest: 0.03ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 180288ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 448, completed moves 448, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 15], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" 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 idle in state(s) 0 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 8761, send timeouts 26, received 9733, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 57602, free buffers 49 (min 47) === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 29686/29686 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2d410 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 8.35 Maximum length of RX/TX data transfers: 2588/1520 m122 b121 Diagnostics for board 121: Duet TOOL1LC firmware version 3.3beta1 (2021-02-14 16:34:04) Bootloader ID: not available Never used RAM 3976, free system stack 0 words Tasks: Move(notifyWait,90) HEAT(delaying,91) CanAsync(notifyWait,67) CanRecv(notifyWait,75) CanClock(notifyWait,67) TMC(delaying,56) MAIN(running,252) AIN(delaying,63) Last reset 00:14:41 ago, cause: power up Last software reset data not available Driver 0: position 34448, 426.0 steps/mm, standstill, SG min/max 0/282, read errors 0, write errors 0, ifcnt 20, reads 47135, writes 20, timeouts 0, DMA errors 0, steps req 81994 done 81994 Moves scheduled 1234, completed 1234, in progress 0, hiccups 0, step errors 0, maxPrep 532, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 9, peak Rx sync delay 610, resyncs 1, no step interrupt scheduled VIN: 29.9V MCU temperature: min 25.8C, current 37.0C, max 42.1C Ticks since heat task active 249, ADC conversions started 878201, completed 878201, timed out 0 Last sensors broadcast 0x00000002 found 1 5 ticks ago, loop time 0 CAN messages queued 10272, send timeouts 0, received 9157, lost 0, free buffers 36, min 35, error reg 0 dup 0, oos 0, bm 0, wbm 0

I've run a million Raspberry PIs, but I've never run in SBC mode, so this might be completely wrong. Did flashing your SD card with Etcher work? That looks like the filesystem from an normal "Insert into the Duet3"SD card to me. A Raspberry PI SD card boot partition should have stuff like this on it: kilian@DESKTOP-UP82TLJ /cygdrive/f $ ls -l total 54469 -rw-r--r-- 1 kilian None 18693 Dec 10 20:43 COPYING.linux -rw-r--r-- 1 kilian None 1594 Dec 10 20:43 LICENCE.broadcom drwxr-xr-x 1 kilian None 0 Dec 10 13:33 'System Volume Information' -rw-r--r-- 1 kilian None 25426 Dec 10 20:43 bcm2708-rpi-b-plus.dtb -rw-r--r-- 1 kilian None 24774 Dec 10 20:43 bcm2708-rpi-b-rev1.dtb -rw-r--r-- 1 kilian None 25163 Dec 10 20:43 bcm2708-rpi-b.dtb

Hi, Please help our client or do you accept the sensor under warranty?

Agreed on Pathio being an outlier. I have one more coming, but then I'll stop, promised (-:

I am using RRF 3.2.2. I got a -sorta- fix. Apparently the offset of the second nozzle isn't applied, yet when I apply it to the first nozzle it seems to work. Maybe this would need more investigation why the y-offset is only applied on the first nozzle and not the second.

@jay_s_uk sorry about that had a brain fart moment, I understand now I got confused because the link you provided says those drivers are supported but that's for the LPC boards I assumed it meant RRF in general has support for those and since Duet is running RRF I assumed it could drive them but I get it wasn't designed to support them via hardware well it does but I'd lose a lot of functionality. I get it now it's the same thing with those marlin boards some support the UART, or SPI but never both interfaces because the pins are not broken out, etc. Thanks for all your help Jay, I'm barely learning RRF and getting into the Duet ecosystem.

Thanks, I've got an update ready for this format, too.

Anyone know where we can get the expansion board in Uk please? None of the big reseller have this on stock , not even listed.

@dm86 For info, and for future reference, extruders are treated as if each one is an individual axis. So multiple extruders can be mapped to a single tool using M563, but they are still individual "axes", so you have to set steps per mm, currents, acceleration, speeds, jerk etc etc etc, for every extruder.

@Dougal1957 said in Piezo-Probe to auto-adjust offset after Nozzle change: @kuhnikuehnast said in Piezo-Probe to auto-adjust offset after Nozzle change: The Piezo Disc itself is easy to get! But it is always used with a special "converter board". This is hard to get- and I don't know exactly what this baord is doing? have a look at https://pyroballpcbs.com thanks Dougal1957 - I already got one- ordered from alieexpress

@TF_Sinthoras You can use the retraction tab here to tune it. https://teachingtechyt.github.io/calibration.html

@Nuramori Cool! Of course, here it is: https://www.amazon.com/Barrow-Temperature-Sensor-Fitting-Silver/dp/B06XB4JK7G I am looking to do an up and downstream sensor to measure the temp split on either side of the radiator.

Oh well, it doesn't get boring - thanks Here some more escaped regexs for Filament usage filament used extruder \\d+ \\(mm\\) = (?<mm>\\d+\\.?\\d*) Print time: total print time \\(s\\) = ((?<s>(\\d+\\.?\\d*)))

I was told via side-channel that there is a way to add layer height info in ideamaker. I will check that out. Next up: MatterControl (-:

I just started a 26 hour print on the test machine ... I will fuzz with duetcontrolserver after that's failed or finished (-:

@fcwilt okay thank you i will check this

Here's a simple dual extrusion system to tilts the unused extruder away from the print: https://hackaday.com/2021/03/07/this-dual-extrusion-system-rocks/

@bernardomattiucci sounds like that would work

@fcwilt Thanks! I’m running the latest 3.x firmware on the SKR 1.4. My original Duet boards are all in actual printers. 😁

@dc42 Thanks, in this case is VIN the 24V PSU as opposed to the separate 5V feeding the Duet/SBC?