-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BL Touch #12
Comments
I am looking to add BL Touch to the Mingda D2 as well. The release D2-Default-v1.0.zip does not have this complied in. I think if you modify the Marlin configuration.h, and compile, it will work. It looks like configuration.h in the marlin folder already has BL-Touch enabled, we just need select D2. If I can figure it out, I'll try to paste the compiled firmware.bin here, but it might be awhile. marlin-mingda-md-d301/Marlin/Configuration.h Lines 24 to 55 in 5c3d126
|
I had some problems getting this to work, but think I solved them all.
I'm attaching the |
I ran into some problems with the hot end never reaching temperature. I discovered I'm attaching the |
I'm reading this and am about to try it 👍 Thanks! |
Thanks! Let me know if you run into any issues. |
@spessoni Last night I flashed the main build for the Mingda D2 in the releases section, then noticed that it wasn't configured properly for a BL-touch. Then without thinking I flashed my old firmware.bin file and broke the UI on the touch screen since the assets on the printer are for the new LVGL UI...! I spent the next 5 hours trying to figure out how to Flash the legacy Mingda UI assets back on to the printer, but could not figure it out! I have the stock firmware source code but after compiling it in VScode I can't find where the UI assets are compiled to since there are no .bmp files created... where are they after the firmware is compiled? I was able to find another custom build of the stock firmware online and in the source code it contained a TFT folder with .bmp files in it, that look like the correct legacy Mingda UI images but after flashing it to the printer half of the icons were still missing. I'm completely stumped on how all that works. I'm assuming if I flash your compiled firmware you posted, I am still going to have the same issue correct? Well I guess I'll find out cuz I'm going to try here in a minute. |
I owe an update on my experience. using the firmware posted here by @spessoni. What follows may be totally unique to me/my printer. I also experienced a problem with the BL Touch. The printer kept not deploying the probe and slamming into the bed. I figured the firmware might require some within-GUI config so I persisted (for hours). Then the printer went dead. The fuse in the back hadn't blown. The fuse in the PSU hadn't blown. The switch was not burned. So I took a punt and ordered a genuine Meanwell PSU. I figured if the board wasn't dead I would find a way to reverse out the firmware. However, on fitting the new and undoubtedly much better (much quieter!) PSU, everything works as expected and I have printed multiple good prints since on this new firmware by @spessoni |
Hi @bigjoncoop, I replied to your issue on the other ticket. My version doesn't use @stringerppt, thanks for the update! That sounds like it was a problem with the power supply. When they don't supply stable power, all sorts of weird stuff can happen. I'm still on the original Mingda power supply without any problems if that helps. |
Hi @spessoni. Is this version your latest "working" version? I'm using your configuration files, but my BLTouch + ABL isn't working (i've tested several sensors, so it might be something software related). |
@spessoni I am still reading as well..I just decided to bring my Mingda D2 out of retirement and give it to my son. I wanted to install Marlin, and you provided a solution for me. Last time I complied Marlin, I used the Arduino IDE, so I am lost using VSC. (Klipper is so much easier, lol) Anyway, thanks for your time/help! |
Hi!
Any chance you have a build or configuration.h that installs the BL Touch for the Mingda D2, D301 board?
Thanks!
Jack
The text was updated successfully, but these errors were encountered: