X-In/1-Out Non-Mixing Extruder Config

Team help please, can some one without being a troll or other “wise ass” give my sound advise after looking at my log to see why the one runout works on T0 this log is from my T0 with filament and T1 T2 I remove the filament to cause a runout on T1 T2, to trigger, but it does not. Again with it is trigger the mainsail shows empty on the screen but does not trigger the pause. for T1 or T2 only T0 will trigger. I see that it is in the sync of the runout switch with the extruder, but anything I try does not work yet…

Sorry logs to follow creating a new fresh log.

**EDIT ok I Give up I cannot get the encoder runout working in the “extruder_stepper” config… it seems like it will only allow one “extruder” to work. I think we need to do some kind of sync like with the “motion” sync. but I do not see a way.
First log is running though with all filament in and working.
Next log is running though with all creating an runout on T0 There is no dertection on the screen or the logs for T1 & T2

printer.cfg (22.2 KB)
moonraker.log (6.2 KB)
klippy.log (657.9 KB)
klippy (1).log (652.5 KB)

Hi there.
Maybe I was a bit stupid.

I changed the G-Code Flavor to Marlin and now it seems to work. No more tries from PrusaSlicer to change the Pressure Advanced to 0 in the generated g-code

@HoltiWilan
Check out this document on how to setup the Slicer: X-In/1-Out Non-Mixing Extruder - Automate SuperSlicer & PrusaSlicer Filament Swaps

Although I’ve created the documentation using SuperSlicer, setting up Prusa Slicer is very similar.

Regarding your issue on Pressure Advance, that is in your Slicer Tool Change customer G-Code. I’ve put in Pressure Advance strings in each Filament start G-Code as PA can be unique per filament and extruder.

Hope this helps.
-James

@Snakn1
I’m not using a rotary encoder, but my understanding is that you should have one Filament Run-Out sensor active at a time.

Reference: G-Codes - Klipper documentation

When you change to a new extruder, activate the Filament Run Out Sensor, and before changing, deactivate it.

SET_FILAMENT_SENSOR SENSOR=<sensor_name> ENABLE=[0|1]

I do not want to sound like I know anything. I do not, or I would find a fix on my own. I have tried all the options and choices. This has to be a bug in klipper. I tried to report it in GitHub, it only lets you post here… so no one in the know is looking in to it.

I have tried all different configs. The motion side works great, it is only when you are using more then one motion type runout sensors and the stepper_extruders. Even a 2 in to one. if you are using a “motion sync” config to use the same hotend it only triggers on the main or T0 not on any other extruders or the “stepper_extruder” I have tried all different possible ways to help troubleshooting this issue with the same outcome.

I needed to get something working so for now only as a temp workaround. I first "rem or # " out all the runout motion sensers and made one runout switch (non motion) the motion still did not work even if it was going to T0 input only. I first fooled it with the hardware below and just passed the input from the runout to the mcu depended on the T0, T1 or T2 active. It would show empty on Mainsail but Klipper did not trigger. I then created a external hardware (Pi Pico) that I have 6 inputs 3 for the sensing pins for there motion runout sensors and 3 for the T0, T1 and T2 extruders that I control with a command shell prompt macro. I then count the pluses and as long as there is at lease a pulse a sec it I push the output pin to high to let klipper know I have filament. I also made a few custom cables to connect everything so I did not have to destroy my current cables.

I’m using the same setup, also two in and one out non-mixed colors. But I have a problem with my machine. When I print a single color model, the surface of the model is very smooth with no lines, but when I print a two color model, the single color part is fine, but when I print the two color part, there are 3D printing layer lines. do you have any problem with this?

Going from white to red and back again is a high change In pigmentation.

Looks like you might not be purging enough between color changes.

  1. Check under Filament → Multimatetial → pigment percentage, if using Prusa Slicer/Super Slicer. Adjust the number accordingly for each color.

  2. increase the size of the purge block.

Pigment Percentage should be adjusted from 0 to 1 based on the filament pigment. 0 = natural/clear. 1 = black. This should be taken into consideration for how much purging is necessary to clean out the nozzle during the wipe tower moves. example: Light to Dark = less purging, Dark to Light = more purging needed.

For my printer, the xy axis is a 57 closed loop stepper motor, model MKS servo57D. the dual z-axis is a 42 stepper motor with 1204 ball screws. The hot end is two 36 stepper motor HGT extruders and a 2in1 3DSWAY dual color print head.Semiconductor cooling and water cooling at the hot end。The white and red color ratio is 50:200, and even then the model has 3D printing layer lines on the surface.Help me, thank you very much.
config.zip (12.2 KB)
pictures1.zip (2.5 MB)



To me it looks like you have a setting wrong in the slicer it appears the layer height is different between the two slicer setting in the two extruders.


According to the preview of the slicing software prusaslicer, the layer heights are all 0.2According to the preview of the slicing software prusaslicer, the layer heights are all 0.2

@magical3D
It may also be more flow settings settings are more for the red filament?
Could also be different settings for each extruder?

In your circular towers, swap the red for white and white for red filaments and print the same g-code you previously did. I’d expect the red color to be tight layers and the white to be wide.

I’m willing to help, but you have to do the work so you understand how to ‘fix’ your setup.

In the physical printer is both extruder stepper A and B the same steppers and exturders? If they are physically the same, are they setup the same in printer.cfg? If they are physically different, are they setup correctly?

My guess is this is your issue. You’re extruding 4x the red over the white filament?

You should be extruding the same filament, just purging more white filament than red in the purge block so you can clear out the red pigment before printing white on the model.

Hey guys, hoping someone can help me out. I can’t seem to get my 2 in 1 out non-mixing setup working. I’ve ruled out physical problems, such as bad cables, as well as pin designations. I’m not getting any errors. I have attached my klipper log and printer config files.
On startup, my extruder will extrude when commanded to do so. When I give a T1 command, it reports back that my belted_extruder is now syncing to extruder. However, when I issue an extrude command, neither extruder moves. If I issue a T0 command, then an extrude command, my extruder will move. Basically, my belted_extruder is not moving when it should be. Any thoughts?
printer.cfg (19.8 KB)
klippy.log (3.7 MB)

@tymau5, your T0/T1 macro looks good
The only thing I can think, atm, is your belted_extruder is not setup correctly.

Looks like the enable_pin needs to be inverted. Add an ! In front of PD13

step_pin: PD11
dir_pin: !PD10
enable_pin: PD13
microsteps: 16
rotation_distance: 34.406

If that does not work, I would take these settings from belted_extruder and swap them into extruder to see if the second extruder works.

-James

Mannnnn do I feel so dumb! Sure enough that did it. I checked to make sure the pins were correct, but I put the “!” in the wrong place. I have been trying to figure this out for longer than I want to admit :smiling_face_with_tear: . Thank you!!

1 Like

No problem. Enjoy.
BTW, I’m working on updating my Slicer doc post related to multiple extruders. Don’t forget to check that one out too.

1 Like

I’m currently using CURA. From what I understand so far, CURA doesn’t require much modification, is that correct?

That’s a good question, I have not used Cura in a long time.

I don’t think Prusa/Super Slicer needs much modification, just an understanding of how to configure it for the printer.

For Cura there are 2 plugins you want to use, but other then that it is good…

Has anyone figured out how to use two ( or my case 3) motion stye of runout detector with this stepper extruder sync config? I gave up and I had to go back to separate extruders ( I use a three in one) and force the “shared pins” so it would let me use my three big thee tech (V1) smart runout. The motion side, works great only on the first motion style detector, but the system ignores all other detectors, regardless on any setting or workaround micro. (tried for 2 months)

*** Note if setup with microswitch style , that works on all extruders, but I only want to use my motion style, I will not downgrade to get it to work. So I went back to the old way and it works as intended.

I will go back to the stepper config after this is fixed… But there seems to be no real support or a valid way to submit a bug in GitHub.

[duplicate_pin_override]
pins:PA2,PF4

A comma separated list of pins that may be used multiple times in

a config file without normal error checks. This parameter must be

provided.