Aquila X3 MAX 400x400x400 PROUI UBL

[Jlsmith97]

Hi! I have attempted to compile my own firmware from this source code and have changed any values that I have been able to find to allow my 400x400x400 Aquila X3 Max to use a modified version of the Aquila X3 firmware.

However, I am running into a problem during the Auto Mesh Level where it only ends up probing 1/4 of the bed as if it was still a 220x230 bed like the X3. I have checked the settings in the firmware before compiling and even again once it has been flashed on the printer and everything shows 0 min and 400 Max but the leveling isn’t respecting it. Could anyone assist me with this? I’m not sure what I’ve missed

[classicrocker883]

yes this can be the Mesh Inset. change the mesh Inset values. you can find them in the Mesh settings in the menu.

[classicrocker883]

thats odd, are you sure the firmware flashed? if you are unaware, sometimes you have to rename the file if it has the same name or it won't flash the new file.

so when you click Maximize Area, it should reset the mesh insets (max/min, x/y) to the max and min they can be. Center Area basically just sets the mesh square evenly.

even if you change the configuration parameters, it shouldn't load old settings as if it were somehow hard coded, it really should update them.

so you're not able to change the physical bed size in the settings?? I know there is an option to set it using custom Gcode commands, but I think with the more recent versions I disabled that to make room for other things. but it should work normally through using the LCD.

maybe you if you can upload a video id be able to see whats going on.

and to get things straight, youre able to use the printer normally at 400x400? you're able to print and everything moves as it should? but the only issue here is probing for a bed mesh right? so like only half the bed is probed?

so in Control menu, Physical Settings, once you change the Y/"X Max Position" to 400, you change Y/"X Bed Size" to 390. then go to "Unified Bed Leveling" Level menu, Mesh settings, Mest Inset (below grid points). you should then be able to change those inset values to anything 390 and under. you may have to save between menus.

in which menu is it restricting you going passed 230?

[classicrocker883]

I just checked this out and realized you need to "store settings" after changing the bed size, thats why it was restricting to 230.

[Jlsmith97]

With the precompiled firmware I can change the bed physical settings to a max of 230 but no higher in the UI. However I have compiled my own with it set to 400 and that seems to read just fine.

I have not attempted to print anything without needing first to complete a bed level. But I have used other settings outside the level menu and it is aware that the bed is 400X400.

I have set the mesh inset sizes once I had the physical settings correct from my compiled version.

I did also hit store settings after setting these values. Do I need to completely restart the printer after saving these settings? Or should I be able to run it instantly?

I have tried running after store settings and it still uses 230x230 even though the mesh size and physical size have been made to 390x400

[classicrocker883]

you should not need to restart after saving the settings. I tested this and I do not run into the 230 restriction once settings are stored/saved. I have also posted a new release build for March you can try out.

which precompiled firmware file was it you were using? also if you can either post some pictures or video, or write out the steps you take like:

• Go to Control menu
• Go to Physical settings menu
• Change ...

I mean I dont know what more I can say to help if it works as it should on my end. What I might be able to do is have it automatically save after changing the values.

in Marlin\src\lcd\e3v2\proui\dwin.cpp line ~3000
add , WriteEeprom() to the end of the function (before ; }), or copy/replace with the following.

  void SetBedSizeX() { HMI_value.axis = NO_AXIS_ENUM, SetPIntOnClick(X_BED_MIN, X_MAX_POS, ProEx.ApplyPhySet), WriteEeprom(); }
  void SetBedSizeY() { HMI_value.axis = NO_AXIS_ENUM, SetPIntOnClick(Y_BED_MIN, Y_MAX_POS, ProEx.ApplyPhySet), WriteEeprom(); }
  void SetMinPosX()  { HMI_value.axis = X_AXIS,       SetPIntOnClick(     -100,       100, ProEx.ApplyPhySet), WriteEeprom(); }
  void SetMinPosY()  { HMI_value.axis = Y_AXIS,       SetPIntOnClick(     -100,       100, ProEx.ApplyPhySet), WriteEeprom(); }
  void SetMaxPosX()  { HMI_value.axis = X_AXIS,       SetPIntOnClick(X_BED_MIN,       999, ProEx.ApplyPhySet), WriteEeprom(); }
  void SetMaxPosY()  { HMI_value.axis = Y_AXIS,       SetPIntOnClick(Y_BED_MIN,       999, ProEx.ApplyPhySet), WriteEeprom(); }
  void SetMaxPosZ()  { HMI_value.axis = Z_AXIS,       SetPIntOnClick(      100,       999, ProEx.ApplyPhySet), WriteEeprom(); }

