Bricked My Machine #20
Replies: 7 comments 12 replies
-
What do you have in /home/mike/printer_data/config/printer.cfg? The new klipper/moonraker uses a bit different paths see #19. So you have to use new ones (they are also in the updated readme). |
Beta Was this translation helpful? Give feedback.
-
@JesterIsDead Kiauh usually installs your printer configuration into a sub directory depending on what you named your printer. I.e Can you run the following on your machine so I can verify this? I recently installed this after using Kiauh, which lead to me making my pull request here:
|
Beta Was this translation helpful? Give feedback.
-
Fresh install of Armbian and Klipper. |
Beta Was this translation helpful? Give feedback.
-
I'm working on it now, do you have discord by chance? That SS was likely right after my re-flash. I can resend now. Actually oddly enough, I get different results from SSH and via direct. |
Beta Was this translation helpful? Give feedback.
-
Ok, clean Arbian, Klipper, Mainsail and Moonraker. Using the "make menuconfig" for Klipper I get the following and I am assuming settings at this point. I only have UART interface (serial technically) and some speed and baud to change. GPIO I'm guessing is not needed now. |
Beta Was this translation helpful? Give feedback.
-
I have this working via USB now after reflashing the 32u2 on the Einsy. |
Beta Was this translation helpful? Give feedback.
-
So I followed the instructions here and now have a bricked machine. I updated the items noted to be off such as file paths from previous Mainsail builds but no matter what Klipper will not connect to the MCU. The log is showing its trying to load a printer.cfg file that is empty, yet when I go into the UI or Putty, the file in that directory is normal. The below text is from the klippy-log, If I look at the file noted under "Args" that is the file I see in the web-ui, which is not the blank one. Any hints would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions