RepRapFirmware 3.6.0-alpha.2 for Duet main boards available

[Exerqtor]

@dc42 I'll try without PA first and see how that fairs ☺️

[droftarts]

@Exerqtor You should definitely retune PA with the new IS implementation, if you haven't.

Ian

[N3XT3D]

I have tested the new version and I have to say it really is a huge improvement. For me, it's the best and most important update so far. My printer is heavy and has quite a high mass that is being moved. Now I can increase the acceleration and jerk with higher print speeds and a much better surface as a result. The printer used to make a lot of noise, especially when changing direction quickly (contours of figures etc.), which is no longer the case. In short, my printer now finally prints the way I always imagined it would, in terms of speed, noise and quality. Thank you for the release and the work involved.

[Exerqtor]

@droftarts said in RepRapFirmware 3.6.0-alpha.2 for Duet main boards available:

@Exerqtor You should definitely retune PA with the new IS implementation, if you haven't.

Ian

Oh i have 😅 Went from 0.045 too 0.0072 lol

[balajiramani]

I just tried this on the delta that I have and during calibration, the effector is crashing into the bed. After reverting back to 3.5.2, calibration works fine.

Here is a video of the crash.

Here is config.g

; Setup some global variables
global power_fail_retract = 2   ;  Retract 2mm when power fails

; Communication and general
M550 P"BigDelta"				        ; Machine name and Netbios name (can be anything you like)
M551 Preprap                        	; Machine password (used for FTP)
M552 S1					                ; Enable WiFi. Disabled for setup and testing. Enable once set up on your network.

; Enable telnet
M586 S1 P2

; Debugging
M111 S0                                 ; Debug off
M929 P"eventlog.txt" S1                 ; Start logging to file eventlog.txt

M555 P2                           	    ; Set output to look like Marlin
G21                                 	; Work in millimetres
G90                                	    ; Send absolute coordinates...
M83                                 	; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S0				; Drive 0 goes backwards
M569 P1 S0				; Drive 1 goes backwards
M569 P2 S0				; Drive 2 goes backwards
M569 P3 S0				; Drive 3 goes backwards

; Assign extruder drive
M584 E3


; Set homing switch config
M574 X2 S1 P"!xstop"        ; Set homing switch configuration on S1 = high-end, active-low
M574 Y2 S1 P"!ystop"        ; Set homing switch configuration on S1 = high-end, active-low
M574 Z2 S1 P"!zstop"        ; Set homing switch configuration on S1 = high-end, active-low

; Set it as a linear delta
M669 K3

; Setup paneldue 5i
M575 P1 S1 B57600

M665 R215.062 L395.317:395.475:395.433 B160 H374.050		; set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0				; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 Z16 E16 I1    	; Set 16x microstepping with interpolation
M92 X200 Y200 Z200			; Set axis steps/mm

M906 X1400 Y1400 Z1400 E1400 I60	; Set motor currents (mA) and increase idle current to 60%
M84 S60                             ; Set idle timeout
M201 X12000 Y12000 Z2000 E10000        ; Accelerations (mm/s^2)
M203 X30000 Y30000 Z5000 E3600		; Maximum speeds (mm/min)
;M566 X900 Y900 Z300 E3600 P1		; Maximum instant speed changes mm/minute
M566 X300 Y300 Z300 E450 P1         ; Maximum instant speed changes mm/minute
M204 P6000 T6000                    ; Set acceleration for print and travel moves

; Configure Input shaping
M593 P"zvdd" F45

; Thermistors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700 H30 L0	; Put your own H and/or L values here to set the bed thermistor ADC correction
M308 S1 P"e0_temp" Y"thermistor" T100000 B3950 R4700 H30 L0	; 100K NTC 
;M308 S1 P"e0_temp" Y"thermistor" T100000 B4658 C6.5338987554e-08 ; 104-NT Aliexpress thermistor

M950 H0 C"bed_heat" T0      ; Set up H0 as the bed heater using T0 as the sensor
M950 H1 C"e0_heat" T1       ; Set up H1 as the extruder heater using T1 as the sensor
M140 H0                     ; Map H0 as the bed heater

; Set temperature excursion warnings
M570 H0 P20
M570 H1 P20

M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as thermistor on pin e1temp for left stepper
M308 S4	Y"drivers"  A"Drivers"  ; configure sensor 4 as temperature warning and overheat flags on the TMC2660 on Duet
M912 P0 S-3.5               ; Calibrate MCU temp

; Fan definitions
M950 F0 C"fan0"
M950 F1 C"fan1"
M950 F2 C"fan2"

; Thermostatic fan on 1 for cooling the hotend
M106 P1 T50 H1
; Thermostatic fan on 2 for cooling the board
M106 P2 H3:4 L.3 X1 B0.3 T35:70 ; set fan 2 value

; Tool definitions
M563 P0 D0 H1                       	; Define tool 0
G10 P0 S0 R0                        	; Set tool 0 operating and standby temperatures
;M92 E1392								; Based on https://www.thingiverse.com/thing:1359717; 2023/01/06
M92 E1077.1646                          ; This is the new value for the hobb-goblin extruder.  03/07/2023
;M92 E319.2005                           ; Set extruder steps per mm.  This is for the MK8 gear

; Z probe and compensation definition
M558 P8 C"^!zprobe.in" R0.4 H4 F1200 T6000 A5 S0.01	; Z probe is a piezo sensor
G31 X0 Y0 Z-0.08 P100			; Set the zprobe height and threshold
M557 R150 S20				; Probe within a radius of 150mm and mesh spacing of 20
M376 H5                     ; Taper off bed compensation after 5mm

; Configure power failure and resume
M911 S21.0 R23.0 P"G91 M83 G1 Z3 E{-global.power_fail_retract} F1000" ; Relative movement and extrusion.  Move head up and retract 2mm filament.

M208 S1 Z-0.5				; set minimum Z
T0					        ; select first hot end

M501					    ; Load any config overrides

Here is bed.g:

M561						; clear any bed transform, otherwise homing may be at the wrong height
M290 R0 S0			; Remove any baby stepping

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 4 factors, probing radius: 150, probe offset (0, 0)

; If the printer hasn't been homed, home it
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  G28

; Probe the bed and do auto calibration
G1 X0 Y0 Z10 F10000        ; go to just above the first probe point
while true
  if iterations = 5
    abort "Too many auto calibration attempts"

  G30 P0 X0.00 Y150.00 Z-99999 H0
  if result != 0
    continue
  G30 P1 X96.42 Y114.91 Z-99999 H0
  if result != 0
    continue
  G30 P2 X147.72 Y26.05 Z-99999 H0
  if result != 0
    continue
  G30 P3 X129.90 Y-75.00 Z-99999 H0
  if result != 0
    continue
  G30 P4 X51.30 Y-140.95 Z-99999 H0
  if result != 0
    continue
  G30 P5 X-51.30 Y-140.95 Z-99999 H0
  if result != 0
    continue
  G30 P6 X-129.90 Y-75.00 Z-99999 H0
  if result != 0
    continue
  G30 P7 X-147.72 Y26.05 Z-99999 H0
  if result != 0
    continue
  G30 P8 X-96.42 Y114.91 Z-99999 H0
  if result != 0
    continue
  G30 P9 X0.00 Y75.00 Z-99999 H0
  if result != 0
    continue
  G30 P10 X64.95 Y37.50 Z-99999 H0
  if result != 0
    continue
  G30 P11 X64.95 Y-37.50 Z-99999 H0
  if result != 0
    continue
  G30 P12 X0.00 Y-75.00 Z-99999 H0
  if result != 0
    continue
  G30 P13 X-64.95 Y-37.50 Z-99999 H0
  if result != 0
    continue
  G30 P14 X-64.95 Y37.50 Z-99999 H0
  if result != 0
    continue
  G30 P15 X0 Y0 Z-99999 S6
  if result != 0
    continue
  if move.calibration.initial.deviation <= 0.03
    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"

[Exerqtor]

Moved to new topic.

@balajiramani
Funny that you mention that.

I've been doing roughly 24hours of printing on 3.6.0-a2+2 now without any notable issues, but when I'm about to start print this morning (a print finished in the middle of the night, and the printer has just stood idle since that) it's acting up/crashing into the bed.

---

(The printer is a Voron Triden by the way.)

---

I start a print from the office and waits for the printer to start homing, hear it homing XY and when it goes of to home Z I hear steppers just turning and turning, so I go out and check on the printer. Turns out the rear-center Z stepper is standing still(with the carriage roughtly about where it should be), while both the front Z steppers are still going in a downwards motion about halfway along the Z-axis (I have "WobbleX" on the z-axis).

So I hit the E-stop and check out DWC and what it has to say about this:

26.7.2024, 09:58:32	Emergency Stop! Reset the controller to continue.
                        Error: Failed to home axes Z
26.7.2024, 09:58:32	Emergency stop, attemping to reconnect...
26.7.2024, 09:58:12	G28 Z
                        Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected
26.7.2024, 09:55:59	Error: G10: Probe was not triggered during probing move
                        Cancelled printing file 0:/gcodes/Automower/Rim_automower_305_0.2mm_ABS_0.4n_2h14m.gcode, print time was 0h 16m
                        Error: in file macro line 114: G1: insufficient axes homed
26.7.2024, 09:53:33	Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected
26.7.2024, 09:51:07	Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected
26.7.2024, 09:49:20	Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected
26.7.2024, 09:39:45	M32 "0:/gcodes/Automower/Rim_automower_305_0.2mm_ABS_0.4n_2h14m.gcode"
                        File 0:/gcodes/Automower/Rim_automower_305_0.2mm_ABS_0.4n_2h14m.gcode selected for printing

This all sounds somewhat odd since "Driver 0.2" is the one for the rear-center stepper, which don't seem to be doing anything weird.

Anywho, I power down the printer and manually reset the two font axis & lock the bed. Then I flip the machine around to check the wiring which all looks good. But the machine back on it's feet, power up, remove the bed locks and home the printer: all seems fine. Ok? So I jog the printer through full Z motion min-max-min with Paneldue and all seems fine.

Not seeing anything apparently borked I bring the bed up to heat again and attempt to run a tram routine (homing all axis, coarse tramming pass with 10mm dive height, then "n-number" of fine passes with 2mm dive height until the deviation is bellow 0.005mm). It runs the coarse pass, and ATTEMPTS to apply the initial adjustments:

2024-07-26 10:15:06 [warn] Leadscrew adjustments made: -2.315 2.178 1.401, points used 3, (mean, deviation) before (0.660, 1.775) after (-0.000, 0.000)

But for some reason the steppers don't move correctly so when it goes of with the second pass @ 2mm dive height it ends up scraping the nozzle allong the buildplate rather than hover 2mm above it (I've got Voron TAP, so it's not the biggest issue in the world with a slight "nozzle kiss" thankfully).

At this point I of course slap the E-stop again and go over everything once more still without finding anything wrong. And again confirming full range of motion on the Z axis and rulling out phase/connection issues to the Z-steppers as far as I can understand.

Try once more, and the exact same happens, and that's where I'm at now.

Like I opened up with saying, I've done multible trams (restarted the printer a couple times and it trams the bed first print after each reboot), without issues during the roughly 24hours of print time I have on it with 3.6.0-a2+2.
And that this happens with the printer standing idle after a print has finished is somewhat weird (roughly 3.5 hours between the night print finished and i tried starting a new one this monring).

[balajiramani]

I should add that this with a Duet 2 Wifi running 3.6.0-a2+3

[Notepad]

@Exerqtor I think @dc42 is right. This looks like under extrusion to me from weird PA artifacts or possible retraction behaviours

[Notepad]

