@droftarts said in Duet 2 Wifi Board - Wifi not working:
@elpeter I can confirm that we consider this a warranty replacement issue. Please contact the reseller you bought it from, follow their warranty claim process, and quote this post as authorisation. Sorry for the inconvenience.
Ian
Thanks so much Ian for your help. Already contacted them. I just hope this goes smooth and fast and I can get the printer finally working soon...
Cheers!!
Sorry, forgot to attach config.g. Here it is:
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Sixtina V-core 3" ; set printer name
M669 K1 ; CoreXY
G29 S1 ; Set Units to Millimeters
; Network
M552 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S1 ; enable Telnet
; PanelDue
M575 P1 S1 B57600
; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P3 S1 ; physical drive 2 goes forwards
M569 P7 S0 ; physical drive 7 goes forwards
M569 P8 S0 ; physical drive 8 goes forwards
M569 P9 S0 ; physical drive 9 goes forwards
M584 X0 Y1 Z7:8:9 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 ; set steps per mm
M906 X1000 Y1000 Z800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M566 X400.00 Y400.00 Z6.00 E120.00 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X10800.00 Y10800.00 Z1000.00 E3600.00 ; set maximum speeds (mm/min)
M201 X5000.00 Y5000.00 Z100.00 E3600.00 ; set accelerations (mm/s^2)
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X510 Y500 Z500 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure active high endstops
M574 Y2 S1 P"ystop" ; configure active high endstops
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
M671 X-4.5:250:304.5 Y-4.52:505:-4.52 S5 ; Define positions of Z leadscrews or bed levelling screws
; Z-Probe
;; Inductive Probe
; M558 P5 C"!io3.in" H5 F400 T5000 ; set Z probe type to unmodulated and the dive height + speeds
;; BL-touch
; M558 P5 C"io2.in" H5 F500 T10800 ; set Z probe type to unmodulated and the dive height + speeds
; Z-Probe
M950 S0 C"duex.pwm5" ; 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 X-28 Y-13 Z4.582 ; set Z probe trigger value, offset and trigger height
M557 X30:215 Y15:195 S20 ; define mesh grid
;M557 X30:300 Y15:300 P5 ; define mesh grid
; Heaters
; M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0 ; V-core Default
; M950 H0 C"out0" T0 ; create bed heater output on out5 and map it to sensor 0 ; V-core Default
; M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit ; V-core Default
; M140 H0 ; map heated bed to heater 0 ; V-core Default
; M143 H0 S110 ; set temperature limit for heater 0 to 110C ; V-core Default
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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 B4138 ; 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 S300 ; set temperature limit for heater 1 to 300C
;; Run Bed PID Tune!! Bellow is an example for a 300x300 bed
M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0 ; V-core Default
; Fans
;M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency ; V-core Default
;M106 P0 C"Hotend Fan" S0 H1 T45 L255 ; set fan 0 name and value. Thermostatic control turned on for Hotend ; V-core Default
;M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency ; V-core Default
;M106 P1 C"Layer Fan" S0 H-1 L255 ; set fan 1 name and value. Thermostatic control is turned off ; V-core Default
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
; Tools
; M563 P0 D0 H1 F1 ; define tool 0 ; V-core Default
; G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets ; V-core Default
; G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; V-core Default
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
; M950 H1 C"out1" T1 ; create nozzle heater output on out2 and map it to sensor 1 ; V-core Default
; M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; V-core Default
; M143 H1 S250 ; V-core Default
; EVA 2 / BMG / E3D V6
M92 E415 ; set extruder steps per mm, 1.8 angle/step
M906 E800 ; set extruder motor current (mA) and idle factor in per cent
; M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend" ; V-core Default
;; Run Heater PID Tune!!
M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0 ; V-core Default
;G31 P500 X-30 Y-15 Z0.20 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed ; V-core Default
T0
; Pressure Advance
; M572 D0 S0.10
Sorry for the mess, I'll clean it once I get it finally working...
@droftarts said in Duet 2 Wifi Board - Wifi not working:
@elpeter please connect via USB and send M552 S-1 to turn off WiFi, then M552 S0 to set it to idle. Then send M122, and post response. Then send M997 S1 to try the update again.
Ian
Already tried what you mentioned. That's what lead me to open the issue, as I've looked into this forum and other similar posts like mine got to that faulty wifi module conclusion...
Here's the output though:
M552 S-1
WiFi module stopped
ok
M552 S0
ok
WiFi module started
Error: Failed to initialise WiFi module: SPI timeout
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85S4-7JKF2-3SD6S-1UAMP
Used output buffers: 1 of 24 (14 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73880 of which 60 recycled
Never used RAM 14680, free system stack 174 words
Tasks: NETWORK(ready,364) HEAT(blocked,306) DUEX(blocked,31) MAIN(running,408) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 01:15:18 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 14680, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 36.0, current 36.6, max 36.9
Supply voltage: min 23.9, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 100.19ms; fastest: 0.21ms
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
Heater 1 is on, I-accum = 0.0
=== 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: 200.24ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 1
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 0, 0.00 reads/min
ok
M997 S1
T:18.6 /0.0 T0:18.6 /0.0 B:19.1 /0.0
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
Thanks all for your help!
@paulhew said in Duet 2 Wifi Board - Wifi not working:
@elpeter Please post your config.g and results of a M122
Do you have a panelDue connected as the second part of your post looks like it is looking for something that is not there.... Guess.
There you go:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85S4-7JKF2-3SD6S-1UAMP
Used output buffers: 1 of 24 (14 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73880 of which 60 recycled
Never used RAM 14680, free system stack 174 words
Tasks: NETWORK(ready,446) HEAT(blocked,306) DUEX(blocked,31) MAIN(running,409) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 01:13:20 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 14680, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 36.0, current 36.2, max 36.8
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 5.11ms; fastest: 0.21ms
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
Heater 1 is on, I-accum = 0.0
=== 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.33ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is changingMode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 5
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 0, 0.00 reads/min
ok
It does have a PanelDue connected to it and working.
Hello everyone!
I've bought a Duet 2 Wifi board and I'm facing an issue which after googling and looking into this forum apparently ends up in a defective wifi module of my board. Been told to open this post for support so here it is.
It gives me the following error:
M552 S1
ok
WiFi module started
Error: Failed to initialise WiFi module: SPI timeout
And when I try to update the WifiServer it gives following error:
M21 M111 P14 S1 M997 S1
T:19.6 /0.0 T0:19.6 /0.0 B:19.9 /0.0
SDHC card mounted in slot 0, capacity 7.95Gb
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) LinuxInterface(16) CAN(17)
T:19.4 /0.0 T0:19.4 /0.0 B:20.0 /0.0
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
Thanks and regards.