Patent Application
20050182511
1. Field of the Invention
This Invention relates to a high-speed insert machine for inserting flat materials into an open pocket and, more particularly, to a straight line insert machine employed for printed matter such as newspapers.
2. Art Relating to the Invention
Machines for inserting flat materials into an open pocket, especially for use with newspapers, are known (see, for example, U.S. Pat. No. 4,723,770). The '770 patent teaches a straight-line insert machine for introducing inserts into an open jacket which is held in the open pocket carried on a conveyor. Such machines are made up of a number of units or elements which act in a coordinated manner to introduce inserts into an open jacket. A “jacket” is the term used in the publishing industry to refer to newspapers, magazines, books and the like. Typically, insert machines include jacket and insert feeders, a moving conveyor carrying pockets that open and close, a missed insert repair mechanism, a product pick-up unit, and other structures. “Product” is the term used to refer to a jacket with inserts therein.
The known prior art patents and publications for insert machines normally do not show any “control system” at all for controlling all the elements and operations of an entire insert machine. Even in commercial prior art insert machines, the control system, if any, has conventionally been all-mechanical or electromechanical (such as relay-driven). There is no known prior art for an all-electronic control system, including computers, for an insert machine of the type described in the present invention.
In a conventional prior art insert machine, there are many “pockets” on a moving pocket conveyor, which forms a continuous element which is driven by a motor. Generally, there are two types of conveyors, straight line and carousel. A plurality of pockets are mounted on the conveyor and move with the conveyor. Each pocket usually comprises two walls which are movable with respect to each other, one stationary and one fixed. Generally, there are two styles of pockets, one which opens only from the top and another which opens both from the top and from the bottom. The former are referred to as top opening pockets and the latter are referred to as bottom opening pockets.
The feeders are positioned in close proximity to the conveyor and feed jackets or inserts (flat material), into the open pocket as the open pocket passes under the feeder. The pockets employ suction and lap grippers to open the jacket once it is in the pocket. A jacket feeder transfers jackets into the open pocket while a plurality of insert/jacket feeders transport inserts into the open jacket as the pocket with the open jacket passes underneath the feeder. In a preferred embodiment, the feeder of the present invention may operate either as a jacket feeder or an insert/jacket feeder.
A missed insert repair mechanism determines when an insert was not fed into the open jacket and corrects for the non feed.
The pick-up unit is also positioned in close proximity with the pocket conveyor for removing the product from the pockets after the insert has been introduced into the jacket. A gripper conveyor transports the product from the pick-up unit to an infeed device of a bundler or stacker.
As is known to those of skill in the art, each one of the elements is independently powered by an electric motor.
There is a constant need for improving insert machines to decrease the cost of production and improve the efficiency of their operation. This invention accomplishes these goals.
A new insert machine has now been developed which increases the speed of operation of the various elements of the machine, simplifies the overall operation of the machine, and decreases the manufacturing cost of the machine.
In order to accomplish this, the machine of the present Invention employs a unique all-electronic control system wherein the individual elements of the machine each are controlled by electronic network controllers. A central control computer sends and receives messages to and from the network controllers by means of a bus. The messages are addressed to the network controllers and provide activation and deactivation of selected elements at selected times. The individual network controllers read the address of each message and thereby know which messages to read and which messages to ignore.
Broadly, the invention relates to an insert machine, comprising:
More particularly, the control system for the insert machine of the present Invention can be defined as comprising:
Suitably, the insert machine is a machine for inserting flat materials into folded items, e.g. newspapers.
Preferably, the messages generated by the control computer are generated in a protocol so as to permit message differentiation and soft addressing of the network controllers, whereby some of the messages are broadcast messages that activate all of the network controllers at a given time, and others of the messages are individual messages that activate only certain ones of the network controllers at a given time. More preferably, the protocol is configured such that a single bit in each message enables each controller to determine if a message is a broadcast message or an individual message.
Preferably, at least one network controller is connected to a quadrature encoder for receiving and processing signals from the encoder and for generating timing signals based on rotation of the encoder, the timing signals being communicated to the control computer and other network controllers to determine the exact physical position for all parts of the machine at a given time, and wherein the timing signals are dynamically changeable in real time, based on machine states, user inputs or both, and in response to messages received from the control computer.
Preferably, the control computer runs under the control of a multi-threaded control program.
Preferably, the control computer is coupled to a display computer for providing a graphical user interface.
Preferably, each network controller runs under the control of either a single-threaded program or a multi-threaded program.
Preferably, the bus comprises a controller area network (CAN) bus compliant with the ISO 11898 and 11519 protocols.
The electronic control system for controlling the operations of a machine for automatically inserting flat materials into folded items in accordance with the present Invention can also be defined as comprising:
The electronic control system for controlling the operations of a machine for automatically inserting flat materials into folded items in accordance with the present Invention can also be defined as comprising:
Furthermore, the electronic control system for controlling the operations of a machine for automatically inserting flat materials into folded items, comprising:
Furthermore, improvements have been discovered for the feeder. Some of the improvements relate to the vacuum means for use in the feeder, and, more specifically, to the vacuum control system and the sucker bar arrangement.
The improvement relates to the vacuum control system and can be defined as comprising:
Preferably, the sensor/encoder comprises a slave encoder coupled to a feeder and to a master encoder for generating timing signals as the second area moves.
In the vacuum system, the first area comprises a tray and the second area comprises a rotating drum rotating at a variable speed.
In the vacuum system, the servo drive includes a servo control and a memory storing data representative of (a) a plurality of speeds of rotation of the drum, and (b) predetermined vacuum and air start and stop times for each speed, each time corresponding to an angular movement of a point on the drum relative to a fixed reference point for each speed. The vacuum and air points are changed with changing drum speeds to optimize the feeding function. The angular position of the drum controls the vacuum and air start and stop times.
The vacuum system is configured such that the vacuum is turned on sooner when the drum speed increases, thus optimizing the feeding function.
The improved vacuum system can also be defined as a method for controlling a vacuum at a variable rate corresponding to a variable rotational speed of a rotating drum, comprising the steps of:
Preferably, the steps of calculating, determining, starting and stopping are performed by a servo drive under software control.
Preferably, data representative of the first and second angular displacements are stored in a memory in a servo drive, and data representative of the vacuum start and stop times are stored in the memory for a plurality of rotational speeds of the drum. The functions for determining air and vacuum times are stored for a plurality of rotational speeds of the drum.
Other improvements to the vacuum means relates to the sucker bar arrangement of the feeders. These improvements to the sucker bar are suitably defined with respect to a conventional vacuum device for a feeder of flat material to a moving element wherein said feeder has a tray for holding said flat material, said vacuum device separating the flat-material from the tray and a gripper drum for gripping and transporting the separated flat material to the moving element, the improved sucker bar arrangement of the present Invention comprising:
Preferably, the sucker bar arrangement has an air inlet in said manifold.
Alternatively, instead of a vacuum manifold, a set of stationary valves may be used for both vacuum and air.
Preferably, said pivot shaft is easily removable from said feeder, and more preferably, said pivoting shaft has a fixed pivoting angle.
Another improvement in the feeders has been found in the tray assembly for each of the feeders which improves the feeder's overall operation. More specifically, an improved tray assembly for a feeder of flat material to a moving element wherein said feeder has a tray assembly for holding a plurality of flat material, said tray assembly having a bottom wall on which said flat material rest and a front wall which abuts a side of said flat material, a vacuum device for separating the flat material from the tray assembly and a gripper drum for gripping and transporting the separated flat material between the bottom wall and the front wall to the moving element, the improved tray assembly comprising:
Preferably, said angle, with the horizontal is about 11E.
More preferably, said front wall of the tray assembly vibrates forward and backward to help align said flat material in said tray assembly.
Preferably, the angle between said bottom wall and said front wall is substantially perpendicular.
Preferably, a back wall of the tray assembly is movably fixed to the frame. It can move backward and forward to accommodate different sized products.
Yet another improvement in the feeder relates to the drive means for the feeder drum. Specifically, the improved drive means is a frameless motor directly driving the shaft of the feeder drum. Such an arrangement eliminates belts, gears, line shaft and associated drives. As such, it reduces cost, reduces maintenance and improves efficiency of the feeder.
More specifically, this improved drive means for the feeder can be defined as an improved drive motor for a gripper drum of a feeder of flat material to a moving element wherein said feeder has a tray assembly for holding flat material, a vacuum device for separating said flat material from said tray assembly, and a gripper drum for gripping and transporting a separated flat material to the moving element, said improved drive motor comprising:
Suitably, said winding or stator is concentric with said shaft of said gripper drum and said rotor is concentric with said shaft of said gripper drum.
Improvements in a pocket have also been discovered. These improvements relate to the physical design of the pocket and to both top opening and bottom opening pockets.
The improved pocket design includes ridges along the bottom of the pocket to help hold the jacket in a top opening pocket, a square pocket bottom for a top opening pocket, an on-the-fly adjustable pocket gripper for both top and bottom opening pocket, and a pocket latch for a top opening pocket.
The improved pocket with ridges can be defined as an improved top opening pocket for an insert machine wherein said machine has a conveyor with a plurality of pockets attached to said conveyor and feeders positioned along said conveyor for feeding flat material into a moving open pocket, and improved pocket comprising:
Preferably, said ridges extend along the entire length of said bottom wall. More preferably, there are three ridges. Each of said ridges are formed by a line of bumps in said bottom wall.
The squared pocket of the present Invention can be defined as an improved top opening pocket for an insert machine wherein said machine has a conveyor with a plurality of pockets attached to said conveyor and feeders positioned along said conveyor for feeding flat material into a moving open pocket, the improved pocket comprising:
Preferably, said bottom wall is integral with said leading wall and said trailing wall can pivot with respect to said bottom wall.
More preferably, said leading wall is integral with said conveyor and said trailing wall moves relative to said conveyor.
The pocket latch of the present Invention provides for an improved top opening pocket for an insert machine wherein said machine has an endless conveyor with a plurality of pockets attached to said conveyor and feeders positioned along said conveyor for feeding flat material into an opening moving pocket and said pocket returns inverted, the improvement comprising:
The pocket latch improvement of the Invention is also used for improved product repair functions. The first position of the latch allows the pocket to close fully.
The adjustable pocket gripper of the present Invention when employed with the pocket results in an improved pocket for an insert machine wherein said machine has a conveyor with a plurality of pockets attached to said conveyor feeders positioned along said conveyor for feeding flat material into a moving open pocket and said pocket having a leading wall, a trailing wall and a bottom wall, said improvement comprising:
Preferably, said moving means comprises:
Preferably, said car is spring biased in said other direction.
An improved gripper device for flat material has also been discovered wherein said device holds flat material in a vertical orientation between two arms, said device having a spring means for biasing said arms in a closed position, one arm being fixed and the other arm being movable between an open and closed position, the improvement comprising:
These and other aspects of the present Invention may be more fully understood by reference to one or more of the following drawings.
Each one of the individual elements, i.e. jacket feeder 10, conveyor 12, insert/jacket feeder 16, product pick-up 18, and bundler 20, employ individual motors and a network controller which control the operation of the unit. As shown in
As shown in
In feeder 10, the jackets are placed such that their spine is against front wall 34.
Grippers 41 attach to an insert which has been separated from tray assembly 30 by the sucker bar arrangement and then transport the insert to an open pocket.
Any conventional frameless motor can be used in the feeders of the present Invention.
Conventional rotary encoders are employed with motor 43 and are connected to the network controller for the feeder so as to determine the speed at which motor 43 is operating. Master and slave encoders may both be employed.
The pivot angle is preferably fixed but may also be adjustable. The short stroke of the cups allows for decreased response time and increased speed. The movement, vacuum and air is coordinated with the movement and operation of gripper 41 to facilitate the movement of flat material from tray assembly hopper 30 to open pocket 14.
Also, as shown in
The purpose of ridge 86 on bottom wall 82 is to help catch and maintain the position of the spine of the jacket which has been introduced into pocket 14. As will be appreciated, ridges 86 help maintain the position of the spine of the jacket which has been introduced into pocket 14 by jacket feeder 10.
The operation of the adjustable gripper in
The missed insert repair system of the present Invention in conjunction with pocket latch will now be described. A conventional sensor is used to determine when there is a failure to insert flat material into an open jacket. This sensor detects when an insert has not been picked up by the feed drum or when there is a jam of inserts in the feed drum.
If the sensor detects either a jam in the feed drum or a missed insert in the feed drum, control computer 22 is notified and instructs all downstream insert feeds not to feed inserts into the incomplete pocket. The pocket is incomplete because one of the inserts was not fed into the pocket. The incomplete pocket remains open during its continued travel to the product pick-up unit. At the product pick-up unit, the incomplete pocket remains open. Because the incomplete pocket is open, the gripper of product pick-up unit cannot pick-up the product from pocket. Thus, the contents of the incomplete pocket remain in the pocket. Trigger 110 is integral with the frame of the machine, and positioned downstream of the product pick-up point. Control computer 22 instructs trigger 110 to activate latch 118 which is part of the pocket. Latch 118 causes the pocket to close after the product pick-up point and maintains the pocket in a closed position throughout the rest of its travel on the conveyor. The closed pocket continues on the conveyor until it has completed one complete cycle and arrives back at the feeder where the non-feed took place. At that point, latch 118 is reactivated so that the pocket opens and the missed insert can be fed into the pocket thereby correcting the error. Normally, the pocket is in an upside down and open position on its return trip from the pick-up unit to jacket feeder, to insure that the pocket is empty.
Preferably, each pocket is always open as it moves into position under a feeder. A decision on whether or not to feed an item into a particular pocket depends upon knowing what was previously fed into that pocket.
Vacuum Control
Another feature of the present invention is an electronic vacuum control system that provides a variable vacuum control for use in the feeder operations described previously. A block diagram of one embodiment of the vacuum control system is shown in
A feature of the invention is that the drum does not always rotate at a constant angular velocity. For example, in the event of a misfeed or other handling problem, a control system (discussed below) is programmed to speed up or slow down the entire machine, including the drum, or make other adjustments. Thus, the timing and duration of the vacuum and air flows must be adjusted accordingly.
An electronic control system for accomplishing this is shown in
The drum encoder 200 is shown in more detail in
Alternatively, a separate drum speed sensor/encoder 204 may be provided to generate continuous (or rapidly periodic) signals to the controller representative of the rotational speed of the drum, and a separate drum position sensor/encoder 202 may be provided to generate continuous (or rapidly periodic) signals to the controller representative of the angular position of the drum.
The servo controller includes a servo control circuit board and a drive with a memory (not shown) that stores data (such as in a look-up table) representing optimal, predetermined starting, ending and duration times for the vacuum and air for a plurality of drum speeds. In the event the servo controller, monitoring signals from the drum speed sensor/encoder, detects a change in the rotational speed of the drum, the network controller automatically searches the data to locate the appropriate data entry for the new speed. Associated with that data entry are new vacuum and air timing (starting and ending), and vacuum and air duration, values for the new speed. The servo controller then automatically alters the timing of the vacuum signals and air signals sent to the vacuum and air pump controls accordingly. For example, if the drum has slowed by 10 percent, there will be an entry in the look-up table “telling” the servo controller to delay the starting and stopping of the vacuum and air by a certain time, and to change the duration of the vacuum and air flows, so as to compensate for the change in drum speed. The look-up table for the vacuum control can be pictured as follows:
where:
θ = reference angle for start of vacuum (fixed)
β = reference angle for end of vacuum (fixed)
Δθ = angle from reference to start vacuum
Δβ = angle from reference to stop vacuum
An analogous table is also provided for the air control. In this way, accurate transfer of the inserts to the drum is maintained, and the through-put of the entire machine is optimized.
Overall Electronic Control System
Another important feature of the present invention is an all-electronic control system for automatically controlling the individual elements and operations of all components of the insert machine. A block diagram of one embodiment of this control system is shown in
As seen in
In a preferred embodiment, there is also a second computer, namely display computer 23, housed in a dual computer chassis 26 and coupled to control computer 22 via an ethernet link 290. Preferably, display computer 23 is also a conventional personal computer with a Pentium or later class processor running a conventional operating system and a plurality of proprietary and commercially available application programs.
In a preferred embodiment, the display computer provides a graphical user interface (GUI) for an operator to run the entire machine. For example, an operator can graphically set up the parameters for a machine “run”, such as insert type and size, and run the entire machine.
The display computer (or user interface computer) 23 also has a connection to an external network that can be used to download production planning information to the system. The display computer performs some processing on information, and then sends it to the control computer, which performs additional processing on the information. The information is used, for example, to determine what inserts are put into a package, and what is done with the package (for example, whether to send the package to an optional external bundler or stacker).
Control computer 22 controls the overall operations of the machine, and display computer 23 provides the graphical user interface (GUI) to the user or operator. An uninterruptible power supply (UPS) 25 provides standard AC power to both computers. The UPS provides a status signal to the computers to allow them to automatically shut themselves off in the event that power is lost Display computer 23 has conventional peripherals such a keyboard 280, display screen 270 and a mouse 260, and is configured to communicate with an external network 240 and a network printer 250, and can connect to the Internet via a phone line 230 or through a local area network (not shown), which may be located at a customers site. In normal operation, control computer 22 does not have a display or other user interface, but has direct connections to controllers and other machine components and an auxiliary connection for optional connection to external machines such as bundlers or stackers.
In another feature of the invention, the control computer 22 is connected to a plurality of network controllers (“NC”), such as machine network controller 300 (
Control computer 22 runs a main inserter control application (MICA) (discussed in more detail below), which is a proprietary program and preferably running under a commercially available operating system. The application runs in “soft” real time. The system is designed to provide control messages in a rapid and timely manner to the network controllers. For example, the control computer tells the machine what pocket to select for use at a particular time. Control messages sent over the CAN bus use standard CAN format, but the message content and bit definitions of the CAN messages are based on a proprietary protocol, discussed in more detail below.
Each network controller is a custom-designed microprocessor or microcontroller, preferably based on the Motorola 68000 family, and operating under software control. Each network controller runs a proprietary program, specific to each controller, written in the “C” language, with no operating system. A variety of network controllers may be employed. In this embodiment, the following network controllers are included: machine network controller 300 (
Each network controller has a plurality of inputs for receiving electrical signals from sensors such as air pressure sensor 310 (
Each network controller is also preferably equipped with a memory (preferably a flash memory) that stores the program and setup data for that controller. New programs may be downloaded to selected network controllers. Software for all the network controllers resides on the control computer. The display computer can download software to the control computer. An advantage of this is to permit automated upgrades. The display computer is also configured to receive software updates that may be downloaded under remote control, such as over a customer network or the Internet.
Operation
Generally speaking, in operation, each network controller controls all input and output for the control of specific machine elements and operations taking place within a specific operational group or functional area of the machine, such as the vacuum control system, whereas the central control computer 22 controls the activation and deactivation of all network controllers by way of control messages, as well as the activation and deactivation of selected individual devices such a specific pockets. Using this architecture, which is a hybrid central/distributed architecture, the efficient real-time electronic control of all machine operations is achieved, which is a significant improvement over the prior art in that, for one thing, it reduces overall system cost.
The overall control system is based on the logical tracking of the contents of a pocket and what actions need be performed for a particular pocket. The control system logically references individual pockets until the finished product (newspaper plus inserts) leaves the machine. A typical pocket cycle will be described in more detail hereafter.
The control computer 22 is configured to send two different types of control messages to the network controllers and to other machine elements. One type is a “broadcast” message that is intended for all network controllers in the machine. The other type is an “individual” message that is intended for only one or a few network controllers or individual or local devices. In a feature of the invention, both types of messages can be sent over the same CAN bus. Each network controller “knows” whether an individual message is intended for it by reason of a unique protocol (described below) that is used for the messages. More particularly, a special addressing scheme is used whereby a single bit in the message is used to designate the specific network controller “targeted” by a given individual message.
The overall architecture of the control system of the invention permits hybrid central/distributed machine processing, with a central control computer 22 coupled to a plurality of network controllers via a CAN bus 24. In this embodiment (see
Each network controller receives input signals from a plurality of sensors, detectors, switches and encoders, such as a vacuum sensor 297, air pressure sensor 310, drum position encoders 200 and 201 and miss/jam detectors. Each network controller also provides output control signals to a plurality of solenoids, valves, servo-amplifiers and other control devices, such as air blast solenoid 320, vacuum pump control 67, pocket cleanout air control 71 and motor controller 350. The network controllers, sensors, solenoids and control devices are preferably powered, for example, by a DC power supply 298 over a power bus 299.
One network controller, specifically the machine network controller 300 (
Regarding the control messages, part of each message itself carries the address of a specific network controller or other device. Only a limited number of messages need be sent at a given time. This reduces the total number of messages required to operate the machine, and reduces the data transfer requirement on the bus. Several messages per pocket are sent to each feeder. The messages need to arrive at the feeders at different times.
In a feature of the Invention, the invention uses “soft addressing” to differentiate messages between individual and broadcast messages. This protocol permits the optimization of the utilization of bits in a CAN bus message. This reduces the number of messages required because more data may be provided in a particular message.
The protocol used for the control messages sent over the CAN bus is unique in several ways. First, all messages are received by all devices on the network. Based on a single bit in the message, each device determines if the message is a broadcast message or an individual message. Second, a message encodes either command information, which is intended to cause some activity at the receiving device, or status information, that indicates a condition or state. Third, some messages require the receiving device to send an acknowledgment message while others do not. Fourth, in broadcast messages, a particular bit field is used for the “Command,” which specifies the action to be taken by the receiving device. Other bit fields may hold additional information for the receiving device. Fifth, depending on the job of an individual device, it may or may not perform any action in response to a broadcast message. Sixth, in an individual message, the same bit field used for the command in a broadcast message contains an address of the device, the recipient of the message. Other bit fields may hold additional information for the receiving device. Finally, individual messages are intended to cause an action by a single receiving device. However, is possible for other devices to “eavesdrop” on the messages. This capability is used, for example, to allow the control computer to “know” that a “stop” message has been sent from a feeder control network controller to the machine network controller so the control computer can cause the state to be displayed.
Machine cycling speed is calculated by an algorithm in a network controller, specifically the one that is connected to the encoder (machine/timing network controller 300, in
There is also a commercially available annunciator 295 on the system that consists of an array of LEDs that can be lighted to display both textual and graphic information. The information can be displayed in various fonts, sizes and colors.
All messages are generated by one or more proprietary software application programs running in the display computer, the control computer or both. This application has multilingual capability, and generates message strings in the appropriate language. These messages are then sent to the visual annunciator.
The annunciator can be connected to the system in several ways. First, a serial connection to the control computer can be used. Text or graphic messages are sent either from the display computer or from the control computer. If the annunciator is connected to the control computer, then text or graphic messages are sent from the display computer to the control computer. The program in the control computer embeds the received message information into a message that is sent to the annunciator over a serial port. Multiple annunciators can be connected either to the control computer or to the display computer using either separate Com ports or a single Com port as a Multi-drop (RS—485) serial interface. Multiple annunciators can be addressed individually, and can display either the same or different information. One or more annunciators can be connected to the system via an Ethernet connection, using TCP/IP. The annunciators can be connected to either the control computer through a network port, or to the display through a network port. One or more annunciators can be connected on the same Ethernet network that connects the display computer and the control computer.
In another feature of the invention, considerable redundancy is provided. For example, if the control computer or display computer fails, the machine can continue to operate to complete a “run” at an acceptable speed.
Yet another feature of the invention is that the timing signals can dynamically change in real time between actions. Specifically, the system permits the dynamic changing of the timing of execution of the control messages. For example, if a reject gate device normally turns on at timing message 2 and turns off at timing message 10, the network controller can be told to change the timing so that the device turns on at message 0 and off at message 14. In addition, the speed of the entire machine may be dynamically adjusted in real time to optimize the throughput for the entire machine, based on measured insert performance. For example, speed may be adjusted if the line voltage changes or if the pockets or feeders are not operating correctly.
Another feature of the invention is that the presence of a product in a individual pocket may be detected using a sensor array such as a photocell and two reflectors (not shown) in a pocket. This permits the active diagnosis of machine operations in real time. For example, the system can automatically deactivate a specific pocket in real time if there is a misfeed or some other problem with that particular pocket. Remote diagnosis over a telephone line or over the Internet is also supported.
A more detailed description of specific components and features of one embodiment of the invention is provided below.
Machine Operating Modes
Normal (Full Functional) Mode
In this mode, all features and functions are available. The machine operator uses the software graphical User Interface to define and assign inserts, create packets, and define zones. This information is either entered manually or downloaded from a planning system. A Main Inserter Control Application (MICA), running on the Control Computer, sends messages to Network Controllers, distributed around the machine, to perform required functions. The Network Controllers interface directly with sensors and electrical actuators to actually control the machine. The machine runs the zones, putting inserts into jackets. Functions such as Repair, Backup, Stop on Multiple Miss, etc. will be selected by the operator. Overall Machine speed is controlled from the interface.
No Display Computer Mode (Redundancy Feature)
This is the mode that is in effect if the display computer or the software system fails, but the Control Computer and the Main Inserter Control Application is still functioning. If the display computer or WinLincs fails in the middle of a zone, the Main Inserter Control Application will use the information that it already has to finish the zone. If the machine is not running a zone, or the zone completes, the machine can then be operated from the Feeder Control Panels. The operator will put the Feeders that should be feeding into Auto mode. The Jacket Feeder is put in Off mode. When the Jacket Feeder is put in On or Auto mode, it will start feeding. As the jackets reach the downstream feeders, they will begin feeding. The machine will not feed into unopened jackets or empty pockets. The Run, Stop and Jog buttons, as well as the Emergency stop circuits will be functional. The machine will run at the default speed.
No Control Computer Mode (“Manual Mode”)
This mode will be in effect if the Control Computer fails. In this mode, the Machine Network Controller will detect the loss of communications with the Control Computer, and send a message to the other Network Controllers indicating the mode change. The machine will run at default speed. Feeders that are in “AUTO” mode will switch to “ON” mode. All feeders will feed unless they are placed in “OFF” mode. It will be the operator's responsibility to turn feeders “ON” as a jacket reaches them. There will be no repair, skew detect, reject or other similar functions.
Feeder Control System
Each feeder on the machine has a Network Controller. Typically, there are even feeders and odd feeders, with two feeders in a so called two-box frame that has two NCs. The NCs are powered from a DC supply in the two-box. Each feeder shares a motor controller with the other feeder in the two-box. There is a CAN Bus connection to each NC. There is a main machine encoder bus connection to each NC. Each NC is directly connected to the motor controller via discrete signal lines. Each feeder also has hardware for detecting misses, multiple feeds, jams, and other errors.
Network Controller Board
The Network Controller acts as the central point for all data flow and connections within the Feeder. It processes inputs from various detectors, the Motor Controller, User Interface Panels, Emergency Stops, the Cover Interlocks, and the Control Computer via the CAN Bus. It sends control outputs to the Status Indicator Lamps, Air Table solenoid, and Motor Controller. It sends data to the User Interface Panel and the Control Computer via the CAN Bus.
One of the Network Controllers in a two box has a serial connection to the Motor Controller. Through this connection, it has the ability to exchange setup data with the Motor Controller. There is a two-wire (differential) connection to the CAN Bus. An output is provided for the Air Table solenoid. Outputs are also provided for the Status Indicator Lamps. The board receives inputs from the Miss/Multiple Detector circuit, the Floater Detector, the Low Level Detector, the Miss/Jam Detector, two Emergency Stop switches, and the Cover Interlock switch.
WinLincs
WinLincs is a proprietary graphical user interface (GUI) program running under a commercial operating system. It provides the primary user interface to the machine. It provides the operator with the ability to create and runs zones, and to monitor production statistic and machine performance. It provides a variety of diagnostic and setup information and controls.
Main Inserter Control Application (MICA)-Architecture
MICA is a multi-threaded software application. There are six running threads, each handling specific functions. The threads are the CAN Receive Thread, CAN Send Thread, TCP Control Thread, Control Thread, Operation (Oper) Thread, and Download Thread. In addition, there is a Main Thread, which is responsible for starting the other threads and initializing the system. The threads functions independently and asynchronously.
Structures
There are several structures that are key to the functioning of The Main Inserter Control Application.
Position Array and Position Control Object
The Position Array is a large array, each element having two structures that correspond to a pocket and to a gripper. Pointers in these structures provide a “handle” for accessing the information in the structures. The pointers also provide the mapping of the array elements to the physical pockets and grippers. The Position Control Object provides a mechanism to indirectly access the Position Array using the pointers, based on a position or location on the machine. There is a correspondence between each of the elements of the array and a physical location on the machine. The structures in an array element contain information pertaining to the product that is in the pocket or gripper at a location. This information consists of general information, such as the zone that the product belongs to, data necessary to produce the product, such as the required inserts, status information, such as the inserts that have been inserted up to that instant, and disposition information, such as if the product will be Rejected or Repaired. It also contains the physical number of the pocket and gripper that will contain the product. The array is large enough to handle all the pockets and grippers from the longest machine.
Element 800 of the array corresponds to a location slightly beyond the Pickup area. This location is the same for all machines. All access to the array elements is indirect, via pointers. As the Inserter cycles, and product moves through the machine, the pointers to the array are shifted to imitate the shifting of data, without having to copy the data from one element to the next. At about the time that the product is physically transferred from the pocket to a gripper, the data in the pocket portion of the array is copied to the gripper portion. It is necessary to provide for separate storage in each array element for pocket and gripper information primarily to allow for Repair, particularly because the number of pockets and grippers varies from machine to machine.
There are several other key mechanisms that allow the Position Array to function properly. First is Synchronization. Because it cannot be predicted if a First Gripper detection or First Pocket detection will be occur first, the software was written to handle either case. As soon as both the First Pocket and First Gripper are detected, the application correctly determines the correspondence between the number of the physical pocket, and the number of the physical gripper that will remove the product from that pocket. The second key mechanism is the Position Shifter functionality.
This function performs several tasks. The first task happens on a pocket that reaches the Pickup area of the Inserter, and is performed on the array element corresponding to the pocket. The function determines if the product in the pocket will be repaired. Based on the determination, it copies appropriate data from the pocket section of the element to the gripper section, and clears other data. For example, if a product will be repaired, the information on the inserts that have already been fed would not be cleared. If the product is not being repaired, all data would be copied to the gripper area, and the pocket portion would be reinitialized.
The second task is to shift the pointers in the elements in the array. This mimics the effect of shifting all the data from one element to the next, but is more efficient The data is always accessed indirectly, so it is not necessary to actually shift the data.
The third task is handling the rollover of the pockets and grippers. The physical pockets and grippers on the Inserter are in loops, so, just as they cycle back around through the Inserter, the corresponding pointers must re-circulate.
The fourth task is resetting the correspondence of the pockets and grippers. Because the number of pockets and grippers varies from Inserter to Inserter, and the number of grippers may be either greater or less than the number of pockets (or, in rare cases, the same), a calculation must be performed each cycle to determine the number of the gripper that will receive the product from a particular pocket.
Task Table—The Task Table contains pointers to the software tasks that are performed at various times throughout the pocket cycle. It is described elsewhere.
WinLincs Data—Data being sent bi-directionally between WinLincs and the Main Inserter Control Application is stored in various structures. Each structure is specific to the data that it contains. The structures are passed between the two systems in message that is a union of the various structures.
Zone Data—Information for each zone being produced is stored in Zone Data structures. This data is sent from WinLincs, and is used by the Main Inserter Control Application to determine how to produce products. Types of information include the specific inserts required for the product, how many to produce, and delivery information such as the number of pieces in each bundle. In addition to information that is common to all products in the zone, piece specific information, such as an address, may also be included.
Machine Configuration
The Machine Configuration structure contains information that describes the particular Inserter. For example, it would contain the number of feeders and deliveries on the Inserter. At system startup, this information is retrieved from a file stored on a drive in the Control Computer. A user can change this information through the WinLincs 4 user interface. If a change occurs, the new configuration it is sent from WinLincs 4 to the MICA. It is then immediately stored in the file on the disk. This allows the MICA to start up with a valid configuration for the Inserter even if WinLincs 4 fails to start for some unknown reason.
Tasks
The following is a partial list of tasks that would be operational on a typical Inserter. The exact number and type of tasks varies with the Inserter's configuration. There are two types of tasks. Real Device tasks relate to physical devices on the Inserter, for example, a Reject mechanism. Virtual Device tasks relate to pure software functions that are not specifically associated with any devices on the machine. An example would be the Pocket Loader, which writes information into the Position Array. There are also tasks for controlling Feeders and Deliveries, and for keeping track of Network Controllers.
Startup—At startup, all required memory is allocated, all variables and structures and classes initialized, and all threads started. The inserter configuration information is retrieved from a file, and the Task Table is loaded. Note that the configuration information determines the exact contents of the Task Table. After appropriate time delays, the TCP and CAN communications are started. Status information is collected from the Network Controllers and sent to WinLincs 4.
The Inserter is cycled, and eventually, the First Gripper and the First Pocket will be detected, and this information sent to MICA. After both have been detected, the Position Array is initialized and MICA begins processing Timing messages received on the CAN Bus, using the Task Table to determine which tasks to perform.
As the Inserter is cycled, MICA send messages on the CAN Bus to Network Controllers to control various functions. Examples include requesting the Reject mechanism to operate, turning a feeder On, or requesting a feeder to feed a piece. MICA also receives CAN messages from Network Controllers that provide status information about the Inserter and its operation. Examples would include detecting that an Emergency Stop button was pressed, receiving notification of a successful feed from a feeder, or a message indicating a delivery device had been turned Off. MICA will properly act on this information, and if appropriate, pass the information on to WinLincs 4 so that it can be displayed to the user. A key feature is that status data indicating if a Feeder successfully fed a piece is sent to MICA and stored in a timely enough manner that the data may be used to control the feeding of the next Feeder on the Inserter. MICA also receives configuration and control messages from WinLincs 4. Examples would include changing the configuration of the Deliveries, a request to change the Inserter's speed, and a request to initiate inserting and begin producing a zone.
Generally, MICA sends only a single control message on the CAN Bus to a Network Controller to cause a specific control action to occur. This would be sent only once per pocket cycle, and would occur before the control action is required. It is not time critical. Prior to the control message, information would be sent from MICA to the Network Controller via the CAN Bus telling the Network Controller how to handle the control message. The Network Controller would initiate the control action at the required time, and terminate the action, if required, at the appropriate time. For example, MICA would send a Network Controller the Start time and End time for control of a Reject mechanism. Some time before the Start time, Mica would send a control message to the Network Controller, requesting it to actuate the Reject mechanism. When the Network Controller received the Timing message on the CAN Bus corresponding to the Start time, it would control an output circuit connected to the Reject mechanism. When the Timing message corresponding to the End time was received, the Network Controller would deactivate the output to the Reject mechanism. In some cases, the control message from MICA may contain information telling the Network Controller to start operation of a device at the Start time, but not to end operation of the device at the normal End time. This causes the device to remain actuated for the next pocket or gripper. During this subsequent time, another control message from MICA would be sent, requesting either to terminating the control at the normal End time or continuation into the next pocket. This allows devices such as solenoids to remain activated for multiple pockets or grippers, rather than actuating and de-actuating for each pocket when their activation is required for several sequential pockets or grippers. This reduces noise and reduces wear on the devices.
Once the Inserter is properly setup and synchronized, WinLincs 4 may sent a Zone Start request. The Pocket Loader task will begin to put data into the structures in contained in the Position Array. As the Inserter cycles, the information stored in the Position Array “shifts” as the corresponding physical gripper and pocket move down the Inserter. Various tasks read information from the Position Array, based on a predetermined location for each task. That is, each task is associated with a location on the machine, and it reads the information from the Position Array as the physical pocket moves into the location. The task uses the information from the Position Array, plus general configuration and Zone information to determine what action to take. For example, a Feeder Control Task may look at the information for a pocket to determine if it should feed an insert into that pocket. It could also use status information, such as whether or not a previous feeder had missed a feed, along with general information, such as if Repair was turned on, to modify the decision to feed. This procedure is generally typical for most tasks on the machine. In a similar manner to the control of the Feeder for a particular pocket, control decisions for a product continue to be made as it transitions from pocket to gripper, and eventually to the delivery of the Inserter. All information related to the contents of a particular pocket or gripper is stored in the Position Array in the element corresponding to the pocket or gripper.
In addition to sending CAN Bus messages to Network Controller to effect control of the Inserter, MICA also collects information for status and diagnostics needs. For example, data provided from MICA and displayed on WinLincs 4 allows an operator to view information showing the eventual disposition of a piece, whether it will be rejected or sent to a Delivery device.
The MICA software can be reloaded on the Control Computer from WinLincs 4. This provides a mechanism to update the Control Computer with a new version of MICA without having to directly access the Control Computer. Also, a similar mechanism allows MICA to Down Load new software versions to the Network Controllers on the Inserter, from files stored on the WinLincs 4 computer. The Network Controllers can then be restarted and begin executing the new software. This allows the Network Controllers to be reprogrammed without being physically accessed. This taken in conjunction with the ability to remotely access (via the Internet) WinLincs 4, allows a remote technician to completely reprogram the machine without any manual intervention at the Inserter itself.
Typical Pocket Cycle
This section describes the major actions that take place during a typical pocket cycle of the Inserter of the present invention. In one embodiment, a pocket cycle is defined as the occurrence of 32 Timing messages. These messages are generally referred to as Timing Message 0 to Timing Message 31, the “times” referred to as Time 0 to Time 31. The timing messages are derived from the Main Machine Encoder, and correspond to the movement of the pocket chain through the length of one pocket, or six inches. The spacing of the gripper chain is the same as the pocket chain, and they move synchronously, so the same timing is common to both. A procedure is performed on the Inserter to synchronize the Timing Messages with the machine by defining Time 0 as occurring when a specific point on a pocket reaches a specific location on the machine. Although this description starts at Time 0 and progresses, it should be remembered that this is a continuous process, and that actions can span through Time 0. Note that the “pocket cycle” for a specific device should be viewed relative to the device and its exact physical location on the machine.
For example, a Reject mechanism consists of a cam actuated by a solenoid that is fastened at a specific location on the machine. It opens the gripper by acting on a roller mounted on an arm on the gripper. From the perspective of the Reject, the cycle for a particular gripper may be thought of as starting when the roller of the preceding gripper leaves the cam, past the point where the roller of the gripper in question reaches the cam, to the point when the gripper's roller leaves the cam. The Timing message that defines the start of this cycle depends on exactly where on the Inserter the Reject mechanism is located.
Note: Many things are happening to many pockets and devices simultaneously on the Inserter. Also note: the times at which events in this example occurs are not necessarily the same for any other Inserter.
Example Typical Pocket Cycle for a A16 into 1″ Inserter, Two Deliveries in Split Mode.
Time 0—Message sent from MICA to Drop 1 Network Controller (NC) requesting it to accept the next paper.*
Time 1—No action occurs.
Time 2—The Position Shifter logically shifts the data for the pockets and grippers by one position in the Position Array.
Time 3—Message sent to Machine NC to actuate Pocket Repair for Pocket 5.* Feeder 2, 6 and Jacket A feed, requested last cycle.
Time 4—Broadcast message from MICA sent to Feeder NCs 3, 7, 15 to feed, and Feeder 111 to inhibit.* Feeder 14 feeds, requested last cycle. Feed status messages from Feeders 3, 7, 11, 15 received. These statuses are for the feeds that were requested two pocket cycles previously.*
Time 5—Message sent from Mica requesting the Reject mechanism to actuate.* Feeder 10 feeds, requested last cycle.
Time 6—Machine NC actuates Pocket Repair solenoid.* Paper taken by Delivery 1.
Time 7—Message sent to Machine NC to actuate Gripper Repair Solenoid for Gripper 113 (Pocket 7).*
Time 8—No action occurs.
Time 9—Machine NC actuates Gripper Repair solenoid.* Check Copy request received from WinLincs.
Time 10—Machine NC activates Reject Solenoid.*
Time 11—No action occurs.
Time 12—Broadcast message from MICA to Feeder NCs 2, 6, 10, 14, and Jacket A to feed.* Feed status messages from Feeders 2, 6, 10, 14, and Jacket A received. These statuses are for the feeds that were requested two pocket cycles previously.*
Time 13—Check Copy request sent to Machine NC.* Feeders 5 and 9 Feed, requested last cycle.
Time 14—Message sent from MICA to Drop 2 Network Controller (NC) requesting it to accept the next paper.* Feeders 1 and 13 Feed, requested last cycle.
Time 15—First Pocket Detected message sent by Machine NC.
Time 16—Paper taken by Delivery 2.
Time 17—Upstream Unopened Jacket Sensor detects Open. Opener NC send message to MICA.
Time 18—Machine NC de-activates Reject Solenoid.*
Time 19—Downstream Unopened Jacket Sensor detects Open. Opener NC send message to MICA. Feeder 12 feeds, requested last cycle.
Time 20—Broadcast message from MICA sent to Feeder NCs 1, 5, 9, 13 to feed.* Feeder 4 feeds, requested last cycle. Feed status messages from Feeders 1, 5, 9, 13 received. These statuses are for the feeds that were requested two pocket cycles previously.*
Time 21—Machine NC de-activates Pocket Repair solenoid.* Feeder 8 feeds, requested last cycle. Feeder 16 inhibits.
Time 22—Unopened Jacket task writes “Unopened” bit into Position Array for pocket 78.*
Time 23—Message from Feeder 8 to Machine NC—Stop Button pushed. Message from Machine NC acknowledging Stop Button. Machine NC sends command to Main Drive requesting the Inserter stop. MICA sends message to WinLincs 4 to display a Stop at Feeder 8.
Time 24—No action occurs.
Time 25—First Pocket message processed by MICA.*
Time 26—Machine NC de-activates Gripper Repair solenoid.*
Time 27—No action occurs.
Time 28—Broadcast message from MICA sent to Feeder NCs 4, 8, 12, 16 to feed.* Feed status messages from Feeders 4, 8, 12, 16 received. These statuses are for the feeds that were requested two pocket cycles previously.* Drive stops, machine continues to coast. Feeder 3 feeds piece, requested this cycle.
Time 29—Machine NC actuates Check Copy mechanism (De-actuates during next cycle.)* Feeder 11 inhibits, requested this cycle.
Time 30—Feeders 7 and 15 feed pieces, requested this cycle.
Time 31—No action occurs.
* Action occurs synchronously with the Timing Message, all other action are asynchronous.
Task Table Description
The Task Table is a dynamic software mechanism based on a C++ class, in the MICA software, for allowing various control functions to execute at specific times in a pocket cycle. It provides a structure that allows the point (time) in a pocket cycle for a task to be performed to be set easily and in a standard fashion, for this time to be changed dynamically, and for multiple tasks to be preformed at the same point in a pocket cycle without interfering with or requiring the modification of other tasks. The Table also insures that data in the system is processed in a controlled, sequential manor, and that functions are executed in a specific, sequential order. A task take the form of a software function, which is called will optional parameters.
In one embodiment, there are approximately 32 Timing messages generated by the Machine Network Controller for every 6 inches (one pocket length) of movement of the pocket chain. These messages are sent over the CAN Bus and are received by the Control Computer, which is running MICA. The Machine NC uses an encoder to determine the movement of the pocket chain, and generates the messages based on encoder counts, so that they are evenly spaced. The messages are numbered from 0 to 31. When the Control Computer receives a message over the CAN Bus, it is processed by MICA, and appropriate software tasks for that “time” are executed.
The Task Table Class contains the Task Table array, a two dimensional array of structures of type TASK_ENTRY. Each TASK_ENTRY element consists of a Device Number (Dev_Num), which is the real or logical device that the task is performed for, a Task Number (Task_Num), which is used for Table maintenance, a pointer (Task_Param_Ptr) to the function (task) which is to be executed, and a pointer (Passed_Param_Ptr) to an optional list of parameters for the task.
One dimension of the array holds the structures for all the tasks that will occur at a particular time. There is an arbitrary maximum (specified by a parameter) of 20 tasks that can occur for a particular timing message. The other dimension specifies the “time” that the task will be performed.
The total size of the table is 640 (32×20) elements.
The Task Table Class also contains several variables that contain counts that are used for table maintenance.
There are five Methods or functions for the Task Table Class. They are: Register_Task, Delete_Task, Compress_Table, Get_Table_Entry, and Get_Task_Count. Register_Task adds a task into the Task Table. The time for the task to execute, and a pointer to the task function are key parameters. Delete_Task removes a task from the Task Table. Compress_Table is a utility function that moves elements in the Table after a task is deleted. Its purpose is to insure that all tasks for any specific time are adjacent in the Table. Get_Table_Entry returns the information for task From the Table. This information is then used to execute the actual task function by means of an indirect function call using the Task_Param_Ptr. Get_Task_Count returns the number of tasks for a particular time.
The Task Table is used as follows: On startup, tasks are loaded via Register_Task in the Task table. The list of tasks, and their execution “times” (i.e. the timing message when they execute) are either specified in MICA by a configuration file previously generated through the User Interface, or are “hard coded.” When a timing messages is received by the Control Computer via the CAN Bus, the message is parsed to determine the “time.” The Get_Task_Count function returns the number of tasks for that time. Get_Table_Entry is called repeatedly, depending on the number of tasks. Note that it is possible that there may be no tasks for a particular time. Each time Get_Table_Entry is called, the task for the entry is executed. These tasks typically either involve processing data based on flags that may have been set previously, or sending a message on the CAN Bus to one or more NCs. If the user changes the machine's configuration via the User Interface, the number or timing of tasks may change. If the timing for a task is changed, the existing task entry is first deleted from the Table. The Table is then compressed, and the task added back in at the new time using Register_Task. The added task becomes the last task executed for the time. Note that our usage rules specify that no two tasks with any dependency on each other (either directly in the code or through an external device) can be executed at the same task time. For example, assume there is a task that executes at “Time 2” and sends a message to an NC to cause a device to actuate. It would be improper to also query the status of the device at “Time 2,” since it may not be possible to determine which of the two tasks would be executed first, leading to unpredictable results.
CAN Message Structure
This section contains an explanation of the CAN message structure for the present invention.
As previously discussed, a typical system will consist of a Control Computer (CC), Network Controllers (NCs) for feeders, and NCs for other devices. It is possible to have multiple CCs in the network, although this is not the common implementation. The CC will send messages to the NCs and the NCs will send messages to the CC, but NCs will not communicate with other NCs. There are two exception: The first exception is the Timing NC. It will send broadcast messages containing timing information to all CCs and NCs. The second exception is the Run, Stop, Jog command. This is sent from a Feeder or Drop NC to the Machine NC. The Run, Stop, Jog command is also received by the Control Computer. If there is more than one CC in the system, the CCs will communicate with each other.
Normal transmissions will be of 6 types:
Messages are split into two classes, Individual Messages and Broadcast Messages. Individual messages are sent by one device to another device. All devices receive the message, and then look at the address portion of the identifier field to determine if it matches the address of that particular device. If the address does not match, the message is ignored. Broadcast messages are for groups of devices. Each device examines the command portion to determine if the message applies to them.
The CAN protocol specifies a combined Address/Priority identifier for each message. Each device on the CAN bus has an address which is compared with incoming messages. There is also a mask register that specifies the bits of the address that will be tested. If the bits of the device's address, specified by mask register, match the corresponding bits of the incoming message, the message will be received. Otherwise, the message is ignored. The same identifier field of the message is used to determine message priority for collision avoidance. In CAN, the lower the value of the identifier, the higher the priority of the message. For the present invention, all the mask register is not used. All devices receive all messages, and are responsible for determining if the message is applicable for the particular device. In addition to identifier portion, the message will contain from zero to eight data bytes. These bytes can contain a variety of information, depending on the particular message being sent.
Bytes are defined as: |Byte 0|Byte 1| Bits are numbered in a similar manner, with the least significant bit of Byte 1 being Bit 0.
Since only 11 bits are used in a CAN address, the five leftmost bits of Byte 1 are unused or “Don't Cares.” Therefore, the value range is:
for 2048 distinct values.
Details:
Identifier, Individual Messages
b10-b9 Priority bits—These are used to specify the priority of the message. They are used to insure that important messages get through immediately. Code 00 has the highest priority.
b8 Broadcast/Individual—Defines the class of the message. When this bit is 0 the message is an Individual Message.
b7 Address Specifier—Set to ‘1’ for messages sent from an NC to the Control Computer, ‘0’ otherwise. Because several NCs may simultaneously respond to a Broadcast message from the Control Computer, a means of distinguishing the messages is required. When this bit is set to ‘1’, the Address is the address of the NC sending the messages, and the destination is defined to be the Control Computer. This makes the Identifier for each of these messages unique. In all other messages, the Address is the address of the destination NC.
b6-b0 Address—There are 128 possible address for devices. Addresses 64 through 127 are reserved for the feeder NCs. Addresses 8 through 63 are reserved for non-feeder NCs. Address 8 is the Timing NC. Address 9 is the Machine NC. Address 10 is the Idler End NC. Address 111 is the Opener NC. The addresses for the Drop NCs start with Address 12. Addresses 0 through 7 are for CCs. Note that these addresses refer to the functionality of the NC, not a specific piece of hardware. A single NC may have more than one address if it performs more than one logical function. And example would be combining Timing and Machine NC functionality into a single NC.
Identifier, Broadcast Messages
b10-b9 Priority bits—These are used to specify the priority of the message. They are used to insure that important messages get through immediately. Code ‘00’ has the highest priority.
b8 Broadcast/Individual—Defines the class of the message. When this bit is ‘1’ the message is a Broadcast Message.
b7 Spare—For future use.
b6-b5 Spare—For future use.
b4-b0 Command—There are thirty-two possible broadcast commands that can be sent. The Command bits are used to specify the predetermined group that the message applies to, and how the receiving device should interpret the data bits.
Data, Individual Messages
byte0 Sequence Number—Number that corresponds to the next number in sequence for messages being sent from the sending device to the receiving device.
byte1 Message Number—Defines the Message. See the Messages section.
byte2 Data—See individual message for data definition.
byte7
Data, Broadcast Messages
byte0 Sequence Number—Number that corresponds to the next number in sequence for all broadcast messages.
byte1 Source Address—The address of the device sending the broadcast message. See above for address description.
byte2 Source Address-Data—See individual message for data definition.
byte7
Note: “Command” is used to refer to the bits that define the function of a Broadcast CAN message and “Message” is used to refer to the bits that define the function of a Individual CAN message.
Sequence Numbers
Most messages will have a sequence number to insure that no messages are lost. The number will start at zero, and be incremented for each message sent to a particular device. A sending device will keep a separate count for each device it sends messages to. All devices will maintain the count for broadcast messages. See the Messages section for details on which messages have sequence numbers.
Identifier Construction
The basic unit for CAN messages is the byte. The identifier is composed of two bytes. Each byte is built up separately by combining together defined constants and variables. The constants can be bitwise “ORed,” or they can be mathematically added. Note that the constants are byte length. If the identifier is being treated as a word, use the word length constants for the high order byte (Byte1). See below for a list of certain defined constants.
A typical identifier for a Broadcast message would be:
A typical identifier for a message sent from a CC to a Feeder NC would be:
Note: It is not necessary to include the SPARE constants.
Example of a Broadcast Message
Example of an Individual Message
| Number | Date | Country | |
|---|---|---|---|
| 60390808 | Jun 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10465284 | Jun 2003 | US |
| Child | 11109182 | Apr 2005 | US |
