Duet 2 WiFi - Web Control Connection Issues

tec_bamm

Hi guys! New to the forum.

Setting up our large scale 3D printer, using the DuetWiFi with the Duex5 extension. We had some trouble connecting it to our office network (WiFi connects, but IP address that's stated on YAT and console doesn't exist on our network), and I tried to connect it using M587.

To remove and add networks, I do M588 S"" and M589 S"", then I re-enter the network IDs through M587 S"XXXX" P"XXXX" Ixxxx Jxxxx Kxxxx. I reset the WiFi module M552 S0 and S1.

On the other hand, we connected it to a tethered phone, through the same means, which worked, but the Duet Web through my local 192.168.x.xx IP disconnects a few seconds after it's been connected to the board.
On the LCD screen we have, Console is saying that we are experiencing a "WiFi reported error: incomplete write".

Can anyone please advise on what to do, since it seems like we're going around in circles with our current process.

dc42

Are you sure that the IP address you are specifying in the M587 command is available on your office network? It needs to be on the same subnet, and not already in use. It's usually better not to specify an IP address and let your router allocate one using DHCP.
Is it a small office WiFi network, or a corporate network? Some corporate networks require a logon procedure that is not supported by the Fuet WiFi.
Regarding the "incomplete write" error, please connect YAT and send M122, then report the main firmware version and WiFi firmware version from the report.

tec_bamm

1: Yes. I know all of the used IP addresses on the network, and our Duet is connecting to an unused IP. It was initially done, not specifying an IP address through DHCP, but it still doesn't appear on our office router. Since it never managed to connect to it through automatic means, I entered manual numbers, which still doesn't appear to run the Web Server.

2: It's a small office WiFi network. The router we're connecting it to doesn't require the corporate login.

3: I shall report to you what M122 states. I am hoping that it's both at 1.21. I'll reply with the M122 results in a few minutes.

There are only two problems right now though:
1: It cannot connect to our office WiFi
2: It connects to my tethered phone, although it drops after 30 seconds, after successfully connecting, so config.g is inaccessible from the timeframe that it's active.

tec_bamm

@dc42 Do you perhaps know how to split the lines on YAT? M122 only separates them with <LF> but keeps on going the single line. It now says that I've run out of bytes.

tec_bamm

=== Diagnostics ===
Used output buffers: 1 of 32 (3 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDD-3SD6J-93YHX
Static ram used: 16152
Dynamic ram used: 101400
Recycled dynamic ram: 1232
Stack ram used: 3576 current, 4420 maximum
Never used ram: 7868
Last reset 00:00:11 ago, cause: power up
Last software reset at 2018-09-03 17:47, reason: User, spinning module GCodes, available RAM 7484 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00433000, BFAR 0xe000ed38, SP 0xffffffff
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 29.3, current 32.7, max 32.8
Supply voltage: min 0.1, current 0.7, max 0.8, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not
<Warning: Maximal number of bytes per line exceeded! Check the end-of-line settings or increase the limit in the advanced terminal settings.>

I just separated the <LF>s manually so you can see it more clearly, but that's all that the lines give me. I notice it saying DuetWiFi 1.02, but I really don't recall even touching that version on the downloads list. Does that mean that I've forgotten a file and it didn't install when I did M997 S0:1:2?

dc42

@tec_bamm said in Duet 2 WiFi - Web Control Connection Issues:

@dc42 Do you perhaps know how to split the lines on YAT? M122 only separates them with <LF> but keeps on going the single line. It now says that I've run out of bytes.

In the YAT text settings, change the line ending to LF only.

The WiFi firmware version comes later in the report.

tec_bamm

Ok. I shall find out what the full M122 says. Thank you for the reply!

tec_bamm

@dc42 Here is what comes up with M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDD-3SD6J-93YHX
Used output buffers: 1 of 20 (3 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 97128 of which 16 recycled
Exception stack ram used: 272
Never used ram: 5180
Tasks: NETWORK(ready,1276) HEAT(blocked,1248) MAIN(running,3484)
Owned mutexes:
=== Platform ===
Last reset 00:02:54 ago, cause: reset button or watchdog
Last software reset at 2018-09-07 15:05, reason: User, spinning module GCodes, available RAM 4940 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00417000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
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 38.4, max 38.4
Supply voltage: min 0.4, current 0.7, max 0.8, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Expansion motor(s) stall indication: no
Date/time: 1970-01-01 00:00:00
Slowest loop: 43.89ms; fastest: 0.06ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 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 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 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 ===
Slowest loop: 14.22ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 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.21
WiFi MAC address 5c:cf:7f:a4:a5:be
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17032
WiFi IP address 192.168.1.134
WiFi signal strength -67dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
DueX I2C errors 0

dc42

Thanks. Your firmware is up to date with latest stable release. Please upload and re-install DuetWiFiServer.bin from the 2.01 release area (https://github.com/dc42/RepRapFirmware/releases/tag/2.01) and see if that fixes the "incomplete write" error. If it doesn't then ask for your Duet to be replaced under warranty.

tec_bamm

Thank you for your reply! I completely forgot to re-name the file inside the sys file for the WiFi Server, previously, so it never managed to install it at all.

I have reset the board once more and performed the M997 S0:1:2 for the complete reinstall.

I'm currently trying to load the web server, but it's taking a long while to load up. Once it's fully loaded up, I'll have a check on its connection reliability, so you're also up-to-date with the information. I hope this does

Is it normal for the Duet Web Server to take ages to load upon first boot? Everytime I do M552 S0 and S1 now, it times out while trying to connect, unless I've done S1 twice.

[EDIT]

Ok, I found out why my web server was taking ages... It was because my phone was updating apps in the background, hindering the local tether bandwidth. I've disabled it now, and the web server loaded instantly - so at least that's sorted.

[EDIT 2]

So far, no disconnections have happened. It's been connected for nearly 10 minutes now, which broke it's old record of an uptime of 30 seconds, so good news as of now. I will create an Edit 3 once I have further analysis.

[EDIT 3]

It's been connected for over 30 minutes now! That's done the charm! Now it's time to sort out the configs for the printer, then I will work out on how to connect it to our office WiFi.