Tach output and tool board help.

DIY-O-Sphere

@kordris said in Tach output and tool board help.:

out2.tach"

50.out2.tach?

dc42

@kordris that configuration looks OK to me if your tool board is at address 50. I use this config on my tool changer and I get the RPM readings:

M950 F5 C"22.out2+out2.tach" 			; Tool 2 hot end fan with tacho
M950 F7 C"23.out2+out2.tach" 			; Tool 3 hot end fan with tacho
M106 P5 S255 H3 T50 					; Tool 2 hot end
M106 P7 S255 H4 T50 					; Tool 3 hot end

One of the fans is a Noctua 3-pin fan. The S255 parameters could equally well be S1.

Which firmware versions are you running on the main board and the tool board?

DIY-O-Sphere

@dc42
I now interpret this to mean that the tach CAN address is hard coded in relation to the CAN fan output?

dc42

@diy-o-sphere said in Tach output and tool board help.:

@dc42
I now interpret this to mean that the tach CAN address is hard coded in relation to the CAN fan output?

More or less. It means that the "50:" prefix applies to the remainder of the port names string. Both ports have to be on the same board.

DIY-O-Sphere

@dc42
Now I have found it https://duet3d.dozuki.com/Wiki/Gcode#Section_M950_Create_heater_fan_spindle_or_GPIO_servo_pin
Learned someting new....

kordris

@dc42 Im running the last version on the tool board and latest firmware on the board. I updated the tool board last week.

dc42

@kordris does it make any different if you remove the Q500 parameters? I only mention this because a Q500 parameter caused an unrelated fan issue for another user recently.

kordris

@dc42 No that was first thing I tried. But I will try that again see if it helps or not. I even tried to add the ! which only made it come on when it wasnt supposed and go off when I wanted it on. That was just to invert so not helpful. Not sure what else I could do. Could try to redo the wire.

dc42

@kordris to test the tacho input, you could disconnect the fan and connect a push button between the tacho input pin and the ground pin. Configure the fan as normal, then if you push and release the button rapidly (e.g. twice a second), you should get a RPM reading. The reading will be zero if you don't push and release the button for 3 seconds.

kordris

@dc42 Ok I tried to removed the Q500 and didn't make any difference going to try the other thing you suggested but I got to make some prints first. Im working on my other Duet 3 and got the new tool board. I made a comment asking if you should connect the two outer wires on the 4 wire harness. When you connect the onboard resistor. Im not getting any response from the board in the dashboard right now. So not sure whats going on. Using the same cable I did for my other board and it worked fine. So its not the cable. I guess I could try to touch up the solder spot to make sure. But Im not getting thing from the board and the red light is blinking fast.

kordris

sorry dc I got the other duet 3 figured out. soldered wrong wire.. must of been really tired. Also the fan rpm line works on my other duet so.. It must be either the wiring going to the fan. I also have a connection that could be bad or bad crimp. So i need to check those. I know the line in the config is good. Because it works on my other duet.

dc42

@kordris use the wiring shown here but omit the resistor because it's already present. It doesn't actually matter which CANL pin you use on the tool board because both of them are connected in parallel. Similarly for CANH.

alt text

kordris

@dc42 Yea I got it fixed. I got the two Wire on the internal pin on the cord swapped around. Been kinda working on this one on and off. Because my feet have been getting swollen alot so I can work on it alot. So i been trying to do what I can. I do a little here and there. I finally got it right and it worked right. I had to get the main board updated which was a pain because it was outdated and wouldn't update though sbc. So i had reset it and try to run the update on bosse on my laptop which still would see it. Finally got the pi to run bosse. Then i was able to run the updates on the tool board and everything. Also is the only way to use a runout sensor is on the toolboard that using the extruder. Is there going to be a update to allow you to run the runout sensor to the duet 3 board. I really don't need to know how much filament is going out. I just need to know when it runs out and stops the board etc.. The one Im using is the bigtree tech so its not small and would really fit good on my carriage.

dc42

@kordris said in Tach output and tool board help.:

Also is the only way to use a runout sensor is on the toolboard that using the extruder. Is there going to be a update to allow you to run the runout sensor to the duet 3 board.

I have added this to the firmware wish list.