Duex Heater LED lit....unused
-
Hello all. Today I added a duex5 to my corexy in preparation of going to triple Z. Moved the BLTouch, moved X,Y and current dual Z to the Duex (keeping stepper wires away from heater line seemed like good practice). Changed config.g & home files and all seems to work well. There is an LED lit on the Duex that doesn’t seem like it should be. The LED above the E6 heater is lit....though E6 is not called for in the config. Its not lit on startup, but lights after home and stays lit. It’s also the only LED lit on the Duex. I cant find an LED explanation on the Duex like on the Duet2wifi dozuki so thought I would ask if this is normal and what that LED is for. Would also be nice to get a more experienced set of eyes on my config....just to be sure I have not missed something. I have two duet machines now, but I'm still pretty green.
-
config.g
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.10 on Mon Dec 07 2020 13:07:39 GMT-0500 (Eastern Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"SK-Go2" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; panel due
M575 P1 S1 B57600 ;activates panel due display; Drives
M569 P0 S1 ; physical drive 0 goes forwards (X)
M569 P1 S1 ; physical drive 1 goes forwards (Y)
M569 P2 S1 ; physical drive 2 goes forwards (Z)
M569 P3 S1 ; physical drive 3 goes forwards (extruder)
M569 P4 S1 ; physical drive 2 goes forwards (Z on E1)
M584 X9 Y8 Z7:5 E3 ; wws two Z motors connected to driver outputs Z and E1
M671 X-36:363 Y0:0 S3 ; wws leadscrews at left (connected to Z) and right (connected to E1) of X axis
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X200.00 Y200.00 Z400.00 E393.00 ; set steps per mm
M566 X900.00 Y900.00 Z34.00 E120.00 ; wws set JERK maximum instantaneous speed changes (mm/min)
M203 X22000.00 Y22000.00 Z2000.00 E5400.00 ; set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z40.00 E1000.00 ; wws set accelerations (mm/s^2)
M906 X1300 Y1300 Z800 E850 I20 ; wws set motor currents (mA) and motor idle factor in per cent
M593 F41.2 ; wws cancel ringing at 41.2Hz
M84 S30 ; Set idle timeout; Axis Limits
M208 X-1 Y-2 Z0 S1 ; set axis minima
M208 X324 Y329 Z304 S0 ; set axis maxima; Endstops
M574 X1 S3 ; configure sensorless endstop for low end on X
M574 Y1 S3 ; configure sensorless endstop for low end on Y
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
;M915 X Y S3 R0 F0 ; wws s1 sets up the last main command needed for sensorless homing; Z-Probe
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H3 F600 T21000 ; set Z probe type to bltouch and the dive height + speeds
G31 P25 X35 Y-4 Z3.08 ; set Z probe trigger value, offset and trigger height (Z-smaller number raises nozzle)
M557 X35:315 Y15:315 S31 ; define mesh grid
M376 H3 ; wws define fade height; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 A314.6 C690.4 D3.6 S1.00 V24.1 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
M308 S1 P"e0temp" Y"pt1000" ; wws configure sensor 1 as pt1000 on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 A893.3 C322.6 D5.3 S1.00 V24.0 B0 ; wws 64w BZAMD disable bang-bang mode for heater and set PWM limit
M143 H1 S450 ; set temperature limit for heater 1 to 450C; Fans
M950 F0 C"fan0" Q500 ; PART COOLING 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 ; HOTEND create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; fan 2 - driver cooling 40mm on during print only
M106 P2 S1 H1 T45 ; fan 2 - thermostatic control
M950 F7 C"duex.fan7" Q500 ; DUEX driver cooling 40mm on during print only
M106 P7 S1 H1 T45 ; fan 7 - thermostatic control; Tools
M563 P0 S"Hemera" D0 H1 F0 ; 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
M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85S4-7JKDL-3S46M-1SBHP
Used output buffers: 8 of 24 (21 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73888 of which 176 recycled
Never used RAM 14556, free system stack 186 words
Tasks: NETWORK(ready,182) HEAT(blocked,295) DUEX(blocked,35) MAIN(running,466) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:39 ago, cause: power up
Last software reset at 2021-01-16 16:08, reason: User, GCodes spinning, available RAM 14488, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 28.2, current 33.2, max 33.7
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-01-16 16:17:24
Cache data hit count 123162317
Slowest loop: 88.75ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.9ms, write time 2.2ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 27.77ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24288
WiFi IP address
WiFi signal strength -56dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.60 reads/min
- WiFi -
-
@TampaPrinter said in Duex Heater LED lit....unused:
Its not lit on startup, but lights after home and stays lit.
Post your homing files?
-
@TampaPrinter, the E6 Heater and PWM5 outputs on the DueX share the same control signal. So the E6 Heater led lights up when you first send a control signal to the BLTouch.
-
@dc42 I thought it might be something like that! Thanks much for the clarification. It's all working very well!