[Jlsmith97]

Just wanted to pop back and update now that I've had time to try more things. I downloaded the April N32 compiled file and it seems to be working great and respecting the new sizes!

[Andreunto]

I have the same problems with auto leveling on november firmware. Not level over 220x230

[classicrocker883]

after INPUT_SHAPING_X/Y/Z is enabled just make sure so is SHAPING_MENU, you should be able to find it in Motion Settings under Control.

Main Menu > Control > Motion > Input Shaping

[classicrocker883]

With your test firmware remain the same problem. April firmware is good.

I have uploaded another Test here, this time it should work, I reverted some changes from April and that should fix it
see next comment

[classicrocker883]

I have uploaded a new release this should be fixed
https://github.com/classicrocker883/MRiscoCProUI/releases/tag/2.1.3f-11-1

[Striker7616]

I still have the same issue with November and December release. As the other two commenters have mentioned, the April release works as expected.

[classicrocker883]

the same issue being the Mesh Inset does not move to the 400x400?

[Striker7616]

Yes Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Andrew ***@***.***> Sent: Wednesday, January 8, 2025 9:09:28 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) the same issue being the Mesh Inset does not move to the 400x400? — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWVNVQYJ7I57R3NB5J32JU5SRAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGQ3TMMY>. You are receiving this because you commented.Message ID: ***@***.***>

[Striker7616]

Yes, even when you change the bed size, on the display or the source code and recompile it produces the same result. It will only probe the left hand corner for the mesh. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Andrew ***@***.***> Sent: Wednesday, January 8, 2025 9:09:28 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) the same issue being the Mesh Inset does not move to the 400x400? — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWVNVQYJ7I57R3NB5J32JU5SRAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGQ3TMMY>. You are receiving this because you commented.Message ID: ***@***.***>

[classicrocker883]

what file did you use/what settings so I can make another file you can test to see if it works, like for example:
[Aquila_GD32_UBL-ProUI-EX-12-12.bin]

[Striker7616]

I tried all 4 versions of Aquila_N32_IND_UBL. I was wanting specifically to try the Aquila_N32_IND_UBL_ProUI_EX_IS_MPC build. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Andrew ***@***.***> Sent: Wednesday, January 8, 2025 10:40:35 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) what file did you use/what settings so I can make another file you can test to see if it works, like for example: [Aquila_GD32_UBL-ProUI-EX-12-12.bin] — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWUBAGAYPM2AKSV5Y6L2JVIIHAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGU4TANY>. You are receiving this because you commented.Message ID: ***@***.***>

[Striker7616]

I am trying to learn more about coding/firmware when it comes to 3d printing and would be more than glad to help anyway possible with testing and anything else I can be of use for. I have 4 printers so testing different versions and stuff for other printers is an option as well. I have a flashforge adventure 5m, an ender 3 pro (not stock used parts to custom build), anycubic kossel linear plus, and the Aquila x3 max. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Aaron Means ***@***.***> Sent: Wednesday, January 8, 2025 10:56:18 AM To: classicrocker883/MRiscoCProUI ***@***.***>; classicrocker883/MRiscoCProUI ***@***.***> Cc: Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) I tried all 4 versions of Aquila_N32_IND_UBL. I was wanting specifically to try the Aquila_N32_IND_UBL_ProUI_EX_IS_MPC build. Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________ From: Andrew ***@***.***> Sent: Wednesday, January 8, 2025 10:40:35 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) what file did you use/what settings so I can make another file you can test to see if it works, like for example: [Aquila_GD32_UBL-ProUI-EX-12-12.bin] — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWUBAGAYPM2AKSV5Y6L2JVIIHAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGU4TANY>. You are receiving this because you commented.Message ID: ***@***.***>

