Topics created by wouldstain

Weirdest thing... It's back up now.

WiFi module has been up the whole time (it was responding to pings(ICMP))
Telnet to ports 23 and 80 were getting nothing

I did not connect directly to USB with my workstation and try to print.
I did put a file in the gcode directory on the SD card by hand and was able to print.

I did set up and connect an OctoPi as a possible work around and it did seem to be communicating but I had not had a chance to print with it.

I've been beating my head against my desk for the last 8 hours trying to get this sorted
and I walk away from my desk for few minutes and its back up.

I do not like issues that seem to resolve themselves in this way for obvious reasons.

It may have something to do with burning some sage and swinging a dead chicken around but.... That's dinner so it would have happened regardless.

Just for posterity:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DJM-9178L-L2MS8-6JKDA-3S06M-K8HAP
Used output buffers: 3 of 26 (26 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 76456 of which 12 recycled
Never used RAM 8248, free system stack 96 words
Tasks: NETWORK(ready,37.5%,242) HEAT(notifyWait,0.1%,324) Move(notifyWait,2.9%,292) DUEX(notifyWait,0.0%,24) MAIN(running,59.4%,460) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 01:52:37 ago, cause: power up
Last software reset at 2022-08-15 23:22, reason: User, GCodes spinning, available RAM 8608, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x0c
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 15.3, current 23.6, max 28.3
Supply voltage: min 23.9, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/40/40, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2022-08-29 15:49:42
Cache data hit count 4294967295
Slowest loop: 135.33ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.9ms, write time 14.1ms, max retries 0
=== Move ===
DMs created 83, segments created 27, maxWait 3482734ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 40317, completed 40317, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0: pos 247.50, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== DueX ===
Read count 1, 0.01 reads/min
=== Network ===
Slowest loop: 40.98ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 84:0d:8e:ad:74:86
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24680
WiFi IP address 192.168.1.226
WiFi signal strength -37dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is enabled on port 23
Error: Heater 1 not switched on due to bad model

config.g

@droftarts Will give it a try! Thank you!

@phaedrux done. thank you!

Yes it's a bit unusual to have so many hotfixes on a beta.

https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0

These should be the 7+7 files I think.

@phaedrux Too early to tell. I have a long print job I'm going to kick off tomorrow. I will certainly let you know.

A few days ago I faced the same problem. Tried many ways. Changed the wi-fi channel. Turned on and off DHCP. Rebooted the router. I changed the firmware from 3.4 b 7 to 3.4 rc1. This did not improve the situation in any way. When pinging via cmd, packets were constantly lost and there was a big ping.
444.png

Packet exchange from 192.168.1.10 to 32 bytes of data: The waiting interval for the request has been exceeded. Response from 192.168.1.10: number of bytes=32 time=316ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=207ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=122ms TTL=255 Ping statistics for 192.168.1.10: Packets: sent = 4, received = 3, lost = 1 (25% loss) Approximate receive-transmit time in ms: Minimum = 122 m sec, Maximum = 316 m sec, Average = 215 m sec

I had a spare router. After replacing the router, the problem went away. The ping is minimal. The connection is not lost. Maybe this will help you.

Packet exchange from 192.168.1.10 to 32 bytes of data: Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Ping statistics for 192.168.1.10: Packets: sent = 4, received = 4, Lost = 0 (0% loss) Approximate receive-transmit time in ms: Minimum = 1msec, Maximum = 1msec, Average = 1msec

@wouldstain If you can still print other filament types, then it rules out anything related to Duet hardware or firmware and has to be related to PLA swelling and blocking the heat break area of the hot end. I refer you back to the first post I made on 14th November.

@t3p3tony I did not as it ran for a fairly long time. If there's a way to get sample logs out of it I'd be happy to run it again and provide data.

@wouldstain For peace of mind, you should make a copy of the config files, macros etc.. Just in case the SD card fails one day.