Yet another BLtouch problem
-
other output requested is as follows
12/17/2021, 5:41:15 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9K662-MGPSS-6JKD2-3SJ6J-1ASYW
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75152 of which 12 recycled
Never used RAM 12520, free system stack 170 words
Tasks: NETWORK(ready,13.5%,233) HEAT(delaying,0.0%,314) Move(notifyWait,0.1%,329) MAIN(running,86.3%,403) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:14:02 ago, cause: power up
Last software reset at 2021-12-14 08:54, reason: HardFault invState, GCodes spinning, available RAM 15168, slot 2
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00400003 BFAR 0xe000ed38 SP 0x2001ff60 Task MAIN Freestk 31241 ok
Stack: 20011a00 0000f76e 00000002 00000000 00000f79 00409be9 00000000 200f000f 00000000 20004c8c 0000c0f7 00000000 00000001 0040cac3 00000000 00000000 0000c0f7 0045acef 00000000 20005cd8 00000001 40080000 00030d41 00000000 00000001 00000407 20004c8c
Error status: 0x00
Step timer max interval 0
MCU temperature: min 14.6, current 25.3, max 25.5
Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, 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-12-17 17:41:14
Cache data hit count 4294967295
Slowest loop: 5.15ms; fastest: 0.17ms
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 0.6ms, write time 0.0ms, 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: 73.61ms; 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 40:f5:20:0d:a9:ae
WiFi Vcc 3.31, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 21488
WiFi IP address 192.168.66.46
WiFi signal strength -62dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
12/17/2021, 5:40:55 PM M280 P0 S90
12/17/2021, 5:40:46 PM M280 P0 S10
- WiFi -
-
@phaedrux said in Yet another BLtouch problem:
M98 P"config.g"
12/17/2021, 5:43:26 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: bad grid definition: Too many grid points; suggest increase spacing to 28.5mm
Error: in file macro line 73 column 33: M563: expected number after 'F'
Error: Tool 0 not found
Error: Tool 0 not foundInteresting, does this mean it's not seeing the probe at all? Guess kinda makes sense with no blue light...
-
@macgyver said in Yet another BLtouch problem:
this seems correct as I am connected to the Heater 5 output on the expansion connector
I think you should double check that with the wiring diagram.
-
interesting development
I have updated the grid spacing to 28.5 as suggested in the last output.
I have removed the F switch on the M563 on line 73.Now the error message has changed substantially
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin name needed for switch-type endstop on Z axisPretty sure we are getting close to this.
-
So I just did the following change, I know that @Phaedrux suggested that I remove the line but I'm trying to understand where this error is being generated from
I removed Line 1
M574 Z1 S1and replaced it with line 2
M574 Z1 S1 P"!zstop"Now I am not getting any error at all
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabledI am still getting a solid red light on the BLtouch but no blue at all. My understanding is the blue light is your confirmation the "sig" or yellow wire is functional on the board? that being said if I am correct it's not seeing the "rdy" on the heater5 pin on the EXP connector.
I did double-check the wiring on the EXP and I was off by a pin so that is now confirmed to be in the correct location.
-
@macgyver said in Yet another BLtouch problem:
I did double-check the wiring on the EXP and I was off by a pin so that is now confirmed to be in the correct location.
Ok, so now does the deploy and retract work when sending M401 and M402?
-
@macgyver said in Yet another BLtouch problem:
M574 Z1 S1 P"!zstop"
This is fine, but if you have no actua endstop connected to the zstop pins you'll end up with more problems if you ever tried to actually home the Z axis with an endstop movement command. (G1 H1 Z)
-
I've gone the next step, I have a new Duet 2 board, just sitting on my desk, I have moved the firmware over to it and flashed it at 3.3.
Its a little easier to move pins around and troubleshoot with the board on my desk instead of at the bottom of a big ol printer.
I have replicated the current install of the board in the printer and still getting the same symptoms.
I have put an M401 and M402 at the end of my config.g so if the pin deploys and stows 3 times on startup it should be working fine. I have used a new BLtouch, New short harness for the BLtouch.
The only thing I have hooked to it is the BLtouch and an i7 screen. I also wanted to eliminate the possibility that the board is bad in the printer and I think this is the best way to do it.
To give updates, I have tried heater 5,3, and 8. None of them change any of the symptoms. M401 and M402 do not work.
-
Can you show your current config and photo of the wiring?
-
I think I have it, Kinda
I had a P switch in the M950 instead of S. Below are the lines from my config.g
; Z-Probe
M950 S0 C"exp.8" ; assign GPIO port 0 to heater3/Pin 8 on expansion connector, servo mode
;M950 P0 C"exp.8" ; assign GPIO port 0 to heater3/Pin 8 on expansion connector, servo mode
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to 9 BL Touch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:585 Y15:585 S28.5 ; define mesh gridThe commented-out line is the old one. Now if I use the 280 command or call the deploy and retract macros they work just fine. Only issue is the M401 and M402 do not work.
Should I be concerned that this is called somewhere else?
-
Here is the pic as requested, Nothing connected except BLtouch and i7 screen
Now I have the 401 and 402 working, there was an illegal T switch added to the commands in the deployprobe.g and retractprobe.g
-
Sounds like you've got it working now?
-
I would call it working with one exception, When I start the machine and M401 and M402 work, not an issue.
I have everything moved back to the D600 and have the rest of the machine put together. Moved all the firmware over and updated the config. g file with the error I found on the test bench. Kinda a small issue left
When I try to call the G28 it fails on the Z-axis with the error of
G28 Z
Error: Failed to enable endstopsX and Y axis work, not an issue, Pin will not deploy when it starts the Z home, however, the bed does move down 10 mm as expected and requested.
pretty sure this is going to be something in one of the macros, Going to chase it down today. If you have a suggestion where to start looking that would be appreciated.
-
It sounds like you just need to update your homeall to use a G30 to use the probe instead of a G1 H1 Z move to use an endstop.
-
-
@danzaywer
You don't need the M574 line in there. I think the config generator just puts that line in by default but it's not needed (and may actually mean something else if you dig in the docs...)@Macgyver Just make sure your homing files have a G30 command in like @Phaedrux said
-
@engikeneer said in Yet another BLtouch problem:
You don't need the M574 line in there. I think the config generator just puts that line in by default but it's not needed (and may actually mean something else if you dig in the docs...)
So can it be omitted?
-
@danzaywer yes, from the docs for M574 in RRF3:
Snnn 1 = switch-type (eg microswitch) endstop input, 2 = Z probe (when used to home an axis other than Z), 3 = single motor load detection, 4 = multiple motor load detection (see Notes).
I think the intended use of the S2 parameter would be to set your x or y axis to use the z probe as an endstop (like the ormerod printer does). Don't think it does any harm though as it is, which is why it hasn't been taken out from the config tool (though it has caused some confusion for a few people.on here!)
-
@engikeneer said in Yet another BLtouch problem:
I think the intended use of the S2 parameter would be to set your x or y axis to use the z probe as an endstop (like the ormerod printer does).
That's correct.
-
Hi Guys
Sorry for going AWOL on this, unfortunately got Covid but finally back in the office and back on this machine.
Going to work through it and update it shortly.
