3DTouch configuration not working

Nemesis1782

Erm. Yeah you're right no idea how I missed that... I fixed that right away. However it still does not work. Tomorrow I'll double check everything and report back!

The M98 is handy thnx did not know that existed.

Firmware reports: FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.01-RC4 ELECTRONICS: Duet WiFi 1.02 or later + DueX2 FIRMWARE_DATE: 2020-03-16b1

The config for Bedlevel is now:
; Z-Probe
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid

The M98 reported, heater warnings are as expected since I have not configured my tools yet:
6/18/2020, 8:33:16 PM M98 PCONFIG.G
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
6/18/2020, 8:33:16 PM Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.

Warning: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 973C.

Error: Heater 2 not found
Error: Heater 3 not found
Error: Heater 4 not found
Error: Heater 5 not found
Error: Heater 6 not found
Error: Heater 7 not found

Phaedrux

@Nemesis1782 said in 3DTouch configuration not working:

FIRMWARE_VERSION: 3.01-RC4

Please update to 3.1.1

Nemesis1782

@Phaedrux updated a quick test still gets me the same result. I'll double check everything later today.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later + DueX2 FIRMWARE_DATE: 2020-05-19b2

Edit: the Z probe now shows in the web interface though
Edit2: I found a M307 for Heater 7 (PWM 5) in the config-override.g, however I do remember reading the Duet holding on to old config. How do I make sure the duet forgets about the old config?

Phaedrux

Please post your current config.g, config-override.g, deployprobe.g, retractprobe.g, and homeall.g/homez.g

Are you still plugging into the Duex? Which port again?

Nemesis1782

@Phaedrux Hi Phaedrux, thnx for your time as always.

Yes I am using the Duex2 port pmw5. I have only included the homez.g, homeall.g is not right. Do keep in mind that I am not homing I'm just trying to get the probe itself to move. Onze that works the rest should not be a problem.

Config.g:
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 09 2020 12:23:53 GMT+0200 (Midden-Europese zomertijd)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"3DavII" ; 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 S0 ; disable Telnet

; Drives
M569 P2 S0 ; physical drive 2(X) goes backwards
M569 P1 S0 ; physical drive 1(Y) goes backwards
M569 P0 S0 ; physical drive 0 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M569 P4 S0 ; physical drive 4 goes forwards
;M584 X2 Y1 Z0:3:4 U3 V4 P3 ; Set the drive mapping, the Duet drivers are numberred (Z)2,(Y)1,(X)0,(E1)3,(E2)4
M584 X2 Y1 Z0:3:4 ; Set the drive mapping, the Duet drivers are numberred (Z)2,(Y)1,(X)0,(E1)3,(E2)4
M350 X16 Y16 Z16:16:16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1280.00:1280.00:1280.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00:12.00:12.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z1800.00:1800.00:1800.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00:20.00:20.00 ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z1700:1700:1700 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 X575 Y560 Z580 S0 ; set axis maxima

; Endstops
M574 X0 S1 P"zstop" ; configure active-low endstop for low end on X via pin !zstop
M574 Y0 S1 P"ystop" ; configure active-low endstop for low end on Y via pin !ystop
M574 Z1 S1 P"!xstop+!e0stop+!e1stop" ; configure active-low endstop for low end on Z via pin !xstop

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

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
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
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

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

; 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

; Miscellaneous
M501 ; load saved parameters from non-volatile memory

Config-overide.g:
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B0
M307 H1 A948.0 C252.3 D6.0 S1.00 V12.2 B0
;M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
;M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
;M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
;M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
;M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
;M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0

Deployprobe.g:
M280 P7 S10 I1

Retractprobe.g:
M280 P7 S90 I1

Homez.g:
G91 ; relative positioning
G1 H1 Z6000 F1800 ; move Z down until the endstop is triggered
G92 Z580 ; set Z position to axis minimum (you may want to adjust this)

Nemesis1782

@Phaedrux I was checking the documentation and noticed that the duex2 under version 0.8b does not support PWM 4 and 5. How do I check which version the board is?

Edit: Just checked and it is version 0.8. I'll move it to PWM3 later today.

Nemesis1782

@Phaedrux Alright so I am doing something seriously wrong. It is not behaving as I expect.

I've moved the connector to Duex PWM3 and changed the config. When I start the printer the Touch goes into error blue on blinking red.

When I then plug the Touch back into PWM5 and start the printer it does the correct startup procedure even though the config is pointing to PWM3.

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

config-overide.g not changed.

Deploy and retract changed P7 to P5

Phaedrux

@Nemesis1782 said in 3DTouch configuration not working:

Deployprobe.g:
M280 P7 S10 I1
Retractprobe.g:
M280 P7 S90 I1

When using the Duex you must remove the I1 from those commands.
And when using RRF3 you must change the P number to match the index of the servo pin you created, so M950 S0 C"duex.pwm3" is servo #0, so your deploy and retract should be

Deployprobe.g:
M280 P0 S10

Retractprobe.g:
M280 P0 S90

Your home Z is using an endstop move, you'l need to change that to use G30 to use the probe.

Nemesis1782

@Phaedrux said in 3DTouch configuration not working:

M280

Ah Yeah. Saw it in the documentation. I just assumed that hadn't changed for RRF3. Thnx

@HomeZ, yeah that is by design. I have 3 independent Z axis drivers and first home it to the end stop to make sure it's straight after which I'll fine tune using the bed level sensor.

Nemesis1782

@Phaedrux Hi, I've resolved it. It turns out one of the wires on the connector wasn't making a connection

Sorry for wasting your time and thnx for your help and patience!

Edit: So I tried going back to PWM5 since that's the one I would like to use and that is indeed not working. (well only on startup for some reason). Not a big issue thouh. However I would've liked to have the bed level sensor plugged into the most left PWM.