Strange BLTouch behavior after update to 3.3.0-b3

droftarts

@waddo10 First, update to 3.3 RC2: https://github.com/Duet3D/RepRapFirmware/releases
There's been quite a few fixes since the beta releases.

I think you have a Duet 2 WiFi? Update the firmware, then send M122 and post response to clarify your setup.

Cloned BLTouch may not have the same wiring as the original, so check that first. When you send M401, and touch the pin, does it register a change in Probe Value in DWC?

This line:

M558 P9 C"zprobe.in+zprobe.mod" H5 F180 T6000 A30 S0.02

should really be:

M558 P9 C"^zprobe.in" H5 F180 T6000 A30 S0.02

zprobe.mod isn't used, and the ^ enables the pull up resistor, which may help.

Ian

waddo10

@droftarts
Updated and this is my M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3beta3 (2021-04-22 16:27:28) running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSJ-6J1F6-3SJ6L-991UR
Used output buffers: 3 of 24 (18 max)
=== RTOS ===
Static ram: 23156
Dynamic ram: 75272 of which 12 recycled
Never used RAM 15976, free system stack 180 words
Tasks: NETWORK(ready,14.9%,143) HEAT(delaying,0.0%,306) Move(notifyWait,0.1%,190) MAIN(running,84.5%,441) IDLE(ready,0.5%,19), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:06:53 ago, cause: power up
Last software reset at 2021-05-14 14:06, reason: User, GCodes spinning, available RAM 15800, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x10
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 27.8, current 31.3, max 31.6
Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-05-14 15:13:09
Cache data hit count 4294967295
Slowest loop: 863.58ms; fastest: 0.15ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.6ms, write time 205.5ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1469.12ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address cc:50:e3:e3:b9:19
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25360
WiFi IP address 192.168.1.208
WiFi signal strength -47dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

I have modified that line of GCode and will test it now.

Just been comparing the two BLTouche's side by side and noticed a bit of a difference on the circuit board between the two even though they are both V3.1

New

Old

waddo10

Tested the old and new bltouch with the updated firmware and config adjustment. Old BLTouch homes fine. New BLTouch is the same as before, Pin doesn't deploy when trying to home Z.
On the old bltouch on startup the pin probes in and out, ends with the pin stowed and output reads 0. M401 pin out Output 0, M402 pin stowed output 0. M401 and touch the pin output 1000.
On the new bltouch on startup the pin probes in and out, ends with the pin stowed and output reads 1000. M401 pin out Output 1000, M402 pin stowed output 1000. M401 and touch the pin output 0.

Strange behavior.

droftarts

@waddo10 sounds like the output of the clone is inverted. Try:
M558 P9 C"!^zprobe.in" H5 F180 T6000 A30 S0.02
Note ! in probe name.

Ian

waddo10

@droftarts Do you think the old or the new one is the clone? As in ive been using a clone all along?

droftarts

@waddo10 new one is clone, I’d say. They shouldn’t need to be inverted. Also PCB looks simpler on new one, doesn’t have notch top and bottom. Mine has the notches, and I’m sure it’s genuine.

Ian

Phaedrux

@waddo10 said in Strange BLTouch behavior after update to 3.3.0-b3:

3.3beta3

It looks like the update to RC2 failed.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.3RC2

Try uploading again.

Did you resolve the problem with the heightmap not loading? Where were you loading it?

MGJosh

FWIW, http://www.id2db.com/genuine10.php reports both probes' serial numbers as legitimate. I think there's some confusion in this discussion about which probe is new vs old, but either way, I have a new v3.1 that looks basically identical to A7X... (corner notches on PCB, no "A&T" letters on injection molded housing body), and an older V3.0 and a V3.1 that looks very similar to 9CR... (square corners, no "R" on BLTouch on PCB). I'm also very confident that mine are all genuine.

That is all - I can't really help with the main issue, but thought providing some info from my own stock of probes would at least better inform that part of the discussion (it's easy to dismiss a failure as a crappy clone, vs. a legitimately failed BLTouch, which does happen too). I'm also not saying definitively both are real, just that right now my vote would be that both are legit.

waddo10

This post is deleted!

waddo10

@phaedrux Well spotted. I have downloaded again and appears to have worked this time.
I am still testing at the moment, not quite sure whats going on. Using a old model i had printed which i know loads the heightmap.
Just loading the standard heightmap that mesh compensation generates.

waddo10

@mgjosh A7X is the new one i had bought. 9CR is the one ive been using for a long time and suspected was going faulty. 9CR is the only one that works with my current config. That you for your reply.