Knowledge Base > Announcements & Release Notes > EVOLVE Electrical 10.0.1

EVOLVE Electrical 10.0.1

Updated 10 hours ago by Jason Earl

Resources

Compatibility

Autodesk® Revit® 2024.3.4
Autodesk® Revit® 2025.4.5
Autodesk® Revit® 2026.4.1
Autodesk® Revit® 2027.0.2

Summary

EVOLVE Electrical 10.0 introduces a new Connector Placement tool for conduit, adds rolling offset support to Auto Route, and improves Smart Bends and cabling workflows. Spooling and packaging have been fully revamped, reporting is more flexible, and several conduit and bend accuracy fixes round out the release. This release also adds Revit 2027 support.

Update Training Course

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

INSERT TRAINING COURSE LINK HERE

Configuration setting incompatibilities

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

🎉New

Spooling & Packaging

Spooling and packaging have been redesigned for a clearer, more flexible workflow. New dedicated ribbon commands — Add To Spool, Remove From Spool, Merge Spools, Add To Package, Remove From Package, Merge Packages, and Delete Spool — replace the previous Modify commands. Visual cues highlight what's already spooled or packaged, and spools are never modified during worksharing sync that caused failed syncs in some scenarios.
The Single Numbering column in Renumber Configuration has been moved out of the Common Numbering / Identical Part Determination section to reduce confusion.

Conduit, Bending & Routing

New: Connector Placement tool. You can now quickly place conduit connectors on open ends of selected conduits and smart bends. The tool detects conduit standard, remembers your last connector choice per standard, and pushes run data to placed connectors — replacing tedious manual placement.
Auto Route now supports rolling offsets. Pathways can include rolling offsets and Auto Route will place the corresponding conduit automatically.
Smart Bends button renamed to "Smart Bend Settings" and the Minimum Leftover Length default is now 0", reducing unnecessary setup steps.
Align Run Intersection can now match the slope of the stationary run to the branch. A new settings dropdown lets you choose to always match, never match, or be prompted each time.
Insert Offset now provides clearer error messages when an offset is placed out of bounds.

Cabling

Cable length calculations now support padding. A new percentage-based padding field is applied to the total cable run length before makeup lengths and rounding, giving you more accurate cable pull estimates.

Hangers, Supports & Clearances

A new Minimum Trapeze Width setting is available in Hanger Placement. You can now define a floor for trapeze hanger width (default 1'-0").
The redundant "Create Unfiltered View" option has been removed from the Hanger Placement dialog. This setting remains in Hanger Placement Settings.
The Seismic Support Placement tool now uses the eVolve_Feature parameter for content identification, consistent with other placement tools. Existing content continues to work.
Place Clearance now works more reliably in edge-case scenarios.

Reports & Data

Reports now support a secondary filter on the primary profile, eliminating the need to duplicate profiles for different reports.
Reports no longer require a primary profile. This removes an unnecessary constraint and supports new data source workflows.
You can now select a specific sheet when using an Excel file as an External Data table source.
Data Profiles now support PowerShell post-processing. A script can modify, filter, reorder, or extend the resolved dataset before it's returned.

Performance & Stability

The option to disable background processes during worksharing sync now also applies to Reload Latest.
Revit 2027 is now supported. Revit 2023 is no longer supported.

💪Fixes

Fixed: Auto Route could fail with an error when specific conduit runs were selected.
Fixed: Kick 90 families were reporting incorrect Overall_Length and bend dimension values.
Fixed: Factory Elbow families had an incorrect formula for eVolve_Length calculation.
Fixed: Pathway Routing could crash when a conduit run had a size of zero.
Fixed: Clearance was not placing on cable tray.
Fixed: eVolve Description was not updating correctly — the parameter sync rule for part size and description now resolves on the first pass.
Fixed: Hanger Placement could place the wrong hanger in certain scenarios.
Fixed: Hardware Size was not populating for newly placed hangers.
Fixed: Define Spool could throw an unhandled error.
Fixed: Deleting a package could throw an unhandled exception.
Fixed: Point Manager could cause Revit to become unresponsive when renumbering points.
Fixed: Configuration Exchange did not retain order numbers when importing from within Parameter Sync.

📂Content Updates

Added new EMT connector and Myers hub families to replace the existing versions.
- The following families were removed:
  - eE_CF_EMT_Connector
  - eE_CF_Myers_Hub
- The following families were added:
  - eE_CF_EMT_SetScrew_Connector
  - eE_CF_EMT_Compression_Connector
  - eE_CF_Myers_Hub_Connector
- New connector families support the new Connector Placement feature.
- New connector families are properly parametric and thus much lighter than their previous iterations.
Added new Basic Strut Trapeze with Rod hanger families. Each tier configuration is provided as a dedicated family:
- With hardware: 1–4 tier (one family per tier count)
- Without hardware: 1–10 tier (one family per tier count)
- Refer to this Help Page page for detailed information about these families.
Added a new tag for trapeze tier offsets.
- This tag references a new multi-text parameter, Trapeze_Tier_Offsets, and dynamically reports a list of the Elevation from Level values for each tier in a trapeze family. The value for the parameter is generated through a new Parameter Sync rule.
Reports Updates:
- Added the existing EVOLVE reports to the installer (previously available for download and configuration on Foresite).
  - Added Report Global Configuration files.
    - eV_ReportConfigurations.eVGlobal
    - eV_ReportConfigurations.eVGlobal.signature
    - eE_ReportConfigurations.eVGlobal
    - eE_ReportConfigurations.eVGlobal.signature
    - Report configuration files include Report Manager configurations for each Report as well as supporting Data Profiles for each Report.
  - Reports now appear automatically in Report Manager.
  - While customization is supported, Reports included in the installer are configured to work out of the box with no additional setup required by the end user.
- The following existing Reports are included:
  - Equipment BOM: Reports a list of equipment with their family names, type names and quantities.
  - Equipment Schedule: Reports a list of equipment with approval status, description, size and comments.
  - Sample Report: Reports a list of families and types and their quantities.
  - Trapeze Report: Reports essential information for the fabrication of legacy strut trapeze hangers (i.e. Family Name begins with eV_ASM_HS_Trapeze).
  - BOM for Electrical: Reports a bill of materials for electrical elements.
  - Cable Tray Schedule: Reports a bill of materials for cable tray and cable tray fittings.
  - Conduit Bends Report: Reports essential information for the fabrication of conduit bends.
  - Conduit Run Schedule: Reports a list of conduit runs.
  - Wire Fill Report: Reports wire fill information for conduit.
  - Cut List Report: Reports a cut list for electrical elements.
  - In-Wall Report: Reports a bill of materials for in-wall elements.
  - Lighting Schedule: Reports a list of lighting fixtures with counts, approval status, and size.
  - Switchboard Schedule: Reports a list of switchboard equipment with approval status, section count and size.
- Added new Reports:
  - eV_Basic Strut Trapeze With Rod - Assemblies Report
  - eV_Basic Strut Trapeze With Rod - BOM Report
  - eV_Basic Strut Trapeze With Rod - Cut List Report
  - eV_Basic Strut Trapeze With Rod - Build Report
  - eV_Single Element Hangers - Assemblies Report
  - eV_Single Element Hangers - BOM Report
  - eV_Single Element Hangers - Cut List Report
  - eV_Single Element Hangers - Build Report
Added new schedules to the project template file and schedules file:
- eV_Basic Strut Trapeze with Rod - Assembly List
- eV_Basic Strut Trapeze with Rod - Bill of Materials
- eV_Basic Strut Trapeze with Rod - Cut List
- eV_Basic Strut Trapeze with Rod - Fabrication
- eV_Single Element Hangers - Assembly List
- eV_Single Element Hangers - Bill of Materials
- eV_Single Element Hangers - Cut List
- eV_Single Element Hangers - Fabrication
Added a new detail view to the project template file:
- Basic Strut Trapeze with Rod
Added new Parameter Sync rules:
- Conduit Connector Part Description
- Strut Part Description
- Trapeze Assembly Part Description
- Trapeze Tier Offsets
- Basic Strut Trapeze with Rod - Geometry
- Basic Strut Trapeze with Rod - Schedule Data
- Single Element Hanger Part Description
- Single Element Hanger - Schedule Data
Added new Part Encoder rules (and supporting Data Profiles):
- Basic Strut Trapeze with Rod - Part Encoder
- Channel Trapeze - Part Encoder
- Single Element Hanger - Part Encoder
Added new global functions:
- Get-R2SideOffsetCalc
- Get-StrutChannelTypeDepth

👍Improvements

Added Connector Placement feature support to the following families:
- eE_CF_Lock_Ring
- eE_CF_Bond_Bushing
- eE_CF_Garvin_EMT_Compression_Connector
- eE_CF_RMC_Connection
J-Hanger Updates:
- Added support for the Seismic Support feature
  - Note that selecting "Center of Rod" will only place a single seismic support.
  - As a workaround, users can select the "Edge of Strut" option in the tool to place (2) seismic supports.
- Added support for new single element hanger schedules.
- Added support for new part encoder and part description rules.
- Added support for mounting attachment vertical offsets and insert depths.
- Added support for single element hanger Reports.
- Updated default rod rounding values to 1/8".
- Removed previous part description customization parameters.
- Exposed eVolve_PartType to be used for part description customization.
Updates to Channel Trapeze Families:
- Added support for the Trapeze Assembly Part Description Parameter Sync rule.
- Added support for the Trapeze Tier Offsets Parameter Sync rule.
- Added support for the Channel Trapeze Part Encoder rule.
- Added support for Channel Trapeze Reports.

💪Stability

FIXES
- Renamed channel trapeze families to be in-line with other trapeze families.
- Separated the Angled Channel Trapeze family into (2) families (one for each tier).
- Updated the subcategory of channel trapeze families in the Content Browser to "Channel Trapeze".
- Updated the subcategory of legacy strut trapeze families (i.e. eV_ASM_HS_Trapeze_#_Tier) in the Content Browser to "Strut Trapeze (Legacy)".
- Fixed an issue with the eE_CF_Coupling family.
- Fixed an issue with the Equipment Id 3D model text in the eE_EQ_Disconnect family.
- Versioned kick 90 families to v14 to support Overall_Length and eE_ConduitBend_DimE corrections.
- Various schedule and view template fixes:
  - Set eVolve_Length to No calculation in eV_Cut List schedule.
  - Set eVolve_Length to No calculation in eE_Spool Cut List.
  - Set eVolve_Length to No calculation in eV_Dura-Block_Cut List.
  - Set eVolve_Length to No calculation in eE_Trapeze_Cut List.
  - Removed eVolve_CategoryId from sorting in eE_Spool BOM schedule.
  - Removed eVolve_CategoryId from sorting in eE_Spool BOM view template.
  - Set eVolve_Length to No calculation in eE_Spool Cut List view template.
DEPRECATIONS
- Deprecated the Parameter Sync rule "eE_Conduit Hanger Part Description".

🧠Technical Notes

API Notices

New API methods
- eVolve.Core.Revit.Framework.API.OpenPowerShellEditorDialog
- eVolve.Core.Revit.Framework.API.ExecutePowerShell
- eVolve.Core.Revit.Framework.API.GetPowerShellResultAsDictionary
- eVolve.Core.Revit.Framework.API.OpenPowerShellTesterUtility
- eVolve.Core.Revit.Framework.API.RegisterPowerShellTesterResultProcessor
- eVolve.Core.Revit.Framework.API.UnregisterPowerShellTesterResultProcessor
- eVolve.Core.Revit.ParameterSync.API.GetParameterSyncRuleNames
- eVolve.Core.Revit.ParameterSync.API.ProcessElement
- eVolve.Core.Revit.ParameterSync.API.CloseProcessingSession
- eVolve.Core.Revit.ParameterSync.API.OpenConfigurationDialog
API signature changes
Removed API methods

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.

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 and integrity enforcement 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.
- Reset on Copy: when a spool is created via a copy from existing, associations of the "source" spool (packages, status, etc.) are removed from the new spool
- 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):

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

Localization

On startup, our product will set the Revit process' localization/culture according to the language settings configured. If the auto detect setting (which is the default) is used the culture will be set to the language which Revit was launched in.

Examples:

Auto detect is set and Revit is launched in English. The culture will be set to "en-US".
Auto detect is set and Revit is launched in French. The culture will be set to "fr-FR".
French is set as the language and Revit is launched in English. The culture will be set "en-US".

When the environment is in a hybrid setup where all of the following localizations are not consistent: Windows, Revit, and eVolve - the following inconsistencies can occur:

Some dialog messages may display in a different language
Numeric formatting may be inconsistent
- For example, if Revit Project Units define numbers using the #,###.## format and the culture is set to use French, some numeric values may appear as # ###,##
- Certain input fields may require for data to be entered in the format of either the Project Units or the culture

Number Formatting

The following are supported number formats for decimal values. If the settings below are not used, some features may not work as expected.

123,456,789.00 when running in the English language
123.456.789,00 when running in the French language

Revit Limitations

In Revit versions prior to 2023, eVolve Properties and Compare Data may not update when selecting similar elements. To refresh the data displayed in this situation, click on a empty space within the view to clear the grid and then select the target element.

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.
If a Revit Workset referenced in a Workset Manager rule is deleted then Workset Manager configuration must be addressed immediately, otherwise elements may continue to be assigned to the deleted Workset.
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?

(opens in a new tab)