I get the same thing but I had put it down to it being something to do with the very old Laptop I'm using. DWC takes longer to connect than the older version too.

https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

@supset said in Duetwebcontrol interface not loading after upgrade to 3.1.1:

is the firmware and DWC files located all on the SD card?

firmware is written to the processors internal flash memory, it can be written to the internal flash by usb bootloader. the firmware can also self program by executing M997, in which case it will read the binary firmware from the sd card and write it to the processors internal flash.

the only screenshot that is legible suggest that there is an issue with the content if your sd card, its essentially 404 page, there needs to be an index.htm.gz in /www on the cd card.

You'll definitely want to stick with 3.1.1

@Lanovar We've hijacked another persons resolved thread. I think it would be best if you created a new thread with your issue. Include your firmware and DWC version, the example gcode file, your homing file.

@Lanovar said in Layer Count Error:

Isnt that kind of like switching to G91?

Yes that makes sense.

Phaedrux, Thank you for the help that seems to have resolved the issue.

@chrishamm could tell you what has changed.

Documentation will have to be updated to match the new DWC format I suppose.

Release 3.1.1

Do note I've not tried if say IO1.out can be used as a digital input but they would have none of the input protection IO1.in has in hardware - and it would be down to the firmware to allow IO1.out to be configured as an input.

And using IO1.in as an output would probably also be less than ideal; it would only be possible to get it down to about 1v not 0v.

But hopefully you meant you could use IO1.out independent of IO1.in which i hope to be true.

Dear @dc42 thank you for that! I will adapt Danal´s Code for Mircopython. Some changes have to be done. Micropython do not like f-strings ;( Will post the fork then in the orginal thread!

Best

It has been a couple of weeks since I moved the router closer to my printer. I am happy to say that after moving the router to within about a 6ft line of sight with my printer, I have been enjoying DWC undisturbed by constant dropouts, save for one instance today, which I believe I can attribute to mistakenly trying to upload a g-code file into the job list via Slicer while another print was in progress.

I had enough confidence in the system's stability now that I invested in a smart effector & rods for the printer as well and I couldn't be happier with the result.

Thank you to everyone that replied and helped out a new user struggling. When I get around to building a second printer, I know what board I'm putting in it.

Thank you replay
I uploaded www folder know working

@Phaedrux You, too... thanks.

I take a different approach and do things the other way round. That is to say, I keep and maintain "master" copies of everything on a PC and back up to a NAS/cloud storage, then only ever upload to the Duet board.

@Phaedrux Thanks for taking the time to reply! Personally my printer is very compact and small though with a 200x200x250 build volume because I designed it to be foldable and portable so all the electronics are rather efficiently packed in. I don't think there's even much space to stick a Pi Zero W.
I feel like it wouldn't be too hard a software feature to implement but it's beyond my coding skills, at least for now 🙂

@dc42 said in Issue with quoted strings from mobile device:

Does this help https://www.google.com/amp/s/www.howtogeek.com/344310/how-to-turn-off-smart-punctuation-on-your-iphone-and-ipad/amp/ ?

Indeed it does!

Thanks guys

My guess is the klipper isn't reporting the number of visible axes correctly in the rr_status response, or you have somehow configured klipper to have zero visible axes.

@Phaedrux said in Bed Heater settings not appearing in DWC 3.1.1:

; Heaters M308 S0 P"spi.cs2" Y"rtd-max31865" F50 ; configure sensor 0 as thermocouple via CS pin spi.cs2 M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"spi.cs1" Y"rtd-max31865" F50 ; configure sensor 1 as thermocouple via CS pin spi.cs1 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Tools M563 P0 D0 H1 F0 ; define tool 0

Thanks Mate it was the M140 that I was missing