I'm sorry I haven't been able to respond earlier, but now I have some time again to investigate your problem.

Assuming you are using a Duet WiFi, can you confirm you are using my latest Duet WiFi Server version 1.03? There was an issue in prior versions that caused empty responses to be sent to the web interface and this issue looks exactly like it.

Although I doubt an older version will resolve this problem, you can actually get older versions from my GitHub repository by looking through the list of commits. Here a link to the 1.12 DWC files, but be aware that it may not work properly with the latest firmware version: https://github.com/chrishamm/DuetWebControl/commit/edf9c9ba3f1148d67fbafeae0d6b20042705cb2a

0 chrishamm committed to chrishamm/DuetWebControl Packages for first-gen Duets and Duet WiFi added

I had an issue after downloading the .bin file was only 43k, I was about to flash it when I noticed, so I downloaded it again and it was 260kb or so which is the right size. Until the webinterface can do an automatic update it's worth checking the file size is right. Any chance of some sort of md5 check or something similar?

No issues with 1.17d though working perfectly for me.

Might be wise to have some sort of confirmation/warning when trying to downgrade firmware.

My friend got this sorted out. After trying for about an hour on my Mac, he said it's impossible to do thanks to not having access to the required Bin folder and not being able to unlock it using terminal. He used Samba on his PC and got it working.

Phewwww. Glad we got there.

TBH I can't fathom the need for extra length on unretract. I think the theory is that during retract, the hobbed bolt squashes the filament a tiny bit so that when it comes to unretract, that part of the filament is now a slightly smaller diameter so needs a bit more. It's probably another of those theories that have never actually been properly tested and evaluated and I'm guessing that in "real life" if any compensation is needed, it would only be a tiny amount - perhaps 1 or 2 percent?

Anyway. Thanks for getting it sorted - I appreciate that it must be difficult because you can't possibly test everything on every combination of machine. - Always happy to beta test

PS. I've already added R0 to the M207 in my config,g

Ian

ok… all is well!

just got around to checking the download in a folder prob... i'm sure you know its working but yes, it is 🙂

Thanks!!!

`Russ

Yes I've tried that before, still no page.

But now it is fixed: 😄
I connected my Iphone to the duetAP, because I wanted to scan the open ports on the duet.
It found the port 80 open and when I opened in safari, I got the wifi-setup-page.

Really odd behaviour, because I've tried everything (clear dns cache, setup VM with clean windows, reset my tablet, even used a console browser…) nothing worked
I never had any problems with other esp8266.

Thanks anyway!

If you bought it directly from me, then you may send it back for testing, and replacement if necessary. Otherwise, ask your supplier.

If after installing this via the web interface I can no longer access the web interface what is the likely cause?

EDIT- A reboot of the machine solved it.

Usually, new versions of RRF will work with versions of DWC one or two versions out of date. The reverse may not be true because new versions o DWC sometimes rely on features in the latest RRF.

You can get any version of RRF or DWC you want from GitHub by using the History feature.

However it's solved I hope there will be some good description of it. I'm not sure how things affect each other and what the routine should be before a print with the current setup.. I'd opt for a KISS solution!

Thank you all sorted now

@StephenRC:

When that G1 Y260 F3000 move occurs, the printer is already at X0 Y0 due to the G1 X0 Y0 F5000 in pause.g. After the moves in cancel.g are acted on, the dwc & paneldue shows X10 Y260. None of the axes positions are outside the defined printer area of 300x270x200, before, during and after.

The G91 has a G90 in the two macros and they only surround the z moves.

The print files that slic3r makes, have a M83 & G90 at the beginning.

Copied the cancel.g file over to the corexy with the DuetWifi. It worked fine, then changed the Y260 to Y300 for the max y on that printer, and it still worked fine.

Updated Duet085 to 1.17b, problem still there. There must be something odd going on with my Duet085. It doesn't always show the M117 on the PanelDue and every so often on power up the ethernet is unresponsive. Since the problem stops by using Y240, I'm not going to worry about it.

ok, i did not think it was possible (yet), and that's ok, 🙂 i was just not for sure if there was some new stuff i was not aware of 🙂

Thanks

~Russ

After a restart it works ok, I hit heater 1, it starts heating up, then home all and it homes while heating.
But when I pause and cancel printing a file and then after the cancel hit heater 1, it starts heating up and waits until it's ready.

Said g-code starts with :

G21 G90 M83 T0 M116 P0

And I have no magic in pause gcode also, just move up and to the center and retract a bit.

As far as I remember there was no such behaviour in 1.16
Perhaps it would be best to update to your todays version and check.

Figured it out.

Heated bed is P0 while Heaters are P1++

[[language]] ; Bed Temperature M305 P0 T100000 B3950 R4700 H0 L0 ; Tool definition - Standard E3Dv6 M563 P0 D0 H1 ; Define tool 0 uses extruder drive E0 and heater 1

Thanks!