Closed tommygunn212 closed 6 years ago
It's better to copy your configuration.h
to configuration.txt
, then drag the configuration.txt
file here.
Can do the same for configuration_adv.h
.
Thanks for the info I am new here didn't know..
I will say that RC8 hasn't been changed in quite some time. Double-check your setup.
RCBugFix is the latest bleeding edge fixes and new features to RC8.
Also, is it a genuine BLTouch or a clone?
I was on rc6 everything was working fine then I got the bltouch so I moved to rc8 so as far as hard goes I think that part is good. It's a real bltouch
Does my setting look right?
They look okay to me, but I don't have a BLTouch.
Do you have to have #define Z_MIN_ENDSTOP_INVERTING false
.
Will changing that to #define Z_MIN_ENDSTOP_INVERTING true
make any difference for you?
Yea I tried that didn't do anything...
It's plugged into Servo 0?
RC8 (Your config):
// The BLTouch probe emulates a servo probe.
// The default connector is SERVO 0. Set Z_ENDSTOP_SERVO_NR below to override.
#define BLTOUCH
RCBugFix config:
/**
* The BLTouch probe emulates a servo probe.
* If using a BLTouch then NUM_SERVOS, Z_ENDSTOP_SERVO_NR and Z_SERVO_ANGLES
* are setup for you in the background and you shouldn't need to set/modify/enable them
* with the possible exception of Z_ENDSTOP_SERVO_NR.
*/
//#define BLTOUCH
//#define BLTOUCH_DELAY 375 // (ms) Enable and increase if needed
Try upgrading to RCBugFix.... see if that helps.
Yes it is plugged in to pins closes to the reset.
Where do I download the rcbugfix files? Thanks for helping 👍
5:39 am time for bed...will try in the morning again
Since you can deploy & stow the probe tip then we know the servo signal is setup properly. That means you probably don't have the output of the BLTouch setup properly.
There's a utility in the latest RCBugFix that will test the BLTouch.
In Configuration_adv.h enable PINS_DEBUGGING then issue a M43 S command.
An alternative is to use the following sequence. The blue LED is present only on BLTouch units that have a serial number.
bob thanks for your input i am finding the z is always triggered take a look below is there another place to reverse the trigger?
Connect BLTouch, power up controller and upload the firmware using rc8 for now before i try bugfix Blue LED will be ON if a servo signal is present. no orange light M119 ; should return OPEN. If not check that the BLTouch is enabled in the configuration. If enabled then check wiring and check that the correct pin is being used. light color wire is towards board darker color is closer to the edge. on servo 0 the closest to the reset button M280 P0 S10 ; should deploy the probe and the orange LED will be OFF. it deploys out and blue light comes on. M119 ; should return OPEN x and y open but z is triggered M280 P0 S90 ; should stow the probe and the orange LED will be ON yes M280 P0 S60 ; puts it into the M119 test mode. The probe should remain stowed and the blue LED should be OFF. If it's ON then the unit needs to be adjusted. M119 ; should return TRIGGERED M280 P0 S160 ; returns it to normal operation M119 ; should return OP
it look like the Z is always triggered i i have switched the logic on the z to true and false on the endstop and probe in diferent combinations true false, false false // Mechanical endstop with COM to ground and NC to Signal uses "false" here (most common setup).
Enabling BLTOUCH automatically sets Z_MIN_ENDSTOP_INVERTING and Z_MIN_PROBE_ENDSTOP_INVERTING to false no matter what is in the configuration.h file.
Always returns TRIGGERED means either the cable is bad, you're connected to the wrong pin. the pin assignment settings have a problem or the BLTouch is defective.
You have Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN enabled which means the white BLTouch signal wire must be attached to the Z_MIN endstop input. On the RAMPs board the signal pin is the outside pin nearest the board edge. If you need further assistance in identifying the correct pin then take a look at this.
If the above doesn't fix it then there's a couple of tools in RCBugFix that I'd like you to try. After enabling PINS_DEBUGGING in Configuration_adv.h, issue a M43 I command. That'll tell you what pin is being used for Z_MIN (should be D18) and if any other signals/functions are assigned to that pin.
Always returns TRIGGERED means either the cable is bad, you're connected to the wrong pin. the pin assignment settings have a problem or the BLTouch is defective.
Or... That the BL-Touch is in an error state. At least... That is what I've noticed.
Ok turning on the the bltouch it goes in to self test the 3 blinks and in and outs.
Here are some pictures of the wires
Your wiring is correct.
Now to see if the cable/wire/connectors have issues.
Disconnect the BLTouch black & white wire. M119 should still say triggered for Z_MIN.
Jumped the black & white wires together on the controller side at the BLTouch connector. M119 should say open.
Re-connect the BLTouch and, if you can, jumper the black & white wires together at the BLTouch. M119 should say open.
If all the above checks out then your BLTouch is defective.
If the above doesn't checkout then I'll want you to download RCBugFix. If the M43 I command doesn't show any issues then I'll want you to tie one end of a (approximately) 1K resistor to ground and tap the other end to the Z_MIN, Z_MAX & Y_MAX pins. The console port should report that pins D18, D19 & D15 changed state.
Redoing rc8 And retried
M280 P0 S10 ; should deploy the probe and the orange LED will be OFF. M119 ; should return OPEN M280 P0 S90 ; should stow the probe and the orange LED will be ON M280 P0 S60 ; puts it into the M119 test mode. The probe should remain stowed and the blue LED should be OFF. If it's ON then the unit needs to be adjusted. M119 ; should return TRIGGERED M280 P0 S160 ; returns it to normal operation M119 ; should return OPEN.
All of this is is as it should be! I also check homing for x axis which is the on the left side and y is back So when I do auto home It moves to the left on x axis hits the end stop then the y moves back hits the enstop then the y moves forward and then the x moves to the full right and all the way and the pin pops down and tries to hit the bed but it is too far right. (Bltouch is offset x 30 on the extruder). Bed is 200x200
Last error now is doing a g28
here is my latest config h files https://www.dropbox.com/s/gsjq0jep988rhlz/Marlin_config_h.zip?dl=0
In other words... It is trying to probe off the bed??? If so... Turn on the 'Safe Homing' option and set the probe point for a Z-Home operation in the middle of the bed.
i had it on safe homing and i had this // The center of the bed is at (X=0, Y=0)
i took of safe homing it was worst the x and y axis were going crazy also abit confused with this.. / // +-- BACK ---+ // | | // L | (+) P | R <-- probe (20,20) // E | | I // F | (-) N (+) | G <-- nozzle (10,10) // T | | H // | (-) | T // | | // O-- FRONT --+ // (0,0)
i have it set at 30 since that is the distance between the nozzle and the pin. what is this (20, 20) and (10, 10 ) thing?
Here is a video with safe home. And the errors look at previous config h zip file.
Link to video https://www.dropbox.com/s/n80jx33p68c14i2/Video%20Apr%2017%2C%203%2047%2006%20AM.mov?dl=0
What did you do to get the Z axis to lower when doing G28?
Your safe homing setup is normal.
Let's do some sanity checks. Your config file and the video indicates that the nozzle can't travel outside the bed and that he travel area is 200mm x 200 mm. Is this correct?
When you issue a G0 X0 command followed by a G0 X50 command, does the head travel 50mm?
I hadn't noticed that BED_CENTER_AT_0_0 was enabled.
With Marlin thinking the center of the bed is 0,0 and Z safe homing setup to probe at 100,100 then yes, it will try to probe off the bed.
Either disable BED_CENTER_AT_0_0 or disable Z safe homing or change the Z safe homing point to something that can be reached.
Currently the Z safe homing definitions are:
#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 200
#define Y_MAX_POS 200
#define Z_MAX_POS 200
#define Z_SAFE_HOMING_X_POINT ((X_MIN_POS + X_MAX_POS) / 2) // X point for Z homing when homing all axis (G28).
#define Z_SAFE_HOMING_Y_POINT ((Y_MIN_POS + Y_MAX_POS) / 2) // Y point for Z homing when homing all axis (G28).
Will try that in a little bit yes my bed is 200x 200 should I put 190 for max pos? Or 180?
Why do you have BED_CENTER_AT_0_0 enabled? This is normally enabled on circular beds such as on delta printers.
Cartesian, COREXY & COREYX printers normally have the 0,0 point in the left front corner.
My suggestion is to just disable BED_CENTER_AT_0_0.
ok got it working! ok this is what i did... i started with fresh copy of rc8 and unplugged all the endstops and some other wired and reseated them then i setup basic printing function making sure everything was going in the right directions. once that was established i started setting up auto level and ran the instructions bob gave me, everything started working. now why did i have it on center? because i thought it had something to with home to center it said nothing about delta printer maybe they should put a comment in there about that. it is very unclear what it does. i thought it was something like -100---0---+100 in case you wan wanted to move the center a bit more to the left, right etc.
now my final question which will be an easy one for sure now that i tested the auto-level it did the 9 point check and i adjusted the edges. i had seen some in a video where they were still doing the paper thing to get the height of the nozzle and doing m581 to get offset I still have to do that correct? what is the correct order of of the next step? i dont just go to the starting gcode in my slicer and put m29 right after m28 right? Bob you have been a huge! help without it i would be stuck here for who know how long! thank you so much! same to roxy and tanno for pitching in too!
FANTASTIC!!
Yes, doing the paper test and then M851 is the next step.
I'm not aware of a reason to put M29 or M28 in the slicer code. Starting and stopping the print is done via the USB or LCD
I'm not aware of a reason to put M29 or M28 in the slicer code. Starting and stopping the print is done via the USB or LCD
Correct... M28 and M29 probably do not belong in your Slic3r's Start-Up GCode. BUT... You may want a G28 and a G29 in your Start-Up GCode. Almost for sure, the G28 will be there by default along with some stuff to heat the bed and nozzle. But the G29 you will have to edit in with what ever options are appropriate for your machine.
Doh! I meant g28 and g29 not m.. I did all m851 g1 z0 and did the repetition test it said it was 0.0005 Well now I am off to do some pid tuning flow rates and figure why I am getting air prints on this one model... Again thank you all for helping me solve this problem so quickly. You guys rock! 🤘😜🤘
Oh one last thing going back to the center question I was doing a large print last night I had centered it and in the slicer but when I went to print it one side was more on the right side like 1mm off the edge and the left side had a ton of room how do I fix that? Besides moving the model in the slicer?
Hi tommygunn212, I have also a prusa i3 rework 1.5, so it's very difficult for me to configure my BLTouch. Is it possible to share your Marlin RC8 with BLTouch configuration ? Thank you in advance.
BugFix_v1.1.0 has a lot of stuff in it to support BL-Touch probes well. You want to declare you have a BL-Touch and let the system do the right thing. There are places where the BL-Touch can go into an error state and the firmware checks for that and tries to recover. But it only does that if you declare you have a BL-Touch.
tommygunn212 can you pleae provide your config files so that I can compare it to myn? thank you
i actually have to redo mine and i lost the files on my computer...
Tommy
On Thu, Sep 20, 2018 at 7:47 PM nexgen91 notifications@github.com wrote:
tommygunn212 can you pleae provide your config files so that I can compare it to myn? thank you
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MarlinFirmware/Marlin/issues/6371#issuecomment-423369633, or mute the thread https://github.com/notifications/unsubscribe-auth/AaY8ScieDyzgoRO_I5dweRRleGDSgVJ_ks5udCkcgaJpZM4M-96E .
-- Tommy Gunn
i actually have to redo mine and i lost the files on my computer... Tommy … On Thu, Sep 20, 2018 at 7:47 PM nexgen91 @.***> wrote: tommygunn212 can you pleae provide your config files so that I can compare it to myn? thank you — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6371 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AaY8ScieDyzgoRO_I5dweRRleGDSgVJ_ks5udCkcgaJpZM4M-96E . -- Tommy Gunn
Ok thank you anyway. If you need any help or want to check out my config let me know, I was having a bunch of issues and just got it all sorted this morning.
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.
Hi i need some help getting my bl touch to work about my setup i am using prusa i3 rework with a e3d hotend and titan extruder my bed is 200 x200 180 the bltouch offset is on the x 30 it is in the right side of the nozzle.
i think i followed all the basic config h settings x and y homing is fine but the z is not homing at all and the pin is in the up position with red light. i tested the bltouch and it does go up and down using the test code m280 p0 s120 so i have been working on this for 2 days trying to get it to work with no luck at all can someone look at my config h and see if there is some i left out or miss config something.
here is my config h file thank for you help in advance!
```cpp /** * Marlin 3D Printer Firmware rc8 good * Copyright (C) 2016 MarlinFirmware [https://github.com/MarlinFirmware/Marlin] * * Based on Sprinter and grbl. * Copyright (C) 2011 Camiel Gubbels / Erik van der Zalm * * This program is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 3 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program. If not, see