noob help dule z setup

Mobietec

@droftarts ; config-override.g file generated in response to M500 at 2021-05-17 15:30
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.612 C635.254:635.254 D7.63 S1.00 V24.4 B0
M307 H1 R3.237 C65.602:65.602 D6.95 S1.00 V24.3 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00
M486 S-1

droftarts

@mobietec The values in your config_override.g are different from the ones in your config.g. Because you have M501 at the end of config.g, the ones in config_override.g are the ones being used.

config.g:

M307 H0 R0.612 C635.3 D7.63 S1.00 V24.4 ; disable bang-bang mode for the bed heater and set PWM limit
M307 H1 R3.222 C146.1 D6.93 S1.00 V24.3 ; disable bang-bang mode for heater and set PWM limit

config_override.g:

M307 H0 R0.612 C635.254:635.254 D7.63 S1.00 V24.4 B0
M307 H1 R3.237 C65.602:65.602 D6.95 S1.00 V24.3 B0

However, the ones in config_override.g look more correct to me; they have two values for the C parameter, which means they were done with the new tuning algorithm which adapts for the part cooling fan. The bed tuning looks the same between them, but the hot end differs a little.

Either leave it as it is, or comment out M501 in config.g and copy the M307 values from config_override.g to config.g.

Ian

droftarts

@mobietec said in noob help dule z setup:

problem with homing z z probe already trigered at start of probing move

BLTouch troubleshooting: https://duet3d.dozuki.com/Wiki/BLTouch_Troubleshooting

Normal operation is:

When the Duet is first powered up, the BLTouch should perform its self test, which is to light up with red light, and extend and retract pin twice. If this doesn't happen, +5V and GND are not connected correctly.
Send M280 P0 S10 to extend pin. If this doesn't work, check the wiring to the servo pin. Send M280 P0 S90 to retract the pin.
The sys/deployprobe.g file and the sys/retractprobe.g file should contain the above two commands, one command in each file. Send M401 to extend the pin. If this doesn't work, check your sys/deployprobe.g file contains M280 P0 S10. Send M402 to retract the probe, and if this doesn't work, check sys/retractprobe.g contains M280 P0 S90.
With the probe retracted, check in DWC the Z-probe value in the Status panel. It should be 0. If it is 1000, check the probe trigger wire (usually white) is connected to the correct input pin.
Send M401 to extend the pin. VERY lightly, touch the end. The Z-probe reading should go from 0 to 1000. If it goes from 1000 to 0, you need to invert the probe. If it doesn't change, check the wiring again.
If doing the above triggers the alarm (flashing red), send M280 P0 S160 to release alarm and retract probe.

As you're using a clone BLTouch, and there was another thread recently about clones not working properly (see https://forum.duet3d.com/topic/23218/strange-bltouch-behavior-after-update-to-3-3-0-b3), I expect it could be that the output is inverted, and it reads 1000 when not triggered, and 0 when triggered. If so, invert the probe by changing your M558 line to:

M558 P9 C"!io7.in" H5 F120 T6000

Ian

Mobietec

@droftarts said in noob help dule z setup:

M280 P0 S160

i have just ordered proper bltouch will connect it tommrow and go from their also instaling the end stops if you coudld help in the code for this ill add it in would you like the code i have right now many thanks

droftarts

@mobietec I have mine set like this:

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z0             ; configure Z-probe endstop for low end on Z

I am using the X and Y endstops, BLTouch on Z. The only physical change is that I have wired them using the outer two pins (of three) on each microswitch, for NC (normally closed, or active high) operation, which is more reliable. I think you won't need to change your homing files much, except comment out any lines related to sensorless homing. See https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Microswitch

If you want to post your current config.g for reference (or maybe after you have made the changed to endstops), please do. It would be good if you could use the 'code' tags around long bits of code, like the endstop code in the black box in this post, to make it easier to read. Click the '</>' icon at the top of the post edit window to insert these tags, and paste the code in between.

Ian

Mobietec

ok for the next bit nd thank you so much for all your help im slowley learning this i think i need to set the off set propley of the bl touch i have gourn back to clone it seems to be working

when i home the z it works so to speek i need to set the bltouch i di put a -37.6 and a 37.6 with no luck the proble is off the bed the nozzle is correct front left ie nearest to you on left

1 i think i need to set home 0 to center trying to look ant fined out how and tryng to do off set

somtimes i think i bit off more that i can chue with duet3 board its very compleacted for me but the end rerult should be good many thakns

Phaedrux

