Beruflich Dokumente
Kultur Dokumente
CHAPTER 44
DIRECT NUMERICAL CONTROL
Keith Frantz
VP of Development, Cimnet, Inc.
Robesonia, Pennsylvania
44.1 INTRODUCTION
The most obvious failure of numerical control (NC) file management is the crash of a machine tool
into its fixturing, its workpiece, or worse—its operator—because the wrong part program was run.
This is an attention-getting event that brings a shop to a halt. Fortunately, though it’s one of the most
costly single events, it’s also one of the rarer failures of NC file management. The more subtle short-
comings that show up all the time are the ones that really combine to steal productivity and profits
from a facility.
This article introduces the problems that challenge today’s metal fabrication manufacturer and
how direct numerical control (DNC) systems will help to solve these problems. The benefits of
DNC systems are widely understood and acknowledged to improve factory productivity and product
quality.
Calculating the cost of managing your DNC system is not easy. There are many activities involved
with an NC machining operation, some of which are easily overlooked. Some occur in the ordinary
course of events; others happen infrequently and on an irregular basis.
The cost of the recurring activities can at least be estimated by taking a daily average of the number
of programs worked on, and adding up the times spent on each activity involved for a single program,
multiplying these two numbers together, and multiplying the result by an average hourly cost. Creation
of new part programs will usually have to be costed separately from the running of existing part pro-
grams because most shops reuse files as parts that were made previously are rerun for new jobs.
44.1
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)
Copyright © 2004 The McGraw-Hill Companies. All rights reserved.
Any use is subject to the Terms of Use as given at the website.
DIRECT NUMERICAL CONTROL
Costing nonroutine activities is much harder, because both their frequency and the cost of each
occurrence are usually guesses, and thus can vary widely. One approach would be to make a list of
each event involving NC part programs that has been known to occur and get a number of knowledge-
able individuals to make independent estimates of how often they happen and what they cost when
they do. Don’t forget to include direct costs as well as labor and overhead when costing sporadic
occurrences—wasted stock, replacement parts, extra supplies, etc.
If your facility is like most, you will be astounded at the costs involved if a thorough analysis is
made. At almost every point, however, there are actions you may be able to take that will make an
incremental improvement, depending on how things are currently working. These fall into the same
general categories as most manufacturing improvements—saving time, reducing costs, and reducing
waste and scrap.
In order to see where improvements can be made in the processes relating to NC files, let’s first con-
sider the routine activities from beginning to end, and then look at things that don’t happen all the time.
44.4.1 Programming
The first thing that happens to an NC file is, of course, that it is created. The actual time required to
produce the post-processed part program is largely dependent on the CAM system and the pro-
grammer’s skill in using it. However, his job is not finished when the posted file is written. It needs
to be identified with the correct part, operation, and machine, and associated with the right tooling,
fixturing, and any special instructions. If the file is to be stored on physical media for transfer to the
machine, the media must be punched or written, and then stored in the right location with appropri-
ate identification. Even if there is a DNC system so that the transfer will be done electronically, the
file must be put in the appropriate place and identified.
from the file itself, it becomes possible to identify multiple contexts for the same file, e.g., if the
same part program is used for a particular operation on several parts, the file only needs to be stored
once, yet can be identified as being used for each part (Fig. 44.1).
The next thing that happens to an NC program is that it is identified as one of the inputs needed to
run a particular operation on the factory floor. This is a specific case of the more general need for
supervisors to instruct operators what to do. Since the order entry and job scheduling systems are not
necessarily tied to programming, the need for a particular NC file might arise before the file is ready
for manufacturing.
When an operator knows he has a specific job to do, the steps he must take with respect to the NC
part program begin with retrieving the part program from wherever it is stored, and loading it into
the control. He will almost certainly check it out somehow—inspecting the code, dry running the
machine, etc. He may need to edit it, due to a change in tooling or fixturing not anticipated by
programming, a last-minute revision of the part, or just because he has a better way to do the job.
In doing these things he will need to consult other documentation for the current task—a blueprint, a
tool sheet, special fixturing instructions, etc. He will then run the parts and if all goes well, usually
after he’s done, he will save the part program if he had changed it at all, along with any changes made
to the other documentation he was using. Finally these changes will need to be brought to the atten-
tion of the relevant people so they can be documented and incorporated into the information to be
used for the next time that part is to be made.
repeated, or some maintenance must occur before the reading can be successfully completed. Cutting
down on the use of mechanical devices in this process not only saves a little time every time a new
program is read into the control, but occasionally saves quite a bit of time when the process doesn’t
work the first time.
Verification Program With Solid Modeling Software. If the program can be verified electroni-
cally, this will be faster than dry-running (at a reduced feed rate) or visually inspecting the program.
To be most effective, more than the tool center line path must be shown—the actual tool and stock
geometry must be included in the model (see Fig. 44.3).
Modify Program Locally. If editing is needed, and it cannot effectively be done on the control,
the operator must get programming to make the change or find a terminal to make the change him-
self. Having a complete part program editor available locally could end up saving a great deal of time
(see Fig. 44.4).
Manage Toolbreak Restarts. An unfortunate fact of life in metal cutting is that tools sometimes
break. This will mean backing up to some point in the NC program, and restarting again from that
point. While straightforward if the entire part program resides in the control’s memory, recovering
from this can be a time consuming activity if “drip-feeding” from an external source. This usually
also means manually inputting MDI setup information. A system that can electronically provide just
the portion of the program yet to be run, with the requisite header, tool change, etc. can save a lot of
work.
Save Changes to Programs Electronically. If the program is changed, it needs to be saved for
future use, or at least reference. If it needs to be stored on physical media (by punching a tape or
writing a disk) there is time that could be saved both in the actual transfer itself (especially punch-
ing a long tape), and in storing, labeling, and logging the revised version, and notifying the right peo-
ple about it. The same is true of drawings or other paper documents if they are marked up—while
the operator is not a draftsman, markups need to be disseminated to the right people so the originals
can be updated. Any of these activities that can be accomplished electronically, including the notifi-
cation of people, will save time, and potentially reduce errors.
Other activities which touch on the handling of NC files happen less frequently—perhaps only a few
times—yet if not handled well they can take a long time.
Factories using NC machines vary from small job shops up to large multinational manufacturers. In
all cases, most DNC systems have the communications capabilities to expand from small installa-
tions with a single computer up to site-wide installations with servers and networked computers. The
method of communicating with the NC machines is similar in all cases.
There are two mainstream methods of communicating to your NC machines from DNC systems.
One is via the RS232 serial port on your computer and the other is via Ethernet. The method depends
on the communications capabilities of the controller on the machine itself. The more modern
machines support Ethernet.
In the case of serial communications, many DNC systems have multiport serial devices to com-
municate with many NC machines as seen in drawing below. On older machines, it was common
to use paper tape to load a program into a machine. This too can be incorporated into a DNC sys-
tem using a behind the reader device or BTR. A BTR solution involves putting a computer serial
port in series with the old paper system to simulate the loading of the program into the machine
tool (see Fig. 44.5).
44.6 CONCLUSION
By this point it will be apparent that the elimination of physical media using software running
on a common PC will in time save many times the cost of whatever equipment is required to
accomplish it. DNC systems are the rule rather than the exception, and for good reason—they’re
cost-effective. But what characteristics should the DNC system possess to optimize the flow of
part programs and their related information? To summarize the points made in the preceding
sections:
In addition there are a few other points to consider in deciding whether an upgrade to a modern
DNC system is worthwhile:
1. Is the system upgradeable to allow it to eventually be tied in to the rest of the company’s infor-
mation systems? Can it be integrated with data collection, monitoring, document management,
and scheduling?
2. Does the DNC system support special communications protocols that were not present in the
existing system? It may be possible to bring machines into the system that previously operated as
independent islands.
3. To what extent is security implemented in the system? Even if the facility’s work does not deal
with sensitive information, a good security system can prevent mistakes, sabotage, and just plain
old “messing around.” It should be possible to limit who can access which files, for example to
differentiate proven from unproven programs.
In summary, a modern, flexible, expandable DNC system can go a long way toward saving time
and reducing errors in your facility. Ordinary day-to-day activities will be simplified, and the impact
of extraordinary events will be minimized.
INFORMATION RESOURCES
www.cimnet.com
www.mmsonline.com
www.ndx.com
www.e4production.net
www.modernapplicationsnews.com
www.metalworkingdigest.com