RELATED APPLICATION DATA

This application claims the benefit of US provisional application ser. no. 62/907,783, filed September 30, 2019, the disclosure of which is incorporated by reference herein.

BACKGROUND AND SUMMARY

This disclosure is directed to a processing line with a model based speed and backlog control system. The control system is configured to control the speed of a machine based upon a desired backlog set point with a real-time calculation of the backlog before the machine as feedback for the control system. The control system eliminates discreet speed levels, which can cause fault-inducing jerky or start-stop operation, and results in smoother speed operation for the processing line. The control system allows the processing line to operate efficiently by automatically balancing the line and machine speeds without interaction from an operator, which frees up an operator for other tasks.

As will be described in greater detail below, the machines in the processing line may be set for their maximum and minimum speeds, and the control system may be set with a desired backlog level. The desired backlog level may be based upon the optimum backlog to ensure proper infeed into a machine and transfer between a conveyor and one or more machines, and may include factors as product weight, and product accumulation levels for a machine. The desired level may also consider the stopping time and amount of product consumed while stopping a machine to ensure enough accumulated product exists to stop the machine in a desired manner and at a desired point in the machine cycle. This can be done to ensure machines start up reliably after the stop. This will often define the minimum amount of product backlog required. The control system is configured to balance backlog levels automatically by adjusting speeds based on current running conditions and a backlog set point. This generally removes operator interaction and balances the processing line for continuous, smooth operation by reducing the starts and stops that would result from less integrated solutions relying only on traditional photo electric eye control systems. This method allows for shorter lengths of conveyor, resulting in less overall space occupied by the processing line.

In one application, the control system utilizes a real time model of the product flow on a conveyor system. The position of every roll or package on the conveyor is determined by the control system along with the accumulation or backlog level. The accumulation level upstream on the conveyor and downstream on the conveyor is used to control the speed of one or more machines. Each machine may then be controlled to run at any speed in its speed range, proportional to the accumulation or backlog levels.

To better control accumulation and backlog level, the control system includes a controller that is configured to target a specific backlog level. In particular, the controller is configured to generate control signals for machines in the processing line based upon a backlog set point with a modeled backlog level providing feedback to the controller. In one aspect, the controller includes a PID control with the desired backlog level as the set-point and the modeled backlog level as the feedback for the PID control. The output of the PID control is configured to control the speed of a machine in the processing line. The control system allows the backlog level to stay close to the backlog set point during steady state operation regardless of the speed of the conveyor or the rate at which product is being sent to the machine.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is an exemplary schematic diagram of the processing line and control system utilizing a model based speed and backlog control.

Fig. 2 is an exemplary schematic diagram of a database of a controller of the systems and data structures associated with the database.

Fig. 3 is an exemplary schematic diagram showing a conveyor system with a backlog for a downstream machine and the range of speed for operating the conveyor.

Fig. 4 is an exemplary schematic diagram showing data acquisition and process flow for the controller of the control system of the processing line.

DETAILED DESCRIPTION Figure 1 shows an exemplary schematic diagram of the processing line and control system 10 utilizing a model based speed and backlog control. The exemplary control system 10 is described as being implemented on a processing line 12 having a conveyor 14 that is adapted and configured to convey product from upstream processing equipment 16 upstream of the conveyor to downstream processing equipment 18 downstream of the conveyor. However, it may be appreciated that the principles of the control system may be employed on other conveyor systems, for instance, an in-feed conveyor for a saw cutting operation or a conveyor disposed before or after an accumulator. For purposes of illustration and not in any limiting sense, in one aspect, the upstream processing equipment 16 may be a saw cutting operation. The saw cutting operation may be adapted and configured to cut logs of convolutely wound web material or ribbons of folded and stacked web material. In another aspect, the product conveyed on the conveyor 14 may be rolls of convolutely wound web material or rectangularly shaped stacks of folded and stacked web material. In another aspect, the downstream processing equipment 18 may be a wrapping station for wrapping a product, for instance, rolls of convolutely wound web material or rectangularly shaped stacks of folded and stacked web material. In another non-limiting example, the processing line 12 may be configured with a wrapping station as upstream processing equipment, and a bundler or a case packer as downstream processing equipment. In another non-limiting example, the processing line 12 may be configured with a bundler as upstream processing equipment 16, and a case packer or pa I letizer as downstream processing equipment 18. In another non-limiting example, the processing line may be configured with a case packer as upstream processing equipment 16, and a palletizer as downstream processing equipment 18. In the exemplary implementation shown in Figures 1-4, the control system 10 includes a product sensor 30 for the conveyor 14. The product sensor 30 may be adapted and configured to generate signals representative of a number of the products moving on the conveyor 14 from the upstream processing equipment 16 past the product sensor to the downstream processing equipment 18. The product sensor 30 may be configured to generate signals representative of a product count and/or position of the product on the conveyor 14. By way of example and not in any limiting sense, the product sensor 30 may be a photoelectric eye, a camera, or an image capture device such as a CCD or CMOS device. In the exemplary implementation shown in Figures 1-4, the control system 10 further includes a conveyor speed sensor 32 for the conveyor. The conveyor speed sensor 32 may be adapted and configured to generate signals representative of a speed of the conveyor 14. The conveyor speed sensor 32 may directly measure the speed of the conveyor 14 through optics or imaging of the conveyor or indirectly through signals developed by encoders or drives associated with motion components of the conveyor drive system.

In the exemplary implementation shown in Figures 1-4, the control system 10 further includes a controller 40 having a processor 42 and memory 44. The memory or a part thereof may be configured as a database 46. The memory 44 and database 46 may be resident on any one or more physical memories that can take the form of a non-transitory computer-readable storage medium. Such memory can be configured to store data structures representative of the profiles described herein as well as data structures representative of the programming instructions described herein. For example, the memory may take the form of RAM within a server and the memory for the database may take the form of a hard drive or the like within the server or accessible by the server. Further still, it should be understood that the database may be optionally distributed across multiple physical memories as a plurality of databases. It should be noted that the system described herein may be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. Programming for the system and/or mobile device may be loaded into memory and executed by the processor to implement the functions discussed herein.

As such, programming may be stored on a computer readable medium, e.g., RAM memory, magnetic or optical drive or diskette and the like. Illustrated are at least one processor coupled to memory. The processor 42 may be coupled to input/output devices, as will be described below. The memory stores instructions and data used by the processor. As is known in the art, the controller is adapted to execute computer programs for performing the functionality described herein. As used herein, the term "program" or "programming" refers to computer program logic utilized to provide the specified functionality. Thus, a program or programming may be implemented in hardware, firmware and/or software. A program or programming may be stored on the memory and executed by the processor. A program or programming may be loaded as part of client applications downloaded via the system.

In the exemplary implementation as shown in Figures 1-4, the processor 42 is coupled to the product sensor 30 and the conveyor speed sensor 32, which provides inputs to the controller 40, and at least one machine drive 50,52 or control system 54 which receives an output signal of the controller. In Fig. 1, the controller 40 is configured to provide output signals to a conveyor drive control 54 for controlling the operation of the conveyor (e.g., its speed, on, off), a saw operation 50 (e.g. saw conveyor lane operation, saw cut cycle time, on, off), and a wrapping station 52 (e.g., infeed belt conveyor speed, on, off). The programming of the controller 40 may include instructions to enable the presentation of several graphic user interfaces and may enable the operator to access several input/output programs associated with the controller, for instance, via a human-machine interface (HMI).

Programming of the controller 40 may also be adapted and configured to process information representative of a backlog set point, a length of a conveyor, a range of backlog levels for upstream and downstream processing equipment, and the measured backlog. The programming of the controller 40 may include instructions to store a plurality of data structures 60 in the memory of the controller of the control system. By way of example, as shown in Figure 2, the data structures 60 may include a plurality of data items associated together as the backlog set point 62 and the product type 64. The data structures may also include a range of backlog levels for upstream and downstream processing equipment 16,18 and a length of the conveyor 14.

Making reference to Figure 3, the programming of the controller 40 may include instructions to determine a backlog measurement for the conveyor based upon the data structures generated using machine signals, sensor signals, conveyor speed signals, product dimensions, and conveyor length. The programming of the controller 40 may include instructions to compare the backlog measurement to the backlog set point to determine a difference in backlog. The programming of the controller 40 may include instructions to generate signals for controlling the processing line based upon the difference in backlog. The programming of the controller 40 may include instructions to generate a signal to change a speed of the conveyor 14 based upon the difference in backlog. In one example, the controller 40 may include instructions to generate a signal to change the speed of the conveyor 14 based on the amount of product modeled on a section of conveyor. For example, if the product sensor senses 30 that a section of the conveyor 14 is full of product, the controller 40 can be programmed with instructions to develop signals to change the speed of the conveyor to match the speed of the machine 52 the conveyor is feeding. Conversely, if the product sensor 30 senses that a section of the conveyor does not have any accumulated product, then the controller 40 can be programmed with instructions to develop signals to increase the speed of the conveyor 14 until the backlog matches the requirements for the machine the conveyor is feeding. The programming of the controller 40 may include instructions to generate a signal to change operation of the upstream processing equipment 16 based upon the difference in backlog. In one example and not in any limiting sense, the programming of the controller 40 may include instructions to generate signals for controlling operation of a saw cutting operation upstream of the conveyor based upon the difference in backlog. The programming of the controller 40 may include instructions to generate a signal to change operation of the downstream processing equipment 18 based upon the difference in backlog. In one example and not in any limiting sense, the programming of the controller 40 may include instructions to generate signals for controlling operation of a wrapping station downstream of the conveyor based upon the difference in backlog. The control signals may be directed to any/all of the machines in the processing line, for instance, as shown in Fig. 1.

