@dc42:

Can you provide a link to your post in the other thread?

https://www.duet3d.com/forum/thread.php?id=4045#p36563

Since updating to 1.20 release I'd started getting these. I did not get them running the earlier 1.20 betas (going by my downloads I used beta 1, 6 &10) I went to DuetWiFiServer 1.20+1 and 1.20.1RC and it actually seemed more frequent.

I'm now back to 1.20 for firmware, web, and wifi versions, and they're still happening every few minutes. It's the same error others are reporting in DWC: "The last HTTP request has timed out. Please make sure the connection between your device and the board is not interrupted."

Tomorrow I'll connect via usb and use M111 S1 P14 to grab some logs.

Increase the X, Y and Z in G1 S1 X500 Y500 Z500 F2500 in your homedelta to 800+ so you don't have to double tap home when you are stretched out on the build plate.

Yes, RepRapFirmware.bin is the build for the older Duets.

I'm on 1.20.1rc2 on firmware, 1.20+1 for wifi server and, 1.20 rc3 on dwc version. I have set macros up now so I can just use the panel due to reset the wifi turning off then on, I have been speaking to doug and he said to try rolling back to 1.20 on wifi server and try that. Will let ya know how it goes..

There is also another chap on our discord channel that has had the same issues after upgrading his firmware from 1.19 to the 1.20+1 too

@ephemeris:

I've seen this in Firefox as well. I'll guess you have you zoom set to something other than 100%. Try adjusting your zoom and see if that mitigates the bug.

thanx, that was it – fixed it

I am in the process of updating the filament monitor support, and I decided to add support for pulse-type filament monitors at the same time. How many pulses per mm of filament does your sensor produce?

Thank you David.

I'll give that a shot.

Cheers,

Neil

That's a well-known issue. The solution is put a comment starting with ;E or ; E at the end of the G0 or G1 command line that does that movement.

DuetWebControl.bin was used with firmware 1.18 and earlier, when the web server ran on the WiFi module. With 1.19 and later, the web server runs on the Duet main processor instead and the web files are fetched from the SD card. It's because of this big change that the upgrade from 1.18 or earlier to 1.19 or later on the Duet WiFi is more complicated than firmware upgrades normally are.

:C

Eeeeemmmmm… Old trick of polarity...

Mistake.... No... BIG MISTAKE

Sorry

Thanks, that did the trick!

Thanks again. Happily printing now.

@whosrdaddy, thanks for the feedback. It's a shame no-one else has responded.

I have just released 1.20.1RC2 so I will close this thread.

Sorry, just realized you already checked that.

Would you be open to trying to reset your router to factory settings, then re-configuring your SSID name and password?

I'm guessing you've updated to the latest (asus router) firmware, since Asus routers tend to notify you in the console. Perhaps this caused a configuration mis-match.

Thanks DC

Sorry to hear of your problems. What I meant about putting a "T" command in the start code was basically just to make sure that Slic3R had selected the correct tool for the object you want to print. If you don't assign a tool (extruder) to the object then Slic3r will default to not putting a "T" command in the gcode so you can get the situation where you try to extrude with no tool selected.

I find it's easier to enable skirts in Slic3R (not brim), to purge the hot end at the start, rather than using all those manual extrusion commands.

Hi…

Works.... thanks.

threw the whole config out the window and started all over, worked alot better.
still had tons of wifi disconnects though, strangely they stopped immidiatly when I disconnected the LCD display

All set guys…. I got it using SAM. Thank you for your input and Merry Xmas and a Happy New Year