DWC Local cache

jdjeff58

CoreXY machine with bed moving UP TO NOZZLE on Z axis Duet Wifi FW 2.04 DWC 2.04 on Firefox

I'm having problems during BLtouch calibration and I want to try to clear local cache. There is nothing (that I can see) as in the older 1.XX.XX versions of DWC that allows me to do this. I can see a switch to enable local cache storage.

The problem I'm having may or may not be related, but I had this all working 2 days ago. I bring the bed UP TO THE NOZZLE to do G92 Z0. The Z position in DWC Dashboard shows 0.00. Then I do G1 Z10....then G30 S-1 to trigger the BL touch. The Z position showing on the pop up message (and in the console) is now different than the Z position showing on the DWC dashboard by .2 mm. This all worked before where both numbers matched every time I went through this exercise.

I tried doing it over and over and over again with same results. I tried rebooting the Duet by powering off. I remember hearing somewhere that sometimes (especially where height maps are concerned) the local cache can get corrupted and it needs to be cleared. I used to run DWC 1.66.XX and there was a "clear cache" button. I keep looking and can't see a button in DWC 2.04 Is it there and I'm missing it? Or am I getting thrown another Duet curve ball? I found the switch for "Save cache in local storage" and it was apparently enabled by default. I don't even know if this will fix my issue. But I don't know that until I can clear the LOCAL cache.

As a side note, when I first installed DWC 2.04, I saw the switch to "revert to DWC1" Out of curiosity I switched it and apparently made a permanent move to DWC1. I could not see a way to revert back to DWC2 and had to reinstall 2.04 to get it back. Is this yet another curve ball?

Danal

The "enable local storage" in DWC 2 toggles between saving all the parameters that DWC needs in browser local storage vs. on the Duet itself.

This is different/separate from "browser cache".

You may need to clear one or both.

To clear what DWC saves between sessions, click the buttons so that it is saving in local storage. Then use any of several available plug-in tools to examine, and potentially delete, local storage. Note: most of these tools require you to be on the page (i.e. DWC) when you use them to look at local storage.

To clear ordinary browser cache is a keystroke sequence when reloading the page. I'm not sure exactly what that is for Firefox; it is usually holding shift, or ctl, or alt, while clicking refresh. Another way to the same goal is to have the developers console open when reloading the page; F12 opens this console in most browsers. You don't need to do anything other than have the console open, and the browser will bypass all cache.

Summary: To clear DWCs saved stuff, make it local storage, and use a plugin to delete local storage. To clear the overall browser cache, follow your browsers instructions and/or open the developer console.

droftarts

I'm not sure why you are getting different values in the console and dashboard. Have you applied a Z offset to the probe? Can you post your config.g?

As far as I'm aware, the 'local cache' is for holding gcode files for editing (see https://duet3d.dozuki.com/Wiki/Duet_Web_Control_Manual#Section_Editing_a_print_G_Code_file), and for holding a list of files on the Duet (see https://duet3d.dozuki.com/Wiki/Duet_Web_Control_Manual#Section_G_codes though this does refer to the older version of DWC), which I don't think relates to this issue. Usually refreshing the browser page (F5) is enough to clear caches.

To switch between DWC 1.x and 2.x, remove the "reprap.htm" from the browser address bar. That should take you back to 2.x.

Ian

jdjeff58

@droftarts said in DWC Local cache:

I'm not sure why you are getting different values in the console and dashboard. Have you applied a Z offset to the probe? Can you post your config.g?

I'm not sure either. The whole purpose of what I'm doing here is to record the Zoffset in the config.g file. Before this glitch or bug or whatever, the numbers on the dashboard and the popup numbers were identical other than the resolution. (i.e 4.25 on the Dashboard vs. 4.249 on the pop up). Now the numbers are off by way more than that. The only thing my config will show you is that I recorded the latest value. I'm using the higher resolution value that comes up in the console but I'm left wondering which one is accurate.

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.2 on Sat Nov 09 2019 21:10:45 GMT-0500 (Eastern Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name

M669 K1 ; select CoreXY mode

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 D3 ; Drive 0 goes forwards, CoreXY_1
M569 P1 S1 D3 ; Drive 1 goes forwards, CoreXY_2
M569 P2 S1 D3 ; Drive 2 goes forwards, Z Motor
M569 P3 S0 D3 ; Drive 3 goes forwards, Extruder
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X79.80 Y79.80 Z282.70 E830.00 ; set steps per mm (.9 deg extruder motor)
M566 X420.00 Y420.00 Z39.60 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X4200.00 Y4200.00 Z2298.00 E2500.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z75.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I65 ; set motor currents (mA) and motor idle factor in per cent
M84 S60 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z-0.5 S1 ; set axis minima
M208 X347 Y285 Z364 S0 ; set axis maxima

; Use this if you have BL Touch
M574 X2 Y2 S0
M574 Z1 S2 ; Define Z to use Probe. Home to Min (BL Touch Nozzle)

; Z-Probe
M307 H3 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X28.9 Y0 Z4.054 ; set Z probe trigger value, offset and trigger height
M557 X0:347 Y0:285 S65 ; define mesh grid

; Heaters
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C

;Part Fan
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings
M572 D0 S0.05 ; Extruder Pressure Advance

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

droftarts

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

Ian

jdjeff58

@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

dc42

@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.