torinwalker
Newbie level 6
alias symbol
Cadence has a logical "alias" symbol that permits one to use multiple names for the same physical net. There are numerous uses of this symbol in a design I am referencing, and I would like to retain the original schematic design.
For example, a particular pin that returns current from a sensing loop is called BOOST_SENSE_N, but happens to be connected to ground via one of these alias symbols. In @ltium however, the net name is overidden with 'GND', which makes it more difficult to track when laying out the PCB. Each one also generates a compiler warning. This means I must review all the warnings, not just new ones, each time I make an edit. It slows me down, and increases the possibility of errors.
The only way I know to overcome this is to use a jumper (a zero-ohm resistor). This unfortunately invokes a physical component in the PCB layout. For obvious reasons, I am looking for a logical, rather than physical solution. I have also considered a virtual library component (two pins end-to-end for example), but it still requires manual placement and routing. A logical solution is the only way.
Any ideas?
Torin...
Cadence has a logical "alias" symbol that permits one to use multiple names for the same physical net. There are numerous uses of this symbol in a design I am referencing, and I would like to retain the original schematic design.
For example, a particular pin that returns current from a sensing loop is called BOOST_SENSE_N, but happens to be connected to ground via one of these alias symbols. In @ltium however, the net name is overidden with 'GND', which makes it more difficult to track when laying out the PCB. Each one also generates a compiler warning. This means I must review all the warnings, not just new ones, each time I make an edit. It slows me down, and increases the possibility of errors.
The only way I know to overcome this is to use a jumper (a zero-ohm resistor). This unfortunately invokes a physical component in the PCB layout. For obvious reasons, I am looking for a logical, rather than physical solution. I have also considered a virtual library component (two pins end-to-end for example), but it still requires manual placement and routing. A logical solution is the only way.
Any ideas?
Torin...