Posts made by TokeDK

@phaedrux Thanks for the help. I've ordered a new Duet board, can't live without it

@phaedrux So the board is likely dead?

@dc42 Yes the main processor gets quite hot (probably 50c within 30 seconds) while the other components stay cool.

While fixing something my hotend, the parts cooling fan wires came loose and shorted somehow, I saw a small spark for a millisecond and afterwards the board was unresponsive and never connected to WiFi again.

I've tried following the guide here ("What to do if your Duet won't respond")

The DIAG light is constantly on, so is 3.3v, 5v and the light between reset and USB. I've not been able to reset or erase the firmware following the guide and the port doesn't show up on my MacBook (using SerialTools and Terminal).

I've completely disconnected the board from the 3D printer, checked the fuses and that the reset button isn't pressed in...

Is it dead? I read something about fixing a shorted fan somewhere on here?..

I did turn out to be a hot end short causing the weird errors. Closed.

@Phaedrux Uhm, do you mean phsyical screw terminal? In that case it is, and yes it is DC.

Apologies for dumb questions... Still learning

@Phaedrux Do you mean switching the "terminals" so E1 --> E0?

E0 (heated bed) works fine as far as I can tell although I had to do a PID autotune after the suspected short, and the bed is heating slower than I remember.

I caused a heater cartridge short (I believe), I accidentally worn the wire insulation to the hot end down by overtightning the assembly.

I replaced a blown 7.5a fuse, insulated the wires with electrical tape as an attempt to revive it.

Now I'm having thermister faults...

I changed the thermister as I thought that was the issue, but I'm getting VSSA faults on both the bed and hotend, after the bed has warmed up and while the hotend is warming up?

I read that a heater cartridge short can cause VSSA fault, so should I assume that I need to replace the heater cartridge?

@Phaedrux
This video shows what I mean:
https://youtu.be/Dt5jatG5b4M

My config is:

; 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 H0:1 T45                                ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500                               ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H-1                                     ; set fan 2 value. Thermostatic control is turned off
 
; Tools
M563 P0 S"tool" D0 H1 F0:2                         ; 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

@Phaedrux
Altough now when I manually adjust the levels of the tool fan (fan1) all the other fans follow the same level... The only one that I can change independently is fan2??

@Phaedrux
Thanks. This is great, I didn't realize I'd have to configure a tool also.

Yes it was my intention to have 2 part cooling fans on 1 tool.

Your snippet helped me understand the configuration perfectly! Now I'm finally just about ready to do some test prints!

I'm having problems configuring my fans for my TeVo Little Monster.

I'm using a Duet 2 Wifi v.1.02 (or later) and firmware version 3.1.1.

My current wiring is like so:
Always on = board fan

fan0 = part cooling 1,
fan1 = hot end fan,
fan2 = part cooling 2

My config is:

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

With this configuration the fan0 (part cooling) and board fan is always on, but when I heat up the hotend nothing changes, and I can not control the fans either through commands or the interface.

I'm an absolute noob to configuration, hopefully some of you smart people can help, apologies.

Edit:
I'm sure the wiring is as stated, as I've tested pluging it in different ports.

Awesome, I set it up like you suggested and it works! So it is faulty wiring/connections. I will report back with my findings.

@Veti said in BLTouch not responding properly Duet 2 Wifi:

M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop

Perfect! Now endstops are working. Although Z probe is still giving the same error:

	Error: Z probe was not triggered during probing move

Now my endstops are not working... I tried to rebuild the config from the configurator with no succes.

First I got the error "failed to enable endstops", then I changed my config to:

; Endstops
M574 X2 S1 P"xstop"                                ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                                ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S2                                         ; configure Z-probe endstop for high end on Z

Now when it's homing the endstops doesn't work, so the stepper motors keep going...

@Veti

m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-01-03b3

I believe the BLTouch is SMART v.1.0

The previous owner sold it with the BLTouch now working. He said it was a firmware issue on the original board.

I got a spare BLTouch with the deal, and both are returning the same error.

The wires seem fine... Could it have something to do with the BLTouch 3.3v logic bridge (as shown here)
In the video he says to test it with a multimeter? Here I'm guessing you test the continuity? And it's suppose so show 0? On my multimeter it doesn't shows that there is continuity, and I'm sure the bridge is gone...

Well that's progress! Now it's working (kind off). It probes but returns;

4.10.2020 15.50.40	Error: Z probe was not triggered during probing move
4.10.2020 15.50.46	Error: Compensation or calibration cancelled due to probing errors
4.10.2020 15.50.34	Error: Z probe was not triggered during probing move
4.10.2020 15.50.28	Error: Z probe was not triggered during probing move
4.10.2020 15.50.22	Error: Z probe was not triggered during probing move
4.10.2020 15.50.16	Error: Z probe was not triggered during probing move
4.10.2020 15.50.10	Error: Z probe was not triggered during probing move
4.10.2020 15.50.04	Error: Z probe was not triggered during probing move
4.10.2020 15.49.57	Error: Z probe was not triggered during probing move
4.10.2020 15.49.51	Error: Z probe was not triggered during probing move
4.10.2020 15.49.44	Error: Z probe was not triggered during probing move
4.10.2020 15.49.38	Error: Z probe was not triggered during probing move