Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESP32 eeprom saves needs planner sync. #24753

Closed
wants to merge 1 commit into from
Closed

ESP32 eeprom saves needs planner sync. #24753

wants to merge 1 commit into from

Conversation

philmb3487
Copy link

Description

This is related to #17946. On my platform ESP32 there is a delay of around 1-second whenever an EEPROM save occurs, which happens during the print counter save step. This causes layer shifts.
Is there any reason not to enable PRINTCOUNTER_SYNC globally for all platforms?

Requirements

Benefits

Configurations

Related Issues

@thisiskeithb
Copy link
Member

thisiskeithb commented Sep 11, 2022

Is there any reason not to enable PRINTCOUNTER_SYNC globally for all platforms?

It’s not needed for real EEPROMs, at least not on STM32 and LPC:

That and pausing all motion during printing isn’t exactly desirable as a default behavior.

// ESP32 boards seem to lose steps when saving to EEPROM during print (see issue #20785)
// TODO: Which other boards are incompatible?
#if PRINTCOUNTER_SAVE_INTERVAL > 0
#define PRINTCOUNTER_SYNC 1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #24731 for existing methods of applying this.

@philmb3487
Copy link
Author

philmb3487 commented Sep 11, 2022 via email

@EvilGremlin
Copy link
Contributor

EvilGremlin commented Sep 11, 2022

Nope, you enabled it gloabally for ESP32, which is not the best solution. Better make it on NONE(I2C_EEPROM, SPI_EEPROM, QSPI_EEPROM, SRAM_EEPROM_EMULATION) condition, so whoever decide to add one of these won't have anything to worry about.

@philmb3487
Copy link
Author

I don't understand. Someone please fix this, losing a kilo of filament to a 2mm layer shift fk sucks.

@philmb3487 philmb3487 closed this Sep 11, 2022
@philmb3487 philmb3487 deleted the pr-printcountersync branch September 11, 2022 20:56
@EvilGremlin
Copy link
Contributor

#if PRINTCOUNTER_SAVE_INTERVAL > 0 && NONE(I2C_EEPROM, SPI_EEPROM, QSPI_EEPROM, SRAM_EEPROM_EMULATION)

@EvilGremlin
Copy link
Contributor

Well, none of the hardware i know about have any of these so your variant will do fine in any forseeable future, but futureproofing is always nice :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants