[BUG] Mesh inset settings do nothing

[Arson31]

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

Updated to MAY 2024 Rev.2 build. (Aquila_GD32_MM-ProUI-EX-05-23.bin)

I set the X maximum to 199.0 because I'm using a Satsana shroud for the Haldis Red Lizard Q1 like I have with the previous builds. After setting and saving the settings the shroud still crashes onto the LCD screen mounted vertically to the right of my Aquila.

I set the X maximum to 160 (which should be dead center) and the shroud still crashes into the screen.

Printer Model

Voxelab Aquila

Model Type

OG

Your Mainboard

Aquila GD32

Other Mainboard Type

No response

Add-ons that could be involved

Satsana shroud for the Haldis Red Lizard Q1

ProUI-EX | Extra Features?

Yes

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

No response

[classicrocker883]

how about the Physical Settings, under the Control menu? shouldn't this be adjusted instead of the Mesh Inset?

[Arson31]

@classicrocker883 I set the X max on physical settings to 180, stored settings, and it still crashes into the lcd screen.

[classicrocker883]

so I'm a bit confused. physical settings are one thing, and mesh inset are another. being able to set the bed dimensions, X/Y Bed Size, and X/Y Min/Max should be working normally.

if you set it to max 180, what then is the actual limit that it ends up crashing?

[Arson31]

@classicrocker883 The mesh X maximum was set to 199.0 in the Mesh Inset settings so I guess that's the limit. It never crashed into the LCD screen when I set the mesh X maximum to 199.0; I was able to create the mesh in the past.

[classicrocker883]

I had made some changes regarding mesh_inset code, how it is defined. I was able to test with probe firmware fine, so I have a suspicion of what it can be.

could you tell me which firmware release did work fine last that you know?

I will try some changes and upload a firmware file for you to try

Update: Aquila_GD32_MM-ProUI-EX-test.zip

here you can unzip this and flash this update see if this works. please let me know if this fixes the issue. (dont worry about the file name just place into the SD card like normal)

[Arson31]

@classicrocker883 I think it was the November release of last year, I couldn't remember it's been a while since I updated the firmware.

I'm using a 3x3 mesh and I tested Aquila_GD32_MM-ProUI-EX-test.zip. The 1x3 point of the mesh (the last X point until it begins the next Y set) is at the middle of the bed. The 2x3 is maybe 1 inch or 1/2 inch away from the 1x1 which the 1x1 point is right where the X home is.

Adjusting the X maximum mesh inset to 220 (when it was 210) does not make a difference, the 1x3 point is still at the middle of the bed.

[classicrocker883]

okay, give this one a try, that should do it.

Aquila_GD32_MM-ProUI-EX-test2.zip

[Arson31]

@classicrocker883 Same. The 3rd probe point is at the middle of the bed.

[classicrocker883]

Aquila_GD32_MM-ProUI-EX-test3.zip Aquila_GD32_MM-ProUI-EX-test4.zip

heres a couple more tests. I went back and took a look through the code from when you say it worked, I couldn't find anything that stood out, but made a couple changes I thought would work.

if you can, make a quick video and upload it, that'll help me understand whats actually happening.

[Arson31]

@classicrocker883 Neither of the two made a difference. Here's a quick video of what I'm talking about. It doesn't probe the entire bed just half of it.

[vw72]

I don't know if this helps, In the physical settings menu, I set the max bed size to 230 for both x and y and the bed size to 220 for both of them. I then set the mesh inset to 10.0 for each. I'm using a bltouch, not manual, but maybe these settings will have the head move to the right positions for the mm.

[classicrocker883]

I'm not sure what's going on, I will have to perform some tests to figure it out. because I had updated the mesh inset code, I tried reverting to what it was originally, so i'll have to do some git bisect I think all the way back to November, so thats gonna take some time, trial and error.

looking back and comparing the code didn't give much clue. it is just odd how the mesh is appearing to be almost exactly half of what it should be.

for now I suppose either use the last build release which worked, or work with what you got. because technically with a good and level bed you should not need any active bed leveling, that is even if there is slight variation +/-0.10, that isn't really significant enough to effect the first layer. I know with mine I can turn active leveling off and there's no noticeable difference.

just hang in there i'll try and figure this out.

[Arson31]

@classicrocker883 It could've been either the November or October release, they may have the same logic so I doubt it makes a difference.

[RCP1990]

Im having a similar issue when using the June UBL PRO UI. my Aquila has an ender extender kit so my bed is 400mm x 400mm. Ive set my physical settings and mesh settings to 400mm. When I home my Z axis, it correctly goes to the center of the bed but when I try to make a mesh, it probes based on the default ~220X220 bed size instead.

[classicrocker883]

@RCP1990 have you used an October or November version? if so, did it work normally then?
also, do you experience the same kind of result how it is half of the bed, or is it a bit different?

that is interesting since it is UBL, yet works fine on default bed sizes.

[RCP1990]

I have not. ill install the November and test it out.