Think its broken...

Phaedrux

What do you currently have in your config.g?

Shaun

Still getting an error

m552
WiFi module is idle
ok
m122
=== 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 (24 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93688 of which 0 recycled
Exception stack ram used: 288
Never used ram: 11416
Tasks: NETWORK(ready,1244) HEAT(blocked,1236) MAIN(running,3756) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:09:08 ago, cause: software
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: 4
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.5, current 37.1, max 37.3
Supply voltage: min 1.7, 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 1085375973
Slowest loop: 1.10ms; 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: 2.02ms; 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 running
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
Error retrieving WiFi status message: bad reply format version
m552
WiFi module is idle
ok

Shaun

@Phaedrux said in Think its broken...:

What do you currently have in your config.g?

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.0.0 on Sun Sep 01 2019 16:01:34 GMT+0100 (British Summer Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CR10" ; set printer name
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350Z16 I0 ; configure microstepping without interpolation
M350X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z4000.00 E420.00 ; 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 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X950 Y950 Z950 E950 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 Z400 S0 ; set axis maxima

; Endstops
M574 X1 Y1 Z1 S1 ; set active high endstops
M574 Z1 S3 ; set endstops controlled by motor stall detection

; Z-Probe
M574 Z1 S2 ; set endstops controlled by probe
M558 P5 H5 F0 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P0 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid

; 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

; Fans
M106 P0 S0 I0 F500 H T45 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S1 I0 F500 H-1 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S1 I0 F500 H-1 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; 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

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Custom settings are not defined

Phaedrux

@Shaun said in Think its broken...:

M350Z16 I0 ; configure microstepping without interpolation
M350X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation

Unrelated, but you're missing a space between the M350 and the axis letter.

I understand the frustration. Let's see if we can nail down the issue.

The config looks ok.

Can you send M587 by itself to get a list of saved SSIDs? This will confirm that the SSID has been properly added.

The error message network scan failed would indicate that it's unable to identify a network SSID in range to connect to and it's given up. In your other thread we did identify that the signal strength was rather weak. In order to diagnose if this is in fact the case, I suggest temporarily relocating the wireless access point or the printer so that they are both in close proximity with very little obstruction and seeing if you can then in fact connect.

Shaun

@Phaedrux said in Think its broken...:

@Shaun said in Think its broken...:

M350Z16 I0 ; configure microstepping without interpolation
M350X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation

Unrelated, but you're missing a space between the M350 and the axis letter.

I understand the frustration. Let's see if we can nail down the issue.

The config looks ok.

Can you send M587 by itself to get a list of saved SSIDs? This will confirm that the SSID has been properly added.

The error message network scan failed would indicate that it's unable to identify a network SSID in range to connect to and it's given up. In your other thread we did identify that the signal strength was rather weak. In order to diagnose if this is in fact the case, I suggest temporarily relocating the wireless access point or the printer so that they are both in close proximity with very little obstruction and seeing if you can then in fact connect.

Remembered networks:
Spiffy IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok

Signal is 100%

How do i clear any config for network. maybe a clean slate would be a good idea.

Shaun

I have redone the config.

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.0.3 on Wed Sep 11 2019 09:04:56 GMT+0100 (British Summer Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CR10" ; set printer name

; Network
M552 S0 ; 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 S1 ; physical drive 2 goes forwards
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 Z4000.00 E420.00 ; 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 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X950 Y950 Z950 E950 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 Z400 S0 ; set axis maxima

; Endstops
M574 X1 Y1 Z1 S1 ; set active high endstops

; Z-Probe
M558 P0 H5 F0 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:215 Y15:195 S20 ; define mesh grid

; 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

; Fans
M106 P0 S0 I0 F300 H1 T45 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S0 I0 F300 H1 T150 ; set fan 1 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

; 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

Phaedrux

@Shaun said in Think its broken...:

How do i clear any config for network. maybe a clean slate would be a good idea.

From the previous thread:

From the console can you please send the following:
M552 S0
M588 S"*"
M587 s"Spiffy" p"Password1"
M552 S1
M122
This will take the wifi module to idle, clear all saved SSIDs, re-add your SSID, and re-enable the module and hopefully connect. Then the diagnostic should show the connection stats.

Shaun

@Phaedrux said in Think its broken...:

@Shaun said in Think its broken...:

How do i clear any config for network. maybe a clean slate would be a good idea.

From the previous thread:
From the console can you please send the following:
M552 S0
M588 S"*"
M587 s"Spiffy" p"Password1"
M552 S1
M122
This will take the wifi module to idle, clear all saved SSIDs, re-add your SSID, and re-enable the module and hopefully connect. Then the diagnostic should show the connection stats.

I’ve done all of that, same problem. Ill set up my old router tonight and see if I can connect to that. Just in case it’s my current router.

themelle

@Shaun said in Think its broken...:

Supply voltage: min 1.6, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no

Is it just me or are those 1.6-1.8V VIN indeed usable?

T3P3Tony

@themelle if just powering off USB (fine for WIFI tests) you don't need VIN

themelle

@T3P3Tony Ah ok, I see
(I thought powering off USB would show up as VIN around 5V)
Thanks for clarifying!

Shaun

OK so ive done the following.

Changed WiFi SID, no change
Changed WiFi Password. no change
Tried old router, no change

I 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.

Shaun

Did i mention that im also getting this.....

Failed to change WiFi mode (code -7)
m587
M587: Failed to retrieve network list
ok

A Former User

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.

T3P3Tony

@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.

https://www.duet3d.com/warranty

dc42

@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.

Danal

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.

Shaun

@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.

Shaun

@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.

https://www.duet3d.com/warranty

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.

Shaun

@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.