I really tried to fix it myself it on my own.

TOFUATSU

I cannot get it to homez.g

I have a coreXY running Duet 3 Mini 5+ with a CRTouch.

The M280 deploy and retract work just fine when I send the commands that are in the deploy and retract .g files.

Any help would be greatly appreciated

This is the config.g

; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Fri Aug 11 2023 17:43:56 GMT-0400 (Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CoreXY" ; set printer name
M669 K1 ; select CoreXY mode

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S1 ; enable Telnet

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forkwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E409.00 ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z380 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"!io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io5.in
M574 Y1 S1 P"!io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io6.in

; Z-Probe
M950 S0 C"io3.out" ; create servo pin 0 for BLTouch
M558 P9 C"io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X150 Y150 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S285 ; set temperature limit for heater 1 to 285C

; Fans
M950 F0 C"out6" Q500 ; create fan 0 on pin out6 and set its frequency
M106 P0 S1 H1 T45 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

Here is the homez.g

; homez.g
; called to home the Z axis
;

G90 ; absolute positioning
G1 X105 Y100 F900
G30

And here is the M122 result

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3RC2 (2021-05-11 14:55:40) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 37V3T-V196U-D65J0-40KMJ-1P03Z-ZGDWZ
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 102476
Dynamic ram: 106108 of which 336 recycled
Never used RAM 31928, free system stack 132 words
Tasks: NETWORK(ready,15.8%,226) HEAT(delaying,0.0%,338) Move(notifyWait,0.1%,288) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,357) CanClock(delaying,0.0%,341) TMC(notifyWait,0.7%,115) MAIN(running,82.6%,412) IDLE(ready,0.1%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:06:43 ago, cause: software
Last software reset at 2023-08-12 22:19, reason: User, GCodes spinning, available RAM 31712, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU revision 3, ADC conversions started 403972, completed 403972, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 31.8, current 32.1, max 32.9
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/8/8, gc cycles 0
Driver 0: position 16000, standstill, SG min/max 0/8, read errors 0, write errors 1, ifcnt 39, reads 21221, writes 12, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/8, read errors 0, write errors 1, ifcnt 39, reads 21221, writes 12, timeouts 0, DMA errors 0
Driver 2: position 20000, standstill, SG min/max 0/2, read errors 0, write errors 1, ifcnt 40, reads 21221, writes 12, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/2, read errors 0, write errors 1, ifcnt 40, reads 21220, writes 12, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 29, reads 21224, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2023-08-12 22:26:44
Cache data hit count 772018305
Slowest loop: 23.01ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 6.3ms, max retries 0
=== Move ===
DMs created 83, maxWait 30420ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 14, completed moves 14, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamberHeaters = -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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 3637, send timeouts 3634, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 75.80ms; 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 f0:08:d1:03:81:a0
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 26104
WiFi IP address 192.168.1.164
WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

A Former User

This post is deleted!

dc42

@TOFUATSU a few questions:

What happens when you try to home Z?
If you send M401 does the pin deploy, and when you send M402 does it retract?
If so, then after you send M401 to deploy the pin, what is the Z probe reading shown in Duet Web Control? Does it change if you push the pin up?

TOFUATSU

@dc42

All that happens when I run the homez.g is the bed moves down 5 mm then I get a G28 Z failed error.

The pin deploys with M401 and retracts with M402: The Z-probe reading never changes

I just changed the line in my Confing.g from
M557 X15:215 Y15:195 S20 to
M557 X15:215 Y15:195 P12

I copied and pasted the homez.g file thet Herve_Smith just supplied above. Now everything looks like it's gonna work. The bed moves down a bit, the pin deploys. The bed moves up, hits the pin on the CRTouch and pushes it up and keeps going until the bed crashed into the nozzle.

This is progress.

Thank you for the help so far.

A Former User

This post is deleted!

TOFUATSU

@Herve_Smith. I checked continuity, my crimps are sufficient.

I tried that homez and pushed the pin while it was traveling. It didn’t stop it.

There is no reading for the probe on the web interface.

I also noticed that after the M401 command, if I press the pin in, I cannot get it to redeploy with another M401. I tried to send M402 then M401. M280 does nothing either. I have to reset the firmware to get it to deploy again.

A Former User

This post is deleted!

TOFUATSU

@Herve_Smith

Duet. - CRTouch. - Wire
3.3v - none. - none
IN - OUT - Blue
GND - GND - Red and White
OUT - Control - Yellow
+5V - +5V - black

A Former User

This post is deleted!

TOFUATSU

@Herve_Smith off to Microcenter then… should I try a different io on the board?

dc42

@TOFUATSU said in I really tried to fix it myself it on my own.:

The Z-probe reading never changes

Yes, but what is the Z probe reading? is it 0, 1000, or something else?

The reading never changing suggests either a faulty CRTouch, a bad connection (e.g. bad crimp) in the wire from the CRTouch output to the Duet, a problem with that input on the Duet, or an error in configuring the sensor on the Duet.

If it's a genuine UK-manufactured Duet then the input will have been tested by our ATE (automated test equipment). So:

Check that you have continuity in the blue wire from the CRTouch OUT pin to the Duet IN pin. A bad crimp connection is the most likely fault. If the crimp connection is open circuit then you will get a Z probe reading of 1000 all the time. OTOH if the pin is shorted to ground, you will get a reading of zero all the time (although this could also mean that the pullup resistor on the Duet is missing or open circuit).
Check that you have plugged the connector into the IO3 port, not some other port.

TOFUATSU

@dc42

Thank you so much!

Solved

The CRTouch was fried and my code was bunk.

I’ll dedicate the first Benchy to you guys