New firmware 2.0RC5 available

zerspaner_gerd

@dc42 said in New firmware 2.0RC5 available:

Upload errors are expected with the new firmware if you have a password set on your Duet (other than the default 'reprap') and you use DWC 1.21.

Please load DWC ~~1.21.4~~ 1.21.1RC4 on to your Duet, clear the browser cache, load it and immediately press control-shift-J to get the debugging console. Then when DWC becomes unresponsive, there may be an exception message.

For me there was of course no change with DuetWebControl-1.21.1, too bad.

Why 1.21 runs smoothly, and with 2.0 and 1.21.1 DWC does not work at all? And the sporatic problem with the gcode files.

I have not set up a password.

Here is a video to clear the browser cache.
https://www.dropbox.com/s/zs87rwetvx862hl/clear the browser cache.wmv?dl=0

Here are the results of debugging console:

crosshair.png:1 Failed to load resource: the server responded with a status of 404 (page not found)
diabase_calibration_diagram.png:1 Failed to load resource: the server responded with a status of 404 (page not found)
/rr_download?name=0:/sys/oem.json:1 Failed to load resource: the server responded with a status of 404 (file not found)
dwc.js:2 GET http://192.168.188.40/rr_status?type=1 0 ()
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612
setTimeout (async)
success @ dwc.js:1456
u @ dwc.js:2
fireWith @ dwc.js:2
done @ dwc.js:2
(anonymous) @ dwc.js:2
load (async)
send @ dwc.js:2
ajax @ dwc.js:2
updateStatus @ dwc.js:612

Can someone try to upload this gcode file, these are not displayed on me with RRF 2.0RC5 + DWC 1.21.
Is this due to RRF or the gcode file.
0_1527096457013_960 Justier Teil fuer rund gleichmaessigkeit.gcode

BMMal

I'm having some strange under extrusion issue. Not sure how I started a print at all but I can see that my support is under extruded. The first layer of the part barely pushed out any plastic. I tested by trying to manually extrude 100mm of material and only about 40mm got extruded. I did this twice. Once by commanding a full 100 and then commanding 20mm 5 times.

~~I have to revert to 2b for now which did not have any issues that I noticed.~~

wilriker

@bmmal I can confirm this. I tried 100mm and 50mm extrusion and it did barely extrude less than 100mm altogether - that might also explain why my print today hat what I first thought was a layer shift. Now it rather makes sense that extrusion was so low that bed adhesion failed at one point, moved the print and gladly found hold again in a place where I did not have to toss the print away.

I will also downgrade to RC4 and check again.

EDIT: I retested and now can no longer reproduce the problem.

@BMMal how fast did you extrude? When I tried with 5mm/s it would fail most often. I tried again with 1mm/s and it extruded exactly 100mm on RC5.

denke

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 open

There was no print or simmulation since cold bootup, just deleted a bunch of other gcode files.
After "emergency stop" the file deleted successfully.

BMMal

This post is deleted!

BMMal

@wilriker said in New firmware 2.0RC5 available:

@bmmal I can confirm this. I tried 100mm and 50mm extrusion and it did barely extrude less than 100mm altogether - that might also explain why my print today hat what I first thought was a layer shift. Now it rather makes sense that extrusion was so low that bed adhesion failed at one point, moved the print and gladly found hold again in a place where I did not have to toss the print away.

I will also downgrade to RC4 and check again.

EDIT: I retested and now can no longer reproduce the problem.

@BMMal how fast did you extrude? When I tried with 5mm/s it would fail most often. I tried again with 1mm/s and it extruded exactly 100mm on RC5.

I have to retest. I found a mechanical problem and suspect there may be another. Working on it.

wilriker

@bmmal said in New firmware 2.0RC5 available:

I have to retest. I found a mechanical problem and suspect there may be another. Working on it.

More or less the same here. Too fast extrusion speed plus a bad angle in my Reverse Bowden. Retested twice now and both times perfect 100mm extrusions.

BMMal

@wilriker said in New firmware 2.0RC5 available:

@bmmal said in New firmware 2.0RC5 available:

I have to retest. I found a mechanical problem and suspect there may be another. Working on it.

More or less the same here. Too fast extrusion speed plus a bad angle in my Reverse Bowden. Retested twice now and both times perfect 100mm extrusions.

Something is not adding up for me. I have tried both RC3 and RC5 and I'm getting half of what I should with both of them. I don't recall changing anything with my steps/mm or microstepping...

wilriker

@bmmal What speed are you testing with? For me 1mm/s works fine, 5mm/s did not reliably extrude the requested amount - at least not with the bad angle in my reverse bowden and a comparably weak ungeared extruder setup.

BMMal

@wilriker

1mm/s

Usually 5 is just on the edge of too fast.

wilriker

@bmmal said in New firmware 2.0RC5 available:

Usually 5 is just on the edge of too fast.

Found that out as well.

BMMal

@wilriker So not really sure what it was, may have been a combination of the way I had my steps/mm for each extruder and microstepping explicitly defined ie Exx:xx:xx:xx rather than just Exx.

At one point it looks like I had the arrays mismatched in size so default 16x were being loaded rather than the 8x

Seems to be back to normal now...

wilriker

@bmmal said in New firmware 2.0RC5 available:

Seems to be back to normal now...

Happy to hear that.

zerspaner_gerd

These are the last two entries in "Network" (debugging console)

penultimate

Request URL: http://192.168.188.40/rr_status?type=1
Referrer Policy: no-referrer-when-downgrade
Provisional headers are shown
Accept: application/json, text/javascript, */*; q=0.01
Referer: http://192.168.188.40/
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
X-Requested-With: XMLHttpRequest
type: 1

Last entry

Request URL: http://192.168.188.40/
Request Method: GET
Status Code: 200 OK
Remote Address: 192.168.188.40:80
Referrer Policy: no-referrer-when-downgrade
Connection: close
Content-Length: 168262
Content-Type: text/html
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7
Connection: keep-alive
Host: 192.168.188.40
Referer: http://192.168.188.40/
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
X-Requested-With: XMLHttpRequest

0_1527107037531_debugging console.JPG

dc42

@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?

dc42

@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 open

There 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?

denke

@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.

denke

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.

zerspaner_gerd

@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.

Dr_Ju_Ju

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 Error

A 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"