search

manu7irl / klipper-DWC2-installer

to streamline the install or upgrade of KLIPPER & DWC2 front-end for it. With these 2 together no need to use octoprint. I run mine on orangepi zero with H2+ CPU 512MB and it works nicely.
GNU General Public License v3.0
55 stars 13 forks source link

Invoking of the Webinterface isn't possible #7

Closed Peuqui closed 4 years ago

Peuqui commented 4 years ago

...even with a clean installation described from here: https://klipper.info/klipper-+-dwc2-1/installing-klipper-with-dwc2 or with your scripts, also fresh and clean installed. Then I tried to follow the "solutions" on several issues tracked from the original github sources and your responses there. -> no luck.

With Octoprint and the correspondent plugin, it runs smooth. But I wanted to go to DWC2...

manu7irl commented 4 years ago

Did check for errors in your klippy-0.log?

On Sun, Jun 14, 2020, 3:24 PM Peuqui notifications@github.com wrote:

...even with a clean installation described from here: https://klipper.info/klipper-+-dwc2-1/installing-klipper-with-dwc2 or with your scripts, also fresh and clean installed. Then I tried to follow the "solutions" on several issues tracked from the original github sources and your responses there. -> no luck.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/manu7irl/klipper-DWC2-installer/issues/7, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWT4RCYNN7NZZKPIHUNAV3RWS6PNANCNFSM4N5NW3DA .

Peuqui commented 4 years ago

I got to manage to sort out this issue: Was a config error in regard of the serial connection: the [mcu] was doubled in the printer-0.cfg, so that klippy won't start.

Sorry for that!

notp1ssed commented 3 years ago

I am having this same error, and double MCU is not the problem here, what more could it be?