CommandWrapper instance has no attribute 'get_command_tag'

General Discussion
1

Hey guys,

I’m pretty new to Klipper, I’m running a neptune 4 pro and just updated the firmware from Elegoo, now I am getting an error:

Internal error during connect: CommandWrapper instance has no attribute ‘get_command_tag’

I can’t for the life of me work out why the error is occuring.

I’ve attached the klippy log which led me to look at the stepper.py file (also attached as a txt file), and I have attached my printer.cfg file for good measure.

Anyone have any ideas?

Thanks!
Chris
klippy.log (1.3 MB)
printer.cfg (12.6 KB)

1 Like
2

stepper.txt (19.9 KB)

3 
Git version: 'v0.11.0-271-g5f990f93-dirty'
Untracked files: klippy/extras/gcode_shell_command.py, klippy/extras/x_twist_compensation.py
Modified files: klippy/extras/probe.py, klippy/gcode.py, klippy/mcu.py, klippy/stepper.py
Branch: master
Remote: origin

Your version of Klipper has been modified with unofficial files. Go back to an original Klipper and try again. The error is almost certainly caused by such a modification.

4

Thanks for your reply. I’ve got no idea how that would have happened. I’ve reflashed the firmware provided by elegoo and I’m still getting the same error unfortunately.
Would replacing the files with stock files cause other issues?

5

Ok so I took a risk and just copied the mcu.py file from github via ssh, restarted the printer, and it the printer is back up and running.
Thanks for your help!

6

Where did you download this Klipper from?
It is very dangerous and can cause a lot of unwanted effects if you just replace files.

I strongly recommend that you run a clean Klipper from GitHub - Klipper3d/klipper: Klipper is a 3d-printer firmware unless you know exactly what you are doing and are able to troubleshoot if something does not work as intended.

1 Like
7

Hey guys,

I my pretty new to Klipper as well and I have the same issue as chris had. I cant get mine running because I have no clue how chris did it.

8

It wasn’t too difficult. The exact process was:

  • Download the file from the Klipper GitHub
  • Log into the printer via a SSH client, I used WinSCP
  • Copy the file to your desktop as a backup
  • For good measure I did do a line by line comparison of the two and found nothing meaningful so decided to take the risk
  • Via WinSCP, copy the file you got from the Klipper GitHub and replace the file that has the issue
    Just keep in mind that it is a risk to do this, and your issue may not necessarily be exactly the same as mine. Is yours a Neptune 4 as well? I’ve found Elegoo are quite helpful so if you haven’t already definitely reach out to them.
    With that in mind my printer has since been running fine, with no issues.
    Hope that helps
9

Hello,
Copying the file is not the only thing to do, I also updated klipper and moonraker as I should not have and had issues. Follow these instructions:
https://www.reddit.com/r/ElegooNeptune4/comments/16u0m7x/gcode_shell_command_clear_plr_how_to_fix/

Hope it helped :slight_smile: