Stats

  • Replies 4
  • Subscribers 160
  • Views 12998
  • Members are here 0
More Content

axlDBCreatePath

dgstan

Hi,

Maybe I'm mildly retarded, but I'm sure having problems grasping the functionality of axlDBCreatePath as far as how it treats the net names. Obviously, there are arguments to the function to assign the net name to the path definition, but it doesn't work. Then, I find in the documentation that unless the new path touches an existing net, the new cline with be added without a net.

From the documentation:

Notes:
axlDBCreatePath does not add a net name to an etch when the etch is not connected
to a pin, via, or shape.


If an etch is added, it is tied to the first net it touches, otherwise it remains “not on a net”.

----------------------

If this is the case, what is the point of the "t_netname" argument that you can pass to the function? Basically, I can pass it a net name, but unless the path is already attached to an existing net, it ignores it, and if it is attached to an existing net, it takes that net name and disregards the net you passed to the function.

Basically, I'm trying to add a cline at a specific location and assign it to a specific net. 

 

  • The t_netname in axlDBCreatePath is the name of the net you want to attach the path to. It's a 2-step process first add the net to the database using axlDBCreateNet, then add the path.

    axlDBCreateNet("cal") 

    path = axlPathStart( list(100:0 100:500)) 

    axlDBCreatePath(path "CONDUCTOR/TOP" "cal")

     

    -cal 

  • Craig,

    I'm sorry, but this does not work in Allegro 15.7. If the endpoints of the cline do not touch another net, the line is added as a dummy (not on a net). If the endpoints of the line do touch another net, is adopts that net, regardless of what you specify in your arguments to the function.

    Do you see it working properly in APD (I'm assuming APD since you call out "conductor" instead of "etch").

  •  The netname argument is to break a tie in case the cline touches two objects. Only shapes and pins can be assigned persistently to nets. A cline that doesn't connnect to anything will always be assigned to a dummy net.

  • Thanks fxfffxf. That makes sense. I'll add that vias can accept netname arguments when they are added in SKILL. I've got a little program that allows you to touch a via first and then a pin/shape/line and the via will take on the net of the other object. It's great when your vias get confused and change nets. I was hoping to do the same thing with clines.

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.