I have a duet wifi on my cr10 running the latest fw 2.04rc1. When I'm on my first layer and I click z babystepping up 0.05mm it does nothing. I've changed it all the way up to 3mm and the nozzle doesn't move up at all. Is there a trick to this in the DWC? I see the command being sent in the gcode console but zero movement.

While the printer is idle, I click the babystepping and it responds instantly. I know it may have to finish a layer before processing the babystepping command but it never responds, layer after layer.

@Phaedrux
Yep.. I forgot to try that troubleshooting step before posting. I just made the assumption that the red lead on the fan would go to vfan and black lead would go to fan-.
After your response, I was like duh. went to test it on the always on port and it didn't work, swapped pins and it worked.

this thread can be closed and deleted from existence.

I have a cartesian printer setup with 2 z motors and a touch probe setup for homing, bed compensation and bed leveling.
From what I've read and how I have it set up, this is what happens when I start a print:

• Home XYZ with z being probed in the center of the bed
• probe left X/center Y then probe right side for bed leveling
• Home XYZ, again with z being probed in the center of the bed

I just want to confirm that I'm not homing twice for no reason but I feel like I followed all setup instructions properly so maybe it is necessary?
If it is necessary to home all twice to get the bed leveled, is it possible to just home all once when printing one after another?
Configs are below
Config.g

; Axis Limits
;M208 X0 Y0 Z-1 S1                                   ; set axis minima
;M208 X300 Y300 Z400 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                                ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
M574 Z1 S1 P"zstop"                                ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop

; Z-Probe

M558 P9 C"^zprobe.in" H5 F200 T3000 ;f50 original probe speed mm/min
G31 X-44 Y0 Z1.343 P15 
M557 X15:251 Y15:285 P12                           ; define mesh grid





; Tools
M563 P0 D0 H1 F1                                   ; 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
M501                                               ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0                                                 ; select first tool
M950 S0 C"exp.heater3" ; Duet 2 WiFi/Ethernet bltouch
M376 H8 ;bed taper compensation 20x max error of .391
;M572 D0 S0.3

homeall.g

; 
; called to home all axes
;

G91                    ; relative positioning
G1 H2 Z5 F6000         ; lift Z relative to current position
G1 H1 X-305 Y-305 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000     ; go back a few mm
G1 H1 X-305 Y-305 F360  ; move slowly to X and Y axis endstops once more (second pass)
;G1 H1 Z-405 F360   ; move Z down stopping at the endstop
G1 x150 y150 F6000
G30
G90                    ; absolute positioning

homez.g

G90
G1 x150 y150 F6000 ;G1 x150 y250 F6000
G30
G1 Z10 F6000

custom g-code from slicer at start of print

G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S{first_layer_temperature[0]} ; set final nozzle temp
M190 S{first_layer_bed_temperature[0]} ; wait for bed temp to stabilize
M109 S{first_layer_temperature[0]} ; wait for nozzle temp to stabilize
G32
M561 ; clear height map
G28 ; home xy
G29 S1

@Phaedrux
Yep.. I forgot to try that troubleshooting step before posting. I just made the assumption that the red lead on the fan would go to vfan and black lead would go to fan-.
After your response, I was like duh. went to test it on the always on port and it didn't work, swapped pins and it worked.

this thread can be closed and deleted from existence.

I sincerely apologize in advance for this stupid question but I cannot seem to get my print cooling fan set up.

When I repurposed my 3d printer for production work I was printing with PETG and didn't need a cooling fan anymore so I took it out. Now it is being repurposed for general use and cannot get it to operate anymore.
I previously had a fan on fan0 pins to cool the drivers and an led strip on fan2 pins. I added a print cooling fan to fan1 pins and adjusted the config accordingly.
The fan0 is(or was) set to turn on when the mcu temp got to 45C. I haven't noticed it spinning up anymore.
In DWC, I see "tool fan", "fan 1", and "fan 2" listed on the status window. I can turn on the led strip but moving "tool fan" or "fan 1" slider does nothing except the sliders move together. I think they move together because I assigned fan 1 to the tool.

Is there something that I'm missing here?

; Fans
M950 F0 C"fan0" Q250                    
;M106 P0 S0 H-1                                   
M950 F1 C"fan1" Q250                  
M106 P1 S0 H-1                            
M950 F2 C"fan2" Q500                             
M106 P2 S0 H-1                              
M308 S4 Y"mcu-temp" A"MCU"   ; configure sensor  as thermistor on pin e1temp for left stepper
M106 P0 H4 L0.0 X1 B0.5 T45:55      ; set fan 0 value, turn on at 50% if the CPU temperature reaches 45C, and increase to full speed gradually as the temperature rises to 55C

; Tools
M563 P0 D0 H1 F1                                   ; 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

new duet2 wifi board did the trick. no issues so far.

@dc42 nice. I already ordered a new one from filastruder last night. I've got orders to fill! I'll still order the mcu and save it as a spare.

I wonder if the 74hc125 getting warm is the cause of my z steppers stalling...
man, I wish I had gone into computer engineering.

@gixxerfast haha. I'm in the US. I've repaired some flight controllers in the past so I think I can do the SMD replacement. Just need the chip.

@dc42 said in Duet 2 wifi, Bltouch won't deploy anymore:

@skhotso the component next to the USB port getting hot looks to be the diode that feeds USB power to the board. It will be hot if you are providing 5V power through the USB port and something either on or off the board is drawing excessive 5V power. That could be the microcontroller, or possibly the BLTouch is drawing solenoid current continuously (normally it activates the solenoid only briefly).

Nothing was plugged into the board at the time I was viewing the heatmap. Likely just the mcu then.

If the MCU is hot, that normally means that the MCU had been damaged and part of it is not functional. It might perhaps be the part that drives the BLTouch servo pin.

got it. looks like no one will have the mcu in stock until december of 2022! yikes.

The 74HC125 chip drives the stepper driver SPI pins and the DIAG LED. It should not normally run warm.
the diag LED flashes for a quick second when turning on but it's normally off. and the steppers all work fine so i'm wondering if that's even bad at all.

Anyone got a spare ATSAM4E8EA-AU lying around?

@phaedrux
I didn't time it but it did seem like it was taking longer than usual.

There aren't any silkscreened labels around the the IC other than for the adjacent components.
It is this ic with the hc125 part number on it. It's not burning hot, just warm. The MCU is burning hot though.

No potholes or visibly damaged components.

The funny(maybe not) thing is everything seems to work fine except for the bltouch deploying. I can home all, jog, start a print, update firmware through dwc, etc.
Dwc says MCU was up to 100c while flashing firmware. I had a little fan on it in case, it likely would have went even higher without.

just thought of another detail that may be relevant.
The night before I had this failure, I was attempting to autotune the heatbed pids. It ran for over 20 minutes with no results so I hit the emergency stop button and kept my old pid settings.

@phaedrux
Just went through the "unresponsive" troubleshooting steps and everything is good from leds to usb port recognition.
The 5v led was dimmer than the 3.3v led but I would think it's due to the usb port of my laptop, and not a real issue.

I felt around for other hot components and found this one chip was mildly warm. Red arrow on right.
I used my flir infrared cam on it and found a component(capacitor or resistor?) next to the usb port was heating up.

I'm not sure what that chip does or if it's normal for it to heat up.

The only thing I can think of that touched shorted the 5v or 3v rails is the bltouch connector but I hadn't touched that area before the BLtouch deployment issue.

one possibility is the bltouch shorting internally but seems like it'd be a rare case.

Anyone care to chime in on what that IC does and if possible to just remove it for testing purposes or permanently?!