mixed library settings of DBUperUU for schematic and schematicSymbol

Hi ,

I have been trying a bit to fix a nasty situation:
one designer created schematics and symbols (lots of them) with these
DBUperUU settings
schematic:5 schematicSymbol:100 snapgrid:0.05
This gives problems to those want to use his schematics in a library
with default settings
schematic:160 schematicSymbol:160 snapgrid:0.0625

I tried a few obvious things like modifying/deleting the DBUPerUU
property, and unsing the dfII/bin/scale utility, but did not find a
satisfactory solution.
It seems to me the solution would require snapping the symbols to the
new grid, and doing the same to schematics. I wouldn t know how to do
that, but maybe some skill gurus around here a a bit of code that would
help.

Also, if you think there is a simpler solution than resnapping
everything, please tell !

 

The DFII "Scale" command (changes dbuperuu & magnification) is the correct
command to use to change the scaling.

Just remember, in DFII, the DBUPERUU property is stored in multiple places.
I think it can be in up to four different places (check the manual).

I don't remember exactly where I saw that, but I think it can be stored
in the techfile, the cellview, the cdsenv file, and one other place. Maybe
one of your DBUPERUU properties is winning out over the ones you are changing.

Again, check the manual for the four locations the DBUPERUU is stored.
Maybe someone who knows this better can post them for you.

 

Simon,

I tried dfII/bin/scale, but this is not enough to solve my problem.
From the situation with schematic:5 symbol:100 snapgrid:0.05 I need
- to set the symbol at the same dbuperuu as the schematic,
- to set both symbol and schematic at 160
- to set symbols and wires on 0.0625 grid (re-snap).

In my case, the only place where DBUPerUU is set is the library
properties, it has . I grokked the documentation on DBUPerUU, I found
the most interesting is the compatibility guide.

Do you know a way to snap symbols and schematics to a new grid ?

--

 

No, sorry. All I knew is that the DBUPERUU was stored in four places
in DFII on CDBA because it burned me in the past as I tried to figure
out why one cellview was different than the rest in a test library.

I've since received an email from an engineer at Cadence that on
OpenAccess, they've reduced the DBUPERUU ambiguity by storing
the DBUPERUU property ONLY in the techfile (for DFII on OpenAccess).

I've been amazed while testing DFII on OpenAccess that Cadence has
done a great job of making it almost totally transparent to me, the
user; yet, there are subtle improvements (like this one) in either
usability or efficiency (for example, the engineer noted a new XScale
command in OpenAccess which scales designs more intuitively by ONLY
scaling and not taking the DBUPERUU factor into account). Apparently
both Scale & XScale executables exist in the OpenAccess incarnation
of DFII (Scale, of course, having the same use model as before).

I ran a search on "snap to grid" for you on comp.cad.cadence & found
three pages of references, which I skimmed for content by the subject
lines but did not find any eurika's (but I didn't dive deeply either).

Maybe someone else better understands your problem.

I hope you get the answer you need,
Simon