EEVblog Electronics Community Forum
General => General Technical Chat => Topic started by: BravoV on February 26, 2018, 08:45:42 am
-
Ok, maybe for complex chip like microprocessor or similar is understandable.
But for simple common component types, like for op-amp, power management etc, or even more simpler discrete ones like diode, transistor and etc, there are manufacturers just love to use their own proprietary filename that don't have a relation at all to the chip's name, not even a slightest hint.
An example from ST, a simple well known TL431 IC is named "en.CD00000986.pdf". :(
Understand they need to put some formatting fields for quick hint, say its in English, its not hard to use something like .. "EN.TL431_XXXXXXX.PDF" where the XXXXXX is the additional field for their other internal proprietary numbers needed for book keeping, tractability and etc.
Who do you think are the worst ones ? And also manufacturers that at least made an effort to ease their customer in this matter ?
-
Ok, maybe for complex chip like microprocessor or similar is understandable.
But for simple common component types, like for op-amp, power management etc, or even more simpler discrete ones like diode, transistor and etc, there are manufacturers just love to use their own proprietary filename that don't have a relation at all to the chip's name, not even a slightest hint.
An example from ST, a simple well known TL431 IC is named "en.CD00000986.pdf". :(
Understand they need to put some formatting fields for quick hint, say its in English, its not hard to use something like .. "EN.TL431_XXXXXXX.PDF" where the XXXXXX is the additional field for their other internal proprietary numbers needed for book keeping, tractability and etc.
Who do you think are the worst ones ? And also manufacturers that at least made an effort to ease their customer in this matter ?
I don't have a problem. I can find most data sheets, using a search engine and for the ones which aren't as easy to find, I save them to my hard drive. Before I had reliable, fast, Internet access, I used save all the data sheets to my hard drive, but now I don't bother, as can ensure I always get the latest version.
-
Just "buy" the book then you'd have no problems. :popcorn:
-
Just "buy" the book then you'd have no problems. :popcorn:
Your quotation marks have been noted. We will be with you shortly.
-
I'm tired of this too, most of the time I have to rename the PDF as its either:
a) For multiple ICs so has xx in the filename, or contains the numbers of all parts.
b) It's a database number which is totally meaningless
c) File name starts with company name.
For something I'm reverse engineering at the moment, the filename exactly matching the part makes it far easier to look up any pinout etc.
Only source of annoyance at the moment is when current datasheets don't contain any mention of the suffix/package code, eg TL082ACN, just what does ACN mean ? All I found is A is revision A, N is DIP, no idea what C is.
-
Only source of annoyance at the moment is when current datasheets don't contain any mention of the suffix/package code, eg TL082ACN, just what does ACN mean ? All I found is A is revision A, N is DIP, no idea what C is.
Commercial temperature range.
Data sheets have a section usually titled "ordering information," which lists all of the possible orderable part numbers with suffixes. ST here (see section 9) (http://www.st.com/content/ccc/resource/technical/document/datasheet/a1/13/87/67/ab/ad/4c/f9/CD00000492.pdf/files/CD00000492.pdf/jcr:content/translations/en.CD00000492.pdf). TI here (see Packaging at the end) (http://www.ti.com/lit/ds/symlink/tl082.pdf).
-
be careful what you wish for.
http://ww1.microchip.com/downloads/en/DeviceDoc/Microchip%208bit%20mcu%20%20PIC18%20L_F26_27_45_46_47_55_56_57K42%20low-power%20high-performance%20mcu%20with%20xlp%20tech%2040001919B.pdf (http://ww1.microchip.com/downloads/en/DeviceDoc/Microchip%208bit%20mcu%20%20PIC18%20L_F26_27_45_46_47_55_56_57K42%20low-power%20high-performance%20mcu%20with%20xlp%20tech%2040001919B.pdf)
-
They can put whatever they want on the end, but I wish they'd at least start with the chip number/designator. I have to rename almost every one I download if I expect to find it again quickly.
-
I usually rename the datasheet but leave the original name between parenthesis - some manufacturers actually append revision letters or numbers after the original literature number, which helps trying to match whatever I have offline with what is available online.
I tend to save as many datasheets as I can for the parts I use - after being burned a few times, I learned never to rely on a working Internet connection for my work.
-
For any component that I own I also keep a local copy of the data sheet. So I always name it to the part number. This serves two purposes for me, 1: I don't need to google it, or if my internet is down I still have it and 2: it serves as a rough inventory of parts I have. If I'm looking for a part I can just look at my datasheet folder.
I do eventually want to come up with a better system but it works for me for now. I don't really have that many components yet.
-
Save As...
Type part number
Press "Save"
It's not even a file name, it's a URL. It's probably tailored to locate the document in their database. That it ever resembles a file named for a given part, is coincidence at best. :-//
Tim
-
I just keep whatever file name they provide and add the chip name to the front. I can then find it easily and I still have the original filename, in case there is a superceded datasheet available - or ones for some other variant.
-
Renesas is pretty bad for a lot of chips/compiler docs. Not only random file name, but multiple random filenames for the same document, depending exactly what part of their website you download it from.
-
It's what happens when you let management tell you to use a "content management system" instead of just uploading the files with their original, sensical, names.
-
TI used to name their documents xxxxyyy[rev].pdf. I'm glad they now name the new one according to the part number, although it still retain the former numbering for internal reference. Slight inconvenience if older documents/pages still use the old name and now when you click/search the code it leads to nonexistent pages.
Still wondering what's the logic behind the old numbering. Some pattern I notice is that the first letter is always s; second and third letter is la/le/lu/lv/nv/vu for power management, lo/oa for audio, pr for processors, bo/lo for opamps; fourth letter is a for application report, u for user guide, s for datasheet, b for brochure, p/t for publications. Of course there's exceptions. I suspect (at least on some) the second letter is somewhat related to product line derived from companies they acquire.
-
One of my favorite datasheet naming scheme is from Linear Technology.
Consistent, plain simple & straight forward, and they even strip off alphabet character and use only digits as the chip's name, as this numbers matter cause customer will intuitively and naturally memorize the number's part.
I believe most people in this industry, when seeing the number 317 will easily associate it with LM317, or other popular ones like 2400 as for LTC2400 and etc. Also like older popular chips like 431 for example, as this is heavily are cross-referenced (cloned), so the digits part only just works especially for user/customer POV.
Someone in Linear Technology really thought of these and for sure its good for customer too, kudos. :-+
-
Renesas is pretty bad for a lot of chips/compiler docs. Not only random file name, but multiple random filenames for the same document, depending exactly what part of their website you download it from.
Silicon Labs never bothers to put version numbers on any of their software downloads. How do you know if there's a newer version? You don't. Their support department knows the users hate that but yet it has not made any dent in their thinking. (Also, their new web site sucks eggs.)
-
This is why I keep a local directory on a real physical hard drive on my actual PC with all datasheets, named and organized to my liking. Then I simply use file system links to the datasheets for each project. Keeps things small and there's one place to keep datasheets.
Yup, it's old school but I don't care. No cloud, no URLs, no nothing.
I'm such a lovable Luddite I even print datasheets!
-
I keep a local directory for a different but related purpose: these are the documents I used to direct my engineering decisions. If those decisions should be questioned in court (unlikely -- I hope -- but possible!), I can refer to precisely the version and copy of documents that I based those decisions on.
Fortunately, electrical engineering is less strict than, say, architectural engineering, where a PE might need not only a datasheet for, say, some structural material, but included with it, the assurance (and if not, the liability for the manufacturer to be included in a given action) that that information is accurate and representative of the material used.
Even for an EE, it's such a small cost, to simply download a datasheet, that it's well worth the time to do so!
Tim
-
I keep a local directory for a different but related purpose: these are the documents I used to direct my engineering decisions. If those decisions should be questioned in court (unlikely -- I hope -- but possible!), I can refer to precisely the version and copy of documents that I based those decisions on.
Thanks for the insight, never thought of that. :-+
-
I keep a local library of the datasheets I use. Sometimes, as is the case with complex components, I keep app notes, examples and reference designs under the same folder of the datasheet.
I also setup Altium to link to these datasheets.
A CMS would make my life easier, but I am too lazy to install one.
-
That and one websites that one clicks for an enlarged image and it's the same bloody size and in some cases smaller. Every single image on their site.
And people (usually numpty office administrators who think they run the place) who write long file names including dates like "Letter to blah 2nd March 1018" instead of in ISO 8601 format YYYY-MM-DD.
-
Apart from having also noticed the phenomenon, maybe we should have speaking filenames for datasheets, such as:
LM124_224_324_2904_turning_away_in_disgust.pdf
OPA2353_-_the_beast_that_will_not_hold_still
LT1498_1499_do_not_thank_me_-_just_as_ordered
...and so on?