Smart Effector hotend fan and Lights

oryhara

A thermistor.

I checked and it actually was at 450C

I guess the hotend heater was turned on this whole time i've been trying to sort it out. or something.
I should have smelled it sooner.

oryhara

There is an error about heater 1 being overpowered. It came up when I did the PID tune.

oryhara

ok. I got most of it working. Fan 2 acts as Fan0(part cooling fan), and the bed and extruder heater operate as expected.
Except: G30 tries to do manual bed probing. I'm guessing that my Z-probe was not set up properly. Back to the config.g for me.

In case anyone is following:

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Tue Feb 26 2019 21:31:01 GMT+0000 (Greenwich Mean Time)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Delta Settings
M665 L440.440 R226.821 H420 B185.0 X0 y0 z0 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 y0 z0 A0.00 B0.00 ; Put your endstop adjustments here, or let auto calibration find them

; Network
M550 P"Predator" ; Set machine name
M551 P"" ; Set password
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards - extruder
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E415 ; Set steps per mm
M566 X3000 Y3000 Z3000 E3000 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z12000.00 E12000 ; Set maximum speeds (mm/min)
M201 X9000.00 Y9000.00 Z9000.00 E6000.00 ; Set accelerations (mm/s^2)
M906 X1800.00 Y1800.00 Z1800.00 E900.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Retraction
M207 S1.85 F7000 R0 T2500 Z0.5 ; Firmware retraction

; Axis Limits
M208 Z-1 S1 ; Set minimum Z

; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops

; Z-Probe
M558 P8 R0.4 F1200 H2 T5000 ; Set Z probe type to switch and the dive height + speeds
G31 P100 X0 Y0 Z-.1 ; Set Z probe trigger value, offset and trigger height
M557 R175 S20 ; Define mesh grid

; Heaters
M307 H0 A137.8 C533.3 D1.5 V24.3 B0 ; Disable bang-bang mode for the bed heater and set PWM limit
M308 S0 P"bedtemp" Y"thermistor" F0 T100000 B4300 C0 R2200 ; Set thermistor + ADC parameters for heater 0
M950 H0 C"bedheat" T0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M308 S1 P"e0_temp" Y"thermistor" F0 T100000 B4725 C7.06e-8 ; Set thermistor + ADC parameters for heater 1
M950 H1 C"e0heat" T1 ; Define Heater 1
M143 H1 S290 ; Set temperature limit for heater 1 to 240C
M307 H2 A-1 C-1 D-1 ; Disconnect H2 from being a heater - LED

; Fans
M950 F2 C"nil"
M950 F0 C"fan2" ;set fan B as fan 0
;M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 T30 H100:101:102 ;sets up an electronics cooling fan that starts to turn on when the MCU temperature (virtual heater 100) reaches 45C and reaches full speed when the MCU temperature reaches 65C or if any TMC2660 drivers (virtual heaters 101 and 102) report that they are over-temperature

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

; Automatic saving after power loss is not enabled

; Custom settings are not configured
M591 D0 P2 C4 S0 ; Activate filament sensor
M404 N1.75 ; Set for print monitor
M592 D0 A0.011806 B0.0026876 ; Nonlinear extrusion. Set parameters for extruder drive 0 - 0.4mm
M575 P1 B57600 S1

; Miscellaneous
M501 ; Load saved parameters from non-volatile memory

; This is a system-generated file - do not edit
; Delta parameters
M665 L440.440 R220.804 H410.714 B185.0 X-0.174 Y-0.027 Z0.000
M666 X-0.368 Y-0.441 Z0.809 A0.00 B0.00
; Heater model parameters
M307 H0 A137.8 C533.3 D1.5 S1.00 V24.3 B0
M307 H1 A799.6 C271.4 D4.4 S1.00 V24.0 B0
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

dc42

@oryhara said in Smart Effector hotend fan and Lights:

M558 P8 R0.4 F1200 H2 T5000 ; Set Z probe type to switch and the dive height + speeds

You haven't defined the Z probe input pin. See https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M558. For a Smart Effector on a Duet Maestro, use C"zprobe.in+zprobe.mod".

oryhara

yep. that did it. thank you.

oryhara

@dc42

regarding the fan mosfet, I reached out to filastruder(where I bought my maestro) about an RMA and they said that unless you or another duet admin authorizes the warranty repair, it's a no-go.

I have my fan2 workaround functioning, so just how "not ideal" is it to have the hotend fan always-on and the print fan running from Fan 2?

oryhara

so i'm getting warnings from my MCU that its at 46-47 degrees. I know 45 is the cutoff, but its holding stable just a few degrees above that.

I'm concerned that my fan A mosfet may be even less functional, since that is what is running the MCU fan.

