Can reflash Klipper in MCU?

Basic Information:

Printer Model: Vcore 3
MCU / Printerboard: Octopus Pror
Host / SBC rpi4
klippy.log

its strange

{“error”: {“code”: 404, “message”: “Not Found”, “traceback”: “Traceback (most recent call last):\n\n File "/home/pi/moonraker-env/lib/python3.11/site-packages/tornado/web.py", line 1790, in _execute\n result = await result\n ^^^^^^^^^^^^\n\n File "/home/pi/moonraker/moonraker/components/application.py", line 795, in get\n self.absolute_path = self.validate_absolute_path(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\n File "/home/pi/moonraker-env/lib/python3.11/site-packages/tornado/web.py", line 2900, in validate_absolute_path\n raise HTTPError(404)\n\ntornado.web.HTTPError: HTTP 404: Not Found\n”}}

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hi,

I was updating Klipper on the MCU and when I thought it was finished I rebooted… but I think it was NOT finished.

I use Fluidd, and it doesn’t access the MCU… I tried to log in to rpi and send a LSUSB, and the MCU is listed…

When I try to record the LOG, to attach it to this message, it redirects me to a website where you can see the message I posted.

What options do I have?
How can I know if it’s fried?
Can I flash Klipper again with an SD card?
Is there another option?

thx in advance

I really have a hard time to follow this description and understand your issue.
Please check How-To Ask for Help. Here are various methods listed to access the relevant log files.

2 Likes

Sorry, my English is not very good, I use Google Translator… I’ll try to rephrase the question.

First of all, I don’t attach any Klippy.log, because I can’t download it, when I try I get the message in Fluidd that I posted above…

{
  "error": {
    "code": 404,
    "message": "Not Found",
    "traceback": "Traceback (most recent call last):\n\n  File \"/home/pi/moonraker-env/lib/python3.11/site-packages/tornado/web.py\", line 1790, in _execute\n    result = await result\n             ^^^^^^^^^^^^\n\n  File \"/home/pi/moonraker/moonraker/components/application.py\", line 795, in get\n    self.absolute_path = self.validate_absolute_path(\n                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\n  File \"/home/pi/moonraker-env/lib/python3.11/site-packages/tornado/web.py\", line 2900, in validate_absolute_path\n    raise HTTPError(404)\n\ntornado.web.HTTPError: HTTP 404: Not Found\n"
  }
}

The problem occurred this morning, I looked at the Fluidd updates section and it said there was one for Klipper and for something else… I don’t remember. In general, when there are updates for Klipper I apply them.

Well, when I thought I had finished the installation, I restarted the printer (but I think I had NOT finished)…

When the restart process finished, I accessed Fluidd through the WEB portal and I get the message that it can’t access Klipper.

After several restarts, I decided to check if rPi “saw” the MCU. So I connected to rPi with Putty and sent the command “lsusb”, with this result:

I checked that the Octopus board ID had NOT changed, and that I had it correctly in the rPi CONFIGURATION

and my config in fluidd

After trying a couple more things without success, I tried to reflash Klipper on the MCU, using the method I originally used, using the SD.

But after doing the procedure, the result is the same. Fluidd does NOT connect to the MCU (Octopus Pro)

I was asking what I can do to reestablish communication between rPi and the MCU… or if on the contrary, by finishing the update early I had “fried” something…

What can I try?

You already used Putty to connect to your Rpi.
You may use the search function here to search in which directory on your Rpi the “klippy.log” is stored


or Klpper documentation Debugging - Klipper documentation

Good luck, hcet14

  1. Disconnect the Octopus board
  2. Reconnect the board
  3. Follow How-To Trouble-Shoot

i have find klippy.log

klippy.log (5.6 MB)

i have sended dmesg by console… but i cant interepretate.

can someone help me?

Thx
dmesg.txt (36.7 KB)

EDIT: Without knowing much…in dmesg appears listed Octopus…
andin lsusb result does appear detected by rPi.

I’m not sure that I understand your report:

  • dmesg shows that the Octopus MCU is correctly enumerated
  • your latest klippy.log shows a correct Klipper start with connected Octopus MCU

my god…

solved…

i have use Kiauh, and Rollback Klipper…

AND NOW WORKS…

thanks, as ever for your help, and sorry for disturb

versions after rollback…

now i am triying to rerun update… more info later…

eiii…

after update… now works…

and screenshot working

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.