Stats

  • Locked Locked
  • Replies 2
  • Subscribers 164
  • Views 12716
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

some questions about Allegro 15.7!!!

archive

what is the function of these layers:
(1)"package keepin"  "route keepin" , how about the difference about them?
(2)assembly_top;
(3)board geometry;
(4)cut_masks

another question is the word of "slot", what is the meaning of "slot"?

thanks!


Originally posted in cdnusers.org by watchdog1976

  • Hello,

    (1) Package Keepin:Package keepin subclass can be used to define a constraint area within which the components are to be placed ( generally this command is used with autoplace command ) If the components are placed manually outside the keepin area , design rule check report generated shows the DRC error for voilation of constraint.

    (2) Route Keepin:Route keepin subclass can be used to define a constraint area within which the tracks are to be routed ( generally this command is used with autoroute command ) If the tracks are routed manually outside the keepin area , design rule check report generated shows the DRC error for voilation of constraint.

    (3) Assembly Top: This subclass is used to define component details for assembly , assembly instructions ( that are useful at the the time of board assembly ) etc...

    (4) Board Geometry:Generally used to define outline for board ( that defines actual size of the board ).

    (5) Cutmarks: can be used instead of bord outline ( for manufacturing convinience ).

    Regards,
    Prajakta
    Solar Biotronic Laboratories Pvt.Ltd.
    www.sblindia.com.


    Originally posted in cdnusers.org by psj

  • Assembly-top (bottom): also used by tesprep process to know where component's body is located

    Should be as close as possible from reality for this reason (external dimensions)

    Hope this help,

    jean-charles


    Originally posted in cdnusers.org by jch teyssier
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.