+ Post New Thread
Results 1 to 3 of 3
  1. #1
    Newbie level 6
    Points: 2,271, Level: 11

    Join Date
    Apr 2003
    Posts
    13
    Helped
    0 / 0
    Points
    2,271
    Level
    11

    HELP - "name too long" errors in Cadence Export Ph

    I'm using PSD 15.0 on an Concept/Allegro "Reference Design" ,which
    obviously SHOULD work but doesn't ...

    When I try to Export Physical to Allegro, Netrev gives me the following error (many times) ...

    It looks as if my configuration is constrained to a Part Name of 31 characters ? I have set Part Type Length to 50 in Setup.

    Anybody got any ideas ?

    RJR.



    ------ Oversights/Warnings/Errors ------


    #1 ERROR(302) Device library error detected.

    Problems with the name of device 'TE
    ST_POINT_THRU_HOLE-51-0184-001': 'name too long'.

    Device 'TEST_POINT_THRU_HOLE-51-0184-00' has library errors. Unable to transfer to
    Allegro.

    ....... etc.

    •   Alt30th June 2005, 05:24

      advertising

        
       

  2. #2
    Full Member level 5
    Points: 3,795, Level: 14

    Join Date
    Dec 2002
    Posts
    288
    Helped
    34 / 34
    Points
    3,795
    Level
    14

    Re: HELP - "name too long" errors in Cadence Expor

    This is normal with Allegro. Even when you use Orcad capture with Allegro if
    you have long names it creats problems. Obviously you should rename your device.
    This is way too long for a name!

    Regards,

    Majnoon



    •   Alt30th June 2005, 18:07

      advertising

        
       

  3. #3
    Member level 2
    Points: 1,535, Level: 8

    Join Date
    Jun 2005
    Posts
    44
    Helped
    8 / 8
    Points
    1,535
    Level
    8

    Re: HELP - "name too long" errors in Cadence Expor

    Friend, all the I can infer from the error message is that, the library part has not been created correctly. Check this from the part developer. This error should have been detected while packaging the library part itself, during the part creation stage. Open the part using the part developer and try saving it or Run a DRC check on the package or library part which you have created. One more guess is that the part table file would would not correct also...please check.



+ Post New Thread
Please login