Think its broken...
-
@T3P3Tony Ah ok, I see
(I thought powering off USB would show up as VIN around 5V)
Thanks for clarifying! -
OK so ive done the following.
Changed WiFi SID, no change
Changed WiFi Password. no change
Tried old router, no changeI get the same result each time.
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93644 of which 0 recycled
Exception stack ram used: 256
Never used ram: 11492
Tasks: NETWORK(ready,1244) HEAT(blocked,1236) MAIN(running,3808) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:08:56 ago, cause: power up
Last software reset at 2019-09-11 08:23, reason: User, spinning module GCodes, available RAM 11436 bytes (slot 2)
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 34.9, current 35.9, max 36.1
Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 1062453510
Slowest loop: 46.87ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, 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: 77.22ms; 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 changing mode
WiFi module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 84:f3:eb:41:4e:f8
WiFi Vcc 3.39, reset reason Hardware watchdog
WiFi flash size 4194304, free heap 26560
Socket states: 0 0 0 0 0 0 0 0
ok
I am now totally exhausted.
- WiFi -
-
Did i mention that im also getting this.....
Failed to change WiFi mode (code -7)
m587
M587: Failed to retrieve network list
ok -
Are you powering the board off USB now? If so what type of USB power supply are you using, could be its insufficient current from USB as the ESP8266 wifi module is somewhat power hungry.
-
@bearer don't think its that in this case, the ESP is reporting >3.3V VCC.
@Shaun thanks for the thorough investigation. What is not clear is if this is conducted from where it previously worked, or in your printer.
Nevertheless we should arrange a replacement, and test this board. Please can you submit a warranty request and reference this forum topic.
-
@Shaun said in Think its broken...:
@dc42 said in Think its broken...:
Have you tried re-flashing the WiFi firmware?
DC i have, all went through fine. Was one of the 1st threads i read on here where you suggested that.
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
That doesn't say anything about the WiFi firmware version. If you already have DuetWiFiServer.bin in /sys and it is dated this year, you can just send M997 S1 to re-install it (even better, download a fresh copy from https://github.com/dc42/RepRapFirmware/releases/tag/2.03). Preferably, send that command from PanelDue or from a PC running YAT, then you can watch the progress and verify that it completes successfully.
If you have already done this, no need to do it again, fill in the warranty form. The hardware watchdog reset message in the M122 report suggests either corrupt firmware or faulty hardware.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Board swap is on the table form Duet... and may be a good idea... just to possibly avoid the time/hassle, try hooking up VIN (in addition to USB) to a solid 12V or more supply, and re-flash wifi firmware, and re-test, with that power hooked up.
These guys know MUCH more than I... but... something is just itching my brain about power, flash, wifi module, etc, etc, etc. Probably I'm wrong, but it is something quick to try, before getting into a full board swap.
Delta / Kossel printer fanatic
-
@dc42 said in Think its broken...:
@Shaun said in Think its broken...:
@dc42 said in Think its broken...:
Have you tried re-flashing the WiFi firmware?
DC i have, all went through fine. Was one of the 1st threads i read on here where you suggested that.
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
That doesn't say anything about the WiFi firmware version. If you already have DuetWiFiServer.bin in /sys and it is dated this year, you can just send M997 S1 to re-install it (even better, download a fresh copy from https://github.com/dc42/RepRapFirmware/releases/tag/2.03). Preferably, send that command from PanelDue or from a PC running YAT, then you can watch the progress and verify that it completes successfully.
If you have already done this, no need to do it again, fill in the warranty form. The hardware watchdog reset message in the M122 report suggests either corrupt firmware or faulty hardware.
Hi
Ive actually re-installed the firmware, wifi and web a nuber of times in an attempt to get this working.
-
@T3P3Tony said in Think its broken...:
@bearer don't think its that in this case, the ESP is reporting >3.3V VCC.
@Shaun thanks for the thorough investigation. What is not clear is if this is conducted from where it previously worked, or in your printer.
Nevertheless we should arrange a replacement, and test this board. Please can you submit a warranty request and reference this forum topic.
Thank you Tony, believe me when i say i have tried everything i could find on the forums. I have tried this from every possible location including sitting right next to my router with my laptop. Like i said, im happy to try anything else you might suggest but i am now at a total loss.
-
@Danal said in Think its broken...:
Board swap is on the table form Duet... and may be a good idea... just to possibly avoid the time/hassle, try hooking up VIN (in addition to USB) to a solid 12V or more supply, and re-flash wifi firmware, and re-test, with that power hooked up.
These guys know MUCH more than I... but... something is just itching my brain about power, flash, wifi module, etc, etc, etc. Probably I'm wrong, but it is something quick to try, before getting into a full board swap.
Danal
I have powered the board from the PSU, then connected the usb and plugged this into my laptop. Results are the same.
-
@Shaun said in Think its broken...:
@Danal said in Think its broken...:
Board swap is on the table form Duet... and may be a good idea... just to possibly avoid the time/hassle, try hooking up VIN (in addition to USB) to a solid 12V or more supply, and re-flash wifi firmware, and re-test, with that power hooked up.
These guys know MUCH more than I... but... something is just itching my brain about power, flash, wifi module, etc, etc, etc. Probably I'm wrong, but it is something quick to try, before getting into a full board swap.
Danal
I have powered the board from the PSU, then connected the usb and plugged this into my laptop. Results are the same.
Ahhh, well, it was worth a try.
