Browse Prior Art Database

Run Control for Ticket Unit Minimizing Ticket Wastage

IP.com Disclosure Number: IPCOM000080831D
Original Publication Date: 1974-Feb-01
Included in the Prior Art Database: 2005-Feb-27
Document File: 4 page(s) / 92K

Publishing Venue

IBM

Related People

Chamoff, ME: AUTHOR [+5]

Abstract

This run control is used in connection with a string of connected tickets. 10 having a magnetic stripe on one side, which move through a ticket encoding, reading and printing machine in direction 12. The machine includes a magnetic write head 14, a read head 16 spaced from write head 14 (such as by one inch) and a print head 18 still farther downstream (such as five inches from write head 14). Tickets 10 run through the machine in batches, in which all of the tickets are identically printed and magnetically encoded. Read head 16 is used to verify the encoding on a ticket 10 by write head 14; and a ticket 10 is counted to be part of a batch after it is written on, with the assumption that the ticket will verify using head 16.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 34% of the total text.

Page 1 of 4

Run Control for Ticket Unit Minimizing Ticket Wastage

This run control is used in connection with a string of connected tickets. 10 having a magnetic stripe on one side, which move through a ticket encoding, reading and printing machine in direction 12. The machine includes a magnetic write head 14, a read head 16 spaced from write head 14 (such as by one inch) and a print head 18 still farther downstream (such as five inches from write head
14). Tickets 10 run through the machine in batches, in which all of the tickets are identically printed and magnetically encoded. Read head 16 is used to verify the encoding on a ticket 10 by write head 14; and a ticket 10 is counted to be part of a batch after it is written on, with the assumption that the ticket will verify using head 16.

The first ticket of a second batch is encoded using head 14 immediately after the last ticket 10 in a first batch has been encoded, and this occurs while the last ticket of the first batch is verifying using read head 16. Thus, if the last ticket of the first batch does verify, there is no ticket wastage. On the other hand, if the last ticket of the first batch does not verify, the encoding of the first ticket of the second batch has already been started at this time, and the two batches with different data will be intermixed if this first ticket of the second batch is used. The second batch, at this time, is therefore aborted, so that the error ticket can be disregarded and can be remade as another ticket to complete the first batch.

The print head 18 is so controlled that it does not print the ticket of the aborted batch that is being encoded at the time read head 16 is attempting to verify the last error ticket of the first batch, and also does not print the error ticket, so that these two tickets can be easily recognized and discarded.

The machine is preferably controlled by a microcontroller which contains a "last ticket of batch" shift register 20; a "verify error" shift register 22; an "inhibit operations" shift register 24: control logic 26; a "tickets made" counter 28; a "batch size" compare circuit 30; a "verify" compare circuit 32; a buffer 34; and a "write buffer" address register 36, a "print buffer" address register 38 and a "batch size" register 40 for the buffer 34. The illustrated 0 to 7 sections of buffer 34 contain information applicable to consecutive batches of tickets 10, which is "ticket setup", "encode data", "print data", and "batch size" information. The ticket setup information has to do with ticket length, etc. The encode data information is that information which is magnetically encoded on the magnetic stripe of each of the tickets by write head 14. The print data information is that information (which may be identical with the magnetically encoded information) that is printed on each of the tickets 10 of a batch by print head 18. The batch size information is the number of tickets 10 in any particular batch.

The control logic 2...