[PCB_FORUM] Re: How does Auto silkscreen Works
- From: "Mike Finczak" <mike@xxxxxxxxxxxxx>
- To: <icu-pcb-forum@xxxxxxxxxxxxx>
- Date: Fri, 18 Mar 2005 11:28:36 -0500
Prakash,
I'm not a Guru, just a packrat...
Attached is a old thread from the ICU forum that
should serve as an introduction to using AutoSilk.
Regards,
Mike Finczak
CopperCAD Design
www.CopperCAD.com
905-488-8958
START-------------------------------------------------------------------
------------------------------------------------------------------------
-
-----Original Message-----
From: darren_reader@xxxxxxxxx [ <mailto:darren_reader@xxxxxxxxx>
mailto:darren_reader@xxxxxxxxx]
Sent: October 22, 2002 8:34 AM
To: icu-pcb-forum@xxxxxxxxxx
Subject: Re: [PCB_FORUM] autosilk
Hi Mark,
I have had the same problems, and it seems you may be left with re-doing
your whole Autosilk. All I was trying to do was update a mechanical
symbol and Allegro was toasting ALL of the AutoSilk (even with it
disabled). REALLY Annoying, but anyway, here is what Cadence Support
told me:
"The first and foremost thing of importance is that user editing of
AUTOSILK layers is NOT(!) supported. Yes, Allegro does not prevent it
and users do do it, but if they do we can not provide any kind of
guarantee that their changes can be maintained. The SILKSCREEN layers
are provided for user-definition of silkscreen, and the AUTOSILK layers
are for the use of the automatic silkscreen generation and(!) updating
processes that derive their information from the user-defined
SILKSCREEN. If the user makes changes on AUTOSILK, they are short
circuiting the whole process. If the user wants their silkscreen changes
maintained, they should in fact make the appropriate editing changes on
the SILKSCREEN layers to match what they want on AUTOSILK, and then
re-generate the AUTOSILK layers. Then and only then can we begin to
approach any kind of guarantee that user changes can be maintained to
any extent. This is still subject to some override by the automatic
generation and updating processes if lines have to be broken over pin
and via pads, or text has to be moved to avoid pin and via pads, etc.
If a component is subsequently moved, a number of things have to happen
to make sure that AUTOSILK is up to date. The existing AUTOSILK for the
component has to be removed from the board and the component unplaced.
As that component
may(!) have caused AUTOSILK lines and text of other components in the
'vicinity' to have been broken and moved respectively, those components
have their AUTOSILK re-generated on the basis again of the user-defined
SILKSCREEN information. The same thing basically applies when the
component is moved to its new location. Other components in the near
'vicinity' have their AUTOSILK re-generated as lines may now need to be
broken and text moved because of the new component placement. In the new
location as well, the AUTOSILK for the component being moved must
finally be re-generated itself based on its new location, which may
require lines to be broken differently and text to be moved. All of this
is again based on the user-defined SILKSCREEN.
Updating of symbols basically falls under control of the same automatic
updating process. As the user-defined SILKSCREEN information for the
symbol may have changed, we have to automatically update AUTOSILK
information for symbols being updated.
In summary, if users do want to make silkscreen changes and have them
maintained to any reasonable extent, ***DO NOT*** edit AUTOSILK
information. Edit the user-defined SILKSCREEN information instead to
match what they want, and once all changes have been made, then
automatically re-generate everything.
Great explanation and I appreciate it, but I still don't see why symbols
not being checked off in the update symbols are being changed. I
understand what you are saying about the process and in most part agree
with the mind set there. But it should not have any bearing on it being
updated if the silkscreen has been manipulated correctly or not should
not. The check block implies that mechanical parts alone can be updated.
Also that within the Package Symbols individual symbols can be updated.
However this is not the case. Symbols not selected are being altered.
10-08-2002 13:52:19 (e):
Think of a symbol being updated the same as a symbol/component being
moved to a new location, as I had explained above. We (Allegro) don't
know what has been changed on the symbol. It could be pin locations, pin
pad stacks, SILKSCREEN information, etc. For the symbol being updated
the existing AUTOSILK is removed and automatically updated from the
current(!) SILKSCREEN. Because of other possible changes to pin
locations, pad stacks, etc., which could be affecting AUTOSILK of other
components/symbols in the near vicinity, they have their AUTOSILK
automatically updated as well, just as though the initial symbol being
updated was being moved to the location, as opposed to being updated in
place at the location.
So basically it comes down to editing is not supported and is the system
thinks something may have caused interferences it will default to the
default setup. The PCB has been statused to Backlog by R&D Engineering
and may be considered for future software releases."
Hope this helps!
Darren
Darren Reader
PCB Designer
Mitel Networks
(613)592-2122 ext.3802
Mark Grimes <mark.grimes@xxxxxxxxx> on 21-10-2002 04:02:16 PM
Please respond to icu-pcb-forum@xxxxxxxxxx
To: icu-pcb-forum@xxxxxxxxxx
cc:
Subject: [PCB_FORUM] autosilk
I'm having problems with autosilk when importing a new netlist. All of
my refdes autosilk text disappears. I found the below email on this
list, but the proposed fix does not work for me. Any other suggestions?
Thanks,
Mark
Michael Catrambone wrote:
>
>
> Select Manufacture > Silkscreen to open the Auto Silkscreen Form.
> Change the parameter under Classes/Subclasses section from "Silk" or
> "Any" to "None" then Close the form. This will disable the Auto Update
> feature of the Autosilk.
>
> In some designs having this feature enabled causes Allegro to crash
> during Netlist Import or when moving components after Autosilk has
> been run.
>
> Hope this helps,
> Michael Catrambone
> CommWorks Corporation
>
>
>
>
>
> dperry@xxxxxxxx on 01/03/2002 05:41:47 PM
>
> Please respond to icu-pcb-forum@xxxxxxxxxx
>
> Sent by: dperry@xxxxxxxx
>
>
> To: icu-pcb-forum@xxxxxxxxxx
> cc:
> Subject: [PCB_FORUM] silkscreen woes
>
>
> Happy New Year everyone.
>
> Autosilk is giving me pains! Too bad I made adjustments to it before
> the FAB was complete or the engineer had made his usual offering of
> changes. Seems changing the FAB ( or other things) causes the
> silkscreen to update, thereby negating any manual silkscreen changes.
>
> Is there a way to prevent the silkscreen from auto updates????
>
> Thanks
>
END---------------------------------------------------------------------
------------------------------------------------------------------------
------
-----Original Message-----
From: Prakash [mailto:s.prakash@xxxxxxxxxxxxx]
Sent: March 18, 2005 11:01 AM
To: icu-pcb-forum@xxxxxxxxxxxxx
Subject: [PCB_FORUM] Re: How does Auto silkscreen Works
Hey Design Gurus, am waiting to hear your comments
----- Original Message -----
From: Prakash <mailto:s.prakash@xxxxxxxxxxxxx>
To: icu-pcb-forum@xxxxxxxxxxxxx
Sent: Friday, March 18, 2005 3:29 PM
Subject: [PCB_FORUM] How does Auto silkscreen Works
Hi All
Auto Silkscreen Feature : After trying out numerous times am posting
this query to understand the logic in which Auto silkscreen utility
works. Please provide some light on this utility if some body has done
well on it
Thanks & Regards
Prakash S
Other related posts:
