Strange bugs 3.3beta2
-
I installed 3.2.2 firmware - the errors disappeared, the mesh is working, the filament monitor is working.
The printer is printing 5 hours, the flight is normal. So pay attention to what I wrote above.
-
So it's all working fine in 3.2.2 but has problems with 3.3beta2?
If so I will remove the Solved tag as it still needs to be investigated.
-
The errors that fell on the screen and the problem with the filament sensor disappeared immediately. So yes, this is a beta issue.
As for the mesh calibration, I still do not understand. Now it seems to be working. But it somehow still worked on beta. I recalibrated many times, so I got completely confused.
-
FWIW I see those errors too with a Paneldue, so I removed it for the time being. Machine is down for other reasons right now, so I forgot to report it.
-
Next time one of you get these "Bad command" messages on PanelDue, please run M122 from the DWC console or USB. I am especially interested in what value it reports for "Aux0 errors".
-
@Dep said in Strange bugs 3.3beta2:
Another dangerous bug!
M558 K0 H5 A5 F120
Works as it shouldM558 K0 H5 A5 F120: 120
Also works as it shouldM558 K0 H5 A5 F120: 60
Broke today probe.
The bed goes up and breaks the probe. And continue to rise.I checked it several times.
What type of probe is it? Some types of probe (e.g. Smart Effector and piezo probes) don't work at low speeds.
-
Simple micro switch.
-
@dc42 I can't yet, because I installed version 3.2.2 and the messages disappeared.
-
@dc42 here it is:
24/05/2021, 22:20:04 M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3RC2 (2021-05-11 14:55:28) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956BA-NA3TN-6JTD8-3S86J-1UB2T Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 150680 Dynamic ram: 93532 of which 108 recycled Never used RAM 107016, free system stack 120 words Tasks: NETWORK(ready,445.1%,226) ETHERNET(notifyWait,1.3%,124) HEAT(delaying,0.2%,295) Move(notifyWait,0.6%,242) CanReceiv(notifyWait,0.3%,773) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.1%,341) TMC(notifyWait,128.2%,59) MAIN(running,312.5%,619) IDLE(ready,0.0%,29), total 888.3% Owned mutexes: === Platform === Last reset 03:22:59 ago, cause: software Last software reset at 2021-05-24 18:57, reason: User, GCodes spinning, available RAM 110188, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 9,9,9 Aux1 errors 0,0,0 Step timer max interval 133 MCU temperature: min 40.4, current 42.5, max 43.1 Supply voltage: min 23.3, current 23.7, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/40/40, gc cycles 0 Driver 0: position 12600, standstill, reads 41045, writes 30 timeouts 0, SG min/max 0/212 Driver 1: position -22000, standstill, reads 41046, writes 30 timeouts 0, SG min/max 0/212 Driver 2: position 4272, standstill, reads 41046, writes 30 timeouts 0, SG min/max 0/173 Driver 3: position 0, standstill, reads 41046, writes 30 timeouts 0, SG min/max 0/168 Driver 4: position 0, standstill, reads 41065, writes 11 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 41066, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-05-24 22:18:43 Slowest loop: 13.29ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.2ms, write time 2.0ms, max retries 0 === Move === DMs created 125, maxWait 8863916ms, bed compensation in use: mesh, comp offset 0.038 === MainDDARing === Scheduled moves 410, completed moves 410, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 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 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 queued 110176, send timeouts 0, received 146584, lost 0, longest wait 2ms for reply type 6018, peak Tx sync delay 284, free buffers 49 (min 48) === Network === Slowest loop: 5.93ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 1 0 0 Socket states: 5 2 2 2 2 0 0 0
-
@psychotik2k3 and i reproduce for example when doing a bed leveling from the panel due (and other stuffs)
the gcode executed is this one:; bed.g ; called to perform automatic bed compensation via G32 ; if (move.axes[2].homed=false ) echo "homing Z axis" M98 P"homez.g" G30 P0 X297 Y154 Z-99999 s-1 G30 ; home ;for bltouch G30 P0 X297 Y154 Z-99999 ; probe near a leadscrew, half way along Y axis G30 P1 X9 Y154 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors -
@psychotik2k3 and i have these errors since today when i switched from 3.2.2 stable to 3.3 RC2
allways a bad command * M409 * -
This appears related to something we just caught as well on a 3.3-rc2 machine running on a 6HC + SBC. We never saw issues like this on 3.2..
-
@oozebot i think there will be either an RC4 or the RC3 will be delayed a little
-
There will be an RC3 coming shortly.
@oozeBot @psychotik2k3 What paneldue firmware version?
-
@phaedrux I just checked and that machine is on 3.2.10.
-
@psychotik2k3 was in 3.2.10 and when having these errors i went to latest 3.2.11 and got same problems
-
@psychotik2k3 for now this is the last bug i have so far with 3.3 RC3+6
