Web page not loading
-
@that-guy-E said in Web page not loading:
I've been able to connect and access the web page without issue previously
did you update anything?
if not it could be a failing sd card -
@Veti No changes over the past couple months. SD card is only about a year old. 90% of gcodes are run from an expansion SD not, the onboard.
Planning to try to connect after print is complete.
-
What happens when you try to load the web page? Can you ping the Duet?
-
Does it persist after the print is over?
-
@dc42 @phaedrux
I was able to connect after the print was complete. I started a new print and after 5-10 minutes into the print I was no longer able to load the web page. ping results during the time I was unable to load the web interface:Pinging 11.22.33.44 with 32 bytes of data:
Reply from 11.22.33.44: bytes=32 time=3ms TTL=255
Reply from 11.22.33.44: bytes=32 time=3ms TTL=255
Reply from 11.22.33.44: bytes=32 time=2ms TTL=255
Reply from 11.22.33.44: bytes=32 time=23ms TTL=255Ping statistics for 11.22.33.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 23ms, Average = 7msAn interesting thing I noticed is that after being unable to open the web interface, I hit pause on the panel due and printer froze then the Duet rebooted. After reboot the pause function worked as expected.
Started another print and again unable to open web interface after 5 minutes of printing. filament ran out and unit froze then rebooted. known good filament runout routine is on the card.
-
Can you please provide the results of M122 and the contents of your config.g file?
-
can you move the wires on the duet, maybe ones close to the wifi module.
-
M122 after the filament runout, freeze, and reboot
7:57:23 AMM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later Board ID: 08DLM-996RU-N85T0-6J9FJ-3S46R-9ST3P Used output buffers: 3 of 24 (9 max) === RTOS === Static ram: 25712 Dynamic ram: 93248 of which 308 recycled Exception stack ram used: 320 Never used ram: 11484 Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160) Owned mutexes: === Platform === Last reset 15:34:49 ago, cause: software Last software reset at 2021-01-06 16:22, reason: Stuck in spin loop, spinning module GCodes, available RAM 11144 bytes (slot 0) Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f80f BFAR 0xe000ed38 SP 0x20001efc Task 0x5754454e Stack: 00446a47 0044a4ce 41000000 e0000000 41140664 00000000 00000000 3331bb4c 40000000 3f317200 b5ddea0e 388a5455 4209f43c 00000000 4768c200 37d33333 43108df2 80000000 40e0051d 20000010 00000004 00000000 00000004 Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 22.5, current 22.8, max 36.4 Supply voltage: min 24.1, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 2021-01-07 07:57:22 Cache data hit count 4294967295 Slowest loop: 6.93ms; fastest: 0.07ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === DDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 15.65ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is providing access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address ee:fa:bc:5b:47:f3 WiFi Vcc 3.39, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23264 WiFi IP address 11.22.33.44 Connected clients 1 Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: no filamentconfig:
; Configuration file for Duet WiFi (firmware version 2.02B) ; SINGLE EXTRUDER ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P1 ; Set firmware compatibility to look like RepRapFirmare M669 K1 X-1:-1:0:0 Y1:-1:0:0 Z0:0:1:0 U0:0:0:1 ;Select CoreXY mode ; Network ;WAP M552 S0 ;WIFI ON G4 S1 ;WAIT 1 SECOND M552 S2 ; Enable wap ;M552 S1 ;ENABLE NETWORK AS CLIENT G4 S1 ;WAIT 1 SECOND ; Drives M569 P0 S1 ; Drive 0 goes forwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S0 ; Drive 3 goes backwards M569 P4 S1 ; DRIVE 4 GOES forwards M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation M92 X80 Y80 Z2072 E415:415 ; Set steps per mm M566 X1000 Y1000 Z30 E300:300 ; (jerk) Set maximum instantaneous speed changes (mm/min) was M203 X24000 Y24000 Z500 E7000:7000 ; Set maximum speeds (mm/min) M201 X2000 Y2000 Z1000 E2000:2000 ; Set max accelerations (mm/s^2)' M906 X1600 Y1600 Z1600 E1600:1600 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-20 Y0 Z0 S1 ; Set axis minima M208 X485 Y325 Z635 S0 ; Set axis maxima ; Endstops M574 X2 Y2 S1 ; Set active high endstops ; Z-Probe M574 Z1 S2 ; Set endstops controlled by probe M307 H3 A-1 C-1 D-1 ;REASIGN HEATER M558 P9 H5 F100 T10000 ; Set Z probe type to bltouch and the dive height + speeds G31 X28 Y0 Z0.0 P25 ;Set Z probe trigger value, offset and trigger height M557 X80:470 Y10:320 P6:5 ; Define mesh grid ; Heaters M305 P0 S"BED HEATER" T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for BED HEATER M143 H0 S105 ; Set temperature limit for BED HEATER M305 P1 S"LEFT HOT END" T100000 B4725 C7.06e-8 ;R5000 ; Set thermistor + ADC parameters for LEFT HOT END M143 H1 S285 ; Set temperature limit for LEFT HOTEND ;M307 H1 A301.1 C132.2 D2.3 S1 V24.6 ;SET TUNE VALUE FOR 40W LEFT EXTRUDER M307 H1 A322.2 C102.3 D3.9 S1 V24.1 ;SET TUNE VALUE FOR 50W LEFT EXTRUDER ; Fans M106 P0 S0.0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S0.0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off ; Tools M563 P0 S"LEFT EXTRUDER" D0 H1 ; Define tool 0 G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets G10 P0 R20 S200 ; Set initial tool 20 active and standby temperatures to 20C ;ESTOP I/O M581 E2 T0 S1 C0 ;when drive 5 home sensor is low, EXECUTE E-STOP ;M582 T0 ;DOOR I/0 M582 T1 M581 E3 T1 S0 C0 ;WHEN DRIVE 6 HOME SENSOR IS low, EXECUTE PAUSE M582 T1 ;FILAMENT MONITORING M591 P1 D0 C3 S1 ;SET FILAMENT MONITOR EXTRUDER 0 ENDSTOP -
@that-guy-E said in Web page not loading:
Last reset 15:34:49 ago, cause: software Last software reset at 2021-01-06 16:22, reason: Stuck in spin loop, spinning module GCodes, available RAM 11144 bytes (slot 0)
It's tempting to suggest you update to RRF3 at this point. You may benefit from some bug fixes and improvements. 3.2 was recently released. If you do choose to upgrade you'd have to upload the 3.0 zip file, then the 3.2 zip file, to the system tab.
Your config files would need some updating/replacement. Having a config tool generated version to compare against is helpful.
https://configtool.reprapfirmware.org/Start
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview -
Is there a known bug that RRF3 addresses on the web interface or memory management side? I'm using these controller for an OEM printer applications as well as some slightly different applications. There haven't been reports of this issue on units in the field; but I'm wondering if this will arise over time.
-
Well development on RRF2 is basically finished now and moved to RRF3, so there have been quite a lot of fixes and improvements and changes since 2.05. Basically a full year of development between 2.05 and 3.2.
https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md
-
I will take a closer look at RRF3 and see if I can implement.
An interesting thing of note is i left the web page open for the first 10 minutes of the print and I did not appear to disconnect. I then closed the page and then tried to reload the page with out any success.
-
It may be worth trying a fresh SD card. The web files are loaded from the SD card, so if they can't load, the page can't load.
