US20020040291A1

US20020040291A1 - Method of emulating machine tool behavior for programmable logic controller logical verification system

Info

Publication number: US20020040291A1
Application number: US09/966,121
Authority: US
Inventors: J. Walacavage; Jim Coburn
Original assignee: Ford Motor Co; Ford Global Technologies LLC
Current assignee: Ford Motor Co; Ford Global Technologies LLC
Priority date: 2000-09-29
Filing date: 2001-09-28
Publication date: 2002-04-04
Also published as: US7702491B2; US20020069045A1; US20020040290A1; US8135567B2

Abstract

A method is provided of emulating and visualizing machine tool behavior for a programmable logic controller logical verification system for manufacturing a motor vehicle. The method includes the steps of constructing a mechanical model. The method also includes the steps of viewing motion of the mechanical model in a motion viewer and determining whether the motion of the mechanical model is acceptable. The method further includes the steps of replicating the motion previously defined with PLC code if the motion of the mechanical model was acceptable and using the accepted motion of the mechanical model to compare the behavior of the PLC code relative to the accepted motion.

Description

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application claims the priority date of now abandoned U.S. Provisional Patent Application Ser. No. 60/236,964, filed Sep. 29, 2000.[0001]

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to programmable logic controllers and, more specifically, to a method of emulating machine tool behavior for a programmable logic controller logical verification system for manufacturing a motor vehicle.

2. Description of the Related Art

It is known that programmable logic controller code is written by controls engineers after assembly tooling designs are completed and a manufacturing process has been defined. The creation of the programmable logic controller code is mostly a manual programming task with any automation of the code generation limited to “cutting and pasting” previously written blocks of code that were applied to similar manufacturing tools. Once the programmable logic controller code is written, it is used by a programmable logic controller to operate subsequent hard tools used in the manufacture of parts for motor vehicles. The programmable logic controller code is not validated (debugged) until the hard tools are built and tried. A significant portion of this tool tryout process is associated with the debugging of the programmable logic controller code at levels of detail from a tool-by-tool level, to a workcell level and finally at a tooling or manufacturing line level.

It is also known that a manufacturing line is typically made of three to twenty linked workcells. Each workcell consists of a fixture to position product (sheet metal) and associated automation (robots) that process the product (welding). The workcell typically consists of a fixture/tool surrounded by three or four robots. The product is then transferred to the next workcell in the manufacturing line for further processing, until it exits the manufacturing line.

It is further known that the workcells for a manufacturing line can be modeled before the manufacturing line is implemented. The modeling techniques, such as Robcad from Tecnomatix and Igrip from Deneb, for the manufacturing process are limited in scope to a workcell level, due to how these type of technologies represent and manipulate three dimensional data and tool motions. This scope limitation is due to the manner in which tooling geometry is defined and the manner in which tool motions are described and displayed to a user. The geometry representation is defined through the use of (NURB) type equations, which are very exact and precise, but require intensive microprocessor calculations. The tooling and robotic motions are also microprocessor intensive in that the articulations and movements are described through the use of complex kinematic equations and solvers.

Debugging a PLC control program can broadly be grouped into two sets of conditions: one is verifying the correctness of machine logic as it applies to a workcell and local devices within the workcell; and secondly, verifying the logic of integrating the series of workcells into a manufacturing line, and especially “inter-workcell” devices like robots. Today, there is a need of using three-dimensional (3D) representations of a workcell linked to a PLC to demonstrate the correctness of the PLC logic. However, because these representations typically are full kinematic structures, the ability to scale up these representations to a full manufacturing line is severely limited by its impact on computer resources. In addition, there is no way of verifying the PLC code with the motion of a CAD model.

Therefore, it is desirable to provide a method of emulating machine tool behavior as part of a programmable logic controller logical verification system. It is also desirable to provide a method of emulating machine tool behavior with less than full kinematic structures as part of a programmable logic controller logical verification system. It is further desirable to provide a method of comparing the behavior of PLC code to accepted motion of a CAD model as part of a PLC logical verification system. Therefore, there is a need in the art to provide a method that meets these desires.

SUMMARY OF THE INVENTION

Accordingly, the present invention is a method of emulating machine tool behavior for a programmable logic controller logical verification system for manufacturing a motor vehicle. The method includes the steps of constructing a mechanical model. The method also includes the steps of viewing motion of the mechanical model and determining whether the motion of the mechanical model is acceptable. The method includes the steps of replicating the motion previously defined with PLC code if the motion of the mechanical model was acceptable. The method further includes the steps of using the accepted motion of the mechanical model to compare the behavior of the PLC code relative to the accepted motion.

One advantage of the present invention is that a method of emulating machine tool behavior for a programmable logic controller logical verification system is provided for use in building a tooling or manufacturing line to manufacture parts of a motor vehicle. Another advantage of the present invention is that a method is provided for allowing a controls engineer to compare the behavior of the PLC code to accepted motion of a CAD model as part of PLC logical verification system. Yet another advantage of the present invention is that the method uses transformational arrays that allows a different software technology to do the rendering; one that requires much less computer resource per unit of machine. Still another advantage of the present invention is that the method allows a controls engineer to examine the visual behavior of an entire manufacturing line, thereby verifying some of the more difficult controls problems such as inter-workcell behavior through observation of the visual operation of multiple concurrent workcells. A further advantage of the present invention is that the method allows a controls engineer to verify that the PLC control design system being planned will work as intended, prior to physically building the tools/manufacturing line. Yet a further advantage of the present invention is that the method allows the analytical verification of PLC code prior to vendor tool tryout (VTTO) and directly shortens product development timing, resulting in substantial timing and cost savings.

Other features and advantages of the present invention will be readily appreciated, as the same becomes better understood, after reading the subsequent description taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic view of a system, according to the present invention, for using a method of emulating machine tool behavior for a PLC logical verification system illustrated in operational relationship with an operator. [0013]
FIG. 2 is a diagrammatic view illustrating a method, according to the present invention, of emulating machine tool behavior as part of a PLC logical verification system for the system in FIG. 1. [0014]
FIG. 3 is a diagrammatic view of a user interface for a mechanical model used in the method of FIG. 2.[0015]

DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

Referring to the drawings and in particular FIG. 1, one embodiment of a [0016] system 10, according to the present invention, of emulating machine tool behavior for a programmable logic controller (PLC) logical verification system is illustrated. In the present invention, a user 12 uses a computer 14 for carrying out the emulation. The computer 14 sends and receives information from a mechanical tool design system 16 via an electronic link. The mechanical tool design system 16 is a computer aided design (CAD) system and provides engineering data for standard components, tools, fixture models, and robots to create a mechanical model. The mechanical tool design system 16 allows the user 12 to define a set of kinematics or motions for the geometry of individual components in the mechanical model. The computer 14 sends and receives information from a control system design system 17 via an electronic link. The control system design system 17 creates the binding between a unit element such as a clamp in the mechanical model—the mechanism and the unit of control—and a control assembly. The control system design system 17 provides information for controls such as valves and switches. The control system design system 17 allows the user 12 to generate PLC code. The computer 14 sends and receives information with a PLC logical verification system 18 via an electronic link. The PLC logical verification system 18 allows the user 12 to create an electromechanical system model and verifies the PLC code for a workcell or a tooling or a manufacturing line. The computer 14 also sends and receives information with a “virtual PLC” emulator 20 via an electronic link. The emulator 20, with the mechanical tool design system 16, creates the binding between the unit element in the mechanical model, the mechanism, and the visualization of its behavior. The emulator 20 sends and receives information with the PLC logical verification system 18 to verify the PLC code. Once the PLC code is analytically verified, it is exported by the computer 14 via an electronic link to at least one PLC 22. The PLC 22 is then used at physical tool build to operate a workcell (not shown), which is used in a tooling or manufacturing line (not shown) for the manufacture of parts (not shown) for a motor vehicle (not shown). It should be appreciated that the computer 14, electronic links, and PLC 22 are conventional and known in the art.
Referring to FIG. 2, a method, according to the present invention, of emulating machine tool behavior as part of the PLC [0017] logical verification system 18 is shown. In general, the method includes generating transformational arrays based on CAD geometries during the design phase of the machinery for the mechanical model. The transformational arrays are movies of manipulation of individual components in the mechanical model and are generated with the mechanical tool design system 16. These transformational arrays are then associated with the particular piece of machine component, such as a clamp, throughout the life cycle of the design and verification process. It should be appreciated that the motion of the mechanical model can be generated without transformational arrays and could be generated with other similar technology.
Once the transformational arrays exist and the mechanical design is implemented on a CAD system to produce the mechanical model, the method includes exporting the mechanical model to a special purpose viewer or [0018] motion player 30 such as VisLine. Within the motion player 30, these transformational arrays are sequenced to give a first pass rendition of what the overall machine or manufacturing line behavior will be. After the user 12 is satisfied that the behavior is acceptable or the one desired, then all this information is exported to the controls system design system 17. The controls system design system 17 converts the sequence of the transformational arrays to PLC code. It should be appreciated that the machine components are bound to particular pieces of controls logic or the PLC code in such a way as to preserve the original intention of the first-pass representation. It should also be appreciated that the transformational arrays are bound to logical models of the machine components that are invoked through the virtual PLC technology.
The [0019] user 12, using the controls system design system 17, has now substituted the sequencing logic of the transformational arrays that was present in the first pass rendition with the PLC code that is intended to be executed on the plant floor. The user 12 exports the PLC code to the PLC emulator 20 to play and visualize the PLC code. By playing this PLC code in the PLC emulator 20, and through the binding that has been preserved through this process, the user 12 can observe the sequencing of these transformational arrays using the actual PLC code as if they were watching a machine or manufacturing line of a vehicle assembly plant floor. It should be appreciated that the method is carried out on the computer 14 by the user 12.
As illustrated in FIG. 2, the method includes using the PLC [0020] logical verification system 18 to construct an electro-mechanical model 24. The electro-mechanical model 24 is the collection of devices and their associated behavior that translates PLC I/O voltages into mechanical motion and provides appropriate feedback. The method includes exporting the electromechanical model 24 into a mechanical model 26.
The method also includes using the mechanical tool design system to construct a [0021] mechanical model 26. The mechanical model 26 is a portion of a simulated assembly or manufacturing line representing actual machines, as opposed to control hardware. The mechanical model 26 contains CAD geometries and mechanical motion from the electromechanical model. The geometry representation is defined through the use of (NURB) type equations.
The method includes generating [0022] transformational arrays 28 for the mechanical model 26 with the mechanical tool design system 16. The transformational arrays 28 are a set of coordinates in each of a plurality of arrays. The set of coordinates comprise six coordinates of three dimensions and three rotations. The transformational arrays 28 translate or transform the original coordinates for each point on the CAD geometry into a linear file of recorded coordinates. The transformational arrays are generated by incrementally recording one position of a specific piece of geometry as it is moved through space over a period of time. It should be appreciated that the user 12 of the CAD software for the mechanical tool design system 16 is the creator of the path of the mechanical element in the mechanical model.
The method includes constructing a motion file based on the [0023] mechanical model 26 and the transformational arrays 28 and viewing motion of the mechanical model 26 based on the transformational arrays 28 using a motion player 30 to play the motion file. A motion file is a series of transformations that represent the motion path of a three-dimensional object through simulation space. The motion player 30 interfaces with the mechanical model 26 to control when and in what direction a given motion file plays. The motion player 30 is a software product known as VisLine that provides a lightweight visual animation capability based on CAD three-dimensional models and sets of transformations called “motion files” derived from the CAD models. The order and time for the playing of a motion file is determined by executing a program written in the PLC emulator 20. The written program is a language specification supported by the PLC emulator 20, which is capable of communicating a complex sequence for the execution of motion files and is based on the execution of specified events according to specified conditions. It should be appreciated that events cause actions to occur and create signals available as conditions for executing other events. It should also be appreciated that the transformation does not change nature of object or part but moves the object or part in space.
The method further includes determining whether the motion of the [0024] mechanical model 26 is acceptable. The user 12 views the motion or behavior of the mechanical model 26 and determines whether the behavior is acceptable or desired. If the behavior is acceptable, the method exports all of this information to the controls system design system 17, which converts this information to PLC code to build a manufacturing line. The user 12 replicates the motion of the mechanical model 26 previously defined in the mechanical model 26 with motion commands in PLC code using the controls system design system 17. If the user 12 determines that the behavior is not acceptable or desired, the method includes returning to the mechanical tool design system 16 to change the mechanical model 26 as illustrated in FIG. 3.
After the sequencing logic of the transformational arrays has been replicated with PLC code, the [0025] user 12 exports the PLC code to the PLC emulator 20 to play and visualize the PLC code. The user 12 compares the behavior of the PLC code to the accepted motion of the mechanical model 26 through the sequencing of the transformational arrays 28 as if they were watching a machine or manufacturing line of a vehicle assembly plant floor. It should be appreciated that the method is carried out on the computer 14 by the user 12.
Referring to FIG. 3, a simulation user interface for the [0026] mechanical model 26 is shown that allows a manual override of current position to create a change of state in the mechanical model 26 that was not initiated by the control system design system 17. The interface includes a mechanism 34 to simulate a velocity 36 on the mechanical part or component in the mechanical model 26. The mechanism 34 has a position pointer 38 which may be moved to increase the capability from zero to one hundred. This position pointer 38 is then used to dynamically determine the appropriate position of the light duty geometry in the motion player 30. This is done by incrementally interpreting the position in the transformational array. It should be appreciated that each mechanical part requires certain persistent information in order to run motion files appropriately in order to accurately manipulate state of the mechanical model at rest. The position function file and the position of the verification system are synchronized by the verification system and putting a percentage on the signal to the motion player 30.
The present invention has been described in an illustrative manner. It is to be understood that the terminology, which has been used, is intended to be in the nature of words of description rather than of limitation. [0027]
Many modifications and variations of the present invention are possible in light of the above teachings. Therefore, within the scope of the appended claims, the present invention may be practiced other than as specifically described. [0028]

Claims

What is claimed is:

1. A method of emulating machine tool behavior for a programmable logic controller logical verification system for manufacturing a motor vehicle, said method comprising the steps of:

constructing a mechanical model;

viewing motion of the mechanical model in a motion viewer;

determining whether the motion of the mechanical model is acceptable;

replicating the motion previously defined with PLC code if the motion of the mechanical model was acceptable; and

using the accepted motion of the mechanical model to compare the behavior of the PLC code relative to the accepted motion.

2. A method as set forth in claim 1 wherein said step of constructing comprises using a mechanical tool design system to construct the mechanical model.

3. A method as set forth in claim 2 including the step of constructing an electromechanical model.

4. A method as set forth in claim 3 wherein said step of constructing the mechanical model includes binding the electromechanical model to the mechanical model.

5. A method as set forth in claim 4 wherein said step of constructing the electromechanical model comprises using a PLC logical verification system to construct the electromechanical model.

6. A method as set forth in claim 1 including the step of generating transformational arrays based on computer aided design (CAD) geometries of the mechanical model.

7. A method as set forth in claim 6 including the step of exporting the mechanical model to a control system design system.

8. A method as set forth in claim 7 including the step of constructing a motion file based on the mechanical model and transformational arrays.

9. A method as set forth in claim 8 wherein said step of displaying further comprises playing the motion file by a motion player.

10. A method as set forth in claim 8 including the step of returning to the mechanical tool design system if the motion of the mechanical model is not acceptable.

11. A method of emulating machine tool behavior for a programmable logic controller logical verification system for manufacturing a motor vehicle, said method comprising the steps of:

constructing a mechanical model;

generating CAD transformational arrays for motion in the mechanical model;

constructing a motion file based on the mechanical model and the CAD transformational arrays;

viewing the motion of the motion file in a motion viewer;

determining whether the motion of the mechanical model is acceptable;

replicating the motion previously defined with motion commands initiated by PLC code if the motion of the mechanical model was acceptable; and

using the accepted motion of the mechanical model to compare the behavior of the PLC code to the accepted motion.

12. A method as set forth in claim 11 wherein said step of constructing comprises using a mechanical tool design system to construct the mechanical model.

13. A method as set forth in claim 12 including the step of constructing an electromechanical model.

14. A method as set forth in claim 13 wherein said step of constructing the mechanical model includes binding the electromechanical model to the mechanical model.

15. A method as set forth in claim 14 wherein said step of constructing the electromechanical model comprises using a control system design system to construct the electromechanical model.

16. A method as set forth in claim 11 wherein said step of generating comprises generating CAD transformational arrays based on computer aided design (CAD) geometries of the mechanical model.

17. A method as set forth in claim 11 including the step of exporting the mechanical model to a PLC emulator.

18. A method as set forth in claim 11 wherein said step of displaying further comprises playing the motion file by a motion player.

19. A method as set forth in claim 11 including the step of returning to the mechanical tool design system if the motion of the mechanical model is not acceptable.