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

"solved"Internal error during connect: MCU_stepper instance has no attribute 'steppers #96

Open
PatrickYCY opened this issue Apr 14, 2022 · 5 comments · May be fixed by #100
Open

"solved"Internal error during connect: MCU_stepper instance has no attribute 'steppers #96

PatrickYCY opened this issue Apr 14, 2022 · 5 comments · May be fixed by #100

Comments

@PatrickYCY
Copy link

When include ercf's config have error as the tittle,
Attached the Klippy log for reference
Machine: Voron 2.4 350, MCU 1 BTT OCTOPUS V1.1, MCU 2 BTT Mini SKR E3 V2.0
klippy (2).log

@EtteGit
Copy link
Owner

EtteGit commented Apr 14, 2022

Please include the ercf cfg files at the end of your printer.cfg, not at the beginning

@PatrickYCY
Copy link
Author

Please include the ercf cfg files at the end of your printer.cfg, not at the beginning

I tried include the ercf cfg files at the end of the printer .cfg ,but with same error
attached new klipper log for reference
klippy (3).log

@Benoitone
Copy link

Benoitone commented Apr 15, 2022

Hello, if you name your mcu ercf you must adapt the pin with ercf to allow klipper to know on which mcu your ERCF is connected to.
And are you sure you declare correctly the mcu sections?

@PatrickYCY
Copy link
Author

i confirm that the ercf pins and config is declare correctly the mcu sections, and still error

@PatrickYCY PatrickYCY changed the title Internal error during connect: MCU_stepper instance has no attribute 'steppers "solved"Internal error during connect: MCU_stepper instance has no attribute 'steppers Apr 16, 2022
@cmroche
Copy link
Contributor

cmroche commented Apr 27, 2022

This will be fixed by #100

@cmroche cmroche linked a pull request May 7, 2022 that will close this issue
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

Successfully merging a pull request may close this issue.

4 participants