New firmware bundle 3.2beta2
-
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.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42
This update has fixed the M701 crashes for me. -
@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?
-
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.gversions:
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-05b2Board TOOL1LC firmware 3.2beta (2020-09-14b1)
-
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
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 -
@Touchthebitum How are you trying to downgrade?
-
@Phaedrux
I upload the previous firmware... -
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. -
FYI I have managed to boot the RPi4 straight from SSD on USB3, no pesky uSD cards involved at all.
-
@JuJuDelta said in New firmware bundle 3.2beta2:
FYI I have managed to boot the RPi4 straight from SSD on USB3, no pesky uSD cards involved at all.
Very interesting!!
-
@BoA said in New firmware bundle 3.2beta2:
I just updated PanelDue, DWC and RRF to latest betas.
I am afraid the issue with not refreshing temps on Panel during wait on M116 is still there.
Duet3 standalone.
Thanks again for reporting. This will be finally fixed in the next release of RRF.
-
This post is deleted!
