JP2720334B2 - Game equipment - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a game machine using a game machine such as a pachinko machine, an arrangement ball machine, a slot machine, etc., and more particularly to a game machine in which operation data of a game machine is collected by a management machine. And effective technology.

[0002]

2. Description of the Related Art In a pachinko gaming facility as an example of a conventional gaming facility, a plurality of gaming machines are each connected to a management device by a cable or the like, and the management device receives a jackpot as operating information from each gaming device. In some cases, a signal indicating the occurrence of a special game state called or the number of collected balls (for example, in units of 10) is transmitted.

[0003]

[0004]

[0005]

However, in the conventional game equipment, since the type of operation information of the game device collected by the management device is small, when the collected operation data is stored in a storage device such as a hard disk,
It was possible to accumulate data for several days without requiring such a large storage capacity.

[0006] However, in recent years, computerization has advanced computerization in amusement arcades, and accordingly, there has been a demand for collecting various kinds of operation data in a game machine. By collecting such various kinds of operation data, it becomes possible to analyze the characteristics of each gaming device and the business performance of the entire game store, and appropriately determine a business policy for the next day and thereafter.

[0007]

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems. It is an object of the present invention to provide a game machine in which a variety of operation data in a game machine can be collected by a management machine. It is an object of the present invention to provide a technique capable of accumulating various kinds of operation data generated in a large number of gaming machines over several days without significantly increasing the storage capacity of a storage means.

[0009]

In order to achieve the above object, the present invention provides a plurality of gaming machines and a management device capable of collecting operation data of these gaming machines. In the gaming facility configured to be able to communicate with the management device, the management device is configured to collect the operation data of the gaming device (see FIG. 84). First storage means (each file in the main storage device M-MEM) for storing operation data;
A second storage means (for example, a floppy disk storage device 402) capable of storing the operation data stored in the storage means,
Operating data transfer means (Table 1) for transferring the operation data stored in the first storage means to the second storage means for storage.
9), and the operation data transfer means transfers the operation data stored in the first storage means to the second storage means in association with the tabulation management period of the business data and stores the operation data. .

[0010]

According to the above means, the operation data collected from each gaming machine is stored in the first storage means, and the operation data is transferred to the second storage means in association with the total management period of the business data and stored. It is possible to store a variety of operation data generated in a large number of gaming devices for several days without significantly increasing the storage capacity of the first storage means. As a result, for example, In addition, it is possible to analyze the characteristics of each gaming device and the sales performance of the entire game store, and appropriately determine a sales policy.

[0011]

FIG. 1 shows an embodiment of a pachinko game system as an example of a storage medium type game facility to which the present invention is applied.

The pachinko gaming system according to this embodiment includes a pachinko machine 100 as a game machine and a storage medium issuing device for issuing a card CD as a storage medium having a local value in order to start a game in each pachinko machine. Centralized management of the issuing machine 200 of the above, a prize ball obtained as a result of the game and a payment device 300 as a storage medium payment device for payment of a purchase money not used for the game, and the above various terminals. A management device 400 for controlling and a data transmission line 500 as a transmission means for organically connecting the management device 400 and each terminal, and these constitute an organic combination. The organic combination can be interposed only by the card CD, and the operation of the card and the conversion of the valuable data can be performed only by the organic combination. Therefore, the pachinko machine 100, the issuing machine 200,
The settlement machine 300 and the management device 400 each have a card reader (in this specification,
A card reader that writes data on the magnetic surface of the card is also referred to as a card reader), and information on the card and information on each terminal are stored in a storage device of the management device 400 in the form of a file. It has become.

Next, before entering into a detailed description of each component of the organic combination, a card CD used in the storage medium type game facility of the present embodiment will be described.

As shown in FIG. 2A, for example, the card CD used in the storage-medium type game equipment of this embodiment includes a purchase amount AM, an issue date (= effective date) DATE, and the like. A print display section PRT is provided along the card insertion direction (longitudinal direction of the card) on which information necessary for the player and an issue serial number n and the like required when the damaged card is restored are printed at the time of issuance. Therefore, there is no need to prepare a plurality of types of cards on which different amounts of money are printed in advance.

Immediately above the print display section PRT, a perforation forming section for recording the card status, that is, the history or status transition of the card such as issued, resurrected, played, returned to zero (zero), and settled, in the form of perforations. Hole forming area PH as
Are also provided along the card insertion direction.

By detecting the perforations formed in the card CD with a photoelectric detector, it is easy to read and confirm the number-of-balls data from the file of the management device 400 using the code recorded on the magnetic surface. Thus, the load on the controller of the card reader and the management device 400 required to determine the processing corresponding to the status of the card can be reduced.

On the other hand, at a position slightly below the center of the card CD, there is provided a magnetic recording portion MG coated with a band-shaped magnetic material from the front end to the vicinity of the center (see FIG. 2B). However, the magnetic recording portion MG may be formed not only on a part of the card in the longitudinal direction but also in a continuous band shape from end to end of the card as in the print display portion PRT, or a magnetic material may be applied to the entire back surface of the card. May be used as a magnetic recording unit.

Further, in the card CD of this embodiment, a belt-like roller running area RRA slightly wider than the transport roller in the card reader is provided between the print display section PRT and the magnetic recording section MG, that is, in the center of the card CD. Are provided along the longitudinal direction of the card, and the magnetic recording unit MG, the print display unit PRT, and the authenticity discrimination which have important information used for determining the surface of the card, especially the card by contact with the transport roller, The area TF is prevented from being damaged, and the information can be prevented from being unreadable.

Further, in the card CD of this embodiment, a true / false discrimination area TF made of a security mark concealed in characters such as a hole name printed on the card surface is provided below the magnetic recording portion MG. That is, the characters "PLAZA" printed on the front surface of the card correspond to the detection bit patterns B0 to B9 in which the legs of each character are provided at a pitch of 3.5 mm or the like as shown in FIG. Design and print in such a way as to come to the desired position. Then, the character width is set to 0.5 to 1.5 mm and the distance between each bit is set to 3.5 mm, and "1" or "0" of each bit is expressed by shading of the character. In addition, the fifth bit B4 from the left and the last bit B9 of the 10 bits are bits B0 to B3 and B5 to B5.
The shading of the character is determined so as to represent the parity of B8. It is more preferable that the security bits concealed in the character string be formed using a special ink that can be detected only by the sensor and cannot be distinguished by human eyes.

Further, on the surface of the card CD of this embodiment, a head cleaning area HCN is provided in which a cleaning agent for removing dirt on the magnetic head is applied to a band-shaped area continuous with the magnetic recording portion MG. ing. At the same time, in the card CD of the embodiment, the magnetic recording unit MG
To keep track of where is located,
As shown in FIG. 3D, a white layer 13 is formed on a magnetic layer 12 formed by uniformly coating magnetic particles on a base material 11 made of plastic such as polyester, and a pattern is further formed thereon. After placing the print layer 14, a thermosensitive coloring layer 15 is formed on a part thereof (a portion corresponding to the print display unit PRT),
A transparent protective film 16 is coated thereon.

A cleaning agent of the same color as that of the white layer 13 is applied to the cleaning area HCN, and the surface thereof is exposed so that the protective film 16 is not coated, so that the cleaning area HCN is colored with other parts. In order to improve the aesthetic appearance, it hardly changes. A pattern printing layer 17 is formed on the back surface of the base material 11 of the card CD, and the pattern printing layer 17 is coated with a protective film 18 thereon.

In the card CD having the above structure in which the white layer 13 is formed on the surface of the magnetic layer 12,
Since the magnetic layer 12 made of black magnetic particles is covered with the white white layer 13, it is possible to provide a card with a fashionable character by printing a picture and conceal the magnetic recording unit MG. It also has functions.

Furthermore, since the protective film 16 is coated on the surface of the card CD, an area holding important information used for discriminating the card, such as the print display section PRT, the magnetic recording section MG, and the authenticity discrimination area TF. Is protected, the information is less likely to be destroyed, and the reliability of the card is improved.

FIG. 4 shows a configuration example of the magnetic recording section MG provided on the card CD.

The magnetic recording portion MG of the card CD of this embodiment
Is composed of two tracks, of which the first track TRC1 records clock data giving sampling timing. The second track TRC2 includes, in order from the left, a 4-bit start code and a field STX containing the parity bit, a company code MKC indicating the manufacturer of the card reader, and a device code MC indicating the model of the card reader.
C, game store identification code DSC, date data DAT
E, a card number No., an issue command code FNC given from a card reader at the time of card issuance, a text field TXT containing a security data SDC read from the authenticity discrimination area, a field ETX containing a text end code, text data and an end code. Is composed of a field LRC containing an exclusive OR value (detection code) and a field STX containing a start code. Moreover,
In the date data DATE, a bit P indicating each parity is provided for every four bits, and the first four bits represent “month”, and the sixth to ninth bits and the eleventh bit represent “day”. , And the 12th to 14th bits and the 16th to 19th bits are binary-coded and recorded in the last two digits of the Christian era.

In a card having a magnetic recording section, it is generally easiest to decode the recording format and recording data from the date. In the card CD of the above embodiment, the order of the date is changed. Since a parity bit is inserted for each bit and the correspondence of the recording bits is changed, forgery of the card becomes extremely difficult. Also,
Since the issue serial number n is printed on the print display unit PRT, the card can be restored from the file information of the management device 400 even if the information of the magnetic recording unit MG cannot be read due to damage of the card or the like. .

Further, as described above, the information recorded in the magnetic recording portion MG of the card CD of this embodiment includes an identification code DSC for specifying the usable space of the card,
Date DATE to indicate the validity of the card,
Only a card number as an identification code obtained from the issue serial number n using an appropriate function or conversion method and a check code for error detection are used, and the purchase amount and the number of balls are not recorded. These are configured so that they can be extracted in real time from the data file of the management device 400 by the card number NO. This prevents fraud by copying the card and minimizes the damage caused by fraud. In other words, even if the card is copied, no damage occurs beyond the purchase price and the number of balls registered in the data file, so copying the card is a completely useless act.

Further, in the above embodiment, the authenticity of the card is determined not only by the magnetic recording information recorded on the card CD but also by the authenticity discrimination area TF which is difficult to forge. It can be reliably prevented. In addition, since the unauthorized card can be immediately detected by checking the authenticity discrimination area TF, the magnetic information is stored in the management device 400.
To detect fraudulent cards more quickly than sending fraudulent cards. It is to be noted that a hole is also formed in a telephone card or the like having a magnetic recording section, but a conventional card is provided to inform the user of the remaining balance, and a card reader is used to make a hole. Is not intended to be used for any processing or determination.

Next, an example of the configuration of a gaming machine that provides an original game will be described with reference to FIGS.

The gaming machine serving as the gaming machine of this embodiment is provided on a pachinko machine 100, and in a one-to-one correspondence with the pachinko machine 100, on an island facility or the like above the gaming machine body, and mainly relates to a display and a card reader. The control unit 160 is configured to control and collect operation data during a game.

The pachinko machine 100 is mounted in a machine frame 101 fixed to an island facility of a pachinko parlor by a hinge 102 so as to be openable and closable. A reinforcing plate 107 having an operation dial reinforcing member 107a that withstands the weight of the pachinko machine 100 and absorbs the vibration of the hit ball firing device 103 is fixed to a lower portion of the machine frame 101. In the lower part of the pachinko machine 100, a hit ball launching device 103 for firing the enclosed balls one by one into the game area and an operation dial 104 thereof are provided,
The card CD is located above the operation dial 104.
A money amount display 111, a ball number display 112, a purchase switch 113 for enabling a procedure for starting a game using
An operation panel 110 including a suspend switch 114, an end switch 115, a game state display 116, and the like is provided. The configuration of the game area on the front of the pachinko machine is the same as that of the conventional one. The purchase switch 113 is connected to the control unit 160
An instruction switch for converting this into a game ball in a unit of 200 yen or the like within a range of the amount of money of the card assuming insertion of the card into the card reader 800 built in,
The converted game balls are the number of possessed balls. The remaining amount of the card is displayed on the amount indicator 111 in a unit of 100 yen as one unit, and the converted number of balls is indicated by the number of balls indicator 1
12, the number of possessed balls is decremented by one each time one game ball is fired by the hit ball firing device 103, and when a winning ball is generated, the number of prize balls is added and displayed. The end switch 115 can be turned on whenever the player wants to end the game (including a case where the player wants to change the game console), so that the control unit 160 can eject the card in use. At that time, the unit controller 190 registers the remaining amount of the player and the number of balls (the sum of the purchased ball and the acquired ball) at that time in the file of the management device 400, and then inserts and ejects the card from the card reader 800. 802a
Discharge more. The interrupt switch 114 is a switch used by the player to temporarily stop the game for a break, although the player does not intend to stop the game at the game machine currently playing. When this switch is operated, The unit controller 190 temporarily ejects the card and waits for the same card to be inserted again, during which time no other card is accepted. The purchase switch 113 of the above switches is of a built-in lamp type, and the number of balls held is “0”.
Then, the lamp in the purchase switch 113 blinks.

As shown in FIG. 6, the operation panel 110 is mounted on the openable front panel 105 at the lower part of the pachinko machine 100, has a hollow shape with a triangular cross section, and has an upper surface inclined downward and forward. This makes the display easier to read.

The display surface 11 is provided inside the operation panel 110.
0a are arranged in parallel with the wiring boards 120A and 120B,
On this substrate 120A, a money amount indicator 111 and a ball number indicator 112 each composed of a 7-segment LED are provided.
The switches 113 to 115 and the built-in lamp are mounted on B, and are covered with a display plate 117. A portion of the display plate 117 corresponding to the indicators 111 and 112 is a transparent window 117 a and a switch 113.
Portions corresponding to .about.115 are openings 117b (see FIG. 7). An operation button 118 is mounted in the opening 117b so as to cover above the switches 113 to 115. 121 is a purchase switch 11
3 is a built-in lamp corresponding to FIG.

At the front end of the operation panel 110, there is provided a game state display section 116 in which a display lamp 123 is covered with a translucent Fresnel lens 119 or the like. Dial 1
When it is turned 04, it turns on.

Further, on the side (left side in the embodiment) of the operation panel 110, an operation button 125 having a built-in stop switch 124 is mounted.
Is turned on, it is possible to give a command related to the game, such as stopping the operation of the accessory provided in the game section. The stop switch 124 is mounted on a wiring board 120C provided in the operation panel 110, and the wiring group 1 extending from the wiring board 120C.
26C and a wiring group 126A, 126B extended from each of the boards 120A, 120B is drawn out to the outside, and the pachinko machine control device 19 arranged at the lower part of the back of the pachinko machine by connectors 127A to 127C connected to its ends.
5 can be connected.

On the other hand, the pachinko machine 100 constituting the gaming machine of this embodiment is configured as a closed-type gaming machine that circulates and uses the game balls sealed in the machine, and includes a sealed ball circulating device 130 for circulating the sealed balls. On the back surface.

FIG. 15 shows a configuration example of the back side of the pachinko machine 100.
Shown in

A prize ball collecting gutter 131 covering a plurality of prize ball lead-out holes formed to penetrate the game board corresponding to a prize area provided in the game area on the front of the game board is held by the frame 106. It is attached to the back of the game board. The bottom wall of the winning ball collecting gutter 131 is inclined downward toward the center to form a guide shelf 131a, and below it, an out ball gutter 132a, a first safe ball gutter 132b, and a second safe ball gutter 132c, as shown in FIG. Are formed integrally with each other. In the middle of each gutter in the guide gutter 132, a photoelectric type out sensor SNS1, a first safe sensor SNS2, and a second safe sensor SNS3 each including a pair of light emitting and receiving devices are mounted.

The guiding gutter 132 has a merging gutter 132d for collecting the balls flowing into each gutter at one place.
The terminal end of 32d is connected to the upstream side of the guide trough 133 which is gently inclined so as to align the pachinko balls in a line as shown in FIG. 9, thereby forming the sealed ball circulation device 130. Further, on the upstream side of the guide gutter 133, a foul ball receiving port 134 (FIG. 1) provided at the upper end of the firing rail to collect a so-called foul ball in which a hit ball hit along the firing rail returns toward the rail base. No. 11) and a foul ball gutter 133 arranged to face
a is formed integrally, and the foul ball is
Through the guide gutter 133 to join the ball. A foul sensor SNS4 is provided in the middle of the foul ball gutter 133a.

The lower end of the guide gutter 133 has a storage portion 135a for one ball facing the lower end of the guide gutter 133.
A ball feed 135 that separates the balls on the ball 3 one by one and allows the balls to flow downward is swingably attached. A stopper 136 is fixed to the rear of the ball feed 135 to prevent the ball feed 135 from rotating more than necessary, and when the ball feed 135 is turned downward by the weight of the ball that has flowed in, the upper end surface thereof is a guide gutter. 133
The upper sphere can be prevented from flowing down. further,
A rotatable ball leveler 137 is attached in the middle of the guide gutter 133, and a slide type ball punching mechanism 138 is provided downstream.

As shown in FIG. 10, when the sealed ball circulating device 130 is mounted on the back of the frame board 109, the ball removing mechanism 138 is provided with a blocking piece 148 protruding from the back of the frame board. The slide has been blocked and the ball cannot be removed. Thus, the enclosed ball circulating device 130 is mounted so as to be able to rotate as a whole by a hinge portion 139 provided on one side (the right side in FIG. 10), and is turned rearward around the hinge portion 139. When moved, the ball removing mechanism 138 can be slid to remove the ball. In addition, an elastic locking piece 133a is fixed to the end of the guide gutter 133, and by engaging this with the engaging step 149 of the frame board 109, the sealed ball circulation device 130 cannot be rotated. Can be fixed.

The pachinko balls separated by the ball feed 135 pass through a ball passage hole 139 (see FIG. 11) formed in the frame board 109 provided behind the front panel 105, and are slanted toward the front of the frame board. One falls down to the base of the launch rail 140 that is fixed to the base. The firing rod 103a is disposed so as to face the base of the firing rail 140 (see FIG. 12). At the same time, below the base of the firing rail 140, an interlocking member 141 having a push-up piece 141a that is rotated in conjunction with the firing rod 103a and pushes up the ball feed 135 upward is provided.

Further, a concave groove is formed on the upper surface of the firing rail 140 to guide the sphere, and a reflection type photoelectric switch for detecting a sphere passing on the rail is formed on the front surface of the frame board 109. A sensor SNS5 is mounted at a distance of at least one ball from the rail upper surface by a bracket 142, and a return ball at the upper end of the mounting bracket 142 of the firing sensor SNS5 for preventing the return ball from jumping over the sensor. A blocking wall 143 is provided. Further, a foul ball receiving port 134 is formed in the frame board 109 corresponding to the upper end of the firing rail 140 to guide the return ball into the guiding gutter 132 behind the frame board, and the ball extends along the lower side of the foul ball receiving port 134. A receiving piece 144 protrudes.

At the upper end of the frame board 109,
A game board placement portion 109a is provided, and game board positioning projections 145 are provided upright at both ends.
Further, along the upper end of the frame board 109, a frame engaging portion 146 having a groove capable of engaging with the frame 106 for holding the game board is formed, and as shown in FIG. Frame 10 from above
6 are lowered along the positioning projections 145, and the lower ends thereof are engaged with the grooves of the frame engaging portions 146, so that the two can be connected. A lock 1 for detachably engaging a game board with a side wall of the frame 106
06a are provided, and the fasteners 147 are tightened and fixed in a state where the game board held by the frame 106 is placed on the placement portion 109a of the frame board 109.
Note that a speaker 15 for generating a sound effect related to the game is provided on one side of the front of the frame board 109 (the left side in FIG. 11).
0 is attached.

On the other hand, the front panel 105 covering the front of the frame board 109 is, as shown in FIG.
The lower end of the opening framed by the inner holding frame 108c is mounted to be openable and closable with one end (left end) as a fulcrum, and a firing rail frame 151 positioned above the firing rail 140 corresponding to the firing rail 140 is provided on the back side. A cutout 151a is provided in the middle of the firing rail frame 151 so that the firing sensor SNS5 can face the frame. A lock lever 152 is provided on the back surface of the front panel 105 opposite to the hinge. Above the front panel 105 in the front frame 108, the glass frame 1
54 is also mounted to be openable and closable. On the other hand, on one side opposite to the hinge portion 102 on the back surface of the front frame 108, a locking tool 156 for locking the front surface to the machine frame 101 and a locking device 157 thereof are mounted as shown in FIG. Have been. Reference numeral 155 denotes an opening lever of the glass frame 154.

The frame 106 (see FIG. 13) holding the game board and the frame board 1
09 to the fitting receiving portion 108b on the back of the front frame, the fitting projection 106b on the back of the frame, and the fitting projection 1 on the back of the frame board.
The frame 1 holding the front frame 108 and the game board by screwing together so as to make the 09b coincide with each other.
06 and the frame board 109 are integrated.

FIG. 15 shows a state in which the frame 106 and the frame board 109 are attached to the back surface of the front frame 108 in this manner, and the winning ball collecting gutter 131 is further provided on the back surface of the game board held by the frame 106. The pachinko machine control device 195 is disposed below the frame board 109. Further, on the back of the frame 106 and the winning ball collecting gutter 131, a game control device 158 is provided.
And a relay board 159 are mounted.

FIGS. 16 to 18 show an embodiment of the control unit 160 which is constructed separately from the pachinko machine 100. FIG.

The control unit 160 of this embodiment includes a status display 162 on the front of the storage frame 161 indicating the status of the pachinko machine 100, an analog display 163 in which a plurality of lamps are arranged in a line, and a winning ball generation. It has a safe ball lamp 164 for display, a call button 165 for calling a clerk, and the like. The analog display 163 is used to display the number of balls held in a game in an analog manner, or to display a hit state or a free state by simultaneous blinking and moving blinking.

The speaker 166 is provided in the storage frame 161.
And a card reader 800, a card insertion / ejection opening 802a of the card reader 800 is exposed on the front surface of the storage frame, and a card reader 800 is located above the insertion / ejection opening 802a.
Card holding display lamp 16 indicating whether there is a card inside
7 (LED 1) is provided below the card insertion / ejection opening 802a with a card insertion display lamp 168 for indicating whether or not a card can be inserted into the control unit 160.

Further, the storage frame 16 of the control unit 160
In the inside of the front panel 161a, the pachinko machine 100 is mounted.
A test switch 179 for enabling a game operation using a test card, which will be described later, is provided in a unique state separated from the management device 400, and the switch is turned on from the outside using a pin on the front of the storage frame. Pin insertion hole 169 for allowing the pachinko machine 1
Nameplates 170 are provided, each of which specifies a machine number given to 00.

Then, inside the front panel 161a of the control unit 160, as shown in FIG. 17, a setting switch 171 of the machine number displayed on the machine name plate 170, the status display 162 and the analog display 163. Lamp groups L11 to L15, L21 to L of the safe lamp 164
A lamp substrate 172 having the reference numerals 28, L31, and L32 (see FIG. 18), and a holding substrate 173 for the speaker 166 and the card insertion lamp 168 are mounted. A call switch 165a is provided behind the call button 165.

Further, in the storage frame 161, a card reader 800, a unit controller 190 for controlling the entire control unit 160, transmission means, and a monitor display 17 are provided.
A unit controller 180 having 4,175,176, a card reader controller 188, and a power supply 177 are built therein. In addition, below the card reader 800,
A storage box 178 for punched pieces generated when punching is performed by a punching device (described later) in the card reader 800 is detachably disposed. A card ejection switch (not shown) for instructing the card reader 800 to eject a card is provided on a substrate constituting the card reader control device 188.

The control unit 160 includes the front panel 1
Locking tool 179a and its release lever 1 on the free end side of 61a
79b is provided, and the release lever 179b faces the opening 161b formed at the lower end of the front panel 161a. As shown in FIG. 19, the control unit 160 is mounted on the machine frame 101 of the pachinko machine 100 and the unit mount 24 at the same height as the machine frame 101, and at this time, the front panel 161a is It is arranged so as to be flush with the front frame 108 of the pachinko machine. Therefore, the opening 161b of the front panel 161 facing the release lever 179b is normally closed on the upper surface of the front frame 108, and the opening 16
1b is exposed, and the release lever 179b can be operated. Thereby, the control unit 160
Need not be provided with a locking device.

The unit control device 180 in the control unit 160 is connected to the control device 19 of the pachinko machine 100 via a transmission line such as an optical fiber or a coaxial cable.
5 and a management controller 400 via a transmission controller and a local network (transmission cable) described later.

The control unit 160 of the embodiment is configured to perform data transmission using any transmission path.
An optical fiber connector 186 and a coaxial cable connector 187 are provided on the back surface of the storage frame 161 (FIG. 22).
reference).

FIGS. 20 to 22 show the pachinko machine 10.
1 shows an example of an island facility on which a gaming machine including a control unit 160 and a gaming machine is placed, and a state in which the gaming machine is mounted thereon.

In the island facility of this embodiment, a plurality of columns 22 are erected on a base 21 at an interval equal to the width of the gaming machine, and a horizontal mounting is provided at a height of about 60 cm from the floor. Table 2
3 is fixed by a support 22. In addition, this mounting table 2
Above 3, a first installation shelf 24 is fixed at a position separated by the height of the machine frame 101, and a second installation shelf 25 is further secured above the first installation shelf 25 by columns 22. A top plate 26 is fixed above the second installation shelf 25 so as to cover the upper end of the column 22. The table 23 described above
The first installation stand 24 has a front end projecting slightly closer to the support 22 than the support 22.
It is located rearward by the thickness of 01.

Then, the pachinko machines 100 are mounted together with the machine frames 101 on the mounting tables 23 between the columns 22, respectively.
1, the control unit 160 is mounted. Also,
A transmission path (not shown) constituting a local network is extended on the second installation table 25, and between the columns 22 is used for data transmission with the management device 400 via the transmission path. A transceiver 185 is mounted. In addition,
The front of the transceiver 185 is closed by the upper plate 27, and the lower part of the mounting table 23 is closed by the lower plate 28.

Further, although not shown, a 24 V power supply line extends on the lower surface of the mounting table 23, and a 100 V power supply line extends on the lower surface of the top plate 26. An outlet 30 for 24V power supply is provided at a position on the upper surface of the mounting table 23 corresponding to each gaming machine, and an outlet 31 for 100V power supply is provided on the bar 29 on the lower surface of the top plate 26 in correspondence with each gaming machine. Each is provided (see FIG. 22).

FIG. 23 shows an example of the configuration of a control system for the entire gaming machine including the pachinko machine 100 and the control unit 160.

Referring to FIG. 28, reference numeral 188 denotes a transport motor 8 which is a component of the card reader 800 shown in FIG.
07, a magnetic head 821, a punching device 820, and the like. The card reader controller 188, the pachinko machine controller 195, and various switches 171 and 1 provided in the control unit 160.
The unit 79, the displays 162, 163, 164, 168, and the speaker 166 are controlled by the unit control device 180.

Although not particularly limited, in this embodiment, the control device 195 of the pachinko machine 100 is connected to the unit control device 180 via an optical cable 191.
A detection signal from various sensors is input, and a drive control signal for a display or the like is output. To enable communication using an optical fiber cable, an optical multiplexed data link (interface) including a parallel-to-serial converter for converting parallel data and serial data, an optical-to-electric converter for converting electric signals to optical signals, and the like. ) Are provided between the unit controller 180 and the optical fiber cable 191 and at the connection between the optical fiber cable 191 and the pachinko machine controller 195 (described later).

By using the optical fiber cable 191 for data communication between the unit control device 180 and the pachinko machine control device 195, a large number of wirings conventionally arranged in a complicated manner behind the pachinko machine can be reduced. In addition to facilitating maintenance and management, malfunctions due to noise can be prevented.

Under the control of the pachinko machine control device 195, the money amount display 111, the number of balls display 112, the purchase lamp 121, the game state display lamp 123, the hit ball launching device 10
3 control device 194 and accessory control device 158, the purchase switch 113, the interruption switch 1
14. The signals from the ball detection sensors SNS1 to SNS5 such as the end switch 115 and the out sensor are subjected to waveform shaping by the pachinko machine control device 195 and the unit control device 18
0 is supplied. In this embodiment, the power supply system has two systems, 24 V AC and 100 V AC, and 24 V AC is supplied to the pachinko machine 100 side, and 100 V AC is supplied to the control unit 160 side. Separating the power supply in this way prevents the pachinko machine control unit from being inadvertently destroyed by the influence of the power supply in a pachinko parlor having many problems in the power supply system.

FIG. 24 shows the pachinko machine control device 19.
5 is shown.

The pachinko machine controller 195 is provided with a pachinko machine controller CPU 1 comprising a microcomputer.
This enables optical data transmission between the unit control device 180 and a reset circuit RST1 that monitors a periodic watchdog pulse output from the controller CPU1 and generates a reset signal when the pulse is interrupted. Therefore, a multiplex transmission controller CNT1 having parallel / parallel conversion means for converting parallel transmission data into serial data and serial / parallel conversion means for converting serial reception data into parallel data, and a photoelectric converter connected to the optical cable 191 via the optical connector 193. Conversion circuit OET and filter circuit FL for cutting noise of detection signals from various sensors
T, decoders DEC1 and DEC2 for decoding display data to the money amount display 111 and the ball number display 112, and a driver DR for forming a display drive signal based on the output thereof.
V1 and DRV2, a purchase lamp 121, a game state display lamp 123, and a driver DRV3 for generating a drive signal of the hit ball launching device 103.

Regarding the processing of the detection signal from the sensor in the pachinko machine control device 195, the unit control device simply removes noise from the detection signal, shapes it into a fixed pulse width, and outputs it as detection data of a launch sphere or a safe sphere. 18
Send to 0. That is, the pachinko machine control device 195 does not calculate the number of safe balls or the like, and such calculation is performed on the unit control device 180 side.

In the pachinko machine, noise is easily generated due to static electricity or the like. However, even if the pachinko machine controller CPU1 goes out of control due to noise or the like, since the reset circuit RST1 monitors the watchdog pulse, the watchdog periodically runs out due to runaway. When the pulse disappears, a reset signal is generated to initialize the CPU, so that runaway can be prevented.

The watchdog pulse can be easily generated by an interrupt from a timer counter in the CPU.

FIG. 25 shows a configuration example of the unit control device 180.

The unit controller 180 controls the card reader controller 188 and the pachinko machine controller 195 in order to enable a pachinko game to be played with a card. And a network controller 553 that establishes a transmission / reception right in a network and performs serial-parallel conversion of data under the control of the data transmission controller 551. The transfer of data between the controllers 190 and 551 and between the controllers 551 and 553 can be executed via dual port memories (RAMs) 550 and 552. Among them, the packet memory 552 is divided into a transmission data storage area and a reception data storage area, and has an adjustment function for making all transmission / reception data lengths the same (packetization), and a high speed data transmission ( (2.5 Mbps).

Each of the packet memories 552 has 256
It is composed of four pages each having a byte capacity, of which page 0 is used for transmitting a transmission request packet and page 1 is used for transmitting a regular data transmission packet. On the other hand, pages 2 and 3 are used alternately for data packet reception. Which page to use depends on the data transmission controller 5
51 instructs the network controller 553.
While the data transmission controller 551 is processing the received packet data, even if the next packet data is sent,
Since it is received by another page, all packets can be received reliably. A common reset circuit 555 is provided so that the controllers 551 and 553 can be initialized at the same time.

At the connection side of the network controller 553 with the management device 400, a signal conversion circuit 554 and a changeover switch 542 for performing waveform shaping of the received data and level conversion of the signal in order to increase the drive capability of the transmitted data. The transmission and reception signals are separated and coupled via the changeover switch 542 so as to be connectable to the optical connector 186 and to cope with the case where the transmission line of the low-layer network is constituted by a coaxial cable. The connection can be made to the branch circuit 540.
The optical transceiver 186 shown in FIG.
5 is connected.

Further, between the data transmission controller 551 and the network controller 553, a latch circuit 561 for storing the data reception result by the network controller 553 in response to a request from the data transmission controller 551, and a data transmission controller 551
Is a latch circuit 562 for storing a command such as a data transmission command to the network controller 553 and a latch circuit 563 for storing a low-layer network address, and three for displaying an abnormal communication control state in the unit controller 180. Latch circuit 5 for storing display data to monitor display 556 comprising an LED lamp
64 are provided. 557 is the latch circuit 56
This is a decoder that decodes addresses given to 1 to 564 and generates a selection signal.

On the other hand, a transceiver 571 for performing level conversion of transmission / reception data is provided between the unit controller 190 and the card reader control device 188, and a parallel / direct conversion of transmission / reception data is performed between the unit controller 190 and the pachinko machine control device 195. Multiplex transmission controller 572 and photoelectric conversion device 57
3 are connected.

Further, a latch circuit 574 for latching display data (segment data and common data) of a monetary amount and a number of balls, a purchase lamp, a game state display lamp, a hit ball A latch circuit 575 for latching a control signal for the launching device, an input signal from various switches provided in the pachinko machine 100 and the control unit 160 is loaded on the data bus 581 at a predetermined timing, and an output signal for displaying various lamps is latched. Input / output controller 576 and speaker 1 in control unit 160
A latch circuit 577 for latching audio data and the like generated from the memory 66 is connected.

Reference numeral 582 denotes a speech synthesis LSI, 583 a low-pass filter that cuts high-frequency components to improve sound quality,
Reference numeral 4 denotes an amplifier for adjusting the volume, of which a voice synthesis LSI is used.
Reference numeral 582 stores a plurality of audio data in a built-in EPROM, selects audio data in response to a selection signal (S0 to S3) given from the unit controller 190, and outputs the audio signal in synchronization with the start signal ST. And output is stopped by the reset signal R.

Note that 558 is the unit controller 19
0, a program ROM storing a control program, 55
A program ROM 9 stores a control program for the data transmission controller 551. 585 decodes an address signal output from the unit controller 190, and decodes the program memory 558 and the unit memory 55.
0, a decoder for forming selection signals for the latch circuits 574, 575, 577 and the input / output controller 576.

As described above, the unit control device 180
The management device 400, the card reader control device 188, and the pachinko machine control device 195 have information exchange windows on three sides, and perform control for playing pachinko games on the card CD under the control of the management device 400. At the same time, it has software for periodically transmitting pachinko machine game information generated as a game result to the management device 400. further,
In the unit controller 180 of this embodiment, the digit select signal (common signal) of the display data output from the unit controller 190 in order to drive the monetary value and the number of balls is periodically changed at intervals of, for example, 2 ms. Paying attention to the point that is output to the reset circuit 555
Is input as a watchdog pulse. The reset circuit 555 is configured to monitor the watchdog pulse in addition to the power-on reset and generate a reset signal when the pulse disappears.

Therefore, even if the unit controller 190 runs away due to noise or the like, the common signal is not output at normal intervals when the unit controller 190 runs away.
55 is activated to initialize the unit controller 190 and the data transmission controller 551, so that runaway is avoided.

At the same time, the unit controller 19
0 has an internal timer counter, and does not return ACK (positive) or NAK (negative) as a response to the transmission request within a fixed time (ex. 10 seconds), or a fixed time (ACK) after receiving the ACK. ex. 2 seconds), or when a disturbance in the internal memory (RAM) is detected, the common signal is forcibly fixed to a low or high level to reset itself. I can do it. In addition, the disorder of the internal memory can be easily determined by writing a specific code (A55A or the like) at a predetermined address in the memory at the time of initialization, and checking it by an interrupt process every 1 ms. Can be detected.

Further, the unit control device 180 of the embodiment
Means that the data transmission controller 551 operates for a certain time (5.12
Even if data cannot be transmitted within (sec), the unit controller 190 is initialized, and abnormal data is
It is handled so that it is not transmitted to 0. That is, in the embodiment, a watchdog counter area is provided in the unit memory 550, and the data transmission controller 55
1 sets a predetermined code FF each time data is transmitted to the management device 400, and sets the unit controller 19
0 counts down this counter by “1” every 20 ms. Therefore, if the data transmission controller 551 cannot transmit for more than 5.12 seconds, the watchdog counter of the unit memory 550 becomes "0".
, It can be determined that the data transmission controller 551 has gone down and reset itself.

Further, in this embodiment, a special RAM is used as the unit memory 550 such that when data is written at a predetermined address (7FE), a predetermined terminal INT rises.
Utilizing this function, the data transmission controller 551 writes data at the predetermined address to start the terminal INT at the time of system startup, and inputs the signal of the terminal to the unit controller 190 to store the unit memory. Synchronization between controllers for use of 550 is provided. Note that the specific terminal INT falls when the unit controller 190 reads data at the predetermined address.

On the other hand, when the system is started up, synchronization with the management apparatus 400 is performed by the data transmission controller 551. The data transmission controller 551 receives a line test command (described later) transmitted from the management apparatus 400, and responds to the reception. Is transmitted to the management device 400.

As described above, the pachinko machine control device 195 does not calculate the number of safe balls, etc., but performs such calculation on the unit control device 180 side. , A detection signal related to a game ball such as a safe signal and a signal from the purchase switch 113 are input. Unit controller 19
0 is based on these signals, the number of payout balls, the number of outgoing balls,
It calculates operation data such as the number of balls held and the amount of sales, generates operation information (game state) and monitor information relating to the pachinko machine 100, and transmits them to the transmission data area SDA (see FIG. 26
See).

The operation data and the like written in the unit memory 550 are transmitted by the data transmission controller 551 to the management device 400 through data communication.
Sent to The data sent from the management device 400 is also temporarily written into the reception data area RDA in the unit memory 550, and the unit controller 190 reads the data to receive the data. The unit memory 550 includes a communication area CCA for storing commands and status information for notifying the other controller that other transmission data and reception data are in the memory, and a working area UWA for each controller.
And a DWA and an inter-controller synchronization area CSA.

FIG. 26 shows the entire configuration of the unit memory 550, and [Table 1], [Table 2] and [Table 3]
2 shows a configuration example of a transmission data area SDA, a reception data area RDA, and a communication area CCA.

[0089]

[Table 1]

[0090]

[Table 2]

[0091]

[Table 3]

[0092]

[Table 4]

[0093]

[Table 5] The monitor information 1 shown in [Table 1]
As shown in [Table 4], a bit indicating that a test is being executed at system startup, a bit indicating initial value setting / unset, a bit indicating a hot code error, and a bit indicating a local network abnormality (for low layer and high layer) 2 bits), a bit indicating a gaming machine abnormality, and the like. The monitor information 2 is stored in the card reader 80 as shown in [Table 5].
It has a bit indicating an abnormality of 0.

Further, the operation information includes a bit indicating a stop state as shown in [Table 6], a bit indicating that the game is interrupted, a forced termination state by the management device 400 or the controller based on a communication error or illegal detection. , A bit indicating that a game is in progress, a bit indicating that the gaming machine is in a free state without a player, and the like.

[0095]

[Table 6] From the above [Table 6], the actual state of the pachinko machine 100 can be represented by the free state, 0000000000000001 during the game, 0000000000000010 at the time of forced termination reception, 0000000000000100 at the time of interruption, and 0000000000001000 at the time of the occurrence of the stop, 0000000000010000. Recognize.

FIGS. 27 to 33 show the control unit 160.
2 shows a specific configuration example of a card reader 800 for a pachinko machine provided therein.

At the front end of a box-shaped case main body 801 constituting the card reader 800, a front lid 802 having a card holding display section LED1 and a card insertion / ejection port 802a is attached.
An L-shaped bracket 803 for fixing in the storage frame 161 of the control unit 160 is provided on a side wall of the case body 801.
Are fixed at the four corners.

As shown in FIG. 28, a base plate 804 serving as a card transport path is disposed in the case main body 801. Above the base plate 804, a gap slightly larger than the thickness of the card CD is provided and supported in parallel with the base plate. Substrate 8
05,806 are attached.

A card insertion detecting sensor 808 composed of a motor 807 and a micro switch, and a shutter solenoid 8
09, a card insertion detection sensor 808 composed of a microswitch, a shutter solenoid 809, and reflection type optical sensors 810a and 810b for reading a security code are attached. In this embodiment, the sensors 810a,
Only one (810a) of the 810b is used, and the other sensor (810b) is provided as a spare so that the security code may be increased in the future.

The motor 807 and the shutter solenoid 8
09, a second roller shaft 811 is rotatably mounted, and the center of the second roller shaft 811 is a transport roller 81.
2 is provided, and one end of the second roller shaft 811 is made to be able to protrude outside from the side wall 801a of the case body, and a pulley 813 is fixed to the protruding end. Also,
A projector 814 that irradiates the card position detection sensor SNS1 with detection light is attached near the shutter solenoid 809, and the detection light of the second position detection sensor SNS2 is provided between the second roller shaft 811 and the motor 807. A translucent portion 815 that can transmit light is formed. Further, a light projector 816 for irradiating a detection light to the punch hole detection sensor SNSp is attached to a side of the motor 807, and a rotary encoder 817 is fixed to one end of a rotation shaft 807a of the motor 807, and Rotating shaft 807
The other end of “a” protrudes outside from the side wall 801 b of the case body 801, and a small-diameter pulley 818 is fixed thereto.

On the other hand, the first roller shaft 81 is placed on the support substrate 806 disposed on the opposite side of the card insertion / ejection port 802a.
9 is rotatably arranged, and a punch device 820 using a solenoid as driving means and a magnetic head 821 can be attached. A through-hole 822 is formed in the support substrate 806 corresponding to the position where the magnetic head is mounted so that the head surface can face downward when the magnetic head is inserted downward from above. A transport roller 823 is fixed to the center of the first roller shaft 819, and both ends of the shaft are made to be able to protrude to the outside from the side wall of the case, and pulleys 824 and 825 are attached thereto. A belt 826 is wound between the pulleys 818 and 825, and a belt 827 is wound between the pulleys 824 and 813. The rotational driving force of the motor 807 is transmitted to the first roller shaft 819 by the belt 826. And transmitted to a second roller shaft 811 by a belt 827.

Further, on the lower surface of the support substrate 806,
Third and fourth card position detection sensors SNS3, SN
Light projectors 828 and 829 that irradiate S4 with detection light are attached.

Above the support substrates 805 and 806,
The first interface board 830 is arranged so as to cover this, and is fixed to the side walls 801a and 801b of the case. The interface board 830 includes the control unit 1
An interface circuit is provided for receiving various control signals from a card reader control device 188 provided in the device 60 and for passing a read signal from a sensor or a magnetic head provided on the card reader side to the card reader control device 188. ing. Also, on the lower surface of the interface board 830,
A light projector 831 is provided at a position corresponding to the light transmitting portion 815, and a speed detection sensor 832 is provided at a position corresponding to the encoder 817.

On the other hand, on the base plate 804 disposed below the supporting substrates 805 and 806, an auxiliary roller 836 urged upward by torsion springs 834 and 835 is provided at a position corresponding to the transport rollers 812 and 823. 837 is mounted so that the face slightly emerges from the openings 841 and 842 formed in the base plate 804. The base plate 804 also has an auxiliary roller 838 urged upward by a torsion spring 836 at a position corresponding to the magnetic head 821 attached so as to face below a through hole 822 provided in the support substrate 806. It is mounted so that the face is slightly raised from the opening 843. At the same time, the projectors 814, 816,
Through holes 844 are formed at positions corresponding to 828, 829 and 831, respectively. Further, a concave portion 845 (see FIG. 30) is formed at the front end of the base plate 804 along the width direction, and a cylindrical shielding member 846 is placed thereon. The shielding member 846 is a card insertion / ejection port 802a.
In order to prevent dust from entering, and to act so that only cards having a certain rigidity or more by weight can be accepted.

On the lower surface of the base plate 804, a second interface board 848 is attached by screws. On this second interface board 848, a circuit for interfacing with the card reader controller 188 is provided. Floodlights 814, 831,
828, 829 and 816,
Fourth position detection sensor SNS1, SNS2, SNS3
SNS4 and a punch hole detection sensor SNSp are attached. Also, auxiliary rollers 833, 837, 838
Relief holes 8 at positions corresponding to
49 are provided.

The upper supporting substrate 8 corresponds to the cylindrical shielding member 846 placed on the front end of the base plate 804.
An empty space 851 which is slightly larger than the shielding member 846 is formed at the front end of the shutter 05, and when the supporting substrate 805 is arranged on the base plate 804, the shielding member 846 is vertically movably housed in the empty space 851. It has become.

Further, the frame 85 constituting the empty space 851
2, an opening 853 is formed in the rear wall, and the insertion detection switch 808 is disposed behind the opening 853 to move the movable contact 808.
a protrudes from the opening 853 into the empty space 851. The distal end of the movable contact 808a is usually located above the shielding member 846 as shown in FIG. 30, and when a card CD is inserted through the card insertion / ejection port 802a, the position shown in FIG. As described above, the movable contact 808a is rotated so that the card CD pushes the shielding member 846 upward, and the insertion detection sensor 808 is turned on.

The shutter solenoid 809 mounted on the support substrate 805 is disposed downward as shown in FIG. 31A, and a pin 809b formed at the tip of the plunger 809a is provided on the support substrate 805 in the solenoid demagnetized state. 31B, the card C is inserted into the corresponding hole 855 formed at the corresponding position on the upper surface of the base plate 804 as shown in FIG.
D is prevented from being inserted.

Although not particularly limited, the card reader 800 of this embodiment has an open rear wall so that the card can be ejected backward so that the card reader 800 can be used in a card issuing machine. Structured.

FIG. 32 shows the mounting positional relationship of various sensors and magnetic heads in the card reader.

The insertion detection sensor 808 is arranged on the side closest to the card insertion / ejection port 802a, and the first position detection sensor SN
S1 is disposed immediately before the transport roller. The shutter pin 809b is disposed between the insertion detection sensor 808 and the first position detection sensor SNS1, and the security code reading sensors 810a and 810b are disposed almost right beside the first position detection sensor SNS1. The second position detection sensor SNS2 is located behind the transport roller 812, the third position detection sensor SNS3 is located behind the transport roller 823, the fourth position detection sensor SNS4 is located at the innermost part of the card reader, and -4th position detection sensor SNS1
SNS4 are located on the same straight line.

Further, the punch hole detection sensor SNSp and the punch pin PP are disposed between the second position detection sensor SNS2 and the transport roller 823, and the magnetic head 821 is disposed between the transport roller 823 and the third position detection sensor SNS3. Have been.

FIG. 33 shows the timing of card detection by various sensors arranged in a positional relationship as shown in FIG. 32 when a card is inserted, and the timing of control signals to the motor 807 and the shutter solenoid 809. As can be seen from the figure, in the card reader 800 of this embodiment, when the card is inserted, the insertion detection sensor detects the insertion of the card CD, drives the motor 807 and the shutter, and uses the position detection sensors SNS1 to SNS4 to determine the position of the card. While detecting, the information on the card is read at a predetermined timing in the order of a security code, a punched hole, and a magnetic code.

In addition, since the relative distances between the various sensors and the punch pins are important for accurately performing processes such as reading a card and punching a hole, the components are accurately mounted so as to have a predetermined positional relationship. Have been.

FIG. 34 shows a card reader controller 188.
A specific circuit configuration example (see FIG. 23) is shown.

A card reader controller 188 is a card reader controller CPU comprising a microcomputer.
2, a transceiver TRV that performs level conversion of a data signal transmitted and received between the unit control device 180, and drivers DRV 11 and DRV that form drive signals for monitor displays 175 and 176 provided in the control unit 160.
V12, motor 807 and punching device 820 in card reader 800, magnetic head 821, LED lamp 16
7, a driver DRV13 for generating a control signal for driving the shutter solenoid 809, a driver DRV14 for driving a relay RLY for turning on / off the power supplied to the motor 807, read data of the magnetic head in the card reader 800, and various kinds of data. A waveform shaping circuit SMG including a Schmitt trigger circuit for shaping a waveform of a detection signal from the sensor;
Flip-flop circuits F / F1, F / F for latching respective read data of two tracks read by a magnetic head
2 and a built-in power-on reset circuit and a watchdog timer. A pulse periodically output from the controller CPU2 (shared with the reset pulses of the latches LT1 and LT2) is monitored as a watchdog pulse and reset when the pulse is interrupted. Reset circuit RS for generating signal
T2.

The card reader controller CPU 2
The ON / OFF signal from the setting unit 171 of the device provided in the control unit 160 and the card ejection switch SWc is input to the control unit 160.

The four light-emitting diodes constituting the monitor display 176 include a power-on display LED 11 that is lit while the power is on, and a card-in display that indicates that the card CD is in the card reader 800. LED
12 and an OK display LE illuminated when the control by the card reader controller CPU2 is normally executed.
Used as D13, the LED 14 is unused so that it can be used for any other monitor display.

On the other hand, the segment type monitor display 175
Is obtained by combining seven segments representing numbers and one dot display segment DT, as shown in Table 7 below.
, The contents of the abnormality of the card reader 800 are indicated by a code. The error codes in the right column of Table 7 are used when the card reader controller CPU2 notifies the higher-level control device of the contents of the abnormality when a corresponding abnormality occurs.

[0120]

[Table 7] The card reader controller CPU 2 operates according to a control program in the built-in ROM,
Based on the command from 0, the controller executes the card travel control, reads out the card data, checks the card data, and transmits the card number and the control information of the card reader 800 to the unit controller. Communication with the unit controller 180 is performed by a built-in serial communication circuit using the serial ports TX and RX. Card reader 8
The output of the control signal to the components constituting 00 and the input of the detection signal from various sensors are performed via an interface circuit 198 as shown in FIG.

The flip-flop FF2 for latching the magnetic data a on the track TRC2 of the magnetic recording unit MG of the card CD operates using the read clock b read from the track TRC1 and triggering the flip-flop FF1 as a sampling clock. Is done. The flip-flop FF1 is triggered by the read clock b and the CPU
The periodic signal c is output by being reset by the pulse e output from 2.

FIG. 35 shows a card reader control device 188.
5 shows a configuration example of an interface circuit 198 provided between the input and output components in the card reader 800.

In the figure, reference numerals SMG1 to SMG5 denote waveform shaping circuits including Schmitt trigger gates, REC1 and REC2 denote rectifier circuits, and MCCs.
1, MCC2 is a magnetizing current switching circuit, AMP1 to AMP4
Is an amplifier, MHD1 and MHD2 are magnetic heads, MT is a motor, SOL1 and SOL2 are solenoids, LED1 is a light emitting diode, DRV21 and DRV22 are drivers, S
NS11, SNS12, SNSp, SNS1 to SNS5
Is a sensor. CCC is a current switching circuit for switching the rotation direction of the motor MT, and VCC is a voltage switching circuit for switching the rotation speed of the motor MT.

The read clock signal of the read data read by the two magnetic heads MHD1 and MHD2 corresponding to the two tracks TRC1 and TRC2, respectively, is amplified by the amplifiers AMP1 and AMP3.
The data is rectified by the rectifier circuits REC1 and REC2, and further sent to the card reader controller 188 as rectangular waves through the waveform shaping circuits SMG1 and SMG3.

On the other hand, the write data and write clock supplied from the card reader control device 188 pass through the waveform shaping circuits SMG2 and SMG4 and the magnetizing current switching circuit MCC.
1, MCC2 and write data “1”,
The direction of the head drive current is switched according to “0” and amplified by the amplifiers AMP2 and AMP4, and the magnetic head MHD is amplified.
1, MHD2.

In order to drive the motor MT, the current switching circuit CCC changes the direction of the current flowing to the driver DRV21 based on the normal rotation signal and the reverse rotation signal given from the card reader control device 188, and changes the direction of the driver according to the speed switching signal. The voltage applied to the motor MT is switched by the DRV 21.

On the other hand, the security code reading sensor S
NS11 (810a), SNS12 (unused), punch hole detection sensor SNSp, position detection sensors SNS1 to SN
S4: The detection signal of the speed detection sensor SNS5 (821) is shaped by the waveform shaping circuit SMG5 and then supplied to the card reader control device 188, where the insertion detection switch 8
The detection signal 08 is noise-cut by the low-pass filter LPF, and is then shaped by the waveform shaping circuit SMG5.

FIG. 36 shows a card reader control device 188.
2 shows the timing of writing and reading magnetic data.

In the signals shown in FIG. 14, (A) to (D) relate to write data information, (E) to (G) relate to write clock information, (H) to (J) relate to read data information, and (K). ~
(M) shows the signal waveform of each part regarding the read clock information. 34 (N) to (R) show timings of signals indicated by reference symbols a to e in the card reader control device 188 of FIG.

Of these, the signals of (H) and (K) are
Amplifier AMP1 Constituting Interface Circuit of FIG.
AMP3, the output signals of (I) and (L) are the output signals of rectifier circuits REC1 and REC2, and the signals of (J) and (M) are waveform shaping circuits SMG1.
And SMG3 output signals, respectively.

In this embodiment, a so-called NRZI method is employed in which the polarity is inverted when the data is "1" and the polarity is not inverted when the data is "0" or no signal. Has adopted.

Accordingly, the CPU output, the write current, and the signals (B), (C), and (D) indicating the magnetization state are respectively changed when the internal data (A) of the CPU changes from "0" to "1". It is inverted.

On the other hand, when the data written as described above is read by the magnetic head MHD2, the magnetization state (D)
The output of the amplifier AMP1 changes to + or-in accordance with the direction of magnetization when the signal changes, so that the card reader controller CPU2 corresponds to the signal (J) obtained by waveform shaping the output of the amplifier AMP1 at the rise of the read clock b. When the read data a is taken into the latch F / F2, if the signal a (N) is at a high level, it is recognized as data "1", and if the signal a is at a low level, the data is "0". (See (S) of FIG. 36).

In this embodiment, the recording density of magnetic data on the card CD is 4.134 bits / mm (= 105 BP).
I) and the card transport speed was 300 mm / sec.
The pulse cycle of the read clock data is about 806 μS. Therefore, when magnetic data is written by the CPU 2, the cycle T of the CPU output (E) related to the write clock is used.
0 is output as twice the clock pulse (1.612 mS).

FIG. 37 and FIG. 38 show the card issuing machine 2
00 shows a configuration example.

The card issuing machine 200 of this embodiment comprises a bill validator 210 for recognizing bills for card purchase,
Issuer 700 that prints an amount corresponding to the inserted bill and issues a card, bill dispenser 230 for dispensing bills as change, various displays 221 to 225, and overall control and management of card issuing machine 200 Apparatus 400
And a unit control device 280 for performing data communication between them.

[0137] Corresponding to the bill discriminating apparatus 210, the front panel 201 which can be freely opened and closed is provided with a bill insertion slot 211, a purchase selection switch group 212 and a money amount display 213. Therefore, when the player first inserts a bill through the bill insertion slot 211, the inserted amount is displayed on the amount display 213. Then, by pressing a switch corresponding to a desired purchase price from the purchase selection switch group 212, a card CD corresponding to the desired purchase price is issued from the card ejection port 202 of the issuing device 700. Also,
Each of the purchase selection switch groups 212 is constituted by a switch with a built-in lamp, and when a bill is inserted, three switches are selectable within the range of the inserted money (three switches for 3,000 yen,
The built-in lamp corresponding to 5) is turned on.

[0138] When a bill is inserted from the bill insertion slot 211 of the card issuing machine 200 and the purchase amount is determined by the purchase selection switch 212 and a balance is generated, the bill dispensing device 230 for paying back the balance is used to store the bill. The bill storage tank is provided so as to discharge bills corresponding to the balance from a bill payout port 232 provided on the front panel 201.

On the front panel 201 of the card issuing machine 200, an in-progress lamp 221 indicating that the card can be issued, an issuance stop lamp 222 indicating that the card cannot be issued, and a bill inserted into the bill insertion slot 211. A bill insertion display 223 for indicating whether or not the card is accepted, a card issuance display 224 for notifying the card issuance state, and a bill dispensing display 225 for notifying the state of disbursement of the balance. Also, inside the front panel 201 of the card issuing machine 200, a monitor display 206 for displaying the type (number) of the abnormality of the issuing machine by a two-digit number, and resetting the display of the monitor display 206. And a reset button 207 for resetting.

Further, the card issuing machine 200 of this embodiment
In order to distinguish each of a plurality of (several tens) issuing machines installed in a game arcade and to allow the management apparatus 400 to identify the issuing machine that has issued a specific card, the machine number setting device 205 is internally provided. The serial number set by the setting unit 205 is sent to the management device 400, and is used for generating a transmission address in data communication and creating a data file for each issuing machine.

On the other hand, the issuing device 700
01, take out the blank cards stocked one by one and send them to the card reader 800 first.
The card number and identification code (store code), issue date code, check code, etc., which are calculated and sent by the management device 400 to the magnetic recording unit MG of D, are recorded,
After punching a hole at the issued punching position PH1 (see FIGS. 2, 3 and 4) with the punching device 820 in the card reader 800, the printing device 750 issues a date of issuance and a serial number n.
Then, the purchase amount is printed and discharged from a card issuing port 202 provided in the front panel 201. The issuance serial number n is determined by the management apparatus 400, which has received an application for card purchase from the card issuing machine 200, in the order in which it is received for purchase applications from a plurality of card issuing machines under its control. A code assigned to each card issuing machine and obtained by performing the code conversion processing such as the rearrangement of bits based on the serial number n is recorded as a card number on the magnetic surface of the card CD. The information on the card is recorded in a file in the management device 400.

In order to enable generation of a card number from the serial number n, the control program of the management device 400 is provided with a card number generation routine and a code conversion routine, and is read from the card CD. In order to confirm the coincidence between the card number and the issue serial number n, an inverse conversion and inverse calculation routine is provided.

The card issuing machine 200 of this embodiment
The card reader 800 records the magnetic data and prints the card with the issue serial number n, the issue date, and three “0” excluding the thousands digit of the purchase amount printed, and the card is kept on standby. When a purchase switch is pressed, a thousand-digit number is printed and discharged, thereby shortening the apparent issuance time.

FIG. 39 is an overall perspective view of an issuing device 700 incorporating a card reader, and FIG. 40 shows a schematic configuration example of the issuing device 700.

The issuing device 700 of this embodiment includes a card ejection device 710 for taking out cards one by one from a card tank 701 in which a large number of cards whose magnetic recording portion MG and print display portion PRT are blank are stored. And a card reader 800 disposed behind the card reader 800, a card reversing device 740 disposed further behind the card reader 800, and a card reader 80
0, and a card deriving device 770 disposed in front of the printing device 750, and is controlled by a card issuing control device 790 disposed above the card reader 800. Has become.
The card reader in the issuing device 700 of this embodiment may have the same structure and function as the card reader 800 for the pachinko machine.

The card reader for the issuing machine is different from the card reader for the pachinko machine in that (1) it is necessary to have a function of recording magnetic data, and (2) the card can be ejected backward. It is necessary to be. Of these, regarding (1), as shown in FIG. 35, the interface circuit 198 shapes the waveform of the write data signal with the waveform shaping circuits SMG2 and SMG4 and the magnetic current switching circuit MCC.
1 and MCC2, and magnetic heads MHD1 and MHD1
There is no problem because the HD2 can write as well as read magnetic data. As mentioned in the description of the structure of the card reader 800 for the pachinko machine, FIG.
The card reader 800 shown in FIGS. 7 to 30 has an open rear wall of the case so that the inserted card CD can be ejected backward. Therefore, the same issuing device 700 as the card reader 800 for the pachinko machine can be used as the issuing device 700 of this embodiment.

On the other hand, the card tank 701 is formed of a U-shaped frame having a space of the same size as the card, and is fixed to the upper end of the side wall 711 of the card removing device 710 by bolts. On the card stored in the card tank 701, a pressing member 702 for applying a certain pressure to the card and ensuring the removal of the card is placed. Notches 702a are formed on the right and left sides of the pressing member 702 so as not to be detected by a sensor 703 for detecting the presence or absence of a card in the tank. The blank card CD stored in the card tank 701
Is mounted on the front half of the base substrate 711 of the card removal device 710 as shown in FIG. This base substrate 711 has openings 711a, 711 along the center line.
b, 711c are formed, and the first transport roller 712, the second transport roller 713, and the third transport roller 714 are arranged so as to slightly protrude above the opening. A cutout 711d is formed at the front end of the base substrate 711 so that the operating piece 703a of the card presence / absence detection sensor 703 can be seen from below.

Further, a support plate 715 orthogonal to the base plate 711 is disposed substantially at the center above the base substrate 711, and is fixed to a side wall 716 of the card removal device 710. Then, on the front surface of the support plate 715,
A bracket 718 having a stopper 717 facing the base substrate 711 with an interval of one card is mounted. Further, a take-out motor 719 for driving the transport rollers 712 to 714 is disposed behind the support plate 715, and is fixed to the side wall 716.

A drive pulley 721 is connected to the rotation shaft of the take-out motor 719 via a speed reduction mechanism 720, and the drive pulley 721 and the transport rollers 713 and 7
14 between the driven pulleys 722 and 723 attached to the ends of the rotary shafts 713a and 714a
4 is wound. Further, the second transport roller 71
A clutch disc 725a is mounted on the rotating shaft 3 and a second clutch disc 725b is rotatably arranged facing the disc 725a. Further, the pair of clutch disks 725a,
A clutch lever 727 having, at one end, a roller 726 that can abut on the outer periphery of 725b is swingably attached to the side wall 716. And this clutch lever 727
Is connected to a plunger 729a of a clutch solenoid 729 via a spring 728. When the solenoid 729 is excited, the clutch lever 727 is rotated and the roller 726 is moved to the clutch disk 725a.
And 725b are simultaneously contacted and transmit rotational force,
When the solenoid 729 is turned off, the rotational force is shut off. Further, a pulley 730 is fixed to the rotating shaft of the clutch disc 725b, and a belt 732 is provided between the pulley 730 and the pulley 731 fixed to one end of the rotating shaft 712a of the first transport roller 712.
Is wound. Therefore, the rotational force of the take-out motor 719 is transmitted to the first transport roller 712 via the clutch mechanism (725, 726) only while the clutch solenoid 729 is excited.

Further, the first transport roller 712 is mounted eccentrically with respect to its rotary shaft 712a, and its upper surface is usually lower than the base substrate 711, and the rotary shaft 712a rotates by 180 °. Then the opening 7
It protrudes slightly upward from 11a.

The issuing device 700 of this embodiment is
When the purchase selection switch 212 is operated after the bill is inserted,
The take-out motor 719 is rotated, and then the clutch solenoid 729 is turned on for a certain period of time.
Is rotated once. Thereby, the first
The transport roller 712 is eccentrically rotated, and sends out the card in the card tank 701 above the first transport roller 712 while pushing up the card. At this time, since the pressing member 702 is placed on the card CD and a constant pressure is applied, the lowermost card is separated from the card group in the tank by the frictional force with the roller. In addition, since the stopper 717 having an interval of one card and the base substrate 711 is provided at the rear, feeding of two cards is prevented.

In this way, only one card taken out of the tank is sent out toward the rear card reader 800 by the second and third transport rollers 713 and 714 that are being rotated while the take-out motor 719 is rotating. It is.

At the rear end of the card removal device 710, a traveling position detection sensor CPS1 is provided so as to detect the sent card.

In addition, above the third transport roller 714,
A press roller 734 for preventing the card from floating is provided.

The card removed from the tank 701 by the card removal device 710 is stored in the card reader 800.
Then, an identification code, a card number, and the like are written in the magnetic recording unit MG, and a punch hole is made at an issuance hole punching position by an internal punching device 820, and then sent out to a card reversing device 740 at the rear. Below the card reader 800, a case 705 for accommodating perforated pieces, that is, punch waste is arranged.

Card reader controller 2 for issuing machine corresponding to controller 188 of card reader 800 for pachinko machine
88 is provided in the card issuance control device 790.

The card sent to the card reversing device 740 first has a belt 742 wound around transport rollers 741a, 741b and 741c, and a transport roller 743a and 743.
b is conveyed along the S-shaped traveling path while being sandwiched between the belt 744 wound around the roller b and the transport roller 746 while pushing the traveling path switching piece 745 disposed at the exit as shown by the broken line a.
a, 746b, and 746c are sandwiched between the belt 747 wound around the belt 747 and the belt 742, and are once sent upward. When the card passes through the runway switching piece 745, the switching piece 74
5 is rotated back from the position indicated by the broken line to the position indicated by the solid line by the tension of the spring 745a, and drives the belt 742 when the rear end of the card is detected by the traveling position sensor CPS2 disposed above the position. Traveling motor 7
06 is reversed. As a result, the card changes its direction and starts to be conveyed downward. Then, the transport roller 748
a, a belt 749 wound around 748b, 748c,
The direction is gradually changed by being sandwiched between the belts 747, and finally the sheet is fed forward in the horizontal direction.

The belts 742 and 749 are driven by a belt 707 directly driven by a traveling motor 706 and a belt 708 linked therewith. The running motor 70 is provided on the belts 744 and 749.
The driving force of No. 6 is not transmitted, and the card rotates with the frictional force as the card moves.

The belt 707 is also wound around a pulley integrated with a transport roller 771 of a card ejecting device 770 described later, and the card is discharged by the driving force of the traveling motor 706.

Further, the rotating shaft 709 of the transport roller 748c is protruded to the side, and a knob 709a is fixed to an end thereof as shown in FIG.
By manually turning the card, the card can be manually moved while the traveling motor 706 is stopped, and the card having a paper jam can be removed. Card reversing device 7
A travel position sensor CPS3 is disposed at the end of the drive 40. When the sensor detects the rear end of the card, the travel motor 706 is stopped.

The card sent from the card reversing device 740 enters the printing device 750, and is detected by the traveling position sensor CPS4. Then, the transfer motor 751 in the printing device 750 is driven, and the driving force is applied to the belt 7.
62 and the transfer roller 752a via the gear group 763,
The card is transferred to the press roller 752b, and the card is held between the pressing rollers 753a and 753b disposed above the card and moved forward. In front of the transfer rollers 752a and 752b,
Transfer rollers 754 and 755 are arranged along the traveling path,
Above it is a print head 756 such as a thermal head.
Are arranged so as to be able to ascend and descend along the guide pins 757. A return spring 758 is provided around the guide pin 757.
Is inserted.

Reference numeral 758 denotes a print head raising / lowering motor. The rotation of the motor 758 is reduced and transmitted to the driven shaft 759. A detection piece 760 having a notch is fixed to the driven shaft 759, and rotation position sensors 761 a and 761 b are arranged to face the periphery of the detection piece 760. Although not shown, the rotational force of the lifting motor 758 is transmitted to the print head 756 via, for example, a cam fixed to the driven shaft 759 and a tappet abutting on the outer periphery of the cam, thereby raising and lowering the same. At this time, the lifting motor 75
Numeral 8 rotates the driven shaft 759 by 180 ° in one operation. That is, the elevation motor 758 is always connected to the detection frame 76.
The notch of 0 stops rotation at a position facing the sensor 761a or 761b. When the traveling position sensor CPS4 detects a card and operates the elevating motor 758, the sensor 761a or 761b detects the detected frame. When the notch 760 is detected, the rotation of the motor is stopped. As a result, the print head 756 is lowered when the card is detected by the traveling position sensor CPS4, and when printing is completed, the elevating motor 758 is operated again to rotate the driven shaft 759 by 180 °, whereby the print head 756 is raised and stopped. I do. At the exit of the printing device 750, a traveling position sensor CPS5 is provided.
5 detects the leading end of the card, operates the traveling motor 706 in the same direction (reverse direction) as before, and
Belt 772 wound around 71a, 771b, 771c
When the sensor CPS5 detects the rear end of the card, the transport motor 751 in the printing device is stopped. As a result, the card sent from the printing device 750 is immediately conveyed into the card deriving device 770 in front.

In the card deriving device 770, FIG.
As described in detail below, transport rollers 773, 774a, and 774b are disposed below the belt 772, and a belt 775 is wound around the transport rollers 774a and 774b. Moreover, in this embodiment, the conveying roller and its belts 772 and 775 are provided in two rows only in this card deriving device so that the ejection can be performed reliably. A card issuing port 202 is disposed in front of the conveyance path formed by the belts 772 and 775, and a traveling position sensor CPS6 is disposed immediately before the card issuing port.

Further, between the transport rollers 773 and 774b, a track switching member 7 rotatable about a support shaft 776 is provided.
77 are provided. The runway switching member 777 is normally positioned at the lower end by a spring 778 as shown by a broken line B in FIG. 40, and guides the card sent from the printing device 750 toward the card issuing port 202.
If the card is not valid or cannot be correctly recorded on the magnetic recording unit due to scratches, the card is guided to the lower confiscation tank 780 by the runway switching member 777. When the card is correctly written, the switching member 777 is rotated downward as shown by the solid line in FIG. Then, the card sent from the printing device 750 is guided to the card issuing port 202. A confiscation tank 780 is provided below the transport rollers 774a and 774b.
The card guided downward by the runway switching member 777 located in the normal state is stored in the confiscation tank 780.

A notch 781a is formed in the rear wall 781 of the confiscation tank 780, and a sensor 782 is disposed so as to face the notch 781a. This sensor 782 is a light receiver and a corresponding light projector 783
Is disposed between the pair of belts 775, the detection optical axis is set to be oblique, and detects cards entering the confiscation tank 780, and when the number of cards in the tank exceeds a certain amount, the The upper end blocks the detection optical axis, so that it is possible to detect that the detection optical axis is full. Further, the confiscation tank 780 is slidably mounted on a plate 784 arranged obliquely below the tank 780, and a guide pin 785 for engaging with a long hole 784a formed in the plate 784 is fixed to a lower surface thereof. It is always urged rearward by a spring 786 stretched between the guide pin 785 and the rear end of the plate 784.

When the end of the card passes and the traveling position sensor CPS6 or the detection sensor of the confiscated card changes from on to off, the card dispensing device 770 operates.
06 is turned off to stop the discharge or confiscation operation.

A card issuance display 787 indicating the progress of card issuance work in the issuance device 700 is provided above the card issuance slot 202.

Further, the issuing device 700 of this embodiment is
As shown in FIG. 39, it is placed on a fixed base 791 on a base 793 supported by left and right rails 792a and 792b so as to be slidable in the front-rear direction. A power supply box 794 having a built-in power supply
On the front side of 4, a counter 795 for displaying the number of cards issued and a spare counter 796 for displaying the number of confiscated cards are provided.

Reference numeral 797 denotes a handle used to slide the entire issuing device mounted on the fixed base 791 forward, and reference numeral 798 denotes an operation button for locking the slide mechanism.

FIG. 43 shows a configuration example of a control system of the card issuing machine 200 configured as described above.

In the figure, 790 is a card issuing control device, 280 is a unit control device, 288 is a transport motor 807 which is a component of the card reader 800,
A card reader control device that controls the magnetic head 821, the punching device 820, and the like. Reference numerals LMP1 to LMP5 denote lamps built in the selection switch group 212 for the purchase amount, corresponding to the switches turned on. The operation button is illuminated from behind by turning on a lamp.

The control system of this embodiment is roughly divided into a control system by the unit control device 280 and a control system by the card issue control device 790. Selecting means, communicating means for transmitting valuable data to the management device 400 and receiving a card number in place of the valuable data, controlling means for paying out coins, and status display means indicating the issuing processing state. The card issuance control device 790 includes a card ejection device 710, a card reversing device 740, a printing device 750, and a card deriving device 770, which constitute the above-described issuing device 700, and a card reader 800 that is in charge of checking a card and recording magnetic data. In charge of the overall control of the control device 288. Communication between the unit controller 280 and the card issuing controller 790 is performed by serial communication.

On the other hand, the unit control device 280 can be connected to the low-layer network communication line 510 made of an optical cable or a coaxial cable via the optical transceiver 185 in order to transmit and receive data such as a card number to and from the management device 400. Has been. The card issuing machine 200 according to the present embodiment allows the user to perform operation procedures by lighting or blinking status display means including various displays 221 to 225 provided on the front panel 201 by the unit control device 280 in accordance with the card issuing procedure. In addition, the card and the change of the discharged card are prevented from being forgotten.

That is, when the power of the card issuing machine 200 is turned on and the preparation for card issuance is completed, the unit control device 280 first turns on the issuance display 221 provided on the front panel 201, and displays the bill insertion display. 223 is blinked to display a message prompting the insertion of a bill to notify the outside that it is in a bill insertion waiting state. When a bill is inserted into the bill insertion slot 211 in this state, the unit controller 28
0 displays a number corresponding to the inserted amount on the amount indicator 213 and turns on the purchase lamps LMP1 to LMP5 built in the purchase selection switch 212 up to the amount corresponding to the inserted amount. That is, the lamp LMP1 for 1,000 yen, the lamp LMP1 to LMP3 for 3,000 yen, and the lamp LMP1 for 5,000 yen
ＬLMP5 is turned on to clearly indicate the operable switch. When any one of the valid purchase selection switches 212 is turned on in this state, the bill insertion display 223 is turned off, and the card issuance display 224 near the card issuance slot 202 is blinked instead, and the card is ejected. To the user.

Then, when the card is actually ejected from the card issuing slot 202, the unit control device 280 turns off the amount indicator 213 and the purchase lamps LMP1 to LMP5. At this time, if there is a change, the bill payout display 225 is blinked to pay attention, and the change is paid out. When there is no change, the bill payout indicator 225 is kept off. When the card is ejected, if the user removes the card ejected to the card issuing slot 202, the blinking of the card issuing display 224 is stopped and the light is turned off.

On the other hand, when there is change, the bill payout display 2
30 detects the removal of change and receives the payout completion signal sent, and then turns off the bill insertion indicator 223.

Table 8 shows the state transition of various indicators on the front panel 201 by the unit controller 280.

[0178]

[Table 8] In the table, ○ indicates lighting, × indicates no light, Δ indicates blinking, D indicates numerical display according to the inserted amount, and B indicates turning on a lamp corresponding to the amount. Table 8 also shows how the bill insertion state of the bill insertion slot 211 is in each state. This indicates that the next bill cannot be inserted until the card and change are removed.

FIG. 44 shows an example of the configuration of the unit control device 280.

The unit control device 280 of the issuing machine includes a card reader control device 288 and a card issue control device 79.
0, a unit controller 290 for comprehensively controlling 0.
A data transmission controller 551 for controlling data transmission with the management device 400;
A network controller 553 and the like perform establishment of transmission / reception rights in a network and serial / parallel conversion of data under the control of 51, and the communication system is exactly the same as the unit controller 180 of the pachinko machine. That is, the transfer of data between the controllers 290 and 551 and between the controllers 551 and 553 can be executed via the dual port memories (RAM) 550 and 552. Of these, the memory 552
Is divided into a transmission data storage area and a reception data storage area, and measures an adjustment function for making all transmission / reception data lengths the same (packetization) and speeds up data transmission (2.5 Mbps). It has a buffer function for it.

Each of the packet memories 552 has 256
It is composed of four pages each having a byte capacity, of which page 0 is used for transmitting a transmission request packet and page 1 is used for transmitting a regular data transmission packet. On the other hand, pages 2 and 3 are used alternately for data packet reception. Which page to use depends on the data transmission controller 5
51 instructs the network controller 553.
While the data transmission controller 551 is processing the received packet data, even if the next packet data is sent,
Since it is received by another page, all packets can be received reliably. A common reset circuit 555 is provided so that the controllers 551 and 553 can be initialized at the same time.

At the connection side of the network controller 553 with the management device 400, a signal conversion circuit 554 and a changeover switch 542 for performing waveform shaping of the received data and level conversion of the signal in order to increase the drive capability of the transmitted data. The transmission and reception signals are separated and coupled via the changeover switch 542 so as to be connectable to the optical connector 186 and to cope with the case where the transmission line of the low-layer network is constituted by a coaxial cable. The connection can be made to the branch circuit 540.
An optical transceiver 185 is connected to the optical connector 186.

Further, between the data transmission controller 551 and the network controller 553, a latch circuit 561 for storing the data reception result by the network controller 553 in response to a request from the data transmission controller 551, and a data transmission controller 551
There are a latch circuit 562 for storing a command such as a data transmission command to the network controller 553 and a latch circuit 563 for storing a low-layer network address, and three latch circuits 563 for displaying an abnormal communication control state in the unit control device 280. Latch circuit 5 for storing display data to monitor display 556 comprising an LED lamp
64 are provided. 557 is the latch circuit 56
This is a decoder that decodes addresses given to 1 to 564 and generates a selection signal.

On the other hand, the point that the unit controller 280 of the issuing machine differs from the unit controller 180 of the pachinko machine 100 is that the unit controller 290 does not directly communicate with the card reader controller 288 and the card issuing controller 790 Is to do it through Therefore, a transceiver 571 that performs level conversion of transmission / reception data is connected between the unit controller 290 and the card issuing control device 790.

The unit controller 290 includes:
An input / output controller 576 for placing input signals from the unit number setting unit 205 and the reset switch 207 on the data bus 581 at a predetermined timing and latching drive signals for displaying various lamps such as the in-progress display 221.
And input signals from the bill validator 210, the bill dispenser 230, and the purchase selection switch 212 on the data bus 581 at a predetermined timing, and latch the control signals to the bill validator 210 and the bill dispenser 230. An output controller 578 is connected.

The control signal from the unit controller 290 to the bill validator 210 includes an instruction signal for storing a bill determined to be a true bill in a safe while distinguishing between 10,000 yen, 5000 yen, and 1000 yen, and There is an instruction signal for enabling or disabling insertion of a bill into the bill insertion slot.

The input signal from the bill validator 210 to the unit controller 290 includes a signal when the inserted bill is determined to be a true 10,000 yen bill and a signal when the inserted bill is determined to be a true 5000 yen bill. There is a signal when the inserted bill is determined to be a true 1000 yen bill, an alarm signal output when the bill is pulled out toward the bill insertion slot after the bill determination, and insertion of the bill, and the bill is identified. There is a signal indicating that the banknotes are being stored, a signal indicating that banknote jam has occurred, and a signal indicating that the banknote storage in the safe is full.

On the other hand, the control signals from the unit controller 290 to the bill dispenser 230 include an instruction signal for setting the number of bills to be dispensed by a binary code and an instruction signal for executing the dispensing of bills based on the set number of sheets. And an instruction signal for clearing the display of a monitor display (not shown) for displaying the payout execution result.

The input signals from the bill dispenser 230 to the unit controller 290 include a signal output each time one bill is dispensed and a signal output when an abnormality occurs in the dispensing apparatus and the dispensing operation cannot be executed. Alarm signal, a signal indicating that the remaining amount of bills in the bill storage unit has become 20 sheets or less, a signal indicating that the bill dispensing operation is being performed, and the bill dispensing operation is completed. There is a signal indicating that the bill at the issuing port has been removed.

Further, the unit controller 290 includes decoders 586, 587 and a decoder driver for dynamically displaying an amount display 213 for displaying the purchase amount and a monitor display 206 for displaying a number indicating the type of abnormality of the issuing machine. 588, 589 and a data bus 581.

[Table 9] shows an example of the error numbers displayed on the monitor display 206, their contents, and processing.

[0192]

[Table 9] In Table 9 above, when an error marked with an asterisk occurs, the system is brought down and reset.
When the error display is blinking, it indicates that the reset button needs to be pressed after the error recovery processing.

Note that 585 is the unit controller 29
The address signal output from 0 is decoded and the program memory 558 and the unit memory 550, the input / output controllers 576 and 578, the decoders 586 and 587,
This is a decoder for generating a selection signal for the decoder drivers 588 and 889.

Further, the unit control device 2 of this embodiment
In 80, of the display data output from the unit controller 290 to drive the money amount display 213, the digit select signal (common signal) periodically output at intervals of 2 ms is sent to the reset circuit 555, Input as a dog pulse. The reset circuit 555 monitors the watchdog pulse in addition to the power-on reset, and generates a reset signal for each controller 290, 551, 553 when the pulse disappears.

As described above, the unit control device 280
The management device 400 and the card issuance control device 290 have information exchange windows in two directions, and perform control for issuing a card under the control of the management device 400 and generate information as a result of the issuance process. And software for periodically transmitting operation information of the issuing machine to the management device 400.

Transmission and reception of data with the management device 400 are performed via the unit memory 550 as in the case of the pachinko machine 100. The configuration of the unit memory 550 is exactly the same as that of the pachinko machine (see FIG. 26), and is used to inform the other controller that the transmission data area SDA, the reception data area RDA, and the transmission data and the reception data are in the memory. , And a shared data area CDA for storing status information.

Tables 10 and 11 show examples of the structure of the transmission data area SDA and the reception data area RDA in the unit memory 550, respectively. The configuration of the communication area CCA is exactly the same as that of the unit memory of the pachinko machine (see [Table 3]).

[0198]

[Table 10]

[0199]

[Table 11] The hot code shown in the above [Table 10] is stored in the unit memory 5 by the management device 400 when the system starts up.
Within the 50 transmission areas SDA, for example, 010101 ...
A code No. 01 is written and sent to the management device 400 periodically to check whether or not the RAM data is destroyed due to noise such as static electricity, so that abnormalities in the transmission data can be detected quickly.

As shown in [Table 12], the monitor information 1 shown in [Table 10] includes a bit indicating that a test is being executed at the time of system startup, a bit indicating initial value setting / not set, and a hot bit. It is composed of a bit indicating a code error, a bit indicating an abnormality in the local network (transmission cable 500) (two bits for a low layer and a high layer), a bit indicating an abnormality in an issuer, and the like.

As shown in [Table 13], the monitor information 2 includes a bit indicating a failure of the card reader, a bit indicating the presence or absence of a card, a bit indicating a state in the banknote tank, a bit indicating a jammed banknote, and a bit indicating a banknote jam. , A bit indicating the state of the balance dispenser in the bill tank, a bit indicating abnormality of the balance dispenser, and the like.

[0202]

[Table 12]

[0203]

[Table 13] FIGS. 45 to 48 show a configuration example of the above-described settlement machine 300.

The payment machine 300 of this embodiment has a built-in card reader for reading the card number recorded in the magnetic recording section MG of the inserted card CD and checking the code, and receives data from the management device 400. Card payment device 310 for collecting the card after the payment, a bill dispenser 321 and a coin dispenser 325 for refunding an amount corresponding to an unused amount remaining unused for the card.
And a printer 330 for issuing a receipt printed with the number of balls possessed by the game, and various indicators 303, 304, and 3
41, 342 and a unit control device 350 for controlling the entire settlement machine 300.

[0205] The settlement machine 300 is configured such that the upper panel 301 is rotatable up and down.
Corresponding to 0, a card insertion slot 302 is provided at the front end of the upper surface panel 301, and a ball number display 303 for displaying the number of awarded balls (number of possessed balls) and an unused amount are provided on the upper surface of the upper surface panel 301. Is displayed. In addition, the settlement machine 300 of this embodiment has a flat upper surface so as to constitute a counter installed in a pachinko parlor, and has a ball number display 303 and an amount display 304.
Are provided, one of which is inclined forward to make it easier for a player to read, and the other is inclined backward to make it easier for a staff member inside the counter to read. Moreover, the upper part of the ball number display 303 and the amount display 304 is covered with a transparent plate such as a glass plate. A display reset switch 30 for clearing the display on the display to "0" is provided on the rear side of the upper surface of the upper panel 301.
5 are provided. The player first enters the card slot 30
When a card is inserted from Step 2, the card reader 800 in the checkout machine 300 reads the card number recorded on the magnetic surface of the card CD, sends the card number to the management device 400, and receives data relating to the card. Then, the amount indicator 304
Display the unused amount, and display the number of balls 303
, The number of obtained balls is displayed, and the printer 330 issues a receipt on which the unused amount, the obtained number of balls, the history data, and the like are printed. Further, the inserted card in the card reader 800 is formed into a punch hole (adjusted hole) at a predetermined punch position PH5 by a punch, and then discharged into the internal card collection tank 314.

In this embodiment, a recording head is not required for the card reader of the settlement machine 300. However, a recording head is provided to erase and discharge the data on the magnetic surface of the settlement card. Thus, the decoding of the card number conversion method may be disabled, and the forgery of the card may be prevented.

As a card reader, the pachinko machine 100 is used.
The card reader 800 (see FIG. 27) is used as it is, and the card can be ejected to the rear similarly to the card reader for the issuing machine. A card collection tank 314 is disposed behind the card reader 800. . Printer 33
In the case of 0, a blank sheet stocked in a roll state is pulled out, the date of issue, the number of obtained balls, the amount of unused money, the card history, and the like are printed on the surface of the sheet. The paper is discharged from the receipt issuing port 331 opened at the end.

At the same time, money corresponding to the unused amount is paid out from the balance payout device.

[0209] The balance dispensing device includes a bill dispensing device 321 for dispensing bills and a coin dispensing device 325 for dispensing 100 yen coins.
Is provided with a bill discharge port 322 and a coin payout port 326 corresponding to the coin payout device 325. In addition, in the settlement, a fraction of less than 1,000 yen is generated as unused money, and therefore, a coin dispenser 325 that pays out coins of 100 yen unit as described above is required.

Further, the upper panel 3 of the settlement machine 300
On the upper surface of 01, there is provided a check-in lamp 341 indicating that the card is being settled, and a check-out stop lamp 342 indicating that the card cannot be settled.

Further, inside the openable and closable front panel 306, as shown in FIG. 46, a monitor display 343 for displaying an abnormality of the settlement machine such as a shortage of bills using an error number, and a display of the monitor display 343. A reset switch 351 for resetting the number and a number setting device 352 for distinguishing each of a plurality of payment machines installed in the game arcade so that the management device 400 can recognize the payment machine that has performed the payment for the specific card. And a coin removal switch 35 for discharging coins remaining in the tank of the coin dispenser 325 when the store is closed.
3 and a print changeover switch 354 for instructing whether or not to print the history data on a receipt issued by the printer 330.

The machine number set by the machine number setting unit 352 is sent to the management device 400, and is used for generating a transmission address in data communication and creating a data file for each settlement machine.

As shown in FIG. 47, the card settlement device 310 controls the card reader 800, the auxiliary transport device 311 disposed behind the card reader 800, and the card reader 800 and the auxiliary transport device 311 in accordance with instructions from the unit control device 350. And a card collection tank 314 disposed behind the power supply unit 313 and the auxiliary transport unit 311.

The card recovery tank 314 is removably inserted into a vertically long tank storage frame 316 fixed to a frame 315 of the card settlement device 310. Further, two counters 317 and 318 are provided on the side surface of the frame 315, and one of the counters 317 and 318 displays the number of collected cards. The other counter is unused.

The auxiliary transport device 311 is provided with a transport roller 36.
1, 362, a pair of upper and lower transport belts 363 and 364 wound therearound, and a transport motor 365 for driving the lower transport belt 364. Belts 363 and 36
4 and is transported toward the collection tank 314 at the rear.

Although not shown in FIG. 47, the card recovery tank 314 includes a card sensor 3 for detecting that the card has been discharged into the tank or that the card is full.
19 are provided (see FIG. 50). However, the settlement machine 300 of this embodiment is in the card confiscation mode only when the highest digit of the machine number setting device 352 is set to “9”, and the card inserted for settlement is settled in the card collection tank after settlement. The card is guided and confiscated, and at other times, the card is ejected forward after the settlement and returned to the player.

In addition, the settlement machine 300 of this embodiment has a plurality of arrangements as shown in FIG.
A counter provided in a prize exchange corner of a pachinko parlor can be configured.

That is, the main body of the checkout machine 300 is designed so that the upper panel 301 is about 1 m above the floor and the upper surface is substantially flat, so that it is used as a work table for prize exchange and the like. be able to.

The card collecting machine 900 has a card insertion port 905 and a prize payout port 906 on the front side, and has a built-in card reader (not shown) for reading the inserted card. A CRT display 910 as a game device to be provided is placed.

FIG. 49 shows the print switch 354.
4 shows an example of a print format of a receipt printed out in two print modes set by the following.

[0221] Of these, (A) of the figure is an example of a receipt format when printing of only the adjustment data is designated by the print changeover switch 354.
ALL, card issue serial number n, settlement date and reception time TIME, settlement amount AMs, settlement number CN
T and the message MSG are printed.

On the other hand, FIG. 46 shows an example of a receipt format when the history data printing is designated by the print switch 354. In addition to the settlement data shown in FIG. History data (unused amount and number of balls at each time the card status changes during the game) and CRR are printed.

In the settlement machine 300 of the above embodiment, the card collection mode is set by setting the most significant digit of the unit number setting unit 352 to "9". In other cases, the card after settlement is ejected forward. However, by checking the card status at the time of checkout, if the card used is "0" and the entire purchase amount is refunded,
After refund of the unused money, the card is collected in the rear collection tank 3
14 can be controlled by software. This makes it possible to avoid abuse of purchasing a card only for the game in the case where the system is configured so that the game using the adjusted card is performed by the collection machine.

FIG. 50 shows an example of the configuration of a control system of the settlement machine 300 configured as described above.

The control system of this embodiment is roughly divided into a control system by the unit control device 350 and a control system by the card settlement control device 312. The unit control device 350 includes the bill and coin dispensers 321 and 325.
And control of various displays 303, 304, 341-343 and printer 330 and various switches 351-354,
The card settlement controller 312 is in charge of accepting the input of the card 305, and the card settlement controller 312 is provided with an auxiliary transporting device 311; a counter 317 as a means for counting and displaying collected cards; and a card reader 8 for checking cards and reading magnetic data.
00 is in charge of the overall control of the control device 388.
Then, the unit controller 350 and the settlement controller 312
Communication with the communication is performed by serial communication.

On the other hand, the unit control device 350 can be connected to the low-layer network communication line 510 made of an optical cable or a coaxial cable via the optical transceiver 185 in order to transmit and receive data such as a card number to and from the management device 400. Has been.

FIG. 51 shows the structure of the unit control device 350 of the settlement machine 300. This unit controller 350
Is almost the same as the unit control device 280 of the issuing machine 200 shown in FIG. 44, a unit controller 390 for controlling the card reader control device 388 and the card settlement control device 312 in general, and a management device 400. And a network controller 553 that establishes a transmission / reception right in a network and performs serial / parallel conversion of data under the control of the data transmission controller 551.
The communication system is pachinko machine 1
The configuration is exactly the same as that of the unit control device 180 of FIG. That is, the transfer of data between the controllers 390 and 551 and between the controllers 551 and 553 can be executed through the dual port memories (RAM) 550 and 552. Among them, the packet memory 552 is divided into a transmission data storage area and a reception data storage area, and has an adjustment function for making all transmission / reception data lengths the same (packetization), and a high speed data transmission ( (2.5 Mbps).

Each of the packet memories 552 has 256
It is composed of four pages each having a byte capacity, of which page 0 is used for transmitting a transmission request packet and page 1 is used for transmitting a regular data transmission packet. On the other hand, pages 2 and 3 are used alternately for data packet reception. Which page to use depends on the data transmission controller 5
51 instructs the network controller 553.
While the data transmission controller 551 is processing the received packet data, even if the next packet data is sent,
Since it is received by another page, all packets can be received reliably. A common reset circuit 555 is provided so that the controllers 551 and 553 can be initialized at the same time.

The connection side of the network controller 553 with the management device 400 is connected via a signal conversion circuit 554 and a changeover switch 542 which perform waveform shaping of the received data and level conversion of the signal in order to increase the drive capability of the transmitted data. The transmission signal and the reception signal are separated and coupled via the changeover switch 542 so as to be connectable to the optical connector 186 and to cope with the case where the transmission line of the low-layer network is constituted by a coaxial cable. The connection can be made to the branch circuit 540.
An optical transceiver 185 is connected to the optical connector 186.

Further, between the data transmission controller 551 and the network controller 553, a latch circuit 561 for storing the data reception result by the network controller 553 in response to a request from the data transmission controller 551, and a data transmission controller 551
There are a latch circuit 562 for storing a command such as a data transmission command to the network controller 553 and a latch circuit 563 for storing a low-layer network address, and three for displaying an abnormality in the communication control state in the unit control device 350. Latch circuit 5 for storing display data to monitor display 556 comprising an LED lamp
64 are provided. 557 is the latch circuit 56
This is a decoder that decodes addresses given to 1 to 564 and generates a selection signal.

On the other hand, the unit controller 3 of the settlement machine 300
The difference of 50 from the unit controller 180 of the pachinko machine is that the unit controller 390 does not directly communicate with the card reader controller 388, but through the card settlement controller 312. Therefore, a transceiver 571 that performs level conversion of transmission / reception data is connected between the unit controller 390 and the card settlement controller 312.

The unit controller 390 includes:
The reset switch 305 of the ball number display 303, the unit number setting device 352, and the reset switch 3 of the monitor display 343
51, an input / output controller 576 for placing input signals from the coin removal switch 353 and the print changeover switch 354 on the data bus 581 at a predetermined timing, and for latching the drive signals of the check-in-progress display 341 and the check-out display 342. And input signals from the bill dispenser 321, the coin dispenser 325 and the printer 330 to the data bus 581 at a predetermined timing, and latch control signals to the bill dispenser 321, the coin dispenser 325 and the printer 330. An input / output controller 578 is connected.

The control signals from the unit controller 390 to the bill dispenser 321 include an instruction signal for setting the number of bills to be dispensed in a binary code, an instruction signal for executing the dispensing of bills based on the set number of sheets, and the like. There is an instruction signal for clearing the display of a monitor display (not shown) for displaying the payout execution result.

The input signals from the bill dispenser 321 to the unit controller 390 include a signal output each time one bill is dispensed and a signal output when an abnormality occurs in the dispensing apparatus and the dispensing operation cannot be performed. The alarm signal to be output, a signal indicating that the bill remaining amount of the bill storage unit has become 20 or less, a signal indicating that the bill payout operation is being performed, and the bill payout operation is completed,
There is a signal indicating that the bill in the bill issuing port has been removed.

On the other hand, as a control signal from the unit controller 390 to the coin dispenser 325, there is a drive signal for a coin dispensing motor, and while this drive signal is being output, coins are continuously discharged one by one. The coin dispenser 325 supplies the unit controller 390 with a coin detection signal output every time one coin is paid out and a signal indicating that the remaining amount in the coin storage tank is low. The control signals from the unit controller 390 to the printer 330 include a print data, an 8-bit data signal for giving a paper cut command after printing, a print command, a signal for instructing the start of capture of this data signal, There is a printer initialization signal. Printer 33
Input signals from 0 to the unit controller 390 include an error signal indicating a printing error, a signal indicating that the printing paper has run out, and a signal indicating that a printing operation is being performed.

The unit controller 390 further includes a ball number display 303 for displaying the number of payment balls, an amount display 304 for displaying the payment amount, and a monitor display 343 for displaying a number indicating the type of abnormality of the payment device 300. Decoders 586a and 586b for dynamically displaying
587 and decoder drivers 588 and 589 are connected via a data bus 581.

[Table 14] shows an example of error numbers displayed on the monitor display 343, their contents, and processing.

In the table, when an error marked with an asterisk occurs, the system is reset as a system down. When the error display is blinking, it indicates that the reset button needs to be pressed after the error recovery processing.

[0239]

[Table 14] Reference numeral 585 denotes an address signal output from the unit controller 390 to decode the program memory 55
8, unit memory 550, input / output controller 57
6,578, a decoder 586, 587 and a decoder driver 588,889 for forming a selection signal.

Further, the unit control device 3 of this embodiment
In 50, of the display data output from the unit controller 390 to drive the monetary indicator 304, a digit select signal (common signal) periodically output at intervals of 2 ms is sent to the reset circuit 555, Input as a dog pulse. The reset circuit 555 monitors the watchdog pulse in addition to the power-on reset, and generates a reset signal for each controller 390, 551, 553 when the pulse disappears.

As described above, the unit control device 350
The management device 400 and the card settlement control device 312 have information exchange windows in two directions. Under the control of the management device 400, it performs control for card settlement and generates a result as a result of the settlement process. Software for periodically transmitting operation data of the payment machine 300 to the management device 400.

Unit controller 39 of payment machine 300
0 controls the above components, checks the card number, receives and displays the card data, executes the settlement process, collects the operation data, and transmits the operation data in the unit memory 550 composed of the dual port memory. Write to data area SDA. The operation data written in the unit memory 550 is transmitted to the data transmission controller 551.
Is transmitted to the management device 400 by data communication with the management device 400 via the transmission cable. Management device 4
00 sent from the unit memory 5
The data is written in the reception data area RDA in 50, and the unit controller 390 reads this to receive data. The unit memory 550 is provided with a shared data area CDA in which a command and status information for transmitting the transmission data and the reception data in the memory to the other controller are stored.

Tables 15 and 16 show examples of the structure of the transmission data area SDA and the reception data area RDA in the unit memory 550, respectively. The configuration of the communication area CCA is exactly the same as that of the unit memory of the pachinko machine (see [Table 3]).

[0244]

[Table 15]

[0245]

[Table 16] As shown in [Table 16], in this embodiment, the history data of the card is also received, and this is printed on the receipt together with the time data and discharged, so that the payment data is highly reliable for the player. Can impress.
However, the history data is data of up to 20 times contained in the card file.

As shown in [Table 17], the monitor information 1 shown in [Table 15] includes a bit indicating that a test is being executed at system startup, a bit indicating initial value setting / unset, and a hot code. It is composed of a bit indicating an error, a bit indicating an abnormality in the local network (transmission cable 500) (two bits for a low layer and a high layer), a bit indicating an error in a checkout machine, and the like.

[0247]

[Table 17] Further, as shown in Table 18, the monitor information 2 includes a bit indicating paper out, a bit indicating printer abnormality, a bit indicating card reader abnormality, a bit indicating status in the card tank, and a coin of the coin dispenser. A bit indicating the presence or absence of
It is composed of a bit indicating an abnormality of the coin dispenser, a bit indicating a state of the bill dispenser in the bill tank, a bit indicating an abnormality of the bill dispenser, and the like.

[0248]

[Table 18] Next, the pachinko machine 100, the card issuing machine 200, and the payment machine 300 configured as described above are collectively controlled, operation data is collected in real time, and the operation status of all terminals is monitored. Even if it occurs, the original data state is restored immediately upon restoration, the operation of each system part is resumed, the data necessary for the management of the amusement store can be counted, and the same qualification is restored if the card is damaged The management device 400 that issues a card will be described.

FIG. 52 shows a specific configuration of the management device 400, and FIG. 53 shows a system configuration of the management device 400.

The management device 400 is a first computer comprising a central processing unit CPU of a minicomputer class and a semiconductor memory (RAM).
A master control device 401 in which a main storage device M-MEM as a storage device, a transmission control device SCC, and the like are stored; a floppy disk storage device 402 as a second storage device provided above the master control device 401; It comprises a storage device 403 and a personal computer 410. In addition, the personal computer 4
Reference numeral 10 denotes a CRT display device 411 for displaying messages and collected data, and a console 412 for an operator to give commands and setting data.
(Including a calendar), a local processing unit 413 connected to a central processing unit CPU in the master control unit 401 via a communication line and an interrupt line, and a printer 414 for printing collected data and the like. It is configured.

The local processing unit 413 and the central processing unit C
The serial communication controller 406 for coupling with the PU
a and 406b are provided in the master control device 401. Among them, the communication control device 406a performs normal communication,
The communication control device 406b is used for emergency interrupt communication.

The printer 414 includes a buffer for temporarily storing data to be printed in order to improve the throughput of the management device 400.

Further, the management device 400 is provided with a resurrection card having the same qualification as the damaged card, and a test card capable of starting the pachinko machine in a state separated from the system, which is unique to the pachinko gaming system. A box 420 containing an auxiliary printer 408 for printing in real time emergency information generated by the system, such as a card issuing device 700 for issuing a card or a "stop" generated by a pachinko machine, and an auxiliary power supply device 409 are used for the master control. It is provided adjacent to the device 401.

Card issuing device 700 and auxiliary printer 40
8 are connected to the central processing unit CPU via the communication control devices 406c and 406d, respectively. Also, the card issuing device 700 includes the issuing device 200 shown in FIG.
Of the same configuration as the card issuing device 700 for use. 202 is the card issuing port.

The auxiliary power supply 409 protects the operation data of all terminals volatilely held in the main memory M-MEM and the data of all issued cards to the hard disk storage 403 when a power failure occurs. In order to be able to do so, backup is performed so that the management device 400 can be operated for at least about 10 minutes.

In FIG. 53, reference numeral SCC denotes a transmission control device for enabling data transmission to / from each terminal via the network 500.

In this embodiment, a system mainly comprising a pachinko machine 100, a card issuing machine 200, a settlement machine 300 and a management device 400 will be described. However, the present invention relates to an in-store broadcasting device, a prize exchange device, and a vending machine. And the like can be extended to a system that is controlled by the management device 400. In particular, there is a possibility that the prize exchange apparatus can easily apply a system in which a prize can be exchanged directly without using the card and passing through the checkout machine 300.

Further, the console 412 constituting the management device 400 also has a unique key configuration most suitable for the pachinko game system of this embodiment.

FIG. 54 shows an example of the configuration of the console 412. FIG. 2B shows the upper surface of the console 412, that is, the panel surface, and FIG.

In FIG. 54, reference numeral 421 denotes a store opening switch for instructing start of business for each terminal of the system;
Reference numeral 22 denotes a store closing switch for instructing the end of business. The card can be operated in each terminal device after the store opening switch 421 is turned on until the store closing switch 422 is turned on. Reference numeral 423 denotes a system end switch for storing the operation data of all terminals in the floppy disk storage device 402 after the business is closed, and instructs the management device 400 to stop the control. Reference numeral 424 denotes an instruction to recover the damaged card. Card resurrection switch for

The four switches of the store opening switch 421, the store closing switch 422, the system end switch 423, and the card recovery switch 424 are particularly important switches for the present system, and are prevented from being easily operated during the operation of the system. Therefore, it is interlocked with the key switch 420 provided behind (the upper side in the figure), and unless the key switch 420 is turned on, the switches 421 to 424 cannot be operated to be turned on. It has become.

Reference numerals 425, 426, and 427 denote ten keys, a return key, and a delete key, which are the same as those provided on a console of an ordinary personal computer or the like.

On the other hand, reference numeral 428 denotes a display menu switch 429 for giving a command to display data on the card, operation data of each terminal, etc. on the screen of the CRT display device 411.
Is a CRT clear switch for requesting erasure of data displayed on the CRT display device 411. Reference numeral 430 denotes data related to the card, operation data of each terminal, and the like.
A print menu switch 14 gives a print command. 432, a setting switch for requesting the setting of the number of hits and the hitting mode in the pachinko machine 100;
433 is a pachinko machine 1 in which the set number of hits are paid out and the prize balls are paid out, that is, the pachinko machine 1 is in a state in which the game can not be continued.
A stop release switch 434 for giving a release command of the stop state of 00 is used to forcibly terminate terminals for each type at the end of business hours or to disable normal control and data collection due to a communication network abnormality or the like. Forced termination switch for forcibly terminating all terminals in the event of a failure, or forcibly terminating a specific terminal if a player's fraud is discovered,
Reference numeral 435 denotes an end release switch for releasing the forcibly stopped terminal, and 439 denotes a date / time setting switch.

Further, the console 412 of the embodiment has a buzzer 440 for generating a sound to urge the operator to wake up when an emergency such as a stoppage in the pachinko machine 100 occurs, and a buzzer stop switch for instructing to stop the sound generation. 436 are provided. 431a and 431b are the management device 40
This is a spare switch prepared in anticipation that the function of No. 0 will be expanded in the future, and can be used, for example, as a switch for instructing interruption of printing by the printer 414.

Of the above switches, switches 421 to 424 and 432 to 436 indicated by double frames in the drawing are:
These switches are built-in lamps, and when these switches are turned on, the built-in lamps are turned on during execution of the corresponding processing or while the state is continued. However, the buzzer stop switch 43
The lamp in 6 is linked with the buzzer, is turned on while the buzzer is sounding, and turned off when the stop switch 436 is pressed.

Further, the console 412 of this embodiment has a test card switch 437 for giving a test card issuance command on the back thereof, an exchange rate of purchased balls, a store code, a total number of terminals, Winning ball 1
A built-in switch 438 is provided for instructing setting of a set value such as the number of prize balls per piece and changing of the set value. Unlike other switches, these switches 437 and 438 are switches that are rarely used, and are switches that only require a specific person (such as a manager of an amusement store) to know the existence thereof.
2 is provided on the back surface.

Here, the test card will be described. As is clear from the configuration already described, the gaming system according to this embodiment includes all terminals (pachinko machines 10).
0, the card issuing machine 200, and the settlement machine 300)
Under the control of 00, the state shifts to an operable state by exchanging a card number and the like, and the terminal cannot operate alone. However, since pachinko machines are frequently used, jams and so-called tulips and other accessories often break down, and it is necessary to adjust nails in the game area to adjust the payout rate.

In this case, test hitting is performed after repair or nail adjustment. In this embodiment, the test switch 179 in the control unit 160 of each pachinko machine described above is turned on and issued by the management device 400. When the special test card thus inserted is inserted through the card insertion / ejection opening 802a of the control unit 160, a certain number of balls is given, so that the pachinko machine can execute the game operation alone. As a result, it is not necessary to start up the entire system in trial running during non-business hours.

Also, during business hours, test hitting can be performed without losing operation data during the game.

In this embodiment, the same card issuing device 700 as that used in the issuing device 200 is used as the card issuing device 700 provided in the management device 400, and a card tank 701 in which blank cards are stored and a card reader 701 are used. 80
Although 0 is built in, a method may be adopted in which a blank card is inserted from outside, a code is recorded on a magnetic surface, and the code is ejected without a blank card inside. In that case, the card tank 701 can be omitted. Further, since the test card and the resurrection card issued by the management device 400 do not necessarily need to specify the date of use and the serial number of the issuance unlike other general cards, the printing device 750 may be omitted. When issuing a resurrection card, the punching device 82
By setting 0, a punch hole is formed at a predetermined punching position PH2 (recovery hole) of the card.

As described above, the terminal 10 of this embodiment
0, 200, and 300 are all under the control of the management apparatus 400, and unless the management apparatus 400 is activated, they cannot operate independently in principle. Therefore, at the time of system startup, the management apparatus 400 gives setting values to all terminals and initializes them. In addition, prior to the initialization, the terminal numbers are collected from each terminal to enable data transmission, and each transmission address is formed. During the operation of the system, the operation data of all the terminals is collected in real time, and the main storage device M-ME is collected.
M.

That is, since the number of terminals under the management of the management device 400 is large, all control is performed by the management device 400.
If you do this, the response will be slow, so we adopted a distributed processing method that entrusts some processing to the terminal unit control device, collects data for all terminals by regular data collection, and monitors the operation status .

[0273] When the regular data is collected, the amount of data handled by the management device 400 becomes enormous. Therefore, in this embodiment, these data are organized by file management to facilitate handling.

FIG. 55 shows the configuration of the main memory M-MEM in which the data files are set, and [Table 19] shows the functions and save locations of each file.

Main storage device M-ME as first storage means
Of the files in M, the files FL1 to FL5 except for the transmission address file FL6 are saved in the hard disk HDD (auxiliary) storage device 403 at the time of power failure. Also,
As the operation data transfer means, a data file relating to the terminal, that is, a pachinko machine file (hereinafter referred to as a P machine file) FL2, an issuing machine file FL3, and a checkout machine file FL4 are used as a daily report file, for example, a floppy disk FDD (second The data is stored in a floppy disk storage device 402) as a storage means, and is provided for monthly operation data totaling and the like. The time when the daily report file is stored on the floppy disk FDD is not limited to the time when the business is over. When storing as a daily report file, use the floppy disk F
Not only DD, but also a microcomputer having another central processing unit CPU or another hard disk, etc.
Any device that functions as a storage device may be used.

Further, the set value file FL5 and the transmission address file FL6 are loaded from the hard disk HDD into the main memory M-MEM at the start of the system, and are saved in the hard disk HDD when there is a change.

The setting value file is stored in the main storage device M-
The data is loaded into the common data area CDA provided in the MEM. This common data area CDA is an area serving as a working area of the central processing unit CPU, and stores, in addition to the setting file FL5, a system mode, the latest card issue serial number, a power failure flag, a random number for creating a card number, and the like. Is done.

[0278]

[Table 19] Next, each file shown in [Table 19] will be described in more detail.

[0279] The set value file FL5 in the table contains the exchange rate of purchased balls, the store code, the number of terminals, the number of terminals, the number of prize balls, the number of hits, etc., which are stored in advance in the hard disk HDD by input of the console 412 when the system is introduced. This is a set value that fluctuates according to characteristics and configurations. The set value file is loaded from the hard disk HDD to the main storage device at the start of normal business. Also, the setting value file FL
5 can be updated by the console 412 by pressing the built-in switch 438 when replacing a pachinko machine or the like.

[Table 20] shows a configuration example of the setting value file FL5.

[0281]

[Table 20] In the same table, the purchase ball exchange rate is the number of lending balls per purchase amount unit (for example, 200 yen), that is, the minimum number of balls, and the number of NAUs is the connection between a high-layer network and a low-layer network as a data transmission system. The total number of network adapter units (communication control devices) provided in the unit. In the above file, the type and number of terminals connected below each NAU 530 are set in the table indicated by h. Further, the number of prize balls from a certain pachinko machine to a certain pachinko machine is set in the table indicated by the symbol j. Two types of prize balls can be set for each prize ball.
Moreover, in this embodiment, as shown by j = 1 to Y,
All pachinko machines at the amusement arcade are divided into groups of Y, so that two main and sub prize balls can be set separately. However, consecutive machine numbers are given to pachinko machines having the same set value, and the target range is specified by the start number and end number.

Further, the number of hits and the hit mode are set in the table indicated by k. Here, the hit mode is
Shows how to calculate the number of hits (arithmetic expression), for example, a mode in which the number of hit balls is subtracted from the number of payout prize balls simply, or a mode in which hitting is performed when the number of payout prize balls reaches the number of hits. There is a mode where a stop is made when the number of hits reaches the number of stops. Although not particularly limited, in this embodiment, k = 1 to Z
As shown by, the number of hits and the hitting mode can be set independently for each of the Z groups.

[Table 21] shows a configuration example of the file FL6 of the transmission address used for data transmission.

In [Table 21], the type flag is a flag for indicating the type of the terminal.
"2" is a card issuing machine and "4" is a checkout machine.
"0" indicates the absence of the terminal. The NAU status indicates the state of the NAU 530. As shown in Table 22, when "1" is set to the bit B, the token bus is abnormal, and "1" is set to the bit B. Indicates that the “opening code” packet has already been received, and further sets “1” to bit B.
Is set, it indicates that the NAU 530 is normal.

[0285]

[Table 21]

[0286]

[Table 22] The terminal number and serial number are the terminal number and its serial number created except for "4" and "9". The unit number is located under one NAU (network adapter unit) 530 regardless of the type of terminal. The number of each terminal placed, that is, a number that becomes an address on a low-layer network described below, and the channel number is an address of each terminal viewed from the management device 400, that is, a number that becomes an address on a high-layer network described below. . However, in the system of the embodiment, the number of pachinko machines connected under one NAU 530 is set to 64 or less.

The NAU number and the machine number are numbers given by the setting switches (171, 205, 352, 544) as described above. In the case of a pachinko parlor, the machine numbers of the pachinko machines are customarily "4" and "4". It is a jump number given by a number excluding "9". Here, the fact that "4" and "9" are not used indicates that an octal representation is possible. Therefore, the base numbers expressed in decimal numbers are represented by only the numbers 0 to 7 using the conversion table shown in [Table 23]. According to this, for example, the stand number “258” is described as “247”.

[0288]

[Table 23] When this is expressed by a binary code in a binary octal system, it becomes "010/100/111". This code indicates the decimal "167", which
Pachinko machine numbers missing “4” and “9” are consecutive serial numbers. On the other hand, in order to suppress the address on the low-layer network to 8 bits, the lower 8 bits of the above code are taken, and this is represented by a code "1010" expressed in binary octal system.
• 0111 ”and expressing this in HEXA,
It becomes "A7H". Further, besides the pachinko machine 100, terminals such as the issuing machine 200 and the settlement machine 300 are also connected under one NAU, and an 8-bit unit number is also given to them. The number is limited to 64, and the above code “A7H” and code “3F
H "(corresponding to decimal number 64) and" 2
7H ". Taking a logical product with "3FH" means an operation of obtaining a remainder obtained by dividing by 64. In this embodiment, this is used as the unit number. And
“NAU number + unit number” with the NAU number prefixed to the unit number is used as the channel number. According to such a method, in the custom of a pachinko game store having a number that does not use “4” and “9”, efficient address processing that matches the characteristics of a microcomputer that performs data processing using only the binary system Becomes possible.

The transmission address file is created by an input from the console 412 when the system is introduced, and the NAU itself also receives an address file (unit) of a unit under its control based on an input from the serial number setting device when the system starts up. Table) is created and stored in the memory. After the line test, the management device 400
When a unit table request is issued to the AU 530 and the response data does not match, the data is automatically changed (described later). The transmission address file can also be changed by a built-in switch 438 on the back of the console 412.

The NAU 530, the issuing machine 200, and the settlement machine 300 are given serial numbers starting from “1” for each type as a machine number, and the NAU 530 and the settlement machine 3 are assigned.
With respect to 00, the machine number is used as it is as an address (unit number), and as for the issuing machine 200, the machine number plus "128" is used as the address (unit number) on the low-layer network. This is to avoid address duplication when the pachinko machine 100 and the issuing machine 200 having the same machine number coexist under the same NAU.
The duplication of the addresses of the pachinko machine 100 and the checkout machine 300
This is avoided by not allowing both to coexist under the same NAU. In addition, the issuing machine 200 and the settlement machine 300 have the same NAU.
It can be placed below (because "unit number +128" is used as the address of the issuing machine 200).

Further, the address of the NAU 530 on the high-layer network uses the NAU number set by the setting unit 544, and the address of the NAU on the low-layer network is "2".
A fixed address of "55" is used. Also, the management device 400
Is "0".

[Table 24] shows a configuration example of the card file FL1. The card file FL1 contains information for each card.

[0293]

[Table 24] In [Table 24], the card number is a number obtained from the issue serial number n using the function f (n). The number of balls and the amount of money, and the card status is the current number of the card specified by the issue serial number n and the card number. This information indicates the status, and is referred to as a card text in this embodiment. Here, the card state is, as shown in the following [Table 25], a bit indicating a free state that is not used for a game, a bit indicating that a game is in progress,
A bit indicating that the player is temporarily suspended from the gaming machine, a bit indicating that the card has already been settled in the checkout machine, a bit indicating that the number of balls held and the balance of the card have both become zero, It is composed of a bit indicating that a hit has occurred more than once, a bit indicating that the card has been used in a pachinko machine that has been forcibly terminated, a bit indicating that the card has been restored, and the like.

[0294]

[Table 25] Returning to [Table 24], the terminal file serial number indicating the position of the terminal where the card is currently located and the terminal number are registered in the card file FL1. Since pachinko parlors do not use the numbers "4" and "9" as the unit numbers, two types of terminal numbers, back and front, are generated.

In Table 24, the i counter indicates the number of times the card has taken an action, that is, the number of times the card has been ejected from the system as an organic combination to the outside. At that time, card information such as a stand number, the number of balls held, the amount of money, time, etc., that is, the card history is recorded. Statistically, most players play with less than 20 pachinko machines per day,
In this embodiment, the card history is recorded up to 20 times. However, if the number of times exceeds 20, i = 20
It is recorded by updating the table indicated by. In addition,
In the above case, the i counter does not count the interruption of the game. That is, each card information is recorded in a new area at the time of interruption, but the value of the i-counter is substantially updated by recording the card information in the same area without updating the counter when the game end switch is turned on after the interruption is released, and recording the card information in the same area. The number is matched.

Here, the state and action of the card and the registration of the FL1 card information in the card file will be described with reference to FIG.

First, when a card is issued in the card issuing machine 200, the card is ejected and the card shifts from the unissued (blank) state SS0 to the free state SS1. Then, when a card is inserted into the desired pachinko machine 100, the game state shifts to the gaming state SS2. Here, when the balls and the amount of money of the card become zero by the game, the card is ejected and the state is shifted to the return-to-zero state SS3. Further, when the interruption switch 114 is pressed during the game, the card is ejected, the state shifts to the interruption state SS4, and the state returns to the game state SS2 by re-inserting the same card. Then, when the end switch 115 is pressed to end the game during the game, the card is ejected and the state shifts to the free state SS1. The card is also ejected by the forced termination or the occurrence of a hit by the CPU, and the state shifts from the gaming state SS2 to the free state SS1. When the user goes to the checkout machine 300 with the card in the free state and performs a checkout process, the card is collected after an invalid mark is added, and the state is shifted to the settled state SS5. In the system of this embodiment, it is also possible to go to the settlement machine 300 without returning to the pachinko machine 100 with the card in the suspension state SS4 and perform the settlement processing. In this case, the settlement state S
Move to S5.

[0298] In the above state transition diagram, a circle with an arrow indicating the transition direction indicates an action involving recording of card information in the card file FL1. In each block, the code indicated by XXH is as shown in [Table 2].
The corresponding state is expressed in hexadecimal digits (HEXA expression) using the code indicating the card state of [5].

Next, [Table 26] shows a configuration example of the P machine file FL2.

In the table, items from the unit number to the card status are the transmission data area S shown in [Table 1].
Data held in DA, which is 1 per second
It is sampled by the time management device 400 and registered in a file. The number of main prize balls, the number of sub prize balls, the number of hits, and the hitting mode are set when the system starts up (Table 20).
Are registered in the P machine file FL2 based on the setting value file FL5 shown in FIG.

[0301]

[Table 26] In Table 26, the data marked with a circle means that the data is saved on a floppy disk as a daily report file at the end of the system. The monitor information 1 and 2 in the pachinko machine file are shown in [Table 4] and [Table 5], and the operation information is shown in [Table 6].

Next, [Table 27] and [Table 28] show the issuing machine file FL3 and the adjusting machine file FL4, respectively. The data items shown in [Table 27] are the data held in the transmission data area SDA of the issuing machine 200 shown in [Table 10], and the data items shown in [Table 28] are [Table 15] Transmission data area SDA shown in
, Respectively. These are 1
It is sampled by the management device 400 once per second.

[0303]

[Table 27]

[0304]

[Table 28] In Table 26 and Table 27, data marked with a circle in the save column indicates that the floppy disk F
This is the data saved in the DD.

The monitor information 1 in the issuing machine file 1
2 is shown in [Table 12] and [Table 13], and monitor information 1 and 2 of the checkout machine file are shown in [Table 17] and [Table 18]. Further, the operation information of the issuing machine 200 and the payment machine 3
00 operation information is 0000000000 0000 00
01 indicates that it is operating.

Next, the card issuing machine 200, the pachinko machine 100, and the payment machine 3 as terminals configured as described above.
A data transmission path (local area network) that enables data transmission and card operation by organically coupling the management device 400 and a management device 400 that performs centralized control of those terminals will be described. FIG. 57 shows a configuration example of a pachinko game system using a hierarchical data transmission path.

That is, 100 to 1000 terminals are grouped by 20 to 40 terminals in units such as island facilities of a game arcade, for example, and the terminals of each group circulate at high speed on a ring-shaped transmission path. A node (terminal) that has received a packet indicating a transmission right called a token to be transmitted has a right to transmit and receive data in the form of a packet. (Hereinafter, referred to as NAU) 530.

A plurality of NAUs 530 that control each low-layer network (token bus) 510 include a CSM
A / CD (Carrier Sense Multip)
leAccess with Collision D
connect) to the management apparatus 400 via a high-layer network 520 of the E.T.

The low-layer network 510 has a capacity of 2.5 Mb.
The high layer network 520 is controlled to have a transmission rate such as 10 Mbps, and the NAU 530 absorbs the difference in transmission rate between the two to provide smooth data transmission. Acts as an enabling buffer. That is, the NAU 530 has a function of relaying data between heterogeneous networks and a function of logical collection and delivery of data. As described above, the data transmission path 500 has a hierarchical configuration because 500 or more terminals are connected to one management apparatus 400, and when trying to collect regular data every second from each terminal, all the host computers are required. In a system that communicates directly with the terminal unit, the load on the host computer becomes too large, and the transmission speed of the chiper network is as fast as 10 Mbps, but the cost of the controller LSI is too high to directly connect the terminal unit. . Also, the transmission speed is too slow to collect data once per second using only the token bus. Moreover, in the system according to the present embodiment, both the transmission line forming the high-layer network 520 and the transmission line forming the low-layer network 510 are configured so that either a coaxial cable or an optical fiber cable can be used.

In FIG. 57, the symbol P indicates a pachinko machine as a terminal, the symbol H indicates a card issuing machine, and the symbol S indicates a checkout machine. .

[0311] Each of the terminals P, H, and S is connected to the network 51.
It is connected to a branch line branched from 0. The control units 160, 250 and 350 of each terminal are connected to the end of each branch line. Reference numeral U in FIG. 57 denotes a unit control device of each terminal.

[0312] As can be seen from the figure, 25 NAUs 530 are arranged in the high-layer network in opposition to the management device 400, and 23 pachinko machines, checkout machines, and issuing machines are arranged in the low-layer network in opposition to the NAU 530. Have been placed.

The low-layer network has a form of one issuer and 22 pachinko machines, and a form of 10 issuers and 5 checkout machines. As described above, since at least one issuer exists in each low-layer network, the NAU 530 is mounted in the issuer 200 in the embodiment of this embodiment. The reason why 10 issuing machines and 5 checkout machines are provided is that it is possible to arrange the issuing machines or checkout machines in one place in a concentrated manner.

FIG. 58 shows an example of a network configuration when a coaxial cable is used as a transmission line, and FIG. 59 shows an example of a network configuration when an optical fiber cable is used as a transmission line.

When a coaxial cable is used as a transmission line, each NAU 530 is connected to a high-layer network cable 515 in a parallel form by a T-shaped connector 505, and each unit (terminal) H1, P2, P3,. P22
Are also connected to the low-layer network cable 525 in a parallel configuration by a T-connector 505.

On the other hand, when an optical fiber cable is used as a transmission line, the management device 400 is provided with a multi-channel optical transceiver 502 having a photoelectric conversion function, transmission data distribution and reception data multiplexing functions.
Each of the optical transceivers 30 is provided with an optical transceiver 507 for performing photoelectric conversion of transmission / reception data, and each optical transceiver 507 and the multi-channel optical transceiver 502 are connected to each other by a two-core optical fiber cable 512. Also, the NAU 530 and the units H1, P1, P2,.
The optical transceivers 2 are provided with optical transceivers 508 that perform token bus data communication in a low-layer network, and are connected by a two-core optical fiber cable 522.
Each optical transceiver 508 has an optical signal branch switching function as well as a photoelectric conversion function of transmission / reception data.

The above optical transceivers 507 and 50
8 and NAU530 or units H1, P1, P2,.
..P22 is connected by a coaxial cable. Although the transmission and reception of data on the high-layer network 520 and the low-layer network 510 both use the packet switching system, the packet format differs on each network.

That is, there is one type of packet on the high-layer network 520, and a synchronization signal of 1010... 1011 consisting of 64 bits called a preamble, a destination address, a source address, a packet type column (unused), It is composed of a data field of 48 to 1500 bytes and an error correction code CRC. Although not particularly limited, data on the high-layer network is transmitted using Manchester codes.

On the other hand, a low-layer network (token bus)
510, each having a different field configuration and function.
Data transmission and reception are performed by the types of packets. 5
The types of packets include a token packet for giving a transmission right, a free buffer inquiry packet for asking the other party whether reception is possible, a data packet for transmitting data, and an acknowledgment and a negative response for the source. "ACK" packet and "NAK" packet.
Each packet has a different length, but has a common bit pattern at the head indicating the head of the packet called an alert burst. In addition to the alert burst, the data packet has an address field indicating a transmission source and a transmission destination, a field indicating a data length, a data field, and a field containing an error correction code. Note that on this low-layer network 510, data is RZ
(Return-to-zero) code is transmitted.

The following Table 29 shows a list of packets used on the high-layer network, and Table 30 shows a list of packets used on the low-layer network.

[0321] The hard ACK in [Table 30] means
AC issued by network controller in hardware
K, which is not a response in which the unit controller or the data transmission controller is involved in software.

[0322]

[Table 29]

[0323]

[Table 30] FIG. 60 shows the NAU buffering data transmission between the low-layer network 510 and the high-layer network 520.
(Network adapter unit) 530 shows an example of a circuit configuration, and FIG. 61 shows an example of the configuration of a unit body incorporating the same.

The NAU 530 of this embodiment includes a low-layer network controller 533 for establishing a transmission / reception right in the low-layer network 510 and performing serial / parallel conversion of data.
A high-layer network controller 537 for establishing a transmission / reception right in a CSMA / CD type high-layer network and performing serial / parallel conversion of data; and a data transmission controller 535 for controlling data transfer between these network controllers 533 and 537. Have.
Among the above controllers, the low-layer network controller 533 is composed of a communication LSI dedicated to token passing, and the high-layer network controller 537 and the data transmission controller 535 are configured by general-purpose microcomputers. Further, between the controllers 533 and 535 and between 535 and 537, a low-layer network 510 and a high-layer network 520 are provided.
A buffer packet memory 534 and a data memory 536 for absorbing the difference in the data transmission speeds are connected to each other. The packet memory 534 and the data memory 536 are constituted by a dual port memory, and have a transmission data area and a reception data area. The data memory 536 has a regular data area for storing regular data collected from the unit, a unit table area for storing a unit transmission address on a low-layer network, and a working area for the data transmission controller 535, in addition to the transmission / reception data area. ing. The transmission data area of all units ([Table 1], [Table 1
0] and [Table 15]), and the unit table area has the same configuration as the transmission address file of the management device 400. The low-layer network controller 533 has a transceiver 5 that performs waveform shaping and level conversion of transmission / reception data signals.
08 is connected. Moreover, this transceiver 50
8, the transmission signal and the reception signal are transmitted via the changeover switch 542 so that the transmission line of the low-layer network can be constituted by a coaxial cable or an optical fiber cable as described above. It is connectable to a branch circuit 540 for separating and coupling signals and an optical connector 186. A coaxial cable connector 187 is connected to the branch circuit 540.

Similarly, high-layer network controller 5
37 is connected to a transceiver 507 that performs waveform shaping and level conversion of transmission / reception data signals. Moreover, as described above, the transceiver 507 transmits the transmission signal via the changeover switch 543 so as to be able to cope with the case where the transmission line of the low-layer network is constituted by a coaxial cable or an optical fiber cable. And a branch circuit 541 for separating and coupling a received signal and an optical connector 186. Branch circuit 541
Is connected to a coaxial cable connector 187.

Further, NAU 530 of this embodiment includes:
A NAU number setting unit 544 for setting a number for distinguishing a plurality of NAUs from each other, and a minimum unit number of the pachinko machine 100 or the settlement machine 300 among terminals existing on the low-layer network 510 under the control of each NAU 530 Number setting unit 545 for setting the number of pachinko machines 100 or checkout machines 300 existing on the low-layer network under its own control, and the minimum number and number of connected issuing machines 200 Are set, and a setter 549 for setting the type of the NAU 530 is provided. Here, the NAU type indicates that the configuration of the terminal indicates either a combination of the issuing machine and the pachinko machine or a combination of the issuing machine and the payment machine. The set values of the setting units 544 to 549 are input to the data transmission controller 535 in the NAU 530 via the buffer gate 538, and the NAU number is used for forming the transmission address of each NAU 530 in the high-layer network 520. The transmission address of each terminal in the low-layer network 510 is formed by the minimum number and the number.

In FIG. 60, reference numeral 531 denotes a program memory for storing a control program of the data transmission controller 535, and 532 denotes each controller 533, 53
5, 537 and memories 531, 534, 536.

A board on which the circuit having the above configuration is mounted is built in NAU unit main body 539 shown in FIG. The connector 186 for the high-layer and low-layer network optical fiber cables and the connector 187 for the high-layer and low-layer network coaxial cable are provided on the front wall and the rear wall of the unit main body 539, respectively. Further, on the upper surface of the unit main body 539, the various setting devices 545 to 54 are provided.
9 are provided. NAU number setting device 544 is provided on a substrate in the case.

Note that reference numeral 501 denotes a power switch, 502 denotes a power-on lamp, 503 denotes a power fuse, and 504 denotes a power connector.

As described above, in the local network having a hierarchical configuration in which the high-layer network and the low-layer network are connected via the NAU 530 (FIGS. 57 and 58), the management device 400
0 to perform a line test and setting of set values for each terminal.
Collects operation data from the terminals P, H and S once per second using the low-layer network 510 and stores it in its own memory. The stored data is stored in the management device 40.
0 from each NAU 530 through the high-layer network 520 once a second in response to a request from the management device 4.
00 is stored in the data file.

As described above, the communication network is NAU5
30 as a buffer, and the high-layer network 520 has a transmission speed of 2.5
Since the transmission rate is set to be four times the transmission rate of Mbps, even in a system having 100 to 1000 terminals, each of the terminals can be used as shown in [Table 1], [Table 10], [Table 1].
A large amount of operation data as shown in [5] can be collected in the management device 400 once a second.

[Table 31] shows that between the management device 400 and the NAU 530 and the NAU in the data transmission system.
The types of packets transmitted and received between the management device 400 and the pachinko machine 100, the card issuing machine 200, and the unit controllers 190, 290, and 390 of the checkout machine 300 via 530 are shown.

[0333]

[Table 31] In the table, the unit is each terminal (pachinko machine 10).
0, a card issuing machine 200 and a payment unit 300). When the system is started, the management unit 400 sends a packet “unit table request” to each NA.
A packet for confirming the connection and address of the unit connected to the U
The connection of the unit is confirmed by the monitor information 1 of the K packet. Also, the address information in the packet is compared with the value of the unit table file, and if they do not match, the data is changed to the data in the packet. The unit whose connection cannot be confirmed is confirmed again by the subsequent initial value setting packet.

[0334] Also, the "card in" to "interruption end" packets described in [Table 31] correspond to the pachinko machine 10
The “card-in” packet is a packet unique to the management unit 400 when a card is inserted into the control unit 160 of the pachinko machine 100.
This is a packet for requesting information (card text) related to the card. Here, the card text is a text containing four pieces of information such as a card number, the number of possessed balls, an amount (unused portion), and a card state. The packet “return to zero” is sent from the control unit 160 of the pachinko machine 100 to the management device 40 when both the number of balls held and the amount of money of the card become zero during the game on the pachinko machine 100.
This is a packet for transmitting a card text to 0.

On the other hand, in the packet of "interruption end", the player presses the interruption switch 114 to receive the card and leaves the pachinko machine, and then inserts the card into the checkout machine without returning to the suspended pachinko machine and performs the settlement. If you do,
The management device 400 is a packet for issuing a command for canceling the suspended state of the pachinko machine that is being suspended. As a result, the player can return to the pachinko machine that has been interrupted and can perform the settlement without pressing the game end switch 115.

The "card purchase" packet described in [Table 31] is a packet unique to the card issuing machine 200. A bill is inserted into the bill insertion slot 211 of the issuing machine, and the purchase selection switch 212 is turned on. This is a packet for requesting a card number and a serial number of the card from the unit control device 280 to the management device 400 when the card is issued.

In the system of this embodiment, a reservation such as a card number is made before a bill is inserted into the card issuing machine 200, and the amount of money is printed and issued when the bill is actually inserted. To be able to do
When the card issuing machine 200 transmits a “card purchase” packet in which the card amount column is “0”, the management device 400 determines that the packet is a reservation reservation packet, determines an issue serial number and a card number, and After securing the area of the card in the file, an ACK packet containing the serial number and the card number is returned to the card issuing machine. On the other hand, when a bill is inserted, the card issuing machine 200
For "0", a "card purchase" packet in which the actual purchase amount is entered in the card amount column is transmitted. Then, the management device 400 determines that the card is reserved for issuance by looking at the card number column, searches the card file, writes data such as the purchase amount and the issuance time in the data area of the card, and then transmits an ACK packet. Is returned to the issuing machine 200.

The “Card Settlement” and “Card Settlement Completed” packets described in [Table 31] correspond to the card settlement machine 3
00 card insertion slot 3
02 when the card is inserted into the unit controller 3
50 is a packet for sending the card number of the card to the management apparatus 400 from the 50 and requesting the unused amount, the number of balls, and the history of the card.

[0339] The "card settlement end" packet is a packet for notifying the management device 400 that the card settlement has been completed. When the management device 400 receives this packet, the card status of the card in the card file is read. Is changed to "paid" and the data at the time of settlement is written in the column of i = 20 of the history data. The management apparatus 400 responds to the “card settlement end” packet with the settlement machine 300 “AC
By transmitting the K "packet, the payment process for the card is completed, and the next card can be inserted into the payment device 300.

The "line monitor check" packet in [Table 31] is a packet for confirming the recovery of the NAU 530 when the NAU 530 is determined to be abnormal by the regular data, and is periodically (every 30 seconds) until the recovery. , And confirms the recovery by receiving the ACK packet from the NAU 530, and transmits the operation data of all the units under the control of the NAU 530 by the "unit recovery data" packet to recover the NAU 530 and the unit. The “unit monitor check” packet is a packet for confirming recovery of a unit when the unit is determined to be abnormal based on the scheduled data.
Transmit periodically until recovery, AC from NAU 530
The recovery is confirmed by receiving the K packet. Upon receiving this packet, NAU 530 performs a connection check with the network controller of the corresponding unit, and transmits an ACK packet to management device 400 when the connection is confirmed.

Further, in Table 31, packets "ACK" and "NAK" correspond to the management device 400, the network adapter unit 530, and the
A packet used between 0, 200, and 300 when a transmission request is received and a response to the request is sent to the other party, and a response is sent to the request that the request is not received.
When "ACK" is returned, requested data such as a card text may be added.

The packet codes 8OH, 81H,... Shown in [Table 31] are represented in hexadecimal notation, and the codes are merely examples, and it is not limited to them. Needless to say.

In FIG. 62A, the high-level network 5
The basic configuration of a packet transmitted / received between the management device 400 and the NAU 530 via the management device 20 is shown in FIG.
The basic configuration on the high-layer network 520 of the packets transmitted and received between the management device 400 and each unit (excluding the command packet that does not require ACK), and the NAU 530 shown in FIG. The basic configuration of packets transmitted and received between units via the low-layer network 510 is shown.

In FIG. 62, a packet head indicated by HHD is a packet head used in the high-layer network 520, and a packet head indicated by LHD is the low-layer network 510.
This is the packet head used in.

In the system of this embodiment, the NA
The communication control by U530 can be roughly classified into control that simply mediates communication and auxiliary control that substitutes for control of the management device 400. The auxiliary control means that the management device 400 entrusts the NAU 530 with communication control for information exchange which should be performed directly with the unit, and the NAU 530 exchanges information with the unit. Information that is not related to card data, such as a test, a store opening code, and scheduled data collection, corresponds to this. With this method, the management device 400 only needs to communicate with 25 NAUs 530,
Since 30 needs only to communicate with 23 units, the load on the management device 400 is greatly reduced.

On the other hand, at the time of mediation control, NAU 530 may simply remove or add a packet head to a transmitted / received packet.

That is, the packet of the format as shown in FIG. 62B transmitted from the management apparatus 400 to the unit is removed from the high-layer packet head HHD by the NAU 530 and sent out to the low-layer network 510, Management unit 4 from each unit with only packet head LHD
The packet sent and received toward 00 includes NAU53
At 0, the high-layer packet head HHD is added to the head of the LHD, and is sent out onto the high-layer network 520 as a packet in the format of FIG.

In Table 32, the definition of the unique data laid out in the head portion of each packet is described.

[0349]

[Table 32] 63 to 70 show examples of typical packet formats transmitted and received between the management device 400 and the NAU 530 on the high-layer network 520.

In the “line test” packet of FIG. 63 (A), the date / date code and the identification code (store code), the pachinko machine 100 belonging to the destination NAU 530, the issuing machine 200, And the minimum number of each. Then, the NAU 530 stores the date code and the identification code, and compares it with the number calculated based on the set value of the unit number setting switch 544 and the like, and instructs the management apparatus 400 to the management apparatus 400 in FIG. Is returned. Upon receiving the “line test” packet from the management device 400, the NAU 530 calculates in advance for all the units belonging to the NAU 530 itself based on the setting values of the unit number setting units and the number setting units 544 to 548. A "line test" packet to which only the low-layer network packet head LHD is attached is formed by using the transmitted address, and is transmitted to the second unit one after another while updating the address. From each unit, "A" containing the unit number, serial number, and channel number is entered.
CK "is received, and a unit table as a transmission address file is created and stored based on the received data.

FIG. 64A shows the structure of a “unit table request” packet from management apparatus 400 to NAU 530, and FIG.
K ”indicates the structure of the packet. When NAU 530 receives the“ unit table request ”packet,
An "ACK" packet containing the U status and data on all units in the unit table is returned.

FIGS. 65A and 65B show the management device 4
The structure of the “initial value setting” packet from 00 to the pachinko machine 100 and the response “ACK” packet on the high-layer network are shown. In the data column of this packet, initial values such as the purchased ball rate and the number of prize balls required for operation of the pachinko machine are entered and transmitted.

FIG. 65 (A) shows a pachinko machine 100.
"Initial value setting" packet for the issuing machine 200
In the “initial value setting” packet (not shown) for the balancer 300, a date code, an identification code, and a hot code are put in a data column and transmitted.

Further, FIGS. 66A and 66B show the structure of the "periodic data request" packet for the pachinko machine 100 and the response packet thereof among the "periodic data request" packets for the unit.

In the response packet to the scheduled data request shown in FIG.
Under the HD, the operation data of all the pachinko machines belonging to one NAU 530 is linked, and the head and data indicated by * 1 relate to the first pachinko machine,
* The head and data indicated by * 2 relate to the second pachinko machine, and the data for all pachinko machines follow in the same manner.

In the data column of a response packet (not shown) for a regular data request to the issuing machine 200 or the settlement machine 300, the transmission data area of all issuing machines (see [Table 10]).
And all the data in the transmission data area (see [Table 15]) of all payment machines.

FIG. 67 shows that the management apparatus 400 sends the payment
An example of the configuration of various command packets without data for 00 and their response packets is shown.

The packet type column PACKET @ T in FIG.
In the YPE, codes 90H (opening code), 91H (closing code), 95H (forced termination request), 96H (forced termination release), 8CH (line monitor check), or B1H
(Restart) is entered. In addition, the above-mentioned “forced termination request”, “forced termination release”, “restart”
Packet type (for the entire unit)
The packet has a column for entering a code indicating the type of the unit.

FIGS. 68 to 70 show a “card-in” packet transmitted to management apparatus 400 when a card CD is inserted into pachinko machine 100 and its acknowledgment packet “ACK” and negative acknowledgment packet “NAK”. 5 shows a format of a packet on the high-layer network 520 of FIG.

In the data field of the "card-in" transmission packet, a card text in which only the card number is written is read from the unit memory and sent. On the other hand, the response “ACK”
The data field of the packet contains the card text among the data related to the card read from the card file of the management device 400. In addition, the card state in the card text indicates the updated card state.

Note that the transmission / reception packet when the interruption switch is turned on, the transmission / reception packet when the interruption card is inserted, the transmission / reception packet when the settlement switch is turned on, the “return to zero” or “stop” occurs The configuration of the transmission / reception packet is the same as that of the “card-in” packet and its response packet in FIGS. 68 to 70, and the packet codes A2H, A1H, A3H, and A corresponding to the packet type column respectively.
The only difference is that 4H or A5H is entered and that different data of each card is entered in the card text in the data column. In particular, in the "card-in" packet, the card text "ball count", "amount" and "card status"
Column is "0", while other packets of the same type are designed to send data relating to the card in those columns as well.

FIGS. 70 and 71 show the low-layer network 5
10 shows a typical example of a format of a packet transmitted and received between the pachinko machine 100 and the NAU 530 via the PC 10.

Among them, FIG. 71 shows “scheduled data transmission”.
FIGS. 72A and 72B show examples of the structure of a packet, and FIGS. 72A and 72B show examples of the structure of a packet for transmitting and receiving “unit recovery data”.

Among these, the “scheduled data transmission” packet contains the transmission of the unit memory of the pachinko machine and all the data in the data area and sends it.
Receives this data and updates the data of the pachinko machine 100 in the P machine file.

On the other hand, the “unit recovery data” packet contains all the data in the P device file of the management device 400, the date read from the set value file, the identification code, and the hot code in the data area of the unit memory. Will be sent to match. However, the reception data packet head and the card text overlapping the transmission data area of the unit memory do not duplicate transmission, and the unit controller copies the transmission data area to the reception data area. In a response packet to the above packet, all data in the transmission data area is put and transmitted.

FIGS. 73 to 75 show the low-layer network 5.
10 shows a typical example of the format of a packet transmitted and received between the card issuing machine 200 and the NAU 530.

Of these, (A) to (C) of FIG.
A configuration example of a “card purchase” packet for requesting the management device 400 to issue a card issuance reservation, a response packet “ACK”, and a negative response “NAK” are shown.

[0368] In the data field of the "card purchase" packet at the time of card issuance reservation, only the issue receipt number m indicating the order number of the target card in the issue machine is entered, and the card amount, card number, Issue serial number is "0"
Send as On the other hand, in the data field of the response “ACK” packet, the management apparatus 400 inserts and issues the issue serial numbers n of all the issuing machines determined from the issue acceptance number m and the card numbers calculated from the issue serial numbers n. ACK
In the "check sum" column at the end of the packet, an added value from the issuer number to the issue receipt number is entered as a check code.

On the other hand, when bills are inserted into the issuing machine 200 and the purchase amount is determined, the issuing machine 200
The structure of the “card purchase” and its response packet sent to 00 is exactly the same as the packet shown in FIG. 73. The actual purchase amount is entered in the card amount column of the transmission packet, and the card number and issue serial number are entered in the columns of the card number and issue serial number. Is different from that of the first embodiment in that a number determined at the time of reservation is entered.

Further, FIG. 74 shows an example of the configuration of a "periodic data transmission" packet, and FIGS. 75A and 75B show an example of the configuration of a "unit recovery data" transmission / reception packet.

Among them, the “scheduled data transmission” packet contains all the data in the transmission data area of the unit memory 550 of the issuing machine and sends it.
Receives this data and updates the data of the issuing machine in the issuing machine file. However, among the transmission data, the card amount and the issue receipt number are data that are not used in the management device 400, and therefore, are not registered in the file even if transmitted.

On the other hand, in the “unit recovery data” packet, all data in the issuing machine file of the management device 400, the date read from the set value file, the identification code and the hot code are stored in the data area of the unit memory 550. I will send it according to the configuration. However, the received data packet head and the card text overlapping the transmission data area of the unit memory 550 omit the duplicate transmission,
The unit controller 290 copies the data from the transmission data area to the reception data area. The data indicated by * 4 in the received data is the unit memory 55
This is written in the reception data area in 0. In the response packet to the above packet, only the entire data in the transmission data area is inserted and transmitted.

FIGS. 76 to 79 show the low-layer network 5.
10 shows a typical example of a format of a packet transmitted and received between the card settlement machine 300 and the management device 400 on FIG. Among these, (A) to (C) of FIG. 76 show a “card settlement” packet requesting the card settlement to the management device 400 and its response packets “ACK” and “NA”.
K "shows a configuration example.

At the time of card settlement, only the card number read by the card reader of the settlement machine 300 is transmitted in the data field of the “card settlement” packet. On the other hand, in the data field of the response "ACK" packet, data of the card read and read from the card file using the issue serial number n calculated from the card number in the management device 400 is sent.

On the other hand, when payment processing such as refund of unused money or issuance of a receipt printed with the number of balls in the payment apparatus 300 is completed, “card payment end” sent from the payment apparatus 300 to the management device 400 and its response Figure 7 shows the structure of the packet.
FIG. Only the card number is put in the data field of the transmission packet and sent. The data field is unnecessary for the response packet.

Further, FIG. 78 shows an example of the structure of a “scheduled data transmission” packet from the settlement machine 300, and FIG.
(A) and (B) show a configuration example of a transmission / reception packet of “unit recovery data” relating to the settlement machine 300.

[0377] Among them, the "scheduled data transmission" packet contains all the data in the transmission data area of the unit memory 550 of the settlement machine 300 and sends it, and the management device 400 receives this data and sends it to the settlement machine file. The data of the payment machine 300 is updated. However, among the transmission data, the card number is data that is not used in the management device 400, and therefore is not registered in the file even if transmitted.

On the other hand, the “unit recovery data” packet includes all data in the checkout machine file of the management device 400,
The date, the identification code and the hot code read from the setting value file are sent according to the configuration of the data area of the unit memory 550. However, the reception data packet head and the hot code overlapping with the transmission data area of the unit memory do not duplicate transmission, and the unit controller 390 copies the reception data area from the transmission data area. The data indicated by * 6 in the received data is written in the received data area of the unit memory 550. In the response packet to the "unit recovery data" packet, all the data in the transmission data area are put and transmitted.

The packets shown in FIG. 62 to FIG. 79 are not the whole of the original packet put on the network but only the main part, and in addition to the above-mentioned packet, an alert for finding the head of the data. There are a header section including a burst or synchronization data, a source address field indicating a transmission source, a count section indicating a data length, and a check code section for error detection. These are automatically generated and added by the network controller 553 in the unit control device of each terminal.

[0380] The "PADDING" portion added to the end of each packet in Figs. 63 to 70 is a dummy data field added to adjust the length of the packet data to a predetermined length. .

Next, the two networks 510 and 5
20, which mediates data transmission.
A control procedure of the data transmission controller 535 in U530 and a procedure of low-layer network abnormality detection processing by a timer interrupt will be described with reference to FIGS. 80 and 81.

When the power of the NAU 530 is turned on and a reset pulse is supplied, the data transmission controller 535
Starts the initialization process shown in FIG.

Then, first, the NAU number setting device 544 provided on the upper surface of the unit main body 539, the pachinko machine 100
Alternatively, the minimum number setting device 545 of the checkout machine 300, the connected number setting device 54 of the pachinko machine 100 or the checkout device 300
6. The setting values of the issuing machine minimum number setting device 547, the number of issuing machine connection devices 548, and the NAU type setting device 549 are read (steps S1 to S6).

Then, based on the unit number and the number read in step S1, the own address on the high-layer network 520 and the unit number and address (unit number) of each terminal on the low-layer network 510 under its control , The serial number and the channel number are calculated by the method described above (step S7).

After that, the network controller 53
After initializing by giving initial value data to 3, 537 (step S8), the unit number, serial number, and channel number calculated in step S7 are written into the monitor table (regular data storage area) in the data memory 536, and , The type of each unit (the distinction between the pachinko machine and the issuing machine) is determined and written from the set value of the NAU type setting device, and the other operation data is cleared to "0" (step S9). Then, the NAU number and the type name, the unit number, the serial number, and the channel number of each unit are written in the unit table (transmission address storage area) in the data memory 536, and the NA in the unit table is written.
Each bit of the U status and monitor information 1 is cleared to "0" (step S10).

Next, the data transmission controller 535
It waits for a packet to be sent from the master control device 401 of the management device 400 (step S11), and upon receiving the packet, determines whether the packet is a "line test" or a "unit table request" (step S1).
2, S13).

If it is determined that the received packet is a "unit table request", the process proceeds to step S13.
Then, the process goes from S14 to S14, and transmits an “ACK” packet containing the data of the unit table read from the data memory 536 to the management device 400.
After setting the second timer and starting the timer interrupt, the process returns to step S11 to wait for the reception of the next packet (step S15).

On the other hand, if the received packet is "line test"
In step S12, the process proceeds from step S12 to step S21, where an "ACK" packet is first transmitted to the management device 400, and then the value of the unit number setting unit 546, 548 is used to determine the unit connected to the NAU. The number is set in a counter or the like (steps S21, S22). Next, step S
A "line test" packet is transmitted to each unit under its control using the address calculated in step 7, and a timer is set (steps S23 and S24). Then, the timer is checked, and "A"
When the "CK" packet returns, the token bus abnormality bit B6 of the monitor information 1 for the corresponding unit in the monitor table is cleared to "0" (steps S25 to S25).
27). If the "ACK" packet has not returned within the predetermined time, the token bus abnormal bit B6 of the monitor information 1 is set to "1" (step S28).
Then, after subtracting (-1) from the counter set in step S22, it is determined whether or not it has become "0", thereby determining whether or not transmission of the "line test" packet has been completed for all units. Step S when finished
Returning to step S23, the packet is sent to the next unit. When the processing is completed for all the units, the process returns to step S11 to wait for the reception of the "unit table request" packet.

Further, if the received packet is neither "line test" nor "unit table request" in step S11, it is determined in step S16 whether or not the packet is a registered packet other than those described above. Step S11 after executing the processing corresponding to the packet
And waits for reception of the next packet (step S1).
7).

[0390] NAU5 corresponding to each received packet
The process of 30 is a mere mediation process (removal or addition of a packet head) of data transmission between the management device 400 and the unit, or an auxiliary process of transmitting a command packet to each unit in place of the management device 400. Since the description will gradually become clear in the following description of the flow of the entire system, the description is omitted here.

On the other hand, when an interrupt signal comes in every one second from the interrupt timer set in step S15,
The data transmission controller 535 of the NAU 530 is configured as shown in FIG.
First, the low-layer network abnormality detection process is started. First, the number of connected units read in steps S3 and S5 is set in a counter, and then it is determined whether or not regular data has been received from each unit within the past 3 seconds (step S3
1, S32). If it has been received, the process jumps directly to step S34. If it has not been received, in step S33, the token bus abnormal bit B6 of the monitor information 1 in the column of the unit in the regular data storage area of the data memory 536 is set to " After that, the process proceeds to step S33. Then, the counter set in step S31 is subtracted, and it is determined whether or not all the units have been checked by determining whether or not the value has become "0". If not, the process returns to step S32 and the above procedure is performed. repeat. As a result, it is possible to detect a communication abnormality in the low-layer network and to embody it in the monitor information 1.

Next, the operation of the pachinko gaming system in which sales are performed while data is transmitted between the management device 400 and each terminal using each packet shown in [Table 31] will be described.

FIG. 82 shows a flow of the procedure of the initialization of each terminal and the line test of the network by the management device 400.

When the power of the system is turned on, in the management device 400, first, the central processing unit CPU stores the main memory M-
After clearing all the files FL1 to FL6 in the MEM, a file (framework) is created (step S25)
01). On the other hand, the local processing device 413 first displays an initial screen on the CRT display device 411, and then notifies the central processing unit CPU of the date and time (steps S1501, S1).
502). Then, when the central processing unit CPU does not determine the presence or absence of the power failure file, it reads out the initial setting values such as the number of terminals, the number of prize balls, the number of hits from the hard disk (auxiliary storage device 1) setting value file, and Initialize each file in the storage device and generate a random number for calculating a card number from the card issue serial number (step S).
2502 to S2504). Then, when a line test request command is sent from the local processing device 413,
A line test is started using the NAU address in the transmission address file (steps S1503, S250
5). That is, each N
A “line test” packet is transmitted to the AU 530. At this time, the local processing device 413 displays a message “line test in progress” on the CRT display 411 and waits for a response of the line test result (step S1504). The “line test” packet is transmitted with the date and identification code (store number) added together with the packet head.

On the other hand, when the power is turned on, the NAU 530 first reads the set values (NAU number, minimum number, number of terminals, etc.) from the NAU number setting units 544 to 549, calculates the network transmission address of each terminal, and sets the unit table. Is created, the transmission address of each unit (terminal) and the NAU itself is recognized, and the monitor table for storing the operation data of each unit is cleared (steps S3501 to S3504). And the management device 40
0 on receipt of a "line test" packet from NAU
530 returns an “ACK” packet containing the transmission address calculated by itself in the unit table (step S35)
05, S3506). The address calculated by the NAU 530 based on the set value read from the setting device is the
In step 2503, the management apparatus 400 should match the NAU address loaded from the data in the setting value file FL1. Recognition of the same address enables each other to communicate with each other.

When management apparatus 400 receives the “ACK” packet from NAU 530, the corresponding N
It can be recognized that there is no line abnormality with the AU 530, and the above procedure (steps S2505 to S250
By repeating 6) by the number of NAUs 530, the check of all the lines is completed, and thereafter, the processing shifts to the unit table request processing (FIG. 83).

On the other hand, the unit controller 18 of each terminal
When the power is turned on, first, the data transmission controller 551 in the unit clears the entire data area of the unit memory 550 and then transfers data to a predetermined address “27FF” in the unit memory 550. Write (steps S4501, S4502). Then, a predetermined terminal INT of the unit memory 550 rises to a high level. The unit controller 190 of each terminal,
After power-on, the internal memories, registers, and I / O ports are initialized, and when the rise of the initialization signal INT from the unit memory 550 is detected, a set value (unit number) is read from the unit number setting device. After calculating the lower order of the serial number and the channel number, they are written in the transmission data area of the unit memory 550 (steps S5501 to S5504). The unit address is recognized on the unit side by reading it by the data transmission controller 551 (step S45).
03). With this, NAU53 using token bus
0 and data transmission between each terminal.

Thereafter, a “line test” packet to which the data (date and identification code) already received from management device 400 is added is transmitted from NAU 530 to each unit (terminal), and data transmission controller 551 on the unit side is transmitted. After receiving it, the received date and identification code are written in unit memory 550, and then NAU 53
"ACK" packet is transmitted to the P.0 (step S450)
4, S4505). Unit controllers 190 and 29
When 0, 390 receives the identification code via the unit memory 550, it waits for the reception of the initial value (steps S5505, S5506). Further, when NAU 530 receives “ACK” from data transmission controller 551, it transmits “line test” to the next unit, and repeats this for all units.
The line test of No. 10 is completed, and a unit table request is awaited (steps S3507 to S3509).

FIG. 83 shows a processing procedure of a unit table request and a subsequent line test.

[0400] When the initialization processing described above is completed, the management device 400 starts unit table request processing, and the central processing unit CPU transmits a "unit table request" packet to each NAU 530 (step S251).
1). Then, NAU 530 receives the packet and places “ACK” (= 08) in the PACKET @ TYPE column.
H) followed by the NAU number and NAU status (token bus error, opening code received, NA
"AC" consisting of bits indicating the U normal state and the above-mentioned unit table data (unit number and type flag, unit number, serial number, channel number and monitor information 1 for each unit) by the number of units.
K "packet is transmitted (steps S3511, S35).
12).

When the central processing unit CPU receives this unit table, it compares it with the address in the transmission address file FL6, and if there is any unregistered one, adds and saves the transmission address file on the hard disk. It checks the monitor information 1 sent from the server, transmits the result of the line test to the local processing device 413, and waits for a command (steps S2512 to S2514).

The local processing unit 413, upon receiving the line test result and no abnormal terminal, immediately transmits an initial value setting command to the central processing unit CPU. On the other hand, when there is an abnormal terminal, on the screen of the CRT display device 411,
An abnormal terminal is displayed, and the opening of the store switch on the console 412 is waited for, and an initial value setting command is transmitted to the central processing unit CPU when a store opening request is made.
(Steps S1511 to S1513).

Upon receiving the initial value setting command, the central processing unit CPU reads out the initial value of each unit from the setting value file FL5 of the main memory M-MEM and stores the initial value in the data section (year, month, day, An “initial value setting” packet including an identification code, a purchase ball exchange rate, an initial value such as the number of main prize balls, the number of sub prize balls, the number of hits, a hit mode, and a hot code is transmitted (steps S2515 and S25).
16).

Then, NAU 530 receives the packet, removes the high-layer network head, transmits an “initial value setting” packet to each unit via the low-layer network, and sends a hard ACK from the network controller of each unit. Upon receiving the (response signal), an “ACK” packet is transmitted to the management device 400 (steps S3513 to S3515). Central processing unit CPU
Confirms the receipt of “ACK” from all units,
The end of transmission of the initial value is transmitted to the local processing device 413, and waits for the opening request command (step S2).
517, S2518).

The local processing device 413, which has received the end of the initial value transmission, displays a store opening request message on the screen of the CRT display device 411 and waits for the store opening switch to be turned on (steps S1514, S1515).

On the other hand, on the lower layer network 510 side, N
When the specified unit receives the packet transmitted from the AU 530, the initial value setting command is written to the command register CR2 in the unit memory (550),
The received initial value is written in the reception data area (step S4511). Then, the unit controller 19
When 0, 290, and 390 read the command in the unit memory and confirm the reception of the initial value, the packet head portion of the reception data area is copied to the transmission data area to create the transmission head, and the hot code is also received. Monitor information 1 after copying from area to transmission area
Is changed to "0" (set already), and when there is an initial value request from the card reader, the function in which the initial value is entered is returned (steps S5511-S5).
514). On the other hand, the fact that the initial value unset bit of the monitor information 1 has been set to “0” causes the data transmission controller 551 to set a regular timer and start transmitting regular data (step S4512).

FIG. 84 shows a procedure for periodically collecting operation data functioning as operation data collection means from each terminal after setting initial values.

Unit control devices 180 and 28 of each terminal
When the transmission controller 551 in 0,350 confirms a fixed time, for example, every 1 second by an interrupt from its own timer, the transmission controller 551 reads the operation data written in the transmission data area SDA in the unit memory 550, and In a “scheduled data transmission” packet, put it on the low-layer network 510, and send it to the NAU 530 (steps S4521 to S4523). When NAU 530 receives the scheduled data from each unit, NAU 530 checks the write flag to check whether the monitor table storing the operation data for each unit formed in its own memory is in a writable state, and After waiting until it becomes "0", the unit table is updated with the received regular data (steps S3521 to S3523). Management device 40
This is to prevent the data from being rewritten during the scheduled data transmission to 0. The periodic data collected by the NAU 530 is stored in the unit controller 19 of each terminal.
0, 290, and 390 download the operation data of the terminal in real time and write it in the unit memory 550 one after another. If the scheduled data cannot be collected three consecutive times, the token bus abnormal bit of the monitor information 1 is set to “1” (step S352).
8).

On the management apparatus 400 side, the central processing unit CPU confirms the scheduled time every second by interruption from its own timer, starts the scheduled data request processing, and sends a “timed” to each NAU 530. A "data request" packet is transmitted (S2521, S2522). When the designated NAU 530 receives the packet, it sets a write flag and then transmits an "ACK" packet containing the data of the monitor table to reset the write flag (steps S3524 to S3527). When this is received by the management apparatus 400, the monitor information is checked, and if there is an abnormal terminal, the abnormal terminal is notified to the local processing apparatus 413, and the unit abnormality is interrupt-displayed on the screen of the CRT display apparatus 411. Is rewritten with the scheduled data (steps S2523-S
2525).

FIG. 85 shows the flow of the store opening process after the management device 400 sets the initial values for each terminal.

[0411] After completion of the above-described preparation processing such as the line test and the initial value setting, the console 412 of the management apparatus 400
When the upper store opening switch 421 is turned on, the local processing device 413 transmits a store opening request command to the central processing unit CPU. Then, the central processing unit CPU “store opening code”
A packet is formed and transmitted to each NAU 530 (steps S1531, S2531). When NAU 530 receives the packet, it transmits an “ACK” packet to management device 400 and then removes the high-layer network head from the received packet and transmits a “store opening code” packet to each unit via the low-layer network. (Steps S3531 to S3533).

[0412] The management apparatus 400 checks all NAUs 530
, The mode is changed to “in business”, the process shifts to normal business processing, and a response is returned to the local processing device 413 (step S2532). Then, the local processing device 413 performs a normal display on the screen of the CRT display device 411, displaying a message indicating that the service is open, a switch name on the operable console 412, and an operation method (step S1532).

On the other hand, when the data transmission controller 551 of each terminal receives the “store opening code” packet transmitted from the NAU 530, each of the unit control devices 180, 2
The "opening code" is written in the command register CR2 of the unit memory 550 in the units 80 and 350, and is read by the unit controllers 190, 290 and 390, whereby the card reader controllers 188, 288 and 38 are read.
8 permits card acceptance and issuance, sets the bill validator 210 of the card issuing machine 200 in a bill acceptable state, and displays 164, 221, external to each terminal.
341 is turned on to notify the player that the terminal is in operation (step S45).
31 to S4533, steps S5531 to S553
3).

FIG. 86 shows a procedure of a card issuing process by the card issuing machine 200.

[0415] After the initialization, the unit controller 290 of the card issuing machine 200 starts the issuance reservation processing even before the actually purchased bill is inserted into the issuing machine 200, and firstly sets the amount to "0". The transmission request command of the “purchase card” packet is written in the command register CR1 of the unit memory 550, and the issue acceptance number in the transmission data area is updated (step S5541). Then, the data transmission controller 551 gives the issue acceptance number as a number indicating the order of acceptance for each issuing machine. "Card purchase" packet (=
0) and transmit it to NAU 530 (step S
4541). When NAU 530 receives this packet, it adds a high-layer packet head and sends it to management device 400 (step S3541). Then, the central processing unit C
The PU checks whether the card number in the packet is “0”, reads the number of issuances from the file of the issuing machine 200 that sent the packet, compares it with the issuance number, If it is determined that there is, an issue serial number and a card number are calculated, a card file is created, and an “ACK” packet containing the card number is sent to the NAU5.
30 (steps S2541-S2544).
The issuance serial number is obtained by adding the number of issuances in all issuing machines.

[0416] Upon receiving the "ACK", the NAU 530 removes the high-layer packet head from the packet and issues the packet to the issuer 20.
0 to the unit controller 280 (step S3).
542). When the data transmission controller 551 in the unit control device 280 receives the “ACK”, the fact is notified to the unit controller 290 via the unit memory 550 (step S4542). Then, the unit controller 290 sends a “card issue” function in which the card number is entered to the card issuing device 700. In response to this, the card issuing device 200 takes out one card from the card tank, supplies the card to the card reader 800, records the card number in the magnetic recording unit MG, and stands by (step S5542).

Thereafter, the bill insertion slot 211 of the issuing machine 200
When the bill is actually inserted, the bill discriminator 210 identifies the bill and informs the unit controller 290, lights the lamp in the purchase selection switch 212, prompts the user to make a selection, and displays the amount of money inserted. Is displayed on the display 213. Then, when one of the purchase selection switches 212 is turned on and the purchase amount is designated, the unit controller 290 confirms the amount and the unit memory 55
The "card purchase" command is written in the command register CR1 in "0", and the purchase amount of the card is written in the transmission data area (step S5543).

[0418] Next, the data transmission controller 551 reads this to form a "card purchase" packet, and inserts the purchase amount and the reserved card number into the NAU 530.
And the NAU 530 attaches the high-layer network head to this and transmits it to the management device 400 (step S4).
543, S3543). When the management device 400 receives the “card purchase” packet, it checks the card number, purchase amount, and issue serial number in the packet and determines that the card purchase is an actual card purchase. "ACK" after writing the amount
Transmit the packet (steps S2545 to S254)
7).

[0419] This "ACK" packet is
0, the head for the high-layer network is removed, sent to the low-layer network 510, and received by the data transmission controller 551 of the designated issuing machine 200 (steps S3544, S4544). Then
The transmission controller 551 notifies the unit controller 290 of the reception of the ACK via the unit memory 550. After that, the unit controller 290 transmits an issue function including the purchase amount to the card issuing device 200 (step S5544). Then, the purchase amount of the waiting card is printed and ejected. At this time, if there is a change, the unit controller 290 gives a change payout command to the balance payout unit 230, turns off the lamps L1 to L5 in the purchase selection switch, and clears the display of the amount display unit 213 to "0". Also, the money data such as the deposit amount in the transmission data area is updated (steps S5545 and S5546).

As described above, when a card is issued, a card issuance reservation is made in advance, the card number is recorded, and the card is kept on standby. At the time of actual bill insertion, only the purchase amount is printed and ejected. The waiting time until card issuance can be greatly reduced.

FIG. 87 shows the procedure from the insertion of the card CD into the pachinko machine 100 to the start of the game until the game is actually started.

Control unit 1 above pachinko machine from outside
When the card CD is inserted into the card insertion / ejection opening 802a of the card 60, the card reader 800 reads the information recorded on the punched hole and the magnetic surface of the card CD, removes the settled or zero-reset card, and removes the other cards. For the card, the date and identification code (store number) are checked. If the date or code does not match, the card is ejected as it is.
Transfer to

Then, the unit controller 190 receives the card number, writes a command indicating that the card has been inserted into the command register CR1 in the unit memory 550, and writes the card number in the transmission data area, and writes the “card-in” packet. A transmission request is made (step S5551). The data transmission controller 551 has a code of “card-in” in the head part, transmits a packet in which the card number is put in the data part to the NAU 530 via the low-layer network, and when the NAU 530 receives the packet, the head for the high-layer network is set. The data is attached to the head and transmitted to the management device 400 (steps S4551 and S355).
1).

[0424] When the management apparatus 400 receives the card number from the NAU 530, it calculates the issue serial number n from the card number and outputs the card file FL1 in the main memory M-MEM.
Then, the data of the corresponding card is read (step S2).
551-S2553). Then, the card number in the file is compared with the received card number and the card number does not match, or the state of the card in the card file is checked and it is determined that it is not appropriate to start the game ( In the case of a settlement card or the like, a "NAK" packet as a response rejection signal is transmitted (step S25).
54-S2556). Then, the NAU 530 receives the packet, removes the head for the high-layer network, and sends it to the low-layer network 510. The data transmission controller 551 of the designated unit receives “NAK” and receives a command in the unit memory 550. Register CR2
A command indicating that the response has been rejected is written in (steps S3552 and S4552). This is read by the unit controller 190 to confirm that the response is rejected, and the card is ejected from the card reader 800 (step S55).
52).

On the other hand, when the central processing unit CPU confirms that the card is appropriate, the card file FL1
And the P machine file FL2 ([Table 24] and [Table 26]) are updated. That is, the card status is updated from "free status" to "playing", and the number of the terminal (pachinko machine) where the card is located or the card number is written in the corresponding table, and then the card text (amount, holding amount) is written. Then, an "ACK" packet as a response signal is transmitted with the number of balls (steps S2557, S2558).

When the specified NAU 530 receives this packet, it removes the head for the high-layer network and sends it out to the low-layer network 510. When the data transmission controller 551 of the specified unit receives this packet, it stores the packet in the unit memory 550. Command register CR2
Into the received data area (steps S3553 through S3553).
4553).

Then, when the unit controller 190 reads the command in the unit memory 550 and confirms that there is a response, the game control is started while the card is held in the card reader 800 and the transmission of the unit memory 550 is performed. The operation information in the data area SDA is changed to "playing", and the number of balls held and the amount of money are displayed on the number-of-balls display 112 and the amount display 111. If the amount is not zero, purchase is indicated. The lamp 121 is turned on to display a purchase available state (step S5553,
S5554).

FIG. 88 shows a procedure of processing when the interruption switch 114 of the pachinko machine 100 is turned on during a game.

[0429] When the suspend switch 114 is pressed, the unit controller 190 suspends the game control, and then changes the card state of the card text in the transmission data area of the unit memory 550 to "suspending" to change the shared data. The command of "interrupt switch ON" is written in the command register CR1 of the area (step S5).
561). Then, the data transmission controller 551 reads this and forms an “interruption switch” packet,
The card text is inserted in the data section and transmitted to NAU 530 (step S4561). Upon receiving the packet, NAU 530 attaches the head for the high-layer network to the head and sends it to management apparatus 400 (step S3561).

[0430] Upon receiving the card number, the management apparatus 400 reversely calculates the issue serial number n from the card number in the card text, reads the card file FL1 in the main memory M-MEM, reads the location number in the file and the location number in the packet. If the card numbers do not match, or if the card status in the file is not playing or interrupted, N
AK is transmitted (steps S2561 to S2566).
On the other hand, if the unit numbers match and the card status is also in a game, the data of the corresponding card is updated, and then an "ACK" packet is attached with a card text and transmitted as a response signal (steps S2567 and S2568). When NAU 530 receives “NAK” or “ACK”, it removes the high-layer network head and sends it out to low-layer network 510 (steps S3562 and S3563).

Then, the unit control device 180 of the transmission destination
Receives the “NAK” or “ACK” packet and transmits the unit memory 55
NAK or ACK is put in the command register CR2 in 0, and in the case of ACK, the card text is further written in the reception data area (steps S4562, S456).
3). When the unit controller 190 confirms the reception of the NAK, the card state is returned to the original "game", and the game control is restarted (step S5562). When it is confirmed that the ACK has been received, the card is ejected from the card reader 800, and then the transmission data area SD of the unit memory 550 is read.
The operation information in A is changed to “interrupted”, the lamp 121 built in the purchase switch 113 provided in the pachinko machine 100 is turned off, and the display state of the game state display lamp 123 and the like is displayed as “interrupted” (flashing). (Steps S5563 and S5564).

Next, FIG. 89 shows the pachinko machine 100 being suspended.
2 shows a processing procedure when a card CD is inserted.

The procedure in this case is almost the same as the procedure for card-in shown in FIG. That is,
Processing Steps S5571-S2571 for Informing that Card Has Been Inserted from Pachinko Machine 100 to Management Device 400
87 corresponds to the processing steps S5551 to S2551 in FIG. 87, and the transmission processing steps S2572 to S5573 of the “ACK” as an acknowledgment thereof correspond to the processing steps S2 to S2553 in FIG.
552 to S5553, and a negative response "NAK"
The transmission processing steps S2572 to S5572 correspond to the processing steps S2552 to S5552 in FIG. 87, respectively.

[0434] The difference is that a "suspended card-in" packet is used as a transmission packet instead of a "card-in" packet. 800
This is that the card is more ejected, and the management apparatus 400 does not update the P machine file FL2. This is because the update of the P machine file has already been performed when the interruption switch is turned on. Note that the card file F
L1 updates the card status from "interrupted" to "during game". Further, the display state of the game state display lamp 123 is changed to a game display (lighting).

FIG. 90 shows the procedure of the game end processing when the game end switch 115 is pressed in the pachinko machine 100. The procedure in this case is substantially the same as the processing procedure when the interruption switch is turned on in FIG.

That is, when the end switch 115 provided at the lower part of the pachinko machine 100 is pressed, the unit controller 190 detects this and detects the
In addition to rewriting the card state of the card text in “0” from “playing” to “free”, the unit memory 55
A command indicating that the end switch has been turned on is written into the command register CR1 within 0 (step S558).
1). Then, the data transmission controller 551 reads this, inserts the card text, and presses the “end switch”
Form a packet and send N
The data is transmitted to the AU 530 (step S4581). NAU
Upon receiving the packet, 530 attaches the head for the high-layer network to the head and sends it to the management device 400 (step S3581). Thereafter, the processing procedure when the interruption switch 114 of the pachinko machine 100 is turned on (FIG. 88)
"ACK" is returned to the unit controller 180 according to the same procedure as in steps S2561 to S2568 (steps S2581 to S2588), and the card reader 8
The card is ejected from 00 (step S5583), and the operation information on the pachinko machine in the unit memory 550 is changed to "free state (waiting for customer)". The display of the ball number display 112 and the amount display 111 is “0”.
And the lamp 121 and the status display lamp 123 in the purchase switch, which indicate that the purchase is possible, are turned off.

FIG. 91 shows a procedure of processing when both the number of balls held and the amount of money become zero during a game (referred to as “return to zero”).

[0438] When the unit controller 190 of the pachinko machine 100 detects the occurrence of the zero return, the firing of the hit ball is stopped, the card state in the unit memory 550 is changed to "return to zero", and the return to zero command is stored in the command register CR1. Is written (step S5591). Then, the data transmission controller 551 forms a “return-to-zero” packet, inserts the card text in the transmission data area of the unit memory 550, and transmits it to the NAU 530 (step S459).
1). When NAU 530 receives this “return-to-zero” packet, it adds a high-layer packet head and sends it to management device 400 (step S3591). In the management device 400,
When the "return-to-zero" packet is received, the issue serial number is calculated backward from the card number in the packet, and the file of the card is read from the file in the main memory M-MEM using the issue serial number, and the card status and the terminal terminal If the card number is checked and the card status is other than "playing" or the unit numbers do not match, a NAK is transmitted (steps S2591-S259).
2595).

On the other hand, if the card status is correct and the unit numbers match, the number of balls, the amount of money, the card status (during game play → return to zero), the terminal number where the terminal is located in the card file are updated, and the card history data is written. Then, ACK is transmitted (steps S2596 to S2598). NA that received ACK
U530 removes the high-layer packet head and transmits the packet to the specified unit (step S3593). When the data transmission controller 551 of the unit receives the "ACK" packet, it writes an ACK reception command in the command register CR2 of the unit memory 550 and a card text in the reception data area (step S459).
3). Then, after the unit controller 190 confirms the ACK reception and instructs the card reader 800 to make a return zero hole and eject the card, the transmission data area S
The operating information of the DA is changed to “free”, the number of balls held and the display of the amount indicator are set to zero, and the purchase lamp 12 is changed.
1 and the game state display lamp 123 and the analog display 163
Is changed to the display indicating "free" (steps S5593 and S5594).

FIG. 92 shows a processing procedure when the unit controller 190 determines that the number of prize balls discharged or the like has reached the number of hits according to the initially set hitting mode and the game has been hit during the game. . The processing in this case is almost the same as the procedure of the zero-zero processing in FIG.

[0441] That is, since the processing factor (pause) has occurred on the pachinko machine 100 side, it is managed by the management apparatus 400.
91 correspond to the processing steps S5591 to S2591 in FIG.
File Update and Response “AC” in Management Device 400
The transmission processing steps S2602 to S2609 of "K" correspond to the processing steps S2592 to S2598 of Fig. 91. The difference is that the unit memory 550 is used when the unit controller 190 determines that the hitting has occurred.
A command "stop" is entered in the command to change the card state to "stop" (step S5601), and a "stop" packet is used for transmission (step S4601).
After confirming the ACK, the operation information in the transmission data area SDA of the unit memory 550 is set to “stop” instead of “free”, and the purchase enable lamp 121 is turned off to clear the display of the number of stops and the amount of money to zero and state Indicator lamp 123
Or the analog display 163 is stopped (blinks).

In addition, the card reader 800 makes it impossible to accept the next card after the card is ejected, and the management device 400 changes the operation information in the pachinko machine file to "stop" together with updating the card file (step In step S2606, an interruption message of the hitting table is displayed on the CRT display device 411, and the hit information is printed by the printer 408 (step S2608). Further, similarly to the update of the card file FL1, the fact that the state of the pachinko machine has changed to "stop" is registered in the P machine file FL2 (step S2607).

FIG. 93 shows the procedure of card settlement processing in the settlement machine 300. Card reader 8 of checkout machine 300
When the card CD is inserted at 00, the information recorded on the magnetic surface of the card CD is read, the date and the identification code are confirmed, and if they match, the card number is transferred to the unit controller 390. Unit controller 390
Is the command register CR1 in the unit memory 550.
, And a card number in the transmission data area (step S5611). Then, the data transmission controller 551 reads it, forms a “card payment request” packet, inserts the card number, and transmits it over the low-layer network 510 (step S4611). Then, the NAU 530 receives it, attaches the high-layer network head to the head of the packet, and transmits the packet to the management device 400 (step S3611). When the management device 400 receives the packet, it reverses the issue serial number (n) from the card number, searches the card file FL1 based on that, reads the corresponding card text (card information), and checks the card state ( Steps S2611 to S2614). Here, if the card status is not appropriate, for example, if the payment has already been completed, or if the return to zero (both the possession and the amount of money are zero), a "NAK" packet indicating payment refusal is formed and transmitted. (Step S2615). Then, the NAU 530 receives it, removes the high-layer network head, and transmits it to the unit controller 350 of the requesting settlement machine 300 (step S3612). Then, the data transmission controller 55
1 receives it, writes "Response rejected" to the command register CR2 in the unit memory 550, reads and confirms it with the unit controller 390, and ejects the card from the card reader 800 (step S46).
12, S5612).

[0444] On the other hand, if the management device 400 determines in step S2614 that the card status is appropriate, it forms an "ACK" packet as a response signal, and sets the payment data (holding ball) read from the card file. NAU 530 removes the high-layer network head from the packet and transmits it to unit control device 350 (steps S2616 and S361).
3). Then, the data transmission controller 551 receives the command and the command register C in the unit memory 550.
ACK is written to R2, and received data such as adjustment data is written to the reception data area RDA (step S461).
3) The unit controller 390 reads it and confirms that there is an affirmative response, and displays the number of possessed balls (including acquired balls) on the ball number display 303 and the unused amount on the amount display 304, respectively. Display and the printer 33
In addition to issuing a receipt (prize exchange voucher) printed with details such as settlement data by 0, if there is unused money, the unused balance is discharged from the bill dispenser 321 and the coin dispenser 325 (steps S5614 to S5616). .

[0445] Thereafter, the unit controller 390 punches a punch hole in the card held by the card reader 800 and ejects the card as a settlement-completed card. The card text is written in the transmission data area (step S5617). Then, the data transmission controller 551 reads this, forms a “payment end” packet, and transmits the packet. The NAU 530 attaches a high-layer network head to the head of the packet and sends it to the management device 40.
0 (steps S4614 and S3614).

[0446] The management apparatus 400, having received the "payment end" packet, reverses the issue serial number n again from the card number in the packet, searches the card file FL1 based on that, reads the card data, and checks the card state. When the card status is “interrupted”, the pachinko machine 100 executes the interruption end process shown in FIG.
After changing the card status to "payment completed" and updating the card history, an "ACK" packet is transmitted to NAU 530 (steps S2618 to S2621).

[0447] When NAU 530 receives "ACK", it removes the high-layer packet head and sends it to unit controller 350 of payment machine 300. When transmission controller 551 receives this, it notifies unit controller 390 via unit memory 550, Unit controller 39
When 0 confirms the reception of "ACK", the next card can be accepted (steps S3615 to S5618).

As described above, the settlement data is sent from the management device 400 in response to the card settlement request from the settlement machine 300, and when the settlement is completed, the management device 40 informs the management device 40 that the settlement has been completed again.
0, and the first time that the payment has been processed is handled at that time. Therefore, even if an accident such as a power failure occurs during the payment in the payment machine 300, the payment data is stored in the FL1 of the card file. As a result, the settlement process can be continued immediately after recovery from the power failure. As a result, there is no possibility that the player will be disadvantaged, and the reliability of the system is improved. In addition, in the above embodiment, since the history data is also printed on the settlement receipt (prize voucher), the credibility of the printed settlement data (number of balls) is increased, and the reliability of the system is increased. Will be able to

[0449] Fig. 94 shows the interruption release processing procedure associated with the card settlement processing described above.

That is, in the system of this embodiment, the game is interrupted by the above-described interrupting process (see FIG. 88), and the interrupted pachinko machine 100 that refuses to accept another card is released from the interrupted machine. When the inserted card is inserted into the checkout machine 300 and the checkout process is performed, the interruption is released by a command from the management device 400.

When the suspended card is inserted into the settlement apparatus 300, the settlement processing (see FIG. 93) is executed by data transmission between the settlement apparatus 300 and the management apparatus 400, and when the management apparatus 400 confirms the end, Then, an “interruption end” packet is transmitted to the corresponding interrupted pachinko machine 100 based on the card information (step S2622). This packet is temporarily received by the NAU 530, and is transmitted to the corresponding unit control device 180 of the pachinko machine 100 after the high-layer network head is removed (step S3621). When the data transmission controller 551 receives this packet, the unit memory 550
Is written in the command register CR2 in the memory, and when the command is read and confirmed by the unit controller 190, the card can be accepted by the card reader 800 and the unit memory 5
The operation information relating to the pachinko machine 100 in 50 is changed from “interrupted” to “free” (step S462).
1, S5621, S5622). Pachinko machine 100
The display of the number-of-balls display 112 and the amount display 111 on the front is cleared to "0", the lamp 168 indicating whether or not a card can be inserted is flashed, and the display of the analog display 163 is set to a customer waiting state (scroll). Yes (Step S5
623-S5625).

On the other hand, the NAU 530 transmits the “interruption end” packet from the management apparatus 400 to the unit control
K, the response signal “AC” to the management device 400 is received.
When the management apparatus 400 receives the "K" packet and receives it, the operation information in the P machine file FL2 is changed from "interrupted" to "free state" (steps S3622 to S3622).
2624).

FIG. 95 shows the console 4 of the management device 400.
12 shows a procedure of a hit release processing based on a hit release command from the control unit 12.

The hit release switch 4 on the console 412
When 33 is turned on, the local processing device 413 sends a hit table data request command to the central processing unit CPU (step S1631). Then, the central processing unit CPU searches the P machine file FL2 and sends the machine number of the pachinko machine being stopped, and the local processing unit 413 sets the CRT display device 4
A list of the percussion tables is displayed on the screen 11 (steps S2631, S2632, S1632). When the operator inputs the machine number of the pachinko machine whose release is desired to be released using the numeric keypad 425 on the console 412, the local processing unit 413 sends a stop release command to the central processing unit CPU (step S1633). . Then, the central processing unit CPU receives the instruction, determines whether or not all the units have been designated, and determines whether the transmission control unit S
The CC transmits a “cancel release” packet containing the serial number and the channel number along with the machine number to all the machines or the designated pachinko machine 100 (step S2633). Then, when the designated NAU 530 receives the packet, it removes the head for the high-layer network and sends it out to the low-layer network 510, and the data transmission controller 5 of the unit control device 180 that has received the packet.
51 is a command register CR in the unit memory 550
2 is written with a "cancel release" command (step S26).
34, S3631, S4631). Then, when this is read by the unit controller 190 of the pachinko machine 100 and it is confirmed that a hit release command has been entered, the pachinko machine operation information in the transmission data area of the unit memory 550 is changed to “free” and the transmission data is changed. After clearing the hit calculation register in the area to zero, change the analog display 163 and the card insertion lamp 168 to the customer waiting display, and instruct the card reader 800 to permit the acceptance of the card. Give (step S5
631 to S5634).

On the other hand, N
Upon receiving the hard ACK from the network controller of the unit control device 180, the AU 530 transmits a response packet “ACK” to the management device 400 (steps S3632 and S3633). After changing the operation information in the FL2 to the “free state”, the result is changed to the local processing device 41.
3 is notified (steps S2635 to S2637). Then, the local processing device 413 changes the status display “stop” at the end of the hit table data on the CRT display screen from “stop” indicating “free” to “empty” (step S1634).

FIG. 96 shows a processing procedure for forcibly terminating a terminal from the management apparatus 400 side.

The business of the game store ends when the store closes.
Conventionally, the end of business has been notified by in-store broadcasting and staff. However, a pachinko machine 10 which is in a good condition in which there is a player who purchases a ball just before the end of the game, or
The gamer who was at 0 did not readily stop the game, and it was difficult to close the business on time.

In the system of this embodiment, the console 4
By operating the forced termination switch 434 on the terminal 12 and selecting the type, the operation can be stopped for each type of terminal. First, about 30 minutes before closing the store, the card issuance by the card issuing machine 200 is performed. In addition, the operation of all pachinko machines is stopped at the business closing time, and the operation of the payment machine 300 is stopped after the payment is completed by the last player, whereby the business closing can be smoothly performed.

In this case, when the forced termination switch 434 is turned on, the local processing device
The forced termination menu is displayed on the screen 11 (step S1641). When the type of the terminal to be terminated according to this menu is selected using the numeric keypad 425, a display prompting entry of the forced termination unit number is displayed (step S164).
2). In this embodiment, the type of each terminal (pachinko,
(Card issuing machine, checkout machine), it is possible to terminate all devices at the same time or only one specific terminal. Here, "0" or When a number is input from the console 412, a forced termination command is transmitted to the central processing unit CPU (step S1643).

[0460] When the central processing unit CPU receives this command, it is first determined whether or not all the machines have been designated. If the card is "suspended", the number of the card being played or suspended is read out, and the issue serial number is calculated backward (steps S2641-S2644). Then, using the issued serial number, the number of balls and the amount of money in the card file are rewritten to data in the pachinko machine file and the card state is changed to "free" (step S2645). After executing this for all the units, the “forced end” packet is sent to NAU53.
0 (step S2646).

When NAU 530 receives this packet, it removes the high-layer network head and sends a “forced end” packet to all pachinko machines.
00, a response signal "ACK" is returned (step S
3641, S3642). When the management device 400 receives the ACK, the result is transmitted to the local processing device 413 (steps S2647 and S2648). Then, the local processing device 413 changes the state display of the display data on the CRT display screen from “empty” indicating “free” to “strong” indicating the forced termination state (step S1644).

On the other hand, the unit control unit 18 of each terminal receiving the “forced end” packet from the NAU 530
At 0, 280, and 350, the data transmission controller 551 writes a forced termination request command to the command register CR2 in the unit memory 550, and the unit controller 190 reads this command. Is cleared, and the operation information is changed to the forced termination (step S
4641, S5641). Then, after the detection of the sensor and the firing motor are stopped, and all the lamps are turned off to stop the game control, a command to eject the card in the card reader 800 is issued, and thereafter, the acceptance of the card is disabled (step S5642, S5643).

In the system of the embodiment, the numeric keypad 42 is used.
It is possible to enter the machine number of a specific pachinko machine and forcefully terminate it without designating all machines using 5, and in this case, the central processing unit CPU determines NO (specified machine designation) in step S2641. The determination is made and the process immediately proceeds to step S2646 to transmit a “forced end” packet to the designated pachinko machine (see the broken line). Then, when ACK returns from NAU 530, steps S2647 to S26
Then, the pachinko machine file is read for the first time to check the operation information, and the card file is read and updated only during the game or during interruption, and the process jumps from step S2645 to S2648 to store the result locally. The data is transmitted to the processing device 413.

FIG. 97 shows the issuing machine 200 or the payment machine 3
Here is a procedure for forcibly terminating 00.

In this case, when the forced termination switch 434 is turned on, the local processing device
The forced termination menu is displayed on the screen of No. 11 (step S1651). When the type of the terminal to be terminated according to this menu is selected using the numeric keypad 425, a display prompting entry of the forced termination unit number is displayed (step S165).
2). In this embodiment, the type of each terminal (pachinko machine 1
00, the card issuing machine 200, and the payment machine 300), it is possible to terminate all the devices at the same time, or to terminate only one specific terminal. "0" or console number to console 4
When input is made from step 12, a forced termination command is transmitted to the central processing unit CPU (step S1653).

When the central processing unit CPU receives this command, it first determines whether or not all the units have been designated. If all the units have been designated, the command is sent to all NAUs 530, and if a specific terminal has been designated, the designated issuing unit has been designated. A “forced end” packet is transmitted to the settlement apparatus 200 or the settlement machine 300 (step S2651).
When the ACK from NAU 530 is received, the operation information in the file of the terminal is changed to “forced termination” immediately when all the devices are designated, and the result is changed to local processing device 513 when the specific device is designated. (Steps S2652, S2653).

On the other hand, the card issuing machine 200 that has received the “forced end” packet clears the operating bit of the operating information in the unit memory 550 (step S565).
At the same time, the issue stop lamp 222 is turned on (S).
5652).

In the case where the forced termination is for the settlement machine 300, when the settlement machine 300 receives the packet,
While clearing the operating bit of the operating information in the unit memory 550, the settlement stop lamp 342 is turned on,
The acceptance of the card by the card reader 800 is disabled (steps S5652 and S5653).

Further, in the transmission system of this embodiment,
There is also provided a "forced termination release" packet for transmitting a command to release the operation stop of the terminal being forcibly terminated from the management device 400 side. There is.

FIG. 98 shows the pachinko machine 100 and the issuing machine 2
00 and the procedure of the forced termination release process common to the settlement machine 300 are shown.

The procedure in this case is almost the same as the procedure for the forced termination processing shown in FIG. That is, when the forced termination release switch 435 is turned on from the console 412 while looking at the CRT display device 411 of the management device 400, the local processing device 413 displays the forced termination release menu (step S1661). Using the numeric keypad while looking at this screen, type (Pachinko machine 100,
Issuer 200 or checkout machine 300)
The local processing device 413 transmits a command for requesting the data of the forcibly terminated unit to the central processing unit CPU (step S1662).

[0472] Then, the central processing unit CPU searches the file of each unit, finds the unit that is forcibly terminated, and transmits the data (steps S2661 and S266).
2). Since the local processing device 413 displays the data on the CRT display device 411, a forced termination release command is sent when all the devices are designated ("0") or a device number is input from the numeric keypad while looking at the screen (step S1663,
S1664). Then, the central processing unit CPU first determines whether or not all the units have been designated.
In step S2663, S2664, a "forcible termination release" packet is transmitted to the designated unit when the designated unit is designated. The “forced termination release” packet is transmitted from the data transmission controller 551 to the unit controllers 190, 290, and 390, and an “ACK” packet is transmitted to the management device 400 (steps S3661, S4661, S3662). Management device 4
When 00 receives the ACK, immediately when all units are designated,
When a specific unit is designated, the operation information in the unit file is changed to “free” (pachinko machine) or “in operation” (issuing machine, payment machine) (steps S2665 and S266).
6), and then jump to step S2667 to notify the result to the local processing device 413 (step S16).
65).

On the other hand, the unit that has received the “forced termination release” packet changes the operation information in the unit memory 550 to “free” or “in operation”, and then turns on the status display lamp 123 in the pachinko machine 100. Or the display of the analog display 163 is changed to the wait-for-customer display, and the card reader 800 can accept the card (steps S5661 to S5663). In addition, the card issuing machine 20
At 0, the bill validator 210 allows the purchase bill to be accepted, and the issuing lamp 241 is turned on.
Further, in the checkout machine 300, a check-in lamp 341 is used.
Is turned on to allow the card reader 800 to accept the card.

FIG. 99 shows that the power of the terminal is cut off by mistake or the unit controllers 190, 290,
The procedure of unit down detection processing when control by the 390 becomes impossible or when an abnormality such as disconnection of a cable of a low-layer network occurs is shown.

When the unit goes down, the scheduled data is not sent. Therefore, if the scheduled data is not received within 3 seconds, the NAU 530 detects a timeout and determines that the unit is down. The token bus abnormal bit is set to "1" (steps S3691 and S3682). Thereafter, the central processing unit CPU of the management device 400 sends a “periodic data request” packet by a timer interrupt (step S
2671), and receives it and transmits an “ACK” packet containing the unit table (step S367).
3, S367). The central processing unit CPU executes the “AC
When K "is received, the monitor information of each unit in the packet is checked first. If there is an abnormality, the occurrence of the unit abnormality and the contents of the abnormality are printed by the printer 408, and the abnormality of the unit is displayed on the CRT display device 411. (Step S267)
2 to S2674).

[0476] Then, the CRT display device 411 displays an interrupt message notifying the unit abnormality at a predetermined position (line 19) of the screen being displayed (step S167).
1).

On the other hand, the central processing unit CPU clears or changes the operation information of the unit file to “free” after instructing the display of the unit abnormality, changes the card state in the card file to “free”, The number of balls in the
After saving the amount in the card file, a "unit check" packet is formed and transmitted to NAU 530 (steps S2675 and S2676). This packet is
When U530 receives the packet, the high-layer head is removed and a "unit check" packet is transmitted to each unit (step S3675). If the unit to which the packet was sent is down or has a low-layer network error,
Hardware ACK from network controller is NAU
530 does not return, so NAU 530
An "ACK" or "NAK" packet is transmitted to the management device 400 according to the presence or absence of K (steps S3676, S3676).
3677).

[0478] Fig. 100 shows the procedure of unit recovery processing when communication with the NAU 530 is interrupted or a unit or a low-layer network is recovered.

While the “unit check” packet is periodically transmitted in step S2676 of the unit down detection processing in FIG. 99, the unit recovers due to power-on of the unit or connection of a low-layer network, Upon confirming the reception of the ACK from the NAU 530 in step S2677, the central processing unit CPU reads the file of the unit and sends a "unit recovery data" packet containing the operation data of the unit immediately before the NAU 53 to the NAU 53.
0 (steps S2681 and S2682).

Upon receiving the “unit recovery data” packet, NAU 530 copies the recovery data in the packet into the monitor table, and then transmits the “unit recovery data” packet with the packet head for the high-layer network removed to the recovered unit. (Steps S3681, S3
682).

Then, the data transmission controller 551 of the unit operates the command register C in the unit memory 550.
A "unit recovery" command is written in R2, and recovery data is written in the reception data area to notify the unit controller 190, 290 or 390 of the packet reception (step S4681). Unit controller 19
0, 290 and 390, upon confirming the reception of the “unit recovery data” packet, copy the packet head to the transmission data area, and in the pachinko machine 100, the card reader 8
After transmitting the identification code to 00, an "ACK" transmission request is made to the data transmission controller 551 via the unit memory 550 (steps S5681, S5).
682). Data transmission controller 551 is "ACK"
The packet is transmitted to NAU 530, and NAU 530 adds a high-layer head to the head of the packet and transmits "ACK" to management device 400 (steps S4682, S368).
3).

The central processing unit CPU of the management device 400
When “ACK” is received, a “restart” packet is formed and transmitted to NAU 530 (step S2683,
S2684).

This packet is transmitted from the NAU 530 to the unit controller 1 via the data transmission controller 551.
When transmitted to the display units 90, 290, and 390, the unit controller restores the display such as the display lamp, the number of balls, and the amount display to the state before the down (steps S3684, S4).
683, S5683). After that, in the pachinko machine 100,
A “reload” command is transmitted to the card reader 800 (step S5684). Then, the card reader 800 re-reads the magnetic data and the like when the card is inside, and stores the card number in the unit controller 19.
Send to 0. Thereafter, the unit controller executes the same processing as in the case of card-in in FIG. 87, transmits the card number, and receives the corresponding card text.

The NAU 530, which has received the “restart” packet in step S3684, checks the hardware ACK from the network controller of the unit and transmits the “ACK” packet to the management device 400 (step S3685).

FIG. 101 shows a procedure of a detection process and a recovery process when the NAU 530 is down due to an accidental power-off of the NAU 530 or disconnection of a cable of a high-layer network.

When the NAU 530 goes down, the ACK for the “scheduled data request” packet from the management device 400 due to the timer interrupt does not return. A display command and an emergency print command are transmitted to the printer 408 (step S26).
91-S2694). Then, the local processing device 413
Is NAU5 at a predetermined position on the screen of the CRT display device 411.
An interrupt message is displayed to notify that 30 has gone down, and printer 408 prints on paper that NAU 530 has gone down.

Thereafter, the central processing unit CPU transmits a “line monitor check” packet to NAU 530 (step S2695). While the above procedure is repeated, for example, every one second by a timer interrupt, an attendant checks the NAU 530 and the high-layer network while watching the interrupt display and the emergency printout. The received ACK is transmitted to the management device 400 (step S
3691, S3692). As a result, the central processing unit 400 confirms the ACK and knows that the NAU 530 has recovered,
An interrupt display command is transmitted to the local processing device 413, and an emergency print command is transmitted to the printer 408 (step S).
2696-S2698). Then, the local processing device 4
Reference numeral 13 denotes an NA at a predetermined position on the screen of the CRT display device 411.
An interrupt message indicating that U530 has recovered is displayed, and printer 408 prints on paper that NAU 530 has recovered.

On the other hand, on the unit side, a transmission cause occurs due to an external action or the like, and when a transmission request is made to the data transmission controller 551 via the command register CR1 of the unit memory 550, the data transmission controller transmits the corresponding packet. It is formed and transmitted to NAU 530 (step S4691). At this time, NAU53
If 0 is down, the network controller 55
3 detects the transmission failure and describes this in the packet memory 552. Thereby, the data transmission controller 5
51 knows the transmission failure (step S4692), returns to step S4691, and repeats transmitting the same packet again. If the NAU 530 is not down, the data transmission controller 551 knows that the transmission was successful, and notifies the unit controllers 190, 290, and 390 of the successful transmission via the unit memory 550 (step S4693). When there is, since the transmission success is not returned forever, the unit controllers 190, 290, and 390 detect that the timer (step S5692) set after the transmission request has timed out and knows the transmission failure (step S5693). . As a result, the unit controller stops outputting the watchdog pulse (step S5694). Thereby, the external reset circuit 55
5 generates a reset signal, and all other controllers 551 and 553 in the unit controllers 180, 280 and 350, including the unit controller, are also reset.
Stop the control operation.

Thereafter, when NAU 530 recovers, NA
The U530 and the central processing unit CPU each detect a unit down and execute a unit recovery process (FIG. 9).
9, FIG. 100). The unit receives the “unit recovery” packet after initialization and returns to the state before the unit went down.

FIG. 102 shows a processing procedure when the store close switch 422 and subsequently the system end switch 423 are turned on.

The store closing switch 422 on the console 412
Is turned on, the local processing device 413 transmits a store closing request command to the central processing unit CPU (step S
1701). When this command is received by the central processing unit CPU, the P machine files are sequentially read from the main storage device to check whether the operation information is "playing", and if there is no pachinko machine being played, an ACK is transmitted to the local processing device 413. And transmits a “closed” packet to all NAUs 530 (steps S2701 to S2704). Upon receiving the ACK, the local processing device 413 waits for the system end switch 423 to be turned on, and when turned on, the local processing device 413 transmits a system end request command to the central processing unit CPU (steps S1703 and S170).
4).

[0492] On the other hand, upon receiving "ACK" from NAU 530, central processing unit CPU having transmitted the "closed" packet in step S2704 has a system end command received from local processing unit 413 (step S27).
04, S2705). Then, when the central processing unit CPU receives this command, it creates a daily report file including business data of one day and saves it on the hard disk HDD.
After erasing the power failure save file from the hard disk HDD, system termination message data is transmitted (steps S2706 to S2708). This is received by the local processing device 413, and a message instructing to turn off the power is displayed on the system end screen (step S).
1705).

The NAU 530 that has received the “closed” packet from the management device 400 transmits the “closed” packet from which the high-rise head has been removed to each unit (step S370).
When the unit receives the packet, the display lamp and the like indicating that the unit is in operation are turned off, and a command is issued to the card reader 800 to reject acceptance or issuance of the card (steps S5701 and S570).
2).

FIG. 103 shows the management device 40 when a power failure occurs.
0 shows the processing procedure.

When a power failure occurs, the power supply is switched, and the central processing unit CPU operates by being backed up by the auxiliary power supply 409. First, the collection of scheduled data from each unit is stopped, and local processing is performed to determine that a power failure countermeasure is being taken. To the device 413 (steps S2711, S271).
2). Then, the local processing device 413 displays a power failure message on the CRT display device 411 (step S17).
11). On the other hand, the central processing unit CPU reads the P machine file and checks the operation information.
, The issue serial number is calculated backward from the card number in the file of the P machine, the card file is searched using the calculated number, and the card status is rewritten to "free" (step S2713).
To S2715). After that, the operation information in the P machine file is rewritten to “free”, and then the data (including the set value file and the power failure flag) of the common data area and the card file, the P machine file, the issuing machine file, and the settlement machine file are stored on the hard disk HDD. And save the result ("Closed")
Is transmitted to the local processing device 413 and then the system goes down (steps S2716 to S2718).

The local processor 413, which has received the “closed store” from the central processor CPU, sends an end message to the CRT.
It is displayed on the display device 411 (step S1712).

FIG. 104 shows the procedure of the system start-up processing after the occurrence of the power failure.

When the power is restored and the system is turned on again, the management device 400
Are all the files FL1 to FL in the main storage device M-MEM.
After clearing L6, a file (framework) is created (step S2721).

On the other hand, the local processing unit 413 first
After the initial screen is displayed on the T display device 411, the date and time are transmitted to the central processing unit CPU (step S1721,
S1722). Then, the central processing unit CPU determines the presence or absence of the power failure file by looking at the power failure flag. The device 413 is notified that the power failure is being started (steps S2722 to S2724). Then, the local processing device has a response after displaying a message “power failure is starting up” on the CRT display 411 (step S1723).

After reading the power failure file, the central processing unit CPU uses the high-level network 520 to read each NAU 5
Then, a "unit recovery data" packet is transmitted to 30 (step S2725).

On the other hand, when the power is turned on, the NAU 530 first reads the set values (NAU number, minimum unit number, number of terminals, etc.) from the NAU number setting units 544 to 549, calculates the network transmission address of each terminal, and sets the unit table. Is created, the transmission address of each unit (terminal) and the NAU itself is recognized, and the unit table in which the operation data of each unit is entered is cleared (steps S3721 to S3724). And the management device 4
Upon receiving the “unit recovery data” packet from 00, the NAU 530 puts the recovery data in the packet into the monitor table, then removes the high-layer head, and sends the “unit recovery data” packet containing the recovery data in the data section. Transmit to the unit (steps S3725, S372)
6).

Also, the unit control device 18 of each terminal
When power is turned on, the data transmission controller 551 in the unit clears all data areas in the unit memory 550 and then writes data to a predetermined address “27FF” in the unit memory. (Steps S4721 and S4722). Then, a predetermined terminal INT of the unit memory 550 rises to a high level. Unit controllers 190 and 29 of each terminal
0, 390 are internal memories, registers, I
When the / O port is initialized and the rise of the initialization signal INT from the unit memory 550 is detected, the set value (unit number) is read from the unit number setting device, and the lower part of the serial number and the channel number is calculated. The data is written in the transmission data area of the unit memory 550 (steps S5721 to S5724). The unit address is recognized on the unit side by reading it by the data transmission controller 551 (step S4723). This enables data transmission between the NAU 530 and each terminal using the token bus.

Thereafter, when a “unit recovery data” packet containing the recovery data already received from the management device 400 is transmitted from the NAU 530 to each unit (terminal), the data transmission controller 551 of the unit is transmitted.
Writes the "unit recovery" command in the command register CR2 in the unit memory 550 and the recovery data in the reception data area to notify the unit controller 190, 290 or 390 of the packet reception (step S4724). Upon confirming the reception of the “unit recovery data” packet, the unit controller copies the packet head to the transmission data area, and the pachinko machine 10
In the case of 0, after transmitting the identification code to the card reader 800, a transmission request of "ACK" is made to the data transmission controller 551 via the unit memory 550 (steps S5725 and S5726). The data transmission controller 551 transmits an "ACK" packet to the NAU 530, and the NAU 530 adds a high-layer head to the beginning of the packet and transmits "ACK" to the management device 400 (steps S4725 and S3727).

[0504] The central processing unit CPU of the management device 400
Upon receiving “ACK”, a “restart” packet is formed and transmitted to NAU 530 (step S2726,
S2728).

This packet is transmitted from the NAU 530 to the unit controller 1 via the data transmission controller 551.
90 (step S3728), the unit controller 190 restores the display such as the display lamp, the number of balls, and the amount display to the state before the down (step S5).
727). Thereafter, the pachinko machine 100 transmits a “reload” command to the card reader 800 (step S5728). Then, when there is a card inside, the card reader 800 re-reads the magnetic data or the like and sends the card number to the unit controller 190. Thereafter, the unit controller 190 returns to FIG.
The card number is sent by performing the same processing as in the case of card-in, and the card text is received.

[0506] Upon receiving the "restart" packet in step S3684, NAU 530 transmits a "ACK" packet to management device 400 after confirming the hardware ACK from the network controller of the unit (step S3729).

Next, a central processing unit in the case where the management device 400 controls the entire system while communicating with the pachinko machine 100, the issuing machine 200, and the settlement machine 300 using various packets shown in [Table 31]. The control procedure of the CPU and the local processing device 413 will be described with reference to FIGS.

FIGS. 105 to 108 show flowcharts of the initialization processing.

The central processing unit CPU and the local processing unit 4
13 resets upon power-on, initializes internal registers and internal memory, etc., sets the file framework in the main memory M-MEM by the central processing unit CPU, and prepares the local processing unit 413 An initial screen as shown in FIG. 150 showing the inside (only the first and second lines) is displayed (steps S1001, S200)
1). Then, the local processing device 413 reads the date and time from its own timer and transmits it to the central processing unit CPU (step S1002). Local processing unit 4
The timer of 13 is backed up by a battery,
Even if the power is turned off, it does not stop and operates constantly to function as a clock.

[0510] Upon receiving the date and time, the central processing unit CPU stores the date and time in the common data area of the main storage device M-MEM and transmits an ACK to the local processing device 413. When the ACK has not been received, the local processing device 413 returns to step S1002 and transmits the date and time again. After receiving the date and time and returning ACK, the central processing unit CPU
The power failure backup file in the hard disk HDD is checked, and the presence or absence of the power failure file is determined by checking whether the power failure flag in the file is set to “1”. It is determined to be inserted, and the process proceeds to step S2041 in FIG. 108 (steps S1003, S2002 to S2004).

[0511] If it is determined in step S2004 that there is no power failure file, the flow advances to step S2005 to prepare for the mode.
Set at a predetermined address position in the MEM (step S
2006). Then, the transmission address file FL6 created when the system is installed is similarly loaded from the hard disk HDD to the main storage M-MEM (step S2007).

Next, the central processing unit CPU is connected to the main memory M
-A pachinko machine file PL2 is formed in the MEM, and the serial number of the pachinko machine constituting the system is read from the transmission address file FL6, and the number of award balls, the number of hits, and the hitting mode are read out from the set value file PL5 to read the pachinko machine. Fill in a predetermined column of the file PL2, and write "0" in the other columns (step S2008). Thereafter, similarly, the serial numbers of the issuers 200 and the settlement machine 300 constituting the system are read out from the transmission address file FL6 and written in predetermined columns of the issuer file FL3 and the settlement machine file FL4, respectively. Write "0" (Step S2
009, S2010).

[0513] In the card file FL1 provided in the main storage device M-MEM, "0" is entered for all items (step S2011), and the flow shifts to step S2012.

[0514] In step S2012, after executing a random number generation process (see Fig. 149) necessary for calculating the card number, it is checked whether or not there is a mode inquiry from the local processing device 413, and there is a mode inquiry. And the response “mode =“ in preparation ”” is sent to the local processing device 413.
(Steps S1004, S2013, S20)
14). Then, the local processing device 413 receives this, and the “under preparation” of the CRT display device 411 shown in FIG.
Message MSG indicating "Line test in progress" on screen 0
1 is displayed (step S1005). Then, the local processing device 413 sends a line test request command to the central processing unit CPU (step S1006).

[0515] When the central processing unit CPU receives and confirms the line test request command, it forms a "line test" packet and transmits all NAUs via the high-layer network 520.
530 in order (steps S2015, S
2016). Then, the response “AC” from NAU 530
When a K "packet is received, the transmission address file FL6
"1" (NAU normal) is written in bit 0 of NAU status 2 in the table (step S2017). And all N
It is determined whether the transmission to the AU 530 has been completed (step S2018).
Forms a "unit table request" packet to
When the packet is transmitted to the AU 530 and the “ACK” packet is received from the NAU 530, it is determined whether there is a response from all the NAUs 530 (steps S2019 to S2021). And "unit table request" for all NAUs 530
Is received, the transmission address of the unit table contained in the packet and step S2
At 007, the main storage device M-ME is
A comparison is made with the address in the transmission address file loaded into M (step S2022). Then, it is determined whether or not a unit not registered in the file exists in the received unit table (step S2023).
In step 2024, the unit is added to the transmission address file, and the flow advances to step S2025.

[0516] In step S2025, it is determined whether or not there is a non-existent unit in the received unit table among the units registered in the transmission address file.
In step S202, the unit is stored as a network error, that is, an uncommunicable unit in step S26.
Move to 7.

At step S2027, the transmission address file is saved on the hard disk HDD. As a result, if the transmission address file is changed in step S2024, the changed transmission address file is read and compared at the time of system startup after restoration from power failure or at the time of system startup the next day.

[0518] Thereafter, the central processing unit CPU transmits the line test result to the local processing unit 413 (step S).
2028). Moreover, at this time, the abnormal terminal (unit)
If there is, the line test result is transmitted together with the screen data for displaying the unit number of the abnormal terminal on the CRT screen.

[0519] When the local processing device 413 receives this line test result (step S1007), it determines whether or not there is an abnormal terminal (step S1008). If not, the process directly proceeds to step S1011 and there is an abnormal terminal. In step S1009, the process proceeds to step S1009, and the number of the abnormal terminal is displayed on the screen of the CRT display device 411.
Display the screen of.

[0520] The line can be returned to normal by checking the abnormal terminal by looking at this screen.

However, even when the terminal abnormality screen (FIG. 151) is displayed, the system can be operated toward opening the store by turning on the store opening switch 421. In step S1010, it is determined whether the store opening switch 421 is turned on. If it is turned on, the process proceeds to step S1011 to transmit an initial value setting request command to the central processing unit CPU. If the store opening switch is turned off in step S1010, the process jumps to step S1006 and transmits a line test request command again. As a result, when the clerk looks at the terminal error display screen and repairs the terminal and becomes normal, the terminal is treated as an abnormal terminal, that is, removed from registration.

[0522] On the other hand, when the central processing unit CPU receives the initial value setting request command from the local processing unit 413 (step S2029), it forms an "initial value setting" packet and puts the contents of the setting value file in the data column. The data is transmitted to each unit (step S2030). Then, if a response "ACK" packet is received, it is determined whether the setting of the initial values for all units has been completed (steps S2031, S2032). When the initial value setting is completed for all the units, the display data of the opening request screen as shown in FIG. 152 is sent to the local processing device 413 (step S2033).

When the local processing device 413 receives this screen data, it displays it on the CRT display device 411, and waits for the store opening switch 421 to be turned on according to the message (steps S1012, S101).
3). Here, when the store opening switch is turned on, the local processing device 413 transmits a store opening request command to the central processing unit CPU (step S1014). When the central processing unit CPU receives this command, the NAU
530 is transmitted to the store opening packet (step S2).
034, S2035). Next, “A” from NAU 530
When "CK" is received, it is checked whether or not transmission of packets to all NAUs 530 has been completed.
The normal display screen data indicating that the business is in operation 59 is transmitted to the local processing device 413, and the control is shifted to the operation in business (steps S2036 to S2038).

[0524] On the other hand, upon receiving the screen data, the local processing device 413 displays the screen data on the CRT display device 411, and shifts to control during operation (step S105).

FIG. 108 shows a control procedure of the central processing unit CPU and the local processing unit 413 when the system starts up after recovery from the power failure.

[0526] When a power failure occurs as described above, the management device 400 stores the card file F in the main storage device M-MEM.
L1 and pachinko machine file FL2, issuing machine file FL
3. Save the settlement machine file FL4 and common data in the hard disk HDD, set the power failure flag to "1", and then shut down the system.

Therefore, when the power failure is recovered and the power is turned on, the initialization processing of FIG. 105 is started, and step S200 is started.
When the number reaches 4, it is determined that there is a power failure file, and the process jumps to step S2041 in FIG. Step S204
At 1, the mode is set to "power-on startup". On the other hand, when the local processing device 413 displays the initial screen, transmits the date and time, and receives the ACK from the central processing unit CPU, the process proceeds to step S1004 to inquire about the mode. Then, at this time, since the mode is already set to “power-on start-up” in the central processing unit CPU, when a mode inquiry is received, the mode is “power-off start-up” as a response (steps S2042, S2043).
Then, when the local processing device 413 receives this mode, it determines whether or not it is “starting up of power failure”. If yes, a message “system recovery” is displayed on the sixth line of the preparation screen in FIG. Display (step S102)
1). Then, a timer is set, and when a predetermined time elapses after the timer expires (step S102).
2, S1023, S1024), and returns to step S1004 to make a mode inquiry again.

On the other hand, when responding to the mode, the central processing unit CPU reads the power failure file from the hard disk HDD and returns it to the common data area of the main memory M-MEM (steps S2044 and S2045), and waits for a timer. During this period, a “unit recovery” packet is transmitted to each unit, and the operation data in the unit memory of each unit is returned to the state before the power failure (step S204)
6). Then, when an “ACK” packet from each unit is received and the process is completed for all units, NAU 530
(Restart (type)) packets are transmitted one after another to restart the unit for each type (step S
2047-S2049). Then, when "ACK" from each NAU 530 is received and the processing is completed for all NAUs 530, the mode of the central processing unit CPU is changed to "in business", and the data on the normal display screen (FIG. 159) indicating business is transmitted. (Steps S2050 to S205)
3). At this point, the local processing device 413
When the timer set in 1023 has timed out and returns to step S1004, and the mode is inquired, "in business" is returned as the mode. Therefore, it is determined NO in step S1021 and step S1025 is determined.
Then, the normal display screen sent from the central processing unit CPU is displayed on the CRT display device 411, and the control is shifted to the control during business.

FIG. 109 shows a procedure for changing the initial set value by the built-in switch 438 provided on the back of the console 412.

In step S1012 of FIG. 107 of the above-described initialization flow, a store opening request screen (FIG. 159) is displayed.
When the built-in switch 438 is turned on while waiting for an input of a switch in step S1013, the local processing device 413 transmits a request command of an initial setting value to the central processing unit CPU (step S1031).
Then, the central processing unit CPU sends the contents of the setting value file loaded from the hard disk HDD to the local processing unit 413 (step S2061). In response to this, the local processing device 413 displays a setting value change screen as shown in FIG. 153 on the screen of the CRT display device 411 (step S1032).

[0531] Here, when the operator inputs a new set value of the purchase ball rate or the identification code using the numeric keypad 425 on the console 512 according to the instruction on the screen, the local processing device 413 stores the updated value in the internal memory. Then, the next setting value change screen (see FIG. 154) is displayed (step S1033). At this time, if the return key 426 is pressed immediately without inputting the set value, the screen shifts to the next change screen without updating the set value.

[0532] When the base number and the number of prize balls are input from the numeric keypad according to the instructions on this screen, the local processing device 413 stores the updated values and displays the next set value change screen (see Fig. 155) (step S1034). . Also, at this time, without inputting the set value, the return key 426
Press to move to the next change screen without updating the set value.

When the number of NAUs, the number of pachinko machines, the number of issuers or the number of payment machines are input from the numeric keypad while looking at the change screen, the local processing device 413 updates the set value file containing the update values stored in the internal memory. The request command is transmitted to the central processing unit CPU (step S10).
35). When the central processing unit CPU receives this command, first, the setting value file in the main storage device M-MEM is
Next, after updating the pachinko machine file, an “initial value setting” packet containing the updated setting value is transmitted to all units (steps S2062 to S2064).

FIG. 110 shows a setting value update processing procedure using the setting update switch 432 or the date / time setting switch 439 on the console 412.

When waiting for a switch input in step S1013 of the initialization flow of FIGS.
When the setting update switch 432 is turned on, the local processing device 413 issues a set value change request command to the central processing unit C.
The data is transmitted to the PU (step S1041). Then, the central processing unit CPU sends the contents of the setting value file loaded from the hard disk HDD to the local processing unit 413 (step S2071). In response, the local processing device 413 displays a setting value change screen as shown in FIG. 156 on the screen of the CRT display 411 (step S104).
2).

Here, when the operator inputs the machine number and the number of hits from the numeric keypad 425 in accordance with the instructions on the screen, the local processing device 413 stores the updated values in the internal memory, and then changes the next setting value change screen (FIG. 157 is displayed (step S1043).

[0537] Looking at this screen, the operator inputs the machine number and the stop mode using the numeric keypad according to the instructions on the screen.
The local processing device 413 stores the updated value in the internal memory, and then transmits a setting value file update request command containing the updated value stored in the internal memory to the central processing device C.
The data is transmitted to the PU (step S1044). When the central processing unit CPU receives this command, first, the main memory M
After updating the setting value file in the MEM and then the pachinko machine file, an “initial value setting” packet containing the updated setting value is transmitted to all units (step S20).
72-S2074).

On the other hand, when the date and time setting switch 439 on the console 412 is turned on while waiting for a switch input in step S1013 of FIG. 107, the local processing device 413 displays a date and time change screen (FIG. 121 (see step S104).
5). Then, when the operator inputs the date and time from the ten keys 425 according to the instructions on this screen, the local processing unit 413 displays the updated date and time on the central processing unit CPU.
(Step S1046). Central processing unit CP
When U receives the date and time, it changes the current time of the internal timer to the received time, and then puts the updated date (all other setting values are unchanged) in all units. Transmit the packet (steps S2075, S20)
76).

In FIG. 111, the NAU is
The procedure of the scheduled data request processing for the 530 is shown.

When the CPU receives an interrupt from the timer every one second, the CPU starts this scheduled data request processing, and first checks whether the operation mode is "business" (step S2101). If not, the flow advances to step S2102 to wait until 15 seconds have elapsed. This is to wait until the line test and the initial value setting process according to the initialization flow are completed.

If it is determined in step S2101 that the business is open, the flow advances to step S2103 to transmit a "periodic data request" packet to NAU 530, and set a timer (step S2104). Then, it is checked whether or not the response ACK from the NAU 530 has returned. If there is an ACK, the process proceeds to the scheduled data reception processing S211 to S2135 in FIG. 112 (step S2105). Step S2105
If it is determined that there is no ACK, step S2104
The timer set in step (1) is checked to determine whether a time-over has occurred (step S2106). And
If a time-out occurs before receiving the response ACK from the NAU 530, the process shifts to step S2107 to return to the common data area CDA of the main storage device M-MEM.
After incrementing the error counter corresponding to the NAU 530 with no response among the error counters provided for each NAU 530, whether or not the error counter becomes 3 or more in step S2108, that is, 3
It is determined whether an error has occurred successively. If the error is equal to or less than 2, the process returns to step S2103 to transmit a “periodic data request” packet to the same NAU 530 again. Then, a time-over occurs before receiving the ACK again, and if this is repeated three times, steps S2108 to S2109
Go to here, NAU530 in the transmission address file
0 (N) of status information corresponding to NAU 530 without ACK among NAU statuses prepared for each
ORMAL) is cleared to "0", an interrupt display command is transmitted to the local processing unit 413, an interrupt message indicating the NAU down is displayed on the screen of the CRT display unit 411, and the same content is displayed on the printer 408. Is printed out. After displaying the interrupt, the local processing device 413 sounds the buzzer 440 (steps S2110, S1051, and S105).
2).

[0542] Thereafter, it is determined whether or not a periodic data request has been made to all NAUs 530.
Returning to step 2103, a “scheduled data request” packet is transmitted to the next NAU 530 (step S2111).
Then, it is determined whether there is no ACK for all the NAUs 530 (step S2112). If no, the interrupt processing is terminated.
Is cleared to "0", then the file FL of all units
2 to 7 of monitor information in FL4 (CHIPEPA)
Is set to "1" to store that the chipper net (high-layer network) is abnormal (step S211).
3, S2114).

FIG. 112 shows “A” in which the scheduled data is entered from NAU 530 as a response to the scheduled data request.
A processing procedure when a CK "packet is received will be described.

Upon receiving the scheduled data, the central processing unit C
The PU first checks the monitor information for each unit at the beginning of the data column of the received packet (step S212).
1) If there is no abnormality, the process jumps to step S2128. If there is an abnormality, the process proceeds to the next step S2123 to determine whether or not it is the same as the previous abnormality (step S2).
122). If the detected abnormality is the same as the previous one, the process jumps to step S2128. If the detected abnormality is different, the new abnormality is printed by the printer 408 in step S2124. Then, the unit abnormality interrupt display screen data is transmitted to the local processing device 413 (step S2125). Local processing device 41
3 receives the screen data, and displays the CRT display device 41
On the 19th line of the first screen, an interrupt message notifying the unit abnormality is displayed.

On the other hand, the central processing unit CPU determines in step S2
When the screen data is transmitted at 125, the hot code at the end of the received scheduled data is checked (step S2126). If there is no hot code error, the process jumps to step S2128. If there is an error, the error recovery processing task (see FIG. 129) is notified of the unit abnormality in step S2127, and then step S212.
8 and inspects the monitor information 2 in the scheduled data.
If there is an abnormality in the monitor information 2, the printer and the printer C are operated in the same procedure as in steps S2122 to S2125.
An abnormality is displayed on the RT display device 413 (step S2
129-S2132).

[0546] Thereafter, if there is no abnormality in the monitor information, in step S2133, the file (pachinko machine file, issuing machine file, or payment machine file) of the unit in the main memory M-MEM is rewritten to the received regular data. After that, when there is an abnormality, the operation information of the unit file is cleared or changed to "free". When the regular data is received from the pachinko machine 100, the card state is set to "free" and the ball in the file of the P machine is changed. After saving the number and the amount in the card file, it is determined whether or not the processing of steps S211 to S2133 has been completed for all units in the received packet.
Return to (Step S2134). If the processing has been completed for all the units, in the next step S2135, all the N
It is determined whether or not the “ACK” packet of the scheduled data from the AU 530 has been processed. If no, the process returns to step S2121 to return to step S212 until all “ACKs” are completed.
121 to S2134 are repeated.

FIG. 113 shows a processing procedure of the central processing unit CPU when a “card purchase” packet is received from the issuing machine 200.

Upon receiving the “card purchase” packet, the central processing unit CPU extracts the card number from the data column in the packet and determines whether or not the number is “0” (steps S2141 and S2142). In the system of the present embodiment, the issuing machine itself may transmit a “card purchase” packet with the card number set to “0” for the card issuing reservation before the actual issuing of the card in the issuing machine 200. This is for discriminating between such a packet for reservation and a reserved original "card purchase" packet.

Here, the card number in the packet is “0”
In other words, if it was a purchase packet for an issuance reservation,
Proceeding to step S2143, the number of issuances is read from the issuer file of the main memory M-MEM, and it is checked whether the issuance number in the packet and the number obtained by adding "1" to the number of issuances in the file match (step S2143). Step S2144). If the issuance receipt number matches the number of issuances + 1, the flow advances to step S2145 to check whether or not the card amount in the packet is "0" (step S2146). As a result, if the amount is $ 0, the process jumps to step S2149. If the amount is 0, the reservation flag is read from the issuing machine file in the next step S2147, and it is checked whether it is "1", that is, reserved (step S214).
8). If the reservation flag is not "1", the card issue serial number in the packet and the number of times of issue in the file are incremented in step S2149. When the amount is not "0" in step S2146, the process proceeds to step S2149 without checking the reservation flag and incrementing the card issuing serial number because the card number is "0" immediately without making a reservation. This is so that a card can be issued even if a packet in which the purchase amount is entered in the card amount column is received.

In step S2149, the serial number of the card is incremented (the number of issues is updated in the unit memory when the card is ejected by the issuing machine, and the number of issuances is updated in the issuing machine file by collecting the data at regular data collection). After that, the card file is searched using the card issuing serial number to clear the file of the card, and then the card number is calculated from the card issuing serial number (steps S2150 and S2151). Then, in step S2152, the calculated value is written in the card number column in the card file, and the value in the received packet is written in the ball count and amount column, and the card state is set to "free".
After that, the received data and the current time are written to the log data with i = 1 and the log data with i = 1, and then the “ACK” packet is issued in step S2153.
Send to

If the card number is determined to be “0” in step S2142 and the issuance reception number received in step S2144 is not compared with the issuance number in the file + 1, the flow advances to step S2154. The number of issued cards and the number of issued cards are compared, and if they match, the flow advances to step S2155 to calculate a card number from the serial number of the card issued, and in the next step S2156 a card file is searched using the serial number of the card issued. After reading the file, the process proceeds to step S2152 to update the card file, and then transmits an "ACK" packet (step S2153). For example, a “card purchase” packet is received for reservation for issuance, and
The case where the “ACK” packet transmitted by executing 141 to S2153 does not reach the issuer 200 within a predetermined time and the same “card purchase” packet is transmitted from the issuer 200 is considered. .

On the other hand, if the card number in the “card purchase” packet received in step S2142 is not “0”, that is, if there is a true purchase application for the reserved card, the flow jumps to step S2157. Compare the issue receipt number in the packet with the number of card issuances in the issuer file plus "1", and if they match, search for the card file using the received card issue serial number and find the file Is read (step S2158), and the flow shifts to step S2152 to update the file. At this time, the actual card purchase amount in the received packet is written in the card file. After the file is updated, an “ACK” packet is transmitted.

[0556] In step S2142, the card number =
If it is determined that the number is not 0 and then it is determined in step S2157 that the issuance reception number does not match the number of issuances, the packet is determined to be an erroneous “card purchase” packet, and step S215 is performed.
Jump to 9 and send NAK.

FIG. 114 shows the management device 40 when a card is inserted into the control unit 160 of the pachinko machine 100.
7 shows a processing procedure of the central processing unit CPU when receiving a “card-in” packet transmitted for “0”.

[0555] Upon receiving the "card-in" packet, the central processing unit CPU first calculates the card issue serial number from the card number in the packet (step S216).
1). Next, a card file is searched using the calculated card issuing serial number, and the file of the card is read (step S2162). Then, the card number is extracted from the read card file and compared with the card number in the received packet (steps S2163 and S216).
4) If they match, the flow advances to step S2165 to check whether the card status of the card in the file is "free". Here, if the card status is "free", the card status in the card file is rewritten to "playing", and the numbers in the received packet are written in the columns of the terminal number and the serial number of the terminal (step S216).
6).

[0556] Thereafter, an "ACK" packet containing the card text (card number, number of balls, amount and card) read from the card file is transmitted to the pachinko machine 100, and then the card number column in the pachinko machine file is transmitted. Then, the card number in the received packet is written in (step S2167, S2168).

In step S2164, if the card number in the packet is not compared with the card number in the file in step S2164, or if the card numbers match but the card state is not "free", step S217 is performed.
In step 1, it is determined whether the game is "playing" or not, and the card state is "playing".
If not, it is determined that an inappropriate card has been inserted, and the flow jumps to step S2174 to transmit a "NAK" packet. In this way, by comparing the card number in the packet with the card number in the file, a forged card can be eliminated. If the inserted card is interrupted by another pachinko machine, step S21
65 and S2171, both are determined to be no, and the process is jumped to step S2174 to transmit "NAK", thereby eliminating the error.

[0558] If it is determined in step S2165 that the card status is not "free", and if it is determined in step S2171 that it is "playing", the flow shifts to step S2172 to determine the P machine number in the received packet and the card in the card file. The reason that "ACK" is returned when the numbers match is that the card is re-read in the pachinko machine after the power failure is recovered, and if there is a card, a "card in" packet is sent. is there.

In FIG. 115, when the interrupted card is inserted into the interrupted pachinko machine, the CPU of the central processing unit CPU when the “interrupted card-in” packet transmitted from the pachinko machine 100 to the management device 400 is received. The processing procedure will be described.

Upon receiving the “interrupted card-in” packet, the central processing unit CPU first calculates the card issue serial number from the card number in the packet (step S21).
81). Next, a card file is searched using the calculated card issue serial number, and the file of the card is read (step S2182). Then, the card number is extracted from the read card file and compared with the card number in the received packet (steps S2183 and S21).
84) If they match, the flow advances to step S2185 to check whether the card status of the card in the file is "interrupted". Here, if the card status is "interrupted", the card text in the card file is updated, the card status is rewritten to "playing", and the data and time at the time of interruption are written in the i-th log data column. , I counter is decremented (steps S2186, S2187).
When the interruption occurs, the data and time at the time of the interruption are temporarily recorded in the history column indicated by the i-counter in the card file, but when the interruption is released, the i-counter is decremented, and the same column is written when the next history data is written. By writing over the data, it is possible to prevent the history data column from becoming full due to frequent interruptions, and to effectively use the memory.

[0562] In step S2186, the card file is updated, and in step S2187, the i counter is set to "-1". In step S2188, the "ACK" packet containing the card text read from the card file is sent to the pachinko machine. Send to 100.

If the card number in the packet and the card number in the file do not match in step S2184, or if the card numbers match but the card state is not "interrupted", step S2184 is executed. S2
At 191 it is determined whether the card status is "playing" or not. If it is not "playing", it is determined that an inappropriate card has been inserted, and the flow jumps to step S2189 to return to "NA".
K "packet is transmitted.

However, if the card status is not “interrupted” but determined to be “playing” in step S 2191, the flow advances to step S 2192 to determine the P machine number in the received packet and the card number in the card file. Compare with the number
If they match, the flow shifts to step S2188 to transmit an "ACK" packet containing the card text. In this case, for example, the management device 400
In this case, it is assumed that the pachinko machine 100 has not received it and transmitted the “interrupted card-in” packet again after executing 2181 to S2188 and transmitting “ACK”.

[0564] If the machine numbers do not match in step S2192, the inserted card is incompatible, so step S218 is performed.
Then, the process proceeds to step S9 to transmit a “NAK” packet.

FIG. 116 shows that the pachinko machine 100
7 shows a processing procedure of the central processing unit CPU when receiving a “suspension switch” packet transmitted from the pachinko machine 100 to the management apparatus 400 when the interruption switch provided in is turned on.

When receiving this packet, central processing unit C
The PU first calculates the card issue serial number from the card number in the packet, searches the card file using the card issue serial number, and reads out the corresponding card data (steps S2201, S2202).

Next, the card state of the card data read from the card file is checked to determine whether or not the game is "playing" (step S2203). here,
If the card status is "playing", the flow advances to step S2204 to compare the card location terminal number in the packet with the location terminal number of the card read from the file, and if they match, the data in the card file (card number , The number of balls, the amount, the card state, the serial number of the terminal located and the terminal number of the terminal) are rewritten to the data in the packet (step S2205). Then, i in the corresponding card file
It is checked whether the counter is less than 19 (step S22).
06), if it is less than 19, the i-counter is incremented in step S2207, and the unit number, the number of balls and the amount of money in the packet and the current time of the timer are written in the next log data column, and then the "ACK" packet containing the card text is inserted Transmission to the pachinko machine 100 (steps S2208, S2
209). If it is determined in step S2206 that the i-counter is 19, the process jumps to step S2208 without updating the i-counter and writes the data in the packet so as to overlap the 19th log data column. In this embodiment, the number of history data columns is 20, and the twentieth data column is left for writing adjustment data.

On the other hand, when it is determined in step S2203 that the card status in the card file is not "playing" and the card status is "playing", the process proceeds to step S22.
If it is determined in step 04 that the unit numbers do not match, the process proceeds to step S2211, and it is determined whether the card state is "interrupted". Here, if no, that is, if the card state is neither “playing” nor “suspending”, step S2214
Jump to and send the “NAK” packet to the pachinko machine 100
Send to

If it is determined in step S2211 that the card status is "suspending", the process proceeds to step S2212.
The process proceeds to step S2213, where the location terminal number in the packet is compared with the location terminal number in the file, and if they match, an "ACK" packet is returned (step S2213). This is in consideration of a case where the same “interruption switch” packet is transmitted again after transmitting “ACK” in step S2209. If the card numbers do not match even if the card status is “suspended” in step S2211, a “NAK” packet is transmitted (steps S2212 to S2214).

FIG. 117 shows that the pachinko machine 100
7 shows a processing procedure of the central processing unit CPU when receiving an “end switch” packet transmitted from the pachinko machine 100 to the management apparatus 400 when the end switch provided in is turned on.

[0571] The processing procedure when this packet is received is almost the same as the processing procedure (steps S2201 to S2214) when the "interrupt switch" packet in Fig. 116 is received.

[0572] The difference is that "free" is written as the card state when the card file is updated in step S2225, and that the card number in the file is "free" in step S2231, instead of whether or not the card number is "interrupted". It is only a point to determine whether or not it is.

FIG. 118 shows that when the pachinko machine 100 returns to zero (both the number of balls and the amount of unused money are zero) during the game, the pachinko machine 100 sends the information to the management device 40.
7 shows a processing procedure of the central processing unit CPU when a “stop” packet transmitted to “0” is received.

The processing procedure when receiving this packet is almost the same as the processing procedure (steps S2201 to S2214) when receiving the "interrupt switch" packet in FIG.

[0575] The difference is that "return to zero" is written as the card state when the card file is updated in step S2225, and "return to zero" is determined in step S2251 instead of whether or not the card number in the file is "interrupted". It is only a point to determine whether or not.

FIG. 120 shows the processing of the central processing unit CPU when the “pause” packet transmitted from the pachinko machine 100 to the management device 400 is received when the pachinko machine 100 is hit during the game. Here are the steps.

Steps S2261 to S2268 in the processing procedure when this packet is received correspond to steps S2201 to S2208 in the processing flow of FIG.
And steps S2275 to S2278 in FIG. 119.
Corresponds to step S221 in the processing flow of FIG.
1 to S2214. The difference is step S
At the time of updating the card file at 2265, "stop" is written as the card state, and at step S2275, it is determined whether the card state is "free" or "stopped" instead of "interrupted". Is a point.

[0578] Further, in this "stop" packet receiving process, the data and time in the received packet are written in the log data column of the card file in step S2268, and the "ACK" packet is not immediately transmitted. ,
As shown in FIG. 119, the P machine file is searched using the machine number in the received packet, and the corresponding pachinko machine 100 is searched.
After rewriting the operation information in the data of
An interrupt command containing the stop interrupt display screen data is sent to the local processing device 413, and the printer 408
The “ACK” packet is printed out together with the machine number indicating that the stoppage has occurred by the pachinko machine 10.
0 (steps S2269 through S2269).
2273).

When the local processing device 413 receives the stop interrupt command transmitted by the central processing unit CPU in step S2271, the stop message (time, stop table, and stop table) is displayed on the 19th line of the screen of the CRT display device 411. Stop times)
Is displayed as an interrupt and the buzzer is turned on (steps S1061 to S1063).

[0580] FIG. 120 shows the payment card 3 based on the "card payment" packet transmitted to the management device 400 when a card is inserted into the payment machine 300 and its "ACK".
Central processing unit CPU when "00" receives a "payment end" packet transmitted after executing card payment
The following shows the processing procedure.

[0581] Upon receiving the "card settlement" packet, the central processing unit CPU first reverses the card issue serial number from the card number in the packet, searches for a card file using the card issue serial number, and retrieves the data of the card. To determine whether the card state is "free" or "interrupted" (steps S2281-S228).
3). If the card status is "free" or "interrupted", the current time of the timer is set as the settlement acceptance time in step S2284, and the card number, the number of balls, and the amount of money in the card data in the card file. An "ACK" packet containing the card issuing serial number and card history data as settlement data is transmitted to the settlement machine (step S2284). On the other hand, if the card status read from the card file is neither “free” nor “suspended”, the flow shifts from step S2283 to S2285 to transmit a “NAK” packet. When receiving the "ACK" packet, the payment machine 300 issues a receipt on which the payment data in the packet is printed, refunds the unused money, and transmits a "payment end" packet.

When the management device 400 receives this “payment end” packet, the central processing unit CPU first calculates the card issue serial number from the card number in the packet, and
The card file is searched using the card issuing serial number, the data of the card is read, and it is determined whether or not the card state is "interrupted" (steps S2291-S229).
3). Here, if the card state is “interrupted”, the “pause end” packet is transmitted to the pachinko machine 100 corresponding to the terminal terminal number of the card read from the card file in step S2274, and the pachinko machine 10 in the suspended state is transmitted.
0 is changed to the free state in which the game can be played, and if the card state is not "interrupted", step S2294
Jumps to step S2295, and updates (increments) the i counter in the card file. Then, the card status in the card file is changed to “payment completed”, the payment data is written in the i-th payment data column, and the “ACK” packet is sent to the payment machine 300.
(Steps S2295, S2296).

FIG. 121 shows a processing procedure in the central processing unit CPU and the local processing unit 413 when the hit release switch 433 provided on the console 412 is turned on.

[0584] When the stop release switch 433 is turned on,
The local processing device 413 transmits a hitting table data request command to the central processing unit CPU (step S1).
071). When the central processing unit CPU receives this command, the P machine files are sequentially read from the main storage device M-MEM, and it is checked whether the operation information is "stopped". The number of hits, the number of outgoing balls, the number of outgoing balls, the number of balls, the number of balls, the number of sales, and the number of pachinko machines in the state are transmitted to the local processing device 413 (steps S2301 to S230).
3).

Then, the local processing device 413 operates as shown in FIG.
A percussion table release display screen as shown in FIG. 60 is displayed, and percussion tables and their operation data are displayed on the screen, one by one per line (step S1072).

On the other hand, after transmitting the operation data of the hitting table, the central processing unit CPU determines in step S2305 whether or not the operation information in the P machine file has been checked for all the pachinko machines, and if not completed, proceeds to step S2301. Return to the next page, and check if the operation information of the next pachinko machine is "stop". When the operation information check is completed for all the units, a stop table data end command is transmitted to the local processing device 413 (step S2304). Then
The local processing device 413 displays a message prompting the user to input the number of the vehicle to be released from the hitting on the 16th and 17th lines of the hitting table release display screen in FIG. 160 (step S1073).

When the operator sees this message and inputs the pachinko machine number or “0” (when “0” is entered, all machines are designated) from the ten-key 425, the local processing device 413 enters A stop release request command is transmitted (step S1074). Central processing unit C
When the PU receives the command, the PU determines whether or not to cancel the stopping for all pachinko machines that are being stopped (steps S2306 and S2307).

[0588] If not all the machines have been designated, the flow advances to step S2308 to read the designated pachinko machine file, and determine whether or not the operation information is "stop" (step S2309). When the operation information is other than “stop”, the process jumps to step S2314 and transmits the result.
If the operation information is “stop”, after transmitting a “stop release” packet to the designated pachinko machine, it is determined whether or not “ACK” has been received. The operation information is changed from "stop" to "free", and the stop release result is transmitted to the local processing device 413 (steps S2310 to S2314).

On the other hand, if it is determined in step S2307 that all units have been designated, the flow advances to step S2315 to sequentially read P machine files and determine whether or not the operation information in the files is "stop". If it is not "stop", the process jumps to step S2320, and if it is "stop", it jumps to step S2320.
"Release hitting" to the corresponding pachinko machine from 2316 to S2319
After transmitting the packet, it is determined whether or not "ACK" has been received. If "ACK" has been received, the operation information of the file of the P device is changed from "stop" to "free", and then the process proceeds to step S2320. It is determined whether the process has been completed for all units. If not completed, the process returns to step S2315 to repeat the above procedure.
Then, the flow shifts to 2314 to transmit the stop release result. Then
The local processing device 413 receives the hit release result, changes the character “hit” displayed in the last column of the corresponding pachinko machine on the hit table release display screen in FIG. 160 to “empty”, and ends the processing. (Step S1075).

[0590] In Fig. 122, the pachinko machine 1 is turned on by turning on the forced termination switch 434 provided on the console 412.
The processing procedure in the central processing unit CPU and the local processing unit 413 when forcibly terminating 00 is shown.

When the forced end switch 434 is turned on,
The local processing device 413 sets the forced termination menu screen to C
Display on the RT display device 411 (step S108)
1). While viewing this screen, using the numeric keypad 425, enter the number indicating the type of terminal that is to be forcibly terminated out of the pachinko machine, the issuing machine, and the checkout machine.
13 displays a unit forced termination screen corresponding to the specified terminal type (step S1082).

FIG. 161 shows the pachinko machine 100 among them.
4 shows a forced termination screen of the above. In the forced termination screen of the issuing machine 200 and the forced termination screen of the checkout machine 300, the characters “Pachinko machine” displayed on the fifth line of the pachinko machine forced termination screen in FIG. Or it just changes to a “payment machine”.

[0593] The pachinko machine 100 to be forcibly terminated by the ten keys 425 of the console 412 while viewing this screen.
, The local processing unit 413 transmits a pachinko machine forced termination request command to the central processing unit CPU, and then displays a normal display screen (FIG. 159). (Steps S1083 and S1084).

When the central processing unit CPU receives the pachinko machine forced termination request command from the local processing unit 413, the central processing unit CPU determines whether or not all machines have been designated. If yes, the P machine files are sequentially read, and the operation information in the file is read. It is checked whether the game is being played or interrupted (step S2341)
S2343). If no, the process jumps to step S2347. If yes, the card issue serial number is calculated back from the card number existing in the pachinko machine read from the P machine file, and the card file is read using the serial number (steps S2344, S2345). . Then, the data read from the P machine file is entered in the fields of the number of balls and the amount of money in the file, the card status is changed to "free" (step S2346), and it is determined whether or not all the devices have been completed (step S2347). If no, return to step S2342 and repeat the above procedure.

[0595] If the operation information has been checked and the card file has been updated for all units, step S2
After transmitting the “forced termination request (type)” packet to all the NAUs 530 and receiving a response from the NAU 530, the result is transmitted to the local processing device 41.
3 (steps S2348 to S2350). Then, the local processing device 413 is operated by the operator in FIG.
Select the specific display on the display menu selection screen of 7,
When the specific-vehicle display screen of FIG. 169 or the all-vehicle display screen of FIG. 169 is displayed, a character “strong” indicating that forced termination is in progress is displayed in the last column of the corresponding pachinko machine (step S1085). , S1086).

On the other hand, if it is determined in step S2341 that all units have not been designated, a "forced termination request (individual)" packet is transmitted to the designated pachinko machine (step S23).
51). Then, it is determined whether or not "ACK" has returned from the pachinko machine (step S2352). If not, the process jumps to step S2350. If the ACK returns, the data of the pachinko machine is transferred from the P machine file. It reads and checks whether the operation information is “in play” or “interrupted”.
After updating the card file according to the same procedure as in steps S44 to S2346, the process proceeds to step S2350 to transmit the forced termination result to the local processing device 413 (step S2).
2353-S2357).

In FIG. 123, the forcible termination switch 434 provided on the console 412 is turned on to
Is a processing procedure in the central processing unit CPU and the local processing unit 413 when the processing is forcibly terminated.

When the forced end switch 434 is turned on,
The local processing device 413 sets the forced termination menu screen to C
Display on the RT display device 411 (step S109)
1). While viewing this screen, when the number indicating the type of the terminal to be forcibly terminated out of the pachinko machine, the issuing machine and the payment machine is input using the numeric keypad 425, the local processing device 41 is displayed.
No. 3 displays an issuer forced termination screen corresponding to the specified terminal type (step S1092).

In the forced termination screen of the issuing machine 200, only the character “Pachinko machine” displayed on the fifth line of the pachinko machine forced termination screen in FIG. 161 is changed to “Issuing machine”.

While viewing this screen, when the machine number or “0” (all machines specified) of the issuing machine 200 to be forcibly terminated is input using the numeric keypad 425 of the console 412, the local processing unit 413 forcibly issues the issuing machine to the central processing unit CPU. After transmitting the end request command, the display is changed to a normal display screen (FIG. 159) indicating that the business is open (step S109).
3, S1094).

[0601] When the central processing unit CPU receives the issuer forced termination request command from the local processing unit 413, it determines whether or not all units have been designated, and if yes, sends a "forced termination request (type)" packet to all NAUs. Is transmitted, and if the response is received, the result is transmitted to the local processing device 413 (steps S2361 to S2364). Then, when the operator views the menu selection screen of FIG. 167 and selects the issuer data display to display the issuer data display screen of FIG. 171, the local processing device 413 displays The character “strong” indicating that the forced termination is being performed is displayed (steps S1095 and S1095).
1096).

On the other hand, if it is determined in step S2361 that not all the units have been designated, a "forced termination request (individual)" packet is transmitted to the designated issuing machine 200 (step S2).
365). Then, it is determined whether or not “ACK” has returned from the issuing device 200 (step S2366). If not, the process jumps to step S2364, and the ACK is returned.
Is returned, the operation information in the file of the issuing machine is changed to the forced termination in step S2367, and the process proceeds to step S2364 to transmit the forced termination result to the local processing device 413.

In FIG. 124, when the forced termination switch 434 provided on the console 412 is turned on,
Is a processing procedure in the central processing unit CPU and the local processing unit 413 when the processing is forcibly terminated.

When the forced end switch 434 is turned on,
The local processing device 413 sets the forced termination menu screen to C
Display on the RT display device 411 (step S110)
1). While looking at this screen, using the numeric keypad 425, enter the number indicating the type of terminal that is to be forcibly terminated among the pachinko machine 100, the issuing machine 200, and the settlement machine 300, and the local processing device 413 corresponds to the type of the specified terminal. A payment machine forced termination screen is displayed (Step S110)
2). The subsequent procedure is the same as in the case of the forcible termination of the issuing machine in FIG.

FIG. 125 shows the central processing unit CPU and the local processing unit 413 when the forced termination state of the pachinko machine 100 terminated by the processing of FIG. 122 is released.
The following shows the processing procedure.

Exit termination switch 4 on console 412
When the user turns on 35, the local processing device 413 displays a forced termination release menu screen similar to the forced termination menu screen
Display on the T display device 411 (step S111
1). While viewing this screen, enter the number for specifying the pachinko machine with the ten keys 425, and the local processor 4
Reference numeral 13 denotes a central processing unit C
The data is transmitted to the PU (step S1112).

Upon receiving this command, the central processing unit CPU reads the pachinko machine files in order and checks whether the operation information is “forcibly terminated”. The number and the number of hits, the number of balls, the number of balls out, the number of differences, the number of balls, the number of sales, and the number of customers are transmitted to the local processing device 413 (step S).
2381-S2383). Then, the local processing device 4
No. 13 displays the data of the pachinko machine which has been compulsorily terminated on a line-by-line basis on a pachinko machine termination release screen as shown in FIG. 162 (step S1113).

On the other hand, the central processing unit CPU determines whether the operation information check has been completed for all the units after transmitting the forced termination unit data (step S2384), and if no, returns to step S2381; S
The process proceeds to 2385 to transmit a display data end command to the local processing device 413. Then, the local processing device 413 issues a forced termination release message prompting the user to input the number of the unit whose forced termination should be released, as shown in the first screen of FIG.
It is displayed on the 7th and 18th lines (step S1114). When the operator inputs the machine number or all machine designation “0” from the numeric keypad 425 while viewing this screen, a pachinko machine forced termination cancellation request command is transmitted to the central processing unit CPU (step S1115).

When the central processing unit CPU receives this command, it determines whether or not all the units have been designated.
After transmitting the “forced termination release (type)” packet to the AU 530, it receives a response (ACK or NAK) from the NAU 530 and transmits the result to the local processing device 413 (steps S2386 to S2389).

If it is determined in step S2386 that all the units have not been designated, the flow shifts to step S2391 to transmit a "forced termination release (individual)" packet to the designated pachinko machine. Then, it is determined whether or not “ACK” has been received (step S2392).
At 393, the operation information in the file of the pachinko machine is changed to "free", and if no, the process directly jumps to step S2389, and the result is sent to the local processing device 4.
13 is transmitted. Upon receiving the transmission from the central processing unit CPU that the forced termination cancellation has been successful, the local processing unit 413 changes the status display in the last column of the display data line of the pachinko machine from “strong” to “empty” indicating free. It is changed (step S1116).

FIG. 126 shows the case where the forcible termination state of the issuing machine 200 which has been forcibly terminated by the processing of FIG. 123 is released, and FIG. 127 shows the case where the settlement apparatus 300 forcibly terminated by the processing of FIG. The processing procedure of the central processing unit CPU and the local processing unit 413 when releasing the end state will be described.

These procedures are substantially the same as the pachinko machine forced termination cancellation procedure in FIG. 125. In the process of FIG. 126, the issuing machine file is searched, and the machine number of the issuing machine, the received amount, the deposit amount, the paid out amount, the number of times of issuance, and the monitor information 2 are transmitted as the forced termination device data, and the CRT display device 411 is displayed in FIG. A screen for canceling the forced termination of the issuing machine as shown below is displayed.

On the other hand, in the processing of FIG. 127, the settlement machine file is searched, and the machine number of the settlement machine, the settlement amount, the number of settlement balls, the number of settlements, and the monitor information 2 are transmitted as the forced termination unit data, and the CRT display device 411 is transmitted. A screen for canceling the forced termination of the settlement machine as shown in FIG. 164 is displayed.

In the forced termination cancellation processing of the issuing machine 200 and the settlement machine 300, if the processing is successful, the status display at the end of each line on the display screen is changed from “stop” indicating that operation is stopped to blank (no display). It is supposed to.

FIG. 128 shows the processing procedure of the central processing unit CPU when a power failure occurs.

When a power failure occurs, the power supply is switched, and the central processing unit CPU is backed up by the auxiliary power supply 409 and operates. First, it is determined whether the operation mode is “business” or “closed” (step S2441, step S2441). S
2442) When the operation mode of the central processing unit CPU is other than "in business" or "closed" (during preparation, during power outage startup), the system goes down without any operation. On the other hand, when the mode is “open” or “closed”, the local processing unit stops collecting scheduled data from each unit, changes the mode to “under power failure countermeasures”, and reports that the power outage countermeasures are underway. 413 (from step S2443).
S2445). Then, the local processing device 413 sets the CR
A power failure message is displayed on the T display device 411 (step S1141). On the other hand, the central processing unit CPU reads the P machine file and checks the operation information, and when the operation information is “playing”, the issue serial number is calculated back from the card number in the P machine file, and the card file is used by using it. The search is performed and the card status is rewritten to “free” (steps S2446 to S2450). After that, the operation information in the P machine file is rewritten to "free", and then it is determined whether or not all pachinko machines have been completed. If yes, the data in the common data area (including the setting value file and the power failure flag)
And the card file P machine file, the issuing machine file, and the checkout machine file are saved on the hard disk HDD, and the mode is changed to "closed" before the system goes down (steps S2450 to S2453).

During the display of the power failure message, the local processing unit 413 inquires of the central processing unit CPU about the mode.
Display on the RT display device 411 (step S1142)
To S1144).

FIG. 129 shows the procedure of the system error recovery processing by the central processing unit CPU.

The central processing unit CPU receives 3
When an interrupt is received every 0 seconds, the error recovery processing of FIG. 129 is started, and it is first determined whether or not the mode is "in business" (step S2461). If so, the flow advances to step S2462 to read the NAU status from the transmission address file and determine whether the bit NORMAL indicating whether the NAU is normal or abnormal is "0" (= abnormal) (step S246).
2, S2463). In addition, NORM of NAU status
The AL bit is set to “1” (= normal) in response to the “line test” packet in steps S <b> 2016 and S <b> 2017 in the initialization flow of FIGS. The NORMAL bit remains "0".

If the NORMAL bit is determined to be “0”, the NAU recovery processing step S in FIG.
2471 to S2475 are executed. On the other hand, if the NORMAL bit of the NAU status is “1”, step S24
Proceeding to 64, the monitor information 1 in the unit file is read to check whether the bit indicating the token bus abnormality is "1". If it is "1", the token bus recovery processing steps S2481 to S2486 of FIG.
If it is "0", it is checked in the next step S2466 whether the bit indicating the hot code error in the monitor information 1 is "1", and if it is "1", the hot code recovery processing S2491 to S2498 of FIG. 131 is executed. I do. On the other hand, if NO (no hot code error) is determined in step S2466, the process advances to step S2467 to check whether the unit abnormality bit in the monitor information 1 is "1". If "1", the unit in FIG. Recovery processing S25
01 to S2509 are executed.

In the NAU recovery processing shown in FIG. 130A, first, a “line monitor check” packet is transmitted to the NAU 530 in which the NORMAL bit of the NAU status is “0”, and the timer is set. If the response "ACK" is received before the time is over, the NORMAL bit of the NAU status is changed to "1", and then the interrupt display command is transmitted to the local processing device 41.
3 to display a message on the CRT display screen indicating that the NAU 530 has been recovered, and
08, the same contents are printed out, and if "ACK" does not return within a predetermined time, the process returns to the original routine without doing anything (steps S2471-S247).
4).

In the token bus recovery processing shown in FIG. 130, first, a “unit monitor check” packet is transmitted to a unit whose token bus abnormality bit is “1” to set a timer (step S2481, step S2481).
S2482). Then, it is determined whether or not a response “ACK” has been received before the time is over (step S24).
83, S2484), if "ACK" is received within the time, the token bus abnormal bit of the monitor information 1 in the unit file is cleared to "0", and then a "restart" packet is transmitted to the unit. It is restarted (steps S2485 and S2486).

In the hot code recovery processing shown in FIG. 131, first, a “unit recovery data” packet is transmitted to the unit having the hot code error, and a timer is set (steps S2491 and S2492). Then, if "ACK" is received before the time over occurs,
The hot code included in the “unit recovery data” packet is compared with the hot code returned in the “ACK” packet (steps S2493 to S2495). If the hot codes do not match, step S249
8 to set the hot code error bit of the monitor information 1 in the unit file to “1”, and when the hot codes match, “restart” to the unit.
After transmitting the packet, the hot code error bit of the monitor information 1 of the unit is cleared (step S2).
496, S2497).

[0624] The reason why the "restart" packet is transmitted in step S2496 is that the unit that has received the "unit recovery data" packet transmitted in step S2491 enters a forced termination state.

In the unit recovery processing shown in FIG. 132, first, a “unit monitor check” packet is transmitted to a unit having a unit abnormality to set a timer (steps S2501, S2502). Then, if "ACK" is received before the time is over, the "unit recovery data" packet is transmitted and the timer is set again (steps S2503 to S2506). Then, if "ACK" is returned within a predetermined time for this packet transmission, a "restart" packet is transmitted to the unit and the unit is restarted (step S25).
07 to S2509).

FIG. 133 shows the processing procedure of the central processing unit CPU and the local processing unit 413 when the store close switch 422 and subsequently the system end switch 423 are turned on.

The store closing switch 422 on the console 412
Is turned on, the local processing device 413 displays a store closing menu screen showing a list of reception valid switches (display menu switch, print menu switch, and end switch), and then transmits a store closing request command to the central processing unit CPU.
(Steps S1151 and S1152).

When this command is received by the central processing unit CPU, the P machine file is read in order to check whether or not the operation information is "playing", and after storing the machine number of the pachinko machine of "playing", It is determined whether or not the search has been completed for all the devices, and if no, the process returns to step S2511 to repeat the above procedure (steps S2512 to S251).
4). When the operation information check is completed for all the machines, the process proceeds to step S2515 to determine whether there is a pachinko machine 100 in play, and if so, transmits the machine number of the pachinko machine 100 to the local processing device 413. If there is no pachinko machine in play, an ACK is transmitted to the local processing device 413, and a "closed" packet is transmitted to all the NAUs 530 to wait for a command from the local processing device 413 (steps S2516 to S251).
8). On the other hand, when the local processing device 413 receives the machine number or “ACK”, if there is a pachinko machine being played, the system end switch is invalidated, the machine number being played is displayed, and then the normal display screen (FIG. 159)
And waits for key input (steps S1153-
S1156). If the operator accidentally turns on the store closing switch during business hours, the operator can notice the error by looking at this display. When there is no pachinko machine in play, the screen does not change.
When is turned on, the system end screen (first to fourth lines) of FIG. 165 is displayed (step S1157).

When "1" is input from numeric keypad 425 in accordance with the instructions on this screen, local processing device 413 transmits a system termination request command to central processing unit CPU (step S1158). When the central processing unit CPU receives this command, it creates a daily report file including business data for one day, saves it on the hard disk HDD, deletes the power failure save file from the hard disk HDD, and transmits the system end message data (step S2520). To S2522). This is received by the local processing device 413, and a message instructing to turn off the power is displayed on the system end screen (see the ninth line in FIG. 165).
Is displayed (step S1159).

FIG. 134 shows the procedure of card recovery processing when the card recovery switch 424 provided on the console 412 is turned on.

When the card recovery switch 424 is turned on, the local processing device 413 displays a message (first to third lines) for prompting the user to input a card number on a card recovery screen as shown in FIG. (Step S116)
1).

[0632] Looking at this screen, when the issue serial number of the damaged card (printed on the card) is entered from the ten keys 425, the local processing unit 413 is turned on by the central processing unit C.
The card resumption data request command including the card issue serial number is transmitted to the PU (step S1162). Then, the central processing unit CPU searches the card file using the sent card issuing serial number, reads the data of the card, and determines whether or not the card state is "playing" (steps S2531, S2532).

If the card status is “playing”, the pachinko machine file is searched using the terminal number in the card file, the data of the pachinko machine is read, and the number of balls and the amount of money in the pachinko machine file are read. Is the current value of the card. The data is transmitted to the local processing device 413 together with the data (steps S2533 to S253).
6).

Then, the local processing device 413 displays the received card data and the history on the card recovery screen (FIG. 166) (step S1163). Then, when the card recovery switch 424 is turned on again, a card recovery request command is transmitted (step S1164). When this command is received by the central processing unit CPU, first, an "initial value transmission" function including an initial value such as a date and an identification code is sent to the card issuing apparatus 700, and a response ("normal end" function) to the function is transmitted. Upon receipt,
This time, a "card rebirth" function including the card number, the card issuance serial number, and the amount at the time of issuance is sent to start the rebirth card issuance processing (steps S2537 to S2537).
2539). When the issuance of the resurrection card is completed in the card issuing device 700, the result (normal termination function) is transmitted. The central processing unit CPU receives the resend card and transmits the resurrection completion to the local processing device 413 (step S2540, step S2540). S2541). Then, the local processing device 413 displays the result on the card resurrection screen, and then changes the screen to the normal display screen (step S1).
165). The card issuing device 700 that has received the “card resurrection” function prints the issue date and the serial number, and issues a resurrection card with a reissue hole (the amount is not printed).

FIG. 135 shows the procedure of the test card issuing process when the test card switch 437 provided on the back of the console 412 is turned on.

When the test card switch 437 is turned on, the local processing device 413 displays a test card issuance message on the screen of the CRT display device 411,
A test card issuance request command is transmitted to the central processing unit CPU (steps S1171, S1172).

When this command is received, the central processing unit C
The PU sends an “initial value transmission” function in which initial values such as the date and the identification code are entered to the card issuing device 700 and responds to the function (“normal end” function).
Is received, a "test card issuance" function is transmitted (steps S2542 to S2544).

[0638] When the test card issuance process in the card issuing device 700 is completed, the result is transmitted.
After receiving the result, a test card issuance end is transmitted to the local processing device 413 (step S2545,
S2546). Then, the local processing device 413 displays the test card issuance result on the CRT display device 411 ”, changes the display screen to the normal display, and ends (step S1173).

[0639] Upon receiving the "test card issuance" function, the card issuing device 700 prints a test card character instead of the issuance date and amount, and records the test card issuance function code in the magnetic recording unit MG. Issue a test card (do not punch holes).

FIG. 136 shows a display flow of business statistical data by a timer interrupt.

In the management apparatus 400 of this embodiment, when an interrupt signal comes in at a predetermined cycle from the timer TMR,
The sales statistics data display flow of 36 is started, and first, the local processing device 413 transmits a sales statistics data request command to the central processing unit CPU (step S1181). When this command is received by the central processing unit CPU, the pachinko machine files are sequentially read, and first, the number of payout balls, the number of outgoing balls, and the total sales are calculated from the operation data collected as the regular data (steps S2551, S2552).

Next, the operation information in the file is checked, and if the game information is “playing”, the number of the game machines is added by one, and if the operation information is “stopped”, the number of the game machines is added by one (step S).
2553-S2556). Then, it is determined whether the search has been completed for all the pachinko machines (step S2557),
If no, the flow returns to step S2551 to repeat the above-described procedure.
In step 8, after calculating the dividing number (the number of outgoing balls ÷ the number of outgoing balls) from the cumulative value of the number of outgoing balls and the number of outgoing balls, and the operating rate (the number of playing games ÷ the total number of pachinko machines) from the cumulative value of the number of playing games Then, the sales, the division number, the operation rate, and the number of hits are transmitted to the local processing device 413 as the sales statistical data (step S25).
58, S2559).

On the other hand, when the local processing device 413 receives the sales statistical data from the central processing unit CPU, the local processing device
The second screen of the display screen of the display device 411 (see FIG. 159)
The data is displayed on the 0th line (step S11).
82).

[0644] Fig. 137 shows the procedure of the hit table display processing.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1201).

When the operator selects percussion table display using the numeric keypad 425 while viewing this screen, the local processor 413 sends a percussion table display data request command to the central processing unit CPU (step S1202). Upon receiving this command, the central processing unit CPU reads the pachinko machine file in order, checks whether the operation information in the file is “stopped”, and operates only the file that is “stopped”. Among the data, the number of hits, the number of balls, the number of outgoing balls, the number of differences, the number of balls, the number of sales, and the number of customers are used as hitting table data together with the table number as the local processing unit 4.
13 (steps S2561 to S2563).

[0647] Then, the local processing device 413 displays each hit table data on the hit table display screen as shown in FIG.
Are sequentially displayed on one line of the table (step S120)
3). On the other hand, when the central processing unit CPU completes the search for the percussion table for all the pachinko machine files (step S2564), the central processing unit CPU notifies the local processing unit 4 of the end of the display data.
13 and when the local processing device 413 receives it, it waits for a key input (steps S2565 and S12).
04).

[0648] Fig. 138 shows the procedure for specific-unit display processing.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 130 is displayed on the RT display device 411 (step S1211).

[0650] When the operator selects a specific-table display using the numeric keypad while viewing this screen, the local processing device 41
3 transmits a specific-unit display data request command to the central processing unit CPU (step S1213). On the CRT display device 411, a message prompting to specify (input) a card number is displayed on the first to third lines of the specific-unit data display screen shown in FIG. 169 (step S121).
2). While looking at this screen, the operator presses the ten-key 425
When the card number is input, the local processing device 413
Transmits a specific-unit display data request command including the card number to the central processing unit CPU (step S121).
3).

Upon receiving this command, the central processing unit CPU calculates a serial number from the machine number, searches the pachinko machine file using the serial number, and searches the corresponding pachinko machine 1
00 is read (steps S2571, S2).
2572). Then, the number of hits, the number of outgoing balls, the number of outgoing balls, the difference number, the number of balls, the number of sales, and the number of customers in the operation data are transmitted to the local processing device 413 (step S25).
73). Then, the local processing device 413 displays the received data on the fifth line of the specific-unit data display screen (FIG. 169) (step S1214). Thereafter, a data end command is transmitted from the central processing unit CPU to the local processing unit 413, and the process ends (steps S2574, S2).
1215).

FIG. 139 shows the procedure of data display processing for all pachinko machines.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1221).

When the operator selects the display of all units using the numeric keypad while viewing this screen, the local processing unit 413
Transmits an all-unit display data request command to the central processing unit CPU (step S1222). Upon receiving this command, the central processing unit CPU reads the pachinko machine file in order, and calculates the number of hits, the number of outgoing balls, the number of outgoing balls, the difference, the number of balls, the number of sales, and the number of customers among the operation data in the file. The number is transmitted together with the number (step S258)
1, S2582).

[0655] Then, the local processing device 413 sequentially displays the data of all the pachinko machines on the display screen of all the pachinko machines, one by one, as shown in FIG. 169 (step S12).
23). On the other hand, when the central processing unit CPU completes the search for all the units in the pachinko machine file (step S25)
83), the end of the display data is transmitted to the local processing device 413, and when the local processing device 413 receives this, it waits for a key input (steps S2584, S1224).

[0656] Fig. 140 shows the procedure of data display processing of a so-called red board (red box) in which the number of payout balls is larger than the number of outgoing balls.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1231).

[0658] While viewing this screen, if the operator selects red display using the numeric keypad 425, the local processing unit 413 sends a red display data request command to the central processing unit CPU (step S1232). Upon receiving this command, the central processing unit CPU sequentially reads the pachinko machine file (step S2591) and determines whether the difference number in the file is negative (minus) (step S2592). Then, only the operation data of the pachinko machine with the negative difference is transmitted to the local processing device 413 (step S2593).

Then, the local processing unit 413 sequentially displays each red stand data on the red stand display screen, one by one, as shown in FIG. 170 (step S1233).
On the other hand, when the central processing unit CPU completes the search for the red platform for all the pachinko machine files (step S259)
4), display data end is transmitted to the local processing device 413, and when the local processing device 413 receives this, it waits for a key input (steps S2595 and S1234).

FIG. 141 shows the procedure of data display processing of a so-called black table (black table) in which the number of payout balls is smaller than the number of outgoing balls.

This black stand display flow is performed according to almost the same procedure as the red stand display flow of FIG. The only difference is that instead of determining whether the difference number is negative in step S2592, the difference number is determined to be positive (plus) and only the operation data of the positive pachinko machine is transmitted (step S2612). The configuration of the display screen is also the same as the red platform display screen of FIG.

FIG. 142 shows the procedure of the issuing machine data display processing, and FIG.
1 shows an example of the configuration of an issuer data display screen displayed on the display 1.

The issuing machine data display processing flow is shown in FIG.
The processing is executed according to almost the same procedure as the processing data display processing flow of the 39 pachinko machines. What is displayed on the screen as issuer data together with the machine number is the amount of money received, the amount of money deposited, the amount of money to be paid out, the number of issuances, and the monitor. here,
The monitor corresponds to the monitor information 1. In addition,
After displaying data for all issuing machines, their sum is displayed on the 18th line. Calculation of total data is performed by central processing unit CPU
(Step S2623).

FIG. 143 shows the procedure of the checkout machine data display processing, and FIG.
1 shows a configuration example of a checkout machine data display screen displayed on the display 1.

FIG. 14 is a flow chart of the settlement machine data display process.
The processing is executed according to almost the same procedure as the data display processing flow of the second issuer. What is displayed on the screen as the payment machine data together with the machine number is the payment amount, the number of payment balls, the number of payments, and the monitor.

[0666] Fig. 144 shows the procedure of sales data display processing for displaying the sales data of the entire pachinko parlor, that is, the total of the main operation data of all the units, and Fig. 173 displays the same. 4 shows a configuration example of a sales data display screen.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1271).

When the operator selects sales data display using the numeric keypad while viewing this screen, local processing device 413 transmits a sales data display data request command to central processing unit CPU (step S1272).
Upon receiving this command, the central processing unit CPU sequentially reads the pachinko machine file and calculates the total of the number of payout balls, the number of outgoing balls, the difference number, and the number of possessed balls in the operation data (steps S2641 to S2643). Next, the issuing machine files are sequentially read out, and the total of the deposit amount and the number of issuances among the operation data are calculated (step S264).
From 4 to S2646), the payment machine files are read out in order, and the total of the payment amount, the number of payment balls and the number of payments in the operation data is calculated (steps S2647 to S264).
9). Thereafter, the calculated total data is transmitted to the local processing device 413 as business data, and after transmitting all the data, a display data end command is transmitted (step S).
2650, S2651).

On the other hand, when receiving the business data, the local processing device 413 displays the business data display screen shown in FIG. 173 on the CRT display device 411, receives the display data end command, and waits for key input (step S12).
73, S1274). In the business data, the number of issued cards is displayed as the number of issued cards, and the number of payments is displayed as the number of paid cards.

FIG. 145 shows the procedure of the specific card data display processing for displaying the data of the specific card.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1281).

When the operator selects a specific card display using the numeric keypad 425 while looking at this screen, a message prompting to specify (input) a card number on the first to third lines of the specific card data display screen shown in FIG. 174. Is displayed (step S1282). When the operator inputs a card number from the numeric keypad 425 while viewing this screen, the local processing unit 413 sends a specific card display data request command including the card number to the central processing unit CPU (step S1283). Then, the central processing unit CPU reversely calculates the card issuing serial number from the card number, reads the card file using the issued serial number, and determines whether the card state in the card file is "in play" (steps S2661 to S2663). . When the card status is other than "playing", the number of balls and the amount in the card file are used as the current value of the card, and when the card status is "playing", the card location terminal number in the card file is used. Search the pachinko machine file by using the data in the pachinko machine file (number of balls, amount)
As the current value of the card (steps S2664-S26)
66). This is because the operation data in the card file does not match the actual value during the game because the card file is rewritten when the card state changes.

Next, the central processing unit CPU determines in step S2
664, the card current value determined in S2666 is transmitted to the local processing device 413 together with the card history data read from the card file, and then a display data end command is transmitted (steps S2667, S2668). Then, the local processing device 413 displays the data of the specified card on the fourth line or lower of the specific card data display screen of FIG. 174, receives a display data end command, and waits for key input (step S1284). , S12
85).

FIG. 146 shows the procedure of the all-card details display processing for displaying data on all issued cards, and FIG. 175 shows a configuration example of the all-card details display screen displayed thereby.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1291).

When the operator selects the card detail display with the numeric keypad while viewing this screen, the local processing unit 413 sends a card detail display data request command to the central processing unit CPU (step S1292).
Upon receiving this command, the central processing unit CPU reads the pachinko machine files in order, checks whether the operation information in the file is "under play", and checks whether the card state is "playing" (step S2671, S2
672). When the card status is other than "playing", the number of balls and the amount in the card file are used as the current value of the card, and when the card status is "playing", the card location terminal number in the card file is used. The pachinko machine file is searched for using the data (number of balls, amount) in the pachinko machine file as the current value of the card (step S2).
673 to S2675).

Next, the central processing unit CPU proceeds to step S26.
73, the card current value determined in S2675, the card status read from the card file, and the card location terminal unit number are transmitted to the local processing device 413 (step S).
2676). Then, the local processing device 413
As shown in FIG. 5, the remaining amount of money, the number of balls held, the terminal number where the terminal is located, or the card status of the data of each card are sent to each card.
It is displayed in rows (step S1293).

On the other hand, the central processing unit CPU determines in step S
After transmitting the card data at 2676, after adding the total number of issued cards by “1”, calculating the remaining amount of the card and the total number of balls held, and further calculating the number of cards in each card state It is determined whether or not the processing has been completed for all the cards (steps S2677 and S267).
8). If not completed, the process returns to step S2671 to repeat the above procedure, and if completed, the next step S2679
After transmitting the total data of the card to the local processing device 413 and displaying it on the all card details display screen of FIG. 175, the display data end command is transmitted (step S2).
679, S2680, S1294, S1295).

FIG. 147 shows the procedure of the card data total display process for displaying the total of the card data.

This total display processing is executed according to almost the same procedure as the card detail display processing shown in FIG. 146 (steps S1301 to S1304, S2681 to S268).
9). The only difference is that step S2676 is omitted, that is, the data of each card is not transmitted, and only the total data of all cards is transmitted (step S2686).
On the other hand, in response to this, only the total data (same as the lower half of the all card details display screen in FIG. 175) is displayed on the screen of the CRT display device 411.

FIG. 148 shows the interrupted card data display processing for displaying the data of the interrupted card and the number of the interrupted pachinko machine. FIG. 176 shows the procedure of the interrupted card data display processing on the CRT display device 411. 4 shows a configuration example of a suspended card data display screen.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413
The display menu selection screen as shown in FIG. 167 is displayed on the RT display device 411 (step S1311).

When the operator selects the interrupt card display using the numeric keypad while looking at this screen, the local processing device 413 transmits an interrupt card display data request command to the central processing unit CPU (step S1312).
Upon receiving this command, the central processing unit CPU sequentially reads the pachinko machine file and checks whether the card status in the file is "interrupted" (step S2).
691, S2692).

[0684] Here, when the card status is "suspended", the time read from the i-th log data column of the card (interruption occurrence time) is compared with the current time of the timer to determine the elapsed time. (Difference) (Step S
2693). Then, the elapsed time, the card number and the card data, the amount of money, the number of balls, the terminal number, and the interruption time in the log data column are transmitted to the local processing device 413 (step S2694). Then, the local processing device 413 displays the data of each card for one line as shown in FIG. 176 (step S1313). Further, when the data extraction of the interrupted cards has been completed for all the cards in the file, the central processing unit CPU transmits a display data end command, and when the local processing unit 413 receives this, it waits for a key input (step S2695,
S2696, S1314).

In the management device 400 of this embodiment,
For the pachinko machine in which the interruption elapsed time of the pachinko machine being interrupted is too long by displaying the interrupted card data, a "forced termination request" packet is sent from the management device 400, and then the "forced termination cancellation" is sent. By transmitting the packet, the suspended state can be released and the state can be shifted to the free state. As a result, it is possible to avoid a situation in which one player uses a plurality of cards and occupy a plurality of pachinko machines, and release all the pachinko machines to many players, thereby achieving fairness of the game. Moreover, since the data of the suspended card is stored in the card file in the system of this embodiment, even if the suspended pachinko machine is released to another player, the profit of the player may be lost at all. Absent.

In the above embodiment, the elapsed time of the pachinko machine being interrupted is displayed on the interrupted card data display screen, but the operation information in the pachinko machine file is "interrupted". It is also possible to prepare a suspended table display process and screen to display the data of the object, read the suspension time from the card file using the card number in the suspended pachinko machine file, calculate the elapsed time, and display it It is.

[0687] Although not shown, in the above-described embodiment, if there is too much data to be displayed on one screen as in the all-unit display screen in FIG.
When 26 is turned on, the display character string is scrolled upward by 10 lines.

FIG. 149 is more specific to the random number generation processing S2012 in the initialization flow of FIG. 105 and the card number calculation processing S2151 in the flow of FIG. 113 for calculating the card number using the random numbers obtained thereby. Procedures are shown in succession.

In the generation of random numbers, first, a random number A of 0 or more and 10000 or less is generated. Specifically, for example, “month”, “day”, and “1” of “current time (1/100 second unit)”
With the "number of the last digit" is set as the random number 1 (step S2701).

Next, the program language FORTRAN
Using the random number generation instruction RND (n), which is one of the instructions, the random number 1 generated in step S1 is added to (n), and
Generate a random number (7 digits or more) with a decimal point of ~ 1,
It is multiplied by 10 to obtain a random number 2 (step S27).
02).

Then, the FORTRAN instruction I
The fractional part of the random number 2 is rounded down using NT (n) (step S2703).

Then, in step S2704, whether the random number A satisfies the condition of 0 ≦ A ≦ 10000,
That is, it is checked whether A is larger than 0 and smaller than 10000. If A <0 or A> 10000, step S1 is executed.
And repeat the generation of the random number A. Then, in step S2705, 10000 is added to the random number A satisfying the above condition. Thereby, the random number A becomes any one number between 10,000 and 20,000. So, next, FORTR
Using the instruction MOD of the AN, the remainder obtained by dividing the random number A by the integer “5” is obtained and set as the random number B (step S270).
6). Therefore, the random number B is any one of 0, 1, 2, 3, and 4.

Subsequently, during the card purchase packet reception flow, the card issuance serial number n is set to step S2705.
Is added, and the addition result X is set as a primary card number (step S2707). However, the issuance serial number n given here is a number from 1 to 12767, and it is assumed that cards are not issued such that the number of issued cards exceeds 12767. As a result, the primary card number X becomes a number between 10001 and 32767. The reason why the upper limit of X is 32767 is that 32767 is 2
This is because the largest number that can be represented by 15 bits in the binary system, and in a later-described gaming system that handles 16-bit data, a code in which the most significant bit is set to “1” is replaced with a special card different from a normal gaming card ( Test card)
It is to reserve for.

[0694] However, in the next step S2708,
Primary card number X obtained in step S2707
Then, by using a bit manipulation instruction or the like, the first to fifteenth bits excluding the most significant bit are replaced, and code conversion is performed.

Here, as a bit replacement rule, five types of conversion patterns are prepared in advance in accordance with the random number B, and the conversion pattern according to the random number B is executed to replace bits.

[0696] In the case of 15 bits, there are (15! -1) possible bit replacement patterns. Of these, any five of them can be selected to create a program for performing such bit replacement. As the number of bit replacements increases, the execution time increases, but the conversion pattern becomes difficult to predict. Therefore, it is preferable to select a pattern in which all 15 bits are replaced.

[Table 33] shows an example of the bit replacement pattern corresponding to the random number B.

[0698]

[Table 33] Next, the actual conversion of the card number using the above-mentioned bit replacement pattern will be described by taking as an example a case where the random number A is 14297, the random number B is 2, and the serial number n is 635. In this case, the primary card number X becomes “1493” from X = A + n.
2 ". If this is expressed in hexadecimal, "3A54"
When expressed in a binary number, "001111000101
0100 ". This primary card number is represented by a random number B = 2
Is converted as shown in the following [Table 34], and the secondary card number is "1E13" in hexadecimal notation and "7699" in decimal notation.

[0699]

[Table 34] On the other hand, the process of calculating the card issue serial number from the card number performed in the flow of FIGS. 113 and 114 to 120 (steps S2151, S2161, S218)
1, S2201, S2221, S2241, S226
1, S2281) and the like are described in step S27.
07 and S2708. First, the card number is converted into a binary number, and then each bit is inversely converted with a conversion pattern (see [Table 34]) determined by a random number B to obtain X. The issue serial number can be obtained by subtracting the random number A.

Next, the pachinko machine 100 and the issuing machine 20
0 and each unit controller 180, 2 of the settlement machine 300
Common control procedures related to data transmission in 80 and 350 will be described with reference to FIGS.

[0707] Each controller 1
When a reset pulse is supplied to 90 (or 290, 390), 551, 553, each controller clears the internal register and internal RAM, and the data transmission controller 551 causes the unit controller 19
Also, the unit memory 550 for parallel communication between 0 and 0 is cleared (steps S101, S201, S30).
1). Then, the data transmission controller 551 writes appropriate data to a predetermined address (27FF) in the unit memory 550 (step S202). Then, the unit memory 550 stores the signal INT output from the predetermined terminal.
Start up the level. This signal INT is used as an initialization signal as described above as a unit controller 19.
0 (290, 390).

[0720] On the other hand, the unit controller 190 (29
0, 390) clears the I / O port after clearing the internal register and RAM (step S102), and initializes the initialization signal IN from the unit memory 550.
It is monitored whether T has started (step S10).
3), when the signal INT rises, the unit number setting unit 171
After reading the value set in (205, 352), the terminal serial number and the channel number are calculated from the machine number (steps S104, S105). Then, the channel number is written in the transmission data area SDA of the unit memory 550 (step S106).

The data transmission controller 551 reads the channel number in the transmission data area SDA and judges whether or not it is "0" (steps S203 and S203).
204), if the value is not "0" due to the writing by the unit controller, the read channel number is written to the latch LT3 (563), and then the latch LT2 (56
For 2), a command for designating the page configuration in the packet memory used for data transmission / reception is written (steps S205, S206). Then, the network controller 553 reads the channel number in the latch LT3, stores it in the internal RAM, determines its own address in the low-layer network (step S302), and reads the page configuration of the packet memory from the next latch LT2. It is stored (step S303). Thereby, the configuration of the transmission / reception page is determined.

Subsequently, the data transmission controller 551
Latches the page number used for the next data reception LT
2 (step S207). Then, this becomes a reception permission command to the network controller 553. Therefore, the network controller uses the latch LT
It is checked whether or not there is a reception page number in 2 and if there is a page number, it is determined that the reception has been permitted, and the process proceeds to the transmission processing of step S305 (FIG. 179) and subsequent steps (step S304). In step S305, the network controller 553 determines whether there is a transmission request from the NAU 530. Then, when there is a transmission request, after transmitting to the NAU 530 that reception is possible, a packet transmitted from the NAU 530 is received, and unnecessary portions such as a source address are removed by the received packet, The data section is converted to parallel data, and the received data is written to a specified page in the packet memory 552 (steps S306 to S308). Thereafter, the network controller 553 writes the received command into the latch LT1 (561) (step S30).
9).

Then, the data transmission controller 551 reads the data in the latch LT1 to confirm that there is a reception command, reads the reception data from a predetermined page of the packet memory 552, and temporarily stores it in the working area of the unit memory 550. (Steps S208, S2
09). Then, the data transmission controller 551 writes the next received page into the latch LT2. This is a command for permitting reception of the next packet (step S21).
0). This command (received page) is read and stored by the network controller 553 (step S
310), the next data can be received in parallel with the transmission of the received data from the data transmission controller 551 to the unit controller 190 (290, 390).

[0706] That is, the data transmission controller 551
Has written the received page into the latch LT2 in step S210, checks the command register CR2 in the unit memory 550 to confirm that it is "0", that is, there is no other transmission request to the unit controller 190 (290, 390). After that (step S211), the write position in the reception data area is determined from the reception packet type, and the reception data in the working area is moved to the reception data area of the unit memory 550 (step S2).
12, S213). Then, the received packet type name is written in the command register CR2 of the communication area (step S214).

Then, the unit controller 190 (2
90, 390) monitor the command register CR2 and determine that the packet type has been written, start processing corresponding to the packet type (step S1).
07, S108). Then, when the processing is completed, the command register CR2 is cleared (step S10).
9). On the other hand, after writing the received packet type name in the command register CR2 in step S214, the data transmission controller 551 sets the packet to “initial value setting”.
It is determined whether or not the packet is a packet. If the packet is an “initial value setting” packet, transmission of scheduled data is started.
Set the regular timer (1 second) within 0 (step S2)
15, S216). If the received packet is not the "initial value setting" packet, it is determined in step S217 whether the packet is a "line test" packet. If the packet is a "line test" packet, in step S218, a process is executed to transmit the "ACK" packet as a response. If the packet is not a "line test" packet, the process directly proceeds to another process.

Next, the packet transmission processing will be described with reference to FIG.

The unit controller 190 (290, 3
In step 90), when a packet transmission factor such as "card-in" or "interruption switch" occurs, the packet type name is first written in the "packet type" column in the transmission data area of the unit memory 550. That is, a packet head is created (step S121). Then, the command register CR1 in the unit memory 550 is checked to determine whether another transmission packet has already been entered. If there is no other transmission packet, a packet type name to be transmitted is written in the command register CR1. , A transmission timer is set (steps S122 to S124). Writing the packet type name to the command register CR1 becomes a transmission command to the data transmission controller 551. on the other hand,
The data transmission controller 551 has a command register C
It is monitored whether a packet type is included in R1 (step S221). When it is determined that the packet type is included, the transmission data corresponding to the transmission packet type is read from the transmission data area in the unit memory 550, and the transmission destination is determined. Is written to page 0 in the packet memory together with the address (fixed) of NAU 530 and the number of bytes of transmission data (steps S222 and S223).

[0710] Thereafter, the data transmission controller 551
Writes the transmission command of the data in page 0 into the latch LT2 (step S224).

Then, this becomes a transmission command to the network controller 553, and the network controller 553 checks for the presence or absence of a transmission command. If there is a command, the network controller 553 waits for acquisition of a transmission right on the network. Wait for transmission permission (steps S321 to S323). Then, after transmitting the data in the page 1 of the packet memory, the transmission result is written into the latch LT1 (steps S324 and S32).
5). In response to this, the data transmission controller 551 checks the latch LT1 to determine whether or not the transmission has succeeded. If the transmission has failed, the data transmission controller 551 repeats the transmission process up to three times (steps S225 and S226).

[0712] Then, the transmission result is stored in the unit memory 55.
After writing to the status register STR in the communication area of 0, the command register CR1 is cleared (steps S227 and S228).

[0713] On the other hand, the unit controller 190 (29
(0, 390), after setting the transmission timer in step S124, the command register CR1 is continuously monitored (step S125), and the time is over until the data transmission controller 551 clears the command register CR1 in step S228. Occurs, the common signal (watchdog pulse) of the display data sent to the pachinko machine control device 195 is fixed at a low level, and the watchdog pulse is stopped (step S127). As a result, the reset is performed by the reset circuit 555, and steps S101, S201,
Initialization of 301 is performed.

Next, the scheduled data transmission processing will be described with reference to FIG.
1 will be described. Data transmission controller 551
Checks the regular timer set in step S216 (step S231). When one second has elapsed, the process proceeds to step S232, in which all data in the transmission data area of the unit memory 550 is read and written into the working area (step S233). ). Then, the data is compared again with the data in the transmission data area (step S23).
4) If they match, look at the command register CR1 to see if another transmission request (packet type) to the data transmission controller has been entered (step S23).
5) Read data from the working area and write it as transmission data in the packet memory 552 (steps S237, S238). At this time, the destination address (NAU), the length (number of bytes) of the transmission data, and the packet type name are written in the page 1 in the packet memory together with the transmission data. If another packet name is included in the command register CR1 in step S235, the packet is transmitted (S236), and the process proceeds to step S237.

[0715] The data match is determined in step S234 because the unit controller 190 rewrites one byte of the 2-byte data portion with respect to the transmission data area and transmits the regular data. This is because determined data will be transmitted. By confirming the coincidence of the data, it is possible to determine the determination of the data in the transmission data area.

Writing of transmission data (step S238)
Thereafter, the data transmission controller 551 writes a transmission command of the data in the page 1 to the latch LT2 (step S2).
239).

Then, this becomes a transmission command to the network controller 553, and the network controller 553 checks for the presence or absence of a transmission command. If there is a command, the network controller 553 waits for acquisition of a transmission right on the network. Wait for transmission permission (steps S331 to S333). Then, after transmitting the data in the page 1 of the packet memory, the transmission result is written into the latch LT1 (steps S334, S33).
5). In response to this, the data transmission controller 551 checks the latch LT1 to determine whether transmission has succeeded. If the transmission has failed, the data transmission controller 551 repeats the transmission process up to three times (steps S240 and S241).

Next, the operation state of the pachinko machine reflected in the operation information in the transmission operation data shown in [Table 1], the transition method thereof, and the control of the pachinko machine using this operation state and the card state The method will be described.

In the system of this embodiment, the operating state of the pachinko machine is set to the reset state S as shown in FIG.
S10, a forced termination state SS11 in which a game cannot be performed, a free state SS12 opened to all players, and a gaming state SS13 in which a specific player is playing a game.
There are six states, namely, an interrupted state SS14 in which the game is stopped while the game right is reserved for a specific player, and a stopped state SS15 in which a predetermined number of prize balls are discharged and the game is stopped. Of these, the free state SS12 and the suspended state SS14
Only the card can be accepted, the reset state SS10, the forced termination state SS11, and the stopped state S
S15 is a state where the card cannot be accepted. In the suspension state SS14, only the card that caused the suspension is accepted. On the other hand, in the gaming state SS13, a specific card is held inside the pachinko machine.

[0720] In each of the above-mentioned states, transition in the direction indicated by the arrow in the figure is possible, and no other state transition occurs.

[0721] That is, the reset state SS10 is in the forced termination state SS1 only when an "initial value" packet is received.
Move to 1. However, when a “unit recovery” packet is received in the reset state after the recovery from the power failure, the pachinko machine returns to the state before the power failure occurred. Forced end state S
From S11, it is possible to shift only to the free state SS12, which shifts when a “store opening” packet or a “forced termination release” packet is received. In addition, free state SS12
Can be shifted to the gaming state SS13 or the forced ending state SS11, the processing shifts to the gaming state SS13 upon reception of the “card-in” packet, and shifts to the forced ending state SS11 upon receiving the “closed” packet or the “forced ending” packet. .

In the gaming state SS13, when the end switch is turned on or the return-to-zero state occurs, the free state S13 is set.
Returning to S12, if the interruption switch is turned on during the game, the operation proceeds to the interruption state SS14, and if the stopping condition is satisfied, the stopping state S
The process moves to S15. The state shifts from the interruption state SS14 or the cancellation state SS15 to the free state SS12 when the “interruption end” packet (when the settlement is performed by the settlement machine) or the “stop cancellation” packet is received, and the interruption state SS
When the card that caused the interruption in 14 is reinserted, the process returns to the gaming state SS13.

Further, in the free state SS12, in all of the gaming state SS13, the interrupted state SS14, and the hit state SS15, upon receiving the "forced termination request" packet from the management device 400, the forced termination state SS1 is set.
Move to 1.

Further, in the system of this embodiment, a test mode for enabling a game with a test card is prepared. In this mode, when the power of the entire system is turned on and online, a state transition almost similar to that in FIG. 182 is performed. Do. FIG. 183 (B) shows a state transition diagram of the pachinko machine in the online test mode. In this case, the condition of the state transition is slightly different from that in the normal operation mode.

[0725] That is, the free state S in the normal operation mode
When the regular test card is inserted after the test switch is pressed in S12, the control space is switched, and the state of the pachinko machine shifts to the game state SS13 'in the test mode. Even in the test mode, it is possible to shift to the stop state or the interruption state. However, it is possible to shift from the game state SS13 'to the free state SS12 when the end switch is turned on or when a return to zero occurs, and a "cancel release" packet is sent from the stop state SS15' to the free state SS12 '. When the end switch is turned on, instead of receiving, the game returns to the test game state SS13 'when the original test card or another test card is inserted in the interruption state SS14', and when the end switch is pressed in the interruption state SS14 ', Move to the normal free state SS12. The control space is switched at the same time as the transition from each state in the test mode to the free state SS12. In other words, the test mode is not the test mode, but the normal operation mode. When the player wants to play the game again with the test card, it is necessary to turn on the test switch again and then insert the test card. On the other hand, when a “forced termination request” packet is sent from the management device 400 in each state of the test mode, this is sent to the unit control device 18.
0 is stored and when the end switch is turned on,
The state SS13 ', SS14', SS15 'is shifted to the forced termination state SS11.

Note that the transition to the forced termination state SS11 is also performed at the same time as the switching of the control space, and the test mode ends.

FIG. 183 (C) shows a state transition in the test mode when one of the pachinko machines is powered on independently and disconnected from the management device 400.

[0728] Pachinko machine 100 when offline
Performs initialization upon power-on, and then enters a standby state SS20 for turning on a test switch or waiting for a "line test" packet from the management device. Here, when the test switch is turned on and a regular test card is subsequently inserted, a transition is made to the gaming state SS13 'in the test mode. Thereafter, the interruption state SS1 is performed under the same conditions as in FIG. 183 (B).
4 ', the state shifts to the stop state SS15', and when the end switch is turned on in each state, the state returns to the standby state SS20.

When the "line test" and "initial value setting" packets are received in the standby state SS20, the flow shifts to the forced termination state SS11 in the normal operation mode.

[0731] The unit control device 180 of the control unit 160 of the pachinko machine 100 according to this embodiment communicates with the control and management device 400 of the pachinko machine 100 and the card reader 800 while referring to the operating state and the card state of the pachinko machine 100. Communication, the burden on the management device 400 can be reduced, and malfunctions due to communication errors can be avoided, while maintaining control independence with respect to predetermined processing, and prompt responses to player actions and the like can be made. It has become.

[0731] The processing in the unit controller 190 using the pachinko machine operation information and the card status will be described below.

First, before describing the processing by the unit controller 190, the unit controller 190, the pachinko machine controller 195 and the card reader controller 18
8 will be described with reference to FIGS. 184 to 223.

FIG. 184 shows the procedure from initialization to opening of a store.

[0734] Communication between the card reader control device 188 and the unit controller 190 is performed by a function code.
The "initial value setting" function for providing the card reader 800 with a date code and an identification code for collating with the magnetic data read from the card CD,
A "card accepted" function for permitting acceptance of the card CD, a "card unacceptable" function for instructing the card reader 800 to stop accepting the card CD, and a command to eject the card CD. "Card ejection" function, "Reload" function for instructing rereading of the magnetic data of the card CD, "Resending request" function for requesting resending of the function code sent immediately before, the card held in the card reader controller 188. Reader 800
A "status request" function for requesting transmission of a bit indicating the status of the card and an instruction to punch a return hole PH4 indicating that the card ball and the amount of money have become zero at a predetermined position in the punch hole forming area. Eight kinds of commands of the “return to zero” function are prepared.

[0735] On the other hand, the function code from the card reader control device 188 to the unit controller 190 includes a "card number transmission" function for transmitting the card number read by the card reader 800 to the unit controller 190, and a unit code indicating that the test card has been inserted. A "test card" function for notifying the controller 190, an "initial value request" function for requesting initial values such as date and identification code at reset,
A "normal end" function that notifies the unit controller 190 that the requested processing has been completed normally, and an "abnormal termination" function that indicates that the processing has not been completed normally, and that the inserted card is illegal. "Self-discharge" function for notifying that the card reader controller 188 has detected the card by its own will, a "retransmission request" function for requesting the unit controller 190 to retransmit the function code sent immediately before, and a "retransmission request" function. There are eight types of “status transmission” functions for transmitting the status of the card reader in response to a “reload” request or “status request”.

However, the communication between the card reader control device 188 and the unit controller 190 does not send the function code unilaterally, but first, the transmitting side sends a call signal (calling code) ENQ, and the receiving side permits it. After receiving the response ACK, the function code is sent.

In FIG. 184, when a reset is entered by power-on, the unit controller 190, card reader controller CPU2, pachinko machine controller C
PU1 initializes internal registers and the like (step S1).
401, S501, S601). When initialization is completed,
The pachinko machine controller CPU1 waits for input of a detection signal from each sensor or switch (S410).

[0738] The unit controller 190 reads the set value from the unit number setting unit 171 to calculate the serial number and the channel number, and stores them in the unit memory 550 (step S602). Then, from the management device, "line test"
Wait for a packet to be sent (step S60)
3).

Next, upon receiving an “initial value setting” packet, reception control from the card reader 800 is started, and a call signal ENQ from the card reader controller CPU 2 is received.
Is determined (steps S604 to S606).

[0740] On the other hand, the card reader controller CPU2
When the initialization is completed, the unit controller 190
Sends a call signal ENQ and waits for a response signal ACK in response to the call signal (steps S502 and S503). If there is no ACK in consideration of a case where the unit controller 190 transmits a call such as an “initial value setting” function before transmitting the call signal ENQ, it is determined whether or not there is an ENQ (step S504). . Then, if there is an ENQ, an ACK is transmitted to wait for reception of a function code (steps S504 to S50).
6).

When the unit controller 190 receives the transmission of the call signal ENQ from the card reader controller CPU 2 in step S502 in step S606, it returns a response signal ACK (step S60).
7). Then, the card reader controller CPU2 transmits an "initialization request" function (Step S).
511). This is received by the unit controller 190 and transmission control to the card reader 800 is started, and first, an “initial value setting” function including an identification code is transmitted (steps S608 to S610).

[0742] Upon receiving this initial value, the card reader controller CPU2 stores the date and the identification code in the internal RAM.
And returns a "normal end" function (steps S512 to S514).

[0739] The unit controller 190 receives the "normal end" function (step S611).
Waits for a “store opening code” packet from the management device 400, and upon receiving the “opening code” packet, scrolls the analog display 163 to display a wait for customer and displays the unit memory 5
50 is changed to "free" (step S6).
12 to S614). Then unit controller 19
0 transmits a "card accepted" function to the card reader controller CPU2 (step S61).
5).

[0744] When the card reader controller CPU2 receives this, the shutter is first opened, and then card insertion detection is started (steps S515 to S517). Then, the "normal end" function is returned (step S5).
18), and waits for insertion of a function or card from the unit controller 190 (step S)
520). On the other hand, when the unit controller 190 receives the “normal end” function from the card reader 800, it waits for a packet from the management device 400 or a function from the card reader controller CPU2 (step S620).

FIG. 185 shows an operation procedure when a card CD is inserted into the card reader 800.

[0746] Card reader controller CPU2 waits for function or card (step S520)
In step S521, when the card CD is inserted, this is detected by the insertion detection switch 808, and the motor is driven to take in the card CD (step S521). next,
After checking the punch hole and the security code, the magnetic data is read, and the date and the identification code are inspected (steps S522 to S525). If the card is a normal card, the function including the read card number is transmitted to the unit controller 190, and then the shutter is closed (steps S526 and S527).

[0747] When the unit controller 190 receives the card number, it sends a "card-in" packet to the management device 40.
0, the presence of the card is confirmed by an "ACK" packet, and the operation information is changed to "playing" (step S).
621-S625). Then, the status display lamp 162
Is turned on to inform the outside that the game is being played, the hit ball launching device 103 is made drivable, and input of a detection signal from each sensor is waited (steps S624 and S625).

During this time, the pachinko machine controller CPU 1
Are in a state of waiting for detection signals of sensors and switches (step S410), and after the launch control of the hit ball launching device 103 is started, the launch sensor SNS5, the safe sensors SNS2, SN
S3, foul sensor SNS4, out sensor SNS1
When the detection signal is detected, the unit controller 190 is notified of the detection signal (steps S411 to S41).
6). In addition, at this time, the return ball and the launch ball are distinguished from each other based on the difference in the detection time of the launch sensor SNS5, and the number of returns is output as a foul ball detection signal (step S41).
6). On the other hand, when the unit controller 190 receives the detection signal of the sensor, the unit controller 190 performs an operation according to the type of the signal, obtains the number of balls being played, updates the unit memory 550 (steps S626 to S630), and sets the purchase switch 1
Upon receiving the detection signal of No. 13, an operation of reducing the unused amount of the card and increasing the number of balls is performed (step S631).

FIG. 186 shows that the interrupt switch 11
4 shows an operation procedure when 4 is turned on.

[0750] When the unit controller 190 detects that the interruption switch is turned on, the unit controller 190 stops the control of the hit ball firing device 103, and sends the "interruption switch" to the management device 400.
The packet is transmitted (steps S632 to S634).
Then, when “ACK” is returned from the management device 400, the operation information in the unit memory 550 is changed to “interrupted”, the game state display lamp 123 is driven to blink, and the interruption display is performed. The "card ejection" function is transmitted to the card reader controller CPU2 (steps S635 to S637).

When the card reader controller CPU2 receives this function, the shutter is opened, the motor is reversed, the card is ejected, and a "normal end" function is sent to the unit controller 190 (steps S528 to S531), and the card is inserted or The function waits (step S532). On the other hand, after receiving the “normal end” function (step S638), unit controller 190 waits for reception of a packet or function (step S620).

Then, the interrupted card is transferred to the card reader 8
00, the card reader controller CPU
In step S2, the card is taken in, checked and transmitted, and the shutter is closed according to the same procedure as steps S521 to S527.
538). On the other hand, the unit controller 190 compares the received card number with the card number in the unit memory 550 to check whether or not the card has been interrupted, and if they match, transmits an “interrupted card-in” packet to the management device 400. (Steps S639 to S641). Then, when the response "ACK" is received, the operation state is changed to "playing", the game state display lamp is changed to the continuously lit game display, and the control of the hit ball launching device 103 is started (steps S642 to S644). ).

By the way, in the pachinko gaming facility of this embodiment, when the suspended card is settled by the settlement machine 300, the suspended pachinko machine is released. Therefore, when a packet of step S620 in FIG. 186 or an “interruption end” packet is sent from the management device in the function reception waiting state, the unit controller 190
Changes the operation information to “free” and changes the lamps 123 and 16
3 is changed to the customer wait display, and then the packet or function reception wait is resumed (step S620).

FIG. 187 shows an operation procedure when the end switch 115 is turned on.

[0755] When the unit controller 190 detects that the end switch is turned on, the unit controller 190 stops driving the hit ball launching device 103, and then sends a "end switch" packet to the management device 4.
00 (steps S645 to S647). And
When the response “ACK” is received, the operation information is “free”.
, The game state display lamp 123 is turned off, the analog display 163 is scrolled to change to the customer waiting display, and then the "card ejection" function is sent to the card reader controller CPU2 (steps S648 to S65).
0).

[0756] Upon receiving the function, the card reader controller CPU2 opens the shutter, drives the motor to eject the card, and returns a "normal end" function to the unit controller 190 (steps S539 to S542). Then, it waits for card insertion or function reception (step S520).

[0757] On the other hand, upon receiving the "normal end" function from the card reader controller CPU2, the unit controller 190 waits for a packet from the management device 400 or a function from the card reader controller CPU2 (steps S651, S62).
0). During this time, the pachinko machine controller CPU1 is waiting for the input of the detection signal of the sensor (step S41).
0).

[0758] Next, the procedure in the case where a return-to-zero state in which both the number of balls held and the amount of money become "0" during the game of Fig. 185 will be described with reference to Fig. 188.

[0759] As a result of the calculation of the number of balls in steps S626 to S631, it is determined whether or not the number of balls and the amount of money have become "0".
If “0”, the drive control of the hitting ball launching device 103 is stopped, and then the search timer for 10 seconds is turned on (step S
652-S654). Then, it is checked whether or not the number of floating balls (the number of launched balls−the number of collected balls) existing in the game board has become “0”, and it is further determined whether or not the search timer has passed 10 seconds (steps S655 and S656). If the number of floating balls becomes “0” or the search timer has passed 10 seconds, a “return-to-zero” packet is transmitted to the management device 400 (step S658).

If the number of floating balls exists within 10 seconds after stopping the launching device, it is checked whether there is a safe ball, foul ball, or out ball.
Returning to step 31, the number of balls is calculated again (step S657).

[0741] Then, "ACK" from the management device 400 is received.
When the packet is received, the operation information is changed to "free", and then the lamps 123 and 163 are changed to the customer waiting display.
"Return to zero" function to card reader controller C
The data is transmitted to PU2 (steps S659 to S662).

[0764] When the card reader controller CPU2 receives this function, it punches a punch hole at the return-to-zero hole punching position of the card, opens the shutter, and ejects the card (steps S543 to S546). Then, the “normal end” function is executed by the unit controller 190.
To wait for card insertion or function reception (steps S547 and S520).

[0764] On the other hand, the unit controller 190
When the "normal end" function is received, a packet or function wait state is set (step S66).
3, S620).

FIG. 189 shows a processing procedure when a hit state occurs during the game of FIG. 185.

After calculating the number of balls and the amount of money in steps S626 to S631, a hit calculation is performed, and it is determined whether or not the calculated value has reached the hit number (steps S664 and S665). When the number of hits has been reached, the drive control of the hit ball launching device 103 is stopped, and then a “hit” packet is transmitted to the management device 400 (steps S666 and S667).

[0766] Then, "ACK" from the management device 400 is received.
When a packet is received, the operation information is changed to "stop",
The game state display lamp 123 is turned off, and the analog display 16
3 is changed to a stop display (blinking drive) (step S66)
8-S670). After that, the tap sound is output from the speaker 166, and then the card reader controller CPU2 is turned off.
Then, a "card cannot be accepted" function is transmitted to the user (steps S671, S672).

When the card reader controller CPU2 receives this function, it opens the shutter and ejects the card, and then closes the shutter to prohibit card insertion. Then, a "normal end" function is transmitted to the unit controller 190, and the function waits for function reception (steps S551 to S556). Then, the unit controller 190 receives the “normal end” function and enters a packet waiting state (steps S673 and S674).

[0768] After that, "cancel release" is sent from the management device 400.
When a packet is sent, the unit controller 19
0 changes the operation information to “free”, and the lamps 123, 1
63 is changed to the customer waiting display, and then a "card accepted" function is transmitted to the card reader controller CPUK2 (steps S675 to S678).

Then, the card reader controller CPU
2. After opening the shutter to start card insertion detection and transmitting a "normal end" function (step S5)
57 to S560), and waits for insertion of a function or a card (step S520). On the other hand, the unit controller 190 receives the “normal end” function (step S679), and waits for reception of a packet or function (step S620). During this time, the pachinko machine controller CPU1 is in a state of waiting for input of a detection signal of each sensor and switch (step S410).

FIG. 190 shows a processing procedure at the time of forced termination. 184, 187, 188, 18
When the “forced end” packet is sent from the management apparatus 400 in the packet No. 9 or the function reception waiting state (step S620), the unit controller 190
Changes the operation information to “forced end” and changes the lamp 123,
After turning off the light 163 and clearing the number of balls and the amount display to "0", a "card cannot be accepted" function is transmitted to the card reader controller CPU2 (step S6).
81-684).

Then, the card reader controller CPU
After receiving the function, it is determined whether or not a card is present in the card reader 800. If the card is present, the shutter is opened and the card is ejected. If there is no card, the process proceeds to step S565. After the shutter is closed, the "normal end" function is transmitted, and the function waits for function reception (steps S561 to S5).
67).

[0772] On the other hand, when the unit controller 190 receives the "normal end" function from the card reader controller CPU2, it waits for packet reception (steps S685, S686).

After that, when a “forced termination release” packet is sent from the management device 400, the unit controller 190 changes the operation information to “free” and the lamp 12
3, 163 is changed to the wait-for-customer display, and then a "card accepted" function is transmitted to the card reader controller CPU2 (steps S687 to S690).

Then, the card reader controller CPU
2. After opening the shutter to start card insertion detection and transmitting a "normal end" function (step S5)
68 to S571), and waits for insertion of a function or a card (step S520). On the other hand, the unit controller 190 receives the “normal end” function (step S691), and waits for reception of a packet or function (step S620). During this time, the pachinko machine controller CPU1 is in a state of waiting for input of a detection signal of each sensor and switch (step S410).

[0775] Fig. 191 shows the procedure of unit recovery processing after a power failure occurs.

When the power outage is restored, each controller C
The PU1, CPU2, and 190 respectively initialize internal registers and the like (steps S421, S581, and S70).
1) Then, the unit controller 190 reads the unit number from the unit number setting unit 171 to calculate the serial number and the channel number, store them in the unit memory 550, and waits for the reception of the "line test" packet (steps S702 and S70).
3).

On the other hand, after initialization, the pachinko machine controller CPU1 waits for input of a detection signal of a sensor or a switch (step S410), and the card reader controller CP
U2 is the step S5 at the time of the power-on reset in FIG. 184.
02 to S506, after transmitting the call signal ENQ, the signals ACK and E from the unit controller 190 are transmitted.
Judgment of NQ reception is performed, and ACK is received when ENQ is received.
And waits for function reception (steps S582-S586).

The unit controller 190 determines in step S
When the "line test" packet is received at 703, the "unit recovery data" packet sent from the management device 400 is subsequently received, the data in the unit memory 550 is returned to the state before the power failure occurred, and the "ACK" packet is received. Is returned (steps S704 and S705). then,
After the firing drive control is turned off irrespective of the state before the power failure, if the previous operating state is a game, the operation information is set to "free" (steps S706 and S707). next,
Since a "restart" packet is sent from the management device 400, if it is received, transmission / reception control with the card reader controller CPU2 is started, and a call signal ENQ is transmitted first (steps S708 to S71).
0). When a response signal ACK is received, an "initial value setting" function is sent to the card reader controller CPU2 (steps S711 and S71).
2).

[0779] The card reader controller CPU2
Upon receiving the "initial value setting" function, the date and the identification code are stored, and then the "normal end" function is returned. Upon receiving this, the unit controller 190
The lamps 123 and 163 are displayed according to the operation information (steps S713 and S714). That is, the original operating state returns to the original display state except for “in game”. Subsequently, the unit controller 190 transmits a function corresponding to the operation information (Step S715). In other words, if "Free", the "Reload" function of the card is used. If "Paused", the "Card accepted" function is used. Otherwise, "Card accepted" is not accepted.
Send the function.

Then, the card reader controller CPU
2 executes a process corresponding to the transmitted function, and then determines whether a card is present in the card reader 800. If no card is present, the "status"
Transmit the function (steps S590 to S59)
2). When a card is present in the card reader 800, after the card is authenticated in steps S522 to 525, the card number is inserted into the function and transmitted. Then, the function reception or card insertion in step S520 is performed. It goes into a waiting state.

[0783] On the other hand, when the unit controller 190 receives the "status" function from the card reader 800, it waits for a packet or a function corresponding to step S620, and when it receives a function including a card number, the "card in" corresponding to step S622. "After transmitting the packet to the management device 400, the game processing is started according to the procedure of steps S623 to S631 in FIG. 185.

As described above, when the operating state before the occurrence of the power failure is “in game”, the game is restarted after rereading and checking the card, so that erroneous data (especially in the event of power failure recovery) It is possible to avoid confusion due to transmission of the card number), to enhance reliability, and to eliminate fraudulent acts such as card removal during a power outage.

Next, a specific control procedure in the unit controller 190 will be described with reference to FIGS.

[0784] The processing in the unit controller 190 includes an initialization task after power-on or reset,
Subsequent 10 main tasks, a timer interrupt process based on an interrupt signal received from the timer every 1 millisecond, and a serial interrupt process that occurs when a function is transmitted to and received from the card reader control device 188. .

[0785] Of these, ten types of main tasks are repeatedly executed in real-time processing. Here, the ten types of main tasks are a packet reception task and a card reader control task, a packet transmission task, an error control task, a ball count calculation task, a switch detection task, a sound output task, a timer control task, a lamp drive task, and a port. There are ten types of output control tasks.

FIG. 192 shows the timer interrupt processing.
2 shows a procedure of a serial interrupt process.

In the timer interrupt processing of FIG. 192, first, the hot code (A55A) in the unit memory 550 is checked (procedure P1). The timer is reset (procedure P2).

Next, after the timer prepared in the internal RAM of the unit controller 190 is updated, "FFH" is set every transmission by the data transmission controller, and -1 is set every 20 mS. Check the dog counter (procedure P3, P
4). Here, if the watchdog counter is "0", it is determined that the data transmission controller has gone down, and the common signal for driving the segment type display is fixed and reset by the reset circuit 555 is applied.

If the watchdog counter is normal,
Next sensor and switch detection processing (see FIG. 194)
, And then executes a switch detection signal invalidating process (see FIG. 195) (procedures P5 and P6).

[0790] Thereafter, the amount data and the number-of-balls data are read out from the unit memory and code-converted.
The common data is formed and output, and the amount and the number of balls are dynamically displayed (procedures P7 and P8).

On the other hand, in the serial interrupt processing shown in FIG. 193, when an interrupt is received from a transmission buffer or a reception buffer inside the unit controller 190, it is first determined whether or not the reception is an interruption. Move data to internal RAM (procedures P11, P1
2). Further, when the serial interrupt is an interrupt from the transmission buffer, a one-byte transmission process of converting the one-byte transmission data into serial data by shifting the transmission buffer and outputting the serial data is executed (procedures P13 and P13).
14). Note that the serial interrupt is automatically activated when transmission / reception data enters the reception buffer or the transmission buffer.
An interrupt signal is input to U.

The sensor and switch detection processing during the timer interrupt processing (FIG. 192) is performed according to the procedure shown in FIG.

[0793] That is, first, the on / off states of the purchase switch 113, the interruption switch 114, the settlement switch 115, the test switch 179, and the call switch 165a are read and compared with the previous state (procedures P51 and P51).
52). In the comparison of the states, it is possible to easily know whether the state has changed by performing a logical operation such as an exclusive OR. Here, if there is a switch that is newly turned on, the on state of the switch is saved in the internal RAM (procedure P53).

Next, it is determined whether or not the sensor is being detected (procedure P54), that is, whether or not the game is being played. If the sensor is being detected, the firing sensor SNS5 and the safe sensor SN are detected.
The states of S2, SNS3, foul sensor SNS4, and out sensor SNS1 are read and compared with the previous states (procedures P55 and P56). If there is a sensor that is newly turned on, the on state of the sensor is set to the internal R
Save to AM (procedure P57).

Thereafter, it is determined whether or not the driving control of the hit ball launching device 103 is being performed.
Jump to step P57 if not controlled
Invalidates the ON state of the firing sensor saved in the RAM (procedures P58 and P59). Then, if the firing sensor is turned on after looking at the data saved in RAM,
The counter for counting the number of floating balls provided in the RAM is added (procedures P60 and P61). If the firing sensor is off, the process proceeds to the next procedure P62 without incrementing the number of floating balls and determines whether the number of floating balls is “0”. Here, if the number of floating balls is "0", the ON state of the first safe sensor SNS2 saved in the RAM is invalidated (procedure P76), and if it is not "0", it is checked whether the first safe sensor is ON and ON. Then subtract the number of floating balls (procedure P
63, P64), and if the first safe sensor is off, the process directly proceeds to the procedure P65, and it is determined again whether or not the number of floating balls is “0”.

[0796] If the number of floating balls is "0", the on-state of the second safe sensor SNS3 saved in the RAM is invalidated (procedure P77). If not, it is checked whether or not the second safe sensor is on. If it is on, the number of floating balls is subtracted (procedures P66 and P67), and if the second safe sensor is off, the process proceeds directly to procedure P68 to determine again whether the number of floating balls is "0". Here, if the number of floating balls is "0", the foul sensor SNS4 saved in the RAM.
Is invalidated (procedure P78). If it is not "0", it is checked whether or not the foul sensor is on. If it is on, the number of floating balls is subtracted (procedures P69 and P70). Proceeding directly to procedure P71, it is determined again whether the number of floating balls is "0".

Here, if the number of floating balls is "0", the on state of the out sensor SNS1 saved in the RAM is invalidated (procedure P79). If not, it is checked whether the out sensor is on or not. After subtracting the number of floating balls (procedures P72 and P73), if the out sensor is off, proceed directly to procedure P74. If either of the safe sensors 1 or 2 is valid, reservation of hit sound output and lighting of the safe ball display lamp , And increments (+1) the on-times counter for the valid on-state sensor saved in the RAM (procedure P75).

After that, the switch invalidating process shown in FIG. 195 is executed. In this process, first, it is checked whether the operating state is "playing", and if "playing", the ON state of the test switch saved in the RAM is invalidated (procedures P81 and P82).
If the state is other than "playing", the ON state of the suspend switch 114 and the purchase switch 113 is invalidated (procedure P83), and then it is determined whether the card state is "return to zero". And end switch 1
Invalidates the ON state of the P15 (procedures P84, P8)
5).

As described above, in the control of the pachinko machine by the unit controller 190 of this embodiment, the concept of a floating ball is adopted, and a winning ball, an out ball,
Balls equal to the number of foul balls subtracted are considered to be present in the game board as floating balls, and if a winning prize ball or the like with the number of floating balls falling below “0” is detected, it is invalidated I am trying to do it. Thus, an erroneous detection signal due to noise or the like can be eliminated, and the calculation accuracy of the number of balls can be improved.

Next, the initialization task by the unit controller 190 and the ten kinds of main tasks to be processed in real time will be described.

FIG. 196 shows the initialization task.

When a reset signal is input from the reset circuit 555 at the time of power-on or the disappearance of the watchdog pulse, the unit controller 190 starts an initialization task, first clears the internal RAM, and writes a check code at a predetermined address. Is written, an initial value is set in an internal register, and an I / O port is set to a predetermined initial state (procedures P91 to P93). Then, after setting a plurality of reference timers prepared in the RAM, the data transmission controller 551 waits for the rise of the initialization signal INT output by writing to the unit memory 550 (procedure P94, procedure P94).
P95).

[0813] Then, when the INT signal rises, the setting number of the unit number setting switch 171 is read, the serial number and the channel number are calculated, and they are written in the transmission data area of the unit memory 550. It waits for a "line test" packet to be sent (procedures P96 to P98) and checks the test switch 179. Then, when the “line test” packet is received, the “ACK” packet is
Returning to 0 returns to the main task, and if the test switch is turned on before the reception of the "line test" packet, the test mode flag is set and the process moves to the main task.

FIG. 197 shows the unit controller 19
The processing procedure of the “packet receiving task” among the ten types of main tasks “0” is shown.

In this task, first, the unit memory 550 is checked to determine whether or not a packet has been sent from the management device 400.
A check is made to see if a K "packet is waiting to be returned (procedures P101 and P102). If no (No), the procedure returns to procedure P101 to repeat the above procedure, and returns to procedure P10.
When an "ACK" packet is waited for in step 2, procedure P103
To step P in the packet transmission task in FIG.
The timer for waiting for ACK set in 157 is read.
Next, it is checked whether or not the timer has timed out. If the timer has timed out, an ACK reception error flag in the internal RAM is set (procedure P10).
4, P105). This flag is referred to in an error control task (FIG. 223) described later.

[0806] On the other hand, if it is determined in step P101 that there is a received packet, the type name of the received packet is read from the unit memory into the internal RAM, and is read as "NA".
First, it is determined whether the packet is a K ″ packet (procedures P106 and P106).
107). If it is "NAK", the NAK flag prepared in the RAM is set (procedure P108), and if it is not "NAK", the process directly proceeds to procedure P109 to determine whether the received packet is registered. I do. If it is an unregistered packet, the packet type name in the command register CR2 of the unit memory is cleared to "0" in procedure P110, and the procedure returns to procedure P101.
It is determined that no packet has been received by clearing the command register CR2.

If it is determined in step P109 that the received packet has been registered, the procedures P111 to P125
Then, it determines which packet it is, and executes a process (FIGS. 198 to 211) corresponding to the type of the found packet.

[0808] Fig. 198 shows the procedure of the "initial value setting" packet receiving process in the packet receiving task.

[0809] Upon receiving the "initial value setting" packet, unit controller 190 copies the hot code to the transmission data area in the corresponding column in the reception data area of unit memory 550 (procedures P301 and P302). . By writing the head portion of the transmitted packet in the reception data area and the transmission data area, the creation of a packet head in the transmission data area by the unit controller 190 can be simplified. Next, the "initial value not set" bit in the monitor information 1 is checked to determine whether or not the initial value has been received (procedure P303). If the initial value has been received, the procedure immediately proceeds to the procedure P306. Change the information to "forced termination" and disable transmission to the card reader,
Proceed to step P306 to proceed to card reader 800
To enable communication control (reception) with. The “initial value setting” packet is transmitted to the console 5 of the management device 400 after opening.
In some cases, the information may also be transmitted when the prize ball or the number of hits is changed in step 12, and in that case, it is not preferable to change the operation information. Then, by checking the flag of the internal RAM, it is checked whether or not the test mode is set (procedure P30).
7) If it is in the test mode, the process directly proceeds to the procedure P310. If it is in the normal operation mode, it is checked in the procedure P308 whether or not the initial value has been transmitted to the card reader by a flag. P30
9) Then, the process shifts to procedure P310, and transmission to the card reader is permitted. Then, after making a transmission reservation by writing an "initial value setting" function in a predetermined area (transmission buffer area) of the internal RAM, it is determined whether the initial value has been received again by checking the flag (procedures P311 and P312). ).

[0810] In the procedure P308, the card reader 80
If the "initial value setting" function to 0 has not been transmitted yet, the procedure jumps to the procedure P312 because the "initial value request" function from the card reader is received at the time of the initial initial value transmission. This is to send the value. When it is determined in the procedure P312 that the initial value packet has not been received, the process proceeds to the procedure P313, where the “initial value setting” bit of the monitor information 1 is cleared,
If it is determined that the initial value has been received, the procedure P312 to P312
The flow shifts to 314, makes a transmission reservation for the "initial value setting" function, and then returns to the original processing routine (FIG. 197).

FIG. 199 shows the procedure of the “opening code” packet receiving process in the packet receiving task.

[0812] When the unit controller 190 receives the "store opening code" packet, it first sets the operation information to "free".
After the setting is made, it is determined whether or not the mode is the test mode by looking at the flag (procedures P321 and P322). If it is in the test mode, the process returns to the original routine. If it is in the normal operation mode, the display by the lamps 123 and 163 is changed to the customer waiting state, and then the "card accepted" function is set to R.
After writing to the AM and making a transmission reservation, the card insertion lamp 168 is changed to blinking drive, and the process returns to the original routine (procedures P323, P324, and P325).

[0813] Fig. 200 shows the procedure of the "close code" packet reception process in the packet reception task.

[0814] When the unit controller 190 receives the "store closing code" packet, it first checks the operation information, and if the operation information is "playing" or "interrupted", returns directly to the original routine. The "close code" is normally sent after the "forced end" packet, so the "close code" should not be sent even if there is a pachinko machine being played or suspended. Thereby, it functions as a safety device when the store closing switch is turned on by mistake. If the operation information is not “playing” or “interruption”, the operation information is changed to “forced termination”, and the flag is checked to determine whether or not the operation is in the test mode (procedures P331 to P33).
3). If it is in the test mode, the process returns to the original routine. If it is in the normal operation mode, all lamps are turned off, a "card cannot be accepted" function is written in the RAM, transmission is reserved, and the process returns to the original routine (procedure P334). , P336).

[0815] After the operation information is changed to "forced termination" in procedure P332, the test mode is determined (P333).
Is performed to accept the “closed” packet during the online test mode operation and to immediately shift the pachinko machine to the forced termination state after the test mode ends.

FIG. 201 shows the procedure of the “forced end” packet receiving process in the packet receiving task of FIG. 197.

Upon receiving the "forced end" packet, unit controller 190 first clears the card text data in the transmission data area of unit memory 550, and then changes the operation information to "forced end" (procedure P3).
41, P342). Then, in the next procedure P343,
The "test mode" flag is checked, and if it is in the test mode, the process returns to the original routine as it is, so that it is possible to immediately shift to the forced termination state after the end of the test mode. On the other hand, in the normal operation mode, after stopping the detection of the sensor and the control of the hit ball launching device 103, all the lamps are turned off, and a “card cannot be accepted” function is sent to the card reader 800. Data for designating the type of sound is written, the output of the forced end sound is reserved, and the process returns to the original routine (FIG. 198) (procedure P
344-P348). As a result, the pachinko machine ejects the card during the game and becomes unplayable, and in other cases, does not accept the card.

FIG. 202 shows a processing procedure when a “forced termination release” packet is received.

[0820] Upon receiving the "forced termination release" packet, the unit controller 190 first checks the operation information to determine whether or not the forced termination is in progress. If not, the unit controller 190 returns to the original routine without doing anything (procedure P351). ). If the operation information is being forcibly terminated, change the operation information to "free",
The flag is checked to determine whether the mode is the test mode (procedures P352 and P353). Here, during the test mode, the routine returns to the original routine as it is, and the pachinko machine can be immediately shifted to the free state after the end of the test mode.

[0820] On the other hand, when the mode is not the test mode, the display of the lamp is changed to the customer waiting state, and then the transmission of the "card acceptable" function to the card reader is reserved.
The procedure returns to the original routine (FIG. 197) in which the card insertion lamp 168 is changed to the blinking state (procedures P354 to P35).
6).

[0821] Fig. 203 shows the procedure of the "cancel release" packet reception process.

This procedure is almost the same as the procedure for canceling forced termination in FIG. 202. The only difference is that after the operation information is set to "free" in the procedure P362, the stop operation register in the unit memory 550 is cleared and then the test mode is judged.

FIG. 204 shows the procedure of the "interruption end" packet receiving process.

This procedure is almost the same as the procedure for canceling the forced termination in FIG. 202. The difference is that after setting the operation information to “free” in the procedure P372, the card text data in the unit memory 550 is cleared and then the test mode is determined, and the card can be accepted even during suspension. Therefore, there is no need to make a transmission reservation for the “card accepted” function corresponding to the procedure P355.

FIG. 205 shows the procedure of the reception processing of the “unit recovery” packet in the packet reception task of FIG. 197.

[0827] Upon receiving this packet, unit controller 190 first copies the packet head of the reception data area to the transmission data area, and then clears the "initial value setting" bit of monitor information 1 (procedure P381, P381).
P382). The “unit recovery” packet is transmitted when an abnormality is detected in the periodic data collection or when the power failure is recovered. In the former case, the unit controller 19 is already transmitted.
This is because “0” indicates that the initial value is received and held, and that “unit recovery” packet is transmitted after transmission of “initial value setting” packet upon restoration of power failure.

[0827] After the bit of the monitor information 1 is cleared, the control of the hit ball launching device 103 and the detection of the sensor are stopped, and the transmission reservation of the packet or function generated before the abnormality is detected is canceled to transmit the packet or control the card reader. After clearing the flag related to the operation and stopping the operation, reservation of transmission of the “ACK” packet to the management device 400 is made (P383 to P387).

Next, the operating information of the restored transmission data area is checked, and if the original operating state is not in the game, the original routine (FIG. 197) is changed to the original routine. If the game is in the game, the operating information is changed to "free". And then return to the original routine. This is to make it match the actual state and to smoothly execute the processing according to the operation information in the processing of the “restart” packet transmitted thereafter.

FIG. 206 shows the procedure for receiving a "restart" packet.

[0832] Upon receiving the "restart" packet, unit controller 190 first starts communication control with card reader 800, and reserves transmission of the "initial value setting" function (procedures P391 and P392).

Next, the operation information is checked, and if "forced termination", the flow shifts to the procedure P341 in FIG. 201, and the pachinko machine is set to "unit recovery" according to the same procedure as the forced termination request processing.
The same state as before stopping the operation by the packet is set (procedure P393).

[0832] If the operation information is "stop", the flow shifts to the procedure P483 described below to put the pachinko machine in a stop state (procedure P394). After making a transmission reservation for the "card accepted" function, the flow shifts to the later-described procedure P427 of FIG. 208 to suspend the game of the pachinko machine (procedures P395 and P396).

On the other hand, when the operation information is other than "forced end", "stop" or "interrupted", that is, "free"
At this time (the operation information does not indicate "playing" because of the unit recovery procedure P389 in FIG. 205), the lamp display is set to the customer waiting state, and then the card reader 800 is instructed to reread the card. A transmission reservation of the "reload" function is made, the card insertion lamp 168 is driven to blink, and the process returns to the original routine (FIG. 197) (procedure P
397-P399).

FIG. 207 shows a processing procedure when a response to the “card-in” packet is received in the packet reception task of FIG. 197.

[0835] When the unit controller 190 responds to the "card-in" packet, the controller
Check if CK is waiting (procedure P401)
Then, "A" containing the card text without waiting for ACK
When the CK "packet arrives, it is regarded as an error and the card text data in the reception data area is cleared (procedure P
402). On the other hand, when a packet arrives in the ACK waiting state, it is checked whether the packet is a NAK (negative acknowledgment) (procedure P403). The sound output for generating a sound indicating transmission and card acceptance failure makes a reservation and returns to the original routine (procedures P405 and P406). Further, even when the response is not a NAK, if the card number in the "ACK" packet does not match the previously transmitted card number, the flow shifts to procedures P404 and P405 to reject the acceptance of the card (procedure P404). .

If the card numbers match in procedure P404, the card text data in the received data area sent by the “ACK” packet is copied to the corresponding position in the transmitted data area, and the number of balls in the card text is copied. Is copied to the column of “number of balls” in the operation data area (procedures P407 and P408).

[0837] Thereafter, the card state in the card text is checked (procedure P409). If the card is in the "stopped" state, the card state is set to "free", and the operation information of the pachinko machine 100 is set to "game". After rewriting to "medium", transmission reservation of the "end switch" packet to the management device 400 is made (procedures P421 to P423).

[0838] As a result, the "end switch" packet is transmitted to the management device 400, and when the "ACK" packet is returned, the card is ejected by the end switch processing described later (FIG. 209), and the game using the hit card is performed. Is disabled.

[0839] On the other hand, if it is not a hit card, procedure P40
Move from P9 to P410 to check the operation information, "Free"
If so, the column of the number of customers in the transmission data area is updated (procedure P411), and if it is not “free” (during suspension), the process directly proceeds to procedure P412, and the operation information is changed to “playing”. , After changing the lamp display to the game state, clears the floating ball number counter in the internal RAM and starts detection by the sensor (procedures P413 to P41)
5). Next, the number of balls in the card text is checked, and if it is "0", it is left as it is.
After the start of the drive control, the process proceeds to procedure P418 to make an output reservation for a card reception success sound (procedures P416 to P416).
P418).

[0839] When a response "ACK" packet from the management device 400 to the "interrupted card-in" packet is received, the packet is processed according to the same procedure as that of the response packet to "card-in" shown in FIG.

[0841] Fig. 208 shows a processing procedure when a response to the "interrupt switch" packet is received in the packet reception task of Fig. 197.

[0839] When there is a response to the "interruption switch" packet, unit controller 190 checks whether the controller is in an ACK waiting state (procedure P425).
If an "ACK" packet arrives without waiting for an ACK, the process returns to the original routine without doing anything. Next, it is checked whether or not the response packet is NAK (procedure P426).
If it is not K, the operation information is changed to "interrupted", the lamp display is changed to the interrupted display state, and then the detection by the sensor and the drive control of the hit ball launching device 103 are stopped. A discharge sound output reservation is made (procedures P427 to P432).

[0843] On the other hand, if it is determined in step P426 that NAK is to be received, the flow shifts to step P433 where it is determined whether the pachinko machine operation information in the received data is "playing" or not. Since the response itself is strange, the process returns to the original routine (FIG. 197) without doing anything. When the game is being played, the card state is changed to "playing", and then the detection by the sensor and the hit ball firing control are started ( Procedures P433 to P436). In other words, if the NAK is returned from the management device 400 and the operation information indicates that the game is in progress even if the interruption switch is pressed, the card status is returned to the game and the shift of the pachinko machine to the interrupted state is refused. To interrupt the operation, press the interrupt switch again.

FIG. 209 shows a processing procedure when an “ACK” packet for the “end switch” packet is received.

[0845] This process is executed along substantially the same flow as the "ACK" reception process of the "interrupt switch" in FIG. The difference is that the card text in the transmission data area is cleared (procedure P443), the operation information is changed to "free" instead of "interrupted", and the lamp display is changed to a customer waiting display (procedures P444 and P445). Is a point. Also in this process, if the operation information indicates that the game is being played when the NAK is received, the card state is returned to the game and the end process is stopped (procedures P451 to P45).
4).

FIG. 210 shows a processing procedure when an “ACK” packet for a “return-to-zero” packet is received.

This process is executed according to the same flow as the “ACK” receiving process of the “end switch” in FIG. 210 (procedures P461 to P474).

[0848] The reception processing of the "ACK" packet for the "stop" packet shown in FIG. 211 is executed along substantially the same flow as the "ACK" reception processing of the "interruption switch" in FIG. 211 (procedure P481). ＰP494). The only difference is that in addition to the card ejection function, a transmission reservation (procedure P488) of a card rejection function is entered.

FIG. 212 shows the unit controller 19.
The processing procedure of the card reader control task among the ten main tasks 0 is shown.

In this task, first, it is determined whether or not the card reader 800 can be controlled by checking the flag in the internal RAM. If no, the serial transmission interrupt and the reception interrupt are prohibited (procedures P131 to P133). .

[0851] On the other hand, when the card reader 800 can be controlled, the procedure shifts from procedure P131 to P134 to determine whether the function is being transmitted. Next, it is determined whether the function is being received. If the function is being received, it is checked whether the reception is completed within the set time (procedures P135 and P14).
0). In addition, it is checked whether or not there is a function in the reception buffer area of the internal RAM, and if there is a reception function (procedure P136), the reception data transformed into a form that is easy to transmit is restored to the original form, or a parity error occurs. After checking whether there is no code or the length of the code is correct (procedure P141), the type of the function is determined (procedures P143 to P150), and the processing corresponding thereto (FIGS. 213 to 220) is executed.

[0852] If it is determined in step P136 that there is no reception function, the flow shifts to step P137, where it is determined whether a response function from the card reader controller CPU2 is in a waiting state. Check (procedure P142). If not waiting for a response function, it is determined whether or not the function can be transmitted. If transmission is possible, it is determined whether or not there is a function to be transmitted (procedure P13).
9) If there is a transmission function, function transmission processing (see FIG. 221) is executed.

[0853] Fig. 213 shows the procedure for receiving the "test card" function in the card reader control task.

[0854] When this function is received, the flag is checked first to determine whether or not the "test card" function is waiting (procedure P501). This flag is set when the test switch 179 is turned on in the switch detection task (see FIG. 230). If it is waiting for a function, then it checks whether the operation information is "free", and if it is free, checks whether it is offline (procedure P50).
2, P503). If the state is off-line, the same or different number of prize balls for a test game as is sent from the management device 400 when stored online in the program ROM is set (procedure P504). This is because the number of prize balls is not sent from the management device 400 during offline. After setting the number of prize balls, the first number of balls (0) and the amount (1000 yen) fixedly given to the test card are set (procedure P
505).

[0855] When online, the procedure jumps from procedure P503 to P505, skipping the setting of the number of prize balls in procedure P504, and setting the number of balls and the amount of money. After that, the counter for counting the number of floating balls is cleared, the lamp display state is changed, control of the hit ball launching device 103 and detection of the sensor are started, and a reservation for outputting a sound indicating successful card reception is made. The operation information in the test mode operation data area is changed during the game, and the process returns to the original routine (procedures P506 to P511).

On the other hand, when the test card function is received without waiting for the test card function, the procedure moves from the procedure P501 to the procedure P512, and whether the operation information in the test mode operation data area (see [Table 1]) is "interrupted". Determine whether or not. If the interruption switch 114 is pressed during the game in the test mode and the operation is interrupted, the interruption is released by inserting the test card without pressing the test switch, and the game can be resumed. Since the number has already been set, the routine immediately shifts to procedure P506 to enable the test game to be restarted.

[0857] If it is determined in the above-mentioned procedure P512 that the operation information is not interrupted, the flow shifts to procedure P513 to determine whether or not the system is offline. Here, when it is determined that the game is offline, the process shifts to the procedure P504 to set the number of prize balls and the like, and prepares for a test game. this is,
This is because an unexpected situation is assumed, and if there is a test card at the time of off-line, there is no particular problem even if the test mode is entered.

[0858] On the other hand, if it is determined in step P513 that it is online, the transmission reservation of the "card ejection" function and the output reservation of the card reception failure sound are made (procedures P514 and P515). That is, when the test card is inserted without pressing the test switch 179 at the time of online, the test card is ejected and the test game is not started. As a result, it is possible to prevent an illegal game by a player.

[0859] Fig. 214 shows the processing procedure when accepting the "send card number" function in the card reader control task of Fig. 212.

Here, first, the flag is checked to determine whether or not the “test card” function reception waiting state is established, and then it is determined whether or not the test mode is being performed (procedures P521 and P52).
2). If it is determined that the reception of the function is waiting or the test mode is set, the process jumps to step P525 to make a “card ejection” function transmission reservation, and then makes a reservation for outputting a card reception failure sound (procedure P526). In other words, even if a regular game card is inserted immediately after the test switch is turned on or during the suspension of the test mode, the normal game card is ejected immediately to prohibit the transition to the normal game.

[0861] If neither the "test card" function reception waiting state nor the test mode is set, the process shifts to procedure P523 to determine whether or not the operation information is interrupted. (Procedure P527), and if suspended, compare the card number read in procedure P524 with the card number in the transmission data area. If they do not match, proceed to procedure P525 to make a card ejection reservation, If they match, the flow shifts to procedure P528, where the reservation of transmission of the “interrupted card-in” packet is made.

FIG. 215 shows the procedure of the “status” function reception processing in the card reader control task of FIG. 212.

When this function is received, the "abnormal termination" flag is first cleared, and then statuses 1 and 2 in the reception buffer are saved in the internal RAM (procedure P53).
1, P532). The "abnormal end" flag is referred to in the error control task procedure P170 in FIG.

Next, it is determined whether or not the "card accepted" function was transmitted in the previous transmission, whether or not the card is present in the card reader, and whether or not the operation information is "in game" (procedure). P533 to P535). Here, since the previous transmission was the "card acceptable" function and the card is present in the card reader and the game is not in a normal state except during the game, the "card ejection" function transmission and ejection sound output reservation are made. After that, it is determined whether the end of the test mode is online or offline. If it is still offline, the flow shifts to procedure P98 in FIG. 196 to wait for reception of a “line test” packet (procedures P536 to P5)
38).

On the other hand, if the previous card accepting function has not been transmitted or the card is not in the card reader even if it has been transmitted, or if the card accepting function is transmitted and the card is in the card reader, If "playing", the flow shifts to procedure P538 without making a card ejection reservation, and determines whether the end of the test mode is online or offline. If the test mode is offline, the process jumps to a "line test" packet wait.

[0866] Fig. 216 shows a processing procedure when the "retransmission request" function is received.

In this case, first, it is determined whether or not a retransmission request was made in the previous transmission (procedure P541). If yes, it is strange that the retransmission request is returned in response to the retransmission request.
Set the reader error flag (procedure P54)
3). This is because, when a retransmission request is returned in response to a retransmission request, this is repeated thereafter, and other function transmissions cannot be performed. On the other hand, if no in procedure P541, a retransmission reservation for the function already transmitted (procedure P54
Perform 2) again, and then return to the original routine. The reader error flag is referred to in the procedure P163 in the error control task in FIG.

FIG. 217 shows the unit controller 19
FIG. 218 shows a processing procedure when a “normal end” function is received, and FIG. 218 shows a processing procedure when an “abnormal end” function is received.

[0890] When the "normal end" function is received, the error flag is cleared (procedure P545), and the flow shifts to the procedure P531 in FIG. 215 to thereafter perform the processing according to the same procedure as when the "status" function is received. On the other hand, when the "abnormal termination" function is received, the status 1 sent at the same time is checked, and if the initial value to the card reader is not set, the process jumps to the procedure P532 of FIG. 215 as it is, and the initial value is not set. If not, set the "abnormal termination" flag and then proceed to procedure P532.
The process jumps to and executes the same processing as the status reception processing (procedures P546 and P547). The "abnormal end" flag is referred to during the error control task in FIG. 223, and the card cannot be accepted thereafter.

FIG. 219 shows the procedure of the “initial value request” function receiving process in the card reader control task of FIG. 212.

[0873] When this function is received, a transmission reservation of the "initial value setting" function is made first, and then it is determined whether transmission is prohibited by checking the flag (procedure P
551, P552). Here, if transmission is prohibited, procedure P5
If transmission is permitted in step 55 and transmission is not prohibited, procedure P5
At 53, the operation information of the pachinko machine 100 is checked and "free" is checked.
If it is "playing" or "interrupted", a transmission reservation of the "card accepted" function is made (procedure P554). On the other hand, in the judgment of the procedure P553, “free”, “in game”,
If the status is other than "interruption" (stop or forced termination), a transmission reservation of the "card rejection impossible" function is made (procedure P556).

If it is determined that the “self-discharge” function has been received during the task in FIG. 212, the output of the card unsuccessful sound is reserved as shown in FIG. 220, and the process returns to the original routine (procedure P558).

Next, FIG. 221 shows a transmission processing procedure when it is determined in step P139 that there is a transmission function during the processing of the card reader control task of FIG. 212.

In transmitting the function, first, the number of retries (for example, three times) is set in the internal RAM, the ACK reception timer (5 seconds) is set, and the call signal EN is set.
Q to the card reader (procedure P560
ＰP562). Then, if ACK does not come, procedure P
It is determined whether the timer set in 561 has exceeded (procedures P563 and P564). Even if the time is over, the number of retries is checked. If the number of retries has not reached the predetermined number (three times), the flow returns to procedure P561, the timer is reset, and the transmission of ENQ is repeated. If the number of retries is exceeded without receiving an ACK, the error flag is set and the function transmission is stopped (procedure P
565, P566, P567). On the other hand, if ACK is returned within the number of retries, the transmission data is created, and then the STX code is first put into the transmission buffer to start transmission, and the transmission flag is set (procedures P568 to P5).
70).

FIG. 222 shows the unit controller 19.
The processing procedure of the packet transmission task among the ten main tasks of 0 is shown.

In this task, it is first determined whether or not there is a packet to be transmitted. If there is a packet, the packet type name is written in the packet head section of the transmission data area of the unit memory 550, and then the command register CR1 in the communication area is written.
, The packet transmission timer is set (procedures P151 to P154). The data transmission controller 551 starts transmitting the corresponding packet by writing the packet type name into the command register CR1, and clears the command register CR1 when the transmission is completed.

[0877] If there is no transmission packet in procedure P151, or after setting the transmission timer in procedure P154, it is determined in step P155 whether the transmission timer has been set. If so, the procedure moves to procedure P156.
If not set, the flow returns to P151. Procedure P15
At 6, the command register CR1 becomes "0" upon completion of transmission
Is determined, and if it is not yet "0", it is checked whether the transmission timer is over (procedure P159). If the transmission timer has not expired, the process returns to procedure P151. On the other hand, when the transmission timer has expired, the "Z-80 error" flag is set and then the transmission timer is reset (procedures P160 and P15).
8).

[0887] If the command register CR1 becomes "0" in procedure P156, and if the transmitted packet is of a type that receives "ACK" such as "card in", the ACK wait timer ( 10 seconds) and then reset the transmission timer (procedure P156,
P157). This ACK wait timer is referred to in procedures P103 and P104 in the packet reception task in FIG. 197.

FIG. 223 shows the unit controller 19
0 shows the procedure of the error control task among the main tasks.

In this task, first, “Z-80 error”
The flag (see P160 in FIG. 222) and "packet ACK
The "error" flag (see P105 in FIG. 197) is checked (procedures P161 and P162). If either flag is set, the process proceeds to procedure P174 to prohibit the timer interrupt or the serial interrupt, and to execute the task After stopping the processing, the CPU is powered down (procedures P175 and P176).
4 to P176), for example, by fixing the level of a common signal for a segment display which becomes a watchdog pulse,
The unit controller 190 is operated by the reset circuit 555.
Can be executed by resetting.

On the other hand, when neither the “Z-80 error” flag nor the “packet ACK error” flag is set, the “reader error” flag (P543 in FIG. 216, FIG.
17 (see P565 in FIG. 221) and if the flag is not set, the "reader abnormality" bit of the monitor information 2 in the unit memory 550 is reset, and the procedure returns to the procedure P161 (procedure P163).
P164). If the "reader error" flag has been set, the process shifts to procedure P165, sets the "reader error" bit of the monitor information 2, clears all the reader control flags, and enables reader control. (Procedures P166, P167). Thereafter, it is checked whether or not the test mode is being set and whether an initial value is set (procedures P168 and P169). If the test mode is set or the initial value is not set, the test mode shown in FIG. 231 is ended. Execute the process.

If the initial value is set instead of the test mode, an “abnormal end” flag (FIG. 21) is set in procedure P170.
8 (see procedure P547), and if the flag is "0", the process returns to the procedure P161. If the "abnormal termination" flag is set, the process proceeds to the procedure P171 to change the operation information to "forced termination". After the change, make a transmission reservation for the “card cannot be accepted” function, clear the “abnormal end” flag, and return to the procedure P161 (procedure P1
72, P173).

FIG. 224 shows the unit controller 19
The procedure of the ball number calculation task among the ten main tasks of 0 is shown.

In this task, first, it is determined whether or not a sensor is being detected, that is, a game is being performed by checking a flag or a signal (procedure P181). If no sensor is being detected, a counter for counting the number of times each sensor is turned on is cleared (step P181). Procedure P182),
During sensor detection, the firing sensor SNS5, the first safe sensor SNS2, and the second safe sensor SNS3 obtained in the processing of FIG. 194 according to the procedures P183 to P199.
The number of ON times of each sensor of the foul sensor SNS4 and the out sensor SNS1 is read, and the total number of winning balls, the number of payout balls, the number of outgoing balls, and the difference number are calculated. Finally, the total number of winning balls is added to the hitting calculation register. (Procedure P200).

FIG. 225 shows the unit controller 19
The procedure of the switch detection task of the main task 0 is shown.

In this task, a flag or a signal is first checked to determine whether or not the sensor is being detected (procedure P201).
13. It is checked whether the end switch 115, the call switch 165a or the test switch 179 is turned on (procedures P202 to P206). When any one of the switches is turned on, a corresponding process (see FIGS. 227 to 230) is executed. When the call switch among the above switches is turned on, the status display lamp 162 of the pachinko machine is changed to blink, and the output of the switch operation sound is reserved (procedure P219).

[0887] On the other hand, when a sensor is being detected in procedure P201, the flow shifts to procedure P207 to determine whether or not a search timer (procedure P216) to be described later is operating. If not, a card being played in procedures P213 and P214 is determined. It is determined whether or not the number of balls and the amount are “0”. If the number of balls is "0" and the amount is not "0", purchase request processing (procedure P217) is performed. More specifically, an output reservation for a sound prompting the purchase switch 113 to be turned on and a display update reservation for blinking of a lamp built in the purchase switch are made.

[0888] If both the number of balls and the amount of money are "0", the search timer (10 seconds) is operated to start the return-to-zero determination, and the output of a sound indicating that the search timer is operating is reserved, and then the procedure is started. Return to P201 (Procedure P2
15, P216).

[0889] Then, in procedure P207, it is determined again whether the search timer is operating. If the search timer is operating, the process proceeds to procedure P208, and it is determined whether there is any floating ball remaining in the game board.
Here, if there is no floating ball, the process proceeds to procedure P212,
It determines the occurrence of a zero return and reserves the transmission of the “return zero” packet.

[0890] In this zero-return determination procedure, FIG.
The test mode ending process as shown in FIG. 7 is performed, and if a zero is generated during the test mode, the test mode is ended.

On the other hand, while floating balls remain during the operation of the search timer, the process proceeds from procedure P208 to step P209 to determine whether the search timer (10 seconds) has expired. The process returns to P212 to return to zero. This is because it is usually impossible for floating balls to exist even after 10 seconds have elapsed since the number of balls reached “0”.

[0891] If the search timer has not expired, the flow shifts from procedure P209 to P210 to determine again whether or not the number of balls is "0". If not, the search timer is stopped to return to zero. Is stopped (procedure P21).
1). This considers the case where the floating ball wins the winning opening during the operation of the search timer and the number of balls held is added, whereby the game control is continued again. If the number of balls is not “0” while the search timer is not operating, the procedure P2
The process proceeds to 18 to determine whether or not the value of the hit calculation register has become larger than a predetermined number of hits, and when the value has increased, hitting processing as shown in FIG. 226 is executed. For the number of hits, a plurality of hitting modes may be prepared in advance, a mode may be selected by a program or the like, and the number of hits according to the mode may be compared with the value of the hitting operation register.

FIG. 226 shows the procedure of the hitting process during the process of FIG. 225.

[0894] Upon entering this stop processing, first, it is determined whether or not the test mode is in effect by checking the flag (procedure P581). After the number of hits in 550 is updated (+1) and the card status is set to "hit and free", the detection of the sensor and the drive control of the hitting ball firing device 103 are stopped, and the output of hitting sound is reserved ( Procedure P582
~ P587). Although the card ejection command has not been issued here, the “stop” packet is transmitted to the management device 4.
When the ACK is returned, the "card ejection" function is sent to the card reader (procedure P487) in the receiving process (FIG. 211). As described above.

[0895] On the other hand, if a stop occurs during the test mode, the procedure shifts from procedure P581 to P591 to "stop".
When the ACK for the packet is received, procedures P591 to P597 substantially the same as procedures P483 to P489 (excluding P488) in FIG.
The test mode takes into account that the test mode is executed even when the management apparatus 400 is not connected and is offline. If a stop occurs during the test mode, the end switch 115 is turned on to shift to the test mode end process, and the subsequent state is determined depending on whether the system is online or offline (see FIGS. 230 and 231). ).

FIG. 227 shows the procedure of the interrupted switch process in the switch detection task of FIG. 225.

[0897] When the interruption switch 114 is detected to be on, this processing is started, and it is first determined whether or not the test mode is in effect (procedure P601). Here, if the test mode is not set, the process proceeds to procedure P602, in which the reservation of the transmission of the "interruption switch" packet is made, and then the card state is changed to "interruption". Stop and return to the original routine (procedures P603 to P6
05). The ejection of the card or the like due to the ON of the interruption switch is performed when an ACK packet corresponding to the above packet is received (see FIG. 208).

On the other hand, if the interruption switch is turned on during the test mode, the operation information is updated, the transmission of the card ejection function is reserved, and the display of the control stop lamp is changed during the interruption switch processing ( Procedure P61
1 to P616). This is for offline test mode.

FIG. 228 shows the procedure of the purchase switch process in the switch detection task of FIG. 225.

When the purchase switch 113 is turned on, first, an instruction to turn off the lamp 121 (hereinafter, referred to as a purchase lamp) built in the purchase switch is given (procedure P621). This lamp is lit as long as the amount does not become "0", and is driven to blink by the purchase request procedure P217 in FIG. 225 performed when the number of balls becomes "0". The blinking is stopped at the same time when the purchase switch is turned on. Next, it is determined whether the amount of the card is “0”, and if it is “0”, the process returns to the routine of FIG. 225 without doing anything (procedure P622).

On the other hand, if the amount remains, the procedure P6
The process proceeds to step S23, where the conversion rate of the purchased ball is read, and then the number of balls corresponding to 200 yen is added to the number of balls and the number of balls in the unit memory 550 (procedure P624). Then, the frequency of the amount of money (the balance) is “−2”, the number of purchases is “+1”,
It is determined whether or not the amount has become “0” after the sales frequency is increased by “+2” (procedures P625 to P628).

If the amount is "0", the purchase lamp is not turned on, and if the balance is left, the purchase lamp is turned on, and then the driving control of the hit ball launching device 103 is started (procedures P628 to P630). ). Accordingly, the purchase lamp is temporarily turned off when the purchase switch 113 is turned on, but is turned on immediately while there is a balance. Further, when the player turns on the purchase switch based on the purchase request sound and the display, the purchase lamp shifts from blinking to lighting or from blinking to off according to the amount of the card.

After the control of the hitting ball firing device is started, the output of the purchase request sound is canceled, the output of the switch operation sound is reserved, and the process is terminated (procedures P631, P632).

FIG. 229 shows the procedure of the end switch processing in the switch detection task of FIG. 225.

[0905] If the end switch 115 is detected to be on, the detection of the sensor is first stopped, and then the hit ball launching device 10 is turned off.
3 (the procedures P641 and P64)
2). Then, in the procedure P643, it is determined whether or not the test mode is set. If the test mode is set, the process shifts to a test mode end process shown in FIG. 231. If the normal operation mode is set, a "end switch" packet transmission reservation is made and the card state is changed. Change to "free" (procedure P644, P64
5). The card ejection command, lamp display change, and the like are performed during the process of receiving the response packet ACK for the “end switch” (FIG. 209).

FIG. 231 shows the procedure of test switch processing in the switch detection task of FIG. 225.

[0907] When the ON of the test switch 179 is detected, first, a switch operation sound output reservation and a test card function wait flag are set (procedure P65).
1, P652). This flag is referred to in a procedure P501 in FIG. 213 showing the procedure of the test card processing. Then, it is determined whether or not it is offline. If it is offline, it makes a transmission reservation for the "card accepted" function to the card reader, and if it is online, it does nothing. That is, the transmission of the “card accepted” function is not performed.

[0908] Therefore, when online, the mode shifts to the test mode only when the acceptance of the card is enabled. However, even if the card can be actually accepted online (suspended), the test card is ejected when the operation information is other than "free" (procedures P502 and P513 in FIG. 213). reference).

[0909] The test switch processing (procedure P
651-P654), it is also possible to set a timer to return to the original state when a test card is not inserted within a certain time after the test switch is turned on.

FIG. 231 shows the specific procedure of the error control task of FIG. 223 and the test mode end processing during the end switch processing of FIG. 229.

When this process is started, first, all lamps are turned off, the detection of sensors and the drive control of the hit ball launching device 103 are stopped, and it is determined whether the process is offline or online (procedures P661 to P664).

Here, if online, it is checked whether the operation information of the pachinko machine is “forced termination” (procedure P665), and if forced termination, reservation of transmission of “card cannot be accepted” function and reservation of output of card ejection sound are made and the original routine is executed. Return to (procedures P671, P672).

[0913] The card reader is "card not accepted"
When the function is received, the card held is ejected and then the card is not accepted. In the case other than the forced termination, the display of the lamps 123 and 163 is changed to the customer waiting state, and then it is checked whether the operation information in the operation data area in the test mode is “stop” (procedures P666 and P6).
67). If it is a stop, the process jumps directly to the procedure P670. If it is not a stop, the transmission reservation of the "card ejection" function and the output reservation of the card ejection sound (procedures P668, P669) are made, and then the procedure goes to the procedure P670. Change the display of the card insertion lamp to blink and return to the original routine. Therefore, the pachinko machine returns from the test mode to the “free” state of the normal operation mode.

[0914] When the player is in the stopped state as described above, the procedure P6 is executed.
68 (card ejection function transmission reservation) is skipped and the procedure jumps from procedure P667 to P670.
This is performed in the stop processing of FIG. 226 (procedure P59).
This is from 1) in order to avoid duplication of procedures.
Also, the reason why the procedure P669 (card ejection sound output reservation) is omitted at the time of stopping is to prevent the ejection sound from being output when the card is not ejected. That is,
In the test mode, when a hit occurs, the card is ejected at that time, and thereafter, when the end switch 115 is turned on, the process shifts to the test mode end processing (procedure P642 in FIG. 229). Is output because it becomes inconsistent with reality.

[0991] On the other hand, if it is determined in the above-mentioned procedure P664 that the apparatus is offline, the flow shifts to procedure P673 to make a transmission reservation for the "card rejection disabled" function and an output reservation for the card ejection sound, and then "offline at the end of test mode" Flag is set, and it is checked whether the "reader error" flag is set (procedure P673-
P676). Here, if there is no reader error, the process returns to the original routine. If there is a reader error, the flow shifts to procedure P677 to clear the "offline at the end of test mode" flag and then wait for a "line test" packet (FIG. 196).
Procedure P98). The above flag indicates the procedure P in the “status” function reception processing (FIG. 215).
Reference is made to 538, and when the status is transmitted, this flag is seen and the process shifts to a line test wait. That is, when there is no reader error, the procedure returns to the original routine after the end of the procedures P673 to P676, and then shifts to the line test wait when the status 1 and 2 are received together with the "normal end" function after the card is ejected from the card reader. . On the other hand, if there is a leader error, procedure P6
When the card ejection process is executed in response to the function 73 and the status 1 and status 2 are sent from the card reader together with "abnormal termination", the procedure P5 in FIG.
In step P677, the "offline at the end of the test mode" flag is cleared in order to prevent the system from shifting to the line test waiting state to prevent the card from being removed.

FIG. 232 shows the unit controller 19
The processing procedure of the sound control task among the ten main tasks 0 is shown.

In this task, “hit sound”, “switch operation sound”, “card ejection sound”, “card reception success sound”,
Alternatively, it is checked whether or not there is an output reservation for "card reception failure sound" (procedures P221 to P225). And then a speech synthesis circuit (Sound I
C) Reset 582 to stop the sound being output (procedures P231 and P232). Then, the procedure P2
The process proceeds to 34, where a control signal is given to the sound IC to output the selected sound. Then, it is determined whether or not the set output time has elapsed, and if it is over, the output is stopped (procedures P235 and P237). On the other hand, if the output time has not exceeded, it is determined whether the output sound is a repetitive sound,
If the sound is not a repetitive sound, the sound output is stopped (procedures P236 and P237). However, even if the sound output stop command is issued in the procedure P237, the sound IC does not stop sound output until one phrase of the sound being output ends, and stops at the end of the phrase.

[0918] If there is no output reservation for any of the above five types of sounds, it is checked in step P226 whether sound is being output. If output is in progress, the process proceeds to step P235 to check whether the output time has been exceeded. . On the other hand, when the sound is not being output, it is checked whether there is an output reservation of “search timer sound”, “purchase request sound”, “stop sound” or “forced end sound” (procedures P227 to P230). After setting data and time to specify the sound to be played (procedure P23
3) The procedure shifts to procedure P234 to start sound output, and stops sound output when a time-out occurs. In other words, these four sounds are output after the output of other sounds is completed.

FIG. 233 shows the procedure of the timer control task among the main tasks of the unit controller.

In this task, 10 m which is a reference for blinking of a lamp, a packet transmission timer, an ACK reception timer, etc.
It manages two reference timers, S and 100 ms, and
Update 10ms timer every 0ms (decrement)
And updates the 100 ms timer every 100 ms
(Procedures P241 to P244).

FIG. 234 shows the unit controller 19
The processing procedure of the lamp display control task among the 0 main tasks is shown.

In this task, the safe ball lamp 164, the P machine status display lamp 16
2. When the purchase switch built-in lamp 121, the card insertion lamp 168, and the game status lamp 123 are updated,
Change the display state (procedures P251 to P25)
5). Next, it is determined whether "customer waiting display" or "stop display" is necessary.
63 is scrolled and all lamps of the analog display 163 are blinked simultaneously at the time of stop display (procedure P
256-P259). Further, the necessity of displaying the number of balls is determined, and if necessary, the lamps of the analog display 163 are turned on in order from the left according to the number of balls (procedure P
260, P261). In addition, the analog display of the number of balls is performed in a so-called log display in which the number of balls displayed by one lamp increases as the number of lit lamps increases. Further, when none of the "customer wait display", "stop display" and "ball count display" is required, the analog lamp 163 is turned off (procedure P262).

[0923] The following Table 35 shows an example of the display state of each lamp according to the state of the pachinko machine.

[0924]

[Table 35] In the same table, × mark is off, ○ mark is on, △ mark is blinking,
S indicates a scroll display, and A indicates an analog logarithmic display corresponding to the number of balls. In the "search" column during the game, the amount of money and the number of balls become zero and the search timer (10
Second) The display state during operation is displayed, and after 10 seconds elapse, the state is shifted to the zero return state.

[0925] The main tasks of the unit controller include a port output control task in addition to the above nine kinds of tasks. In this task, a process of outputting the output state determined in each task to the corresponding I / O port is executed (not shown).

FIG. 235 shows the timing of input / output signals when the pachinko machine is controlled according to the above control flow.

[0927] The number indicating the number of balls is, for example, a purchase ball rate of 50 pieces / 200 yen and a main prize ball number of 13
And the number of sub prize balls calculated as seven.

[0928] After receiving a response packet ACK to the "card-in" packet at the timing t1, when the ON signal of the purchase switch 113 comes in at the timing t2, the firing drive control signal is changed to the high level, and the hit ball firing device 103 can be driven. At the same time, the frequency of the balance of the card is subtracted by "2", the number of balls for 200 yen is added, and the display of the amount of money and the number of balls are updated.

[0929] Thereafter, when a detection pulse is received from each sensor, the unit controller 190 calculates the number of floating balls and the number of held balls in real time, and changes the number of balls and the display thereof one after another. When the number of floating balls is "0" inside the controller, even if there is a detection pulse (see P1) of the safe sensor, this is invalidated, and the prize ball number corresponding thereto is not added.

During such game control, the interruption switch 1
When the ON signal 14 is input (timing t3), the firing drive control signal is turned off. However, the display is maintained in the state immediately before the interruption. After that, A of "Suspended Card In"
When the CK packet is received (timing t4), the game control is started again, the game ends when the ON signal of the end switch 115 is input (timing t5), and the ACK of the "end switch" is received (time t5). Timing t6)
The display, the number of balls and the amount data are cleared to "0".

[0931] On the other hand, if a return-to-zero state occurs in which both the amount of money and the number of balls of the card become "0" during the game (timing t7), the search timer is started and the detection pulse of the safe sensor 1 or 2 is detected within 10 seconds. If there is no packet, a "return-to-zero" packet is transmitted, and the number of floating balls is cleared to "0" at the time (t8) when the ACK is received. If the number of floating balls becomes “0” during the operation of the search timer, a “return-to-zero” packet is transmitted at that time.

[0932] Next, an example of a card reader control procedure by the card reader control device 188 based on a command from the unit controller 190 will be described with reference to Figs. 236 to 265.

[0933] Communication between the card reader control device 188 and the unit controller 190 is performed by a function code.
"Initial value setting" function for giving the card reader a date code and an identification code for collating with the magnetic data read from the card, permitting the card reader to accept the card "Card accepted" function, "Card unacceptable" function to instruct card reader to stop accepting cards, "Card eject" function to instruct card eject, Card magnetic data reread "Reload" function to request retransmission of the function code sent immediately before, "status request" to request transmission of a code indicating the status of the card reader held in the card reader controller Function and Return Reiana PH indicating that the lifting ball cards, the amounts becomes zero at a predetermined position of the punch hole forming region
Eight kinds of commands of a "return-to-zero" function for giving a command to pierce No. 4 are prepared.

[0934] On the other hand, as a function code from the card reader control device 188 to the unit controller 190, a "card number transmission" function for transmitting the card number read by the card reader to the unit controller, and a function for notifying that the test card is inserted to the unit controller. "Test card" function to inform
At the time of reset, an "initial value request" function for requesting an initial value such as a date and an identification code, a "normal end" function for notifying the unit controller 190 that the requested processing has been normally completed, and conversely, the processing is normally performed. An "abnormal termination" function to notify that the card has not been terminated, a "self-discharge" function to notify that the card reader controller 188 has determined that the inserted card is illegal and the card has been voluntarily discharged, a unit controller Eight types of "retransmission request" function for requesting retransmission of the function code sent immediately before to 190, and "status transmission" function for transmitting the status of the card reader in response to "reload" or "status request" There is. Each function is composed of an STX code indicating the head, a function code FNC, and an ETX code indicating the end, and there are some functions in which data, status, and the like are inserted between the function code FNC and the ETX code.

[0935] However, the communication between the card reader control device 188 and the unit controller 190 does not unilaterally send the function code, but first, the transmitting side sends an interrogation code ENQ, and receives the permission response ACK from the receiving side. After the function code is sent.

[0936] The "normal end" function, the "abnormal end" function and the "status" function include an 8-bit status 1 indicating the state of the card reader as shown in [Table 36] and [Table 37]. ,
A column for status 2 is provided, and the status is sent to the unit controller together with the function code. In the "self-discharge" function, there is provided a column for entering an 8-bit code indicating the cause of fraud as shown in [Table 38], which is sent together with the function code.

[0937]

[Table 36]

[0938]

[Table 37]

[0939]

[Table 38] FIG. 236 shows the entire procedure of the main control by the card reader control device 188, and FIGS. 252 and 253 show the control procedure of an interrupt process generated by a timer interrupt separately from the main control.

[0940] When a reset is applied, that is, when the reset input terminal changes to low level, the card reader control device 188 first performs internal initialization (procedure R1) as shown in FIG. Request an initial value (routine R2). Then, the unit controller 190 checks whether an interrogation code ENQ is entered (routine R3), and if so, shifts to routine R11 and returns a response code ACK, and then receives a function code. Then, after executing the processing (routine R12) corresponding to the received function code, it transmits a function code indicating the processing result such as normal end or abnormal end, status transmission, etc. (routine R13).

[0941] Thereafter, it is checked whether or not the initial value has not been set (routine R14). If the initial value has not been set, the routine returns to the routine R2 to request the unit controller 190 again for the initial value. On the other hand, if the initial value has been set, the routine returns to the routine R3 to check whether or not the calling code ENQ has been entered. Here, when the ENQ has not been entered, the process proceeds to the routine R4, and it is checked whether or not the card insertion is prohibited by checking a predetermined flag prepared in the built-in RAM. This "card insertion prohibition" flag is set to "1" in the initialization routine R1 and is cleared to "0" when the reception function processing routine R12 performs processing for permitting the acceptance of a card. Therefore, if "1" is set in the "card insertion prohibition" flag in the routine R4, the process returns to the routine R3, and if the flag is "0", the process proceeds to the next routine R5. Determine if it has been inserted. Here, if the card insertion sensor is off, the routine returns to the routine R3, and if the sensor is on, the routine proceeds to the routine R6 to read the card. Then, the read data is analyzed to check whether the card is a fraudulent card (routine R7). If it is determined that the card is fraudulent, the card is ejected by its own instruction.
Return to (Routine R21). On the other hand, if it is determined in R7 that the card is a legitimate card, the process proceeds to R8,
Here, it is determined from the magnetic code whether or not the inserted card is a special test card. If the inserted card is a test card, a "test card" function is transmitted to the unit controller, and then the routine R3 is executed. Return to (routine R22).

On the other hand, if the inserted card is a regular card which is not a test card, the flow advances to routine R 9 to execute a “card number transmission” function on the unit controller 19.
Send to 0.

FIGS. 237 to 241 show more detailed procedures of the processing flow of FIG. 236.

FIG. 237 shows details of the initialization routine R1 and the initial value request routine R2 in FIG. 236.

[0945] That is, the card reader controller 18
8 is reset, first, various flags and counters,
The internal memory including the buffer, the work area, the register and the like is cleared (routine R101). Then, after setting the stack pointer at the time of occurrence of the interrupt, initializing the I / O port and setting the state of the input / output terminal, the setting code is read from the device code setting device MCS and stored, and then, the card for card transport is set. The relay RLY1 for supplying power to the motor 807 is turned on (routines R102 to R10).
5).

[0946] Next, the monitor display 175 for displaying the cause of the error is set to the off state, the power-on lamp LED 21 for indicating the power-on state is turned on, and the initial value non-setting instruction bit of the status register in the RAM is set to " 1 "is set (routines R106 to R108).

[0947] Thereafter, the "card insertion prohibition" flag in the built-in RAM is set to "1", and then the shutter solenoid 809 is turned off to close the shutter (routines R109 and R110). Then, in routines R111 to R113, it is checked whether the position detection sensors SNS2 to SNS4 in the card reader are off or on. If any one of the sensors is on, the card indicating the card insertion state is displayed. In lamp L
After the ED 12 is turned on (routine R114), and if all the sensors are off, the routine R
Proceed to 115.

[0948] This makes it possible to notify the outside that a card is in the card reader at the time of reset at the time of restoration from power failure. Then, in the routine R115, after setting the "initial value request" function code and the termination code EXT in the transmission buffer, the function transmission processing routine R4 according to the procedure shown in FIG.
Move from 01 to R423. Then, after the execution of the transmission processing routine, the routine R shown in FIG.
The process proceeds to 132 (see M1).

[0949] In the routine R132, the OK lamp LED13 of the status display lamp group is turned on, and then the routine R132 is executed.
The process proceeds to 133, where it is checked whether the "transmission incomplete" flag is set. This flag corresponds to the routine R in the flow (FIG. 254) indicating the function transmission procedure.
Set at 423. In other words, the unit controller 190 and the card reader controller 188 are provided in order to avoid a collision in the case where the transmission process starts simultaneously. In this embodiment, when two transmissions collide, the transmission right is passed to the unit controller 190. The card reader controller 188 sets the "transmission incomplete" flag, and then proceeds to the reception process.

[0950] Returning to FIG. 238, if the transmission has been completed in the routine R133, the flow shifts to the routine R121.
When the "transmission incomplete" flag is "0", the process proceeds to the routine R121 to permit the reception of the reception data into the reception buffer in the RAM, and then the error information area provided in the RAM is cleared. Clear (Routine R12
2). Next, the state of the "transmission interrupted" flag is checked, and "1"
When is standing, that is, during suspension, the routine R1
34, the transmission data saved in the stack area in the transmission processing routine of FIG. 254 is transferred to the transmission buffer, the "transmission interruption" flag is cleared to "0" (routine R135), and the transmission processing is performed again. A routine is executed (routines R401 to R423).

On the other hand, when the “transmission interruption” flag is “0” in the routine R123, the process proceeds to the routine R124, where the transmission call code ENQ from the unit controller is entered.
239 is checked. If yes, the routine jumps to the routine of FIG. 239 (see reference numeral M5). If ENQ is not found, the discharge switch provided on the control board in the control unit is turned on in the next routine R125. If it is on, it jumps to the routine of FIG. 240 (to be described later) (see M6), and if it is off, it checks the state of the "card number waiting" flag.

[0952] This "card number waiting" flag indicates that the card reader is holding only the leading end of the card immediately after the motor is reversed and the card is ejected, and is waiting for the player to remove the card (at this time, the insertion detection sensor 808 and the A flag indicating that the first position detection sensor SNS1 is on)
When this flag is "0", the routine R130 is performed as it is.
If the value is "1", the routines R127 and R128
The routine proceeds to routines R124 to R124 until both sensors are turned off.
128 is repeated, the routine proceeds to the routine R129 at the time of turning off, the "card reception waiting" flag is cleared, and the routine proceeds to the routine R130.

[0953] In the routine R130, "card insertion prohibited"
The state of the flag is checked, and if "1", the routine R124
If "0", the card insertion processing routine shown in FIG. 257 is executed, and the "card reading end" flag is checked in the routine R131. If not completed, the process returns to the routine R124. move on. Then, after the OK lamp is turned on, if the determination in the routine R133 is YES and if the determination in the above-described routine R124 is YES, the process proceeds to the routine of FIG. 239 (see reference numeral M5).

[0954] Here, first, the reception processing R431 to R441 as shown in Fig. 255 is executed, and then the state where the reception of the reception data into the reception buffer is prohibited in the routine R141. Then, the monitor display unit 175 and the OK lamp LED 13 indicating the cause of the card reader abnormality are displayed.
Is turned off (routines R142 and R143), and the function code of the received data received in the above-described reception processing and stored in the buffer is read and decoded (routine R14).
4, R145), and in the case of a regular function code, the processing corresponding to the code (FIGS. 242 to 249) is executed.

On the other hand, if it is not a regular function code, the routine jumps to the routine R150, writes a function code error in the error information area in the RAM, and shifts to the error processing of FIG. 241 (see reference numeral M7).

After executing the processing according to the reception function code, the "initial value not set" flag is checked in the routine R147, and if "0", the process proceeds to the routine R132 in FIG. 238 (see reference numeral M1). If the initial value is not set, the OK lamp is turned on in the routine R148, and the "transmission incomplete" flag is checked. If it is "1", the process returns to the reception processing routines R431 to R441 (see reference numeral M5).
If it is "0", the flow shifts to the routine R115 in FIG. 237 (see reference numeral M4).

If it is determined in the routine R125 that the discharge switch has been turned on, the flow jumps to the routine R161 in FIG. 240. First, the reception of the reception data into the reception buffer is prohibited, and then the OK lamp is turned off (routine R16).
2) The card ejection process and R451 to R484 are executed according to the procedure shown in FIG.

[0958] Thereafter, the "card reception waiting" flag is set (routine R163), and then the self-ejecting function code and the ETX code indicating the cause of the invalidity and the end of the transmission data are sequentially set in the transmission buffer in the RAM (routines R164 to R164). R166), and then performs transmission processing (routines R401 to R4) in accordance with the procedure shown in FIG.
23) is executed. Then, in the routine R167, OK
After turning on the lamp, the "transmission incomplete" flag is checked (routine R168). If "1", the process proceeds to the routine of FIG. 239 (see reference numeral M5).
At 9 the monitor display 175 is turned off, and the process proceeds to the routine R121 of FIG. 238 (see reference numeral M2).

[0959] Furthermore, the routine R150 shown in FIG.
After writing the error information in FIG.
When the process proceeds to the error processing routine 1, the monitor display data corresponding to the error information written in the RAM
OM, and reads the display data from the monitor display unit 1.
The error is output to the terminal 75 and the cause of the error is displayed by a numeral or the like (routines R171 and R172).

[0960] Then, the OK lamp is turned off and the timer is locked so as not to be interrupted by the timer. Then, the motor 807 for conveying the card is stopped, and the shutter solenoid 809 is operated.
Is turned off so that the card cannot be inserted (routines R173 to R176). Next, in the routine R177, it is determined whether or not the error is a parity error. If the error is a parity error, a "retransmission request" function code and an ETX code are set in the transmission buffer (routines R178, R17).
9) Then, the transmission processing routines R401 to R42 in FIG.
Then, the process proceeds to the routine R180, checks the "transmission incomplete" flag, and proceeds to the routine R121 in FIG. 238 or the reception processes R431 to R441 in FIG. 239.

[0961] On the other hand, in the determination in the routine R177,
If it is determined that there is no parity error, the routine R1
When the error information is checked in steps 81 and R182 and the cause of the error is a card error, the flow proceeds to the card ejection processing routine of FIG. 240 as indicated by reference numeral M6. The process proceeds to the routine R121 of FIG. 238, and otherwise, the abnormal end processing routines R293 to R296 shown in FIG. 248.
Is executed, the "transmission incomplete" flag is checked in a routine R180, and the routine shifts to a routine indicated by reference numerals M2 and M5.

FIGS. 242 to 249 show flowcharts for executing processing corresponding to each reception function code appearing in the routine R12 of the flow of FIG. 236 and the routine R146 of FIG. 239.

[0963] FIG. 242 shows the processing procedure when the "initial value setting" function code is received. In this flowchart, the routine R202 is a binary evolution 1
An extra bit and a parity bit added to adjust the number of bits are removed from the date code expressed in the 0-base system, converted to a binary code, and set in the initial value area in the RAM. The reason why the “transmission not completed” flag is cleared in the routine R204 is that the unit controller 190 sends an initial value when the card reader controller 188 is transmitting the “initial value request”. In this case, the card reader controller temporarily suspends transmission and preferentially processes reception.

[0964] Fig. 243 shows a processing procedure when the "card accepted" function code is received.

[0965] As for the "card accepted" function code, packets such as "opening code", "cancel release", "forced release", and "restart" are sent from the management device 400 to the control unit. Sometimes transmitted from the unit controller 190 to the card reader controller 188.

[0966] In the flow of the figure, the routine R2
The reason for checking the status of the position detection sensors 2, 3, and 4 in 13 to R215 is that when a power failure occurs while the card is inserted in the card reader, and then when the power is restored, it is troublesome to reinsert the card. Is omitted. Further, the shutter closed in the routine R218 is
8 is opened when the switch 8 is turned on. On the other hand, when the shutter is closed in the routine R225, since the "card insertion prohibition" flag is set before that, the shutter is not opened even if the insertion detection sensor is turned on unless this flag is cleared. This avoids double insertion of the card.

[0967] Fig. 244 shows the processing procedure when the "card cannot be accepted" function code is received.

[0968] In this flow, if at least one of all the sensors in the card reader is turned on in the routine R233, it is determined that the card is present in the reader, and the card ejection processes R451 to R484 are performed. Has become.

[0969] In the routine R231, "transmission not completed"
The flag is cleared by the unit controller 1
90 and the transmission of the card reader controller 188 overlap, the card reader controller 188 interrupts the transmission,
This is because, when the function is received, if the function is a “card cannot be accepted” function, only the reception is required until a reset is performed or a status request or the like is issued from the unit controller 190.

[0970] The "card not accepted" function determines that a packet such as "closed code" or "forced termination" has been sent from the management device 400 to the control unit, or that the stop condition has been satisfied. In this case, it is transmitted from the unit controller 190 to the card reader controller 188.

FIG. 245 shows a processing procedure when the “card ejection” function code is received.

[0972] In this flow, if the function interrupted and received is the "card ejection" function, and the transmission interruption function is "card number transmission", "test card" or "self ejection", The "transmission interruption" flag is cleared (routines R244 to R248). As a result, retransmission after the reception processing can be omitted. This is because there is no longer a valid card in the card reader, and there is no need to transmit again. If the transmission of the function codes other than the above three is interrupted, the transmission is performed again after the card ejection processing by referring to the “transmission interrupted” flag.

The punching process performed after routine R250 is performed according to the procedure shown in FIGS. 250 and 251 (routines R301 to R35).
1).

FIG. 246 shows a processing procedure when the “reload” function code is received.

In this flow, it is first checked whether the initial value has been set. If not, the flow shifts to the "abnormal end" function transmission processing routines R293 to R296 in FIG. 248 (routine R261).

If the initial value has been set, the routine R2
After clearing the "insertion prohibition" flag at 62 and permitting card insertion, the position detection sensors SNS2 to SNS4 are checked, and if any one is on, it is determined that a card is present.
Set the "unread security" flag. Then, the flow shifts to the magnetic processing routines R541 to R579 in FIG. 257, where the magnetic data and security of the card, the rereading of the punched holes, and the inspection of the read data are performed.
The result is transmitted to the unit controller 190.

[0977] On the other hand, the position detection sensors SNS2 to SNS4
Are turned off, that is, when there is no card in the reader, the insertion detection sensor 808 and the position detection sensor SNS1 are checked (routines R266 and R267). If both are off, the shutter is closed and the card-in display lamp LED12 is turned off. Is turned off and the card holding lamp LED1 is turned on (routines R269 to R271).
The status transmission processing (R291, R294-
R296) and the unit controller 190 is notified that no card has been inserted.

[0978] When the sensor is turned on in either of the routines R266 and R267, it is regarded that only the leading end of the card is held in the card reader, and the "card reception waiting" flag is set in the routine R268. Then, the process shifts to the routine R269 to close the shutter.

FIG. 247 shows a processing procedure when a “return-to-zero” function code is received.

[0980] In this flow, first, the position detection sensor SN
Check S2 to SNS4 (routines R281 to R28
3) If any of the sensors is on, it is determined that a card is present, and the routine goes to a routine R284 to check the punch hole buffer and determine whether or not a game hole has already been opened in the punch hole forming area of the card. If the game hole is open, the process jumps to the routine R286. If the game hole is not open, the position information of the game hole is set in the routine R285, and then the punching process shown in FIGS. 250 and 251 (routine R301). To R352) to open a game hole in the card, and then the routine goes to a routine R286 where the position information of the return-to-zero hole is set and the punching process is performed again (routine R301).
To R352).

[0981] Thereafter, the card discharge processing R45 in FIG.
After executing steps 1 to R484 to set the "waiting for card reception" flag, the flow shifts to the "normal end" function transmission processing (R292, R294 to R596) in FIG.

FIGS. 248 and 249 show the procedure for transmitting the “status” function code and the “retransmission request” function code.

These function transmissions are performed in response to a “status request” and a “retransmission request” from the unit controller 190. First, codes to be transmitted are sequentially set in a transmission buffer, and then the transmission shown in FIG. The process proceeds to R401 to R423.

Note that FIG. 248 includes FIGS. 242 to 247.
Also, the processing executed when the processing result is transmitted after the execution of each processing of FIG.

In the punching process of FIG. 250, first, the punch failure bit in status 1 is cleared to “0”, and then the distance from the reference position is determined based on the punch hole position set in the RAM by the initialization routine or the like. 251 is read from the ROM and stored in the buffer, and then the hole forming process (R
311 to R352).

In the punching process, first, the card is moved to the innermost position of the card reader 800 (routine R311) to clear the “punch OK” flag (routine R312), and then the motor is rotated in reverse to start the timer (3 seconds). And launch
After setting the "movement amount detection" flag, the movement amount counter is cleared (routines R314 to R318). Then, the "timer 2 operation" flag is set, the timer interrupt is permitted, the movement amount is detected by the timer interrupt, and the rotation of the motor is stopped when the punching position is reached (routines R321 and R322). After waiting for 150 msec (routine R323) to wait for the stop, the punch device 820 is operated (routines R324 to R324).
R327). The above routines R323 to R327 are repeated twice to make sure that a hole has been formed. Then, the moving amount counter is cleared, the motor is reversed at high speed, and the card is moved in a direction in which the opened punch hole faces the punch hole detection sensor SNSp. .

[0987] Then, it is determined whether or not the punch hole detection sensor is turned on. If the punch hole is opened at a regular position, the "punch OK" flag is set, and then the first position detection sensor SNS1 is turned on. When the rear end of the card is detected, the timer interrupt is stopped and the motor is stopped (routines R329 to R340). Then, the routine returns to the processing of FIG.
It is determined whether the "K" flag is "1". If the flag is "0", the punching is determined to be defective and the process proceeds to error processing (routines R304 and R305).

In the above routine, if a time-out occurs during the movement of the card, it is determined that a card jam (paper jam) has occurred, and error processing is started (routines R315 and R332).

Next, processing when a timer interrupt occurs will be described with reference to FIGS. 252 and 253.

As described above, in the card reader of this embodiment, the detection signal from the sensor 832 for detecting the rotation speed of the motor is input to the card reader controller 188 as an interrupt signal, and the "timer 2 operation" inside the controller is performed. When this signal comes in while the "flag" is set to "1", the timer 2 shown in FIGS.
Interrupt processing is executed.

[0991] The speed sensor 832 is provided to face the rotary encoder 817 attached to the rotating shaft of the motor.
An interrupt signal comes in every mm movement.

In the timer 2 interrupt processing, first, in the routine R7
01: "Security read" flag and "Punch hole read"
When all the flags are "0", the mode is the movement amount detection mode, the routine proceeds to routine R710, the movement amount counter is incremented, and the interrupt processing ends. The movement detection mode is set during the magnetic processing in FIG. 259 and FIG. 260 (routine R572) and in FIG. 250 or FIG.
Is required to know the movement amount of the card from the reference position during the hole punching process (routine R317).
The movement amount detection mode is set by clearing the “security reading” flag and the “punch hole reading” flag.

[0993] If the "movement amount detection" flag is "0" after the timer 2 interrupt process, the flow advances to routine R702 to increment the movement amount counter, and then the "security reading" flag is set in routine R703. Check if it is set, and if it is set, the routine R7
04, it is determined whether or not the movement amount has become 4.8 mm or more (when the “security reading” flag is “0”, FIG.
The routine proceeds to a punch hole reading routine of 53). The "reading security" flag is set when the punch sensor SNSp is turned on in the routine R523 during the security reading process in FIG. 258. At this time, the security code reading sensor 810a sets the security area (TF) of the card. Located at the beginning. Thus, the first security mark is 4.8 from the beginning of the security area.
It is provided at a distance of at least mm. Therefore, the routine R7
At 04, it is determined that the movement amount has become 4.8 mm or more. If the distance is 4.8 mm or less, the interrupt processing is terminated, and the moving amount counter is incremented again by the next timer 2 interrupt. Then, when the movement amount reaches 4.8 mm, the process proceeds to the routine R711, where the movement amount and the routine R5 are first determined.
At step 19, the read range set in the RAM is compared, and if it is within the read range, it is determined whether or not the security code reading sensor is on, and if it is on, the counter for counting the width of the security code is incremented. The interrupt processing ends (routines R712 and R713). And
When the code reading sensor is turned off, the value of the counter is checked (routine R714). If the width of the security code is "0", it is determined that there is no code, and the interrupt processing ends. On the other hand, if the security width is not "0", the counter width is transferred to the buffer, the counter is cleared, and it is determined whether or not the security width is 0.5 mm or more (routines R715 and R716). If the width is 0.5 mm or less, it is regarded as abnormal. If the width is 0.5 mm or more, "1" is set to the most significant (or least significant) bit of the security buffer operated as a shift register.

[0995] Then, when the next timer interrupt is entered and the read out of the read range in the routine R711, the process proceeds to the routine R721 as the end of reading the first code, and the security read number (counter) is decremented. Then, the security buffer storing the read code is shifted by one bit in the routine R723, and then the read range is added by the security code pitch (3.5 mm), and the processing is terminated. By shifting the security buffer every time one bit of security is detected, the serially read security code is converted into parallel data. By repeating the above routine, when the security reading number becomes “0”, the routine R722
Then, the process proceeds to R714, where the read security width is 0.
When it is 5 mm, "1" is written to the most significant bit of the security buffer. Then, after the security reading, the process proceeds to the magnetic data reading process, and the routine R553 in FIG.
When the "punch hole reading" flag is set to "1" and the "security reading" flag is cleared to "0" and the timer 2 interrupt of FIG. 252 is started, the routine R703 to the routine R731 of FIG. 253 are started. Then, it is checked whether or not the punch hole detection sensor is ON. If the sensor is ON, the counter for counting the punch hole width is incremented in a routine R732, and the interrupt processing is terminated. And
If the punch hole detection sensor is turned off by the next interruption, the flow shifts to routine R733 to check the punch hole width.

[0995] Here, the width of the detected punch hole is 0.8
If it is more than mm, it is regarded as a regular punch hole and the routine R7
At 34, "1" is written to the most significant (or least significant) bit of a buffer (operated as a shift register) for storing the presence or absence of a punched hole.
If it is 8 mm or less, the punch hole width counter is cleared in the routine R735, and then the routine proceeds to the routine R736.

[0996] Here, it is determined whether or not the card movement amount is within the reading range, and if so, the above procedure is repeated.

In the routines R741 to R745, the buffer containing the read bits is shifted by one bit by subtracting the number of punched holes read out, the punched hole width counter is cleared, the read range is set again, and the processing ends. And
When the number of readings becomes "0", the "timer 2 operation" flag is cleared and the subsequent timer 2 interrupt operation is stopped (routine R742, R746).

FIG. 254 shows a procedure for transmitting a function code appearing in the main routine shown in FIGS. 237 to 241. FIG. 255 shows a procedure for receiving a function code similarly.

[0999] Further, FIG. 256 shows the procedure of the card ejection processing which appears in the main routine, FIG. 257 shows the rough procedure of the card insertion processing, and FIGS. 258 to 265 show the procedure during the routine of FIG. Specific procedures of various processes that appear are shown.

In the function transmission process of FIG. 254, first, the number of retransmissions is set in a counter in the RAM (routine R401), and 2 seconds is set as a transmission time in a timer (routine R404). If the response code ACK is returned from the unit controller 190 within two seconds after the transmission of the interrogation code ENQ, the process proceeds to the routine R411 to prohibit the reception and then returns to the S indicating the head.
After the TX code, a code (FNC, ETX, etc.) already set in the transmission buffer is transmitted, reception is permitted to the reception buffer, the "transmission incomplete" flag is cleared, and a series of transmission processing ends. (Routines R412 to R4
16).

On the other hand, if the ENQ code is input before the response code ACK is returned from the unit controller 190, the flow shifts to the routine R421 to temporarily store the transmission data set in the transmission buffer in the work area in the RAM. "Transmission interrupted" and "Transmission not completed" after saving
By setting a flag and returning to the main routine, reception is prioritized (routines R421 to R421).
423).

[1002] If the response code ACK is not returned within 2 seconds after the transmission of the ENQ, the retransmission counter is decremented, and the routine returns to the routine R402 again to return the calling code E.
Retransmit the NQ. Then, when time-out occurs five times, a reset is performed (routine R409).

In the function receiving process shown in FIG. 255, the response code ACK is first sent to the unit controller 1
90 and sets 2 seconds to the timer (routine R
431, R432). Then, within 2 seconds, the head code STX of the function is sent from the unit controller 190.
Is not sent, the type of error is written in the error information area of the RAM, and then the process proceeds to the error processing routines R171 to R180 (FIG. 241) in the main routine (routine R433 → R441). After receiving the STX code, the timer is reset to 1 second, and if the next data (function code, ETX, etc.) is not sent within 1 second, the process also shifts to the error processing routine. Data reception is performed in units of bytes (4 bits), and when data exceeds the capacity of the reception buffer, error processing is performed (routine R439).

In the card ejection process shown in FIG. 256, when the card ejection function comes in the middle of card insertion, that is, when the first position detection sensor SNS1 is on and the insertion detection sensor 808 is off, the motor Is rotated forward (routines R451 to R457). Then, the shutter is opened and the motor is rotated in the reverse direction. The motor is stopped 0.2 seconds after the position detection sensor SNS2 is turned off, the shutter solenoid is turned off, and the shutter is closed (routines R455 to R467). This takes into account the time required for the card to come off the transport roller 812. When the card is removed from the card transport roller 812, the card cannot be discharged any more. At this time, the first position detection sensor SNS1 and the insertion detection sensor 808 are both on.

After the shutter is closed, the jam display bit of status 1 is cleared, the security read flag is cleared, the card-in display LED 12 is turned off, and the fact that there is no card in the status area in the RAM is written ( Routines R468 to R471). In the above-described routines R451 to R471, if a time-over occurs during normal rotation or reverse rotation of the motor, the motor is stopped, and if a card is inside, the jam is processed (routines R481 to R484).

In the card insertion process shown in FIG. 257, after reading various information (security code, magnetic code, and punched holes) of the card, various kinds of information such as parity check of magnetic data, LRC check, security check, and the like are performed. After the inspection, the card number transmission function code and the read card number are written into the transmission buffer (routine R493), and then the transmission processing routines R401 to R423 are executed. If the card number read from the magnetic recording unit is a test code indicating that the card is a test card, a "test card" function code is written to a transmission buffer before transmission processing is executed. Yes (routine R4
92 → R494).

Note that there are many routines common to the re-reading process and the card insertion process shown in the routine at the time of receiving the "reload" function in FIG. 246, and FIG. The processing is also shown.

FIG. 258 to FIG. 265 further show FIG.
7, card reading processing, magnetic processing, parity and LRC inspection processing, security inspection processing, punch hole inspection processing, card data inspection processing, date and identification code inspection processing, which appear in the card insertion processing routine and the re-reading routine shown in FIG. A flowchart is shown.

In the card reader of this embodiment, as described above, the security code reading sensor 810 is used.
a is disposed closest to the card insertion / ejection port, and when the sensor 810a faces the end of the security area (TF), the punch detection sensor SNSp still reaches the first punch hole formation location PH1. The distance between the sensors is determined so as not to cause this. Therefore, the security code is first read, and then the detection of the punched holes and the reading of the magnetic data are performed in parallel.

The program is configured so that the actual reading of the security code is performed by a timer interrupt triggered by the output of the encoder that detects the rotation speed of the motor. In the card reading process of FIG. 258, the routine R501 is executed. Preparation for security reading is performed in steps R523 to R523, and a flag for permitting the timer interrupt is set in the routine R524. Then, the process proceeds to magnetic code reading processing.

The card reader of this embodiment prevents the punched hole and the magnetic recording section from reaching the punched hole detection sensor SNSp and the magnetic head 821 until the rear end of the card reaches the first position detection sensor SNS1 at the time of insertion. The interval between each sensor is set. Therefore, in the magnetic code reading process of FIG. 111, after the position detection sensor SNS1 is turned on in the routine R545, the detection of the punched holes and the reading of the magnetic code are performed.

In reading magnetic data, a work area for storing data read bit by bit is operated as a shift register to convert the data into parallel data (routine R590). In addition, the card reader according to this embodiment includes the first and third position detection sensors SNS.
2, the distance l3 between the SNS3 is longer than the regular card length l0, and the distance l4 between the second and third position detection sensors SNS2, SNS3 is shorter than the regular card length l0. (See FIG. 32).

Therefore, during the 1-bit reading process shown in FIG. 260, the first to third position detection sensors SNS1 to SNS1
By checking the output of NS3, a card size defect is detected (routines R584 to R5).
87).

[1014] In the processing routine of Fig. 261, the routine R6 is executed.
In steps R03 to R609, exclusive OR of data, ETX, and LRC data in units of bytes is taken and successively entered into the work area. In the routine R611, it is determined whether or not the operation result is "0", thereby determining the LRC of the LRC. Checking.
Note that STX is set in the work area in the routine R604, and the first byte to be read out in the routine R605 is the ST.
Since it is X, the result is that STX is not included in the exclusive OR.

[1015] Since the parity bit (fifth bit of each data) is not subject to the LRC check, the routine is masked in the routine R610, and the process proceeds to the determination of R611. In FIG. 261, the routines R614 to R614 are executed.
At 620, a parity check is performed for each byte of data, and the parity check is repeated by the number of data (routines R621 and R622).

In the security inspection process shown in FIG. 262, the 10-bit security code read by the security sensor 810a and stored in the security buffer is divided into upper 5 bits and lower 5 bits. Is read, put into a shift register, and the parity is checked by counting the number of bits with "1".
The bits are read from the buffer and parity check is performed in the same manner (routines R639 to R645).

In the processing routine of FIG. 263, it is first determined whether or not the issued code in the read magnetic data is correct (routines R651 to R653), and then it is checked whether the punched holes are correctly opened (routines R651 to R6).
57). The issuing code is usually 5 on the game card.
1H, 52H is given to the resurrected or reissued card, and 53H is given to the test card. If the code is any other code, the processing shifts to error processing (routines R665 and R66).
6). If the issuance code is reissued, the process goes to the routine R661 to check whether a hole is opened at the reissue hole forming position of the card. If not, the card is processed as an invalid card (routines R662 and R664). Also,
It is impossible that both the issuing hole and the re-issuing hole are open, so that the card is eliminated in the routine R656, and the card having the zero return or settlement hole cannot be used for the game, so that the card is eliminated when inserted. (Routines R656 and R663).

In the card data inspection processing routine of FIG. 264, first, the company code in the magnetic data read from the card is compared with the code given as an initial value by the program (routine R671), and then the equipment in the magnetic data is compared. The code is compared with the code set by the code setting switch (routine R672) to determine a match, and then it is checked whether the security in the magnetic data matches the security code read from the authenticity discrimination area (routine R672). R674).

In the processing routine of FIG. 265, the identification code and the date code previously sent from the unit controller 190 as initial values are compared with the data read from the magnetic recording unit (routines R681, R682).
If they do not match, the cause of error and error information are written in the RAM, and then the process proceeds to error processing.

FIGS. 266 to 270 show a main control flow of the pachinko machine controller CPU1, and FIG. 271 shows an example of an interrupt control flow by a timer interrupt.

The task of the pachinko machine controller of this embodiment is to monitor the output signals of the five ball detection sensors of the launch sensor SNS5, the first and second safe sensors SNS2 and SNS3, the foul sensor SNS4 and the out sensor SNS1. The firing sphere and the returning sphere are distinguished, and only the signal of a fixed pulse width is recognized as a detection signal, and the number of detections of each sphere is counted, and the waveform-shaped detection signal of a fixed pulse width (launch signal, safe 1 signal , Safe 2 signal, foul signal and out signal)
The main content is to output to 0 at predetermined intervals.

More specifically, the output signal of each sensor is sampled in a 200 μs timer interrupt process to determine the presence or absence of a detection signal, and then the counter is updated. In the main control flow, the output control of the detection signal and each detection signal are performed. The minimum time interval (pause) between them is guaranteed.

First, the main control flow in FIGS. 266 to 270 will be described.

When the pachinko machine controller CPU1 is reset, it first clears the internal memory and then writes the check data into the memory (routine R801, R
802). Then, after setting a stack pointer to be a save area at the time of interruption, the timer is activated for the 200 μs timer to start the timer interruption shown in FIG. 271 (routines R803 and R804).

[1025] Thereafter, the flag is checked to determine whether or not the firing signal to be output to the unit controller 190 is being output (routine R805). If the firing signal is not being output, the flow advances to routine R806 to see the "pause" flag. Determine whether the output is paused. In the routine R807, by looking at the counter, it is determined whether or not there is a portion of the detected shooting spheres that has not output a firing signal. If there is any remaining firing signal output, the routine proceeds to routine R810, in which the number of remaining firing signal outputs is reduced by one, and then the firing signal output rises from a low level to a high level. Is set (routine R811). Then, after setting the firing signal output timer (5 mS), the process proceeds to the next sensor output process (FIG. 267).

[1026] Then, when the routine returns to the routine R805, it is determined that the firing signal is being output, and the routine R813 is executed.
Then, it is determined whether the output timer set in the routine R812 has timed out. Here, if the time is not over, the process directly proceeds to the next sensor output process. If the time is over, the output of the firing signal is lowered from the high level to the low level in the routine R814. As a result, a detection signal having a pulse width of 5 ms is formed. Also, the routine R81
In step 4, the flag indicating that the firing signal is being output is reset. Thereafter, the "pause" flag is set to "1", the pause timer (10 mS) is set, and the process proceeds to the next sensor output process (routine R815). , R816).

[1027] When the flow returns to the routine R805, the flow shifts to the routine R806. Here, it is determined that the pause is being performed, and the flow shifts to the routine R808. Here, it is determined whether or not the time of the pause timer is over. If the time is not over, the process directly proceeds to the next sensor output process. If the time is over, “pause” is performed.
After the flag is reset, the process proceeds to the routine R807 (routine R809). Thereby, even when the output of the sensor is continuous, a pause period of 10 ms is always provided, and the detection signal is transmitted to the unit controller 190 accurately.

[1028] Fig. 267 shows the procedure of the output processing of the safe 1 signal corresponding to the detection signal of the safe sensor SNS2.
This procedure is almost the same as the output processing of the firing sensor SNS5 in FIG.
A safe 1 signal having a pulse width of mS is output at intervals of at least 10 mS (routines R817 to R82).
8).

Following the same procedure, the output process of the safe 2 signal (routines R829 to R830 in FIG. 268)
Foul signal output processing (FIG. 269) Routine R831
R842), and an out signal output process (routines R843 to R854 in FIG. 270) is executed.

Next, the procedure of the timer interrupt processing of the pachinko machine controller CPU1 will be described with reference to FIG.

When the timer counter is started in the routine R804 in the main control flow of FIG.
A timer interrupt is started every time, and first, the routine R8
02 checks the check data written in the internal memory to check whether there is any abnormality in the memory (routine R90).
1). If there is an error in the check data, the CPU
It lowers its own power (routine R940). Then, since the watchdog pulse is not output,
Reset is performed by an external reset circuit RST1 (see FIG. 24).

On the other hand, when there is no abnormality in the check data, the routine proceeds to a routine R902, in which output signals of all five types of game ball sensors in the pachinko machine are read and then converted to positive logic (routine R903). That is, there are sensors that indicate "valid" when the output signal is low and those that indicate "valid" when the output signal is high.
The detection signals of all the sensors are converted to indicate valid at a high level. Thereafter, the on-edge of the sensor, that is, the change from off to on is detected by comparing the previous read data with the present read data (routine R9).
04). And the launch sensor, the first safe sensor, the second
It is determined whether or not all sensors of the safe sensor, the foul sensor, and the out sensor have an on-edge (routines R905 to R909), and the on-timer prepared for each sensor is cleared for the sensor that has detected an on-edge (routines R910 to R914). ). Then, after the on-timer of each sensor is updated (+1) (routine R915), it is determined whether or not each sensor has an off edge, that is, whether there is a change from on to off (routine R916 to R916).
R920).

When the off-edge of the firing sensor is detected in the above-mentioned routine R916, the flow shifts to a routine R921 to determine whether or not the sensor on-time is 0.4 ms or more and less than 3.0 mS. The counter that counts the remaining output of the firing signal (the number of firing spheres) is updated (+1) (routine R922). On the other hand, if the on-time of the firing sensor is 3.0 ms or more, it is regarded as a foul ball detection, and the counter for counting the remaining number of foul signal outputs is updated (+1) (routine R923,
R924). This is because, due to the configuration of the pachinko machine, a ball struck from the firing rail toward the inside of the game board may pass through the firing sensor in the opposite direction without returning to the foul ball receiving port 134 and return to the base of the rail. Because there is. Such a difference in the direction of the sphere can be detected by arranging two or more sensors along the rail, but the present inventors focused on the difference between the speed of the returning sphere and the speed of the firing sphere, and It was found that the firing sphere and the returning sphere could be distinguished by one sensor because it was always faster. Looking at this from the output time of the sensor, it was found that the sensor ON time when detecting a shooting ball having a high ball speed is 0.8 to 2.4 mS, and the ON time when detecting a returning ball having a low ball speed is several tens mS or more. Therefore, when the on-time of the firing sensor is 3.0 ms or more, it is regarded as a foul ball and the remaining number of foul signal outputs is updated.

On the other hand, the on time of the firing sensor is 0.4 ms.
If it is less than the threshold value, it is regarded as noise, and the routine R917 is executed without updating any of the counters of the firing signal and the foul signal.
The routine goes to (routine R923).

[1035] Also, the routines R917, R918, R9
When the first safe sensor, the second safe sensor, the foul sensor, and the off-sensor of the out sensor are detected at 19 and R920, respectively, the on-time of the sensor is set to 4.
It is determined whether it is 0 mS or more, and if it is 4.0 mS or more, the remaining output number of each detection signal is updated (+1) (routines R925 to R932).

[1036] After that, the output timer and the pause timer of each of the above sensors are updated in the routine R933, respectively.
The watchdog pulse is output, and the interrupt processing ends (Routine R934).

[1037] Next, control procedures in the unit controller 280, the card issuing controller 790, and the card reader controller 288 in the issuing machine 200 will be described in relation to data communication between them.

[1038] In the card issuing machine of this embodiment, the unit controller 290 can communicate only with the card issuing control device 790 and cannot directly communicate with the card reader control device 288. That is, the card reader control device 288 can communicate only with the card issuance control device 790. Therefore, the unit controller 29
0 and the card issuance control device 790 are communicated by a function code.
Communication between 90 and the card reader control device 288 is performed by a command. Incidentally, as the function code from the unit controller 290 to the card issuance control device 790, an "initial value setting" function for giving the card reader a date code and an identification code to be recorded in the magnetic recording section of the card, a function of the card A "card issue" function for issuing issuance and a "retransmission request" function for requesting retransmission of the function code sent immediately before, and a status indicating the status of the card reader received from the card reader controller 288 by the card issuing controller 790. Four types of commands of a "status request" function for requesting transmission are prepared.

[1039] The function code from the card issuing control device 790 to the unit controller 290 includes an "initial value request" function for requesting initial values such as a date and an identification code at the time of reset, and the instructed processing ends normally. Unit controller 29
"Normal end" function to notify 0 and conversely "abnormal end" to notify that processing did not end normally
The function and the “retransmission request” function for requesting the unit controller 290 to retransmit the function code sent immediately before and the “status transmission” for transmitting the status of the card reader in response to the “status request” from the unit controller 290 There are five types of functions.

[1040] Although not particularly limited, the above function code is transmitted between a start code of STX and an end code of ETX, and between the STX and ETX, a status and data to be transmitted are included in addition to the function code. There is also.

[1041] Specifically, the above [Table 36] and [Table 3] are included in the above "normal end" function, "abnormal end" function and "status transmission" function.
7], an 8-bit status 1 and status 2 column indicating the status of the card reader is provided, and the status is sent to the unit controller 290 together with the function code.

[1042] In the status 1 of [Table 36],
The transport unit sensor abnormality bit is set to “1” when any of the traveling position sensors CPS2 to CPS6 of the card issuing device 700 has failed.

On the other hand, a communication command from the card issue control device 790 to the card reader control device 288 includes a “magnetic write” command for recording magnetic data on the card, a magnetic data of the card, a security code, and a punch hole. A "magnetic read" command instructing to read each piece of information and sending magnetic data, a "security request" command instructing to send the read security data, and a "punch hole request" instructing to send the read punch hole data Command, a "reload" command for instructing rereading of data of the card held in the card reader, a "punch hole" command for instructing to punch a hole in the card,
A “card forward ejection” command to eject the card in the card reader toward the front insertion slot, a “card backward ejection” command to eject the card in the card reader backward, and a card reading command There are nine types of “cancel” command for canceling the status and “status request” command for instructing transmission of status information indicating the status of the card reader.

[1044] When the card reader control device 288 receives the above-mentioned command from the card issuance control device 790, it executes the corresponding processing and always returns a response. The types of response include: normal, communication error, command error, no magnetic recording data, magnetic data read failure, magnetic recording data error, security and magnetic data mismatch, company code or device code mismatch, magnetic write error, punch error, There are punch hole read error, security read error, punch dust full, motor error, RAM error, sensor error, card reader error, card length error, and card jam.

[1045] Although not particularly limited, the code indicating the command is transmitted between a start code of ESC and an end code of CR, and data to be transmitted is inserted between the ESC and CR in addition to the command code. Sometimes. The card reader controller 288 sends the card controller 79
The response to "0" is transmitted with a code indicating the type of error or an error code and requested data interposed between a start code STX and an end code CR.

FIGS. 272 to 279 show the card issuing machine 2
The specific control procedure of the main processing in the unit controller 290 of FIG.

[1047] When a reset signal is received, the unit controller 290 initializes the CPU, that is, clears the internal memory (RAM) and writes a check code at a predetermined address, and also executes a timer, an internal register, and an I / O port. Is cleared or set to a predetermined value (procedure P
C101). Then, it waits for the initialization signal INT to rise from a predetermined terminal of the unit memory 550 (procedure PC102). When this signal rises, the machine number of the issuing machine is read from the machine number setting unit 205, and the terminal is used by using the machine number. Calculate the serial number and channel number,
These numbers are written in the transmission data area of the unit memory 550 (procedures PC103 and PC104).

Next, it is determined whether or not the date in the reception data area of unit memory 550 is "0" to wait for reception of a "line test" packet (procedure PC10).
5). That is, until the “line test” packet containing the date is sent from the management device 400, the date field in the unit memory is “0”, and when the packet is received, the date is changed to “0”. Since it is no longer “0”, it is possible to know whether a “line test” packet has been received by monitoring this date.

[1049] Upon receiving the "line test" packet, unit controller 290 sets the initial value unset bit of monitor information 1 (see [Table 12]) in the transmission data area to "1" (procedure PC106). This bit is cleared to "0" when an "initial value setting" packet or a "unit recovery data" packet is received.
Then, the unit controller 290 checks whether or not there is a packet received from the management device 400 by referring to the command register CR2 in the communication area of the unit memory 550 (procedure PC107). Packet reception processing (procedure PC
201 to PC209), and then execute procedure P
Proceed to C108.

[1050] In the procedure PC 108, the unit memory 55
It is checked whether the reservation flag in the transmission data area of “0” is “0”.
No. 4 card number reservation processing (procedures PC211 to PC22)
After performing 7), the process proceeds to the procedure PC 109.
However, when the procedure PC 109 is first reached, the reservation flag is set to “0” by the initialization of the procedure PC 101, so that the card number reservation process is executed first.

[1051] In the procedure PC 109, the bill validator 210
Check the signal BUSY during the insertion of the banknote from the banknote, and check for the presence or absence of the insertion of the banknote.
C231 to PC264) and then the next procedure PC
Proceed to 110.

[1052] The procedure PC 110 checks whether or not there is a packet registered as an unprocessed packet in the internal memory. If there is no unprocessed packet, or if there is an unprocessed packet, the packet receiving process of FIG.
After executing C209), the procedure moves to the procedure PC111.

[1053] The procedure PC 111 checks from the card issuance control device 790 whether an "initial value request" function is included.
Returning to step 107, if any, the procedure PC 112 transmits an "initial value transmission" function containing the date and the identification code, and then returns to procedure PC 107 to repeat the above procedure.

FIG. 273 shows an example of a specific procedure of the packet receiving process in the flow of FIG. 272.

[1055] When there is a received packet, the unit controller 290 first sets the received packet to "initial value setting".
It is determined whether or not the packet is a packet (procedure PC201). If the packet is an "initial value setting" packet, the initial value setting process (procedures PC271 to PC274) shown in FIG.
The process shifts to C209, where the command register CR2 in the unit memory 550 is cleared to notify the data transmission controller 551 that the packet has been received.

[1056] If the received packet is not the "initial value setting" packet, it is determined whether it is a "unit recovery data" packet (procedure PC202), and if yes, the unit recovery processing shown in FIG. 277 (procedure PC281 to PC28).
8) is executed, and the process proceeds to the procedure PC 209.

If the received packet is neither "initial value setting" nor "unit recovery data", it is determined whether or not "ACK" is received (procedure PC203). If "ACK" is received, nothing is done. The process directly proceeds to procedure PC 209. The “ACK” packet received at this time is “ACK” other than when the unit controller 290 transmits the packet to the management device 400 and waits for a response.
This is because

[1058] When the received packet is "AC"
If it is not "K", the process proceeds to procedure PC 204, where it is checked whether the initial value unset bit in monitor information 1 is "1". Here, if the initial value unset bit is “1”, the procedure proceeds to the procedure PC 209;
Go to 5. This is to prevent the issuing machine from erroneously starting the issuance operation when the “opening code” or the “forced termination release” packet comes in before the “initial value setting” packet is received.

[1059] The procedure PC 205 determines whether or not the received packet is a "store opening code" packet.
Forcible termination release processing shown in FIG.
293). When the received packet is not the “opening code”, the received packet is “forcibly terminated” by the procedure PC 206.
Judgment whether or not, if yes, forced termination cancellation processing PC
291 to P293, if no, PC 207
Proceed to.

[1060] In procedure PC207, it is determined whether or not the received packet is a "closure code". If yes, the forced termination process (procedures PC295 to PC297) shown in Fig. 279 is executed. If it is not "Close code", PC2
At 08, it is determined whether or not the received packet is a “forced termination request”,
If yes, force termination processing PC295-PC297
And if no, the procedure PC20
The process proceeds to 9 to clear the command register CR2 in the unit memory 550.

FIG. 274 shows a specific procedure of the card number reservation processing in the flow of FIG. 272.

Here, it is first determined whether or not the initial value unset bit of the monitor information 1 in the unit memory 550 is “1” (procedure PC211). Here, if the bit is "1", the initial value has not yet been received from the management device 400, so that the process returns to the original routine (FIG. 272) without doing anything. Then, a “card purchase” packet containing only the issue receipt number with the issue serial number set to “0” is transmitted. It should be noted that, as the issuance acceptance number, a number obtained by adding 1 to the number of issued cards in the card issuing machine 200 is used. The management apparatus 400 determines the issue serial number n by adding the number of times of issuance of all issuers under its management.

Next, the unit controller 290 operates as follows:
After setting the 0-second timer, it is determined whether or not the timer has timed out. If the timer is not set, the command register CR1 in the unit memory 550 is checked to determine whether a packet has been received from the management device 400 (procedures PC213 to PC213).
215). If a packet has not been received, the process returns to the procedure PC 214 to determine again whether the 10-second timer has expired. When the time is over before receiving the packet, the procedure PC 21
The flow goes to 9 to fix the common signal of the amount indicator 213 to a low level or a high level, thereby stopping the output of the watchdog pulse. Incidentally, when this pulse is stopped, a reset signal is generated by the reset circuit 555, and the unit controller 290 and the data transmission controller 553 are reset.

[1064] If a packet is received before the timer set in procedure PC 213 times out, the procedure advances from procedure PC 215 to PC 216 to determine whether or not the received packet is "ACK".
It is determined whether the received packet is "AK" (procedure PC 217), and if the received packet is neither "ACK" nor "NAK", it is registered as an unprocessed packet in the internal memory (procedure PC 218). The presence / absence of the processing packet is determined by the procedure PC 110 in the main flow of FIG. 272, and the processing packet is processed.

If the received packet is determined to be "NAK" in procedure PC 219, the procedure proceeds to procedure PC 219, where the watchdog pulse is stopped and reset.

On the other hand, if the procedure PC 216 determines that the received packet is “ACK”, the procedure proceeds to procedure PC 221 to set the reservation flag to all “1”, and then sends the amount to the card issuing control device 790. Send "Card issue" function as "0" (procedure PC
222).

Then, it is determined whether a "normal end" function has been received from the card issuing control device 790 (procedure PC223).
To determine whether the "abnormal termination" function has been received. If NO here, the procedure returns to the procedure PC 223 again to repeat the above-described determination. When the “normal end” function is received, the procedure proceeds to the procedure PC 225 to start the blinking of the bill insertion lamp 223 and then return to the original routine (FIG. 2).
Return to 72).

When the procedure PC 224 receives the "abnormal termination" function, the monitor display 206 displays an error number indicating the content of the error, waits for the recovery of the error state, and returns to the procedure PC 222 after the recovery. Then, the “card issuance” function is transmitted to the card issuance control device 790 again.

[1069] When the card issuance control device 790 receives the "card issuance" function with the amount of "0",
Take out the card from the card tank, record the magnetic data including the card number in the magnetic recording unit, and after interrupting the issuance hole, stop the process when three “0” s except for the thousands are printed and suspend. It is moving.

[1070] FIG. 275 shows a specific procedure of the card purchase processing in the flow of FIG. 272.

[1071] When detecting that a bill has been inserted into the bill validator 210, the unit controller 290 first checks whether or not the bill insertion lamp 223 is in a blinking state (procedure PC231). Returning to the original routine (FIG. 272), if the PC is blinking,
Move to the procedure of 232 or less. The above bill insertion lamp 2
23 is a procedure PC2 during the card number reservation process described above.
25 or PC in forced termination release processing in FIG. 278
Since the blinking starts at 293, the card purchase processing is executed after the reservation processing of the card number is completed or after the "forced termination release" packet is received.

[1072] The procedure PC 232 gives the bill accepting instruction signal STACK to the bill validator 210,
The amount of money is read from the bill validator 210, and the lamps LMP1 to LMP5 with built-in switches are shown to indicate the purchase selection switch 212 that can be purchased according to the amount of money (LMP1 for 1,000 yen, LMP1 for 5,000 yen,
To LMP5) (procedure PC233).

Next, it is determined whether the inserted bill is less than 5,000 yen (procedure PC234), and if it is 5,000 yen, the procedure PC236 is executed.
Turn off the bill insertion lamp 223 at
The process proceeds to C237, and if it is less than 5,000 yen, procedure PC236 determines whether the next bill is inserted. This is because it is possible to purchase a high-priced card by continuously inserting bills. Here, when the insertion of the next bill is detected, the procedure returns to the procedure PC 232 again to give a bill taking instruction, turn on the purchase lamp corresponding to the total bill, and determine whether the total bill is less than 5,000 yen. I do.

If the inserted amount reaches 5,000 yen or the next bill is not inserted, the flow shifts to procedure PC 237 to determine whether or not any of purchase selection switches 212 has been turned on. Here, when the selection switch 212 is not turned on, the process returns to the procedure PC 234, and waits without shifting to the next procedure until the purchase selection switch is turned on.

[1075] Thereafter, when the purchase selection switch 212 is turned on, the bill insertion lamp 223 is turned off, and then all the built-in lamps other than the switch that was turned on are turned off (procedures PC238 and PC239). Next, card issuing port 2
After the blinking of the card issuing lamp 224 provided in the banknote 02 is started, it is determined whether or not there is a change. When there is a change, the blinking of the bill payout lamp 225 provided in the bill payout port 232 is started. (Procedure PC240-PC2
42). In the card issuing machine of this embodiment, the bill validator 2
This is because a card that can distinguish between 1,000 yen, 5,000 yen, and 10,000 yen is used as 10, and an issuance card can be issued up to 5,000 yen per thousand yen.

On the other hand, when there is no change, the procedure PC 241
To PC 243 to proceed to the next procedure without blinking the lamp, and determine whether the reservation flag is "0".

If the reservation flag is “1”, the value selected by the purchase selection switch 212 is entered in the column of the amount of money in the next procedure PC 244, and the card number and the serial number of FIG. A “card purchase” packet in which the reservation number received from the management device 400 in the reservation process and the number of issuances sent to the management device 400 at the time of reservation are entered in the column of the issuance reception number, respectively.
Send to On the other hand, when the reservation flag is “0”, the selected value is added to the amount column, and the number of issued items is added to the issuance number column.
A value “1” is entered, and the “card purchase” packet in which the card number and the issue serial number are each “0” is stored in the management device 400.
Send to It is assumed that a bill is inserted before the issuing machine reserves a card number.

[1078] Unit controller 29 after packet transmission
0 determines whether the time is over after setting the 10-second timer.
To determine whether a packet has been received from the PC (procedure PC
246-P248). If no packet has been received, the procedure returns to procedure PC 247 to check the timer.
If the "ACK" packet does not return within the time-out, that is, within 10 seconds, the process proceeds to procedure PC252 to stop the output of the watchdog pulse.

If the packet is received within the time, it is determined whether or not the packet is "NAK". If the packet is "NAK", the flow shifts to procedure PC252 to stop the output of the watchdog pulse.

Further, if the received packet is not "NAK", it is checked whether it is "ACK". If not, it is registered as an unprocessed packet in the internal memory and returns to procedure PC 247 to set the timer again. To check. Then, only when the received packet is “ACK”, the procedure shifts to procedure PC 253 to increment the number of issuances, and then sets the reservation flag set to “1” in procedure PC 221 of the reservation processing flow to “0”. Yes (procedure PC254).

[1081] After that, the unit controller 290
After transmitting the "card issuance" function including the card number, the issue serial number and the purchase price to the card issuance control device 790, it waits for a response from the "normal end" function (procedures PC255 to PC257). If an "abnormal end" response is sent from the card issuing control device 790 before the "normal end" response, the unit controller 290 displays an error number indicating the content of the error on the monitor display 206, and then displays an error. Wait for the state to recover (procedure PC263, PC264).

On the other hand, when the "normal end" function returns after the card issuance command, the card issuance lamp 224 blinked by the procedure PC 240 is turned off.
It is determined again whether change has been made, and if change has been made, a change payout command signal is given to the bill payout device 230 (procedure P
C258-PC260). Then, the procedure PC242
After turning off the banknote payout lamp 225 blinking with, the received amount in the transmission data area of the unit memory 550,
The deposit amount and the payout amount are calculated and updated (procedures PC261 and P262). If there is no change, the procedure jumps from PC259 to PC262 and returns to the original routine (FIG. 272).

FIGS. 276 to 279 show specific procedures of the initial value setting processing, unit recovery processing, forced termination cancellation processing, and forced termination processing shown in the flow of FIG. 273, and are sent from the management apparatus 400. The corresponding processing is executed according to the received packets.

FIG. 276 shows the processing when an “initial value setting” packet is received. The unit controller 290 first copies the head portion of the received packet written in the received data area of the unit memory 550 to the transmission data area. By doing so, a portion that becomes the head of the packet at the time of transmission is created, and the hot code of the reception data area is copied to a predetermined address of the transmission data area (procedures PC271 and PC272).

Next, by clearing the initial value unset bit of the monitor information 1 in the transmission data area set to "1" by the procedure PC 106, it is clearly indicated that the unit controller 280 has received the initial value. Transmits an "initial value transmission" function to the card issuance control device 790, and returns to the original routine (procedures PC273 and PC2).
74).

When the "unit recovery data" packet is received, the processing in FIG. 277 is started. First, the packet type in the reception data area and the received recovery data are copied to the area corresponding to the transmission data area, and then the unit is copied. Command register C in communication area of memory 550
The transmission command of the "ACK" packet is written in R2, and the data transmission controller 551 is instructed to transmit the packet (procedures PC281 and PC282).

Next, after setting a timer (10 seconds), an "initial value transmission" function is sent to the card issuance control device 790 (procedure PC283, PC284). Then, it waits for the reception of the packet from the management device 400, and returns “ACK”
If a predetermined packet ("restart" packet) is not transmitted within a predetermined time (10 seconds) after transmission, the output of the watchdog pulse is stopped and the self-reset is performed (procedures PC285 to PC287). When the "restart" packet is transmitted within 10 seconds, FIG.
The procedure PC209 in step 3 clears the command register CR2 and then returns to the main routine in FIG.
C288).

FIGS. 278 and 279 show the management device 400
2 shows a process when a “forced termination release” packet or a “forced termination” packet is received.

[1089] When the unit controller 290 receives "forced termination release", it first sets the bit indicating "operating" in the operation information of the issuing machine, and then issues the issuance stop lamp 2
22 is turned off, the issuing lamp 221 is turned on, and the bill insertion lamp 223 is started to be turned on (procedures PC291 to PC291).
PC 293). On the other hand, when the "forced end" packet is received, the bit indicating "in operation" in the operation information is cleared, the issue stop lamp 222 is turned on, and the issue lamp 221 is turned on.
Is turned off, and then the bill insertion lamp 223 is turned off (procedures PC295 to PC297).

FIG. 280 shows the unit controller 29
0 shows a procedure of a timer interrupt process executed by a timer interrupt separately from the main process (FIG. 272).

The unit controller 290 operates as shown in FIG.
When an interrupt signal is received at an interval of 1 ms from the internal timer set by the procedure PC 101 in the flow of step 1, the check code written in the internal memory is first read by the procedure PC 101 to check whether the code has changed. If the internal memory is checked and there is any abnormality, procedure P
Reset is performed by jumping to C124 and omitting the output of the watchdog pulse (procedure PC12
1). When the internal memory is normal, the procedure PC 122
After outputting a watchdog pulse after updating the timer in step, data for dynamically displaying the money amount display 213 is output and the interrupt processing is terminated (procedure PC
123, PC 124).

Although not shown in the flowcharts of FIGS. 272 to 280, the unit controller 290
When the function is received from the card issuing control device 790, the code is checked, and if there is an error, a "retransmission request" function is transmitted.

FIG. 281 shows a card issuance control device 790
2 shows a control procedure such as a card issuance.

[1094] When the card issuance control device 790 is reset, the internal memory, registers, I / O ports and the like are first cleared and initialized, and then a timer (ex. 10 seconds) is set, and "initial value request" The function is transmitted to the unit controller 290 (routines RN101 to RN101).
RN103). Next, it is checked whether a function from the unit controller 290 has been received, and if not, it is determined whether or not the timer set in the routine RN102 has expired (routines RN104 and RN105). Then, the routine RN104, RN104 until the time is over
5 is repeated, and if the time is over, the routine RN1 is executed.
Returning to step 02, the timer is reset and the "initial value request" function is transmitted again. First, "Initial value request"
This is because the unit controller 290 may not yet be ready for reception at the time of transmitting the function.

[1095] After receiving the function from the unit controller 290 after transmitting the function, the routine shifts from the routine RN104 to the RN106 to check whether or not the received function is an "initial value transmission" function. After transmitting the function, return to the routine RN102,
Retransmit the "Request Initial Value" function. This is because a specific process such as issuing a card is accurately executed after first receiving an initial value from the unit controller 290.

[1096] If the function received in the determination of the routine RN106 is "initial value transmission", the flow advances to the routine RN108 to store the date and identification code sent together with the function code in the internal memory. Thereafter, the initial value unset bit of the status register also prepared in the internal memory is cleared, and the "normal end" function is transmitted to the unit controller 290 (routines RN109 and RN110).

After that, the routine RN111 waits for the reception of the next function from the unit controller 290. When the function is received, the process proceeds to the routines RN112 to RN115 to determine which function has been received. If the function is the "send value" function, the identification code is stored, and then the "normal end" function is sent (routine RN1).
16, RN117), and when the function is the “card issuance” function, the card issuance processing of FIG.
121 to RN129). If the received function is "retransmission request", the routine RN
At 118, the previously transmitted function is retransmitted, and if it is a "status request", a "status request" function is transmitted at routine RN119. Routine R
The reason for determining again whether or not the function is the “initial value transmission” function in N112 is that the function returns to the routine RN111 after execution of error processing (see FIG. 289) described later (reference numeral V).
1) is considered.

FIG. 282 shows a specific procedure of the card issuing process in the flow of FIG. 281.

[1099] Upon receiving the "card issuance" function from the unit controller 290, the card issuance control device 790 first checks the sensor 761a in the printing device 750 to determine whether or not there is a card waiting in the printing device. (Routine R121). Here, if there is no card, it is checked in the next routine R122 whether the amount in the "card issuance" function is "0", and if yes, the card removal processing routines RN201 to RN2 shown in FIG.
12, the reader control processing routines RN213 to RN227 in FIG. 284, the card inversion processing routines RN288 to RN243 in FIG. 285, and the print 1 processing routines RN245 to RN266 in FIG. 285 are executed. It transmits to the controller 290 and returns to the original routine (FIG. 282) (routine RN129). As a result, an issuance reservation process is executed in which one card is taken out from the card tank, magnetic data is written, and the printing device stands by in a state where all the data except for the thousands of purchases are printed by the printing device.

If the routines RN121 and RN122 determine "no card" and "$ 0", respectively, the card removal processes RN201 to RN212, the reader control processes RN213 to RN227, and the card inversion process RN2.
28 to RN243, print 1 processing RN245 to RN266
And the card ejection processing RN268 to RN28 in FIG.
After executing 0, the counter 795 for counting the number of cards removed is counted up, and a "normal end" function is transmitted (routines RN123, RN129). In this way, a card can be issued when a "card issue" function containing an amount of money is sent before the card number reservation. Such a situation occurs, for example, when only the card reader is turned off and the unit controller 29
0 or the power of the card issuance control device 790 is turned on, the process proceeds, and thereafter, the power is turned on to the card reader.

On the other hand, in the routine RN121, the printing device 75
When it is determined that there is a card (reserved card) within 0, the routine goes to the routine RN124, where the card number of the already reserved card is compared with the card number sent by the "card issue" function. If the card numbers do not match, the stacking processes RN281 to RN299 shown in FIG. 288 are executed to store the reserved card in the confiscation tank 780, and then the number of cards taken out and the number of stacked cards are counted. One counter 79
5,796 is updated (routine RN125). This is to avoid inconsistency between the issued card data and the card file data in the management device 400. afterwards,
It is determined whether or not the amount is “0” (routine RN12
6) If the amount is zero, the print 1 process RN24 from the card removal processes RN201 to RN212 next to the routine R122
5 to RN266 to execute the card issuance reservation processing. If it is determined in the routine RN126 that the amount is not “0”, the card removal processes RN201 to RN201 to R
From N212, the card discharge processing RN268 to RN280 is executed, and the card is issued immediately without card reservation.

[1102] On the other hand, if the card numbers match in the above routine RN124, the flow shifts to routine RN127 to determine whether or not the amount is "0". Here, if the amount is "0", the process goes to the routine RN129 without any operation and transmits the "normal end" function. If the amount is not "0", FIG.
86 print 2 processing (routines RN126 to RN266)
After executing this, the card ejection process RN26 is executed.
8 to RN280 are executed to update the card takeout number counter and then transmit the "normal end" function (routines RN128, RN129). That is, the printing and discharging of a thousand digits of the amount of money on the card waiting for the reservation are performed by the procedures of the routines RN127 to RN128.

Note that the above routines RN121 and RN12
In step R4, it is determined that "there is a reserved card" and "card number matches", and then, in the routine R127, it is determined that "amount = 0".
80 is turned off, turned on again, and the management device 400
After receiving the “unit recovery data” packet from
The unit controller 290 controls the card issuance control device 79
This occurs when a “card issue” function for card reservation is transmitted to “0”.

[1104] FIG. 283 shows a specific procedure of card ejection processing in the card issuing function reception processing flow of FIG. 282.

[1105] Here, first, it is checked whether there is a card in the card tank 701 by looking at the card presence / absence sensor 703 (routine R201). If the sensor is off, that is, the tank is empty, the routine jumps to the routine RN212 to jump to the internal memory. After setting the take-out device abnormal bit of status 2 in the “1” to “1”, the processing shifts to the error processing routine of FIG. 289.

[1106] If there is a card in the card tank 701, the routine shifts from the routine RN201 to RN202 and sends a "magnetic write" command to the card reader control device 288. Then, after setting the timer, the clutch solenoid 729 is turned on, and the take-out motor 719 is set.
Is rotated (routines RN203 and RN204). Thereby, one card is sent out from the card tank.

[1107] Next, it is checked whether or not the timer set in the routine RN203 has timed out.
It is checked whether the traveling position sensor CPS1 has been turned on (routines RN205, RN206). First traveling position sensor CPS
When 1 is off, the routine returns to the routine RN 206 to repeat the timer check. Thus, the first traveling position sensor C
When the time is over before the sensor is turned on, the routine jumps to the routine RN211 to set the traveling position sensor 1 abnormality bit of the status 1 to "1", and then sets the status 2 extraction device abnormality bit to "1". After setting to “1”, the flow shifts to the error processing routine of FIG. 289.

On the other hand, if the first traveling position sensor CPS1 is turned on before the time is over, the routine RN20
7, the clutch solenoid 729 is turned off, and the card is sent out from the tank to the roller 712.
Then, the transmission of the rotational force is stopped to prevent the feeding of two cards, and it is again checked whether the timer set in the routine RN203 has timed out (routine RN208). Then, the first traveling position sensor C
It is checked whether or not the PS1 has been turned off. If the sensor is turned off within a predetermined time, it is determined that the card has been removed from the card tank 701 and has been normally delivered, and the removal motor 719 is stopped to terminate the processing and return to the original routine. It returns to (FIG. 282). If the traveling position sensor CPS1 is not turned off within a predetermined time, it is determined that the card is jammed halfway, and the routine shifts to the routine RN211 to set the traveling position sensor 1 abnormality bit of status 1.

[1109] FIG. 284 shows a specific procedure of the reader control processing in the card issuing function reception processing flow of FIG. 282.

In this flow, first, after setting a timer, before the timer expires, it is checked whether or not there is a response to the "magnetic write" command transmitted by the routine RN202 in the card removal processing flow (routine). RN213 to RN215). And
If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormality bit of the status 2 to "1", and shifts to the error processing routine of FIG. 289.

If the response from the card reader control unit 288 is received within a predetermined time, the routine RN21
6 to check whether the response is normal or not. If there is an error, the routine RN227 is executed in the same manner as when the time is over.
Jump to and execute error handling. On the other hand, if the response is normal, a "punch hole" command containing data indicating the position of the issued hole is transmitted to the card reader control device 288, and the timer is set (routines RN217, RN217).
218). Then, it is checked whether or not there is a response from the card reader control device 288 before the timer times out (routines RN219, RN22).
0). If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormality bit of the status 2 to "1", and shifts to the error processing routine of FIG. 289.

If a response is received from the card reader control device 288 within a predetermined time, the routine RN221
Then, it is checked whether the response is normal. If there is an error, the process jumps to the routine RN227 as in the case of time over, and executes error processing.

On the other hand, if the response is normal, a "card rear ejection" command is transmitted to the card reader control device 288 to set a timer (routines RN222 and RN22).
3). Then, it is checked whether there is a response from the card reader control device 288 before the timer times out (routines RN224, RN22).
5). If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormality bit of the status 2 to "1", and shifts to the error processing routine of FIG. 289.

If the response from the card reader control device 288 is received within a predetermined time, the routine RN22
6 to check whether the response is normal or not. If there is an error, the routine RN227 is executed in the same manner as when the time is over.
Jump to and execute error handling. On the other hand, if the response is normal, the process returns to the original routine (FIG. 282).

FIG. 285 shows a specific procedure of the card inversion process in the card issuing function reception process flow of FIG. 282.

In this process, first, the transport motor 706 is rotated forward, a timer is set, and it is checked whether or not the second traveling position sensor CPS2 is turned on before the timer times out (routines RN228 to RN).
231). Then, within the time, the second traveling position sensor CPS
If No. 2 is not turned on, the routine jumps to the routine RN242 to set “1” to the jam error bit of the status 1 and “1” to the card transport error bit of the status 2 in the routine RN243. To the error handling routine of.

On the other hand, the second traveling position sensor C
When PS2 is turned on, the routine RN232, RN2
33 and before the timer set in the routine RN229 times out, the second traveling position sensor CPS
Check if 2 is off. When the second traveling position sensor CPS2 is turned off, it means that the card has passed the traveling path switching piece 745.

Therefore, the second traveling position sensor CP
If S2 has not been turned off, the routine jumps to the routine RN242 to set the jam abnormality bit of the status 1 to "1".
Further, the routine RN243 sets "1" to the card transport error bit of status 2 and then shifts to the error processing routine of FIG. 289.

[1119] The second travel position sensor C
When PS2 is turned off, the process proceeds to the routine RN234, a new timer is set, and then the transport motor 706 is rotated in the reverse direction (routine RN235). As a result, the card is transported in the reverse direction, and is guided by the runway switching piece 745 to the runway toward the printing device 750.

[1120] After the transport motor reversely rotates, the card issuance control device 7
90 checks whether the second traveling position sensor CPS2 is turned on again before the timer set in the routine RN234 times out (routine RN23).
6, RN237). If the second traveling position sensor CPS2 does not turn on within the time, the routine RN242
Then, the process jumps to and sets "1" in the jam error bit of status 1 and "1" in the card transport error bit of status 2 in the routine RN243, and then proceeds to the error processing routine in FIG. 289.

On the other hand, the second traveling position sensor C
When PS2 is turned on, the routine RN238, RN2
39, the second travel position sensor CPS is executed before the timer set in the routine RN234 times out.
Check if 2 is off. If the second traveling position sensor CPS2 has not been turned off within the time, the routine jumps to the routine RN242 to set the jam abnormality bit of the status 1 to "1", and the routine RN243 sets the card abnormality bit of the status 2 to "1". ”Is set, and then the process proceeds to the error processing routine of FIG. 289. Further, when the second traveling position sensor CPS2 is turned off within a predetermined time, the process proceeds to routines RN240 and RN241, and whether or not the third traveling position sensor CPS3 is turned on before the timer set in the routine RN234 times out. It is checked if the sensor is turned on within the time, and the routine returns to the original routine (FIG. 282).

FIG. 286 shows a specific procedure of the print 1 process (including the print 2 process) in the card issuing process flow of FIG. 282.

[1123] Here, the timer is set first, and then
Before the timer times out, it is checked whether or not the fourth traveling position sensor CPS4 has been turned on (routines RN245 to RN267). Fourth travel position sensor CP
If the time is over before S4 is turned on, the routine jumps to routines RN265 and R266, sets "1" in the jam error bit of status 1, and sets "1" in the printer error bit of status 2. After that, the flow shifts to the error processing in FIG. 289.

If the fourth traveling position sensor CPS4 is turned on before the time is over, the routine RN
Proceeding to 248, the print motor 751 is rotated,
Before the time over occurs, the third traveling position sensor CPS
3 is turned off (routine RN24)
9, RN250). Here, when the time is over, the routine jumps to the routine RN265 and shifts to error processing. When the third traveling position sensor CPS3 is turned off within a predetermined time, the transport motor 706 driven by the routine RN235 in FIG. 285 is stopped. Then, before the time is over, it is checked whether or not the fourth traveling position sensor CPS4 is turned off (routines RN251 to RN253).
Here, when the time is over, the routine jumps to the routine RN265 as described above. On the other hand, if the fourth traveling position sensor CPS4 is turned off before the time is over, the routine proceeds to a routine RN254, in which the elevation motor 758 of the print head is moved.
Is rotated 180 ° to lower the head. Then, after printing the identification code, the date, and the number other than the thousandth digit of the purchase amount, that is, “000” by the print head 756, whether the amount data transmitted with the “card issue” function code is “0” or not. A determination is made (routines RN255 to RN258).

If the amount is "0", the routine R
In step 259, the printing motor 751 is stopped with the print head 756 lowered, the movement of the card is stopped, and the printing apparatus 750 waits. If the amount is not "0", the flow advances to routine RN261 to print a thousand-digit number of the amount, and then the head elevating motor 7
58 is again rotated by 180 ° to raise the print head 756, and a new timer is set (routine RN26).
2). Thereafter, it is checked whether or not the fifth traveling position sensor CPS5 is turned on before the timer times out (routines RN263, RN264). After setting "1" to the printer error bit of status 2 and "1", the process proceeds to the error processing of FIG. 289. On the other hand, if the fifth traveling position sensor CPS5 is turned on before the time is over, the process returns to the original routine (FIG. 282).

[1126] Furthermore, this flow also shows the print 2 process in FIG. 282. That is, in the card issuance processing of FIG. 282, when the reserved card is waiting in the printing device 750, the “card issuance” function is received, and the card number in the function matches the card number of the reserved card in standby. If the amount is not "0", the printing motor 75 is immediately executed in the routine RN260 of FIG.
1 is started to move the card, and the following routine RN2
By executing 61 to RN 264, the thousands of digits of the remaining money are printed, and then the process returns to the routine of FIG. 282 and shifts to the card discharging process. Thus, when the banknotes are actually inserted into the card issuing machine 200, the execution of the routines RN245 to RN258 in FIG. 286 is omitted, and only one character is printed on the reservation card which has already been printed up to a value other than the thousands digit. By immediately discharging the paper money, the apparent time required from the insertion of the bill to the discharge of the card can be greatly reduced.

FIG. 287 shows a specific procedure of the card ejection process in the card issuing process flow of FIG. 282.

When this process is started, first, the lead-out solenoid 779 in the card lead-out device 770 is turned on to rotate the track switching member 777 downward, and then the transport motor 70
6 is started and a timer is set (routines RN268 to RN270). Thereby, the printing device 7
The card sent out from the card 50 is transferred to the card issuing port 202 through the dispensing device 770. And
If the fifth traveling position sensor CPS5 is turned off before the timer set in the routine RN270 has timed out, the printing motor 751 in the printing device 750 is stopped (routines RN271 to RN273). This is because the card has already been sent from the printing device 750. If the time runs out before the fifth traveling position sensor CPS5 is turned off, the routine R279, RN28
The status transitions to 0, the status error jam bit of status 1 and the card transport error bit of status 2 are set to “1”, and the process proceeds to the error processing of FIG. 289.

[1129] In the above routine RN273, the print motor 7
After stopping the 51, the timer set in the routine RN270 is checked again, and if the sixth traveling position sensor CPS6 immediately before the card issuing port 202 is turned on before the time is over, the derived solenoid 779 is turned off ( Routines RN274 to RN276). If the timer times out before the sixth traveling position sensor CPS6 is turned on, the routine shifts to the routine RN279.

[1130] Solenoid 77 derived in routine RN276
After turning off No. 9, a new timer is set, and after 0.5 seconds, the transport motor 706 is stopped. 0.5 above
The second is determined from the relationship with the rotation speed of the transport motor 706, and the transport belt 77
2 is enough time to move the card a distance equal to its full length l0. By waiting 0.5 seconds after the sixth traveling position sensor CPS6 detects the card, the card is stopped in a state where it is protruded about two thirds from the card issuing port 202. The sixth traveling position sensor CPS6 is turned off when the player manually pulls out the card from the issuing port 202.

FIG. 288 shows a specific procedure of the stack processing in the card issuing processing flow of FIG. 282.

[1131] The card issuance control device 790 executes the routine R
If it is determined in N121 that there is a reserved card in the printing device 750, but the received card number does not match the card number of the waiting card, this stacking process is executed, and the head lifting motor 758 of the printing device 750 is first turned on. 1
The print head 756 is raised by rotating by 80 ° (routine RN281). Then, a timer is set and the printing motor 751 is rotated to start the transfer of the card, and then the timer is checked (routines RN282 to RN
285). If the timer times out before the fifth traveling position sensor CPS5 at the exit of the printing device 750 is turned on, it is determined that a card is jammed in the printing device 750, and the process proceeds to the routines RN296 and RN297 to return to status 1 289 is set to each of the jam error bit and the status 2 printing device error bit, and then the flow shifts to the error processing in FIG. 289.

If the fifth traveling position sensor CPS5 is turned on before the timer expires, the flow advances to routine RN286 to rotate the transport motor 706 in the reverse direction to start transport of the transport belt 772 of the card dispensing device 770. Then, set a new timer. Then, if the timer is checked and a time-out occurs before the fifth traveling position sensor CPS5 is turned off, the routine jumps to the routines RN298 and R299 to set the status 1 jam error bit and the status 2 card confiscation device error bit respectively. After setting “1”, the process shifts to the error processing of FIG. 289 (routines RN288 and RN28).
9).

On the other hand, if the fifth traveling position sensor CPS5 is turned off before the timer times out, the routine proceeds to the routine RN290, where the printing motor 751 is stopped. Thereafter, the timer set in the routine RN287 is checked again, and if the time is over before the card full sensor 783 in the card deriving device 770 is turned on, or the time is over before the card full sensor 783 is turned on but turned off ( Routine RN291RN2
94), after executing the routines RN298 and RN299, shifts to the error processing routine of FIG. 289. If the card full sensor 783 is turned on within a predetermined time after setting the timer, and if the card full sensor 783 is subsequently turned off, the process proceeds to the routine RN295 and stops the transport motor 706.

In this stacking process, unlike the card ejection process in FIG. 287, since the lead-out solenoid 779 is not turned on before the drive of the transport motor 706, the runway switching member 777 in the card lead-out device 770 has the card issuing port 202.
Motor 706 with the traveling path toward
Is driven. As a result, the transport belt 77
The card transferred in 2 is guided into the lower confiscation tank 780, and is detected by the card full sensor 783 on the way.

[1136] FIG. 289 shows error processing executed when a time-over occurs before various sensors CPS1 to CPS6 for detecting the position of the card are turned on or off in the processing flows of FIGS. 283 to 288. The specific procedure is shown.

In this process, first, the card issuing device 700
All motors (extraction motor 719, transport motor 7
06, printing motor 751 and head lifting / lowering motor 75
8) is stopped, and an “abnormal termination” function is transmitted to the unit controller 290 (routine RN1).
51, RN152). Next, the unit controller 29
It is determined whether or not the function has been transmitted from 0 (routine RN153). If the function has not been received, it is determined whether or not the error has been recovered by checking the sensor in the card issuing device 700 (routine RN154). ), If not recovered, routine RN15
Wait for the error to recover by returning to step 3. If the cause of the error disappears while waiting for the recovery, for example, the card stuck in the card issuing device 700 is removed, the process proceeds to the routine RN155 to clear each abnormal bit of the status 1 and 2 to “0”. And then the routine RN156
Then, the counters 79 and 796 for counting the number of cards taken out and the number of cards confiscated are updated, and the process returns to the routine RN111 in the main processing flow (FIG. 281) (see reference numeral V1).

On the other hand, when a function from the unit controller 290 is received while an error is being recovered in the routines RN153 and RN154, the processing shifts to the routine RN157 to determine whether or not the received function is a "status request" function. If the answer is yes, the "status transmission" function is transmitted in the next routine RN158, and the process returns to the routine RN153 and waits until the error is recovered again. If the function received during the error recovery wait is not “status request”, it is determined in the routine RN159 whether or not the received function is “initial value transmission” function. Is stored in the internal memory, the "normal end" function is transmitted, the routine returns to the routine RN153, and the system waits for an error recovery again (the routines RN160 and RN16).
1).

If the function received while waiting for error recovery is neither “status request” nor “initial value transmission”, the routine returns from routine RN159 to RN152, transmits an “abnormal termination” function, and then performs error recovery. wait.

Next, an example of a control procedure of the card reader 800 of the issuing machine 200 by the card reader control device 288 based on a command from the card issuance control device 790 is shown in FIG.
This will be described with reference to FIGS. It should be noted that the flow of this embodiment can be commonly used as any control flow on the assumption that the same card reader as that of the issuing machine is used for the settlement machine 300 and the management device 400.

[1141] The major difference from the control flow relating to the card reader in the control unit 160 of the pachinko machine 100 is as follows.
It has a control flow for writing and verifying a magnetic code and a flow for ejecting a card to the rear of the card reader instead of to the front.

[1142] As described above, the card reader control device 2
Communication between the unit controller 88 and the unit controller 290 is performed by command transmission as described above. As a communication command from the card issue controller 790 to the card reader controller 288, magnetic data of the card is recorded. "Magnetic write" command to read, and "magnetic read" command to read the magnetic data and security code and punch hole information on the card and send magnetic data, and send the read security data A "security request" command, a "punch hole request" command to send the read punch hole data, a "reload" command to re-read the data of the card held in the card reader, Instructs the user to punch holes "Punching" command, "Card backward ejection" command to eject the card in the card reader toward the front insertion slot, and "Card forward ejection" to eject the card in the card reader backward. A command, a "cancel" command for canceling the card read command, and a "status request" for instructing transmission of status information indicating the status of the card reader
There are nine types of commands.

[1143] Of these, "magnetic read" and "reload"
The command is not used in the issuing machine 200, and "magnetic write"
The command is not used in the checkout machine 300 or the management device 400. The “magnetic read” command is transmitted to the card reader 8.
00 is instructed to read not only magnetic data but also all data on the card, and requests transmission of only magnetic data. Data request commands are separately prepared for security data and punch hole data.

FIG. 290 shows the card reader controller 28
8 are the same as those shown in FIGS.
08 shows the detailed procedure, and FIGS.
0 and FIG. 311 show a control procedure of an interrupt process generated by an interrupt separately from the main control.

[1146] When a reset is applied, that is, when the reset input terminal changes to a low level, the card reader control device 288 first stores the internal memory containing various flags, counters, buffers, work areas, registers, etc., as shown in FIG. Clear (routine R1101). Then, after setting the stack pointer when an interrupt occurs, initializing the I / O port and setting the state of the input / output terminals, the setting code is read from the device code setting device MCS and stored, and then the card transport motor is set. The relay RLY1 for supplying power to the power supply 807 is turned on (routines R1102 to R1102).
1105).

[1146] Next, the monitor display 175 for displaying the cause of the error is turned off, the power-on lamp LED 21 for turning on the power is turned on, and the "card insertion prohibition" flag in the built-in RAM is set to "1". (Routines R1106 to R1108). Then, after permitting the reception buffer to receive the command from the card issuing control device 790, it is checked whether or not the command has been received (routines R1109 and R1110).

If there is no received command, the flow shifts to the routine R1117 to check whether the "card insertion waiting" flag is set to "1". If "0", the flow returns to the routine R1110 to receive the command. When the "card insertion waiting" flag is "1", the card reading process shown in FIG.
Return to 110. The card reading process is the same as the process when the “magnetic reading” command is received. The flowchart of this embodiment is designed so that it can be used in common when the same card reader 800 as the pachinko machine 100 or the issuing machine 200 is used for the checkout machine 300 or the management device 400. The flow to the "read process" is conscious of the control in the settlement machine 300 and the management device 400. In the flow of the issuing machine 200, the "card insertion waiting" flag is set to "0" all the time. Not done.

[1148] In the payment machine 300, the "store opening code"
When a “card accepted” function is sent to the card settlement controller 312 based on the reception of the packet, and a “magnetic read” command is sent from the card settlement controller 312 to the card reader controller 388, the routine R1 is executed.
At 110, it is determined that a command has been received, and the flow advances to the routine R1111.
By jumping to 1118 and proceeding to R1121, the type of command is determined, and the flow shifts to the magnetic reading process of FIG. 291. Further, the card reading process of FIG. 300 is executed from the routine R1202. Is OFF, the card is not read, the "card not read" flag is set, and the routine R1203 to R1 is executed.
At step 204, the "card insertion waiting" flag is set, and the routine shifts to the routine R1122 → R1117 of FIG. 290, and shifts again to the processing of FIG. 291. In other words, it waits for the card to be inserted for a long time.
Is executed.

On the other hand, if it is determined in the routine R1110 that a command has been received and if the received data is not "ESC" indicating the beginning of the command in the routine R111,
In the routine R1112, it is determined whether or not the command is the cancel command “CAN” of the previously transmitted command. Unlike the other communication commands, the cancel command “CAN” does not have the start code ESC and the end code CS, and is transmitted by the command code itself, so that such determination can be made. If the received command is not "CAN" in the routine R1112, the routine R1117
Then, if "CAN" is reached, the next routine R1 is executed.
Proceeding to 113, the "card insertion prohibition" flag is set, the card holding lamp is turned off, a code indicating normal end is set in the transmission buffer, and the transmission processing of FIG. After the transmission to 790, the "card insertion wait" flag is cleared and the routine returns to the routine R1110. As a result, the card insertion waiting state due to the “magnetic read” command transmitted from the card issuance control device 790 before that is canceled.

[1150] Thereafter, the command is received again, and the process proceeds to the routine R1111. If it is determined that the command head code is received, the process jumps to the routine R1118 to prohibit the subsequent command reception, and then the monitor display 206 of the card reader is displayed. The OK lamp indicating the reception state of the card reader control device 288 is turned off (routine R11).
19, R1120). Then, in a routine R1121, it is checked whether or not the received command corresponds to any of the nine commands described above.
"Command error" as error information in memory at 124
308, and then proceeds to an error processing routine shown in FIG. 308. If the command corresponds to the registered command, the corresponding process is executed, the OK lamp is turned on, the process returns to the routine R1109, and the above procedure is performed. It repeats (routine R1122, R1123).

FIG. 291 shows a processing procedure when a “magnetic read” command is received, and FIG. 292 shows a processing procedure when a “reload” command is received.

[1152] These command processes are executed by the card issuing machine 20.
Since 0 is irrelevant, the description is omitted.

FIG. 293 shows the processing procedure of the card reader controller 288 when receiving the “magnetic write” command.

When this command is received, first, the magnetic recording data sent in the form of ASCII code together with the "magnetic write" command is converted into a binary code suitable for internal processing and stored in the magnetic data buffer of the internal memory. Then, the head code STX (see FIG. 4) indicating the head of the magnetic data is inserted at the head of the magnetic data buffer, and the head code STX next to the magnetic recording data in the magnetic data buffer (the twenty-first code when the number of magnetic data is 20). ) Is filled with an ETX code indicating the end of data (routines R1231 to R123)
3). Next, after setting the number of magnetic data to be written (22 including the LRC calculated in the next routine), an address for sequentially reading magnetic recording data from the saved magnetic data buffer is set in the address counter ( Routine R1234, R1235).

Thereafter, the STX code (0BH) is set in a predetermined register A in advance in a routine R1236, and the exclusive OR of the data in the register A and the next magnetic data is determined in the routines R1237 to R1244. The process of re-entering the calculated data into the register A is repeated until the magnetic data is exhausted, so that the LRC code, which is the error check code of all the magnetic data, is finally left in the register A. Since the STX code (0BH) is initially set in the register A in the routine R1236, the first exclusive OR operation is performed (routine R1238).
Then, the same data is calculated, the result is all "0", and the same result as when STX is not included in the LRC calculation is obtained, so that the initial purpose can be achieved.
In the processing of the routines R1237 to R1248, LR
Simultaneously with the calculation of C, it is determined whether the number of ON bits (bits of “1”) in each read data is odd or even. If the number is even, the parity bit in each data is set to “1” and stored in the data buffer. By saving, addition of a parity (odd parity) bit is also performed (routines R1239 to R1241). After the LRC and parity bit calculation processing, a code indicating STX is inserted at the end (24th) of the magnetic data buffer (routine R1245). That is, the magnetic data and ETX and L
The RC is sandwiched between two STX codes (see FIG. 4).

Next, the data (LC
R), the parity bit is set to "1" only when the number of ON bits is even or odd, and the parity bit is also added to the LRC itself. (Routine R1246)
ＲR1248).

Thereafter, the write processing (routines R1301 to R1337) shown in FIG. 303 is executed to output magnetic data and a write clock, and the verify processing (routines R1341 to R1361) shown in FIG. After checking whether or not the data has been correctly written, it is determined whether or not a verify error has been detected (routine R1249). If an error has occurred, a magnetic write error is set as error information in the memory, and then FIG. (Routine R1)
251).

[1158] If there is no verify error, a "normal" response command is set in the transmission buffer, and then the transmission processing shown in FIG. 307 (routines R1421 to R1426).
And returns to the main flow of FIG. 290.

FIG. 294 shows the card issuing control device 790
Shows the control procedure of the card reader control device 288 when receiving a "status request" command from the PC.

[1160] When the "status request" command is received, the device code stored in the internal memory and the contents of status 1 are transferred to the transmission buffer, and a code indicating the end of the command is sent to the address next to the last data in the transmission buffer. C
After setting R, STX is set as transmission data and is transmitted first (routines R1261 to R126).
4). Thereafter, the address of the transmission buffer is set in the counter, and one byte of data is read from the transmission buffer using the address and transmitted. Then, the address of the transmission buffer is updated (routine R1265).
-R1268). Then, it is determined whether or not the CR code has been transmitted. If no, the process returns to the routine R1266 to transmit the next data, and the transmission of the CR code ends the processing for the “status request” command (routine R1).
269).

In FIG. 295, “Punch hole request” is displayed.
FIG. 296 shows a control procedure when a command is received, and FIG. 296 shows a control procedure when a "security request" command is received. Response processing for these commands (R1271-R1279 and R1281-R1
289) is exactly the same as the response process to the “status request” command in FIG. The difference is
The only difference is that first, punch hole data or security data read from the card and held in the internal memory is transferred to the transmission buffer instead of the content of the device code and the status 1.

FIG. 297 shows a control procedure of the card reader control device 288 when receiving a “punch hole” command from the card issuance control device 790.

When this command is received, a reference is made based on the punch hole position set in the RAM by the initialization routine or the like based on the data indicating the hole to be punched (in this case, the issued hole) sent with the command. The distance from the position is read from the ROM and stored in the buffer (routine R1
291), and then performs a punching process (R311 to R311) in FIG.
352). Then, the "punch OK" flag is checked to determine whether or not the punching has been performed reliably (routine R1292). If yes, a normal response command is set in the transmission buffer (routine R1293), and FIG.
7 is executed, and if no, the punch failure bit of status 1 is set to "1", punch error is written in the error information, and the process proceeds to the error processing routine of FIG. 308 (routines R1294 and R1295).

FIG. 298 shows a control procedure in the card reader control device 288 when receiving the “card backward ejection” command.

When this command is received, a one-second timer is first set, and then the motor 807 is rotated forward at high speed (routines R1401, R1402). Then, it checks whether the timer set in the routine R1401 has timed out, and then checks whether or not the rearmost position detection sensor SNS4 in the card reader has been turned on (routines R1403, R1404). If a time-out occurs before the position detection sensor SNS4 is turned off, the process jumps to the routine R1413 to stop the motor 807 and then checks whether all the sensors are off (routine R1414). If at least one of the sensors in the card reader is turned on, "1" is set to the card jam bit of status 1 and a card jam error is written as error information, and then the process proceeds to the error processing routine of FIG. Transition. If all the sensors are turned off in the routine R1414, it is determined that the discharge is completed, and the process jumps to the routine R1407.

On the other hand, before the timer set in the routine R1401 times out, the position detecting sensor SNS
When the motor 4 is turned off, wait 0.4 seconds before starting the motor 807.
Is stopped (routine R1403). The card reversing device 740 behind the card reader is driven, and the card reader 8 is turned on.
This is to wait for the card sent from 00 to be conveyed by the card reversing device 740.

After stopping the motor 807, the card jam bit of status 1 is cleared, the "verify error" flag set in the routine R1351 of FIG. 304 is cleared, and then the card holding LED is turned off (routines R1407 to R1409). ). Thereafter, the "card insertion prohibition" flag is set to prohibit insertion of the next card, and after setting the code of the "normal" response command in the transmission buffer, the transmission processing of FIG. 307 is executed (routine R
1410, R1411).

FIG. 299 shows the card issuance control device 790
The following describes the processing procedure of the card reader control device 288 when a "card forward ejection" command is received from the PC.

This process is a flow prepared because it is necessary in the card settlement machine 300.
Is not executed, and the description is omitted.

[1170] FIGS. 300 and 301 show FIGS.
The specific procedure of the card reading process, the parity, and the LRC inspection process in the “magnetic reading” command reception flow of
Further, FIG. 302 shows a specific procedure of the magnetic processing in the flow of receiving the "reload" command in FIG. 292, but these processings are also executed in the card settlement machine and not in the card issuing machine. Is omitted.

FIG. 303 shows the specific procedure of the writing process in the flow of FIG. 293.

In this process, first, the rear end of the card is moved to the position of the position detection sensor SNS1 on the entrance side of the card reader 800, and then the number of magnetic data (ex. 24)
Is set in the counter (routines R1301, R13
02). At this time, the head of the card has not reached the position of the magnetic head 821. Then, after setting the head address of the magnetic data buffer containing the magnetic recording data in the address counter, the motor 807 is rotated at a high speed to turn on the write enable signal for the magnetic head 821 (high level).
(Routines R1303 to R1305). afterwards,
Erase data "0" for providing a non-data area at the beginning and end of the track TRC2 of the magnetic data recording section is set, a 200 ms timer is set, and then the "write interrupt" flag is set to "1". Set to start a write interrupt every 806 μsec (routines R1306 to R130
8). The write interrupt is set to occur every 806 μsec (when the card transport speed is 300 mm / S) according to a detection signal from an encoder that detects the rotation of the motor 807.

Next, after checking the timer set in the routine R1307, the write clock data is inverted, and the "write wait" flag is set to "1". It waits until it is cleared to "0" (routines R1309 to R1312). Then, it is checked whether or not the position detection sensor SNS3 disposed slightly behind the magnetic head 821 is turned on (routine R1313). If it is off, the process returns to the routine R1309, and the above procedure is repeated until the sensor SNS3 is turned on. By repeating the above loop, the write clock data is inverted every time the write interrupt is executed once every 806 μsec. As a result, the direction of magnetization of the magnetic portion of the card by the magnetic head is inverted every 806 μs, and clock data twice as long as 1.612 msec is written to the track TRC1 of the card. In addition,
The position of the position detection sensor SNS3 is determined such that the magnetic head comes to the STX code writing start position of the track TRC2 when this sensor detects the end of the card. When the sensor SNS3 is turned on, the next routine is executed. The process proceeds to R1314 to start writing magnetic data. If the timer set in the routine R1307 has timed out before the sensor SNS3 is turned on, it is determined that the card is jammed, and the routine R1303 is executed.
The program jumps from 9 to R1336, sets the card jam bit of status 1 to "1", writes the card jam in the error information, and shifts to the error processing routine of FIG. 308 (routine R1337).

If the position detection sensor SNS3 is turned on before the time is over, the flow advances to routine R1314, where the number of bits (5 bits) of each data (including parity) is first set in the counter, and then the routine R1303 is executed.
The 1-byte (8-bit) magnetic recording data is read from the magnetic data buffer by using the address set in the step (1) and is inputted into the shift register as the parallel-to-direct conversion means, and the address counter is incremented (routine R1315)
R1316). Then, the data in the output buffer is
The bits are further shifted left by one bit for a total of three bits (routines R1317 and R1318). This places the most significant bit of the 5-bit magnetic data at the left end of the shift register.

Then, next, in the routine R1319, the bit at the left end of the shift register is turned on, that is, "1".
It is determined whether or not “0”, the write data is inverted in the next routine R1320, and if “1”, the process jumps to the routine R1321 without inversion. Thus, a write signal of the NRZI system can be formed and output.
Following the output of the write data, the routine R1
The output of the write clock is also executed in the same procedure as that performed in steps 310 to 1312 (routines R1321 to R1).
323). Of these, the write data is on the second track TRC2 of the card, and the write clock is on the first track TC2.
Write to RC1 respectively.

[1176] After the output of the 1-bit data, the bit counter is decremented to determine whether the counter has become "0". If not, the flow returns to routine R1318 to return the magnetic data in the shift register by one bit. By repeating the process of shifting to the left and outputting the data until the bit counter becomes "0", the 5-bit parallel magnetic data is converted into serial write data and output (routine R1324, R1325). And 1
When the output of the byte magnetic data is completed, the routine R1
Proceeding to 326, the number of magnetic data is decremented by one, and then the flow returns to routine R1314 to repeat the parallel-to-direct conversion and output of the next magnetic data. (Routine R132
7).

[1177] In the routine R1328, a timer of 100 ms is set, and then the routine R1309 to R13
The write clock data is output until the position detection sensor SNS4 is turned on in accordance with the same procedure as in step 13 (routines R1329 to R1333). That is, even after writing the STX code as the last data of the magnetic data to the second track TRC2 on the first track TRC1 of the card, the clock data continues to be written until the end of the card (see FIG. 4). Since the magnetic data is not inverted on the second track after the writing of the magnetic data is completed, the direction of the magnetization is fixed and the data is erased.

On the other hand, if the position detection sensor SNS4 is turned on before the timer is over in the routine R1329, the process proceeds to the routine R1334, where the write permission signal to the magnetic head 821 is turned off (low level), and then the rotation of the motor 807 is stopped. Stop and end (Routine R133
5). If the timer set in the routine R1328 times out before the position detection sensor SNS4 is turned on, the routine jumps to the routine R1336, sets the card jam in the status 1 and the error information, and then proceeds to the error processing routine of FIG. Transition.

[1179] FIG. 304 shows a specific procedure of the verify process performed subsequent to the write process of FIG. 303.

Here, first, the motor 807 is rotated backward to retract the card until the rear end of the card is detected by the first position detection sensor SNS1 in the card reader, and then a one second timer is set (routine R1341, R
1342). Then, the motor 807 is rotated forward at high speed, the number of magnetic data is set (here, the next STX code of the LRC is not checked, so that the number is 23), and the second address of the magnetic data buffer is set in the address counter ( Routines R1343 to R1344). This is for excluding the first STX code from the target of verification.

After the address is set, the 1-bit reading process shown in FIG. 305 is executed to determine whether the data read in the routine R1346 and stored in the work area matches the STX code, and waits until the data matches. It proceeds to the routine R1347. In the routine R1347, 5 bits are set in the bit counter, 1 bit of the magnetic data is read by the 1-bit reading process of FIG. 305, the bit is shifted into the least significant bit of the work area, and the bit counter is decremented. The process is repeated until the bit counter becomes "0", that is, until 5 bits are read (routines R1347 to R1349).

Then, the magnetic data read from the magnetic data buffer is compared with the magnetic data read from the card and stored in the shift register by using the address set in the counter in the routine R1345 (routine R1350). Here, if the two data do not match, a verify error is set in the error information in the routine R1351, and if the data matches, the routine jumps from the routine R1350 to R1352 to increment the address counter of the magnetic data buffer. Routines R1347 to R1353 are repeated until the number of magnetic data becomes "0" by subtracting "1" from the number of magnetic data (routine R1354).

If the number of magnetic data becomes "0", the flow advances to routine R1355 to clear the 1-bit read latch and erase the read data. Then, the 1-second timer set in routine R1342 is reset. It is determined whether a time-over has occurred (Routine R1356).
In the next routine R1357, it is determined whether the position detection sensor SNS4 has been turned on. If the position detection sensor SNS4 is turned on before the time is over, the routine proceeds to a routine R1358, where the card jam bit of status 1 is cleared and then the motor 807 is stopped (routine R1359).

On the other hand, if a time-over occurs before the position detection sensor SNS4 is turned on, "1" is set in the "card jam" bit of status 1 and then the card jam is written in the error information. Shift to processing routine (routines R1360, R136
1).

FIG. 305 shows the specific procedure of the 1-bit reading process common to the verification process flow of FIG. 304 and the magnetic process flow of FIG. 302.

In this process, the 1-bit read latch is first cleared (routine R581), and then the size of the card is inspected based on the outputs of the sensors SNS1 to SNS4 in the card reader (routines R582 to R5).
88). Then, it is checked whether magnetic data is latched in the read latch cleared in the routine R581, and if it is, the work area to which the latch data is transferred is shifted left by one bit and the least significant bit is set to zero. Transfer the data of the latch and finish (Routine R
589-R590).

In the card reader of this embodiment, the distance l3 between the first and third position detection sensors SNS2 and SNS3 is longer than the regular card length l0, and the second and third position detection sensors SNS1 and SNS3 The distance l4 is the regular card length l0
The distance between sensors is set to be shorter than
(See FIG. 32). Therefore, during the one-bit reading process shown in FIG.
By checking the output of SNS3, a card size defect is detected (routines R584 to R584).
587).

FIG. 306 shows a specific procedure of the hole punching process in the “punch hole punching” command reception flow of FIG. 297.

In this hole making process, first, the card is moved to the innermost position of the card reader 800 (routine R311) to clear the "punch OK" flag (routine R312).
After that, the motor is reversed to start the timer (3 seconds) (routine R313), the "movement amount detection" flag is set, and then the movement amount counter is cleared (routine R31).
4-R318). Then, the "timer 2 operation" flag is set to permit the timer interrupt, the movement amount is detected by the timer interrupt, and the rotation of the motor is stopped when the punching position is reached (routines R319 to R322). After waiting for 150 msec (routine R323) to wait for the stop, the punch device 820 is operated.
(Routines R324 to R327). The above routine R323
After R327 is repeated twice to make sure that the hole is opened (routine R328), the moving amount counter is cleared, the motor is reversed at high speed, and the punched hole that is opened faces the punched hole detection sensor SNSp. move. Then, it is determined whether or not the punch hole detection sensor is ON. If the punch hole is opened at a regular position, "Punch OK" is displayed.
After setting the flag, the first position detection sensor SNS
When 1 is turned on and the rear end of the card is detected, the timer interrupt is stopped and the motor is stopped (routines R329 to R340).

In the above routine, if a time-out occurs while the card is moving, it is determined that a card jam (paper jam) has occurred, and error processing is started (routines R315 and R332).

FIG. 307 shows “Magnetic writing” in FIG. 293.
299, the processing flow when receiving the “punch hole” command in FIG. 297, the processing flow when receiving the “card backward ejection” command in FIG. 298, and FIG. 299.
A specific procedure of the transmission process of the response command in the processing flow at the time of receiving the “eject card forward” command is shown below.

In the transmission processing, first, the reception of the reception buffer is prohibited, and then the start address of the transmission buffer is set in the counter (routine R1421, R1422). Next, the transmission data saved in the transmission buffer during each flow is read and transmitted for one byte, and then the address counter of the transmission buffer is incremented (routine R1423, R1424). Thereafter, it is determined whether or not the code CR indicating the end of the response command has been transmitted (routine R1425). If not, the process returns to the routine R1423 to sequentially transmit the next one-byte data. , And then returns to the original routine (routine R1426).

On the other hand, FIG. 308 shows FIGS. 290 and 291.
299 and FIGS. 300 to 306 show specific procedures of error processing executed when an error occurs.

In this error processing, monitor display data, ie, an error display code (see [Table 7]) corresponding to the error information written according to the content of the error that has occurred in each flow is read out from the internal memory and Is output to the monitor display 175 to display the type of error (routine R1131, R1132). And OK
The lamp is turned off, the "write inhibit" flag is set to "1" to inhibit the magnetic data write process, and then the timer 2 interrupt is stopped to inhibit the magnetic read process (routine R
1133-R1135).

Then, after stopping the motor 807 in the card reader 800, the shutter solenoid 809 is turned off and the shutter is closed to prohibit the card from entering, the response code corresponding to the type of error ([Table 7] (See right column)
Is transmitted (routines R1136 to R1138), and FIG.
The process returns to the routine R1109 in the main flow of 90 (see reference numeral V2).

Next, FIGS. 309 and 310 show the processing procedure when a read interrupt occurs, and FIG. 311 shows the processing procedure when a write interrupt occurs.

As described above, in the card reader 800 of this embodiment, the detection signal from the sensor 832 for detecting the rotation speed of the motor 807 is input to the card reader control device 288 as an interrupt signal. When this signal comes in when the "timer 2 operation" flag in the controller is set to "1" in the routine R524 in the card reading processing flow, FIGS. 309 and 3
When the "write interrupt start" flag is set in the routine R1308 during the write process flow of FIG. 303, the timer 2 interrupt process of FIG.
Is executed.

The speed sensor 832 is provided so as to face the rotary encoder 817 attached to the rotating shaft of the motor 807. An interrupt signal is input every time the card moves 0.1 mm regardless of the rotating speed. .

In the timer 2 interrupt processing, first, in the routine R7
01: "Security read" flag and "Punch hole read"
When all the flags are "0", the mode is the movement amount detection mode, the routine proceeds to routine R710, the movement amount counter is incremented, and the interrupt processing ends. Note that the movement detection mode is set when it is desired to know the movement amount of the card from the reference position during the magnetic processing (routine R572) in FIG. 302 and the punching processing (routine R317) in FIG. 306. The movement amount detection mode is set by clearing the “security reading” flag and the “punch hole reading” flag.

If the "move amount detected" flag is "0" after entering the timer 2 interrupt processing, the flow advances to routine R702 to increment the move amount counter, and then the "security reading" flag is set in routine R703. Check if it is set, and if it is set, the routine R7
04, it is determined whether or not the movement amount is 4.8 mm or more (when the “security reading” flag is “0”, FIG.
Then, the process proceeds to a punch hole reading routine of No. 10. The "security reading" flag is set when the punch hole sensor SNSp is turned on in the routine R523 during the card reading process in FIG. 300, and at this time, the security code reading sensor 810a sets the security area (TF) of the card. Located at the beginning. Thus, the first security mark is provided at a position at least 4.8 mm away from the beginning of the security area. Therefore, it is determined in the routine R704 that the movement amount has become 4.8 mm or more. If the distance is 4.8 mm or less, the interrupt processing is terminated, and the moving amount counter is incremented again by the next timer 2 interrupt. When the movement amount reaches 4.8 mm, the routine R
The process then proceeds to step 711, where the movement amount and the routine R519 are first determined.
Compares with the reading range set in the RAM, determines if the security code reading sensor is on if it is within the reading range, and if it is on, increments the counter that counts the width of the security code and interrupts The process ends (routines R712 and R713).

When the code reading sensor is turned off, the value of the counter is checked (routine R714). If the width of the security code is "0", it is determined that there is no code, and the interrupt processing ends. On the other hand, security width is “0”
If not, the width of the counter is transferred to the buffer and then the counter is cleared, and it is determined whether or not the security width is 0.5 mm or more (routines R715 and R716). here,
If the width is 0.5 mm or less, it is regarded as abnormal. If the width is 0.5 mm or more, "1" is set to the most significant (or least significant) bit of the security buffer operated as a shift register.

If the next timer interrupt is entered and the reading is out of the reading range in the routine R711, the process proceeds to the routine R721 as the end of reading of the first code, and the security reading number (counter) is decremented. Then, the security buffer storing the read code is shifted by one bit in the routine R723, and then the read range is added by the security code pitch (3.5 mm), and the processing is terminated. By shifting the security buffer every time one bit of security is detected, the serially read security code is converted into parallel data. By repeating the above routine, when the security reading number becomes “0”, the routine R722
Then, the process proceeds to R714, where the read security width is 0.
When it is 5 mm, "1" is written to the most significant bit of the security buffer. Then, after the security reading, the process proceeds to the magnetic data reading process, and the routine R553 in FIG. 302 is executed.
When the timer 2 interrupt shown in FIG. 309 is started after the "punch hole reading" flag is set to "1" and the "security reading" flag is cleared to "0", the routines R703 to R731 in FIG. Then, it is checked whether or not the punch hole detection sensor is ON. If the sensor is ON, the counter for counting the punch hole width is incremented in a routine R732, and the interrupt processing is terminated. And
If the punch hole detection sensor is turned off by the next interruption, the flow shifts to routine R733 to check the punch hole width. Here, when the detected width of the punched hole is 0.8 mm or more, it is regarded as a regular punched hole, and the highest level (or the highest level) of the buffer (operated as a shift register) storing the presence or absence of the punched hole is determined in the routine R734. After writing "1" to the (lower) bit, the punch hole width is 0.8mm again
In the following cases, the punch hole width counter is cleared in the routine R735, and then the routine proceeds to the routine R736.

Here, it is determined whether or not the card moving amount is within the reading range. If the moving amount is within the reading range, the above-described procedure is repeated.

In the routines R741 to R745, first, the buffer containing the read bits is shifted by one bit by subtracting the number of punched holes read, the punched hole width counter is cleared, the read range is set again, and the processing is terminated. And
When the number of readings becomes "0", the "timer 2 operation" flag is cleared and the subsequent timer 2 interrupt operation is stopped (routine R742, R746).

On the other hand, after the "write interrupt start" flag is set in the routine R1308 during the write processing flow of FIG. 303, when a detection signal comes in every 806 .mu.S from the rotation detection sensor 832 of the motor 807 of the card reader. The write interrupt processing of FIG. 311 is started, and first, the write clock data set in the routine R1310 or R1330 or the write data and write clock data set in the routines R1320 and R1321 in the flow of FIG. 303 are output (routine R7).
51). Thereafter, the "write waiting" flag set in the routine R1311, R1322 or R1331 is cleared and the write interrupt processing is terminated (routine R75).
2).

[1206] Next, the unit controller 3 of the settlement machine 300
The control procedure in 50, the card settlement controller 312 and the card reader controller 388 will be described in connection with data communication between them.

In the card settlement machine of this embodiment, the unit controller 390 can communicate with the card settlement control device 312 and cannot directly communicate with the card reader control device 388. That is, the card reader control device 388 can communicate only with the card settlement control device 312. Communication between the unit controller 390 and the card settlement controller 312 is performed by a function code, and communication between the card settlement controller 312 and the card reader controller 388 is performed by a command. Incidentally, as the function code from the unit controller 390 to the card settlement controller 312, an “initial value setting” function for giving the card reader a date code and an identification code for collating with the magnetic data read from the card, "Card accepted" function to allow card reader to accept card, "Card unacceptable" function to instruct card reader to stop accepting card, "Card eject" to instruct card eject "Function," Reload "function to instruct the card to re-read magnetic data,
"Retransmission request" function for requesting retransmission of the function code sent immediately before, card settlement controller 3
12, a "status request" function for requesting the transmission of the status indicating the status of the card reader received from the card reader control device 388, and a settlement hole P indicating that the card settlement has been completed at a predetermined position in the punch hole forming area.
Nine types of functions: a "card forfeiture" function that gives a command to confiscate (discharge backward) the card after punching H5 and a "payment" function for giving a command to eject the card to the insertion slot side (front) after the settlement hole is formed Directives are provided.

[1208] The function code from the card settlement controller 312 to the unit controller 390 includes an "initial value request" function for requesting an initial value such as a date and an identification code at the time of reset, and the instructed processing ends normally. Unit controller 39
"Normal end" function to notify 0 and conversely "abnormal end" to notify that processing did not end normally
Function, “Card number” function code for sending the card number read by the card reader to the unit controller 390, “Resend request” function for requesting the unit controller 390 to resend the function code sent immediately before, inserted card The card reader controller 390 determines that the card is illegal and sends a card reader status in response to a "self-ejection" function to notify that the card has been ejected by itself and a "status request" from the unit controller 390. There are seven types of "status transmission" function.

[1209] Although not particularly limited, the above-mentioned function code is transmitted between a start code of STX and an end code of ETX, and between the STX and ETX, status and data to be transmitted are included in addition to the function code. There is also.

[1210] Specifically, the above [Table 35] and [Table 3] are included in the "normal end" function, the "abnormal end" function and the "status transmission" function.
6], an 8-bit status 1 and status 2 column indicating the status of the card reader is provided, and the status is sent to the unit controller 390 together with the function code.

[1211] The "self-discharge" function is provided with a column for entering an 8-bit code indicating the cause of fraud as shown in [Table 37], and is sent together with the function code. .

[1212] On the other hand, as a communication command from the card settlement controller 312 to the card reader controller 388, a "magnetic write" command instructing recording of magnetic data on the card, a magnetic data of the card, a security code, and a punch hole are provided. A "magnetic read" command instructing to read each piece of information and sending magnetic data, a "security request" command instructing to send the read security data, and a "punch hole request" instructing to send the read punch hole data Command, a "reload" command for instructing rereading of data of the card held in the card reader, a "punch hole" command for instructing to punch a hole in the card,
A “card forward ejection” command to eject the card in the card reader toward the front insertion slot, a “card backward ejection” command to eject the card in the card reader backward, and a card reading command There are nine types of “cancel” command for canceling the status and “status request” command for instructing transmission of status information indicating the status of the card reader.

[1213] When the card reader control device 388 receives the above-mentioned command from the card settlement control device 312, it executes the corresponding processing and always returns a response. The types of response include: normal, communication error, command error, no magnetic recording data, magnetic data read failure, magnetic recording data error, security and magnetic data mismatch, company code or device code mismatch, magnetic write error, punch error, There are punch hole read error, security read error, punch dust full, motor error, RAM error, sensor error, card reader error, card length error, and card jam.

Although not particularly limited, the code indicating the command is transmitted sandwiched between a start code of ESC and an end code of CR, and between the ESC and CR, there is data to be transmitted in addition to the command code. Sometimes. A response from the card reader control unit 388 to the card settlement control unit 312 is transmitted between the start code STX and the end code CR, with the code indicating the type of the error or the error code and the requested data interposed therebetween. It is supposed to.

FIG. 312 shows a specific control procedure of main processing in the unit controller 390 of the card settlement machine 300.

When a reset signal is received, the unit controller 390 initializes the CPU, that is, clears the internal memory (RAM), writes a check code at a predetermined address, and operates a timer, an internal register, and an I / O port. Is cleared or set to a predetermined value (procedure P
C301). Then, it waits for the initialization signal INT to rise from a predetermined terminal of the unit memory 550 (procedure PC302), and when this signal rises, reads the machine number of the settlement machine from the machine number setting unit 352, and uses the machine number to set the terminal. Calculate the serial number and channel number,
These numbers are written in the transmission data area of the unit memory 550 (procedures PC303 and PC304).

Next, it is determined whether or not the date in the reception data area of unit memory 550 is "0" to wait for reception of a "line test" packet (procedure PC30).
5). That is, until the “line test” packet containing the date is sent from the management device 400, the date field in the unit memory is “0”, and when the packet is received, the date is changed to “0”. Since it is no longer “0”, it is possible to know whether a “line test” packet has been received by monitoring this date.

Upon receiving the "line test" packet, unit controller 390 sets the initial value unset bit of monitor information 1 (see [Table 15]) in the transmission data area to "1" (procedure PC306). This bit is cleared to "0" when an "initial value setting" packet or a "unit recovery data" packet is received.
Then, the unit controller 390 checks whether or not there is a received packet from the management device 400 by checking the command register CR2 in the communication area of the unit memory 550 (procedure PC307). Packet reception processing (procedure PC
341 to PC349), and then execute procedure P
Proceed to C308.

[1219] The procedure PC 308 checks whether or not a function from the card settlement controller 312 has been received.
If it is not received, the function is not received, and if it is received, the function reception processing corresponding to each function (FIG. 3)
18), and then proceed to procedure PC 309.

At procedure PC 309, the internal memory is checked to see if any unprocessed received packets remain.
After performing the packet receiving process (PC341 to PC349), the process proceeds to procedure PC310. This case considers a case where a packet is received from the management device 400 while the "card number" function is received in the function receiving process (FIG. 318) and the settlement process in FIG. 319 is executed.

At procedure PC310, it is checked whether or not the coin payout switch 353 is turned on. If it is turned on, the motor of the coin payout device 325 is driven by the procedure PC311 and the process proceeds to the procedure PC313. Procedure P
The motor started in C311 returns to procedure PC307 after execution of procedure PC313 or PC314, and returns to
The process proceeds from 308 to PC309 to PC310, and stops when the coin payout switch 353 is determined to be off.
That is, the motor of the coin dispenser 325 is rotated only while the coin dispensing switch 353 is turned on, and continues discharging coins during that time.

On the other hand, the opening / closing panel 30 is
1 to check whether the display reset switch 305 is on or off.
After clearing the display data of the amount and number of balls display 303 and 304 with, return to the procedure PC 307 and repeat the above procedure.

FIG. 313 shows an example of a specific procedure of the packet receiving process in the flow of FIG. 312.

[1224] When there is a received packet, the unit controller 390 first sets the received packet to "initial value setting".
It is determined whether the packet is a packet (procedure PC341). If the packet is an "initial value setting" packet, the initial value setting process (procedures PC401 to PC403) shown in FIG.
The process shifts to C349, where the command register CR2 in the unit memory 550 is cleared to notify the data transmission controller 551 that the packet has been received.

Next, if the received packet is not the "initial value setting" packet, it is determined whether it is a "unit recovery data" packet (procedure PC342), and if yes, the unit recovery processing shown in FIG. 315 (procedures PC411 to PC41).
8) is executed, and the flow shifts to the procedure PC 349.

If the received packet is neither “initial value setting” nor “unit recovery data”, it is determined whether or not “ACK” is received (procedure PC343). If “ACK” is received, nothing is done. The flow directly proceeds to procedure PC 349. The “ACK” packet received at this time is “ACK” other than when the unit controller 390 transmits the packet to the management device 400 and waits for a response.
This is because

At procedure PC343, the received packet is “AC
If it is not "K", the process proceeds to procedure PC344, where it is checked whether the initial value unset bit in the monitor information 1 is "1". Here, if the initial value unset bit is “1”, the procedure proceeds to the procedure PC 349, and if “0”, the procedure PC 34 is executed.
Go to 5. This is to prevent the settlement machine from erroneously starting the settlement operation when the “store opening code” or the “forced termination release” packet comes in before the “initial value setting” packet is received.

At procedure PC345, it is determined whether or not the received packet is a "store opening code" packet.
16 (procedures PC421-PC
423). If it is not the “opening code”, the received packet is “released forcibly” by procedure PC 346.
Judgment whether or not, if yes, forced termination cancellation processing PC
421 to P423 are executed, and if no, procedure PC347 is executed.
Proceed to.

At procedure PC347, it is determined whether or not the received packet is a "closure code". If yes, the forced termination process (procedures PC431 to PC433) shown in FIG. 317 is executed. If it is not "Close code", PC3
At 48, it is determined whether or not the received packet is a "forced termination request".
If yes, also forcibly terminate processing PC431-PC434
, And if no, proceed to procedure PC34
The process proceeds to 9 to clear the command register CR2 in the unit memory 550.

FIGS. 314 to 317 show specific procedures of the initial value setting processing, unit recovery processing, forced termination cancellation processing, and forced termination processing shown in the flow of FIG. 313, and are sent from the management apparatus 400. The corresponding processing is executed according to the received packets.

FIG. 314 shows the processing when the “initial value setting” packet is received. The unit controller 390 first places the head portion of the received packet written in the received data area of the unit memory 550 in the transmitted data area. By copying, a portion which becomes the head of the packet at the time of transmission is created, and the hot code of the reception data area is copied to a predetermined address of the transmission data area (procedure PC401, PC402).

Next, by clearing the initial value unset bit of monitor information 1 in the transmission data area set to "1" by procedure PC 106, it is clearly indicated that unit control device 350 has received the initial value. To return to the original routine (procedure PC403).

When the “unit recovery data” packet is received, the processing in FIG. 315 is started. First, the packet type in the reception data area and the received recovery data are copied to the corresponding area of the transmission data area, and then the unit is copied. Command register C in communication area of memory 550
The transmission command of the "ACK" packet is written in R2 to instruct the data transmission controller 551 to transmit the packet (procedures PC411 and PC412).

Next, after the timer (10 seconds) is set, reception of a packet from the management device 400 is waited, and "ACK" is set.
If a predetermined packet ("restart" packet) is not transmitted within a fixed time (10 seconds) after the transmission, the output of the watchdog pulse is stopped and reset is performed by itself (procedures PC413 to PC417). When the "restart" packet is transmitted within 10 seconds, FIG.
3 to clear the command register CR2 in the procedure PC 349 and then return to the main routine of FIG. 312 (procedure P
C418).

FIG. 316 shows a “store opening code” or “forced termination release” packet from the management device 400, and FIG.
17 shows a process when a “closed code” or “forced end” packet is received. When the unit controller 390 receives the “store opening code” or “compulsory termination release”, it first turns off the checkout stop lamp 342 and turns on the checkout lamp 341, and then transmits a function that enables acceptance of a card. Set the bit indicating "in operation" in the operation information of the PC (procedure PC
421-PC424). On the other hand, when the “closed code” or “forced end” packet is received,
After turning off 1 and turning on the settlement stop lamp 342, a function for disabling card acceptance is transmitted, and the bit indicating "in operation" in the operation information is cleared (procedure P
C431-PC434).

FIG. 318 shows a specific procedure of the function receiving process in the flow of FIG. 312.

Here, procedure PC 308 in FIG. 312 is used.
(Steps PC351 to PC35) It is checked whether the function received in Step 3 is any one of “normal end”, “abnormal end”, “status transmission”, and “retransmission request”.
4). And the received function is "normal end"
In the case of, the "card reader abnormality" bit of the monitor information 2 is cleared, and in the case of "abnormal termination", the bit is set to "1" and the routine returns to the original routine (procedures PC361 and PC361).
362). If the received function is "status transmission", the statuses 1 and 2 sent together with the function code are stored in the internal memory (procedure PC363). Further, when the received function is "retransmission request", the previously transmitted function is retransmitted, and the process returns to the original routine (procedure PC364).

On the other hand, if the function received by procedure PC 308 is not any of the above four functions, procedure PC 355 checks whether or not the “initial value not set” bit in monitor information 1 is “0”. If "0", do nothing. If it is "0", proceed to procedure PC356 to check whether the received function is the "initial value request" function. If yes, send the "initial value setting" function in procedure PC365 and then return to the original. Return to the routine (procedure PC365). The reason why the “initial value request” function is accepted only when the initial value unset bit is “0” is that the unit controller 390 still transmits “initial value setting” from the management device 400 while the bit is “1”.
This is because no packet has been received. If the received function is not “initial value setting”, the process proceeds to procedure PC 357 to determine whether the function is a “card number transmission” function. If yes, the settlement processing (procedures PC451 to PC481) shown in FIG. 319 is executed, and then the process returns to the original routine (FIG. 312).

If the received function is "self-discharge" for notifying the ejection of the card, this fact is stored in the internal memory and the routine returns to the original routine (procedures PC358 and PC359).

[1240] Using this storage, the ejection sound may be output by a speaker, or the cause of the fraud sent along with the card ejection function may be stored, and the cause may be displayed externally.

In the settlement process executed when the “card number transmission” function is received, as shown in FIG. 319, first, the “card settlement” in which the card number read by the card reader is input to the management device 400. Send a packet and set a 10 second timer (procedure PC
451, PC452). Then, while checking the timer, wait for a packet response from the management device 400 (procedures PC453 and PC454).
If a packet is not received from the management apparatus 400 within 10 seconds after the packet transmission, the procedure jumps to the procedure PC 481 to transmit a “card discharge” function to the card settlement control apparatus 312 and insert the card forward (card insertion slot). After being discharged to 302), the amount and number of balls indicator 3
03 and 304 are cleared and the process returns to the original routine (procedure PC482).

On the other hand, when a response packet from the management apparatus 400 is received before the timer set by the procedure PC 452 causes a time-over, the packet is set to “NA”.
K ”or“ ACK ”(procedure PC455, PC
456) If "NAK", jump to procedure PC481 to eject the card. If the received packet is neither "NAK" nor "ACK", it is registered in the internal memory as an unprocessed packet (procedure PC45).
7). This unprocessed packet is detected and processed by the procedure PC 309 in FIG.

[1243] If the received packet is "card payment"
When the response to the packet is “ACK”, “A”
After setting the data for displaying the unused amount and the number of balls relating to the card sent in the CK "packet in the amount and number of balls display devices 303 and 304 in the output buffer, the print switch It is determined whether 354 is on or off (procedures PC459 and PC460).
If 0, the settlement data (unused amount and the number of balls) is output to the printer 33.
Send to 0 for printing. On the other hand, the print switch 354
If is turned on, the history data as well as the settlement data are sent to the printer for printing (procedure PC461).

Thereafter, unit controller 390 determines the presence or absence of a change from the unused amount data, and if there is no change, jumps to procedure PC469 (procedure PC4).
62). If there is a change, it is determined whether or not there is a fraction less than 1,000 yen. If there is a fraction, a payout command is given to the coin dispenser 325 to discharge the number of coins corresponding to the fraction. The settlement amount and the coin amount data in the transmission data area of the memory 550 are added (procedure PC46).
3-PC465). If the unused money has no fraction of less than 1,000 yen, the procedure jumps from PC 463 to PC 466 to determine whether the unused money is 1,000 yen or more. After giving the payout command, the settlement amount and the bill amount data in the unit memory 550 are added (procedures PC466 to PC468).

If the unused money is less than 1,000 yen, the procedure jumps from PC 466 to PC 469, increments the number of settlements in unit memory 550, and adds the data of the number of settlement balls (procedure PC470).

[1246] Next, the unit controller 390 determines whether or not the mode is the card confiscation mode by referring to the set value of the unit number setting unit 352. When the mode is not the confiscation mode, the "payment" function is transmitted (procedures PC471 to PC473). Then, the management device 4
A “payment end” packet is transmitted to 00 and again
Set the second timer (procedure PC474, PC47
5). Then, while waiting for a response packet from the management device 400 while checking the timer (procedures PC476 and PC477), if the timer times out before receiving the packet, the procedure PC
The process jumps to 482 to clear the display data of the amount and number of balls display.

On the other hand, if a packet is received before the time-over occurs, it is checked whether the received packet is "ACK". If "ACK", the settlement process is terminated and the process returns to the original routine. In this case, register as an unprocessed packet and return to procedure PC 476 to return “ACK”.
(Steps PC478 and PC479).

FIG. 320 shows the unit controller 39.
0, the procedure of the timer interrupt process executed by the timer interrupt is shown separately from the main process (FIG. 312).

The unit controller 390 operates as shown in FIG.
When an interrupt signal is received at an interval of 1 msec from the internal timer set by the procedure PC 301 in the flow of (1), first, the check code written in the internal memory is read by the procedure PC 321 to check whether the code has changed. The internal memory is checked, and if there is an abnormality, a reset is performed by jumping to the procedure PC 324 and omitting the output of the watchdog pulse (procedure PC 32
1). When the internal memory is normal, the procedure PC 122
After the timer (including the timer for the data transmission controller) is updated and the watchdog pulse is output, the data for dynamically displaying the monetary and ball number indicators 303 and 304 is output, and the interrupt processing is terminated ( Procedures PC323 and PC324).

Although not shown in the flowcharts of FIGS. 312 to 319, the unit controller 390
When the function is received from the card settlement controller 312, the code is checked and if there is an error, a "retransmission request" function is transmitted.

FIG. 321 shows a card settlement controller 312
2 shows a control procedure such as card settlement.

[1252] When a reset is applied, the card settlement controller 312 first clears and initializes the internal memory, registers, I / O ports, etc., sets a timer (ex. 10 seconds), and sets an "initial value request". The function is transmitted to the unit controller 390 (routines RN301 to RN301).
RN303). Next, it is checked whether or not the function from the unit controller 390 has been received, and if not, it is determined whether or not the timer set in the routine RN302 has elapsed (routines RN304 and RN305). Then, until the time is over, the routine RN304, RN30 is executed.
5 is repeated, and if the time is over, the routine RN3
Returning to step 02, the timer is reset and the "initial value request" function is transmitted again. First, "Initial value request"
This is because the unit controller 390 may not yet be ready for reception at the time the function is sent.

[1253] After transmitting the "initial value request" function,
Upon receiving the function from the unit controller 390, the process shifts from the routine RN304 to the RN306 to execute processing corresponding to the received function.

Thereafter, the initial value unset bit of the status 1 in the internal memory is checked, and if "1", that is, the initial value has not been set yet, the routine returns to the routine RN302, where the timer is reset and the "initial value" is again set. Send value request function. When the corresponding processing (FIG. 323) is executed in the routine RN 306 in response to this function, the routine RN 307 determines NO (initial value unset bit = “0”) and shifts to the routine RN 308. Here, it is checked whether or not a command from the card reader control device 388 has been received. If there is no received command, or if there is a received command, processing corresponding to the command (described later) is executed in the routine RN309 and then the routine RN3
The process proceeds to step 10 to check whether or not the next function has been received. If there is, the corresponding process is executed in the routine RN306. If not, the process jumps to the routine RN307.

FIG. 322 shows processing (routine RN3) corresponding to the reception function in the flow of FIG.
06) is shown below.

In this processing, first, it is determined whether the received function corresponds to any of “initial value transmission”, “status request”, or “retransmission request” (routine RN).
321 to RN323). If the received function is “initial value transmission”, the initial value function receiving process (routine RN) shown in FIG.
401 to RN403) to execute the original routine (FIG. 32).
Return to 1).

On the other hand, if the received function is "status request", a "status transmission" function including statuses 1 and 2 is transmitted to unit controller 390, and the process returns to the original routine (routine R
N326). If the received function is "retransmission request", the previously transmitted function is transmitted again and the process returns to the original routine (routine RN32).
7).

[1258] Furthermore, the received function is the above 3
If it is not one of the three functions, it is checked in routine RN324 whether the initial value unset bit of the status 1 is set to "1", and if "0", the received function is "card accepted", "card accepted". It is determined whether any of “impossible”, “card ejection”, “reload”, “card confiscation” or “payment” is applicable (routines RN328 to RN333). Then, when any of the above cases is satisfied, processing corresponding to each function shown in FIGS. 324 to 329 is executed.

On the other hand, if the initial value unset bit is "1" in the routine RN324, the "abnormal termination" function is returned without doing anything (routine RN325). This is because the processing corresponding to the above six reception functions should not be executed in a state where the initial value is not set.

FIG. 323 shows a specific procedure of the “initial value transmission” function reception processing in the function reception processing flow of FIG. 322.

[1261] Upon receiving this function, the card settlement controller 312 stores the identification code and the identification code sent in the function together with the function in the internal memory, clears the initial value unset bit of the status 1, and then returns "normal". An "end" function is transmitted to the unit controller 390 (routines RN401 to RN403).

FIG. 324 and FIG. 325 show a specific procedure of the processing of the card settlement controller 312 when the “card accepted” function and the “card unacceptable” function are received.

[1263] When the "card accepted" function is received, a magnetic read command is transmitted to the card reader control unit 388, and then the unit controller 39 is controlled.
A "normal end" function is transmitted to 0 (routines RN411 and RN412). On the other hand, "Card not accepted"
When the card settlement controller 312 receives the function, it first sends a cancel command to cancel the card reading command to the card reader controller 388 and then sets the timer (routines RN421 and RN42).
2). Then, while monitoring this timer, it is checked whether a response command has been received from the card reader control device 388 (routines RN423, RN424). If a time-out has occurred before receiving a response, the routine RN42 is executed.
7 and sends an “abnormal termination” function to the unit controller 390. If a response command is received before the time is over, it is checked whether the command is normal. If the command is normal, a "normal end" function is transmitted to the unit controller 390 and the process returns to the original routine (routine RN425). , R
N426).

FIG. 326 shows a processing procedure of the card settlement device 312 when the “card discharge” function is received. The processing in this case is substantially the same as the processing when the “card cannot be accepted” function shown in FIG. 325 is received. The difference is that the first "card ejection in front" command is transmitted (routine RN431).
If the response command from the card reader control device 388 is normal, the “magnetic read” is sent to the card reader control device 3
88 and then send a “normal end” function to the unit controller 390 (routine RN4
36, RN437). The reason why the "magnetic read" command is transmitted in the routine RN436 while giving the card ejection command is to enable the card reader 800 to accept the next card. Card reader 8
00 does not start reading the card immediately after receiving the “magnetic read” command, but starts after the card is inserted (see routines R1201 to R1223 in FIG. 291).

FIG. 327 shows a specific procedure of the “reload” function receiving process in the function receiving process flow of FIG. 322.

[1266] Upon receiving this function, the card settlement controller 312 first operates the card reader controller 38.
By checking the buffer for receiving the command from the card controller 8, it is determined whether or not the card is present in the card reader, and if there is no card, a “status transmission” function is transmitted to the unit controller 390 (routine RN 4).
41, RN461). On the other hand, when there is a card in the card reader, a "reload" command is transmitted to the card reader control device 388, and then a timer is set (routine RN442).

While monitoring this timer, it waits for a response command from the card reader control unit 388 (routines RN444, RN445). If a time-out occurs before a response arrives, the routine jumps to the routine RN462 and transmits an “abnormal termination” function to the unit controller 390. If the response command is received before the time-over occurs, the magnetic data inspection processing RN501 to RN509 shown in FIG. 331 is executed, and then the presence or absence of impropriety is determined (routine RN446). If there is any fraud, the process jumps to the routine RN453 to instruct the card reader to eject the card.

On the other hand, if the magnetic data read from the card is correct, a "punch hole request" command is transmitted to the card reader control unit 388 to set a timer and wait for a response command (routines RN447 to RN4).
50). Then, when the time is over, the "abnormal termination" function is transmitted in the routine RN462, and when the response command is received within the time, the punch hole inspection processing RN511 to RN516 shown in FIG. 332 is executed. Then, it is determined whether there is any fraud (routine RN45).
1) If there is a fraud, the routine jumps to the routine RN453 to give a card ejection command.
In step 452, a “send card number” function is transmitted to the unit controller 390, and the routine RN in FIG.
Return to 307.

When the routine jumps to the routine RN453 after detecting an illegality in each of the routines RN446 and RN451, a "card ejection" command is first transmitted to the card reader control unit 388, and then a timer is set (routine RN454). Then, it waits for a response command while monitoring the timer (routines RN455, RN45).
6) When the time is over, the routine R46
The program jumps to step 3 and transmits an “abnormal termination” function to the unit controller 390. When the response command is received within the predetermined time, the process proceeds to a routine RN457 to check whether the response is normal. If the response command is normal, a "self-ejection" function is transmitted to inform the unit controller 390 that the card has been ejected. A "magnetic read" command is transmitted to the card reader control device 388 (routines RN458, RN459). This is to make it possible to accept the next card.

FIG. 328 shows a specific procedure of the “card confiscation” function receiving process in the function receiving process flow of FIG. 322.

Upon receiving this function, the card settlement controller 312 first executes the settlement hole punching processes RN521 to RN525 shown in FIG. 333, and then checks whether there is any abnormality in the hole making process (routine). R471). If there is an abnormality, the routine RN
The process jumps to 479 to transmit an "abnormal end" function to the unit controller 390. If there is no punch hole error, a "card rear ejection" command is transmitted to the card reader control device 388 to set a timer (routine RN472). , RN473). Then, it waits for a response command while monitoring the timer (routines RN474 and RN475). If the time is over or the response command is not normal, the "abnormal termination" function is transmitted. After transmitting the function, the counter for counting the number of confiscated cards is counted up.
1 to the routine RN307 (routines RN476 to RN476).
RN478).

FIG. 329 shows a specific procedure of the “pay-out” function reception processing in the function reception processing flow of FIG. 322.

This function reception processing is performed as shown in FIG.
This is almost the same procedure as the card confiscation function receiving process. The only difference is that a "card front ejection" command is transmitted in place of the "card rear ejection" command in the routine RN482, and that a counter for counting the number of cards is not counted up.

As a result, when the "card confiscation" function is received, the card is ejected into the card storage tank 314 behind the card reader, and when the "payment" function is received, the card is ejected to the front card insertion slot 302. .

FIG. 330 shows a specific procedure of processing when a response command to the "magnetic read" command is received from the card reader control device 388 in the flow of FIG. The response command contains magnetic data read from the card.

This command receiving process is similar to the process after receiving the response command in the “reload” function process flow shown in FIG. That is, first, the magnetic data inspection processing R shown in FIG.
After executing steps N501 to RN509, it is determined whether or not the magnetic data is invalid (routine RN341). Then, if there is any fraud, the process jumps to the routine RN355 to instruct the card reader to eject the card (forward).

On the other hand, if the magnetic data read from the card is correct, a "punch hole request" command is transmitted to the card reader control unit 388 to set a timer and wait for a response command (routines RN342 to RN3).
45). When the time is over, the "abnormal termination" function is transmitted in the routine RN362, and when the response command is received within the time, the punch hole inspection processing RN511 to RN516 shown in FIG. 332 is executed. Then, it is determined whether there is any fraud (routine RN34).
6) If there is a fraud, jump to the routine RN355 to give a card ejection command. If there is no fraud, send a "security request" command to the card reader control device 388 and set a timer (routine RN34).
7, RN348). Then, it waits for a response command while monitoring the timer (routines RN349 and RN35).
0), it is determined whether or not the security data in the received command matches the security in the magnetic data (routine RN351).
If they do not match, the routine RN352 sets a security fraud bit indicating the cause of the fraud, and then moves to the routine RN353 to determine whether there is fraud.

If it is determined that there is no fraud, a "card number transmission" function is transmitted to the unit controller 390 in a routine R354, and the process returns to the routine RN307 in FIG.

[1279] Routine RN341, RN346, RN3
At 53, when a jump has been made to the routine RN355 upon detecting a fraud, a "card ejection" command is first transmitted to the card reader control device 388, and then a timer is set (routine RN356). Then, it waits for a response command while monitoring the timer (routine RN35).
7, RN358), when the time is over, the routine jumps to the routine R363 and transmits an "abnormal end" function to the unit controller 390. If a response command is received within a predetermined time, the routine RN3
Go to step 59 to check whether the response is normal or not. If the response is normal, send the "self-ejection" function to inform the unit controller 390 that the card has been ejected,
A "magnetic read" command is transmitted to the card reader control device 388 (routines RN360, RN361). This is to make it possible to accept the next card.

FIG. 331 to FIG. 333 show the “reload” function reception processing flow of FIG.
A specific procedure of the magnetic data inspection process in the command reception process flow of FIG.

In this inspection processing, the company code in the magnetic data read from the card and sent from the card reader controller 388 is compared with the company code read from the program ROM of the card settlement controller 312. (Routine RN501) If they match, the device code in the magnetic data is compared with the device code sent from the card reader control device 388 in response to the "status request" command (routine RN502). If the company code or the device code does not match, "1" is set to the security fraud bit indicating the cause of the fraud in the internal memory (routine RN506).

If both codes match, the date code and the identification code in the magnetic data are compared with the code sent as an initial value from the unit controller 390 (routines RN503 and RN504). If the date codes do not match, "1" is assigned to the bit indicating the date and time mismatch of the cause of the fraud, and if the identification codes do not match, "1" is assigned to the bit indicating the mismatch of the identification code of the cause of the fraud. Stand up (routines RN507, RN
508).

Further, when the date code and the identification code also match, it is checked whether a specific code indicating the test card is written in the card number column in the magnetic data, and the inserted card is the test card. When it is determined that there is, the test card bit of the cause of the fraud is set to "1" (routine RN509).

On the other hand, if all the codes in the magnetic data match and the card is not a test card, it is determined that the card is a normal card, and the process returns to the original routine in FIG. 327 or 330 to continue each processing.

FIG. 332 shows a specific procedure of punch hole inspection processing in each processing flow of FIGS. 327 and 330.

In this punch hole inspection process, first, it is checked whether a hole is opened in either the issue hole or the resurrection hole, and when either hole is opened, the issue command code FNC in the magnetic data (see FIG. 4) ) Is matched with a predetermined issued function code or resurrection function code (routines RN512, RN513).
If neither the issue hole nor the resurrection hole is open, or if both are open and if the issuance instruction codes do not match, the bit indicating issue or resurrection hole improper cause is set to "1". Then, the process returns to the original routine (routine RN515).

If either the issue hole or the resurrection hole is open and the issuance instruction code matches, it is checked whether the return-to-zero hole or the settlement hole is open (routine RN5).
13, RN514), and if any one of the holes is open, set "1" to the bit indicating the cause of the fraud or return hole improper settlement (routine RN516). This is because a card with a return-zero hole is a card that does not require settlement because both the amount of money and the number of possessed balls are zero, and a card with a hole in the settlement hole is a settlement card. When it is determined that neither the return-to-zero hole nor the settlement hole is opened, the process returns to the original routine and continues.

FIGS. 331 to 333 show the specific procedure of the settlement hole punching process in the function receiving process flow shown in FIGS. 328 and 329.

In this processing, by setting data indicating the type of punch hole (payment hole), the punch hole punching position is indirectly specified, and then a “punch hole request” command containing the punch hole data is sent to the card. The data is transmitted to the reader control device 388 (routines RN521 and RN522). Then, a timer is set, and while monitoring the timer, the system waits for the reception of a response command from the card reader control device 388 (routines RN523 to RN525).
The "abnormal termination" function is transmitted to the terminal 90 (routine RN526). When the response command is received within the predetermined time, the process directly proceeds to the routine RN471 or RN481 in FIGS. 323 to 329 to continue the processing. If there is a defect in punching holes in the card reader 800, a code indicating an error is included in the response command received in the routine RN525, and the card settlement controller 312 sends the routine RN472 or RN.
By examining the code at 482, it can be known whether or not punching has been performed normally.

On the other hand, the control flow of the card reader 800 of the payment machine 300 by the card reader control device 388 based on the command from the card payment control device 312 is shown in FIG.
311 is common to the control flow in the card reader of the issuing machine 200 shown in FIG.

The major difference from the control flow relating to the card reader in the control unit 160 of the pachinko machine 100 is as follows.
This is a point of having a control flow for ejecting the card backward rather than forward of the card reader.

[1292] As described above, the card reader control device 3
Communication between the unit controller 88 and the unit controller 390 is performed by command transmission.
8, a “magnetic write” command instructing to record magnetic data of the card,
A "magnetic read" command to read the magnetic data, security code and punch hole information on the card to send magnetic data, a "security request" command to send the read security data, and a read punch hole A "punch hole request" command to send data, and a "reload" command to reread data on the card held in the card reader
Command, a "punch hole" command to instruct the card to punch a hole, a "card forward ejection" command to eject the card in the card reader toward the front insertion slot, and a "Card backward eject" command to eject the card backward, and "Cancel" to cancel the card reading command
There are nine types of “status request” commands that instruct transmission of commands and status information indicating the status of the card reader.

[1293] Of these, "magnetic read" and "reload"
The command is not used in the issuing machine, and the “magnetic write” command is not used in the checkout machine 300 or the management device 400. The "magnetic read" command instructs the card reader 800 to read not only magnetic data but also all data on the card, and requests transmission of only magnetic data. Data request commands are separately prepared for security data and punch hole data.

Since the control flow of the card reader control device 288 (FIGS. 290 to 311) has already been described for the issuing machine, FIGS. 291, 292 and 29 relate to only the card reader of the payment machine, the description of which is omitted here.
The process 3 will be described.

FIG. 291 shows a specific procedure of processing when a "magnetic read" command is received among the command processing shown in the routine R1122 in the flow of FIG. 290.

In this command processing, first, the “card insertion permission” flag is set to “1” (routine R120).
1). If the "card insertion permission" flag is not set, the motor is not rotated even if the card is inserted, and the card is not taken into the card reader. Thereafter, the card holding LED (which is turned off when a card is inserted) is turned on (routine R1201), and the card reading processes R501 to R536 in FIG. 300 are executed. Then, it is determined whether the "card unread" flag is set to "1" (routine R1203). As described above, if the card insertion detection sensor is off when the card reading process of FIG. 300 is executed, the "card reading" flag is set in the routine R536, so the process proceeds to the routine R1204 to set the "card insertion waiting" flag. It returns to the main flow of 290.

On the other hand, when the insertion detection sensor is ON at the time of executing the card reading process, the routines R504 to R525 of the flow of FIG. 300 and the magnetic process of FIG.
05, the security data, the punched hole data and the magnetic data are all read. In addition, since the “card unread” flag is not set, the determination is NO in the routine R1203 of FIG. Therefore, the parity, L shown in FIG.
After shifting to the RC inspection process and executing this, the number of magnetic data to be transmitted is set in the routine R1205, and then the address (source) of the data buffer containing the magnetic data and the address (destination) of the transmission buffer are set. )
Are set (routines R1206 and R1207). Then, in routines R1208 to R1214, the magnetic data in the magnetic data buffer is sequentially transferred to the transmission buffer by one byte, and the magnetic data is converted into an ASCII code suitable for transmission.
Put R in the transmission buffer (routine R1215). Thereafter, the STX indicating the beginning of the response command is set at a predetermined address in the internal memory, and the STX is first transmitted to the card settlement controller 312 (routine R121).
Next, the address of the transmission buffer in which the magnetic data is set is set, and the magnetic data is transmitted to the card settlement controller one byte at a time while sequentially incrementing the address (routines R1218 to R122).
2). When the transmission of the last code CR is completed, the "card insertion wait" flag is cleared, and the process returns to the main flow in FIG. 290.

FIG. 292 shows the procedure when a "reload" command is received. Card reader controller 388
Receives the “reload” command, executes magnetic processing R541 to R579 in FIG. 302 to read magnetic data, and then executes parity and LRC check processing R60 in FIG.
1 to R624 to execute the routine R1205 in FIG.
And the read magnetic data is transmitted (reference numeral J1).
reference).

FIG. 299 shows the processing procedure of the card reader control unit 388 when receiving a “card forward ejection” command from the card settlement control unit 311.

[1300] In the card ejection process shown in FIG. 299, when the card ejection function comes while the card is being inserted, that is, the first position detection sensor SNS1 is on and the insertion detection sensor 808 is off, the motor Is rotated forward (routines R451-R457). Then, the shutter is opened and the motor is rotated in the reverse direction. The motor is stopped 0.2 seconds after the position detection sensor SNS2 is turned off, the shutter solenoid is turned off, and the shutter is closed (routines R458 to R467). This takes into account the time required for the card to come off the transport roller 812.
When the card comes off the transport roller 812, the card cannot be discharged any more. At this time, the first position detection sensor SNS1 and the insertion detection sensor 808 are both on.

After the shutter is closed, the jam display bit of status 1 is cleared, the security read flag is cleared, the card-in display LED 12 is turned off, and the fact that there is no card in the status area in the RAM is written ( Routines R468 to R471). In the above-described routines R451 to R471, if a time-over occurs during normal rotation or reverse rotation of the motor, the motor is stopped, and if a card is inside, the jam is processed (routines R481 to R484).

On the other hand, FIGS. 300 and 301 show FIGS.
The specific procedure of the card reading process, the parity, and the LRC inspection process in the “magnetic reading” command reception flow of
Further, FIG. 302 shows a specific procedure of the magnetic processing in the “reload” command reception flow of FIG. 292.

In the card reader of this embodiment, as described above, the security code reading sensor 810 is used.
a is disposed closest to the card insertion / ejection port, and when the sensor 810a faces the end of the security area (TF), the punch detection sensor SNSp still reaches the first punch hole formation location PH1. The distance between the sensors is determined so as not to cause this. Therefore, the security code is first read, and then the detection of the punch holes and the reading of the magnetic data are performed in parallel.

The program is configured so that the actual reading of the security code is performed by a timer interrupt triggered by the output of the encoder that detects the rotation speed of the motor. In the card reading process shown in FIG. 300, the routine R501 is executed. Preparation for security reading is performed in steps R523 to R523, and a flag for permitting the timer interrupt is set in the routine R524. Then, the process proceeds to magnetic code reading processing.

The card reader of this embodiment prevents the punched hole and the magnetic recording portion from reaching the punched hole detection sensor SNSp and the magnetic head 821 until the rear end of the card reaches the first position detection sensor SNS1 at the time of insertion. The interval between each sensor is set.

[1306] Therefore, in the magnetic code reading process of FIG. 302, after the position detection sensor SNS1 is turned on in the routine R545, the detection of the punched hole and the reading of the magnetic code are performed.

[1307] Moreover, the reading of the magnetic data is performed as shown in FIG.
5, one bit is read at a time, and the work area for storing the read data is converted into parallel data by operating the work area like a shift register (routine R590). Further, the card reader according to this embodiment includes first and third position detecting sensors S.
The distance l3 between NS2 and SNS3 is longer than the regular card length l0, and the second and third position detection sensors SNS2 and SNS3
The distance between the sensors is set so that the distance l4 between them is shorter than the regular card length l0 (see FIG. 32). Therefore,
During the 1-bit reading process shown in FIG. 305, the output of the first to third position detection sensors SNS1 to SNS3 is checked to detect a card size defect (routine R584 to R587).

[1308] In the system of this embodiment, the same device as the card issuing device 700 provided in the issuing device 200 is used as the card issuing device for the management device 400, and the control program of the card issuing control device 790 is used. Only the difference is that the control program for the card reader control device 288 is common to the card reader control flow of the payment machine as well as the issuing machine.

Next, the control procedure of the management device 400 for controlling the card recovery in the card issuing device will be described with reference to FIGS. 334 to 341.

[1310] As described above, in the card issuing device, the central processing unit CPU can communicate only with the card issuing control device 790 and cannot directly communicate with the card reader control device 288. That is, the card reader control device 2
88 can communicate only with the card issuing control device 790. Therefore, communication between the central processing unit CPU and the card issuing control device 790 is performed by a function code, and communication between the card issuing control device 790 and the card reader control device 288 is performed by a command. Incidentally, as the function code from the central processing unit CPU to the card issuance control device 790, an "initial value setting" function for giving a card reader a date code and an identification code to be recorded in the magnetic recording unit of the card, "Issue card" function to issue a card, "restore card" function to instruct the card to be restored, "test card issue" function to issue a test card, and request to resend the function code sent immediately before Six types of commands are provided: a "retransmission request" function and a "status request" function for requesting transmission of a status indicating the state of the card reader received from the card reader control device 288 by the card issuing control device 790.

[1311] Among these, only the "card resurrection" function and the "test card issuance" function are used in the management device 400, and the other functions are prepared for the card issuing device built in the issuing machine 200. Is what is being done.

[1312] The function code from the card issuing control device 790 to the central processing unit CPU includes an "initial value request" function for requesting an initial value such as a date and an identification code at the time of reset. The "normal termination" function that notifies the central processing unit that the processing has been completed, and the "abnormal termination" function that indicates that processing has not ended normally, and the retransmission of the function code sent immediately before to the central processing unit. There is a "retransmission request" function to request. The issuer 200 also has a “status transmission” function for transmitting the status of the card reader in response to a “status request” from the unit controller 299.

[1313] Although not particularly limited, the above function code is transmitted between a start code of STX and an end code of ETX, and between the STX and ETX, status and data to be transmitted are included in addition to the function code. There is also.

[1314] On the other hand, as communication commands from the card issuing control device 790 to the card reader control device 288, a "magnetic write" command instructing recording of magnetic data on the card, a magnetic data of the card, a security code, and a punch hole are provided. A "magnetic read" command instructing to read each piece of information and sending magnetic data, a "security request" command instructing to send the read security data, and a "punch hole request" instructing to send the read punch hole data Command, a "reload" command for instructing rereading of data of the card held in the card reader, a "punch hole" command for instructing to punch a hole in the card,
A “card forward ejection” command to eject the card in the card reader toward the front insertion slot, a “card backward ejection” command to eject the card in the card reader backward, and a card reading command There are nine types of “cancel” command for canceling the status and “status request” command for instructing transmission of status information indicating the status of the card reader.

[1315] When the card reader control device 288 receives the above-mentioned command from the card issuance control device 790, it executes the corresponding processing and always returns a response. The types of response include: normal, communication error, command error, no magnetic recording data, magnetic data read failure, magnetic recording data error, security and magnetic data mismatch, company code or device code mismatch, magnetic write error, punch error, There are punch hole read error, security read error, punch dust full, motor error, RAM error, sensor error, card reader error, card length error, and card jam.

FIG. 334 shows a control procedure of the card issuance control device 790 of the management device 400, such as card recovery.

When the card issuance control device 790 is reset, the internal memory, registers, I / O ports, etc. are first cleared and initialized, and then a timer (ex. 10 seconds) is set, and the "initial value request" is set. Central processing unit C
Transmit to PU (routines RN101 to RN10
3). Next, it is checked whether a function from the central processing unit CPU has been received, and if not, it is determined whether the timer set in the routine RN102 has expired (routines RN104 and RN105). Then, the routines RN104 and RN105 are repeated until the time is over. If the time is over, the process returns to the routine RN102, resets the timer, and transmits the "initial value request" function again. This is because, when the "initial value request" function is first transmitted, the central processing unit CPU may not be ready for reception yet.

After transmitting the function, the central processing unit C
Upon receiving a function from the PU, the routine RN
The process proceeds from the step 104 to the RN 106, and checks whether the received function is the “initial value transmission” function. If no, the routine RN107 transmits the “abnormal termination” function, and then returns to the routine RN102 to return to the “initial value request” function. Is retransmitted. First, after receiving an initial value, specific processing such as card issuance is accurately executed.

However, the management apparatus 400 does not send an initial value at the time of initialization, but sends an “initial value transmission” function immediately before a “card resurrection” or “test card issuance” function.

If the function received in the determination of the routine RN106 is "initial value transmission", the process proceeds to the routine RN108, where the date and identification code sent together with the function code are stored in the internal memory. After that, the initial value unset bit of the status register also prepared in the internal memory is cleared, and a "normal end" function is transmitted to the central processing unit CPU (routine R
N109, RN110).

Thereafter, the routine RN111 waits for the reception of the next function from the central processing unit CPU. When the function is received, the routine RN1 is executed.
The process proceeds to steps 12 to RN115 to determine which function has been received. If the function is the "initial value transmission" function, the identification code is stored, and the "normal end" function is transmitted (routine RN116, routine RN116). R
N117) If the function is the "card recovery" function, the card recovery processing of FIG. 335 is executed (routine R
N113). If the received function is "test card issuance", a test card issuance process is executed according to the same procedure as that of the card restoration process of FIG. 116 (not shown) (routine RN114). Routine RN1
The determination of whether or not the “initial value transmission” function is performed again in step 12 takes into consideration the case where the process returns to the routine RN111 after execution of error processing (see FIG. 118) described below (reference numeral V1).

FIG. 335 shows a specific procedure of the card restoration process (common to the test card issuing process) in the flow of FIG. 334.

When the card issuance control device 790 receives the “card resurrection” function or the “test card issuance” function from the central processing unit CPU, the card issuance processing routine RN shown in FIG.
After executing steps 201 to RN212, the reader control processing routines RN213 to RN227 in FIG. 337, the card inversion processing routines RN228 to RN243 in FIG. 338, and FIG.
9 after the execution of the print 1 processing routines RN245 to RN266 in FIG.
After executing step 80, the counter 795 that counts the number of cards removed is counted up and a "normal end" function is transmitted (routines RN121 to RN127).

FIG. 336 shows a specific procedure of card ejection processing in the card recovery (or test card issuance) processing flow of FIG. 335.

Here, first, it is checked whether or not there is a card in the card tank 701 by looking at the card presence / absence sensor 703 (routine R201). If the sensor is off, that is, the tank is empty, the routine jumps to the routine RN212 to go to the internal memory. After setting the take-out device abnormality bit of status 2 in the “1” to “1”, the processing shifts to the error processing routine of FIG. 341.

If there is a card in the card tank 701, the routine shifts from the routine RN201 to RN202 and sends a "magnetic write" command to the card reader control device 288. Then, after setting the timer, the clutch solenoid 729 is turned on, and the take-out motor 719 is set.
Is rotated (routines RN203 and RN204). Thereby, one card is sent out from the card tank.

Next, it is checked whether or not the timer set in the routine RN203 has timed out.
It is checked whether the traveling position sensor CPS1 has been turned on (routines RN205, RN206). First traveling position sensor CPS
When 1 is off, the routine returns to the routine RN 206 to repeat the timer check. Thus, the first traveling position sensor C
When the time is over before the sensor is turned on, the routine jumps to the routine RN211 to set the traveling position sensor 1 abnormality bit of the status 1 to "1", and then sets the status 2 extraction device abnormality bit to "1". After setting to “1”, the flow shifts to the error processing routine in FIG. 341.

On the other hand, if the first traveling position sensor CPS1 is turned on before the time is over, the routine RN20
7, the clutch solenoid 729 is turned off, and the card is sent out from the tank to the roller 712.
Then, the transmission of the rotational force is stopped to prevent the feeding of two cards, and it is again checked whether the timer set in the routine RN203 has timed out (routine RN208). Then, the first traveling position sensor C
It is checked whether or not the PS1 has been turned off. If the sensor is turned off within a predetermined time, it is determined that the card has been removed from the card tank 701 and has been normally delivered, and the removal motor 719 is stopped to terminate the processing and return to the original routine. It returns to (FIG. 335). If the traveling position sensor CPS1 is not turned off within a predetermined time, it is determined that the card is jammed halfway, and the routine shifts to the routine RN211 to set the traveling position sensor 1 abnormality bit of status 1.

FIG. 337 shows a specific procedure of the reader control processing in the card recovery processing flow of FIG. 335.

In this flow, first, after setting a timer, it is checked whether or not there is a response to the "magnetic write" command transmitted by the routine RN202 in the card removal processing flow before the timer expires (routine). RN213 to RN215). And
If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormal bit of the status 2 to "1", and shifts to the error processing routine of FIG.

If the response from the card reader control device 288 is received within a predetermined time, the routine RN21
The process proceeds to step 6a to check whether the response is normal or not.
Jump to and execute error handling. On the other hand, if the response is normal, it is determined whether or not the reception function is the “card resurrection” function (routine RN216b). If yes, data indicating the reissue hole position is sent to the card reader control device 288, Is "Test card issuance", a "punch hole" command containing data indicating the position of the issuance hole is transmitted, and the timer is set (routines RN217a and RN217a).
N217b, RN218). Then, before the timer times out, the card reader controller 288
Check if there is a response from the routine (routine RN
219, RN220). If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormality bit of the status 2 to "1", and shifts to the error processing routine of FIG.

If the response from the card reader control device 288 is received within a predetermined time, the routine RN221
Then, it is checked whether the response is normal. If there is an error, the process jumps to the routine RN227 as in the case of time over, and executes error processing. On the other hand, if the response is normal, the "card rear ejection" command is transmitted to the card reader control device 288 to set the timer (routines RN222, RN223). Then, before the timer times out, the card reader controller 288
Check if there is a response from the routine (routine RN
224, RN225). If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormality bit of the status 2 to "1", and shifts to the error processing routine of FIG.

If a response from the card reader control device 288 is received within a predetermined time, the routine RN22
The process proceeds to step 6 to check whether the response is normal. If there is an error, the process jumps to the routine RN227 as in the case of time over, and executes error processing. On the other hand, if the response is normal, the process returns to the original routine (FIG. 335).

FIG. 339 shows a specific procedure of the printing process in the card recovery process flow of FIG. 335.

[1335] Here, after setting the timer first,
Before the timer times out, it is checked whether or not the fourth traveling position sensor CPS4 is turned on (routines RN245 to RN247). Fourth travel position sensor CP
If the time is over before S4 is turned on, the routine jumps to routines RN265 and R266, sets "1" in the jam error bit of status 1, and sets "1" in the printer error bit of status 2. Then, the process proceeds to the error processing in FIG.

If the fourth traveling position sensor CPS4 is turned on before the time over occurs, the routine RN
Proceeding to 248, the print motor 751 is rotated,
Before the time over occurs, the third traveling position sensor CPS
3 is turned off (routine RN24)
9, RN250). Here, when the time is over, the process jumps to the routine RN265 and shifts to error processing. When the third traveling position sensor CPS3 is turned off within a predetermined time, the transport motor 706 driven by the routine RN235 in FIG. 338 is stopped. Then, before the time is over, it is checked whether or not the fourth traveling position sensor CPS4 is turned off (routines RN251 to RN253).
Here, when the time is over, the routine jumps to the routine RN265 as described above. On the other hand, if the fourth traveling position sensor CPS4 is turned off before the time is over, the routine proceeds to a routine RN254, in which the printhead elevating motor 758 is rotated by 180 ° to lower the head. then,
It is determined whether or not the received function is “card resurrection” (routine RN255).
In step 6, the serial number and the date are printed, and if the function code is NO, that is, the "test card issuance" function code, the characters "TEST" indicating the test card are printed (routines RN256 to RN259).

Thereafter, the head raising / lowering motor 758 is again rotated by 180 ° to raise the print head 756, and a new timer is set (routines RN261 and RN26).
2). Thereafter, it is checked whether or not the fifth traveling position sensor CPS5 is turned on before the timer times out (routines RN263, RN264). After setting "1" to the status 2 and "1" to the printer error bit of the status 2, the flow shifts to the error processing of FIG. 341. On the other hand, if the fifth traveling position sensor CPS5 is turned on before the time is over, the process returns to the original routine (FIG. 335).

FIG. 340 shows a specific procedure of card ejection processing in the card restoration processing flow of FIG. 335.

When this process is started, first, the lead-out solenoid 779 in the card lead-out device 770 is turned on to rotate the track switching member 777 downward, and then the transport motor 70
6 is started and a timer is set (routines RN268 to RN270). Thereby, the printing device 7
The card sent out from the card 50 is transferred to the card issuing port 202 through the dispensing device 770. And
If the fifth traveling position sensor CPS5 is turned off before the timer set in the routine RN270 has timed out, the printing motor 751 in the printing device 750 is stopped (routines RN271 to RN273). This is because the card has already been sent from the printing device 750. If the time runs out before the fifth traveling position sensor CPS5 is turned off, the routine R279, RN28
Then, the process goes to 0 to set “1” to each of the status 1 jam error bit and the status 2 card transport error bit, and then goes to the error processing of FIG. 341.

At the above routine RN273, the print motor 7
After stopping the 51, the timer set in the routine RN270 is checked again, and if the sixth traveling position sensor CPS6 immediately before the card issuing port 202 is turned on before the time is over, the derived solenoid 779 is turned off ( Routines RN274 to RN276). If the timer times out before the sixth traveling position sensor CPS6 is turned on, the routine shifts to the routine RN279.

[1341] Derived solenoid 77 in routine RN276
After turning off No. 9, a new timer is set, and after 0.5 seconds, the transport motor 706 is stopped. 0.5 above
The second is determined from the relationship with the rotation speed of the transport motor 706, and the transport belt 77
2 is enough time to move the card a distance equal to its full length l0. By waiting 0.5 seconds after the sixth traveling position sensor CPS6 detects the card, the card is stopped in a state where it is protruded about two thirds from the card issuing port 202. The sixth traveling position sensor CPS6 is turned off when the player manually pulls out the card from the issuing port 202.

FIG. 341 shows error processing executed when a time-over occurs before the various sensors CPS1 to CPS6 for detecting the position of the card are turned on or off in the processing flows of FIGS. 336 to 340. The specific procedure is shown.

In this process, first, the card issuing device 700
All motors (extraction motor 719, transport motor 7
06, printing motor 751 and head lifting / lowering motor 75
8) is stopped, and an “abnormal termination” function is transmitted to the central processing unit (routines RN151 and RN15).
2). Next, it is determined whether or not a function has been transmitted from the central processing unit (routine RN153).
It is determined whether or not the error has been recovered by checking the sensor in 0 (routine RN154). If the error has not been recovered, the process returns to the routine RN153 and waits until the error is recovered. While waiting for recovery, the card issuing device 70
When the cause of the error disappears, for example, when the card stuck in 0 is removed, the process proceeds to the routine RN155 to clear each abnormal bit of the status 1 and 2 to “0”, and then proceeds to the routine RN156 to remove the card. The counters 795 and 796 for counting the number of cards and the number of confiscated cards are updated, and the routine RN1 in the main processing flow (FIG. 334) is updated.
11 (see reference numeral V1).

On the other hand, if a function from the central processing unit is received while waiting for the error recovery in the routines RN153 and RN154, the routine shifts to the routine RN157, and the received function sets the "status request".
It is determined whether the function is a function, and if yes, a "status transmission" function is transmitted in the next routine RN158, and the process returns to the routine RN153 to wait until the error is restored again. This flow is the same as that of the issuing card issuing device, and the unit controller 29 of the issuing machine is used.
It is prepared assuming a “status request” from 0. If the function received during the error recovery wait is not “status request”, the reception function sets “initial value transmission” in routine RN159.
It is determined whether or not the function is a function. If "initial value transmission" is found, the date and the identification code in the function are stored in the internal memory, a "normal end" function is transmitted, the routine returns to the routine RN153, and an error occurs again. Is waited for (steps RN160 and RN161).

If the function received while waiting for error recovery is neither “status request” nor “initial value transmission”, the routine returns from routine RN159 to RN152, transmits the “abnormal termination” function, and then performs error recovery. wait.

The control flow of the card reader 800 by the card reader control device 288 based on the command from the card issuance control device 790 is described below.
0 is the same as the control flow of the card reader control device.

[1347] The major difference from the control flow relating to the card reader in the control unit 160 of the pachinko machine is that the control flow for writing and verifying the magnetic code and the flow for ejecting the card to the rear of the card reader instead of to the front are as follows. It has a point.

As described above, the card reader control device 2
The communication between the card issuance control device 790 and the card issuance control device 790 is performed by command transmission as described above. The communication command from the card issuance control device 790 to the card reader control device 288 includes the magnetic data of the card. A magnetic write command instructing to record the data, a magnetic read command instructing to read the magnetic data and the security code of the card and each information of the punch hole and send the magnetic data, and send the read security data. "Security requirements" to instruct
Command, a "punch hole request" command to send the read punch hole data, a "reload" command to reread the data of the card held in the card reader, and punch a hole in the card. Command to eject the card in the card reader, a command to eject the card in the card reader toward the front insertion slot, and an instruction to eject the card in the card reader backward. There are nine types of commands: a "card rear ejection" command, a "cancel" command for canceling a card reading command, and a "status request" command for instructing transmission of status information indicating the status of the card reader.

[1348] Of these, "magnetic read" and "reload"
The command is not used in the issuing machine 200, and "magnetic write"
The command is not used in the checkout machine 300 or the management device 400. The “magnetic read” command is transmitted to the card reader 8.
00 is instructed to read not only magnetic data but also all data on the card, and requests transmission of only magnetic data. Data request commands are separately prepared for security data and punch hole data.

[1350] Card reader control device 2 of management device 400
Since the control procedure by 88 is the same as that of the issuing machine 200, the description is omitted.

In the above embodiment, the backup auxiliary power supply is provided only in the management device 400, and the operation data of the pachinko machine 100 is periodically collected.
Alternatively, when the data relay means interposed between the pachinko machine 100 and the management device 400 goes down and recovers thereafter, the management device 400 sends restoration data to the terminal device and then gives a command to start again, and also gives a restart command. Is given a re-read command to eject the card once and read it again to the card reader, but a memory for storing its own operation data in the pachinko machine and a backup of the memory An auxiliary power supply may be provided, and when a power failure occurs, only its memory may be backed up to store operation data. Further, in the present embodiment, a storage medium type game facility for playing a game using a card as a storage medium has been described, but the present invention is not limited to this.

[1352]

As described above, the present invention relates to a gaming machine in which a plurality of gaming machines and a management device capable of collecting operation data of these gaming machines are communicable by transmission means. The device includes an operation data collection unit that can collect operation data of the gaming device, a first storage unit that stores operation data collected by the operation data collection unit, and an operation data stored in the first storage unit. Storage means capable of storing operating data, and operation data transfer means for transferring the operation data stored in the first storage means to the second storage means for storing the operation data. The operation data stored in the first storage means is transferred to and stored in the second storage means in relation to the tally management period of, so that the operation data collected from each gaming machine is stored. Store over data in the first storage means, the second in connection with this operation data to the aggregation management period of sales data
The data can be transferred to the storage means and stored, so that various operation data generated in a large number of gaming devices can be stored for several days without significantly increasing the storage capacity of the first storage means. As a result, for example, there is an effect that the characteristics of each gaming machine and the business performance of the entire game store are analyzed, and the business policy can be appropriately determined.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram showing an overall configuration of a pachinko gaming system to which the present invention is applied.

FIG. 2 is a front view and an internal configuration diagram showing an example of a card used in the system according to the present invention.

FIG. 3 is an explanatory diagram illustrating a configuration example of a true / false identification area in the card and a cross-sectional view illustrating an example of a cross-sectional structure of the card.

FIG. 4 is an explanatory diagram showing a configuration example of a magnetic recording unit in the card.

FIG. 5 is a perspective view showing a configuration example of an entire pachinko machine constituting the gaming system.

FIG. 6 is a cross-sectional side view showing a configuration example of an operation panel on the front of the pachinko machine.

FIG. 7 is an exploded perspective view of an operation panel on the front of the pachinko machine.

FIG. 8 is a perspective view showing a configuration inside an operation panel unit on the front of the pachinko machine.

FIG. 9 is a perspective view showing an example of the configuration of a sealed ball circulation device on the back of a pachinko machine.

FIG. 10 is a perspective view showing a state in which the sealed ball circulation device is attached to a pachinko machine.

FIG. 11 is a perspective view showing details of a base of the hit ball firing rail.

FIG. 12 is a perspective view showing a state where a front panel of the pachinko machine is opened.

FIG. 13 is a perspective view showing a configuration example of a frame holding a game board and a frame board provided with a firing rail coupled thereto.

FIG. 14 is a perspective view showing a rear surface configuration of a front frame of the pachinko machine.

FIG. 15 is a rear perspective view showing a configuration example of a rear surface of the pachinko machine.

FIG. 16 is a perspective view showing a configuration example of a pachinko machine control unit.

FIG. 17 is a perspective view showing an internal configuration of a pachinko machine control unit.

FIG. 18 is a perspective view showing a configuration of a front panel of the control unit.

FIG. 19 is a perspective view showing a mounting positional relationship between the pachinko machine and the control unit.

FIG. 20 is a perspective view showing a framework of an island facility in which a pachinko machine is installed.

FIG. 21 is a perspective view showing a state where a pachinko machine and a control unit are installed in the island facility.

FIG. 22 is a perspective view showing a back surface of the island facility.

FIG. 23 is a block diagram showing a control system of the whole pachinko machine.

FIG. 24 is a block diagram illustrating a circuit configuration example of a pachinko machine control device.

FIG. 25 is a block diagram illustrating a circuit configuration example of a pachinko machine control unit.

FIG. 26 is a memory map showing an area configuration of a unit memory.

FIG. 27 is a perspective view showing a configuration example of a card reader of a pachinko machine.

FIG. 28 is an exploded perspective view of the card reader.

FIG. 29 is an exploded perspective view showing details of a card insertion portion of the card reader.

FIG. 30 is a sectional side view showing details of a card insertion portion of the card reader.

FIG. 31 is a sectional side view showing details of a shutter portion at the entrance of the card reader.

FIG. 32 is an explanatory plan view showing a mounting positional relationship of various sensors provided in the card reader.

FIG. 33 is a detection timing chart of a sensor when a card is inserted.

FIG. 34 is a block diagram illustrating a circuit configuration example of a card reader control device.

FIG. 35 is a block diagram showing an interface circuit of the card reader.

FIG. 36 is a timing chart showing data reading and writing timings of the card reader.

FIG. 37 is a perspective view showing a configuration example of a card issuing machine used in the gaming system according to the present invention.

FIG. 38 is a perspective view showing a state where a front panel of the issuing machine is opened.

FIG. 39 is a perspective view of a card issuing device provided in the issuing machine.

FIG. 40 is a schematic configuration diagram of the card issuing device.

FIG. 41 is a perspective view showing the configuration of a card ejection device that constitutes the card issuing device.

FIG. 42 is a perspective view illustrating a configuration of a card deriving device that configures the card issuing device.

FIG. 43 is a block diagram illustrating a configuration example of a control device of the card issuing machine.

FIG. 44 is a block diagram illustrating a configuration example of a unit control device of a card issuing machine.

FIG. 45 is a perspective view showing a configuration example of a checkout machine.

FIG. 46 is a perspective view showing a state where a top panel and a front panel of the checkout machine are opened.

FIG. 47 is a perspective view showing a configuration example of a card payment device constituting a payment device.

FIG. 48 is a perspective view showing a case where a counter of a game arcade is configured using the payment machine of the present embodiment.

FIG. 49 is an explanatory diagram showing a configuration example of a receipt issued by a checkout machine.

FIG. 50 is a block diagram illustrating a configuration example of a control device of a checkout machine.

FIG. 51 is a block diagram illustrating a configuration example of a unit control device of a checkout machine.

FIG. 52 is a perspective view illustrating a configuration example of the entire management device.

FIG. 53 is a block diagram illustrating a system configuration example of a management device.

FIGS. 54A and 54B show a configuration example of a console of the management device, wherein FIG. 54A is a plan view and FIG.

FIG. 55 is a memory map showing a configuration example of a file in a main storage device.

FIG. 56 is an explanatory diagram showing a state transition of a card in the gaming system of the present invention.

FIG. 57 is a block diagram illustrating a configuration example of a transmission system in the gaming system of the present invention.

FIG. 58 is a block diagram illustrating a connection method of a transmission system when a transmission path is configured by an optical cable.

FIG. 59 is a block diagram illustrating a connection method of a transmission system when a transmission path is configured by a coaxial cable.

FIG. 60 is a diagram showing an example of controlling data transfer on a network.
FIG. 3 is a block diagram illustrating a configuration example of an AU (network adapter unit).

FIG. 61 is a perspective view showing the appearance of the NAU.

FIG. 62 is a configuration diagram showing a packet structure between the management device and the NAU and between the management device and the unit on the high-layer network, and a configuration showing a packet structure between the management device and the NAU and between the management device and the unit on the low-layer network. FIG.

FIG. 63: “Line test” packet and response “AC”
It is a block diagram of a K "packet.

FIG. 64 is a configuration diagram of a “unit table request” packet and its response packet.

FIG. 65 is a configuration diagram of an “initial value setting” packet and its response packet.

FIG. 66 is a configuration diagram of a “periodic data request” from the management device to the pachinko machine and a response packet thereof.

FIG. 67: “Various command” packets and response “AC”
It is a block diagram of a K "packet.

FIG. 68: “Card-in” packet and response “AC”
It is a block diagram of a "K" and negative acknowledgment "NAK" packet.

FIG. 69: “Card-in” packet and response “AC”
It is a block diagram of a "K" and a negative acknowledgment "NAK" packet.

FIG. 70: “Card-in” packet and its response “AC”
It is a block diagram of a "K" and negative acknowledgment "NAK" packet.

FIG. 71 is a configuration diagram of a “scheduled data transmission” packet from the pachinko machine to the NAU.

FIG. 72 is a configuration diagram of “unit recovery data” for a pachinko machine on a low-layer network and a response packet thereof.

FIG. 73 is a configuration diagram of a “card purchase” packet, a response “ACK” packet, and a negative response “NAK” packet between the issuer and the NAU on the low-layer network.

FIG. 74 is a configuration diagram of a “scheduled data transmission” packet from an issuer to a NAU.

FIG. 75 is a configuration diagram of a “unit recovery data” packet and a response “ACK” packet for an issuing machine on a low-layer network.

FIG. 76 is a configuration diagram of a “card checkout” packet, a response “ACK” and a negative response “NAK” packet to a checkout machine on a low-layer network.

FIG. 77: “Card settlement end” packet and response “A”
It is a block diagram of a "CK" and a negative acknowledgment "NAK" packet.

FIG. 78 is a configuration diagram of a “scheduled data transmission” packet from the checkout machine to the NAU.

FIG. 79 is a configuration diagram of a “unit recovery data” packet and a response “ACK” packet to the checkout machine.

FIG. 80 is a flowchart showing a data transmission control procedure in the NAU data transmission controller.

FIG. 81 is a flowchart showing a control procedure for detecting a token bus abnormality by a timer interrupt in the NAU.

FIG. 82 is a flowchart showing a procedure for initializing the entire system.

FIG. 83 is a system flowchart showing a procedure from a unit table request to a setting of an initial value for a unit by the management device.

FIG. 84 is a system flowchart showing a procedure for collecting periodic data from each terminal by the management device.

FIG. 85 is a system flowchart showing a processing procedure of a store opening instruction to each terminal by the management device.

FIG. 86 is a system flowchart showing a processing procedure in a case where a bill is inserted in a card issuing reservation and a card issuing machine and a purchase switch is turned on.

FIG. 87 is a system flowchart showing a processing procedure when a card is inserted into a suspended pachinko machine.

FIG. 88 is a system flowchart showing a processing procedure when a suspending switch of a pachinko machine is turned on during a game.

FIG. 89 is a system flowchart showing a processing procedure when a card is inserted into a suspended pachinko machine.

FIG. 90 is a system flowchart showing a processing procedure when the game end switch of the pachinko machine is turned on during the game.

FIG. 91 is a system flowchart showing a processing procedure when both the number of balls held and the amount of money of a card become zero during a game.

FIG. 92 is a system flowchart showing a processing procedure when a hit occurs during a game.

FIG. 93 is a system flowchart showing a processing procedure when a card is inserted into a checkout machine.

FIG. 94 is a system flowchart showing an interruption end processing procedure when an interrupted card is settled in an adjustment machine.

FIG. 95 is a system flowchart showing a processing procedure when a stop release command is input from the console of the management device.

FIG. 96 is a system flowchart showing a processing procedure when a forcible termination command is input to the pachinko machine from the console of the management device.

FIG. 97 is a system flowchart showing a processing procedure when a forcible termination command is issued to the issuing machine or the payment machine from the console of the management device.

FIG. 98 is a system flowchart showing a processing procedure in the case of canceling termination of a terminal being forcibly terminated.

FIG. 99 is a system flowchart showing a detection processing procedure when a unit goes down.

FIG. 100 is a system flowchart showing a unit restoration processing procedure in which the management device restores data of the terminal device when the downed unit is restored.

FIG. 101 is a system flowchart showing a data recovery processing procedure for each terminal when the NAU is detected to be down and the NAU recovers thereafter.

FIG. 102 is a system flowchart showing a system closing process procedure from a store closing command to each terminal by the management device.

FIG. 103 is a system flowchart showing a processing procedure when a power outage is detected.

FIG. 104 is a system flowchart showing a procedure of a system start-up process after recovery from a power failure.

FIG. 105 is a flowchart showing an initialization procedure of a central processing unit and a local processing unit in the management device.

FIG. 106 is a flowchart showing an initialization procedure of a central processing unit and a local processing unit in the management device.

FIG. 107 is a flowchart showing an initialization procedure of the central processing unit and the local processing unit in the management device.

FIG. 108 is a flowchart showing an initialization procedure of the central processing unit and the local processing unit in the management device.

FIG. 109 is a flowchart showing a processing procedure when a built-in switch on the back of the console is turned on in the management device.

FIG. 110 is a flowchart showing a processing procedure when a setting update switch on the upper surface of the console is turned on in the management device.

FIG. 111 is a flowchart showing a routine data request processing procedure by a timer interrupt;

FIG. 112 is a flowchart showing the procedure of a process for receiving periodic data as a response.

FIG. 113 is a flowchart showing a processing procedure when the management device receives a “card purchase” packet.

FIG. 114 is a flowchart showing a processing procedure when the management device receives a “card-in” packet.

FIG. 115 is a flowchart showing a processing procedure when the management device receives an “interrupted card-in” packet.

FIG. 116 is a flowchart showing a processing procedure when the management device receives an “interruption switch” packet.

FIG. 117 is a flowchart showing a processing procedure when the management device receives an “end switch” packet.

FIG. 118 is a flowchart showing a processing procedure when the management device receives a “return-to-zero” packet.

FIG. 119 is a flowchart showing a processing procedure when the management device receives a “stop” packet.

FIG. 120 is a flowchart showing a processing procedure when the management device receives a “card settlement” packet.

FIG. 121 is a flowchart showing a processing procedure when a hit release switch on the upper surface of the console is turned on in the management device.

FIG. 122 is a flowchart showing a processing procedure when a forced termination switch on the upper surface of the console is turned on in the management apparatus.

FIG. 123 is a flowchart showing a processing procedure when a forced termination switch on the upper surface of the console is turned on in the management apparatus.

FIG. 124 is a flowchart showing a processing procedure when a forced termination switch on the upper surface of the console is turned on in the management apparatus.

FIG. 125 is a flowchart showing a processing procedure when a forced termination release switch on the console upper surface is turned on in the management device.

FIG. 126 is a flowchart showing a processing procedure when a forced termination release switch on the console upper surface is turned on in the management apparatus.

FIG. 127 is a flowchart showing a processing procedure when a forced termination release switch on the upper surface of the console is turned on in the management device.

FIG. 128 is a flowchart illustrating a procedure of a power failure process in the management device when a power failure occurs.

FIG. 129 is a flowchart illustrating a procedure of a network error recovery process in the management device.

130 is a flowchart (A) showing a specific procedure of the NAU recovery processing in the processing flow of FIG. 129 and a flowchart (B) showing a specific procedure of the token bus recovery processing in the processing flow of FIG. 129.

FIG. 131 is a flowchart showing a specific procedure of a hot code recovery process in the process flow of FIG. 129;

132 is a flowchart showing a specific procedure of unit recovery processing in the processing flow of FIG. 129.

FIG. 133 is a flowchart showing a processing procedure when a store close switch on the upper surface of the console is turned on in the management device.

FIG. 134 is a flowchart showing a processing procedure when a card recovery switch on the upper surface of the console is turned on in the management device.

FIG. 135 is a flowchart showing a processing procedure when the test card issuing switch on the back of the console is turned on in the management device.

FIG. 136 is a flowchart showing the procedure of an interrupt display process of business statistical data by a timer interrupt.

Fig. 137 is a flowchart showing a procedure of a data display process of a hitting table.

FIG. 138 is a flowchart showing the procedure of data display processing for a specific device.

FIG. 139 is a flowchart showing the procedure of a data display process for all devices.

FIG. 140 is a flowchart showing the procedure of data display processing for a red box;

FIG. 141 is a flowchart showing a procedure of a data display process for a surplus table;

FIG. 142 is a flowchart showing a procedure of a data display process of the issuing machine.

FIG. 143 is a flowchart showing a procedure of a data display process of the checkout machine.

FIG. 144 is a flowchart showing the procedure of all sales data display processing.

FIG. 145 is a flowchart showing the procedure of data display processing of a specific card.

FIG. 146 is a flowchart showing the procedure of card total data display processing.

FIG. 147 is a flowchart showing the procedure of all-card details data display processing.

Fig. 148 is a flowchart showing the procedure of data display processing of a suspended card.

FIG. 149 is a flowchart showing a card number generation procedure in the management device.

FIG. 150 is a display screen configuration diagram showing a configuration example of an initial screen displayed on a CRT display device in the management device.

FIG. 151 is a display screen configuration diagram showing a configuration example of an abnormal terminal display screen displayed on the CRT display device in the management device.

FIG. 152 is a display screen configuration diagram showing a configuration example of a store opening request screen displayed on a CRT display device in the management device.

FIG. 153 is a display screen configuration diagram showing a configuration example of an initial value setting screen displayed on a CRT display device in the management device.

FIG. 154 is a display screen configuration diagram showing a configuration example of an initial value setting screen displayed on the CRT display device in the management device.

FIG. 155 is a display screen configuration diagram showing a configuration example of an initial value setting screen displayed on a CRT display device in the management device.

FIG. 156 is a display screen configuration diagram showing a configuration example of a number of hits setting screen displayed on the CRT display device in the management device.

FIG. 157 is a display screen configuration diagram showing a configuration example of a hitting mode setting screen displayed on the CRT display device in the management device.

FIG. 158 is a display screen configuration diagram showing a configuration example of a date and time setting screen displayed on the CRT display device in the management device.

FIG. 159 is a display screen configuration diagram showing a configuration example of a normal display screen during business hours displayed on the CRT display device in the management device.

FIG. 160 is a display screen configuration diagram showing a configuration example of a hit release screen displayed on a CRT display device in the management device.

FIG. 161 is a display screen configuration diagram showing a configuration example of a pachinko machine forced termination screen displayed on the CRT display device in the management device.

FIG. 162 is a display screen configuration diagram showing a configuration example of a pachinko machine forced termination cancellation screen displayed on the CRT display device in the management device.

FIG. 163 is a display screen configuration diagram showing a configuration example of an issuer forced termination cancellation screen displayed on the CRT display device in the management device.

FIG. 164 is a display screen configuration diagram showing a configuration example of a checkout device forced termination cancellation screen displayed on the CRT display device in the management device.

FIG. 165 is a display screen configuration diagram illustrating a configuration example of a system end screen displayed on a CRT display device in the management device.

FIG. 166 is a display screen configuration diagram showing a configuration example of a card recovery screen displayed on the CRT display device in the management device.

FIG. 167 is a display screen configuration diagram showing a configuration example of a display menu selection screen displayed on the CRT display device in the management device.

FIG. 168 is a display screen configuration diagram showing a configuration example of a hit table display screen displayed on the CRT display device in the management device.

FIG. 169 is a display screen configuration diagram illustrating a configuration example of a specific-unit display screen displayed on a CRT display device in the management device.

FIG. 170 is a display screen configuration diagram showing a configuration example of an all-unit data display screen displayed on a CRT display device in the management device.

FIG. 171 is a configuration diagram of a display screen showing a configuration example of a data table for displaying data in a red circle displayed on a CRT display device in the management device;

FIG. 172 is a display screen configuration diagram showing a configuration example of an issuer data display screen displayed on a CRT display device in the management device.

FIG. 173 is a display screen configuration diagram showing a configuration example of a checkout machine data display screen displayed on a CRT display device in the management device.

FIG. 174 is a display screen configuration diagram showing a configuration example of a sales data display screen displayed on a CRT display device in the management device.

FIG. 175 is a display screen configuration diagram showing a configuration example of a specific card data display screen displayed on a CRT display device in the management device.

FIG. 176 is a display screen configuration diagram showing a configuration example of a card detail data display screen displayed on a CRT display device in the management device.

FIG. 177 is a display screen configuration diagram showing a configuration example of a suspended card data display screen displayed on the CRT display device in the management device.

FIG. 178 is a flowchart illustrating a procedure of packet transmission / reception control in NAU.

FIG. 179 is a flowchart illustrating a procedure of packet transmission / reception control in NAU.

FIG. 180 is a flowchart showing the procedure of packet transmission / reception control in NAU.

FIG. 181 is a flowchart illustrating a procedure of packet transmission / reception control in NAU.

FIG. 182 is a state transition diagram in a normal operation mode showing a transition of an operation state of the pachinko machine;

FIG. 183 is a state transition diagram in a test mode at the time of on-line and a state transition diagram in a test mode at the time of an off-line showing a transition of an operation state of the pachinko machine;

FIG. 184 is a flowchart at the time of initialization and reception of a store opening packet.

FIG. 185 is a flowchart when a card is inserted into a card reader.

FIG. 186 is a flowchart when a suspend switch is turned on.

FIG. 187 is a flowchart when the settlement switch is turned on.

FIG. 188 is a flowchart when a zero-reset state occurs.

FIG. 189 is a flowchart when a hit state occurs.

FIG. 190 is a flowchart when a “forced end” packet is received.

FIG. 191 is a flowchart at the time of unit recovery after power failure recovery.

FIG. 192 is a flowchart showing the procedure of a timer interrupt process.

FIG. 193 is a flowchart showing the procedure of serial interrupt processing.

194 is a diagram showing a sensor in the interrupt processing flow of FIG. 192;
It is a flowchart which shows the specific procedure of a switch detection process.

FIG. 195 is a flowchart showing a specific procedure of the switch invalidation processing of FIG. 192.

FIG. 196 is a flowchart showing the procedure of an initialization task that is one of the main tasks of the unit controller.

FIG. 197 is a flowchart showing the procedure of a packet reception task.

FIG. 198 is a flowchart showing a specific procedure of “initial value setting” packet reception processing during the packet reception task of FIG. 197;

FIG. 199 is a flowchart showing a specific procedure of a “store opening code” packet receiving process.

FIG. 200 is a flowchart showing a specific procedure of a “closing code” packet receiving process.

FIG. 201 is a flowchart showing a specific procedure of a “forced termination request” packet receiving process.

FIG. 202 is a flowchart showing a specific procedure of a “forced termination release” packet receiving process.

FIG. 203 is a flowchart showing a specific procedure of a “cancel release” packet receiving process.

FIG. 204 is a flowchart showing a specific procedure of “interruption end” packet reception processing.

FIG. 205 is a flowchart showing a specific procedure of a “unit recovery data” packet receiving process.

FIG. 206 is a flowchart showing a specific procedure of a “restart” packet reception process.

FIG. 207 is a flowchart showing a specific procedure of a “card in ACK” and “suspended card in ACK” packet reception process.

FIG. 208 is a flowchart showing a specific procedure of a “suspension switch ACK” packet reception process.

FIG. 209 is a flowchart illustrating a specific procedure of “end switch ACK” packet reception processing.

FIG. 210 is a flowchart showing a specific procedure of a “return-to-zero ACK” packet reception process.

FIG. 211 is a flowchart showing a specific procedure of a “stop ACK” packet reception process.

FIG. 212 is a flowchart showing a procedure of a reader control task which is one of the main tasks of the unit controller.

FIG. 213 is a flowchart showing a specific procedure of a “test card” function reception process in the reader control task of FIG. 212.

FIG. 214 is a flowchart showing a specific procedure of a “card number” function receiving process in the reader control task of FIG. 212.

FIG. 215 is a flowchart showing a specific procedure of “status” function reception processing during the reader control task of FIG. 212.

FIG. 216 is a flowchart showing a specific procedure of a “retransmission request” function receiving process in the reader control task of FIG. 212.

FIG. 217 is a flowchart showing a specific procedure of a “normal end” function receiving process in the reader control task of FIG. 212.

FIG. 218 is a flowchart showing a specific procedure of “abnormal termination” function reception processing during the reader control task of FIG. 212.

FIG. 219 is a flowchart showing a specific procedure of an “initial value request” function receiving process in the reader control task of FIG. 212.

FIG. 220 is a flowchart showing a specific procedure of a “self-discharge” function receiving process during the reader control task of FIG. 212.

FIG. 221 is a flowchart showing a specific procedure of a function transmission process during the reader control task of FIG. 212.

FIG. 222 is a flowchart showing the procedure of a packet transmission task which is one of the main tasks of the unit controller.

FIG. 223 is a flowchart showing a procedure of an error control task which is one of the main tasks of the unit controller.

FIG. 224 is a flowchart showing the procedure of a ball count calculation task which is one of the main tasks of the unit controller.

FIG. 225 is a flowchart showing the procedure of a switch detection task which is one of the main tasks of the unit controller.

FIG. 226 is a flowchart showing a specific procedure of a hitting process during the switch detection task of FIG. 225;

FIG. 227 is a flowchart showing a specific procedure of interrupt switch processing during the switch detection task of FIG. 225;

FIG. 228 is a flowchart showing a specific procedure of a purchase switch process during the switch detection task of FIG. 225;

FIG. 229 is a flowchart showing a specific procedure of end switch processing during the switch detection task of FIG. 225;

230 is a flowchart showing a specific procedure of test switch processing during the switch detection task of FIG. 225.

FIG. 231 is a flowchart showing a specific procedure of a test mode end process during the end switch process of FIG. 229;

FIG. 232 is a flowchart showing a procedure of a sound control task which is one of the main tasks of the unit controller.

FIG. 233 is a flowchart showing the procedure of a timer control task, which is one of the main tasks of the unit controller.

FIG. 234 is a flowchart showing the procedure of a lamp display control task which is one of the main tasks of the unit controller.

FIG. 235 is an input / output timing chart in the unit control device.

FIG. 236 is a flowchart showing an outline of the entire control procedure by the card reader controller.

FIG. 237 is a flowchart showing a more detailed procedure of the flow in FIG. 236.

FIG. 238 is a flowchart showing a more detailed procedure of the flow in FIG. 236.

FIG. 239 is a flowchart showing a more detailed procedure of the flow in FIG. 236.

240 is a flowchart showing a more detailed procedure of the flow in FIG. 236.

FIG. 241 is a flowchart showing a more detailed procedure of the flow in FIG. 236.

FIG. 242 is a flowchart showing a processing procedure when receiving an “initial value setting” function.

FIG. 243 is a flowchart showing a processing procedure when a “card accepted” function is received.

FIG. 244 is a flowchart showing a processing procedure when a “card cannot be accepted” function is received.

FIG. 245 is a flowchart showing a processing procedure when a “card ejection” function is received.

FIG. 246 is a flowchart showing a processing procedure when a “reload” function is received.

FIG. 247 is a flowchart showing a processing procedure when a “return-to-zero” function is received.

FIG. 248 is a flowchart showing a processing procedure when a “status request” function is received.

FIG. 249 is a flowchart illustrating a processing procedure when a “retransmission request” function is received.

250 is a flowchart showing a specific procedure of punch processing in the flows of FIGS. 245 and 247.

FIG. 251 is a flowchart showing a specific procedure of a punching process in the flow of FIG. 250.

FIG. 252 is a flowchart showing the procedure of timer interrupt processing in the card reader controller.

FIG. 253 is a flowchart showing a procedure of a timer interrupt process in the card reader controller.

FIG. 254 is a flowchart showing a specific procedure of transmission processing during the control flow of FIGS. 237 to 241 and the like.

255 is a flowchart showing a specific procedure of a reception process during the control flow of FIGS. 237 to 241. FIG.

FIG. 256 is a flowchart showing a specific procedure of the control flow of FIGS. 237 to 241 and a card ejection process during each function reception process of FIGS. 244 to 247.

FIG. 257 is a flowchart showing a specific procedure of card insertion processing in the control flows of FIGS. 237 to 241.

FIG. 258 is a flowchart showing a specific procedure of a card reading process in the flow of FIG. 257.

FIG. 259 is a flowchart showing a specific procedure of magnetic processing in the flows of FIGS. 257 and 258.

260 is a flowchart showing a specific procedure of a 1-bit reading process during the magnetic process of FIG. 259.

FIG. 261 shows parity and L in the flow of FIG. 257.
It is a flowchart which shows the specific procedure of RC inspection processing.

FIG. 262 is a flowchart showing a specific procedure of a security inspection process in the flow of FIG. 257;

FIG. 263 is a flowchart showing a specific procedure of punch hole inspection processing in the flow of FIG. 257.

FIG. 264 is a flowchart showing a specific procedure of card magnetic data inspection processing in the flow of FIG. 257.

FIG. 265 is a flowchart showing a specific procedure of an identification code inspection process in the flow of FIG. 257.

FIG. 266 is a flowchart showing a control procedure in the pachinko machine controller.

FIG. 267 is a flowchart showing a control procedure in the pachinko machine controller.

FIG. 268 is a flowchart showing a control procedure in the pachinko machine controller.

FIG. 269 is a flowchart showing a control procedure in the pachinko machine controller.

FIG. 270 is a flowchart showing a control procedure in the pachinko machine controller.

FIG. 271 is a flowchart showing a procedure of a timer interrupt process in the pachinko machine controller.

FIG. 272 is a flowchart showing a control procedure of a main process in a unit controller of the card issuing machine.

FIG. 273 is a flowchart illustrating an example of a specific procedure of a packet reception process in the flow of FIG. 272.

FIG. 274 is a flowchart showing a specific procedure of card number reservation processing in the flow of FIG. 272;

FIG. 275 is a flowchart showing a specific procedure of card purchase processing in the flow of FIG. 272.

FIG. 276 shows “initial value setting” in the flow of FIG. 273;
It is a flowchart which shows the processing procedure at the time of packet reception.

FIG. 277 is a flowchart showing a processing procedure when receiving a “unit recovery data” packet in the flow of FIG. 273.

FIG. 278 is a flowchart showing a processing procedure when a “forced termination release” packet is received in the flow of FIG. 273.

FIG. 279 is a flowchart showing a processing procedure when a “forced end” packet is received in the flow of FIG. 273.

FIG. 280 is a flowchart showing the contents of an interrupt process executed by a timer interrupt in the unit controller of the issuing machine separately from the main process.

FIG. 281 is a flowchart showing a control procedure by the card issuance control device.

FIG. 282 shows “Card issue” in the flow of FIG. 281;
It is a flowchart which shows the specific control procedure at the time of receiving a function.

FIG. 283 is a flowchart showing a specific procedure of card ejection processing in the flow of FIG. 282.

FIG. 284 is a flowchart showing a specific procedure of reader control processing in the flow of FIG. 282.

FIG. 285 is a flowchart showing a specific procedure of card inversion processing in the flow of FIG. 282.

FIG. 286 is a flowchart showing a specific procedure of printing and printing 2 processing in the flow of FIG. 282.

FIG. 287 is a flowchart showing a specific procedure of card ejection processing in the flow of FIG. 282.

FIG. 288 is a flowchart showing a specific procedure of stack processing in the flow of FIG. 282.

FIG. 289 is a flowchart showing a specific procedure of error processing executed when an error occurs in each processing flow of FIGS. 283 to 288.

FIG. 290 is a flowchart showing a control procedure common to the issuing machine and the card reader control device in the checkout machine.

FIG. 291 is a flowchart showing a specific control procedure of the card reader control device at the time of receiving a “magnetic read” command.

FIG. 292 is a flowchart showing a specific control procedure of the card reader control device when a “reload” command is received.

FIG. 293 is a flowchart showing a specific control procedure of the card reader control device when a “magnetic write” command is received.

FIG. 294 is a flowchart showing a specific control procedure of the card reader control device when a “status request” command is received.

FIG. 295 is a flowchart showing a specific control procedure of the card reader control device when a “punch hole request” command is received.

FIG. 296 is a flowchart showing a specific control procedure of the card reader control device when receiving a “security request” command.

FIG. 297 is a flowchart showing a specific control procedure of the card reader control device at the time of receiving a “punch hole” command.

FIG. 298 is a flowchart showing a specific control procedure of the card reader control device at the time of receiving a “card rear ejection” command.

FIG. 299 is a flowchart showing a specific control procedure of the card reader control device at the time of receiving a “card forward ejection” command.

300 is a flowchart showing a specific procedure of a card reading process in the flow of FIG. 291.

301 shows parity and L in the flow of FIG. 291.
It is a flowchart which shows the specific procedure of RC inspection processing.

302 is a flowchart showing a specific procedure of magnetic processing in the flow of FIG. 292.

303 is a flowchart showing a specific procedure of a writing process in the flow of FIG. 293.

304 is a flowchart showing a specific procedure of a verify process in the flow of FIG. 293.

305 is a flowchart showing steps 1 in the flow of FIGS. 302 and 304. FIG.
It is a flowchart which shows the procedure of a bit reading process.

FIG. 306 is a flowchart showing a specific procedure of a punching process in the flow of FIG. 297;

FIG. 307 is a flowchart showing a specific procedure of a transmission process during the control flow of FIGS. 291 to 299 and the like.

308 is a flowchart showing a specific procedure of error processing when an error occurs in the control flows of FIGS. 291 to 299. FIG.

FIG. 309 is a flowchart illustrating a timer interrupt processing procedure for magnetic reading in the card reader controller.

FIG. 310 is a flowchart showing a timer interrupt processing procedure of magnetic reading in the card reader controller.

FIG. 311 is a flowchart illustrating a procedure of a write interrupt process during magnetic writing in the card reader control device.

FIG. 312 is a flowchart showing a control procedure of a main process in a unit controller of the card settlement machine.

FIG. 313 is a flowchart illustrating an example of a specific procedure of a packet reception process in the flow of FIG. 312.

314 is an "initial value setting" in the flow of FIG. 313;
It is a flowchart which shows the processing procedure at the time of packet reception.

FIG. 315 is a flowchart showing a processing procedure when receiving a “unit recovery data” packet in the flow of FIG. 313.

FIG. 316 is a “store opening code” in the flow of FIG. 313;
6 is a flowchart illustrating a processing procedure when a “forced termination release” packet is received.

FIG. 317 is a “closing code” in the flow of FIG. 313;
6 is a flowchart illustrating a processing procedure when a “forced end” packet is received.

FIG. 318 is a flowchart showing a specific procedure of each function receiving process in the control flow of FIG. 312.

FIG. 319 is a flowchart showing a specific procedure of a settlement process in the function receiving process of FIG. 318.

FIG. 320 is a flowchart showing the contents of an interrupt process executed by a timer interrupt separately from the main process in the unit controller of the checkout machine.

FIG. 321 is a flowchart showing a control procedure by the card settlement controller.

FIG. 322 is a flowchart showing a specific control procedure when a function is received in the flow of FIG. 321;

FIG. 323 is a flowchart showing a specific procedure at the time of receiving an “initial value setting” function in the flow of FIG. 322;

FIG. 324 is a flowchart showing a specific procedure at the time of receiving a “card accepted” function in the flow of FIG. 322;

FIG. 325 is a flowchart showing a specific procedure at the time of receiving a “card cannot be accepted” function in the flow of FIG. 322;

FIG. 326 is a flowchart showing a specific procedure at the time of receiving a “card ejection” function in the flow of FIG. 322;

FIG. 327 “Reload” in the flow of FIG. 322
It is a flowchart which shows the specific procedure at the time of function reception.

FIG. 328 is a flowchart showing a specific procedure at the time of receiving the “card confiscation” function in the flow of FIG. 322;

FIG. 329 is a flowchart showing a specific processing procedure at the time of receiving the “payment” function in the flow of FIG. 322;

FIG. 330 is a flowchart showing a specific procedure of received command processing in the flow of FIG. 321;

FIG. 331 is a flowchart showing a specific procedure of a magnetic data inspection process in the process flow of FIG. 330;

FIG. 332 is a flowchart showing a specific procedure of punch hole inspection processing in the processing flow of FIG. 330.

FIG. 333 is a flowchart showing a specific procedure of an adjustment hole punching process in the process flow of FIG. 330.

FIG. 334 is a flowchart showing a control procedure by the card issuance control device in the management device.

FIG. 335 “Resurrection of card” in the flow of FIG. 334
It is a flowchart which shows the specific control procedure at the time of receiving a function.

FIG. 336 is a flowchart showing a specific procedure of card ejection processing in the flow of FIG. 335.

FIG. 337 is a flowchart showing a specific procedure of a reader control process in the flow of FIG. 335.

FIG. 338 is a flowchart showing a specific procedure of card inversion processing in the flow of FIG. 335.

FIG. 339 is a flowchart showing a specific procedure of print processing in the flow of FIG. 335.

FIG. 340 is a flowchart showing a specific procedure of card ejection processing in the flow of FIG. 335.

FIG. 341 is a flowchart showing a specific procedure of error processing executed when an error occurs in each of the processing flows of FIGS. 336 to 340.

[Explanation of symbols]

 100 Pachinko machine 110 Operation panel 113 Purchase switch 114 Interruption switch 115 Exit switch 130 Ball circulation device 160 Control unit 180 Unit control device 188 Card reader control device 195 Pachinko machine control device 190 Unit controller 200 Card issuer 700 Card issuing device 710 Card removal Device 740 Card reversing device 750 Printing device 770 Card deriving device 300 Payment device 400 Management device 550 Unit memory 551 Data transmission controller 553 Network controller 800 Card reader 802 Card insertion / ejection port 807 Transport motor 809 Shutter solenoid 820 Punch device 821 Magnetic head

──────────────────────────────────────────────────続 き Continuation of the front page (51) Int.Cl. ⁶ Identification number Agency reference number FI Technical indication location G07F 9/00 107 G07F 7/08 H

Claims (1)

(57) [Claims] 1. A game facility in which a plurality of gaming devices and a management device capable of collecting operation data of these gaming devices are communicable by transmission means, wherein the management device comprises: Operating data collecting means capable of collecting operating data, first storing means for storing operating data collected by the operating data collecting means, and second storing means capable of storing operating data stored in the first storing means. Operating data transfer means for transferring the operation data stored in the first storage means to the second storage means and storing the operation data, wherein the operation data transfer means relates to a total management period of the business data. A game facility wherein the operation data stored in the first storage means is transferred to and stored in the second storage means.