Stable firmware 2.01 (Duet 2) and 1.22 (Duet 06/085) released

[dc42]

@qdeathstar said in Stable firmware 2.01 (Duet 2) and 1.22 (Duet 06/085) released:

I’ve never uploaded a new one, can i just delete the old one and replace it with the new one using the web interface?

You can just upload the new one through the web interface.

[brunofporto]

New features/changed behaviour:

• The Z probe MOD pin can now be accessed as a GPIO pin

GPIO pn can be PWM capable? This pin should be PWM capable...... It would be so much easier to set a lot of different probes with a single connector if it was.

[dc42]

The Z probe MOD pin on the Duet WiFi/Ethernet is not PWM capable.

[DADIY]

One very minor bug with the latest DWC, on smaller screens the text for speed is mangled, I think with some reduction in padding this should be fixable.

[Dougal1957]

@dadiy thats not the latest version of DWC

[DADIY]

@dougal1957 1.21.2-dc42 was the that was on the Github with the firmware and its newer than on https://github.com/chrishamm/DuetWebControl so perhaps a pointer to the newer version would be helpful.

[dc42]

Try https://github.com/chrishamm/DuetWebControl/tree/dev.

[Dougal1957]

@dadiy https://forum.duet3d.com/topic/5485/duet-web-control-wishlist-notes-and-priorities/63 in the DWC Section of the forum

[whosrdaddy]

Found a new problem, "object height" is no longer populated since the latest firmware/DWC.

Slicer is the same as can be seen from the pic.
The only thing I have changed is upgrading DWC and the firmware to the latest available versions:

Firmware Name:	RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics:	Duet WiFi 1.02 or later + DueX5
Firmware Version:	2.01(RTOS) (2018-07-26b2)
WiFi Server Version:	1.21
Web Interface Version:	1.22-b3

[wilriker]

@whosrdaddy I just checked on my machine with same versions and I cannot reproduce it neither for existing nor for just now newly uploaded Gcode files. Though, mine are all sliced with Cura.

[whosrdaddy]

Ok, I sliced a smaller file and now I can see the object height. I suppose the firmware does not attempt to read the height for larger files?

[wilriker]

@whosrdaddy I just uploaded the largest GCode file I could find on my hard drive (just a little under 11 MiB) and it got the height correctly from it. I also checked the file and it does not contain a comment with object height, so RRF must have scanned for the last rise in Z.

Don't get me wrong, I don't wanna say you don't have a problem, just that I cannot reproduce it.

Could you try to slice the same source file with another slicer?

[whosrdaddy]

Well did as requested and it seems it has nothing to do with the slicer, used exactly the same STL files:

[wilriker]

@whosrdaddy OK, your file is larger than mine, so maybe there is a lower limit to this issue.

[Dougal1957]

@whosrdaddy Can you post the stl for the 2 that fail so we can try it? I have several file much bigger than those that are correct

[whosrdaddy]

Sure, you can download it from here:
https://www.thingiverse.com/download:3377042

[wilriker]

@whosrdaddy With this file I can reproduce your issue:

[Dougal1957]

@whosrdaddy this is what I get for that file

It's not easy to read cos this forum is re-sizing the image but my file is 3 times the size of yours but gives 8.2mm hight and 39.xxx mtrs of filament. the diff may be the amount of infill mind

[whosrdaddy]

so we established there is an issue, it's not the file size because you have a 31MB file.
Lets wait & see what @dc42 thinks about this...

[Dougal1957]

I Too am on the latest FW and DWC