Wifi Module startup inconsistencies

patakopecek

I would say a defective duet/wifi chip, if it is original, send it back to get it replaced/repaired

dc42

Please confirm which versions of the main and the WiFi firmware you are using.

gbiski

@dc42 Sorry for the late reply but I was away from home.
The version is:

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.0(RTOS) (2018-06-05b3)
WiFi Server Version: 1.21
Web Interface Version: 1.21.1

Iamturbo1978

I too am having problems with this. I only see it if I hit emergency stop, and force the Duet to reboot. The only way I can get it back working again, is to either power reset, or push the on board reset button. I had the issue on firmware version 2.02, but I just upgraded to RC4 and I have not tested the issue yet.

Phaedrux

Have you seen this?
https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors

gbiski

@dc42 Do i have to upgrade the firmware ?

dc42

If you upgrade the main firmware to 2.02RC4 then the automatic wifi reconnection feature may help you. However, I suspect that the wifi signal strength at the Duet's antenna is too low. Please read the wiki page that @Phaedrux linked to.

gbiski

@dc42 When the wifi signal is low the wifi module does not light up when booting ?

dc42

@gbiski said in Wifi Module startup inconsistencies:

@dc42 When the wifi signal is low the wifi module does not light up when booting ?

It should still flash while it is searching for networks.

gbiski

@dc42 Mine does not. I have to reboot it 2-3 times to have it searching. It is weird.

gbiski

Can i ask something not relevant to my issue ? I am thinking upgrading my CR10s with a Duet ethernet. I will use the same power supply of the CR10s. Can i connect directly the bed to the Duet or do i need a mosfet ? Or i must use the mosfet of the CR10s ?

dc42

@gbiski said in Wifi Module startup inconsistencies:

@dc42 Mine does not. I have to reboot it 2-3 times to have it searching. It is weird.

When it has failed to start up, if you send M552 via USB (or PanelDue if you have one), what is the response?

gbiski

@dc42 Hello,
It says:
WiFi module is idle

dc42

Please post yor config.g file.

gbiski

@dc42 Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Nov 23 2018 11:29:23 GMT+0200 (EET)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 P"Dark Printer" ; Set machine name
M551 P"3369: ; Set password
M552 S1 ; Enable network
M587 S"Dark" P"*****" I192.168.1.42 J192.168.1.1 K255.255.255.0 ; 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 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X160.00 Y160.00 Z800.00 E837.00 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z600.00 E1500.00 ; Set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z50.00 E5000.00 ; Set accelerations (mm/s^2)
M906 X1150.00 Y1150.00 Z1250.00 E1150.00 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 X160 Y160 Z200 S0 ; Set axis maxima

; Endstops
M574 Z1 S0 ; Set active low endstops
M574 X1 Y2 S1 ; Set active high endstops

; Z-Probe
M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z1.9 ; Set Z probe trigger value, offset and trigger height
M557 X0:0 Y0:0 S20 ; Define mesh grid

; Heaters
M305 P0 T100000 B3950 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4388 C7.060000e-8 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-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 ; 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

; Automatic power saving
M911 S10 R11 P"M911 S10 R11 P”M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings are not configured

dc42

I suggest you remove the M587 command from config.g. It should only be sent when setting up the connection, not every time you start up. Leaving it in there is also a security hazard.

gbiski

@dc42 Hello,

I removed the M587.
It is much better but again not completed solved. In the 70% of the cases bow I do not need to reboot.

In addition (not because removing the M587) I have some times disconections from the http during operation. When this happens I have to just reconnect by refreshing the page and or hitting reconnect but more rarely to reboot the duet in order to gain again wifi connectivity.

dc42

Try upgrading to main firmware 2.02RC4 and DWC 1.22.5. The automatic retries may solve the remaining 30%.