[classicrocker883]

firmware-20250108-163351.zip

here is basically the same Aquila_N32_IND_UBL-ProUI-EX
let me know how this goes

[classicrocker883]

firmware-20250109-055306.zip

similar to the first test, but if the first one doesnt work, try this one.

just have me know if Test1 or Test2 works or neither works

[Striker7616]

The first one works! The second one the display is all messed up even after reflashing the dwin set, so I wasnt able to test the mesh inset. Thank you so much! Is the input shaping and MPC enabled on the first one?

…

On Thu, Jan 9, 2025 at 4:57 AM Andrew ***@***.***> wrote: firmware-20250109-055306.zip <https://github.com/user-attachments/files/18360337/firmware-20250109-055306.zip> similar to the first test, but if the first one doesnt work, try this one. just have me know if Test1 or Test2 works or neither works — Reply to this email directly, view it on GitHub <#114 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWQ7RKOQ4ZWEZG3AB4T2JZIYRAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZYGUZDENA> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11785224@ github.com>

[classicrocker883]

firmware-20250110-030219.zip

I have both input shaping and MPC enabled on this one, it should work just like the other working one please try it out and let me know what else I can do

[Striker7616]

Ok, so another strange development, everything leveled, did PID tuning and then when I went to run a print the print is scaled down and contained to the front corner.

…

On Thu, Jan 9, 2025 at 8:31 PM Aaron Means ***@***.***> wrote: The first one works! The second one the display is all messed up even after reflashing the dwin set, so I wasnt able to test the mesh inset. Thank you so much! Is the input shaping and MPC enabled on the first one? On Thu, Jan 9, 2025 at 4:57 AM Andrew ***@***.***> wrote: > firmware-20250109-055306.zip > <https://github.com/user-attachments/files/18360337/firmware-20250109-055306.zip> > > similar to the first test, but if the first one doesnt work, try this one. > > just have me know if Test1 or Test2 works or neither works > > — > Reply to this email directly, view it on GitHub > <#114 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BOFCPWQ7RKOQ4ZWEZG3AB4T2JZIYRAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZYGUZDENA> > . > You are receiving this because you commented.Message ID: > <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11785224@ > github.com> >

[classicrocker883]

I haven't enabled inputshaping or MPC either. I can do that for the next test, but im interested in what the next issue you meant. the print scaled down?? do you mean reduced in size or could this be something to do with the Gcode/Slicer?

also, try with and without M420 in the .gcode file, simply put a ; before the code --- that will disable bed leveling for the print. ex: ;M420 S1

[Striker7616]

I will try this when I get home tonight. The issue I had was the print scaled down to fit the 220x220. I know that the print was cut for a 350 mm bed because it is a gcode file I have on a SD card, I have used it many times at the full size so I was really surprised. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Andrew ***@***.***> Sent: Friday, January 10, 2025 2:06:30 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) firmware-20250110-030219.zip<https://github.com/user-attachments/files/18372576/firmware-20250110-030219.zip> I have both input shaping and MPC enabled on this one, it should work just like the other working one please try it out and let me know what else I can do — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWRAPGSFKDYL2LLOPVL2J55QNAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZZGUYTENI>. You are receiving this because you commented.Message ID: ***@***.***>

[Striker7616]

This one works on the leveling aspect however prints are scaled down to fit 220x220 regardless of size in slicer/gcode.

…

On Fri, Jan 10, 2025 at 9:34 AM Aaron Means ***@***.***> wrote: I will try this when I get home tonight. The issue I had was the print scaled down to fit the 220x220. I know that the print was cut for a 350 mm bed because it is a gcode file I have on a SD card, I have used it many times at the full size so I was really surprised. Get Outlook for Android <https://aka.ms/AAb9ysg> ------------------------------ *From:* Andrew ***@***.***> *Sent:* Friday, January 10, 2025 2:06:30 AM *To:* classicrocker883/MRiscoCProUI ***@***.***> *Cc:* Striker7616 ***@***.***>; Comment < ***@***.***> *Subject:* Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) firmware-20250110-030219.zip <https://github.com/user-attachments/files/18372576/firmware-20250110-030219.zip> I have both input shaping and MPC enabled on this one, it should work just like the other working one please try it out and let me know what else I can do — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWRAPGSFKDYL2LLOPVL2J55QNAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZZGUYTENI> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11795125@ github.com>

[classicrocker883]

that is strange, but the first Test1 -firmware-20250108-163351.zip that worked in both ways flawlessly??

[Striker7616]

No, the first test worked the same as the last one. The mesh inset adjusts and it will level the whole bed but it will not print on it. It will only print on the left front 220mm square

…

On Sat, Jan 11, 2025 at 3:00 PM Andrew ***@***.***> wrote: that is strange, but the first Test1 -firmware-20250108-163351.zip that worked in both ways flawlessly?? — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWQEEFSH7SPJIP7DQFL2KGBAPAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBQHA2TMNI> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11808565@ github.com>

[classicrocker883]

oh i see Mesh Inset = Okay, but Bed Size not Okay.

so to be sure none of the tests worked perfectly?

[Striker7616]

Correct, everything looks good until you actually try to print. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Andrew ***@***.***> Sent: Saturday, January 11, 2025 5:36:14 PM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) oh i see Mesh Inset = Okay, but Bed Size not Okay. so to be sure none of the tests worked perfectly? — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWUMG7WY2B3AOAYLMX32KGTG5AVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBQHEYTSNQ>. You are receiving this because you commented.Message ID: ***@***.***>

[classicrocker883]

MRiscoCfirmware.zip

here is MRiscoC's upstream firmware, filament runout sensor had to be disabled.
try this out let me know how it works out for you. ( it is going to look very different just FYI)

and you did say April's firmware version worked great, no issues printing? no issues with mesh inset?
because that is what I am working with trying to revert whatever changes had been made.

[Striker7616]

This one doesn't work at all, does it need a different display firmware? When I try to move through the menus it reboots. Yes, the april firmware works on both the mesh inset and the printing.

…

On Sun, Jan 12, 2025 at 9:01 AM Andrew ***@***.***> wrote: MRiscoCfirmware.zip <https://github.com/user-attachments/files/18389832/MRiscoCfirmware.zip> here is MRiscoC's upstream firmware, filament runout sensor had to be disabled. try this out let me know how it works out for you. and you did say April's firmware version worked great, no issues printing? no issues with mesh inset? because that is what I am working with trying to revert whatever changes had been made. — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWQ5PCB2L5O3ZT4YWFL2KJ7V3AVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBRGIZTQOA> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11812388@ github.com>

[classicrocker883]

MRiscoC-Ex-firmware.zip

this one should work, its updated and the "Experimental" version of his. I'm just curious if this works.

but looks like I will be reverting changes back to April, hopefully that'll be it and we can call it a day! :-D

[classicrocker883]

firmware-April-newer.zip

do me a favor though, there is a difference between the Released firmware and Repo firmware. let me know if this one firmware-April-newer (which comes from the Repo version) works the same as the other April one which you say works perfectly.

[Striker7616]

Unfortunately neither of these work. On the mriscoc i cant select anything it causes the screen to refresh as if you have rebooted the printer. On the april repo firmware, the mesh inset does not change to probe the whole bed. In addition prints that worked on april release version are scaled down.

…

On Tue, Jan 14, 2025 at 7:34 AM Andrew ***@***.***> wrote: firmware-April-newer.zip <https://github.com/user-attachments/files/18410956/firmware-April-newer.zip> do me a favor though, there is a difference between the Released firmware and Repo firmware. let me know if this one firmware-April-newer (which comes from the Repo version) works the same as the other April one which you say works perfectly. — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWVWCKOAZDYQSIVPDAL2KUG6FAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBTGE3TONI> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11831775@ github.com>

[classicrocker883]

thanks for your help trying. I figured as much the new Mriscoc is way out of touch, unfortunately doesnt seem compatible with any MAPLE type of chip which is what these GD32, N32, HC32 are. he stopped incorporating support for those in the PROUI_EX library quite long along so i've just been keeping up with the Marlin releases.

so it looks like the older (Released) version of April is the one I'll be trying out.

wish I had my own Max Aquila, but I wonder if I can somehow test it on my own just decouple the belts from the motors and see what the display says.

anyway, if you dont mind keeping in touch I'll post some tests to see what works. and thanks again very much

[Striker7616]

I will be glad to help any way I can. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Andrew ***@***.***> Sent: Friday, January 17, 2025 4:59:42 AM To: classicrocker883/MRiscoCProUI ***@***.***> Cc: Striker7616 ***@***.***>; Comment ***@***.***> Subject: Re: [classicrocker883/MRiscoCProUI] Aquila X3 MAX 400x400x400 PROUI UBL (Discussion #114) thanks for your help trying. I figured as much the new Mriscoc is way out of touch, unfortunately doesnt seem compatible with any MAPLE type of chip which is what these GD32, N32, HC32 are. he stopped incorporating support for those in the PROUI_EX library quite long along so i've just been keeping up with the Marlin releases. so it looks like the older (Released) version of April is the one I'll be trying out. wish I had my own Max Aquila, but I wonder if I can somehow test it on my own just decouple the belts from the motors and see what the display says. anyway, if you dont mind keeping in touch I'll post some tests to see what works. and thanks again very much — Reply to this email directly, view it on GitHub<#114 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOFCPWWH6TFW4SIUGDFROMT2LDPB5AVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBWGU3DENQ>. You are receiving this because you commented.Message ID: ***@***.***>

[classicrocker883]

firmware-20250119-134915.zip
my hope is with this firmware-20250119-134915 test is that is does work

okay lets just confirm something, the Release which works is April Release here, correct?

so we tried the repo which I worked on right after and it doesnt work. what I did was kind of combine the two.

if the first one - firmware-20250119-134915 - works then great.

here is another which has one small change so its a bit more optional, but if first doesnt work you can try this one.
firmware-20250119-140515.zip

[classicrocker883]

firmware-20250119-235231.zip

here is another test if any of those do not work.
what I am trying to do is take the files which do work, and put them in the next repository which didn't work and once that works then I can narrow down what the issue can be.

[Striker7616]

This very last file works as far as I have been able to test. Both the mesh inset and the actual print work as expected. The first two the mesh inset works but the print remains small. Hope this helps.

…

On Sun, Jan 19, 2025 at 10:56 PM Andrew ***@***.***> wrote: firmware-20250119-235231.zip <https://github.com/user-attachments/files/18472402/firmware-20250119-235231.zip> here is another test if any of those do not work. what I am trying to do is take the files which *do* work, and put them in the next repository which didn't work and once that works then I can narrow down what the issue can be. — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWXYW3G2QCLES4VLVA32LR6YFAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBYGYZTGNI> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11886335@ github.com>

[classicrocker883]

firmware-works-tests.zip

in here are two files - firmware-works1.bin and - firmware-works2.bin

just want to confirm #1 works like the last, and to see if #2 still works the same.

[Striker7616]

The first one in this pack works fully. The second one shrinks the prints down, but the mesh inset works.

…

On Wed, Jan 22, 2025 at 4:53 AM Andrew ***@***.***> wrote: firmware-works-tests.zip <https://github.com/user-attachments/files/18504139/firmware-works-tests.zip> in here are two files - firmware-works1.bin and - firmware-works2.bin just want to confirm #1 works like the last, and to see if #2 still works the same. — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWULGZXFPZKEBH6U6GL2L52EHAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJRGQ4TIMY> . You are receiving this because you commented.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11914943@ github.com>

[classicrocker883]

firmware-UBL-debug-tests.zip

this one has tests similar to the previous, except I enabled UBL Debugging.

 * G29
 *
 * With UBL_DEVEL_DEBUGGING:
 *
 *   K #  Kompare     Kompare current Mesh with stored Mesh #, replacing current Mesh with the result.
 *                    This command literally performs a diff between two Meshes.
 *
 *   Q-1  Dump EEPROM Dump the UBL contents stored in EEPROM as HEX format. Useful for developers to help
 *                    verify correct operation of the UBL.
 *
 *   W    What?       Display valuable UBL data.
 *
 *
 *   Release Notes:
 *   You MUST do M502, M500 to initialize the storage. Failure to do this will cause all
 *   kinds of problems. Enabling EEPROM Storage is required.

I'm not sure what the release notes is talking about here, but the goal is to get some Serial output of what is going on.

first, I'd like to know which of the firmwares works, they are firmware-test1a and firmware-test2a.
if you have Pronterface or Octoprint, in the terminal simply put G29 K# where # just start at 1 and see what it says.

i think I am most interested in G29 W,
but also try

• G29 Q-1
• G29 Q0
• G29 Q1
• G29 Q2

you can use Q0/1/2 in firmwares without the UBL debugging enabled (which it is only enabled here for now)

[classicrocker883]

UBL-tests.zip

in these two tests I took what I thought what is needed to be changed in the most recent (January-2025) repo. test1 and test2 have one small difference between them. I'm wondering if they still both work or not.

[classicrocker883]

@Striker7616 actually if you dont have a lot of time for all this, I'd rather have these two tests done before the previous ones above - if you could:

April-tests.zip

test1 should work perfectly, please confirm that it does, I am wondering if test2 also works just like 1.
this will help narrow down which differences is the issue.

also posted a test release

[Striker7616]

Both of the files in the last april-test zip work.

…

On Sat, Jan 25, 2025 at 11:42 PM Andrew ***@***.***> wrote: @Striker7616 <https://github.com/Striker7616> actually if you dont have a lot of time for all this, I'd rather have these two tests done if you could: April-tests.zip <https://github.com/user-attachments/files/18549054/April-tests.zip> test1 should work perfectly, please confirm that it does, I am wondering if test2 also works just like 1. this will help narrow down which differences is the issue. — Reply to this email directly, view it on GitHub <#114 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWQZ52L4QZ2TKXONK2T2MRYV7AVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJVGYYDONQ> . You are receiving this because you were mentioned.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11956076@ github.com>

[Striker7616]

Disregard the last comment. The first one works fine, but the bed tramming wizard doesn't work on the second one.

…

On Tue, Jan 28, 2025 at 8:08 PM Aaron Means ***@***.***> wrote: Both of the files in the last april-test zip work. On Sat, Jan 25, 2025 at 11:42 PM Andrew ***@***.***> wrote: > @Striker7616 <https://github.com/Striker7616> actually if you dont have > a lot of time for all this, I'd rather have these two tests done if you > could: > > April-tests.zip > <https://github.com/user-attachments/files/18549054/April-tests.zip> > > test1 should work perfectly, please confirm that it does, I am wondering > if test2 also works just like 1. > this will help narrow down which differences is the issue. > > — > Reply to this email directly, view it on GitHub > <#114 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BOFCPWQZ52L4QZ2TKXONK2T2MRYV7AVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJVGYYDONQ> > . > You are receiving this because you were mentioned.Message ID: > <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11956076@ > github.com> >

[Striker7616]

Please disregard all comments from yesterday. I dont know what I did but I got everything all mixed up. When I get home from work tonight I need to start over.

…

On Tue, Jan 28, 2025 at 8:51 PM Aaron Means ***@***.***> wrote: Disregard the last comment. The first one works fine, but the bed tramming wizard doesn't work on the second one. On Tue, Jan 28, 2025 at 8:08 PM Aaron Means ***@***.***> wrote: > Both of the files in the last april-test zip work. > > On Sat, Jan 25, 2025 at 11:42 PM Andrew ***@***.***> wrote: > >> @Striker7616 <https://github.com/Striker7616> actually if you dont have >> a lot of time for all this, I'd rather have these two tests done if you >> could: >> >> April-tests.zip >> <https://github.com/user-attachments/files/18549054/April-tests.zip> >> >> test1 should work perfectly, please confirm that it does, I am wondering >> if test2 also works just like 1. >> this will help narrow down which differences is the issue. >> >> — >> Reply to this email directly, view it on GitHub >> <#114 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/BOFCPWQZ52L4QZ2TKXONK2T2MRYV7AVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJVGYYDONQ> >> . >> You are receiving this because you were mentioned.Message ID: >> <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/11956076@ >> github.com> >> >

[classicrocker883]

well I posted a new release here.
figured why not since were at the end of the month anyway.

please let me know how things are working, and ty very much for all the help

[Striker7616]

Hey, thanks again for all you have done and continue to do keeping this up and going and helping me to work on these issues! After more testing tonight the results I have found are as follows. April test 1&2 from the last zip work well. Also testing the latest release it works as well! Some things I did differently tonight that might help other users...(For Aquila X3 Max, doing this on other printers could damage your printer. Steps 9 & 10 are safe for all users!) 1. Adjust physical settings and Store Settings. 2. Adjust mesh settings maximize area followed by centering area. Store Settings 3. Tune Hotend Using MPC Tune Store Settings 4. Run Bed Tramming Wizard Store Settings 5. Run Bed Leveling Mesh (Auto Build Mesh Function) Save Mesh, not continue, store settings as well. 6.View mesh (Basically verifying that it is actually stored.) I believe now that this might have been a big part of my problem. 7. Run Z probe wizard, store settings again. 8. Test print size... Cross fingers toes and eyes if necessary LOL 9. Last but definitely not least give many thanks and appreciation to the classicrocker883 for keeping this firmware updated and the crazy amounts of effort that he has put in! 10. Send some beer money or Mountain Dew money! Times are tough for most people right now, but people's time isn't free and we should show our appreciation by donating where we can to show appreciation for the work they do for our community!

…

On Thu, Jan 30, 2025 at 12:20 AM Andrew ***@***.***> wrote: well I posted a new release here <https://github.com/classicrocker883/MRiscoCProUI/releases/tag/2.1.3g-1>. figured why not since were at the end of the month anyway. — Reply to this email directly, view it on GitHub <#114 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOFCPWSOEJRBDACKI4SUJ3L2NHAEFAVCNFSM6AAAAABRRZFX5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBQGMYTENY> . You are receiving this because you were mentioned.Message ID: <classicrocker883/MRiscoCProUI/repo-discussions/114/comments/12003127@ github.com>

[classicrocker883]

hahah thanks I appreciate the appreciation.

I'm not sure its always necessary to Store Settings between steps, I mean it doesn't hurt, and some parts automatically save anyway. but if thats what you have to do for sure let me know at some point I can write up a wiki page which will help others as you said.

for 7. Run Z probe wizard thats for the Z offset right? I would actually put this before step 4. I'm not sure where or if I had this written down somewhere, but there is a certain procedure I do which makes it easy and gives me great enough results I dont even bother using paper or anything, or even sometimes the Auto Bed Leveling.

a quick rundown

once youre ready to do bed tramming, do the Z offset wizard. the goal is to adjust so the nozzle is just just touching the bed. once that is done, confirm this by going to bed Tramming Wizard, checkbox to Manual Tramming, select Center, and you should observe the nozzle just touching or barely touching (shine flashlight behind if a tiny bit of light comes through that is okay, you dont need the nozzle digging into the bed).

then copy what you did with the Center to each corner. this is what I like to do first is get a good Manual bed Tramming done first. after you do the corners, re-home, and go to the center make sure its barely touching or close enough, and go to each corner and adjust the knobs so you get the same as center.

you should not need to do this more than one or two times. and you can confirm this using auto leveling by unchecking the Manual leveling box and select Tramming Wizard.

it should be very close to 0.0 (within tolerance).

but if you find it is not in the end with the Auto Tramming Wizard, as long as you can confirm Manually the Center and all the Corners match you can call your bed level - as perfectly level as it will get.