Posts made by bramerrf

@bramerrf
Many thanks. That did it.

Previously I was using RRF2.x and when a print was completed and new one was to be started it was not necessary to run"home all" or "bed levelling" again. After upgrading to RRF3.4.1 and adding a stop.g file after each print before I can start a new one I now have to run 'home all' and 'compensation & calibration'.

It is very likely something I have done or not done something that is the issue. Can anyone advise on how I can hold onto the home all and bed level status at the end of a print so that a new on be started immediately?

config.g and stop.g below:-

; Configuration file for Duet WiFi / Ethernet running RRF3 on E3D Tool Changer
; executed by the firmware on start-up
;modified Thursday June 9th 2022

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M667 S1 ; Select CoreXY mode

; Network
M550 P"ImpTC" ; Set machine name
;M587 S"ssid" P"password" ; WiFi Settings
;M552 S1 P"ssid" ; Enable WiFi Networking
M552 S1 ; Enable Networking
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drive direction
M569 P0 S0 ; Drive 0 X
M569 P1 S0 ; Drive 1 Y
M569 P2 S1 ; Drive 2 Z
M569 P3 S0 ; Drive 3 E0
M569 P4 S0 ; Drive 4 E1
M569 P5 S1 ; Drive 5 E2
M569 P6 S1 ; Drive 6 E3
M569 P7 S0 ; Drive 7 COUPLER
M569 P8 S0 ; Drive 8 UNUSED
M569 P9 S0 ; Drive 9 UNUSED

M584 X0 Y1 Z2 C7 E3:4:5:6 ; Apply custom drive mapping
M208 X-35:328.5 Y-49:243 Z0:300 C-45:360 ; Set axis maxima & minima
M92 X100 Y100 Z1600 C91.022 E834:834:834:834 ; Set steps per mm assuming x16 microstepping
M350 E16:16:16:16 I1 ; Configure microstepping with interpolation
M350 C16 I10 ; Configure microstepping without interpolation
M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation
M566 X400 Y400 Z8 C2 E2:2:2:2 ; Set maximum instantaneous speed changes (mm/min)
M203 X35000 Y35000 Z1200 C5000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min)
M201 X6000 Y6000 Z400 C500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2)
M906 X1800 Y1800 Z1330 I30 ; Idle motion motors to 30%
M906 E1000:1000:1000:1000 C500 I10 ; Idle extruder motors to 10%

; Endstops
M574 X1 Y1 S3 ; Set X / Y endstop stall detection
M574 C0 Z0 ; No C Z endstop

; Z probe
M558 P8 C"zstop" H3 F360 I0 T20000 ; 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
M557 X10:290 Y20:180 S40 ; Define mesh grid

;Stall Detection
M915 X Y S3 F0 H400 R4700 ; X / Y Axes

; Heaters
M308 S0 P"bedtemp" Y"thermistor" A"Bed" T100000 B4138 C0 ; Set thermistor
M950 H0 C"bedheat" T0 ; Bed heater
M143 H0 S225 ; Set temperature limit for heater 0 to 225C
M140 H0 ; Bed heater is heater 0

M308 S1 P"spi.cs1" Y"rtd-max31865" ; Set PT100
M950 H1 C"e0heat" T1 ; Extruder 0 heater
M143 H1 S305 ; Set temperature limit for heater 1 to 305C

M308 S2 P"spi.cs2" Y"rtd-max31865" ; Set PT100
M950 H2 C"e1heat" T2 ; Extruder 0 heater
M143 H2 S305 ; Set temperature limit for heater 2 to 305C

M308 S3 P"duex.cs5" Y"rtd-max31865" ; Set PT100
M950 H3 C"duex.e2heat" T3 ; Extruder 0 heater
M143 H3 S305 ; Set temperature limit for heater 3 to 305C

M308 S4 P"duex.cs6" Y"rtd-max31865" ; Set PT100
M950 H4 C"duex.e3heat" T4 ; Extruder 0 heater
M143 H4 S305 ; Set temperature limit for heater 4 to 305C

; Tools
M563 P0 S"T0" D0 H1 F2 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Reset tool 0 axis offsets
G10 P0 R0 S0 ; Reset initial tool 0 active and standby temperatures to 0C

M563 P1 S"T1" D1 H2 F4 ; Define tool 1
G10 P1 X0 Y0 Z0 ; Reset tool 1 axis offsets
G10 P1 R0 S0 ; Reset initial tool 1 active and standby temperatures to 0C

M563 P2 S"T2" D2 H3 F6 ; Define tool 2
G10 P2 X0 Y0 Z0 ; Reset tool 2 axis offsets
G10 P2 R0 S0 ; Reset initial tool 2 active and standby temperatures to 0C

M563 P3 S"T3" D3 H4 F8 ; Define tool 3
G10 P3 X0 Y0 Z0 ; Reset tool 3 axis offsets
G10 P3 R0 S0 ; Reset initial tool 3 active and standby temperatures to 0C

; Fans
M950 F1 C"fan1"
M950 F2 C"fan2"
M950 F3 C"duex.fan3"
M950 F4 C"duex.fan4"
M950 F5 C"duex.fan5"
M950 F6 C"duex.fan6"
M950 F7 C"duex.fan7"
M950 F8 C"duex.fan8"