Its on the Fan 1 output. I have it set to turn on if the MCU is above 30(despite the comments in my gcode above), and without the proportionaly control.
Is there a way to test the speed of a 2-wire fan?

or can i drive a fan from something else like one of the expansions slots or the second heater? E1, that is.

oryhara

At the risk of dredging up a dead thread, i want to give one last update.
I didn't calibrate the MCU temperature sensor, so i'm going to do that and it should fix the issue i mentioned in my previous post.

dc42

Re the blown fan MOSFET, it's likely that when the fan wire came loose from the connector, it shorted to something else, and that blew the MOSFET. I'm sorry, this sort of thing isn't covered by the warranty. However, Filastuder may be able to put you in touch with our stateside Duet repairer, if you haven't a local hackspace or makerspace where you can get it done. Or you could watch https://youtu.be/LADgxZgyJ04, practice on an old hard disk drive, and if that gives you enough confidence then do it yourself. If you can remove the blown MOSFET without lifting the traces, fitting the new one is easy.

Re CPU temperature, 45C is not unusual. The CPU will function up to at least 85C die temperature.

HTH David

oryhara

thank you. It's worth asking i suppose. I'll stick with the workaround I've found. I rather like the effector lights always on.

My MCU was reading 6 degrees too high, based on the 'calibrate MCU temp' procedure which I executed this morning. Given that it was hovering at 47 during a print before that calibration, it should stay well below the warning threshold now.

dc42

@oryhara said in Smart Effector hotend fan and Lights:

thank you. It's worth asking i suppose. I'll stick with the workaround I've found. I rather like the effector lights always on.

My MCU was reading 6 degrees too high, based on the 'calibrate MCU temp' procedure which I executed this morning. Given that it was hovering at 47 during a print before that calibration, it should stay well below the warning threshold now.

Is the warning coming from Duet Web Control, or somewhere else? 45C is too low for a MCU temperature warning threshold.

oryhara

It was high temperature on drivers. usually 0 and 1.
I see it in gcode console and a popup on web control and the panelDue.

I thought the warning started at 45 and then they stopped at 65, is that not correct?

dc42

@oryhara said in Smart Effector hotend fan and Lights:

It was high temperature on drivers. usually 0 and 1.
I see it in gcode console and a popup on web control and the panelDue.

I thought the warning started at 45 and then they stopped at 65, is that not correct?

The drivers warn of over temperature when their temperatures exceed about 100C according to the on-chip sensor. That warning is not related to MCU temperature, except that when the drivers are generating a lot of heat, some of this will feed through to the MCU.

oryhara

I can probably afford to turn down the current.
But with a fan blowing across the back of the board, should they really be getting that hot?

I wonder if there is some other problem.

droftarts

I was doing some testing of the latest firmware (2.0.5RC2) this week, and set up my Maestro with 4x chunky NEMA17 motors, on drives 0, 1, 2 and 3, set stepper current to 1.6A, set to spreadcycle (runs hotter) and 100% idle hold. I created a Gcode file that ran all four motors for 20 minutes, which I ran twice back to back. No fan cooling on the board, ambient temperature was 18C.

Times between high temp reports of different motors:
12/5/2019, 11:50:35 AM Warning: high temperature reported by driver(s) 0 1 2 3 - (3 minutes later)
12/5/2019, 11:47:31 AM Warning: high temperature reported by driver(s) 0 1 2 - (10 seconds later)
12/5/2019, 11:47:21 AM Warning: high temperature reported by driver(s) 0 1 - (9 seconds later)
12/5/2019, 11:47:12 AM Warning: high temperature reported by driver(s) 0 - (33 seconds from start of print)
12/5/2019, 11:46:39 AM M32 “0:/gcodes/StepperTest.g”

I couldn’t get them to 130C, which is when they’d shutdown, so while they all generated high temperature warnings, motor movement continued for the whole test uninterrupted. Motors got pretty hot too! Temperatures dropped below 100C within 30 seconds of the end of the test, despite being on 100% idle hold.

Now I’d be more worried about motors overheating than the stepper drivers!

Ian

dc42

@oryhara said in Smart Effector hotend fan and Lights:

I can probably afford to turn down the current.
But with a fan blowing across the back of the board, should they really be getting that hot?

I wonder if there is some other problem.

How hot are the drivers getting?

oryhara

@dc42 How can I find that out?
I looked for a gcode but was unable to find one.

oryhara

I think I fixed it.

I repositioned the fan blowing at the MCU so it aims underneath instead of directly at the board from the side(see picture). That fan was standing straight up vertically, now angled down under the maestro.
Haven't seen a warning since.

jay_s_uk

1.8 amps is the full current requirements of the motors fitted to the predator.
Try dropping the current to 1400. That's what I have mine set at.

Phaedrux

@oryhara Would it be possible to mount the board vertically? That would have a big impact on convective cooling.