QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2

[Exerqtor]

Strange issue just happened, sliced and printed a job with the exact same slicer profile and no changes done to RRF. No issues.

Loaded a new STL in the slicer, sliced, exported and started printing it, it runs through start.g as expected, opens the job file but aborts the print somewhere in the QUI image data (added echo's at the start and end of QUI to see where it shits the bed).

So i opened the file with DWC editor and removed all the image data between ; thumbnail_QOI begin & ; thumbnail_QOI end, saved the changes and tried again. Law & behold, now it worked just fine!

The QOI in question: QUI.g

QOI removed/working:

echo “QOI start”
;
; thumbnail_QOI begin 160x160 27648
; thumbnail_QOI end
;
; 
echo “QOI end”

I have no idea how the QOI generation or handeling happens in either PrusaSlicer or in RRF, so I don't know whats going on lol.

[dc42]

@Exerqtor please post the complete print file containing that QOI image, that abort when you try to print it. I suspect the issue is caused by the way that RRF processes (or doesn't) some other data later in the file.

Are you running in standalone or SBC mode? Which Duet are you using?

Do you see any error messages when the print aborts?

Please post a M122 report taken after the print has aborted.

[Exerqtor]

@dc42

Okok, here is the full job file.

This is how what it prints in console (full of echo's don't mind them):

25.2.2023, 16:44:02	Cancelled printing file 0:/gcodes/Tap_Front_r2_0.2mm_ABS_0.4n_1h5m.gcode, print time was 0h 0m
'abort' command executed
25.2.2023, 16:44:01	start.g end
job start, before QOI image
25.2.2023, 16:43:15	M32 "0:/gcodes/Tap_Front_r2_0.2mm_ABS_0.4n_1h5m.gcode"
File 0:/gcodes/Tap_Front_r2_0.2mm_ABS_0.4n_1h5m.gcode selected for printing
start.g start

[Exerqtor]

@dc42
FYI i just had the same thing happen to another job, removed all the QOI image lines, saved and tried again: all ok.

[gloomyandy]

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Are you running in standalone or SBC mode? Which Duet are you using?
Do you see any error messages when the print aborts?
Please post a M122 report taken after the print has aborted.

@Exerqtor See the questions/requests from DC42 above...

[Exerqtor]

@gloomyandy said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Are you running in standalone or SBC mode? Which Duet are you using?
Do you see any error messages when the print aborts?
Please post a M122 report taken after the print has aborted.

@Exerqtor See the questions/requests from DC42 above...

Ah dang it, i answered to his original post and didn't see that he edited it and asked for more info lmao.

---

---

---

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Are you running in standalone or SBC mode? Which Duet are you using?

It's happening on a Duet 3 Mini (with a 1LC connected for what might be worth) in standalone mode.

Do you see any error messages when the print aborts?

DWC gives me a prompt that the msg is to long, and to look in console, Regarding what comes out in console have a look at the previous post

Please post a M122 report taken after the print has aborted.

I'll fire up one of the failing job files and post the M122 report once the current print job is finished!

Sorry i didn't notice that you have added a request for more info, my bad!

[Exerqtor]

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Do you see any error messages when the print aborts?

Please post a M122 report taken after the print has aborted.

Here is a complete console "log" with an M122:

26.2.2023, 12:07:04	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5beta2 (2023-02-08 17:42:04) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: FAP55-Q967A-G65J0-401GL-0S02Z-RF9TL
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 103012
Dynamic ram: 125452 of which 300 recycled
Never used RAM 9108, free system stack 126 words
Tasks: NETWORK(ready,1.5%,185) HEAT(notifyWait,0.8%,326) Move(notifyWait,4.5%,257) CanReceiv(notifyWait,1.3%,771) CanSender(notifyWait,0.1%,325) CanClock(delaying,0.2%,340) TMC(notifyWait,32.1%,71) MAIN(running,154.6%,351) IDLE(ready,47.5%,30) AIN(delaying,21.8%,263), total 264.4%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 24:49:43 ago, cause: software
Last software reset at 2023-02-25 11:17, reason: User, Gcodes spinning, available RAM 11380, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 89383760, completed 89383759, timed out 0, errs 0
Step timer max interval 1488
MCU temperature: min 34.7, current 38.9, max 45.6
Supply voltage: min 23.3, current 23.8, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/27, heap memory allocated/used/recyclable 2048/1836/1480, gc cycles 11643
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 141, reads 64615, writes 159, timeouts 3, DMA errors 0, CC errors 0, failedOp 0x41
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 139, reads 64616, writes 159, timeouts 2, DMA errors 0, CC errors 0, failedOp 0x6f
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 1, reads 64703, writes 73, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 250, reads 64706, writes 70, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x72
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 249, reads 64704, writes 73, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 98, reads 64767, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 98, reads 64766, writes 10, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6f
Date/time: 2023-02-26 12:07:03
Cache data hit count 4294967295
Slowest loop: 342.28ms; fastest: 0.08ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 13.0ms, write time 63.5ms, max retries 0
=== Move ===
DMs created 83, segments created 41, maxWait 63706983ms, bed compensation in use: mesh, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 13], CDDA state -1
=== DDARing 1 ===
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 ===
Movement locks held by null, 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 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 907768, received 1788825, lost 0, boc 0
Longest wait 6ms for reply type 4014, peak Tx sync delay 505, free buffers 18 (min 11), ts 446919/446918/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 356.28ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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 2.1beta2
WiFi MAC address bc:ff:4d:e6:b1:62
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 4194304, free heap 43060
WiFi IP address 192.168.10.50
WiFi signal strength 0dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0
26.2.2023, 12:06:56	start.g end
Cancelled printing file 0:/gcodes/ALL_IS_35Hz-ringing_tower_0.2mm_ABS_0.4n_25m.gcode, print time was 0h 1m
'abort' command executed
26.2.2023, 12:05:29	M32 "0:/gcodes/ALL_IS_35Hz-ringing_tower_0.2mm_ABS_0.4n_25m.gcode"
File 0:/gcodes/ALL_IS_35Hz-ringing_tower_0.2mm_ABS_0.4n_25m.gcode selected for printing
start.g start
26.2.2023, 12:05:11	Upload of ALL_IS_35Hz-ringing_tower_0.2mm_ABS_0.4n_25m.gcode successful after 1s

The job file in question.

[Exerqtor]

@dc42
FYI this is still an active issue between PS 2.6.0-a5 & RRF 3.5.0b2. I've been doing heaps of prints with the thumbnails disabled (without any issue), and thought i would give it another go now after they released alpha5 but it behaves just the same✌

[jay_s_uk]

@Exerqtor this is strange as i'm printing with PS 2.6 a4 and not had an issue with thumbnails enabled.
What resolution do you have set for them?

[Exerqtor]

@jay_s_uk
Agreed, I've got them set to 160x160.

[jay_s_uk]

@Exerqtor mine are set to 64x64, 400x400
can you try those?

[Exerqtor]

@jay_s_uk said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

64x64, 400x400

Sure, I got a print running ATM. But i'll slice the next job with those resolutions.

[Exerqtor]

Naah, it shit's the bed with 64x64, 400x400 as well. Are you using any form of start.g though @jay_s_uk ?

I deleted the 400x400 QUI data from the sliced file that just failed, and now it works. So it might seem like it kinda panics and aborts if the QUI image data is to large/long or something.

[jay_s_uk]

@Exerqtor I'm not using start.g
I pass parameters through to another macro

[Exerqtor]

@jay_s_uk Might be the combo of larger/longer QUI images and start.g that makes it shit the bed then.

I just tried another print at 64x64 and it didn't work either. This was a larger stl/object so the QUI image data was more lines than the one that worked though.

Next i'll test dropping the start.g to see how that works out 😮‍💨🤷‍♂️

[Exerqtor]

Ditched start.g and now it all works with both 60x60 and 400x400 thumbnails. Soooo thats the last nail in start.g in my regard lmao.

[dc42]

@Exerqtor thanks. This is on my list to look at when I have finished my current tasks. Have you already posted your start.g in this thread? If not, please do so.

[Exerqtor]

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Have you already posted your start.g in this thread? If not, please do so.

Here you go:

; start.g  v1.3
; Called whenever you start a print, run before slicer gcode at start of print

echo "start.g start"
G21                                                                            ; Set units to millimeters
G90                                                                            ; Use absolute coordinates
M83                                                                            ; Use relative distances for extrusion
M140 S65                                                                       ; Set bed temperature to 65°C
if exists(global.sb_leds)
  set global.sb_leds = "heating"                                               ; StealthBurner LED status
T0                                                                             ; Select Tool 0
M291 P"Print started, preheating." T10                                         ; Info message
G4 S1                                                                          ; Wait 1 second
M220 S100                                                                      ; Reset speed factor
M221 S100                                                                      ; Reset extrusion factor
M290 R0 S0                                                                     ; Reset baby stepping
M107                                                                           ; Turn off the part cooling fan
if heat.heaters[0].current < 65
  M140 S65                                                                     ; Set bed temperature to 65°C
  M116 H0                                                                      ; Wait for the bed to reach its temperature
echo "start.g end