M106 P1 S255 H1 T70 ; T0 HE
M106 P2 S0 ; T0 PCF
M106 P3 S255 H2 T70 ; T1 HE
M106 P4 S0 ; T1 PCF
M106 P5 S255 H3 T70 ; T2 HE
M106 P6 S0 ; T2 PCF
M106 P7 S255 H4 T70 ; T3 HE
M106 P8 S0 ; T3 PCF

M593 F42.2 ; cancel ringing at 42.2Hz (https://forum.e3d-online.com/threads/accelerometer-and-resonance-measurements-of-the-motion-system.3445/)
;M376 H15 ; bed compensation taper

;tool offsets
; !ESTIMATED! offsets for:
; V6-tool: X-9 Y39 Z-5
; Volcano-tool: X-9 Y39 Z-13.5
; Hemera-tool: X20 Y43.5 Z-6

G10 P0 X-9 Y39 Z-4.670 ; T0
G10 P1 X-8.65 Y38.8 Z-4.950 ; T1
G10 P2 X-9 Y39.2 Z-4.655 ; T2
G10 P3 X-8.85 Y38.8 Z-4.673 ; T3
; the bigger the negative number for Z the more the nozzle lifts up off the bed

;M572 D0 S0.2 ; pressure advance T0
;M572 D1 S0.2 ; pressure advance T1
;M572 D2 S0.2 ; pressure advance T2
;M572 D3 S0.2 ; pressure advance T3

;M575 P1 S1 B57600 ; Enable LCD
G29 S2 ; disable mesh
T-1 ; deselect tools

M501 ; load config-override.g

; stop.g
; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled)
M568 P0 A0 ;turn off T0 extruder heater
M568 P1 A0 ;turn off T1 extruder heater
M568 P2 A0 ;turn off T2 extruder heater
M568 P3 A0 ;turn off T2 extruder heater
M140 H0 S-274 ;turn off bed heater
M84 ;turn off motors

@stephen6309 said in New issue after upgrading firmware to 3.4.1:

M591 D0 S0 ; turn off filament monitor

Thanks for all the replies.
I will try to put everything I want into stop.g and see how few mistakes I make.
Thanks again.

Historically at the end of each print the extruder and bed heaters were automatically switch off. After upgrading to 3.4.1 I noticed that when a print finished the extruder and bed heaters remained active.
Previously my ending script finished with "M0" now that has no discernable effect. I tried replacing with "M104 S0" and "M140 S0" but they had no effect either.
I must be doing something incorrectly, any advice will be much appreciated.

@phaedrux
Granpa Pig solution worked. Disconnect printer, shut down completely, have a cup of coffee, turn power back on, restart printer. Z probe now working correctly. Printing a test job right now.
Thanks again.

@phaedrux
I spoke too soon. DWC is working fine now. Theprinter connects and everything looks OK but when I do a 'home all' the Z probe is not working, in that is would prefer to drive itself through the bed.
I did a complete reinstall of Duet2and3Firmware-3.4.1.zip and it completed successfully, no errors reported. Upon restarting the Z probe is still not being cooperative, it does not seem to be activating even though it is flat on the bed.
Can you, please, suggest anything I can try? Previously to all these issues with firmware upgrading the printer was working well with no issues.

@phaedrux
Many thanks. I did as you advised and now I have a working printer again.
Your help is very much appreciated.

@phaedrux
with the 3.0 firmware loaded the DWC was working. So I uploaded Duet2and3Firmware-3.4.1.zip using that. As each item was being loaded to registered 100% and did not report any issues.

@jay_s_uk
Since I cannot connect using the DWC I used a terminal emulation program. The results are:-
M552 S0
ok
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
M552 S1
Turn off the current WiFi mode before selecting a new one
ok

I had my E3D Toolchanger running nicely on RRF v3.0 and (stupidly) decided to upgrade to RRFv3.4.1 As far as I can tell the upgrade ran with no issues but after a restart the DWC interface does not open and I do not have a WiFi connection.

At start up I get :-

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1
Executing config.g… HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Macro file config-override.g not found
Done!
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.

Then running M114, M115 and M122 I get the output below.

M114
X:0.000 Y:0.000 Z:0.000 C:0.000 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 E3:-0.0 Count 0 0 0 0 Machine 0.000 0.000 0.000 0.000 Bed comp 0.000
Ok

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2022-06-01 21:05:38
Ok

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MSD-6J9DD-3SN6Q-1STH9
Used output buffers: 1 of 26 (1 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 77720 of which 0 recycled
Never used RAM 10500, free system stack 193 words
Tasks: NETWORK(ready,7.0%,521) HEAT(notifyWait,0.1%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,92.8%,437) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:21:41 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 0
MCU temperature: min 31.6, current 36.8, max 37.1
Supply voltage: min 0.5, current 0.5, max 1.5, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5: ok, SG min n/a
Driver 6: ok, SG min n/a
Driver 7: ok, SG min n/a
Driver 8: ok, SG min n/a
Driver 9: ok, SG min n/a
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 101.24ms; 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 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
=== DueX ===
Read count 1, 0.05 reads/min
=== Network ===
Slowest loop: 0.41ms; 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 1, noresp 0
  Socket states: 0 0 0 0 0 0 0 0
  Ok

M587
Failed to retrieve network list: another SPI transfer is pending
ok

The WiFi module has its blue lit up but the module is not talking.
If I do network scan it is not there.

Any ideas on how to proceed from here will be much appreciated.