Wifi module disabled at start

jay_s_uk

@haggan90 something strange going on there. can you post an output of M122 once its up and running?

Haggan90

@haggan90 OK this is super strange.. all the code in my config.g file is gone, all other code is there (like i bed.g etc.) What could heva casued this? And can I recover the config.g?

jay_s_uk

@haggan90 what board is it?

jay_s_uk

@haggan90 and unless you have a config.bak, its gone

Haggan90

@jay_s_uk Duet Wifi.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJMSJ-6JTDD-3S86L-1APHG
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93292 of which 0 recycled
Exception stack ram used: 296
Never used ram: 11772
Tasks: NETWORK(ready,628) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,4600) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:05:04 ago, cause: power up
Last software reset at 2022-09-08 07:58, reason: User, spinning module GCodes, available RAM 11812 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 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 33.0, current 33.3, max 33.3
Supply voltage: min 24.4, current 24.4, max 24.7, 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
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2022-09-08 15:44:27
Cache data hit count 920337581
Slowest loop: 1.11ms; 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 idle 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: 200.64ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
- WiFi -
Network state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address bc:dd:c2:53:09:3f
WiFi Vcc 3.32, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25704
WiFi IP address 192.168.68.77
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

jay_s_uk

@haggan90 it could be a bug in 2.05.1. I know some FTP issues were recently fixed in 3.4 that may have been present in 2.05.1
If you're going to be recreating your config, you might as well upgrade to 3.4.1

Haggan90

@jay_s_uk Aw crap... my config.g has been a constant trail and error document for years haha, finetuning and experimenting... is there no way to recover it?

Everything else on the SD-card seems to be there

jay_s_uk

@haggan90 you may be able to use some recovery software to get it back from the sd card, but otherwise, no

Haggan90

@jay_s_uk As soon as I restarted the board I lost connection again... very strange..

jay_s_uk

@haggan90 you will if you have no config.g

Phaedrux

There was a bug that could occasionally cause config.g to be lost. Upgrading to RRF 3.4+ would be recommended for many reasons. 2.05 is a few years old now.

If this is your first upgrade to RRF3 I suggest starting with a config file set from the online config tool.

https://configtool.reprapfirmware.org/Start

Haggan90

@phaedrux well I guess I have no choice now Where does the duet save the login for the WiFi?

jay_s_uk

@haggan90 to the ESP (WiFi chip) flash

Haggan90

@jay_s_uk Aha ok, so it's not stored in the config.g file then?

Phaedrux

No, but the config file needs to have M552 S1 to enable the module at startup.

Haggan90

@phaedrux Hi,

I've been trying to migrate to RR3 for a coupple of days now but I just can't get it to work..
I've been using the config tool, but I can't see any diffrence in the gcode compared to my old config file, should it be so?

I can't even home any of the axis...

This is my config.g file atm.

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.12 on Wed Sep 14 2022 08:24:17 GMT+0200 (centraleuropeisk sommartid)

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"My Printer test cartesian"       ; set printer name

; Network

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

; Drives
M584 X6 Y1 Z2:5:4 E3			; set 3 Z drivers 
M569 P1 S0                              ; Drive 1 goes backwards
M569 P2 S0                              ; Drive 2 goes backwards
M569 P3 S1                              ; Drive 3 goes forwards
M569 P4 S1                              ; Drive 4 goes forwards
M569 P5 S0                              ; Drive 5 goes backwards
M569 P6 S1                              ; Drive 6 goes forwards

; Defining X and Y coordinates of the leadscrews

M671 X-80:580:580 Y245:490:0 S5 	; leadscrews at front right, rear right and middle left

M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation
M92 X80.00 Y240.00 Z200.00 E415.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 X800 Y800 Z800 E800 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 X500 Y500 Z700 S0                  ; set axis maxima

; Endstops
M574 X1 S0				; Set active low endstops  
M574 XY S1                          	; set active high endstops
M574 Z1 S2                              ; set endstops controlled by probe

; Z-Probe
M307 H3 A-1 C-1 D-1                     ; disable heater on PWM channel for BLTouch
M558 P9 H5 F650 T9000                   ; set Z probe type to bltouch and the dive height + speeds
G31 P50 X0 Y0 Z4.5                   	; set Z probe trigger value, offset and trigger height
M557 X0:500 Y0:400 S100	                ; define mesh grid

; Heaters
M307 H0 B0 S1.00                        ; disable bang-bang mode for the bed heater and set PWM limit
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.3 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 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

Phaedrux

@haggan90 said in Wifi module disabled at start:

I've been using the config tool, but I can't see any diffrence in the gcode compared to my old config file, should it be so?

This config is still for RRF2. Did you select RRF3 in the config tool on the first page?

; Configuration file for Duet WiFi (firmware version 1.21)

On the General tab, at the top, firmware version drop down should be 3.3 or later.

Haggan90

@phaedrux Ah, thanks!
Now I got it working, finaly!
I do have some problems with the endstops, sometimes they work and sometimes not.

dc42

@haggan90 thanks, I'll mark this as solved. If you don't resolve the issues with the endstops, please start a separate thread for that.