New test firmware 1.19+4 and DuetWiFiServer 1.19+1
-
Thanks for the reply
Both the suggestions I have been using since the beginning of my issues:
- I've set my modem to a fixed channel from earlier suggestions
- i've always been using 16x with interpolation (0.9 steppers)
I've had macpronterface hooked up while i print and its disconnected. Running M122 on it after i lose web browser connection, the output ri posted above.
Perhaps I don't understand your instructions of " see what reconnection messages are written to USB" as i see no messages mirrored to the usb when it disconnects and as mentioned the M122 output is as i posted above where it states reconnections 0. Is there a different command you want me to run via usb after it disconnects?My Settings:General are as per default, ajax retries 5 (I've boosted to 10 with no effect),
-
Are you definitely running version 1.19.2 of DuetWiFiServer as well as version 1.19.2 of DuetWiFiFirmware? Look in the Settings General tab to check.
-
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19.2 (2017-09-01)
WiFi Server Version: 1.19.2
Web Interface Version: 1.19 -
If the WiFi module has disconnected from your router then it should write a message to USB saying so and giving progress information about the reconnection attempt. This was new in 1.19.2.
-
Is the "File Information" section of the web page getting information from the firmware or purely on the web server side of things? How is it identifying layers if on the firmware? Mine is currently reporting 0.35mm layer thickness, which is only the first layer. I have however stripped a lot of code out of the gcode file to stop it using heat, and might have accidentally stripped what it is using to identify layers!
Edit: Nuts. Just seen the rc5 release… Will upgrade after testing the time estimation.
-
Late report on the build time estimation! This is a test build with no heat. Works fine for me.
Actual build time: 2hr20m36s
Time to run the simulation: 0hr5m30s
Predicted build time: 2hr2125.6 times quicker than build time on a Duet 0.6. I'll run a similar test on the DuetWifi at home soon. Guess I could just run the simulation and use this machine's config file temporarily.
Edit: Running the above again in 1.19+5 (2017-08-30) Will report on that thread.
-
Please use the 1.19.2 release from https://github.com/dc42/RepRapFirmware/releases, not the older +5 release.
The file information is provided by the firmware.
The Duet WiFi has a faster processor than the 0.6 so it should run the simulation faster.
-
Thanks. Will do - after the current test has completed. Didn't spot the 19.2 release.
-
If the WiFi module has disconnected from your router then it should write a message to USB saying so and giving progress information about the reconnection attempt. This was new in 1.19.2.
Doing a mesh bed calibration it disconnects mid way through. No output or messages on MacPronterface which was connected via serial at the time. I get no messages via serial at all unless I type a command to get a response.
On the MacPronterface if I do a M122 I get the following Wifi section:
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19.2
WiFi MAC address 5c:cf:7f:a4:a1:64
WiFi Vcc 3.13, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39840
WiFi IP address 192.168.2.54
WiFi signal strength -38dBm
Reconnections 0
HTTP sessions: 1 of 8
Socket states: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)Trying to reconnect via browser that was open previously is " Error, Could not establish a connection to the Duet firmware! Please check your settings and try again" repeatedly, unable to reconnect.
Opening a new browser, to check Router (Asus AC3100) I see its connected and assigned an IP. Clicking on IP within router browser its unable to open a new window, it just times out.
-
That sounds like a different failure mode (connection stable but messages not getting through). Try enabling Webserver and Network debugging using M111, then see whether the failed attempts to open a session in a browser give rise to any debug messages in Pronterface.
-
heres whats the serial connection reports after after a disconnect :
HTTP connection accepted
Found responder
Received 394 bytes
Sending reply, file = no
HTTP req, command words { GET /rr_status HTTP/1.1 }, parameters { type=3 }
New conn on socket 0 for local port 80
HTTP connection accepted
Found responder
Received 394 bytes
Sending reply, file = no
HTTP req, command words { GET /rr_status HTTP/1.1 }, parameters { type=3 }
New conn on socket 0 for local port 80
HTTP connection accepted
Found responder
Received 394 bytes
Sending reply, file = no
HTTP req, command words { GET /rr_status HTTP/1.1 }, parameters { type=3 }
Class Network spinning.
Class Network spinning.
Class Network spinning. -
According to that, the Duet appears to be behaving correctly. Can you get a Wireshark trace of the network traffic?
-
That is beyond my current level of network troubleshooting ability…
Once it disconnects, My web browser just repeatedly states it cannot connect, and the serial output is :
Class Network spinning.
Class Network spinning.
Class Network spinning.
Class Network spinning.
File DuetWifi_Wiring_Box.gcode print time was 5h 8m
Class Network spinning.
Class Network spinning.
Class Network spinning.
Class Network spinning. -
Sounds like the WiFi module has stopped responding. Sending M552 S-1 to reset it followed by M552 S1 to reconnect may get it working again, but that doesn't solve the problem.
-
Noticed that my PanelDue 7 flashes now every second or so. didnt do this before.. not sure whats causing it.
-
If you mean the backlight flashes on and off, or isn't a steady brightness, that's common if you try to power a 7" PanelDue from USB power only. A standard 500mA USB port can't provide enough current for the 7" display.
-
Sounds like the WiFi module has stopped responding. Sending M552 S-1 to reset it followed by M552 S1 to reconnect may get it working again, but that doesn't solve the problem.
This helps occasionally.
After initial power on, once connected it seems to remain connected until I print. I have yet to have a print go beyond 15-20 min and stay connected since the update from 1.18I have a macro that disconnects wifi and reactivates so after it loses connection I can attempt to reacquire. I have maybe 50-50 success rate. Many times, doing this still I am unable to require web browser. The only sure fire way is to power completely off, unplug serial if connected, and power back up. Even if i do reacquire connection mid print using this method (macro not reboot) it disconnects again after a period of time.
My router shows ip assigned the entire time.
Safari, chrome, etc, browser has no change.
-
If you run M122 after a print, what MaxReps value does it give?
-
Tested during a print last night.
Disconnected 5 or 6 times I believe. Near the end of the print after I reconnected (by using M552 S-1, M552 S1) it stated MaxReps 5.
After print completed when I connect and do a M122 it says MaxReps 4. -
That value is nice and low, so it looks like excessive step pulse rate isn't a factor.
