EVOLVE Electrical 10.2.1

Updated 2 days ago by Jason Earl

Resources

• Downloads
• Feedback and Ideas
• Support
• Licensing
• Known Limitations/Bugs

Compatibility

• Autodesk® Revit® 2024.3.6
• Autodesk® Revit® 2025.4.6
• Autodesk® Revit® 2026.5
• Autodesk® Revit® 2027.2

Summary

EVOLVE Electrical 10.2 improves detailing workflows with automatic tag arrangement for quick and easy tag arrangement.

Update Training Course

To learn all about the new update complete the training course below on EVOLVE University:

🎉New

• Auto Tag Arrangement
  • Used to quickly arrange tags to avoid overlapping other tags or elements
• Create Spool API methods

👍Improvements

• Allow disabling Spool and Package visual cues
• Disable bend updaters during worksharing sync
  • This change resolves conduit/elbow disconnections and deletions during sync. If all users are not using EVOLVE then an EVOLVE user must update bends manually via Smart Bend Settings to trigger the bend updaters to ensure geometry of smart bends and factory elbows is accurate.

💪Fixes

• Fix Conduit Run Schedule columns being duplicated in exported files
• Fix users being incorrectly put into offline mode when logging into the product
• Prevent reporting of erroneous stats from external plugins
• Fix Error Check not reporting issues that exist
• Fix package related error when opening Sheet Manager
• Fix view position resetting after Spool and Package operations
• Fix Auto Place Sleeves placing incorrectly for small elements
• Fix invalid Content Browser configuration crashing Revit
• Fix Convert to Box Out failing silently in certain scenarios
• Fix blank PreFab Manager listing when insulation packaged
• Fix merged packages receiving invalid name and breaking PreFab Manager

📂Content Updates

🔦 Highlights

• Refactored the Junction Box Assembly family with expanded rod support, mounting attachment controls, hardware customization, and improved parameter organization.
• Various bug fixes

⤴️ Family Version Changes

• eV_ASM_HS_Trapeze_1_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_1_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_2_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_2_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_3_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_3_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_4_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_4_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_1_Tier_v9.rfa → eV_ASM_HS_Trapeze_1_Tier_v10.rfa
• eV_ASM_HS_Trapeze_2_Tier_v9.rfa → eV_ASM_HS_Trapeze_2_Tier_v10.rfa
• eV_ASM_HS_Trapeze_3_Tier_v9.rfa → eV_ASM_HS_Trapeze_3_Tier_v10.rfa
• eV_ASM_HS_Trapeze_4_Tier_v9.rfa → eV_ASM_HS_Trapeze_4_Tier_v10.rfa
• eV_ASM_HW_Threaded_Rod.rfa → eV_ASM_HW_Threaded_Rod_v2.rfa
• eV_HW_4_Hole_Steel_Plate.rfa → eV_HW_4_Hole_Steel_Plate_v2.rfa
• eE_ASM_HS_Conduit_Hanger_v3.rfa → eE_ASM_HS_Conduit_Hanger_v4.rfa
• eE_ASM_Junction_Box_v3.rfa → eE_ASM_Junction_Box_v4.rfa
• eE_ASM_Panelboard_Wireway_EMT_v3.rfa → eE_ASM_Panelboard_Wireway_EMT_v4.rfa
• eE_CF_Plastic_Push_On_Bushing.rfa → eE_CF_Plastic_Push_On_Bushing_v2.rfa
• eE_CF_Plastic_Screw_On_Bushing.rfa → eE_CF_Plastic_Screw_On_Bushing_v2.rfa
• eE_CF_PVC_Bell_End.rfa → eE_CF_PVC_Bell_End_v2.rfa
• eE_LT_Exit_Wall_Mounted.rfa → eE_LT_Exit_Wall_Mounted_v2.rfa
• eE_LT_Recessed_Can_v2.rfa → eE_LT_Recessed_Can_v3.rfa

🎉New

• Added the parameter eVolve_Version_Number to the SharedParameterDefinitions.txt file. This parameter will replace eVolve_Version in all families in a future release.

👍Improvements

• Refactored the junction box assembly family:
  • Removed the nested family Nested_ASM_HW_Threaded_Rod.
  • Removed the parameters associated with the legacy mounting attachments nested withing the threaded rod assembly.
  • Added the latest nested rod and nested hardware families, configured to match the previously used nested rod assembly.
  • Added 5/8" rod and hardware support.
  • Improved parameter organization.
  • Added a generic mounting attachment to each rod.
  • Added generic mounting attachment related parameters.
  • Added the ability to have the center rod and corner rods enabled simultaneously.
  • Added end of rod zones of influence and associated parameters.
  • Added hardware part description customization parameters.
  • Added the ability to disable hardware.
  • Added a parameter to adjust the bottom offset of the support rods.
  • Added additional EVOLVE Tools parameters.
  • Removed eVolve_Version.
  • Added eVolve_Version_Number with a formula value of 10.2.

💪Stability

