Small accident where i fried diode D2

[temporal-distortion]

Unfortunately, while trying out a new SD-card (Samsung, to replace the SanDisk one that i later saw on the wiki-pages where not suited) i managed to touch the chassie of my se/30 and the BlueScsi V2 2023.10a, which resulted in some smoke coming out of the D2 diode (thats the only visual thing i can see. F3, D1 and C7 looks unharmed.

Excuse my ignorance, but what "type" of diode is used here really. Specific specifications? (i assume so)

[erichelgeson]

Oh no! Sorry to hear that - You can find the BOM (Bill of Materials) here with part numbers https://github.com/BlueSCSI/BlueSCSI-v2/blob/main/hardware/Desktop_50_Pin/ProductionFiles_JLCPCB/Desktop_50_Pin_TopConn_BOM.csv

HTH

[temporal-distortion]

No worries. It was my own fault :)

After scouring around Mouser, Rs-components, etc (lowest shipping starting at ~17usd irregardless if you want to buy 1-2 pieces (~0.2usd a piece), i finally went to Amazon and bought (pack of) 50 of them with a total price of ¨10usd incl. shipping. That should last me a lifetime imho :-D

I'm good now.

Thanks for the detailed information Eric. Much appreciated.

[temporal-distortion]

replaced the component and everything is working like a champ again :) Thank again Eric for the look-up.

Had to buy 50 of them in one go in order to save some cost of shipping (how crazy is that??) and so if anyone is located within the EU region and despise enterprise shipping/toll, do contact me. I have ~49 of these to go for postage/stamps only ;)

[temporal-distortion]

@erichelgeson one question if i may?

While the scsi portion of it works great once again, i do have some difficulties getting the (pico-w) wifi to work again (maybe i fried something else on the pico..? idk).

Is there some way at all to test the wifi-portion of the blue-scsi in some shape or form? Be it embedded or maybe even via windows (via PCI-scsi, etc).

When booting up the SE/30, i can see my wifi-name (as it is hardwired in the settings) but i now always get the "too many sockets" error even after reinstalling it all (System 7.5.3 and 7.5.5) even after multiple clean installs of opentransport 1.3 and 1.3.1. I guess it can't "find its ways" any longer.

Its no big disaster by any means as I just bought another one of these (and I can basically alway reuse this potentially non-wifi-capable blueScsi as an ordinary bluescsi), but i'm just curious.

[erichelgeson]

Haven;t really thought how to do that hmm. A debug log when networking is happening might be helpful. BlueSCSI behaves as a "layer 2" device meaning it doesn't know anything about sockets or the like, that's too high level. Try 7.1 with MacTCP 2.1 (7.1 can do almost everything 7.5 can anyways :)

If you can use the BlueSCSI Wi-Fi DA to scan, see, and connect to an AP, that's should be a pretty good indication the Wi-Fi is working, at least at the hardware level.