jlarkin@highlandsniptechnology.com wrote:> On Mon, 18 May 2020 19:35:41 -0700 (PDT), sroberts6328@gmail.com > wrote: > >> To make sales and marketing happy, by making them think they actually DO something. >> >> If you can't find the data, then THEY feel good when they tell you where to find it. I've seen this many times, HERE is a picture of our beautiful product. Call/Email to get data, we may call you some time next week. Forces customers to talk to marketing and sales so they can justify their existence. >> >> When you call them, if they answer their phone, they have a cryptic number on a spread sheet to give you. >> >> No, I'm not kidding... >> >> Steve >> > > It also annoys me when people send me a resume' with file name > resume.doc. > > >Then pass it on to (eh, what's up .DOC) Buggsie.
why do they do this?
Started by ●May 18, 2020
Reply by ●May 19, 20202020-05-19
Reply by ●May 19, 20202020-05-19
Michael Terrell <terrell.michael.a@gmail.com> wrote:> On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: >> ST makes a nice little LDO, super-low dropout with an aux Vbias >> supply. Saves me from rolling my own with an opamp and a mosfet. >> >> It's an ST1L08. >> >> So why is the data sheet file en.DM00123507.pdf ? > > > To track revisions.Not buying that as good reason to obfuscate document names. Part numbers for components are not random numbers only trackable with a database lookup. There's no reason document names have to be completely contextless to be "trackable". Let's see how a smart company that's been able to adapt over the years and still remain relevant does it. Texas Instruments has employees with IQs over 43 maintaining their website. I clicked around for a random part, the OPA1622 audio amp. The URL to the datasheet has a clear meaning, even if you don't click on it http://www.ti.com/document-viewer/OPA1622/datasheet If you want to save the PDF, you get this really cool file name by default opa1622.pdf wow, how did they do it? The first link even has a clear revision history list link in case you want to know what happened prior to November 2015. There appear to be a document control number at the top of the PDF too. So yeah, short story is ST is just stupid.
Reply by ●May 19, 20202020-05-19
On Mon, 18 May 2020 23:03:17 -0700, Robert Baer <robertbaer@localnet.com> wrote:>John Larkin wrote: >> >> ST makes a nice little LDO, super-low dropout with an aux Vbias >> supply. Saves me from rolling my own with an opamp and a mosfet. >> >> It's an ST1L08. >> >> So why is the data sheet file en.DM00123507.pdf ? >> > ST is not the only one with nutty data sheet names; they abound and >rebound thru one's skull with free abandon. > The clangs created are tuned for maximum confuddleifcation.That file naming method has always bothered me. It's not just ST of course. TI starts their app notes with something like slup1234.pdf When I save any of these documents, I always rename them to something meaningful to me, usually the part number first and a quick description....
Reply by ●May 19, 20202020-05-19
On Tuesday, May 19, 2020 at 2:46:25 AM UTC-4, Cydrome Leader wrote: wrote:> > > On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: > >> ST makes a nice little LDO, super-low dropout with an aux Vbias > >> supply. Saves me from rolling my own with an opamp and a mosfet. > >> > >> It's an ST1L08. > >> > >> So why is the data sheet file en.DM00123507.pdf ? > > > > > > To track revisions. > > Not buying that as good reason to obfuscate document names. Part numbers > for components are not random numbers only trackable with a database > lookup. There's no reason document names have to be completely contextless > to be "trackable". > > Let's see how a smart company that's been able to adapt over the years and > still remain relevant does it. > > Texas Instruments has employees with IQs over 43 maintaining their > website. I clicked around for a random part, the OPA1622 audio amp. > > The URL to the datasheet has a clear meaning, even if you don't click on > it > > http://www.ti.com/document-viewer/OPA1622/datasheet > > If you want to save the PDF, you get this really cool file name by default > > opa1622.pdf > > wow, how did they do it? > > The first link even has a clear revision history list link in case you > want to know what happened prior to November 2015. There appear to be a > document control number at the top of the PDF too. > > So yeah, short story is ST is just stupid.So, it's better to have all the datasheets by part number? Try keeping multiple versions from one vendor, plus second sources, all with the same file name. Some jellybean parts have dozens of versions of a datasheet. The head of Engineering at Microdyne was pushing for a new inventory system. His concept was that the part number for a 1K resistor would be 1002. He threw a real hissy fit when I pointed out that we stocked 14 different 1K resistors, and other components had a value of 1002. He wasn't there very long before they fired him. All of our documentation had form numbers, unrelated to the product model numbers. They were filed by model number, but under ISO9001 we had to have traceability for all revisions. One board had 14 versions, and 14 test procedures. Every one ended up with over 100 lines that had to be marked N/A. I wrote a new procedure to cover every version of the board. It had 14 datasheets, one per version with no extra lines, plus a spare to allow for you to add new versions. The first page clearly stated to only use the specified datasheet for the version being tested. It reduced both the test time, and the paperwork to be stored. There are reasons to use other than obvious file naming. I am currently going through thousands of PDF files for test equipment. I am adding the actual document numbers to the file names, not just 'HP3325' since the A and B versions are different, but the manuals were revised multiple times. I have 180 GB of files, over 32,000 of them to sort, rename and compare. Some are duplicates, some are incomplete but I save every Electronics manual I come across.
Reply by ●May 19, 20202020-05-19
On 5/19/2020 9:31 AM, jlarkin@highlandsniptechnology.com wrote:> On Mon, 18 May 2020 17:57:06 -0700 (PDT), > bloggs.fredbloggs.fred@gmail.com wrote: > >> On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: >>> ST makes a nice little LDO, super-low dropout with an aux Vbias >>> supply. Saves me from rolling my own with an opamp and a mosfet. >>> >>> It's an ST1L08. >>> >>> So why is the data sheet file en.DM00123507.pdf ? >> >> Who cares, it's a crappy regulator. And the lying bastards with their fake dropout specs while conveniently omitting the fact that Vbias must be greater than Vout + 1.5V. > > Lying? It's all over the data sheet. It's how they get the millivolts > of dropout. I do that when I make my own super-LDOs, power an opamp > from some higher voltage and over-drive an nfet follower down to > milliohms of Rds-on. > >> The GND current at no load of 35uA, sucks , as does that showy 80dB PSRR at 100 Hz. Battery operation usually doesn't care a whole lot about PSRR. And the thermal impedance specs are so bad, you just try getting 800mA out of it with any kind voltage headroom without using a liquid nitrogen drip. >> > > I'm dropping a switched 1.8 to 1.5. That's 0.3 volts. Times 800 mA > would be 0.24 watts dissipated. Actually, I don't need that much > current to run a couple DRAM chips. >Not directly comparable to the ST1L08 but the Holtek HT75xx-1 series is nice. Max Vin 30V, 100mA, 2.5uA ground current, 25mV drop-out. 16 different fixed output voltages from 2.1V to 12V with 3% tolerance. As usual with products originating in the East, the datasheet is rather sparse about details, but I've used them and they do what I want.> You sure are in a bad mood lately. >I've noticed that lately with some regulars here, including a few who normally exhibit decent manners.
Reply by ●May 19, 20202020-05-19
On 19/05/2020 02:51, Michael Terrell wrote:> On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: >> ST makes a nice little LDO, super-low dropout with an aux Vbias >> supply. Saves me from rolling my own with an opamp and a mosfet. >> >> It's an ST1L08. >> >> So why is the data sheet file en.DM00123507.pdf ? > > To track revisions.More likely because it was stuffed into a crude document management system and it is in English. Try it.DM00123507.pdf or es.* I confess I rename such things to the chipname. They are not the only vendor guilty of having datasheets filed with random numbers for their filename. It is a PITA since they could just as easily have used en.<partno>-01.pdf And give it a new part number if they overflow the revision level. -- Regards, Martin Brown
Reply by ●May 19, 20202020-05-19
On 5/19/2020 1:46 PM, Martin Brown wrote:> On 19/05/2020 02:51, Michael Terrell wrote: >> On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: >>> ST makes a nice little LDO, super-low dropout with an aux Vbias >>> supply. Saves me from rolling my own with an opamp and a mosfet. >>> >>> It's an ST1L08. >>> >>> So why is the data sheet file en.DM00123507.pdf ? >> >> To track revisions. > > More likely because it was stuffed into a crude document management > system and it is in English. Try it.DM00123507.pdf or es.* > I confess I rename such things to the chipname. > > They are not the only vendor guilty of having datasheets filed with > random numbers for their filename. > > It is a PITA since they could just as easily have used > en.<partno>-01.pdf > > And give it a new part number if they overflow the revision level. >Some 30 years ago, NatSemi sent me their linear data book along with a CD. I dumped the contents of the CD into my hard disk and am still using it. It has an html interface but the search function doesn't work and individual types can be found only via the product tree. I often want to copy out individual datasheets for quicker access but the file names are all generic. The only way to do it is to go through the product trees in my browser, select a type, click download and save the displayed page.
Reply by ●May 19, 20202020-05-19
On 5/19/2020 2:59 PM, Pimpom wrote:> On 5/19/2020 1:46 PM, Martin Brown wrote: >> On 19/05/2020 02:51, Michael Terrell wrote: >>> On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: >>>> ST makes a nice little LDO, super-low dropout with an aux Vbias >>>> supply. Saves me from rolling my own with an opamp and a mosfet. >>>> >>>> It's an ST1L08. >>>> >>>> So why is the data sheet file en.DM00123507.pdf ? >>> >>> To track revisions. >> >> More likely because it was stuffed into a crude document management >> system and it is in English. Try it.DM00123507.pdf or es.* >> I confess I rename such things to the chipname. >> >> They are not the only vendor guilty of having datasheets filed with >> random numbers for their filename. >> >> It is a PITA since they could just as easily have used >> en.<partno>-01.pdf >> >> And give it a new part number if they overflow the revision level. >> > > Some 30 years ago, NatSemi sent me their linear data book along > with a CD. I dumped the contents of the CD into my hard disk and > am still using it. It has an html interface but the search > function doesn't work and individual types can be found only via > the product tree. > > I often want to copy out individual datasheets for quicker access > but the file names are all generic. The only way to do it is to > go through the product trees in my browser, select a type, click > download and save the displayed page. >That should be '20 years', not 30.
Reply by ●May 19, 20202020-05-19
On 2020-05-19 04:16, Martin Brown wrote:> On 19/05/2020 02:51, Michael Terrell wrote: >> On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote: >>> ST makes a nice little LDO, super-low dropout with an aux Vbias >>> supply. Saves me from rolling my own with an opamp and a mosfet. >>> >>> It's an ST1L08. >>> >>> So why is the data sheet file en.DM00123507.pdf ? >> >> To track revisions. > > More likely because it was stuffed into a crude document management > system and it is in English. Try it.DM00123507.pdf or es.* > I confess I rename such things to the chipname. > > They are not the only vendor guilty of having datasheets filed with > random numbers for their filename. > > It is a PITA since they could just as easily have used > en.<partno>-01.pdf > > And give it a new part number if they overflow the revision level. >I normally rename them to things like OPA192_2192_4192_10MHzRRIO_CMOS_Trimmed_LowDriftBuckFifty.pdf Cheers Phil Hobbs -- Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics Briarcliff Manor NY 10510 http://electrooptical.net http://hobbs-eo.com
Reply by ●May 19, 20202020-05-19
On Monday, May 18, 2020 at 7:41:34 PM UTC-4, John Larkin wrote:> ST makes a nice little LDO, super-low dropout with an aux Vbias > supply. Saves me from rolling my own with an opamp and a mosfet. > > It's an ST1L08. > > So why is the data sheet file en.DM00123507.pdf ?I'll take a stab at answering this one.... A: Because they hired the same ISO 9001:2015 consultant that we did! :) Maybe that's a :( ? I'll let you know after the audit.
