WORKAROUNDS

[KenO 0]

Note From Admin: Please do not make meaningless first posts with gif's.

[KenO 0]

Open ticket = 00835580

Problem parameters: 

- Cura_SteamEngine 5.6.0

- BIBO2 dual printer

Complaint:

Extruder no longer heats up with new GCODE  line =M109 T0 S(200, 0)

Workaround:

uninstall Ultimaker Cura version 5.6.0

reinstall version 5.5 to get working GCODE line =M109 T0 S200

 

Additional workarounds - you may edit your GCODE replacing all instances of "M109 T0 S(200, 0)" with "M109 T0 S200" or install the interim version 5.7.0-alpha.0

Edited March 2 by KenO
additional workarounds

[GregValiant 1,258]

There is a bug in the "initial_extruder_nr" replacement pattern.  It always returns "0" rather than the actual tool number.  You have it in two places in your startup gcode.  Hopefully it will be addressed in Cura 5.7.0.

 

A workaround is to remove the temperature lines from your StartUp Gcode and allow Cura to determine temperatures.  It might not be as efficient as a custom one but it should work.

 

This is from the BIBO definition file and has my suggestions.

;M104 T0 165 ; remove
;M104 T1 165 ; remove
M109 S{material_print_temperature_layer_0} ; alter
G21 ;metric values
G90 ;absolute positioning
M107 ;start with the fan off
G28 X0 Y0 ;move X/Y to min endstops
G28 Z0 ;move Z to min endstops
G1 Z2.0 F400 ;move the platform down 2mm
;T0 ; remove
G92 E0
G28
G1 Y0 F1200 E0
G92 E0
;T{initial_extruder_nr} ; remove
M117 BIBO Printing...

[Slashee_the_Cow 270]

Heads up: deleted a lot of seemingly unrelated tags from this topic.

[Dustin 130]

5 hours ago, KenO said:

Open ticket = 00835580

Problem parameters: 

- Cura_SteamEngine 5.6.0

- BIBO2 dual printer

Complaint:

Extruder no longer heats up with new GCODE  line =M109 T0 S(200, 0)

Workaround:

uninstall Ultimaker Cura version 5.6.0

reinstall version 5.5 to get working GCODE line =M109 T0 S200

This should have been your first post.
Please dont start threads with meaningless gif images if they are just going to be the only thing in the post..
You could have combined both posts into 1.

Additionally UltiMaker Support tickets have nothing to do with the UltiMaker Community they are not the same.

[gr5 2,176]

@GregValiant - do you happen to know if there is an issue in github for this bug?

[GregValiant 1,258]

Yes there are several.  On Jan 23 @CasperLamboo responded HERE  on Github in response to one of the bug reports.  It would appear that the problem with "initial_extruder_nr" might have been addressed for 5.7.