Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen

[maggit13]

Did you test the latest release build?

No, but I will try it!

Bug Description

I use G29 in my Cura gcode to run a new mesh for every print, then M500 to save settings. Here is a sample from a print:

G92 E0 ; Reset Extruder
G28 ; Home all axes
G29 ; Run mesh leveling on every print
M500 ; Save settings to EEPROM
C108; Close the mesh viewer, optional

Up until 2.1.3f-11-1, Nov. 2024 build, it would run the mesh then save the settings and I would hear the beep and it would return to the print progress screen on the printer automatically. Since installing the Nov. build, PROUI with BLT, same options as before, it no longer beeps or closes the mesh window. It will start printing but I have to go to the printer and click continue manually. If I click Save, the screen flashes a few times and the print aborts.

I have reproduced this since installing the newer firmware for every print, I even refreshed all of recommended gcode options in Octoprint and in Cura.

Printer Model

Voxelab Aquila

Model Type

OG

Your Mainboard

Aquila GD32

Other Mainboard Type

No response

Add-ons that could be involved

BL Touch, Octoprint, Cura

ProUI-EX | Extra Features?

Yes

Bed Leveling

BLT - BL Touch Bilinear mesh

Did you include your own configuration files?

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

Additional information & file uploads

No response

[yrabbit]

Just out of curiosity, if you build mesh every time you print, why do you save it to EEPROM?

[maggit13]

That's a great question, I guess in case I start another print that doesn't have that code in it. Just want to get something saved in case.

…

Sent from my Revvl 5G

________________________________ From: YRabbit ***@***.***> Sent: Sunday, March 16, 2025 8:40:07 PM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) Just out of curiosity, if you build mesh every time you print, why do you save it to EEPROM? — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6DSMECEIEXBDMSK3D32UYKWPAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXG43DAOJTGY>. You are receiving this because you authored the thread.Message ID: ***@***.***> [yrabbit]yrabbit left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> Just out of curiosity, if you build mesh every time you print, why do you save it to EEPROM? — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6DSMECEIEXBDMSK3D32UYKWPAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXG43DAOJTGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[yrabbit]

That's a great question, I guess in case I start another print that doesn't have that code in it. Just want to get something saved in case.

Ok, but somehow I doubt the M500 records mesh, shouldn't something like the G29 S be used?

Again out of pure curiosity, with no relation to the error itself:)

[maggit13]

I can certainly try it. My concern is that this worked perfectly before I updated the firmware a few months ago, so not sure what changed. What command is sent when clicking on save in the mesh screen?

…

Sent from my Revvl 5G

________________________________ From: YRabbit ***@***.***> Sent: Sunday, March 16, 2025 9:08:55 PM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) That's a great question, I guess in case I start another print that doesn't have that code in it. Just want to get something saved in case. Ok, but somehow I doubt the M500 records mesh, shouldn't something like the G29 S be used? — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6EHLXVIMZYHHK7WPJL2UYOCPAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXG44DINZZGA>. You are receiving this because you authored the thread.Message ID: ***@***.***> [yrabbit]yrabbit left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> That's a great question, I guess in case I start another print that doesn't have that code in it. Just want to get something saved in case. Ok, but somehow I doubt the M500 records mesh, shouldn't something like the G29 S be used? — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6EHLXVIMZYHHK7WPJL2UYOCPAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXG44DINZZGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[yrabbit]

Well this is definitely not my area of expertise - I'm just a simple user here. It just seems to me that given that there are multiple slots for meshes, there would be a whole paragraph on the M500 page describing which slot the current mesh falls into or something like that. Since there isn't, the mesh probably just isn't saved by M500 😄

https://marlinfw.org/docs/gcode/M500.html

[maggit13]

Makes sense, I'll look into it. Thanks for the suggestion!

…

Sent from my Revvl 5G

________________________________ From: YRabbit ***@***.***> Sent: Sunday, March 16, 2025 9:29:37 PM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) Well this is definitely not my area of expertise - I'm just a simple user here. It just seems to me that given that there are multiple slots for meshes, there would be a whole paragraph on the M500 page describing which slot the current mesh falls into or something like that. Since there isn't, the mesh probably just isn't saved by M500 😄 https://marlinfw.org/docs/gcode/M500.html — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6GXXRENFQMTKJLUBC32UYQQDAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXHAYDGNJUGQ>. You are receiving this because you authored the thread.Message ID: ***@***.***> [yrabbit]yrabbit left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> Well this is definitely not my area of expertise - I'm just a simple user here. It just seems to me that given that there are multiple slots for meshes, there would be a whole paragraph on the M500 page describing which slot the current mesh falls into or something like that. Since there isn't, the mesh probably just isn't saved by M500 😄 https://marlinfw.org/docs/gcode/M500.html — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6GXXRENFQMTKJLUBC32UYQQDAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXHAYDGNJUGQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[maggit13]

I found another issue that is pretty much what I'm experiencing, I have the C108 in my gcode and it used to close the menu after saving
mriscoc#344

[classicrocker883]

I found another issue that is pretty much what I'm experiencing, I have the C108 in my gcode and it used to close the menu after saving mriscoc#344

some firmware files dont have the custom C gcodes. especially if its UBL and ProUI-EX because it takes up a lot of room. what firmware .bin have you used? also M420 is usually the right gcode when it comes to the mesh leveling. i mean i believe G29 might only work for _BLT versions.

but there have been some issues after the first October release so please try the most recent. but if you are using or need to use custom configuration let me know

[maggit13]

Thanks. I use the BLT and PROUI EX bin file, not UBL. That makes sense about the October release since I'm having this problem with the November release. I will update to March and see what happens. Thanks again!

…

Sent from my Revvl 5G

________________________________ From: Andrew ***@***.***> Sent: Monday, March 17, 2025 10:30:59 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) I found another issue that is pretty much what I'm experiencing, I have the C108 in my gcode and it used to close the menu after saving mriscoc#344<url> some firmware files dont have the custom C gcodes. especially if its UBL and ProUI-EX because it takes up a lot of room. what firmware .bin have you used? also M420 is usually the right gcode when it comes to the mesh leveling. i mean i believe G29 might only work for _BLT versions. but there have been some issues after the first October release so please try the most recent. but if you are using or need to use custom configuration let me know — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6FGQVI6KFELV7NHMGD2U3MCHAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRZG4ZTINRZGE>. You are receiving this because you authored the thread.Message ID: ***@***.***> [classicrocker883]classicrocker883 left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> I found another issue that is pretty much what I'm experiencing, I have the C108 in my gcode and it used to close the menu after saving mriscoc#344<url> some firmware files dont have the custom C gcodes. especially if its UBL and ProUI-EX because it takes up a lot of room. what firmware .bin have you used? also M420 is usually the right gcode when it comes to the mesh leveling. i mean i believe G29 might only work for _BLT versions. but there have been some issues after the first October release so please try the most recent. but if you are using or need to use custom configuration let me know — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6FGQVI6KFELV7NHMGD2U3MCHAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRZG4ZTINRZGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[maggit13]

I updated to March 2025 with BLT and ProUI EX, removed the C108 command and the first print still did not close the mesh menu. I then tried a few other files that I used in the past and suddenly it saved, beeped and closed the menu. These files had the C108 command but who knows. So seems to be working as expected now. Thanks for the suggestions! On a side note, the progress bar is no longer working in the printer display. I have M73 Progress and Detailed Progress plugins in Octoprint but the progress stays at 0%. Not a big deal but curious as to why it's not working anymore. Thanks again!

…

Sent from my Revvl 5G

________________________________ From: Andrew ***@***.***> Sent: Monday, March 17, 2025 10:30:59 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) I found another issue that is pretty much what I'm experiencing, I have the C108 in my gcode and it used to close the menu after saving mriscoc#344<url> some firmware files dont have the custom C gcodes. especially if its UBL and ProUI-EX because it takes up a lot of room. what firmware .bin have you used? also M420 is usually the right gcode when it comes to the mesh leveling. i mean i believe G29 might only work for _BLT versions. but there have been some issues after the first October release so please try the most recent. but if you are using or need to use custom configuration let me know — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6FGQVI6KFELV7NHMGD2U3MCHAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRZG4ZTINRZGE>. You are receiving this because you authored the thread.Message ID: ***@***.***> [classicrocker883]classicrocker883 left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> I found another issue that is pretty much what I'm experiencing, I have the C108 in my gcode and it used to close the menu after saving mriscoc#344<url> some firmware files dont have the custom C gcodes. especially if its UBL and ProUI-EX because it takes up a lot of room. what firmware .bin have you used? also M420 is usually the right gcode when it comes to the mesh leveling. i mean i believe G29 might only work for _BLT versions. but there have been some issues after the first October release so please try the most recent. but if you are using or need to use custom configuration let me know — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6FGQVI6KFELV7NHMGD2U3MCHAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRZG4ZTINRZGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

