[BUG] ABL-BLT not working properly
Closed this issue · 39 comments
Did you test the latest release build?
Yes, and the problem still exists.
Bug Description
Ok, I downloaded what I THINK is the correct version and Fashed it.
"Aquila_GD32_BLT-5x5-NoPro-MPC.bin"
My Machine is:
G32
BLtouch ABL
and I want MPC so I downloaded
"Aquila_GD32_BLT-5x5-NoPro-MPC.bin"
Not sure about NoPro but this was as close as I could get.
I flashed
I rebooted, UI came up fine.
Reset Probe Offsets
Manually set Z-Offset, and confirmed it was correct with another reboot and check Z
Tried to do a "Build Mesh"
It did the G28 Z
Moved to the First position and probed once while showing "Bilinear Leveling" on the UI and... Back to the UI after doing 1 probe, The Screen still says "Biinear" at the top. If I attempt to generate a mesh NOW, it does the G28 Z sort of (only 1 probe) and then goes to try the corner and never gets low enough for the probe to touch.
REBOOT and try the same thing....
It does a FULL G28 Z, two probes, one fast, one slow
Goes to the corner, probes the corner properly.... and STOPS
Without touching anything else, any attempt to generate a mesh now just repeats with the proper G28 Behavior.
When It finishes the corner probe it lifts, pauses and then lifts again before returning to the Menu.
Did I get the right version, or am I missing something else... is there another step I need to do before tying to create a mesh. My Bed is pretty well trammed already but I can try seeing ig going through that procedure makes any difference.
Give me a direct email, and I will send you videos of the behavior...
Bob Sisson
Printer Model
Voxelab Aquila
Model Type
Aquila
Your Mainboard
Aquila GD32
Other Mainboard Type
I only know it as G32 not GD32
Add-ons that could be involved
BL touch
ProUI?
NoPro
Bed Leveling
BLT - BL Touch Bilinear mesh
Did you include your own configuration files?
- A ZIP file containing your
Configuration.handConfiguration_adv.h.
Additional information & file uploads
Please let me know what to try in the way of tests to see what it is doing.
I also can give you access to my PRONTO interface so You can play with system remotely
(Its actually Repetier and Has a Camera as well)
go to one of the commits made by me, ex.:
https://github.com/classicrocker883/MRiscoCProUI/commit/65c3dd34d65d1c890be71d7cac25eb1a09d38cfc
copy the URL and add ".patch" to the end, you should see the email at the top
that is very cool I didnt know I could be able to access remotely that way. you can do that if you like - send access, I just dont know when I would be able to get around. I'd like to try anything I can on my end first.
the -BLT / Bilinear version is one I have focused on less, since there are a couple issues/or lets say inconveniences - regarding that.
for that reason, I do suggest trying -UBL / Unified Bed Leveling.
the thing about this, is it takes more up more memory space, so if I were to enable -MPC for it, I would have to disable a couple other things, but these things are like: being able to change the UI color theme, or viewing End Stop diagnostics - stuff that doesnt effect printing in anyway.
but what I'm able to do is leave you with some options you can try out. I'm going to make a version with the most recent MRiscoC that just came out the other day. the UI is very different, but it may have some new code and fixes.
It just came out so I haven't gone through it just yet, which I would fork over anything that makes this one better.
as soon as the issue im having doing the github Actions are worked out, I can then compile the new release version. hopefully sometime today.
I will upload UBL with -MPC, I recommend using that one.
Then moved up (back) and to the right and almost probed. Missed the bed by
about 2mm. And then it probed again, and again...
so the probe missed the bed, like it was off to one side?
have you updated your Probe Offsets??
it may be different for everyone.
the probe should be touching the same point as with nozzle
https://www.youtube.com/shorts/FKvPU2nwdts
another thing is changing the Mesh inset. by making the Min X/Y inset bigger. or Max smaller, may help align where the probe goes.
edit:
I understand being able to set and forget printing. I use OctoPrint to do just that, being able to print from another room and not have to worry. Once you have everything all calibrated, you should be all good to go.
default parameters may be close, but they should not be expected to be exact for everyone's printer, because even though it is set for a stock machine, there are still variations between each one built for whatever reason.
Question. Is there a "Z" probe offset? I re-loaded some old software as I
needed to print something so I can't go check. If there is, how do you
choose a value?
yes, I think this is why you are having difficulty. Z probe offset can be changed through "Z-Offset Wizard" in the "Prepare" menu.
sorry if there was any confusion.
Adjusting the Probe Offset for Z was removed from the "Probe Settings" menu, in "Level" Menu, which was next to the ones for X + Y. because it is redundant.
you can also edit the value using M851 Z + the value. so like M851 Z-0.15 for a negative Offset, same goes for X|Y
https://marlinfw.org/docs/gcode/M851.html
I may have mentioned this somewhere else but the ideal way to level everything is first get your Z-Offset, using the wizard in "Prepare". I mean before anything you should go through the menu's settings in both "Control" > "Advanced Settings", and anything in "Level". then go to "Prepare" > "Z-Offset Wizard". follow the instructions, which should automatically move the nozzle to the center, and lower it to the bed. once there (or near), change the Z-Offset value using the knob, its better not to like paper in between and let the nozzle itself just barely touch the bed. once that happens, you should have a true Z-offset. a way to double check this is to either redo the "center nozzle on bed" or tell the printer to move to Z0.00, like G1 Z0. there should not be a gap, but also the nozzle should not be pushing down on the bed, except only just barely be touching.
then go ahead and perform the "Bed Tramming Wizard". I like to do it Manually first, which is basically like the same thing for Z-Offset, except when the nozzle goes to each corner, turn the knobs until it is just barely touching the bed, like for center. you may have to rehome Z and do this one more time for better precision. then by doing an auto Tram with the probe, the values don't have to be exactly zero, close enough is fine, thats why I like to do it Manually first and double check with the probe.
again if the values are off, you may need to adjust the Z-Offset value. then go ahead to the Level menu and perform an Auto Level procedure. you should have a mesh that is ready to print.
I have noticed that even if the mesh is +/-0.10 (max difference), you should be fine printing without auto bed leveling enabled (G29/M420)
I should be having a Build Release within an hour or two.
new release should be ready, finally
if you havent, check out the WIki https://github.com/classicrocker883/MRiscoCProUI/wiki/Calibration-Guides
hi sorry what was your email?
also, the thing with these boards is they cannot flash a firmware larger than 228k, nor can they support non-Maple, that is the ones labeled for -422, which use an STM32. if your Aquila doesnt have that chip, it will not flash. only Maple environment is supported for GD32/N32
also, I have since uploaded a new release for January, I may have re-released it more than once, but the newest one should have the ProUI with MPC you were looking for. and you should be using -GD32 only
I think that when you hit load defaults, it resets the values so anything saved will be reverted.
sometimes some settings do save from the previous even after a new flash.
Ok, I know I have a "G32" board, but I don't know about the STM32.
you mentioned flashing the "422" version. that is meant specifically for if you had replaced the board with a creality 4.2.2 board, just like if it were a creality 4.2.7 board, you would use the "427" version. this is why some of the versions would not work.
there are similarities and differences between the G32 aka GD32, and STM32 (which is on 427 and 422 boards).
- 422/427 have 512k flash memory, GD32 has 256k.
- GD32 and N32 use a Maple type bootloader. STM32 do not.
- 422/427 firmwares are compiled using standard non-Maple. they will not flash on GD32 or N32.
that said, firmware .bin files 228k and under will work, because max is 256k (= bootloader + firmware.bin). if you have a "G32/GD32" use firmware that have only "GD32".
have you tried the most recent release?
Try the ProUI version with MPC
what probe are you using? BL-touch, CR-touch, 3D-touch?
sometimes there may be issues using these. apparently there has been reports of the CR-touch having issues. I have a cr-touch and have not experienced any problem.
I couldn't tell you why you are having the issue but yes definitely send a video in email. I sent you one back.
so when it is saying 11.10 that is the minimum clearance of 10mm + offset.
it appears your Z offset is +1.10
this seems not correct. usually if you have a probe the offset will be (-) negative.
lets say you reset the Z offset to 0.00. G28 Z should bring the nozzle to the center. do G1 Z0, observe the relation between the nozzle and bed. the nozzle should be above the bed slightly, right?
this is another way to change the Z offset. you want a negative number for Z offset - you want it until the nozzle reaches the bed, then stop and record the offset. you may have to enter M211 S0 to turn off soft endstop. remember to do M211 S1 after this is done.
so you can manually tell the printer to move down with M290 Z-0.1. it might help using paper, do this until the paper doesn't move. whatever number Z is at should be your Z offset. it should be a negative number and don't forget to take away the thickness of the paper which is usually 0.10mm
I really like your version of the firmware, but I have the same problems, one day I started printing and almost broke the extruder nozzle because the offset for some reason went wrong, before this incident several prints went through without problems, the 3D touch does not work, the same problem I can’t build a mesh, I feel like after the next firmware some data remains in memory from the previous firmware. Also, the printer does not correctly determine the area of the bed when manually setting the bed level; all points are shifted forward by about 4 centimeters. I tried to compile the firmware myself from your sources (I need a maximum bed temperature of 120 degrees, and presets for a larger amount of ABS, PETG, Nylon, PLA filament), the same problem. Aquila x2 N32.
@inspectionsbybob were you able to send me the video via email? if that doesn't work send it to the same screen name @gmail.com.
the 3D touch does not work, the same problem I can’t build a mesh, I feel like after the next firmware some data remains in memory from the previous firmware.
@Cr-opas in what way does your probe not work?? it is possible that sometimes data does roll over.
Also, the printer does not correctly determine the area of the bed when manually setting the bed level; all points are shifted forward by about 4 centimeters. I tried to compile the firmware myself from your sources (I need a maximum bed temperature of 120 degrees, and presets for a larger amount of ABS, PETG, Nylon, PLA filament), the same problem. Aquila x2 N32.
for bed temps I might be able to increase it next build. as for points being shifted, this might be due to the mesh_insets. after starting, go to the leveling menu, and Probe settings, look for Mesh Insets. make sure those values can cover the bed. its possible that the "workaround" I made hasn't loaded properly. so what happened originally, the mesh_insets would automatically shrink based on the probe offsets. this is so all the points can be reached by the probe, basically moving the points inward so the probe can reach. this isnt right because you want the mesh to be able to take up as much as the bed as possible, so I implemented a workaround. the mesh_insets should "max" out covering most of the bed. you should be able to adjust the inset if necessary, defaults should place a 10mm inset from the edge.
you can test this by going to the edit mesh menu, set the probe to any point along each edge, and in essence you should have a perimeter 10mm inside of the bed. this is for a couple reasons, 1. being you dont want to probe exactly on against the edge. you can always adjust this to account for any bed clips that might be in the way.
also, are you using the "_BLT" version or "_UBL". someone had pointed out in the _BLT version that the mesh may not load correctly from starting, and that either manually loading settings or reset defaults fixes it.
there has been reports of the probe not working correctly. however that was in the past and should have been fixed then. I have a CR-touch and not had a problem, but some others report issues using this.
These Aquila's might be a clone of Creality Ender-3V2, but there are still differences which sometimes there is an issue with the probe.
just make sure the probe is plugged in correctly, some come with wires with split connectors, like having one with 2 wires, and one with 3, instead of the usual 5 in a row on just 1 connector.
oh one thing I forgot to mention was try disabling HS mode - High Speed mode. its in the Probe settings, bottom setting below M48. I bet you that might be it, thats something that has been an issue. You can also try changing "Extra Probing". its the same as "Multiple Probing". extra meaning additional probes. there was some weird thing going on since the ProUI_EX features were updated, it used to work normally as in it probed twice. but I set it to 0, because 1 doesnt work with HS mode. you can set it to another value (like 2) if you want but it will probe 3 times +.
I can confirm with HS mode disabled bed meshing and tramming wizard work.
Bug or feature? ;-)HS is an enhanced feature, some probes (clones of the original Antclabs BLTouch) are incompatible with HS mode.
hi yes busy days for sure, I'm working on a few fixes, and so that we are able to adjust the mesh and grid array in the NoPro version, like the ProUI with all the extra features.
i've been trying to get the multiple/extra probing to work like it is supposed to, that is being able to set any value 0-4. where 0 - probes once, 1 - two times, 2 - three times.....so on.
the latest right now is for January. I would go for one of the UBL versions. which is just an enhanced BLT. here is one w/MPC
Aquila_GD32_UBL-ProUI-MPC.bin
you can also use a "NoPro-#x#-" file, like 7x7. are you using a different size bed? because to be frank, you don't really need to go higher than 7x7 on a bed this size. the reason why 7x7 is ideal is because the probe offset limits how far right it can probe, so unless you lessen the X max mesh_inset, the last row cannot actually be probed. but the firmware is able to "fill in the blanks" accurately. so its a good compromise because you are able to get the most probed points without sacrificing more than 1 row. like if it were 8x8 or 9x9, at least the last two rows wont be probed.. again it can be filled it smartly.
and you can always check the actual offset manually if need to.
https://github.com/classicrocker883/MRiscoCProUI/releases/tag/2.1.3f-2
new build here. there has been a few fixes, ill do a complete list later, but real quick I updated the Multiple Probing so that it actually works as it should. 1 probes once, 2 two times, so on...
trammingwizard works better as well, cancel bed leveling... for the -NoPro versions, I was able to make it so you can adjust the grid_array, 3x3 5x5 ect..., mesh_inset's, zprobe speed...
let me know how everything is, any changes to be made. also if you still have issue with BL touch, disable HS mode in the Probe Settings menu, under Level menu
That is more than all the previous versions have done.
this is good news!
Ok, first problem.... MANUAL leveling doesn't deploy the probe AND It doesn't recognize the probe offsets. Bottom left, where I start, was too far left so It was off the bed, I mostly use auto leveling so I can move forward with this...
Manual leveling is not supposed to deploy the probe. the purpose is to check the bed level without the probe at all. if you are familiar with (-MM) Manual Mesh Bed Leveling then you would know what that is for. basically instead of using a probe, you're able to find the level of the bed by the distance of the nozzle from the bed.
for instance, using a piece of paper to gauge the distance. the Manual leveling part when having a probe is to double check in a sense. or if the probe cannot reach certain parts of the bed, manual leveling is a way to check the level using the nozzle - as if the Nozzle is the probe (edit)
so basically you take the piece of paper (i actually dont use anything, no gauge no paper, I have the nozzle come straight to the bed surface and thats how i know the level, anyway...) place it under the nozzle and the point you with to probe, and find the "sweet spot" and record the distance like you would tramming a corner of the bed. then you would subtract the thickness of the paper from the measurement and thats your new value.
since you have a bed probe this really isnt necessary, but its there to check any of the grid points if you wish.
hello I hope everything has been working as it should since that new update. I think the previous issue could have been due to a small change in the code which changed how "Center Nozzle on Bed" behaved, which would explain the main issue, the Z offset distance was registering too far.
basically Center nozzle in bed should have places the nozzle in the center, and also lower it to nearly touching the bed surface. you can see the differences between firmware versions.
I have been running the basic version for a week or so with no other issues.
I will try a MPC version next… thought the version I downloaded said it had it but can’t find any reference to it in control or prepare. when tried to invoke the test with an Mcode it said not found
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.
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.