The programming of the controller 40 may also include instructions to process information indicative of the product type 64. In one aspect, the programming of the controller 40 may include instructions to process information indicative of whether the product type is a cylindrical roll. The programming of the controller 40 may include instructions to process information indicative of an orientation of the product and/or a dimensional size of the product in the specified orientation. The programming of the controller 40 may include instructions to store a plurality of data structures in the memory that includes data representative of the orientation and/or dimensional size of the product. In one aspect, the dimensional information of the product may be representative of an axial length of the roll. In another aspect, the dimensional information of the product may be representative of a diameter of the roll. In another aspect, the programming of the controller 40 may include instructions to process information indicative of whether the product has a rectilinear or rectangular form. In another aspect, the dimensional information of the product type may be representative of a length of a side of the rectangular form. With this information, the controller 40 may be enabled to generate signals indicative of backlog level on a real time basis which may then be used as a feedback signal for use in the controller to increase or decrease the speed of one or more machines in the processing line. In one aspect, for instance, as shown schematically in Figure 4, the controller 40 may be programmed with a modeled backlog based upon the requirements of the machine which the conveyor is feeding. If the product sensor determines that the real-time backlog does not match the modeled backlog, the upstream machine 16, downstream machine 18, and/or conveyor 14 (e.g, conveyor speed) may be adjusted accordingly. By way of example, and not in any limiting sense, the modeled backlog may correspond or be representative of an array of products on a section of the conveyor adjacent the in-feed of a downstream machine. The array may correspond or be representative of product arranged side-to-side or end-to-end on the conveyor with no gaps between the products. For purposes of illustration, if a section of conveyor adjacent the in-feed of the downstream machine is 10 feet long and the rolls to be processed in the downstream machine are 4 inches long, the array would have a length of 30 elements. The width of the array would depend on the conveyor width. During operation, the product sensor 30 may be configured to sense the location of product on and/or the rate of delivery of product to the section of conveyor adjacent the in-feed of the downstream machine 18 and send corresponding signals to the controller 40. During operation, the conveyor speed sensor 32 may be configured to sense the speed of the conveyor 14 and send corresponding signals to the controller

40. Based upon the product sensor and the conveyor speed signals, and the dimension/orientation information of the product being processed, the controller 40 may be programmed with instructions to compare the rate of shift of the array with the rate of delivery of product to the section of conveyor adjacent the in-feed of the downstream machine 18. Based on differences, the controller 40 may be programmed to adjust the speed(s) of the upstream machine 16, the conveyor 14, and/or the downstream machine 18 accordingly. For example, if the conveyor speed sensor sends signals to the controller that conveyor is moving 100 feet/min, for a four inch product as described above, the array elements would be shifted every 0.2 seconds. The measurements of the rate of delivery of product to the top end of the array may be based on the product sensor 30 or a signal from the upstream machine 16 (e.g., the producing machine). The rate of removal of product from the bottom end of the array may be based on the product sensor 30 or signals from the downstream machine 18. The controller 40 may be enabled to determine that no shift has occurred if the products being delivered to the section of the conveyor adjacent the in-feed of the downstream machine 18 occupy successive elements in the array and otherwise match the modeled backlog. The controller 40 may be enabled to determine that a shift has occurred if the products being delivered to the section of the conveyor adjacent the in- feed of the downstream machine 18 do not occupy successive elements in the array or otherwise do not match the modeled backlog. Once a shift is detected, the programming of the controller 40 may include instructions to compare the real-time backlog rate to the machine and/or conveyor speeds and make adjustments taking into account a desired backlog level (e.g., backlog set point). For example, the downstream machine 18 may send signals to the controller 40 that it is operating in a manner such that a four inch product is being removed from the bottom of the array every 0.5 seconds. The conveyor speed sensor 32 may send signals to the controller 40 that the conveyor is moving at 100 feet/min, that, is the top end of the array is shifting every 0.2 seconds. The controller 40 may compare the removal rate at the downstream machine 18 to the backlog set point, and generate signals to the downstream machine 18 to increase the rate of removal and/or the upstream equipment 16 to slow the delivery of product to the top end of the array. The controller may be programmed to generate multiple signals to the upstream and downstream equipment (e.g., increasing the rate of removal by the downstream equipment and lowering the rate of delivery by the upstream equipment) to minimize drastic operational changes in the system. In cases where generating signals to the upstream and downstream equipment 16,18 does not result in the backlog level reaching the set point as quick as is desired, the controller may also be programmed to change the speed of the conveyor. For example, in a very short conveyor span it may be necessary to transport the product from the upstream machine 16 to the downstream machine 18 more quickly so as to prevent the conveyor from filling up before the downstream machine 18 has had a chance to reach the target speed set by the controller 40. As shown in Fig. 1, the programming of the controller 40 may include instructions to generate signals to change the conveyor speed, and/or the speed of the upstream processing equipment, and/or the speed of the downstream processing equipment in response to the comparison of the real-time modeled backlog level and the backlog set point to allow the real-time backlog level to stay close to the backlog set point during steady state operation regardless of the speed of the conveyor. While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments.