New firmware 2.0RC5 available
-
@zerspaner_gerd said in New firmware 2.0RC5 available:
These are the last two entries in "Network" (debugging console)
...Thanks, those all look OK. The 404 errors for those particular files are normal.
One difference between 2.0 and earlier versions is that the total size of output buffers is reduced in 2.0. Because of the way that DWC fetches the file list, this means that the number of files that DWC will display in a single directory is about 1/3 lower than it was before. So if you have a lot of GCode files on the SD card and you do not organise them into directories, then you will not see new files that you upload into the /gcodes folder in DWC even though they are there. The workaround is to create subdirectories and move some of the files into them.
What other problems are you having with 2.0RC5 and DWC 1.21.1 final?
-
@denke said in New firmware 2.0RC5 available:
gcode file delete problem threw dwc:1.21.1, fw:2.0-rc4:
->http://printer.loc/rr_delete?name=0%3A%2Fgcodes%2Fvase.gcode
<-{"err":1}
Message displayed: Error: Cannot delete file 0:/gcodes/vase.gcode because it is openThere was no print or simmulation since cold bootup, just deleted a bunch of other gcode files.
After "emergency stop" the file deleted successfully.It may be that at the time you tried to delete the file, DWC had it open because after the previous file deletions it rescanned the files for the GCode information. Did you try deleting it more than once before you did the emergency stop?
-
@dc42
Yep, about 6-8 times across the duration of about 2 minutes. I opened the debugger on maybe the 4th time I tried it. -
Also, another strange experience, Not all the gcode files were listed in dwc, and I could not fild any method to turn the page.
-I selected the sorting method of mtime, newest first, but the most recent prints did not show up.
-Then selected all entrys, right click, delete.
-The selected entrys were deleted, and a new set of gcode files appeared containing those most recent I was looking for.As if not all the entries were in the list of gcode files, and the sort would only apply to those which were visible.
-
@dc42 said in New firmware 2.0RC5 available:
@zerspaner_gerd said in New firmware 2.0RC5 available:
These are the last two entries in "Network" (debugging console)
other problems are you having with 2.0RC5 and DWC 1.21.1 final?
Thanks,
Another problem is the DWC with this error (rr_status? Type = 1 in red, see picture above) stops responding.
Comes between 7 and a maximum of about 30sec.There is no message, I only see it in the debugging console.
I could confirm if I choose a folder, the gcode file is displayed.
But is that the reason for the DWC problem?
Should I again downgrade to DWC and RRF 1.21, move gcode, and then try again on 1.21.1 und RC5.
@denke said in New firmware 2.0RC5 available:
Also, another strange experience, Not all the gcode files were listed in dwc, and I could not fild any method to turn the page.
...........
As if not all the entries were in the list of gcode files, and the sort would only apply to those which were visible.That sounds exactly like one of my problems!
Did you try that:
@dc42 said in New firmware 2.0RC5 available:
Wenn Sie also viele GCode-Dateien auf der SD-Karte haben und diese nicht in Verzeichnissen organisieren, werden Sie keine neuen Dateien sehen, die Sie in den DWC-Ordner / gcodes hochladen, obwohl sie vorhanden sind. Die Problemumgehung besteht darin, Unterverzeichnisse zu erstellen und einige der Dateien in sie zu verschieben.
-
Sitting on the 'G-code files' page, while aprint is in progress, I received this error message:
G-Codes Directory Go Up
Connect to your Duet to display G-Code files
JavaScript ErrorA 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:
Version: 1.21.1
Message: uncaught exception: out of memory
URL:
Line: 0:0
Error object: "out of memory" -
@denke said in New firmware 2.0RC5 available:
Also, another strange experience, Not all the gcode files were listed in dwc, and I could not fild any method to turn the page.
-I selected the sorting method of mtime, newest first, but the most recent prints did not show up.
-Then selected all entrys, right click, delete.
-The selected entrys were deleted, and a new set of gcode files appeared containing those most recent I was looking for.As if not all the entries were in the list of gcode files, and the sort would only apply to those which were visible.
See my earlier response, https://forum.duet3d.com/topic/5394/new-firmware-2-0rc5-available/30. There has always been a limit to how many files DWC will display in a single folder, but it's a little lower in release 2.0.
-
@dr_ju_ju said in New firmware 2.0RC5 available:
Sitting on the 'G-code files' page, while aprint is in progress, I received this error message:
G-Codes Directory Go Up
Connect to your Duet to display G-Code files
JavaScript ErrorA 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:
Version: 1.21.1
Message: uncaught exception: out of memory
URL:
Line: 0:0
Error object: "out of memory"That's one for chrishamm.
-
@dc42
Thanks for the info!A behaviour suggestion if i may:
-The sorting could be implemented in the duet fw, not dwc.
-The board could send down the first ~25 entries initially (the first 25 of the sorted list), then send the follow-up entries threw page turning or infinite scrollingOr at least a warning that "there are too many files in this directory, not all files are shown".
-
@denke said in New firmware 2.0RC5 available:
@dc42
Thanks for the info!A behaviour suggestion if i may:
-The sorting could be implemented in the duet fw, not dwc.
-The board could send down the first ~25 entries initially (the first 25 of the sorted list), then send the follow-up entries threw page turning or infinite scrollingOr at least a warning that "there are too many files in this directory, not all files are shown".
Thanks, I am already in discussions with chrishamm about how to resolve this.
-
Nice, thanks @dc42 !
-
Hi! I've been testing RC5 since the release date and everything works fine. I was previously on 1.21. I found no bug or anything strange to repport.
-
@3doeste said in New firmware 2.0RC5 available:
Hi! I've been testing RC5 since the release date and everything works fine. I was previously on 1.21. I found no bug or anything strange to repport.
Thanks for the feedback!
-
I don't know if anyone else have this issue, but with the 1.21.1 web interface, I seem to have a hard time controlling the fan speed in the "Machine Control" tab. If I pull on the slider, it would move over, but when I let go it would bounce back to the previous value. I repeat the same process on IE and Firefox and had the same issues. Sometimes if I double click slowly it would stay, but its a bit annoying.
When I move the fans, speed factor or extrusion factor in the "Print Status" tab, I have no problem moving the sliders. The slider in the fan control on the "Print Status" jumps slightly, but nowhere near as often as the "Machine Control" slider.
I don't think its related to RC5, but it seems like a problem with the recent updates.
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.0 or 1.01
Firmware Version: 2.0(RTOS)RC5 (2018-05-22b1)
WiFi Server Version: 1.21
Web Interface Version: 1.21.1 -
@shadowx
I have the same problems in Safari.
It looks like for me this annoying bug got worse in the recent updates. -
@dc42 With your advice, uploading the gcode files works without any problems.
The connection problems with DWC are still present.
The funny, on the Tablet (also with chrome and Windows10) comes for a long time no mistake.
On desktop PC this comes more often.I do not understand that.
It seems that the update suspends the web interface but the connection remains.
With combination DWC 1.21.1 and RRF 1.21, the dropouts are not present.
-
There are problems with this firmware (upgraded from 1.21, so I don't know if it is 2.0 specific or not).
Uploading a file, creating a directory (through DWC or FTP) is not shown in web UI. I've dumped the traffic between the browser and the Duet and indeed the file list does not show the added entries. If using FTP, they are there. If using M32 directly to print they are there.
Old files on the SD card are shown in DWC, but anything new since 2.0RC5 upgrade is not shown.
-
@sigxcpu said in New firmware 2.0RC5 available:
There are problems with this firmware (upgraded from 1.21, so I don't know if it is 2.0 specific or not).
Uploading a file, creating a directory (through DWC or FTP) is not shown in web UI. I've dumped the traffic between the browser and the Duet and indeed the file list does not show the added entries. If using FTP, they are there. If using M32 directly to print they are there.
Old files on the SD card are shown in DWC, but anything new since 2.0RC5 upgrade is not shown.
Example:
Create a folder in
gcodes/Raducu
namedccc
:T 2018/05/24 22:21:48.056786 192.168.27.125:54849 -> 192.168.27.7:80 [AP] #74 GET /rr_mkdir?dir=0%3A%2Fgcodes%2FRaducu%2Fccc HTTP/1.1. Host: 192.168.27.7. Accept-Encoding: gzip, deflate. Connection: keep-alive. Accept: application/json, text/javascript, */*; q=0.01. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14. Referer: http://192.168.27.7/. Accept-Language: en-us. X-Requested-With: XMLHttpRequest. . T 2018/05/24 22:21:48.143654 192.168.27.7:80 -> 192.168.27.125:54849 [AP] #78 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: 9 Connection: close {"err":0}
Reload shows no
ccc
entry.T 2018/05/24 22:21:48.151622 192.168.27.125:54850 -> 192.168.27.7:80 [AP] #87 GET /rr_filelist?dir=0%3A%2Fgcodes%2FRaducu HTTP/1.1. Host: 192.168.27.7. Accept-Encoding: gzip, deflate. Connection: keep-alive. Accept: application/json, text/javascript, */*; q=0.01. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14. Referer: http://192.168.27.7/. Accept-Language: en-us. X-Requested-With: XMLHttpRequest. . T 2018/05/24 22:21:48.168250 192.168.27.7:80 -> 192.168.27.125:54850 [A] #88 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: 1992 Connection: close {"dir":"0:/gcodes/Raducu","files":[{"type":"f","name":"loubie_aria_dragon_PLA.gcode","size":6043030,"date":"2017-04-03T19:10:15"},{"type":"f","name":"spaceShuttle1_PLA.gcode","size":1735511,"date":"2017-04-03T22:55:18"},{"type":"f","name":"2part_-_A_head_ABS.gcode","size":4456480,"date":"2017-04-23T22:04:29"},{"type":"f","name":"nema17_support_PLA.gcode","size":1277492,"date":"2017-04-07T13:03:07"},{"type":"f","name":"belt_support_PLA.gcode","size":911789,"date":"2017-04-07T15:22:11"},{"type":"f","name":"plate_and_pillars_PLA 220 (Sacele).gcode","size":2990130,"date":"2017-04-08T00:29:20"},{"type":"f","name":"robot_pillar_PLA 220 (Sacele).gcode","size":1621129,"date":"2017-04-08T14:13:06"},{"type":"f","name":"2part_-_B_body_ABS.gcode","size":6222247,"date":"2017-04-23T23:01:19"},{"type":"f","name":"Variable_Speed_Gears_-_Main_Gear-1_ABS.gcode","size":9204723,"date":"2017-05-01T10:16:23"},{"type":"f","name":"metal_detector_coil_PLA.gcode","size":1589034,"date":"2017-05-06T20:54:17"},{"type":"d","name":"Spinner","size":0,"date":"2017-05-22T02:26:25"},{"type":"f","name":"Hull_Mk6_ABS.gcode","size":3329265,"date":"2017-05-31T15:23:21"},{"type":"f","name":"Finger_Pad_V2_Twisted_Pins_ABS.gcode","size":958387,"date":"2017-05-15T22:36:15"},{"type":"d" T 2018/05/24 22:21:48.271859 192.168.27.7:80 -> 192.168.27.125:54850 [AP] #90 ,"name":"Microscop","size":0,"date":"2017-05-19T01:31:00"},{"type":"f","name":"SphericalIrisBox_PLA.gcode","size":11446362,"date":"2017-05-20T21:24:09"},{"type":"f","name":"Jumping_Turtle_PLA.gcode","size":7794056,"date":"2017-08-10T23:55:16"},{"type":"f","name":"Jumping_Turtle_PLA_0.3.gcode","size":4326095,"date":"2017-08-10T23:59:10"},{"type":"f","name":"Spikey_Top_PLA.gcode","size":2177682,"date":"2017-08-22T20:17:24"},{"type":"f","name":"Rocket_Launcher_PLA.gcode","size":5816173,"date":"2017-08-28T17:56:01"},{"type":"f","name":"Rocket_Launcher_10mm.gcode","size":3424444,"date":"2017-08-29T14:46:10"},{"type":"f","name":"2LiterThreads_1fourth_npt_FINS_righted_PET-G.gcode","size":2229123,"date":"2017-08-30T19:36:09"}]}
-
@sigxcpu said in New firmware 2.0RC5 available:
There are problems with this firmware (upgraded from 1.21, so I don't know if it is 2.0 specific or not).
Uploading a file, creating a directory (through DWC or FTP) is not shown in web UI. I've dumped the traffic between the browser and the Duet and indeed the file list does not show the added entries. If using FTP, they are there. If using M32 directly to print they are there.
Old files on the SD card are shown in DWC, but anything new since 2.0RC5 upgrade is not shown.
Please see this response https://forum.duet3d.com/topic/5394/new-firmware-2-0rc5-available/30.
-
Thank you for the answer.
I've scanned this thread, but missed that.
Is this a permanent issue or we can expect it to be fixed in the future? I don't know the internals, but I assume that the serialization buffer is small. If it is that, can't you simply generate the JSON on the fly (i.e. streaming)?
Another option is to shrink the JSON. On a machine to machine transfer there is no need to repeat
type
,name
,size
,date
all the time. They can be abbreviated tot n s d
, for example.LE: now that this started me, I dug in the source code.
I see that the big M122 reply is sent at this size:
Content-Length: 2539
My example reply is:
Content-Length: 1992
My example with shorted field names is
1739
bytes in size, around 250 bytes smaller.So there are ~550 bytes that could've taken more files to be displayed.
Also the modified times can be encoded as UNIX timestamps instead of formatted, which will reduce that even further, from 21 bytes to 9 bytes per entry.
We can have a parameter in rr_filelist sent by DWC to request short format and implement a list with all the above mentioned optimizations, so things are backward compatible.
I can take a stab at this, without the buffer size part (M122 is big, filelist is small) because I don't know why you've chosen it to be that way.
This will be for a 2.1 release maybe.