Professional Documents
Culture Documents
TFlash Overview PDF
TFlash Overview PDF
TFlash
Lightning Stroke Simulation Software
For Transmission Line Designers
Developed 1996-1997
TFlash
The “T” in TFlash stands for transmission, as the program was specifically designed for
use in designing power transmission lines – those strings of large towers which run
across the landscape, carrying enormous amounts of electrical energy. There was also
a sibling program called DFlash, designed for distribution lines – the network of wooden
poles throughout most communities, carrying much lower current levels. We weren’t
involved with creating DFlash, although we considered what a connection between the
two programs might look like in future incarnations of TFlash.
Lightning causes serious problems for electric power utilities. Being higher than most of
the surrounding trees and structures, the lines and towers act as lightning rods. One
lightning bolt can carry upwards of 30,000 amps of electrical energy – enough to
destroy electrical equipment that isn’t properly protected, and even damage portions of
the towers that support the lines. The danger of being struck varies considerably from
one part of the country to another, from one season to another, and also varies with the
local terrain. Power utility engineers need some way to estimate the relative
effectiveness of various types of towers and lines, in an effort to keep construction and
maintenance costs low and still provide reliable, continuous service to their customers.
When it was developed in 1997, TFlash was the most sophisticated program of its kind.
My father had spent most of his career studying lightning, and had developed a new set
of algorithms for approximating what happens when a complex object such as a
transmission tower is subjected to an enormous surge of energy. For my part, I had
always taken a strong interest in user interface design, and used Microsoft’s Visual
Studio to create an intuitive front end to the mathematics. The result was a Windows
application which was well-received by EPRI’s members.
For the most part, I used the visual metaphor of a notebook for the user interface. The
user began by selecting the number of conductors (power-carrying wires) to use, which
would be consistent throughout the model, and would limit the selection of towers which
carried those conductors. Then the user would create a new page in the notebook for
each tower in the model. Tower shapes could change from place to place, the material
could change from steel to wood to fiberglass, the insulators holding the wires could
change, and the nature of the foundation connecting the tower to the ground could
change. The model also stored an approximate latitude and longitude for each tower.
The user could apply historical weather data if desired, or could simply specify a
particular atmospheric scenario. Lightning strokes could be specifically directed at any
points in the system by the user, or could be selected by the simulator based on its
historical data and a “best guess” algorithm.
The user could attach “probes” at any point on the wires or the towers; the output from
the system resembled a chart recorder showing energy levels over time. Failures (such
as cracked insulators or tripped lightning arrestors) would be called to the user’s
attention regardless of where the probes were. Finally, a commercial graphic tool called
Pro-Essentials was provided with TFlash, which allowed the user to create a variety of
charts from the output data.
The simulation calculations could take anywhere from a few seconds to an hour or
more, depending on the length and complexity of the transmission line and the period of
time under study. There was, or course, a progress indicator, showing the status of the
simulation, and the estimated time of completion.
The remainder of this paper shows screen captures and descriptions from the original
project design documentation. These screen captures came from an early design
document; more pages were added to the notebook over time as our confidence in the
algorithms increased, and the models became more detailed.
TFlash Design Overview page 4
Figure 2 - at the top of the main window is a control for selecting the
current tower. Similar to the controls on a VCR, the buttons move the
current view to either end of the transmission line, or move one tower
forward or backward. Clicking the center allows a specific tower to be
selected.
The four controls to the right of the selector buttons are for creating,
editing and deleting towers. ‘Enter’ takes the current data and
substitutes it for the data in the model at the current point. ‘Insert’
puts a new tower into the model using the current data.
TFlash Design Overview page 5
The first tower may be any of those in the library. Subsequent towers
must conform to the type of the first tower - for example, AC and DC
tower types cannot be mixed.
Each tower has default dimensions. The user may change any of the
dimensions after selecting a tower. Selecting the same tower type for
subsequent towers will thereafter use the modified dimensions.
TFlash Design Overview page 6
Figure 5 - Once a tower type has been selected for a node in the
model, the tabs allow the user to enter data appropriate for that type of
tower. Shown here is the data entry screen for the “Radial
Counterpoise,’ an array of grounding rods beneath the tower.
The Resistivity field is greyed out, indicating that this value is supplied
by TFlash. The Calculate button in the lower right performs that
calculation and updates the Resistivity field.
TFlash Design Overview page 7
Fields such as conductor type and name use data from Access
databases, associated with each page. When the user clicks on one of
these fields, a pop-up menu allows only recognized items to be
selected. These databases can be customized with a selection window
in TFlash, allowing the user to narrow the scope of the selections for a
project.
TFlash Design Overview page 8
There is also a text output display (not shown), which gives the
user a plain ASCII file with the results expressed as numeric
data. This is convenient for exporting to reports.
TFlash Design Overview page 9
Like the Graph Page, this window is not anchored into the
general display, but floats above it.