Hello again and thanks for responding and the explanation. More on that though, if I may. In regards to a. it was initially set like that, stock from Creality. I did everything upside down. But when I went over my (marlin 2 bugfix) config, I file compared with the example config (which mine was built upon). Only difference is one was downloaded 2 days ago, the other about 6 weeks ago. Not sure hoby OrAnGeWorX - Firmware - Marlin
QuoteMMcLure It's possible that Creality has changed the design of the Ender 5 - they have been known to constantly change things without notice. I know that many people on the Marlin discord would mention that the nozzle could _not_ physically reach the whole bed on their Ender 5s which is why the bed size was reduced for the example configurations. I am in the process of writing a document on hby OrAnGeWorX - Firmware - Marlin
Hey there, couple questions, are you using Marlin 2.0 or the Bug Fix? Also how did you compile Marlin (options/environment)? Did you grab the example config for your printer/board from the config git?by OrAnGeWorX - Firmware - Marlin
Well, you don't necessarily need to know GCode but it definitely helps to speed up and better control the process... I'm also a noob so no worries You can also have both auto and manual leveling which is useful, you need to make sure that mesh leveling is on and as well as whichever ABL you use, i.e linear/bilinear/UBL... HTHby OrAnGeWorX - Firmware - Marlin
QuoteMMcLure The reason the bed is defined as 220x220 is because the nozzle cannot actually reach the full area of the bed. In this case it's better to define a "virtual bed" that is smaller than the physical bed to ensure that you don't run into the limits by mistake. Thanks for taking the time to answer. That's incorrect (physically) because with stock firmware, the nozzle covered the whole beby OrAnGeWorX - Firmware - Marlin
if you can't lower it, that's because you're against SOFT_ENDSTOPS... you can disable them for Z setting and locking them after saving your Z to EEPROM. check out this video it should help you get your offset GLby OrAnGeWorX - Firmware - Marlin
Hello everyone, I've tried looking for information regarding my "issue" to no avail. I have an ender 5 Pro with the stock 8bit board, flashed with Marlin 2,0 BF and pretty much everything is bone stock aside from a BL Touch. When I got the Bug Fix files along with the config examples and started to go through the fw, I noticed that it was configured with a 220x220 bed size. The bed is in fact 235by OrAnGeWorX - Firmware - Marlin
@Dust: thank you! Indeed it seems I have extracted the 2.0.7.2 over the 2.0.x BF... and that crapped everything. I've cleared the files in my build folder, redownloaded BF and config, compiled the default and the modded config correctly. But this brings me back to the initial post; successfully compiling with the TFT_LVGL_UI... When I compile with TFT_COLOR_UI enabled, firmware build is ok. whenby OrAnGeWorX - Firmware - Marlin
that's so strange... could it be that I downloaded a non bug fix and dumped over a bugfix ?by OrAnGeWorX - Firmware - Marlin
Here are my latest logs. Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\Marlin-bf2> platformio run -e chitu_f103 Processing chitu_f103 (platform: ststm32@~12.0; board: CHITU_F103; framework: arduino) -------------------------------------------------------------------------------------------------------------------------------------------------------------by OrAnGeWorX - Firmware - Marlin
Here's a follow up. Started from scratch. marlin 2.0 bug fix + new modified config files following the examples (also 2.0 bug fix) I can no longer successfully compile the firmware... so weird here's the logby OrAnGeWorX - Firmware - Marlin
Hello everyone, I'm here because I was referred from the Marlin Github page because I am having a user-support issue and not a bug. I won't dwell on this as it's a waist of time, energy and really not constructive (plenty of examples on there of actual user-support but hey, I'm not an all-knowledgeable mod) To be honest, I'm not even sure what I'm asking. I had posted my tests here but haven't haby OrAnGeWorX - Firmware - Marlin
I have a X5SA-Pro with the Chitu v6 board. Like most here initially thought there was something weird with the sensor... crashed the nozzle into the bed several times and having lost lotsa hair trying to figure out what was the issue. The main problem with this printer is the implementation of marlin on the software side and the fact that the double Z aren't synch'd, hardware wise. I ended up goiby OrAnGeWorX - CoreXY Machines