New firmware 1.09n and DWC v1.07

Quote

DWC version 1.07:
- Thanks to fotomas a new dark theme can now be set on the Settings page
- "Axis not homed" warning may be displayed next to machine name
- Added support for 6 extruders and 6 heaters (thanks T3P3)
- DWC no longer blocks the HTTP G-Code reader during tool changes
- Last layer time is displayed for two seconds after each layer change
- Speed factor now goes from 20% - 200%
- rr_files uses flagDirs parameter if possible
- Print+Delete buttons on file and macro pages are now fixed and don't float around on smart displays any more
- Filament info for multi-colour prints and first layer height are now displayed on the files page
- Default bowden tube length increased to 500mm
- Improved Extrude+Retract buttons on Spools page (might be later replaced by macro files though)
- Status requests are no longer sent while fileinfo is being polled
- Added new machine properties page to settings
- If a config file has been uploaded, the DWC asks for a software reset
- RRF status responses may now provide the fan values as an array
- Translations have been disabled for MSIE (and Edge) to make the page load
- Load+Unload filament uses the stack and switches to relative mode
- Responses of faulty JSON requests are now logged to console
- Cancel button sends 'M0 H1' to instruct RRF to leave all heaters on
- Bug fix: Web interface didn't update when heated bed was re-enabled
- Bug fix: Macro directories were not deleted on the control page by the corresponding button on the macros page
- Bug fix: DWC wasn't scaled properly after load on smartphones
- Minor improvements

Quote

Firmware version 1.09n-ch:
- Added warning message to M22 (Release SD card)
- M140+M141 can no longer use heaters that are already in use
- Print time estimations aren't affected by pauses any more
- LWIP timers are now called at 8Hz (used to be 16Hz)
- Decreased network transaction count from 24 to 16 and MEM_SIZE in lwipopts
- Changed IRQ priorities once more, but their overall priorities remain equal
- Cleaned up PrintMonitor class and improved several details
- Added new fields to advanced status and config responses (see wiki)
- Added optional "flagDirs" parameter to rr_files
- Webserver shares the G-Code response with all clients
- Fixed potential memory leaks in the Webserver class
- Improved and verified OutputBuffer reference counters
- M22 reports a warning message because the SD card must not be removed during runtime
- Changed M27 to return the file size and the number of bytes read from the file being printed
- M0 always turns off all heaters unless an 'H' parameter with a non-zero value is passed
- Bug fix: Detected first layer height was too high if "Lift Z" G1 code was included in G-Code files
- Bug fix: M20 wasn't properly encoded for Pronterface
- Bug fix: Very long G-Code responses could hang up the web interface
- Bug fix: M1 in Marlin emulation didn't pause the print
- Bug fix: Added missing break to M190

Quote
o_lampe
Hi Chris,
your firmware is a fork from dc42s branch or the original RRF branch?

Will try to use your web control with dc42 1.09f later.

Thanks for keeping development going on, I have high hopes your work leads to an app, running on all smartphones/tablets
-Olaf

Quote
chrishamm
Hi Olaf,

My firmware was originally forked from dc42's repository, but a couple of things have been implemented differently. Basically the entire movement code is identical to dc42's fork though, and I can confirm that my firmware works as well on Delta and CoreXY printers. Besides, all G-Codes should be compatible, because I usually merge in most of dc42's changes when he releases a new firmware version.

The web interface works nicely on tablets and smartphones (tested with Chrome), but on some devices the stock browsers cannot deal with it properly. If you want to use all new features of this web interface version, I suggest you either flash my current firmware first or wait for dc42 to incorporate my latest changes.

Quote
mhackney
To use DWC 1.07 with DC42 firmware - is all that's needed is copy the DWC files to the flash card www directory?

thanks,
Michael

Quote
David J
I think that I had the same problem when uploading bed.g (about 700 bytes) - the upload appeared to fail, but in fact the file arrived intact (I took the memory card out to check).
Linux Mint 17.2 64-bit, Firefox browser. Latest dc42 firmware.

I haven't yet had an opportunity to follow this up and investigate further...

Quote
mhackney
Firstly, I am also running DWC v1.07 on the latest dc42 firmware with no problems.

Now, regarding file upload failures - I was having intermittent problems too along with occasionally very long upload times. This was with the sandisk CF card that came with my v0.8.5 Duet. I noticed my v.6 was uploading very fast. I swapped CF cards and the issues (slow and occasional failures) followed the card. I've since replaced the "bad" card with a new sandisk and I've not had a problem since. Could be the CF. I had similar issues with CF cards on smoothieboard too.

Quote
mhackney
Firstly, I am also running DWC v1.07 on the latest dc42 firmware with no problems.

Now, regarding file upload failures - I was having intermittent problems too along with occasionally very long upload times. This was with the sandisk CF card that came with my v0.8.5 Duet. I noticed my v.6 was uploading very fast. I swapped CF cards and the issues (slow and occasional failures) followed the card. I've since replaced the "bad" card with a new sandisk and I've not had a problem since. Could be the CF. I had similar issues with CF cards on smoothieboard too.

Quote
mhackney
@dc42 I ran into a similar issue when I converted to Smoothieboards over a year ago. I was having all sorts of problems until Arthur recommended swapping the SDCH card. Interestingly, it seems that some cards branded Sandisk might actually be counterfeits.

@dougal1958 The new card is a Sandisk that looks exactly like and has the same numbers as the bad card but I bought it locally. I usually buy Sandisk too but I've run into this problem several times. Perhaps they are a target for counterfeits because of their brand.