Solved 2-n-1 Extruder Heat Rises after Filament Change

[louvanna]

Duet 2 WiFI board.
Printer is working great. Now, I want to go faster.
Extruder is a 2-into-1 on a delta printer.
Both materials are same temperature setting,
H1 = 200c and 200c-stby.
Cura 4.8.0 slicer.

During change of filament, with M116 involved ( wait ), I notice that the H1 rises above 200C to 203-205, and then H1 will need to wait to <=201C before it will resume. This is 4-9 seconds. This time adds up with hundreds of layers of dual color.

My speculative thought is to use Cura's anticipated tool change, where it coasts the selected tool heat prior to tool change. This would be coupled with H1-stby temperature of a few degrees cooler.

What would the forum suggest as a 'tweak' to be to remove this temperature rise and fall wait period?

[Phaedrux]

Might be easier to just relax the tolerance on M116

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M116_Wait

[louvanna]

Thank you, now, got that implemented, on to next tweak.

As they say, 'Read the manual.'
I guess during my quick read, I skipped over that parameter.

BTW, the default states 2 deg but my experience of watching the from my panel display it is 1 degree.

OK, looks like my firmware is prior to some change.

== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9568A-F23SD-6J9DL-3SJ6Q-K9RMH

[Phaedrux]

@louvanna said in 2-n-1 Extruder Heat Rises after Filament Change:

RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
That will get your firmware and DWC up to date.

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

[louvanna]

Well, now I have a brick.
Uploading them numerically ordered, 2.05, 3.0, 3.2.2, with restart between each was good until 3.2.2.
I no longer have WiFi connection so limited to Panel, and hoping for USB, but ...
Apparently the ATX mod with the external 5V I jumper is incompatible with this state of machine.

The console is a rolling set of messages about various.

Temperature -273 ..
Error attempt to set/report offsets
Error attempt to move motors when Vin ...
Tool 0 not driven, because heater
G0/G1 insufficient homed axes ...
Failed to enable endstops ....
Warning obsolete user of S ......

USB connection is non-responsive to being enumerated.
( not sure if this is the ext 5V mod incompatibility)

A greater warning would have been appreciated.

[louvanna]

USB has enumerated, connection established.

For the record:
The ATX mod with external 5V, and such was the culprit.
Both jumpers 5V and E 5V are removed, to allow the USB to function.

I have the last firmware shown via M115 on my terminal, via USB:

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet
FIRMWARE_VERSION: 3.2.2
ELECTRONICS: Duet WiFi 1.02 or later
FIRMWARE_DATE: 2021-02-11

I will go looking elsewhere for how to uncover all the incompatibilities moving up to 3.x.x.

[droftarts]

@louvanna see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files
(The whole page is useful to understand differences between RRF 2 and 3).

As @Phaedrux suggested, generate a new config with the configuration tool, and compare it to your existing config is also useful in understanding the change.

Ian

[louvanna]

Thank you for the URL.
I still have issues with WiFi/network.
The new config.g, etc have been transferred to the SD card an rebooted several times, but ....

Trying to understand what is yet incorrect.
From the terminal, it is apparent that the WiFi is not happy.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-02-11
ok
M552 S0
ok
M587
Error: M587: Failed to retrieve network list: another SPI transfer is pending

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-02-11
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9568A-F23SD-6J9DL-3SJ6Q-K9RMH
Used output buffers: 1 of 24 (2 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73072 of which 0 recycled
Never used RAM 15548, free system stack 192 words
Tasks: NETWORK(ready,521) HEAT(blocked,308) MAIN(running,471) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:29 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 16760, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043d000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 25.5, current 27.5, max 27.8
Supply voltage: min 0.0, current 0.1, max 0.1, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 130618, ok, SG min/max not available
Driver 1: position 130618, ok, SG min/max not available
Driver 2: position 130618, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 37113105
Slowest loop: 4.94ms; fastest: 0.15ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, 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, 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 ready with "M122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.24ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

• WiFi -
  Network state is starting2
  WiFi module is disabled
  Failed messages: pending 0, notready 0, noresp 0
  Socket states: 0 0 0 0 0 0 0 0
  ok

[louvanna]

Firmware now running correctly,
WiFi able to connect, etc.
Back to making config.g via configurator, compatible with 3.2.2.

closed.