Topics created by TypQxQ

@TypQxQ that's a long write time on the SD card. I would suggest refreshing the SD card (don't forget to back everything up) or replace the SD card for a newer one

@TypQxQ if the 3.3V regulator is getting hot then most likely another component has failed. Is anything else getting hot? Check the SD card the WiFi module and the microcontroller in particular.

@dc42 Thank you! That did it!

@typqxq
If I understood it right, the multi-gcode streaming feature has the goal to extend look-ahead and allow better temp control for toolchangers. (mainly switching the heaters ON, before toolchange is due)
I guess, this would also help you with your problem?

Unfortunately it'll be RRF3.5 until we see this feature.

however I would check the mechanics from the belts to the bearings and the frame, from the graph you can see many peaks of great value, which suggests a significant mechanical instability ... I'll show you my graph by X axisCattura.JPG

@t3p3tony Thankyou, I missed that when checking the code for it....

@typqxq this is a known issue: heater faults on tool or expansion boards shut down the heater and report their status as "fault", but RRF does not pause the print. This is one of the few remaining items on my TODO list before release 3.4.0 is considered complete.

@typqxq said in Unhandled heater runaway due to a faulty heatblock:

and the heater cartridge is electrically connected to the heatsink.

What's the point in that? Better thermal conductivity? Seems to me, the new hotend isn't compatible with the major market...

@maxgyver said in [3.3RC3] Missed stepps or overdue moves:

@dc42 I had the same problems described by @TypQxQ after upgrading from RC3.2 to RC3.3.
The new binaries fixed the issue.

Cheers
Max

Thanks for confirming that!

I confirm this is fixed in 3.3RC3.

Thank you, here is the gcode file: https://we.tl/t-itUE75F1lq
The config files are here: https://we.tl/t-AeXDiQaFII

@ctilley79 said in 3.3b1CAN timeout resets itself?:

I may have screwed this up. So It's best to power the 3HC from the 6HC Mainboard instead of running a separate wire from the PSU? Why?

It only matters if you are powering a high-powered bed heater directly from the Duet and you have long wires between the Duet and the PSU. Under those conditions, the changes in ground voltage caused by the bed heater being switching on/off rapidly with PWM can affect the CAN communication.

After Canceling the print I tried restarting it but it says it is already printing.

2021-01-17 00:25:02 M32 "0:/gcodes/Front Stepper v5.2 - Bottom.gcode" Error: M32: Cannot set file to print, because a file is already being printed 2021-01-17 00:20:49 Cancelled printing file 0:/gcodes/Front Stepper v5.2 - Bottom.gcode, print time was 0h 19m

Diag after trying to restart:

=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKDD-3SJ6L-TB62G Used output buffers: 1 of 40 (16 max) === RTOS === Static ram: 149788 Dynamic ram: 65316 of which 152 recycled Never used RAM 143576, free system stack 128 words Tasks: Linux(blocked,71) HEAT(blocked,271) CanReceiv(blocked,809) CanSender(blocked,341) CanClock(blocked,352) TMC(blocked,19) MAIN(running,720) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 06:48:26 ago, cause: software Last software reset at 2021-01-16 17:37, reason: User, none spinning, available RAM 143816, slot 0 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 45.4, current 45.6, max 45.8 Supply voltage: min 31.9, current 31.9, max 32.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 Driver 0: position 159870, standstill, reads 31841, writes 0 timeouts 0, SG min/max not available Driver 1: position 0, standstill, reads 31841, writes 0 timeouts 0, SG min/max not available Driver 2: position 9282, standstill, reads 31841, writes 0 timeouts 0, SG min/max not available Driver 3: position 0, standstill, reads 31837, writes 4 timeouts 0, SG min/max 0/152 Driver 4: position 0, standstill, reads 31837, writes 4 timeouts 0, SG min/max 0/201 Driver 5: position 0, standstill, reads 31836, writes 4 timeouts 0, SG min/max 0/124 Date/time: 2021-01-17 00:25:32 Slowest loop: 77.73ms; fastest: 0.06ms === 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 === DMs created 125, maxWait 2861714ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 2, completed moves 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 Heater 0 is on, I-accum = 0.1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "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 queued 2053, send timeouts 0, received 6149, lost 0, longest wait 1ms for reply type 6013, free buffers 48 === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 2343/3448 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2c8a8 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0 File: Finishing macro /sys/custom/Conditional_HomeAll.g, started by G0 Z5 F5000 ; Ensure nozzle is at 5mm over the bed > Next stack level Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 3160.22 Maximum length of RX/TX data transfers: 3720/1688 File /opt/dsf/sd/gcodes/Front Stepper v5.2 - Bottom.gcode is selected, processing, paused, cancelled

DSF:

[debug] IPC#938: Received command SimpleCode [debug] Waiting for execution of M32 "0:/gcodes/Front Stepper v5.2 - Bottom.gcode" [debug] Processing M32 "0:/gcodes/Front Stepper v5.2 - Bottom.gcode" [debug] Waiting for finish of M32 "0:/gcodes/Front Stepper v5.2 - Bottom.gcode" => Error: Cannot set file to print, because a file is already being printed [debug] Completed M32 "0:/gcodes/Front Stepper v5.2 - Bottom.gcode" => Error: M32: Cannot set file to print, because a file is already being printed

I have reverted to the files I attached in my post from "31 Dec 2020, 00:24".

I had double checked the version. I couldn't attach debug info because the post exceeded the allowed length.

=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKDD-3SJ6L-TB62G Used output buffers: 1 of 40 (15 max) === RTOS === Static ram: 149788 Dynamic ram: 64700 of which 112 recycled Never used RAM 144232, free system stack 154 words Tasks: Linux(ready,71) HEAT(blocked,295) CanReceiv(blocked,801) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1120) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 01:36:39 ago, cause: software Last software reset at 2021-01-05 21:57, reason: User, none spinning, available RAM 144336, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 39.4, current 39.8, max 40.4 Supply voltage: min 31.9, current 31.9, max 32.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 Driver 0: position 0, standstill, reads 13972, writes 0 timeouts 0, SG min/max not available Driver 1: position 0, standstill, reads 13972, writes 0 timeouts 0, SG min/max not available Driver 2: position 0, standstill, reads 13972, writes 0 timeouts 0, SG min/max not available Driver 3: position 0, standstill, reads 13972, writes 0 timeouts 0, SG min/max not available Driver 4: position 0, standstill, reads 13972, writes 0 timeouts 0, SG min/max not available Driver 5: position 0, standstill, reads 13972, writes 0 timeouts 0, SG min/max not available Date/time: 2021-01-05 23:34:00 Slowest loop: 93.48ms; fastest: 0.06ms === 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 === DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 3, completed moves 3, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 doing "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 queued 18738, send timeouts 0, received 56197, lost 0, longest wait 1ms for reply type 6036, free buffers 48 === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 59729/59729 SPI underruns 0, overruns 0 Number of disconnects: 2, IAP RAM available 0x2c8a8 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 35.62 Maximum length of RX/TX data transfers: 3364/292 pi@qTC:~ $ sudo /opt/dsf/bin/DuetControlServer -l debug Duet Control Server v3.2.0 Written by Christian Hammacher for Duet3D Licensed under the terms of the GNU Public License Version 3

If you run this code you can run the code above yourself and see.

M950 J3 C"0.io3.in" ; Use the input pin on io3 on the main board as carriage coupling check. M581 P3 T4 S1 ; Use triggers as info.(Run Trigger4.g)

I included a fix for this in RC2 so it should no longer be a problem.

@TypQxQ said in RRF 3.2RC1 - SPI task faulted on abort comand:

Thanks, I can confirm that. It will be fixed in RC2.

@chrishamm Thank you!
Please also note that the log level of S1 and S2 are reversed to what is stated in Gcode documentation.

@TypQxQ Yes, those changes have been merged into the new beta as well.

Yes, the documentation was out of date. I have corrected it. Thanks for pointing this out.

Enabling debugging for all modules is no longer useful because of the very large amount of output it produces.