@Jarery:

Looking back I think everyone with issues reported using routers with Merlins firmware? Perhaps anyone with Ajax disconnect issues who is running stock firmware on their router could confirm/deny.

Researching Asus routers that drop wireless clients, one thread had success turning off beamforming. In Merlins firmware there are two beamforming settings under "Professional" tab, Explicit and Universal.
Another thread reported wireless client issues dropping with both Merlins and stock firmware but problem cleared when they used DD-WRT firmware.

Last night I turned off both beamforming options. My system has stayed connected overnight. I wont be able to run it through any prints till tomorrow, but perhaps some others with the issue capable of printing sooner could also test and let us know prior to that.

If this route fails I'll start messing with other router firmware. If anyone with issues is using dd-wrt firmware please let me know so i don't go down that path unnecessarily.

the router connected to the duet is running dd-wrt and yes i'm also having the Ajax disconnects since a couple of versions. it seems that after the Ajax disconnect the router and connection is still alive (or back) since i can ping and nmap shows the open port. however the when connecting via http i get an instant disconnect (see my post earlier in this thread)

the server is still in the network and http seems to be there but a request instantly dies

Uwes-MBP-3:Edge uwe$ nmap 192.168.178.36

Starting Nmap 7.40 ( https://nmap.org ) at 2017-10-27 19:52 CEST
Nmap scan report for duet.fritz.box (192.168.178.36)
Host is up (0.056s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
80/tcp open http

Nmap done: 1 IP address (1 host up) scanned in 1.31 seconds
Uwes-MBP-3:Edge uwe$ nmap 192.168.178.36

Starting Nmap 7.40 ( https://nmap.org ) at 2017-10-27 19:52 CEST
Nmap scan report for duet.fritz.box (192.168.178.36)
Host is up (0.047s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
80/tcp open http

Nmap done: 1 IP address (1 host up) scanned in 2.66 seconds
Uwes-MBP-3:Edge uwe$ wget 192.168.178.36
–2017-10-27 19:53:04-- http://192.168.178.36/
Connecting to 192.168.178.36:80… connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

i hate to join this thread but i started to see Ajax disconnects in the recent versions. today i'm getting just disconnects within minutes. switching printer on (heat bed+heat hotted) end disconnect. the board is alive via usb and can be pinged. i attach the m122 logs

M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (20 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-MQ4S4-6J1FG-3S06T-T5H3Z
Static ram used: 21176
Dynamic ram used: 96064
Recycled dynamic ram: 1544
Stack ram used: 4008 current, 4840 maximum
Never used ram: 7448
Last reset 00:03:38 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7448 bytes (slot 0)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
[ERROR] 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 14.3, current 18.9, max 19.5
Supply voltage: min 16.2, current 18.7, max 19.1, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-10-27 19:28:11
Slowest main loop (seconds): 0.015995; fastest: 0.000034
=== Move ===
MaxReps: 3, StepErrors: 0, FreeDm: 240, MinFreeDm 234, MaxWait: 717ms, Underruns: 0, 0
Scheduled moves: 5, completed moves: 5
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
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.1
=== GCodes ===
Segments left: 0
Stack records: 2 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 running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:2b:e7:ae
WiFi Vcc 3.12, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 40232
WiFi IP address 192.168.178.36
WiFi signal strength -50dBm
HTTP sessions: 1 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)

M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (24 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-MQ4S4-6J1FG-3S06T-T5H3Z
Static ram used: 21176
Dynamic ram used: 96128
Recycled dynamic ram: 1480
Stack ram used: 4008 current, 6156 maximum
Never used ram: 6132
Last reset 00:02:27 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 7208 bytes (slot 1)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
[ERROR] Error status: 0

Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 456.1ms
MCU temperature: min 18.5, current 19.4, max 21.2
Supply voltage: min 18.0, current 18.5, max 19.2, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-10-27 19:33:47
Slowest main loop (seconds): 0.457424; fastest: 0.000035
=== 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
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.1
=== GCodes ===
Segments left: 0
Stack records: 2 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 running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:2b:e7:ae
WiFi Vcc 3.12, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39352
WiFi IP address 192.168.178.36
WiFi signal strength -51dBm
HTTP sessions: 1 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)

if i understand it right there are fees involved with pushover. so far i have been using octoprint's telegram messaging which works great not just as messaging but also to control octo+the printer

hahahahaha seems i earned this weekends looser price

for your entertainment: while upgrading i installed a fuse between psu and duet. that fuse is in a little box with an LED. actually the fuse should be in the box

essentially the duet got enough power to light the vin led but that was only what came via the addon led of the fuse. once i installed the fuse all is as expected

regards

where is the 5v regulator on the board?

i will send a few snaps in a minute

yes they look like this

with usb plugged i see 5v+3.3v leds on.

hi,

just about to install a new duet wifi v1.01…

is it expected that the 5v and 3.3v leds are only on when the 5v rail gets external 5v via a psu/usb? i have 24v connected to vin and only see the vin (blue) led and i also have the feeling that the 5v and 3.3 v rails are not powered (no connect etc).

btw i have the jumper INT_5V_EN set

regards
/uwe