On a side note, the progress bar is no longer working in the printer display. I have M73 Progress and Detailed Progress plugins in Octoprint but the progress stays at 0%. Not a big deal but curious as to why it's not working anymore.

I'm not sure, it should work haven't touched that in a while, maybe something in an update changed it. ill get back to you.
ps. you can run a dry print run with a certain command M111 8
disable with M111 0
https://marlinfw.org/docs/gcode/M111.html

[maggit13]

Awesome, thank you! From: Andrew ***@***.***> Sent: Thursday, March 20, 2025 9:43 PM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) On a side note, the progress bar is no longer working in the printer display. I have M73 Progress and Detailed Progress plugins in Octoprint but the progress stays at 0%. Not a big deal but curious as to why it's not working anymore. I'm not sure, it should work haven't touched that in a while, maybe something in an update changed it. ill get back to you. ps. you can run a dry print run with a certain command M111 8 disable with M111 0 https://marlinfw.org/docs/gcode/M111.html — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6CQ2G7HQAVS46P6W2D2VNVAPAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBSGAZDKNRVGM>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> [classicrocker883]classicrocker883 left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> On a side note, the progress bar is no longer working in the printer display. I have M73 Progress and Detailed Progress plugins in Octoprint but the progress stays at 0%. Not a big deal but curious as to why it's not working anymore. I'm not sure, it should work haven't touched that in a while, maybe something in an update changed it. ill get back to you. ps. you can run a dry print run with a certain command M111 8 disable with M111 0 https://marlinfw.org/docs/gcode/M111.html — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6CQ2G7HQAVS46P6W2D2VNVAPAVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBSGAZDKNRVGM>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[classicrocker883]

so this is what I've noticed regarding the print % bar. what happens after the screen times out and turns off, it basically freezes the image until you press the knob. turning the encoder knob may bring the screen back on, but you have to press the knob in to update the screen. if you do this after the print is finished it will select Done and bring you to the mainmenu so you wont be able to see the % bar changed. before the print ends if the screen if off just press the knob in and you should see it updated to the correct %, or disable LCD display timeout entirely (LCD timeout 0).

let me know if that solves that issue. otherwise is there anything else?

[maggit13]

Thanks for the update. My LCD timeout is always 0 so it's on all the time. Everything else updates normally during a print, the printer messages, positions, everything else, except the progress stays at 0% even though octoprint and my app move normally. I've tried reinstalling the m73 progress and detailed progress plugins but nothing is working.

…

Sent from my Revvl 5G

________________________________ From: Andrew ***@***.***> Sent: Sunday, March 30, 2025 11:57:01 PM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Harris Norton ***@***.***>; Author ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila G32 M29 Auto Save Mesh no longer closes Mesh screen (Issue #203) so this is what I've noticed regarding the print % bar. what happens after the screen times out and turns off, it basically freezes the image until you press the knob. turning the encoder knob may bring the screen back on, but you have to press the knob in to update the screen. if you do this after the print is finished it will select Done and bring you to the mainmenu so you wont be able to see the % bar changed. before the print ends if the screen if off just press the knob in and you should see it updated to the correct %, or disable LCD display timeout entirely (LCD timeout 0). let me know if that solves that issue. otherwise is there anything else? — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6DX6SSGXN4HCWVKS2L2XC4I3AVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRVGAZTCMBTGA>. You are receiving this because you authored the thread.Message ID: ***@***.***> [classicrocker883]classicrocker883 left a comment (classicrocker883/MRiscoCProUI#203)<#203 (comment)> so this is what I've noticed regarding the print % bar. what happens after the screen times out and turns off, it basically freezes the image until you press the knob. turning the encoder knob may bring the screen back on, but you have to press the knob in to update the screen. if you do this after the print is finished it will select Done and bring you to the mainmenu so you wont be able to see the % bar changed. before the print ends if the screen if off just press the knob in and you should see it updated to the correct %, or disable LCD display timeout entirely (LCD timeout 0). let me know if that solves that issue. otherwise is there anything else? — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAUDU6DX6SSGXN4HCWVKS2L2XC4I3AVCNFSM6AAAAABZEG77COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRVGAZTCMBTGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>