New beta Duet WiFi firmware bundle
-
Brian, I suspect you did not select the board in SAM-BA as described on the wiki page. The board should be atsam91sam4e8-ek. I got that exact dialog the first time I tried it and had not set the board.
-
Brian. you mentioned ajax disconnects. Can you describe what's happening please. I was rock stable for the first couple of days I installed the Duet WiFI then yesterday I attempted to upload a modified DWC.bin and I can't stay connected for more than a few seconds before I get disconnected. Is this what's happening in your case?
-
@mrhackney
This is what I have the settings at before clicking connect:
I've been having a massive amount of ajax disconnects ever since I connected to a secondary wireless network, while I had only ever connected to one network it was rock solid and I never had any disconnects (1.13 firmware), since changing network or updating firmware I get disconnects all the time (on 1.14 firmware).
I was hoping that upgrading to this beta version may help, but it's left me with an unusable printer at the moment
thats what I get for being brave I guess.. 
-
Brian & Michael,
I'm sorry to hear that you have both been experiencing problems since installing new firmware. If you want to revert to the original firmware that was installed on the pre-production boards when they were shipped, you can find it here: https://www.dropbox.com/sh/lf9sgndzmoiepas/AACn6NS8GuPjvoikQ7xF8zY6a?dl=0.
If that gets it working well again over an extended period of time, please try upgrading either the main firmware (DuetWiFiFirmware.bin, installed using M997 S0) or DuetWebControl.bin (installed using M993 S2) and see if it is still reliable.
If you encounter any instances of web interface disconnects and then you find that you can't reconnect, then first try closing the browser tab and connecting in a new one, in case DuetWebControl has got into a state it can't recover from. If that doesn't work, then if possible open your router's status page showing connected wireless devices, and see if the Duet WiFi is still connected. Currently, if your router kicks the Duet off the network, it won't attempt to reconnect unless you stop and re-start the WiFi module. I will fix this in the next DuetWiFiServer release.
-
I just tried again and for some reason SAM-BA worked this time.. was able to reflash with the beta version and PanelDue and the web interface are connecting now!
-
Hi,
This new version works well for me (window 7 64b).
There is a little bug in the duet web control, it's not possible to replace a file even if you delete it before trying to upload it.
I've to rename it. Deconnecting from the session doesn't solve this for me. -
I'm still getting web interface ajax timeouts with this version.
-
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?