New Duet Web Control 1.10 and RepRapFirmware 1.09v-ch

• Firmware updates using the web interface (via M997)
• Updated LWIP stack from v1.4.0 to v1.4.1
• Several networking improvements
• mDNS support
• Implemented M143 (set maximum heater temperature)
• Improved layer detection

Quote

Duet Web Control v1.10
- Added support for autonomous firmware updates
- Fan RPM field can be hidden on the Settings page
- DWC asks for page reload after web interface update
- ZIP file uploads are now only allowed on Macros and Settings pages
- Minor other changes

Duet Web Control v1.09
- Replaced textarea autoresize library to fix issues with the dark theme
- Warm-up time on the print status page always uses firmware value
- Moved web cam integration panel on the settings page to the centre
- Added margin below config file textarea
- Bug fix: Web cam integration generated a faulty URL

Quote

RepRapFirmware 1.09u-ch and RepRapFirmware 1.09v-ch
- Recompiled with updated Arduino board files

RepRapFirmware 1.09t-ch
- Firmware reports new 'F' status character to indicate when a new firmware is about to be flashed
- G32 is now allowed even if no axes are homed (if bed.g is used)
- Implemented M143 (Set maximum heater temperature)
- Enabled M997 (Perform autonomous firmware update)
- Changed USB manufacturer to "RepRap"
- Improved networking subsystem to deal better with connection resets
- TCP polling timers are only called while data is sent (for retransmissions)
- Webserver keeps LwIP running while file info responses are processed
- Bug fix: Macros didn't send responses to the right destinations
- Bug fix: Object heights were not detected if G-code was follwed by comment

RepRapFirmware 1.09s-ch
- Added and tested mDNS support
- Improved and simplified layer detection algorithm
- Layer-based estimation is made when the first layer has been finished
- Reduced PrintMonitor update interval to 200ms
- File prints can be interrupted again using stack codes
- Parts of the G-code queue rewritten and enabled queuing for macro files
- G1 R1 codes are now processed in GCodes::LoadMoveBufferFromCode
- Moved a few classes to (almost) match dc42's file structure
- Merged in recent changes from 1.09q-alpha3 and 1.09r-dc42 (thanks wrangellboy and dc42)
- Updated Makefiles for new Arduino tree and for different directory structure
- Slightly improved pbuf memory usage in the networking code
- Updated README and removed change lists
- Removed RTC module from HSMCI driver (for now)
- Removed limitation to send network data to only one client at a time
- Bug fix: Hopefully fixed unreliable network connections for some users
- Bug fix: M24 and M226/M25 occasionally hung up
- Bug fix: M99 didn't cancel nested macros
- Bug fix: Progress bar on web interface jumped around during resume
- Bug fix: First layer height detection didn't work for some slicers
- Bug fix: HTTP sessions weren't cleaned up in the right order (thanks dc42)
- Preparations for automatic firmware updates via M997
- Other minor changes

Arduino Duet Board v1.11
- Disabled mDNS debugging again (oops)

Arduino Duet Board v1.10
- Bug fix: EMAC driver didn't handle incoming IGMP packets

Arduino Duet Board v1.09
- EMAC driver resets EMAC initially during boot
- Better separation from LwIP and EMAC driver for other platforms
- Upgraded LwIP from v1.4.0 to v1.4.1
- Evaluating SerialUSB checks VBUS to determine if a cable is connected
- Removed Wire library examples
- Reduced EMAC RX buffer size from 32 to 16

Arduino Duet Board v1.08
- Removed networking classes from Arduino core
- Moved all low-level libraries from RRF to this board
- Implemented TRNG in Arduino core (see WMath.cpp and variant.cpp)
- Purged a few more warning messages
- Removed HID library again
- Removed unused RingBuffers

Quote
chrishamm
[*] Firmware updates using the web interface (via M997)

Quote
chrishamm
In order to use the web interface for firmware updates, you have to upload a file called "iap.bin" once to the /sys directory. This file can be obtained here: [github.com] After that, you can upload your RepRapFirmware*.bin file using the upload button on the Settings page and follow the instructions.

Quote
chrishamm
Feel free to post some feedback! If you appreciate my work, please consider a small donation as well - I'm a student and new filament is expensive smiling smiley

Quote
Ormerod187
Done ..my grain of sand in your account.

Quote
pantau
I get these errors a lot!
But what is even more severe: Hot end temperature regulation is very unstable (+-5°C) and also PanelDue (no webend because of the errors) seems to report the wrong temperature in that case: My setpoint is 248°C for ABS, but even if it is reporting 248 unstable it is printing much hotter! A lot of smoke and very bad printing results... Going back to dc42 109r with the same gcode file provides the expected result again.
Not sure if the 2 errors (ajax and temperature) are somehow related, because I couldn't print without getting the error.

Quote
markdoll01
Just a question, I see you removed the Spool Menu from the interface to load and unload filament. Any reason why - I liked the options.

Quote
chrishamm

Quote
pantau
I get these errors a lot!
But what is even more severe: Hot end temperature regulation is very unstable (+-5°C) and also PanelDue (no webend because of the errors) seems to report the wrong temperature in that case: My setpoint is 248°C for ABS, but even if it is reporting 248 unstable it is printing much hotter! A lot of smoke and very bad printing results... Going back to dc42 109r with the same gcode file provides the expected result again.
Not sure if the 2 errors (ajax and temperature) are somehow related, because I couldn't print without getting the error.

That's quite weird. Can you post your config.g so I get an idea how your heaters are configured? Also, when using my latest firmware, could you attach Pronterface or Arduino IDE while trying to use the web interface? If you can, please make a Wireshark dump too.

Yesterday I tested the new firmware and web interface on another setup and although I had gotten an AJAX error about every 30 seconds with previous versions, none showed up after two hours of printing.

Quote
chrishamm
pantau, could you try out this binary instead? [www.dropbox.com] I think I've found the cause for this, sorry for the trouble. Also, can you confirm you were using DWC v1.10 while the AJAX errors showed up? If you're still on an older version (pre-1.08), you can use FileZilla as well to update all web interface files. Just make sure you limit the number of concurrent connections to 1 if you try this.

Quote

- Improved warm-up detection and estimations in the PrintMonitor class
- Removed unused variables from the Platform class
- Emergency stop no longer turns off ATX power to keep the fans running
- Slightly improved closed connection handler in the Network class
- Bug fix: Swapped ADC channels were not sampled
- Bug fix: M562 didn't accept the bed heater
- Other minor changes

Quote

Bug fix: Some time variables were not properly initialised during initialisation (only relevant if you are on 1.09w)
Bug fix: When adjusting the thermistor series resistance, the thermistor overheat sums were not updated

  LD      RepRapFirmware.elf
P:\3dprinting\firmware\Duet\RepRapFirmware-ch\Release\obj\ethernet_sam.c.o: In function `start_ethernet':
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\EMAC/ethernet_sam.c:174: warning: u
ndefined reference to `ethernetif_init'
P:\3dprinting\firmware\Duet\RepRapFirmware-ch\Release\obj\ethernet_sam.c.o: In function `init_ethernet':
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\EMAC/ethernet_sam.c:202: warning: u
ndefined reference to `ethernet_hardware_init'
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\EMAC/ethernet_sam.c:204: warning: u
ndefined reference to `ethernetif_set_mac_address'
P:\3dprinting\firmware\Duet\RepRapFirmware-ch\Release\obj\ethernet_sam.c.o: In function `ethernet_task':
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\EMAC/ethernet_sam.c:250: warning: u
ndefined reference to `ethernetif_input'
P:\3dprinting\firmware\Duet\RepRapFirmware-ch\Release\obj\ethernet_sam.c.o: In function `ethernet_set_rx_callback':
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\EMAC/ethernet_sam.c:265: warning: u
ndefined reference to `ethernetif_set_rx_callback'
P:\3dprinting\firmware\Duet\RepRapFirmware-ch\Release\obj\lwip_timers_141.c.o: In function `sys_timeouts_init':
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\Lwip\lwip\src\core/lwip_timers_141.
c:249: warning: undefined reference to `sys_now'
C:\Users\Jackal\AppData\Local\Arduino15\packages\RepRap\hardware\sam\1.1.1\libraries\Lwip\lwip\src\core/lwip_timers_141.
c:249: warning: undefined reference to `sys_now'
P:\3dprinting\firmware\Duet\RepRapFirmware-ch\Release\obj\Network.cpp.o: In function `Network:pin()':
P:\3dprinting\firmware\Duet\RepRapFirmware-ch/Network.cpp:458: warning: undefined reference to `ethernet_establish_link'

Quote
voi9viper
I apologize for newbie questions, but I just got my printer running with the latest dc42 1.09r code, and www files. Should I be using your firmware branch instead? It's a delta printer with a duet 0.85 board. The web interface no longer tracks layer changes for some reason. This changed mid print. Before reporting any bugs I want to be sure I'm using the correct software.