Hi,
The gcodes generated by Cura (4.11.0)with multi extruders only show the filament usage of the last extruder in DWC 3.3.0 (SBC mode).
I am attaching the gcodes I used to test it (I shortened the files so they are not too heavy).
In the first one, both extruders are used, and only the filament usage of the last extruder (T1) is reported, and 1 extruder only appears in the OM.
TEST_FILAMENT_USAGE_1.gcode
In the second one, both extruders are activated, but one only (T0) is used. The OM report an unvalid type code 15 (the gcode shows a filament use of 0m).
TEST_FILAMENT_USAGE_2.gcode
Does anybody knows if it comes from the 4.11.0 Cura (the parser is looking for "ilament" so it should work) or from a bug in DWC 3.3.0?
Thanks for you feedbacks.

@dc42 , Thanks for your feedback.
I got this error message when I run it:
Error: Failed to read code from macro test: Failed to evaluate "mod(iterations, 50) = 0": expected ','
I am sure it is a very obvious mistake from me, but I can't find it.

Hi everybody,

I am using the mod(,) function in a while loop and I noticed that the function doesn't work with the contstant "iterations" in it.
Here is my while loop:

while iterations < 1000
  if mod(iterations, 50) = 0
    M117 "mod function OK!"
  G4 P100
  continue

The evaluation of mod(140,50) returns the proper value.
If I create a global variable [name], set it to 140 (and check the assignment with M117) and evaluate mod(global.[name],50), it doesn't return any value.

Is there somehing I missed?

Thanks in advance.

I double checked my setup, and the SSR wasn't a zero cross as I thought I purchased. Replacing it by a zero cross solved the issue.
Thanks for your support.

@dc42 I tried to connect power the bed with cable running outside the machine, but still the same issue.

I found again more elements this morning:

• If I start a print with heating bed ON (with a PID control for the bed temp) when the bed is already at 55°C (for a 60°C target), then the error doesn't occur.
• I started the gcode below --> no error.

; no error
T0
M190 S60

• I started the gcode below --> no error

; no error
T0
M190 S60
M104 S213

• I started the gcode below --> no error

; no error
T0
M190 S60
M109 S213

• I started the gcode below --> error

; error
T0
M190 S60
M104 S213
M109 S213

• I started the gocde below --> error

; error
T0
M190 S60
G90 G1 X0 Y0 Z200
M400

• The error also occur with the last gcode ran as a macro (so without the start.g)

I emptied my tpre0.g and tpost0.g without any impact.

Any idea?

Thanks @dc42.
I do not have a PanelDue, but the 220V bed cable is running close to the CAN bus cables. I will isolate the bed cables from my other cables, test it again and come back with some results.

Observation:
After couple of tries, I noticed a pattern:
If I want to print a gcode with the heating bed ON (let's say 60°C), then as soon as the temperature of the bed is around 55-58°C, the error appears.

Error: Failed to switch off remote heater 0:
Error: Failed to switch off remote heater 1:
Cancelled printing file 0:/gcodes/IDX420_Left_2x_Impeller_4h43min_93g.gcode, print time was 0h 0m
Emergency Stop! Reset the controller to continue.

It looks like the error occurs as soon as the regulation (as soon as the command is not 100% any more) of the bed heat starts.
I do not explain the link between the bed and the heater 0 and 1 (respectively the hotend left and right on my setup).
I am controling the bed in 220V with an SSR zero cross (line frequency 60Hz) with a control frequency of 6Hz (although still 10Hz on the config I sent).
I am controlling the SSR with the 2-wire fan output out7 from the 6HC.

Test:

• I tried to print with the bed controled in bangbang, and the error appears more randomly (sometimes at the beginning of the print, sometimes after couple of hours).
• I am trying to suppress the bed heating. The print starts properly, but I will let it print over night to confirm that it prints without any issue).

@phaedrux , sorry for the very long delay to answer due to my holiday trip.
I updated the firmware to the 3.3 release and checked that the 6HC and both 1LC are running on it (M122, M122 B#).
I also now run on standalone mode to keep it as simple as possible.

Please find below my config and the M122, M122 B20 and M122 B21 responses below.
config.txt
M122.txt
M122 B21.txt
M122 B20.txt

I continue the investigation and keep you updated.
Thanks a lot for your help.

Hi,
I am experiencing an unexpected error while printing (Error: Failed to switch off remote heater 0:). After this, an emergency stop is triggered.
I am running the 3.3 release on a 6HC + 2x 1LC with a SBC.
Here are the logs of the event:

05/07/2021, 13:25:09	Connection established
05/07/2021, 13:24:59	Connection interrupted, attempting to reconnect...
05/07/2021, 13:06:36	Emergency stop, attemping to reconnect...
05/07/2021, 13:06:36	Emergency Stop! Reset the controller to continue.
05/07/2021, 13:06:36	Cancelled printing file 0:/gcodes/IDX420_Duplicate_2x_Impeller_4h08min_79g.gcode, print time was 0h 16m
05/07/2021, 13:06:36	Error: Failed to switch off remote heater 1:
05/07/2021, 13:06:36	Error: Failed to switch off remote heater 0:
05/07/2021, 12:54:37	Height map saved to file heightmap.csv
05/07/2021, 12:49:37	M32 "0:/gcodes/IDX420_Duplicate_2x_Impeller_4h08min_79g.gcode"
File 0:/gcodes/Impeller_4h08min_79g.gcode selected for printing
05/07/2021, 12:49:29	Upload of Impeller_4h08min_79g.gcode successful after 1s

It happens sporadically, sometimes after 1min, sometimes after 16min or more.

I am surprised by the non existing message following the error message.

Does anybody have an idea about the cause of this issue?

Thanks in advance.

@dc42 Thanks again.
I will purchase the ATMEL ICE and try this procedure keeping the bootloader.