• Removed redundant, old versions of the legacy strut hanger families from the hanger.
• Fixed an issue where R_Length_Minimum calculations in the threaded rod assembly, conduit hanger assembly, and junction box assembly families did not correctly account for family geometry variations.
• Fixed default values in the 4-tier basic strut trapeze family.
• Fixed an issue with the 4-hole steel plate family that resulted in hole diameter referencing radius instead of diameter.
• Fixed an issue with the duct bank template part description parameter sync rule not rounding properly.
• Fixed the eVolve_SubCategoryId value in various connector families.
• Fixed a visibility issue with the wall mounted exit sign family not displaying properly in plan view and fine detail.
• Fixed an issue with the recessed can lighting fixture family's lighting aperture not maintaining center or offsetting properly when adjusted by the user.
• Fixed an issue with the element filter for the parameter sync rule "eE_Junction Box Description (Deprecated)".
• Fixed an issue with the eE_ASM_Panelboard_Wireway_EMT family where wireway length and offset parameters were not working as expected.
• Added missing support for the Trapeze Tier Offsets tag to the legacy strut trapeze hanger families.

🧠Technical Notes

Upgrade Notices

Configuration setting incompatibilities

Some feature's project configurations may not be compatible with previous versions. To prevent compatibility issues, all project members should be on the same version.

Known Technical Issues

Compatibility issue with other addins

Our product uses DevExpress 25.2.5 for it's UI components. Any other Revit addin (regardless of vendor) installed on the client also using DevExpress but on a different version may cause crashes and/or unpredictable behavior with our product and/or the other addin. When this is the case, the user must either uninstall the other addin or contact the vendor to issue a new release with updated DevExpress references.

API Notices

• New API methods
  • eVolve.Core.Revit.Spooling.API.CreateSpool
  • eVolve.Core.Revit.Spooling.API.SpoolNameExists

External communication

Access to the following must be allowed and unfiltered on all client machines:

• api.evolvemep.com

Revit Project Units

Unit precision

Content and/or default configurations shipped with the product use measurements of a set precision level. Revit projects must use (at a minimum) this precision level otherwise content and/or configurations may produce errors, incorrect results, or behave unpredictably.

Length units must be set to a precision of at least:

• 1/16" in imperial
• 0.001 m in metric

Conduit Size units must be set to a precision of at least:

• 1/8" in imperial
• 0.001 m in metric

Cable Tray Size cannot use imperial notation. Fractional values should be used when imperial measurements are used.

Rounding

Configuration data will be saved against the precision level at the time of save, regardless of the precision level of the previous value.

For example, assume a configuration value is currently set to 2 1/32" and the current precision level is 1/16". When the user opens the configuration form, the value will show as 2 1/16". Upon the user clicking OK or Apply, the value will be saved as 2 1/16" even if the user did not explicitly update this particular value. The value will remain 2 1/16" even after the precision level is changed to 1/32", however at this point the user can update and save the configuration value as 2 1/32".

Licensing

When a license is disabled, the following automatic processes will not run which can cause the elements they update to become "stale" and/or lead to data issues:

• Data protection prompts on elements with a Pre-Fab Package (eV_PackageId) assigned
• Conduit Schedule (Parameter Push) run assignment and updates on modifications during modeling
• System Families/Content
  • Update of eVolve_Description on modeled content
  • Working with Bends, Offsets, and Kicks may fail or produce incorrect results
  • Working with Family Hangers may fail or produce incorrect results
• Clearance change monitoring
• Spool Modeling
  • Deletion: disassociates parts, deletes generated spool sheets
  • Change monitoring: assists in monitoring spools on the document
    • If this is re-enabled in a session where spools have been modified then this must be rebuilt by either closing/reopening the model or by opening Prefab Manager.
      Failure to do so can cause incorrect behavior with the execution and/or detection of spooling events.
  • Assignment to Locations based on part assignments
• Automatic control of product specific View Template parameters
• Parameter Sync
• Workset Manager
• Macro Automation
• Colorizer
• Part Encoder
• Automatic Point Status updating
• Automatic Renumber

Default Configurations

Default feature configurations (what is applied when a feature is first used within a model) is applied in the following order (first match wins):

1. Configuration exists within the model (i.e. the project template the model was created with contains configuration information)
2. Default configuration is defined within Network Default Configuration of Workstation Settings
3. Default configuration exists in the local machine's user profile folder for the product the feature was opened under
4. Factory defaults are used

Misc

• Some features which utilize background processes and data caches may not work correctly until a project is saved with a unique RVT file name.
• A licensed version of Microsoft Excel must be installed on the local machine for some import/export functionality to work.
• Background processes required for successful operation of the product are flagged as optional within Revit. If Revit fails to load them for any reason, the user will not be notified.
• The PowerShell version used for the execution of scripts depends upon the host Revit version:
  • Revit 2025+ uses 7.4.2
  • Prior versions use 5.1
• Some file operations may not work as expected when using either a network path, mapped folder location, or a directory which utilizes Windows symbolic or junction links. When this is encountered, it is recommended to use a local user path (such as the user's desktop) to perform the operation.
• Due to Revit's internal workings, Revit should be set to open on your primary monitor. When Revit is initially opened on a monitor other than the system's primary, unexpected/unpredictable behavior can occur with the initialization methods.

How did we do?