Here's my M122 output - this is new to me - :
M122
=== Diagnostics ===
RepRapFirmware for STM32H7 based Boards (biquskr_3_ez_h723) version 3.5.0-rc.1+102 (2023-09-05 23:17:13) running on STM32H723 (standalone mode)
Board ID: L0001-082KA-D43WN-6R1DG-WF6XX-70000
Used output buffers: 3 of 40 (27 max)
=== RTOS ===
Static ram: 44072
Dynamic ram: 87752 of which 0 recycled
Never used RAM 114968, free system stack 112 words
Tasks: NETWORK(2,nWait,9.8%,224) HEAT(3,nWait,0.0%,350) Move(4,nWait,0.0%,256) CanReceiv(6,nWait,0.0%,431) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,333) TMC22xx(4,nWait,0.7%,147) FSWRITE(2,nWait,0.0%,567) MAIN(1,running,89.2%,1131) IDLE(0,ready,0.3%,30), total 100.0%
Owned mutexes: WiFi(NETWORK) BITIO(TMC22xx)
=== Platform ===
Last reset 00:04:53 ago, cause: software
Last software reset at 2023-09-19 00:08, reason: User, Gcodes spinning, available RAM 114968, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 49.6, current 53.2, max 53.2
Supply voltage: min 24.0, current 24.0, max 24.0, 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
Events: 0 queued, 0 completed
Driver 0: standstill 2209, SG min 38, reads 24356, writes 17, error r/w 0/1, ifcnt 38, timeout 0
Driver 1: standstill 2209, SG min 14, reads 24356, writes 17, error r/w 0/1, ifcnt 38, timeout 0
Driver 2: not present
Driver 3: standstill 2209, SG min 14, reads 24356, writes 17, error r/w 0/1, ifcnt 42, timeout 0
Driver 4: standstill 2209, SG min 0, reads 24360, writes 13, error r/w 0/1, ifcnt 27, timeout 0
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Driver 12:
Driver 13:
#I can't seem to get Z to work properly
1 messages · Page 1 of 1 (latest)
Date/time: 2023-09-19 00:13:48
Slowest loop: 3.60ms; fastest: 0.03ms
=== Storage ===
Free file entries: 20
SD card 0 detected
SD card longest read time 2.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 142990ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 10, completed 10, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x80000007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 2635, received 0, lost 0, boc 528
Longest wait 0ms for reply type 0, peak Tx sync delay 0 free buffers 50 (min 50), ts 1465/0/0
Tx timeouts 0,0,1193,0,0,904 last cancelled message type 0 dest 1
=== Network ===
Slowest loop: 25.09ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0)
HTTP sessions: 1 of 8
Uploads/Errors: 0/0
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Bad header: 0/0
Firmware version 1.27-04S32-D
MAC address b4:75:0e:63:da:95
Module reset reason: Turned on by main processor, Vcc 0.00, flash size 4194304, free heap 143588
WiFi IP address 192.168.1.79
Signal strength -21dBm, channel 9, mode 802.11n, reconnections 0
Clock register 00002003
Socket states: 0 0 0 0 0 0 0 0
Driver 2: not present
That's not good is it
no. time to revisit that driver
i would swap drivers 2 and 3 and see what RRF reports
remember to do so with the power off
what does M122 say now?
=== Network ===
Slowest loop: 25.09ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0)
HTTP sessions: 1 of 8
Uploads/Errors: 0/0
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Bad header: 0/0
Firmware version 1.27-04S32-D
MAC address b4:75:0e:63:da:95
Module reset reason: Turned on by main processor, Vcc 0.00, flash size 4194304, free heap 143588
WiFi IP address 192.168.1.79
Signal strength -21dBm, channel 9, mode 802.11n, reconnections 0
Clock register 00002003
Socket states: 0 0 0 0 0 0 0 0
you probably want this part?
Driver 0: standstill 2209, SG min 0, reads 13076, writes 13
Driver 1: standstill 2209, SG min 0, reads 13076, writes 13
Driver 2: standstill 2209, SG min 0, reads 13076, writes 13
Driver 3: standstill 2209, SG min 0, reads 13076, writes 13
Driver 4: standstill 2209, SG min 0, reads 13075, writes 13
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Driver 12:
Driver 13:
must not have been seated properly
does this mean i got a bad ez driver?
no, they're being read fine now. give it a try
see if both z steppers work
ok i'm sending g92 z0
now from dashboard sending z+5
HOLY THAT WORKED
That looked so smooth I am geeking out like Sam Tripoli right now
ok gonna try to home z
if I can do this I can autolevel the bed then I'm off to the races
probe went to middle of bed then bed started going south
had to emergency re-start
reversed z motors (i think)
The only issue seems to be that the bed goes up and hits the probe but it does triegger. Trigger height I'm thinking?
why do you have an M558 H30 line in your config?
not sure what that is, let me check
have this
M558 P9 H10 F300:100 T8000 C"^probe" ; set Z probe type to bltouch and the dive height + speeds H=dive height; F=probing speed; T=travel speed
;;M558 Set Z probe type: P9=BLTouch that needs to be retracted and redeployed between probe points
;;M950 S0 C"Servo0" ; Setup Servo0 as servo port on SKR3EZ H723
; Miscellaneous
T0 ; select first tool
hmm
when the bltouch is retracted, does it show as 1000 in the interface?
it should show 1000 when the pin is in and 0 when its out
I've got z probe at zero when it is in
If it never changes then you need to check your wiring
when I click pin down (macro) it causes the pin to extend
but still says z probe is at zero
There's 2 sides to a bltouch, the servo, which in your case is working, and the switch side, which isn't
So you need to investigate the black and white wires from the switch
Check the wiring
i don't understand
Well the wiring is obviously wrong
if i can hit the macros and make the pin go up and down?
ok. So theoretically I could switch the white and black wires?
Not really. Black is ground, white is the probe pin
That's fine
thx jay
gonna send it
ok. 2 be clear what's going on is
when i hit "home z" the bed (on ender 5 plus) goes up as expected
but when the bed hits the probe it does not trigger
and a bad noise ensues
until i hit emergency stop
right, because your probe isn't working properly, probably due to a wiring fault
i'm not sure how else to say it
i'm thinking if I can control the probe through the macros, how can there be a wiring fault
i will say this again, there are 2 parts to a bltouch
the servo part that deploys and retracts the pin that you did have working
then, theres the detection part that doesn't work
you need to investigate the BLACK AND WHITE WIRES
DO NOT mess about with the others as that part is (although not anymore) working