DWC 1.21.1 not staying connected or saving files.

Milesy · 17 Jun 2018, 16:16

So I have had some issues with DWC 1.21.1 and sorted them, so i feel this is more of a "bug report"

The first is that it would only stay connected for very short periods of time and on re-connection "machine status" and "Heater temps" would only update sporadically.

Also I could not save/update any filament configuration files or macros.

All of this was solved by rolling back to 1.21 although this could not be done via DWC as it just reported errors when uploading the zip file.

Since going back to 1.21 it seems that the wifi connection is more stable.

dc42 · 17 Jun 2018, 19:10

Which Duet are you using?

Milesy · 17 Jun 2018, 21:56

I have the duetwifi.

dc42 · 18 Jun 2018, 08:05

I guess you mean you upgraded to firmware 2.0 then? There isn't a firmware 1.21.1 for the Duet WiFi.

Milesy · 18 Jun 2018, 12:42

Yes. I upgraded to 2.0 and as far as I can tell there are no problems with it.

My issues are with the DuetWebControl-1.21.1.zip and the problems that has had in my origional post. I am now doubting if I should have used this at all?

dc42 · 18 Jun 2018, 12:54

Does reverting to Duet Web Control 1.21 help?

Milesy · 18 Jun 2018, 13:02

Reverting back to 1.21 solves all the issues and anecdotally my WiFi connection has improved.

zerspaner_gerd · 18 Jun 2018, 13:11

A small remedy for me if I increase the AJAX retries to 3.
But as stable as DWC 1.21 it does not work for me either. (see beta thread of 2.0)
I hope it will be even improved!

deadwood83 · 20 Jun 2018, 03:22

Same issue here.
Reverted to DWC1.21 as a test.

When 1.21.1 stopped responding, I captured this from ctrl+shift+j

XML Parsing Error: no root element found
Location: http://10.10.30.86/rr_download?name=0:/sys/oem.json
Line Number 7, Column 1: rr_download:7:1
Use of nsIFile in content process is deprecated. NetUtil.jsm:302:12
Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4
Use of nsIFile in content process is deprecated. NetUtil.jsm:302:12
Removed unsafe attribute. Element: svg. Attribute: xlink. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: xmlns. react-dom.js:11623:4
Removed unsafe attribute. Element: svg. Attribute: version. react-dom.js:11623:4
Error: WebExtension context not found! ExtensionParent.jsm:861:13

On average, I would have 10-15 seconds to perform an action before everything stopped responding. I even got to the point of using an Asus RT-N16 as a wireless AP on my second VLAN (10.10.30.0/24 for wireless clients) wired to my trunked switch. I placed the AP in the same room about 6-7ft away. No dice on that front.

While typing this, I popped back into the machine and was able to update a macro about 3 minutes after connecting. This is a massive improvement compared to reloading DWC between each button click and pre-typing commands/macros for a copy/paste in 1.,21.1.

RTOS full release on DuetWifi. My second machine has the same issue, just not to such a great extent. Both have the "disappearing.config.g" experience.

dc42 · 20 Jun 2018, 10:17

@deadwood83 said in DWC 1.21.1 not staying connected or saving files.:

XML Parsing Error: no root element found
Location: http://10.10.30.86/rr_download?name=0:/sys/oem.json

File oem.json is not normally present, so that I think that error is ok, although a "file not found" error is more normal.

Error: WebExtension context not found! ExtensionParent.jsm:861:13

That one doesn't sound right to me. Can you have the browser break on that error and get a stack trace?