RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0 released

tobias_munich

SBC Version
Tool: Heater Error after a couple of minutes print. I tried 3 prints, any every print fails with the following message

Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

gtj0

@tobias_munich said in RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0 released:

SBC Version
Tool: Heater Error after a couple of minutes print. I tried 3 prints, any every print fails with the following message

Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

Can you start a new thread for this issue? I want to ask some questions but don't want to clog this thread up.

ChrisP

D3 + Pi4.
I haven't found a 100% repeatable way of replicating this yet, but for the last 5 prints I've done the printer just hangs for ~5-10 seconds mid-print. Running the same file twice has it stop at different places. Only every seems to do it once per print, and always happens within the first minute or so of the print.
During this time data stops scrolling in DCS when in debug mode but doesn't show any error. DWC also stops updating - can be noticed by temperature values not updating. I've never had this before on this system and the only change is applying latest update bundle.

Will start a new thread if I can find a means to easily reproduce issue or if others report similar issue.
edit: following other comments, thread started here: RRF 3.01-RC8/DWC 2.1.3/DSF 2.0.0: Mid-print hanging

gtj0

@ChrisP Turn off debug mode
https://github.com/chrishamm/DuetSoftwareFramework/issues/119

gtjoseph created this issue in chrishamm/DuetSoftwareFramework

closed DCS 2.0.0 Occasional hangs during printing #119

ChrisP

@gtj0 said in RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0 released:

@ChrisP Turn off debug mode
https://github.com/chrishamm/DuetSoftwareFramework/issues/119

The first 4 time it happened, it was off.
I turned it on to see if there was an obvious error/warning, but I wasn't aware of the issue you pointed to so will stop using it for now. However, having is running is not the reason the first 4 prints stopped. For me, so far, in a 20 minute print it has only ever happens once per print and within the first minute or so.

gtj0

@ChrisP Gotcha. I'd open a new thread anyway. I want to ask a few questions as well.

dc42

PanelDue firmware release 1.24 is now available at https://github.com/dc42/PanelDueFirmware/releases/tag/1.24. This provides improved compatibility with Duet 3 systems running with attached SBC. However, there are still some issues:

If a file or macro list is longer than about 8 files (depending on how long the filenames are) then PanelDue is unable to retrieve the list;
It is not possible to enter subfolders from PanelDue;
When you touch a filename in the file list displayed by PanelDue, the displayed file information may be incomplete. In particular, the file size may be displayed as zero.

We expect to resolve these issues in the stable release of RRF 3.01+DSF.

Dr_Ju_Ju

Have the default settings for Tuning the bed changed, as I'm trying to M303 the bed for 125 degrees, but it doesn't allow anything above 80 ??

Dr_Ju_Ju

I re-flashed it & now its at least letting me get to 125, but I'd really like to get to 150.

As dc42 announced PanelDue 1.24, I've also updated my PD 5, but one thing I've noticed, and to be fair it was in earlier versions, but running a multi G32 macro from the PanelDue, runs everything ok, but where I'd like to see the output and changes, on the console of the PanelDue at least, but it also doesn't show in the console of a DWC which was already connected.

dc42

@Dr_Ju_Ju said in RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0 released:

I re-flashed it & now its at least letting me get to 125, but I'd really like to get to 150.

Have you increased the default temperature limit, using M143?

Dr_Ju_Ju

Yes I have, i.e.
; Bed
M308 S0 P"bedtemp" Y"thermistor" A"Bed" T105000 B4138 C0 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S150 ; set temperature limit for heater 0 to 140C
M307 H0 B1 ; enable bang-bang mode for the bed heater
M140 H0 ; map heated bed to heater 0
M144 S1 ; set bed 'Active'

jay_s_uk

@Dr_Ju_Ju What type of bed is it? AC or DC?

dc42

Tuning always overshoots the target temperature, so to tune nat 150C you will need to raise the M143 limit some more.

dc42

I'm locking this thread how because RRF 3.01-RC9, DWC 2.1.4 and DSF 2.0.0 are released.