Duet Web control is not available at time of printing
-
@Phaedrux
Good. After the work is checked. -
@Phaedrux
After the transfer of the Ethernet cable from the printer body, hovering stopped interface (tested on a daily print interface can be accessed at any time) -
@DronBroks said in Duet Web control is not available at time of printing:
@Phaedrux
After the transfer of the Ethernet cable from the printer body, hovering stopped interface (tested on a daily print interface can be accessed at any time)Any new infos here? I have also a problem with network connection. Sometimes I lost connection (mostly after upload a file - bigger then 10 mb)
-
@jovo0911 Might want to start a new thread with your specific details.
-
Good afternoon!
Problems continued, but less frequently. Most often, the problem appears when you create a folder on the memory card, or transfer to the card volumetric files. Sometimes the interface freezes during long-term work. And it is such that when downloading files pauses printing for a split second. -
@DronBroks Can you confirm that you have switched to x16 microstepping?
Do you have a new SD card to test with?
-
@Phaedrux Yes, I switched to 1x16 microsteps. Perhaps the reason is actually in the memory card. I’m not very fast. Today I will buy a new one and check with a new card
-
@Phaedrux
; Configuration file for Duet Maestro (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Sep 23 2020 13:34:11 GMT+0300 (Москва, стандартное время); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M80
M550 P"Dron Printer" ; set printer name
M669 K1 ; select CoreXY mode; Network
M551 P"" ; set password
M552 P192.ххх.ххх.ххх S1 ; enable network and acquire
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 D3 ; physical drive 0 goes forwards stealthChop2
M569 P1 S1 D3 ; physical drive 1 goes forwards stealthChop2
M569 P2 S1 D3 ; physical drive 2 goes forwards stealthChop2
M569 P3 S0 D3 ; physical drive 3 goes forwards stealthChop2
M584 X0 Y1 Z2 E3 ; set drive mappingM350 X16 Y16 Z16 E32 I1 ; configure microstepping interpolation
M92 X80.00 Y80.00 Z804.875 E1001 ; set steps per mm; Jerk
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) Jerk; Maximum Speeds
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min); Accelerations
M201 X1000.00 Y1000.00 Z100.00 E250.00 ; set accelerations (mm/s^2)M204 P1000 T5000 ; Maximum printing acceleration 1000.0, maximum travel acceleration 5000.0
M906 X900 Y900 Z900 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z240 S0 ; set axis maxima; Endstops
M574 X1 S1 P"!xstop" ; configure active-low endstop for low(min) end on X via pin xstop
M574 Y2 S1 P"!ystop" ; configure active-low endstop for high(max) end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low(min) end on Z
M591 D0 P5 C"e0_stop" R50:140 E4.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 7mm comparison length, enabled; Z-Probe
M558 P9 C"zprobe.in" H5 F120 T3000 ; BLTouch set Z probe type to unmodulated and the dive height + speeds
M950 S0 C"zprobe.mod" ; BLTouch servo/gpio 0 is Z probe MOD pin
M280 P0 S10 ; BLTouch send control signal to BLTouch through servo/gpio 0
M280 P0 S90 ; Send PWM channel 0 the S90 (angle) command
G31 P25 X-2.7 Y-50.6 Z1.54 ; BLTouch set Z probe trigger value, offset and trigger height
M557 X10:290 Y10:290 S20 ; probe from X=10 to 290, Y=10 to 250mm with a mesh spacing of 20mm; Heaters
M308 S0 P"bedtemp" Y"thermistor" R2200 T100000 B3950 A"Stol-Temp" ; configure sensor 0 as thermistor on pin bedtemp
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 heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 130C
M308 S1 P"e0temp" Y"thermistor" R2200 T100000 B3950 A"Nozl_0-Temp" ; configure sensor 1 as thermistor on pin e0temp
; M308 S1 P"e0temp" Y"pt1000" R2200 A"Nozl_0-Temp" ; configure sensor 1 as thermistor on pin e0temp
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
M308 S2 P"ctemp" Y"thermistor" R2200 T100000 B3950 A"Drivers-Temp" ; configure sensor 2 as thermistor on pin сtemp
M308 S3 Y"mcu-temp" A"MCU-Temp" ;; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q1000 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H2 T40 ; set fan 2 value. Thermostatic control is turned on; 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 are not defined
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M501
M200 D1.75 ; set all extruder filament diameters to 1.75mm -
@DronBroks said in Duet Web control is not available at time of printing:
@Phaedrux Yes, I switched to 1x16 microsteps. Perhaps the reason is actually in the memory card. I’m not very fast. Today I will buy a new one and check with a new card
Yes please test with a new SD card. When you do so, replace the files in the /www folder with a fresh set from the DWC 3.1.1 zip file.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/DuetWebControl-SD-3.1.1.zip
Also try with a different ethernet cable, just in case.
-
@Phaedrux said in Duet Web control is not available at time of printing:
Yes please test with a new SD card. When you do so, replace the files in the /www folder with a fresh set from the DWC 3.1.1 zip file.
I replaced the SD card with a new (class 10), the DWC has updated the files, replace the cable. As a result, the DWC fell off after 8 hours printing. On the old card it occurred 5-6 hours after printing
-
@DronBroks said in Duet Web control is not available at time of printing:
Most often, the problem appears when you create a folder on the memory card, or transfer to the card volumetric files.
Can you share one of your volumetric gcode files?
Do you have a large number of nested folders?
Can you try a different ethernet port on your switch/router?
-
@Phaedrux said in Duet Web control is not available at time of printing:
Can you share one of your volumetric gcode files?
And where to put this file?
-
@Phaedrux said in Duet Web control is not available at time of printing:
Do you have a large number of nested folders?
There are many subfolders (each project has its own folder). But this problem does not depend on the depth of nesting. The interface also freezes if you print a file from the root of the card and from a subfolder.
-
@DronBroks said in Duet Web control is not available at time of printing:
@Phaedrux said in Duet Web control is not available at time of printing:
Can you share one of your volumetric gcode files?
And where to put this file?
If it's too large to upload directly you can try zipping the gcode file and then changing the file extension to .txt and uploading that. Otherwise put it on dropbox or google drive and share a link.
@DronBroks said in Duet Web control is not available at time of printing:
There are many subfolders (each project has its own folder). But this problem does not depend on the depth of nesting. The interface also freezes if you print a file from the root of the card and from a subfolder.
I was just speculating that a large number of folders could be causing DWC to spend a lot of time searching recursively through folders causing issues.
One way to test would be to place your SD card in aPC, cut and paste the contents of the gcodes folder to your PC as a backup, and then see if the DWC still has problems responding.
