noob help dule z setup

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

Mobietec

This post is deleted!

Mobietec

This post is deleted!

Mobietec

@mobietec alt text

links to photos i hope

droftarts

@mobietec Yellow pin crimp looks like it's up, not in the crimp shell properly. May not be making contact. Better to use the supplied Duet crimps and housings, rather than ~~Molex~~ Dupont connectors.

Ian

Mobietec

@droftarts i can promice you its making good contection the dupont socket is just temp and i did push it down fully after pic and check it still not working i do have another bl with duet socket still same problem

droftarts

@mobietec Sorry, should have remembered this before; see https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_Num_3

Connect the BLTouch to IO_7 ... It's also possible to use IO_4 or IO_5 instead of IO_7.

(Edit: I've updated the text on the wiki to make it clearer.)

You can't use IO_3!

Only IO_4, IO_5 and IO_7 are PWM capable, so able to control a servo (like the BLTouch). See table here for IO pin capability: https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_IO.
Use one of IO_4, IO_5 or IO_7 instead. So, with the BLTouch connected to IO_4, your config.g should be (which is what you had earlier):

; 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

Also, this line is incorrect, and may be interfering:

 M574 Z2 S2 C"io4.in" ; configure Z-probe endstop for low end on Z

Are you wanting to use the endstop on the high end (as in where Z value is 'high', with the bed furthest from nozzle, so bed at the bottom of travel)? That's what 'Z2' means. Though 'S2' means probe not endstop, and the 'C' parameter is wrong (should be P). To set it up correctly, see https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_RepRapFirmware_Num_3. For now, change it to:

M574 Z0 ; No Z endstop

Make these changes, test and post your config.g.

Ian

Mobietec

yipeee got the bl working

now got to work on bedsize and bed mesh because it probs outside
of bed aeira

Phaedrux

@droftarts said in noob help dule z setup:

You can't use IO_3!

Oof! that was on the tip of my brain yesterday.

Mobietec

@phaedrux yep duet well my board only bl on duet 3 io7 will not work on any others strange
i can now prob bed do a mesh level etc

now for next problem

need to figer out how to dule z level

Mobietec

@mobietec Thank you every one who is trying to help me

droftarts

@mobietec said in noob help dule z setup:

need to figer out how to dule z level

See https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

Ian

Mobietec

@droftarts thank you i was thnking do i need to probe more than once im ow using a gen bltouch or is just 1 prob enoth many thanks

droftarts

@mobietec generally you home all axes, which probes be centre, then probe as near as you can to each leadscrew, one probe per leadscrew.

Ian

Mobietec

@droftarts thank you ian so once is enoth i know when i did it in marlin it did it a few times till it was spot on

new error message now regarding mesh error invlaid higt map
my bed is 330 x 330

i have set center to 0

M557 X-135:135 Y-135:135 P5 is what i have at present

Mobietec

@mobietec fixed that updated the web and that fixed that problem many thanks

Mobietec

@mobietec where can i see the log reports please if this has any after the dual z i get bad command in config file any idears

droftarts

@mobietec This is my bed levelling macro:

; Two point bed levelling, automatic leadscrew adjustment

M561                                 ; clear any bed transform
G29 S2                               ; disable compensation
G28                                  ; home all axes
M671 X255:-255 Y0:0 S5               ; leadscrews at right (255,0) and left (-255,0)
G30 P0 X135 Y-145 Z-99999            ; probe near right front adjusting screw
G30 P1 X-145 Y-145 Z-99999 S2        ; probe near left front adjusting screw and report adjustments needed
G1 X0 Y0 F6000

I also have a macro for manually levelling the bed; I have just three of the adjustable screws, not all six:

; Three point bed levelling

M561                                 ; clear any bed transform
G29 S2                               ; disable compensation
G28                                  ; home all axes
M671 X160:-160:0 Y-160:-160:160 P0.5 ; adjusting screws at front right (160,-160) and front left (-160,-160), rear centre (0,160) thread pitch M3 0.5mm
G30 P0 X135 Y-145 Z-99999            ; probe near an adjusting screw
G30 P1 X-145 Y-145 Z-99999           ; probe near an adjusting screw
G30 P2 X0 Y145 Z-99999 S3            ; probe near an adjusting screw and report adjustments needed
G1 X0 Y0 F6000

These rely on a number of settings in config.g, particularly M208 bed size and G31 probe X Y offset:

; Dual Z
M584 X0 Y1 Z2:3 E4                                 ; Set drive mapping - 2 Z right, 3 Z left
...
; Axis Limits
M208 X-165 Y-165 Z0 S1                         ; set axis minima
M208 X165 Y165 Z400 S0                         ; set axis maxima
...
; Z-Probe
M950 S0 C"exp.heater3"                         ; 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
M558 A10 S0.003 B0 R0.2                        ; BLTouch extra settings from Phaedrux
G31 P500 X-30 Y0 Z1.65                            ; set Z probe trigger value, offset and trigger height
M557 X-145:135 Y-145:145 P5                   ; define mesh grid

Hope that helps.

Ian

droftarts

@mobietec said in noob help dule z setup:

@mobietec where can i see the log reports please if this has any after the dual z i get bad command in config file any idears

In config.g? Send M98 P"config.g" to run config.g, and it will report errors in the console. Post config.g and error reported if you can't find it.

Ian