Topics created by Ted

It looks like Cura has acceleration control enabled and set to M204 P1500 so definitely higher than what you have in config.g. Try disabled acceleration control for now and control it via config.g. You can experiment with changing it mid print by sending different M204 P values to see the effects.

@ted said in Cloned extruder:

It works. The only problem is that I now need to post-process my gcode to have the other extruder printed out as well:
G1 X4 Y0 E0.5 => G1 X4 Y0 E0.5:0.5

You don't need to do that if you send this command:

M567 P0 E1:1

That enables mixing on tool 0 with the mixing ratio set to 1:1. So G1 E0.5 will advance both extruders by 0.5mm.

You could add M562 and M116 to your resume.g file if you want to clear heater faults automatically.

@aidar Thanks, that solves the problem for me!

@phaedrux I set the dive height to 50 mm. It gives me a lot of failure tolerance. It is working fine for me. So far no problems and much safer than just the 5 mm default. The mentioned error while probing (which I now avoid with a higher dive height) was due to mechanical tolerances in my extruder / laser mount.

It is working fine for single probes using G30. Wasn't aware that this would affect the dive height of G29, too. Haven't tried G29 in a while now as I still don't know if it resets z=0 when called AFTER G30.
I got the problem that whenever G29 after G30 the printer prints with different z=0 heights. It is always a way too high and it is different every sequence! Trigger height of BLTouch probe is wonderful stable with < 0.01 mm tolerance, which is amazing! Also checked if I have missing steps and lowered max z speed to 1 mm/s. It's fine. Still looking for the error and still thinking about my question above: When G29 is not setting z=0 than this could cause the changing z=0 height. Need to investigate here.

BTW: When having dive height at 50 mm and then G30 down and get the probe triggered already after 1 mm it is not driving back 1 mm but driving back whole 50 mm. So it ends at 50 mm over the trigger point while started at 1 mm over the trigger point. Not sure if this is not a bug. When first setting the dive height to 180 mm (my build volume) I got the problem that it rises even over the endpoint switch. Since G29 seems to use that dive height also it is not a good idea to do so anyway (unless I have too much time).