search

Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.34k stars 5.28k forks source link

Question- Is it necessary to update MCU firmware? #2404

Closed scarecrow2k6 closed 4 years ago

scarecrow2k6 commented 4 years ago

I am running Klipper on top of the Smoothie firmware. Is it necessary to update the Smoothie firmware if I want any new features? Or is it that Klipper overrides and becomes the primary fw and only uses the MCU for the hardware? I hope my question made sense, I'm new to this.

klipper-gitissuebot commented 4 years ago

Hi @scarecrow2k6,

It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions).

Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days.

For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md

The log can still be attached to this ticket - just add a comment and attach the log to that comment.

Best regards, ~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

timmit99 commented 4 years ago

Klipper is the firmware. When you flash the MCU's with the klipper.bin from the make menuconfig and make flash commands it erases whatever was on the MCU and puts the klipper "slave" code on it. there would be no smoothieware left so you only have to update the Klipper code and possibly reflash if the code requires an MCU update.

This make sense?

scarecrow2k6 commented 4 years ago

Klipper is the firmware. When you flash the MCU's with the klipper.bin from the make menuconfig and make flash commands it erases whatever was on the MCU and puts the klipper "slave" code on it. there would be no smoothieware left so you only have to update the Klipper code and possibly reflash if the code requires an MCU update.

This make sense?

Yes absolutely, for some reason I thought Klipper ran on top of the original fw. Didn't know it actually replaced it. The reason I say that because I have been using a Raspberry Pi + Klipper, I thought Klipper ran on RPi on top of Smoothie (Smoothie being dormant). Thanks for your answer!

timmit99 commented 4 years ago

Youa re very welcome and welcome to Klipper. Having a single file to edit your settings and not having to flash EVERY time you want to change a minuscule setting is so worth it!

WojciechBednarski commented 4 years ago

I'll add my 5 cents to that question, and ask - does Klipper report in Octoprint that the MCU firmware has to be updated?

KevinOConnor commented 4 years ago

This is answered in the FAQ - https://www.klipper3d.org/FAQ.html#how-do-i-upgrade-to-the-latest-software . In short, yes, the software should inform the user if a flash is necessary.

-Kevin

KevinOConnor commented 4 years ago

I'm going to close this as it looks like the original question was answered.

-Kevin