-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ERCF V1.1 #11
Comments
Hi, |
I just built it but currently don't have any multifilament prints planned. If the V2.0 encoder works, then my mod also works. The only thing I changed is the magnet on the back, which I can confirm can open the V1.1 gates. |
so... if i have a v1 with binky, springy, sturdy bunny and triple decky.. i pretty much have a V2 minus some bling? |
Maybe... I designed the Encoder to work with the default V1.1 Filament blocks |
With all the mods it is basically already a V2, if you are still using the triple decky magnet gates try this mod, otherwise the normal Beta6 files should work just fine |
ok, sweet. just noticed i wrote the wrong block mod. i use thumper blocks :) |
I added the V-Bearing Version of the Encoder and removed the clearance i needed |
Hi again, |
I don't know completly understand what pull requests are but yes, do so. |
You are not the only one who doesn't understand how PRs work, already got some feedback that this system is way to complicated. I completely agree since it took me almost a month to understand GitHub completely, it's not really user friendly but sadly the only way how others can contribute to the repository. Sorry for the hassle, here is a cookie 🍪. |
I am using ERCF system V1.0, but with binky style optical decoder. |
According to my understanding, with Beta6 ERCF V1 is no longer supported because the new Binky Encoder no longer has a magnet to open the gates. So I added the magnets back (and 0.2mm clearance between the filament blocks and the encoder) to the 623 Bearing Version.
V1.1 Binky Encoder for 623 Bearing.zip
The text was updated successfully, but these errors were encountered: