S5 in network & cloud: suddenly always material conflict on dual-print with new firmware/cura

[assaero 2]

Hey all,

I run a first-gen S5 and updated a few days ago on fw9.0 when the display offered it. Since then, when I dispatch a dual-material printjob from Cura, via network or cloud, in 98% the materials do not seem to be properly transmitted with the printjob; I select the printer and printer material configuration in cura to sync and send after slicing, but the printer shows then on the printjob a conflict and under printcore type and material name for both cores "N/A" with a red warning label, so I can not override it. What is happening here? Dev mode deactivated. I managed it once to print normal yesterday, but did not do anything different then trying for the 20th time. Cura version originally 5.8, tried updating onto 5.9beta yesterday after I noticed the issue, but behaviour persists. Filaments are externally installed profiles (Flex medium and ApolloX ASA), but were working fine until now.

 

//EDIT1:

Even more weirdly, digitalfactory throws the error:

"This print job exceeds the build volume of the printers in this group. Delete this print job and resubmit it using a reduced build volume.". The printjob is centered on the buildplate and has dimensions of perhaps 10x5x5cm. So what is going on?

Edited November 17 by assaero

[assaero 2]

Actually I found it out. The reason seems to be resurfacing of an old bug in firmware rev9.0

The X-max-size in the griffin-header seems to be no longer accepted when to big in the current gcode. Manually reducing

;PRINT.SIZE.MAX.X:357

to

;PRINT.SIZE.MAX.X:327

makes the file printable. So Is this a cura or firmware bug? Why is Cura giving out >max size values when dual filament printing?

[PaulKuiper 11]

Hi assaero,

 

I cannot reproduce it. The x max remains 330mm in my case. Could it be that your S5 printer settings became corrupted for some reason? Please check the width in the printer settings menu.
Otherwise please export a support package and share with us for analysis. 

kind regards,

 

    Paul Kuiper

[assaero 2]

Hey Paul,

I moved to a new pc and set it up with cura. First time it started the print fine; after I changed some settings and sliced again (disabled retraction) and it threw the same error. This led me to investigate and its actually the retraction setting producing the problem. I attach two support packages, one without retraction triggering the error, one with retraction printing fine.

export-20241123-171313_w_retr.3mf export-20241123-170940_wo_retr.3mf

[assaero 2]

Hi, can anybody else reproduce the problem?