Cant get the WiFi to Work

Amilious · 7 Dec 2017, 02:37

I was talking on this https://www.duet3d.com/forum/thread.php?pid=31956 thread, but the supplier suggested that I start a new thread so they can see documentation of what has been tried.

[[language]]
M122
=== Diagnostics ===
Used output buffers: 1 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4S8-6JTDG-3S06T-1MZVX
Static ram used: 15488
Dynamic ram used: 97680
Recycled dynamic ram: 1520
Stack ram used: 4328 current, 5444 maximum
Never used ram: 10940
Last reset 01:05:55 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 33032 bytes (slot 2)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 41.0, current 41.7, max 42.4
Supply voltage: min 24.3, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest main loop (seconds): 0.003824; fastest: 0.000042
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -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 state is disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
HTTP sessions: 0 of 8
Socket states:  0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
ok

```And this is what happens when i try to set up the wifi, or when i try to upgrade the firmware.

[[language]]
M552 s0
ok
M552 s1
Turn off the current WiFi mode before selecting a new one
ok
M552 s-1
WiFi module stopped
ok
M552 s1
ok
M587 S"Amilious" P"{my pass was here}"
M587: Failed to add SSID to remembered list
ok
M587
M587: Failed to retrieve network list
ok
M552 S-1
WiFi module stopped
ok
M587 S"Amilious" P"{my pass was here}"
M587: Failed to add SSID to remembered list
ok
M552 s0
ok
M552 s1
Turn off the current WiFi mode before selecting a new one
ok
M587 S"Amilious" P"{my pass was here}"
M587: Failed to add SSID to remembered list
ok
M997 S-1
M997: Invalid module number '-1'

ok
M552 S-1
WiFi module stopped
ok
M552 S1
ok
M587 S"Amilious" P"{my pass was here}"
M587: Failed to add SSID to remembered list
ok
M997 S1
Trying to connect at 460800 baud: failed
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Error: Installation failed due to comm write error
ok
M552 s0
ok
M552 s1
Turn off the current WiFi mode before selecting a new one
ok
M552 s-1
WiFi module stopped
ok
M552 s1
ok
M997 S1
Trying to connect at 460800 baud: failed
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Error: Installation failed due to comm write error
ok

elmoret · 7 Dec 2017, 02:52

What have you done leading up to this? I saw in your past posts some comments about changing firmware versions, could you detail what was done with regards to that?

Amilious · 7 Dec 2017, 02:59

I just tried a few different versions to see if it was caused by the firmware. I have tried
1.18
1.18.2
1.19
1.19.1
1.19.2
1.20beta11
I could not get the wifi to work on any of those firmware versions.

I just get:

M587: Failed to add SSID to remembered list
and

M997 S1
Trying to connect at 460800 baud: failed
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Error: Installation failed due to comm write error

Amilious · 7 Dec 2017, 03:07

I have had this board since Aug, but I did not try to use it until last week. I had been busy and did not have my printer put together yet. I have built a Hypercube Evolution. Just trying to give any information that may help. It could maybe be something in my config.g as well. I am new to this board and got this config from another thread about a HEVO.

[[language]]
M503
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Jun 30 2017 19:04:28 GMT-0500 (Central Daylight Time)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z300 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 S1; Define active high microswitches
M558 P1 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z2.32 ; Set Z probe trigger value, offset and trigger height
M557 X13:293 Y5:260 S83 ; Define mesh grid

; Drives
M569 P0 S0 ; X goes forwards
M569 P1 S1 ; Y Reversed
M569 P2 S0 ; Z goes forwards
M569 P3 S0 ; Extruder goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X99.5 Y99.5 Z399.7 E79.9 ; Set steps per mm
M566 X900 Y900 Z120 E900 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z500 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M572 D0 S0.1	;Pressure Advance

; Heaters
M143 S260 ; Set maximum heater temperature to 260C
;M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C7.06e-8 R4700 ; Set thermistor + ADC parameters for heater 1

; Tools
M563 P0 D0 H1 ; 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
M550 PHYPERCUBE ; Set machine name
M552 S1 ; Enable network
;M587 S"Amilious" P"{my password was here}"; Configure access point and IP addresses. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S1 ; enable Telnet

; 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 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured

ok

Amilious · 7 Dec 2017, 03:18

Just tried to comment out all the network lines, but got the same result

dc42 · 7 Dec 2017, 09:06

@Amilious:

…
M997 S1
Trying to connect at 460800 baud: failed
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Error: Installation failed due to comm write error

If you were using USB power only at the time, try again with VIN power. Otherwise, ask for your Duet to be replaced or repaired - sounds like it needs a new WiFi module.

Amilious · 7 Dec 2017, 15:51

I figured it was probably that. I have read through the forums and that seemed likely to be the problem. I purchased this board on August 11th, and did not take it out of the box until last week. I project got delayed and i was not able to work on it until recently. I have been talking to my supplier(Filastruder). I am waiting for them to get a response from Think3DPrint3D, because I guess I am past the normal time for the exchange. I guess the six month warranty is only after November 14th purchases. The supplier has been very helpful and informative. I'm just a little frustrated because i have been excited to use this board on the HEVO that I have built, that ended up costing twice as much as i originally planed. At least i still have my trusty Anet A8. Ha ha ha. I do have a spare 24V ramps kit laying around, but i hope it does not come to that.

Amilious · 8 Dec 2017, 01:04

I replacement was approved. Thank you for your time and help. I would also like to thank Tim from Filastruder, for his work getting this issue resolved for me.

elmoret · 8 Dec 2017, 02:51

*Tim

Amilious · 8 Dec 2017, 05:52

ha ha ha ha. I knew that, I don't know why i wrote Jim. lol!! Probably because my father is Jim. lol!! Thank you!!!

elmoret · 13 Dec 2017, 23:51

Just got this return, it seems the ESP8266 has developed an internal fault. It gets warm, not too hot to touch but noticeably warm. Can confirm the following:

SENT: M552
READ: WiFi module is disabled

SENT: M552 S1
READ: ok

SENT: M552
READ: WiFi module is being started

Issuing replacement.

Amilious · 23 Dec 2017, 06:08

I received the fixed or replaced board. I was able to update the firmware and connect to wifi!

lolorc · 18 Feb 2018, 17:28

Hi,

I've upgraded to 1.21RC2 and I'm encountering the same issue.
Can't get the board to add the SSID

WiFi -
Network state is starting
WiFi module is disabled

it was working perfectly with 1.19 just before

[[language]]
ttyACM1 18°> M115
SENDING:M115
FIRMWARE_NAME: RepRapFirmware for Duet WiFi and Duet Ethernet FIRMWARE_VERSION: 1.21RC2 ELECTRONICS: Duet WiFi 1.0 or 1.01 FIRMWARE_DATE: 2018-02-15 build 2
ttyACM1 18°> M552 S1
SENDING:M552 S1
Turn off the current WiFi mode before selecting a new one
ttyACM1 18°> M589
SENDING:M589
M589: Failed to retrieve own SSID data

dc42 · 18 Feb 2018, 18:20

Send M552 S-1 to reset the wifi module, then M552 S0. Then send M122 and check what wifi firmware version it reports in the network diagnostics.

lolorc · 18 Feb 2018, 19:03

[[language]]
=== Diagnostics ===
Used output buffers: 1 of 32 (1 max)
=== Platform ===
RepRapFirmware for Duet WiFi and Duet Ethernet version 1.21RC2 running on Duet WiFi 1.0 or 1.01

[[language]]
=== Network ===
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 starting
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0

Can't see the specific WifiServer version

dc42 · 18 Feb 2018, 19:40

The WiFi module is stuck on starting. Copy the new DuetWiFiServer.bin file to /sys on the SD card in a PC, then put the card back in the Duet and try installing it using M997 S1 again.

lolorc · 18 Feb 2018, 20:08

yep, sorry for the noise, it's now ok :

[[language]]
ttyACM0 17°> M997 S1
SENDING:M997 S1
Trying to connect at 230400 baud:
 success       
Erasing 4096 bytes...
Erasing 24576 bytes...

I should have checked the filesize when I downloaded the bin…

Thanks !

SputnikOC3d · 1 Mar 2018, 21:21

I just tried this or noticed this issue and sent M997 S1 to the board via YAt … wonder if it changes anything

dc42 · 1 Mar 2018, 21:41

@lolorc:

yep, sorry for the noise, it's now ok :
[[language]]
ttyACM0 17°> M997 S1
SENDING:M997 S1
Trying to connect at 230400 baud:
 success       
Erasing 4096 bytes...
Erasing 24576 bytes...
I should have checked the filesize when I downloaded the bin…

Thanks !

Yes, 24576 bytes is about 10% of the correct size.