Custom CAD plugins
Full applications with ribbons, palettes and dialogs on the AutoCAD, Civil 3D, BricsCAD and ARES .NET APIs. Installers, licensing and automatic updates included.
HomeServices
From a single LISP command to a full design application with installer, licensing and a web portal around it. We pick the lightest technology that does the job well and build it around your drawing standards.
Small, frequent tasks suit a LISP routine. Tools with palettes, data and installers suit .NET. Revit work suits Dynamo or the Revit API. Work done outside CAD suits a web portal.
Full applications with ribbons, palettes and dialogs on the AutoCAD, Civil 3D, BricsCAD and ARES .NET APIs. Installers, licensing and automatic updates included.
Quick, dependable commands for repetitive drafting. We also convert old VBA macros to LISP so they keep working in new CAD releases.
Add-ins and Dynamo graphs that place, number, tag and schedule elements across a whole model.
Jobs that open, edit and export drawings in the cloud (formerly Autodesk Forge), so large batches run without a desktop CAD seat.
BOQs, cable schedules and summary tables pulled straight from the drawing into Excel or back into the DWG.
| Item | Qty |
|---|
The same standards and the same support, whichever CAD your offices run.
Plugins and LISP routines for AutoCAD and its toolsets, such as Map 3D, Electrical and Mechanical.
Alignments, profiles, surfaces, point groups and corridors driven from code, with labels that follow your standards.
Add-ins and Dynamo graphs for placing, tagging, numbering and scheduling, and for checking models against your rules.
LISP and .NET tools that behave the same on BricsCAD as on AutoCAD, so a mixed office runs one toolset.
Native .NET plugins for ARES Commander, including ports of existing AutoCAD tools.
LISP and API customization, often moving an AutoCAD toolset across without retraining your drafters.
Routines, menus and toolbars that give ProgeCAD users AutoCAD-style automation.
LISP and .NET customization for teams standardised on ZWCAD.
LISP and API tools for DraftSight, from drafting shortcuts to batch processing.
We've moved complete commercial plugins from AutoCAD to ARES Commander, with their ribbons, palettes, installers and licensing. One shared codebase keeps both versions in step, so a fix or a new feature ships on every platform at once.
A routine that only works on the developer's machine isn't finished. These come as standard on .NET projects, and the parts that apply come with LISP work too.
Commands grouped by workflow step, with icons your team recognises at a glance.
One MSI that supports several CAD releases at once, ready for IT to roll out.
Written for drafters, not developers, and updated with every release.
Optional licensing and automatic updates for tools you distribute.
Working builds at each milestone, tested on your own drawings.
Fixes, new CAD release updates and new features as your needs change.
Installers, licensing, updates and documentation are where many CAD tools fall short. We built them for our own product first, and every client tool can use the same pieces.
Not everyone who depends on your drawings has CAD open. We can put calculators, estimates and project data where your whole team can reach them. These are ideas we can build around your standards, and the pictures use sample data.
The calculations your engineers repeat on every project, in one place and using your own data and limits. Everyone gets the same answer, and it can be saved or sent to Excel.
A first answer for a bid, before anyone opens CAD. Enter a few inputs or draw a boundary on a map, and see what the site could hold.
One place for the drawings, quantities and decisions around a project, so nobody hunts through email for the latest revision.
Upload a drawing and get the result back, with no CAD seat on the desk. The same kind of automation as a plugin, running in the cloud.
Anything your team looks up, retypes or emails around is a good place to start. Tell us what it is and we'll suggest the simplest thing that would help.
Discuss a portalAutoLISP is the scripting language built into AutoCAD and most AutoCAD-compatible programs.
A routine defines a new command. Type it, pick some objects, and the routine does the drafting a person would otherwise do by hand.
The example labels the diameter of every circle you select. It's twelve lines, and it replaces a few hundred clicks on a plate full of holes.
Run a routine in three steps
.lsp file.;; RT-HOLEDIM: label the diameter of every selected circle
(defun c:RT-HOLEDIM (/ ss i ent ctr rad)
(if (setq ss (ssget '((0 . "CIRCLE"))))
(repeat (setq i (sslength ss))
(setq ent (entget (ssname ss (setq i (1- i))))
ctr (cdr (assoc 10 ent))
rad (cdr (assoc 40 ent)))
(entmake
(list '(0 . "TEXT")
(cons 10 (polar ctr 0.0 (* 1.4 rad)))
(cons 40 (* 0.5 rad))
(cons 1 (strcat "%%c" (rtos (* 2.0 rad) 2 2)))))))
(princ))
A rough guide from your own numbers. Move the sliders to match one repetitive drawing task in your team.
PVAstra takes up to 70% off utility-scale solar layouts; simpler repetitive tasks often save more.
About 3 months of one drafter's year, back for engineering.
Talk about your taskA defined tool, a written scope and a fixed price split into milestones. You pay as each milestone is delivered and accepted.
Most clients keep extending their tool. Phase 2 and beyond are scoped the same way, building on the tool your team already uses.
Our own solar plant design software for AutoCAD.
pvastra.com →Describe the task and the CAD platform you use. We'll suggest the simplest way to automate it and quote for it.