Firmware 2.0RC4 released

[hurzhurz]

I just discovered that the Duet crashes when I open the DWC using Internet Explorer.
After looking with Wireshark, I can say this request causes it... the crash also happens when I send it via putty directly to port 80:

GET /fonts/glyphicons.eot? HTTP/1.1
Accept: /
Referer: http://192.168.2.23/
Accept-Language: de-DE
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
Origin: http://192.168.2.23
Accept-Encoding: gzip, deflate
Host: 192.168.2.23
Connection: Keep-Alive
Cache-Control: no-cache

I have also tested some older versions: 2.0RC1 crashes, but 1.21 not.

Here is the output of M122 after a crash:
0_1526726134777_M122.txt

Oh, and the reason for trying Internet Explorer was that the DWC always scrolls to the top every few seconds... at least with Firefox and Chrome.

EDIT/UPDATE:
Looks like it doesn't like the "?" at the end of the URI.
Working: "/fonts/glyphicons.eot" or "/fonts/glyphicons.eot?aa=aa"
Causing crash: "/fonts/glyphicons.eot?" or "/fonts/glyphicons.eot?aa"

[zerspaner_gerd]

it seems to me that the Web Interface does not react anymore,

here is a video

https://www.dropbox.com/s/iy93ev9hi6bhizy/duet web interface.wmv?dl=0

not all gcode will be displayed, they are present on the panel.
the same behavior with 2.0 (RTOS) RC2b (2018-05-13b3)

My browser is chrome

[dc42]

Try c!earing the browser cache and reloading the page.

[dc42]

@hurzhurz said in Firmware 2.0RC4 released:

I just discovered that the Duet crashes when I open the DWC using Internet Explorer.
After looking with Wireshark, I can say this request causes it... the crash also happens when I send it via putty directly to port 80:

GET /fonts/glyphicons.eot? HTTP/1.1
Accept: /
Referer: http://192.168.2.23/
Accept-Language: de-DE
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
Origin: http://192.168.2.23
Accept-Encoding: gzip, deflate
Host: 192.168.2.23
Connection: Keep-Alive
Cache-Control: no-cache

I have also tested some older versions: 2.0RC1 crashes, but 1.21 not.

Here is the output of M122 after a crash:
0_1526726134777_M122.txt

Oh, and the reason for trying Internet Explorer was that the DWC always scrolls to the top every few seconds... at least with Firefox and Chrome.

EDIT/UPDATE:
Looks like it doesn't like the "?" at the end of the URI.
Working: "/fonts/glyphicons.eot" or "/fonts/glyphicons.eot?aa=aa"
Causing crash: "/fonts/glyphicons.eot?" or "/fonts/glyphicons.eot?aa"

Thanks, I will test this on Monday.

[zerspaner_gerd]

@dc42
Has nothing changed, it seems that about 3-10 sec works after that everything is frozen like (temperature does not fluctuate anymore)

On the device where the update was recorded, the problem does not seem to occur. Here only the gcode files are not complete.
Both Windows 10 with Google Chrome

I'm back on web interface version: 1.21, it works on both devices.

[Catalin_RO]

I did some machining on the WorkBee with 2.0RC4 and found no issues apart from the already known incompatibility with trochoidal machining GCode generated by CamBam. I used "classic" machining patterns and all OK.

[dc42]

@zerspaner_gerd said in Firmware 2.0RC4 released:

@dc42
Has nothing changed, it seems that about 3-10 sec works after that everything is frozen like (temperature does not fluctuate anymore)

On the device where the update was recorded, the problem does not seem to occur. Here only the gcode files are not complete.
Both Windows 10 with Google Chrome

I'm back on web interface version: 1.21, it works on both devices.

Did you try clearing the browser cache? I had to do that after upgrading DWC.

If the problem persists, please open the debugging console in your browser by pressing control-shift-J and see if any Javascript exceptions have been logged.

You can use DWC 1.21 with RRF 2.0RC4 if necessary.

[dc42]

@hurzhurz said in Firmware 2.0RC4 released:

I just discovered that the Duet crashes when I open the DWC using Internet Explorer.
After looking with Wireshark, I can say this request causes it... the crash also happens when I send it via putty directly to port 80:

GET /fonts/glyphicons.eot? HTTP/1.1
Accept: /
Referer: http://192.168.2.23/
Accept-Language: de-DE
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
Origin: http://192.168.2.23
Accept-Encoding: gzip, deflate
Host: 192.168.2.23
Connection: Keep-Alive
Cache-Control: no-cache

I have also tested some older versions: 2.0RC1 crashes, but 1.21 not.

Here is the output of M122 after a crash:
0_1526726134777_M122.txt

Oh, and the reason for trying Internet Explorer was that the DWC always scrolls to the top every few seconds... at least with Firefox and Chrome.

EDIT/UPDATE:
Looks like it doesn't like the "?" at the end of the URI.
Working: "/fonts/glyphicons.eot" or "/fonts/glyphicons.eot?aa=aa"
Causing crash: "/fonts/glyphicons.eot?" or "/fonts/glyphicons.eot?aa"

I confirm this bug. I have found the cause and the fix will be in the next RC, or the 2.0 release if there isn't another RC.

[dc42]

@catalin_ro said in Firmware 2.0RC4 released:

I did some machining on the WorkBee with 2.0RC4 and found no issues apart from the already known incompatibility with trochoidal machining GCode generated by CamBam. I used "classic" machining patterns and all OK.

Thanks for your feedback!

[dc42]

I have put a new firmware binary (RC4a) in the EdgeRelease folder at https://github.com/dc42/RepRapFirmware/tree/v2-dev/EdgeRelease. Please can those of you having problems connecting a browser try it. It fixes the issue of Internet Explorer causing the Duet to reboot, and may help in other cases too.

[Dr_Ju_Ju]

FYI
installed ok:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.0(RTOS)RC4 (2018-05-17b2)
Web Interface Version: 1.21.1-RC4

Successfully printed a large print, but subsequent to that the Web browser (Firefox) threw a Javascript error (unfortunately I couldn't capture the exact error) but the only recovery was to re-set the board.

[zerspaner_gerd]

@dc42 said in Firmware 2.0RC4 released:

@zerspaner_gerd said in Firmware 2.0RC4 released:

@dc42
Has nothing changed, it seems that about 3-10 sec works after that everything is frozen like (temperature does not fluctuate anymore)

On the device where the update was recorded, the problem does not seem to occur. Here only the gcode files are not complete.
Both Windows 10 with Google Chrome

I'm back on web interface version: 1.21, it works on both devices.

Did you try clearing the browser cache? I had to do that after upgrading DWC.

If the problem persists, please open the debugging console in your browser by pressing control-shift-J and see if any Javascript exceptions have been logged.

You can use DWC 1.21 with RRF 2.0RC4 if necessary.

Yes,
update:
With web interface version: 1.21 and with firmware version: 2.00RC4

• Not all gcode files are displayed

• I can not upload gcode files, message says Upload Complete, but gcode is not listed.
  Again on firmware version: 1.21 all gcode files will be displayed (on DWC) even those over firmware version: 2.00 have been uploaded (they will not be displayed on the panel).

No matter which browser (Chrome, Internet Explorer, Edge)

I have several devices that access the Duet

The updating / freezing problems are gone with this combination. Like in this video https://www.dropbox.com/s/iy93ev9hi6bhizy/duet web interface.wmv?dl=0

What else can I try?

Here are pictures with debugging console:

2.0(RTOS)RC4 (2018-05-17b2

1.21 (2018-03-21)

@dc42 said in Firmware 2.0RC4 released:

I have put a new firmware binary (RC4a) in the EdgeRelease folder at https://github.com/dc42/RepRapFirmware/tree/v2-dev/EdgeRelease. Please can those of you having problems connecting a browser try it. It fixes the issue of Internet Explorer causing the Duet to reboot, and may help in other cases too.

When installing this error comes

[dc42]

The "not valid for this electronics" message means that you have downloaded the firmware binary incorrectly. Follow the links (don't right click on them) until you reach a page with a Download button.

[zerspaner_gerd]

@dc42 said in Firmware 2.0RC4 released:

The "not valid for this electronics" message means that you have downloaded the firmware binary incorrectly. Follow the links (don't right click on them) until you reach a page with a Download button.

Sorry, my mistake.

But other mistakes are still there
Here are my problems via video

gcode disappear on update from firmware version: 2.0
https://www.dropbox.com/s/y7wop43cqoyzuiv/gcode disappear.wmv?dl=0

Uploaded gcode will not be displayed
https://www.dropbox.com/s/l49s4x2d91fjcf6/Upload gcode problem.wmv?dl=0

Can that be that the file name is too long? With short works the upload.
But why do not all disappear too long?
But with 1:21 I have no problems with it!

[WalterSKW]

I do have the same issue.
After uploading a file, I cannot find it in the list. On the panel due I however, I can select and print the file succesfully.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.0(RTOS)RC4 (2018-05-17b2)
WiFi Server Version: 1.21
Web Interface Version: 1.21

[Catalin_RO]

@walterskw Why is the DWC v1.21? With latest firmware you need the latest DWC beta (1.21.1-RC4) for proper functionality, as specified in the WhatsNew document.

[dc42]

Firmware 2.0RC5 is out so I have started a new thread for it and I am closing this one.