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

Printer LCD stopped working after 1.7.0 final update (PRUSA logo not showing in self-check) #67

Open
F4r0kh opened this issue Jul 4, 2022 · 3 comments

Comments

@F4r0kh
Copy link

F4r0kh commented Jul 4, 2022

Great job guys... After the update to 1.7.0 final the monochrome LCD stopped working. Was surpriced I didn't hear the pealing sound of the first few layers on my SL1S. Tried cleaning the FEP foil via the new feature, nothing pealed off, poured the resin back to the bottle and the FEP foil was spotless. So I ran a self-check and when it was time to check the display, the PRUSA RESEARCH logo did not show up. After rebooting 3x and downgrading back to the previous stable version the selfcheck went fine and the printer is printing again.

@murk-sy
Copy link

murk-sy commented Jul 6, 2022

I've had issues installing beta4 and I went to verify this as I just upgraded, but the screen seems to work fine.

Are you using 1.6.6 now and did you attempt to install 1.7.0-beta4 before?

@F4r0kh
Copy link
Author

F4r0kh commented Jul 6, 2022

Yep, went from 1.6.6 to 1.7.0 and back. Have tried to install beta 4 a day before and almost bricked my SL1S, it got stuck on initializing after the update. Anyway yesterday I tried to install the 1.7.0 final again (from the same exact file) and it went fine and the display is working, so no idea why it was acting up the last time I installed it.

@Prusa-Support
Copy link

Hello,

thank you for sharing this error, we did not see it in any version so far. Could you please send us the log file to [email protected] or share the upload code?
We would appreciate more info about the details and perhaps we can find the cause for this within a short time.
Bricking the printer can happen but there is always a way to fix it. Our Technical support will be happy to guide you through it in case it happens

Sarah Kapodistria
Prusa Research

filipkotoucek pushed a commit that referenced this issue Mar 19, 2024
- 6193057: Update errors.yaml
- 0057469: Sl1 fix codes (#95)
- 46071ae: xl: G425 error codes
- 12bb215: Fix few issues (#93)
- 9838dd3: Update error-codes.yaml (#67)
filipkotoucek pushed a commit that referenced this issue Jun 6, 2024
- Prusa-Error-Codes@9bb23e3: Shorten power painic detected on startup, it did..
- Prusa-Error-Codes@14b01d0: Add MCU_MAXTEMP_ERR to MK3.5
- Prusa-Error-Codes@f37e3a7: Add MCU_MAXTEMP_ERR (#112)
- Prusa-Error-Codes@95837d1: Add XX601 and XX609 errors to yamls
- Prusa-Error-Codes@ffe5f4c: Edit XX401 error text
- Prusa-Error-Codes@c6f514a: Sync PEC and private
- Prusa-Error-Codes@bac05cb: Add MMU error from private
- Prusa-Error-Codes@8b0a264: Add CONNECT_REGISTRATION_FIALED
- Prusa-Error-Codes@98f438f: Delete duplicate
- Prusa-Error-Codes@e9e5670: Add type to MMU errors
- Prusa-Error-Codes@208b066: Update README.md
- Prusa-Error-Codes@008dce1: Update error-codes.yaml (#101)
- Prusa-Error-Codes@432c601: Update error-codes.yaml (#102)
- Prusa-Error-Codes@dcdef28: Update error-codes.yaml (#103)
- Prusa-Error-Codes@8d8a22f: Add iX and MK35 error codes.
- Prusa-Error-Codes@533524b: xl: Add dwarf nozzle overcurrent error code
- Prusa-Error-Codes@7a93189: Update error-codes.yaml (#97)
- Prusa-Error-Codes@6193057: Update errors.yaml
- Prusa-Error-Codes@0057469: Sl1 fix codes (#95)
- Prusa-Error-Codes@46071ae: xl: G425 error codes
- Prusa-Error-Codes@12bb215: Fix few issues (#93)
- Prusa-Error-Codes@9838dd3: Update error-codes.yaml (#67)
- Prusa-Error-Codes@3d625c7: Update errors.yaml
- Prusa-Error-Codes@a30dff7: Shorten the texts to M1 user level
- Prusa-Error-Codes@92f153c: Add point in MK3.5 folder name, it is needed for..
- Prusa-Error-Codes@5c021ff: xl: Add tool offset out of bounds error code
- Prusa-Error-Codes@9532e64: Introduce MK3.5 error codes
- Prusa-Error-Codes@094ef73: Add DOCK POSITION OUT OF BOUNDS for XL (#88)
- Prusa-Error-Codes@520a21a: Replace "Retry" for "Continue" in LOAD_TO_EXTRUD..
- Prusa-Error-Codes@604ad01: Fix an include in generate_buddy_headers.py, adj..
- Prusa-Error-Codes@8e7ca89: Refactor error code handling
- Prusa-Error-Codes@8764a62: Fix ESP_NOT_CONNECTED print code on Mini
- Prusa-Error-Codes@3b3533a: Edit homing error Y message
- Prusa-Error-Codes@cd6c6dd: Edit I2C error title
- Prusa-Error-Codes@7b12b5e: Mention new printers in readme
- Prusa-Error-Codes@2a4f709: Migrate error yamls to Prusa-Error-Codes
- Prusa-Error-Codes@658b9dc: Shorten messages as user will contact support an..
- Prusa-Error-Codes@b7e919e: Rename `MMU unit` to `MMU` Counter part of https..
- Prusa-Error-Codes@12f70fe: Add ResetMMU and DisableMMU buttons to specific ..
- Prusa-Error-Codes@0ffeeca: Add 04306 MMU MCU UNDERPOWER error
- Prusa-Error-Codes@456db8f: Update README.md
- Prusa-Error-Codes@64752b9: Add SYSTEM_SERVICE_CRASHED error to indicate cra..
- Prusa-Error-Codes@b7a111a: Add missing '-'
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

No branches or pull requests

3 participants