Duet Wifi-Establishing Wifi connection requires multiple resets

bricor

I recently purchased a Duet Wifi. I have experience a bunch of issues which I'll report on separately.

The biggest issue I have right now is getting on my wifi network. This has been the most annoying.

The only way I can establish connection is to either send M552 S1 a minimum three times (pausing between commands) through YAT terminal session or by pressing the Reset button on the DUET also a minimum of 3 times (sometimes 4)(pausing between presses). If I initiate a reboot from the web interface (emergency stop or config file edit) I need to perform the same routine.

The board came with 1.21, I updated the firmware to 2.02RC1 hoping to solve the issue, it didn't.

Phaedrux

@bricor did you also update the wifi firmware and the DWC?

Have you seen this?

https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors

bricor

Most, if not all from that article do not seem to apply to my situation.
I have been through the steps listed that could possibly apply with no success.

Signal is strong, Duet is wired in a plastic (printed, PETG) box sitting on the work bench (wood) 200-300 mm away from the printer and 500+mm away from everything else. there are no wires running near that part of the board and there aren't any other obstacles (including a lid to the box) in the way. The box is stationary. Eitehr I have to initiate a terminal session and issue M552 S1 multiple times (3, sometimes 2, sometimes 4 usually no more than 4) or by pressing the reset button on the DUET 3 times (sometimes 2, sometimes 4 usually no more than 4) the wifi will work. I have the timing down,

press reset
after a count of 1, blue flash from wifi module
after a count of 3 second blue flash followed by steady blue
all good

if no second flash after 3 count press reset, follow procedure until led is solid

Once on the network, I rarely have issues. In fact I cant recall any issues except for the timeout message from the browser if I walk away for awhile and come back. Browser reconnects as expected when you press connect. I printed from Repetier Server over the network with no issues either, 3 hour print. I can connect anytime from multiple devices. I'ts only at boot (cold or warm)

Everything is configured as it should, I cleared out all networks and started from scratch weeks ago.

Originally I would use terminal with multiple (3 to 5) M552 S1 commands (pausing after the first blue led flash at boot waiting on the second flash and steady blue led from the wifi module).

That was really annoying so out of frustration I tried the reset button and after 3 press (possibly 4, it was a few weeks ago) the wifi came to life just like the terminal, multiple M552 S1 commands. It's easier than having to connect usb, launch termainal, ......

I'm concerned that I'll wear out the reset button or accidentally hit the ERASE button.

There are rare occasions where it works without my interaction, but <10% of the time, possibly <5%.

I use my printers daily so this is an everyday occurrence, multiple times a day since I've been configuring and dialing in the printer and firmware parameters.

dc42

@bricor said in Duet Wifi-Establishing Wifi connection requires multiple resets:

Signal is strong

How strong - when you have established a connection, what is the RSSI reported by M122?
Which version of DuetWiFiServer are you running? Look in the Settings/General page of DWC to check.
Please share your config.g file.

bricor

my apologies, i should've included them in my original post

M122
=== Network ===
Slowest loop: 14.03ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21RC4(08b3)
WiFi MAC address 5c:cf:7f:76:72:9d
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 16496
WiFi IP address 192.168.1.90
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===

bricor

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Sep 25 2018 16:48:33 GMT-0400 (Eastern Daylight Time)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
;M665 R133.969 L272.869 B110 H287.79 ; Set delta radius, diagonal rod length, printable radius and homed height
;M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them

M665 L272.869 R134.077 H287.651 B110.0 X0.735 Y0.381 Z0.000
M666 X0.107 Y-0.408 Z0.301 A0.00 B0.00

; Network
M550 PDelta2 ; Set machine name
M552 S1 ; Enable network
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 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z80 E475 ; Set steps per mm
M566 X1000 Y1000 Z1000 E300 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E3600 ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z3000 E3000 ; Set accelerations (mm/s^2)
M906 X1250 Y1250 Z1250 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S60 ; Set idle timeout

; Axis Limits
M208 Z0 S1 ; Set minimum Z

; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops

; Z-Probe
;M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
;M558 P9 H5 F120 A10 S.035 T9000 ; Set Z probe type to bltouch and the dive height + speeds
;G31 P25 X2 Y28 Z1.1 ; Set Z probe trigger value, offset and trigger height
;M557 R80 S15 ; Define mesh grid

; Heaters
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S285 ; Set temperature limit for heater 1 to 280C5

; 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
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 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 saving after power loss is not enabled

; Custom settings are not configured

; Miscellaneous
M501 ; Load saved parameters from non-volatile memory
T0 ; Select first tool

bricor

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02RC2(RTOS) (2018-09-07b2)
WiFi Server Version: 1.21RC4(08b3)
Web Interface Version: 1.21-RC4

Phaedrux

@bricor said in Duet Wifi-Establishing Wifi connection requires multiple resets:

WiFi Server Version: 1.21RC4(08b3)
Web Interface Version: 1.21-RC4

I suggest upgrading these for starters. I don't know that that would help your issue, but it's something to try.

