Stats

  • Replies 6
  • Subscribers 158
  • Views 14519
  • Members are here 0
More Content

axlDBCreateVia

archive

Hello all.

I have a lot of unconnected vias. they have no connect line, they are only vias to interconnect negatives shapes together through the cross section.
I want them to be connected to a net. By hand, I have to connect from something (a shape for example) and then put the connection to the via.

I wrote a little routine to this.
I cannot use the axlChangeNet (not allowed for vias).
So i use a workaround:
I extract via xy and name and then use axlDBCreateVia to create a new one at the same point, with the same name but another net.
It works perfectly. all my vias are finally connected. I save the BRD file, reopen it. They are still connected to what I wanted..
But, after some commands in Allegro, they came back to unconnected vias!
I tried to add a axlDBRefreshId on new vias (not really necessary, they are new ;-), run a dbdoctor on the BRD, not better!

Whatever I did, they finish to be unconnected.

Any ideas to fix it?

Thanks in advance.


Originally posted in cdnusers.org by willbi
Parents

  • The problem you had makes sense:

    1. When creating a new via at the same xy, the existing (floating) via connects to your new via.
    2. Next, when you delete the original via, any connected objects need to be updated. (your new via)
    3. Since there is no other connected object to keep the new via on the desired net, the new via becomes floating when the update occurs.

    Here is a speed tip when re-creating objects:
       Save the data for the new objects in a single variable.
       Delete the original objects if needed.
       Create a single procedure to create objects; pass in all the data using the one variable
       Use axlDBCloak on the call to create the objects
       (only add the axlDBCloak when you know the code works, it has error catching and will not show any errors if they occur which will make it difficult to debug)


    Originally posted in cdnusers.org by natebizu
Reply

  • The problem you had makes sense:

    1. When creating a new via at the same xy, the existing (floating) via connects to your new via.
    2. Next, when you delete the original via, any connected objects need to be updated. (your new via)
    3. Since there is no other connected object to keep the new via on the desired net, the new via becomes floating when the update occurs.

    Here is a speed tip when re-creating objects:
       Save the data for the new objects in a single variable.
       Delete the original objects if needed.
       Create a single procedure to create objects; pass in all the data using the one variable
       Use axlDBCloak on the call to create the objects
       (only add the axlDBCloak when you know the code works, it has error catching and will not show any errors if they occur which will make it difficult to debug)


    Originally posted in cdnusers.org by natebizu
Children
No Data
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.