Firmware 1.19+3 (1.19.1 release candidate)
-
+1 was fine, +3 repeats the same response since last console command as a UI notification. Is there an update to the web interface, too?
There is no update to the web interface. Please can you explain more clearly what you think has changed.
-
During printing the last console message is repeated. In this case I was checking the motors currents (I've typed M906 once).
-
Is that a behaviour that you can reproduce? Does it also happen if you install the 1.19+4 firmware?
-
I have installed +4, but didn't have the chance to test it, as I have nothing to print yet
-
I experienced something similar to that, where every command in the console showed the output of an older M122 command, but I haven't seen it happen yet in +4.
-
Yeap, can confirm that. It seems +4 is not repeating.
-
Actually it is repeating again.
[[language]] 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.3
It looks like the issue is with the client side, because server doesn't repeat.
T 2017/10/13 16:05:33.938039 192.168.27.116:34083 -> 192.168.27.7:80 [AP] GET /rr_gcode?gcode=M221%20D0%20S95 HTTP/1.1. Host: 192.168.27.7. Connection: keep-alive. Accept: application/json, text/javascript, */*; q=0.01. X-Requested-With: XMLHttpRequest. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36. Referer: http://192.168.27.7/. Accept-Encoding: gzip, deflate. Accept-Language: en-GB. . T 2017/10/13 16:05:33.941879 192.168.27.7:80 -> 192.168.27.116:34083 [AP] HTTP/1.1 200 OK Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache Expires: 0 Access-Control-Allow-Origin: * Content-Type: application/json Content-Length: 12 Connection: close {"buff":243}
Or server is repeating in "rr_reply"?
T 2017/10/13 16:05:34.403518 192.168.27.116:34085 -> 192.168.27.7:80 [AP] GET /rr_reply HTTP/1.1. Host: 192.168.27.7. Connection: keep-alive. Accept: text/html, */*; q=0.01. X-Requested-With: XMLHttpRequest. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36. Referer: http://192.168.27.7/. Accept-Encoding: gzip, deflate. Accept-Language: en-GB. . T 2017/10/13 16:05:34.407117 192.168.27.7:80 -> 192.168.27.116:34085 [AP] HTTP/1.1 200 OK Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache Expires: 0 Access-Control-Allow-Origin: * Content-Type: text/plain Content-Length: 62 Connection: close File Elevator/pulley.FCStd_PLA.gcode selected for printing
-
I believe this is an issue with the interaction between DWC and the firmware. It's more chrishamm's area than mine. It's probably triggered by connecting two network clients and stopping one of them without pressing Disconnect first.
-
I believe this is an issue with the interaction between DWC and the firmware. It's more chrishamm's area than mine. It's probably triggered by connecting two network clients and stopping one of them without pressing Disconnect first.
I can confirm this behavior, as I often upload a print from my computer and then control the printer via my phone (they are not in the same room).
When I connect with my phone and control the printer, and I go back to my PC , sometimes the session is disconnected (AJAX error) and if I reconnect, I get echo on each command. -
I've just released an update to firmware 1.19. the binaries an be found at https://www.dropbox.com/sh/wq0u70kpapqc3is/AAC6I8TS5Lbwuziq_r3M15Qea?dl=0. The changes since the 1.19+1 test version are:
Thank you for this link, the one on github says it would not work with my electronics ( a duet ethernet, I did not grab the wifi firmware on accident)
-
Version 1.19+1 has been superseded by 1.19.2 which is an official release on github.