Strange Behavior , after "Pause" 'Cancel ""print again"
-
So to check if the SD card was writing/reading i put the "G28 X Y" into the pause.g file to test it was working, and yes the pause.g did the "G28 X Y" but it still does not read the cancel.g file i have alsso updated to the new 3.4.0 version released today
-
@phaedrux
new Firmware loaded
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 3R9YY-6T9RL-D65J0-40KMN-2UW2Z-RHYT0
Used output buffers: 3 of 40 (19 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 110484 of which 0 recycled
Never used RAM 27472, free system stack 132 words
Tasks: NETWORK(ready,11.6%,202) HEAT(notifyWait,0.0%,342) Move(notifyWait,0.0%,292) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,337) TMC(delaying,1.1%,114) MAIN(running,86.1%,428) IDLE(ready,0.2%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:36 ago, cause: software
Last software reset at 2022-03-18 15:14, reason: User, GCodes spinning, available RAM 23704, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 96385, completed 96385, timed out 0, errs 0
Step timer max interval 751
MCU temperature: min 35.9, current 36.4, max 41.2
Supply voltage: min 23.7, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
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: standstill, SG min 0, read errors 0, write errors 1, ifcnt 26, reads 8712, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 26, reads 8712, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 8712, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 25, reads 8712, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 46, read errors 0, write errors 1, ifcnt 53, reads 8706, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 14, read errors 0, write errors 1, ifcnt 55, reads 8705, writes 16, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 74, read errors 0, write errors 1, ifcnt 51, reads 8705, writes 16, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-03-18 15:16:32
Cache data hit count 187991149
Slowest loop: 5.91ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 624ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2, completed 2, 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 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 864, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 481/0/0
Tx timeouts 0,0,480,0,0,382 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 138.62ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address f0:08:d1:02:a1:0b
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 2097152, free heap 25512
WiFi IP address 192.168.0.19
WiFi signal strength -53dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
Still getting this error after "Pause" "Cancel" "print again"
Cancelled printing file 0:/gcodes/shark-v2-0-a_0.35mm_PLA__2h32m.gcode, print time was 0h 0m
Error: Failed to home axes
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown - WiFi -
-
Can you upload your actual files for pause.g and cancel.g?
-
@phaedrux
;cancel.g
G28 X Y; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 30 2021 11:07:38 GMT+1300 (New Zealand Daylight Time)
M83 ; relative extruder moves
G1 E-10 F3600 ; retract 10mm of filament
G91 ; relative positioning
G1 Z5 F360 ; lift Z by 5mm
G90 ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0
G28 X YThe G28 X Y works on pause.g but still not on cancel.g
-
Can you drag and drop the actual files to upload them? That way we can see if there are any non-standard characters or something like that in the file itself.
And since it's calling some homing files, perhaps you can share those as well. Maybe there is something happening in homex and homey.
-
@phaedrux ```
;cancel.g G28 X Y; homex.g ; called to home the X axis ;M98 P/macros/sensorless_Z G91 ; relative positioning G1 H1 X-235 F12000 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X15 F6000 ; go back a few mm G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass) ;G1 H2 Z-5 F12000 ; lower Z again G90 ; absolute positioning G1 X20 F6000 ; go to X 0 print area G92 X0 ; set X to 0 position;sensorless_z M915 P0.4:0.5:0.6 S3 F0 R0 ; Configure Z-Axis Stall Detection M906 Z300 ; Lower motor current by 50% M574 Z2 S4 ; Configure Z-Axis stall detection homing M400 ; make sure everything has stopped before we make changes M906 Z1000 ; Reset motor current M400; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 30 2021 11:07:38 GMT+1300 (New Zealand Daylight Time) M98 P/macros/sensorless_Z G91 ; relative positioning G1 H1 Y315 F12000 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y15 F12000 ; go back a few mm G1 H1 Y315 F360 ; move slowly to Y axis endstop once more (second pass) ;G1 H2 Z-5 F12000 ; higher Z again G90 ; absolute positioning G1 Y0 F6000 ; go to X 0 print area G92 Y0 ; set X to 0 position```; pause.g ; called when a print from SD card is paused ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 30 2021 11:07:38 GMT+1300 (New Zealand Daylight Time) M83 ; relative extruder moves G1 E-10 F3600 ; retract 10mm of filament G91 ; relative positioning G1 Z5 F360 ; lift Z by 5mm G90 ; absolute positioning G1 X0 Y0 F6000 ; go to X=0 Y=0 G28 X Y -
@moth4017 said in Strange Behavior , after "Pause" 'Cancel ""print again":
M98 P/macros/sensorless_Z
You may need to start quoting your file names when calling macros. It should be fine in standalone mode, but in SBC mode it is required and may be required in standalone in the future.
It's a long shot, but still worth a shot.
M98 P"/macros/sensorless_Z" -
@phaedrux
No changeCancelled printing file 0:/gcodes/Body1_0.35mm_ABS__17m.gcode, print time was 0h 0m
Error: Failed to home axes
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Warning: Driver 0.5 warning: over temperature warning
Warning: Driver 0.4 warning: over temperature warning -
Are your drivers actually getting hot to the touch or are they spurious warnings? Printing is working correctly, right?
-
@phaedrux
No they are not hot and i did a 8 hour print and they were ok , i only get that error after the "Pause, Cancel" -
I assume you're in stealthchop mode for the stall detection?
-
@phaedrux
M569 P0.4 S1 D3 V30 ; physical drive 4 goes forwards D3=stealthchop
M569 P0.5 S0 D3 V30 ; physical drive 5 goes backwards
M569 P0.6 S1 D3 V30 ; physical drive 6 goes forwards -
Can you zip up the entire sys and macros folders and share them with me, either upload them here but first change the file extension to .txt or use a file sharing cloud service. I'd like to get a complete look at what's going on with the actual files.
-
-
Thanks, I'll have a look tomorrow.
-
@phaedrux
Cheers
Mark -
Can you try copying your cancel.g to stop.g?
-
@phaedrux
Hi; stop.g ; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled) ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 30 2021 11:07:38 GMT+1300 (New Zealand Daylight Time) ;cancel.g G28 X YCopied cancel .g to stop.g
Did "Pause" "M0" stop.g ran perfectly
Did "Pause " "cancel" ran perfectly
Did "Print again" after cancel
Cancelled printing file 0:/gcodes/Body1_0.2mm_ABS__9h28m.gcode, print time was 0h 1m
Error: Failed to home axes
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Warning: Driver 0.5 warning: over temperature warning
Warning: Driver 0.5 warning: over temperature warning<
-
I just noticed in your pack of files that cancel.g has a leading blank space character.
Screen Shot 2022-03-22 at 12.16.36 AM.png -
@moth4017 said in Strange Behavior , after "Pause" 'Cancel ""print again":
Did "Print again" after cancel
Cancelled printing file 0:/gcodes/Body1_0.2mm_ABS__9h28m.gcode, print time was 0h 1m
Error: Failed to home axesDo you have a start.g file? If not, can you create one and add G28 to it?
That should make sure all axis are homed before the sliced gcode is executed.I think the over temperature warnings on drivers 0.4 and 0.5 may be related to stall detection on the Z axis.
