A unified Autodesk Revit add-in for electrical and lighting automation, supporting Revit 2024, 2025, and 2026, built for electrical/lighting designers working on luxury architectural lighting projects. Sixteen commands plus a Settings dialog, shipped as a per-version TurboSuite.dll (.NET Framework 4.8 for Revit 2024, .NET 8.0-windows for Revit 2025, .NET 10.0-windows for Revit 2026), x64.
- Navigate to the TurboSuite network share folder
- Run
TurboSuiteInstaller.exe - Click Install — the installer detects which Revit versions (2024, 2025, 2026) are present and installs the matching channel for each, copying all required files to the correct locations and configuring auto-update
- Launch Revit 2024, 2025, or 2026 — the TurboSuite ribbon tab will appear automatically
Revit must be closed during installation.
TurboSuite checks for updates on each Revit launch by comparing version files against the network share. If a newer version is found:
- A notification dialog lets you accept or skip the update
- If accepted, the update is applied automatically after you close Revit
- Skipped updates will prompt again on next launch
If the network share is unreachable (offline, VPN disconnected), TurboSuite loads normally from local files.
Run TurboSuiteInstaller.exe again and click Uninstall to remove all TurboSuite files. Revit must be closed before uninstalling.
The "TurboSuite" ribbon tab has four panels:
| Button | Description |
|---|---|
| Settings | Configure general options stored in ExtensibleStorage |
| TurboTab | Toggle document tab coloring — colors each open tab by project for visual identification |
| Script | Shortcut | Description |
|---|---|---|
| TurboNudge | TN |
Slide a selected keypad along its wall to exactly 5" from a picked door corner — replaces the manual place-then-dimension flow (3D and 2D) |
| Button | Shortcut | Description |
|---|---|---|
| TurboCompact | Ctrl+Shift+S |
Remove unused materials and compact-save the active family |
| TurboSnoop | TS |
Selection-aware: snoop your own element's host (churn/orphan risk), or pick a linked family to list the Visibility/Graphics checkboxes it draws under |
| TurboTag | TT |
Batch-place type tags on selected lighting fixtures |
| TurboWire | WW |
Create arc/spline wires between fixtures |
| TurboBubble | TB |
Place switchleg tag and stub wire on a fixture |
| TurboDriver | TD |
Deploy power supplies for selected RPS fixtures |
| TurboMask | BB |
Mask selected elements while preserving fixture footprint graphics |
| Button | Description |
|---|---|
| TurboSetup | Set up a new project from the linked architectural model (levels, views, link graphics), and name Spaces from the architect's Rooms |
| TurboName | Modeless 2D job setup: linked-CAD layer show/hide + role tagging, region generation, and CAD room-name/ceiling-height assignment to filled regions |
| TurboSchedule | Edit lighting fixture and driver type specs, one Type Mark per page — plus a per-project Excel round-trip for non-Revit designers |
| TurboZones | Manage circuit load names and visualize dimmer panel allocation |
| TurboNumber | Manage circuit numbers, keypad and power supply Switch IDs |
| TurboRPS | Flag stale power-supply selections across all RPS circuits and batch-fix them in place |
| TurboDocs | Generate fixture/RPS schedules, load/panel schedules, cut sheets, and cover/notes PDFs |
All commands work in both:
- 3D Model — Hosted families with 3D geometry in plan/RCP views
- 2D Drafting — Unhosted families placed over linked CAD in floor plan views
Companion references are published via GitHub Pages from docs/, indexed at cdltg.github.io/TurboSuite3D (docs/index.html is the hub):
- Counts Cheat Sheet (
docs/counts.html) — quick reference for authoring TurboDocs Counts parameters: Catalog Number length tokens (max=/sizes=/pool=/min=) and Catalog Qty modes (N,1/N,N @type, and the stock-cutN @ft/N @in). - Lighting Family LOD (
docs/lod-reference.html) — theAL.###authoring ladder mapping our lighting-family tiers to the BIMForum 2024 LOD Specification (D5040.50), with geometry and spec tracked on separate axes.
TurboSuite expects certain families, parameters, and annotation types to be loaded in the Revit project. See each command's README for specific requirements. The table below summarizes shared dependencies.
| Category | Used By |
|---|---|
Lighting Fixtures (OST_LightingFixtures) |
TurboTag, TurboWire, TurboBubble, TurboDriver, TurboZones, TurboDocs, TurboMask |
Lighting Devices (OST_LightingDevices) |
TurboTag, TurboDriver, TurboNumber, TurboZones, TurboDocs, TurboMask, TurboNudge |
Electrical Fixtures (OST_ElectricalFixtures) |
TurboWire, TurboBubble, TurboZones, TurboMask |
Electrical Equipment (OST_ElectricalEquipment) |
TurboWire, TurboNumber, TurboZones, TurboMask |
| Parameter | On | Type | Used By |
|---|---|---|---|
TurboSuite Role |
Fixture, device & tag/detail family types | Text | All commands (classifies which family a command acts on or stamps) |
Switch ID |
Lighting Device instances | Text | TurboDriver, TurboNumber |
Remote Power Supply |
Lighting Fixture types | Yes/No (Integer) | TurboDriver, TurboWire, TurboBubble |
Power |
Lighting Device types | Double (Watts) | TurboDriver, TurboRPS |
Sub-Driver Power |
Lighting Device types | Double (Watts) | TurboDriver, TurboRPS, TurboTag, TurboNumber |
Scale Factor |
Fixture instances | Double | TurboBubble, TurboWire |
Dimming Protocol |
Lighting Fixture types | Text | TurboZones, TurboDocs, TurboDriver |
Data Sheet URL |
Lighting Fixture/Device types | Text (URL) | TurboDocs |
TurboSuite selects tag families by their TurboSuite Role type parameter, not by family name — load a tag family for each role below and assign it that role (the family's own name is up to you). A project must have one tag family per role a command uses, or that command places no tag.
Role (TurboSuite Role) |
Category | Used By |
|---|---|---|
FixtureTypeTag |
Lighting Fixture Tags | TurboTag |
LinearTag |
Lighting Fixture Tags | TurboTag, TurboDriver |
RunLengthTag |
Lighting Fixture Tags | TurboTag |
LinearFeedTag |
Lighting Fixture Tags | TurboBubble |
FixtureSwitchlegTag |
Lighting Fixture Tags | TurboBubble |
RemoteSwitchlegTag |
Lighting Fixture Tags | TurboBubble |
ElectricalSwitchlegTag |
Electrical Fixture Tags | TurboBubble |
SwitchIdTag |
Lighting Device Tags | TurboTag, TurboDriver |
KeypadTag |
Lighting Device Tags | TurboTag |
DeviceSwitchlegTag |
Lighting Device Tags | TurboDriver |
| Type Name | Used By |
|---|---|
AL_Annotation_4.5" |
TurboName |
AL_Annotation_3" |
TurboName (optional — ceiling descriptions) |
- At least one WireType must exist in the project (TurboWire, TurboBubble, TurboDriver)
- A Filled Region type named
Room Regionmust exist (TurboName) - Linked DWG files with room name blocks or text layers (TurboName)
- RevitAPI.dll and RevitAPIUI.dll (Revit 2024, 2025, or 2026, depending on the channel)
- Xceed.Wpf.AvalonDock.dll (ships with Revit) — used by TurboTab for document tab coloring
- ACadSharp (NuGet) — .NET library for reading AutoCAD DWG/DXF files without requiring an AutoCAD installation
- PDFsharp (NuGet) — PDF generation, reading, stamping, and merging. Used by TurboDocs.
- .NET Framework 4.8 (Revit 2024) / .NET 8.0-windows (Revit 2025) / .NET 10.0-windows (Revit 2026) / WPF
dotnet build TurboSuite.sln -c ReleaseThe shared add-in source lives once in Shim/ (a Visual Studio Shared Project) and compiles into a thin per-version shim: Revit2024/ (net48, Revit 2024 API), Revit2025/ (net8.0-windows, Revit 2025 API), and Revit2026/ (net10.0-windows, Revit 2026 API). Each emits TurboSuite.dll into its own Addins\{year}\ folder. To build a single channel directly:
dotnet build Revit2025/TurboSuite.Revit2025.csproj -c Release # or Revit2024/..., Revit2026/...Platform target is x64. Requires the .NET 8.0 SDK and a local install of the matching Revit version (for RevitAPI.dll / RevitAPIUI.dll references). Post-build copies each add-in into %APPDATA%\Autodesk\Revit\Addins\{year}\ for local testing.
Released under the GNU General Public License v3.0.
- pyRevit — TurboTab's document tab coloring was inspired by pyRevit's tab coloring. pyRevit is developed by Ehsan Iran-Nejad and contributors under the GNU GPL v3 license.