Z-probe commissioning problem

RGN01

I'm assembling a new delta printer with a Duet WiFi and a Smart PCB effector and am having a strange problem with z-probing.

Everything seems to work OK:

the green LED flashes twice when 5V is applied
it flashes when I tap the effector
M31 reports 0 normally, 1000 when it is tapped

Unfortunately despite this, a tap is not recognised when doing a G30 and, if not manually stopped then the hot end crashes into the bed - and the impact is still not recognised.

My config.g file is as follows:
[c]; Configuration file for testing Duet Ethernet and Wifi

; Communication and general
M111 S0 ; Debug off
M550 PRGN_Duet ; Machine name and Netbios name (can be anything you like)
;M551 PPassword ; Machine password (used for FTP)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address

;*** Networking - Enable for both WiFi and Ethernet boards.
M552 S1 ; Turn network on

;*** Ethernet networking: Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P192.168.0.244 ; (0 = DHCP)
M554 P192.168.0.254 ; Gateway
M553 P255.255.255.0 ; Netmask

M555 P2 ; Set output to look like Marlin
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)

;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M665 R246.6 L440.0 B360 H550 ; set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 Z16 E16:16 I1 ; Set 16x microstepping with interpolation
M92 X200 Y200 Z200 ; Set axis steps/mm
M906 X1000 Y1000 Z1000 E800 I50 ; Set motor currents (mA) and increase idle current to 50%
M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E1200 ; Maximum instant speed changes mm/minute

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
; M305 P1 T100000 B3974 R4700 H30 L0 ; Put your own H and/or L values here to set first nozzle thermistor ADC correction
M305 P1 X200 ; RGN added for PT100 on extruder
M305 P0 X201 ; RGN added for PT100 on Bed
M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds

; Fans
M106 P1 H-1 ; Disable Fan 1 thermostatic mode

; Tool definitions
M563 P0 D0 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
M92 E663:663 ; Set extruder steps per mm

; Z probe and compensation definition
M558 P5 R0.4 F1000 ;Z-probe Smart Effector
G31 P100 X0 Y0 Z-0.1 ;Z-Probe Smart Effector Probe threshold settings

;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here

M208 S1 Z-0.2 ; set minimum Z
M912 P0 S-1.1 ; adjust internal temperature sensor that was over reading by 1.1°C https://duet3d.com/wiki/Calibrating_the_CPU_temperature

T0 ; select first hot end
M307 H0 A645.6 C1147.3 D12.1 S1.00 B0 ; RGN PID Settings for Bed (from AutoTune)
M106 P2 H100:101 T20:35 L0.6 B0.2 ; RGN - for electronics cooling fan https://www.duet3d.com/forum/thread.php?pid=21953#p21953
M80 ; Turn on 24V & 12V PSU
[/c]

Is there something obvious I'm missing?

Thanks.

Richard

number40fan

What firmware version are you running?

Do you really have a 720mm diameter bed? If not, and it is the 360 you have in the M665, then that should be the radius.

M665 R246.6 L440.0 B360 H550 Should be 180 then,

dc42

My best guess is that the output of the effector is not connected to the Z probe input pin. Make sure you have the Out and Mod pins of the effector connected to the correct pins on the Z probe connector, and test the cable with a multimeter in case you have a bad crimp connection.

RGN01

Thanks, David, for picking up the diameter error - this is my first delta after a fair bit of experience with a cartesian and I'm finding it a steep learning curve.

Would the fact that the web interface is reporting 1000 when I tap the nozzle, or drop it carefully onto the bed, not mean that the cable is correct?

RGN01

Sorry, I missed the firmware question - M115 reports FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.19 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-08-14

MoS-tekknix

Do you have deployprobe.g and/or retractprobe.g Files in your /sys - Folder?

number40fan

What does the web interface show for Z height when you have the nozzle just touching the bed?

Good call on the deploy and retract files too.

MoS-tekknix

@number40fan:

…

Good call on the deploy and retract files too.

Thanks, i've trapped into the same issue after i'v exchanged BLTouch against Davids IR-Probe

RGN01

@MoS-tekknix:

Do you have deployprobe.g and/or retractprobe.g Files in your /sys - Folder?

Yes, I had those - I guess from the default SD install. I renamed both with a 'old_' prefix but now when I do a G30 the printer seems to freeze and the web interface says 'Busy'

Should I have left them in place?

MoS-tekknix

Did you check the Connections and proofed if you have bad crimped connections as David suggests?

number40fan

Delete those folders.

RGN01

@MoS-tekknix:

Did you check the Connections and proofed if you have bad crimped connections as David suggests?

I checked them with a multimeter when I installed the cable - it was OK. I'll check again. Thanks.

RGN01

@number40fan:

Delete those folders.

Do you mean files, please?

number40fan

Yes, the deploy and retract files. Delete them completely.

RGN01

@number40fan:

Yes, the deploy and retract files. Delete them completely.

OK, I've done that, they are deleted.

I've also homed the printer and slowly dropped the nozzle until it just touches the bed. The Z-height readings were:
Homed: 645.0
Touching bed: 212.5

And as it touched the bed the Z-probe field went pink and read 1,000 from the normal 0 for a split second.

Going to power it down and check the cable as suggested.

Thanks for the help, I appreciate it!

number40fan

Change the H numbers in M665 to 433. That'll fix the issue.

RGN01

Cable is good, no bad crimps and no crossed wires - they are in the same order on both ends.

number40fan

What type of motors, pulleys and belts are you running? Reason I ask is your M92 numbers are goofy.

RGN01

@number40fan:

What type of motors, pulleys and belts are you running? Reason I ask is your M92 numbers are goofy.

Motors are 17HM19-2004S, pulleys 16-tooth GT2, belt GT2

number40fan

Thanks. You're ok then. Just looked off to me having only ran 20 toothed pulleys.