Stutter on long curves - bitrate?
-
hello all together,
these days I started printing diffent kind of planters for a shop.
When printing long curves, a stuttering was shown on the wall / long curves. Infill where just straight lines, which is not a Problem.My Printer is quiet big ( 1m3 print volume) and it´s driven by closed loop system (x and double motor y-axis).
I think the rj11 cable are about 10 meter long, if the cable to the toolboards also counts. So i though it´s a good Idea to increase the bitrate to 2mb. That was not working, I couldn´t connect all boards together, after conceting 2 or 3 the can bus blinking rapidly.
Other way around I dicreased to 0.5mb and the stuttering is still there. May a bit more?- I´m not sure.
So my question is, If a higher bitrate is recommended when having long rj11 system with closed loop motors?
I have to start somewhere....
I would be very happe, if you have some ideas.; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Aug 02 2021 16:15:35 GMT+0200 (Mitteleuropäische Sommerzeit) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"BlackFlamingo" ; set printer name M952 B0 S500 M552 S1 M587 S"AndroidAPebc3_EXT" P"hhhhhhhh" G4 S4 M574 C1 S3 M574 C0 Z0 M915 P0.5 C S0 F0 R1 ; Drives ;closed loop M569.1 P20.0 T2 C1000 E12:8 R150 I0 D0.015 H100 ; Configure the 1HCL board at CAN address.20quadrature encoder 128 steps/motor full M569.1 P21.0 T2 C1000 E12:8 R150 I0 D0.015 H100 ; Configure the 1HCL board at CAN address.21quadrature encoder 128 steps/motor full step. M569.1 P30.0 T2 C1000 E12:8 R120 I0 D0.015 H100 ; Configure the 1HCL board at CAN address.21quadrature encoder 128 steps/motor full step. M569 P20.0 D4 S0 ; Configure the motor on the 1HCL at can address 20 as being in closed-loop drive mode (D4) and not reversed (S1) M569 P21.0 D4 S1 ; Configure the motor on the 1HCL at can address 21 as being in closed-loop drive mode (D4) and not reversed (S1) M569 P30.0 D4 S1 ; Configure the motor on the 1HCL at can address 21 as being in closed-loop drive mode (D4) and not reversed (S1) Other drives; open loop; M569 P0.0 S0 ; physical drive 0.0 goes forwards M569 P0.1 S0 ; physical drive 0.2 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes forwards M569 P0.3 S0 M569 P0.5 S0 M569 P100.0 S0 ; physical drive 0.2 goes forwards M569 P110.0 S1 ; physical drive 0.2 goes forwards M569 P111.0 S1 ; physical drive 0.2 goes forwards M584 X30.0 Y20.0:21.0 Z0.0:0.1:0.2:0.3 C0.5 E100.0:110.0:111.0 ; set drive mapping M350 X32 Y32 Z16 E16:16:16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00:80.00 Z640.00 C91.022 E397.00:690.00:400.00 ; set steps per mm M566 X600.00 Y600.00 Z300.00 C3000 E600.00:600.00:600.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z300.00 C10000 E24000.00:24000.00:24000.00 ; set maximum speeds (mm/min) M201 X1600.00 Y1600.00 Z2000.00 C550 E8000.00:8000.00:8000 ; set accelerations (mm/s^2) M906 X1700 Y1700 Z2300:2300:2300:2300 C600 E1000:1000:600 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S300 ; Set idle timeout M671 X-140:-140:990:990 Y-140:990:990:-140 S20 ; leadscrews at front left1 and n´back2. back rigth3 and front4 ; Axis Limits M208 X0 Y-100 Z0 S1 ; set axis minima M208 X860 Y860 Z850 S0 ; set axis maxima ; Endstops M574 X2 S1 P"^30.io1.in" ; configure active-high endstop for high end on X via pin ^io3.in M574 Y2 S1 P"^20.io1.in+21.io1.in" ; configure active-high endstop for high end on Y via pin ^io1.in M574 Z1 S1 P"^0.io2.in" ; configure active-high endstop for high end on Y via pin ^io1.in ; Z probe M558 K0 P5 C"0.io1.in" H8 F2000 I0 T5000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height; Z probe M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters M557 X50:700 Y50:700 S65 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 R0.243 C586.2 D33.87 S1.00 V0 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 M143 H0 S120 M308 S1 P"100.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as PT1000 on pin 121.temp0 M950 H1 C"100.out0" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 R1.553 C487.8 D10.35 S1.00 V0 ; disable bang-bang mode for heater and set PWM limit M143 H1 S250 M308 S2 P"110.temp0" Y"pt1000" T100000 B4138 ; configure sensor 2 as PT1000 on pin 121.temp0 M950 H2 C"2.out0" T2 ; create nozzle heater output on out1 and map it to sensor 2 M307 H2 B0 R1.553 C487.8 D10.35 S1.00 V0 ; disable bang-bang mode for heater and set PWM limit M143 H2 S250 ; set temperature limit for heater 1 to 250C M308 S3 P"111.temp0" Y"thermistor" T100000 B4138 ; configure sensor 2 as PT1000 on pin 121.temp0 M950 H3 C"111.out0" T3 ; create nozzle heater output on out1 and map it to sensor 3 M307 H3 B0 R1.553 C487.8 D10.35 S1.00 V0 ; disable bang-bang mode for heater and set PWM limit M143 H3 S280 ; set temperature limit for heater 1 to 250C ; set temperature limit for heater 1 to 250C ; Fans M950 F0 C"100.out2" Q500 ; create fan 0 on pin 100.out1 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M563 P0 D0 H1 ; tool uses extruder 0, heater 1 M950 F1 C"100.out1" Q500 ; create fan 1 on pin 100.out2 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M563 P0 D0 H1 F1 ; tool uses extruder 0, heater 1 M950 F2 C"110.out1" Q500 ; create fan 2 on pin 101.out1 and set its frequency M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off M563 P1 D1 H2 ; tool uses extruder 0, heater 2 M950 F3 C"110.out2" Q500 ; create fan 3 on pin 101.out2 and set its frequency M106 P3 S0.8 H2 T45 ; set fan 3 value. Thermostatic control is turned on M563 P1 D1 H2 F2 ; tool uses extruder 1, heater 2 M950 F4 C"111.out2" Q500 ; create fan 3 on pin 101.out2 and set its frequency M106 P4 S1 H-1 ; set fan 3 value. Thermostatic control is turned on M563 P2 D2 H3 F3 ; tool uses extruder 1, heater 2 M950 F5 C"111.out1" Q500 ; create fan 3 on pin 101.out2 and set its frequency M106 P5 S0.8 H3 T45 ; set fan 3 value. Thermostatic control is turned on M563 P2 D2 H3 F3 ; tool uses extruder 1, heater 2 ; Magnete M950 F8 C"0.out8" Q500 CMagnet0 ; create magnet 0 on pin out9 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F9 C"0.out7" Q500 CMagnet1 ; create magnet 0 on pin out9 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F10 C"21.out0" Q500 CMagnet2 ; create magnet 0 on pin out9 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F11 C"21.out1" Q500 CMagnet3 ; create magnet 0 on pin out9 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X-9 Y-39 Z-4.1 ; set initial tool 0 active and standby temperatures to 0C G10 P0 R0 S0 M563 P1 D1 H2 F3 ; define tool 1 ; set initial tool 0 active and standby temperatures to 0C G10 P1 X-8.85 Y-39.25 Z-4.104 G10 P1 R0 S0 M563 P2 D2 H3 F4 ; define tool 2 ; set initial tool 0 active and standby temperatures to 0C G10 P2 X-8.85 Y-39.25 Z-24.104 G10 P2 R0 S0 I´ll show a video.. ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossR.G.
-
@IndeX4D set the can bitrate back to 1MB for now.
If you are getting stuttering on curves, try increasing the jerk of the XY (and Z if you are using a mesh) to a higher values.
When you are getting stuttering send M122 and post the results here.
-
@IndeX4D If the effect is just on curves, then it's more likely that the problem is due to too low a jerk setting (instantaneous speed change) - especially extruder jerk. Try setting that really high, like 3000 (it'll do no harm) and increase XY jerk to 900 or 1200 and see what effect that has.
Edit - Tony beet me to it
-
This post is deleted! -
@T3P3Tony mesh is disabled, extruder jerk to 6000 has not changed behaviour.
Try higher jerk for x and z, now. Is 10mm/s not enough?
Edit: Even a jerk of 1200 would be no solution. That´s causing other problems.... but I´ll give it a try.I´ll come back asap. Thanks for the fast replies!
Edit 2.0
:
May SD-Card is pretty much full.
-
@IndeX4D free space 7.78GB? sounds alright. lets see the M122 for the mainboard when the stuttering is occuring and also the M122 for boards 30, 20 and 21
-
@T3P3Tony let ne just test print with new Jerks. Changing back to default bitrate took a while....
-
@T3P3Tony
It´s not the jerk - still stutter.
M122 is coming...
-
m122 b0 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5beta2 (2023-02-08 17:43:01) running on Duet 3 MB6HC v1.01 (standalone mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46R-9U2AD Used output buffers: 1 of 40 (40 max) Error in macro line 15 while starting up: No WiFi interface available === RTOS === Static ram: 154344 Dynamic ram: 119384 of which 0 recycled Never used RAM 68072, free system stack 128 words Tasks: NETWORK(ready,29.4%,194) ETHERNET(notifyWait,0.2%,559) HEAT(notifyWait,0.0%,321) Move(notifyWait,10.8%,214) CanReceiv(notifyWait,0.1%,771) CanSender(notifyWait,0.5%,325) CanClock(delaying,0.0%,340) TMC(notifyWait,8.1%,56) MAIN(running,50.9%,446) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:33:06 ago, cause: software Last software reset at 2023-03-24 18:35, reason: User, Gcodes spinning, available RAM 69384, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 269 MCU temperature: min 41.5, current 41.9, max 41.9 Supply voltage: min 23.8, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/80/16, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 488, reads 45589, writes 0 timeouts 0 Driver 1: standstill, SG min 0, mspos 488, reads 45588, writes 0 timeouts 0 Driver 2: standstill, SG min 0, mspos 488, reads 45588, writes 0 timeouts 0 Driver 3: standstill, SG min 0, mspos 488, reads 45588, writes 0 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 45588, writes 0 timeouts 0 Driver 5: standstill, SG min n/a, mspos 440, reads 45588, writes 0 timeouts 0 Date/time: 2023-03-24 19:08:50 Slowest loop: 8.30ms; fastest: 0.06ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.6ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 34, maxWait 627ms, bed compensation in use: none, comp offset 0.000 next step interrupt due in 2156 ticks, disabled === DDARing 0 === Scheduled moves 65387, completed 65327, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 Heater 2 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is ready with "m122 b0" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 3 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 File2 is idle in state(s) 0, sync state 1 Queue2 is idle in state(s) 0 Q0 segments left 26, axes/extruders owned 0x40000007 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 31229, received 3638, lost 0, boc 0 Longest wait 2ms for reply type 6029, peak Tx sync delay 461, free buffers 50 (min 16), ts 239/239/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 13.45ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 2 of 8 = Ethernet = State: active Error counts: 0 0 0 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === Multicast handler === Responder is inactive, messages received 0, responses 0 -
m122 b30 Diagnostics for board 30: Duet EXP1HCL firmware version 3.5beta2 (2023-02-08 15:50:31) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 51496, free system stack 173 words Tasks: Move(notifyWait,0.3%,110) HEAT(notifyWait,0.0%,78) CanAsync(notifyWait,0.0%,53) CanRecv(notifyWait,0.2%,42) CanClock(notifyWait,0.0%,69) TMC(notifyWait,48.0%,346) CLSend(notifyWait,0.0%,152) MAIN(running,49.6%,407) IDLE(ready,0.0%,30) AIN(notifyWait,1.9%,265), total 100.0% Last reset 00:33:44 ago, cause: software Last software reset data not available Closed loop enabled: yes, pre-error threshold: 12.00, error threshold: 8.00, encoder type rotaryQuadrature, position 41370 Encoder reverse polarity: yes, raw count 24167 Tuning mode: 0, tuning error: 0, collecting data: no Control loop runtime (us): min=12, max=41, frequency (Hz): min=9868, max=15306 Driver 0: pos 132268, 160.0 steps/mm,ok, SG min n/a, mspos 948, reads 0, writes 49516 timeouts 0, steps req 3485420 done 0 Moves scheduled 70382, completed 70361, in progress 1, hiccups 0, step errors 0, maxPrep 128, maxOverdue 3, maxInc 1, mcErrs 0, gcmErrs 0 Peak sync jitter -5/17, peak Rx sync delay 208, resyncs 0/0, next step interrupt due in 3 ticks, enabled VIN voltage: min 24.2, current 24.3, max 24.3 V12 voltage: min 12.2, current 12.3, max 12.3 MCU temperature: min 32.4C, current 38.7C, max 38.7C Last sensors broadcast 0x00000000 found 0 128 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 5664, send timeouts 0, received 53704, lost 0, free buffers 37, min 36, error reg 20000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 333, adv 34395/82094 -
m122 b21 Diagnostics for board 21: Duet EXP1HCL firmware version 3.5beta2 (2023-02-08 15:50:31) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 51320, free system stack 173 words Tasks: Move(notifyWait,0.2%,110) HEAT(notifyWait,0.0%,78) CanAsync(notifyWait,0.0%,53) CanRecv(notifyWait,0.2%,42) CanClock(notifyWait,0.0%,69) TMC(notifyWait,48.5%,346) CLSend(notifyWait,0.0%,152) MAIN(running,49.1%,407) IDLE(ready,0.0%,30) AIN(notifyWait,1.9%,265), total 100.0% Last reset 00:33:42 ago, cause: software Last software reset data not available Closed loop enabled: yes, pre-error threshold: 12.00, error threshold: 8.00, encoder type rotaryQuadrature, position 43300 Encoder reverse polarity: yes, raw count 22235 Tuning mode: 0, tuning error: 0, collecting data: no Control loop runtime (us): min=12, max=40, frequency (Hz): min=10000, max=15306 Driver 0: pos 132383, 160.0 steps/mm,ok, SG min n/a, mspos 444, reads 0, writes 31928 timeouts 0, steps req 3538630 done 0 Moves scheduled 70151, completed 70130, in progress 1, hiccups 0, step errors 0, maxPrep 117, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter -2/16, peak Rx sync delay 205, resyncs 0/0, next step interrupt due in 21 ticks, enabled VIN voltage: min 24.6, current 24.7, max 24.8 V12 voltage: min 12.2, current 12.2, max 12.2 MCU temperature: min 31.0C, current 34.6C, max 35.0C Last sensors broadcast 0x00000000 found 0 110 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 8788, send timeouts 0, received 54034, lost 0, free buffers 37, min 36, error reg 10000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 333, adv 35010/82643 -
m122 b20 Diagnostics for board 20: Duet EXP1HCL firmware version 3.5beta2 (2023-02-08 15:50:31) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 51496, free system stack 172 words Tasks: Move(notifyWait,0.2%,110) HEAT(notifyWait,0.0%,78) CanAsync(notifyWait,0.0%,53) CanRecv(notifyWait,0.1%,42) CanClock(notifyWait,0.0%,69) TMC(notifyWait,47.8%,346) CLSend(notifyWait,0.0%,152) MAIN(running,49.8%,407) IDLE(ready,0.0%,30) AIN(notifyWait,2.0%,265), total 100.0% Last reset 00:33:41 ago, cause: software Last software reset data not available Closed loop enabled: yes, pre-error threshold: 12.00, error threshold: 8.00, encoder type rotaryQuadrature, position -35748 Encoder reverse polarity: yes, raw count 35748 Tuning mode: 0, tuning error: 0, collecting data: no Control loop runtime (us): min=12, max=42, frequency (Hz): min=10000, max=15306 Driver 0: pos 144227, 160.0 steps/mm,ok, SG min n/a, mspos 764, reads 0, writes 48368 timeouts 0, steps req 4052086 done 0 Moves scheduled 69892, completed 69871, in progress 1, hiccups 0, step errors 0, maxPrep 117, maxOverdue 1, maxInc 1, mcErrs 0, gcmErrs 0 Peak sync jitter -3/16, peak Rx sync delay 210, resyncs 0/0, next step interrupt due in 17 ticks, enabled VIN voltage: min 24.6, current 24.6, max 24.7 V12 voltage: min 12.1, current 12.1, max 12.1 MCU temperature: min 31.9C, current 36.1C, max 36.3C Last sensors broadcast 0x00000000 found 0 187 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 6662, send timeouts 0, received 55645, lost 0, free buffers 37, min 36, error reg 10000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 333, adv 34737/82358 -
Did this start happening after updating to 3.5 Beta 2? Or same thing on 3.4.5?
-
@Phaedrux
It has been starting in the last time somehow. I've not printing curvy things in last time. So I can't say it 100%. But it could be.
Strange - other printer is printing with 3.5beta2 also and has no problems. Just smaller nozzles at work and there are no stutter in (smaller) curves.https://forum.duet3d.com/topic/22746/cura-uses-concentric-circles-to-fill-will-be-a-layer-of-lag
May I thought about this.... I have a new extruder with 100mm3 maximum flow so the flow rate has been increased from 20mm3 to almost 80mm3.
-
@IndeX4D ok, now start a print running (you can remove the filament to avoid wasting it) and when you have had that stuttering happening for a while, then send the M122s as above.
I am looking to see if there are any issues reported on the CAN communications, or driver hiccups or buffer underruns etc.
if you let it stutter for a while then it will rule out a single hiccup etc.
-
@T3P3Tony
The diagnostics above are made by a print when some stutter happened.... or do I need to print for a longer time? -
@IndeX4D it does not look like you were printing a file. I suggest pritning one that stutters a lot and have it stuttering for at least (say) 100 stutters then send the M122 9while its still printing).
If that doe snot show up anything in the CAN communication, hiccups or buffers then the next thing to try is temporarily switch the axes into open loop mode
-
@T3P3Tony
I added a M413 S0 to stop power loss like somebody said. was not working. may that´s the reason it looked like it was not printing.
I´ll start a print, now. -
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5beta2 (2023-02-08 17:43:01) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3S46R-9U2AD
Used output buffers: 3 of 40 (40 max)
Error in macro line 15 while starting up: No WiFi interface available
=== RTOS ===
Static ram: 154344
Dynamic ram: 119384 of which 0 recycled
Never used RAM 68072, free system stack 128 words
Tasks: NETWORK(ready,31.1%,194) ETHERNET(notifyWait,0.2%,559) HEAT(notifyWait,0.0%,321) Move(notifyWait,1.8%,214) CanReceiv(notifyWait,0.1%,771) CanSender(notifyWait,0.1%,325) CanClock(delaying,0.0%,340) TMC(notifyWait,8.4%,56) MAIN(running,58.2%,446) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:33:42 ago, cause: software
Last software reset at 2023-03-24 18:35, reason: User, Gcodes spinning, available RAM 69384, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 271
MCU temperature: min 39.8, current 41.1, max 42.0
Supply voltage: min 23.7, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/104/40, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 488, reads 4467, writes 4 timeouts 0
Driver 1: standstill, SG min 0, mspos 488, reads 4467, writes 4 timeouts 0
Driver 2: standstill, SG min 0, mspos 488, reads 4467, writes 4 timeouts 0
Driver 3: standstill, SG min 0, mspos 488, reads 4467, writes 4 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 4471, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 440, reads 4468, writes 2 timeouts 0
Date/time: 2023-03-24 20:09:25
Slowest loop: 54.15ms; fastest: 0.05ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 4.3ms, write time 146.2ms, max retries 0
=== Move ===
DMs created 125, segments created 34, maxWait 3037708ms, bed compensation in use: none, comp offset 0.000
next step interrupt due in 1472 ticks, disabled
=== DDARing 0 ===
Scheduled moves 50125, completed 50065, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== DDARing 1 ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 2 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 3
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
File2 is idle in state(s) 0, sync state 1
Queue2 is idle in state(s) 0
Q0 segments left 3, axes/extruders owned 0x40000007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 417508, received 276475, lost 0, boc 0
Longest wait 5ms for reply type 6024, peak Tx sync delay 655, free buffers 50 (min 16), ts 18180/18180/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 147.44ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0 -
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5beta2 (2023-02-08 17:43:01) running on Duet 3 MB6HC v1.01 (standalone mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46R-9U2AD Used output buffers: 1 of 40 (40 max) Error in macro line 15 while starting up: No WiFi interface available === RTOS === Static ram: 154344 Dynamic ram: 119384 of which 0 recycled Never used RAM 68072, free system stack 128 words Tasks: NETWORK(ready,28.8%,194) ETHERNET(notifyWait,0.3%,559) HEAT(notifyWait,0.0%,321) Move(notifyWait,12.6%,214) CanReceiv(notifyWait,0.1%,771) CanSender(notifyWait,0.5%,325) CanClock(delaying,0.0%,340) TMC(notifyWait,8.0%,56) MAIN(running,49.6%,446) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 01:50:56 ago, cause: software Last software reset at 2023-03-24 18:35, reason: User, Gcodes spinning, available RAM 69384, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Step timer max interval 252 MCU temperature: min 41.5, current 41.7, max 41.8 Supply voltage: min 23.7, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/104/40, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 488, reads 10678, writes 0 timeouts 0 Driver 1: standstill, SG min 0, mspos 488, reads 10676, writes 0 timeouts 0 Driver 2: standstill, SG min 0, mspos 488, reads 10676, writes 0 timeouts 0 Driver 3: standstill, SG min 0, mspos 488, reads 10677, writes 0 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 10677, writes 0 timeouts 0 Driver 5: standstill, SG min n/a, mspos 440, reads 10677, writes 0 timeouts 0 Date/time: 2023-03-24 20:26:39 Slowest loop: 9.70ms; fastest: 0.09ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.5ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 34, maxWait 165ms, bed compensation in use: none, comp offset 0.000 next step interrupt due in 2125 ticks, disabled === DDARing 0 === Scheduled moves 225820, completed 225760, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 Heater 2 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 3 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 File2 is idle in state(s) 0, sync state 1 Queue2 is idle in state(s) 0 Q0 segments left 58, axes/extruders owned 0x40000007 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 11311, received 1164, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 292, free buffers 50 (min 18), ts 77/77/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 12.66ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 2 of 8 = Ethernet = State: active Error counts: 0 0 0 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === Multicast handler === Responder is inactive, messages received 0, responses 0Slowest loop 12.66ms?
Is this right?
When having 12 in M569.1