The G30 will just start probing at whatever XY position it's currently at, so you'll need to manually position the probe in the homeall.g and homez.g files so that the probe is where you want it to be before the G30.

G1 X150 Y150 F6000
G30

Mobietec

This post is deleted!

Mobietec

@phaedrux
@phaedrux my updated config file
i cant get the bltouch to deply now grrr i am trying to look for answers befor i post first i have the bl on io3 now their are two grounds form touch that are wired together sence on io out and triger on ioin

i have checked for contunety lol i cant spell today and i have also tried 3.3 and 5v lines and i have tried diffrent probs still get same

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed May 19 2021 20:59:11 GMT+0100 (British Summer Time)

; General preferences
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Raptor CoreXY" ; set printer name
M669 K1 ; select CoreXY mode

; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable 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 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S0 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3:0.4 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E440.00:400.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00:60.00
M584 X0 Y1 Z2:4 E3 ; two Z motors connected to driver outputs Z and E1 ; set maximum instantaneous speed changes (mm/min)
;M671 X-20:220 Y0:0 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
;M208 X-5:205 Y0:200 ; X carriage moves from -5 to 205, Y bed goes from 0 to 200
M203 X6000.00 Y6000.00 Z180.00 E1200.00:180.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-165 Y-165 Z0 S1 ; set axis minima
M208 X165 Y165 Z400 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S2 C"io4.in" ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io4.out" ; create servo pin 0 for BLTouch
M558 P9 C"io4.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-30 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X-155:130 Y-155:155 P5 ; define mesh grid

;M558 A10 S0.003 B0 R0.2 ; BLTouch extra settings from Phaedrux
G31 P500 X-37.6 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X-155:130 Y-155:155 P5 ; 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 R0.612 C635.3 D7.63 S1.00 V24.4 ; disable 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 B4138 ; 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 R3.322 C149.5 D6.72 S1.00 V24.3 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out6" Q500 ; create fan 2 on pin out6 and set its frequency
M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on
M950 F3 C"out7" Q500 ; create fan 3 on pin out7 and set its frequency
M106 P3 S1 H1 T45 ; set fan 3 value. Thermostatic control is turned on
M950 F4 C"out8" Q500 ; create fan 4 on pin out8 and set its frequency
M106 P4 S1 H1 T45 ; set fan 4 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
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Phaedrux

Does M401 and M402 work?
Does M280 P0 S10 or M280 P0 S90 work?
What do you have in your deploy and retract macros?
Are those deploy and retract macros located in your /sys/ folder?

Mobietec

@phaedrux no im trying a clean install see if that helps

Mobietec

@phaedrux said in noob help dule z setup:

Does M401 and M402 work?
Does M280 P0 S10 or M280 P0 S90 work?
What do you have in your deploy and retract macros?
Are those deploy and retract macros located in your /sys/ folder?

no
no
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu May 20 2021 20:02:55 GMT+0100 (British Summer Time)
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu May 20 2021 20:02:55 GMT+0100 (British Summer Time)
M280 P0 S90 ; retract BLTouch

yes

Phaedrux

99.9% of the time it's wiring.

Mobietec

@phaedrux i fully understand that i have checked and rechecked im using duet 3

bl conected to io3

5volt to 5volt in bl
io out to sig
both grounds from bl to gnd
and out(z) to io3 in

rom socket to bl no broken conections and correct readings ie cable conected ok

hope this helps

Phaedrux

@mobietec said in noob help dule z setup:

M950 S0 C"io4.out" ; create servo pin 0 for BLTouch
M558 P9 C"io4.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds

@mobietec said in noob help dule z setup:

bl conected to io3
5volt to 5volt in bl
io out to sig
both grounds from bl to gnd
and out(z) to io3 in

Are you using io3 or io4?

Mobietec

@phaedrux io3

Phaedrux

@mobietec said in noob help dule z setup:

M950 S0 C"io4.out" ; create servo pin 0 for BLTouch
M558 P9 C"io4.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds

If you are connected to io3.... and your config is using io4....

Mobietec

@phaedrux i changed it just in case that was a problem port made no diffreance im pulling my hair out i have tested both bl in a marlin boards and work as they should just will not work in here

i have also reflashed board to 3.2 no luck i was on 3.3 so im going to put that back on

Phaedrux

Ok, so your config is using io3 now as well?

when you tested on the marlin boards did you use the same cable harness?

Can you show a photo of your BLtouch connection at the duet board io3 connection?

Mobietec

@phaedrux yes same harness i have to change pins over so 5v n sig were correct