knutwurst / Marlin-2-0-x-Anycubic-i3-MEGA-S

Marlin 2.0.x Version for Anycubic i3 MEGA M/S/P/X/CHIRON and 4MAX with Anycubic TFT or the "new" DGUS Clone TFT - Now also with BLTouch!
GNU General Public License v3.0
782 stars 183 forks source link

M280 p0 s10 doesn't work #201

Closed phyex0 closed 2 years ago

phyex0 commented 3 years ago

Hi dear developer. I'm in trouble with the bltouch. I couldn't use my Chinees clone to auto-level it. It didn't respond and I thought it's broken. So, I've updated the firmware and tried to use it again. It didn't respond again. Then I decided to buy the original bltouch. I've started to arrange bltouch by your guide but somehow it doesn't respond to m280 command again. I've checked the connections and it seems fine. When I turned on the power Bltouch works. but now it doesn't respond to m280 commands. What to do?

phyex0 commented 2 years ago

I've replaced whole connections to be sure there is no problem and it didn't work. I also used Mega_S_BTL_10 and Mega_S_BLT_11 and it still doesn't work. How can I debug the firmware to be sure it's not related bltouch?

phyex0 commented 2 years ago

Connecting... start Printer is now online. echo:Marlin 2.0.x Marlin-AI3M echo: Last Updated: 2021-09-18 | Author: (knutwurst) echo:Compiled: Sep 18 2021 echo: Free Memory: 1232 PlannerBufferBytes: 1568 echo:V76 stored settings retrieved (712 bytes; crc 24143) echo: G21 ; Units in mm (mm) echo:; Filament settings: Disabled echo: M200 D1.75 echo: M200 D0 echo:; Steps per unit: echo: M92 X79.21 Y79.21 Z404.04 E477.40 echo:; Maximum feedrates (units/s): echo: M203 X500.00 Y500.00 Z6.00 E30.00 echo:; Maximum Acceleration (units/s2): echo: M201 X3000.00 Y2000.00 Z60.00 E10000.00 echo:; Acceleration (units/s2): P R T echo: M204 P1500.00 R1500.00 T3000.00 echo:; Advanced: B S T X Y Z E echo: M205 B20000.00 S0.00 T0.00 X8.00 Y8.00 Z0.40 E5.00 echo:; Home offset: echo: M206 X0.00 Y0.00 Z0.00 echo:; Auto Bed Leveling: echo: M420 S0 Z0.00 echo:; Endstop adjustment: echo: M666 Z0.00 echo:; PID settings: echo: M301 P15.94 I1.17 D54.19 echo: M304 P251.78 I49.57 D319.73 echo:; Z-Probe Offset (mm): echo: M851 X-2.00 Y-25.00 Z-0.40 echo:; Linear Advance: echo: M900 K0.00 echo:; Filament load/unload lengths: echo: M603 L538.00 U555.00 echo:SD init fail

This is the output when I connect my device via pronterface.

knutwurst commented 2 years ago

Hello, can you show me some photos of your soldering? Also I need a picture of all connections you made and one from the small pcb in the print head.

Thanks in advance!

phyex0 commented 2 years ago

WhatsApp Image 2021-09-21 at 23 47 42 (1) WhatsApp Image 2021-09-21 at 23 47 42 (2) WhatsApp Image 2021-09-21 at 23 47 42 WhatsApp Image 2021-09-21 at 23 47 43 (1) WhatsApp Image 2021-09-21 at 23 47 43 (2) WhatsApp Image 2021-09-21 at 23 47 43 (3) WhatsApp Image 2021-09-21 at 23 47 43 WhatsApp Image 2021-09-21 at 23 47 44 (1) WhatsApp Image 2021-09-21 at 23 47 44 WhatsApp Image 2021-09-21 at 23 47 45 (1) WhatsApp Image 2021-09-21 at 23 47 45 (2) WhatsApp Image 2021-09-21 at 23 47 45

All of those connections and soldering are controlled via a multimeter. It seems all correct and works.

phyex0 commented 2 years ago

Also, it was the same before changing the Chinees clone and it was working. I just changed the black-blue-purple colored wires today and it seems working.

knutwurst commented 2 years ago

So.. as I understand... it's working now?

phyex0 commented 2 years ago

no it was working before but somehow it's not working now

knutwurst commented 2 years ago

Ok.. what I see is that your wiring seems to be wrong.

  1. The white cable (z-min) goes to the G3 pin which is the one which points to the edge of the PCB. In your pictures it's the other way around.
  2. I can not see or follow your servo cables. The color coding on the Trigorilla Board seems ok to me, but they might have changed somewhere...

Also I assume that the sensor itself shows an error when booting up, right? Slow or fast flashes.

phyex0 commented 2 years ago

I'll check the wiring at pcb again. Color coding seems correct. I'll check it again.

There is no error at Bltouch. There is only red color and no flashing. I can't see any error log at pronterface

phyex0 commented 2 years ago

I can't use M43 to debug pins. Why?

https://marlinfw.org/docs/gcode/M043.html

knutwurst commented 2 years ago

Because PINS_DEBUGGING ist disabled for production use. That's intended.

I'll check the wiring at pcb again. Color coding seems correct. I'll check it again.

For me it seems that white and black are switched.

phyex0 commented 2 years ago

For me it seems that white and black are switched.

I changed white and black wires but the result is the same.

phyex0 commented 2 years ago

What else I can do to solve this problem. The problem could be the PCB at the head?

phyex0 commented 2 years ago

image I replaced the PCB with this. It still doesn't respond.

phyex0 commented 2 years ago

Hey dear @knutwurst what should I do? How can I debug? Dude, please help me. I'm so fu*ked up.

knutwurst commented 2 years ago

Hi @phyex0 , sorry for the late answer. If you replaced the pcb and the sensor still doesn't work, maybe it's defective? Can you try another bltouch sensor?

You can debug the behaviour if you start the auto leveling and then short the black and white wire out so the sensor think that it's triggered.

phyex0 commented 2 years ago

Hey man, I just bought the original Bltouch and I don't think it's the problem. But I'm going the try to trigger the sensor as you said.

phyex0 commented 2 years ago

If I'm going to unplug black&white wires or make a short it doesn't start to auto-leveling. But if I plugged it, it starts to auto-leveling and it doesn't extend the probe.

phyex0 commented 2 years ago

image I guess it occurred when I short black&white wires.

knutwurst commented 2 years ago

Wait.. no... just jeave them open, start the auto leveling an then short them for a second or so to see if the printer stops.

phyex0 commented 2 years ago

If I unplug the black&white wires it doesn't start to print. How can I detect it's a motherboard issue?

phyex0 commented 2 years ago

https://user-images.githubusercontent.com/48446413/138588983-019a6993-d0c8-49ec-b2d9-9e48c5ffea2e.mp4

when I plug&unplug on the black and white wires bltouch changes the brightness. What does it mean? Are all the connections fine?

phyex0 commented 2 years ago

hey, what should I do to connect bltouch directly to the motherboard? I need to find the correct pins for black and white wires. I would like to test bltouches with my old motherboard. I'll also try to test it in an Arduino circuit. If I can test the sensors then I can find the problem I guess.

phyex0 commented 2 years ago

signal-2021-10-25-004147_001 If I can find the correct pins for the black and white wires I can test the sensors with my old board. Then I can be sure it's sensor issue

knutwurst commented 2 years ago

when I plug&unplug on the black and white wires bltouch changes the brightness. What does it mean? Are all the connections fine?

No! It seems that you have a weak GND connection or a short circuit somewhere. It must be a connection problem.

If I can find the correct pins for the black and white wires I can test the sensors with my old board. Then I can be sure it's sensor issue

Your wiring in the last picture is partially correct. You need the servo plug and "Z Min" (PIN 2). Bildschirmfoto 2021-10-25 um 07 56 23

phyex0 commented 2 years ago

D2 and D12 you mean?

knutwurst commented 2 years ago

No! Just ignore all "straight" red marks... these are for something else. You need to connect the servo port and D2. Please read and understand the diagram ;)

The BLTouch uses two separate connections.

  1. The Servo Wire (3 pins in total) to let the nozzle come down and up
  2. The "trigger" pin, which is the black and white wire. Black is Ground (GND) and White is signal, which goes to D2.

That's it.

phyex0 commented 2 years ago

Thanks a lot. Anything else I have to change? Maybe in firmware?

knutwurst commented 2 years ago

No. D2 is the default BLTouch Pin. If you use a _BLT Firmware, it should work out of the box.

phyex0 commented 2 years ago

Thanks my friend.

phyex0 commented 2 years ago

hey man. I plugged black and white wires to d2 and gnd as you told and then I sent the m119 command. z probe is open says the board. If I unplug or plug somewhere else it says triggered.

Now it's plugged to d2(white) and gnd(black) and when I send m280 p0 s10- m280 p0 s160 - m280 p0 s90 there is no probing.

There could not be a short right?

signal-2021-10-25-110058

phyex0 commented 2 years ago

So, no new idea?

phyex0 commented 2 years ago

https://photos.app.goo.gl/BR65FSCeq5HQkvUh7 i tested the sensors on arduino. Pin in pin out and self test all worked for the both sensors

What should I do?

knutwurst commented 2 years ago

I would say: rewire everything. It must be a bad connection on some of your wires.

phyex0 commented 2 years ago

I would say: rewire everything. It must be a bad connection on some of your wires.

I've already did this. I also used muter to be sure wires are not broken

knutwurst commented 2 years ago

But your cables probably have too much contact resistance. I can't do any more either. I'm sorry.

phyex0 commented 2 years ago

Well when I directly connect sensor to motherboard it didn't work too. It could be motherboard issue?

knutwurst commented 2 years ago

Try to connect the sensor directly to the board which is installed in the printer. You need to home first, then you can control the Sensor. Also it might be that you need the 12V.

Did you try another firmware? Please test the 1.1.6.

phyex0 commented 2 years ago

I'm going to try this in my free time. I'll connect the board to my PC via a type-B USB cable. Still, need 12?

knutwurst commented 2 years ago

I would say... yes... since it might need more power from the voltage regulator on the board.

phyex0 commented 2 years ago

I sold the 3d printer lmao.

github-actions[bot] commented 2 years ago

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.