Topics created by matteo2u

Given the amount of time and things that sound like they have changed, it may be best to start a new thread with your issue and give us as much detail as possible.

@matteo2u said in Duplicate Extruder Signal:

@deckingman Thanks for this great help. I got it up and running and all seems to be working fine with the exception of something strange. When I increase the slider for extruder 1 (the new pusher) it seems to slow down. Inversely, when i drag it below the setting for Extruder 0, it speeds up. Is there a good explanation for this?

Thanks again,
Matt

Just thinking out loud but one possibility for that behaviour is this. Essentially, the firmware doesn't "know" that you have two extruders in a push-pull configuration. In a way we've tricked it by saying that there are two extruders feeding one hot end (similar to a two in, one out hot end) but we've set the mixing ration to 1:1 giving an overall extrusion percentage of 200%. That's what we would be getting if we used a two in, one out hot end with the extruders is parallel rather than in series. Normally, with any sort of multi input, single hot end, that mixing ratio would always add up to unity (or 100%). So it's likey that the firmware is reacting in such as way as to maintain the sum of the mixing ratios. So that if a multiplier is applied to one extruder (which is what yo are doing by using the slider), then the other extruder would need to be reduced to maintian the overall extrusion amount. i.e. If we define a mixing ratio of 1.00:1.00 using M569 to give an overall extrusion amount of 200%, then we apply a multiplier to the first extruder of (say) 10% then the second extruder would need to be reduced by 10% to maintain the overal total of 200% and maybe that's the behaviour that you are seeing.

Just guessing. But in any case, we've used a sort of trick to fool the firmware into taking a normal mixing hot end type of extruder configuration and using it to control extruders that are actually in a push-pull arrangement. So strange things might happen if you then try to control each extruder independently (which is what the sliders do). For that reason, it's probably better if you don't mess with the sliders. If you have to make adjustments to one extruder with respect to the other, it might be better to adjust the steps per mm for that extruder.

Thanks! I'll look into this.

@matteo2u

… should be barking up a tree in a Cura forum?

First, you should have a look at the last, say: 10 lines of your .gcode files - take one which parks the head properly after printing, compare this to a file which leaves the nozzle stuck to the build.

On the Mac, you can open a .gcode file from Cura with TextEdit. Just scroll down to the very end…

There, I think you might find something like M18 or M84, Gcodes who turn off the steppers, thus disabling any further movement of the head. Note that there are other candidates I’m just not aware of, look up the commands here to understand what’s happening.

Glad you solved it. Yes, stepper motors are noisy. The belts can also generate static, which may cause static discharge to the motor terminals. For this reason we recommend that stepper motor bodies are grounded, either through the printer frame if it is metallic, or using a ground wire.

@Bravewildheart the m558 and g31 commands define the probe. M557 defines the mesh size. M558 P10 is for stall detection probing. Then g29 will start the routine and create the heightmap.csv.

Thanks for the peace of mind! (piece of mind? :))