Datasheet archive collection

[MODULARFREAK]

https://experimentalistsanonymous.com/diy/index.php?dir=Datasheets

Thought id post this for yall, Hope these help some of you guys

[Dud]

This link has already been posted in this thread

Links to DIY builders

Just dumping my bookmarks, trying to avoid dups with the previous posts… DIY: http://phobos.000space.com/synthdiy/synthdiyframes.html http://stickneysynthyards.000space.com Commercial sites with schematics for (some of) their modules…

but not the direct link to the datasheets, which can be useful

[analogoutput]

For devices in production I find it best to go to the manufacturer’s website; for one thing, when there’s more than one manufacturer some have better datasheets than others (I generally prefer TI’s because they provide more information). For another, they’re the latest version.

For instance, here under “TL07” they have TI’s datasheet for TL07x… dating from 1996, 17 pages long. Under “TL074” is ST’s 2001 datasheet for the quad op amp only, 11 pages. At https://www.ti.com/lit/ds/symlink/tl071.pdf?ts=1656338971676 is the December 2021 revision of TI’s TL07x datasheet. 94 pages.

[TimMJN]

heh, funny. I just started my own archive of datasheets. I’ve begun including them in all my repos (e.g. Arduino-Euclidean-Rhythm-Generator/arduino_euclidean_rhythm_generator_datasheets at main · TimMJN/Arduino-Euclidean-Rhythm-Generator · GitHub), hope the habit will spread.

[Sonosus]

That, is an excellent idea. I wonder if I could write a script that pulls the datasheet link from the KiCad symbol and downloads all relevant data sheets into a folder.

[analogoutput]

Eh, I already have the most common datasheets in a folder on my computer and I know how to find others (like by looking in the KiCad symbol). I don’t really need to download and store more copies whenever I clone a repo. Maybe links to datasheets in the README would be better (though subject to link rot, but then again, the datasheets themselves will get out of date too).

[TimMJN]

@analogoutput

I already have the most common datasheets in a folder on my computer

So do I. But in all fairness, I didn’t add them with experienced builders and designers like yourself in mind

[analogoutput]

But I think you could serve them better, and the inexperienced builders just as well, with information on where to find the datasheets.

[Dave]

This ^^ 100%. Current datasheets should always come from the manufacturer of the part being used. These are updated when required and vary between component sources.

[TimMJN]

I think you’re both slightly missing the point here… I’m including the datasheets of the parts I used when designing the circuit. So I’m documenting my design choices. Whenever anyone wants to substitute a part, they can compare the datasheets. Yeah okay I could use links to the manufacturers websites instead, but I’m not gonna hunt around for dead links. Persistence is key. Also, ‘specs used at the time of design’ do not out date, even if a newer datasheet is available…

That all being said, I think I should add a note to the readme explaining all this.

[analogoutput]

But 94 pages of TL07x datasheet is both too much information and not enough information to document why you picked a TL07x. If you want to document your design choices, you need to say “I chose this part because of <these requirements> and <these specs which meet those requirements>.”

To choose a part, you need to read the datasheet. To understand why a part was chosen, you need to read the designer’s explanation. The datasheet won’t tell you that.

[TimMJN]

Fair point, but I think mine stands as well. I consider it quite useful to give some more specs than just a part number. And after, I’m not forcing anyone to look at them, so it won’t hurt, will it?

[analogoutput]

As I said, it’s downloading and storage I don’t need. So it hurts a little.

If someone wants to substitute a part, telling them “here’s the datasheet for what I used” isn’t very useful. If you specify a BC557 and I want to know if a 2N3904 will work, all the BC557 datasheet will tell me is how it differs from a 2N3904 — not which differences matter in your circuit. If you tell me “it needs to be an NPN transistor with such and such characteristics” then I don’t even need to look at the BC557 datasheet; I need to look at the 2N3904 datasheet and see if it meets the requirements you specified.

[feralbeagle]

Yes, this is how we keep track of our designs and the exact parts that went into them. Second sourcing is when you specify a primary part and then add more parts that will also work in the same location. Usually these are parts with the same specs from different manufacturers. Each source has the manufacturer’s datasheet file attached and not just a link. If the manufacturer decides to correct something in the datasheet, we can see what was changed. Manufacturer’s also merge and then the documentation gets wonky.