INTRODUCTION & BACKGROUND
Overview
Power plane generation in Proteus aims to be as complete, safe, and automatic as possible. Once the user defines the area for the power plane to occupy the presence and connectivity is computed without further input from the user. However, many options are present in the Edit Zone dialogue from the context menu, allowing for many different use cases and behaviours.
How it Works
Computing the copper presence of a power plane roughly comprises the following steps:
- A list of all nearby layout objects (overlapping the appropriate layer) is compiled.
- For each object on this list the appropriate DRC clearance is found from the DRC system. Note that the power plane is treated as a trace, for the purposes of DRC checking as its boundary is defined as such. Where the clearance generation between an object and the power plane is complex (for example, if the object spans DRC Rooms with defined rules) then per-object clearances are resolved through the normal design rule hierarchy, so a plane crossing a room boundary uses the room rule inside the room and the surrounding rule outside it.
- Next, the bounding region of each object is expanded by the larger of the retrieved DRC clearance or the power plane's own clearance parameter, to generate a list of areas which the power plane should be excluded from. Thermal resist regions are also generated at this step and added to the list.
- Each expanded area is then cut out of the power plane's area. This leaves zero or more electrically connected pieces of copper presence.
- At this point rules about nesting and islands (electronically isolated pieces of copper presence) can be enforced.
Performance
Regenerating the copper presence of a power plane is required after every change in the overlapping layout. For small power planes or simple designs, this isn't a problem, but on larger boards and more complex designs a full regeneration takes enough time that editing is disrupted, or even stalled.
With this in mind two behaviours have been incorporated into the regeneration logic.
1. If the layout change is contained in a small area, only that area is regenerated, with the rest of the copper presence staying the same. The connectivity of the power plane *is* updated as appropriate.
2. If the number of objects overlapping the regenerated region of the power plane is sufficiently high (the Background Regen. Threshold field, set from System > Set Zone Operation in the Zone Configuration dialogue) then a background regeneration is triggered. In this mode the full power plane area is hatched, indicating that a background regeneration is underway, while the user is free to continue editing. The actual regeneration is performed in a background thread with the main window updating with the result after it has been computed.
Power plane regeneration complexity grows with the number of objects overlapping it. One last ditch method of improving the regeneration speed is to split a large power plane into a number of smaller ones, linking with same-net tracking, if required.
Redundancy
Power plane regeneration involves many geometrical intersection and difference calculations and relies on a heavily tested library of functions. However, to improve safety further, an independent geometry library is used within the pre-production check to verify that the power plane doesn't overlap objects that it should not. Because the check does not share an implementation with the code that generated the plane in the first place, it cannot share a bug with it either.
It follows that best practise is ALWAYS to run a pre-production check before generating output files for manufacture, even if it takes a few minutes to complete.
See Also: