Blinking bltouch

PaulHew

M122 as well, please

crchisholm

M122 return....

12:33:51 PMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6J9FL-3SD6R-KDB0F
Used output buffers: 3 of 20 (11 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98660 of which 0 recycled
Exception stack ram used: 280
Never used ram: 6608
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:04:22 ago, cause: power up
Last software reset at 2019-09-15 18:22, reason: User, spinning module GCodes, available RAM 6340 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 30.9, current 37.4, max 37.6
Supply voltage: min 23.6, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-10-06 12:33:46
Cache data hit count 973540141
Slowest loop: 2.50ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 23.07ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22
WiFi MAC address b4:e6:2d:53:00:09
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28568
WiFi IP address 192.168.0.11
WiFi signal strength -54dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

PaulHew

Firstly, what version BL Touch are you using, 2 or 3?
Do you have another printer to test it with?
Also do you have a ' config-override.g '? If you have please check it does not have a M307 H3 command in it.

Secondly, may I suggest you update your firmware to at least 2.03.

I have combined your 'BLTouch code' and 'Z-Probe' into one.
It has the main commands I think to get you going.

I am not saying it is perfect....... Just trying to help.
;New BLTouch
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F100 T2000
G31 X30 Y15 Z2.63 P500
M557 X30:290 Y30:290 S112

Have you tried this again?
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Software_setup_Duet_2_WiFi_Ethernet

The BLT not doing its probe test on power up is the mind boggling thing.

P.

Phaedrux

@crchisholm said in Blinking bltouch:

G29 S
M375 ; load "heightMape.csv"

It's best to NOT load the heightmap in the config.g since at power up the Z0 point hasn't been located yet. Better to add it to the end of homeall or to the slicer start gcode as long as it's after the Z axis has been homed using the probe.

If you upgrade to firmware 2.03 it will complain that the heightmap has been loaded before the Z 0 datum has been established.

If the BLTouch problem seems to follow the board and not the probe itself then there is either something wrong with the board connectors or wiring.

antlestxp

I just went through the same issue. I rewired and still had the same problem even thought my bl would be able to drop and lift the pin. I could even probe without any problems. It would just always flash. I ended up removing the top grub screw and seeing how well the pin could move. I found that there was just the slightest resistance as it moved. It could still move on its own but it must be able to tell if there is any lag or hesitation. I used a replacement pin and still had the same issue. I ended up cleaning up the hole at the end of the bltouch body and that seemed to fix the issue. The bl should be able to self test without the duet giving it commands when you first power up. If you are into radio controlled models or drones you can plug it into a receiver and see if it works. Its just a fancy servo after all.

crchisholm

yep. I took the pin out and checked it out. There was absolutely no resistance. If I turned the BLT upside down, the pin will fall out with no effort.

I also re-terminated the connectors on the Duet side of the cable and looked at them under the USB microscope and they are exactly as they should be.

And yet, it only flashes and does not initialize.

I will look more closely at the changes that @Phaedrux and @PaulHew suggested tomorrow.

I am really baffled. I always hope that it's something that I am doing wrong. That's been the case in the past, but I have been over this over and over and over and I can't find it.

antlestxp

@crchisholm i would say hit them up. They are a little slow to respond but they may work out a replacement for you. antclabs@gmail.com

crchisholm

the only thing I HAVE NOT changed is the Duet board. I have ....

tried three versions of the cable.
tried two BLTouches...one that has never been used before now.
checked all the connectors
checked continuity and resistance on all wires (all wires show 0.4 oms)
Looked at the pins on both the Duet and the BLT with a usb microscope. All looked good (no bends or discoloration)
tried all the code changes suggested.
probobly a few other thing I can't remember now.

The only thing that has been constant through the whole ordeal has been the problem and the Duet board itself.

Has anyone experienced a problem with the BLT and found that there was an issue on the Duet board itself?

I can't really afford to buy another Duet board. I might buy another BLT, but am afraid that's another rabbit hole. Also, this problem went from working perfetly and then not working at all with no changes in between other than not printing for a few days.

Frustrated in Florida!

crchisholm

How can I determine which version BLTouch I have. Amazon says it’s Antclabs, but does not show a version. I believe I have v3, but not sure.

Phaedrux

@crchisholm If it's a genuine BLTouch there should be a silk screened version number on the PCB.

antlestxp

If you don't have the cut trace you probably have a v3. If it has the trace then v2

crchisholm

Ok, I have v2. Was there much improvement between v2 and v3? I just ordered another v2 (now I know - wish I had waited.).

Phaedrux

@crchisholm the v3 is native 3v tolerant now. No more resistors or traces to cut. Not sure what other tweaks they may have made. The v2 is still very capable.

crchisholm

@Phaedrux Wow. There may be clue in this. I just got the BLTouch and to my surprise, it is a v3.1 Some time back, @dc42 had sad that I did not need to add a resistor or cut the trace any more, but he may have thought I had the v3.1. I did not cut the trace or add a resistor because of that. Even if that is the case, certainly, no blame on DC42. I did not make it clear what version I was using because I didn't know it made a difference.

If that's the case, maybe I blew out the other two BLT's. (both v2)

Does that sound likely?

dc42

@crchisholm said in Blinking bltouch:

If that's the case, maybe I blew out the other two BLT's. (both v2)
Does that sound likely?

No. You would blow a BLTouch if you applied significantly more than 5V to it. It might also be possible to blow the output driver in the BLTouch by shorting the output (white wire) to ground or to +5V or +3.3V, but without the schematic I can't say whether that is likely or not.

crchisholm

Hu-ray!!!

The new BLT v3.1 works. After I established that, I plugged in the old ones into the new cable and they still didn't work, so I think that means that the two v2's are tiny boat anchors. I still have to unmount the old BLT and mount the new, but I suspect I will be printing again tomorrow.

Happy Me!!!!
Thanks for all the suggestions and help I got on this thread. Wish I could buy you all a couple of coffee and a dough nut.

Charlie

PaulHew

Glad you have got it working again.

How old are the others, you might be able to return them under warranty, might!

However, brilliant and look forward to seeing your first straight print!

Paul

crchisholm

Hey Paul,
I looked up when I bought them and it was January of '19, so i had them a little longer than I thought. Looking at it that way, I guess that's an ok life span.

I'm just happy to have it working.

tdybare69

This post is deleted!

crchisholm

@antlestxp said in Blinking bltouch:

If you are into radio controlled models or drones you can plug it into a receiver and see if it works. Its just a fancy servo after all.

That is an interesting idea. Can you tell me more about how that works. I have a RC tx and rx.