Prusa-firmware: M500 and EEPROM functions

[pboschi]

M500 function can't be enabled; the max_*_jerk variables don't exist (they have to be renamed) and also some variable declarations about preheat temperature are kept off by some #define.
Anyway, after fixing those bugs, the M500 still doesn't store values into eeprom (e.g., PID tuning values).

[bubnikv]

The Prusa3D firmware does not store any usual Marlin configuration values
into EEPROM as of today. This is intentional, the configuration values are
expected to be set to the optimal values by the manufacturer.

On Thu, Dec 8, 2016 at 3:02 PM, pboschi [e-mail] wrote:

M500 function can't be enabled; the max_*_jerk variables don't exist (they
have to be renamed) and also some variable declarations about preheat
temperature are kept off by some #define.
Anyway, after fixing those bugs, the M500 still doesn't store values into
eeprom (e.g., PID tuning values).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/Prusa-Firmware/issues/21, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFj5IzVvzZCc_drMk62AixyMv9lFy5Sfks5rGA3ngaJpZM4LH2ZK
.

[nicw]

Hi, I'm coming over here from Unable to set PID settings, which are settings that are very specific to an individuals printer. We need to be able to set those in EEPROM.

I understand that Prusa wants to have an optimal configuration, but this is not a product meant to work out-of-the-box; Prusa _literally_ uses zipties to hold its product together. Tolerance is too great to consider anything optimized.

Please reconsider blocking users from setting EEPROM values.

[ryanneufeld]

@bubnikv I can tell you that the manufacturer PID values are 100% not optimal for every printer.

With the stock values I was seeing 2-5 degree temp swings. Additionally now that Prusa has started quietly shipping w/ 40w heat cartridges the PID values will again not be optimal.

Please re-enable this feature, or provide instructions on how to properly build this firmware so we can do it our selves.

[bubnikv]

We plan to enable the storing / loading of the EEPROM values, but there multiple things on our plate.

[GreatGrizzly]

I am probably over simplifying this, but would fixing this just mean uncommenting

define EEPROM_SETTINGS

in configuration.h?

[pboschi]

This thread is about the problems you encounter AFTER you do that!

[jspiro]

Looks like this was addressed in the new release candidate!

[jspiro]

@PavelSindler Thanks for addressing this btw, with my e3d socks on it's great having the tuning saved. Will this persist across firmware updates?

[bubnikv]

Yes, these settings will not be influenced by the firmware update.

On Feb 4, 2017 8:52 AM, "Jono Spiro" [e-mail] wrote:

@PavelSindler https://github.com/PavelSindler Thanks for addressing
this btw, with my e3d socks on it's great having the tuning saved. Will
this persist across firmware updates?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/Prusa-Firmware/issues/21#issuecomment-277426936,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFj5I4VznevHbdqJ156v3vXV1VyREJrxks5rZC5RgaJpZM4LH2ZK
.