Machines for emulating machines

TECHNICAL FIELD

The present application relates generally to machine emulation and, more particularly, machine emulator machines comprising an emulator that mimic programmable logic controller code of a programmable logic controller to produce output response data that emulates a machine.

BACKGROUND

Machines and systems used to fabricate products, such as consumer goods products, for example, often use programmable logic controllers to control the various actuators of the machine. Programmable logic controllers are programmed with programmable logic controller code to generate drive signals for the various actuators in accordance with a desired sequence to fabricate the products.

A designer or operator of the machine may be required to make modifications to the programmable logic controller code for many reasons. For example, there may be a change to the specifications to the product that necessitates a change to the programmable logic controller code. A new product may require changes to the programmable logic controller code. Additionally, changes to the machine used to fabricate the product may require updating the programmable logic controller code.

Modifying the programmable logic controller code may be time consuming for the designer or operator. In many cases, changes are made to the programmable logic controller code is accomplished by trial and error. Changes are made and then observation of the machine with the code changes is performed. However, such an iterative process may be time consuming and create down-time for the machine.

Accordingly, alternative systems and methods for emulation a machine, and predicting product values of a product manufactured by a machine as well as predicting a process of a machine are desired.

SUMMARY

According to the present disclosure, a machine includes a plurality of actuators, a plurality of mechanical elements, wherein individual ones of the plurality of mechanical elements are coupled to individual ones of the plurality of actuators such that the plurality of actuators move the plurality of mechanical elements, and a human machine interface having a machine graphics display device, the human machine interface configured to accept input parameters. The machine graphics display device is operable to display the input parameters and output data. The machine further includes a programmable logic controller including a machine computer usable medium. The programmable logic controller is communicatively coupled to the human machine interface and is configured to receive input parameters from the human machine interface and provide output signals to the plurality of actuators in accordance with the received input parameters. The machine also includes a computer device including a processor and a non-transitory computer usable medium for emulating a process of the machine. The non-transitory computer usable medium is configured to display a graphical user interface comprising a plurality of input fields corresponding to the plurality of actuators and the plurality of mechanical elements, and a graphical representation of output response data of the machine using inputted parameters, computer readable code instructions for receiving a plurality of parameters inputted into the plurality of input fields, wherein the plurality of parameters are associated with the plurality of actuators and the plurality of mechanical elements. The non-transitory computer usable medium emulates a mechanical operation of the machine using the plurality of parameters inputted into the plurality of input fields by simulating the programmable logic controller code, and generating the output response data based on an emulation of the mechanical operation of the machine. The non-transitory computer usable medium is configured to convert the output response data into the graphical representation of output response data for display within the graphical user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> schematically depicts a computer system for emulating a machine according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 2</figref> schematically depicts a human machine interface of a machine according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 3</figref> schematically depicts internal components of the computer system depicted in <figref idref="DRAWINGS">FIG. 1</figref> or the human machine interface depicted in <figref idref="DRAWINGS">FIG. 2</figref> according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 4</figref> schematically depicts a graphical user interface of an emulator computer program product for emulating a machine according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 5</figref> schematically depicts a geometry settings form of a graphical user interface according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 6</figref> depicts graphs and tables corresponding to output response data generated by a computer emulation of a machine according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIGS. 7A and 7B</figref> depict a screen shot of a machine animation resulting from output response data according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 8</figref> depicts a flowchart of the process for generating an animation file of a machine animation according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 9</figref> schematically depicts an emulator linked to a programmable logic controller of a machine according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIGS. 10A and 10B</figref> schematically depict a graphical user interface of an emulator computer program product for presenting training scenarios to a user according to one or more embodiments illustrated and described herein; and

<figref idref="DRAWINGS">FIG. 11</figref> schematically depicts a machine emulator computer program product linked to a product model and a process model according to one or more embodiments illustrated and described herein;

<figref idref="DRAWINGS">FIG. 12</figref> schematically depicts a diagram illustrating a machine emulator linked to a product model according to one or more embodiments illustrated and described herein; and

<figref idref="DRAWINGS">FIG. 13</figref> schematically depicts a diagram illustrating a machine emulator linked to a process model according to one or more embodiments illustrated and described herein.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments disclosed herein are generally related to computer program products, systems, and methods for emulating a machine of a manufacturing process. Generally, the embodiments described herein may comprise an emulator model that utilizes a calculation routine that emulates programmable logic controller code used by a programmable logic controller provided as a component of the machine to control various actuators of the machine. As used herein, the phrase “programmable logic controller” encompasses traditional programmable logic controllers as well as microcontrollers, application specific integrated circuits (ASIC), and the like, that may be utilized in embedded systems. Further, the phrase “programmable logic controller code” as used herein means program code that is executed by a programmable logic controller, microcontroller, ASIC, or the like. The calculation routine may use geometric information regarding the various mechanical elements of the machine (e.g., mandrels, rods, turrets, etc.) and actuators (e.g., servo motors, pneumatic cylinders, hydraulic cylinders, linear actuators, etc.) to produce output response data, such as servo drive positioning tables, for example. In one embodiment, an animation of the machine process based upon user-inputted parameters is provided.

The embodiments described herein may be used by an operator of the emulated machine for training purposes. For example, the computer program product may be installed on a computer device that the operator may use to enter various parameters to determine the effect of such parameters without actually programming the programmable logic controller and perhaps causing damage to the products being manufactured and/or the machine. Further, in one embodiment, training scenarios are presented to the user that requests the user to make adjustments to the parameters in accordance with the training scenarios.

As described in detail below, embodiments may be used on a computer device as well as on the actual human machine interface of the machine being emulated. For example, an operator of a machine may switch between the actual human machine interface used to control the machine and the emulator graphical user interface. The emulator model may be linked with a product model and/or a process model to share parameter values therebetween. Various embodiments of the computer program products, methods, and systems for emulating a process of a machine are described in detail below.

Although embodiments are described herein in the context of a winder machine for winding a continuous web material onto rolls (e.g., paper towels), embodiments may be used to model any machine and/or process. As non-limiting examples, embodiments may be used to emulate a diaper manufacturing process, a shoe manufacturing process, and the like. An exemplary winder machine for which the embodiments described herein may emulate is described in U.S. Pat. No. 7,392,961. Embodiments described herein may also be utilized in other industrial processes, such as the processes of spraying, gluing, and the manufacture of liquid/powder products, such as detergent. Although embodiments described herein emulate mechanical elements and mechanical actuation, embodiments may also be used to emulate flow rates of fluid (e.g., based on nozzle configuration, fluid lines, etc.), fluid patterns and boundary layers, etc.

Referring now to the drawings, <figref idref="DRAWINGS">FIG. 1</figref> depicts an exemplary computer system <b>10</b> on which a computer program product in accordance with the embodiments described herein may be installed. The computer system <b>10</b> may comprise a computer device <b>12</b>, a graphics display device <b>13</b>, and input devices, such as a keyboard <b>14</b> and a mouse <b>15</b>. It should be understood that while the computer system <b>10</b> is depicted as a personal computer system, this is a non-limiting example. More specifically, in some embodiments any type of computing device (e.g., smart phone, tablet computer, laptop computer, media player, server, specialized computer, etc.) may be utilized. As described in detail below, machine emulator computer program code may be installed on the computer device <b>12</b> such that a user may input parameters into the graphical user interface to emulate machine processes.

Referring now to <figref idref="DRAWINGS">FIG. 2</figref>, an exemplary human machine interface <b>20</b> a machine is depicted, wherein the human machine interface <b>20</b> is configured as an operator terminal. An operator of a machine, such as a winder machine, may use the human machine interface unit to interact with, program, and otherwise control the machine. The human machine interface <b>20</b> of the illustrated embodiment comprises a machine graphics display device <b>23</b> and user input elements <b>24</b> (e.g., a keyboard and other buttons) built into a human machine interface cabinet <b>22</b>. The human machine interface <b>20</b> may enclose a programmable logic controller <b>28</b> and other hardware components, such as a processor and memory (see <figref idref="DRAWINGS">FIG. 3</figref>). The human machine interface <b>20</b> may have a door <b>26</b> to provide access to the electrical components maintained therein. The programmable logic controller may be electrically coupled to a plurality of actuators associated with the machine, and may be programmed to provide output signals such that each of actuators move in accordance with programmable logic controller code logic, which may be stored on a machine computer usable medium (i.e., a memory component) within the programmable logic controller. It should be understood that the human machine interface <b>20</b> may take on a variety of configurations, and that embodiments of the present disclosure are not limited to the configuration of the human machine interface <b>20</b> depicted in <figref idref="DRAWINGS">FIG. 2</figref>. As an example and not a limitation, the human machine user interface may be configured as a tablet or pendant that the operator may hold in his or her hands.

<figref idref="DRAWINGS">FIG. 3</figref> depicts internal components of the computer device <b>12</b> or the human machine interface <b>20</b> depicted in <figref idref="DRAWINGS">FIGS. 1 and 2</figref>, respectively, further illustrating a system for emulating a process of a machine, and/or a non-transitory computer usable medium having a computer program product comprising computer readable code instructions for emulation of a machine as hardware, software, and/or firmware, according to embodiments shown and described herein.

As also illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, the computer device <b>12</b> or the human machine interface <b>20</b> may include a processor <b>30</b>, input/output hardware <b>32</b>, network interface hardware <b>34</b>, a data storage component <b>36</b> (which may store parameters data <b>38</b><i>a</i>, output response data <b>38</b><i>b</i>, and graphics element data <b>38</b><i>c</i>, described below), and a non-transitory memory component <b>40</b>. The memory component <b>40</b> and data storage component may be configured as volatile and/or nonvolatile computer readable medium and, as such, may include random access memory (including SRAM, DRAM, and/or other types of random access memory), flash memory, registers, magnetic disks, compact discs (CD), digital versatile discs (DVD), and/or other types of storage components. Additionally, the memory component <b>40</b> may be configured to store operating logic <b>42</b>, calculation routine logic <b>43</b>, graphical representation logic <b>44</b>, and animation logic <b>45</b> (each of which may be embodied as computer readable program code instructions, firmware, or hardware, as an example). A local interface <b>46</b> is also included in <figref idref="DRAWINGS">FIG. 3</figref> and may be implemented as a bus or other interface to facilitate communication among the components of the computer device <b>12</b> or the human machine interface <b>20</b>.

The processor <b>30</b> may include any processing component configured to receive and execute computer readable code instructions (such as from the data storage component <b>36</b> and/or memory component <b>40</b>). The input/output hardware <b>32</b> may be configured to receive signals from user input and output devices such as a graphical display device, a keyboard, a mouse, a printer, a camera, a microphone, a speaker, a touch-screen, and/or other device for receiving, sending, and/or presenting data. In some embodiments, the computer device <b>12</b> or the human machine interface <b>20</b> may be connected to a network via the network interface hardware <b>34</b>. The network interface hardware <b>34</b> may include any wired or wireless networking hardware, such as a modem, LAN port, wireless fidelity (Wi-Fi) card, WiMax card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices.

It should be understood that the data storage component <b>36</b> may reside local to and/or remote from the computer device <b>12</b> or human machine interface <b>20</b>, and may be configured to store one or more pieces of data. As illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, the data storage component <b>36</b> may store parameters data <b>38</b><i>a</i>, which in at least one embodiment includes a plurality of parameters entered into a graphical user interface by a user or an operator. The parameters may define operational and mechanical characteristics of mechanical elements and actuators of the machine. Similarly, output response data <b>38</b><i>b </i>may be stored by the data storage component <b>36</b> and may include output response data resulting from previous emulation sessions executed by the calculation routine logic <b>43</b>. Graphics element data <b>38</b><i>c </i>used to generate animations of the machine process (e.g., computer graphics associated with each of the parts of the emulated machined, such as a mandrel, a belt, a turret, etc.) may also be stored in the data storage component <b>36</b>.

Included in the memory component <b>40</b> may be the operating logic <b>42</b>, the calculation routine logic <b>43</b>, the graphical representation logic <b>44</b>, and the animation logic <b>45</b>. The operating logic <b>42</b> may include an operating system and/or other software for managing components of the server computing device <b>12</b><i>b</i>. The operating logic <b>42</b> may also include computer readable program code for displaying the graphical user interface described herein. Similarly, the calculation routine logic <b>43</b> may reside in the memory component <b>40</b> and may be configured to mimic the programmable logic controller code used to control the machine, and produce corresponding output response data of the plurality of mechanical elements and the plurality of actuators of the machine. The graphical representation logic <b>44</b> may be configured to receive the output response data generated by the calculation routine logic <b>43</b> and generate a graphical representation of output response data, such as graphs and tables, for example. The animation logic <b>45</b> may be configured to create one or more animations of a machine process based on the output response data generated by the calculation routine logic <b>43</b>. In an alternative embodiment, the memory component <b>40</b> and the data storage component <b>36</b> are the same element such that the operating logic <b>42</b>, the calculation routine logic <b>43</b>, the graphical representation logic <b>44</b>, the animation logic <b>45</b>, the parameters data <b>38</b><i>a</i>, the output response data <b>38</b><i>b</i>, and the graphics element data <b>38</b><i>c </i>are all stored on the same physical memory device.

It should be understood that the components illustrated in <figref idref="DRAWINGS">FIG. 3</figref> are merely exemplary and are not intended to limit the scope of this disclosure. More specifically, while the components in <figref idref="DRAWINGS">FIG. 3</figref> are illustrated as residing within the computer device <b>12</b> or the human machine interface <b>20</b>, this is a non-limiting example. In some embodiments, one or more of the components may reside external to the computer device <b>12</b> or the human machine interface <b>20</b>.

As described above, embodiments of the present disclosure are directed to emulation of a machine and machine process using a graphical user interface wherein the user may enter machine parameters into the graphical user interface and the emulator module will produce output response data corresponding with the parameters entered by the user. As used herein, the phrase “graphical user interface” means any type of interface using a screen or monitor that presents information to a user and allows a user to input information. Graphical user interfaces may include, but are not limited to, traditional graphical user interfaces (such as interactive windows), tables, and command line interfaces, such as DOS prompts. Referring to <figref idref="DRAWINGS">FIG. 7A</figref>, a screen shot of an animation of a hybrid winder machine <b>210</b> provided by an emulation model of one embodiment is illustrated. A winder or reel is typically known as a device that performs the very first wind of the continuous web material, generally forming what is known as a parent roll. A rewinder, on the other hand, is generally known as a device that winds the continuous web material from the parent roll into a roll that is essentially the finished product. For purposes of the present application, the words “winder” and “rewinder” are interchangeable with one another.

As shown in <figref idref="DRAWINGS">FIG. 7A</figref>, a hybrid winder machine <b>210</b> of the exemplary animation generally comprises a turret <b>222</b> supporting a plurality of winding spindles <b>218</b> and a conveyor belt having a first conveyor roller <b>228</b> and a second conveyor roller <b>230</b>. The hybrid winder machine <b>210</b> may be suitable for use in winding a continuous web material <b>212</b> to produce a final wound product <b>214</b>. As an example and not a limitation, the continuous web material <b>212</b> may be transported by the conveyor belt <b>216</b> into winding contact with at least one winding spindle <b>218</b>. In one embodiment, a plurality of winding spindles <b>218</b> are disposed upon a winding turret <b>222</b> indexable about a center shaft thereby defining a winding turret axis. The winding turret <b>222</b> is preferably indexable, or moveable, through an endless series of indexed positions. For example, a first winding spindle <b>224</b> can be located in what may be conveniently called an initial transfer position and a second winding spindle <b>226</b> can be located in what may conveniently be called a final wind position. In any regard, the winding turret <b>222</b> may be indexable from a first index position into a second index position. Thus, the first winding spindle <b>224</b> may be moved from the initial transfer position into the final wind position. Such indexable movement of the first winding spindle <b>224</b> disposed upon winding turret <b>222</b> may comprise a plurality of discrete, defined positions or a continuous, non-discrete sequence of positions. However, it should be appreciated that winding spindle <b>218</b> can be brought into proximate contact with conveyor belt <b>216</b> by any means known to one of skill in the art.

In one embodiment, the conveyor belt <b>216</b> is driven at a surface speed that corresponds to the speed of the incoming continuous web material <b>212</b>. A positioning device(s), such as first positioning actuator <b>252</b> and second positioning actuator <b>254</b> (e.g., linear actuators, servo motors, cams, links, and the like known by those of skill in the art), are provided for control of the position of first conveyor roller <b>228</b> and second conveyor roller <b>230</b> supporting conveyor belt <b>216</b>. Thus, first positioning actuator <b>552</b> associated with first conveyor roller <b>228</b> may be capable of moving first conveyor roller <b>228</b> along a first axis. In such an embodiment, the first axis is generally parallel to the Z-direction relative to continuous web material <b>212</b> as web material <b>212</b> passes proximate to a winding spindle <b>218</b>. Likewise, second positioning actuator <b>254</b> associated with second conveyor roller <b>230</b> may be capable of adjusting the position of second conveyor roller <b>230</b> along a second axis. In such an embodiment, the second axis is generally parallel to the Z-direction relative to web material <b>212</b> as web material <b>212</b> passes proximate to a winding spindle <b>218</b>. The position of first conveyor roller <b>228</b> and second conveyor roller <b>230</b>, when combined with the known diameter growth of the log associated with second winding spindle <b>226</b>, can provide the desired contact, clearance, and/or pressure between the conveyor belt <b>216</b> and the log associated with second winding spindle <b>226</b>.

As mentioned above, the winding spindles <b>218</b> may engage a core (not shown) upon which the web material <b>212</b> is wound. The winding spindles <b>218</b> are driven in a closed spindle path about the winding turret <b>222</b> assembly central axis. Each winding spindle <b>218</b> extends along a winding spindle <b>218</b> axis generally parallel to the winding turret <b>222</b> assembly winding turret axis, from a first winding spindle <b>218</b> end to a second winding spindle <b>218</b> end. The winding spindles <b>218</b> may be supported at their first ends by the winding turret <b>222</b> assembly. The winding spindles <b>218</b> may be releasably supported at their second ends by a mandrel cupping assembly (not shown).

Once the desired number of sheets of web material <b>212</b> has been wound into a log associated with second winding spindle <b>226</b>, a web separator <b>234</b> can be moved into position proximate to web material <b>212</b> disposed upon conveyor belt <b>216</b> in order to provide separation of adjacent sheets of perforated web material <b>212</b>. The web separator <b>234</b> can be provided as a rotary unit sharing apparatus known to those of skill in the art useful for the severance of the web material <b>212</b> into individual sheets. In one embodiment, the web separator <b>234</b> cooperates with the surface of conveyor belt <b>216</b> upon which web material <b>212</b> is disposed. The web separator <b>234</b> may be provided as a continuous speed roll moved intermittently and/or periodically into contact with the web material <b>212</b> disposed upon conveyor belt <b>216</b>. The movement of the web separator <b>234</b> may be timed such that the web separator <b>234</b> nips the web material <b>212</b> against the conveyor belt <b>216</b> when the perforation at the trailing end of the last desired sheet for the log associated with second winding spindle <b>226</b> is located between the first, or new, winding spindle <b>224</b> at the transfer position (i.e., at the web material <b>212</b> nip point) and the web separator <b>234</b> surface when it contacts the conveyor belt <b>216</b>. Element <b>217</b> may be utilized to secure a loose tail of the web material associated with the second winding spindle <b>226</b> after the separation of the web material <b>212</b> by the web separator <b>234</b>.

Referring now to <figref idref="DRAWINGS">FIG. 4</figref>, an exemplary graphical user interface <b>100</b> of an emulator computer program product for emulating a winder machine (i.e., “emulator”) is illustrated. The graphical user interface <b>100</b> of the illustrated embodiment is for the winder machine that is schematically illustrated in <figref idref="DRAWINGS">FIG. 7A</figref>. As described above, the graphical user interface <b>100</b> may be generated and displayed by the computer device <b>12</b> or the human machine interface <b>20</b> illustrated in <figref idref="DRAWINGS">FIGS. 1-3</figref>. In one embodiment, a visual layout of the graphical user interface <b>100</b> of the emulator is substantially similar to the graphical user interface of the actual human machine interface <b>20</b> used to program and control the machine. In this manner, operators of the machine may feel comfortable operating the emulator, and real scenario training of operators may be facilitated.

Generally, the graphical user interface <b>100</b> of the emulator comprises a plurality of input fields <b>101</b>-<b>106</b> into which a user may enter or otherwise adjust parameters associated with mechanical elements and actuators of the machine, as well as product parameters desired of the finished, wound product. As an example and not a limitation, the emulator may be a VB.Net 2010 application. Mechanical elements are defined herein as the mechanical components of the machine, such as belts, mandrels, turret, rods, etc., while actuators are defined herein as the components that provide motion to the machine, and may include, without limitation, servo motors, linear actuators, pneumatic actuators, and hydraulic actuators. An individual input field displayed by the graphical user interface <b>100</b> may correspond to a particular property of a mechanical component or actuator of the machine (e.g., size, length of travel, actuation speed, etc.). The input fields <b>101</b>-<b>106</b> displayed by the graphical user interface <b>100</b> may be the same input fields displayed by the human machine interface of the machine.

As an example and not a limitation, plurality of machine input fields <b>101</b>-<b>103</b> may correspond with hybrid winder machine element/actuator parameters, while plurality of product input fields <b>104</b> may correspond with various product parameters. The parameters associated with input fields <b>101</b>-<b>103</b> may correspond, for example, to elements such as the conveyor belt <b>216</b>, first and second positioning actuators <b>252</b>, <b>254</b>, winding turret <b>220</b>, web separator <b>234</b>, etc.

More or fewer input fields may be provided depending on the particular application. It should be understood that the type of parameters and input fields will depend on the machine being emulated. For example, the parameters for a machine used to manufacture shoes will have different mechanical elements and actuators than a winder machine and therefore the graphical user interface face will display input fields.

In one embodiment, a user of the emulator may also define the geometric configurations of the various mechanical elements of the machine. As an example and not a limitation, a user may select an option from a menu bar <b>107</b> to display a geometry setting form such as the geometry settings form <b>160</b> depicted in <figref idref="DRAWINGS">FIG. 5</figref>. The user may enter dimensional parameters into the form into a plurality of input fields <b>164</b>/<b>165</b> of the geometry settings form <b>160</b>. In the illustrated example, the geometry settings form <b>160</b> enables a user to enter parameters associated with a particular machine element associated with geometry tab <b>162</b><i>d</i>. Parameters for other machine elements may be entered by selected geometry tabs <b>162</b><i>a</i>-<b>162</b><i>c</i>. In one embodiment, the geometry settings form includes error checking input fields <b>164</b> and machine element geometry input fields <b>165</b>. The error checking input fields <b>164</b> may allow a user to enter belt actuator minimum and maximum parameters such that the emulator may generate error messages when the output response data for the belt actuator indicates that the belt actuator is below the minimum or above the maximum values entered into the error checking input fields <b>164</b>. Similarly, the user may enter belt geometry parameters into the plurality of machine element geometry input fields <b>165</b> (e.g., machine element dimensions). The geometry settings form <b>160</b> may be used by the user (e.g., machine designer, operator, trainee, etc.) to make design changes to the machine to predict how the redesigned machine will perform without actually changing the physical machine.

Input fields <b>106</b> may correspond with parameters associated with the product. In the winder machine context, the product may be wound web material, such that the parameters associated with input fields <b>106</b> may be sheet length, roll diameter, etc.

The parameters inputted into the plurality of input fields <b>101</b>-<b>106</b> and the geometry settings form <b>160</b> may be received and used by calculation routine logic that mimics the actual programmable logic controller code of the programmable logic controller in detail to produce output response data such that the machine process is emulated. A user may alter one or more parameters to predict an output response of the machine without physically running or altering the machine. The calculation routine may allow for ease of future updates to the machine and may reduce the potential for errors in the code.

The calculation routine logic may be computer readable program code that has been translated from the programmable logic controller code and operable to run on a computer device. As an example and not a limitation, the calculation routine logic may be implemented in an event-driven programming language (e.g., Microsoft® Visual Basic, or similar languages) application. Programs of the programmable logic controller code may be translated into modules, and routines may be translated into subroutines and functions, within calculation routine logic of the emulator application. In some embodiments, other calculation software packages may be used to develop functions that are imported into the calculation routine logic (e.g. MATLAB-generated algorithms provided as a DLL file utilized by the calculation routine logic).

In one embodiment, the output response data produced by the calculation routine may be displayed in a graphical representation within the graphical user interface <b>100</b>. The graphical representation of the output response data may come in a variety of forms. In one embodiment, as depicted in <figref idref="DRAWINGS">FIG. 4</figref>, the graphical representation may be in the form of a servo drive data chart <b>120</b> that displays servo drive data of one or more of the servo actuators of the machine. In one embodiment, the servo drive data chart <b>120</b> mimics an output from the programmable logic controller code used to control the machine. The graphical representation may provide graphs (as well as tables) of the actuators' position, velocity, acceleration, and jerk. The graphical user interface <b>100</b> may include a graphical representation selection area <b>130</b> having one or more selectable buttons to generate particular charts, graphs, tables, etc. In the illustrated embodiment, the graphical representation selection area <b>130</b> has an upper belt button to generate an upper belt chart, a lower belt button to generate a lower belt chart, a chopper roll button to generate a chopper roll chart, a tail pan button to generate a tail pan chart, a roll build button to generate a roll build chart, a turret button to generated a turret chart, and a mandrel button to generate a mandrel chart. By selecting one of these buttons within the graphical representation selection area <b>130</b>, a user may cause a graph and/or table depicting output response data associated with the particular actuator (e.g., the upper belt, the lower belt, etc.).

<figref idref="DRAWINGS">FIG. 6A</figref> depicts exemplary graphs and tables of output response data generated by the emulator with respect to the upper belt actuator. More specifically, <figref idref="DRAWINGS">FIG. 6A</figref> depicts four graphs <b>176</b> and four tables <b>177</b> relating to output response data in machine degrees for a particular mechanical element or actuator. As an example and not a limitation, the graphs <b>176</b> and tables <b>177</b> may correspond to element position, element velocity, element acceleration, and element jerk. The element may be any machine element or actuator (e.g., a machine belt). In one embodiment, the user may zoom or pan the graphs using an input device (e.g., a mouse or a touch screen). Further, in some embodiments the output response data generated by the calculation routine may be exported to a spreadsheet for further analysis.

Referring once again to <figref idref="DRAWINGS">FIG. 4</figref>, the graphical user interface <b>100</b> may include one or more animation buttons <b>122</b>, <b>124</b> that cause an animation of at least one predicted machine operation to be displayed. In the illustrated embodiment, the graphical user interface <b>100</b> includes a “View Single Animation” button <b>122</b> and a “View Comparison Animation” button <b>124</b>. Selection of the “View Single Animation” button <b>122</b> may cause an animation of a machine process corresponding output response data resulting from an emulation using the currently inputted parameters. <figref idref="DRAWINGS">FIG. 7A</figref> depicts a screen shot of an animation of a winder machine process. The animation may depict the movement of the mechanical elements of the machine over a range of machine degrees (e.g., 0 to 360 degrees). The animation may be based on the output response data produced by the calculation routine, and graphics elements associated with each of the mechanical elements and actuators. A graphics element provides a graphical representation of a mechanical element or an actuator within the animation. As an example and not a limitation, the animation may be an Adobe Flash-based executable file that provides continuous single-cycle animation. Other file formats may also be utilized. The animation may provide a visual indication to a user of changes made to the parameters inputted into the graphical user interface <b>100</b>. A user may stop or start the animation by selecting the play/pause button <b>162</b>, jump to a particular point in time of the animation using the scroll bar <b>260</b>, change the speed using speed scroll bar <b>264</b>, select a modeling mode using model mode selection <b>269</b> (e.g., select between a three-dimensionally rendered animation or a two-dimensionally rendered line animation, or select between one or more animations), and zoom in and out using zoom buttons <b>268</b>. Other features may also be provided.

Selection of the “View Comparison Animation” button <b>124</b> may allow a user to select two (or more in some embodiments) previously saved files representing two different output response data sets for a comparison animation wherein two animations are overlaid with respect to one another. <figref idref="DRAWINGS">FIG. 7B</figref> depicts a screen shot of a comparison animation of two animations corresponding to two different output response data sets (e.g., a first machine animation <b>700</b> generated from a first plurality of parameters and a second machine animation <b>710</b> generated from a second plurality of parameters). For example, the output response data for the first machine animation <b>700</b> may have resulted from a first set of parameters, while the output response data for the second machine animation <b>710</b> may have resulted from a second set of parameters that is different from the first set of parameters. A user may then visualize the differences between the two animated machine processes and make adjustments to the parameters accordingly.

The animation file may be created in a variety of ways. <figref idref="DRAWINGS">FIG. 8</figref> depicts a flowchart <b>270</b> of a process to create a Flash-based animation file. At block <b>272</b>, the calculation routine logic <b>43</b> receives a plurality of parameters entered into the graphical user interface <b>100</b> as described above. Using the plurality of parameters, a calculation routine is executed to emulate the machine process and produce output response data at block <b>274</b>. In response to a request for the display of one or more animation files, multiple comma-separated values files are generated at block <b>276</b>. One comma-separated values file may list the geometry parameters entered into the geometry settings form <b>160</b> (i.e., a geometry settings comma-separated values file). Another comma-separated values file may list the output response data generated by the calculation routine in the form of position vs. time output data from one or more actuators (i.e., an output response comma-separated values file). A flash executable file pre-built with graphics elements that represent machine elements (i.e., cylinders, rods, etc.) may then be started and load the data from the comma-separated values files to display a continuous single cycle animation in block <b>278</b>. In the comparison animation, an A set and a B set of comma-separated values files may be created that a Comparison Flash executable file loads into arrays and displays an overlaid output.

In an alternative embodiment, the emulator may generate and present still images representing the output response data based on different points in the emulated process rather than, or in addition to, an animation of the output response data. In this embodiment, a user may selectively view still images of the emulated process at desired points or times during the process. For example, the screen shots of the animations depicted in <figref idref="DRAWINGS">FIGS. 7A and 7B</figref> may be configured as still images rather than animations as described above.

In one embodiment, the emulator is configured to calculate and output programmable logic controller input values based on the parameters inputted into the graphical user interface <b>100</b> that may then be inputted into the programmable logic controller. For example, the emulator may produce a report that lists the programmable logic controller input values for each actuator based on the parameters that the user has entered into the graphical user interface <b>100</b>. In this manner, a programmer or designer may easily enter the programmable logic controller input values generated by the emulator into the programmable logic controller. The emulator may also be configured to receive parameters inputted into the human machine interface from the programmable logic controller <b>28</b>. For example, the graphical user interface <b>100</b> may be displayed within the human machine interface (e.g., the human machine interface <b>20</b> depicted in <figref idref="DRAWINGS">FIG. 2</figref>) so that a user may view an animation based on parameters or values entered into the programmable logic controller <b>28</b>. In this manner, the operator of the machine may view not only the actual operation of the machine based on the parameters or values entered into the human machine interface, but also a detailed animation that may provide information that may not be readily apparent to the operator based on observing the machine alone.

Further, in another embodiment, the emulator may receive the actual output data of the programmable logic controller <b>28</b> (e.g., servo drive data) separate from, or in addition to, the parameters or values entered into the programmable logic controller <b>28</b> via the human machine interface. In this embodiment, the animation file is based on the actual output data (e.g., servo drive data or other drive data) of the programmable logic controller <b>28</b> rather than the output response data generated by the emulator. Therefore, the operator of the machine may view an animation that is based on the actual output data of the programmable logic controller <b>28</b>.

<figref idref="DRAWINGS">FIG. 9</figref> illustrates an embodiment wherein the emulator <b>50</b> is communicatively coupled to the programmable logic controller <b>28</b>, which has machine computer readable medium <b>27</b> that store programmable logic controller code. As an example and not a limitation, the emulator <b>50</b> may be installed within the human machine interface <b>20</b> as depicted in <figref idref="DRAWINGS">FIG. 2</figref>. In this embodiment, a user of the emulator <b>50</b> may enter various parameters into the graphical user interface <b>100</b> displayed by the emulator and then output programmable logic controller values directly into the programmable logic controller <b>28</b>. The programmable logic controller <b>28</b> may then send output signals to the various actuators <b>29</b><i>a</i>-<b>29</b><i>d</i>. Communication between the emulator <b>50</b> and the programmable logic controller <b>28</b> may be effectuated by a variety of means. For example a commercially available object linking and embedding for process control (OPC) software package or dynamic data exchange (DDE) software package may be used to enable communication between the emulator <b>50</b> and the programmable logic controller <b>28</b>. It should be understood that other methods of communication may be utilized, such a custom driver written for communication between the emulator <b>50</b> and the programmable logic controller <b>28</b>, for example.

The emulator and its graphical user interface may also incorporate smart testing such that the emulator may be used as a training tool to train new operators of the machine. <figref idref="DRAWINGS">FIG. 10A</figref> depicts a graphical user interface <b>100</b> that displays a training scenario to the user via a pop-up training scenario message box <b>150</b>. It should be understood that the training scenario may be presented in a manner other than a message box. The training scenario message box <b>150</b> may include text that describes a particular situation relating to the machine and prompts the user to make the appropriate parameter change(s) by inputting the correct parameter(s) into the correct corresponding input field(s). A feedback message (e.g., in a feedback message box) may be presented to the user in response to the inputted parameters. For example, the feedback message may indicate that the user entered to correct parameters, or the feedback message may indicate to the user that he or she is incorrect, and also indicate the correct parameters that the user should have entered in response to the training scenario. In this manner, the emulator may provide real-time feedback based upon the changes made by the user.

<figref idref="DRAWINGS">FIG. 10B</figref> illustrates a video training scenario message box <b>152</b> that includes a video display of an exemplary mechanical process of the machine that presents a question referring to a problem or issue. Similar to the training scenario message box <b>150</b> depicted in <figref idref="DRAWINGS">FIG. 10A</figref>, the video training scenario message box <b>152</b> prompts the user to make parameter changes, and will then provide feedback to the user based on his or her response. In this manner, the machine may be emulated while also displaying real-time feedback to the user.

In some embodiments, if a user does not answer a particular question correctly (either a text-based question or a video question), the emulator may be configured to ask the same question again at a later time during the same or a different training scenario, or it may be configured to ask the question in a different manner. As an example and not a limitation, the emulator may be configured to ask a user a text based question that corresponds to a video question that the user answered incorrectly.

<figref idref="DRAWINGS">FIG. 11</figref> illustrates a system wherein the machine emulator (e.g., emulator module <b>340</b>) is also communicatively coupled to a product model <b>320</b> corresponding to the product manufactured by the machine and a process model <b>330</b> of the overall process used to manufacture the product. The emulator module <b>340</b> may be communicatively coupled to only the product model <b>320</b>, only the process model <b>330</b>, or both.

Linking the emulator module <b>340</b> to the product model <b>320</b> may allow the user to input product parameters as required by the product model and then, based upon the inputted process/equipment settings, the product implications could be displayed to the user within the graphical user interface. Similarly, linking the emulator module <b>340</b> to the process model <b>330</b> may allow the user to input product parameters as required by the process model and then based upon the inputted process/equipment settings, the process implications could be displayed to the user. Like the emulator module <b>340</b>, the product model <b>320</b> and the process model <b>330</b> may be configured as computer readable program code, such as product model computer readable program code and process model computer readable program code, respectively. The emulator module <b>340</b>, the product model <b>320</b> and the process model <b>330</b> may all be stored in a single memory component (i.e., a computer readable medium capable of storing computer readable instructions that are executable by a processor) of a single computer device (e.g., a personal computer, a server, the human machine interface, etc.). In another embodiment, the emulator module <b>340</b>, the product model <b>320</b> and the process model <b>330</b> may be stored on separated memory components of separate computer devices.

Referring now to <figref idref="DRAWINGS">FIG. 12</figref>, a system in which an emulator module <b>340</b> is linked to a product model <b>320</b> is illustrated. The product model may be configured as a mathematical model of a product that is generated in calculation software, such as, but not limited to, MathCAD, MATLAB, Excel, and the like. The product model <b>320</b> (e.g., a MathCAD model or a MATLAB model) may be configured to receive input parameters and calculate predicted product values <b>322</b> (i.e., transform input parameters into predicted product values). The product model <b>320</b> may be linked to the emulator module <b>340</b> such that the product model <b>320</b> receives inputted parameters from the emulator module <b>340</b> rather than from a user (although the product model <b>320</b> may be configured to receive inputted parameters from both the emulator module <b>340</b>, a user, and other sources). In one embodiment, various desired product properties <b>342</b> (e.g., parameters corresponding to input fields <b>101</b>-<b>106</b> illustrated in <figref idref="DRAWINGS">FIG. 4</figref>) may be entered into the emulator module <b>340</b>, as described above. The desired product properties may reflect desired characteristics of the finished product. Although the desired product properties <b>342</b> are shown as broken out into product properties <b>344</b> (e.g., sheet count, sheet length, etc.) and material properties <b>346</b> inputted into one or more material input fields of the graphical user interface (e.g., paper caliper, stretchability, etc.) embodiments are not limited thereto. For example, the machine process properties described above may also be inputted as the desired product properties. Any parameter described above with respect to the finished product and the overall process may be inputted.

After receiving the desired product properties <b>342</b>, the emulator module <b>340</b> may calculate output response data, as described above. The output response data may include input parameters that are then provided to the product model <b>320</b>. In one embodiment, some or all of the desired product properties <b>342</b> are also provided to the product model <b>320</b>. The product model <b>320</b> may then utilize the provided input parameters from the emulator module <b>340</b> to calculate and output various predicted product values. In a wound web material product context, such as a paper towel roll, the various predicted product values <b>322</b> may include, but are not limited to, roll diameter value, perforation strength value, winding tension value, roll compressibility value, embossed depth value, etc. In this manner, a user may make changes to the desired product properties of the product and/or the process of the machine (e.g., actuator parameters, geometry parameters, etc.) using the emulator, and then predict various output properties of the finished product.

In one embodiment, the emulator module <b>340</b> may provide an option that generates a graphical representation of an anticipated product at any point during the process based on the parameters entered into the emulator module <b>340</b> and the parameters of the product model <b>360</b> (as well as the process model <b>360</b>). The graphical representation of the anticipated product may include, but is not limited to, a three-dimensional illustration, a pictorial representation, or a CAD file. The graphical representation of the anticipated product may allow the user to see how the resulting product will look. For example, the emulator module <b>340</b> may be configured to present a user-selectable button that, when selected by a user, displays an illustration of what the finished product will look like. As non-limiting examples, the user may see if the appearance of the rolled product is flat, or if it has an uneven wind, etc. In an exemplary wrapper process, the graphical representation may show how much overlap is present, how well the ends are sealed, how firm or loose the wrapper material is on the roll, etc.

Referring now to <figref idref="DRAWINGS">FIG. 13</figref>, an embodiment in which the machine emulator module <b>340</b> is linked to a process model <b>360</b> is depicted. The process model <b>360</b> may be configured to predict how inputted parameters may affect the overall process of the machine, and to detect potential problems with the process based on the inputted parameters (i.e., transform input parameters into output messages indicative of the overall process of the machine). For example, the process model <b>360</b> may generate a process output message <b>362</b> that indicates to the user that particular inputted parameters may cause a predicted process of the machine to operate in a manner that is harmful to the machine and/or the manufactured product. The process model <b>360</b> may be programmed to recognize problems based on inputted parameters. Regarding machine process issues, a message may be generated in response to a particular combination of inputted parameters that indicates that the inputted parameters may cause the elements of the machine to wear quickly such that the process may be adversely affected over time. Other process output messages may indicate that the particular inputted parameters may cause the machine to operate in a manner that is outside of protocol. Regarding product issues, the process model may be configured to detect how inputted parameters may affect the overall process, and how the process may affect the finished product. For example, product model may indicate that inputted parameters may cause known problems, such as coning, breaking at the incorrect perforation, tail control, etc. The process model <b>360</b> may be programmed empirically, mathematically, or a combination of both.

As stated above with respect to the product model <b>320</b>, the process model <b>360</b> may receive the inputted parameters from the output response data and/or desired product properties <b>342</b> (e.g., parameters corresponding to input fields <b>101</b>-<b>106</b> illustrated in <figref idref="DRAWINGS">FIG. 4</figref>) of the emulator module <b>340</b>. In this manner, a user may make changes to the desired product properties provided to the emulator, and then predict how the desired product properties will affect the process of the machine.

One specific, non-limiting example of a process model linked to an emulator module is the prediction or modeling of how a web material behaves based on different input parameters, such as input parameters corresponding to different machine operations, mechanical elements, actuators, inertias, friction surfaces, and the like. The emulator module in conjunction with a process model may predict how stable the web material is, and how reliable a particular process is, based on changes in process and product parameters, particularly as the line speed of the hybrid winder machine increases. This model may incorporate parameters and predict based on physics how stable the process will be, what speed limitations might be reached, etc. Such web handling modeling may be utilized to develop better machine equipment. For example, in the hybrid winder context, better surface coatings for rollers may be developed, how to add or modify air foils may be determined, how to best change the draws between rolls may be developed, etc.

The emulator module <b>340</b> may be linked to both the product model <b>320</b> and the process model <b>360</b> simultaneously. The functionality of the product model <b>320</b>, the process model <b>360</b>, or both, may be integrated directly into the emulator module <b>340</b>. In one embodiment, the emulator module <b>340</b>, the product model <b>320</b>, and the process model <b>360</b> are all components of the machine (or human machine interface), and may be accessed through the human machine interface. A user may then be able to not only control the machine, but also run simulations and make output predictions using the emulator and product/process model functionality.

Linking the emulator module <b>340</b> with a product model <b>320</b> and a process model <b>360</b> may enable the emulator module <b>340</b> to determine how the product, process, and machine will behave based on user inputted parameters (e.g., material properties, geometries, actuators, etc.) and independently make conclusions about how a particular process will run or react. The emulator module <b>340</b> may utilize output response data from past scenarios based on particular input parameters to predict ideal input parameters based on empirical modeling. In one embodiment, the emulator module <b>340</b> may have a smart mode that predicts parameter values based on past experience, which may ideally provide the most reliable process for a given set of parameters.

The dimensions and values disclosed herein are not to be understood as being strictly limited to the exact numerical values recited. Instead, unless otherwise specified, each such dimension is intended to mean both the recited value and a functionally equivalent range surrounding that value. For example, a dimension disclosed as “40 mm” is intended to mean “about 40 mm.”

Every document cited herein, including any cross referenced or related patent or application, is hereby incorporated herein by reference in its entirety unless expressly excluded or otherwise limited. The citation of any document is not an admission that it is prior art with respect to any invention disclosed or claimed herein or that it alone, or in any combination with any other reference or references, teaches, suggests or discloses any such invention. Further, to the extent that any meaning or definition of a term in this document conflicts with any meaning or definition of the same term in a document incorporated by reference, the meaning or definition assigned to that term in this document shall govern.

While particular embodiments of the present invention have been illustrated and described, it would be understood to those skilled in the art that various other changes and modifications can be made without departing from the spirit and scope of the invention. It is therefore intended to cover in the appended claims all such changes and modifications that are within the scope of this invention.