Tool board configuration

Danal

This works for me, my tool board is CAN 22. I also have tools on a 3HC at CAN 1.

; Temperature sensors
M308 S0 P"0.temp0" Y"thermistor" T100000 B3950 A"Bed" 
M308 S1 P"1.temp0" Y"thermistor" T100000 B3950 A"HE1"
M308 S2 P"1.temp1" Y"thermistor" T100000 B3950 A"HE2"
M308 S3 P"22.temp0" Y"thermistor" T100000 B3950 A"HE3"
;M308 S4 P"23.temp0" Y"thermistor" T100000 B3950 A"HE4"

; Heaters
M950 H0 C"0.out0" T0           ; Bed.  H = Heater 0, C is output for heater itself, T = Temperature sensor (defined above)
M950 H1 C"1.out0" T1           ; Heater for extruder out tool 0
M950 H2 C"1.out1" T2           ; Heater for extruder out tool 1
M950 H3 C"22.out0" T3           ; Heater for extruder out tool 2
;M950 H4 C"23.out0" T4           ; Heater for extruder out tool 3

; Further setup for bed
M143 H0 S130                                           ; set temperature limit for heater 0 to 130C
M307 H0 B0 S1.00                                       ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0

; Default heater model
;;;;M307 H0 A270.7 C90.4 D6.7 B0 S1.0          ; Default Bed Heater Parameters, before tuning / if config-override.g is missing
; Calibration 28 Oct 2019
;Heater 0 model: gain 139.6, time constant 252.2, dead time 0.7, max PWM 1.00, calibration voltage 24.5, mode PID
;Computed PID parameters for setpoint change: P468.8, I35.594,  D225.7
;Computed PID parameters for     load change: P468.8, I136.631, D225.7
M307 H0 A140 C252 D0.7 S1.0 V24.5 B0       ; Tuned Bed Heater Paramaters, same as report above, also B0 to turn off bang-bang

; Fans for hot end cooling
M950 F1 C"1.out6"
M106 P1 S255 H1 T45    ; S = Speed of fan Px, Hxx = heater for thermo mode, T = temps for thermo mode.
M950 F2 C"1.out7"
M106 P2 S255 H2 T45    ; S = Speed of fan Px, Hxx = heater for thermo mode, T = temps for thermo mode.
M950 F3 C"22.out1"
M106 P3 S255 H3 T45    ; S = Speed of fan Px, Hxx = heater for thermo mode, T = temps for thermo mode.
;M950 F4 C"23.out1"
;M106 P4 S255 H4 T45    ; S = Speed of fan Px, Hxx = heater for thermo mode, T = temps for thermo mode.

; Fans for print cooling
M950 F5 C"1.out3" 
M106 P5 C"PrintCool5"
M950 F6 C"1.out4" 
M106 P6 C"PrintCool6"
M950 F7 C"22.out2" 
M106 P7 C"PrintCool7"
;M950 F8 C"23.out2" 
;M106 P8 C"PrintCool8"

; Tool definitions
M563 P0 S"Tool 0" D0 H1 F5      ; Px = Tool number, Dx = Drive Number (start at 0, after movement drives), H1 = Heater Number, Fx = Fan number print cooling fan
G10  P0 S0 R0                   ; Set tool 0 operating and standby temperatures(-273 = "off")
;M572 D0 S0.1  		            ; Set pressure advance on 

M563 P1 S"Tool 1" D1 H2 F6      ; Px = Tool number, Dx = Drive Number (start at 0, after movement drives), H1 = Heater Number, Fx = Fan number print cooling fan
G10  P1 S0 R0                   ; Set tool 0 operating and standby temperatures(-273 = "off")
;M572 D1 S0.1		            ; Set pressure advance on 

M563 P2 S"Tool 2" D2 H3 F7      ; Px = Tool number, Dx = Drive Number (start at 0, after movement drives), H1 = Heater Number, Fx = Fan number print cooling fan
G10  P2 S0 R0                   ; Set tool 0 operating and standby temperatures(-273 = "off")
;M572 D2 S0.1		            ; Set pressure advance on

;M563 P3 S"Tool 3" D3 H4 F8      ; Px = Tool number, Dx = Drive Number (start at 0, after movement drives), H1 = Heater Number, Fx = Fan number print cooling fan
;G10  P3 S0 R0                   ; Set tool 0 operating and standby temperatures(-273 = "off")
;;M572 D3 S0.1		            ; Set pressure advance on

dc42

Please try the following:

Check whether the config settings have been applied, by sending M308 S1 and M950 H1 and checking the response.
Run M98 P"config.g" and see if any errors are reported.

@madmattco said in Tool board configuration:

Also, all firmwares are up to date.

Please specify the firmware versions. Your idea of up to fate might not be the same as ours!

madmattco

@dc42 I am using the firmware you posted the other day. https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC12

My problem ended up being the wrong temp sensor connector.

alt text

I was also wondering if everything is in place to have a bl-touch running off of the IO_0 port on the tool board.

dc42

@madmattco said in Tool board configuration:

My problem ended up being the wrong temp sensor connector.

I'm glad you solved it.

I was also wondering if everything is in place to have a bl-touch running off of the IO_0 port on the tool board.

Yes.

madmattco

@dc42 Cheers

madmattco

@Danal You wouldnt happen to have a bl-touch on your toolboard would you?

Danal

@madmattco said in Tool board configuration:

@Danal You wouldnt happen to have a bl-touch on your toolboard would you?

Not on the toolboard. I do have a BLt, it is on io4 on the mainboard.

Here is the setup. Unless the firmware does/doesn't support something, I don't see why this couldn't be xx.io0.in (and out) on a toolboard.

M558 K0 P9 C"^io4.in" H9 A5 T6000 S0.02   ; Z probe BLtouch - Set the height of the bed when homing G28.  Combined with content of bed.g as invoked by G32, levels bed. Also used for Mesh.  
					                        ; Hn = dive height
				                            ;   A bigger dive height prevents a situation where the bed is out of alignment by more than the dive height
                                            ;   on any corner, which can crash the hot-end into the bed while moving the head in XY.
                                            ;   Probing speed and travel speed are similarly reduced in case the Z probe isn't connected properly (or
                                            ;   disconnects later after moving to a point) giving the user more time to stop.
                                            ; An = Number of times to probe each point. 
                                            ; Tnnn = Travel speed between probe points. 
                                            ; Snnn = Tolerance when probing multiple times. Two readings inside this window and we move on. 
G31 K0 X28.1 Y-27.5 Z0                          ; Probe offsets

M950 S0 C"^io4.out"                       ; Servo Control Pin for BLtouch.

madmattco

@Danal That worked for me sir. Cheers

Nuramori

I have a BLTouch on my toolboard, if you need some help.

dintid

@Nuramori Care to share your BLTouch config on Toolboard? I've tried setting it up using the RRF configurator, but I can't pick ioO.out as PWM for BLTouch, when also using Out 0 for heater.. don't know if there is a shared PWM (hope not) or just bad RRF configurator?

Nuramori

@dintid

I’m happy to, but I won’t be able to get to it until I’m back from vacation. Sunday is the likely opportunity.

dintid

@Nuramori I got it working.. sort of. !! (Original BLTouch v3.1 on Toolboard v1) All newest firmware (non-rc).

It does not selftest on power on of machine.
If I unplug BLTouch, power machine on, and plug in BLTouch after machine has started it does self test.
I've done a lot of continuity tests, and all wires are connectors are good all around.
I've measured on the connectors on Toolboard which reads 5v.. but when connecting BLTouch it briefly drops below 3v, so my issues might be some voltage drop?
Once the machine is ready I can run a long self test. It will however blink red afterwards, and I can't do a new self test.
The "reset warning and retract probe" does not work in this case.. but if I deploy and retract it stops blinking and I can do a new self test, and it starts over.
I can get it to use the "reset warning SW mode".. but can't do anything afterwards.
Z probe reads as 0. When I deploy and manually trigger it, it reads 1000 as it should
I noticed it is VERY weak, compared to other machine's BLTouch (maybe voltage issue?)
I've considered issuing the EEProm command to put it into 5v state, but I'm unsure wheter I risk burning something?

Sidenote: I'm using a Quality Meanwell HRP psu. I measure output Volt at 24.2 at PSU and on Duet3 terminals,, while Duet3 reports it at 23.7v. Always... I find this somewhat.. odd? Using a decent quality Multiemter.

dc42

@dintid said in Tool board configuration:

I've measured on the connectors on Toolboard which reads 5v.. but when connecting BLTouch it briefly drops below 3v, so my issues might be some voltage drop?

You could try adding a 100uF capacitor between the BLTouch +5V and ground connections.

Sidenote: I'm using a Quality Meanwell HRP psu. I measure output Volt at 24.2 at PSU and on Duet3 terminals,, while Duet3 reports it at 23.7v. Always... I find this somewhat.. odd? Using a decent quality Multiemter.

The Duet uses its 3.3V regulator as the voltage reference, so it can be few percent inaccurate. Your multimeter is probably more accurate.

Nuramori

Out of curiosity, do you have a terminating resistor on your can-fd line?

dintid

@Nuramori I don't know what that means? I have the requisite jumpers on my Distribution board.

dintid

@dc42 I only had a 35v 470uf. It didn't make a difference.
In your documentation you write that Orange i control wire.. but it's really yellow though?
https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Connecting_a_BL_Touch

dc42

@dintid said in Tool board configuration:

In your documentation you write that Orange i control wire.. but it's really yellow though?

It depends on your colour vision and how you assign colours. I see it as orange.

dintid

@dc42 I'm colorblind but asked my two girls who aren't
Any ideas to steps I can try to make BLTouch work on the Toolboard? I havn't had time to try it on the mainboard yet.

dc42

@dintid said in Tool board configuration:

@dc42 I'm colorblind but asked my two girls who aren't
Any ideas to steps I can try to make BLTouch work on the Toolboard? I havn't had time to try it on the mainboard yet.

It's odd that it's not working, because BLTouch worked fine connected to the tool board when I took that photo. Are you certain that you have connected the wires correctly? The brown wire goes to ground (2nd terminal from the top) along with the black wire, which isn't clear in that photo.

dintid

Yea, I have it wired correctly. Might be faulty probe. It's rare but it happens.
I'm about to hook it up to Duet3 MB, and will report back