@dc42 That sounds plausible. By now I wish I had not cheaped out on the 0.6, but it became a too good a deal when the DuetWifi becaime popular 😉 But it still works just fine. I will certainly buy a new one some time, but that will not be for my Rostock V2, but probably for a custom design.

I have to Probe to 0.01mm repeatable and must be able to make Sure the value i apply ist consistent.

This is to calibrate the Offset of my Z-Probe, the distance to the nozzle gets measured by another Probe in the system. And this calibration must be Filly Automatic, without a possible wrong measurement, which would infect every following measure.

Thank you for the report.

@wildblue said in Bes conpensation varies depending in z-height:

Did i Understand this Feature the wrong way?

That's easy to verify. Turn off compensation taper and repeat your experiment.

I believe this is a known bug. See post

I have already switched from 1.22.6 to 2.04.

I produce printers and always have the same config and firmware on them.

Lan cable is certainly not a problem since I have tested it on other printers and there are no problems.

If this is a guarantee case, I will be happy to discuss this with roland.

thank you reformatting the sd card seemed to fix the problem. thank you
for the quick replay. I would have never thought of that possibility.

@deckingman said in names not showing properly after upgrade to webcontrol 2:

M563

Thanks. Looking much better now.

I can confirm this is happening with latest stable firmware/web control
Cory

My guess is that it's caused by interference from another device. See https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors, especially the bit about trying a different WiFi channel.

@dc42

Tried upgrading to firmware 2.05RC2. No change.

Figured it out. both my computer and cell phone were in "Public network mode" and wouldn't communicate with other devices on the network. Thanks for the help, probably wouldn't have figured it out without it.

Not sure what it was, but since I updated the firmware all is good.

@kylemoo said in Connected via web control then next day can't connect?:

Does that happen a lot with Duet2wifi boards?

No more than any other WiFi device, in my experience.

If your Duet is set up to use DHCP, so gets its address from the router, connecting using the printer name with .local on the end means you don't need to keep track of the IP address if the router resets. However, using the printer name to connect will depend on your router and your PC supporting mDNS/DNS-SD (also known as zeroconf and Bonjour, longer article about this here), which is the network protocol used for this. Generally, routers less than 5 years old should support it. For your PC, see this article, but basically Apple Macs (and, I think, Windows 10) support it, while Linux and Windows (other versions) need to have it installed.

Alternatively, set your Duet to a fixed IP address, using M587 to update the stored WiFi access point information (run this from the console), eg:
M587 S"your_wifi_network_SSID" P"your_wifi_password" I"192.168.0.114"
Then the IP address you connect to will always be the same.

Ian

you can open your browser directly to
http://<ip.of.printer>/reprap.htm
to go to the old version. just set a bookmark

thanks i'll give it a go.

There is a known incompatibility between RRF 2.05RC1 and DWC2. Either revert to DWC 1.22.6, or revert to RRF 2.03, until RRF 2.05RC2 us released (hopefully tomorrow).

@jdjeff58 said in DWC Local cache:

@droftarts said in DWC Local cache:

What firmware version? The config.g says 2.03, but send M115 and post response.

Ian

Another Duet curveball. The RRF config tool (https://configtool.reprapfirmware.org/General) does NOT have 2.04 as a choice in the drop down. I showed my FW version in the first line of my post 2.04

M115

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.04 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-11-01b1

Thanks for reporting this! We'll get it changed. 2.04 and 2.05 are upwards compatible with 2.03, so select 2.03.

@dc42 thanks for your answer.
Are layer comments the same for every slicer?
Could you answer two more questions, please:

How DWC determines layer change? If I'll place any G-command (one or block of commands) with summary Z, DWC will take it, divide per layer height, then show me correct info? You wrote, that it looks for Z moves , so, it looks like "last Z" minus "pre-last Z" = "layer height" for DWC, then "last Z" / "layer height" = "layer quantity"?

Yes. Confirmation dialog. ITS Missing.