Paneldue crashing?
-
Its on the settings screen on the panel
-
thanks
1.23.2
-
I suggest upgrading to 1.24 and seeing whether the issue still manifests itself.
https://github.com/Duet3D/PanelDueFirmware/releases/tag/1.24
I would also suggest upgrading the duet firmware to 2.05.1
https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1 -
How are you connecting the Paneldue to the Duet? 4 wire connector or ribbon cable? Have you set a specific baud rate for the panel?
-
The printer is in the middle of a 4 day print. I did update the DUET firmware (not paneldue yet as I thought I would try in stages) but that has not had any effect (still crashing)
Connecting to the Paneldue with the 4 wire connector, not set a specific baud rate
Cheers
-
Update the panel when you get a chance. How long is the 4-wire cable? I have had to replace the 4-wire cable that came with the panel at one point due to a similar connection issue. Replacing the cable solved it for me. It may have been a bad crimp or even wire weak spot. Not sure. I never tried to get too deep once I swapped it out and the new one worked. I did use that same cable on a different Paneldue where it seemed to work fine though, so who knows. cosmic rays.
-
I have also noticed that when the paneldue 'freezes' the wifi connection also drops and there is no way to connect to the DUET. IT will finish the print it is on, but if anything pauses (filament run out etc) you cannot restart, or even see the message to work out why it has paused. Hopefully this is a clue
-
Are you able to safely connect a usb cable and log the console to see if there are any hints, and if not enable some debugging with M111 and repeat?
Duet recommends YAT, my preference is RealTerm as i know it will write logs to files and timestamp the entries if you ask nicely. By all means use YAT if you have it installed and it can log and timestamp.
-
I can try that. Just started another 24 hour print for a customer, so not too bad to wait. Not used YAT very much at all apart from initial setup, and never used RealTerm, but will give it a go.
If I used RealTerm how would i get it to write the log file repeatedly?
Cheers
-
@CTRDevelopments said in Paneldue crashing?:
If I used RealTerm how would i get it to write the log file repeatedly?
It has a capture tab, just choose filename and timestamp and start it (it will insist on "direct capture" of you enable timestamp i.e. you will not see it while it captures, but you could monitor the output file in another application)
-
sorry for late reply
Although it didnt hang, I logged WiFi and got (it did seem to dc from the wifi although the wifi has been perfect and this PC is on the same network)
1597693361,Leadscrew adjustments made: 0.216 0.148 0.287, points used 9, deviation before 0.278 after 0.196
1597693429,Leadscrew adjustments made: 0.012 -0.003 -0.039, points used 9, deviation before 0.187 after 0.186
1597693595,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597693850,72 points probed, min error -0.269, max error 0.419, mean 0.091, deviation 0.158
1597693850,Height map saved to file heightmap.csv
1597699390,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597705873,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597708531,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597708760,WiFi: bcn_timout,ap_probe_send_start
1597711968,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597714967,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597715138,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722743,WiFi: bcn_timout,ap_probe_send_start
1597722746,WiFi reported error: Lost connection, auto reconnecting
1597722746,WiFi: ap_probe_send over, rest wifi status to disassoc
1597722746,WiFi: state: 5 -> 0 (1)
1597722746,WiFi: rm 0
1597722746,WiFi: pm close 7
1597722746,WiFi: wifi evt: 1
1597722746,WiFi: STA disconnect: 200
1597722748,WiFi: scandone
1597722748,WiFi: state: 0 -> 2 (b0)
1597722748,WiFi: state: 2 -> 3 (0)
1597722748,WiFi: state: 3 -> 5 (10)
1597722748,WiFi: add 0
1597722748,WiFi: aid 4
1597722748,WiFi: cnt
1597722748,WiFi:
1597722748,WiFi: connected with CTRDevelopmentsWiFi, channel 6
1597722748,WiFi: dhcp client start...
1597722748,WiFi: wifi evt: 0
1597722753,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722758,WiFi: pm open,type:2 0
1597722770,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722772,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722774,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722776,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722778,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722780,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722782,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722784,WiFi: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
1597722786,WiFi reported error: Timed out while trying to connect to CTRDevelopmentsWiFi
1597722786,WiFi: sleep enable,type: 2
1597722786,WiFi: sl
1597722786,WiFi: scandone
1597722786,WiFi: usl
1597722786,WiFi: state: 5 -> 0 (0)
1597722786,WiFi: rm 0
1597722786,WiFi: pm close 7
1597722786,WiFi: del if0
1597722786,WiFi: usl
1597722786,WiFi: mode : null
1597722786,WiFi: wifi evt: 1
1597722786,WiFi: STA disconnect: 8
1597722786,WiFi: wifi evt: 8
1597757185,Done printing file
1597757185,Finished printing file 0:/gcodes/Electronics Cover.gcode, print time was 17h 46m -
@CTRDevelopments said in Paneldue crashing?:
: ../src/Listener.cpp(66): refused conn on port 80 already 4 conns
do you have multiple clients / processes connecting to the duet?
-
Not that I know of. All I have is my single PC that I use for uploading. Nothing else is connected. Is there any way to see what those connections are?
-
Hi there
some time ago I have also expirienced the same behaviour of freezing communication between PanelDue and DuetWifi. And it allways happens when the Wifi Module reports a lost of connection.
After running all latests updates, both on PanelDue and DuetWifi and resetting the Wlan Hotspot (finding a better channel) this issue was gone for a while.
But now this week it started again.
Today I have rebootet my Hotspot, to hopefully find a new and better 2.4GHz channel and therefore creating a stable connection.In my opinion the freeze of the comm is related to the procedure how the DuetWifi handles the Wifi connection initialisation and time out.
I have also noticed, that right after restart of the DuetWifi and before the Wifi conn is established the communication between the PanelDue ant the DuetWifi is extremly delayed.
For example:- Switch on DuetWifi
- run Home all (during this period the Wifi Conn is not established as the machine has something different to do...)
- after Home all and without promt of Wifi Conn-> try to activate a Makro or reading out files via PanelDue...extreme delay in 10+ sec
- right after the Wifi has established a stable Connection everything works fine and in usual speed
One more thing. The "Wifi lost conn" occurs shortly after the first connection build up (prompt by Duet) or even during a print.
Only the STOP button on the Paneldue keeps working!Any ideas?
-
Any comments at all?
-
@Hornetrider said in Paneldue crashing?:
Any comments at all?
Please create a new thread with your issue. Include your config.g and homeall.g files since you mention those. Include what firmware version on the duet and paneldue. Thanks.
-
HI @Phaedrux
why a new thread if everything is explained here?
Please find requested data below.xxxxxxxxxxxxxxxxx
PanelDUE FW: 1.24
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Duet WiFi Server Version: 1.23
xxxxxxxxxxxxxxxxDiag:
Send code...
10.9.2020, 20:26:29 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6J9DD-3SN6R-1SVB9
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 91948 of which 36 recycled
Exception stack ram used: 560
Never used ram: 8012
Tasks: NETWORK(ready,640) HEAT(blocked,1240) MAIN(running,3740) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 84:43:09 ago, cause: software
Last software reset at 2020-09-07 07:42, reason: User, spinning module GCodes, available RAM 8028 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 10
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 390.4ms, max retries 0
MCU temperature: min 32.1, current 34.0, max 36.3
Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/173
Driver 1: standstill, SG min/max 0/155
Driver 2: standstill, SG min/max 0/781
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max 0/176
Date/time: 2020-09-10 20:26:15
Cache data hit count 4294967295
Slowest loop: 84.39ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 102, MaxWait: 82940312ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 7, completed moves: 7, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 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: 391.94ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address ec:fa:bc:2d:e8:d1
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25672
WiFi IP address 192.168.1.110
WiFi signal strength -39dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
10.9.2020, 20:26:11 Connected to 192.168.1.110
XXXXXXXXXXXXXXXXXX
Config:
M552 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S0 ; Drive X goes backwards
M569 P1 S1 ; Drive Y1 goes forwards
M569 P2 S0 ; Drive Z goes forwards
M569 P3 S1 ; Drive E0 goes backwards
M569 P4 S0 ; Drive Y2M584 X0 Y1:4 Z2 E3 ; Apply custom drive mapping
; Microstepping
M350 X32 Y32 Z16 E16 I1 ; Configure microstepping without interpolationM92 X160 Y160 Z1600.00 E410 ; @32 X and Y Ratio 24:20 (2020.01.12)Set steps per mm for Bondtech BMG Extruder
; Speed & Acceleration
M566 X600.00 Y600.00 Z80.00 E1200.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X8000.00 Y8000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)
;M203 X8000.00 Y8000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)M201 X800.00 Y800.00 Z45.00 E3000.00 ; Set accelerations (mm/s^2)
;M201 X800.00 Y800.00 Z30.00 E3000.00 ; Set accelerations (mm/s^2); Motor Current
M906 X1000.00 Y1000.00 Z900.00 E950 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S5 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X295 Y330 Z298 S0 ; Set axis maxima; Endstops
M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2; Z-Probe Inductive
;M558 P5 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
;G31 P500 X0 Y0 Z1.42 ; Set Z probe trigger value, offset and trigger height
;M557 X5:170 Y5:275 S40 ; Define mesh grid; BLTouch
;M307 H4 A-1 C-1 D-1
;M558 P9 F100 H3 R0.3 T7000 A5 B1 ; Set Z probe type to switch and the dive height + speeds
;G31 P25 X-40 Y40 Z2.26 ; Set Z probe trigger value, offset and trigger height
;M557 X5:215 Y5:295 S55 ; Define mesh grid; Precision Piezo
M558 P8 C"zprobe.in+zprobe.mod" I1 R0.4 H2 F420 T3000 A5 B0 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z-0.5 ; Set Z probe trigger value, offset and trigger height
M557 X5:285 Y5:330 S93 ; Define mesh grid; Laser Filament Sensor
;M591 D0 P5 C3 R130:280 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm comparison length, disabled; Rotating Magnet Filament Sensor
M591 D0 P3 C3 R70:130 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm comparison length, disabled; Heaters RRF3.0x
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Heaters RRF2.05
;M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
;M143 H0 S120 ; Set temperature limit for heater 0 to 120C
;M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
;M143 H1 S280 ; Set temperature limit for heater 1 to 280C; 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; Board Cooling
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as thermistor on pin e1temp for left stepper
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H2:3 L0.15 X1 B0.3 T36:45 ; set fan 2 value; Fans RRF2.05
;M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
;M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P2 T36:46 H100:101:102 ; Set Fan speed to cool MCU; Tools
M563 P0 D0 H1 ; 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; Automatic saving after power loss is not enabled
; Custom settings are not configured
; MCU temp Adjustment
M912 P0 S-9; Miscellaneous
T0 ; Select first tool;load config-override
M501xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Homeall:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Dec 31 2018 02:05:14 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-300 Y-340 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X10 Y10 F6000 ; go back a few mm
G1 H1 X-15 Y-15 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X147.5 Y167 F8000 ; go to first bed probe point and home Z
M140 S50 ; Set Bed to 50DEC
G10 S210 ; Set current tool temperature to 130C
M116 ; Wait for the temperatures to be reachedG30 ; home Z by probing the bed
;play sound
M400
G4 P200
M300 P200 S523.25
G4 P200
M300 P200 S659.25
G4 P200
M300 P200 S739.99
G4 P250
M300 P285 S880.00
G4 P450
M300 P285 S880.00
G4 P285
M300 P625 S1108.73
G4 P200G90
XXXXXXXXXXXXX
- WiFi -
-
@Hornetrider said in Paneldue crashing?:
why a new thread if everything is explained here?
because it gets confusing for people who will start to get mixed up.
-
@Hornetrider said in Paneldue crashing?:
why a new thread if everything is explained here?
Because this isn't your thread and it becomes incredibly difficult to keep the information straight. If you think this thread is relevant, include a link to it. It may seem draconian and unnecessary to you, but we ask that each individual issue be contained in it's own thread for the benefit of those trying to help you resolve it.
-
