New Duet Web Control 1.10 and RepRapFirmware 1.09v-ch

Quote
markdoll01
Thank you Chrishamm,

Just updated my Ormerod 2 with your new firmware and also the updated Web Interface. All went smooth. Very happy about the new firmware update feature via Web Interface! I always left my controller box open because of firmware updates and finally now after a year I actually screwed the lid on :-) . Hope to not having to open it again, Thank you for continuing with upgrading and enhancing the Duet!

Quote
Vertikar
Someone had actually created a part to print to press the buttons without opening the case which I've used sucessfully, but I can't find who did it right now.

Quote
chrishamm
Did you mean these? [www.thingiverse.com] In fact there are multiple ways to enter the bootloader, but until now you always had to connect a USB cable to flash a newer firmware:

Quote
chrishamm
pantau, thank you for that Wireshark dump. I have addressed the underlying problem in my new firmware release, please feel free to give it a try and let me know if that fixes your problem. I tried to flash dc42's firmware using the web interface as well, but this actually resulted in the first 512 bytes of flash memory being erased. Unfortunately I don't have a good explanation for this yet, because the flasher binary compares the data as soon as it's written (which succeeds) and when I try to flash my own firmware binaries via the web interface, it always works. I will try to fix this as soon as I get an idea why it's happening though.

Quote
pantau
But I had to cycle power on my printer during print (still have an ATX power supply with a switch). I did this very fast, like off-on in less then 1s.
After that T0 (heater 1) was stuck at -273 and T1 (heater 2) at 50.
I first did suspect a hardware defect after fast power cycle, but as I couldn´t find one I did flash 1.09r from dc42. That fixed the problem!
I also checked the sd card but no file was corrupt.
Could it be that something in the firmware is overwritten on a fast power cycle?

Quote
chrishamm
I've just pushed version 1.09x to my GitHub repository. This problem wasn't caused by the firmware update process, but because I forgot to initialise some time variables after I had restructured some initialisation routines in my previous release. I'm not sure why this problem didn't show up on my Ormerod 1 though, but I could easily reproduce it on my Ormerod 2.

Quote
appjaws1
Just thought you would like some feedback.
I was using dc42's firmware and web control 1.08 before and had no disconnection problems.
With your 1.09x-ch I have had many disconnections - ajax error
Also, the print status detail is not being updated, I can only get Print Duration updated after a page refresh or reconnection.

I am using simply3d.
The old web control/firmware worked well.

Quote
appjaws1
Tried your beta3 firmware and I still have the same result.
On the print screen, as soon as I confirm which a file to print, the %completion is 100% and all of the detailed boxes are at 0.

I am using windows 10 and the new browser and slicing is with simplyfy3d.

This is very strange.

Quote
appjaws1
It should work with all popular browsers---shouldn't it?

Quote
appjaws1
It should work with all popular browsers---shouldn't it?

Quote
appjaws1
Well, as usual it's been my fault.

with 1.09x-dc42-beta3 and web interface 1.10 all works in firefox and chrome.--- will I ever learn.

Thanks for all your efforts

Quote
appjaws1
I was using edge in windows 10, I have just tried again and it will not show the data.

Quote
Fpex
It that a newer version than 1.09r-dc42 (2016-01-16) (the one I am using)?