@phaedrux It's at 12v....because the LEDs are 12v, but the rest of the system is 24v! Of course!
I'll try fixing this tomorrow but I seem to remember there was some reason I had it wired up this way.
EDIT: I remember, I blew some of the mosfets on the duet over the years so the duet fan headers don't work right, hence I used the deus. I really should fix this things properly someday
I have a robo3d R1+. It's a mendel type machine. Does that help explain this any? Mesh leveling is absolute crap for me.
I've only had the files necessary for operation in the sys folder. I only ever notice config.g isn't there when I go to edit it. Sometimes I'll realize I forgot to do something after it goes to reboot the board, so I'll wait, then go back to system editor and see the file is gone.
I don't know if this is relevant, but if I reload the page (like if it's on a tab and my mac has to reload the tab because I was doing lots of other things) the board will repeat the last few instructions sent to it. Even if it is printing, it will interrupt the print to home and calibrate. This happens every time on safari, and a little less frequently on firefox.
Basically, once it's all dialed in, the board works great, but interacting with it in any way leads to unpredictable results. Still nowhere near as bad as octoprint though.
Seems better now. Wow, that was simple.
@jens55 I rolled back to the stock board and will just be using Klipper for it instead while I take a closer look at this board. I cant turn the parts fan on and off so I think there's a dead mosfet on here too. I measured with the stock board and it was 0.2 volts higher than the duet. I tuned the voltage up just a touch to hit 24 even even with the bed head on. shouldn't matter but meh.
My soldering skills are potato-class so I might not be able to repair this board.
@jay_s_uk It's a brand new printer.
@jens55 So measure in parallel with the bed rather than measuring with the meter connected where the bed would normally be?
EDIT: 23.4v. not great, but not bad either, right?
@dc42 I disconnected the bed in the chamber and measured there. 24V dead on. o_lampe, what s this about adjusting fans?
My duetwifi has been moved between multiple printers. I love it so much, every time I get a new machine, the first thing I swap in is my duet board. I have had to repair it a few times. The connectors for the bed and extruder heaters broke free (tiny gaps between solder and the pins) and had to be resoldered. It's been a great board.
It was just installed into my ender 6. While working on tuning, I noticed the bed heats MUCH slower than the stock board. It was slow then too, but it wasn't as severe as now. It shouldn't take 5 minutes to hit 70C, should it?
I also notice the fans spin much more slowly than if I directly connected them to the PSU. A little slower is expected, but this is quite a bit more than normal.
My theory is that along the way, something must have broken or worn down that I haven't seen yet. It's been several years, so maybe I should just retire this board. Ideas?
@phaedrux It's at 12v....because the LEDs are 12v, but the rest of the system is 24v! Of course!
I'll try fixing this tomorrow but I seem to remember there was some reason I had it wired up this way.
EDIT: I remember, I blew some of the mosfets on the duet over the years so the duet fan headers don't work right, hence I used the deus. I really should fix this things properly someday
Config.g
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri May 14 2021 22:58:27 GMT-0400 (EDT)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"foamboard forge" ; set printer name
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P5 S1 ; physical drive 5 goes forwards
M584 X0 Y1 Z2 E5 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E686.66 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z1800.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E350 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z350 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"duex.pwm3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X27 Y14.2 Z4.122 ; set Z probe trigger value, offset and trigger height
M557 X10:290 Y10:290 S20 ; define mesh grid
; Heaters
M308 S0 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"e1heat" T0 ; create bed heater output on e0heat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"duex.e2temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin duex.e2temp
M950 H1 C"duex.e2heat" T1 ; create nozzle heater output on duex.e2heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M950 F0 C"fan1" Q500 ; create fan 0 on pin fan1 and set its frequency
M106 P0 C"part cooler" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"duex.fan5" Q31600 ; create fan 1 on pin duex.fan5 and set its frequency
M106 P1 C"hotend" S0 H1:2 T60 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"duex.fan6" Q500 ; create fan 2 on pin duex.fan6 and set its frequency
M106 P2 C"lighting" S1 H-1 ; set fan 2 name and value. Thermostatic control is turned off
; Tools
M563 P0 S"hotend" 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
M308 S2 P"duex.e3temp" Y"thermistor" A"chamber temp" T100000 B3988 C0 R2200 ; chamber temperature sensor
M307 H0 A77.5 C296.9 D3.8 C24.1 B0 ; calibrate bed heater
M307 H1 A348.9 C165.7 D3.7 C24.2 B0 ; calibrate hotend heater
; TODO
; When a seperate lighting control method is found, break lighting out from fan controls
M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX2
Board ID: 08DDM-9FAM2-LW4SD-6J9F4-3S46Q-92XHW
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73880 of which 24 recycled
Never used RAM 14716, free system stack 189 words
Tasks: NETWORK(ready,169) HEAT(blocked,308) DUEX(blocked,31) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:12 ago, cause: power up
Last software reset at 2021-05-15 00:11, reason: User, GCodes spinning, available RAM 14716, slot 0
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 21.1, current 27.7, max 28.5
Supply voltage: min 24.1, current 24.2, max 24.5, 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
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-05-17 22:44:34
Cache data hit count 159721035
Slowest loop: 8.67ms; fastest: 0.21ms
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 0.0ms, 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: 15.65ms; 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.25
WiFi MAC address 60:01:94:34:39:67
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26176
WiFi IP address 10.0.0.17
WiFi signal strength -47dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.45 reads/min
M98
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
@phaedrux It's the strangest thing, but all of them do this. It's a consistent behavior.
@phaedrux Thanks, but that doesn't solve the issue of fan speed. its still much slower than a direct connection to the power supply.
; Fans
M950 F0 C"fan1" Q500 ; create fan 0 on pin fan1 and set its frequency
M106 P0 C"part cooler" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"duex.fan5" Q500 ; create fan 1 on pin duex.fan5 and set its frequency
M106 P1 C"hotend" S0 H1:2 T60 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"duex.fan6" Q500 ; create fan 2 on pin duex.fan6 and set its frequency
M106 P2 C"lighting" S1 H-1 ; set fan 2 name and value. Thermostatic control is turned off