- Reblog
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
- Privacy
In EPLAN 2021, EDZ ( EPLAN Data Archive Zipped ) files serve as the primary vessel for complex part data, containing everything from commercial specifications to 2D/3D macros and technical documentation. By consolidating this data into a single compressed file, EPLAN ensures that all necessary assets for a component are imported simultaneously, maintaining data integrity across your electrical designs. The Value of the EDZ Format Unlike standard XML imports that may only carry textual part data, an EDZ file is a complete package. It typically includes: Part Data : Commercial and technical properties like manufacturer names and technical ratings. Graphical Macros : Detailed schematic symbols and 3D layout data for Pro Panel applications. Documentation : PDF data sheets and image files that populate your project's documentation automatically. How to Import EDZ Files in EPLAN 2021 While newer versions (2022 and up) utilize the Ribbon interface, EPLAN 2021 and its P8 predecessors follow a structured management workflow: Open Parts Management : Navigate to Utilities > Parts > Management . Access the Import Tool : Click the [Extras] button at the bottom of the dialog and select Import . Select File Type : In the "Import records" dialog, set the "File type" dropdown to EPLAN Data Archive Zipped (*.edz) . Configure Import Settings : Select your source file. Choose an import mode, such as Update existing records and add new ones , to ensure you don't lose existing data while adding the new components. Finalize : Click OK . EPLAN will unpack the file and distribute the macros and images to their respective directories within your master data. Sourcing Reliable Data Most major automation manufacturers provide pre-configured EDZ files to streamline your engineering process: EPLAN Data Portal : The most integrated source, allowing you to download and import EDZ data directly into your parts management system. Manufacturer Websites : Leaders like Siemens , Phoenix Contact , and ABB offer specialized generators or libraries for their product lines. Common Troubleshooting Integrated Tooling : For versions 2.2 and later (including 2021), the EDZ import tool is built-in; you do not need a separate "EDZ Import Tool" plugin. Directory Management : Ensure your project settings point to the correct directories for macros and images, as the EDZ import will automatically place files in these default locations.
Review: EPLAN EDZ files (2021) Overview EPLAN EDZ (EPLAN Data Zip) is a compressed archive format used by EPLAN Electric P8 and other EPLAN products to exchange projects, parts data, macros, and configurations. In 2021, EDZ remained the primary container for sharing complete project packages between users, offices, and external partners. What EDZ contains
Project files (.elk, .elkx, .elc) and their folder structure Parts and device master data (parts catalogs, device variants) Macros and graphic symbols User and project-specific settings (page templates, title blocks, macros) Connection data, PLC data, and terminal diagrams (when exported) Optional export metadata (export log, version info)
Strengths (2021)
Complete package: Bundles everything needed to open/import a project on another EPLAN installation. Version-friendly: EDZ exports include EPLAN version metadata so import can warn about version mismatches. Transportable macros & user data: Eases re-use of company-specific symbols and part libraries. Compression: Reduces transfer size compared with raw folders; convenient for email or cloud transfer. Standardized exchange: Widely supported within EPLAN ecosystem and by many resellers/partners.
Weaknesses (2021)
Version compatibility issues: Projects exported from newer EPLAN versions can require conversion or cause loss when opened in older versions. Opaque structure for non-EPLAN tools: Although it's a ZIP technically, many internal files use proprietary formats (.elk/.elc), limiting interoperability. Large size for big projects: Compression helps but complex projects with many macros/3D data can still be very large. Dependency on local master data: If recipient lacks referenced master data or manufacturer libraries, imports can produce unresolved references requiring manual mapping. Limited incremental exchange: No built-in diff/merge for partial updates—typical workflow is full-export/import. eplan edz files 2021
Practical advice for 2021 workflows
Match EPLAN versions: Export with the lowest common EPLAN version if recipients use older software, or provide version notes. Include master data: When sharing, add relevant parts catalogs and device master data in the EDZ to avoid missing references. Use export options carefully: Choose to include/exclude user-specific templates or heavy 3D/MCAD attachments to reduce size. Validate after import: Import into a test workspace to check for unresolved symbols, missing parts, or warnings before production use. Document customizations: Supply a short readme listing custom macros, title blocks, or naming conventions included. Leverage VCS for libraries: Keep reusable parts and macros in a shared repository (outside EDZ) to avoid repeated large transfers.
Common import/export pitfalls and fixes
Missing device master data → include device catalogs in EDZ or provide separate library package. PLC/terminal mapping errors → export PLC/terminal mapping files and check device numbering. Broken hyperlinks to external attachments → use relative paths or embed attachments in EDZ. Loss of attributes or custom properties → ensure "export project data" options include attributes/properties.
Interoperability & automation
Hardcore Casual