https://github.com/dc42/RepRapFirmware/releases/download/2.02RC2/DuetWiFiServer-1.21.bin
https://github.com/dc42/RepRapFirmware/releases/download/2.02RC2/DuetWebControl-1.22.3.zip

dc42

I agree, upgrade those first.

If the problem persists, please connect USB, try sending M552 S1 a few times, and let us know what error message it reports when it fails to connect.

bricor

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02RC2(RTOS) (2018-09-07b2)
WiFi Server Version: 1.21
Web Interface Version: 1.22.3

bricor

m552 s1
ok<LF>WiFi reported error: no known networks found<LF>WiFi module is idle<LF>
m552 s1
ok<LF>WiFi reported error: no known networks found<LF>WiFi module is idle<LF>
m552 s1
ok<LF>WiFi module is connected to access point SpicyNacho, IP address 192.168.1.90<LF>

bricor

As requested I updated to the files linked in the post. Smooth and simple. No change though. at least it's consistent.

dc42

I've never see this fault reported before, and your reported signal strength looks reasonable. So I think there must either be some incompatibility between your router and the ESP-12S WiFi module, or the wifi module has an unusual fault. If you wish to ask your supplier to exchange your Duet, I will approve that.

bricor

I bought the board direct. Left over v1.03. Did I make a mistake with the going with the old board, the cost difference is insignificant I sort of feel I made a foolish purchase thinking it was a significant savings.

dc42

There are no differences in the WiFi support between 1.03 and 1.04 apart from some layout changes to reduce EMI.

bricor

That was more of a general question and (mostly) unrelated to the issue.
What is typical in this situation, did I really mess up by buying this "deal" direct?
I have to ship the board back to the UK at my expense? (i'm in the US).
or is that a question for Duet3D.com (or is that you?)

SupraGuy

I'm nit sure if this applies, but I was having trouble connecting my printer to networks other environments other than my home.

Ultimately, I told my Duet to forget all of the various networks that it thought that it knew, and put in only the 3 that I will personally use.

It comes factory configured to a wifi network, which I assume is the one that is used for testing (With a static Ip, 192.168.1.14, if memory serves) and it might have more, depending on what you've set up with M587.

Take a look at the output of M587 with no parameters. I think that it will show you all of the networks that it has stored.

you can then use M588 to have it forget some of those networks. I'd suggest that you tell it to forget everything except "SpicyNacho" and see if that clears things up.

Phaedrux

@supraguy That's actually one of the steps from the network troubleshooting wiki posted above.

If unable to connect to your wireless network at boot up, try deleting all saved wifi networks with M588 "*" (That is, using an asterix for the network name), then re-adding it with M587. For example, M587 S"networkname" P"password".

bricor

The basic network stuff has all been addressed. This is seems to be beyond that.

dc42

@bricor said in Duet Wifi-Establishing Wifi connection requires multiple resets:

That was more of a general question and (mostly) unrelated to the issue.
What is typical in this situation, did I really mess up by buying this "deal" direct?
I have to ship the board back to the UK at my expense? (i'm in the US).
or is that a question for Duet3D.com (or is that you?)

See https://www.duet3d.com/warranty.

bricor

The board has been replaced (incredibly fast) and is in operation.
Upgraded from the 1.03 to the current ver (1.04)

Out of the box, cabled, with the restored files backed up from the original board
I started a terminal session (YAT)
M587 (List stored networks)
M588 "what ever net name was there" (M588 S"*" didn't work for some reason) (cleared existing stored networks)
M587 S"SSID" P"NetPass" (set my network wifi credentials)
M552 S1 (launched wifi, obtained IP adsdress)

Found device IP and connect to DWC via Chrome

Shut power to board waited 10 count reapplied power

Same issue as the v1.03 board, no wifi (blue LED flash just after power up and ~1 count)

Pressed reset blue LED flash wait ~10 count
Pressed reset blue led flash, followed by 2 more then steady

I updated board as before, except all in one pass
Duet2CombinedFirmware.bin 2.02RC2(RTOS) (2018-09-07b2)
WiFi Server Version: 1.21RC4(08b3)
Web Interface Version: 1.21-RC4

All seems to work as it should!!!

I restarted many times and it HAS NOT repeated the behavior.

I just finished a 2 hour print and restarted the board both from the power switch and the Emergency Stop button in DWC.

So far so good.

The wifi (LED) behavior is different compared to the last board

I am also getting different print results. i have to print more to know for sure, but a model that I've been having issues with actually printed the best it has since I changed to the DUET. It has some ringing that it didn't have before but overall it's printing better. No setting changes were made. (ringing might be machine related)

dc42

I'm glad it's working.

You are running old RC versions of DuetWiFiServer and Duet Web Control. I suggest you upgrade them to released versions.

bricor

My mistake, I copied and pasted the wrong information.
I should have copied it from the DWC not from the post above.

I applied the same updates that were suggested on 10-10 by Phaedrux

This is what should be on the DUET
Firmware Version: 2.02RC2(RTOS) (2018-09-07b2)
WiFi Server Version: 1.21
Web Interface Version: 1.22.3

I will confirm these values are what is on the DUET later this afternoon.
The DWC is definitely not the old version (easy visual thing)

bricor

Thank you for your help and hard work.