New firmware bundle 3.2beta2

Is it not an idea to use the Mk1 eyeball while printing a small test piece to allow you to adjust the extrusion factor for that particular material on the fly ?

T3P3Tony

@deckingman the work on the can support for mini 5+ did not change the functionality on any of the expansion boards.

@T3P3Tony said in New firmware bundle 3.2beta2:

@deckingman the work on the can support for mini 5+ did not change the functionality on any of the expansion boards.

I think it should read :

The work on the can support for mini 5+ has not removed any of the current limitations on any of the expansion boards.

deckingman

@CaLviNx said in New firmware bundle 3.2beta2:

@T3P3Tony said in New firmware bundle 3.2beta2:

@deckingman the work on the can support for mini 5+ did not change the functionality on any of the expansion boards.

I think it should read :

The work on the can support for mini 5+ has not removed any of the current limitations on any of the expansion boards.

Or perhaps the release notes should say

"Supports Duet 3 Mini version 0.4 prototypes including limited CAN expansion" or "Supports Duet 3 Mini version 0.4 prototypes including CAN expansion (with limitations)." Either statement would be honest IMO.

oozeBot

@Nuramori @dc42 - the homing issues have reappeared this morning on 3.2b2. This is with a Duet3/RPi and a toolboard. Here is the relevant section from my config that has worked without issue until 3.2b2:

G1 X130 Y130 F24000			; aligns BLTouch in center of build plate
...
G30	Z-99999				; sets z-height relative to print bed
M561					; clear any bed transforms
G30 P0 X20 Y150 Z-99999			; probe midway between front and rear belt on left side
G30 P1 X280 Y150 Z-99999 S2		; probe midway between front and rear belt on right side

Now, on 3.2b2, sometimes it only probes once during G30 Z-99999. Sometimes it doesn't probe at all, then moves to the next G30 and fails. Sometimes, it makes it this far, then goes to X0 Y0 and does a probe there? That isn't even in the code..

@dc42 - There is definitely something wrong here. Please tell me how I can assist with testing to provide you better details.. I can also start another thread for the issue.

Stephen6309

@dc42 The BLTouch is doing a double tab on homing, like it does on G29 S0. Original BLTouch with a metal pin. It appears to be messing up the G31 offset. I change the offset and nothing changes. Also, when called in a macro: M117 and M118 to http, never displays the message, but it does when being called with M98. I use a macro to set the pla offset.

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-10-05b2

Using a PI 4.

For emaple, I changed the offset from 2.5 to 2.8, and the first layer thickness never changes.
PLAOffset macro:
M118 P3 S"PLAOffset"
G31 P500 X0 Y-55 Z2.8 ; Set Z probe trigger value, offset and trigger height; increase to get closer

; homeall.g
; called to home all axes
;
M98 P"/sys/homex.g"
M98 P"/sys/homey.g"
M98 P"/sys/homez.g"

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 21 2020 16:28:37 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-450 F3000 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 H1 X-405 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 21 2020 16:28:37 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-350 F3000 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 H1 Y-350 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 21 2020 16:28:37 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X200 Y200 F6000 ; go to first probe point
G30 ; home Z by probing the bed

TC

@GrodanB I have the exact same problem. Seems like the M701 causes a reboot no matter where it is used. Even when selecting a filament in DWC

Here is my diagnostics:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta2 running on Duet Ethernet 1.02 or later + DueX5
Board ID: 08DGM-917NK-F2MSW-6JKDG-3S86T-KZ5ND
Used output buffers: 1 of 24 (13 max)
=== RTOS ===
Static ram: 24028
Dynamic ram: 96364 of which 44 recycled
Exception stack ram used: 200
Never used ram: 10436
Tasks: NETWORK(ready,137) HEAT(blocked,308) DUEX(blocked,36) MAIN(running,445) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:01:36 ago, cause: software
Last software reset at 2020-10-08 18:22, reason: AssertionFailed, GCodes spinning, available RAM 10436, slot 0
Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0x20004264 Task MAIN
Stack: 0000059e 004716a8 00450849 0000000d ffffffff 20000db0 4d454144 200032a8 ffffffff 00000000 20002eb4 a5a5a5a5 004508cb 200042b0 0045e98c 20007940 0044e14f 200042cc 00446049 2000329c 200042cc 00000001 200042d4 00000000 004460b3 000000c8 200042d4
Error status: 0x00
MCU temperature: min 34.4, current 35.2, max 35.4
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-10-08 18:24:23
Cache data hit count 187762902
Slowest loop: 11.53ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.4ms, write time 13.9ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock 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
Code queue is empty.
=== Network ===
Slowest loop: 50.53ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
=== DueX ===
Read count 1, 0.62 reads/min

GrodanB

@TC
Yes, seems like the same assert as I have.

That gives me hope that this is possible to recreate at duet3d.

@dc42 If you need to run special firmware to get extended diagnosis or if there is a logfile or similar please just tell me and I test it for you. So far the failure rate for this is 100%.

Other than this the firmware works rock solid on my Cartesian printer.

Another thing, have looked in the setting up documentation and the M221 G-Code reference page. I find no note of the updated/changed behaviour. I guess this is then a minor "bug report" for the documentation.

TC

@GrodanB Yes and I can confirm it is working in 3.2beta1

Touchthebitum

Hello
I just updated my firmware and I get this when I want to upload or modify my config.g file :
Operation failed (Reason: Access to the path '/opt/dsf/sd/sys/DuetWiFiServer-1.24beta2.bin' is denied.)
Here is the general info :
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.0-beta2
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2-beta2 (2020-10-05b2)
I made update and upgrade on my Raspberry Pi too.
Where am I wrong ?
Thanks

dc42

For those of you experiencing an unexpected reboot when M701 or M702 is used, there is a binary for Duet WiFi/Ethernet to fix this at https://www.dropbox.com/s/5vhjjz4a28hu33g/Duet2CombinedFirmware.bin?dl=0.

OwenD

@dc42
This update has fixed the M701 crashes for me.

achrn

@GrodanB said in New firmware bundle 3.2beta2:

My workflow for a new filament is to do this controlled extrusion, check the error, enter the compensation, verify that the compensation is correct... if not start over until correct amount is extruded.

Isn't it just a case that at your 'check the error' stage, rather than (say) a G1 E100, you need a G1 X100 E100?

oliof

On my independent triple axis CoreXY (a v-core pro), since upgrading to 3.2beta2, the second axis is being probed three times when doing fully automated bed leveling (it probed that point only once while on 3.2b1 and earlier). Probing completes successfully.

Electronics is a duet3 v0.6 board with a toolboard and a duet3d mini IR sensor as z probe (connected to the toolboard).

files:
vcp-config.g
vcp-homeall.g
vcp_zzz.g

versions:
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-beta2 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-10-05b2

Board TOOL1LC firmware 3.2beta (2020-09-14b1)

Stephen6309

I've changed to my genuine BLTouch 3.1, that I've been using on my Duet Ethernet w/3.11. The BLTouch 3.1 does not have that double tap.

Looks like the genuine original BLTouch with metal pin doesn't work properly.

Info provided here: https://forum.duet3d.com/post/183881

Touchthebitum

@Touchthebitum
Impossible to go back. I can downgrade but I get "busy" message in DWC and sd access is denied.
Is it a known issue or I missed something ?

Here is my diagnostic log :

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9FJ-3S86S-983QD
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 157532
Dynamic ram: 135804 of which 44 recycled
Exception stack ram used: 272
Never used ram: 99564
Tasks: Linux(ready,36) HEAT(blocked,296) CanReceiv(blocked,947) CanSender(blocked,371) CanClock(blocked,353) TMC(blocked,51) MAIN(running,1127) IDLE(ready,20)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:07:20 ago, cause: software
Last software reset at 2058-01-24 11:14, reason: HardFault imprec, none spinning, available RAM 187280, slot 2
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x0440f803 BFAR 0x00000000 SP 0x20418438 Task MAIN
Stack: 0000004c 204184e4 204186ac 204186c4 20418518 204187ec 00416198 81000000 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Error status: 0x00
MCU temperature: min 30.5, current 31.0, max 31.3
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Driver 0: position 0, standstill, reads 64862, writes 18 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 64862, writes 18 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 64862, writes 18 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 64863, writes 18 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 64863, writes 18 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 64871, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-10-11 12:56:13
Slowest loop: 147.69ms; fastest: 0.22ms
=== 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 ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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 ready with "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
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages sent 1729, send timeouts 1729, longest wait 0ms for type 0, free CAN buffers 48
=== SBC interface ===
State: 0, failed transfers: 1
Last transfer: 19ms ago
RX/TX seq numbers: 13846/13847
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0-beta2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 31.95

Phaedrux

@Touchthebitum How are you trying to downgrade?

Touchthebitum

@Phaedrux
I upload the previous firmware...

Touchthebitum

It's ok now. I had to reflash my Raspberry Pi4 and make all the procedure and it worked.
I don't have sd card access denied anymore.

JuJuDelta

FYI I have managed to boot the RPi4 straight from SSD on USB3, no pesky uSD cards involved at all.