Skip to content
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

[FR] DIAG1 stallGuard as additional filament runout sensor #16

Open
q3ok opened this issue Feb 21, 2018 · 3 comments
Open

[FR] DIAG1 stallGuard as additional filament runout sensor #16

q3ok opened this issue Feb 21, 2018 · 3 comments

Comments

@q3ok
Copy link

q3ok commented Feb 21, 2018

While the DIAG1 on X and Y axis can be used for sensorless homing, there I found additional usage of the stallGuard for E axis. It can be connected to filament sensor pin, to trigger the M600 when the filament is clogged, and detected by TMC2130.
Together with filament sensor and connected with OR logic gate made from two diodes and resistors this can detect more problems with the filament.
I strongly believe it's not a big problem to implement this, as it should be just enabling the DIAG1 as stallGuard on E stepstick, and there will be more with the cable connections :)

@teemuatlut
Copy link
Owner

Sounds like a good idea.
However, I'd rather not go the way of having users making OR gates for themselves. Merely checking two pins should be easier from end user perspective.

@q3ok
Copy link
Author

q3ok commented Feb 21, 2018

I was thinking about logic gate, as soon there will be no enough free pins to connect something more :) 5 stepsticks + software SPI to avoid problems with SD cards, its 8 pins, so the whole AUX2 on ramps will be used, two pins for filament runout sensor and stallguard from E motor, and only 4 pins are left, when the RRD fan extension will be used - even no more easily accesible pins. More pins free will be available only if not every endstop will be used, but using the sensorless homing on X and Y can give 2 free pins from MAX endstops. And it's still on just one extruder, what if we want to have additional extruder, also driven by TMC2130? Even with any multiplexer, there can be a problem :)

@monterman
Copy link

I second this initiative! I have azteeg x5 gt, got it to compile with your bf2 2660 branch with all tmc2660 5x drivers. I have a filament runout sensor conected but adding the stallguard to the 2660's is the challenge. Let me know if I can test anything for you?

teemuatlut pushed a commit that referenced this issue Oct 10, 2019
# This is the 1st commit message:

Add Support for ADIMLab Granty

# The commit message #2 will be skipped:

# Update Configuration.h

# The commit message #3 will be skipped:

# Add files via upload
#
# Add Support for ADIMLab Granty

# The commit message #4 will be skipped:

# Create Configuration.h

# The commit message #5 will be skipped:

# Delete Configuration.h

# The commit message #6 will be skipped:

# Create Test.h

# The commit message #7 will be skipped:

# Add files via upload

# The commit message #8 will be skipped:

# Delete Test.h

# The commit message #9 will be skipped:

# Delete Configuration.h

# The commit message #10 will be skipped:

# Delete Configuration_adv.h

# The commit message #11 will be skipped:

# Add files via upload
#
# Add ADIMLab Pins

# The commit message #12 will be skipped:

# Add files via upload
#
# Add Bootscreen

# The commit message #13 will be skipped:

# Update Configuration.h
#
# Add Bootscreen

# The commit message #14 will be skipped:

# Update pins.h
#
# Add ADIMLab Board

# The commit message #15 will be skipped:

# Update boards.h
#
# Add ADIMLab Granty

# The commit message #16 will be skipped:

# Update Makefile
#
# Add ADIMLab Granty

# The commit message #17 will be skipped:

# Update boards.h

# The commit message #18 will be skipped:

# Update Makefile
teemuatlut pushed a commit that referenced this issue Oct 10, 2019
* # This is a combination of 18 commits.
# This is the 1st commit message:

Add Support for ADIMLab Granty

# The commit message #2 will be skipped:

# Update Configuration.h

# The commit message #3 will be skipped:

# Add files via upload
#
# Add Support for ADIMLab Granty

# The commit message #4 will be skipped:

# Create Configuration.h

# The commit message #5 will be skipped:

# Delete Configuration.h

# The commit message #6 will be skipped:

# Create Test.h

# The commit message #7 will be skipped:

# Add files via upload

# The commit message #8 will be skipped:

# Delete Test.h

# The commit message #9 will be skipped:

# Delete Configuration.h

# The commit message #10 will be skipped:

# Delete Configuration_adv.h

# The commit message #11 will be skipped:

# Add files via upload
#
# Add ADIMLab Pins

# The commit message #12 will be skipped:

# Add files via upload
#
# Add Bootscreen

# The commit message #13 will be skipped:

# Update Configuration.h
#
# Add Bootscreen

# The commit message #14 will be skipped:

# Update pins.h
#
# Add ADIMLab Board

# The commit message #15 will be skipped:

# Update boards.h
#
# Add ADIMLab Granty

# The commit message #16 will be skipped:

# Update Makefile
#
# Add ADIMLab Granty

# The commit message #17 will be skipped:

# Update boards.h

# The commit message #18 will be skipped:

# Update Makefile

* Add Support for ADIMLab Granty

* Optimize bootscreen

* Update Makefile

Updated Description

* Update boards.h

Updated Description

* Update pins_HJC2560C_REV2.h

Updated Description

* Update Configuration.h

Added Author + Custom_Machine_Name

* Create _Bootscreen.h

Add Bootscreen

* Add files via upload

Add ADIMLab Granty v1

* Update boards.h

Add ADIMLab Granty v1

* Update Makefile

Add ADIMLab Granty v1

* Update pins_HJC2560C_REV2.h

* Consolidate Granty configs

* config updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants