Teaser of upcoming version 5.1 - Runout sensor

Here is an image of what the settings for the runout sensor will look like.


It will be possible to set the amount of filament to extrude before pausing when no filament are detected (it is typically the distance between your sensor and the extruder). You will be able to choose the trigger (high to low or low to high) since there are many different sensors. The filament LED is there to help you test if your sensor is properly detected.
I have finished the implementation of this new feature but I have some small bugs to fix. Version 5.1 will also be based on Marlin, currently the latest version.

Is there a recommend sensor or sensor you are testing with?

Any sensor should work

Any idea of What I/O pins its gonna be using. I’m about to open mine up and would like to add the wiring for it while im down there.

Pin 3 on the EXT connector (PC1). And ground also of course (pin 9)

Thanks :+1:

If I read the below diff properly, this mod will not be compatible with the Silence3D stepper mod as it uses PC1 for the Y_STEP_PIN. Is that correct?

diff -ur “projects/3D print/Silence3D/Stock-ADVi3pp-advi3-4.0.6/Marlin/pins_I3_PLUS.h” “projects/3D print/Silence3D/ArduinoCore-4.0.6.S.4.rar_ADVi3pp-advi3-/ADVi3pp-advi3-/Marlin/pins_I3_PLUS.h”
— “projects/3D print/Silence3D/Stock-ADVi3pp-advi3-4.0.6/Marlin/pins_I3_PLUS.h” 2020-03-08 11:15:45.000000000 -0700
+++ “/projects/3D print/Silence3D/ArduinoCore-4.0.6.S.4.rar_ADVi3pp-advi3-/ADVi3pp-advi3-/Marlin/pins_I3_PLUS.h” 2020-03-30 18:24:59.959284200 -0700
@@ -49,13 +49,13 @@
// Steppers
-#define X_STEP_PIN 61 // PF7 / A7
-#define X_DIR_PIN 62 // PK0 / A8
-#define X_ENABLE_PIN 60 // PF6 / A6

-#define Y_STEP_PIN 64 // PK2 / A10
-#define Y_DIR_PIN 65 // PK3 / A11
-#define Y_ENABLE_PIN 63 // PK1 / A9
+#define X_STEP_PIN 37 //silence3d
+#define X_DIR_PIN 35 //silence3d
+#define X_ENABLE_PIN 56 //silence3d
+#define Y_STEP_PIN 36 //silence3d
+#define Y_DIR_PIN 34 //silence3d
+#define Y_ENABLE_PIN 40 //silence3d

#define Z_STEP_PIN 67 // PK5 / A13
#define Z_DIR_PIN 69 // PK7 / A15
@@ -65,6 +65,9 @@
#define E0_DIR_PIN 59 // PF5 / A5
#define E0_ENABLE_PIN 57 // PF3 / A3

+#define Y_CS_PIN 32 // silence3d
+#define X_CS_PIN 33 //silence3d
// Temperature Sensors

Silence3D Is using its own firmware, so they can use whatever they like.

Thank you for the update, I’m sure this may have already been asked but when will this be available?

Thank you

I want to also fix some existing bugs in current version and check carefully some behaviors raised by some people that may be bugs. So end of this month or beginning of March.

Thank you

Maybe a can give a more complete version of my answer: As far as I know Silence3D use an old version of ADVi3++, a fork of version 4. So in order to support new features of version 5 and later, they will need to adapt their fork and align it with ADVi3++. During this work, they can choose another pin for the runout sensor.

Another thing: I will not allow to change the pin from the LCD panel because it would require too many changes in Marlin and will consume more memory.

Thanks for your reply. Yes, it is a fork of ADVi3pp 4.0.6. I completely understand about limitations of the LCD.

On the surface, the complete diff between the two has some additional code for a fan mod they produce. I do not have that mod. I am trying to just isolate the changes for the steppers. For pin changing, I thought about adding logic to select the alternate pins in gcode. However, It looks like there is also a change to the driver type. So it might not be possible to support both drivers configurations in one binary without some other changes. For now I’ll research more and see if their mod can use a different pin. I’ll open a another topic if I can make something workable.

Yes they use other drivers, this how they achieve a more silent printer at the level of the stepper motors. If I remember well, they have indicated in their source code all of their modifications with something like @silence. Something like that.

So I just noticed pin 9(ground) is being used by the bl touch. Would it be ok splitting the wire into a y connector to be utilize for both the bl touch and runout sensor?


I am currently testing and fixing the small latest bugs. I think I will be able to release 5.1 at the end of this week.

1 Like