I have a BIGTREETECH SKR Mini E3 V2.0 Control Board 32Bit New Upgrade for Creality Ender 3, with TFT35 E3 V3.0 Graphic Smart Display Controller Board. I am trying to get firmware for this board with the firmware would be for a skr mini e3 v2.0, the bin file will have the z axis wizard enabled, baby step also. for some reason my computer won’t compile anything. I have got a bltouch. I don’t know why Iget the errors but if I can upload the config file i sned it.
What tool are you using to compile? The Marlin folder structure has gotten so large the Arduino IDE on Windows chokes on it. Current recommendation is to use platformio to compile on Windows. There’s some additional setup but it is covered in the docs section.
We don’t have a firmware for that board and your configuration.
You might not have the proper resources for the board installed. Really without seeing the compile error it could be any number of things.
what do you mean, its another program.
these are the crazy errors I am getting and its getting old. It’s acting like the hardware, the way they have the hardware configured in there script is wrong. to many things the program itself is not recognizing. and even the )) to ) is coming up as an error. It should bypass it.
It is my understanding you are trying to install a BLTouch. If that is the case you don’t want to use “mesh bed leveling” you want “auto bilinear bed leveling”.
Mesh bed leveling is for manual bed leveling and does not accept babystepping. Babystepping allows you to change a PROBE’s z offset by a fraction of a mm for more accurate first layer calibration. Because mesh bed leveling does not use a probe, you have nothing to babystep. (Thus the sanity check)
Bilinear bed leveling will create a mesh using the probe, and allows for babystepoing the z offset of that probe. So in config.h comment out mesh and uncomment bilinear.
As far as the errors being wired. As soon as one error is found it throws off the rest of the compile and it can generate some nasty messages fix the primary problem and the rest should go away.
If you still have errors post another picture of the remaining errors and I will try to help.
The use of “mesh” in several places in the Marlin bed levelling documentation can lead to confusion. As @Atom states above, mesh bed leveling is done through a manual process. I don’t have direct experience with that as I included a differential IR probe on my 3D printer.
The option that use on my printer (haven’t tried it on the MPCNC) is Unified Bed Leveling or UBL. It uses the probe to measure the bed at a number of points (up to a 10 by 10 grid) and builds a “mesh” that it stores in eeprom and can then apply corrections to Z heights in different amounts at different coordinates on the bed. It works well in conjunction with Baby Stepping.
My understanding is that linear and bilinear are best when you have a flat (planar) bed that may be mounted at a slight angle. UBL is best for beds (like mine) that may have irregular high and low spots - I print on glass on top of a pc-board heater and have multiple glass tops I can switch out. I can build a mesh for each glass that I’ve got and store up to 10 in eeprom. When it’s time to print you can activate the mesh that matches the currently installed glass piece. I then do a quick 3-point check before each print and “tilt” the mesh to match the current bed situation since the may not have gone back down exactly the same as it was the last time it was used.
I know, but the commented mesh text is giving error. don’t know why.
like seeing me suffer, lol
If you can provide an image of the config.h file at the bed leveling area maybe we can spot the error for you.
Bilinear works a lot like ubl. I have one printer with bilinear and it probes the whole grid (25 points) when I send G29. I do that each print. Then it interpolates between points to get the right Z. The other has UBL and it has 81 points, which would be annoying to do every print, but it gets saved to eeprom. I think you can save the bilinear grid to eeprom too, but I haven’t tried.
In his other thread I have gone through his configuration.h and got it to the stage where it will compile, he only needs to enter the offsets but he is still getting errors
on mine it retains the bilinear mesh data until the next bed level
81points… dang!!! You know, I have had to defend using 3pt on my rig before, when talking with some pro machinists about it.
I think he means 81 points total. Or a 9x9 point grid. Your probably using 9 points or a 3x3 point grid.
And don’t let others make you feel bad, if it works than it works, doing more than what works for you just wastes time
This is on my 310mmx310mm gridbot, and I had some problems with the first bed. It turned out it was flexing in funny ways as it was heating up. I am sure I hit the 9x9 grid at some point in my testing and tuning and never turned it down.
I also have a (pretty annoying) 5 min wait after I heat the bed up, but before I print. I have replaced the first bed, and I think the second one works better. But if I change anything and I don’t get perfect adhesion, I’m going to doubt myself.
But yeah, I don’t mind the 81 points. I don’t have to do them. The BL Touch does. . And I only do those once a month or whatever when I change something.
Yeah if it works it works, no need to mess with non-broken items… and yes it’s not much more than a little bit of time and maybe slightly more wear, but no labor for more probing. TBH, I would use more of a grid if I had a bltouch. With my inductive I would have to cover my bed in target dots.
That is nice that you are getting away with probing only once a month. My printer changes z ever so slightly depending on bed and nozzle temps (like 0.15mm diff between say, nylon and pla). This is likely due to thermal expansion of the bed and/or nozzle. So I have my slicer do a probe before every print. I also have a short wait after bed preheat, but not forced; I have the bed preheat before the nozzle. So the bed gets to soak for about a minute or 2 before probing for leveling.
[edit: I didn’t explain how I work around my issue with z changing… to compensate for that I have my slicer configured for a different z offset for each different filament. So really leveling every time is probably not needed… but not fixing it as it works. Ironic though, that my printer may actually probe more points per month than yours if I do a lot of prints. LOL!]