DWC crashing; repeatedly
-
also having a lot of problem with wifi and the betas
timo outs or can't connect
start to get very frustrating
Please prioritize this -
I am pleased to report that with the latest betas (Firmware 1.19beta10+2, WiFi Server 1.19beta9, and DWC 1.17+2) my Wifi and Ajax connection problems have largely gone away and I can connect and stay connected pretty reliably. This was a major problem for me the past month or so in previous releases and I was almost ready to bail it had gotten so unusable. Thanks for getting it fixed!
-
I'm also getting the following error on occasion now. Is this just due to less than great wifi too?
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:
Message: Uncaught TypeError: Cannot read property 'axesHomed' of undefined
URL: http://10.0.0.115/js/dwc.js
Line: 763:69
Error object: {}I think I spoke too soon about my issue with disconnecting after files have been uploaded. Regardless of that, the beta firmware still seems more sensitive to changes in wifi strength than previous versions.
-
Hi everyone,
I have something for you to try to see if it helps (it worked for me though DC42 does not know what change couldnhave lead to this)
After upgrading to the beta versions i had the same issue, i could not stay connected. What I did and now rarely get disconnected is delete the DHCP lease from the router and reboot the router then readd the assigned ip via mac address and reboot again
after doing this things have been much smoother.
-
Hi everyone,
I have something for you to try to see if it helps (it worked for me though DC42 does not know what change couldnhave lead to this)
After upgrading to the beta versions i had the same issue, i could not stay connected. What I did and now rarely get disconnected is delete the DHCP lease from the router and reboot the router then readd the assigned ip via mac address and reboot again
after doing this things have been much smoother.
I'll have to give that a try when our IT guy is in. Fortunately, I am building this machine for work. Unfortunately, I don't have much freedom to go and make changes to the network.
I have updated to the 10+2 firmware and though it seems my wifi signal is maybe a little better, the issues still prevail.
I'm also going to make a bracket and cut some holes to allow my wifi antenna to protrude through the wall of my control box.
-
Was finally able to get an AP set up next to the machine. The WiFi signal is now -45dbm which has improved the stability of my connection when I am simply looking at the control screen and issuing manual commands.
When I try to go to the gcode files tab, the files will be greyed out and the connection is quickly dropped. If I attempt to upload a file through this interface, it usually fails to upload and drops the connection. However, using the "Upload and Print" button works alright. Even if the connection gets dropped, the machine starts the print and I can reconnect to see the status screen. This typically gets very unstable eventually as well and often ends up with me not being able to connect at all.
Additionally, it seems that some part of the Duet is having a difficult time computing the layer height, as it generally is never actually calculated and if it is, it calculates two, the second one is usually because I use a Z offset in the slicer, or maybe only one. I'm using the newest beta of Kisslicer. Is the Duet having difficulty in parsing information from files and causing these issues? If there is something I can test to help determine a cause please let me know.
-
BMMal, if you are running older beta firmware then please upgrade to the latest betas (DuetWiFiFirmware 1.19beta11, DuetWiFiServer 1.19beta10 and DWC 1.17+2). If after that you still have problems, here are some suggestions:
- another user reported that changing WiFi channel on the router made a big difference
- if you can capture a Wireshark trace of what happens when you try to get the Gcode files list, that may help us diagnose the problem.
HTH David
-
Thanks for the suggestion David. I will have to try changing the channel tomorrow. For now here is a couple wireshark captures.
https://www.dropbox.com/sh/lubl3jzp2jffil8/AAAafAxwGmdWUMUaJKus4bd2a?dl=0
-
BMMal, thanks for the captures. Are you running the latest betas as listed in my previous email?
It looks like it is having problems retrieving file info for file HandlePommel.gcode. Please can you put that file on Dropbox for me to try. Also, try deleting that file from the SD card, to see if it has the same problem on the next file.
-
David,
I believe I am running all of the newest available:
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0 + DueX5
Firmware Version: 1.19beta11 (2017-07-25)
WiFi Server Version: 1.19beta10
Web Interface Version: 1.17+2I have added the file and another one to the Dropbox folder. I have noticed it producing similar error messages in the Repetier log (for several different files) when I resorted to using Repetier to start prints from SD because DWC was crashing so much and I did not have a Panel Due at the time. I am not using the SD card on the Panel Due. This issue has persisted after deleting, reuploading (if it works), or otherwise directly adding them to the card. Often times the behavior changes after resetting the board where the file name will be read but often the other statistics/info are still missing. Generally, after a reset the Panel Due can then see the file and start it but I often still cannot get the file to start from DWC. Thank you for the help!
-
Thanks. I've uploaded the file to one of my printers and DWC gets the file info over WiFi without difficulty. It failed to find the layer height because it was given too far down the file, so I've just fixed that in the forthcoming 1.19RC1 firmware.
-
By using a phone app to see which WiFi channel has the strongest signal, I was able to purposefully change it to broadcast on the strongest one. This boosted the Duet's signal from -45dbm to -25dbm. But this has not yet resolved my issue. For now I will probably wait until 1.19RC1 is released and see if that helps.
-
It seems that since I updated to 1.19 RC1 these poor behaviors have greatly improved and possibly disappeared.
