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

Internal error during connect: 'ManualExtruderStepper' object has no attribute 'cmd_SET_E_STEP_DISTANCE' #530

Open
koekie40 opened this issue Nov 20, 2024 · 3 comments
Labels
believe fixed / answered The bug is believed fixed in latest release stale

Comments

@koekie40
Copy link

koekie40 commented Nov 20, 2024

I am going through set up of Happy Hare V3 now and I'm getting this error 'ManualExtruderStepper' object has no attribute 'cmd_SET_E_STEP_DISTANCE'
I am still kind of new Happy Hare and the ERCF ERCF v1.1. i have also try to do a restart a Firmware restart
I am following the guide and I'm afraid I'm over looking something simple.
Schermafbeelding 2024-11-20 190634

@ningpj
Copy link
Contributor

ningpj commented Nov 23, 2024

how up to date is klipper? Theres been allot of changes to klipper over the last 12-mths that required updates to HH and there is now a dependency between to two so will need to keep klipper reasonably up to date.

Update klipper and try again

@moggieuk
Copy link
Owner

moggieuk commented Dec 5, 2024

Hi, sorry for the delay. You are using and VERY old version of Happy Hare that is deprecated and not supported anymore. The new version v2.7.3 and soon to be released v3.0.1 don't use ManualSteppers.

It is possible that if you did upgrade to v2.7.3 / v3.0.0 from a very old version that the upgrade of mmu_hardware.cfg was not able to be performed. The best thing to do is to save the info from that file (then DELETE the file) and re-run:

./install.sh -i

This will re-create a correct mmu_hardware.cfg to which you can apply the configuration from your previous install.

@moggieuk moggieuk added the believe fixed / answered The bug is believed fixed in latest release label Dec 5, 2024
Copy link

github-actions bot commented Jan 4, 2025

This issue is stale because it has been open for over 30 days with no activity. It will be closed in 14 days automatically unless there is activity.

@github-actions github-actions bot added the stale label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
believe fixed / answered The bug is believed fixed in latest release stale
Projects
None yet
Development

No branches or pull requests

3 participants