Archive for August, 2012

New Release Need for Speed II, Block Clusters Introduction, and Data Updates

Tuesday, August 28th, 2012

Greetings DraftLogicers,

We are pleased to release build to you. This release focuses on further improving the new Drawing Validation, a vast speed jump in Automated Circuiting, data updates that affect conductor and protection selection, and introducing a new feature–‘block clusters’!  What follows is a summary of the differences between this build and the prior.  Given the extra functionality and fixes, we strongly recommend you implement this build ASAP.


Automated Circuiting’s main function has been vastly sped up.  Small projects will complete Automated Circuiting in about half the time (i.e. our tutorial school now completes in about a minute versus just over two minutes prior).  Large projects will see even more of a speed increase, for example a 350K ft2 fitness center used to take about 37 minutes for Automated Circuiting on one of our test machines, now takes about 8 minutes on that machine, about a five times speed increase.


Have you ever needed to put a repetitive cluster of the same blocks to service the same type of device throughout a project?  It gets pretty boring after the first five, or ten, or twenty, right?  Well, the same auto placement and auto snap and rotate features that you have seen in action for single blocks in DraftLogic Electrical can be applied to groups of blocks.  In this build, we have dipped our toes in those waters and included a couple of new rules that support block clusters:  a hospital bed rule and a computer rule.  The hospital bed rule places 4 receptacles and a data/telephone port behind the bed.  Two of the receptacles are pre-tagged as ‘emergency serviced’.  The computer rule places a receptacle for the computer and a data/telephone port alongside it.  So block clusters can contain any combination of DraftLogic Electrical blocks & they will retain all of your attribute and xdata settings that you had when you create the block cluster.  In a near future release, we’ll add a tool palette to support some premade clusters and to support ones you make.

In conjunction with the release of this new ‘Computer’ autoplacement rule, we have downgraded the existing ‘Desk Receptacle’ rule to specifically look for desks rather than doing so but falling back to placing a receptacle opposite the door if desk not found, now will only place receptacle behind desk.  I would recommend only mapping computers during drawing mapping if they are in the architect source unless you want both the regular desk receptacle and the computer package where desks + computers are both mappable from the source.  Alternatively, if you have desks as blocks or closed polylines in the source but no computers, you can choose to map the desks to computers if you want the computer block cluster for each desk.  To support the new rule, we have added ‘Computer’ as destination category in Drawing Mapping Wizard so if there are blocks representing computers or a layer with closed polylines representing computers they can be mapped during the Drawing Mapping process.

There is information on making more types of block clusters added to the forums at:



This release includes 124 additional luminaires (now 1,638), 36 additional room definitions (now 1,554), and some additional project and design parameter templates.  We have gone through each and every table that affects protection and conductor selection and made a number of updates.  Some other tables have also been updated, like the addition of a computer rule that you can apply to rooms that applies a receptacle+data block cluster to computers & hospital bed clusters that apply four blocks to beds in hospital rooms.



The  automatic drawing validation feature included in the last release checks your drawing for the most common trouble spots.  It will completely automatically fix issues that we are 100% confident can be resolved without your interaction & identify the rest with error arrows.  This tool checks out the issues that are behind about 70% of our support calls, specifically issues with:  room boundaries, room IDs, floor boundaries, floor match blocks, duplicate blocks, and bad polylines.  In  this version, we have added some more automatic fixers, added more issue identifications, and also excluded some ‘non-issues’ that were causing false positive issue identifications.

See the Drawing validation forums entry for detail on what it does and how to take advantage of it, changes for this release have been appended to the bottom of the original entry:

The near-zero length polyline cleanup will affect those who edit DraftLogic Electrical block definitions, please review this forums item if you plan on editing DraftLogic Electrical blocks, including block clusters:

As you probably already noticed, the Automated Drawing Validation threatens that you must resolve critical issues before you can continue…this is hot air right now, we are not yet preventing anyone from continuing with known issues.  This will be left this way until we are comfortable that the validation checks are all identifying only valid issues & when we do make a change, you’ll still have an ‘out’ to simply continue onward with the identified issues left as-is.



Osnaps Active Management has been audited, over 200 instances of it have been checked to ensure that user osnaps are saved and restored before/after DraftLogic Electrical functions.  Also, we have added a user preference to allow expert CAD users to disable the Osnaps Active Management, see this forums entry for details:


This release includes resolution of the harmless-but-annoying Automated Exception error on exit from AutoCAD 2011 after using Automated BCW, it manifested as an empty dialog box in AutoCAD 2012.  See this forums entry for information:


For those who have already updated to DraftLogic Electrical V3.0.0.545, we have new update installers to take you from up to this version (  The server and client update installers take care of all the updates except the database update for now.  If you were not already at V3.0.0.545, contact me to plan your update as the update installs may not catch everything that is out of date on your installation.



For those who have already upgraded to V3.0, this update will take 10-15 minutes.  See the attached instructions on downloading and installing, it has been written to apply to this and future updates so file references are generic (files specific to this update are mentioned below).


Give me a call or drop me an email if you want to arrange a time for me to execute the updates or a complete V3.0 installation for you via WebEx.


The two upgrade packages & database update needed for this specific update are:




The database update is for all three databases.  Refer to the attached update manual for details on whether you need to do anything with your database pointers or not.

*** If, however, you have added data that you desire to retain in any of your four libraries, you MUST contact me and let me know what data you have added & we need to execute a manual update by running SQL scripts to make the updates without harming your added data!

Dean Whitford
Chief Executive Officer
Phone 780-906-2888 (9AM to 6PM MTN time)
Visit us on the Internet: