Copper planes are solid copper blocks where airgaps for pads/ traces will not be created. Such copper areas are usually used for shielding and as Keep Off Zones. It is recommended not to use these copper areas for distributing power supply or ground since Pwr/ Gnd Planes mode is used for such purposes. In some cases, it may be necessary to relieve certain areas on the board from copper. This may be done by creating Copper pour areas in any shape. Atleast three vertexes must be defined. These introduced relieve copper on the processed layer.

Creation Of Copper Planes

All Edwin 16 bit databases and libraries should be converted to EDWinXP format using Conversion Manager (exactly as in EDWin 32).
A library element in EDWinXP format contains additional fields for storing cross-references and in case of parts even thermal parameters These cross-references are not needed for proper functioning of the system but are useful for searching and browsing. Since this information cannot be reconstructed automatically during conversion, a special program called Field Editor has been provided. Certain cross references required for proper functioning of Library Browser and Library Explorer will be updated automatically when library file is passed through Field Editor. For example: in Edwin 16 thermal parameters were kept in separate files (.DAT/.TAL). Now all this data is stored within the respective Parts. Field Editor also enables to add other necessary information (manufacturer name, type etc) in manual edit mode.
In EDWinXP, when you try to save old DEVICES or PARTS taken from old DATABASES, it is required that you have to save the corresponding symbols and packages used by the Parts into User Libraries (and of course subsequently included those files into the Search Sequence).

Using EDWin 32 Libraries and databases

All EDWin 32 libraries and databases are upward compatible and for usage with EDWinXP NEED NOT to be converted.
CAUTION:
Any attempt (even for browsing using Library Explorer or Browser) to access EDWin32 libraries from EDWinXP environment causes permanent change of format. EDWin 32 libraries and databases once used with EDWinXP cannot be used with EDWin32. PLEASE ALWAYS USE SEPARATE COPIES OF LIBRARY AND DATABASE FILES FOR EDWIN 32 AND EDWINXP.
THE PATHS FOR LIBRARY AND DATABASE FILES OF EDWIN 32 AND EDWINXP MUST NOT BE SAME.
A library element in EDWinXP format contains additional fields for storing cross-references and in case of parts even thermal parameters These cross-references are not needed for proper functioning of the system but are useful for searching and browsing. Since this information cannot be reconstructed automatically during conversion, a special program called Field Editor has been provided. Certain cross references required for proper functioning of Library Browser and Library Explorer will be updated automatically when library file is passed through Field Editor. For example: in Edwin 16 thermal parameters were kept in separate files (. DAT/.TAL). Now all this data is stored within the respective Parts. Field Editor also enables to add other necessary information (manufacturer name, type etc) in manual edit mode.
In EDWinXP, when you try to save old DEVICES or PARTS taken from old DATABASES, it is required that you have to save the corresponding symbols and packages used by the Parts into User Libraries (and of course subsequently included in the Search Sequence).