Failed to update DuetWifiServer
-
@bearer
The same..
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
ok
M21 M111 P14 S1 M997 S1
SDHC card mounted in slot 0, capacity 3.98Gb
ok
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)
ok
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write error
ok
M997 S1
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write error
ok -
-
Yes, followed the instructions as in the link...step by step..same error
I’ve also downgraded the firmware to 1.21 and tried to update to 2.02 with the DuetWiFiServer 1.22 and 1.23...same error; and also tried with all major releases
I will try again in the morning maybe I’ve missed something
Anyway thank you guys for support! -
Sorry I missed that you included that link in your first post.
What should work is if you have 2.05.1 already installed with DWC 2.0.7 in the /www folder, and the M552 command commented out in your config file, and you have the 1.23 wifi server bin file on the SD card you should be able to send the wifi server update command to initialize the update.
So the one thing you haven't mentioned doing is the commenting out of the M552 command. Have you done that?
If you have commented it out, have you tried sending any other M552 S commands over yat?
M552 S-1 to disable the wifi module
M552 S0 to disable networking
M552 S1 to enable networking -
@Phaedrux said in Failed to update DuetWifiServer:
So the one thing you haven't mentioned doing is the commenting out of the M552 command. Have you done that?
wouldn't starting the Duet without the SD inserted sort of achieve that? that was my thinking at least to rule out any conflicting config, mount the SD card and then update.
-
I've tried yesterday this aproach and also tried again today with M552 commented and all M552 variants..no success,
I've also tried as suggested by @dc42 in other posts with and without VIN power, without endstops connected or BL-Touch
When I use the M997 S1 the wifi led blinks as if starting up but after a few seconds it is turning off.please see below today's log from YAT
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
M552
WiFi module is disabled
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6JKDL-3S86R-KWBDF
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93160 of which 396 recycled
Exception stack ram used: 312
Never used ram: 11492
Tasks: NETWORK(ready,1360) HEAT(blocked,1232) MAIN(running,3728) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:05:06 ago, cause: power up
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 12300 bytes (slot 1)
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 36.4, current 41.9, max 42.1
Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
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: 1970-01-01 00:00:00
Cache data hit count 606309682
Slowest loop: 1.67ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 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 ready with "M122" 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: 1001.18ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
M997 S1
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write errorM997 S0
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
M552
WiFi module is disabled
M552 S0WiFi module started
M997 S1
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write errorM552 S-1
M552
WiFi module is disabled
M552 S1WiFi module started
WiFi module is connected to access point v2.4GhzE, IP address 192.168.0.108
M997 S1
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write errormy config file
; Configuration file for Duet WiFi (firmware version 1.21) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2 on Tue Dec 11 2018 03:52:52 GMT+0200 (Eastern European Standard Time) ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P1 ; speak the firmware M667 S1 ; Select CoreXY mode ; Network M550 P"hypercubeEvo" ; Set machine name ;M552 S1 ; Enable network M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives M569 P0 S1 ; Drive 0 goes forwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S0 ; Drive 3 goes forwards M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E521 ; Set steps per mm M566 X1000.00 Y1000.00 Z150 E1000 ; Set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z300.00 E700 ; Set maximum speeds (mm/min) M201 X4000.00 Y4000.00 Z250.00 E4000 ; Set accelerations (mm/s^2) M906 X960.00 Y960.00 Z960.00 E1000.00 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 X285 Y285 Z270 S0 ; Set axis maxima ; Endstops M574 X2 Y2 S1 ; Set active high endstops ;M574 X1 Y2 S1 ; X home to max. Y home to max. Normally Closed limit switches. ;M574 Z1 S2 ; Define Z to use Probe. Home to Min ; Z-Probe M574 Z1 S2 ; Set endstops controlled by probe M558 P9 H2 F500 T6000 ; Set Z probe type to switch and the dive height + speeds G31 P1000 X0 Y-30 Z0.62 ; Set Z probe trigger value, offset and trigger height M557 X5:285 Y5:235 S56:76 ; Define mesh grid M376 H15 ; Set bed compensation to taper off over 15mm ; Heaters M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0 M143 H0 S120 ; Set temperature limit for heater 0 to 120C M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1 M143 H1 S280 ; Set temperature limit for heater 1 to 280C ; BLTouch - Heaters M307 H3 A-1 C-1 D-1 ; Disable the 3rd Heater to free up PWM channel ; 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 ; Tools M563 P0 S"e3D_V6_0.4" D0 H1 ; Define tool 0 G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets G10 P0 R60 S220 ; Set initial tool 0 active and standby temperatures to 0C ; Automatic power saving M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss ; Miscellaneous M572 D0 S0.54 ; Pressure advance ;use volumetric M200 D1.75 ; ############################ ; 9 - RETRACTION SETTINGS ; ############################ M207 S2.3 R-0.000 F4000 T3000 Z0.0 ;M207 ; echo the settings to the console to show they are applied ; M207: Set retract length ; Parameters ; Snnn positive length to retract, in mm ; Rnnn positive or negative additional length to un-retract, in mm, default zero ; Fnnn retraction feedrate, in mm/min ; Tnnn feedrate for un-retraction if different from retraction, mm/min (RepRapFirmware 1.16 and later only) ; Znnn additional zlift/hop ; Example: M207 S4.0 F2400 Z0.075 ; known to work M207 S2.3 R-0.000 F4000 T3000 Z0.0 ; FEEDRATE CONVERSIONS ; 20mm/s = F1200 ; 35mm/s = F2100 ; 50mm/s = F3000 ; 70mm/s = F4200 ; 100mm/s = F6000 ; 120mm/s = F7200 ; 133mm/s = F8000 - WiFi -
-
To me it seems like the communication with the ESP is working, but the resetting and entering bootloader fails.
If the board is past its warranty period or the problem is not considered for a warranty replacement i suppose you could try to use an FTDI adapter + esptool to re-flash the ESP if the provided binary is the same format esptool expects; or just poke around the Reset, GPIO00 and GPIO02 pins of the ESP to get it into the correct bootmode before letting RRF do the update. (but spidy sense says something got bust, or some peripheral is interfering, however I can't see any shared functions on those signals)
-
@bearer said in Failed to update DuetWifiServer:
but the resetting and entering bootloader fails.
maybe this will shed some light on what doesn't work, seems there is no debug output from wifi when using M997 S1 - however this should get something.
M111 P14 S1 ;to enable wifi debug M552 S-1 ;to disable the wifi module M552 S0 ;to disable networking M552 S1 ;to enable networking -
@vucheria said in Failed to update DuetWifiServer:
The error that I get is when I use YAT with M997 S1 is
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write errorWe've seen this happen a few times. Unfortunately, the only 100% reliable fix we know of when this happens every time you try to update is to replace the WiFi module.
-
@bearer said in Failed to update DuetWifiServer:
seems there is no debug output from wifi when using M997 S1
@dc42 shouldn't we see
Wifi: ets Jan 8 2013,rst cause:2, boot mode:(1,6)after M997 S1? just as we see
WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,6)after M552 S1 with debugging enabled?
Even if RRF doesn't switch to 74880 baud to read the bootloader message I'd still think we got some output (but seems not even if the flashing works?)
-
Thank you so much guys for your support;
The board is out of warranty, but since I have no problems regarding the prints I will use it/wait for repair until it fails;
Anyways duet boards are the best, never looked back since 2018
-
@bearer
I'm not that confident in re-flashing the ESP and don't want to damage the board.
Thanks -
@vucheria said in Failed to update DuetWifiServer:
@bearer
I'm not that confident in re-flashing the ESP and don't want to damage the board.
ThanksNo worries, my interest was as much as determining cause as to solve problem.
The good news is that while you do need hot air tools, the wifi module isn't the worst part to replace on a duet if you later need to replace it.
-
undefined faaz referenced this topic