@balajiramani Do you think it would be possible to gather some diagnostic logs? I also use a Duet 2, but on a coreXY system, I would assume a delta has a higher amount of processing requirements So it would be interesting to see what's going on behind the hood.

I personally use this process to gather the data:

• Power cycle the printer
• YAT USB connection
• M122 as a baseline diagnostic
• m111 p4 d1 b2048
• Print till failure / untill not happy (Dont Estop, only cancel as you want to save the data from the printer)
• M122 as a final diagnostic log
• Estop
• Save diaglog

[Exerqtor]

Just had time to roll back to 3.5.2 to check if fixes the problem, which it did. So it looks like it's something going on somewhere in regard to Z axis controll in 3.6.0-a2+3 @dc42.
I haven't got anything else than eventlogging going on at the time so i don't know if it's much if any usefull info one can pick up from that. If you think it might i can supply the entire log from the last couple days.

---

I'll open a new topic for the issue to keep this one from overflooding 👌

[ProteanReverie]

I have begun testing on two machines that are nearly identical, but one with a Duet 2 controlling it and one with a Duet 3 controlling it. I am very excited about the results I am seeing in print quality improvement. I have not yet encountered any noticeable issues with 3.6A2+3. Prints have run largely unattended, so if there was anything unusual that happened mid-print I could have missed it. Results off of the Duet 2 setup and Duet 3 setup look the same for the tests I have run.

Gcode was identical across both machines and both firmware versions. Input shaping is configured as ZVDD F15 on both machines. Pressure advance is enabled with a value of 0.04 on both machines.

These tests were done with a Hemera Revo 0.4HF nozzle and PETG material. I am also starting tests with a 1.0 nozzle but do not have that data yet.

---

Duet 2 setup:
Duet 2 Wi-Fi external antenna
Duex 5

Ghost text:
3.5.2 = Never used RAM 11712, free system stack 112 words
3.6A2+3 = Never used RAM 21704, free system stack 120 words

Benchy:
3.5.2 = Never used RAM 11544, free system stack 110 words
3.6A2+3 = Never used RAM 18512, free system stack 116 words

Accel test:
3.5.2 = Never used RAM 11568, free system stack 114 words
3.6A2+3 = Never used RAM 21656, free system stack 122 words

---

Duet 3 setup:
Duet 3 Mini 5+ WiFi main board in standalone mode
Duet 3 Mini 5+ CAN expansion board

Ghost text:
3.5.2 = Never used RAM 12068, free system stack 128 words
3.6A2+3 = Never used RAM 39644, free system stack 130 words

Benchy:
3.5.2 = Never used RAM 11900, free system stack 122 words
3.6A2+3 = Never used RAM 37052, free system stack 130 words

---

Here is an example of the difference in ringing/ghosting from the Ghost Text model. 3.5.2 is on bottom, 3.6A2+3 on top.

Please let me know if there is any other information I can provide that would be beneficial.

[DonStauffer]

@ProteanReverie Sorry I'm not up to speed on the latest features, but is there some particular feature that has to be enabled or configured to get that improvement in the ringing, or is it just improvements to the RFF code?

[balajiramani]

@Notepad thank you for your guidance. I was able to reproduce the issue and here are the output files.

Here is the output of M122 right after booting up with 3.6.0-alpha2+3

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-alpha.2+3 (2024-07-17 20:03:21) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX
Used output buffers: 15 of 26 (22 max)
=== RTOS ===
Static ram: 23368
Dynamic ram: 66320 of which 0 recycled
Never used RAM 28388, free system stack 178 words
Tasks: NETWORK(2,nWait 6,17.5%,222) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,81.2%,748) IDLE(0,ready,1.3%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:04 ago, cause: software
Last software reset at 2024-07-22 19:58, reason: User, Gcodes spinning, available RAM 12348, slot 0
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
MCU temperature: min 31.2, current 33.3, max 34.5
Supply voltage: min 24.1, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/24/0, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-08-02 11:27:17
Slowest loop: 150.13ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.2ms, write time 15.6ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00, mcet 0.000
Pos req/act/dcf: 114452.00/114452/0.00 114452.00/114452/0.00 114452.00/114452/0.00
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 190.46ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 5c:cf:7f:2c:25:00
Module reset reason: Turned on by main processor, Vcc 3.40, flash size 4194304, free heap 41332
WiFi IP address 192.168.1.61
Signal strength -39dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Then I ran M111, here is the output:

M111 P4 D1 B2048
Debugging enabled for modules: Move(4 - 0x1)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Gcodes(3) Heat(5) Kinematics(6) InputShaping(7) unused(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) SbcInterface(16) CAN(17) Expansion(18)

Next, I ran G32 and here is the output. Note that before it gave up, the nozzle crashed into the bed, as shown in the previous video.

G32
Error: G30: Probe was not triggered during probing move
Too many auto calibration attempts

Here is the output of M122 after the failure:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-alpha.2+3 (2024-07-17 20:03:21) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX
Used output buffers: 15 of 26 (22 max)
=== RTOS ===
Static ram: 23368
Dynamic ram: 66320 of which 0 recycled
Never used RAM 28388, free system stack 178 words
Tasks: NETWORK(2,nWait 6,17.5%,222) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,81.2%,748) IDLE(0,ready,1.3%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:04 ago, cause: software
Last software reset at 2024-07-22 19:58, reason: User, Gcodes spinning, available RAM 12348, slot 0
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
MCU temperature: min 31.2, current 33.3, max 34.5
Supply voltage: min 24.1, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/24/0, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-08-02 11:27:17
Slowest loop: 150.13ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.2ms, write time 15.6ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00, mcet 0.000
Pos req/act/dcf: 114452.00/114452/0.00 114452.00/114452/0.00 114452.00/114452/0.00
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 190.46ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 5c:cf:7f:2c:25:00
Module reset reason: Turned on by main processor, Vcc 3.40, flash size 4194304, free heap 41332
WiFi IP address 192.168.1.61
Signal strength -39dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Here is the relevant section from eventlog.txt:

power up + 00:00:00 [info] Event logging started at level warn
power up + 00:00:00 [info] Running: Duet WiFi 1.0 or 1.01: 3.6.0-alpha.2+3 (2024-07-17 20:03:21)
power up + 00:00:00 [warn] Warning: Heater 1 predicted maximum temperature at full power is 627°C
power up + 00:00:01 [warn] WiFi module started
power up + 00:00:08 [warn] WiFi module is connected to access point yablibli, IP address 192.168.1.61
power up + 00:00:09 [warn] HTTP client 192.168.1.163 login succeeded (session key 304643682)
2024-08-02 11:23:22 [warn] Date and time set at power up + 00:00:09
2024-08-02 11:24:23 [warn] HTTP client 192.168.1.163 login succeeded (session key 545348926)
2024-08-02 11:25:22 [warn] HTTP client 192.168.1.163 login succeeded (session key 219193886)
2024-08-02 11:28:48 [warn] Error: G30: Probe was not triggered during probing move
2024-08-02 11:30:01 [info] Event logging stopped
power up + 00:00:00 [info] Event logging started at level warn
power up + 00:00:00 [info] Running: Duet WiFi 1.0 or 1.01: 3.6.0-alpha.2+3 (2024-07-17 20:03:21)
power up + 00:00:00 [warn] Warning: Heater 1 predicted maximum temperature at full power is 627°C
power up + 00:00:01 [warn] WiFi module started
power up + 00:00:08 [warn] WiFi module is connected to access point yablibli, IP address 192.168.1.61
power up + 00:00:09 [warn] HTTP client 192.168.1.163 login succeeded (session key 1182103538)
2024-08-02 11:30:11 [warn] Date and time set at power up + 00:00:09

[ProteanReverie]

@DonStauffer said in RepRapFirmware 3.6.0-alpha.2 for Duet main boards available:

@ProteanReverie Sorry I'm not up to speed on the latest features, but is there some particular feature that has to be enabled or configured to get that improvement in the ringing, or is it just improvements to the RFF code?

The difference between my pictures is only an update to the RFF code, but the difference in the code pertains to how input shaping is handled. So, if you are using input shaping the update should improve things. If not, you would likely need to configure input shaping as well as applying the update. You can learn more about Input Shaping for Duet here https://docs.duet3d.com/en/User_manual/Tuning/Input_shaping

[edsped]

Haven't used my RRF printer in a few months due to it not printing as well as the Qidi. I saw this post and decided to dust off the Jubilee and load up 3.6 alpha and give it a go. I only have a few prints in but see a big improvement in print quality over the 3.5 version it replaced. So far not having an issues but have only used a single tool. Will try to do a multi color this weekend.

[ProteanReverie]

@ProteanReverie said in RepRapFirmware 3.6.0-alpha.2 for Duet main boards available:

These tests were done with a Hemera Revo 0.4HF nozzle and PETG material. I am also starting tests with a 1.0 nozzle but do not have that data yet.

Here is data from my 1.0 nozzle tests.

Duet 2

accel test
3.5.2 = Never used RAM 11736, free system stack 112 words
3.6A2+3 = Never used RAM 22616, free system stack 116 words

benchy
3.5.2 = Never used RAM 11664, free system stack 122 words
3.6A2+3 = Never used RAM 18992, free system stack 116 words

ghost text
3.5.2 = Never used RAM 11808, free system stack 114 words
3.6A2+3 = Never used RAM 22112, free system stack 114 words

---

Duet 3

accel test
3.5.2 = Never used RAM 12068, free system stack 130 words
3.6A2+3 = Never used RAM 40076, free system stack 130 words

benchy
3.5.2 = Never used RAM 11972, free system stack 128 words
3.6A2+3 = Never used RAM 36236, free system stack 130 words

ghost text
3.5.2 = Never used RAM 12092, free system stack 128 words
3.6A2+3 = Never used RAM 39788, free system stack 130 words

---

additionally, here is data from the duet 3 using a 0.4 nozzle for the accel test model, since that data wasn't ready for my prior post
3.5.2 = Never used RAM 11876, free system stack 128 words
3.6A2+3 = Never used RAM 39884, free system stack 130 words

---

I have still not encountered any noticeable issues on either the Duet 2 Wi-Fi or Duet 3 Mini 5+ setups when using 3.6A2+3.

[DonStauffer]

@dc42 I've been having major problems with bed leveling. One Z stepper either adjusts the wrong direction, or doesn't move at all. I had been doing extensive work on bed.g a few weeks ago and got it working perfectly. This problem doesn't correspond with that, but it gives a time frame which indicates to me there's something with this alpha version since that's the only major change since then. At that time I had probably run the routine 100 times in a row, working on LED issues. The actual leveling worked well.

[balajiramani]

@DonStauffer I too am having a similar problem with bed levelling. Printing with 3.6.0-alpha2+3 works fine and the input shaping is absolutely awesome! BTW, the printer I have is a delta.

The input shaping is so good that I am able to increase the accleration and jerk, without any artefacts. I was also able to drop the pressure advance value. I went from 0.21 to 0.14.

[DonStauffer]

@balajiramani I need to look into input shaping. The pics I've seen a really awesome.

[dc42]

I've put new 3.6.0 alpha RRF builds at https://www.dropbox.com/scl/fo/yc7mnauicu5vqw6yegeq7/AKnV4j8k1MCADG4VE4EIG6Y?rlkey=skjxh23i9c953yvxm2tb8qr36&dl=0. Some notes:

• The issue with bed tramming might be fixed. I don't have a suitable machine to test it on.
• Scanning Z probes are fixed (they didn't work in previous 3.6.0 alpha releases)
• Also included are 3.6.0 alpha versions of some expansion board firmware (not EXP1HCL or M23CL). You can revert to 3.5.2 versions if you have any issues with them.

See https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta#reprapfirmware-360-beta1-in-preparation for more details.