New beta Duet WiFi firmware bundle
-
Can somebody try to dump network traffic using Wireshark to and from DuetWiFi board with this ajax timeouts issues?
-
All, when you get the ajax timeouts can you please report if you are able to reconnect or if you have to reset/reboot the Duet board please. In my case, once I get the timeout I can not reconnect even if I try from a completely different browser or computer.
I am doing a fresh re-install of the original pre-production binaries as I type and I will capture the network traffic with Wireshark too.
-
All, I have reverted back to the pre-production code and captured a complete trace with Wireshark. The link to the trace and details are on my thread here: https://www.duet3d.com/forum/thread.php?pid=578#p578
-
I get more problem of ajax time out, usualy i can reconnect but few minutes ago i had to unplug the printer due to an emergency !
How to use wireshark ? I installed it but i do not know what to enter…I 'm getting this time out mainly when i upload a file to the printer. I've to redo the upload with a new file name otherwise it doesn't work. Also i notice it crash when the upload didn't start at full speed.
-
Learning how to use Wireshark is not terribly difficult. Basically, after launching you need to select the interface to watch - in this case, WiFi. Then you need to apply a filter for IP address to capture traffic from, otherwise you get a lot of extraneous info. You can just capture everything and we can filter out stuff from the log too but I prefer to set a filter. My filter looks like:
ip.addr == 192.168.1.242
Your IP will be different (your Duet WiFi IP - get it from Pronterface when you issue a M552 S1)
By the way, I have discovered that once I get the comm failure I can turn off and then turn on WIFI in Printerface and it will reconnect:
M552 S0
M552 S1I get the time out even if I connect and just sit there and watch with no activity. Try that and see what happens, I bet you'll timeout too.
-
I am able to reconnect, however I get dropped again after not too long (particularly when in the middle of a print).
-
I installed and get wireshark listening my duet, to be sure i reinstalled the last bundle firmware but no timeout connection since 10min
-
No problems with the update for me, all installed fine.
The print motion looks different to me, I can't quite put my finger on exactly what it is, but almost like accelerations have slowed down very slightly or maybe smoothed, but it may be just be me remembering what it was like in the last release.
Anyone see or 'feel' and difference?
Producing very good print results, so I'm happy.
Cheers,
Rich.
-
I cannot confirm that the motion is slower in this new version but i notice a hudge difference when the model is like a low polygonal model with straight path than a curvy model. My extruder was clicking at 200mm/s on the polygonal and i've to slow down to 150 to get it work correctly, the hotend temperature was insanely high for PLA and on the curvy model with near the same loop length and without short curve, no problem.
Did you feel this on the same model ?
-
I've upgraded without any obvious issues and been connected on and off for 6 hours so far via the web page though no actual prints yet
Upgrade was done via the web page for all the modules without any issues.
-
David, I've been keeping statistics on disconnects the last few of days and been monitoring my network for the last day. Firstly, the original network issues that were antagonizing my original issue are gone so that is no longer a factor.
My other 5 deltas are running Duet with a TP-Link wifi bridge and Duet Wifi are all on the same network. The other 5 are running 1.09z-ch firmware and 1.11 HTML and JS.
In 72 hrs I've had 1 of the 5 disconnect one time but the other 4 have stayed connected (both printing and sitting idle over night) for 3 days.
The Duet WiFi has disconnected 8 times in the same time period. The good news is, a simple click of Connect and it reconnects quickly.
-
Michael, can you confirm that you are running DWC 1.11b-dc42 on the Duet WiFi?
One of the items in the firmware plan is to rewrite the web server running on the ESP, using the Duet web server as a basis. That will hopefully reduce the disconnection rate further.
-
This update seems to have resolved the timeout problem for me, 4 hours in without a disconnect.
How is the notification timeout supposed to work? Mine still don't auto-dismiss. Is it possible to make an option in the settings that when selected only shows the most recent notification instead of filling the whole browser window?
-
If I'm having to copy the DuetWiFiServer file onto the SD card by plugging it into my computer, what command do I need to run to ensure it gets installed?
-
David, I'm running 1.15-beta3 (2016-07-09) firmware on Duet WiFI
This machine has disconnected 3 times in the last 24 hrs since my report yesterday. My other 5 deltas running earlier Duets have not disconnected in the last 24 hrs. So to recap 96 hrs (4 days) I've only had 1 disconnect on a Duet 0.6 with a wifi bridge out of 5 printers total so:
Earlier Duets with WIFI bridges: 1 disconnect in (96hrs * 5 printers) = 1 disconnect in 480 hrs
Duet Wifi: 11 disconnects in 96 hrs -
Update: 12 hours in, no disconnect error. Definitely the longest I've gone without a disconnect timeout, thanks David!
-
David, I'm running 1.15-beta3 (2016-07-09) firmware on Duet WiFI
This machine has disconnected 3 times in the last 24 hrs since my report yesterday. My other 5 deltas running earlier Duets have not disconnected in the last 24 hrs. So to recap 96 hrs (4 days) I've only had 1 disconnect on a Duet 0.6 with a wifi bridge out of 5 printers total so:
Earlier Duets with WIFI bridges: 1 disconnect in (96hrs * 5 printers) = 1 disconnect in 480 hrs
Duet Wifi: 11 disconnects in 96 hrsIt was the version of Duet Web Control that I wanted to know.
-
Duet Web Control HTML: 1.11b-dc42, JS: 1.11b-dc42
