Posts made by OneRob

@onerob said in Duet 2 Wifi stopped responding:

Well I think I discovered what happened here. While nothing on the topside of the board was evident, as I unmounted the board and removed it from its case to investigate further, being the neat-freak I am, I routed some wires under the board. What appears happened was when I mounted the board and tightened down the mounting screws, my 24v supply line to my buck converter must have been oriented just right (I'd love to calculate the odds) and got pierced by a solder joint on the board (the Duet 2 Wifi has some long ones). I imagine it didn't initially pierce all the way through but as time went by the vibrations (the board case is mounted on the side of my printer frame) must have caused it to slowly dig until it finally dug deep enough to short out. The vibrations from me mounting my filament spool onto the printer frame in preparation to print must have been what finally did it.

Oh well... Another lesson learned I suppose, albeit a slightly expensive one.

Thank you @elmoret and @jay_s_uk for your responses.

On the bright side, I'm going to use this as an excuse to upgrade to the Duet 3 6HC and finally take it to the next level. I've been wanting to add a laser and a few other things (LEDs, etc.) that the Duet 3 will allow me to do.

Well I think I discovered what happened here. While nothing on the topside of the board was evident, as I unmounted the board and removed it from its case to investigate further, being the neat-freak I am, I routed some wires under the board. What appears happened was when I mounted the board and tightened down the mounting screws, my 24v supply line to my buck converter must have been oriented just right (I'd love to calculate the odds) and got pierced by a solder joint on the board (the Duet 2 Wifi has some long ones). I imagine it didn't initially pierce all the way through but as time went by the vibrations (the board case is mounted on the side of my printer frame) must have caused it to slowly dig until it finally dug deep enough to short out. The vibrations from me mounting my filament spool onto the printer frame in preparation to print must have been what finally did it.

Oh well... Another lesson learned I suppose, albeit a slightly expensive one.

Thank you @elmoret and @jay_s_uk for your responses.

@elmoret Thanks! I'll do that

@onerob Understand, if this is due to something I did wrong, be it loose wiring, lack of providing surge protection (I should know better), etc. I would take full responsibility and own up to the loss (a hundred bucks isn't going to throw me into bankruptcy). I would just like to know what happened. I've really enjoyed working with my Duet over the past several months and I'd love to continue.

@phaedrux 3DMakerWorld, Inc.

@jay_s_uk I purchased it from Amazon on June 22nd of this year. I examined the wiring and it all appears sound. I know looks can be deceiving when it comes to wiring, but I have all wires terminated to Molex KK type connectors and end connectors (VIN, bed & hotend heaters, etc.). When it comes to wiring, I don't cut corners. That being said I know stuff happens but I'm just sick to think my printer's dead right now and I have no explanation as to what went wrong! (I mean, I still have my BTT SKR 2 control board I replaced with the Duet, but I don't want to go back to that!).

@jay_s_uk That's the thing, I don't know where the short would have occurred.. It's not like I was wiring up an external component or something (the last thing I wired up was an accelerometer about a month ago, but that's long since been disconnected after I setup my input shaping). I imagine a power surge could have done it, but as I previously stated the power to the board was turned off (but not disconnected, so I suppose this could have been the cause?). So, what next? Without knowing for sure what happened am I screwed out of a warranty claim?? I certainly hope not I have A LOT of time and knowledge devoted to this.

@jay_s_uk Thank you for your reply. Both PC and power supply are on the same ring so I connecting both and the device still did not show up.

Checking the components, the CPU chip (see attached) gets pretty hot to the touch. Like I can put my finger on it but have to pull it away after 5 secs or so as it becomes too hot to touch. Not sure if this is normal?

Duet 2 Wifi board just stopped responding out of the blue. Diag LED always on, power indicator LEDs appear normal. Unable to connect via USB (no device shows up). Attempted to erase several times, board still not showing up in device list on pc.

I have no idea what just happened... I was preparing for a print, as I've done at least 100 other times. I preheated my bed and hotend via DWC, turn around to load my filament spool and when I turned back around and looked at DWC, it was just spinning saying it was attempting to reconnect. Checked my Wifi LED, it was off, but Diag LED was on.... Odd, so I powered the Duet off, waited for several seconds, powered it back on and same thing. The Power LED's look normal, I believe (VIN blue, 5v red [unsure if that's supposed to be red], 3.3v green). I removed my sd card, attempted to reset but the reset button does nothing. So I powered off and back on without the SD card and everything still the same issue. I then followed the directions in the Duet won't response webpage and I don't even see the Duet show up in the Device Manager, even after multiple erase attempts. Even tried switching USB ports on my pc, as well as USB cables. I'm using a BL Also fyi, I'm using a BL Touch Z endstop so my M558 is P9.

This is very odd, as I've printed at least 100 times with this board without incident and suddenly out of the blue this happens! The only remote possibility I can think of is we had a thunderstorm roll through earlier today, but I had everything shut off so I don't know how that could be the culprit.

Is there anything else I should try aside from everything I already did? I'm out of options here.

Thank you!

@norder Thanks for the info! Yeah I have the CS wire (orange in my case) running by itself (it's paired up with shielding and an unused white wire). Then I have the shielding from that soldered to the cable shielding and both terminated with the GND at BOTH ends. It's working consistently now and I'm just now getting ready to do some input shaping.

If it hadn't been for this forum and everyone who contributed to this topic in one form or another I'd be dead in the water, so a BIG THANK YOU to all of you (of course a special shout out to @dc42 )!!

@onerob So it looks like 5th time's the charm. I decided to scrap it all and start from scratch, got it working and I'm actually collecting data! The new build consisted of:

• another new accelerometer (they're relatively cheap and if the old ones are actually good they'll definitely get used)
• a new (different) USB3 cable
• soldered posts with jst connectors at the accelerometer
• ribbon cable plug at the Duet (ended up tearing apart an old ribbon cable plug and reusing it - see pic).

@cosmowave thank you for your responses, they were much appreciated.

@cosmowave Thank you @cosmowave. Yes I've referred to that post (and 1 or 2 others with the same or similar diagram) and confirmed the wiring many times (to the point of insanity).

@cosmowave config.g

Also, M122 results in case you wanted to see them:

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
Board ID: 0JD0M-9P6M2-NWNS0-7J1DJ-3SD6N-KT3ML
Used output buffers: 3 of 26 (15 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 75308 of which 260 recycled
Never used RAM 9796, free system stack 180 words
Tasks: NETWORK(ready,13.2%,242) HEAT(notifyWait,0.0%,317) Move(notifyWait,0.0%,363) MAIN(running,86.7%,444) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:25:43 ago, cause: power up
Last software reset at 2022-08-23 18:09, reason: User, GCodes spinning, available RAM 10036, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 24.4, current 34.8, max 36.3
Supply voltage: min 23.9, current 24.1, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-08-24 01:52:44
Cache data hit count 4294967295
Slowest loop: 5.15ms; fastest: 0.19ms
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 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, 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 1 is on, I-accum = 0.0
=== 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 sensor: ok
=== Network ===
Slowest loop: 15.78ms; 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 f4:cf:a2:71:b3:f7
  WiFi Vcc 3.32, reset reason Power up
  WiFi flash size 2097152, free heap 26616
  WiFi IP address 192.168.1.100
  WiFi signal strength -61dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

I have the following specs:

• Board: Duet 2 WiFi (2WiFi)
• Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
• Duet WiFi Server Version: 1.26

Going on day 4 with this... I know my wiring is correct, as I've checked it multiple times, then 3 times over. All solders points are good, crimps are good, verified everything with a multimeter, even personally pulled and checked every jst crimp, re-crimping new connectors on any questionable ones. I'm using a 1.5 meter USB 3 cable. I have the wires soldered directly into the LIS3DH (ADA2809) board, cable sheathing soldered to GND. At the Duet side, I have the wires terminating into short, 200mm jst cables that plug into the Duet Temp Daughterboard pins (even tried wrapping them in alum foil). I have every wire color coded from end-to-end to make certain no mistakes were made. ("Error: M955: Accelerometer not found on specified port"). After being certain of the wiring, on day 2, I thought perhaps I have a bad accelerometer so I ordered a 2nd. Got it, wired it one up, and ("Error: M955: Accelerometer not found on specified port"). The light does come on on the LIS3DH (I have pin 8 on the Duet going into VIN on the LIS3DH, and I have verified my Duet is putting out 3v on this pin).

Then I found the post about the resistor, so I soldered a 330 Ohm resister in series with the SDO at the LIS3DH side. ("Error: M955: Accelerometer not found on specified port"). Then I found the post about perhaps a small capacitor may help wired between GND and SCL, so I tried that. ("Error: M955: Accelerometer not found on specified port").

Thought perhaps my short jst runs were the issue, so I ordered and made new connectors directly on the USB3 wires and now the Duet side of the USB3 cable terminates directly into the Temp Daughterboard.

Short of suspecting something is wrong with the Temp Daughterboard, I'm not sure what else to do. I've been at this for 4 days: taking breaks, coming back, reading more posts, verifying wiring again. Also attempted to swap CS and INT from spi_cs4 and spi_cs3 then changed my M955 command, no avail. Even tried wiring up CS to cs5 on the expansion board. Nope. (yes, changed M955 in config)

If anyone has any suggestions outside of the posts already in this forum, I would so appreciate the help. Thank you in advance.