-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SKR v1.4 Turbo + BLTouch marlin configuration #207
Comments
I'm having the same issue with SKR v1.4 Turbo + BLTOUCH v3.1. I tried just commenting out this line: The probe can do self-test etc, but when I try to home the Z axis, the BLTOUCH probe does not deploy. And thus causes the nozzle to crash into the bed. When the BLTOUCH is sitting idle, an M119 command shows that Z_Probe and z_min are in state 'TRIGGERED' , when they should not be, according to Marlin firmware documentation:
|
IDK if this helps but I pulled an all-nighter getting my SKR V1.4 (non-turbo) all configured for my printer and first time installing BLTouch. I managed to get the BLTouch pin headers on the board to work by making a few changes. I started with a fresh 2.0.x branch since I couldn't get the BTT version to compile. Comment out the line in Configuration.H: and define: Open Conditionals_LCD.h located in ..Marlin\src\inc.. and change these lines: to: Basically Marlin doesn't let the printer home the Z-axis with the probe when an end-stop is connected. When I get time, I'll mess around some more and try to add some lines so that the end-stop can be used as a fail-safe in case of probe failure (which is probably the original code's intent). My BLTouch is fully functional and tested with this method. Just keep an eye on it because I'm not sure if the end-stop will do anything if the probe doesn't home properly. |
That is very interesting. I will give that a try.
I am having a similar issue. However, I did finally fix the BLTouch not
homing Z by using the Z-endstop pins for it instead of the designated probe
pins. It worked as it should for a few times then went right back to
crashing into the bed. I didn't change the firmware at all between it
working and it not working. So this leads me to believe the actual
motherboard SKR V1.4 has an issue. I can't figure it out. I'm thinking of
just ditching the whole BTT line and going with a Duet instead.
On 2/2/20 11:53 PM, Evan LeCompte wrote:
IDK if this helps but I pulled an all-nighter getting my SKR V1.4
(non-turbo) all configured for my printer and first time installing
BLTouch. I managed to get the BLTouch pin headers on the board to work by
making a few changes. I started with a fresh 2.0.x branch since I couldn't
get the BTT version to compile.
Comment out the line in *Configuration.H*:
//#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
and define:
#define Z_MIN_PROBE_PIN P0_10
Open *Conditionals_LCD.h* located in ..Marlin\src\inc.. and change these
lines:
#define HAS_CUSTOM_PROBE_PIN DISABLED(Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN)
#define HOMING_Z_WITH_PROBE (Z_HOME_DIR < 0 &&!HAS_CUSTOM_PROBE_PIN)
to:
#define HAS_CUSTOM_PROBE_PIN true
#define HOMING_Z_WITH_PROBE (Z_HOME_DIR < 0)
Basically Marlin doesn't let the printer home the Z-axis with the probe
when an end-stop is connected. When I get time, I'll mess around some more
and try to add some lines so that the end-stop can be used as a fail-safe
in case of probe failure (which is probably the original code's intent).
My BLTouch is fully functional and tested with this method. Just keep an
eye on it because I'm not sure if the end-stop will do anything if the
probe doesn't home properly.
Thanks for this work. I shall try it out as soon as this current print is
finished.
One question just to clarify:
This is when using the designated BLTOUCH probe pins, i.e. these:
[image: image]
<https://user-images.githubusercontent.com/10586/73634800-02594200-4630-11ea-815a-910f9334f5e1.png>
and *not* plugging the probe into the Z-min stop header (as was required
with SKR v1.3) *correct*?
Also, should it not be possible to have both the BLTOUCH and the stock
Ender 3 Z end-stop (it being plugged into Z-Min header) working as well, to
provide as you said, a failsafe?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#207?email_source=notifications&email_token=AMTMQMIILE7IDG5MTCXUTP3RA7EPDA5CNFSM4KLW3342YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKS2SKQ#issuecomment-581282090>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMTMQMOEOD4MAZR3KAAO2LLRA7EPDANCNFSM4KLW334Q>
.
|
Thank you very much @S13Tyler , that did the trick! |
@Evanlec No problem man! As a warning though this is just a band-aid fix. As soon as I have time to sit down and write some new lines I'll post it for you guys or maybe someone else will dive in beforehand! |
Have you got this working using the dedicated pins yet? I've been asking around, but no one seems to have found a solution. |
Good work @hopeinformer ! I've just run into this myself and you've saved me a lot of pain. For anyone else reading through this:
Let's assume this is set correctly by the user. This should be commented out on any board, including the SKR 1.4/Turbo, where there's a dedicated pin/port for the probe that you plan on using.
This isn't required - it's already set correctly in the appropriate pins file.
No need to modify the first line. If configured correctly by commenting out Now, that last line... However, In essence, the Marlin developers have said, "If you have a custom probe pin, you cannot home with your Z probe." I can't believe this is desired behavior, more of an oversight, so I've raised this as a Marlin bug. This is not a BigTreeTech issue, though they themselves should have raised this with Marlin. Tl;dr: in
with
|
i've managed to reproduced as well , correcting this is a rather dangerous band-aid, if you just disable Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN the probe will come crushing down the bed, so this fix could be forgotten during upgrades between firmwares! |
@S13Tyler - The change you suggested in the Conditionals_LCD.h file works great until version 2.0.4.4. of Marlin. |
So I got the BLTouch (3.1 version) to work just fine making no edits whatsoever to vanilla Marlin other than enabling BL Touch and 5V and a single change to the pins file: #else This uses the dedicated pins on the board, with the hotend fan plugged into HE1 and the cooling fan plugged into FAN0 |
@thelittlemike Did you get this working with the v1.4 turbo? Been having a lot of difficulty with trying to get my BLTouch set up with no luck. I tried the fix above (commenting out second half of HOMING_Z_WITH_PROBE) and that didn't work for me. I'll try modifying the pins.h file like you did and see what happens. Also, if it is the v1.4 turbo, shouldn't BLTouch be in 3.3v mode since the v1.4 turbo has 3.3v logic? Why set it to 5v mode? |
This was on the SKR 1.4 Turbo (LPC1769). Are you sure that it is only 3.3V logic? Some of the pinouts denote 5v. Unfortunately the schematic does not say what the probe puts out and I haven't actually hooked up a multimeter to it to confirm one way or the other. I can say that the probe is working just fine after my changes, though. I'm even doing a 7x7 (49 point) grid on my ABL; which takes forever, honestly. Not sure if I recommend that. |
@thelittlemike I'll try changing it to 5v and see what happens. I just tried your fix with 3.3v. When I auto home, X and Y home correctly and Z starts moving down, but the probe doesn't deploy. |
I tried with both force 5v on and off and it worked both ways for me, honestly. The only time it didn't work was before I set that Z_STOP pin. Other than that, it's been working great. One thing you can try is to use Cheetah 5.0, which is a build of Marlin 2.0.3 and change the pin file. |
@thelittlemike Tried with 5v and your fix. My pin still doesn't deploy for whatever reason during Z homing, even though it works fine with deploy/stow and self-test. |
Did you try Cheetah? |
Cheetah does nothing special. |
That's a bit of a stretch. If my configuration works and nakedandjameson tried making the same changes and it didn't work for them, using Cheetah could help in that it would make sure they have everything else configured correctly. I mentioned Cheetah because it works. I'm running it right now while I work on upgrading to 2.0.4.4. |
Whats the current status? If i disable Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN my printer doesnt home Z, if i enable it i get an error and my bltouch only starts clicking and then throws the error |
Does anyone have final solution on this yet? |
@xkuyax i'm not sure if 2.0.5.2 resolves the issue yet but I was able to get it to work using the changes recommended above in 2.0.5.1. The issue is the logic conflicts with itself ... so in Conditionals_LCD.h you need to change line 586 to read Then commenting out This worked for me. |
Thanks ! That worked for me too. Marlin 2.0.5.2 |
I've just been setting up my Ender 3 Pro with an BTT SKR 1.4 Turbo fitted with TMC2209's. My goal was to have sensorless homing + have the BLTouch used for UBL. Initially I had some issue with the z-homing but after experimenting I've been able to get it working well using the SKR1.4's dedicated z-probe pins. Here are the key configs I've landed on: Configuration.h
Configuration_adv.h
On the hardware side, BLTouch is wired up to the corresponding SERVOS/Probe pins on the motherboard. I also have the original z-endstop microswitch still wired up and this is critical to it working. Without this homing won't work for the z-axis. With this setup you can auto-home fine, and G29 etc to use the BLTouch for leveling. If you insist on removing the z-endstop switch you'll likely either need to swap the BLTouch z-pins to the normal z-endstop, or use SENSORLESS_PROBING and rely on stallguard for the z-axis. (Or hack Marlin like mentioned above, however this will make upgrading to newer versions harder so I'd avoid it unless absolutely necessary). |
You do not need to have the endstops wired up. I'm not sure why people aren't able to get it working. I'm not a Marlin guru, so unfortunately, I can't really tell what's wrong. I just know that I have sensorless homing, stallguard, BLTouch 3.1 (authentic) connected to the dedicated pins, cooling fan on auto as well as hotend fan. Auto Home, bed leveling, all that stuff works for me. Here's my configs if maybe some of you guys can reverse engineer what I did. |
@thelittlemike I'll take a look and see if I can figure it out, thanks for posting your configs. Out of interest, what version of Marlin are you using, and did you start with the BTT fork or straight from the official repo? (For this built I started from the BTT fork, but I plan to switch back to the mainstream repo shortly - fork is 2.0.1.) |
@thelittlemike PS - Love the custom machine name ;) |
@djessup Could you help me out since you seem to be one of the people who has the most insight? ^^ Much has changed and I am rather confused: I have regular X, Y and Z endstop switches installed, BL touch (clone) probe plugged into servo + probe ports and being on the latest Marlin main branch (so 2.0.6 + some commits): What are the steps now to enable the BLTouch in Marlin "the correct way" (so as little hacky as possible)? |
Alright, I think I have it working - my entire config changes (using CR10s default config example) to make BLTouch work:
|
I previously tried getting the dedicated "Z_MIN_PROBE_PIN" to work and even tried some of the above. All failed or force modifying other core files which I didn't want to do. So I reverted to the more common way of using the Z Endstop pin (mirrored SKR 1.3 setting using normal z endstop instead). As my cable was DUPONT instead of JST, it kept popping out. So I decided to try using the "Z_MIN_PROBE_PIN" again and found an easy way to get it working (at least for me). Below I've included the only settings changed and/or reverted via other guides for adding a BLTOUCH. Configuration.h: #define Z_MIN_ENDSTOP_INVERTING false // Leave-as or revert to Marlin default //#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN // CHANGE THIS - Comment Out //#define Z_MIN_PROBE_PIN 32 // Leave-as or revert to Marlin default Am curious if this works for others too. Only tried this on Marlin v2.07 and doesn't include other BLTOUCH recommended settings. (Z_MIN_PROBE_PIN == "P0_10" and is already defined in PINS file. See second post above for Z_MIN_PROBE_PIN position on the SKR 1.4 board ) Found this after posting above |
Any news on this? I had my genuine BLTOUCH working without any problems. Suddenly this problem occured without any software changes. Wiring is okay. Ordered a new bltouch and the error still exists. Tried all the newest marlin changes shown in this issue. But don't get it to work. |
Alo can anyone help me, my bl touch does deploy when i home but it doesnt stow when it hit the bed it changes color but crashes into it, tests works fine etc |
After a lot of trial and error, this is working for me (SKR 1.4 Turbo + BL Touch + Ender 5 Plus): `#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN #define USE_PROBE_FOR_Z_HOMING #define Z_MIN_PROBE_PIN P1_27 // Pin 32 is the RAMPS default //MW 1_27 is z endstop pin; probe pin is P0_10` |
Thanks i got the BLTouch working now, but when i try to home or probe the bed the printer cant find the right home location and it probe 5 time in a very small area from the left to the right and then moves a bit down probes 5 times in the same place moves a bit more down and then probes 5 time in a small area to the right and keeps this patteren till its finished with its points, any idea whats wrong ? :) i tried to print one of my old files, and it seems like the plate site is written wrong it prints it very very very small, but i got it on 308mm in marlin and the plate is 310 |
I had to register on GitHub to make my 1st comment, so please be patient my wordiness. I ended-up here after a couple of days of frustration trying to get the my BLTouch and SKR 1.4 Turbo to be friendly with each other, using the dedicated probe port. However, the good news is I finally I got the BLTouch and SKR1.4 Turbo working together! Well, this is after several more days trying some of the helpful suggestions in this thread (i.e. dedicated probe port, z-min port, different Marlin versions, and modifying Configuration.h), and re-reading this thread several more times! Anyways, please see below. ORIGINAL attempt to configure BLTouch: NO GO RESULTS: The BLTouch was functional, and no Z homing crash. However, the printer could never do proper bed-leveling, as the nozzle was always a few mm above the bed, both during testing and printing (note, Z offset was configured in OctoPrint). FINAL attempt to configure BLTouch: SUCCESS (everything is the same as above, except for below) RESULTS: The BLTouch is fully functional (with the Z offset configured in OctoPrint). However, no physical Z-axis endstop (I wish I didn't clip the TMC2209). Anyways, after several print jobs and reboots, the BLTouch and SKR 1.4 Turbo are now working together as intended. Hopefully, this helps someone, and if they can please test the above then comment on their findings! Anyways, now I've got to concentrate on troubleshooting the Filament Sensor. Regards, |
My probe deploys and stowes just fine. M119 shows it triggered when triggered and open when open. |
i have the exactly same problem. i'm on a sidewinder x1 with skr 1.4 turbo and bltouch. |
I did not. I had to buy a different 3d printer control board with a plug for the bltouch.
Rob
…________________________________
From: Chazy12 <notifications@github.com>
Sent: Monday, November 9, 2020 3:30 PM
To: bigtreetech/BIGTREETECH-SKR-V1.3 <BIGTREETECH-SKR-V1.3@noreply.github.com>
Cc: rlbeers <rlbeers@hotmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [bigtreetech/BIGTREETECH-SKR-V1.3] SKR v1.4 Turbo + BLTouch marlin configuration (#207)
@Culem94<https://github.com/Culem94> Check you wiring is correct. Use GCode or menus in Marlin to manually test/deploy/stow to confirm.
FYI I originally had a cheap clone that wouldn't work no matter what firmware/hardware changes I tired. I suspect it was DOA. Got an official BLTouch after that and it worked fine. Not saying all clones are bad or won't work, but there are certainly some out there with issues.
I have the same problem as @Culem94<https://github.com/Culem94>. My BLTouch is a clone but it worked absolutely flawless ever bevore on a GT2560 board. I have attached it to the dedicated Probe connector(s), checked the wiring, the red led is lit permanently and I can deploy/stow/test it with M280. The problem I have is that it simply does not deploy when starting to home Z. I do not have a physical switch connect to the Z-Min connector. Any idea what I can do to make it deploy?
i have the exactly same problem. i'm on a sidewinder x1 with skr 1.4 turbo and bltouch.
did you solved it?!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#207 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACDNXTRM55ETDAGAQGWSWITSPADIRANCNFSM4KLW334Q>.
|
I'm really surprised this is still open. It is possible to make this work, although I haven't pulled bugfix-2.0.X down in about 8 months now: MarlinFirmware/Marlin@201c991...WhittlesJr:ender-3_skr-1.4 I'm too lazy to open up the case and check what the wiring is like, but I suppose I could be convinced to do so if needed. |
Solved it. Attached the bltouch ground to the z endstop and uncommented the |
I have 1.4 Turbo board and 3D Touch. I could'nt run them properly on Ender 3 Pro. Could someone upload all files that works? |
Hi Asil35, You can take a look at my Configuration.h that's setup for my Ender 5. Hopefully, that gets you going! However, you may need to change some settings specific to your Ender 3 Pro. Cheers! |
@Asil35 and others, Please see the Appendix K of this manual with help installing a BLtouch with SKR V1.4 Turbo board: https://github.com/GadgetAngel/SKR-V1.4-Turbo-Stepper-Driver-Jumper-Configuration-Manual/tree/master/CURRENT-Manual Here is the PDF for the manual:https://github.com/GadgetAngel/SKR-V1.4-Turbo-Stepper-Driver-Jumper-Configuration-Manual/blob/master/CURRENT-Manual/SKR%20V1.4%20TURBO%20Stepper%20Driver%20Jumper%20Configuration_version%20V4.0_reducedFileSize.pdf You can download the zip file here: https://drive.google.com/file/d/1FvFCCCenZh_xMIvMoKWdRaBnWbXT4PAJ/view?usp=sharing |
@Asil35 and everyone on the thread - I was experiencing all of the general symptoms and frustrations with getting the configuration correct. GadgetAngel has everything correct as of Marlin 2.0.7. Running Ender 3 Pro + SKR 1.4 Turbo + BL Touch 3.1 + TFT35-3.0 v3.0 Follow all of the steps and settings in Appendix K and everything will be spot on to get it running and ready for some tuning. @GadgetAngel - A very big thank you for the generous detail you have provided in your manual! |
Just to add more credibility for the PDF @GadgetAngel posted, I was able to follow the instructions in that absolutely massive PDF and get everything working correctly. The document outlines different procedures for many different situations and likely has the solution you (the person reading this bug) need. For the sake of posterity, my situation is:
Following the clear document my solution was:
And then everything worked AFAICT flawlessly. That document is a lifesaver, and its worth noting it also has an amazing amount of information about pretty much everything concerning the configuration of an skr 1.4 board. I'm going to be using this document to configure my board and firmware in the future and I wish I had found it sooner. |
I am trying to instal skr 1.4 turbo and bl touch on sw x1, did you succeed ? have any advice pics or anything ? thank you |
I have had problems with the BTT SKR v1.4 Turbo and the BLT v3.0 |
I think they fixed fixed this problem in the new version of Marlin, this method works also for me using the dedicated pin |
hi help please |
So I have gone through the PDF, and set up everything according to instructions, using the Probe pins (0.10), and while the probe passes the startup test it does not trigger during homing at all. I've tried this multiple ways (with the PDF being my last attempt) and it has never worked. I've also tried in klipper, which also didn't work. I can get it to work using the z-endstop pins instead, however the issue there is that the bltouch LED will light up... and then a second later it will retract. Meaning that the z-height offset has to be something like 6mm, and I have no idea if it will even do a bed mesh at that point. Videos of what is happening (one is klipper, one is marlin, but both similar) Wiring is checked and is correct as-per PDF (i've always had it correct, from the looks of things). I've tried many, many variations of settings. None have helped so far. |
Can anybody give me work config file for sk1.4 turbo with bltouch for marlin 2.0.7.2? When auto home i get error. Table push pin of bltouch and board show error. |
Hey did u end up getting it going? |
@wisesokol It sounds to @vortex690 and perhaps others that when you say "Work!" that you are angry at your printer and telling it to work. Explain whether that is what you mean or whether you mean "It works!" with the configuration you provided. Also, the pins_BTT_SKR_V1_4.h file already defines the pins, so you don't need to change that if you use the BLTouch connection diagram you attached. |
@wisesokol thanks for the configuration. It worked for me. However, I don't believe that you need both #define Z_MIN_PROBE_PIN P0_10 in configuration.h and #define Z_STOP_PIN P0_10 // Z-STOP in Marlin-2.0.7.2\Marlin\src\pins\lpc1768\pins_BTT_SKR_V1_4.h I think you can use one or the other as the #define in configuration.h will override the #define in the pins file. |
I have bltouch on my printer and when I enable Power Loss Recovery, as soon as it switches to printing, I get this error: reset the printer and start printing. When Power Loss Recovery is turned off, it smoothly bed-levels and switches to printing. please do not give up your support When I make the settings like this, it works, but it starts printing from the beginning. #define POWER_LOSS_RECOVERY |
Initial marlin configuration has Z_MIN_PROBE_PIN and I don't see in manual what should it be. Currently my BlTouch doesn't work because of that I guess.
The text was updated successfully, but these errors were encountered: