I did as you said and it "kind of worked".
So i am now able to get connected to the board. However when ever I make a change in the config.g file (eather by putting SD in PC or by web edit) the system will not be able to get connected again. (f.ex. I changed the IP adress and after that I was not able to connect to the printer (on eather IP adress.
So far I havent tested that much but I will try to soon to maybe get an idea.
@phaedrux
I thought I did - but it looks like i only overwrote the files with same name.....
However I now did deleated the old files first, copied in the new one and tested again. Still no connection.
Here is what I get now as feedback on M20 P"/www/" in YAT.
(BTW. I tested now multiple IP adresses, without any success 
)
M552
Network is enabled, configured IP address: 192.168.0.200, actual IP address: 192.168.0.200
ok
M20 P"/www/"
Begin file list
css
fonts
img
js
DuetAPI.xml
favicon.ico.gz
index.html.gz
manifest.json.gz
precache-manifest.a4ab8f573fcc203b798fa7d11eee39d5.js.gz
service-worker.js.gz
End file list
ok
Sure 
this is what i got as feedback:
M20 P"/www/"
Begin file list
dwc.json
favicon.ico.gz
html404.htm
language.xml.gz
reprap.htm.gz
css
fonts
js
img
index.html.gz
manifest.json.gz
precache-manifest.a4ab8f573fcc203b798fa7d11eee39d5.js.gz
service-worker.js.gz
DuetAPI.xml
Main_FW-V_2.05_DuetETH
End file list
ok
@phaedrux
I bought it in 05/2020 from the german duet seller Dold Mechatronik.
well I already did tested that - and I am also my own network admin so I checked in my network settings the IPs, and I also tryed to give the MAC address a fixed IP from my network and writing "M552 S1 P0.0.0.0 " in the config.g file however it did not worked at all. I was not able to even find the printer in my own (ethernet) network.
My guess now would be that I eather have a hardware Issue with the network controller section or I might have some issues with the soft/firmware sigth. However I doubt that it is software related - because of the fact that it randomly stopped working without any external influence.
I am open for some other inputs.
Well the ping was correct.
I did changed the SD Card and also overwrote the www folder with a new build.
I also changed the IP address in the config and testet that. But nothing changed.
Still not able to reach the webclient, but ping and everything else looks fine.
sure
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917NK-F2MSW-6JKF2-3SN6K-1G6NG
Used output buffers: 1 of 24 (3 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 74416 of which 0 recycled
Never used RAM 16124, free system stack 193 words
Tasks: NETWORK(ready,23.7%,464) HEAT(delaying,0.0%,278) Move(notifyWait,0.1%,340) MAIN(running,76.2%,467) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 01:04:35 ago, cause: power up
Last software reset at 2021-11-15 22:30, reason: User, GCodes spinning, available RAM 16124, 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
Step timer max interval 0
MCU temperature: min 18.0, current 21.1, max 21.6
Supply voltage: min 1.3, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 5.28ms; fastest: 0.13ms
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.1ms, 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 ready with "M122" 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: 0.47ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
Interface state active, link 100Mbps full duplex
ok
M552
Network is enabled, configured IP address: 192.168.0.254, actual IP address: 192.168.0.254
ok
Hi Tony,
today it happend again. I turned on my printer as usual and the BLTouch and all the lights started as usual. However I was not able to connect the printer via network adress (and I checked my network settings & status - was not the problem)
So I connected the printer via USB (and only powered via usb-pc connection) and sended M122 in YAT.
Result:
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later<LF>Board ID: 08DGM-917NK-F2MSW-6JKF2-3SN6K-1G6NG<LF>Used output buffers: 1 of 24 (2 max)<LF>=== RTOS ===<LF>Static ram: 23876<LF>Dynamic ram: 74416 of which 0 recycled<LF>Never used RAM 16124, free system stack 193 words<LF>Tasks: NETWORK(ready,13.4%,549) HEAT(delaying,0.0%,278) Move(notifyWait,0.1%,340) MAIN(running,86.4%,467) IDLE(ready,0.1%,29), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:11:13 ago, cause: power up<LF>Last software reset at 2021-11-15 22:30, reason: User, GCodes spinning, available RAM 16124, slot 1<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Step timer max interval 0<LF>MCU temperature: min 14.6, current 19.3, max 19.8<LF>Supply voltage: min 0.4, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no<LF>Heap O[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]
(Ethernet was not plugged in while i connected the Duet to the pc via usb. There was only the USB connection - if this makes any diffrence)
Does anyone know why I get these issues now?
Edit:
I now also tested with Ethernet connected. But it did not work.
So I tryed restarting the ethernet again as I did last time. However it did not work at all.
M552 S0
Network stopped<LF>ok<LF>
M552 S1 P192.168.0.254
ok<LF>Network running, IP address = 192.168.0.254<LF>
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03<LF>ok<LF>
M552
Network is enabled, configured IP address: 192.168.0.254, actual IP address: 192.168.0.254<LF>ok<LF>
Even tho it says network is running - it is not reachable over web.
Ethernet LEDs are showing that cable connection is there. BTW I also switched the Ethernet Cable with one I know that it works.
I already solved my issue:
I reinstalled the pc driver - restarted the pc.
After that I was able to connect the printer via YAT.
I then disabled networking with M552 S0 and restartet it again M552 S1 Pxx(your adress)xx
After this I was able to reach the printer again via web.
I still have no idea why this error occurred, but now i was also able to start the print without any issue. (However i reuploaded the gcode file for it just to be sure)
Does anyone have an idea what the issue of the printer could have been? / Do i need to be careful or can i still trust the machine?
Hi all,
I have a Duet 2 Ethernet with latest FW Release Versions (3.3).
I printed a lot last weeks without any issues and have never changed anything in this time.
I startet a print as usual over the web interface. However it did not started the print directly, i got the info that he reconected. So I pushed the restart print in the jobs page and the webclient went offline.
the printer itself did nothing. Everything looked fine / no index light showed diffrent / Endstops are still working f.ex.
Also the Ethernet Index lights at the Ethernet connector showed some traffic / green light blinking.
I then reflashed the SD card with a save file. Did not worked. I then checked with an older FW version, still nothing. I then connected the Board via usb with my pc (only powered by usb). Even tho my pc did recognize the board correctly in the device manager YAT Tool wasnt able to talk with the board.
Has anyone any idea what I can do?
Thanks a lot for your help and inputs!
Greetings
Joe
One more thing - i was happy too early:
I have now the issue that my bed "heats up to slowly".
As fas as my multimeter tells me the 100k @ R25 are correct.
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display
; Network
M551 P"" ; set password
M552 P192.168.0.254 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 S1 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E136.45 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; 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 X235 Y235 Z260 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 low end on Y via pin ystop
M574 Z1 S3 ; configure sensorless endstop for low end on Z
; Z-Probe
M950 S0 C"exp.heater3" ; 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 X42.5 Y-8 Z2.4 ; set Z probe trigger value, offset and trigger height
M557 X50:200 Y50:200 S20 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 ; 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 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"e0temp" Y"thermistor" T100000 B4400 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat 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
;M143 H0 S115 ; set temperature limit for heater 0
;M305 P0 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 0
;M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S275 ; set temperature limit for heater 1 to 275C
; BLTouch - Heaters
M307 H3 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.
; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1:0 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
; Tools
M563 P0 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
T0
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
What am I missing / do i need to correct with the new FW
Update:
Firmware Update was successful. I had to adjust some commands (RRF Config tool helped me a lot there).
And after correcting the connection error at the bed thermistor everything works now as intended and the charts are now looking fine as well. Thanks for the support @fcwilt !
Have a nice day
Sincerely
Joe
@fcwilt
Thanks for the info - i will try.
The Heater was realy missing because I was to dumb to connect the thermistor correctly. It now shows the temp again and works with some ugly additions.
This might had been the issue in first place, that he coudnt measure any resistance at the bed thermistor.
I have tested the M140 but it did not change my issue. So I desided to update to latest stable FW 3.3 and downloaded the Duet2and3Firmware-3.3.zip from there. I used the System/Upload System files and after the upload and decompression it installed the updates without any error mssg. However in diagn. it still shows me that my firmware is 2.03 from 2019.
Is it not possible to upgrade the reprap firmware like this? I thought that this is the recommended way to do an update.
But at least it looks like a "Bed-Heater" is now recognized at least. However there are some things wrong I guess.
I will check first if there is realy no connection on the Bed temp sensor,... but does anyone know why there is now shown 8 Heaters in chart?
Here is the feedback to M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917NK-F2MSW-6JKF2-3SN6K-1G6NG
Used output buffers: 1 of 24 (6 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93324 of which 0 recycled
Exception stack ram used: 388
Never used ram: 11680
Tasks: NETWORK(ready,652) HEAT(blocked,1236) MAIN(running,3756) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:06:07 ago, cause: software
Last software reset at 2021-10-25 19:56, reason: User, spinning module GCodes, available RAM 11836 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 24.4, current 25.2, max 25.4
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/214
Driver 1: standstill, SG min/max 0/180
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-10-25 20:02:11
Cache data hit count 863568591
Slowest loop: 4.82ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 167, MaxWait: 10059ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 7, completed moves: 7, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 5.11ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex
@fcwilt
I dont have M140 command in config.g, config-override.g or bed.g. I have not checked the rest but i guess it should be in config.g.
What exactly do I need to add, just M140? I guess there are some parameters as well ^^
And I still dont get why this was not necessary bevore 
To the out of sync firmware I must admit that I am a very lazy person and I realy like the fact that for the last year I could always just use my printer without any changes and never had to adjust anything (apart from retensioning the belts). The best printer is the one that works 
.
But I will look up the changelog and see if there are important changes and update the firmware then.
Greetings
Joe
Hi all,
I have recently repaired my duet 2 ethernet board after my U3 Chip died (because of a loose cable which I also fixed). After the repair the board and 5v (3.3v) looked fine again and i could start the printer without any issues. All the functions look fine for me as well (Homeing, heating up the tool heater,...) howerver for some reason i am now missing the bed heater in my dashboard.
Does anyone know why this error now appeared? I have not changed anything on my firmware so it is kind of strange that this now happend.
Duet Web Control 3.2.2
Duet Ethernet 1.02
RepRapFirmware for Duet 2 WiFi/Ethernet 2.03 (2019-06-13b2)
config g:
; Heaters
M305 P0 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S275 ; set temperature limit for heater 1 to 275C
@elmoret
Thanks a lot. I'll see if i can get this fixed
@t3p3tony
Its funny because I have not changed anything since a long time. I will rewire my entire device to make sure i dont have any shorts. I only have a BLTouch that uses 5 Volts. Do you have any recommendations for me how i can get my device up and running fast?
I am an electrical electrical engineer so i could solder the damaged chips with hot air away and replace them. However, getting any schematics and component list would help me a lot. And also if someone had experience with this kind of failiure, what components usually die with the controller? (i guess the diode d2, anything else known?)
Hi all,
I have now since 07/2020 a duet 2 ethernet in use and never had any issues. However for some reason the U3 controller randomly blew up last time i turned on the printers main switch. Unfortunately i need the printer up running as soon as possible.
I'm afraid that the controller was nice enough to kill the neighboring components while it died.
Does anyone have any recommendations on what to do?
Thanks a lot.
@Phaedrux
Thank you very much for this post. By going through that page I found multiple problems. Now my machine prints perfect 
Thank you alot