Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 165 subscribers
  • Views 187 views
  • Users 0 members are here
Related

Eagle Library - Texas Instruments - TLV320AIC1110PBS

Former Member

How should I should report what I believe may be a library error?

Here is an extract from the Texas Datasheet for the TLV320AIC1110PBS and the schematic symbol in Eagle using the Texas Library shape.  This TI Library was recently downloaded from the Element14 website.  The library has name "Texas Instruments_By_element14_Batch_1".  Description is "Developed by element14 :
element14 CAD Library consolidation.ulp at 30/07/2012 17:45:58".

 

TI Data Sheet:                                                                                    Eagle – Element14 – TI library (note pins 5 / 6 / 7).

image                                       image

 

My PCB ended up as per the Eagle symbol, which is wrong.  I swapped the connections around for pins 5/6/7 with wire jumpers, to match the TI datasheet and then it worked.

 

How are the libraries maintained?  Is their a query reporting and change process?  Who maintains them?

Regards,

Ian

Parents
  • 0

    Hi,

    That's when I download a component library, I always check the library :

    The worse of course is a wrong pining (as you experienced), but there is also a lot of other risks :

    - wrong io pin direction (not the worse)

    - bad pitch on the pad (often this come from approximative inch/mm conversion),

    - bad dimensions,

    - thermal active on pad that are supposed to dissipate heat......

    - tPlace that overlap tStop mask

    - etc etc etc....

     

    Any way, I never get a library that I could used as it:

    - first because a always add some attributes (manufacturer, alternate references, etc...)

    - second I always change the text font/alignem/size (vector font for package etc....)

    - for device with no value, I change the ">VALUE" text, in order to display one of my personal attributes ( manufacturer reference).

    - A set an attribute 'STATUS' to all my component:

       * I set this attribute to 'downloaded', if this library as just been downloaded,

       * I set this attribute to 'datasheet', if I just create the component from datasheet,

       * I set this attribute to 'Checked', if I checked this component, from is datasheet (in the description, I also add the check date because. I never check a component the same day that the day I create it).

       * I set this attribute to 'OK', if this aboard with this component as been made , and there is no error.,   

     

    Then I never send a prototype board to the manufacturer if all components are not at least checked.

    Then I never send a definitive board to the manufacturer if all components are not at least OK.

     

    So it's my advice :

    - always check a component form a library from Eagle.

    - always double check if it's from a downloaded library,

    - if the library seem so be to crappy, create your own library.

Reply
  • 0

    Hi,

    That's when I download a component library, I always check the library :

    The worse of course is a wrong pining (as you experienced), but there is also a lot of other risks :

    - wrong io pin direction (not the worse)

    - bad pitch on the pad (often this come from approximative inch/mm conversion),

    - bad dimensions,

    - thermal active on pad that are supposed to dissipate heat......

    - tPlace that overlap tStop mask

    - etc etc etc....

     

    Any way, I never get a library that I could used as it:

    - first because a always add some attributes (manufacturer, alternate references, etc...)

    - second I always change the text font/alignem/size (vector font for package etc....)

    - for device with no value, I change the ">VALUE" text, in order to display one of my personal attributes ( manufacturer reference).

    - A set an attribute 'STATUS' to all my component:

       * I set this attribute to 'downloaded', if this library as just been downloaded,

       * I set this attribute to 'datasheet', if I just create the component from datasheet,

       * I set this attribute to 'Checked', if I checked this component, from is datasheet (in the description, I also add the check date because. I never check a component the same day that the day I create it).

       * I set this attribute to 'OK', if this aboard with this component as been made , and there is no error.,   

     

    Then I never send a prototype board to the manufacturer if all components are not at least checked.

    Then I never send a definitive board to the manufacturer if all components are not at least OK.

     

    So it's my advice :

    - always check a component form a library from Eagle.

    - always double check if it's from a downloaded library,

    - if the library seem so be to crappy, create your own library.

Children
No Data