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

[BUG] Mesh gets lost after restart #66

Closed
1 task
Arson31 opened this issue Aug 11, 2023 · 7 comments
Closed
1 task

[BUG] Mesh gets lost after restart #66

Arson31 opened this issue Aug 11, 2023 · 7 comments
Labels
bug Something isn't working work-in-progress Currently focused on this issue

Comments

@Arson31
Copy link

Arson31 commented Aug 11, 2023

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

Old gcodes prior to flashing new firmware seems to work with alex's firmware or MRiscoC's. After flashing this firmware any gcodes sliced from Cura 5.4.0. will only home and will cancel print. I'm not sure if the start gcode in Cura is causing the problem but it can print older gcode just fine.
gcodes.zip

Edit: I found the problem, the gcode is expecting a bed mesh but the printer loses it's mesh every time I power off the machine. I save the bed mesh settings in Leveling => Save Bed Mesh & Control => Store settings but mesh doesn't save like alex's firmware or MRiscoC's.

Printer Model

Voxelab Aquila

Model Type

OG

Your Mainboard

Aquila GD32

Other Mainboard Type

No response

Add-ons that could be involved

Octoprint, Cura

ProUI?

ProUI

Bed Leveling

MM - Manual Mesh Bed Leveling

Did you include your own configuration files?

  • A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

Using the latest Aquila_GD32_MM-ProUI.bin

@Arson31 Arson31 changed the title [BUG] Prints getting cancelled again [BUG] Mesh gets lost after restart Aug 11, 2023
@classicrocker883
Copy link
Owner

this sounds almost like this issue here

which has led to this pull request here

I'll be posting an updated release soon, and this should be fixed in it.

@classicrocker883 classicrocker883 added bug Something isn't working work-in-progress Currently focused on this issue labels Aug 12, 2023
@Arson31
Copy link
Author

Arson31 commented Aug 12, 2023

@classicrocker883 This workaround resolves the issue without having to redo the mesh again.

1. Build mesh

2. Save Mesh

3. Power off printer

4. Power on printer

5. Go to Control/Advanced Settings/Load Settings

6. Then go to Mesh settings and view mesh

@classicrocker883
Copy link
Owner

for some reason the mesh saves do not load at startup.

@Arson31
Copy link
Author

Arson31 commented Aug 13, 2023

For now I simply add M501 after homing in my start gcode in my printer settings from the same post without having to go through the list of steps:

G28 ;Home
M501; Load settings
M420 S1 ;Pull your mesh bed level:
G1 Z15.0 F6000 ;Move the platform down 15mm
;Prime the extruder
G92 E0
G1 F200 E3

Copy link

github-actions bot commented Nov 3, 2023

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2023
@KimmoHop
Copy link

KimmoHop commented Dec 9, 2023

I added this to Configuration_adv.h to specifically loading settings (again) and to prevent losing mesh if I change some other setting. It's a cludge, but I didn't find any reason in source code, why mesh is not initially loaded :/

#define STARTUP_COMMANDS "M501"

Copy link

github-actions bot commented Mar 1, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working work-in-progress Currently focused on this issue
Projects
None yet
Development

No branches or pull requests

3 participants