JPH03242183A - Card type game system - Google Patents

Abstract

PURPOSE:To release a game machine being in an interrupted state simultaneous ly with the settlement of accounts by providing a state deciding means for a card on an account-settling machine, rejecting an account-settling processing as for the card being in the course of interruption, and account-settling only the card being in a free state. CONSTITUTION:A control system of an account-settling machine consists of a unit controller 350 for controlling paper money and coin discharge devices 321, 325, etc., and a card account-settlement controller 312, and when a card is inserted into a card account-settling device 310, a state of the card is read by a card reader 800, and when it is in a free state, the controller 312 executes an account-settling processing. On the other hand, in the case of the card by which a game machine is in an interrupted state, the account-settling processing is not executed, it is informed to a managing device through the unit controller 350 and a low layer network 510, and when the managing device releases the game machine being in the course of interruption, the card account-settling controller executes the account-settling processing by its release, and the dis charge devices 321, 325 are driven through the unit controller 350. In such a way, labor saving in a game store can be contrived.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a gaming system using gaming machines such as pachinko machines, arranged balls, and slot machines, and in particular, to a gaming system that allows playing with cards exchanged for money. The present invention relates to techniques that are effective for use in gaming systems that have been developed.

[Prior Art] In recent years, a card-type pachinko game system has been proposed in which the game is played using a card-shaped storage medium as an intermediary. The card system has the advantage that the player only needs to carry the card, which is a storage medium, and can reduce the effort of carrying a large number of pachinko balls that are prone to falling.

Card-based pachinko gaming systems that have been proposed in the past can be roughly divided into the following two systems.

In the first method, when a card is issued, data on the number of balls held corresponding to the purchase amount is stored on the card, pachinko is played within the range of this data on the number of balls held, and data on the number of balls held that increases or decreases during the playing process is stored on the card. (See Japanese Patent Publication No. 47-42227).

The second card method is to issue a card with only a code number recorded at the time of card purchase, store the number of balls held in a central management device, and insert the card into the card reader of the pachinko machine. This allows you to play a game by calling up the stored number of balls you have (Jikko Kouko 61-32
No. 709, see Special Publication No. 51-17106).

[Problems to be Solved by the Invention] In the second card-based system, all pachinko machines and card issuing machines are centrally managed under the control of a management device, making it possible to play games using code numbers. becomes.

However, in card-based gaming systems, games cannot be played without the presence of cards.
If you leave the game machine with your card, there is a risk that your card will be stolen, and if you leave the game machine with your card, there is a risk that another player will take away your right to play at that machine. . Therefore, in a card-based gaming system, it is desirable to provide each gaming machine with an interrupt switch so that the player can leave the gaming machine with the card while retaining the right to play at that gaming machine.

However, if you do this, even if a player loses the intention to play at a gaming machine while he is away from the gaming machine (during an interruption), he will still have the card at hand and will not be able to play the game during the interruption. There is an inconvenience that the card cannot be settled unless the user returns to the gaming machine and cancels the interruption.

This is because if the suspended card payment is immediately allowed, the suspended game machine will remain as it is, making it impossible for other players to play games. In this case, it is conceivable that the staff at the game parlor take the paid card and go to release the suspended game machine, but this would require manpower and would not be labor-saving, and the paid card would be returned to the player. In this case, it is extremely inconvenient that the suspended game machine cannot be released unless the power of the game machine is turned off and then turned on again, or a command is given from the console of the management device.

This invention was made against the above-mentioned background, and its purpose is to enable players to leave the gaming machine while retaining the right to play on the gaming machine while playing, and also to enable users to leave the gaming machine during play while retaining their gaming rights. In a card-type gaming system, the management device is configured to notify the management device of the card settlement, and the management device issues an instruction to cancel the suspension to the corresponding gaming machine,
To enable a suspended card to be settled at a settlement machine without causing any inconvenience, and to save labor for a game parlor.

[Means for Solving the Problem] In order to achieve the above object, the present invention provides a gaming machine in which a game can be played only with a card on which an identification code is recorded, an issuing device for issuing the above-mentioned card, and 2. A storage medium settlement device for settling data and their management device are connected through a transmission means, and the management device transmits valuable data substantially equivalent to the amount of money or the number of balls for each identification code given to the card. In the card-type gaming system, the card-type gaming system is configured to allow games to be played within the range of valuable data obtained from the management device based on the identification code read from the card in the gaming machine. is configured to execute payment processing for cards in a free state and suspended, and when payment processing for a suspended cart is executed, it is notified to the management device, and the management device issues a suspension release command to the corresponding gaming machine. It was configured to give

[Function] According to the above-described means, the game machine can be automatically released at the same time as payment, without the need for the player or the staff at the game parlor to return to the suspended game machine and cancel the suspended state. This makes it possible to save labor at the game parlor.

[Embodiment] FIG. 1 shows an embodiment of a pachinko gaming system to which the present invention is applied.

The pachinko gaming system of this embodiment includes a pachinko machine 100 as a gaming machine, and an issuing machine as a storage medium issuing device that issues a card CD as a storage medium having local value in order to start a game in each pachinko machine. 200, a settlement machine 300 as a storage medium settlement device for settling the prize balls obtained as a result of the game and the purchase money remaining without being used for the game, and the various terminals mentioned above are centrally managed and controlled. Management bag @400 and this management device E4
A data transmission line 500 that organically connects 00 and each terminal device.
These constitute an organic bond. This organic combination can only intervene with the card CD, and only the organic combination can operate the card and convert its valuable data.

Therefore, the pachinko machine 1 which is each component of the organic combination
00, issuing machine 200, payment machine 300, and management device 40
0, respectively, a card reader (in this specification).

A device that writes on the magnetic surface of the card is also called a card reader), and information on the card and information on each terminal device is stored in the storage device of the management device 400 in the form of a file. It has become.

Next, before going into a detailed explanation of each component of the above-mentioned organic combination, a card used in the system of this embodiment will be explained.

The card CD used in the system of this embodiment contains information necessary for the player, such as the purchase amount AM and the date of issue (=validity date) DATE, as shown in FIG. 2 (A), for example. Issuance serial number n required when restoring a damaged card
A print display section PRT on which the following information is printed at the time of issuance is provided along the card insertion direction (longitudinal direction of the card). Therefore, there is no need to prepare in advance multiple types of cards with different amounts printed on them.

Immediately above this print display part PRT, there is a punch as a perforation forming part that records the history or state transition of the card, such as issued, revived, played, returned to zero, and settled, in the form of a perforation. A hole forming area PH is also provided along the card insertion direction.

By detecting the perforations formed on the card with a photoelectric detector, you can easily check the card's status without having to read and check the number of balls data from the management device's file using the code recorded on the magnetic surface. As a result, the burden on the card reader controller and management device required to determine the processing corresponding to the card status can be reduced.

On the other hand, at a position slightly below the center of the card, there is a magnetic recording section MG coated with a band-shaped magnetic material from the front edge to the vicinity of the center.
is provided (see FIG. 2(B)). However, the magnetic recording part MG may be formed not only in a part of the longitudinal direction of the card, but also in the form of a continuous band from one end of the card to the other, similar to the print display part PRT, or by applying a magnetic material to the entire back surface of the card. It may also be used as a magnetic recording section.

Furthermore, in the card of this embodiment, between the print display section PRT and the magnetic recording section MG, that is, at the center of the card, there is a belt-shaped roller running area RRA that is slightly wider than the conveyance roller in the card reader in the longitudinal direction of the card. The surface of the card, especially the magnetic recording section MG, print display section PRT, and authenticity discrimination area TF, which contain important information used for card judgment, are damaged by contact with the conveyance roller. This prevents the information from becoming unreadable.

Further, in the card of this embodiment, an authenticity discrimination area TF consisting of a security mark hidden in characters such as hole names printed on the surface of the card is provided below the magnetic recording section MG. That is, the rPL printed on the front of the card
The letters AZAJ.

As shown in FIG. 2(C), the legs of each character are designed and printed in a position corresponding to the detection bit patterns B, .about.B, provided at a pitch of 3°51, etc.

The width of one character is 0.5 to 1°5, and the distance between each bit is 3.
There are five cabinets, and each bit's "1" or "0" is expressed by the shade of the character. Of the 10 bits, the fifth bit B from the left and the last bit B are bit B.

The shading of the characters is determined to represent the parity of ~B and B5~B. Note that the security bits hidden in this character string can only be detected by a sensor and are indistinguishable to the human eye. It is more preferable to use a special ink that does not stick.

Further, on the surface of the game card of this embodiment, a head cleaning area HCN is provided in which a cleaning agent for removing dirt from the magnetic head is applied to a band-shaped area continuous with the magnetic recording part MG. At the same time, in the card of the embodiment, in order to make it impossible to tell where the magnetic recording part MG is provided, a base material 1 made of plastic such as polyester is used, as shown in FIG.
A white layer 13 is formed on the magnetic N12 made by uniformly coating magnetic particles on the magnetic layer 1, and a pattern printing layer 4 is placed on the -L, and then a part of it (corresponding to the print display section PRT) A heat-sensitive coloring layer 15 is formed on the area), and a transparent protective film 16 is coated above the thermosensitive coloring layer 15. Note that a cleaning agent of the same color as the white layer 13 is applied to the cleaning area HCN.

The protective film 16 is not coated on the surface so as to be exposed, so that the cleaning area is hardly different in color from other areas, thereby improving the aesthetic appearance. Further, a pattern printing layer 17 is provided on the back side of the base material 11 of the card.
is formed, and a protective film 18 is coated thereon.

In a card having the above structure in which the white layer 13 is formed on the surface of the magnetic layer 12, the magnetic layer 12 made of black magnetic particles is covered with the white layer 13, so that the image cannot be displayed. In addition to making it possible to print and provide fashionable cards, the magnetic recording section MG
It also has the function of concealing.

Furthermore, since the surface of the card is coated with a protective film 16, areas that hold important information used for card identification, such as the print display section PRT, magnetic recording section MG, and authenticity discrimination area TF, are protected. This information becomes less likely to be destroyed, improving the reliability of the card.

FIG. 2(E) shows the magnetic recording section MG provided on the card.
An example of the configuration is shown below.

The magnetic recording section MG of the card of this embodiment is composed of two tracks, of which clock data giving sampling timing is recorded in the first track TRC1. The second track TRC2 includes, from the left, a field STX containing a 4-bit start code and its parity pit.
, Company code MKC indicating the manufacturer of the card reader, Equipment code MCC indicating the model of the card reader1 Identification code of the game store DSC5Year month date data DATE, card number No.
, a text field TXT containing the issuance command code FNC given by the card reader at the time of card issuance and the security data SDC read from the authenticity discrimination area.
, a field ETX that contains a text end code, a field LRC that contains an exclusive OR value (detection code) of the text data and the end code, and a field ST that contains a start code.
It is composed of X. Moreover, the date data DAT
E has a bit P indicating each parity every 4 bits, and the first 4 bits are 1.
The 6th to 9th bits and the 11th bit represent the day, and the 12th to 14th bits and the 16th to 19th bit represent the last two digits of the year in binary code. It has become.

For cards with a magnetic recording section, it is generally easiest to decipher the recording format and recorded data from the date, but in the card of the above example, the order of the year, month, and day is changed, and the parity is set every 4 bits. The presence of pits and the variable correspondence between recording bits make it extremely difficult to counterfeit cards. In addition, since the issuing serial number n is printed on the print display section PRT, even if the information in the magnetic recording section MG becomes unreadable due to damage to the card, it is possible to restore the card from the file information on the management device. can.

Furthermore, as described above, the information recorded in the magnetic recording section of the card of this embodiment includes the identification code DSC for specifying the usable space of the card, and the date of issue for indicating the validity period of the card. Only the DATE, the card number as an identification code obtained from the issuing serial number n using an appropriate function or conversion method, and a check code for error detection are recorded, and the purchase amount and number of balls held are not recorded. . These are configured so that they can be drawn out in real time from the data file of the management device 400 according to the card number No. This makes it possible to prevent fraud due to card copying and to minimize damage caused by fraud. In other words, even if the card is copied, the damage will not be greater than the purchase amount and the number of acquired balls registered in the data file, so copying the card is a completely wasteful act.

Furthermore, in the embodiment described above, the authenticity of the card is determined not only by the magnetic recording information recorded on the card but also by the authenticity discrimination area TF, which is difficult to forge, so that card fraud can be more reliably prevented. I can do it. In addition, since a fraudulent card can be detected immediately by checking the authenticity discrimination area TF, a fraudulent card can be discovered more quickly than by sending magnetic information to the management device 400 to determine whether the card is fraudulent. Note that perforations are now also formed in telephone cards and the like that have magnetic recording parts, but the perforations in conventional cards are provided to inform the user of the unused balance; It is not intended to be used for any kind of processing or judgment.

Next, an example of the configuration of a gaming machine that provides the original game will be explained using FIGS. 3 to 3.

The gaming machine of this embodiment is arranged in island equipment above the gaming machine main body in one-to-one correspondence with the pachinko machine 100, and is mainly used to control the display and card reader, and to control the operation data during the game. It is composed of a control unit ↓60 that controls collection.

The pachinko machine 100 is mounted in a machine frame 101 fixed to island equipment of a pachinko parlor so that it can be opened and closed by a hinge 102. A reinforcing plate 107 having an operation dial reinforcing member 107a that withstands the weight of the pachinko machine 100 and absorbs vibrations of the ball launcher 103 is fixed to the lower part of the machine frame 101. At the bottom of the pachinko machine 100, there is provided a ball launcher 103 that launches enclosed balls one by one into the game area, and its operation dial 104. Amount display 111, number of balls display 112, purchase switch 113, interruption switch 114, for enabling the start procedure.
An operation panel 110 is provided that includes an end switch 115, a game status display 116, and the like. The configuration of the playing area on the front of the pachinko machine is the same as the conventional one. The purchase switch 113 is an instruction switch for converting the amount of money into game balls in units of 200 yen or the like within the amount of money the card has, assuming that the card is inserted into the card reader 800 built into the control unit 160. , the converted game balls become the number of balls you have. The remaining amount of the card is displayed on the amount display 111 in units of 100 yen, and the converted number of balls is displayed on the number of balls display 112, and the ball launcher 103 displays the number of game balls. Each time a ball is fired, the number of balls held is subtracted by one, and when a winning ball occurs, the number of prize balls is added and displayed. By turning on the end switch 115 whenever the player wants to end the game (including when changing the game machine), the card being used can be ejected from the control unit 160.

At that time, the unit controller 190 registers the player's remaining balance and number of balls (sum of purchased balls and acquired balls) in the file of the management device 400, and then inserts the card into the slot 802a of the card reader 800. Emit more.

Furthermore, the interrupt switch 114 is a switch that is used by the player to temporarily interrupt the game for a break, even though the player does not intend to stop playing on the gaming machine that is currently being played. , the unit controller 190 once ejects the card and enters a standby state until the same card is inserted again, and no longer accepts cards at that distance. In addition, among the above switches, purchased switch 11
3 is a built-in lamp type, and when the number of balls held reaches "O", the lamp in the purchase switch 113 flashes.

The operation panel 110 is connected to the pachinko machine 1 as shown in FIG.
It is attached to the front panel 105 that can be opened and closed at the bottom of 00,
The operation panel 110 has a hollow shape with a triangular cross section, and its top surface is sloped downward toward the front to make the display easy to read.
Wiring boards 120A and 120B are arranged in parallel with the board 120A, and the amount display 111 and ball number display 112 made of 7-segment LEDs are mounted on the board 12OA, and the above-mentioned switches 113 to 115 and built-in lamps are mounted on the board 120B. is attached and covered with a display plate 117. A portion of the display plate 117 corresponding to the display devices 111 and 112 is a transparent window portion 117a, and the switches 113 to 1
The portion corresponding to 15 is an opening 17b (see FIG. 5). An operation button 118 is mounted within this opening 117b so as to cover the upper part of each of the switches 113 to 115. 121 is the purchase switch 113
It is a built-in lamp that is compatible with

Further, at the front end of the operation panel 110, there is provided a game status display section 116 in which a display lamp 123 is covered with a translucent Fresnel lens 119 or the like.
3 is turned on when the operation dial 104 of the ball launcher M103 is turned.

Furthermore, an operation button 12 with a built-in stop switch 124 is provided on the side of the operation panel 110 (on the left side in the embodiment).
5 is attached, and when this switch 124 is turned on, it is possible to give commands related to the game, such as stopping the operation of accessories arranged in the game section. The stop switch 124 is mounted on a wiring board 12OC disposed in the operation panel 110, and includes a wiring group 126C extending from the wiring board 120C and a wiring group 1 extending from each of the boards 12OA and 120B.
26A and 126B are pulled out to the outside, and can be connected to a pachinko machine control device M195 disposed at the bottom of the back of the pachinko machine by connectors 127A-↓27C connected to their ends.

On the other hand, the pachinko machine 100 constituting the game machine of this embodiment is configured as a closed-type game machine that circulates game balls sealed inside the machine, and has an enclosed ball circulation device 130 on the back side that circulates the enclosed balls. have.

An example of the configuration of the back side of the pachinko machine 100 is shown in FIG.

A game board in which a winning ball collection gutter 131 covering a plurality of winning ball outlet holes formed to penetrate the game board corresponding to a winning area provided in a playing area on the front side of the game board is held on a frame 106. is attached to the back of the The bottom wall of the winning ball collection gutter 131 is sloped downward toward the center to form a guide column 131a, and below that, as shown in FIG. 7, out pitch types 132a, a first safe ball gutter 132b, and a second safe ball gutter 132c A guide gutter 132 is provided which is integrally formed with the guide gutter 132 and the guide gutter 132. In the middle of each machine in this guide gutter 132, a photoelectric out sensor 5NS consisting of a pair of light emitters and a light receiver is installed.
I, first safe sensor 5NS2, second safe sensor 5N
S3 is installed. In addition, the guide @ 182 is equipped with a confluence seeding section 132d that collects the balls that have flowed into each machine in one place, and the end of the confluence seeding section 132d is gently shaped to align the pachinko balls in a line, as shown in FIG. It is connected to the upstream side of the inclined guide trough ↓33, thereby creating an enclosed ball circulation device! 130 are configured. And guide 11
On the upstream side of 33, there is a foul ball receiving port 134 (see Fig. 9) provided at the upper end of the firing rail to collect so-called foul balls that are hit balls that are hit along the firing rail and return toward the rail board. A foul ball type 133a is integrally formed so as to face the ball, and the foul ball is merged with the ball that has flown down onto the guide gutter 133 via the guide gutter 132. Foul ball @i
A foul sensor 5NS4 is disposed in the middle of l33a.

Then, a ball is placed opposite the lower end of the guide gutter 133.
A ball feeder 135 is swingably attached to the ball feeder 135, which separates the balls on the guide gutter 133 one by one and causes them to flow downward.

A stopper 136 is fixedly installed behind the ball feeder 135 to prevent the single ball feeder 135 from rotating more than necessary, so that when the ball feeder 135 rotates downward due to the weight of the incoming balls, its upper end surface becomes a guide channel. It is possible to prevent the ball above 133 from falling. Furthermore, a rotatable ball leveler 137 is attached to the middle of the guide trough 133, and a sliding ball removing mechanism 138 is provided downstream.

As shown in FIG. 8, this ball extraction mechanism 138 prevents the ball from sliding in the lateral direction by a blocking piece 148 protruding from the back surface of the frame board 109 when the enclosed ball circulation device 130 is attached to the back surface of the frame board 109. This prevents him from removing the ball. Thus, the enclosed ball circulating device 130 is attached so that it can rotate as a whole at a hinge portion 139 provided on one side (the right side in FIG. 8), and rotates rearward around the hinge portion 139. When the ball is moved, the single ball extracting mechanism 138 is slid and the ball can be extracted.

In addition, an elastic locking piece 133a is fixed to the end of the guide gutter 133, and by engaging the elastic locking piece 133a with the engagement step 149 of the frame board 109, the enclosed ball circulation device 1130
can be fixed so that it cannot be rotated.

The pachinko balls separated by the ball feed ↓ 35 pass through the ball passing hole 139 (see FIG. 9) formed in the frame board 109 disposed behind the front panel 105, and are diagonally projected onto the front surface of the frame board. Fixed launch rail 140
One piece is flowed down to the base of. And this launch rail 1
A firing rod 103a is arranged so as to face the base of 40 (
(See Figure 10). At the same time, below the base of the firing rail 140 is a push-up piece 141 which is rotated in conjunction with the firing rod 103a and pushes up the ball feeder 135.
An interlocking member 141 having a shape is provided.

Further, a concave groove is formed on the upper surface of the launch rail 140 to guide the ball, and the frame board 140 is provided with a concave groove for guiding the ball.
On the front of bracket 9 is a launch sensor 5NS5 consisting of a launch type photoelectric switch that detects a ball passing on the rail.
42, the firing sensor 5NS5 is attached to the upper surface of the rail with a distance of at least one ball length, and at the upper end of the bracket 142 there is a return ball prevention wall 143 that prevents the return ball from jumping over the sensor. is provided. Furthermore, the return ball is guided to the frame board 109 at the rear of the frame board in correspondence with the upper end of the launch rail 140.
A foul ball receiving port 134 is formed to guide the foul ball into the foul ball receiving port 132, and a line receiver is formed along the lower side of this foul ball receiving port 134.
4 is provided protrudingly.

A game board mounting portion 109a is provided at the upper end of the frame board 109, and game board positioning protrusions 145 are erected at both ends. Further, a frame engaging portion 146 having a groove in which the frame 106 for holding the game board can be engaged is formed along the upper end of the frame board 109, and as shown in FIG. By lowering the frame 106 from above along the positioning protrusion 145 and engaging the lower end with the groove of the frame engaging portion 146, the two can be coupled. Four locking tools 106a are provided on the side wall of the frame 106 to removably engage the game board, and the game board held by the frame 106 is placed on the mounting portion 109a of the frame board 109. In this state, the fastener 147 is tightened and fixed. A speaker 150 is attached to the front side (left side in FIG. 9) of the frame board 109 to generate sound effects related to the game.

On the other hand, the front panel 1 that covers the front of the frame board 109
As shown in FIG. 10, 05 is attached to the lower part of the opening bordered by the holding frame 108c inside the front frame lO8 so that it can be opened and closed using one end (left end) as a fulcrum, and on the back side there is a firing rail 14.
0 and is located above the launch rail frame 15.
1 is fixed thereto, and a cutout 151a is provided in the middle of this firing rail frame 151 so that the firing sensor 5NS5 can face inside the frame. Further, a lock lever 152 is provided on the back surface of the end of the front panel 105 opposite to the hinge. A glass frame 154 is attached above the front panel 105 within the front frame 108 so as to be openable and closable. On the other hand, on one side of the back side of the front frame 108 opposite to the hinge part 102, as shown in FIG. It is installed. Further, 155 is a lever for opening the glass frame 154.

A frame 106 holding a game board (see FIG. 11) and a frame board 109 are attached to the back side of this front frame 108, and a fitting protrusion 106b on the back side of the frame and a fitting protrusion 106b on the back side of the frame board are attached to the fitting receiving part 108b on the back side of the front frame. The front frame 108, the frame 106 holding the game board, and the frame board 109 are integrated by joining them so that the mating protrusions ↓09b are aligned and screwing them together.

FIG. 13 shows a state in which the frame 106 and frame board 109 are attached to the back side of the front frame 108 in this way, and the winning ball collecting gutter 131 is further attached to the back side of the game board held by the frame 106. Further, a pachinko machine control device 195 is arranged below the frame board 109.

Further, a game control device f158 and a relay board 159 are attached to the back surfaces of the frame 106 and the winning ball gathering gutter 131.

An embodiment of a control unit 160 configured separately from the pachinko machine 100 is shown in FIGS. 14 to 16.

The control unit 160 of this embodiment includes a status indicator 162 that shows the status of the pachinko machine on the front side of a storage frame 161, and an analog indicator 16 that includes a plurality of lamps arranged in a line.
3. It has a safe ball lamp 164 for displaying the occurrence of winning balls, a call button 165 for calling an attendant, etc. The analog display 163 is used to display the number of balls held during the game in an analog manner, and to display the stopped state and free state by simultaneous flashing and moving flashing.

In addition, a speaker 166 and a card reader 800 are built into the storage frame 161, and a card reader 80 is installed in the front of the storage frame.
0 card insertion/ejection opening 802a is exposed, and above this insertion/ejection opening 802a is a card holding indicator lamp 167 (LEDI) that indicates whether or not there is a card in the card reader. Control unit 160 below
A card insertion indicator lamp 168 is arranged to indicate whether or not a card can be inserted.

Furthermore, inside the front panel 161a of the storage frame 161 of the control unit 160, the pachinko machine 100 is stored in a management device 4.
A test switch 17 for enabling a gaming operation using a test card to be described later in a unique state separated from 00.
9 is arranged, and on the front side of the storage frame there is a pin insertion hole 169 for enabling the switch to be turned on from the outside using a pin, and a name plate 170 that clearly indicates the machine number assigned to the pachinko machine. are provided for each.

On the inside of the front panel 161a of the control unit 160, as shown in FIG. lamp 164
Built-in lamp group L11 to L15. L21-L28. L3
1. Lamp board 172 with L32 (see FIG. 16)
and the speaker 166 and card insertion lamp 168.
A holding board 173 is attached. Further, a call switch 165a is provided behind the call button 165.

Furthermore, inside the storage frame 161, there is a card reader 8oO,
A unit controller 190 that controls the entire control unit 160, transmission means, monitor display devices 174, 175,
176, a card reader control device 188, and a power supply device 177 are built in.6 Also, below the card reader 800, there is a unit control device 180 having a card reader control device 188, and a power supply device 177. A storage box 178 for perforated pieces is removably arranged. A card ejection switch (not shown) is provided on the board constituting the card reader control device 188 to instruct the card reader to forcefully eject the card.

The control unit 160 is provided with a locking tool 179a and a release lever 179b on the free end side of the front panel 161a.
It faces an opening 161b formed at the lower end of. As shown in FIG. 17, the control unit 160 is placed on the machine frame 101 of the pachinko machine 100 and the unit installation stand 24 at the same height as the machine frame 101, and at this time, the front panel 161a 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 by the upper surface of the front frame 108.
By opening the front frame 108, the opening 161b is exposed and the release lever 179b can be operated.

This eliminates the need to provide the control unit 160 with a locking device.

Note that the unit control device 180 in the control unit 160
is connected to the control device 195 of the pachinko machine 100 via a transmission line such as an optical fiber or a coaxial cable, and to the management device 400 via a transmission controller and a local network (transmission cable), which will be described later.

The control unit 160 of the embodiment is provided with an optical fiber connector 186 and a coaxial cable connector 187 on the back side of the storage frame 161 so that data can be transmitted using any transmission path (see FIG. 20). reference).

18 to 20 show an example of an island facility on which a gaming machine consisting of the pachinko machine 1.degree.

In the island equipment of this embodiment, a plurality of supports 22 are erected on a base 21 at intervals equal to the width of the gaming machine, and 6
A horizontal mounting table 23 is fixed by a support 22 at a height of about 0 (! A first installation machine 24 is fixed to the top, and a second design machine 25 is fixed above it by a support 22, and a ceiling is installed above the second installation column 25 so as to cover the upper end of the support 22. Board 2
6 is fixed. The front end of the mounting base 23 is configured to protrude slightly in front of the support column 22, and the front end of the first installation base 24 is positioned behind the support column 22 by the thickness of the machine frame 101. There is.

Each pachinko machine 100 is placed together with a machine frame 101 on the mounting table 23 between the pillars 22, and the control unit 160 is placed from the first installation table 24 onto the machine frame 101 which is on the same plane as the first installation table 24. . In addition, the second installation stand 2
A transmission path (shown in FIG. 11i) constituting the local network is extended on the top of the support 5, and a transceiver 185 for transmitting data to and from the management device 1400 is provided between each support 22 via the transmission path. Note that the front of the transceiver 185 is closed by the upper plate 27, and the mounting table 22 is closed.
The lower part thereof is closed by a lower plate 28.

Further, although not shown, a 24V power line extends to the lower surface of the mounting table 22, and a 100V power line extends to the lower surface of the top plate 26. A 24V power outlet 30 is provided at a position corresponding to each gaming machine on the top surface of the mounting table 23, and a 100V power outlet 31 is provided on a crosspiece 29 on the bottom surface of the top plate 26, corresponding to each gaming machine. (See Fig. 20).

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

In the same figure, 188 is a card reader control device that controls each component of the card reader 800 shown in FIG. 26, such as the transport motor 807, the magnetic head 821, and the punching device 820. Various switches 171, 179, displays 162, 163, 164, 168, and speakers 166 are provided in the card reader control device 188, the pachinko machine control device 1195, and the control unit 160.
is controlled by a unit control device 180.

Further, although not particularly limited, in this embodiment, a control device 195 of the pachinko machine 100 is connected to the unit control device 180 via an optical cable 191, and detection signals from various sensors are input, and a display device etc. A drive control signal is output. To enable communication using optical fiber cables, an optical multiplex data link (interface ) are provided between the unit control device 180 and the optical fiber cable 191 and at the connection portion between the optical fiber cable 191 and the pachinko machine control device 195 (described later).

By using the optical fiber cable ↓91 for data communication between the unit control device 180 and the pachinko machine control device 195, the large number of wires that were conventionally arranged in a complicated manner on the back side of the pachinko machine can be cleaned up and maintained. , it is possible to facilitate management and prevent malfunctions due to noise.

Under the control of the pachinko machine control device f195, the amount display 111-, the number of balls display 112, the purchase lamp 121, the game status display lamp 123, and the ball firing bag! ! 103 control device 1194 and accessory control device 158 are placed, as well as a purchase switch 113, an interruption switch 114,
Ball detection sensor 5 such as end switch 115 and out sensor
The signal from NSI~5NS5 is sent to the pachinko machine control device 19.
5, the signal is waveform-shaped and supplied to the unit control device 1180. In this embodiment, there are two power supply systems, AC24V and AClooV (7), and AC24V is supplied to the pachinko machine 100 side, and AClooV is supplied to the control unit 160 side. Separating the power supply in this way prevents the pachinko machine control unit from being accidentally destroyed due to the influence of the power supply in pachinko parlors where there are many problems with the power supply system.

FIG. 22 shows an example of the configuration of the pachinko machine control device 1195.

The pachinko machine control device 1195 includes a pachinko machine controller CPUI consisting of a microcomputer, and a reset circuit R5T1 that monitors periodic watchdog pulses output from the controller CPUI and generates a reset signal when the pulses are interrupted. Multiplex transmission controller CNT1 equipped with parallel-to-serial conversion means for converting parallel transmission data into serial data and direct image conversion means for converting serial reception data into parallel data in order to enable optical data transmission with unit control device 180
, a photoelectric conversion circuit OET connected to the optical cable 191 via the optical connector 193, a filter circuit FLT that cuts noise in detection signals from various sensors, and display data to the amount display 111 and ball number display 112. Decoders DECI and DEC2 that perform decoding and drivers DRVI and DRV that form frame motion signals for the display based on their outputs.
2, the purchase lamp 121 and the game status display lamp 123,
Driver DR that forms a linear motion signal of the batted ball launcher 103
V3.

Regarding the processing of the detection signal from the sensor in this pachinko machine control device 195, the noise is simply removed from the detection signal, the signal is shaped into a constant pulse width, and then sent to the unit control device 1180 as detection data for shooting balls, safe balls, etc. .

In other words, calculations such as the number of safe balls are not performed on the pachinko machine control device 195 side, and such calculations are performed by the unit control device 1.
This is done on the 180 side.3 In addition, pachinko machines tend to generate noise due to static electricity, etc., but the reset circuit R that monitors the watchdog pulse is
Since there are 8 Tl, the pachinko machine controller CPU 1. Even if the CPU goes out of control, if the regular watchdog pulse disappears due to the runaway, a reset signal is generated and the CPU is initialized, so the runaway can be prevented.

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

FIG. 23 shows an example of the configuration of the unit control device 180.

The unit control device 180 controls data transmission between the management device 400 and a unit controller 190 that centrally controls the card reader control device 188 and the pachinko machine control device 1195 to enable pachinko games using cards. a transmission controller 551;
It is comprised of a network controller 553, etc., which establishes receivables in the network and converts data into serial/parallel data under the control of the data transmission controller.

Data is exchanged between the controllers 190 and 551 and between the controllers 551 and 553 through dual port memories (RAMs) 550 and 552. Of these, 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 and reception data the same length (packetization), and a function for increasing the speed of data transmission (packetization). 2,
5Mbps).

This packet memory 552 is composed of four pages each having a capacity of 256 bytes, of which page O is used for transmitting a transmission request packet, and page 1 is used for transmitting a scheduled data transmission packet. On the other hand, pages 2 and 3 are used alternately for receiving data packets. The data transmission controller 551 instructs the network controller 553 as to which page to use. Even if the data transmission controller 551 is processing received packet data, even if the next packet data is sent, it will be received by another page, so all packets can be reliably received.

A common reset circuit 555 is provided so that each controller 551, 553 can be initialized simultaneously.

The connection side of the network controller 553 to the management device 400 is connected to an optical connector via a signal conversion circuit 554 and a changeover switch 542, which performs waveform shaping of received data and converts signal levels to increase the drive capability of transmitted data. 86, and a selector switch 542 is also provided so that it can be connected to a coaxial cable when the transmission line of the low-layer network is configured with a coaxial cable.
can be connected to a branch circuit 540 for separating and combining the transmitted signal and the received signal.

The optical connector 186 includes the optical transceiver 1 shown in FIG.
85 is connected.

Further, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store a data reception result in response to a request from the data transmission controller 551, and a data transmission controller 551. A latch circuit 562 for storing commands such as a data transmission command to the network controller 553, a latch circuit 563 for storing a low-layer network address, and three LED lamps for indicating an abnormality in the communication control state within the unit IIJII device 180. A latch circuit 564 is provided for storing display data on the monitor display 556 consisting of the following. 557 is each latch circuit 561 to 5 mentioned above.
This is a decoder that decodes the address given to 64 and generates a selection signal.

On the other hand, between the unit controller 190 and the card reader control bag [188, there is a transceiver 571 that converts the level of transmitted and received data.
A multiplex transmission controller 572 and a photoelectric conversion device w573 that perform parallel-to-serial conversion of transmitted and received data are connected between the two.

Furthermore, the unit controller 190 includes, via a data bus 581, a latch circuit 574 that latches display data (segment data and common data) of the amount of money and number of balls display, a purchase lamp, a game status display lamp, and control for batted ball firing. A latch circuit 575 that latches the signal. an input/output controller 576 that places input signals from various switches provided in the pachinko machine 100 and the control unit 160 onto the data bus 581 at predetermined timings and latches output signals that display various lamps;
A latch circuit 577 that latches audio data generated from the speaker 166 in the control unit 160 is connected.

582 is an audio synthesis LSI, 583 is a low-pass filter that cuts high frequency components to improve sound quality, and 584 is an amplifier that adjusts the volume. Among these, the audio synthesis LSI 582 stores multiple audio data in its built-in EPROM. ,
Selection signal given from unit controller 190 (
Select audio data according to So-33) and send the start signal S.
The audio signal is output in synchronization with T, and the output is stopped by the reset signal R.

Note that 558 is a program ROM that stores a control program for the unit controller 190, and 559 is a program ROM that stores a control program for the transmission controller 551. 585 decodes the address signal output from the unit controller 190 and sends it to the program memory 558, unit memory 550, and latch circuit 57.
4,575.577 and a selection signal for the input/output controller 576.

As described above, the unit control device 180 includes the management device f4
00, Card reader control device [188, Pachinko machine control device 195] It has information exchange windows on three sides, and controls the pachinko game using cards under the control of the management device Wt400. It has software that periodically sends pachinko machine game information generated as game results to a management device. Furthermore, the unit control device of this embodiment! 180, attention is paid to the fact that among the display data output from the unit controller 190 to open the amount and number of balls display, a digit select signal (common signal) is output periodically at intervals of, for example, 2 ms. Then, this is inputted to the reset circuit 555 as a watchdog pulse. Reset circuit 55
In addition to the power-on reset, 5 is configured to monitor this watchdog pulse and generate a reset signal when the pulse disappears.

Therefore, even if the unit controller 190 goes out of control due to noise or the like, the common signal will not be output at normal intervals when the unit controller 190 goes out of control, so the reset circuit 555 will operate and initialize the unit controller 190 and the data transmission controller 551 to prevent the out of control. Becomes avoided.

Along with this, the unit controller 190 has an internal timer counter, and if an ACK (affirmative) or NAK (negative) as a response to the transmission requirements is not returned within a certain period of time (ex, 10 seconds), When a packet cannot be transmitted within a certain period of time (ex, 2 seconds) after reception, or when a disturbance in the internal memory (RAM) is detected, the common signal is forcibly fixed to a low or high level. It is now possible to perform a reset. Note that the above-mentioned internal memory disturbance can be solved by writing a specific code (A55A, etc.) to a predetermined address in the memory during initialization, and then
This can be easily detected by checking every millisecond using interrupt processing.

Furthermore, the unit controller 180 of the embodiment also controls the unit controller 190 even when the data transmission controller 553 cannot transmit data within a certain period of time (5°12 seconds).
The system is initialized to prevent abnormal data from being sent to the management device [400]. That is, in the embodiment, a watchdog counter area is provided in the unit memory 550, the data transmission controller 551 sets a predetermined code FF every time data is transmitted to the management device, and the unit controller 190 sets a predetermined code FF for 20 m s. This counter is counted down by "1" each time.

Therefore, if the data transmission controller continues to be unable to send data for 5.12 seconds or more, the watchdog counter in the unit memory 550 will become "O", so monitor this counter and if it reaches rOJ, For example, it is possible to determine that the data transmission controller 551 is down and reset it by itself.

Furthermore, in this embodiment, a special RAM is used as the unit memory 550 in which a predetermined terminal INT rises when data is written to a predetermined address (7FE). At startup, the data transmission controller 551 writes data to the above-mentioned predetermined location to start up the terminal NT, and inputs the terminal signal to the unit controller 190 to synchronize the use of the unit memory between the controllers. Note that the specific terminal INT falls when the unit controller 190 reads data at the predetermined address.

On the other hand, synchronization with the management device 400 at the time of system startup is performed by the data transmission controller 551, and the data transmission controller receives a line test command (dictation) sent from the management device 400, and transmits the reception response to the management device! 400.

By the way, as mentioned above, the pachinko machine control device 195 side does not perform calculations such as the number of safe balls, and such calculations are performed by the unit control device! 180, and the unit controller 190 receives detection signals related to game balls, such as a safe signal, and signals from the purchase switch 113.

Based on these signals, the unit controller 190 calculates operating data such as the number of balls put out, number of out balls, number of balls held, and sales amount, and generates operating information (playing status) and monitor information regarding the pachinko machine. and writes them to the transmission data area 5DA (see FIG. 24) of the unit memory 550 consisting of a dual port memory.

The operating data etc. written to the unit memory 550 are
The data is sent to the management device through data communication between the transmission controller 551 and the management device 400 . Further, data sent from the management device 400 is also temporarily written to the reception data area RDA in the unit memory 550, and the unit controller 190 reads the data to receive the data. In the unit memory 550,
Communication area CCA that contains commands and status information to notify the other controller that other transmitted data and received data are in memory, working areas UWA and DV/A for each controller, and area C8A for synchronization between controllers. is provided.

FIG. 24 shows the overall configuration of the unit memory, and Tables 1, 2, and 3 show examples of the configurations of the transmission data area SDA, reception data area RDA, and communication area CCA.

Table: E-pachinko machine unit memory monitor information 1 (circle side table) The monitor information 1 shown in Table 1 is the same as Table 4.
As shown in the figure below, a bit indicates that a test is being executed when the system starts up, a bit indicates that the initial value is set/not set, a bit indicates a hot code error, a bit indicates an abnormality in the local network (two bits, one for the low layer and one for the high layer). It is made up of bits and the like that indicate an abnormality in the gaming machine. Furthermore, the monitor information 2 has a bit indicating an abnormality of the card reader, as shown in Table 5.

Furthermore, as shown in Table 6, the operation information includes bits that indicate a discontinued state, bits that indicate that the game is being suspended, bits that indicate that the game is forcibly terminated by the management device or controller based on communication abnormality or fraud detection, and bits that indicate that the game is being terminated. This consists of a bit indicating that the machine is in a free state with no players present, and the like.

Table 6 From Figure 6 above, the actual state of the pachinko machine is: ■Free state is 0000000000000001■During play is 000000000000001
0 ■ When receiving a forced termination, 000000000000
0100■When interrupted, 000000000
0001000 ■ When a stop occurs, 000000
It can be seen that it is expressed as 0000010000.

25 to 30 show specific configuration examples of a pachinko machine card reader 800 provided in the control unit 160.

Box-shaped case body 801 that constitutes the card reader 800
A front cover 802 having a card holding display LEDI and a card insertion/ejection port 802a is attached to the front end of the case body 8.
On the side wall of 01 is a storage frame 161 for the control unit 160.
L-shaped brackets 803 for fixing inside are fixed at the four corners.

As shown in FIG. 26, a base plate 804 serving as a card conveyance path is disposed inside the case body 801, and support substrates 805, 806 are placed above the base plate 804 in parallel with a gap slightly wider than the thickness of the card. is ready to be installed.

The support substrate 805 is located on the side of the card insertion slot, and on it is a card insertion detection sensor 808 consisting of a motor 807 and a microswitch, a card insertion detection sensor 808 consisting of a shutter solenoid 809 and a microswitch, a shutter solenoid 8O9, and a security sensor. Reflective optical sensors 810a and 810b for code reading are attached.

In this embodiment, one of the sensors 810a and 810b (
Only one sensor (810a) is used, and the other sensor (810b) is provided as a backup so that the security code may be increased in the future.

A 20th-L shaft 811 is rotatably placed between the motor 807 and the shutter solenoid 809.
A conveyance roller 812 is provided at the center of the 0-Ra shaft 811, and one end of the 20-Ra shaft 811 is made to be able to protrude outward from the side wall 801a of the case body, and a pulley 813 is fixed to the protruding end. ing. In addition, a card position detection sensor 5NS is installed near the shutter solenoid 809.
A light transmitter 814 that emits detection light to the second position detection sensor 5NS2 is attached between the 20th light beam 811 and the motor 807.
15 is formed. Furthermore, a floodlight 816 is attached to the side of the motor 807 for irradiating detection light to the punch hole detection sensor 5NSp, and a rotary encoder 817 is fixed to one end of the rotating shaft 807a of the motor 807. The other end of the rotating shaft 807a projects outward from the side wall 801b of the case body 801, and a pulley 818 with a small diameter is fixed thereto.

On the other hand, a tenth-ra shaft 819 is rotatably disposed on the support substrate 806 disposed on the opposite side of the card insertion/ejection opening 802a, and a punch device 820 using a solenoid as a driving means and a magnetic head 821 can be installed. For mounting the magnetic head, a through hole 82 is formed in the support substrate 806 in accordance with the position so that the head surface can face downward when the magnetic head is inserted downward from above.
2 is formed. Further, a conveyance roller 823 is fixed to the center of the tenth-ra shaft 819, and both ends of the shaft can protrude outside from the side wall of the case, and pulleys 824 and 825 are respectively attached. A belt 826 is placed between the pulleys 818 and 825.
Also, a belt 827 is wound between the pulleys 824 and 813, and the rotating piece power of the motor 807 is transferred to the belt 827.
is transmitted to the 10th-ra shaft 819, and further transmitted to the belt 8
27 to the 20th-ra shaft 811.

Further, on the lower surface of the support substrate 806, floodlights 828 and 829 are attached that irradiate detection light to the third and fourth card position detection sensors 5NS3 and 5NS4.

A first interface board 830 is arranged above the support boards 805, 806 so as to cover them, and is fixed to the side walls 80↓a, 801b of the case. This interface board 830 receives various control signals from the card reader controller 188 provided in the control unit 160 and passes read signals from sensors and magnetic heads provided on the cart reader side to the card reader controller 188. Equipped with an interface circuit for Furthermore, on the lower surface of the interface board 830, a light projector 831 is located at a position corresponding to the transparent section 815, and a speed detection sensor 8 is located at a position corresponding to the encoder 817.
32 are provided respectively.

On the other hand, the base plate 804 disposed below the support substrates 805 and 806 has the conveyance rollers 812 and 8
Auxiliary rollers 836 and 83 are biased upward by torsion springs 834 and 835 at positions corresponding to 23.
7 are openings 841 and 84 formed in the base plate.
It is attached so that the face is slightly exposed than 2. Also,
The base plate 804 has an auxiliary roller 83 at a position corresponding to the magnetic head 821 attached so as to face downward from the through hole 822 provided in the support substrate 806 and also biased upward by a torsion spring 836.
8 is attached so as to protrude slightly above the opening 843. Along with this, the base plate 804
Through holes 844 are formed at positions corresponding to the projectors 814, 816, 828, 829, and 831, respectively. Further, a recess 845 (see FIG. 28) is formed along the width direction at the front end of the base plate 804.
A cylindrical shielding member 846 is placed there. The shielding member 846 closes the card insertion/ejection opening 802a to prevent dirt from entering, and also functions to prevent cards other than those having a certain level of rigidity due to its weight from being accepted.

A second interface board 848 is attached to the bottom surface of the base plate 804 with screws, and a circuit for interfacing with the card reader controller 188 is mounted on the second interface board 848.

First to fourth position detection sensors 5NSl, 5NS are arranged to face the projectors 816, 828, 829 and 831.
2, 5NS3, 5NS4 and punch hole detection sensor 5N
Sp is attached.

Furthermore, relief sixes 849 are provided at positions corresponding to the auxiliary rollers 836, 837, and 838 to prevent contact with the rollers.

Corresponding to the cylindrical shielding member 846 placed on the front end of the base plate 804, a cavity 851, which is slightly larger than the shielding member 846, is formed at the front end of the upper support substrate 805. Support board 8
05, the shielding member 846 is housed in the cavity 851 so as to be vertically movable. Furthermore, an opening 853 is provided on the rear wall of the frame 852 constituting the empty space 851.
is formed, behind which the insertion detection switch 808 is arranged, and its movable contact 808a protrudes into the cavity 851 from the opening 853. The tip of this movable contact 808a is normally positioned above the shielding member 846 as shown in FIG.
When the card CD is inserted from point a, the card CD pushes up the shielding member 846 as shown in FIG.
is now turned on.

The shutter solenoid 809 mounted on the support substrate 805 is arranged facing downward as shown in FIG.
When the solenoid is in the demagnetized state, the card passes through the insertion hole 854 provided in the support substrate 805 and engages with the recessed hole 855 formed at the corresponding position on the upper surface of the base plate 804 as shown in FIG. 29(B). It is designed to prevent the insertion of

Although not particularly limited, the card reader 800 of this embodiment has a structure in which the rear wall of the case is open so that the card can be ejected to the rear so that it can also be used in a card issuing machine. ing.

FIG. 30(A) shows the mounting positional relationship of various sensors and magnetic heads in the card reader.

The insertion detection sensor 808 is disposed closest to the card insertion/ejection opening 802a, and the first position detection sensor 5NSI is disposed immediately in front of the conveyance roller. And shutter pin 8
09b is the insertion detection sensor 808 and the first position detection sensor 5
A security code reading sensor 810a is placed between the NSI and the security code reading sensor 810a.

810b is arranged almost right next to the first position detection sensor 5NS1. Further, the second position detection sensor 5NS2 is located behind the conveyance roller 812, and the third position detection sensor 5NS3 is located behind the conveyance roller 812.
is the fourth position detection sensor 5N behind the conveyance roller 823.
S4 is arranged at the innermost part of the card reader, and the first to fourth position detection sensors 5NSI to 5NS4 are arranged on the same straight line.

Furthermore, punch hole detection sensor 5NSp and punch pin PP
is arranged between the second position detection sensor 5NS2 and the transport roller 823, and the magnetic head 821 is arranged between the transport roller 823 and the third position detection sensor 5NS3.

FIG. 30(B) shows the card detection timing when the card is inserted by various sensors arranged in the positional relationship as shown in FIG. 30(A), and the timing of the control signal to the motor 807 and shutter solenoid 809. show. As can be seen from the figure, in the card reader of this embodiment, when a card is inserted, the insertion detection sensor detects the insertion of the cart and drives the motor and shutter.
4, the information on the card is read in the order of security code, punch hole, and magnetic code at a predetermined timing while detecting the position of the card.

Moreover, the relative distances of various sensors and punch pins.

Since it is important to accurately perform processes such as card reading and punching, each component is attached with high precision so that it has a predetermined positional relationship.

FIG. 31 shows a specific example of the circuit configuration of the card reader control device 188 (see FIG. 21).

The card reader control device 188 includes a card reader controller CPU2 consisting of a microcomputer, a transceiver TRV that converts the level of data signals transmitted and received between the unit control device 1180, and a monitor display provided in the control unit 160. Drivers DRVII and DRV12 that form drive signals 175 and 176, motor 807 in card reader 800, and punching device 82
0, a driver DRV13 that forms a control signal that drives the magnetic head 821, an LED lamp 167, and a shutter solenoid 809; a driver DRV14 that drives a relay RLY that turns on and off the power supplied to the eight motors 7;
, a waveform shaping circuit SMG consisting of a Schmitt trigger circuit that shapes the waveform of data read by the magnetic head in the card reader 800 and detection signals from various sensors, and a blip that latches each read data of the two tracks read by the magnetic head. It has a built-in flop circuit F/Fl, F/F2, a power-on reset circuit, and a watchdog timer, and monitors the pulse periodically output from the controller CPU2 (shared with the reset pulse of the latch LTI and LT2) as a watchdog pulse. and a reset circuit R5T2 that generates a reset signal when the pulse is interrupted.

Further, on/off signals from a device setting device 171 and a card ejection switch SWc provided in the control unit 160 are input to the card reader controller CPU2.

The four light emitting diodes that make up the monitor display 176 are a power-on display LED II that lights up while the power is on, a card-in display LED 12 that indicates that a card is in the card reader, and a card-in display LED 12 that indicates that a card is in the card reader. It is used as the OK display LED 13 that lights up when the control by the controller is executed normally.
D14 is left unused so that it can be used for any other monitor display.

On the other hand, the segment type monitor display 175 has seven segments representing numbers and one dot display segment DT.
By combining these, the details of the abnormality of the cart reader can be displayed using codes as shown in Table 7 below. Note that the error codes in the right column of Table 7 are codes used by the card reader controller CPU 2 to notify the higher-level control device of the details of the abnormality when a corresponding abnormality occurs.

Table 7 The card reader controller CPU2 operates according to the control program in the built-in ROM, and the unit control device 18
Based on the commands from 0, it executes card running control, card data reading, card data checking, etc., and transmits the card number and card reader control information to the unit control device.

Communication with the unit control device 180 is via a built-in serial communication circuit via serial ports TX and RX.
Do this using The output of control signals to the components constituting the card reader 8°O and the input of detection signals from various sensors are performed via an interface circuit 198 as shown in FIG. 32.

Furthermore, the flip-flop FF2 that latches the magnetic data a on the track TRC2 of the magnetic recording section MG of the card is as follows:
The signal is read out from the track TRC1, triggers the flip-flop FFI, and operates using the first clock b as a sampling clock. The flip-flop FFI is triggered by the read clock b and reset by the pulse e output from the CPU 2, thereby outputting a periodic signal C.

FIG. 32 shows a configuration example of an interface circuit 198 provided between the card reader control device 188 and input/output components within the card reader.

In the figure, the symbols SMGI to 5MG5 indicate waveform shaping circuits consisting of Schmitt trigger gates, etc.
RECI, REC2 are rectifier circuits, MCCl, MCC2 are magnetizing current switching circuits, AMP1 to AMP4 are amplifiers, MH
DI, MHD2 are magnetic heads, MT is motor, 5OLI
, 5QL2 is a solenoid, LEDI is a light emitting diode,
DRV21, DRV22 are drivers, 5NSII, 5N
812.5NSp, 5NSI to 5NS5 are sensors. Further, CCC is a current switching circuit for switching the rotational direction of the motor HT, and vCC is a voltage switching circuit for switching the rotational speed of the motor MT.

A read clock signal of read data read by two magnetic heads MHDI and MHD2 corresponding to two tracks TRCl and TRC2, respectively, is sent to an amplifier AM.
After being amplified by PI and AMP3, the rectifier circuit REC
I, rectified by REC2, and further waveform shaping circuit SMGI
, 5MG3 as a square wave to the card reader control device 1188. On the other hand, the card reader control device 18
The write data and write clock supplied from 8 are input to magnetizing current switching circuits MCCl and MCC2 through waveform shaping circuits SM, G2, and 5MG4,
The direction of the head opening current is switched in accordance with "O", amplified by amplifiers AMP2 and AMP4, and supplied to magnetic heads MHDI and MHD2.

In order to jump the motor MT, the card reader control device 18
The current switching circuit CCC changes the direction of the current flowing to the driver DRV21 based on the forward rotation signal and reverse rotation signal given from the driver DRV21 in accordance with the speed switching signal.
Switch the voltage applied to the motor by

On the other hand, security code reading sensor 5NS11 (
The detection signals of 810a), 5NS12 (unused), punch hole detection sensor 5NSp, position detection sensors 5NS1 to 5NS4, and speed detection sensor 5NS5 (821) are waveform-shaped by waveform shaping circuit 5MG5 and then sent to card reader control device 188. The detection signal of the insertion detection switch 808 is noise-cut by a low-nos filter LPF, and then waveform-shaped by a waveform shaping circuit 5MG5.

FIG. 33 shows the timing of writing and reading magnetic data by the cart reader control device 188.

Among the signals in the figure, (A) to (D) are write data information, (
E) to (G) relate to write clock information, and (H)
- (J) show read data information, and (K) - (M) show signal waveforms of various parts related to read clock information. Also, the card reader control device shown in FIG. 31 is shown in (N) to (R) of the same figure! !
188 U), the timing of each signal indicated by symbols ae is shown.

Of these, the signals (H) and (K) are the output signals of the amplifiers AMP1 and AMP3 that constitute the interface circuit in FIG. 32, and the signals (I) and (L) are the output signals of the rectifier circuits RECI and REC2. The signals (J) and (M) indicate the output signals of the waveform shaping circuits SMGI and 5MG3, respectively.

In this embodiment, the data is at 1” as the write method.
When the data is “O” or there is no signal, the polarity is inverted and the previous state is maintained without inverting the polarity.
The RZI method is adopted.

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

On the other hand, when the data written in the above manner is read by the magnetic head MHD2, the output of the amplifier AMPI changes to + or - depending on the direction of magnetization when the magnetization state (D) changes, so the card reader controller C.P.
U2 is a signal (J) obtained by waveform-shaping the output of amplifier AMPI at the rising edge of read clock b. When the corresponding read data a is taken into latch F/F2, signal a
If (N) is at a high level, the data is recognized as "1", and if the signal a is at a low level, the data is recognized as "0" (see FIG. 33 (S)).

In this example, the recording density of magnetic data on the card is 4.134 bit/am (=105 BPI),
Since the card transport speed is 30011 Il/sec, the pulse period of the read clock data is approximately 806 μs. Therefore, when writing magnetic data by CPU2,
The period T0 of the CPU output (E) related to the write clock is output as twice the clock pulse (1°612m5).

An example of the configuration of the card issuing machine 200 is shown in FIG. 34 and FIG. 35.

The card issuing machine 200 of this embodiment includes a bill identifying device 1210 that identifies bills for card purchase, and an issuing device 70 that prints an amount corresponding to the inserted bill and issues a card.
0, a bill dispensing device 230 for dispensing bills as change, various displays 221 to 225, and the control and management device 400 for the entire card issuing machine 200. It is configured. Corresponding to the banknote identification device [210].

The front panel 201, which can be opened and closed, has a bill insertion slot 211,
A purchase selection switch group 212 and an amount display 213 are provided. Therefore, the player must first use the banknote insertion slot 21.
When a banknote is inserted from step 1, the amount of money inserted is displayed on the amount display 213. Then, by pressing a switch corresponding to a desired purchase amount from the purchase selection switch group 212, a card corresponding to the desired purchase amount is issued from the cart outlet 202 of the issuing device 700. Also,
The purchase selection switch group 212 is composed of switches each with a built-in lamp, and when a banknote is inserted, there are switches that can be selected within the range of the inserted amount (three for 3,000 yen, three switches for 3,000 yen,
If the price is 5,000 yen, the corresponding built-in lamp (5) will be lit.

When a banknote is inserted through the banknote insertion slot 211 of the card issuing machine 200 and a purchase amount is determined by the purchase selection switch 212 and a balance is generated, a banknote dispensing device 230 for discharging the remaining balance stores banknotes. It is equipped with a banknote tank and is configured to discharge banknotes corresponding to the remaining amount from a banknote dispensing port 232 provided on the front panel 201.

Further, on the front panel 201 of the card issuing machine 200, an issuance lamp 221 indicates that the card is in a state where the card can be issued, and an issuance stop lamp 22 indicates that the card cannot be issued.
2. A bill insertion indicator 223 that indicates whether or not bills can be accepted into the bill insertion slot 211, a card issue indicator 224 that indicates the issuing status of the card, and a bill dispensing indicator 225 that indicates the status of paying out the balance are provided. In addition, card issuing machine 2
On the inside of the front panel 201 of the 00, there is a monitor display 206 for displaying the type of abnormality (number) in the issuing machine as a two-digit number, and a reset button for resetting the display on the monitor display 206. 207 is provided.

Furthermore, in the card issuing machine 200 of this embodiment.

A device that distinguishes between each of the multiple (several 10) issuing machines installed in a game parlor and manages the issuing machine that issued a specific card!
! A machine number setting device 205 is provided inside to enable the machine number setting device 400 to be grasped, and the machine number set by this setting device 205 is sent to the management device 400, and is used to generate a transmission address during data communication and Used to create data files for each issuing machine.

On the other hand, the issue bag [700] takes out the blank cards stocked in the card tank 701 one by one, sends them to the card reader 800, and stores them in the magnetic recording section of the card. The card number, identification code (store code), issue date code, check code, etc. calculated and sent by 400 are recorded, and the card number, identification code (store code), issue date code, check code, etc. After punching a hole in the PH1 (see FIG. 2), the printing device 750 prints the date of issue, serial number n, and purchase price, and the card is discharged from the card issuing port 202 provided on the front panel 201. The above issuing serial number n is the management bag that received the card purchase application from the card issuing machine 200! ! When 400 receives purchase applications from multiple card issuing machines under its control, it sequentially determines an issuing serial number n and assigns it to each card issuing machine based on this issuing serial number n. The code obtained by performing code conversion processing such as bit rearrangement as described above is recorded as a card number on the magnetic surface of the card and issued, and information regarding the card is recorded in a file within the management device 400. ing.

In order to make it possible to generate a card number from the issued serial number n, the control program of the management device 400 is provided with a card number generation routine and a code conversion routine. Inverse conversion and back calculation routines are provided to confirm the match with serial number n.

The card issuing machine 200 of this embodiment has a card reader 800 that records magnetic data, and a printing device that prints out the issuing serial number n, the date of issue, and the three thousand digits of the purchase price.
Leave the card on standby with two rQJs printed,
By printing and ejecting a thousand-digit number when the purchase switch is pressed, the apparent time required for issuance is shortened.

FIG. 36 shows an overall perspective view of an issuing device 700 with a built-in card reader, and FIG. 37 shows an example of a schematic configuration of the issuing device.

The issuing device 1700 of this embodiment includes a card ejecting device 710 that takes out cards one by one from a card tank 701 containing a large number of cards whose magnetic recording part MG and print display part PRT are blank, and Consisting of a card reader 800 placed at the front, a card reversing device 740 placed behind the card reader 800, a printing device 750 placed below the card reader 800, and a card ejecting device 770 placed in front of the card reader 800. A card issuing control device @ 79 is installed above the card reader 800.
It is controlled by 0. The card reader in the issuing device 1700 of this embodiment may have substantially the same structure and function as the card reader 800 for a pachinko machine.

Card readers for issuing machines differ from card readers for pachinko machines in that (1) they must have a magnetic data recording function, and (2) they must have a structure that allows cards to be ejected backwards. At a certain point. Of these, regarding (1), the interface circuit 19 as shown in FIG.
8 is a waveform shaping circuit 5M that shapes the waveform of the write data signal.
G2゜5MG4 and magnetic current switching circuit MCCl, MCC2
It has a magnetic head MI (D 1 and MHD 2
Since it is possible to write as well as read magnetic data, there is no problem. In addition, card reader 8 for pachinko machines
As mentioned in the explanation of the structure of 00, Figure 25~
In the card reader 800 shown in FIG. 28, the rear wall of the case is open so that the inserted card can be ejected to the rear. Therefore, the issuing device of this embodiment f!
As the card reader 700, the same card reader 800 for pachinko machines can be used.

On the other hand, the card tank 701 is composed of a U-shaped frame having a space the same size as the card, and has a card ejecting device! It is fixed to the upper end of the side wall 711 of 710 with a bolt. A pressing member 702 is placed on top of the cards stored in the card tank 7O1 to apply a certain pressure to the cart and ensure removal of the cards. Notches 702a are formed on the left and right sides of the suppressing member 702 so as not to be detected by a sensor 703 that detects the presence or absence of a card in the tank. Further, the blank card CD stored in the card tank 701 is inserted into the base board 711 of the card ejecting device 710 as shown in FIG.
is placed on top of the front half of the

This base substrate 711 has an opening 71 along the center line.
1a, 711b, and 711c are formed, and a first conveyance roller 712, a second conveyance roller 713, and a third conveyance roller 714 are arranged so as to slightly protrude upward from these openings. Further, a notch 711d is formed in the front end side of the base board 711 so that the operating piece 703a of the card presence detection sensor 703 can be viewed from below.

Furthermore, a support plate 715 is disposed approximately in the upper center of the base substrate 711 and is oriented perpendicularly thereto, and is a card ejecting device! 710 . A bracket 718 having a stopper 717 facing the base board 711 at a distance of one card is attached to the front surface of the support plate 715. Further, behind the support plate 715, a take-out motor 719 for driving the transport rollers 712 to 714 is arranged and fixed to the side wall 716.

A drive pulley 721 is connected to the rotating shaft of this take-out motor 719 via a deceleration mechanism 720.
21 and the rotation shaft 7 of the conveyance rollers 713 and 714.
Driven pulley 722 attached to the end of 13a, 7e 4a
, 723, a timing belt 724 is wound between them. Further, a clutch disk 725a is attached to the rotating shaft of the second conveying roller 713, and a second clutch disk 725b is rotatably disposed opposite to this disk 725a.

Also, the pair of clutch discs 725a.

A clutch lever 727 having a roller 726 at one end that can come into contact with the outer periphery of the clutch lever 725b is swingably attached to the side wall 7↓6. And this clutch lever 72
The other end of 7 is connected to a plunger 729a of a clutch solenoid 729 via a spring 728, and when the solenoid 729 is energized, the clutch lever 727
is rotated and the roller 726 is connected to the clutch disc 725.
The outer peripheries of solenoid a and 725b are contacted at the same time to transmit rotational force, and when solenoid 729 is turned off, the rotational force is cut off. Furthermore, the clutch disc 725b
A pulley 730 is fixed to the rotating shaft of the first conveying roller 712, and this pulley 730 and the rotating shaft 712a of the first conveying roller 712 are connected to each other.
A belt 73 is connected between the pulley 731 fixed to one end.
2 is rolled. Therefore, the rotational force of the take-out motor 719 is transmitted to the first conveyance roller 712 via the clutch mechanism (725, 726) only while the clutch solenoid 729 is energized.

Moreover, this first conveyance roller 712 has its rotation shaft 71
2a, and the top surface is normally lower than the base substrate 711, so that when the rotating shaft 712a rotates 180 degrees, it slightly protrudes upward from the opening 711a. .

In the issuing device 700 of this embodiment, when the purchase selection switch 212 is operated after one 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, and the first conveyance roller 712 rotates once. It is now possible to do so.

As a result, the first conveyance roller 712 is rotated eccentrically,
Card tank 701 above this first conveyance roller 712
Push up the card inside and send it out to the rear. At this time, since the pressing member 702 is placed on the card CD and applies a constant pressure, the bottom card is separated from the group of cards in the tank due to the frictional force with the roller. Moreover,
At the rear, a stopper 717 is provided with a distance of one card from the base board 711, so that feeding of two cards is prevented.

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

Note that a running position detection sensor CPS1 is disposed at the rear end of the card ejecting device 710, and is configured to detect the card that has been sent out.

Furthermore, a pressing roller 734 is provided above the third conveying roller 714 to prevent the card from floating up.

The card taken out from the tank 701 by the card removal device W710 has the card reader 800 write an identification code, card number, etc. to the magnetic recording section, and an internal punch device 820 to punch a hole at the issuing hole punching position. After the card is opened, it is delivered to the card reversing device 740 at the rear. A case 705 is arranged below the card reader 800 to store punching pieces, that is, punch waste.

A card reader control device 288 for an issuing machine, which corresponds to the control device E188 of the card reader 800 for a pachinko machine, is provided in the card issuing control device 790.

Card reversal! [The card sent to 740 is first transferred to a belt 742 wound around transport rollers 741a, 741b, and 741c, and a transport roller 743a.

S is sandwiched between belt 744 wound around belt 743b.
The belt 74 is conveyed along a shaped traveling path and is wound around conveying rollers 746a, 746b, and 746C while pushing the traveling path switching piece 745 disposed at the exit thereof as shown by the broken line A.
7 and the belt 742, and is once sent upward. When the card passes the running path switching piece 745, the switching piece 745 is rotated back from the position indicated by the broken line A to the position indicated by the solid line by the tension of the spring 745a, and the running position sensor CPS2 disposed above moves the switching piece 745 back to the position indicated by the solid line. When the end is detected, the travel motor 706 that disengages the belt 742 is reversely rotated. This causes the card to change direction and begin to be conveyed downward. The belt 74 is wound around conveyor rollers 748a, 748b, and 748c.
9 and the belt 747, the direction gradually changes and is finally sent out horizontally forward.

The belts 742 and 749 are driven by a belt 707 directly driven by a travel motor 706 and a belt 708 interlocked therewith.

The driving force of the travel motor 706 is not transmitted to the belts 744 and 749, and the belts 744 and 749 rotate together due to frictional force as the card moves.

Note that the belt 707 is connected to a card ejecting device 770 which will be described later.
It is also wound around a pulley integrated with the transport roller 771, and the card is ejected by the driving force of the travel motor 706.

Furthermore, the rotation shaft 709 of the conveyance roller 748C is protruded to the side, and a knob 7 is provided at the end thereof as shown in FIG.
By turning this knob 709a by hand, the card can be manually moved while the travel motor 706 is stopped, and a jammed card can be removed. A running position sensor CPS3 is arranged at the end of the card reversing device W740, and when this sensor detects the rear end of the card, the running motor 706 is stopped.

The card sent out from the card reversing device t740 enters the printing device 750, and is first detected by the running position sensor CPS4. Then, the transfer motor 751 in the printing device 750 is driven, and its driving force is transmitted to the transfer rollers 752a and 752b via the belt 762 and gear group 763, and the pressure roller 753a disposed above the transfer rollers 752a and 752b.
753b and move the card forward.

In front of the transfer rollers 752a and 752b, transfer rollers 754 and 755 are arranged along the travel path, and above them, a print head 756 such as a thermal head is arranged so as to be movable up and down along a guide bin 757. . Further, a return spring 758 is inserted around the guide pin 757.

758 is a motor for lifting and lowering the print head, and this motor 758
The rotation of is decelerated and transmitted to the driven shaft 759. A detection piece 760 having a notch is fixed to this driven shaft 759, and rotational position sensors 761a and 761b are arranged opposite the periphery of this detection piece 760. Further, although not shown, the rotational force of the elevating motor 758 is transmitted to the print head 756 via, for example, a cam fixed to the driven shaft 759 and a tappet abutted on the outer periphery of the cam, and raises and lowers the print head 756. At this time, the lifting motor 758 rotates the driven shaft 759 by 180" in one operation. That is, the lifting motor 758 always rotates at a position where the notch of the detection piece 760 faces the sensor 761a or 761b. When the traveling position sensor CPS4 detects the card and operates the lifting motor 758, the rotation of the motor is stopped when the sensor 761a or 761b detects the notch in the detection piece 760. .

As a result, the print head 756 moves to the running position sensor CP.
It is lowered when the card is detected in S4, and when printing is completed, the lifting motor 758 is operated again to move the driven shaft 759 to 180 degrees.
By rotating the print head 756, the print head 756 is raised and stopped. A running position sensor CPS5 is disposed at the exit of the printing device 750, and when this sensor CPS5 detects the leading edge of the card, it operates the running motor 706 in the same direction as before (opposite direction) to move the transport rollers 771a,
The belt 772 wound around the belts 771b and 771c is driven, and when the sensor CPS5 detects the rear end of the card, the conveyance motor 751 in the printing device is stopped. As a result, the card sent out from the printing device 750 is quickly conveyed into the card ejecting device 1770 at the front.

In the card ejecting device 770, as shown in detail in FIG.
73, 774a, and 774b are arranged, and a belt 775 is wound around conveyance rollers 774a and 774b. Moreover, in this embodiment, only this card ejecting device has conveying rollers and their belts 772, 775 arranged in two rows to ensure reliable ejection. A card issuing port 202 is arranged in front of the conveyance path formed by belts 772 and 775, and a running position sensor CPS6 is arranged immediately in front of this issuing port.

Furthermore, a travel path switching member 777 that is rotatable about a support shaft 776 is disposed between the conveyance rollers 773 and 774b. This running path switching member 777 has a spring 778.
Normally, the tip is positioned downward as shown by the broken line opening in FIG. 37, and the card sent from the printing device 1750 is guided toward the card issuing opening 202. However, if the card is not genuine or has a scratch that prevents it from being correctly recorded in the magnetic recording section, the card is moved to the lower confiscation tank 780 by the lane switching member 777.
be guided by. When the card is correctly written, the switching member 777 is rotated downward as shown by the solid line in FIG. 37. Then, the card sent from the printing device 750 is guided to the card issuing port 202. Conveyance roller 77
A confiscation tank 780 is disposed below 4a and 774b, and the lane switching member 7, which is located above in the normal state, is
The cards guided downward by 77 are stored in this confiscation tank 780.

The rear wall 781 of this confiscated tank 780 has a notch 781a.
is formed, and a sensor 782 is arranged so as to face this notch 781a. This sensor 782 is a light receiver, and the corresponding light emitter 783 is placed between the pair of belts 775 and set so that the detection optical axis is oblique, and detects cards entering the confiscation tank 780. Additionally, when the number of cards in the tank exceeds a certain level, the upper end of the card blocks the detection optical axis, making it possible to detect that the tank is full. Furthermore, this confiscated tank 780 can be slid forward and backward on a plate 784 diagonally arranged below it. A long hole 784a formed in the plate 784 is formed on the lower surface of the plate 784.
A guide pin 785 that engages with the plate 784 is fixed thereto, and is always urged rearward by a spring 786 stretched between the guide pin 785 and the rear end of the plate 784.

In this card ejecting device 770, when the end of the card passes and the running position sensor CPS6 or the confiscated card detection sensor changes from on to off, the running motor 706 is turned off and the ejecting or confiscating operation is stopped.

In addition, above the card issuing port 202, there is an issuing bag W700.
A card issuance display 787 is provided to show the progress status of card issuance work.

Furthermore, as shown in FIG. 36, the issue bag [700 of this embodiment is a
2a and 792b, and is placed on a base 793 that is slidably supported in the front and rear direction.
A power supply box 794 with a built-in auxiliary power supply is placed on the left half of the unit, and on the front of this power supply box 794 there is a counter 795 for displaying the number of issued cards, and a counter 795 for displaying the number of confiscated cards, etc. There is a spare counter 796 available.

Further, 797 is a handle used when sliding the entire issuing device placed on the fixed base 791 forward;
8 is an operation button for locking the slide mechanism.

FIG. 40 shows a card issuing machine 2 configured as described above.
An example of the configuration of the control system of No. 00 is shown.

In addition, in the same figure, 790 is a card issuing control device, 2
80 is a unit control device, and 288 is a card reader 8
The transport motor 807 and the magnetic head 8 are each component of 00.
21, a card reader control device that controls the punching device 820, etc., and the ones indicated by symbols LMPi-LMP5 are the lamps built into the purchase price selection switch group 212, and the lamps corresponding to the switches that are turned on; is lit to illuminate the operation buttons from behind.

The control system of this embodiment is roughly divided into a control system based on the unit control device 280 and a control system based on the card issuing control device 790. 280
However, there is a means for accepting money, a means for selecting the desired purchase amount, a communication means for transmitting valuable data to the management device and receiving and receiving a card number in place of the valuable data, a means for dispensing change coins, and an issuance processing state. Responsible for controlling the status display means that indicates the card issuance control bag! 79o is the card ejecting device 710, card reversing device 74, which constitutes the issuing bag [700]. O1 printing device 750 and card extraction device! 770, and a controller 1288 of the card reader 800, which is responsible for checking the card and recording magnetic data.
is in charge of overall control. Communication between the unit control bag [280 and the card issuing control device F790 is performed by serial communication.

On the other hand, the unit control device 1280
In order to send and receive data such as card numbers to and from
10.

The card issuing machine 200 of this embodiment is a unit control device! 280, the status display means consisting of various indicators 221 to 225 provided on the front panel 201 are lit or blinked according to the card issuance procedure to instruct the user on the operating procedure and prevent the user from forgetting the ejected card or change. I try to do that.

That is, when the power of the card issuing machine 200 is turned on and the preparation for card issuing is completed, the unit control device 280
First, the full line indicator 221 provided on the front panel 201
is turned on, and the bill insertion display 223 is made to blink to display a message prompting the insertion of a bill, thereby informing the outside that the banknote insertion is in a waiting state. When a bill is inserted into the bill insertion slot 211 in this state, the unit control device 280 causes the amount display 213 to display a number corresponding to the amount inserted,
And purchase lamp LMP1 with built-in purchase selection switch 212
~Turn on the LMP5 until it reaches the amount equivalent to the amount invested. In other words,
For 1,000 yen, use lamp LMP 1 only, for 3,000 yen, use lamp LM
P1~LMP3.5 thousand yen lamp LMPI~LMP5
lights up to clearly indicate which switches can be operated.

When any one of the valid purchase selection switches 212 is turned on in this state, the bill insertion indicator 223 is turned off,
Instead, the card issue display 2 near the card issue slot 202
24 blinks to notify the user that the card will be ejected.

Then, when the unit controller 280 actually ejects the card from the card issuing slot 202, the unit controller 280 controls the amount display 2.
13 and purchase lamps LMP1 to LMP5 are turned off. At this time, if there is change, the bill dispensing display 225 is flashed to draw attention and the change is disbursed. Note that when there is no change, the bill payout display 225 remains off. Further, when the card is ejected, when the user pulls out the card ejected to the card issuing slot 202, the flashing of the card issuing display 224 is stopped and the light is turned off.

On the other hand, when there is change, the bill insertion display 223 is turned off after the bill dispensing indicator 230 detects the removal of change and receives a dispensing completion signal sent.

Table 8 shows the state transitions of various indicators on the front panel 201 by the unit control device 280.

Table 8 In the figure, O indicates lighting, × indicates off, Δ blinks, D indicates numerical display according to the input amount, and B indicates lighting of the lamp corresponding to the amount.

Note that Table 8 also shows the bill receiving state of the bill insertion slot 221 in each state. This indicates that the next bill cannot be inserted until the card and change are removed.

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

The unit control device 280 of the issuing machine is a card reader control bag! 288 and a unit controller 290 that centrally controls the card issuance control device 790, and a management bag [40
0, and a network controller 553 that establishes transmission/reception rights in the network and performs serial/parallel conversion of data under the control of the data transmission controller. has exactly the same configuration as the unit control bag [180] for a pachinko machine. In other words, data is exchanged between each controller 290 and 551 and between 551 and 553 using dual port memory (RAM).
550 and 552. Among these, the 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 and reception data the same length (packetization) and speeding up data transmission (2. , 5MbpS).

This packet memory 552 is composed of four pages each having a capacity of 256 bytes, of which page O is used for transmitting a transmission request packet, and page 1 is used for transmitting a scheduled data transmission packet. On the other hand, pages 2.3 are alternately used for receiving data packets. The data transmission controller 551 instructs the network controller 553 as to which page to use. Even if the data transmission controller 551 is processing received packet data, even if the next packet data is sent, it will be received by another page, so all packets can be reliably received. A common reset circuit 555 is provided so that each controller 551, 553 can be initialized simultaneously.

An optical connector is connected to the connection side of the network controller 553 to the management device 400 via a signal conversion circuit 554 that performs waveform shaping of received data and converts the signal level in order to increase the drive capability of transmitted data, and a changeover switch 542. 186, and also has a selector switch 542 so that it can be connected to a coaxial cable when the transmission line of the low-layer network is configured with a coaxial cable.
can be connected to a branch circuit 540 for separating and combining the transmitted signal and the received signal.

An optical transceiver 185 is connected to the optical connector 186.

Further, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store a data reception result in response to a request from the data transmission controller 551, and a data transmission controller 551. A latch circuit 562 that stores commands such as data transmission commands to the network controller 553, a latch circuit 563 that stores low-layer network addresses, and three LED lamps that display abnormalities in the communication control state within the unit control device 1280. A monitor display 5 consisting of
6557 is provided with a latch circuit 564 for storing display data to be displayed on each of the latch circuits 561 to 564.
This decoder generates a selection signal by decoding the address given to the .

On the other hand, the unit control device 1280 of the issuing machine is different from the unit control device 180 of the pachinko machine.

The unit controller 290 is the card reader control bag W2
Do not communicate directly with 88, card issuance control bag M7
90. Therefore, a transceiver 57 is provided between the unit controller 290 and the card issuing control device 790 to convert the level of transmitted and received data.
1 is connected.

The unit controller 290 also latches drive signals for placing input signals from the machine number setter 205 and the reset switch 207 on the data bus 581 at predetermined timings, and for displaying various lamps such as the issuing stone tool 221. input/output controller 576, bill validator 210, bill dispenser 230, and purchase selection switch 21
2 to the data bus 58 at a predetermined timing.
1, and the bill validator 210 and the bill dispenser 2.
an input/output controller 57 that latches control signals to 30;
8 are connected.

The control signal from the unit controller 290 to the banknote validator 210 is to send 1000 banknotes that are determined to be genuine banknotes.
There is an instruction signal for distinguishing between 0 yen, 5000 yen, and 1000 yen and storing them in the safe, and an instruction signal for allowing or disabling the insertion of banknotes into the bill insertion slot.

In addition, from the banknote validator 210 to the unit controller 29
The input signal for 0 has the inserted banknote true 100000
Signal when inserting a 000 yen bill and inserting a true 5000 yen bill
The signal when it is determined that it is a yen bill and the inserted bill is a true 100 yen bill.
There is a signal when the banknote is determined to be a 0 yen banknote, an alarm signal that is output when the banknote is pulled out toward the banknote insertion slot after the banknote determination, and a signal that indicates that a banknote has been inserted and that the banknote is being identified. There is a signal to indicate that a banknote jam has occurred, and a signal to indicate that the banknote storage in the safe is full.

On the other hand, from the unit controller 290 to the bill dispenser 23
The control signals for 0 include an instruction signal for setting the number of banknotes to be paid out in binary code, an instruction signal for executing the payout of banknotes based on the set value of the number of banknotes, and a monitor display for displaying the result of the payout execution. There is also an instruction signal for clearing the display on the device (not shown).

In addition, from the bill dispenser 230 to the unit controller 29
0, and then the signal output every time one banknote is dispensed, the alarm signal output when an abnormality occurs in the device during dispensing and the dispensing operation cannot be executed, and the banknotes in the bill storage section. A signal indicating that the remaining amount is 20 or less, a signal indicating that the bill dispensing operation is in progress, and a signal indicating that the bill dispensing operation has ended and the bill has been removed from the bill issuing slot. There is a signal for this.

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

Table 9 shows an example of the error number displayed on the monitor display 206, its contents, and processing.

Table 9 In Table 9 above, if an error marked with a double digit occurs, the system will go down and will be reset. Also, if the error display is blinking, after error recovery processing,
Indicates that you need to press the reset button.

Note that 585 decodes the address signal output from the unit controller 290 and stores it in the program memory 55.
8, unit memory 550, input/output controller 596
, 598, decoders 586, 587, and decoder drivers 588, 889.

Furthermore, in the unit control device [280 of this embodiment, 2m of display data output from the unit controller 290 to drive the amount display 213 is
A digit select signal (
A common signal) is input to the reset circuit 555 as a watchdog pulse. Reset circuit 5
In addition to power-on reset, 55 monitors this watchdog pulse and when the pulse disappears, each controller 29
Generates a reset signal for 0.551,553.

As mentioned above, the unit control device 280 is a management device! 4
00, has information exchange windows in two directions of the card issuance control device 290, and performs control for issuing cards under the control of the management device 400, as well as information exchange that occurs as a result of the issuance process. It has software that periodically sends operating information on the machine to the management device.

Data is sent and received to and from the management device via a unit memory 550, similar to a pachinko machine.

The configuration of the unit memory 550 is exactly the same as that of a pachinko machine (see Fig. 24), and the transmission data area SDA
, a reception data area RDA, and a shared data area CDA that contains commands and status information for informing the controller of the other party that transmission data and reception data are in the memory.

Tables 9 and 10 show the transmission data area SDA and reception data area RD in the unit memory 550, respectively.
An example of the configuration of A is shown. The configuration of the communication area CCA is exactly the same as that of the unit memory of a pachinko machine (see Group 3).

Table 1 The hot code shown in the item 10 above is issued to the management device when the system starts up! 400 is 2 nit memory 55
For example, 010101...01 within the transmission area of 0.
A code is written and periodically sent to the management device to check for damage to RAM data due to noise such as static electricity, thereby making it possible to quickly detect abnormalities in transmitted data.

The monitor information 1 shown on the clothing 10 is as shown in Table 1.
As shown in Figure 2, a bit indicates that a test is being executed when the system starts up, a bit indicates that the initial value is set/not set, a bit indicates a hot code error, and a bit indicates an abnormality in the local network (transmission cable 500) (low layer and high layer). It consists of a bit indicating a problem with the issuing machine, etc.

In addition, as shown in Table 12, monitor information 2 includes a bit that indicates an abnormality in the card reader, a bit that indicates the presence or absence of a card, a bit that indicates the state in the bill tank, a bit that indicates a bill jam, and a bit that indicates forced withdrawal of the bill. It consists of a bit, a bit that indicates the state inside the banknote tank of the balance dispenser, a bit that indicates an abnormality of the balance dispenser, and the like.

FIGS. 42 to 44 show configuration examples of the payment machine 300 described above.

The payment machine 300 of this embodiment has a built-in card reader that reads the card number recorded on the magnetic recording section of the inserted card CD and checks the code. A card payment bag W310 that collects the card, a balance payout device 321, 325 that refunds the amount equivalent to the unused amount that remains unused for the card, and a receipt that prints the number of balls acquired in the game is issued. printer 330 and various displays 3
03, 304, 341, 342, and a unit control device 350 that controls the entire payment machine 300.

This payment machine 300 has a top panel 301 that can be rotated in the vertical direction, and corresponds to the card payment bag [310].
The front end of the top panel 301 has a card insertion slot 302, and the top of the top panel 301 has a ball number display 303 that displays the number of winning balls (number of balls you have) and an amount display that displays the unused amount. 304 is provided. Furthermore, the payment machine 300 of this embodiment has a flat top surface so that it can be used as a counter installed in a pachinko parlor, and is provided with two sets of ball number display 303 and amount display 304, one of which is One is slanted forward so that it is easy for the player to read, and the other is slanted back so that it is easy for the staff inside the counter to read it. Moreover, the upper parts of the ball number display 303 and the amount display 304 are covered with a transparent plate such as a glass plate. In addition, on the rear side of the upper surface of the upper panel 301, the display of the above-mentioned display is rQJ.
A display reset switch 305 is provided to clear the display. When a player first inserts a card into the card insertion slot 302, the card reader 800 in the payment machine 300 reads the card number recorded on the magnetic surface of the card CD, sends it to the management device 400, and sends data regarding the card. Uke is taken. Then, the amount display 304 displays the unused amount, the number of balls display 303 displays the number of balls acquired, and the printer 330 issues a receipt with the unspent amount, number of balls acquired, history data, etc. printed. Further, the card inserted into the card reader is punched at a predetermined punching position IIPH by a punching device.

After a punch hole (account liquid hole) is formed in the card, the card is discharged into the internal card collection tank 314.

In this embodiment, the card reader of the payment machine does not require a recording head, but it is equipped with a recording head to erase the data on the magnetic surface of the card that has already been paid and then eject it, so that the card number can be recorded. make it impossible to decipher the conversion method of
It may also be designed to prevent card forgery.

As the card reader, the cart reader 800 (see Fig. 25) of the pachinko machine 100 is used as is, and like the card reader for the issuing machine, the card can be ejected to the rear. Recovery tank 3
14 are arranged. The printer 330 pulls out a blank sheet stocked in a roll, prints the date of issue, the number of balls acquired, unused balance, and card history on the surface of the blank sheet, and prints the card history in the recess 3 of the top panel 301.
The receipt is discharged from the receipt issuing port 331 opened in 01a.

At the same time, money corresponding to the unused amount is paid out from the balance payout device. The balance dispensing device includes a bill dispenser 321 that dispenses banknotes and a coin dispenser 325 that dispenses 100 yen coins. 32
A coin dispensing port 326 is provided corresponding to No. 5. In addition, during settlement, since fractions of less than 1000 yen are generated as unused money, a coin dispenser consisting of a coin dispensing port 325 that dispenses coins in units of <100 yen as described above! 325
is required.

Furthermore, on the top surface of the top panel 301 of the payment machine 300, there is a payment in progress lamp 341 that indicates that card payment is in progress.
, a payment stop lamp 342 is provided to indicate a state in which card payment is disabled.

In addition, there are 5 and 42 numbers inside the openable and closable front panel 306
As shown in Figure (B), a monitor display 343 that displays an error in the payment machine such as a shortage of banknotes using an error number, and a reset switch 351 that resets the display of this monitor display 343 are installed at the game parlor. A machine number setter 352 is provided for distinguishing each of the plurality of payment machines so that the management device 400 can identify the payment machine that has made the payment for a particular card, and a machine number setting device 352 for distinguishing between each of the plurality of payment machines so that the management device 400 can identify the payment machine that has made the payment for a particular card. Coin extraction switch 353 for ejecting coins
and a print selector switch 3 for instructing whether or not to print history data on the receipt issued by the printer 330.
54 are provided.

The machine number set by the machine number setting device 352 is sent to the management device 400, and is used to generate a transmission address for data communication and to create a data file for each payment machine.

Card payment device! 310, as shown in FIG. 43, a card reader 800, an auxiliary transport bag [311] arranged behind it, and a card that controls the card reader 800 and the auxiliary transport bag W311 according to instructions from the unit controller [350]. Settlement control device 312 and their power supply bag M3
13 and a card collection tank 314 located behind the auxiliary transport device 1311.

Note that the card collection tank 314 is a card payment device!
It is designed to be removably inserted into a vertically elongated tank storage frame 316 fixed to a frame 315 of 310.

Additionally, two counters 3 are provided on the side of the frame 315.
17 and 318, one of which displays the number of collected cards. The other counter is unused.

The auxiliary conveyance device 311 includes conveyance rollers 361 and 362,
A pair of upper and lower conveyor belts 363, 36 wound around them
4, and a transport motor 3 that drives the lower transport belt 364.
65, and the card ejected from the rear end of the card reader 800 is sandwiched between a pair of belts 363 and 364 and transferred toward the recovery tank 314 at the rear.

Although not shown in FIG. 43, the card collection tank 3
14 indicates that the card has been ejected into the tank, or -
A card sensor 319 is provided to detect when the card is full (see FIG. 46).

However, the payment machine 300 of this embodiment enters the card confiscation mode only when the most significant digit of the machine number setting device 352 is set to "9", and the card inserted for payment is returned to the card collection tank after payment. The player is guided to the card and confiscated it, and in other cases, the card is ejected to the front after payment and returned to the player.

Moreover, the payment machine 300 of this embodiment can constitute a counter provided in a prize exchange corner of a pachinko parlor by arranging a plurality of them as shown in FIG. 44 and combining them with the corner unit 50 and the card collection machine 900. is now possible.

In other words, the main body of the payment machine 300 is designed so that the top panel 301 is approximately 1 meter above the floor, and the top surface is substantially flat, so it can be used as a workbench for exchanging prizes, etc. .

Note that the card collection machine 900 has a card insertion slot 905 on the front.
and a prize payout port 906, and a built-in card reader (not shown) for reading the inserted card, and a CRT display 910 as a game device that provides games using used cards is placed on the top surface. .

FIG. 45 shows examples of print formats of receipts printed out in two print modes set by the print changeover switch 354.

Of these, (A) is an example of the format of a receipt when printing only payment data is specified by the print selector switch 354, and shows the pachinko parlor hall name HALL, the card issuing serial number n, the payment date and Reception hours TI
ME, settlement amount AMs, number of settlement balls CNT, and message MSG are printed.

On the other hand, FIG. 45(B) shows an example of the format of a receipt when history data printing is specified by the printing selector switch 354. In addition to the payment data in FIG. 45(A), the purchase amount AMi at the time of card issuance is shown. , history data in the card file (unused amount of money and number of balls held at each time the card status changed during the game) CRR are printed.

In addition, in the payment machine of the above embodiment, the card collection mode is set by setting the most significant digit of the machine number setting device 352 to rQJ, and in other cases, the card is ejected forward after payment. By checking the card status, if the amount spent is rQJ and the purchase amount is refunded, the software is configured to discharge the card to the rear collection tank 314 after refunding the unused amount. It can also be controlled. This makes it possible to avoid abuse of purchasing cards only for the game when a system is configured in which a game is played using cards that have already been paid for at a collection machine.

FIG. 46 shows a configuration example of a control system for the payment machine 300 configured as described above.

The control system of this embodiment is roughly divided into a control system based on the unit control device 350 and a control system based on the card payment control bag W312.
However, bill and coin dispensers 321, 325, various displays 303, 304, 341 to 343, and printer 330
The card settlement control device 312 controls the auxiliary conveyance device 311, the counter 317 as a means for displaying the collected card count, and the card check and reception. It is in charge of overall control of the control device 388 of the card reader 800 that reads magnetic data. Communication between the unit control bag fi 350 and the issuance control device 312 is performed by serial communication.

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

FIG. 47 shows the configuration of the unit control device 350 of the payment machine 300. This unit control bag! ! The configuration of 350 is
The unit controller 390, which is almost the same as the unit control bag W280 of the issuing machine 200 shown in FIG. ! !
4.00, and a network controller 553 that establishes transmission/reception rights in the network and performs serial/parallel conversion of data under the control of the data transmission controller. The system has exactly the same configuration as the unit control device t180 of a pachinko machine. That is, each controller 390 and 551 questions and 551 and 5
Data is received and passed between 53 and 53 using dual port memory (
RAM) 550 and 552. Among these, the 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 and reception data the same length (packetization) and speeding up data transmission (2. ,5Mbps
) and has a buffer function to measure the

This packet memory 552 is composed of four pages each having a capacity of 256 bytes, of which page O is used for transmitting a transmission request packet, and page I is used for transmitting a scheduled data transmission packet. On the other hand, pages 2 and 3 are used alternately for receiving data packets. The data transmission controller 551 instructs the network controller 553 as to which page to use. Even if the data transmission controller 551 is processing received packet data, even if the next packet data is sent, it will be received by another page, so all packets can be reliably received.

A common reset circuit 555 is provided so that each controller 551, 553 can be initialized simultaneously.

An optical connector is connected to the connection side of the network controller 553 to the management bag M400 via a signal conversion circuit 554 that converts the signal level in order to waveform shape the received data and increase the drive ability of the transmitted data, and a changeover switch 542. 186, and also has a selector switch 542 so that it can be connected to a coaxial cable when the transmission line of the low-layer network is configured with a coaxial cable.
can be connected to a branch circuit 540 for separating and combining the transmitted signal and the received signal.

An optical transceiver 185 is connected to the optical connector 186.

Further, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store a data reception result in response to a request from the data transmission controller 551, and a data transmission controller 551. A latch circuit 562 that stores commands such as a data transmission command to the network controller 553, and a latch circuit 563 that stores an address for low-layer networking;
A latch circuit 564 is provided to store display data on a monitor display 556 consisting of three LED lamps for indicating an abnormality in the communication control state within the unit control device 1350. 557 is each latch time j! 561-5
This is a decoder that decodes the address given to 64 and generates a selection signal.

On the other hand, the unit control bag 35o of the payment machine is different from the unit control device 180 of a pachinko machine.

The unit controller 390 is the card reader control bag 3!
388, but via the card payment control device 312.3 Therefore, the unit controller 390 and the card payment control bag! 312, a transceiver 5 that performs level conversion of transmitted and received data.
71 is connected.

The unit controller 390 also includes a pitch count display 3.
03 reset switch 305 and machine number setting device 352.
The input signals from the reset switch 351, coin extraction switch 353, and print changeover switch 354 of the monitor display 343 are placed on the data bus 581 at a predetermined timing, and the drive signals of the payment in progress display 341 and payment cancellation display 342 are latched. An input/output controller 576 that outputs input signals from the banknote dispenser 321, coin dispenser 325, and printer 330 to the data bus 581 at a predetermined timing, and input signals from the bill dispenser 321, coin dispenser 325, and printer 330 to
25 and an input/output controller 578 that latches control signals to printer 330.

The control signals from the unit controller 390 to the banknote dispenser 321 include an instruction signal for setting the number of banknotes to be paid out using a binary code, an instruction signal for dispensing banknotes based on the set value of the number of banknotes, and a payout execution result. There is an instruction signal for clearing the display on a monitor display (not shown) for displaying.

Also, from the bill dispenser 230 to the unit controller 39
The input signals for 0 include a signal that is output each time a bill is dispensed, an alarm signal that is output when an abnormality occurs in the device during dispensing and the dispensing operation cannot be executed, and a signal that is output when the dispensing operation cannot be executed. A signal indicating that the remaining amount is less than 20 sheets.

There is a signal to indicate that the bill dispensing operation is being executed, and a signal to indicate that the bill dispensing operation has ended and the bill has been removed from the bill issuing slot.

On the other hand, from the unit controller 390 to the coin dispenser 32
The control signal for 5 is a signal to drive the coin dispensing motor, and while this drive signal is output, coins are continuously ejected one by one.

And from the coin dispenser 325 to the unit controller 39
For 0, there is a coin detection signal that is output every time one coin is paid out, and a signal that indicates that the remaining amount in the coin storage tank is low. In addition, the unit controller 39
The control signal from 0 to the printer 330 includes print data,
There are an 8-bit data signal that gives a paper cut command after printing, a print command, etc., a signal that instructs the start of capturing this data signal, and a printer initialization signal. Input signals from the printer 330 to the unit controller 390 include an error signal indicating a printing abnormality, a signal indicating that printing paper is out, and a signal indicating that a printing operation is in progress.

Furthermore, the unit controller 390 dynamically displays a number of balls display 303 that displays the number of balls paid, an amount display 304 that displays the amount paid, and a monitor display 343 that displays a number indicating the type of error in the payment machine. Decoder 586a for.

586b, 587 and decoder drivers 588, 589 are connected via a data bus 581.

Table 14 shows an example of the error number displayed on the monitor display 343, its contents, and treatment.

In the same table, if an error marked with the title occurs, the system will be reset as a system down. Further, if the error display is blinking, it indicates that it is necessary to press the reset button after error recovery processing.

Table 14 Note that 585 decodes the address signal output from the unit controller 390 and stores it in the program memory 55.
8 and unit memory 550. Input/output controller 596
, 598, decoders 586, 587, and decoder drivers 588, 889.

Furthermore, in the unit control device 350 of this embodiment, 2 ms of the display data output from the unit controller 390 to drive the amount display 304 is
A digit select signal (common signal) that is periodically output at intervals such as is inputted to the reset circuit 555 as a watchdog pulse. Reset circuit 55
In addition to power-on reset, 5 monitors this watchdog pulse and when the pulse disappears, each controller 390
．． Generates a reset signal for 551 and 553.

As described above, the unit control device 350 controls the management device 40
0. It has information exchange windows in two directions of the card payment control device 2312, and performs control for issuing cards under the control of the management device 400. It has software that periodically sends operating data to the management device.

The unit controller 390 of the payment machine 300 executes payment processing by controlling the above components, checking the card number, receiving and displaying card data, etc.
Collects operating data and sends it to the transmission data area SDA in the unit memory 550 consisting of dual port memory.
write to. The operating data written in the unit memory 550 is sent to the management device through data communication between the data transmission controller 551 and the management device F400 via a transmission cable. Data sent from the management device is also first written to the reception data area RDA in the unit memory 550, and the unit controller 390 reads this to receive the data. The unit memory 550 is provided with a shared data area CDA that contains commands and status information for informing the other party's controller that transmission data and reception data are in the memory.

Tables 15 and 16 show the unit memory 550, respectively.
Sending data area SDA and receiving data area R within
An example of the configuration of DA is shown. The configuration of the communication area CCA is exactly the same as that of the unit memory of a pachinko machine (Table 3
reference).

As shown in Table 16, in this embodiment, the history data of the card is also received, and this is printed on the receipt along with the time data and then output, thereby giving the impression to the player that the payment data is highly reliable. I can do it. However, the maximum history data contained in the card file is 20.
This is the data up to the time.

As shown in Table 17, monitor information 1 shown in Table 15 includes a bit indicating that a test is being executed at system start-up, a bit indicating initial value setting/unsetting, a bit indicating a hot code error, and a bit indicating a local network. It is made up of bits (two bits, one for low-rise and one for high-rise) indicating an abnormality in the transmission cable 500, a bit indicating an error in the payment machine, etc.

Table 17 In addition, as shown in Table 8, monitor information 2 includes a bit indicating paper out, a bit indicating a printer error, a bit indicating an error in the card reader, a bit indicating the state inside the card tank, and a bit indicating the coin dispenser. It is composed of a bit that indicates the presence or absence of a coin, a bit that indicates an abnormality in the coin dispenser, a bit that indicates the state in the bill tank of the bill dispenser, a bit that indicates an abnormality in the bill dispenser, and the like.

Table 18 Next, the pachinko machine 100, card issuing machine 200, and payment machine 300 configured as described above are controlled in an integrated manner, and operating data is collected in real time to monitor the operating status of all terminals and prevent power outages. Even if a failure occurs, upon recovery, the original data state is immediately restored and each part of the system resumes operation.

In addition, a management bag [400] that enables the aggregation of data necessary for the management of a game parlor and issues a reinstatement card with the same qualifications if the card is damaged will be explained.

FIG. 48 shows the specific configuration of the management device 400, and FIG.
Figure 9 shows the system configuration of the management device.

The management device 400 is a central processing unit 1c of a minicomputer class.
Main memory bag consisting of PU and semiconductor memory (RAM)! M-
MEM, transmission control bag [Mask control bag [401] containing SCC, etc., and this mask control device! ! A floppy disk storage device I! as an auxiliary storage device provided on the upper part of 401! 402,))-todisk storage! 403 and a personal computer 410.

The personal computer 410 also includes a CRT display device 1411 for displaying messages and collected data, and a console 4 for an operator to give commands and setting data.
12, CPU and timer TMR (including calendar)
The local processing unit 413 is connected to the central processing unit 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.

In order to connect the local processing device 413 and the central processing unit CPU, the serial communication control devices 406a and 406b are master control devices! ! It is located within 40↓. Of these, the communication control device 406a is used for normal communication, and the communication control bag [406b] is used for interrupt communication in an emergency.

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

Furthermore, this management device 400 includes a restoration card that has the same qualifications as the damaged cart and a test card that can start the pachinko machine while disconnected from the system, as unique to the pachinko gaming system. Card issuing bag! 700 and Pachinko machines"
A box 4 with a built-in auxiliary printer 408 that prints out emergency information generated in the system in real time, such as "stopping", etc.
20 and the auxiliary power supply bag [409 are the above master control devices!
It is provided adjacent to 401. Card issuing device 70
0 and the auxiliary printer 408 are each communication control devices! 4
It is connected to the central processing unit 1CPU via 06c and 406d. Further, the card issuing bag M700 has exactly the same configuration as the card issuing device 700 for the issuing machine 200 shown in FIG. 36. 202 is the card issuing port.

The auxiliary power supply device 409 powers up the main memory iM- in the event of a power outage.
The management device can be operated for at least 10 minutes in order to protect the operating data of all terminals and the data of all issued cards, which are volatilely held in the MEM, by transferring them to the hard disk storage device 403. Back up like this.

Further, in FIG. 49, the symbol SCC is the network 5
This is a transmission control device for enabling data transmission between terminals via 00.

Note that in this embodiment, mainly the pachinko machine 100
And cart issuing machine 200, payment machine 300 and management bag! 4
00 will be described, but the present invention can be extended to a system in which an in-store broadcasting device, a prize exchange device, a vending machine, etc. are also placed under the control of the management device 1400. In particular, the prize exchange device may easily adopt a system in which a card can be directly exchanged for a prize without passing through the payment machine 300.

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

FIG. 50 shows an example of the configuration of the console 412.

FIG. 2B shows the top surface of the console, that is, the panel surface, and FIG. 1A shows the back surface of the console.

In FIG. 50, 421 is an opening switch for instructing each terminal of the system to start business, and 422 is a closing switch for instructing end of business. After opening switch 421 is turned on, closing switch 422 is turned on. Cards can be used at each terminal until the end of the transaction. Further, 423 is a system termination switch for storing the operating data of all terminals in the floppy disk storage bag +1402 after business hours and instructing the management device to stop control, and 424 is for instructing restoration processing of a damaged card. It is a card resurrection switch.

In addition, the above-mentioned opening switch 421, closing switch 422,
The four switches, the system termination switch 423 and the card recovery switch 424, are particularly important switches for this system, and are provided behind them (at the top in the figure) to prevent them from being easily operated while the system is running. It is linked to the key switch 420, and if the key switch 420 is not turned on, each switch 420
It is no longer possible to turn on the power switch 424 by operating it.

425, 426, and 427 are the same type of numeric keypad, return key, and delete key as those provided on the console of a normal personal computer or the like.

On the other hand, 428 is a display menu switch that gives commands to display card-related data and operation data of each terminal on the screen of CRT display device 1411, and 429 is a CRT clear switch that requests erasure of data displayed on the CRT display device. It is. Further, 430 is a print menu switch that gives a command to print data related to the cart, operating data of each terminal, etc. by the printer 414. 43
Reference numeral 2 indicates a setting switch for requesting settings for the number of strikes and stopping mode on the pachinko machine, and 433 indicates that the set number of prize balls have been paid out and the pachinko machine has stopped playing, that is, the game cannot continue. The suspension release switch 434 is used to issue a command to cancel the suspension state of the pachinko machine currently in use, and is used to forcefully terminate terminals for each type at the end of business hours, or to prevent normal control or data collection due to communication network abnormalities, etc. 435 is a forced termination switch for forcibly shutting down all terminals when the terminal becomes unavailable, or forcibly stopping a specific terminal when cheating by a player is discovered. 439 is a date and time setting switch.

Furthermore, the console 412 of the embodiment is provided with a buzzer 440 that generates a sound to alert the operator in the event of an emergency situation such as pachinko being stopped, and a buzzer stop switch 436 that instructs to stop the sound. It is being

431a and 431b are spare switches prepared in anticipation of future expansion of the functions of the management device 400, and can be used, for example, as switches for instructing the printer 414 to interrupt printing.

Among the above switches, the switches 421 to 424 and 432 to 436 shown with double frames in the figure are switches with built-in lamps, and when these switches are turned on, the corresponding process is being executed or the state is continuing. The built-in lamp lights up. However, the lamp in the buzzer stop switch 436 is linked to the buzzer, is lit while the buzzer is sounding, and is turned off when the strap inch 436 is pressed.

Furthermore, the console 412 of this embodiment has a test card switch 437 on its back for giving a test card issuing command, and when the system is introduced, the exchange rate of purchased balls, the store code, the total number of terminals, and the number of winning balls. A built-in switch 438 is provided for instructing setting values such as the number of prize balls per piece and changing the setting values. These switches 437 and 438, unlike other switches, are switches that are rarely used and only need to be known to a specific person (such as the manager of an amusement arcade), so they are placed on the back of the console. It is set in.

Here, the above test card will be mentioned.

As is clear from the configuration already explained, in the gaming system of this embodiment, all terminal machines (pachinko machine, card issuing machine, payment machine) are under the control of the management device, and can be operated by exchanging card numbers, etc. The terminal is now in a state where it cannot operate on its own. However,
Since pachinko machines are frequently used, balls often get jammed or accessories such as so-called tulips break down, and it is necessary to adjust the nails in the game area to adjust the ball payout rate. In that case, a test shot will be performed after repair or nail adjustment, but in this embodiment, the test switch 179 in the control unit 160 of each pachinko machine described above is turned on, and the special nail issued by the management device is turned on. When a test card is inserted through the card insertion/ejection port 802a of the control unit 160, a certain number of balls are given to the pachinko machine so that the game operation can be performed independently.

As a result, there is no need to start up the entire system for trial use during non-business hours. Furthermore, during business hours, trial play can be performed without damaging the operating data during the game.

In the embodiment, the card issuing device f700 provided in the management device 400 is similar to that used in the issuing machine 200, and includes a card tank 701 stocked with blank cards and a card reader 800. However, instead of having a blank card inside, a method may be adopted in which a blank card is inserted from the outside, a code is recorded on the magnetic surface, and the card is ejected. In that case, card tank 7
01 can be omitted. Further, since the test card and the revival card issued by the management device 400 do not necessarily have to clearly indicate the date of use, serial number of issue, etc. like other general cards, the printing device 750 may be omitted. Note that when issuing a resurrection card, a punching device 807 punches a hole at a predetermined punching position PH2 (resurrection hole) of the card.

As mentioned above, the terminals 100, 200.3 of this embodiment
00 is always under the management of the management device 400, and cannot operate independently unless the management device 400 is activated. Therefore, when the system starts up, the management device 4
00 gives the setting value to the terminal and initializes it. Furthermore, prior to this initialization, in order to enable data transmission, the machine number is collected from each terminal to form a single transmission address.

While the system is in operation, data on the operation of the terminals is collected in real time and stored in the main memory bags MM to MEM.

In other words, since there are a large number of terminals under the management of the management device 400, the response will be slow if all control is performed by the management device, so a distributed processing method is adopted in which some processing is entrusted to the unit control device of the terminal. Collect data from all terminals through regular data collection and monitor operating status↓
I strained it.

Furthermore, when data is collected at regular intervals, the amount of data handled by the management device 4° becomes enormous. Therefore, in this embodiment, these data are organized by file management to facilitate handling.

Figure 51 shows the main memory M where data files are set.
-The configuration of MEM is shown in Table 19, and the function and save location of each file are shown.

Among the files in the main storage device M-MEM, files FLI to FL5, excluding the transmission address file FL6, are saved in the hard disk HDD (auxiliary) storage device 403 at the time of a power outage. In addition, data files related to terminal machines, that is, pachinko machine file (hereinafter referred to as P machine file) FL2, issuing machine file FL3, and payment machine file FL4, are stored in the floppy disk FDD (auxiliary storage device 402) as daily report files at the end of business hours. ,
Used for monthly operation data aggregation, etc.

Furthermore, the setting value file FL5 and the transmission address file FL6 are stored on the hard disk HHD at system startup.
The data is loaded into the main memory 1M-MEM, and any changes are saved to the hard disk HHD.

Note that the setting value file is loaded into a common data area CDA provided in the main storage device M-MEM.

This common data area CDA is the central processing bag WCPU.
This area is the working area for the above configuration file FL5 and other files.

System mode, latest cart issued serial number, power outage flag, random number for creating card number, etc. are stored.

Table t9 Next, each file shown in Table 5 will be explained in more detail.

The setting value file FL5 in the table corresponds to the characteristics and configuration of the system, such as the exchange rate for purchase, store code, number of terminals, number of prize balls, number of shots, etc. that are stored in advance on the hard disk by input from the console at the time of system installation. This is a setting value that changes depending on the setting. This setting value file is loaded from the hard disk HDD to the main storage device at the start of normal business operations. Further, the setting value file FL5 can be updated from the console 412 by pressing the built-in switch 438 when replacing the pachinko machine.

Table 20 shows an example of the configuration of the setting value file FL5.

In the same table, the purchase exchange rate is the unit of purchase amount (
For example, 200 yen), it is the number of rental balls, that is, the initial number of balls held, and the number of NAUs is the network adapter unit (communication control device) installed at the connection part between the high- and low-layer networks as a data transmission system.
is the total number of

In the above file, each N
The type and number of terminals connected under each AU are set. 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 machine. Moreover, as shown by j=1 to Y, in this embodiment, all pachinko machines in the game parlor are
The number of prize balls for each group can be set separately for the main and sub prize balls.

However, consecutive machine numbers are given to pachinko machines with the same setting value, and the target range is specified by the first number and the last number.

Furthermore, the number of stops and the stop mode are set in the table indicated by k. Here, the stop mode refers to the method of calculating the number of shots (?9 is the formula). For example, there is a mode in which the ball is simply called off when the number of balls to be paid out as a prize reaches the number of balls to be given out, or There is a mode in which the game stops when the number of pitches minus the number of batted balls reaches the number of hits. Although not particularly limited, in this embodiment, as shown by =1 to 2, the number of stops and the stop mode can be set independently for each group of two.

Table 21 shows an example of the configuration of the transmission address file FL6 used for data transmission.

In Table 21, the type flag is a flag to indicate the type of terminal, and "1" indicates a pachinko machine, "2" indicates a card issuing machine, "4" indicates a payment machine, and "o" indicates a terminal. Each indicates the absence of . The NAU status indicates the state of the NAU, and as shown in Table 22, “
If bit B1 is set to ``1'', it indicates that the token bus is abnormal; if bit B1 is set to ``1'',
Further bit B indicates that the ``Opening Code'' packet has already been received. If It 177 is set to
Each indicates that the NAU is normal.

Table 21 Table 22 The unit number and serial number are the terminal number and its serial number created by removing "4" and "9", and the unit number is the number of the terminal that is created by removing "4" and "9". The number of each terminal placed under the unit), that is, the number that becomes the address on the low-layer network described later, and the channel number is the address of each terminal as seen from the management device, that is, the address on the high-layer network that will be described later. This is the number. However, in the system of the embodiment, the number of pachinko machines connected under one NAU is 64 or less. The NAU number and machine number are set using the setting switch (
↓ 71, 205, 305, 561), and in the case of pachinko parlors, the machine number of the pachinko machine is a consecutive number that is customarily given with numbers excluding "4" and "9". Here, the fact that "4" and "9" are not used means that octal representation is possible. Therefore, using the conversion table shown in Table 23, the machine number expressed in decimal notation is expressed only as numbers 0 to 7. According to this, for example, the machine number r258J is written as "247".

Table 23 If this is expressed in binary code using the binary coded octal system, it becomes rolo-100-1114.

This code shows decimal rl 67J,
As a result, the channel number becomes a continuous serial number without "4" and "9".On the other hand, in order to reduce the address on the lower layer network to 8 bits, the lower 8 bits of the above code are removed. is expressed as the code rlo10.0111 expressed in binary coded octal system, and this is converted into HEX.
When expressed as A, it becomes rA 7 I (J. In addition, please lower one NAU ↓ In addition to pachinko machines, terminals such as issuing machines and payment machines are also connected, and they also have 8-bit unit numbers. In order to give this, the number of S-chin 3 machines under one NAU is limited to 64, and the above code rA7HJ and code r3FHJ (corresponding to 64 in decimal) are ANDed to obtain r27H. r3FH. Taking the logical product with 64 means calculating the remainder after dividing by 64. In this example, this is used as the unit number.The NAU number is added to the beginning of this unit number. rNAU number + number unit number channel number.With this method, data processing is performed using only the binary system, which is the practice of pachinko game parlors that have machine numbers that do not use "4" and "9". Efficient address processing that matches the characteristics of a microcomputer becomes possible.

The above transmission address file is created by input from the console when the system is installed, but NAU itself also creates an address file (unit table) for the units under its control based on input from the machine number setter when the system is started up. and is held in memory.
After the line test, the management device makes a unit table request to the NAU, compares it with the response data, and if it does not match, it is automatically changed (described later). Also, the transmission address file is set to the built-in switch 4 on the back of the console.
It can also be changed by 38.

In addition, consecutive serial numbers starting from "1" are given to each type of NAU, issuing machine, and payment machine as machine numbers.
For AUs and payment machines, the machine number is used as is as the address (unit number), and for issuing machines, the machine number plus r128J is used as the address (unit number) on the lower layer network. This is to avoid address duplication when a pachinko machine and an issuing machine with the same machine number coexist. Duplication of addresses between the pachinko machine and the payment machine is avoided by not allowing both machines to coexist under the same NAU.

Furthermore, the issuing machine and the payment machine can be placed under the same NAU (because we decided to use "machine number + 1281" as the address of the issuing machine).

Further, the address of the NAU 530 on the high-level network uses the NAU number set by the setting device 544, and the address of the NAU on the low-level network uses the r255J fixed address. Also, the address of the management device is "O"
It is said that

Table 24 shows an example of the configuration of the card file FLI.

The card file FLI contains information for each card.

Information indicating the current status of the card identified by the card number.
In this embodiment, it will be referred to as card text below. As shown in Table 25 below, the card status here refers to a bit that indicates a free status that is not used for gaming, a bit that indicates that the game is in progress, a bit that indicates that the card is temporarily away from the gaming machine, and a bit that indicates that the card is currently in a suspended state. A bit that indicates that the card has been settled at the settlement machine, a bit that indicates that both the number of balls and the balance of the card are zero, a bit that indicates that the card has been discontinued at least once in the past, and a forced termination. The card is made up of bits that indicate that the card was used in a pachinko machine that has been restored, bits that indicate that the card has been revived, etc.

In Table 24, the card number is the number obtained from the issuing serial number n using the function f (n), and the number of balls held, the amount of money, and the card status are the issuing serial number n and the card status.Meanwhile, returning to Table 24, A location terminal serial number indicating the location of the terminal where the card currently exists and a location terminal number are registered in the card file FLI. As is customary in pachinko machine parlors, the numbers "4" and "9" are not used as machine numbers, so two types of terminal numbers are generated: one for the back and one for the front.

In addition, in Table 24, the i counter indicates the number of actions the card has taken, that is, the number of times the card has been ejected from the system, which is an organic combination. number, number of balls, amount,
Card information such as time, or history of the card, is recorded. Statistically speaking, most players play on less than 20 pachinko machines a day, so in this embodiment, card history is recorded up to 20 times at most. however,
If the number of times exceeds 20, it is recorded by updating the table indicated by 1=20. Note that in the above case, the i counter does not count game interruptions.

In other words, each card information is recorded in a new area at the time of suspension, but when the game end switch is turned on after the suspension is canceled, the counter is not updated and the card information is recorded in the same area overlappingly, so that the value of the i counter is changed to the actual game. It matches the number of units.

Here, the card status, action, and registration of FLI card information in the card file will be explained using FIG. 52.

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 SSO to the free state S81. Then, when the card is inserted into a desired pachinko machine 100, the game state shifts to gaming state SS2. When the number of balls and the amount of money on the card become zero due to the game, the card is ejected and the state shifts to zero return state SS3. Also, during the game, the interrupt switch 11
゜When 5 is pressed, the card is ejected and the suspended state SS
4, and by re-inserting the same card, the game state is returned to S.
Return to S2. Then, when the end switch 114 is pressed to end the game during the game, the card is ejected and the state shifts to the free state SS1.

Cards are also ejected due to forced termination by the CPU or abort occurrence, and the game state SS2 becomes free.
Move to. Take the free card to the payment machine 300.
When the user goes to , and performs payment processing, the card is marked as invalid, then the card is collected, and the process moves to the payment completed state S85. In the system of this embodiment, it is also possible to take the card in the suspended state SS4 and go to the payment machine 300 without returning to the pachinko machine and perform the payment process, and in that case, the card in the suspended state SS4
The process moves to the settled state SS5.

In the above state transition diagram, the arrows indicating the transition direction with a letter O are the actions that involve recording card information in the card file FL3. Further, in each block, the code indicated by xxH is a hexadecimal representation (HEXA representation) of the corresponding state using the code indicating the card state in Table 25.

Next, Table 26 shows an example of the configuration of the P machine file FL2.

In the same table, the items from machine number to card status are the data held in the transmission data area shown in Table 1, and these are sampled once per second by the management device 400 and registered in the file. be done. In addition, the number of main prize balls, the number of sub-prize balls, the number of batting balls, and the batting mode are as follows:
When the system is started up, it is registered in the P machine file FL2 based on the setting value file FL5 shown in Table 20.

Zero total capacity 64 x 506 = 32384 = approximately 32 byte total capacity 6
4X50=3200=3.2 and total byte capacity 64X1
0=640=0.64 Data marked with a circle in the byte table 26 means data to be saved on the floppy disk as a daily report file when the system is terminated.

Further, the monitor information 1.2 in the pachinko machine file is shown in Tables 4 and 5, and the operation information is shown in Table 6.

Next, Tables 27 and 28 show the issuing machine file FL3 and the payment machine file FL4, respectively. The data items shown in Table 27 are the data held in the sending data area of the issuing machine shown in Table 10, and the data items shown in Table 28 are held in the sending data area shown in Table 15. Each match the data shown. These are sampled by the management device once per second.

In Tables 26 and 27, data marked with an O in the save column is data that is saved on the floppy disk FDD at the end of business hours.

Further, monitor information 1 and 2 in the issuing machine file are shown in Tables 12 and 13, and monitor information 1 and 2 in the payment machine file are shown in Tables 17 and 18.

Furthermore, the operating information of the issuing machine and the operating information of the payment machine are 000.
0 0000 0000 0001 indicates that it is in operation.

Next, the card issuing machine 100, the pachinko machine 200, the payment machine 300 as the terminals configured as described above, and the management device that centrally controls these terminals! ! A data transmission path (local area network) that organically connects 400 to enable data transmission and card operation will be described.

FIG. 53(A) shows a configuration example of a pachinko gaming system using a hierarchical data transmission path.

In other words, 100 to 1000 terminals are grouped into groups of 20 to 40 units, such as island equipment at a game store, and each group of terminals is connected to a token that circulates at high speed on a ring-shaped transmission path. A network adapter unit (hereinafter referred to as NAU) is connected to a token-passing low-layer network (token bus) 510 in which a node (terminal device) that receives a packet indicating a transmission right has the right to send and receive data in the form of a packet. ) 530.

A plurality of (7) NAUs 530 that control each low layer network (token bus) 510 are connected to the CSMA/CD
(Carrj, er 5ence Multip
le Access with Co11isi
on Detect) type high-rise network 520
It is connected to the management device 1400 via.

The low layer network 510 has a transmission speed of 2.5 Mbps (megabits per second), the high layer network 520 is controlled to have a transmission speed of 10 Mbps, and the NAU 530 absorbs the difference in transmission speed between the two. It acts as a buffer to enable smooth data transmission. In other words, the NAU 530 has a data relay function between different types of networks and a data logical collection and delivery function.

The reason why the data transmission path 500 is configured hierarchically is that if more than 500 terminals are connected to one management device and you try to collect regular data from each terminal every second, the host computer In a system that directly communicates with the terminal unit, the burden on the host computer becomes too large, and the transmission speed of Cheapanet is 10Mbp.
However, since controller LSIs are expensive, it would be too costly to connect the terminal units directly. In addition, the transmission speed is too slow to collect data once per second using only the token bus. Moreover, in the system of this embodiment, the high-rise network 51
Both the transmission lines constituting 0 and the transmission lines constituting the low-layer network 520 are configured so that either coaxial cables or optical fiber cables can be used.

In Fig. 53 (A), the symbol P indicates a pachinko machine, the symbol H indicates a card issuing machine, and the symbol S indicates a payment machine. be.

Each of the terminals P, H, and S is connected to a branch line branched from the network 510. Control units 160, 250 and 350 of each terminal are connected to the terminal end of each branch line. In FIG. 53(A), the symbol U indicates the unit control device of each terminal.

As can be seen from the figure, 25 NAUs are placed in the high-level network facing the management device, and 23 pachinko machines, payment machines, and issuing machines are placed in the low-level network facing the NAU. .

In addition, the low-layer network consists of one issuing machine and 22 pachinko machines.
There are two types: one with a machine and the other with 10 issuing machines and 5 payment machines. In this way, since there is at least one issuing machine in each low-layer network, in this embodiment, the NA
The U530 is installed inside the issuing machine 200. The reason for providing 10 issuing machines and 41!5 payment machines is to enable issuing machines or payment machines to be arranged in rows in a concentrated manner.As shown in Figure 53 (B), Figure 53 (C
) show examples of network configurations when using optical fiber cables as transmission paths.

When using a coaxial cable as a transmission path, each NAUS
30 are connected to the high-rise network cable 515 in parallel with each other by a T-shaped connector 505, and each unit (terminal) H□P P 11 P 21・゛...P2
□ is also connected to the low-layer network cable 525 in parallel form by the T-shaped connector 505.

On the other hand, when using an optical fiber cable as a transmission path, the management device 400 is provided with a multichannel optical transceiver 502 that has a photoelectric conversion function, a transmission data distribution function, and a reception data multiplexing function, and the NAU 530 is equipped with a multichannel optical transceiver 502 that has a photoelectric conversion function, a transmission data distribution function, and a reception data multiplexing function. Each is provided with an optical transceiver 507 that performs photoelectric conversion.

Each optical transceiver 507 and multichannel optical transceiver 502 are connected by two-core optical fiber cables 512, respectively. In addition, NAU530 and unit H
19P11P2F, . . . P2□ are each provided with an optical transceiver 508 for performing token bus type data communication in a low layer network, and connected by a two-core optical fiber cable 5221. Each optical transceiver 508 has a photoelectric conversion function for transmitting and receiving data as well as a branching and switching function for optical signals.

In addition, each of the optical transceivers 507 and 508 and the NAU5
30 or units H, P, P2゜...P2□ are connected by coaxial cables. Data transmission and reception on the high-rise network 510 and the low-level network 520 both use a packet switching method, but the format of the packets differs on each network.

That is, the packet on the high-rise network 510 is 1
1010...1011 synchronization signal consisting of 64 bits called preamble, destination address, source address, packet type a (unused), 48
It consists of a data field of ~1500 bytes and an error correction code CRC. Further, although not particularly limited, data on the high-rise network is transmitted in Manchester code.

On the other hand, data is transmitted and received on the low layer network (token bus) 520 using five types of packets, each having a different field configuration and function. The five types of packets are a token packet for granting transmission rights, a free buffer intermediary packet for determining whether the other party can receive data, a data packet for transmitting data, and positive and negative responses to the sender. “ACK” for
"packet" and "NAK" packet. Each packet has a different length, but they have a common bit pattern at the beginning that indicates the beginning of the packet called an alert burst. In addition to the alert burst, the data packet address fields to indicate the source and destination;
It has a field indicating the length of data, a data field, and a field containing an error correction code. In addition,
Data is transmitted on this low-layer network 520 using an RZ (Return to Zero) code.

Table 29 below lists the packets used on the high layer network, and Table 30 lists the packets used on the low layer network.

Note that the hard ACK in Table 30 is an ACK issued by the network controller in hardware, and is not a response in which the unit controller or data transmission controller is involved in software.

Table 29 Table 30 FIG. 54 (A) shows an example of the circuit configuration of the NAU (network adapter unit) 530 that buffers data transmission between the low layer network 51O and the high layer network 520, and FIG. An example of the configuration of a unit body incorporating it is shown below.

The NAU 530 in this example is connected to the lower layer network 510.
A low-layer network controller 533 that establishes receivables and converts data from serial to parallel, and CSMA.
A high-rise network controller 537 that establishes transmission/reception credits and performs serial/parallel conversion of data in a high-rise network of the /CD system, and a data transmission controller 535 that controls data transfer between these network controllers 533 and 537. . Among the above controllers, the low layer network controller 533 is
It is composed of a communication LSI dedicated to token passing, and the high-level network controller S37 and data transmission controller 535 are composed of a general-purpose microcomputer. And these controllers 533 and 5
35 and between 535 and 537, there is a buffer packet memory 53 for absorbing the difference in data transmission speed between the low layer network 510 and the high layer network 520.
4 and a data memory 536 are connected to each other.

The packet memory 534 and data memory 536 are configured by dual port memories and have a transmit data area and a receive data area. In addition to the transmission/reception data area, the data memory 536 has a regular data area for storing regular data collected from units, a unit table area for storing unit transmission addresses on the low-layer network, and a working area for the data transmission controller 535. ing. The scheduled data area includes the transmission data area for all units (see Table 1, Table 10, and Table 15).
The unit table area has the same structure as the transmission address file of the management device. In addition, the low layer network controller 533
A transceiver 508 is connected to perform waveform shaping and level conversion of transmitted and received data signals.

Moreover, as mentioned above, this transceiver 508
A branch that separates and combines the transmission signal and the reception signal via the changeover switch 542 so that the transmission line of the low-layer network can be configured with a coaxial cable or an optical fiber cable. circuit 54
0 and an optical connector 186. A coaxial cable connector 187 is connected to the branch circuit 540.

Similarly, a transceiver 507 that performs waveform shaping and level conversion of transmitted and received data signals is connected to the high-level network controller 537.

Moreover, as mentioned above, this transceiver 507
A branch port that separates and combines the transmitting signal and the receiving signal via the changeover switch 543 so that the transmission line of the low-layer network can be configured with a coaxial cable or an optical fiber cable. 541 and an optical connector 86. Branch circuit 5
41 is connected to a coaxial cable connector 187.

Furthermore, the NAU 530 of this embodiment has a plurality of N
A NAU number setter 544 that sets a number to distinguish AUs from each other, and a minimum unit that sets the minimum number of pachinko machines or payment machines among the terminals existing on the low layer network 510 under the control of each NAU 530. A number setting device 545, a number setting device 546 for setting the number of pachinko machines or payment machines existing on the low layer network under its control, and setting devices 547, 548 for setting the minimum number of issuing machines and the number of connected machines. and a setting device 549 for setting the type of NAU.

The NAU type here indicates that the terminal configuration is a combination of an issuing machine and a pachinko machine, or a combination of an issuing machine and a payment machine. The setting values of each setter 561 to 563 are input to the data transmission controller 535 in the NAU 530 via the buffer gate 538, and the NAU number is used to form the transmission address of each NAU in the high-rise network 520. Furthermore, the transmission address of each terminal in the low layer network 510 is formed by the minimum number and the number of terminals.

In FIG. 54(A), 531 is a program memory that stores a control program for the data transmission controller 535, and 532 is a system bus that connects each controller 535, 537 and memories 531, 534, 536.

A board on which the circuit of the above configuration is mounted is shown in FIG. 54(B).
It is built into the NAU unit main body 539.

The front and rear walls of this unit body 539 are provided with the aforementioned high-rise and low-layer network optical fiber cable compatible connectors 186 and high-rise and low-rise network coaxial cable compatible connectors 187, respectively. moreover,
The various setting devices 545 are provided on the upper surface of the unit main body 539.
~549 have been set up. The NAU number setter 544 is provided on a board inside the case.

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

In the local network (FIG. 53) with a hierarchical structure in which a high-level network and a low-level network are connected via the NAU 530 as described above, the management device 400 conducts line tests and settings for each terminal through each NAU 530 at system start-up. Along with setting the value,
While the system is running, the NAU530 is connected to the low layer network 5.
10 to collect operating data from the terminals P, H, and S once per second and store it in its own memory.

Then, the accumulated data is stored in a data file in the management device 400 from each NAU 530 via the high-rise network 520 once per second in response to a request from the management device 400.

As described above, the communication network has a hierarchical configuration using the NAU 530 as a buffer, and the high-level network 520 is connected to the low-level network 510 at a transmission rate of 2.5 Mbps.
Since it is designed to have twice the transmission speed, 100~
Even in a system having 1000 terminals, a large amount of operating data as shown in Tables 1, 10, and 15 can be collected from each terminal to the management device once per second.

Table 31 shows that in the data transmission system, the management device 400 and the NAU 530 questions are connected to the management device 400, the pachinko machine 100, and the card issuing machine 200 via the NAU 530.
, unit controllers 190, 290 of the payment machine 300
, 390 are shown.

In the table, the unit refers to the control unit of each terminal machine (pachinko machine, card issuing machine, payment machine). In addition, the "unit table request" packet is a packet used by the management device to confirm the connection and address of the units connected to each NAU when the system is started up. Connection is confirmed. The address information in the packet is compared with the value in the unit table file, and if they do not match, the data is changed to the data in the packet. For units whose connection cannot be confirmed, confirmation is made again using the subsequent initial value setting packet.

Furthermore, the "Card In" to "End of Interruption" packets depicted in Table 3 are packets specific to the Pachinko machine 100, and among these packets, the "Card In" packet is used to send cards to the control unit 160 of the Pachinko machine. When the is inserted,
This is a packet for requesting information (card text) regarding the card from the unit side to the management device 400.

Here, the card text is text containing four pieces of information: card number, number of balls held, amount (unused amount), and card status. Furthermore, the "return to zero" packet is used to send a card text from the control unit 160 of the pachinko machine to the management device 400 when both the number of balls held and the amount of money on the card become zero during a game with the pachinko machine. This is a packet of

On the other hand, the "Suspension Ended" packet is generated when the player presses the suspend switch 114, receives the card, leaves the pachinko machine, and then inserts the card into the payment machine to make payment without returning to the pachinko machine that was suspended. This is a packet in which the management device instructs the pachinko machine to cancel the suspended state of the pachinko machine. This allows the player to make payment without having to go back to the pachinko machine where the game was interrupted and press the game end switch 115.

Furthermore, the "Card Purchase" packet depicted on Table 3 is a packet specific to the card issuing machine 200, in which a bill is inserted into the bill insertion slot 211 of the issuing machine and the purchase selection switch 200 is used.
12 is turned on, the unit control device 280 requests the management device 400 for the card number and issuing serial number regarding the card.

In the system of this embodiment, the card issuing machine 200
Before inserting banknotes into the bank, you must reserve your card number, etc.
In order to make advance preparations so that the amount can be printed and issued when the bill is actually inserted, the card issuing machine 200 sends a "Card Purchase" packet with "O" in the card amount field. When this happens, the management device 1400 determines that the packet is an issuance reservation packet, determines the issuance serial number and card number, secures an area for the card in the card file, and sends an ACK packet containing the issuance serial number and card number. is returned to the card issuing machine. on the other hand.

When a bill is inserted, the card issuing machine sends a ``card purchase'' packet to the management device with the actual purchase amount entered in the card amount field.Then, the management device looks at the card number field and Determine that the card has been reserved for issue, search the card file, write data such as the purchase amount and issue time in the data area of the cart, and then activate the card.
K packets are returned to the issuing machine.

The "Card Settlement" and "Card Settlement Completed" packets depicted in Table 31 are packets specific to the cart settlement machine 300, and are sent to the unit controller 350 when a card is inserted into the cart insertion slot 302 of the settlement machine. management device 400
This is a packet for sending the card number related to the card and requesting the unused amount, number of balls, and history of the card.

In addition, the ``Card Settlement Completed'' packet is a packet to notify the management device 400 that card settlement has been completed, and when the management device receives this packet, it changes the card status of the card in the card file to ``Settled...''. ” and write the data at the time of payment in the column j = 20 of the history data. In response to this “Card payment completed” packet, the management device 400 sends an “ACK” packet to the payment machine 300 to complete the card payment. Once the process is complete, the primary card can be inserted into the payment machine.

The "line monitor check" packet in Table 31 is a packet to confirm the recovery of the NAU when the NAU is determined to be abnormal based on regular data, and is sent periodically (every 30 seconds) until the NAU recovers. ACK from
Recovery is confirmed upon reception of the packet, and the operation data of all units under the control of the NAU is transmitted using a "unit recovery data" packet to recover the NAU and units. In addition, the 'unit monitor check' packet is a packet to confirm that the unit has recovered when it is determined that the unit is abnormal based on periodic data.It is sent periodically until the unit recovers, and an ACK packet is received from the NAU. The NAU that receives this packet checks the connection with the network controller of the relevant unit, and if the connection is confirmed, the
Send K packet to the management device.

Furthermore, in Table 3, “ACK” and “NA
The packet "K" is sent to the management device 400, network adapter unit 530, and each terminal 100.200.
, 300, is a packet used when receiving a transmission request to respond to the other party that the request has been accepted, or to respond that the request cannot be accepted.
When returning "ACK", requested data such as card text may be added.

Note that the packet codes 80H and 8 shown in Table 31
1H, . . . are expressed in hexadecimal notation, and it goes without saying that the code is an example and is not limited to this.

55(A) shows the basic configuration of packets sent and received between the management device 1400 and the NAU 530 via the high-rise network 520, and FIG. The basic configuration of packets (excluding command packets that do not require ACK) sent and received between the NAU 530 and each unit on the high-layer network 520 is shown in FIG. This shows the basic structure of packets sent and received via.

In FIG. 55, HHD indicates a packet head used in the high layer network 520, and LHD indicates a packet head used in the low layer network 510.

By the way, in the system of this embodiment, the communication control by the NAU 530 can be roughly divided into control that simply mediates communication and auxiliary control that acts as a substitute for controlling the management device. Among these, auxiliary control refers to communication control for information exchange that the management device would normally have to do directly with the unit, entrusted to the NAU, and the NAU exchanges information with the unit. This includes information not related to card data, such as store opening codes, regular data collection, etc. With this method, the management device only needs to communicate with 25 NA, U, and N
Since the AU only needs to communicate with 23 units, the burden on the management device is greatly reduced.

On the other hand, during mediation control, the NAU 530 may simply remove or add packet heads to transmitted and received packets.

In other words, a packet in the format shown in FIG. 55(B) transmitted from the management device 400 to the unit is
530, the high-rise packet head HHD is removed and the packets are sent onto the low-layer network 510, and the packets sent and received from each unit to the management device 400 using only the low-layer packet head LHD are sent to the high-rise packet head HHD at the beginning of the LHD in the NAU 530. A packet head HHD is added to the high-rise network 520 as a packet in the format shown in FIG. 55(B).
sent upwards.

Table 32 lists the definitions of the unique data laid out in the head portion of each packet.

56 to 61, the above-mentioned high-rise network 510
An example of the format of a typical packet transmitted and received between the management device 400 and the NAU 530 is shown above.

In the "line test" packet shown in FIG. 56 (A), the transmission data field contains the date code, identification code (parlor code), and the number and minimum number of pachinko machines, issuing machines, and payment machines belonging to the destination NAU530. Please enter the machine number and send. Then,
The NAU 530 stores the date code and identification code, compares it with the number calculated based on the settings of the single unit number setting switch 562, etc., and sends the information to the management device 400 as shown in FIG. 56(B). ``ACK'' packet is returned. In addition, when the NAU 530 receives a ``line test'' packet from the management device, it sets the unit number setter and number setter 544 to 548 for all units under its control.
Packet head L for low-layer network using the transmission address calculated in advance based on the setting value by
A "line test" packet with only the HD attached is formed and sent to the second unit one after another while updating the address.

Then, an "ACK" containing the unit number, serial number, and channel number is received from each unit, and a unit table as a transmission address file is created and stored based on the received data.

FIG. 57(A) shows the structure of a "unit table request" packet from the management device 400 to the NAU 530, and FIG. 57(B) shows the structure of the "ACK" packet as a response. When the NAU 530 receives the ``Unit Table Request'' packet, it returns an ``ACK'' packet containing the NAU number, NAU status, and data regarding all units in the unit table.

FIGS. 58(A) and 58(B) show the structure of the "Pain initial value setting" packet sent from the management device 400 to the pachinko machine 100 and the "ACK" packet as its response on the high-rise network.The data field of this packet Initial values such as the purchase ball rate and the number of prize balls necessary for operation of the pachinko machine are entered in and transmitted.

In addition, FIG. 58(A) is an "initial value setting" packet for the pachinko machine, and the "initial value setting" packet for the issuing machine 200 and the payment machine 300 (I!8 in the figure),
The date code, identification code, and hot code are included in the data and sent.

Further, FIGS. 59(A) and 59(B) show the structure of the "regular data request" packet for the Pachinko machine and its response packet among the "regular data request" packets for the unit.

In the response packet to the scheduled data request shown in FIG. 59(B), the operation data of all pachinko machines belonging to one NAU 530 are concatenated under the packet head LHD, *1 The head and data indicated by *2 are related to the first pachinko machine, the head and data indicated by *2 are related to the second pachinko machine, and the data for all pachinko machines continues in the same manner.

In addition, the data field of the response packet (not shown) for a regular data request to the issuing machine 200 or the payment machine 300 contains all the data in the transmission data area of all the issuing machines (see Table 1o) or the transmission data of all the payment machines. Area (see table 15)
Enter all the data in the file and send.

FIG. 60 shows an example of the configuration of various command packets without data from the management bag W400 to the payment machine 300 and their response packets.

The packet type l1PACKET$TYPE in the same figure includes codes 90H (opening code), 91.8 (closing code), 95H (forced termination request), and 96H (forced termination release).
, 8CH (line monitor check), or BIH (restart) code is entered. Further, among the "forced termination request", "4 forced termination cancellation", and "restart" packets, the type packet (one that targets the entire unit) is provided with a field in which a code indicating the type of unit is entered.

Figures 61 (A) to (C) show the "card-in" packet, its acknowledgment packet "ACK" and its negative response packet "NAK" that are sent to the management device when a card is inserted into a pachinko machine. 5 shows the format of a packet on a high-rise network 510.

In the data column of the "card-in" transmission packet, a card text in which only the card number is written is read out from the unit memory and sent. On the other hand, the data field of the response "ACK" packet contains the card text among the data related to the card read from the card file of the management device. Moreover, the card status in this card text indicates the cart status after being updated.

In addition, the transmitted and received packets when the suspension switch is turned on, the transmitted and received packets when the suspension card is inserted, the transmitted and received packets when the payment switch is turned on, and "return"
Or, the structure of the transmitted/received packet when "stop" occurs is the same as the "card-in" packet and its response packet in FIG. The only difference is that the text is entered in the data field, and the card text in the data field contains different data for each card. In particular, in the "Card-in" packet, the fields of "Number of balls", "Amount" and "Card status" in the card text are "0", whereas in other packets of the same type, these fields also contain the card. It is designed to include data related to the process and send it.

62 and 63 show typical examples of the format of packets transmitted and received between the pachinko machine 100 and the NAU 530 via the low-layer network 520.

Of these, FIG. 62 shows an example of the structure of a ``periodic data transmission'' packet, and FIGS. 63(A) and 63(B) show an example of the structure of a ``unit recovery data'' transmission/reception packet.

Among these, the "regular data transmission" packet contains the transmission of the unit memory of the relevant pachinko machine and all data in the data area, and the management device receives this data and stores it in the relevant pachinko machine in the P machine file. Update the data. On the other hand, the 'unit recovery data' packet contains all the data in the P machine file of the management device and the date, identification code, and hot code read from the setting value file.
It is sent in accordance with the configuration of the data area of the unit memory. However, for the received data packet head and card text that overlap with the transmitted data area of the unit memory, duplicate transmission is omitted and the unit controller side copies them from the transmitted data area to the received data area.

The response packet to the above packet is configured to include all data in the transmission data area and send it.

64 to 66 show typical examples of the format of packets transmitted and received between the card issuing machine 200 and the NAU 530 in the low layer network 520.

Of these, FIGS. 64(A) to 64(C) show configuration examples of a "card purchase" packet requesting the management device to reserve a card, its response packet "ACK", and negative response "NAK".

In the data field of the "Card Purchase" packet when making a reservation for card issuance, only the issuance acceptance number m indicating the number of issued cards in the relevant issuing machine is entered, and the card amount, card number, and issuance serial number are not included. Send as rQJ6
On the other hand, the data column of the response "ACK" packet contains the issuing serial numbers n for all issuing machines determined from the issuing acceptance number m in the management device and the card number calculated from this issuing serial number n. The last “
The checksum Jll contains the added value from the issuing machine number to the issuing acceptance number as a check code.

On the other hand, when a banknote is inserted into the issuing machine and the purchase amount is determined, the structure of the "card purchase" and its response packet sent from the issuing machine to the management device is exactly the same as the packet shown in FIG. The only difference is that the actual purchase amount is entered in the card amount field, and the number already determined at the time of reservation is entered in the card number and issuing serial number fields.

Furthermore, FIG. 65 shows an example of the configuration of a "regular data transmission" packet, and FIGS. 66 (A) and (B) show examples of the configuration of a "unit recovery data" transmission/reception packet.

Among these, the ``periodic data transmission'' packet.

All the data in the transmission data area of the unit memory of the issuer is sent, and the management device receives this data and updates the data of the issuer in the issuer file. However, among the transmitted data, the card amount and issuance acceptance number are data that are not used by the management device, so even if they are transmitted, they are not registered in the file.

On the other hand, there is no unit recovery data.

All data in the issuer file of the management device and the date, identification code, and hot code read from the setting value file are sent in accordance with the configuration of the data area of the unit memory 550. however.

The received data packet head and card text that overlap with the transmitted data area of the unit memory are configured to omit redundant transmission and are transferred from the transmitted data area to the received data area on the unit controller 290 side. The data indicated by *4 in the received data is written in the received data area in the unit memory. The response packet to the above packet is configured to include only all the data in the transmission data area and send it.

67 to 70 show typical examples of the format of packets transmitted and received between the card payment machine 300 and the management device 400 on the low-layer network 520. Of these, FIGS. 67(A) to 67(C) show an example of the configuration of a "card payment" packet that requests the management device to perform card payment, and its response packets "ACK" and "NAK."

At the time of card payment, only the cart number read by the card reader of the payment machine is entered in the data field of the "card payment packet" and sent.On the other hand, the data field of the response "ACK" packet contains the card number in the management device. The card file is searched using the issuing serial number n calculated backwards from , and the read data of the card is inserted and sent.

On the other hand, when the payment machine 300 completes payment processing such as issuing a receipt with the number of coins printed on it, the payment machine 300 sends a message "Card payment complete" to the management system [400] and a response packet. The configuration is shown in FIG.

Only the card number is entered in the data field of the sending packet. No data field is needed in the response packet.

Furthermore, Fig. 69 shows “regular data transmission” from the payment machine.
An example of the structure of the packet is also shown in FIG. 70(A).

(B) shows an example of the structure of a transmission/reception packet of ``unit recovery data'' related to the payment machine.

Among these, ``periodic data transmission'' packets.

All the data in the transmission data area of the unit memory of the payment machine is sent, and the management device receives this data and updates the data of the payment machine in the payment machine file. However, since the card number of the transmitted data is data that is not used by the management device, it is not registered in the file even if it is transmitted.

On the other hand, the 'unit recovery data' packet includes all the data in the payment machine file of the management device 1400, the date, identification code, and hot code read from the setting value file in the configuration of the data area of the unit memory 550. I'll match it and send it to you.

However, for the received data packet head and hot code that overlap with the transmitted data area of the unit memory, duplicate transmission is omitted and the unit controller 390 side copies the received data area from the transmitted data area. The data indicated by *6 in the received data is written in the received data area of the unit memory 500. the above"
The response packet to the "unit recovery data" packet is configured to include all data in the transmission data area and send it.

Note that the packets shown in FIGS. 55 to 70 are as follows:
It is not the entire packet that is originally carried on the network, but only the main part, and in addition to the above packet, there is a header section that includes an alert burst to discover the beginning of the data, synchronization data, a source address field that indicates the transmission source, etc. , a count section that indicates the length of data, 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.

Further, the part "PADDING" added to the end of each packet in FIGS. 56 to 61 is a dummy data field added to adjust the length of the packet data to a predetermined length.

Next, FIGS. 71 and 72 show the control procedure of the data transmission controller 535 in the NAU 530, which is located between the two networks 510 and 520 and acts as an intermediary for data transmission, and the procedure of low-layer network abnormality detection processing using a timer interrupt. Explain using.

When the NAU 530 is powered on and a reset pulse is supplied, the data transmission controller 535 starts the initialization process shown in FIG. 71.

Then, first, the N
AU number setter 544. Pachinko machine or payment machine minimum machine number setting device 545, pachinko machine or payment machine connection number setting device 546, issuing machine minimum number setting device 547, issuing machine connection number setting device 548, and NAU type setting device 54
9 is read (steps 81 to S6). Then, based on the machine number and number read in step S1, the machine number, address (unit number), serial number and The channel number is calculated by the method described above (step S7).

After that, initial value data is given to the network controllers 533 and 537 to initialize them (step S8).
), write the machine number, serial number, and channel number calculated in step S7 above to the monitor table (regular data storage area) in the data memory 536, and write the NAU
The type of each unit (pachinko machine, issuing machine) is determined and written from the setting value of the type setting device, and other operating data is cleared to "O" (step S9).

Then, write the NAU number, type name of each unit, unit number 1 serial number, and channel number to the unit table (transmission address storage area) in the data memory 536, and write the NAU status and each bit of monitor information 1 in the unit table. It is cleared to "0" (step 510).

Next, the data transmission controller 535 waits for a packet to be sent from the mask control device f401 of the management device (step 5ll), and when the packet is received, the data transmission controller 535 determines whether the packet is a "parameter line test" or "unit table request". (Step S12, 513).

When it is determined that the received packet is a "unit table request", steps S13 to 814
After moving to step Sll and transmitting an "ACK" packet containing the unit table data read from the data memory 536 to the management device, setting a 1-second timer for timer interrupt and starting the timer interrupt, step Sll The process returns to wait for reception of the next packet (step 515).

On the other hand, if the received packet is a "line test", the process moves from step S12 to step S821, where an "ACK" packet is first sent to the management device, and then the set value of the machine number setter 546, 548 is changed. , the number of units connected to the NAU is set in a counter or the like (step S21, 522).

Next, a "line test" packet is sent to each unit under its control using the address calculated in step S7, and a timer is set (steps S23 and 524).
. Then, the timer is checked, and if an "ACK" packet is returned from each unit within a predetermined period of time, the token bus error bit B6 of monitor information 1 regarding the corresponding unit in the monitor table is cleared to rQJ (step 525). ~527).Also, within a predetermined time “
ACK" packet is not returned, the token bus abnormality bit B6 of the monitor information I is set to "1" (step 528). Then, the above step S22
After subtracting (-■) the counter set in
By determining whether the "line test" packet has been sent to all units, the process returns to step S23 and sends the packet to the next unit, and ends for all units. If so, the process returns to step s11 and waits for reception of a "unit table request" packet.

Furthermore, if the received packet in step Sll is neither a "line test" nor a per unit table request, it is determined in step 516 whether or not it is a registered packet other than the above, and if YES, the received packet is After executing the corresponding processing, the process returns to step Sll and waits for reception of the next packet (step 517).

Note that the NAU processing corresponding to each received packet may be a simple intermediary process (removal or addition of a packet head) for data transmission between the management device and the unit, or an auxiliary process of transmitting command packets to each unit on behalf of the management device. Since these will gradually become clear in the following explanation of the flow of the entire system, their explanation will be omitted here.

On the other hand, when an interrupt signal is received every ↓ seconds from the interrupt timer set in step S15 above, the data transmission controller 535 of the NAU starts the low-layer network abnormality detection process shown in FIG. 72, and first performs step S3. S5
After setting the number of connected units read in in the counter, it is determined whether regular data has been received from each unit within the past 3 seconds (steps s31, 532). If the reception is received, the process jumps to step S34, and if the reception is not received, the token bus abnormality 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 "1" in step S33.
”, and then the process moves to step S33. and,
The counter set in step S31 is subtracted and rQ
By determining whether the check has reached J or not, it is determined whether the check for all units has been completed, and if the check has not been completed, the process returns to step S32 and the above procedure is repeated. by this,
It is possible to detect a communication abnormality in a low-layer network and to embody it in the monitor information 1.

Next, the operation of the pachinko gaming system that conducts business while transmitting data between the management device and each terminal using each packet shown in Table 31 will be explained.

FIG. 73 shows the flow of procedures for initializing each terminal and testing the network line by the management device 400.

When the system is powered on, the management device 400
First, the central processing unit CPU clears all files FLI to FL6 in the main memory M-MEM, and then creates a file (framework) (step 52501). On the other hand, the local processing device 413 first starts with the CRT display device 411.
After displaying the initial screen above, the date and time are notified to the central processing unit (steps 51501, 51502). Then,
The central processing unit determines whether there is a power outage file or not, and if there is no power outage file, it reads the initial setting values such as the number of terminals, the number of winning balls, and the number of batted balls from the hard disk (auxiliary storage device II) setting value file and stores them in the main memory. Initialize each file and generate random numbers for calculating the card number from the card issuing serial number (steps 52502 to 525o4)
. Meanwhile, when a line test request command is sent from the local processing device, the NA in the transmission address file is
Start the line test using the U address (step 5)
1503, 52505), that is, sends a "line test" packet to each NAU 530 using the high-level network 520. At this time.

The local processing device displays the message "Line test in progress" on the CRT display 411 and then waits for a response with the line test result (step 51504).

The "line test" packet is transmitted with the date and identification code (store number) added to the packet head.

On the other hand, when the power is turned on, NAU530 first
Reads the setting values (NAU number, minimum number, number of terminals, etc.) from the AU number setters 544 to 549, calculates the network transmission address of each terminal, creates a unit table, and sets each unit (terminal) and NAU itself. In addition to recognizing the transmission address of each unit, the monitor table containing the operation data of each unit is cleared (step 5350).
1-53504). Then, upon receiving the "line test" packet from the management device, the NAU enters the transmission address it calculated itself in the unit table." A CK
”Return packet (steps 53505.53506)
. The address calculated by the NAU based on the setting value read from the setting device is sent to the management device 114 in step 52503.
00 is the N loaded from the data in the setting value file FLI.
It should match the AU address. Mutual communication becomes possible because each party recognizes the same address.

Also, the “ACK” packet from NAU 530 is managed by the device! 400 receives the corresponding NA
It can be recognized that there is no line abnormality between U and U.
NA the above procedure (steps 52505-52506)
By repeating the check for the number of U, all lines are checked, and then the process moves to unit table request processing (FIG. 74).

On the other hand, the unit control device of each terminal! ! 180,280
．． 350, when the power is turned on, the data transmission controller 551 in the unit first transfers the data to the unit memory 550.
After clearing all data areas, the data is written to a predetermined location r27FFJ in the unit memory (steps 54501, 54502). Then, a predetermined terminal INT of the unit memory rises to a high level. After the power is turned on, the unit controllers 19o, 29o, and 390 of each terminal initialize the internal memory, registers, and ■/○ ports, and send the initialization signal I from the unit memory.
When the rising edge of NT is detected, the setting Wi (
machine number), calculate the lower order of the serial number and channel number, and then write it to the transmission data area of the unit memory (steps 85501 to .55504).
．． ), the data transmission controller 551 reads it, thereby recognizing the unit address on the unit side (step 54503). This enables data transmission between the NAU 530 and each terminal using the token bus.

After that, the NAU 530 sends a "line test" packet to each unit (terminal) with the data (date and identification code) already received from the management device 400 added, and the data transmission controller 551 on the unit side receives it. When received, it writes the received date and identification code into the unit memory, and then transmits an "ACK" packet to the NAU 530 (steps 54504 and 54505). The unit controller records the date and time via the unit memory.
l! When receiving another code, it waits to receive the initial value (steps 55505, 55506). Furthermore, when the NAU receives "ACK" from the data transmission controller 551, it transmits the next unit 8 "' line test" and repeats this for all units to complete the line test of the low layer network 510 and update the unit table. A request is awaited (steps 53507 to 53509).

FIG. 74 shows the unit table request and subsequent line test processing procedure.

When the above-mentioned initialization process is completed, the management bag W400 starts the unit table request process, and the central processing bag! lC
The PU transmits a "unit table request" packet to each NAU 530 (step 52511). Then, NAU 530 receives the packet and sends PACKE
Next to the head section where "ACK" (=08H) is entered in T$TYPEIm, the NAU number, NAU status (consisting of bits indicating token bus error, opening code received, NAU normal, etc.) and the unit table mentioned above are displayed. Data (unit number and type flag for each unit, unit number, serial number, channel number and monitor information 1
) is added for the number of units and transmits an "ACK" packet (steps 53511 and 53512).

When the central processing unit CPU receives this unit table, it compares it with the addresses in the transmission address file FLZ, adds any unregistered ones, saves the transmission address file on the hard disk, and then sends it from each terminal. It examines the received monitor information 1, sends the line test results to the local processing device, and waits for a command (steps S2512 to S52514).

When the local processing bag M413 receives the line test result and there is no abnormal terminal, it immediately sends an initial value setting command to the central processing unit. On the other hand, if there is an abnormal terminal, the abnormal terminal is displayed on the screen of the CRT display device 411, waits for the store opening switch on the console to be turned on, and when a store opening request is received, an initial value setting command is issued. to the central processing unit (steps 51511-31513
).

When receiving the initial value setting command, the central processing bag! lCP
U reads the initial value of each unit from the setting value file FLI of the main storage device M-MEM and stores the initial value (
Pachinko machines send an ``initial value setting'' packet containing initial values such as date, identification code, purchased ball exchange rate, number of main prize balls, number of sub prize balls, number of hits, stop mode, etc., and hot code). (Steps 52515, 52516).

Then, the NAU 530 receives the packet, removes the head unit for the high-level network, and sends the ``Parameter initial value setting'' packet to each unit via the low-level network, and also sends a hard ACK () from the network controller of each unit. When receiving the response signal (response signal), it transmits an "ACK" packet to the management device (step 535).
13-S35 Engineering 5). When the central processing unit 1 ICPU confirms the reception of "ACK" from all the units, it transmits an initial value transmission end to the local processing unit 413 and waits for the store opening request command to be sent (step 5251).
7.52518). The local processing device that receives the completion of initial value transmission displays a store opening request message on the screen of the CRT display device and then waits for the store opening switch to be turned on (steps 51514 and 51515).

On the other hand, on the low-layer network 510 side, when the designated unit receives the packet sent from the NAU 530, it writes an initial value setting command to the command register CR2 in the unit memory (1,70°270.370), Write the received initial value to the receive data area (
Step 54511) Then, the unit controller 190゜290.390 reads the command in the unit memory, and after confirming reception of the initial value, copies the packet head part of the receive data area to the transmit data area and sets the transmit head. At the same time, the hot code is also copied from the reception area to the transmission area, and after changing the initial value unset bit of monitor information 1 to "O" (set), when there is an initial value request from the card reader. Returns the function containing the initial value (step 55511~
55514). On the other hand, the data transmission controller 55 indicates that the initial value unset bit of monitor information 1 has been set to "O".
1 sets a fixed timer and starts transmitting fixed data (step 54512).

FIG. 75 shows a procedure for periodically collecting operating data from each terminal after initial value setting.

When the transmission controller 551 in the unit control device 180, 280° 350 of each terminal confirms the fixed time, for example every second, by an interrupt from its own timer, the transmission data area in the unit memory 170° 270, 370 The operating data written in the SDA is read out, put into a "regular data transmission" packet, placed on the low layer network 510, and sent to the NAU 530 (steps 54521 to 54523). When the NAU 530 receives regular data from each unit, it checks the write flag to see if the monitor table that stores the operating data for each unit, which is formed in its own memory, is in a writable state, and if the flag is After waiting until it becomes "0", the unit table is updated with the received regular data (steps 53521 to 53523). Management device 4
This is to prevent data from being rewritten during regular data transmission to 00. Note that the regular data collected by the NAU 530 is transmitted to the unit controller 1 of each terminal.
90, 290, and 390 absorb operating data of the terminal device in real time and transfer them to the unit memories 170 and 27 one after another.
It is designed to be written within 0,370. Furthermore, if regular data cannot be collected three times in a row, the token bus abnormality bit of monitor information 1 is set to ``1'' (step S3528).

On the other hand, on the management device 400 side as well, the central processing unit CPU checks the scheduled time every second by an interrupt from its own timer, starts scheduled data request processing, and
530 (S2521, 52522). Specified NAU530
When it received the packet, it set the write flag and then put the data in the monitor table.” A CK
”Send the packet and reset the write flag (steps 53524 to 53527).
When 0 is received, the monitor information is checked, and if there is an abnormal terminal, it is notified to the local processing unit and the unit abnormality is displayed on the screen of the CRT display device.
The operating data in each unit file is rewritten with regular data (steps 52523 to S2525).

FIG. 76 shows the flow of store opening processing after initial values are set for each terminal by the management device 400.

When the opening switch 421 on the console 412 of the management device 400 is turned on after the preparation process such as the line test and initial value setting is completed, the local processing device 413 transmits a store opening request command to the central processing unit CPU. Then, the central processing unit forms a "store opening code" packet and sends it to each NAU 530 (steps 51531, 5
253 construction). When the NAU 530 receives the packet, it sends an "ACK" packet to the management device, removes the head for the higher layer network from the received packet, and sends an "opening code" packet to each unit via the lower layer network. (Steps 53531-53)
533).

The management device 400 receives information from all NAUs 530.
CK", changes the mode to business, shifts to normal business processing, and returns a response to the local processing device (
Step 52532). Then.

The local processing device is displayed on a CRT display! A normal display is performed on the screen of 41↓, which displays a message that the company is open for business, and the names and operating methods of switches on the console that can be operated (step 51532).

On the other hand, when the data transmission controller 551 of each terminal receives the "opening code" packet transmitted from the NAU 530, each unit control bag [180, 280, 350]
The "opening code" is written to the command register CR2 of the unit memory 170゜270.370 in the card reader control device 188, 288, 288, 288, 390 reads this code.
388, permits card acceptance and issuance, sets the bill validator 210 of the cart issuing machine to a state where bill acceptance is enabled, and displays 161, 221, 3 on the outside of each terminal.
41 is turned on to inform the player that the terminal is in operation (step 5453).
1-54533° step 55531-35533).

FIG. 77 shows the procedure of card issuing processing by the card issuing machine 200.

The unit controller 290 of the card issuing machine 200 is
Once the initialization is processed, the issuance reservation process starts even before the purchased banknotes are actually inserted into the issuing machine, and the amount is
A "card purchase" packet transmission request command of "0" is written to the command register CRI of the unit memory 550, and the issuance acceptance number in the transmission data area is updated (step 55541). Then, the data transmission controller 551 gives an issuance acceptance number to each issuing machine as a number indicating the order of acceptance. Forms a “Card Purchase” packet (=0) for card purchase reservation, and
It is transmitted to U530 (step 54541). When the NAU receives this packet, it adds a high-layer packet head and sends it to the management device (step 53541). Then, the central processing bag [CPU checks whether the card number in the packet is "0" or not, and then reads the number of issuances from the file of the issuing machine that sent the packet and compares it with the issuance acceptance number to confirm the reservation. If it is determined that it is a purchase packet for
Calculates the issuing serial number and card number, creates a card file, and then sends an "ACK" packet containing the card number to NAU (steps S'2541 to 82544)
). The issue serial number is the sum of the number of issues issued by all issuing machines.

Upon receiving the "ACK", the NAU removes the high-level packet head from the packet and transmits it to the unit controller 1!280 of the issuer (step 53542). When the data transmission controller 551 in the unit control device receives the "ACK", it notifies the unit controller 290 of this via the unit memory (
Step 54542). Then, the unit controller sends a "card issue" function containing the card number to the card issuing device 700. In response to this, the cart issuing device takes out one card from the card tank, supplies it to the card reader 800, records the card number in the magnetic recording section, and waits (step 55542).

After that, when a banknote is actually inserted into the banknote insertion slot 211 of the issuing machine 200, the banknote validator 210 identifies this, notifies the unit controller 290, and lights up the lamp in the purchase selection switch 212 to prompt selection. At the same time, the input amount is displayed on the amount display 2 and 3. Then, when one of the purchase selection switches 21-2 is turned on and the purchase amount is specified, the unit controller 290
confirms the amount and writes the "Card Purchase" command in the command register CR] in the unit memo 1, 1550, and the purchase amount of the card in the transmission data area (step 55543).

Next, the data transmission controller 551 reads this and forms a "card purchase" packet, which contains the purchase amount and reserved card number and sends it to the NAU 530.
The AU 530 attaches a high-rise network head to this and transmits it to the management device 400 (steps 54543, 53
543). When the management device 400 receives this "Card Purchase" packet, it checks the card number, purchase amount, and issued serial number in the packet, and if it determines that the card is an actual purchase, the amount is stored in the card file searched using the issued serial number. After writing "ACK+?" packet, it transmits (steps 52545 to 52547).

This "ACK" packet is once received by the NAU 530, the head for the high-level network is removed, and sent to the low-level network 510, where it is sent to the designated issuing device 200.
is received by the data transmission controller 551 of (
Step 53544. ．． 54544). Then, the transmission controller 551 connects the AC via the unit memory 550.
The reception of K is notified to the unit controller 290. After that, the unit controller operates the card issuing device ff1.
The issuing function containing the purchase amount is sent to 700 (step 55544). Then, the purchase amount is printed on the waiting card and the card is ejected. At this time, if there is change, the unit controller 290 gives a change payout command to the balance payout device 230, turns off the lamps L■ to L5 in the purchase selection switch, and displays the amount display 2.
13 is cleared to "O", and monetary data such as the deposited amount in the transmission data area is updated (steps 55545-.55546).

As mentioned above, when issuing a card, a reservation is made in advance for issuing a card, the card number is recorded and the card is placed on standby, and when bills are actually inserted, only the purchase amount is printed and ejected. The waiting time can be significantly reduced.

FIG. 78 shows the procedure from when the card CD is inserted into the pachinko machine OO to start the game until the game actually starts.

When a card CD is inserted from the outside into the card insertion/ejection slot 802a of the control unit 180 on the top of the pachinko machine, the card reader 800 reads the information recorded on the punched hole and the magnetic surface of the card and indicates whether the payment has been completed or the card has been returned to zero. Cards are excluded, and for other cards, the date and identification code (
If the date or code does not match, the card will be ejected, and if they match, the card number will be transferred to the unit controller 190.The unit controller 190 will receive the card number and send it to the unit. Command register CRI in memory 550
Write a command to indicate that the card has been inserted into the area, and write the card number into the sending data area to select “Card In”.
A packet transmission request is made (step 55551).

The data transmission controller 551 has a "card in" code in its head section, and sends a packet containing the card number in the data section to the NAU 530 via the low-layer network. is prefixed and sent to the management device 1400 (steps 54551, 53551).

When the management device 400 receives the card number from the NAU 530, it calculates the issued serial number n from the card number and reads the data of the corresponding card from the card file FL3 in the main storage device 1M-MEM (steps 52551 to 52551).
52553). Then, if the card number in the file and the received card number are checked and the card numbers do not match, or if the card status in the card file is checked and it is determined that it is not appropriate to start the game ( In the case of a cleared card, etc.), it is a response refusal signal.”
N A K” packet (step 5255)
4-52556). Then, the NAU 530 receives the packet, removes the head section for the high-level network, and sends it to the low-level network 510, and the data transmission controller 551 of the designated unit receives the "NAK" and executes the command in the unit memory 550. A command indicating that the response has been rejected is written in register CR2 (steps 53552, 54552). The unit controller 190 reads this, confirms the response refusal, and ejects the card from the card reader 800 (step 5555).
2).

On the other hand, when the central processing unit confirms that the card is valid, the card file FLI and the P machine file FL are
2 (Table 242 Table 26) is updated.

In other words, update the card status from "free status" to "playing", write the machine number and card number of the terminal (pachinko machine) where the card is located in the corresponding table, and then update the card text (amount, amount held). number of balls, etc.) and transmits an "ACK" packet as a response signal (steps 52557, 52558).

When the designated NAU 530 receives this packet,
When the head section for the high-level network is removed and sent to the low-level network 510, and the data transmission controller 551 of the designated unit receives this, a command "card in" is entered in the command register CR2 in the unit memory 550, and the command is received. Enter card text in the data area (steps 53553-54553).

When the unit controller 190 reads the command in the unit memory 550 and confirms that there is a response, it starts the game control while keeping the card in the card reader 800 and transfers the data to the transmission data area SDA of the unit memory 550. In addition to changing the operation information in "Playing", the number of balls held by the card and the amount are displayed on the number of balls display 112 and the amount display 111, and if the amount is not zero, the purchase possible display lamp 121 is displayed. Turn it on to display the purchase availability status (steps 55553 and 55554)
.

FIG. 79 shows the interruption switch of the pachinko machine 100 during play]
14 is turned on.

When the interrupt switch 115 is pressed, the unit controller 190 stops the game control and then stores the unit memory 5.
The card status of the card text contained in the transmission data area No. 50 is changed to "suspended", and a command "suspension switch on" is written in the command register CRI of the shared data area (step 55561). Then, the data transmission controller 551 reads this, forms a "Paper Interrupt Switch" packet, puts the card text in the data part, and sends it to the NAU 530 (step 54561). is prefixed and sent to the management device 400 (step 83.561).

Management bag! When 400 receives it, it calculates the issued serial number n from the card number in the card text, reads the card file FL1 in the main storage iM-MEM, and matches the location number in the file with the number in the packet. However, if the machine numbers do not match, or if the card status in the file is not playing or suspended, a NAK is transmitted (steps 52561 to 52566). On the other hand, if the machine numbers match and the card status is in the game, update the data of the corresponding card and then send "ACK" as a response signal.
"The NAU 530 sends the packet with the card text (steps 52567 and 52568).
When it receives "K" or "ACK", it removes the high-layer network head and sends it out onto the low-layer network 510 (
Step 53562.53563).

Then, the data transmission controller 551 of the unit control device 180 as the transmission destination receives this "N A K" or "A
CK” packet and inputs NAK or ACK into the command register CR2 in the unit memory 550.
In the case of CK, the card text is further written in the received data area (steps 54562, 5456'3). When the unit controller 190 confirms the NAK reception, it returns the card state to the original "playing" state and restarts the game control (step 55562). When the reception of ACK is confirmed, after ejecting the card from the card reader 800, the operation information in the transmission data area SDA of the unit memory is changed to "suspended", and the purchase information set in the pachinko machine 100 is changed. The lamp 121 built in the switch 113 is turned off, and the display status of the game status display lamp 123 etc. is changed to an interrupted display (flashing) (steps 55563 and 55).
564).

Next, as shown in FIG.
The processing procedure when D is inserted is shown.

The procedure in this case is almost the same as the procedure in the case of card-in shown in FIG. That is, the processing steps 55571 to 52571 that notify that a card has been inserted from the pachinko machine to the management device 1400 correspond to the processing steps 55551 to 52551 in FIG.
~55573 is.

The processing steps 52552 to 55553 in FIG. 78 and the transmission processing steps 52572 to 55572 of "NAK" which is a negative response are the processing steps 52 in FIG.
552 to 85552, respectively.

The difference is that a "suspended card-in" packet is used instead of a "card-in" packet as a transmission packet, and if the card number is different from the one before the interruption when the card is inserted, the card reader 800 immediately sends the card and that the P machine file FL2 is not updated on the management device 400 side. This is because the P machine file has already been updated when the interrupt switch was turned on. Note that the card file FLI updates the card status from "suspended" to "playing".

Further, the display state of the game state display lamp 123 is changed to a game in progress display (lit).

FIG. 81 shows the procedure of the game end process 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. 79.

That is, when the end switch 115 provided at the bottom of the pachinko machine 100 is pressed, the unit controller 1
90 detects this and rewrites the card status of the card text in the unit memory 550 from "playing" to "free".

A command indicating that the end switch has been turned on is written into the command register CR1 in the unit memory 550 (step 55581). The data transmission controller 551 then reads this, inserts the card text, forms a 'termination switch' packet, and sends it to the NAU 530 via the lower layer network 510 (step 54581). If you take it.

Management device 4 with a head for high-rise network attached to the head
00 (step 83581). Thereafter, the unit control device 180 receives the '
CK” is returned (steps 52581-S258
8), the card is ejected from the card reader 800 (step 55583), and the operation information regarding the pachinko machine in the unit memory 550 is changed to "free state (customer waiting state)". Further, the displays on the number of balls display unit 11 and the amount display unit 112 are cleared to "0", and the lamp 121 indicating that purchase is possible and the status display lamp 123 in the purchase switch are turned off.

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

When the unit controller 190 of the pachinko machine detects the occurrence of a return to zero, it stops firing the ball.

The card status in the unit memory 550 is changed to "return to zero" and a return to zero generation command is written to the command register CR (step 55591). Then, the data transmission controller 551 forms a "return to zero" packet, contains the card text in the transmission data area of the unit memory, and transmits it to the NAU 53Q (step 54591). NA
When the U530 receives this ``return to zero'' packet, it adds a high-level packet head and sends it to the management device 400 (step 53591).When the management device receives the ``return to zero'' packet, it issues an issue from the card number in the packet. The serial number is counted backwards and the issued serial number is used to store the main memory M-M.
Read the file for the card in question from the file in EM, check the card status and location terminal number, and if the cart status is not "playing" or the machine number does not match, NAK.
(Steps 52591 to 52595).

On the other hand, if the card status is correct and the machine numbers match, update the number of balls, amount, card status (playing → return to zero), location terminal machine number in the card file, and write the card history data. Send ACK (step 5259
6-52598).

Upon receiving the ACK, the NAU 530 removes the high-layer packet head and sends it to the designated unit (step 53).
593) When the data transmission controller 551 of the unit receives the "ACK" packet, it writes the ACK reception command into the command register CR2 of the unit memory 550 and the card text into the reception data area (step 84593). Then, the unit controller 190 confirms the ACK reception and sends the card reader 800
After instructing the player to drill the return hole and eject the card, the operation information in the transmission data area SDA is changed to "free", and the number of balls held and the amount displayed on the amount display are set to zero, The status display of the purchase lamp 121, the game status display lamp 123, and the analog display L63 is changed to a display indicating "free" (steps 55593, 55594).

FIG. 83 shows that during the game, the unit controller 190
The processing procedure will be described when it is determined that the number of prize balls ejected, etc. reaches the number of hits according to the initially set stopping mode, and the game is in a stopping state. The processing in this case is almost the same as the zero return processing procedure shown in FIG.

In other words, even though the processing factor (stopping) occurred on the pachinko machine 100 side, the management device! ! Processing steps 55601 to 52601 for notifying the management device 400 correspond to processing steps 55591 to 52591 in FIG. Corresponds to ~52598. The difference is that when the unit controller 190 determines that termination has occurred, “
Enter the command "Stop" and change the card status to "Stop" (step 55601), and enter the command "Stop" for sending.
Using packets (step 84601) and AC
After confirming K, set the operation information in the transmission data area SDA of the unit memory to "discontinued" instead of "free", turn off the purchase ready lamp 121, clear the discontinued number and amount display to zero, and display the status. The point is that the lamp 123 and the analog display 163 are displayed as a stop indication (blinking).

In addition, the card reader 800 disables the acceptance of the next card after the card is ejected, and the management device updates the card file and changes the operation information in the pachinko machine file to "discontinued" (step 52606).
The RT display device 411 displays the interrupt message of the stop table, and the printer 408 prints the stop information (step 52608). Also, card file FL
Similar to the update of I, the fact that the status of the pachinko machine has changed to "discontinued" is registered in the P machine file FL2 (step 52
607).

FIG. 84 shows the procedure of card payment processing in the payment machine 300. When a cart CD is inserted into the card reader 800 of the payment machine 300, the information recorded on the magnetic surface of the card is read to confirm the year, month, date and identification code, and if they match, the card number is sent to the unit controller 390. Forward. The unit controller 390 writes “card payment” to the command register CRI in the unit memory 550.
A message is written and the card number is written in the transmission data area (step 55611). Then, the data transmission controller 551 reads it, forms a "card payment request" packet, includes the card number, and transmits it on the lower layer network 510 (step 54611).
). Then, the NAU 530 receives it, attaches a high-level network head to the head of the packet, and sends it to the management device 400.
(Step 33611). When the management device 400 receives the packet, it calculates the issuing serial number (n) from the card number and uses the card file FL based on it.
I, read the corresponding card text (card information), and check the card status (step 5261
1-3261.4). Here, if the card status is not appropriate, for example, if the payment has already been made or if the card has returned to zero (both the balance and the amount are zero), the payment will be refused.
N A K " packet is formed and transmitted (step 82615). Then, the NAU 530 receives it, removes the high-level network head, and sends it to the requesting payment machine 3.
00 unit controller 350 (step 5
3612). Then, the data transmission controller 551 receives it and writes "response refusal" to the command register CR2 in the unit memory 550, which is read and confirmed by the unit controller 390, and the card is ejected from the card reader 800 (step 54612
, 55612).

On the other hand, the management device 11400 performs the above processing step 5261.
In step 4, if it is determined that the card status is appropriate, an "ACK" packet is generated as a response signal, and the payment data (number of balls held and unused amount) read from the card file, card history, and payment acceptance are sent to the packet. The NAU 530 removes the high-level network head from the packet and transmits it to the unit controller 350 (steps 52616, 53613). Then, the data transmission controller 551 receives it and sends an ACK to the command register CR2 in the unit memory 550.
In addition, the received data such as settlement data is written in the reception data area RDA (step 54613), and the unit controller 390 reads it and confirms that there is an affirmative response, and displays the number of balls (obtained balls) on the number of balls display 303. In addition to displaying the unused amount on the amount display 304, the printer 330 issues a receipt (prize voucher) with details such as payment data printed on it, and if there is unused money, it displays the unused amount on the amount display 304. The unused balance is discharged from the dispenser 321 and the coin dispenser 325 (steps 55614 to 55616).

After that, the unit controller 390 reads the card reader 8
A punch hole is punched in the card held in 00 to eject it as a cleared card, and a command indicating "settlement completed" is sent to the command register CRI of the unit memory 550.
In addition, the card text is written in the transmission data area (step 55617), and the data transmission controller 551 reads this, forms a ``Payment Completed'' packet, and transmits it, and the NAU 530 places a high-rise network head at the beginning of the packet. and sends it to the management device 400 (steps 54614, 83614).

The management bag [400] that receives the "payment completion" packet calculates the issuing serial number n again from the card number in the packet, searches the card file FLI based on it, reads the card data, and checks the card status. When the card status is "suspended", execute the suspension termination process of the pachinko machine 100 shown in FIG. 85, change the card status to "paid", and update the cart history."
ACK” packet to the NAU 530 (steps 52618-32621).

When the NAU receives "ACK", it removes the high-rise packet head and sends it to the unit controller 350 of the payment machine. When the transmission controller 551 receives this, it notifies the unit controller 390 via the unit memory 550, and the unit controller "ACK""When reception is confirmed, the next cart can be accepted (steps 53615 to s56e8).

As mentioned above, payment data is sent from the management bag ff1400 in response to a card payment request from the payment machine 300, and when the payment is completed, the management device is again notified of the completion of payment, and the payment is processed for the first time at that point. Since we handle goods, even if an accident such as a power outage occurs during the payment process at the payment machine 3OO, the payment data will be saved in the card file F.
It is maintained during LI, and payment processing can be continued quickly after a power outage. Thereby, there is no risk of any disadvantage to the players, and the reliability of the system is improved. Moreover, in the above embodiment, history data is also printed on the payment receipt (prize exchange ticket), so the credibility of the printed payment data (number of balls held) is increased, increasing confidence in the system. You will be able to do it.

FIG. 85 shows an interruption cancellation processing procedure accompanying the above-described card payment processing.

That is, in the system of this embodiment, the game is interrupted by the above-mentioned interruption process (see FIG. 79), and the interrupted pachinko machine 100 that is refusing to accept other carts is released from the interruption machine. When the card is inserted into the payment machine 300 and the payment process is performed, the interruption is canceled by a command from the management device 400.

The suspended card is inserted into the payment machine, and the payment process (
(see Figure 84) is executed, and the management device! 40
0 is confirmed, a "suspension end" packet is sent to the corresponding pachinko machine 100 that is currently suspended based on the card information (step 82622). This packet is once N
It is received by the AU 530, and after the high-rise network head is removed, it is transmitted to the unit control device 1f 180 of the corresponding pachinko machine 100 (step 53
621). This packet is sent to the data transmission controller 55.
1, a command "end of interruption" is written to the command register CR2 in the unit memory 550, and when the unit controller 190 reads and confirms this, the card reader 800 is enabled to accept the card, and the unit Change the operating information regarding the pachinko machine in the memory 550 from "suspended" to "free state"
(Steps 54621, 85621.556
22). In addition, the displays on the number of balls display 111 and amount display 112 on the front of the pachinko machine are cleared to rQJ, the lamp 168 indicating whether or not a card can be inserted is blinked, and the display on the analog display 163 is set to a customer waiting state (scrolling).
(Steps 55623 to 55625).

On the other hand, after the NAU 530 transmits the "suspension end" packet from the management device 400 to the unit control device 180,
When receiving a hard ACK from the network controller, it transmits an "ACK" packet as a response signal to the management device 400, and when the management device 400 receives this,
Change the operation information in the P machine file FL2 from "suspended" to "free state" (steps 83622 to 5262
4).

FIG. 86 shows a procedure for cancellation cancellation processing based on a cancellation cancellation command from the console 412 of the management device 400.

When the cancellation release switch 433 on the console 412 is turned on, the local processing unit 413 is activated by the central processing unit CPU.
Send a stop table data request command to (step 5163
1). Then, the central processing unit searches the P machine file FLI and sends the machine number of the pachinko machine that is discontinued, and the local processing unit displays a list of discontinued pachinko machines on the screen of the CRT display 411 (step 52631). , 52632°51632). While viewing this, the operator inputs the machine number of the pachinko machine he wishes to cancel using the numeric keypad 425 on the console 412, and the local processing device sends a cancellation cancellation command to the central processing unit (step 51).
633). Then, the central processing unit CPU receives the command, determines whether or not all units are specified, and sends a "'" packet to the communication control unit SCC of the management unit containing the serial number and channel number along with the unit number. is sent to all pachinko machines or to a designated pachinko machine (step 32633).

When the designated NA U330 receives the packet, it removes the head part for the high-level network and sends it onto the low-level network 510, and the data transmission controller 551 of the unit control device E180 that received the packet A "cancel cancellation" command is written to command register CR2 in 550 (steps 52634, 53631, 54631). When the unit controller 190 of the pachinko machine reads this and confirms that the cancellation cancellation command has been entered, it changes the pachinko machine operating information in the transmission data area of the unit memory to "free".

After clearing the stop operation register in the transmission data area to zero, and changing the analog display 163 and card insertion lamp 168 to the customer waiting display, the cart reader 80
0, a command is given to permit card acceptance (steps 55631 to 55634).

On the other hand, the NAU 530 that has received the ``PAT cancellation release'' packet receives a hard ACK from the network controller of the unit control device 180 and sends a response packet ``A''.
CK" to the management bag W400. Step 53
632, 53633), when the management device receives this,
After changing the operation information in the P machine file FL2 to "free state" and notifying the result to the local processing device (steps 52635 to 52637), the local processing device 413 changes the end of the stop table data on the CRT display screen. The status display is changed from "stopped" indicating "stopped" to "empty" indicating "free" (step 51634).

FIG. 87 shows a processing procedure when the terminal is forcibly terminated from the management device 1400 side.

Business operations at game parlors end when they close, but conventionally, notices of the closure of the business have been made through in-store announcements and staff. However, there are players who purchase balls just before the end of the game, and players who are using the pachinko machine 100 that is in good condition to play the balls are reluctant to stop playing, making it difficult to end the game on time. there were.

In the system of this embodiment, operation can be stopped for each type of terminal by operating the force termination switch 434 on the console 412 and selecting the type. By stopping the issuance of cards by the issuing machine 200, stopping the operation of all pachinko machines at the closing time of the business, and stopping the operation of the payment machine 300 after the last player has finished paying, the business ends smoothly. can be done.

In this case, when the forced termination switch 434 is turned on, the local processing device 413 displays a forced termination menu on the screen of the CRT display device 411 (step S l 6
41). When the type of terminal to be terminated is selected using the numeric keypad 425 according to this menu, a display prompting the user to input the forced termination machine number is displayed (step 81642). It is now possible to terminate all terminals at the same time or terminate only one specific terminal for each type (payment machine), and if you enter rQJ or machine number from the console to specify batch termination for each type. , a forced termination command is sent to the central processing unit CPU (step 816
43).

When the central processing unit 1cPU receives this command, it first determines whether or not all machines are specified, and if all machines are specified, it sequentially reads the pachinko machine file FL2, checks the operation information, and indicates whether it is "playing" or "suspended."'', the number of the card being played or suspended is read out and the issuing serial number is calculated backwards (steps 52641 to 52641).
2644). Then, using the issued serial number, the number of balls and the amount in the cart file are rewritten to the data in the pachinko machine file, and the card status is changed to "free" (step 52645). After executing this on all machines, send a "forced termination" packet to the NAU530 (
Step 52646).

When the NAU 530 receives this packet, it removes the high-rise network head and sends a ``forced termination'' packet to all pachinko machines, and when it receives a heart ACK from the network controller, it sends a response signal to the management device 1400. ACK” (step 536).
41,53642). When the management device receives the ACK,
Send the results to the local processing device (step 5264)
7,52648). Then, the local processing device
The status display of the display data on the display screen is changed from "Empty" indicating "Free" to "Strong" indicating the forced termination state (Step 51644).

On the other hand, the unit control bag of each terminal that received the "forced termination" packet from NAU530! 180.280,
At 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 1
When 90 reads this, it first clears the card text in the transmission data area in the unit memory and changes the operation information to forced termination (steps 54641 and 5564).
1). Then, after stopping the detection of the sensor and the firing motor, and turning off all the lamps and stopping the game control,
Commands ejection of the card in the card reader 800 and disables card acceptance from now on (steps 55642, 55)
643).

In addition, in the system of the embodiment, it is possible to enter the machine number of a specific pachinko machine without specifying all machines using the numeric keypad 425 to forcefully terminate the machine. In this case, the central processing unit It is determined that the pachinko machine has failed (specific machine specified), and immediately proceeds to step 52646, where it sends a ``forced termination'' packet to the specified pachinko machine (see broken line).

When the ACK is returned from the NAU 530, the process moves from step 52647 to step 52642, where the relevant pachinko machine file is read for the first time, the operation information is checked, and the card file is read only when the game is in progress or interrupted. Update and step 52645-526
48 and sends the result to the local processing device 413.

FIG. 88 shows the procedure for forcibly terminating the issuing machine or the payment machine.

In this case, when the forced termination switch 434 is turned on, the local processing device 413 displays a forced termination menu on the screen of the CRT display device 411 (step S165).
1). When the type of terminal to be terminated is selected using the numeric keypad 425 according to this menu, a display prompting the input of the forced termination machine number is displayed (step 51652). In this embodiment, it is possible to shut down all terminal machines at the same time for each type of terminal machine (pachinko machine, card issuing machine, payment machine), or to shut down only one specific terminal machine. Here, rQJ specifies batch termination for each type.
Alternatively, when the machine number is input from the console, a forced termination command is sent to the central processing unit CPU (step S
], 653).

When the central processing bag WcPU receives this command, it first determines whether all devices are specified, and if all devices are specified, it is sent to all NAUs, and if a specific terminal is specified, it is sent to the specified issuing machine or payment machine. A "forced termination" packet is sent to (step 52651). And AC from NAU530
When K is received, if all devices are specified, the operation information in the file of the terminal is changed to "forced termination" immediately, or if a specific device is specified, the result is sent to the local processing device (^ 52652, 52653).

On the other hand, the card issuing machine 200 that has received the "forced termination" packet clears the operating focus of the operating information in the unit memory 550 (step 55651) and lights up the issuing stop lamp 222 (S 5652).
.

In addition, if 1 forced termination is for the payment machine 300, when the payment machine receives the packet, it clears the in-operation bit of the operation information in the unit memory, turns on the payment cancellation lamp 342, and causes the cart reader 800 to (steps 55652, 5)
5653).

Furthermore, in the transmission system of this embodiment, the management device 40
There is also a "forced termination release" packet for transmitting a command to cancel the operation stoppage of a terminal that is being forcibly terminated from the 0 side.
There are different types.

FIG. 89 shows a procedure for forced termination cancellation processing common to pachinko machines, issuing machines, and payment machines.

The procedure in this case is almost the same as the procedure for the forced termination process shown in FIG. That is, the management device 4
00 on the console 41 while looking at the CRT display 411.
When the forced termination release switch 435 is turned on from step 2, the local processing device 413 displays a forced termination release menu (step 51661). While looking at this screen, use the numeric keypad to select the type (pachinko machine, issuing machine, or payment machine).
When specified, the central processing bag W is transferred from the local processing device to
A command requesting data of the unit being forcibly terminated is sent to the CPU (step 31662).

Then, the central processing unit searches the files of each unit, finds the unit that is being forcibly terminated, and transmits its data (steps 52661, 52662). The local processing device displays the data on the CRT display device, so if the user inputs the all-device designation (rOJ) or device number using the numeric keypad while looking at the screen, a forced termination cancellation command is sent (steps 51663 and 51664). Then, the central processing unit first determines whether all units are specified, and if all units are specified, it sends a "forced termination cancellation" packet to all NAU530s, and if a specific unit is specified, it sends a "forced termination cancellation" packet to the specified unit. (Steps 52663, 52664). The "forced termination cancellation" 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 (steps 53661, 54661, 53662).
. When the management device receives an ACK, it immediately changes the operating information in the unit file if all machines are specified, or if a specific machine is specified, it changes the operation information in the unit file to ``free'' (pachinko machines) or ``in operation'' (issuing machines, payment machines). (step 52665
, 52666), then jumps to step 52667 and reports the result to the local processing unit (step 3
1665).

On the other hand, on the unit side that received the "'forced termination cancellation" packet, the operation information in the unit memory 550 is set to "free".
Alternatively, after changing the state to "in operation", the status display lamp 123 of the pachinko machine is turned on, the analog display 163 is changed to a customer waiting display, and the card reader 800 is enabled to accept cards (steps 55661 to 55661).
55663). Further, in the card issuing machine 200, the bill validator 210 is enabled to accept purchased bills, and the issuing lamp 241 is turned on. In addition, payment machine 3
At 00, the payment in progress lamp 341 is turned on to enable the card reader 800 to accept the card.

Figure 90 shows what happens when an abnormality occurs, such as when the terminal's power is accidentally cut off, when the unit controller 190, 290, or 390 becomes unable to control the terminal, or when a low-layer network cable is disconnected. The procedure for unit down detection processing is shown.

When a unit goes down, scheduled data is not sent, so if the NAU530 does not receive scheduled data within 3 seconds, it will detect a timeout, determine that the unit is down, and display a token bus error on the monitor information of the unit in the monitor table. Set the bit to “1” (step 53
671, 53672). Thereafter, when the central processing unit CPU of the management device 400 sends a "periodic data request" packet by a timer interrupt (step 52671), it receives it and transmits an "ACK" packet containing the unit table (step 53673).゜53674).

When the central processing unit receives the "ACK", it first checks the monitor information for each unit in the packet, and if there is an abnormality, it prints out the occurrence of the unit abnormality and the details of the abnormality using the printer 408, and also sends a message to the local A command is sent to the display device 413 to interrupt the abnormality of the unit (steps 52672 to 52674).

Then, the local display device 413 displays an interrupt message notifying the unit abnormality at a predetermined position (line 19) on the screen being displayed (step 51671).

On the other hand, after instructing the display of unit abnormality, the central processing unit clears or changes the operation information of the unit file to "free", sets the card status in the card file to "free", and sets the number of balls in the P machine file. , save the amount in the card file, form a unit check packet and send it to NAT, J530 (step 52).
675, 52676). When the NAU 530 receives this packet, it removes the high-rise head and sends a "unit check" packet to each unit (step 5367).
5). If the unit to which the packet was sent is down or a low-layer network error occurs, the hard ACK from the network controller will not return to the NAU 530, so the NAU 530 will respond with "ACK" or "N" depending on the presence or absence of the hard ACK. A K” packet is sent to the management device (step 53676.53
677).

FIG. 91 shows a procedure for unit recovery processing when a unit or a low-layer network whose communication with the NAU 530 is interrupted is recovered.

Step 8267 of the unit down detection process in FIG.
While periodically transmitting the ``Unit Check'' packet in Step 6, the unit is powered on or the low-layer network is connected, and the unit recovers, and in Step 52677, when it confirms that it has received an ACK from the NAU. The central processing unit reads the file of the unit and transmits a ``unit recovery data'' packet containing the operating data of the unit immediately before the failure to the NAU 530 (steps 52681 and 52682).

NAU53 that received the “unit recovery data” packet
0 copies the recovery data in the packet into the monitor table, and then sends the "unit recovery data" packet with the high-rise network packet head removed to the recovered unit (steps 83681, 83682).

Then, the data transmission controller 551 of the unit writes a "unit recovery" command to the command register CR2 in the unit memory 550 and recovery data to the reception data area, and notifies the unit controller 190, 290 or 390 of the reception of the packet (step 5
4681).

When the unit controller confirms the reception of the "unit recovery data" packet, it copies the packet head to the transmission data area, and in the pachinko machine 100, after transmitting the date and identification code to the card reader, the ACK" is sent to the data transmission controller (steps 55681, 55682). The data transmission controller transmits an "ACK" packet to the NAU.

NAU adds a high-level head to the beginning of the packet.
CK" to the management device (step 54682.
53683).

When the central processing unit CPU of the management device 400 receives "ACK", it forms a "restart" packet and sends the NAU
Send to 530 (step 52683.52684
).

This packet is sent from the NAU 530 to the unit controller 190.290 via the data transmission controller 551.
, 390, the unit controller restores the display lamp, number of balls, amount display, etc. to the state before the downtime (steps 33684, 54683, 55).
683). The pachinko machine then sends a "reload" command to the card reader (step 8568).
4). Then, if there is a card inside, the card reader 800 re-reads the magnetic data, etc., and transmits the card number to the unit controller 190. Thereafter, the unit controller performs the same process as in the case of cart-in in Figure 78, transmits the card number, and receives the corresponding card text. When the NAU530 confirms the hard ACK from the unit's network controller, it responds with "A CK".
”Send the packet to the management device (step 5368
5).

Figure 92 shows that when the NAU530 power supply is accidentally cut off or the high-rise network cable is cut,
The procedure for detecting and recovering when the system goes down is shown.

When the NAU 530 goes down, the central processing unit CPU does not return an ACK to the "periodic data request" packet from the management device 400 due to a timer interrupt.
It is detected that U is down, and the local processing unit 413
and an emergency print command to the printer 408 (steps 52691 to 52694).
. Then, the local processing device 413 converts the CRT display device 4
An interrupt message notifying that the NAU is down is displayed at a predetermined position on the screen of the printer 40.
8 prints on paper that the NAU is down.

Thereafter, the central processing unit sends a "line monitor check" packet to the NAU (step 82695). While repeating the above procedure every second due to a timer interrupt, the staff member sees the interrupt display and the emergency printout and presses N.
When the NAU recovers after checking the AU and high-level network, the NAU receives the ``line monitor check 2'' packet and sends the ACK to the management device (steps 53691, 53692). checks the ACK, learns that the NAU has recovered, and sends an interrupt display command to the local processing unit 413 and an emergency print command to the printer 408 (step 5269).
6-52698). Then, the local processing unit 403 displays an interrupt message at a predetermined position on the screen of the CRT display device 41 to inform that the NAU has been recovered, and the printer 408 prints on paper that the NAU has been recovered.

On the other hand, on the unit side, when a transmission cause occurs due to an external action or the like and a transmission request is made to the data transmission controller 551 via the command register CRI of the unit memory 550, the data transmission controller forms a corresponding packet. Transmit to NAU 530 (step 84691). At this time, if the NAU is down, the network controller 553 detects unsuccessful transmission and writes a note to that effect in the packet memory 552.

As a result, the data transmission controller learns that the transmission was unsuccessful (step 34692), returns to step 8469, and repeats transmitting the same packet again. However, when the NAU is not down, the data transmission controller learns of the successful transmission and notifies the unit controllers 190, 290, 390 of the successful transmission via the unit memory 550 (step 54693), but when the NAU is down. In this case, no matter how long the transmission success is not returned, the unit controller detects that the timer set after the transmission request (step 55692) has timed out and learns that the transmission was unsuccessful (step 556).
93). As a result, the unit controller stops outputting the watchdog pulse (step 35694).
. As a result, the external reset circuit W&555 generates a reset signal, and the unit controller and other controllers 551, 553 in the unit control devices 180, 280, 350 are all reset, and control operations are stopped.

Thereafter, when the NAU recovers, the NAU 530 and the central processing unit each detect that the unit is down and execute unit recovery processing (FIGS. 90 and 91). After initialization, the unit receives a ``unit recovery'' packet and returns to the state before going down.

FIG. 93 shows the processing procedure when the closing switch 422 and then the system ending switch 423 are turned on.

When the closing switch 422 on the console 412 is turned on, the local processing device 413 sends a closing request command to the central processing unit CPU (step 51701).

When the central processing unit receives this command, it sequentially reads the P machine files from the main memory, checks whether the operating information is "playing", and if there is no pachinko machine in play, the AC
Send K to the local processing unit and send a "closed" packet to all NAUs (steps 52701 to 5270).
4). When the local processing unit receives the ACK, it waits for the system termination switch 423 to be turned on, and when it is turned on, the local processing unit transmits a system termination request command to the central processing unit (steps 51703 and 517).
04).

On the other hand, when the central processing unit that sent the ``Paper Closing'' packet in step 52704 receives the tl ACK'' from the NAU 530, it receives the system termination command from the local processing unit (steps 52704 and 52705).

When the central processing unit receives this command, it creates a daily report file consisting of one day's business data, saves it on the hard disk HDD, erases the power outage save file from the hard disk, and then sends system termination message data (step 52706). ~52708). The local processing device receives this and displays a message instructing to turn off the power on the system termination screen (step 51705).

NAU53 received the “Park Closed” packet from the management device.
0 sends a "closed" packet with the high-rise head removed to each unit (steps 53701, 54701). When the unit receives the packet, it turns off the indicator lamp indicating that it is in operation, and sends the card to the card reader. A command is given to refuse the acceptance of the card and the issuance of the card (steps 55701, 55702).

FIG. 94 shows the processing procedure of the management device 400 when a power outage occurs.

When a power outage occurs, the power is switched and the central processing unit C
The PU operates with backup from the auxiliary power supply device 409, first stops collecting periodic data from each unit, and transmits to the local processing device 413 that a power outage countermeasure is being taken (steps 52711, 52712). Then, the local processing device displays a power outage message on the CRT display device 411 (step 51711). On the other hand, the central processing unit reads the P machine file and checks the operating information, and if the operating information is "playing", it calculates the issuing serial number from the card number in the P machine file and uses that to search the card file. and rewrites the card status to "free" (steps 52713 to 52715). after that,
Rewrite the operating information in the P machine file to "free" and then save the common data area data (including the setting value file and power outage flag), card file, P machine file, issuing machine file, and payment machine file to the hard disk HDD. After sending the result (“closed”) to the local processing device, the system goes down (steps 52716~
52718).

The local processing device that received the message "Closing j" from the central processing device displays a termination message on the CRT display device (step S1712).

FIG. 95 shows the procedure for starting up the system after the power outage occurs.

When the power is restored and the system is powered back on, the management device 4. In OO, the central processing unit CPU first clears all files FL1 to FL6 in the main memory M-MEM, and then creates a file (framework) (step 52721).

On the other hand, the local processing device 413 first uses the CRT display device 4.
After displaying the initial screen on 11, the date and time are transmitted to the central processing unit (steps 51721 and 51722). Then, the central processing unit looks at the power outage flag and determines whether there is a power outage file, and if there is a power outage file, it writes it to the hard disk (
The power outage file is read from the auxiliary storage (on the auxiliary storage) and loaded into the main storage, and the local processing unit is notified that the power outage is being started (step 52722).
~52724). Then, the local processing device displays a message "Power outage starting up" on the CRT display 411 and then responds (step 51723).

Further, after reading the power outage file, the central processing unit cPU transmits a "unit recovery data" packet to each NAU 530 using the high-rise network 520 (step 527).
25).

On the other hand, in NAtJ530 when the power is turned on.

First, set values (NAU number setters 544 to 549)
U number, minimum unit number, number of terminals, etc.) and calculates the network transmission address of each terminal to create a unit table, recognize the transmission address of each unit (terminal) and NAU itself, and check the operation of each unit. The unit table containing data is cleared (steps 5372↓ to 53724). And from the management device
Upon receiving the unit recovery data packet, the NAU puts the recovery data in the packet into the monitor table, removes the high-rise head, and sends the unit recovery data packet with the recovery data in the data section to each unit. (Steps 53725°53726).

In addition, the unit control device 180.280.3 of each terminal
50, when the power is turned on, the data transmission controller 551 in the unit first clears all data areas of the unit memory 550, and then writes data to a predetermined location r27FFJ in the unit memory (step 54).
721, 54722). Then, a predetermined terminal INT of the unit memory rises to a high level. After the power is turned on, the unit controllers 190, 290, and 390 of each terminal initialize the internal memory, registers, and I10 port, and read the setting value (machine number) from the machine number setter when the initialization signal INT from the unit memory rises. After reading and calculating the lower order of the serial number and channel number, it is written into the transmission data area of the unit memory (steps 55721-35724). When the data transmission controller 551 reads it, the unit address is recognized on the unit side (step 54723).
. This enables data transmission between the NAU 530 and each terminal using the token bus.

After that, when the NAU 530 sends a unit recovery data packet containing the recovery data already received from the management device W400 to each unit (terminal),
The data transmission controller 551 of the unit writes a "unit recovery" command to the command register CR2 in the unit memory and the recovery data to the reception data area, and the unit controller 190.2 receives the packet.
90 or 390 (step 54724).

When the unit controller confirms the reception of the ``unit recovery data'' packet, it copies the packet head to the transmission data area, and in the pachinko machine, after transmitting the date and identification code to the card reader, the ``unit recovery data'' is sent to the card reader via the unit memory. ACK'' is sent to the data transmission controller (steps 55725, 55726).The data transmission controller sends the ``ACK'' packet to the data transmission controller.
, send to U, N A U C/< Add a high-rise head to Kerato's head and send "ACK" to the management device (
Step 54725.53727).

When the central processing unit of the management device receives the “ACK”, it forms a “PARISTART” packet and sends the NAU530
(steps 52726, 52728).

When this packet is transmitted from the NAU 530 to the unit controller via the data transmission controller 551 (step 33728), the unit controller restores the display lamps, number of balls, amount display, etc. to the state before the failure (step 35727). ). The pachinko machine then sends a "reload" command to the card reader (step 85728). Then, if there is a card inside, the card reader 800 re-reads the magnetic data etc. and sends the card number to the unit controller 1.
It will be sent to 90. Thereafter, the unit controller executes the same process as in the card-in case of FIG. 78, sends the card number, and receives and receives the card text.

Note that when the NAU 530 receives the "Restart" packet in step 83684 and confirms the hard ACK from the unit's network controller, it receives "A CK".
”Send the packet to the management device (step 5372
9).

Next, the central processing unit cPU and local processing unit are used when the management device 400 controls the entire system while communicating with the pachinko machine 100, the issuing machine 200, and the payment machine 300 using the various packets shown in Table 31. The control procedure of step 413 will be explained using FIGS. 96 to 137.

FIGS. 96(A) to 96(D) show flowcharts of initialization processing.

When the central processing unit CPU and the local processing unit 4〕3 are reset by power-on, they initialize internal registers, internal memory, etc., and the central processing unit sets a file framework in the main memory M-MEM. At the same time, the local processing device displays an initial screen (first and second lines only) indicating that preparation is in progress as shown in FIG. 1838 (steps 51001 and 52001). Then, the local processing unit 413 reads the date and time from its own timer and sends it to the central processing unit CPU (step 510
02). The timer included in the local processing device 413 is backed up by a battery, and does not stop even when the power is turned off, but always operates and functions as a clock.

When the central processing unit CPU receives the date and time, it stores it in the common data area of the main memory iM-MEM and transmits an ACK to the local processing unit. If the local processing device does not receive this ACK, it returns to step 51002 and transmits the date and time again.

After receiving the date and time and returning ACK, the central processing unit checks the power outage backup file in the hard disk HDD and checks whether the power outage flag in that file is set to LL111 to determine whether there is a power outage file. If the power outage file exists, it is determined that the power is turned on after the power outage is recovered, and step 52041 in FIG. 96(D) is performed.
(Steps 51003, 52002 to 520
04).

If it is determined in step 52004 that there is no power outage file, the process advances to step 52005, where the mode is set to preparing, and the setting value file FL5 is read from the hard disk HDD and stored in the main memory. Set to a predetermined address position in M-MEM (step 52006)
. Then, the transmission address file FL6 created at the time of system installation is similarly loaded from the hard disk HDD to the main storage devices M and -MEM (step 520).
07).

Next, the central processing unit creates a pachinko machine file PL2 in the main storage device M-MEM, and obtains the serial numbers of the pachinko machines that make up the system from the transmission address file FL6, and the number of prize balls and batting from the setting value file PL5. Read out the number of stops and stop mode and enter them in the specified columns of the pachinko machine file PL2, and write "O" in the other columns (Step 5
2008). After that, the transmission address file F
Each issuing machine 200 and payment machine 3 that make up the system from L6
Read out the serial number 00 and create each issuing machine file FL3.
in the specified column of the payment machine file FL4, and write "O" in the other columns (steps 52009, 32010).
).

Also, enter "O" in all items in the card file FLI provided in the main storage device M-MEM (step 520).
11), the process moves to step 52012.

In step 52012, after performing the random number generation process (see FIG. 137) necessary to calculate the card number,
Masato checks whether there is an inquiry about the mode from the local processing device 413. If there is an inquiry about the mode, the response “mode = “Preparing”” is sent to the local processing device 413 (steps 51004, 52013, 52014). , the local processing device receives this and displays “Preparing” on the screen of FIG. 138 on the CRT display device 411.
Display message MSG1 indicating “Line test in progress” (
Step 51005). Then, local processing device 4
13 sends a line test request command to the central processing unit CPU (step 51006).

When the central processing unit CPU receives and confirms the line test request command, it forms a "line test" packet and sequentially transmits it to all NAUs 530 via the high-rise network 520 (steps 52015 and 52016).

When the response "A CK" packet is received from NAU530, the NA in the transmission address file FL6 is
Bit O of U status 2 is set to “1” (N A
U normal) is entered (step 52017). and,
It is determined whether transmission to all NA'Us has been completed (step 52018), and when it has been completed, the central processing unit
Each NAU forms a “Unit Table Request” packet.
530 and receives the "ACK" packet from the NAUs, it is determined whether there are responses from all NAUs (steps 52019-S2021).

When an ACK is received for the "unit table request" for all NAUs, the transmission address of the unit table included in the packet and the step 5200 described above are sent.
7, from the hard disk HDD to the main storage iM-MEM
The address in the loaded transmission address file is compared (step 52022). Then, it is determined whether or not there is a unit that is not registered in the file in the received unit table (step 52023), if not, it is left as is, and if there is an unregistered unit, step 52
At step 024, the unit is added to the transmission address file, and then the process proceeds to step 52025.

In step 52025, it is determined whether or not there is a unit that does not exist in the received unit table among the units registered in the transmission address file. After storing it as a unit that cannot communicate, the process moves to step 52027.

In step 52027, the transmission address file is saved on the hard disk HDD. As a result, if there is a change in the transmission address file in step 52024, the changed transmission address file is read out and compared when the system is started up after a power failure or the next day.

After that, the central processing bag WCPU is transferred to the local processing unit 413.
The line test results are sent to (step 82028).

Moreover, at this time, if there is an abnormal terminal (unit), the line test result is transmitted together with screen data for displaying the unit number of the abnormal terminal on the CRT screen.

When the local processing device 413 receives this line test result (step 51007), it determines whether there is an abnormal terminal (step 81008), and if not, it directly moves to step 51011, and if there is an abnormal terminal, it proceeds to step 51009). 139, which displays the serial number of the abnormal terminal on the screen of the CRT display device 411.

By looking at this screen and checking for abnormal terminals, the line can be restored to normal.

However, even when the terminal abnormality screen (FIG. 139) is displayed, the system can be activated to open the store by turning on the store opening switch 421, and the local processing device 413 , step 510
10, it is determined whether the store opening switch 421 is turned on,
If it is turned on, the process advances to step 51011 and sends an initial value setting request command to the central processing unit CPU. If the opening switch is off in step 51010, the process jumps to step 51006 and sends the line test request command again. As a result, when a staff member looks at the terminal abnormality display screen and repairs the terminal and the terminal becomes normal, it is treated as an abnormal terminal, that is, it is removed from registration.

On the other hand, in step 5, the central processing unit cPU receives the initial value setting request command from the local processing unit 413.
2029), generates an "initial value setting" packet, enters the contents of the setting value file in the data field, and sends it to each unit (step 52030). If a response "ACK" packet is received, it is determined whether initial value settings for all units have been completed (step 5203).
1.52032). When the initial value settings for all units are completed, display data of a store opening request screen as shown in FIG. 140 is sent to the local processing device 413 (step 52).
033).

When the local processing device receives this screen data, it displays it on the CRT display device 411 and then waits for the store open switch 42 to be turned on according to the message (
Step 5101.2, 5t013). Here, when the store opening switch is turned on, the local processing unit transmits a store opening request command to the central processing unit (step 51).
014).

When the central processing unit receives this command, the NA
Send a store opening packet to U530 (step 5
2034.52035). Then from NA, U'
ACK" is received, it is checked whether or not the packet transmission to all NAUs has been completed, and when it has been completed, the normal display screen data indicating that the business is in operation as shown in FIG. (steps 52036 to 52038).Meanwhile, when the local processing device receives the screen data, it transfers it to the CRT.
Display on the display device 411 and shift to business operation control (
Step S i O5).

FIG. 96(D) shows the control procedure of the central processing unit CPU and the local processing unit 413 when the system starts up after the power is restored.

As described above, when a power outage occurs, the management device 400 stores the card file FLI, pachinko machine file FL2, issuing machine file FL3 . Save payment machine file FL4 and common data to hard disk HD
D, the power outage flag is set to "1", and the system is brought down. Therefore, when the power is restored and the power is turned on, the initialization process shown in FIG. 96(A) is started, and when it reaches step 52004, it is determined that there is a power outage file and step 5 of FIG. 96(D) is started.
2041 Hejijump. In step 52041, the mode is set to "starting up from power outage". 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 device, step 510
04 to inquire about the mode. At this time, the mode in the central processing unit is already set to "starting up from power outage", so when the mode inquiry is received,
The mode is “starting up from power outage” (step 5).
2042.52043). When the local processing unit receives this mode, it determines whether it is "starting up from power outage" or not, and if yes, it displays the message "System recovery in progress" on the 6th line of the preparation screen in Figure 138. Display it (step S1021.). Then set the timer.

When the timer times out and a certain amount of time has passed (
Steps 51022, 51023, 51024), the process returns to step 51004 and the mode inquiry is made again.

On the other hand, when the central processing unit CPU responds with the mode,
The power outage file is read from the hard disk and restored to the common data area of the main storage M-MEM (steps 52044, 52045), and while waiting for the timer, a unit recovery packet is sent to each unit,
The operating data in the unit memory of each unit is restored to the state before the power outage (step 82046). Then, after receiving the "ACK" packet from each two units and completing for all units, the "ACK" packet is sent to NAU530.
Restart (type)” packets are sent one after another to restart the unit for each type (steps 52047~
52049). Then, “AC” from each NAU530
After receiving "K" and completing all NAUs, the mode of the central processing unit is changed to "open for business" and the data on the normal display screen (Fig. 147) indicating "open for business" is transmitted (steps 52050-32053). . At this point, the timer that the local processing unit 413 set in step 51023 times out, and the process returns to step 51004 to inquire about the mode. Since "business" is returned as the mode, it is determined as NO in step 51021. Then, the process jumps to step 5IO25, displays the normal display screen sent from the central processing unit on the CRT display device 411, and then shifts to control during business hours.

FIG. 97 shows a procedure for changing initial setting values using the built-in switch 438 provided on the back of the console 412.

Step 51 in FIG. 96(C) of the above-mentioned initialization flow
The store opening request screen (Fig. 140) is displayed at step 012, and while waiting for switch input at step 51013,
When the built-in switch 438 is turned on, the local processing units 4/3 sends a request command for initial setting values to the central processing unit W and CP tJ (step 51031).
. Then, the central processing unit sends the contents of the setting value file loaded from the hard disk to the local processing unit 413 (step 52061). In response to this, the local processing device displays a setting value change screen as shown in FIG. 141 on the screen of the CRT display device 411 (step 51032).
.

Here, when the operator follows the on-screen instructions and enters a new set value for the purchased ball rate or identification code using the numeric keypad 425 on the console, the local processing unit stores the updated value in internal memory and then Display the setting value change screen (see Figure 142) (step 51)
033). Further, at this time, if the return key 426 is suddenly pressed without inputting the set value, the screen moves to the next change screen without updating the set value.

When the player enters the machine number and the number of prize balls using the numeric keypad according to the instructions on this screen, the local processing device stores the updated value and then displays the next setting value change screen (see FIG. 143) (step 51034). Further, at this time, if the return key 426 is suddenly pressed without inputting the set value, the screen moves to the next change screen without updating the set value.

While looking at the change screen, input the number of NAUs, pachinko machines, issuing machines, or settlement machines using the numeric keypad.The local processing unit 413 centrally processes the setting value file update request command containing the updated values stored in the internal memory. The information is transmitted to the device (step 51035). central processing unit CPU
When the M-ME receives this command, it first stores the main memory bag [M-ME
After updating the setting value file in M and then the pachinko machine file, an "initial value setting" packet containing the updated setting values is sent to all units (steps 52062 to 5
2064).

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

When waiting for switch input in step 51013 of the initialization flow in FIG.
When turned on, the local processing unit 413 transmits a setting value change request command to the central processing unit 1cpu (step S1041). Then, the central processing unit sends the contents of the setting value file loaded from the hard disk to the local processing unit (step 52071). In response to this, the local processing device displays the first image on the screen of the CRT display 411.
Display the setting value change screen as shown in Figure 44 (Step 5)
1042).

Here, the operator presses the numeric keypad 40 according to the instructions on the screen.
When the machine number and the number of discontinuations are inputted in Step 5, the local processing device stores the updated values in the internal memory and then displays the next set value change screen (see Figure 145) (Step 5).
1043).

When the operator looks at this screen and inputs the machine number and cancellation mode using the numeric keypad according to the instructions on the screen, the local processing unit stores the updated value in internal memory, and then stores the updated value stored in internal memory. A setting value file update request command containing the following is sent to the central processing unit (step 51044).

When the central processing unit receives this command, it first updates the setting value file in the main memory M-MEM, then updates the pachinko machine file, and then all the "initial value setting" packets containing the updated setting values. Send to unit (step 5)
2072-52074).

On the other hand, FIG. 96(C) (1) Step S 1013t
'When waiting for switch input, the console 412
When the upper date and time setting switch 439 is turned on, the local processing device displays the CRT display! 411, the date and time change screen (
(see Figure 146) is displayed (step 51045).
. Then, when the operator inputs the date and time using the numeric keypad 425 according to the instructions on this screen, the local processing device transmits the updated date and time to the central processing device (step S1o46). When the central processing unit receives the date and time,
Change the current time of the internal timer to the received time, then
Sends an ``initial value setting'' packet containing the updated year and month log data (other settings remain as they were) to all units (
Steps 52075, 52076).

FIG. 99 shows a procedure for periodic data request processing from the management device 400 to the NAU 530.

When the central processing unit CPU receives an interrupt every second from the timer, it starts this periodic data request processing and first checks whether the operation mode is "in business" or not in step 52.
10↓), if the store is not open for business, the process moves to step S2↓02 and waits until 15 seconds have elapsed. This is to wait for the line test and initial value setting process according to the initialization flow to be completed.

If it is determined in step 52101 that the business is open, step 52
Proceed to 103 and send the "periodic data request" packet to NAU5.
30 and set the timer (step 5
2104). Then, the response ACK from NAU530
Checks whether ACK has been returned, and if there is an ACK, moves to scheduled data reception processing 52121 to 52135 in Figure 100 (
Step 52105). When step 52105 determines that there is no ACK, the timer set in step 52104 is checked to see if a timeout has occurred (step 52106). And NAU53
If a time-over occurs before receiving the response ACK from 0, the process moves to step 52107, and the response is counted among the error counters provided for each NAU in the common data area CDA of the main memory M-MEM. After incrementing the error counter corresponding to the NAU without , it is determined in step S2↓08 whether the error counter has become 3 or more, that is, whether an error has occurred three times in a row, and if it is 2 or less, the process proceeds to step 52103. Go back and send a ``periodic data request'' packet to the same NAU again. Then, before receiving ACK again, a timeout occurs, and if this is repeated three times, step 5
Proceeding from 2108 to S2↓09, here bit O (NORMAL) of the status information corresponding to the NAU without ACK among the NAU status prepared for each NAU in the transmission address file is cleared to "O", and then An interrupt display command is sent to the local processing device 413 to display an interrupt message informing the NAU down on the screen of the CRT display 411, and the printer 408
Give a command to print out the same content. Further, after displaying the interrupt, the local processing device sounds the buzzer 440 [steps 52110, 51051 and 510].
52).

After that, it is determined whether or not a regular data request has been made to all NAUs 530, and if no, step S 2 ];
03 and transmits a "periodic data request" packet to the next NAU (step 52111). Then, it is determined whether there is no ACK for all NAUs (step 52112). If no, interrupt processing is terminated. If yes, bit O of all NAU statuses is cleared to "O", and the file F L of all units is cleared. 2~F
Set bit 7 (CHIEPA) of monitor information in L4 to “
1" to memorize that the high-rise network is abnormal (steps 52113, 52
114).

FIG. 100 shows "ACK" which contains scheduled data from NAU530 as a response to the above scheduled data request.
The processing procedure when a packet is received is shown.

When regular data is received, the central processing unit CPU first checks the monitor information for each unit at the beginning of the data column of the received packet (step 52121), and if there is no abnormality, jumps to step 52128, and if there is an abnormality. If so, the process advances to the next step 52123, and it is determined whether the abnormality is the same as the previous abnormality (step 52122). Here, if the detected abnormality is the same as the previous time, step 321
If it is a different abnormality, the new abnormality is printed by the printer 408 in step 52124. Then, the unit abnormality interrupt display screen data is sent to the local processing device 413 (step 52125). When the local processing device receives the above screen data, an interrupt message notifying the unit abnormality is sent to the 19th line of the screen of the CRT display device. Display.

On the other hand, when the central processing unit transmits the screen data in step 321.25, it first checks the hot code at the end of the received scheduled data (step 52126). Here, if there is no hot code error, step 5212
If there is an error, the error recovery processing task (see FIG. 117) is notified of the abnormality of the unit in step 52127, and then the process moves to step 32128, where the monitor information 2 in the regular data is inspected. Then, when there is an abnormality in monitor information 2, the steps 52122 to 5 described above are performed.
The abnormality is displayed on the printer and CRT display device using the same procedure as step 2125 (steps 52129 to 52132).

After that, if there is no abnormality in the monitor information, in step 52133, the file (pachinko machine file, issuing machine file, or payment machine file) of the unit in the main storage device M-MEM is rewritten with the received regular data, and then Also, if there is an abnormality, clear or change the operating information in the unit file to "free", and when receiving regular data from a pachinko machine, change the card status to "free" and change the number of balls and amount in the P machine file. After saving to the card file, it is determined whether steps 52121 to 52133 have been completed for all units in the received packet, and if not, the process returns to step 52121 (step 5
2134). Also, once all units are finished,
In the next step S2] 35, it is determined whether or not the "ACK" packets of scheduled data from all NAUs 530 have been processed, and if no, the process returns to step 32121 and all "ACK" packets have been processed.
ACK” until the end of step S212.
], ~52134 are repeated.

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

When the central processing unit receives the “Card Purchase” packet,
Extract the card number from the data column in the packet and determine whether the number is "O" (steps 52141, 52
142). In the system of this embodiment, before the actual card issuance is carried out by the issuing machine 200, one issuing machine itself sends a "card purchase" packet with the card number set to "0" to reserve the card issuance. This is to distinguish between packets for such reservations and original "card purchase" packets that have already been reserved.

Here, if the card number in the packet is "O", that is, it is a purchase packet for issuance reservation, step 82
Go to 1.43 and read the number of issuances from the issuer file in the main storage M-MEM, and check whether the issuance acceptance number in the packet matches the number of issuances in the file plus "1". (Step 52144). Then, if the 1 issue acceptance number matches the number of issues + 1, step 52
The process advances to step 145, and it is checked whether the card amount in the packet is "O" (step 52146). As a result, if the amount ≠ 0, step 52149 jumps, and if the amount = 0, the next step 52147 reads the reservation flag from the issuer file and checks whether it is "1", that is, reserved (step 52148). Here, if the reservation flag is not "rl", the card issuance serial number in the packet and the number of issuances in the file are incremented in step 52149. When the amount is not "0" in step 52146, the reservation flag is not checked and the card issuing serial number is incremented in step 52149. This is because the Ricard number is "O" without making a reservation. This is to enable a card to be issued even if a packet containing the purchase amount in the card amount column is received.

After incrementing the card issuance serial number in step 52149 (the number of issuances is updated in the unit memory when the issuing machine ejects the card, and the number of issues is updated in the issuing machine file by sucking it up through regular data collection), , search the card file using the card issue serial number, clear the file of the cart, and then calculate the card number from the card issue serial number (step S2).
50.52151). Then, in step 52152, write the calculated value in the card number column in the cart file, write the values in the received packet in the number of balls and amount columns, set the card status to "free", and change the card to "1". ] and write the received data and current time in the history data of i=1, then step 5215
3, a "IIACK" packet is sent to the issuing device 200.

Furthermore, if it is determined that the cart number is "0" in step S2↓42 and the issuance acceptance number received in step 52144 and the number of issuances + 1 in the file do not match, the process moves to step 52154. Compare the issuance acceptance number and the number of issuances, and if they match, step 52
Step 155 calculates the card number from the cart issued serial number, and in the next step 52156 the card file is searched using the card issued serial number and the corresponding file is read, and then the process goes to step 52152 described above to update the card file. After that, it transmits an "ACK" packet (step 52153). For example, for issue reservation “
Step 52141~ Receive card purchase'' packet
This takes into consideration the case where the "ACK" packet transmitted by executing 52153 does not reach the issuing machine within a predetermined time and the same "Card Purchase" packet is sent from the issuing machine.

On the other hand, "Card Purchase" received in step 52142
If the card number in the packet is not "O", that is, if there is a genuine purchase application for a reserved card, step 52157 jumps to the issuance acceptance number in the packet and the card in the issuing machine file. The card file is compared with the number of issues plus "1", and if they match, the card file is searched using the received cart issue serial number and the corresponding file is read out (step 52158).
) to step 52152 to update the file. At this time, the actual card purchase amount in the received packet is written to the card file. After updating the file,
Send an “ACK” packet.

If it is determined in step 52142 that the card number is not O, and then it is determined in step 52157 that the issuance acceptance number and the number of issuances do not match, it is determined that the packet is an erroneous "card purchase" packet, and step 52159 is hejjumped. Send NAK.

FIG. 102 shows the control unit i6 of the pachinko machine 100.
4 shows a processing procedure of the central processing unit CPU when receiving a "card-in" packet transmitted to the management device 400 when a card is inserted into the memory card 400.

Upon receiving the “'card-in” packet, the central processing unit first calculates the card issuing serial number backward from the card number in the packet (step 52161), and then searches the card file using the calculated card issuing serial number. , reads the file of the corresponding card (step 5216
2) Then, extract the card number from the loaded card file and compare it with the card number in the received packet (steps 52163, 52164). If they match, proceed to step 52165 and change the card status of the card in the file to " Check to see if it is free. Here, if the card status is "free", the card status in the card file is rewritten to "gaming", and the numbers in the received packet are written in the machine number and serial number columns of the terminal where it is located (step 52166).

After that, I entered the card text (card number, number of balls, amount, and card) read from the card file.
A CK” packet is sent to the pachinko machine 100, and the card number in the received packet is written in the card number field in the pachinko machine file, and the process ends (step 5).
2167, 52168).

Note that if the card number in the packet and the card number in the file are compared in step 52164 and they do not match, or if the card numbers match but the card status is not "free", step 52171 indicates that the card number in the file is not "playing". ”, and if the card status is not “gaming”, it is determined that an inappropriate card has been inserted, and the process goes to step 52174, where it jumps and transmits a “NAK” packet. By comparing the card number in the packet with the card number in the file in this way, counterfeit cards can be eliminated. Also, if the inserted card is the one that was interrupted in another pachinko machine, step 52165
．． 52171, both are determined as NO and step S
2 ], 74 hejjump and send "N A K ".

When it is determined in step 52165 that the card status is not "free" and it is determined in step 52171 that it is "playing", the process moves to step 52172 and the P machine number in the received packet matches the machine number in the card file. The reason why I returned "ACK" when the power was restored is that after the power is restored, the pachinko machine rereads the card and if there is a card, it will send a "Card In" packet.
This is to deal with that.

FIG. 103 shows that when an interruption card is inserted into a pachinko machine that is being interrupted, a management bag M400 is sent from the pachinko machine 100.
The processing procedure of the central processing unit cPU when receiving the ``Suspend Card-in'' packet sent to the CPU is shown.

Upon receiving the "suspended card-in" packet, the central processing unit first calculates back the card issuing serial number from the card number in the packet (step 52181). Next, the card file is searched using the calculated card issuing serial number and the file of the corresponding card is read (step 521).
82). Then, the card number is extracted from the read card file and compared with the card number in the received packet (Step S2], 83, 52184). If they match, the process proceeds to Step 82185 and the card status of the card in the file is changed to "Suspended". Check whether it is "medium" or not. here,
If the card status is "suspended", update the card text in the card file, rewrite the card status to "playing", write the data and time at the time of suspension in the i-th column of history data, and then write the data and time at the i-counter. is decremented (steps 52186 and 52187). When an interruption occurs, the data and time at the time of interruption are temporarily recorded in the history field indicated by the i counter in the card file, but when the interruption is canceled, the i
By decrementing the counter and overwriting it in the same field when writing the next history data, it is possible to avoid the history data field becoming full due to frequently occurring interruptions and to make effective use of the memory.

After updating the card file in step 52186 and setting the i counter to "-1" in step 82187, the process advances to step 82188 and sends an "ACK" packet containing the card text read from the cart file to the relevant pachinko machine. do.

Note that if the card number in the packet and the card number in the file are compared in step 52184 and they do not match, or if the card numbers match but the card status is not "suspended", the card status is changed in step 52191. It is determined whether or not the card is "playing", and if it is not "playing", it is determined that an inappropriate card has been inserted, and the process jumps to step 52193 and transmits a "N A K " packet.

However, if it is determined in step 52191 that the card status is not "suspended" but is "playing", the process moves to step 52192 and the P machine number in the received packet and the machine number in the card file are When the two match, the process moves to step 52187, where the card text is inserted and an "ACK" packet is sent. This also applies, for example, when the management device first performs steps 52181 to 521.
This takes into consideration the case where the pachinko machine executes 97 and sends "ACK", but the pachinko machine cannot receive it and sends the "interrupt card-in" packet again.

If the machine numbers do not match in step 52192, the inserted card is incompatible, so the process moves to step 32193 and a 'NAK' packet is transmitted.

FIG. 104 shows the processing procedure of the central processing bag WcPU when it receives an "interrupt switch" packet sent from the pachinko machine to the management device 1400 when the interrupt switch provided on the pachinko machine 100 is turned on during a game. show.

Upon receiving this packet, the central processing unit first calculates the card issuing serial number from the card number in the packet, searches the card file using the card issuing serial number, and reads the corresponding cart data (step 52201.5).
2202).

Next, it is determined whether or not the card status of the card data read from the card file is "playing" (step 52203).

Here, if the card status is "playing", step 5220
Proceed to step 4, compare the cart location terminal number in the packet and the cart location terminal number read from the file, and if they match, the data in the card file (card number, number of balls, amount, card status, Rewrite the location terminal serial number and location terminal number) to the data in the packet (
Step 52205). Then, check whether the i-counter in the corresponding card file is less than 19 (step 52206), and if it is less than 19, increment the i-counter in step 82207, and enter the machine number, number of balls, and amount in the packet in the next history data column. After writing the current time of the timer, send an "ACK" packet containing the card text to the pachinko machine (steps 52208, 52
209). Further, when it is determined in the above step 82206 that the i counter is 19, the i counter is not updated, but jumps to step 32208, and the data in the packet is written overlappingly in the 19th history data column. In this embodiment, the number of history data columns is 20, and the 20th data column is reserved for writing settlement data.

On the other hand, when it is determined in step 52203 that the card status in the card file is not "playing" or when it is determined that the card status is "gaming" but the machine numbers do not match in step 52204, step 52211
Then, it is determined whether the card status is "suspended" or not.

Here, if the card status is neither "playing" nor "interrupted", the process jumps to step 82214 and transmits an "NAK" packet to the pachinko machine.

If it is determined in step 52211 that the card status is "suspended", the process advances to step 52212, where the terminal number in the packet is compared with the terminal number in the file, and if they match, an 'ACK' packet is sent. (step 5221.3).

This takes into consideration the case where the same "interrupt switch" packet is sent again after "ACK'" is transmitted in step 52209. Note that even if the card status is "suspended" in step 52211, if the machine numbers do not match, a "N A K" packet is transmitted (step 522
12-52214).

FIG. 105 shows the processing procedure of the central processing unit CPU when it receives a pachinko end switch packet sent from the pachinko machine to the management device 400 when the end switch provided on the pachinko machine 100 is turned on during a game. show.

The processing procedure when this packet is received is almost the same as the processing procedure when the "interrupt switch" packet is received (steps 52201 to 52214) in FIG. 104.

The difference is that when updating the card file in step 52225, "Free J" is written as the card status, and in step 52231, it is not whether the card number in the file is "suspended" or not.

The only point is to determine whether it is "free" or not.

FIG. 106 shows the reception of a “return” packet sent from the pachinko machine to the management device W400 when a return to zero (the number of balls held and the unused amount are both zero) occurs in the pachinko machine 100 during a game. The processing procedure of the central processing unit ECPU is shown below.

The processing procedure when this packet is received is almost the same as the processing procedure when the "interrupt switch" packet is received (steps 52201 to 52214) in FIG. 104.

The difference is that "return to zero" is written as the card status when updating the card file in step 52225.
The only point is that in step 82251, it is determined whether the card number in the file is "returning to zero" or not, rather than whether it is "suspended" or not.

FIG. 108 shows the processing procedure of the central processing unit CPU when a "return to zero" packet transmitted from the pachinko machine 100 to the management device N400 is received when a stop state occurs during a game in the pachinko machine 100.

Steps 52261 to 52268 in the processing procedure when this packet is received are steps 52201 to 52208 in the processing flow of FIG. 1.04, and steps 52275 to 52278 in FIG.
Steps 52211 to 52 in the processing flow in Figure 4
214 and consultation. The difference is step 52265
When updating the card file with "
The second point is that it is determined in step 52275 whether the card status is "free" or "cancelled" rather than whether it is "suspended."

Furthermore, in this "stop" packet reception process, instead of writing the data and time in the received packet in the history data column of the card file in step 52268, and then immediately transmitting the "ACK" packet, 10th
As shown in Figure 7, the machine number in the received packet is also used to search the P machine file, and the operation information of the corresponding pachinko machine data is rewritten to "discontinued", and then the discontinued interrupt display screen data is At the same time, the printer 408 prints out the occurrence of cancellation along with the machine number, and then sends an "ACK" packet to the pachinko machine (steps 52269 to 52269). 52273).

Note that when the local processing unit receives the abort interrupt command sent by the central processing unit in step 52271, the CR
A stop message (time, stop table, and number of stops) is displayed on the 19th line of the screen of the T display device 411, and a buzzer is turned on (step S↓06↓~
51063).

FIG. 108 shows that when a card is inserted into the payment machine 300, the payment machine executes card payment based on the "Card Payment" packet and its "ACK" sent to the management device 4.0O. ``Payment completed'' will be sent later
The processing procedure of the central processing unit CPU when a packet is received is shown.

When receiving a "card payment" packet, the central processing unit first calculates the card issuing serial number backward from the card number in the packet, searches the card file using the card issuing serial number, reads the data of the cart, and processes the card. Determine whether the status is "Free" or "Suspended" (
Steps 52281-52283). Here, if the card status is "free" or "suspended", the current time of the timer is set as the settlement acceptance time in step 52284, and the card number, number of balls held, and amount are set as the payment acceptance time in the card file. , “ACK” containing the card issuing serial number and card history data as payment data.
Send the packet to the payment machine (step 52284);
On the other hand, if the card status read from the card file is neither "free" nor "suspended," step 5
It moves from 2283 to 52285 and transmits a "N A K" packet. When the payment machine 300 receives the above-mentioned "ACK" packet, it issues a receipt with the payment data in the packet printed, refunds the unused money, and then transmits a ``Payment Completed'' packet.

When the management device 400 receives this "Payment Completed" packet, the central processing unit first calculates the card issuing serial number backward from the card number in the packet, searches the card file using the card issuing serial number, and stores the information about the cart. The data is read and it is determined whether the card status is "suspended" (steps 52291 to S2293). Here, if the card status is "suspended", a "suspension end" packet is sent to the pachinko machine corresponding to the card location terminal number read from the card file in step 52274, and the pachinko machine in the suspended state is played. After changing to a possible free state, if the card state is not "suspended", jump to step 32294 and proceed to step 5229.
Proceed to step 5 and update the i counter in the card file (
Increment). Then, change the card status in the card file to "settled", write the settlement data in the first place in the history data column, and send "ACK" to the packet settlement machine 300 (step 52295.
52296).

FIG. 109 shows the central processing unit CP when the cancel release switch 433 provided on the console 412 is turned on.
The processing procedure in U and the local processing device 413 is shown.

When the abort release switch 433 is turned on, the local processing unit transmits an abort table data request command to the central processing unit (step 5107e). When the central processing unit receives this command, it sequentially reads the P machine files from the main storage M-MEM and checks whether the operation information is "discontinued". If it is "discontinued", it discontinues it. Of the machine number and operation data of the pachinko machine in the state, the number of stops, number of balls played, number of balls out, number of differences, number of balls held, sales, and number of customers are transmitted to the local processing device (step 52301
~52303).

Then, the local processing device displays a stop table release display screen as shown in Fig.
72).

On the other hand, after transmitting the operation data of the stopping machines, the central processing unit determines in step 52305 whether or not it has finished checking the operation information in one machine file for all pachinko machines, and if it has not finished checking, returns to step 52301 to proceed to the next We will investigate whether the operation information for this pachinko machine is "discontinued" or not. When the check of the operation information for all machines is completed, a stop table data end command is sent to the local processing device (step 52304). Then, the local processing device
On the 16th and 17th lines of the stop-stop release display screen shown in FIG. 48, a message is displayed prompting the operator to enter the machine number for which the stop-stop is to be canceled (step 51073).

The operator sees this message and presses the numeric keypad 425 to press the machine number or rQJ (
When rQJ is input, all units are specified), the local processing device sends a cancellation cancellation request command (step 51074). When the central processing unit receives the command, it determines whether to cancel the suspension of all pachinko machines that are currently suspended (steps 52306 and 523).
07).

Here, if all machines are not specified, proceed to step 82308, read the file of the specified pachinko machine, and determine whether the operation information is "discontinued" (step 52309).
). Then, when the operating information is other than "stopped", jump to step 52314 and send the result, and the operating information is "stopped".
In the case of "Cancellation", after sending a "Cancel Cancellation" packet to the designated pachinko machine, it is determined whether or not "A CK" has been received, and if "A CK" has been received, the operation information of the relevant P machine file is is changed from "discontinued" to "free" and the discontinuation cancellation result is sent to the local processing device (step 5).
2310-52314).

On the other hand, when it is determined in step 52307 that all machines are designated, the process moves to step 52315, where the P machine files are read in order and it is determined whether the operation information therein is "discontinued". Then, if it is other than "stop", jump to step 82320, and if "stop", go to steps 52316 to 52316.
2319, after sending a ``cancellation cancellation'' packet to the corresponding pachinko machine, it is determined whether or not an ``ACK'' has been received, and the RA
CK" is received, the operation information of the P machine file is changed from "discontinued" to "free" and then step 523
Proceed to step 20 to determine whether the processing has been completed for all units. Here, if the process has not been completed, the process returns to step 52315 and the above procedure is repeated, and if the process has been completed for all units, the process moves to step 52314 to transmit the cancellation cancellation result. Then, the local processing device receives the suspension cancellation result and changes the character "Uchi" displayed in the last column of the corresponding pachinko machine on the suspension table cancellation display screen in FIG. 148 to "empty". The process ends (step S1075).

FIG. 110 shows a processing procedure in the central processing unit WCPU and the local processing device 413 when turning on the forced termination switch 434 provided on the console 412 to forcefully terminate the pachinko machine 100.

When the forced termination switch 434 is turned on, the local processing device 413 causes the CRT display 411 to display a forced termination menu screen (step 81081). While looking at this screen, use the numeric keypad 425 to enter the number indicating the type of terminal you want to forcefully terminate among pachinko machines, issuing machines, and payment machines, and the local processing device will forcefully terminate the unit corresponding to the specified terminal type. The screen is displayed (step 51082).

FIG. 149 shows a forced termination screen for the pachinko machine. In addition, on the issuing machine forced termination screen and the payment machine forced termination screen, the characters "Pachinko machine" displayed on the fifth line of the Pachinko machine forced termination screen in Figure 149 are changed to "Issuing machine" or "Pachinko machine" respectively. It will only change to a "payment machine".

While looking at this screen, use the console's numeric keypad 425 to press the machine number or "O" (
When inputting "all machines specified", the local processing device 413 sends a forced termination request command to the central processing bag MCPU, and then changes the display to the normal display screen (Fig. 147) indicating that the pachinko machine is in operation (steps 51083 and 5108).
4).

When the central processing unit receives a pachinko machine forced termination request command from the local processing unit, it determines whether all pachinko machines are specified, and if yes, reads the P machine files in order, and the operation information in the file indicates that the game is in progress or has been interrupted. Check whether it is inside (steps 52341 to 52343). Then, if no, jump to step 32347, and if yes, P
The card issuing serial number is calculated backwards from the number of the card existing in the pachinko machine read from the machine file, and the card file is read using that serial number (Step 5)
2344, 52345). after that.

Enter the data read from the P machine file in the number of balls and amount fields of the file, and change the card status to "Free J" (step 32346), then check whether it is completed for all machines (step 52347). Step 5
Return to 2342 and repeat the above procedure.

After checking the operating information and updating the card files for all units, the process moves to step 52348 and sends a "forced termination request (type)" packet to all NAUs, and then receives a response from the NAU. If so, send the result to the local processing device (step 52348
~52350). Then, when the operator looks at the display menu selection screen in FIG. 155 and selects the specific machine display, the local processing device displays the specific machine display screen in FIG.
When you display the all-machine display screen in Figure 8, the last column for the corresponding pachinko machine will be 1, indicating that it is being forcibly shut down.
Display the characters (steps 51085.5108
6).

On the other hand, if it is determined in step 52341 that all machines have not been specified, a ``forced termination request (individual) n packets'' is sent to the specified pachinko machine (step 52351). Then, ``ACK'' is returned from that pachinko machine. If the ACK does not return, it jumps to step 52350, and when the ACK returns, the data of the pachinko machine in question is read from the P machine file, and the operation information is set to ``Playing'' or ``Interrupted.'' ”, and if yes, follow the steps 52344-5 above.
After updating the card file according to the same procedure as 2346, the process moves to step 82350 and sends the forced termination result to the local processing device (steps 82353 to 52).
357).

FIG. 111 shows the central processing bag WCPU and the local processing unit when the issuing machine 200 is forced to terminate by turning on the forced termination switch 434 provided on the console 412! 4
6 forced termination switch 434 showing the processing procedure in 13
When turned on, the local processing unit! 413 displays a forced termination menu screen on the CRT display device 411 (
Step 51091). While looking at this screen, use the numeric keypad 4.
25 to enter the number indicating the type of terminal you want to forcefully terminate among pachinko machines, issuing machines, and payment machines, the local processing device displays the issuing machine forced termination screen corresponding to the specified terminal type (step 51092).

It should be noted that, on the issuing machine forced termination screen, only the characters "Pachinko machine" displayed in the fifth line of the Pachinko machine forced termination screen in FIG. 149 are changed to "Issuing machine".

While looking at this screen, use the console's numeric keypad 425 to enter the machine number of the issuing machine you want to force terminate or "O" (specify all machines), and the local processing unit will send a command to request forced termination of the issuing machine to the central processing unit. The display is then changed to a normal display screen (FIG. 147) indicating that business is open (step 5L083.51084).

When the central processing unit receives the issuing machine forced termination request command from the local processing unit, the central processing unit determines whether all units are specified or not.
If yes, "forced termination request (type)" for all NAUs
Send the packet, and if the response is received, send the result to the local processing device (steps 52361-5
2364).

Then, when the operator looks at the menu selection screen in Figure 155 and selects the issue machine data display screen to display the issue machine data display screen in Figure 160, the local processing device selects the last column of the corresponding issue machine. , displays the character "Strong" indicating that it is being forcibly terminated (step 51095.
51096).

On the other hand, if it is determined in step 52341 that all machines are not specified, a "forced termination request (individual)" is sent to the specified issuing machine.
Send the packet (step 52365). and,
It is determined whether "ACK" is returned from the issuing machine (step 52366), and if not, step 52
364, and when ACK is returned, the operation information in the file of the issuer is changed to forced termination in step 82367, and the process moves to step 52360, where the forced termination result is sent to the local processing device.

FIG. 112 shows the central processing unit CPU and the local processing unit 41 when turning on the forced termination switch 434 provided on the console 412 to forcefully terminate the payment machine 300.
3 shows the processing procedure in step 3.

When the forced termination switch 434 is turned on, the local processing device 413 displays a forced termination menu screen on the CRT display 411 (step 51101). While looking at this screen, use the numeric keypad 425 to select pachinko machine 100,
When a number indicating the type of terminal to be forcibly terminated among the issuing machine 200 and the payment machine 300 is input, the local processing device displays a payment machine forced termination screen corresponding to the designated terminal type (step 51102). The subsequent procedure is the same as in the case of forced termination of the issuing machine in FIG. 111.

FIG. 113 shows the processing procedure of the central processing unit CPU and the local processing unit 413 when canceling the forced termination state of the pachinko machine 100 that has been forcibly terminated by the process of FIG. 110.

When the termination cancellation switch 435 on the console 412 is turned on, the local processing device 413 displays a forced termination cancellation menu screen similar to the forced termination menu screen on the CRT display device 41.
1 (step 5LILI). When a number specifying a pachinko machine is input using the numeric keypad 425 while looking at this screen, the local processing device transmits a forced termination machine data request command to the central processing unit CPU (step 51112).

When the central processing unit receives this command, it reads the pachinko machine files in order, checks whether the operation information is "forced termination", and if it is forced termination, it reads the machine number and type in the file data of the pachinko machine concerned. The number of pachinko balls played, the number of balls played, the number of out balls, the number of differences, the number of balls held, sales, and the number of customers are transmitted to the local processing device (steps 52381 to 52383).Then, the local processing device generates a pachinko machine as shown in FIG. The data of the pachinko machine that has been forcibly terminated is displayed on the screen for canceling machine termination, with one line addressed to the ↓ machine (step 51113).

On the other hand, after sending the forced termination machine data, the central processing unit determines whether it has finished checking the operating information for all machines (step 52384). ), if No, step 5238
1, and if the answer is YES, the process moves to the next step 52385, and a display data end command is sent to the local processing device. Then, the local processing device displays a forced termination cancellation message on lines 17 and 18 of the screen shown in FIG. 150, prompting the user to input the machine number for which the forced termination is to be canceled (step 51114). When the operator inputs the machine number or "0" to designate all machines using the numeric keypad 425 while looking at this screen, a pachinko machine forced termination cancellation request command is sent to the central processing unit (step 51115).

When the central processing unit receives this command, it determines whether all units are specified, and if all units are specified, all N A T,, J53
After sending a “forced termination release (type)” packet to 0, a response from NAU (ACK or NA, K
) and sends the results to the local processing device (steps 52386-52389).

On the other hand, if it is determined in step 52386 that all the pachinko machines are not designated, the process moves to step 52391 and a "forced termination cancellation (individual)" packet is sent to the designated pachinko machines.

Then, it is determined whether or not "A CK" has been received (step 52392), and if yes, the operation information in the file of the pachinko machine in question is changed to "free" in step 52393, and if it is no, the procedure is continued in step 5238.
9 and sends the result to the local processing unit. When the local processing unit receives a message from the central processing unit that the forced termination has been successfully canceled, the local processing unit changes the status display in the last column of the display data line of the pachinko machine from "Strong" to "Empty" indicating free. (Step 51116).

FIG. 114 shows the case of canceling the forced termination state of the issuing machine 200 that was forcibly terminated by the process of FIG. 111, and FIG. The processing procedure of the central processing unit 1cPU and the local processing unit 413 when canceling the state is shown.

These procedures are similar to the pachinko machine forced termination cancellation procedure shown in FIG. 113. In the process shown in FIG. 114, the issuing machine file is searched and the issuing machine machine number, received amount, deposited amount, payout amount, number of issuances, and monitor information 2 are sent as forced termination machine data to the CRT display device as shown in FIG. 151. Display the issuing machine forced termination cancellation screen as shown in .

On the other hand, in the process shown in FIG. 115, the payment machine file is searched, and the machine number of the payment machine, the payment amount, the number of coins paid, the number of payments, and the monitor information 2 are sent as forced termination machine data, and the data is sent to the CRT.
A screen for canceling forced termination of the payment machine as shown in FIG. 152 is displayed on the display device.

In addition, when the process for canceling the forced termination of the issuing machine and payment machine is successful, the status display at the end of each line on the display screen changes from "stopped", which indicates that the machine is stopped, to blank (no display). There is.

FIG. 11-6 shows the processing procedure of the central processing bag WCPU when a power outage occurs.

When a power outage occurs, the power is switched and the central processing unit is backed up by the auxiliary power supply 409 and operates. First, it is determined whether the operation mode is "open" or "closed" (steps 52441, 52442) + central processing. If the operating mode of the device is other than "open for business" or "closed" (under preparation, during power outage startup), the system will go down without doing anything. - If the mote is "open" or "closed", stop collecting regular data from each unit and change the mode to "power outage countermeasure", then
Sends a message to the local processing device that power outage measures are in progress (
Steps 82443-52445). Then, the local processing device displays a power outage message on the CRT display device (step 31141). On the other hand, the central processing unit reads the P machine file and checks the operating information, and if the operating information is "playing", it calculates the issuing serial number from the card number in the P machine file and uses that to search the card file. and rewrites the card status to "free" (steps 52446 to 52450), then rewrites the iI working information in the P machine file to "free", and then determines whether or not it has been completed for all pachinko machines, and if yes, the common Save the data area data (including setting value file and power outage flag), 4 card files, issuing machine file, and payment machine file to the hard disk HDD, change the mode to "closed", and then the system will go down. (Steps 32450-8245B).

The power outage message display Nakaguchi-Cal processing unit inquires of the mode to the central processing unit, and when the mode becomes "closed," displays a termination message on the CRT display (
Steps 51142-S1144).

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

When the central processing unit receives an interrupt from the internal timer every 3o seconds, it starts the error recovery process shown in FIG.
First, it is determined whether the mode is "open for business" or not in step 824.
61), do nothing when not in business, and if in business, proceed to step 52462, read the NAU status from the transmission address file, and the bit NORMAL, which indicates whether the NAU is normal or abnormal, becomes "○" (= abnormal). (Steps 52462, 52463). Note that the NORMAL bit of the NAU status is
Step s2゜16.52017 in the initialization flow of the figure
If there is a response to the ``Line Test'' packet, it will be set to 111+1 (= normal), so N with no response will be
The NORMAL bit of AU remains at 1'0''.

Therefore, if the NORMAL bit is determined to be l (O11),
NAU recovery processing step 52471 in FIG. 118(A)
Execute ~52475. On the other hand, NAU status N
If the oRMAL bit is II I II, step 524
Proceed to step 64, read monitor information 1 in the unit file, and check that the bit indicating a token bus abnormality is 111 II. And if 111 +1, then the 11th
Token bus recovery processing step 52481 in Figure 8 (B)
Execute ~52486, and if 1g is On, proceed to the next step 5
2466, check whether the bit indicating a watert code error in monitor information 1 is "1", and if it is 11n, the 11th
The real code recovery processes 52491 to 52498 in FIG. 9 are executed. On the other hand, if it is determined in step 52466 that there is no hot code error (no hot code error), the process proceeds to step 52467, where it is checked whether the unit abnormality bit in monitor information 1 is set to '1'. Unit recovery processing 52501 to 52509 is executed.

In the NAU recovery process shown in FIG. 118(A), first
If the PA line monitor check packet is sent to the NAU whose U status NORMAL bit is "O" and the timer is set, and the response "A CK '" is received before the time-out, the corresponding After changing the NORMAL bit of the NAU status to "work", send an interrupt display command to the local processing unit and display it on the CRT.
A message is displayed on the display screen informing that the NAU has recovered, the same message is printed out on the printer 408, and "'ACK" is sent within a certain period of time.
If it does not return, the routine returns to the original routine without doing anything (steps 52471 to 52474).

In the token bus recovery process shown in FIG. 118(B), first, a "unit monitor check" packet is sent to the unit whose token bus error bit is 1, and a timer is set (steps 32481, 5248).
2). Then respond “AC” before causing a timeout.
Step 52483, 5 to determine whether or not K” has been received.
2484), when receiving 'ACK' within the time, clears the token bus error bit of monitor information 1 in the unit file to 'O' and then sends a 'restart' packet to the unit to restart it. (Step 5)
2485, 52486).

In the hot coat recovery process shown in FIG.

First, send a unit recovery data packet to the unit where the hot code error occurred and set the timer (
Steps 52491, 52492).

Then, if an ``ACK'' is received before a timeout occurs, the hot code placed in the ``unit recovery data'' packet is compared with the hot code returned in the ``ACK'' packet (step 5249).
3 to 52495), and if the real codes do not match, the process moves to step 52498 and sets “1” to the hot code error bit of monitor information 1 in the unit file.
'', and when the hot codes match, a ``PARISTART'' packet is sent to the unit, and then the hot code error bit of the monitor information 1 of the unit is cleared (steps 52496.S2'497).

The reason why the ``restart'' packet is sent in step 52496 is that the unit that received the ``unit recovery data'' packet sent in step 52491 will be forced to terminate.

In the unit recovery process shown in FIG.
Send the packet and set the timer (step 52)
501, 52502). Then, if "ACK" is received before a time-out occurs, a "unit recovery data" packet is transmitted and the timer is set again (steps 52503 to 52506). Then, for this packet transmission as well, "ACK" is sent within a predetermined time.
is returned, a "restart" packet is sent to the unit to restart the unit (steps 52507 to 52509).

FIG. 121 shows the processing procedure of the central processing unit CPU and local processing unit 413 when the closing switch 422 and subsequently the system termination switch 423 are turned on.

When the closing switch 422 on the console 412 is turned on, the local processing device displays a closing menu screen showing a list of reception enable switches (display menu switch, print menu switch, and exit switch), and then issues a closing request command. Send to central processing unit (step 51
151,51152).

When the central processing unit receives this command, it reads the P machine files in order, checks whether the operating information is "playing", memorizes the machine number of the pachinko machine that is "playing", and then searches for all machines. It is determined whether or not the process has been completed, and if the answer is NO, the process returns to step 52511 and the above procedure is repeated (steps 52512 to 52514). After checking the operation information for all machines, step 525
Step 15, it is determined whether or not there is a pachinko machine in play, and if there is, the machine number of that pachinko machine is sent to the local processing device, and if there is no pachinko machine in play, ACK is sent.
is sent to the local processing unit, and a ``close'' packet is sent to all NAUs, and the state waits for a command from the local processing unit (steps 52516 to 2518).Meanwhile, the local processing unit sends the machine number or ``ACK'' packet to all NAUs. When this message is received, if there is a Pachinko machine being played, the system end switch is disabled, the number of the machine being played is displayed, the screen is changed to the normal display screen (Fig. 147), and the machine waits for key input ( Step S L 153-511
56) If the operator accidentally turns on the closing switch during business hours, he or she can notice the mistake by looking at this display. Furthermore, since the screen does not change when there is no pachinko machine in play, when the system end switch 423 is turned on, the system end screen (first to fourth lines) shown in FIG. 153 is displayed (step 31157). When "1" is input from the numeric keypad 425 in accordance with the instructions on this screen, the local processing unit transmits a system termination request command to the central processing unit (step 81158). When the central processing unit receives this command, it creates a daily report file consisting of one day's business data, saves it on the hard disk HDD, erases the power outage save file from the hard disk, and then sends system termination message data (steps 52520 to 52522). ), the local processing device receives this and displays a message (see line 9 in FIG. 153) instructing to turn off the power on the system termination screen (step 51159).

FIG. 122 shows the procedure for card restoration processing when the card restoration switch 424 provided on the console 412 is turned on.

When the card restoration switch is turned on, the local processing device E413 displays a message prompting the user to input the card number (first to third lines) on the card restoration screen as shown in FIG.
line) is displayed (step 31161). When you look at this screen and enter the issued serial number of the damaged card (printed on the card) using the numeric keypad 425, the local processing unit sends a card recovery data request command containing the card issued serial number to the central processing unit (step 31
162). Then, the central processing unit searches the card file using the sent card issuing serial number, reads the data of the card, and determines whether the card status is "playing" (steps S2531 and 52532).

Here, if the card status is "playing", search the pachinko machine file using the location terminal number in the card file, read the data of the pachinko machine, and transfer the number of balls and amount data in the pachinko machine file to the card. Let the current value of
Also, if the card status is other than "playing", the number of balls in the card file.

The amount data is set as the current value of the card, and these values are sent as card data to the local processing device along with the history data read from the card file (step 525).
33-52536).

Then, the local processing device displays the above cart revival screen (first
54), the received card data and history are displayed (step 51163). Therefore, when the card restoration switch 424 is turned on again, a card restoration request command is transmitted (step 81164). When the central processing unit receives this command, the card issuing device! First, send the "Initial value transmission" function containing initial values such as date, identification code, etc. to 700, and then respond to it ("Normal end").
When the card is received, a "card restoration" function containing the cart number, card issuing serial number, and amount at the time of issuance is sent, and the restoration card issuance process is started (steps 52537 to 52339). When the card issuing device 700 finishes issuing the resurrection card, it sends the result (normal completion function), so the central processing unit receives it and then transmits the completion of the resurrection to the local processing device (steps 52540, 52541).
. Then, the local processing device displays the result on the card restoration screen and then changes the screen to the normal display screen (step 51165). Note that the card issuing device 1700 that receives the above-mentioned "card restoration" function prints the date of issue and the serial number of issue, and issues a reinstatement card with a reissue hole (the amount is not printed).

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

When test card switch 437 is turned on.

Local processing bags! ! 413 displays a test card issue message on the screen of the CRT display device 411, and then transmits a test card issue request command to the central processing unit 1cPU (steps 51171 to 81172).

Upon receiving this command, the central processing unit sends an "initial value transmission" function containing initial values such as date, identification code, etc. to the card issuing device 700, and responds to it (
``Normal completion'' function) is received, the ``test card issue'' function is sent (step 52).
542-52544). Card issue bag! [When the test card issuance process in step 700 is completed, the result is sent, and after receiving the result, the test card issuance completion message is sent to the local processing device (step 5254).
5.52546), the local processing device displays the test card issuance result on the CRT display device, changes the display screen to normal display, and ends the process (Step 5).
1173).

In addition, when the card issuing device receives the "test card issue" function, it prints the characters "test card" instead of the issue date and amount, and issues a test card with the test card issue function code recorded in the magnetic recording section. (Do not punch holes).

FIG. 124 shows a flow of displaying sales statistical data using a timer interrupt.

In the management bag M400 of this embodiment, when an interrupt signal is received from the timer TMR at a predetermined period, the sales statistics data display flow shown in FIG. Bag WC
Send to PU (step 81181). When the central processing unit receives this command, it sequentially reads the pachinko machine files and first calculates the cumulative total of the number of balls played, number of balls out, and sales from the operating data collected as regular data (steps 52561, 52552). next.

Check the operation information in the file, and if it is "playing", add 1 to the number of gaming machines, and if the operating information is "discontinued", add 1 to the number of discontinued machines (steps S2553 to 5255).
6). Then, it is determined whether the search is completed for all pachinko machines (step 52557), and if it is no, step 5
Return to 2551 and repeat the above procedure, and when it is completed for all machines, in the next step 52558, divide the cumulative value of the number of balls played and the number of balls out (number of balls out ÷ number of balls played), and calculate the cumulative number of playing machines. After calculating the operating rate (number of gaming machines/total number of pachinko machines) from the values, the sales, percentage, operating rate, and number of discontinued machines are sent to the local processing device as business statistical data (steps 52558 and 52559).

On the other hand, when the local processing unit receives the sales statistical data from the central processing unit, it displays those data on the 20th line of the screen currently being displayed on the CRT display 411 (see Figure 147) (step 51182). .

FIG. 125 shows the procedure for displaying a stop table.

When the display menu switch 428 on the console 412 is turned on, the local processing bag W413 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step 51201).

When the operator selects the stop table display using the numeric keypad 425 while looking at this screen, the local processing unit transmits a stop table display data request command to the central processing unit (step 5L202).

When this command is received, the central processing unit reads the pachinko machine files in order, and the operating information in the file is
Check to see if it is a J while it is out of stock, and check the operation data for the ones that are "out of action", including the number of balls out, the number of balls out, the number of balls out, the number of differences, the number of balls held, sales, and the number of customers. is transmitted to the local processing device as stop machine data together with the machine number (steps 52561 to 52563).

Then, the local processing device stores each stop table data as the 156th
As shown in the figure, the ↓ machines are sequentially displayed in one line on the stop table display screen (step 5L203). On the other hand, when the central processing unit finishes searching for stopping machines for all machines in the pachinko machine file (step 32564), it sends a display data end message to the local processing device, and when the local processing device receives this, it waits for key human power. becomes (step 5256
5, 51204).

FIG. 126 shows the procedure for specific machine display processing.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step 51201).

When the operator selects a specific machine display using the numeric keypad while looking at this screen, the local processing unit changes to the central processing unit C.
A specific unit display data request command is sent to the PU (step 51211).

Specify (input) the machine number on the 1st to 3rd lines of the specific machine data display screen shown in FIG. 157 on the CRT display device 411.
Display a message prompting you to do so (step 51)
212). While looking at this screen, the operator presses the numeric keypad 4.
When the machine number is input from 25, the local processing unit transmits a specific machine display data request command including the machine number to the central processing unit (step 51213).

When the central processing unit receives this command, it calculates a serial number from the machine number, searches the pachinko machine file using the serial number, and reads out the operation data of the corresponding pachinko machine (steps 52571, 52572). Of this operating data, we calculate the number of balls stopped, the number of balls out, the number of out balls, the number of differences,
The number of balls held, sales, and number of customers are transmitted to the local processing device (step 52573). Then, the local processing device displays the received data on the fifth line of the specific machine data display screen (FIG. 157) (step 51214).

Thereafter, the central processing unit sends a data end command to the local processing unit and ends (step 52574,
51215).

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

When the display menu switch 428 on the console 412 is turned on, the local processing unit @413 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step S1221).

When the operator selects display of all units using the numeric keypad while looking at this screen, the local processing unit will be displayed as the central processing unit 1c.
Send the all-units display data request command to the PU (
Step 51222). When this command is received, the central processing unit reads the pachinko machine file in order, and records the number of stoppages, number of balls played, number of balls out, number of differences, number of balls held, sales, and number of customers from the operating data in the file. (Steps 52581, 52582).

Then, the local processing device sequentially displays the data of all the pachinko machines on the all-machine display screen, one machine above the other, as shown in FIG. 158 (step 51223). On the other hand, when the central processing unit finishes searching for all the pachinko machines in the pachinko machine file (step 52583), it sends an indication that the display data has ended to the local processing unit, and when the local processing unit receives this, it waits for key human power (step 52584).
゜S 1224).

FIG. 128 shows the procedure for data display processing for a so-called nose board (red board) where the number of balls out is greater than the number of out balls.

When the display menu switch 428 on the console 412 is turned on, the local processing bag M41-3 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step 51231).

When the operator selects nose bridge display using the numeric keypad 425 while looking at this screen, the local processing unit transmits a nose bridge display data request command to the central processing unit CPU (step 51232).

Upon receiving this command, the central processing unit sequentially reads the pachinko machine files (step 52591), and determines whether the number of differences in the file is negative (step 52592). Then, only the operation data of pachinko machines with negative difference numbers are sent to the local processing device (step 52
593).

Then, the local processing device sequentially displays each nose bridge data one line per device on the nose bridge display screen as shown in FIG. 159 (step 51233).

On the other hand, when the central processing unit finishes searching for nose mounts for all machines in the pachinko machine file (step 52594),
The end of display data is sent to the local processing device, and when the local processing device receives it, it waits for key human power (steps 82595, 51234).

Fig. 1.29 shows the procedure for data display processing for a so-called texture (in the black) where the number of balls out is smaller than the number of out balls.

This island stand display flow is performed according to almost the same procedure as the nose stand display flow in FIG. 128. The difference is step 5
2592, instead of determining whether the difference number is negative or not, the difference number is positive (
The only difference is that it is determined whether the positive value is positive or not, and only the operation data of the positive pachinko machine is transmitted (step 52602).

The configuration of the display screen is also the same as the nose bridge display screen in FIG. 159.

Figure 130 shows the procedure for displaying issuing machine data, and the first
FIG. 60 shows an example of the structure of the issuer data display screen displayed on the CRT display device 411.

This issuing machine data display processing flow is executed according to almost the same procedure as the entire pachinko machine data display processing flow of FIG. 127. Displayed on the screen as issuing machine data along with the machine number are the received amount, deposited amount, disbursed amount, number of issues, and monitor. Here, the monitor corresponds to monitor information l. Note that after displaying the data for all issuing machines, the total is displayed on the 18th line.

The central processing unit calculates the total data (step 5
2623).

Figure 131 shows the procedure for displaying payment machine data, and the first
FIG. 61 shows an example of the structure of the payment machine data display screen displayed on the CRT display device 411.

This payment machine data display processing flow is executed according to almost the same procedure as the issuing machine data display processing flow of FIG. 130. Along with the machine number, the payment amount is displayed on the screen as payment machine data.

These are the number of settled balls, the number of settlements, and the monitor.

Fig. 132 shows the procedure for displaying sales data for the entire pachinko parlor, that is, the total of the main pieces of operating data for all units, and Fig. 162 shows the sales data displayed by this process. An example of the configuration of a display screen is shown.

When the display menu switch 428 on the console 412 is turned on, the local processing bag W413 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step 51271).

When the operator selects sales data display using the numeric keypad while looking at this screen, the local processing unit transmits a sales data display data request command to the central processing unit cPU (step 51272). Upon receiving this command, the central processing unit sequentially reads the pachinko machine files and calculates the total number of balls played, number of balls out, number of differences, and number of balls held among the operating data (steps 82641 to 82641).
52643), then read the issuing machine files in order to calculate the total deposit amount and number of issues among the operating data (steps 82644 to 52646), then read the payment machine files in order and calculate the total of the deposit amount and the number of issues among the operating data. The sum of the amount, the number of settled balls, and the number of settlements is calculated (steps 52647 to 52649). Thereafter, the calculated total data is transmitted as business data to the local processing device, and after transmitting all the data, a display data end command is transmitted (steps 52650, 52651).

On the other hand, when the local processing device receives the sales data,
The sales data display screen shown in FIG. 162 is displayed on the CRT display device 411, and a display data end command is received to wait for key human power (step 51273.Sl, 27
4). In addition, among the above business data, the number of card issuances is displayed as the number of cards issued, and the number of settlements is displayed as the number of cards settled τ.

FIG. 133 shows the procedure of a specific card data display process for displaying data of a specific card.

When the display menu switch 428 on the console 412 is turned on, the local processing module 413 causes the CRT display 411 to display a display menu selection screen as shown in FIG. 155 (step 81281).

When the operator selects a specific card display using the numeric keypad 425 while looking at this screen, the machine number is specified in the first to third lines of the specific card data display screen shown in FIG.
31282). When the operator inputs the machine number from the numeric keypad 425 while looking at this screen, the local processing device becomes the central processing device! Sends a specific card display data request command including the ICPUA machine number (step 8128)
3). Then, the central processing unit calculates the card issuing serial number from the card number, reads the card file using the issuing serial number, and determines whether the card status in the card file is "playing" or not (steps 82661 to 52).
663). When the card status is other than ``Playing'', the number of balls and 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 as the current value of the card. to search the pachinko machine file and set the data (number of balls, amount) in the pachinko machine file as the current value of the card (step 52
664-52666). This is because the card file is rewritten when the card status changes, so the operating data in the card file does not match the actual value during the game.

Next, the central processing unit performs steps 52664 and 52666.
The card current value determined in step 5 is sent to the local processing device together with the card history data read from the card file, and then a display data end command is sent (step 5).
2667.52668) e, the local processing device displays the data of the specified card in the fourth line and below of the specific card data display screen in Fig. 163, receives the display data end command, and waits for key input. (Steps 51284, 51285).

FIG. 134 shows a procedure for displaying all card details displaying data regarding all issued cards, and FIG. 164 shows an example of the structure 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 causes the CRT display 411 to display a display menu selection screen as shown in FIG. 155 (step 51291).

When the operator selects card details display using the numeric keypad while looking at this screen, the local processing unit transmits a card details display data request command to the central processing unit CPU (step 51292). When this command is received, the central processing unit reads the pachinko machine files in order, checks whether the operation information in the file is "discontinued", and checks whether the card status is "playing" (step 52671). , 52672). When the card status is other than ``Playing'', the number of balls and 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 retrieved and the data (number of balls, amount) in the pachinko machine file is set as the current value of the card (steps 52673 to 52675).

Next, the central processing unit transmits the current card value determined in steps 52673 and 52675, the card status read from the card file, and the card location terminal number to the local processing unit (step 52676). Then, as shown in FIG. 164, the local processing device displays the remaining amount, number of balls, location terminal number, or card status of each card in one line per card (step 5).
1293).

On the other hand, after transmitting the card data in step 52676, the central processing unit adds rlJ to the total number of issued cards, calculates the remaining amount of the card and the cumulative total of the number of balls, and further calculates the total number of remaining cards and the number of balls in each card state. After calculating the number of cards, determine whether all cards have been completed (
Step 52677.52678). If not completed, return to step 52671 and repeat the above procedure; if completed, the next step 82679 sends the card total data to the local processing device and displays it on the all card details display screen in FIG. 164. Send display data end command (steps 52379, 52680, 5129
4.51295).

FIG. 135 shows the procedure of card data total display processing for displaying the total card data.

This total display process is executed according to almost the same procedure as the card details display process shown in FIG. 134 (step 51).
301-51304, 52681-52689). The only difference is that step 52676 is omitted, that is, data for each card is not sent, but only the total data of all cards is sent (step 52686). On the other hand, correspondingly, total data is displayed on the screen of the CRT display 411 (same as the lower half of the all card details display screen in FIG. 164).
only.

FIG. 136 shows the interrupted card data display processing procedure for displaying the interrupted card data and the machine number of the interrupted pachinko machine, and FIG. 165 shows the interrupted card data displayed on the CRT display 411. An example of the configuration of a display screen is shown.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 causes the CRT display 411 to display a display menu selection screen as shown in FIG. 155 (step 51311).

When the operator selects the interruption card display using the numeric keypad while looking at this screen, the local processing unit transmits an interruption card display data request command to the central processing unit CPU (step S312). Upon receiving this command, the central processing unit sequentially reads the pachinko machine files and checks whether the card status in the file is "suspended" (steps 51691, 51692). Here, for cards whose card status is "suspended", the elapsed time (difference) is determined by comparing the history data 4 of the card with the time read from the first time (interruption occurrence time) and the current time of the timer. ) is calculated (step 52693).

Then, the elapsed time, the card number, the amount of money, the number of balls held in the card data, the location terminal number, and the interruption time in the history data column are transmitted to the local processing device (step S1694). Then, the local processing unit
As shown in FIG. 5, the data of each card is displayed in one line (step S1313). In addition, when the central processing unit finishes extracting the data of the interrupted card for all cards in the file, it sends a display data end command, and when the local processing unit receives this, it waits for key human power (
Steps 52695, 52696, 51314).

In the management device 400 of this embodiment, by displaying the interruption card data, for pachinko machines whose interruption elapsed time has become too long,
The management device sends a ``Parcel Termination Request'' packet, and then ``
By sending a ``forced termination release'' packet, the suspended state can be canceled and the transition to the free state can be made. This makes it possible to avoid this problem and open up all pachinko machines to as many players as possible to make the game fairer.Furthermore, in the system of this embodiment, the data of the suspended card is stored in the card file. Even if a suspended pachinko machine is released to another player, the interests of the player will not be harmed at all.

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

Although not shown, in the above embodiment, when there is too much data to be displayed on one screen, as in the all-machine display screen shown in FIG. Columns are now scrolled upwards.

FIG. 137 shows more specific details of the random number generation process 52012 in the initialization flow of FIG. 96 and the card number calculation process 52151 in the flow of FIG. The steps are shown sequentially.

To generate a random number, first, a random number A between 0 and 10,000 is generated. Specifically, 1. For example, find the sum of the "month" and "day" that correspond to a business day, and "the number of the lowest digit of the current time (in units of 1/100 seconds)" and set it as a random number 1 ( Step 527
01).

Next, using the random number generation command RND (n), which is one of the commands of the FORTRAN programming language, enter the random number (generated in step S1 above) into (n) to obtain a random number (7 digit or more) and convert it to 10
Multiply by 7 to obtain random number 2 (step 52702) e Then, use the same < FORTRAN command INT(n) to round down the decimal part of random number 2 (step 52
703).

After that, in step 52704, the random number A is determined to be O≦A.
Does it satisfy the condition ≦10000?

That is, it is checked whether A is thicker than O and smaller than 10000, and if A<O or A>100OO, the process returns to step S1 and the random number A is generated again. Then step 5
In step 2705, 10,000 is added to the random number A that satisfies the above conditions. As a result, the random number A becomes any number between 10,000 and 20,000. Therefore, the first step is FORTRA
Using the instruction MOD of N, find the remainder when dividing the random number A by the integer "5" and set it as the random number B (step 52706
). Therefore, the random number B is one of 0, 1, 2, 3, and 4.

Thereafter, during the card purchase packet reception flow, the random number A obtained in step 52705 is added to the card issuing serial number n, and the addition result X is set as the primary card number (step 52707).

However, the issue serial number n given here is 1 to 127.
67, and no cards exceeding 12,767 cards will be issued. As a result, the -next card number X is 10001 to 3276
It will be a number between 7. The reason for setting the upper limit of X to 32767 is
This is because 32767 is the largest number that can be expressed in 15 bits in the binary system, and in the gaming system described below that handles 16-bit data, a code with a ``1'' in the most significant bit can be used to create a code that is different from a normal gaming card. This is to reserve it for a special card (test cart).

In the next step 52708, the primary card number Do the following.

Here, five types of conversion patterns are prepared in advance according to the random number B as the bit replacement rules, and the conversion patterns corresponding to the random number B are executed to replace the bits.

In the case of 15 bits, the bit swapping pattern is (15!
-1) There are several possibilities, but you can select any five of them and create a program to perform such bit swapping. The larger the number of bit permutations, the longer the execution time, but the more difficult the conversion pattern is to predict. Therefore,
It is preferable to select a pattern in which all 15 bits are replaced.

Table 33 shows an example of a bit permutation pattern corresponding to random number B.

Table 33 Next, the actual conversion of a card number using the bit replacement pattern described above will be explained using an example in which the random number A is 14297, the random number B is 2, and the issued serial number n is 635. In this case, the -next card number X is.

From X=A+n, it becomes r14932J. If this is expressed in hexadecimal, it becomes r3A54J, and if expressed in binary, it is r
OOllxlOOolololoo”. If this secondary card number is converted using the third conversion pattern corresponding to random number B=2, it will be as shown in Table 34 below, and the secondary card number will be rlE13J in hexadecimal and r7699J in decimal. .

Table 34 On the other hand, the process of calculating the card issuing serial number from the card number performed in the flow of FIGS. 101 and 102 to 108 (steps 52151, 52161, 52
181.52201, 52221.52241, 522
61, 52281) etc., please refer to step 52 above.
This is the reverse operation of 707 and 52708, first converting the card number to binary number, then inversely converting each bit using the conversion pattern determined by random number B (see Table 34) to find X.
By subtracting a random number A from that X, you can obtain the issue serial number.

Next, each unit control device of the pachinko machine 100, issuing machine 200, and payment machine 300
The common control procedure regarding data transmission in the 166th
This will be explained using FIGS.

When a reset pulse is supplied from the reset circuit 555 to each controller 190 (or 290, 390), 551, 553, each controller clears its internal register and internal RAM, and the data transmission controller 551 clears the unit controller 190. Also clears the unit memory 550 for parallel communication with (
Step 5 IOI, 5201, 5301). Then, the data transmission controller 551 connects the unit memory 550
Appropriate data is written to a predetermined address (27FF) within (step 5202). Then, the unit memory 550
raises the level of the signal INT output from a predetermined terminal. This signal INT is used as an initialization signal by the unit controller 190 (290, 3
90).

On the other hand, the unit controller 190 (290°390
) clears the I10 port after clearing the internal register and RAM. Step S102) monitors whether the initialization signal INT from the unit memory 550 has risen (Step 5103), and the signal IN
When T starts up, machine number setting device 171 (205, 35
After reading the value set in 2), the terminal serial number and channel number are calculated from the device number (steps 5104 and 5105). Then, the channel number is written into the transmission data area SDA of the unit memory 550 (step 5106).

The data transmission controller 551 reads the channel number in the transmission data area SDA and determines whether it is rQJ or not (steps 5203, 5204), and if it is no longer rQJ due to writing by the unit controller, it latches the read channel number. LT3 (5
63), and then writes a command to latch LT2 (562) that specifies the page configuration in the packet memory used for data transmission and reception (step 5205).
゜5206). Then, the network controller 55
3 reads the channel number in the latch LTa and stores it in the internal RAM to determine its own address in the lower layer network (step 5302), and then the next latch LT2
The page configuration of the packet memory is read from within and stored (step 5303). This determines the configuration of the send/receive page.

After that, the data transmission controller 5517'' writes the page number to be used for next data reception into the latch LT2 (step 5207), and this becomes a reception permission command to the network controller 553. It is checked whether there is a page number, and if there is a page number, it is determined that there is reception permission and step 5305
(Figure 167) Move to the following transmission process (Step 5)
304), and in step 5305, the network controller 553 determines whether there is a transmission request from the NAU 530. When there is a transmission request, it sends a message to NAU that reception is possible, receives the packet sent from NAU, and removes unnecessary parts such as the source address from the received packet. Convert the data part to parallel data and write the received data to the specified page in the packet memory 552 (step 8
306-5308). After that, the network controller 553 writes the received command to the latch LT1 (561) (step S309).

Then, the data transmission controller 551 releases the latch L.
After reading the TI data and confirming that there is a received command, the received data is read from a predetermined page of the packet memory 552 and temporarily stored in the working area of the unit memory 550 (steps 5208, 5209). Data transfer controller 551 then writes the next received page to latch LT2. This becomes a command to permit reception of the next packet (step 521o).

This command (receiving page) is the network controller 5
53 and stored (step 5310
), 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).

That is, the data transmission controller 551 performs step 5.
Once the received page has been written to latch LT2 in step 210, the command register CR2 in unit memory 550 is checked to indicate "O", that is, unit controller 190
After confirming that there is no other transmission request for (290, 390) (step 5211), the write position in the reception data area is determined from the reception packet type, and the reception data in the working area is transferred to the unit memory. Move to data area (steps 5212 and 5213)
. Then, the received packet type name is written in the command register CR2 of the communication area (step 5214).

Then, the unit controller 190 (290°39
0) monitors the command register CR2 and determines that the packet type has been written, it starts processing corresponding to that packet type (steps 5107, 51
08). Then, when the processing is completed, the command register CR2 is cleared (step 5109). On the other hand, the data transmission controller 551 performs step 5214.
After writing the received packet type name to command register CR2, it is determined whether the packet is an ``initial value setting'' packet, and if it is an ``initial value setting'' packet, scheduled data transmission is started. Set a fixed timer (1 second) for (steps 5215, 5216)
). If the received packet is not an "initial value setting" packet, it is determined in step 5217 whether it is a "line test" packet. If it is a ``6 line test'' packet, the response ``A CK'' is sent in step 8218.
Processing is executed to send the packet, and if the packet is not a ``line test'' packet, it moves directly to other processing.

Next, the packet transmission process will be explained using FIG. 168.

The unit controller 190 (290, 390) is
When a packet transmission factor such as "card-in" or "interrupt 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, create the packet head (step 8
121). Then, check the command register CRI in the unit memory to see if another transmission packet has already been entered, and if there is no other transmission packet, write the name of the packet type to be transmitted in the command register CRI, and then Set a transmission timer (steps 8122-5124). Writing the packet type name to the command register CRI becomes a transmission command to the data transmission controller 551. Meanwhile, the data transmission controller 551 monitors whether the packet type has entered the command register CRI (step 5221).
), when it learns that the packet type has been entered, it reads the transmission data corresponding to the transmission packet type from the transmission data area in the unit memory, and stores it in the packet memory along with the address (fixed) of the NAU that is the transmission destination and the number of bytes of transmission data. (step 5222, 5
223).

Thereafter, data transmission controller 551 writes a command to transmit data in page O to latch LT2 (step 5224).

Then, this becomes a transmission command to the network controller 553, and the network controller 553 checks whether there is a transmission command. If there is a command, it waits for the transmission right to be acquired on the network, and if the transmission right is acquired, it receives transmission permission from the NAU. Wait for (step 8321
~5323).

Then, after transmitting the data in page 1 of the packet memory, the transmission result is written to the latch LTI (steps 5324, 5325). In response to this, the data transmission controller checks the latch LTI to check whether the transmission was successful or not, and if it fails, repeats the above transmission process up to three times (steps 5225 and 5226).

Then, the transmission result is written to the status register STR in the communication area of the unit memory, and then the command register CRI is cleared (steps 5227 and 5228).
).

On the other hand, the unit controller 190 (290°390
) continuously monitors the command register CRI after setting the transmission timer in step 5124 (step 5125), and in step 5228, the data transmission controller 551 sets the command register CRI.
If a time-over occurs before the pachinko machine controller 195 is cleared, the common signal (watchdog pulse) of the display data sent to the pachinko machine control device 195 is fixed at a low level.
Stop the watchdog pulse (step S12)
7). As a result, a reset is performed by the reset circuit 555, and the process proceeds to step S, LO1.

S20↓, 5301 initialization is performed.

Next, the scheduled data transmission process will be explained using FIG. 169. The data transmission controller 551 checks the fixed timer set in step 5216 (step 5231), and when one second has elapsed, steps 52
32, all data in the transmission data area of the unit memory 550 is read out and written into the working area (step 5233). Next, compare the data in the transmission data area again (step 5234), and if it is successful, check the command register CRI to see if there is another transmission request (packet type) to the data transmission controller (step 5235). ), reads data from the working area and writes it to the packet memory 552 as transmission data (steps 5237, 5238
). Also, at this time, the destination address (NAU), the length (number of bytes) of the transmission data, and the packet type name are written in page 1 in the packet memory along with the transmission data. Note that in step 5235 the command register CRI
If there is another packet name in , that packet is transmitted (S236) and then the process advances to step 5237.

The reason why the data match is determined in step 5234 is that when the unit controller rewrites 1 byte of the 2-byte data part in the transmission data area and sends scheduled data, undefined data is detected. This is because it will be sent. By checking whether the data match, it is possible to determine whether the data in the transmission data area is fixed.

After writing the transmission data (step 5238).

The data transmission controller 551 writes a command to transmit data in page 1 to latch LT2 (step 523
9).

Then, this becomes a transmission command to the network controller 553, and the network controller 553 checks whether there is a transmission command. If there is a command, it waits for the transmission right to be acquired on the network, and if the transmission right is acquired, it receives transmission permission from the NAU. Wait for (step 8331
~5333).

Then, after transmitting the data in page 1 of the packet memory, the transmission result is written to the latch LTI (steps 5334, 5335). In response to this, the data transmission controller 551 checks the latch LTI to check whether the transmission was successful or not, and if it fails, repeats the above transmission process up to three times (steps 5240, 5241).

Next, a description will be given of the operating state of the pachinko machine reflected in the operating information of the transmitted operating data shown in Table 1, the manner of transition thereof, and the control method of the pachinko machine using this operating state and card state.

In the system of this embodiment, the operating state of the pachinko machine is reset state 5SI as shown in FIG. 170(A).
O, a forced termination state 5Sll in which no games can be played, a free state 5S12 open to all players, a gaming state 5S13 in which a game is being played by a specific player,
There are six states: a suspended state 5S14 in which the gaming right is reserved for a specific player and the game is stopped, and a stopped state 5S15 in which the game is stopped after a predetermined number of prize balls have been ejected.

Of these, only the free state 5S12 and the suspended state 5S14 are states in which cards can be accepted, and the reset state 5S
IO as well as forced termination state 5Sll, abort state 5S1
5 is a state in which cards cannot be accepted. In the suspended state 5S14, only the card that caused the suspension is accepted.

On the other hand, in the gaming state 5S13, a specific card is held inside the pachinko machine.

Each of the above states can transition in the direction shown by the arrow in the figure.
No other state transitions are allowed to occur.

That is, the reset state 5810 transitions to the forced termination state 5S11 only when an "initial value" packet is received. However, if the "unit recovery" packet is received in the reset state after the power outage has been recovered, the pachinko machine returns to the state it was in before the power outage occurred. From the forced termination state 5S11, it is possible to transition only to the free state 5S12, and this transition occurs when a "store opening" packet or a "forced termination cancellation" packet is received. Furthermore, it is possible to shift from the free state 5S12 to the gaming state 5S13 or the forced termination state 5SII, and the gaming state 5S13 can be changed by receiving a "card-in" packet.
When a "closing" packet or a "forced termination" packet is received, the state shifts to forced termination state 5SII.

Then, in the game state 5S13, when the end switch is turned on or the zero state occurs, the state returns to the free state 5S12, and when the interrupt switch is turned on during the game, the interrupt state 5S1 is returned.
4, when the stop condition is satisfied, the state shifts to the stop state 5515. 7 Interrupt state 5S14 or stop state S S
]-5 to the free state SS 1.2 when a "suspension end" packet (when payment is made at the payment machine) or a "cancellation cancellation" packet is received, and the state is suspended.
When the card that caused the interruption is reinserted in step 14, the game returns to the gaming state 5S13.

Furthermore, in all states of the free state 5S12, the gaming state 5S13, the suspended state SS14, and the abort state 5S15, when a "forced termination request" packet is received from the management device 400, the process immediately shifts to the forced termination state 5511.

Moreover, the system of this embodiment has a test mode that enables games with a test cart, and even in this mode, when the entire system is online and the power is turned on, the state transition is almost the same as that shown in FIG. 170 (A). I do. FIG. 170(B) shows a state transition diagram of the pachinko machine in the online test mode. In this case, the state transition conditions are somewhat different from those in the normal operation mode.

That is, when the test switch is pressed in the free state 5812 of the normal operation mode and a regular test card is inserted, the control space is switched and the state of the pachinko machine shifts to the game state 5S13' of the test mode. Even in the test mode, it is possible to shift to a stopped state or a suspended state. However, it is possible to transition from the gaming state 5S13' to the free state 5SI2 when the end switch is turned on or when a return to zero occurs, and the stop state 5S15'
The transition from 5S12' to free state 5S12' is not due to reception of a "cancel cancellation" packet but by turning on the end switch, and when the original test card or another test card is inserted in suspended state 5S14', test game state 5S13' is entered. When the end switch is pressed in the suspended state 5S14', the program returns to the normal free state 5S12. The control space also switches at the same time as the transition from each state in the test mode to the free state 5S12. In other words, the mode is not the test mode but the normal operation mode, and if you want to play with the test cart again, you need 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, the unit control device! 180 is memorized, and when the termination switch is turned on, each state S S
13'5S14', forced termination state 58 from 5S15'
It is set to move to 11.

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

FIG. 170 <C> shows the state transition in the test mode when one of the pachinko machines is powered on independently and disconnected from the management device 400, offline.

When offline, the pachinko machine initializes when the power is turned on, and then enters a standby state 5S2 where it waits for the test switch to be turned on or for a "line test" packet from the management device.
It becomes 0. Here, when the test switch is turned on and a regular test card is subsequently inserted, the game state shifts to test mode gaming state 5SI3'. After that, Fig. 170 (
Suspended state 5S14' and discontinued state 5SI under the same conditions as B)
5', and when the termination switch is turned on in each state, the process returns to the standby state 5S20.

Note that when a "line test" and "parameter initial value setting" packet is received in the standby state 5S20, a transition is made to the forced termination state 5SII of the normal operation mode.

The unit control device [180] of the control unit 160 of the pachinko machine of this embodiment controls the pachinko machine and the cart reader and communicates with the management device 14.00 while referring to the operational status and card status of the pachinko machine. This reduces the burden on the management device, avoids malfunctions due to communication errors, maintains control independence for predetermined processing, and enables prompt responses to player actions, etc. .

Hereinafter, processing in the unit controller 190 using the pachinko machine operating information and cart status will be explained.

First, before explaining the processing by the unit controller ↓ 90, first we will explain the mutual data transmission and mutually related operation procedures between the unit controller 190, the pachinko machine control device 195, and the card reader control bag @188.
This will be explained using FIGS. 71 to 188.

FIG. 171 shows the procedure from initialization to store opening.

Note that communication between the card reader controller 188 and the unit controller 190 is performed using a function code, and the function code sent from the unit controller 190 to the card reader controller 188 is a code that is compared with the magnetic data read from the card. ``Initial value setting'' function to give the card reader the date code and identification code for the purpose of ``Card acceptance'' function to allow the card reader to accept cards; "Card not accepted" function to command to cancel, "Card eject" function to command to eject the card, "Reload" function to command to reread the magnetic data of the card, the function sent just before. A "resend request" function requests the resending of the code, a "status request" function requests the transmission of a bit indicating the card reader status held in the card reader controller, and a "resend request" function requests the resending of the card in the punch hole forming area. 8 of the "return zero" function that gives a command to drill the return zero hole PH4, which indicates that the number of balls and amount has become zero.
Various types of directives are available.

On the other hand, the function codes from the card reader controller 188 to the unit controller 190 include a "card number transmission" function that sends the card number read by the card reader to the unit controller;
``Test card J function'' that informs the unit controller that a test card has been inserted; ``Initial value request'' function that requests initial values such as date and identification code at the time of reset; "Normal end" to notify the unit controller
conversely, an "abnormal end" function that indicates that the process did not end normally, and a "self-contained" function that indicates that the card reader controller has determined that the inserted card is fraudulent and has detected the card of its own volition. "Eject" function, "Resend request" function that requests the unit controller to resend the function code sent just before, and "Status" that sends the card reader status in response to a "Reload" request or "Status request." There are eight types of "Send" functions.

However, the communication between the card reader controller 188 and the unit controller 190 does not involve sending a function code unilaterally, but first the sending side sends a call signal (challenging code) ENQ, and the receiving side sends an authorization response A.
The function code is sent after receiving CK.

In FIG. 171, when a reset is entered due to power-on, the unit controller 190, card reader controller CPU2. The pachinko machine controller CPUI is
Initialize internal registers, etc. (steps 5401, 5
501, 5601).

When the initialization is completed, the pachinko machine controller CPU
enters a state of waiting for input of detection signals from each sensor or switch (S410).

The unit controller 190 reads the set value from the machine number setting device 171, calculates the serial number and channel number,
Store in unit memory 550 (step S 602
). Then, it waits for a "line test" packet to be sent from the management device (step 5603).

Next, upon receiving the "initial value setting" packet, it starts receiving control from the card reader and determines whether there is a call signal ENQ from the cart reader controller CPU2 (
Steps 5604-5606).

On the other hand, upon completion of the initialization, the card reader controller CPU 2 transmits a call signal ENQ to the unit controller 190 and waits for a response signal ACK thereto (steps 5502 and 5503). Note that before transmitting the call signal ENQ, if there is no ACK, it is determined whether ENQ is present or not, considering the case where there is a call from the unit controller to transmit an "initial value setting" function or the like (step 5504). Then, if there is an ENQ, it transmits an ACK and waits for reception of a function code (steps 5504 to 5506).

When the two-nit controller receives the transmission of the call signal ENQ from the card reader controller in step 5502 in step 8606, it returns a response signal ACK (step 5607).

Then, the card reader controller sends an "initialization request" function (step 5511). The unit controller receives this and starts sending control to the card reader, first sending an "initial value setting" function containing the date and identification code (step 8608).
~5610).

When the card reader controller receives this initial value, it stores the date and identification code in its internal RAM, and then returns a "normal completion" function (steps 8512 to S
5.14).

When the unit controller receives the "normal end" function (step 5611), it waits for the "opening code" packet from the management device, and when it receives this, it scrolls the analog display 163 to display a customer waiting display, and also displays the unit memory The unit controller changes the operation information of the card to "free" (steps 5612 to 5614), and then sends a "card ready" function to the card reader controller (step 56).
15).

When the card reader controller receives this, it first opens the shutter and then starts card insertion detection (steps 8515 to 5517). Then, a "normal end" function is returned (step 8518), and the system waits for a function from the unit controller or insertion of a card (step 5520). On the other hand, when the unit controller receives the "normal end" function from the card reader, it enters a state of waiting for a packet from the management device or a function from the card reader controller (step 5620).

FIG. 172 shows the operating procedure when a card is inserted into the card reader.

When the card reader controller CPU2 is in the function or card waiting state (step 5520),
When a card is inserted, this is detected by the insertion detection switch 808, and the motor is driven to take the card into the interior (step 5521). Next, check the punch hole and security code, read the magnetic data,
Inspect the year, month, date, and identification code (steps 8522 to 5)
525). If the card is normal, the function containing the read card number is sent to the unit controller, and the shutter is closed (step 5526).
, 5527).

When the unit controller 1.90 receives the card number, it sends a "card-in" packet to the management device 400, confirms the existence of the card with an "ACK" packet, and changes the operating information to "playing" (step 5621
~5625). Then, the status display lamp 162 is turned on to notify the outside that the game is in progress, and then the ball launcher 103 is enabled to be driven, and the system waits for the input of detection signals from each sensor (steps 5624, 5625).

During this time, the pachinko machine controller CPUI is in a state of waiting for detection signals from the sensors and switches (step S41.
O), and after starting the launch control of the batted ball launcher, when detection signals from the launch sensor 5NS5, safe sensor SNS2.5NS3, foul sensor 5N34.7, and out sensor 5NSI are detected, this is notified to the unit controller (steps 5411 to 5416). ). However, at this time, returned balls and fired balls are distinguished from each other based on the difference in detection time of the firing sensor, and the number of returned balls is outputted as a foul ball detection signal (step 5416). On the other hand, when the unit controller receives the detection signal from the sensor, it performs calculations according to the type of signal to determine the number of balls being played and updates the unit memory (steps 8626 to 5630), and also receives the detection signal from the purchase switch 11.3. When received, the calculation is performed to reduce the unused amount of the card and increase the number of balls held (step 5631).
.

FIG. 173 shows the operating procedure when the interruption switch 114 is turned on during a game.

When the unit controller 190 detects that the interrupt switch is turned on, it stops controlling the batted ball firing device 103 and transmits an "interrupt switch" packet to the management device 400 (steps 8632 to 5634). Then, when "ACK" is returned from the management device, the operation information in the unit memory 550 is changed to "R Interrupted", and the game status display lamp 123 is blinked to indicate an interruption. , sends the “card ejection” function to the card reader controller (steps 8635 to 5637).
).

When the card reader controller receives this function, it opens the shutter and reverses the motor to eject the card, sends a "normal completion" function to the unit controller (steps 8528 to 5531), and waits for card insertion or function (steps 8528 to 5531). Step S
532).

On the other hand, after the unit controller receives the "correct ftH completed J function" (step 5638), it waits to receive a packet or function (step 5620).

Thereafter, when the interrupted card is inserted into the card reader, the card reader controller CPU 2 takes in the card, checks and sends the function, and closes the shutter according to the same procedure as steps 8521 to 5527 (steps 8533 to 5538). ). On the other hand, the unit controller checks whether the received card number and the card number in the unit memory are the suspended card, and if they match, sends a "Paper Suspended Card In" packet to the management device (step 8639-5641
). When the response "ACK" is received, the operating state is changed to "Playing J", the game state display lamp is changed to a continuously lit game display, and the control of the batted ball launcher is started (steps 8642 to 5644). .

By the way, in the system of this embodiment, when the suspended card is settled at the payment machine, the suspended pachinko machine is released. Therefore, step 86 in Fig. 173
When a "Suspension End" packet is sent from the management device while waiting for 20 packets or functions to be received, the unit controller changes the operating information to "Free",
After changing the lamps 123 and 163 to the customer waiting display, the display waits again for packet or function reception (step 56).
2Q).

FIG. 174 shows the operating procedure when the termination switch 115 is turned on.

When the unit controller 190 detects that the end switch is turned on, it stops driving the batted ball firing device 103 and then sends a "Pa end switch" packet to the management device 400 (
Steps 8645-5647). And the response”
ACK" is received, the operation information is changed to "free", the game status display lamp 1-23 is turned off, the analog display 163 is scrolled to change to the customer waiting display, and the "card ejection" function is changed to "free". Send to the reader controller (steps 8648-5650).

When the card reader controller CPU 2 receives the function, it opens the shutter, drives the motor to eject the card, and then returns the "normal end" function to the unit controller (steps 8539 to 554).
2). Then, it waits for card insertion or function reception (step 5520).

On the other hand, upon receiving the "normal end" function from the card reader controller, the unit controller waits for a packet from the management device or a function from the card reader controller (step 5651,
5620). During this time, the pachinko machine controller is waiting for input of the sensor detection signal (step 5410).
).

Next, we will explain the procedure in the case where the number of balls held and the amount of money are both rQJ during the game shown in Fig. 172.
This will be explained using Figure 75.

As a result of the calculation of the number and amount of balls in steps 5626 to 5631, it is determined whether the number of balls and amount are rQJ, and if rQJ, the drive control of the batted ball launcher 103 is stopped and a 10 second search timer is turned on ( Steps 5652-56
54). Then, it is checked whether the number of floating balls existing in the game board (number of balls fired - number of balls collected) has become "O", and it is further determined whether the search timer has elapsed for 10 seconds (steps 5655, 5656). ), if the number of floating balls reaches rQJ or the search timer elapses for 10 seconds, the control device 4
．． Send a “return to zero” packet to OO (step 56
58). Also, if there are floating balls within 10 seconds after the firing device stops, check to see if there are safe balls, foul balls, or out balls, and if there are, go to steps 8626 to 5633.
The process returns to step S657 and calculates the number of balls again (step S657).

When an "ACK" packet is received from the management device, the operation information is changed to "free", the lamps 123 and 1.63 are changed to the customer waiting display, and the "return to zero" function is changed to the card reader controller. Send to (
Steps 8659-5662).

When the card reader controller CPU 2 receives this function, it punches a hole at the return hole punching position of the card, opens the shutter, and ejects the card (steps 8543 to 3546).

Then, it sends a "normal end" function to the unit controller 190 and waits for card insertion or function reception (steps 5547 and 5520).

On the other hand, when the unit controller receives the "normal end" function, it enters a packet or function wait state (steps 5663 and 3620).

FIG. 176 shows a processing procedure when a stopped state occurs during the game shown in FIG. 172.

After calculating the number of balls and the amount in steps 5626 to 5631, a stop calculation is performed, and it is determined whether the calculated value has reached the stop number (steps 5664, 5665).

When the number of hits reaches the number of hits, the drive control of the batted ball launcher 103 is stopped and the management device 400 sends the message "stop hits".
Send the packet (steps 5666.5667).

When the "ACK" packet is received from the management device, the operation information is changed to "stopped", the game status display lamp 123 is turned off, and the analog display 163 is turned off (
(blinking drive) (steps 8668 to 5670)
. Thereafter, a stop sound is output from the speaker 166, and then a "card not accepted" function is transmitted to the card reader controller CPU2 (step 56).
71°5672).

When the card reader controller receives this function, it opens the shutter to eject the card, and then closes the shutter to prohibit card insertion. Then, it transmits the "normal end" function to the unit controller 190 and waits for reception of the function (steps 5551 to S556). Then, the unit controller receives the "normal end" function and enters the wait state (steps 5673, 5674).
.

After that, when the management device sends a "cancellation cancellation" packet, the unit controller changes the operating information to "free".
, changes the lamps 123 and 163 to the customer waiting display, and then sends the "Card Receivable" function to the card reader controller (steps 8675 to 8678).
).

Then, the card reader controller opens the shutter, starts card insertion detection, sends a "normal end" function (steps S557 to 3560), and waits for the function or card insertion (step 5520).
). On the other hand, the unit controller is "normally completed"
Receive the function (step 5679) and wait for packet or function reception (step 5620)
). During this time, the pachinko machine controller CPU1 is in a state of waiting for input of detection signals from each sensor and switch (step 5410).

FIG. 777 shows the processing procedure for forced termination. When a "forced termination" packet is sent from the management device @ 400 in the packet or function reception waiting state (step 5620) in FIGS. 171, 174, 175, and 176, the unit controller 190
Change the operation information to "forced termination" and turn on lamps 123 and 16.
3 is turned off and the man-hour and amount display are cleared to "O", the "Card not accepted" function is sent to the card reader controller CPU2 (step 8681).
~684).

Then, after receiving the function, the card reader controller determines whether or not a card exists in the card reader, and if so, opens the shutter and ejects the card, and if there is no card, continues to step 85.
The process moves to step 65, closes the shutter, transmits the "normal end J function, and waits for reception of the function" (steps 8561 to S567).

On the other hand, when the unit controller receives the "normal end" function from the card reader controller, it waits to receive a packet (steps 8685 and 8686).

After that, when a "forced termination release" packet is sent from the management device, the unit controller changes the operation information to "free", changes the lamps 123 and 163 to the customer waiting display, and then sends the card reader controller to "card card". "Ready to receive" function (steps 8687 to 56)
90).

Then, the card reader controller opens the shutter, starts card insertion detection, sends a "normal completion" function (steps 8568 to 5571), and then waits for the function or card insertion (step 5520).
). On the other hand, the unit controller displays "Normal completion J".
Receive a function (step 5691) and wait for packet or function reception (step 5620)
). During this time, the pachinko machine controller CPU1 is in a state of waiting for input of detection signals from each sensor and switch (step S410).

FIG. 178 shows the procedure for unit recovery processing after a power outage occurs.

When the power outage is restored, each controller CPU↓, CP
U2 and 190 initialize their internal registers, etc. (steps 5421, 5581 and 5701), and then the unit controller reads the machine number from the machine number setter 171, calculates the serial number and channel number, and stores them in the unit memory 550. 9 line test'' packet is stored (steps 5702, 5703).

On the other hand, after initialization, the pachinko machine controller CPUI waits for input of detection signals from sensors and switches (step 5410).
), and the card reader controller CPU2 is the 17th
Steps 8502 to 85 during power-on reset in Figure 1
Similarly to 06, after transmitting the call signal ENQ, it is determined whether the signal ACK from the unit controller and ENQ have been received, and when ENQ is received, it returns ACK and waits for function reception (steps 8582 to 8586).
).

When the unit controller 190 receives the "line test" packet in step 5703, the unit controller 190 subsequently receives the "line test" packet from the management device 4.
It receives the "unit recovery data" packet sent from OO, returns the data in the unit memory to the state before the power outage, and returns an "ACK" packet (steps 5704, 5705). Then, after turning off the firing drive control regardless of the state before the power outage, if the previous operating state was during gaming, the operating information is set to "free" (steps 5706 and 5707). Next, a "restart" packet is sent from the management device, so when it is received, transmission/reception control with the card reader controller is started, and a call signal ENQ is first transmitted (step 8).
708-5710).

If a response signal ACK is received, the "initial value setting" function is sent to the card reader controller (steps 5711, 5712).

When the card reader controller receives the "initial value setting" function, it stores the date and identification code, and then returns the "normal completion" function. Upon receiving this, the unit controller controls the lamp 123 according to the operation information.
, 163 are displayed (steps 5713, 5714).
. In other words, the original operating state returns to the original display state except for "playing". Next, the unit controller transmits a function according to the operation information (step 5715).
). In other words, if it is "free", you can use the "reload" function of the card, and if it is "suspended", you can "accept card".
function and, at other times, a ``card not accepted'' function.

Then, the card reader controller executes the process corresponding to the sent function, determines whether a card exists in the card reader, and if there is no card, sends a "status" function (
Steps 8590-5592). Further, if a card exists in the card reader, the steps 8522 to 5
After determining the authenticity of the card corresponding to No. 25 and sending the card number into the function, step 5
The system enters a waiting state for function reception or card insertion corresponding to 520.

On the other hand, upon receiving the "status" function from the card reader, the unit controller performs step 562.
0, and when a function containing a card number is received, a "card-in" packet corresponding to step 5622 is sent to the management device, and then steps 8623 to 8623 in FIG. 172 are sent.
Game processing is started according to the procedure of S63↓.

In this way, if the operating status before the power outage was "Playing", the card is reread and checked before the game is resumed, so incorrect data (
In particular, it is possible to avoid confusion caused by the transmission of card numbers) and improve reliability, and also to eliminate fraudulent acts such as card removal during power outages.

Next, a specific control procedure in the unit controller 190 will be explained using FIGS. 179 to 194.

Processing in the unit controller 190 includes initialization tasks after power-on or reset, and subsequent
There are 0 types of main tasks, timer interrupt processing based on interrupt signals received from the timer every millisecond, and serial interrupt processing that occurs when transmitting and receiving functions to and from the card reader controller 188.

Of these, 10 types of main tasks are repeatedly executed in real-time processing. Here, the 10 main tasks are a packet reception task, 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 10 types of output control tasks.

FIG. 179 shows the procedure for timer interrupt processing, and FIG. 180 shows the procedure for serial interrupt processing.

In the timer interrupt processing shown in FIG. 179, first the hot code (A55A) in the unit memory is checked (procedure P
l) If there is an abnormality, a reset is applied, and if it is normal, the timer for the timer interrupt is reset (procedure P2). Next, after updating the timer prepared in the internal RAM of the unit controller 190, the data transmission controller sets rFFHJ every time it is transmitted and checks the watchdog counter in the unit memory, which is decremented by 1 every 20m5. (Procedure P3.P4
). Here, if the watchdog counter is rQJ, it is determined that the data transmission controller has gone down, the common signal for driving the segment type display is fixed, and a reset is performed by the reset circuit 555.

If the watchdog counter is normal, the next sensor and switch detection process (see Figure 181 (A)) is executed, and then the switch detection signal invalidation process (Figure 181 (B)) is executed.
)) is executed (procedures P5 and P6).

After that, the amount and number of balls data are read from the unit memory and converted into codes, and the amount display 111
, segment data and common data for the ball number display 112 are formed and output, and the amount and number of balls are dynamically displayed (procedures P7 to P8).

On the other hand, in the serial interrupt processing shown in FIG. 180, when an interrupt comes from the transmit buffer or receive buffer inside the unit controller 190, it is first determined whether it is a receive interrupt or not, and if it is a receive interrupt, 1 byte of receive data is sent. Move to internal RAM (procedure P1↓, PI3). In addition, if the serial interrupt is an interrupt from the transmission buffer, execute upper byte transmission processing in which 1 byte of transmission data is converted to serial data by shifting the transmission buffer and output (procedure P). 3.PI3). Note that the above serial interrupt is such that an interrupt signal is automatically input to the CPU when transmitted/received data enters the reception buffer or the transmission buffer.

Sensor and switch detection processing during the timer interrupt processing (FIG. 179) is performed according to the procedure shown in FIG. 181(A).

That is, first, the purchase switch 113 and the interrupt switch 11 are activated.
4. Read the on/off states of the payment switch 115, test switch 179, and call switch 165a and compare with the previous state (procedures P51 and P52). Comparison of states is performed by a logical operation such as exclusive OR, for example. This allows you to easily know if the condition has changed. 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, check whether the sensor is being detected (procedure P54).
In other words, it is determined whether or not the game is being played, and if the sensor is being detected, the firing sensor 5NS5 and the safe sensors 5NS2 and 5NS are activated.
3. Read the status of foul sensor 5NS4 and out sensor 5NSI and compare with the previous status (procedure P55)
．． P56).

If there is a sensor that has newly turned on, the on state of that sensor is saved in the internal RAM (procedure P
57).

After that, it is determined whether or not the drive control of the batted ball launcher 1103 is being performed, and if it is being controlled, jumps to procedure P60, and if it is not being controlled, the ON state of the firing sensor saved in the RAM is invalidated in procedure P57. (Procedures P58 and P59). Then, if the data saved in the RAM is checked and the firing sensor is on, a counter provided in the RAM for counting the number of floating balls is incremented (procedures P2O and P61). Also, if the firing sensor is off, proceed to the next procedure P6 without incrementing the number of floating balls.
Proceed to step 2 and determine whether the number of floating balls is "O". here,
If the number of floating balls is "O", disable the ON state of the first safe sensor 5NS2 saved in RAM (P76),
If it is not "O", check whether the first safe sensor is on or not, and if it is on, subtract the number of floating balls (procedures P63 and P64).
), and if the first safe sensor is off again, the process directly proceeds to procedure P65, and it is again determined whether the number of floating balls is rQJ.

If the number of floating balls is "○", then the second number saved in RAM is
Procedure P to disable the on state of safe sensor 5NS3
77), if it is not "O", check whether the second safe sensor is on or not, and if it is on, subtract the number of floating balls (procedure P66).
, P67), and if the second safe sensor is off again, the process directly proceeds to procedure P68, and it is again determined whether the number of floating balls is "0" or not. Here, if the number of floating balls is "0", disable the on state of the foul sensor 5NS4 saved in RAM (procedure P78), and if it is not rOJ, check whether the foul sensor is on or not, and if it is on, subtract the number of floating balls. After (procedure P69.P2O), if the foul sensor is off again, the process directly proceeds to procedure P71, and it is again determined whether the number of floating balls is "O" or not. Here, if the number of floating balls is rQJ, invalidate the on state of the out sensor 5NSI saved in RAM (procedure P79), and if it is not "ro", check whether the out sensor is on or not, and if it is on, subtract the number of floating balls ( After performing procedures P72 and P73), if the out sensor is off, proceed directly to procedure P74, and if either safe sensor 1 or 2 is valid, instruct the output reservation of the hit sound and the lighting of the safe ball indicator lamp, and then The on-count counter for the valid on-state sensor saved in the RAM is incremented (+1) (procedure P75).

Thereafter, the switch invalidation process shown in FIG. 181(B) is executed. In this process, first check whether the operating state is "gaming", "If you are playing, disable the on state of the test switch saved in RAM" (P81, P82), and if it is other than "gaming", press the interrupt switch 114. Purchase switch 113
Disable the on state of the card (procedure P83), then determine whether the card state is "return to zero", and if it is "return to zero", disable the on state of the saved purchase switch, interrupt switch, and end switch 115 (procedure P84°P85).

As mentioned above, the control of the pachinko machine by the unit controller of this embodiment incorporates the concept of floating balls,
The number of winning balls, out balls, and foul balls subtracted from the number of launched balls is considered to exist on the game board as floating balls, and winning balls, etc., where the number of floating balls is less than rQJ are detected. If there is, it will be invalidated. This eliminates erroneous detection signals due to noise, etc., and improves the accuracy of calculation of the number of balls.

Next, the initialization task and the ↓0 types of main tasks processed in real time by the unit controller 190 will be described.

FIG. 182 shows the initialization task.

When the unit controller 190 receives a reset signal from the reset circuit 555 at power-on or when the watchdog pulse disappears, it starts an initialization task, first clears the internal RAM and writes a check code at a predetermined address. Initial values are set in the internal registers, and the I10 port is set in a predetermined initial state (procedures P91 to P93). Then, after setting each of 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 (procedures P94 and P95), and then the INT When the signal rises, the setting number of the unit number setting switch 171 is read, the serial number and channel number are calculated, and after writing them to the transmission data area of the unit memory, a "line test" packet is sent from the management device 400. (Procedure P96~)
P98) and check the test switch 179. And if you receive a “line test” packet, “
After returning the "ACK" packet to the management device, the process moves to the main task, and if the test switch is turned on before receiving the "line test" bucket, the test mode flag is set, and then the process moves to the main task.

FIG. 183 shows the processing procedure of the "packet reception task" among the ten types of main tasks of the unit controller 190.

In this task, first check the unit memory 550 to determine whether a packet has been sent from the management device 400, and if there is no received packet, check whether it is waiting for an "A CK" packet to be returned (procedure PIO
I, P2O3), and if no, procedure PI
Return to OI and repeat the above steps, and in procedure P2O3.
When waiting for an A CK packet, the process moves to 1 procedure P2O3, and the procedure P in the packet transmission task in Figure 187 is executed.
2. Read the ACK wait timer set in S5.

Then, it checks whether the timer has timed out or not, and if a timeout has occurred, it sets the ACK reception error flag in the internal RAM (procedure P2O
3, P2O3). This flag is referenced in the error control task (FIG. 188), which will be described later.

On the other hand, when it is determined that there is a received packet in the above procedure Plol, the type name of the received packet is read from the unit memory to the internal RAM, and it is "NAK".
First determine whether it is a packet (Procedure Pi○6.P2O
3). If it is "NAK", set the NAK flag prepared in RAM (procedure P2O3), and if it is not "NAK", continue with procedure P.
Proceeding to 2O3, it is determined whether the received packet is registered. If the packet is unregistered, procedure P
At IIO, the packet type name in the command register CR2 of the unit memory is cleared to "O" and the process returns to procedure PIO. By clearing the command register CR2, it is assumed that no packet has been received.

If it is determined in procedure P2O3 that the received packet has been registered, it is determined which packet it is in procedures Pill to P125, and processing is performed according to the type of packet found (FIGS. 184 (A) to (N) )).

FIG. 184(A) shows the procedure of the ``initial value setting'' packet reception process in the packet reception task.

Upon receiving the "initial value setting" packet, the unit controller 190 copies the hot code to the corresponding column in the reception data area of the unit memory 550, and similarly copies the hot code to the transmission data area (procedures P2O3 and P2O3).
2O3). By writing the head portion of the transmitted packet into the reception data area and the transmission data area, it is possible to simplify the creation of the packet head in the transmission data area by the unit controller. Next, check the "initial value not set" bit in monitor information 1 to determine whether the initial value has been received.Procedure P303) If the initial value has been received, immediately proceed to procedure P2O3.
, and if it is not received, proceed to procedure P2O3, P2
Change the operation information to "forced termination" in O3, prohibit sending to the card reader, and then perform each procedure P.
2O3 to enable communication control (receiving M) with the card reader. This is because the "initial value setting" packet may be sent even when the prize balls or the number of shots are changed on the console of the management device 400 after the store opens, and in that case, it is not desirable to change the operating information. Then, check the internal RAM flag to see if it is in test mode (procedure P2O3), and if it is in test mode,
Move to procedure P310, and if it is in the normal operation mode, check the flag to see if the initial value has been sent to the card reader in procedure P2O3, and if it has been sent, clear the initial value received flag (procedure P2O3), then proceed to procedure P310. to allow sending to the card reader. Then, after making a transmission reservation by writing the "initial value setting" function to a predetermined area (transmission buffer area) of the internal RAM, check the flag again to determine whether the initial value has been received (procedures P311 and P312). ).

In addition, if the "initial value setting" function has not yet been sent to the card reader in procedure P2O3, the process jumps to procedure P312 because the "initial value request" function is received from the card reader at the time of the first initial value transmission. This is to ensure that the initial value is sent after Procedure P
In 312.

If it is determined that the initial value packet has not been received, proceed to procedure P3↓3 and clear the "initial value setting" bit of monitor information 1. If it is determined that the initial value packet has been received, proceed to procedure P312 to P314. After making a transmission reservation for the "initial value setting" function, the process returns to the original processing routine (FIG. 183).

FIG. 184(B) shows the procedure for receiving the "store opening code" packet during the packet receiving task.

The unit controller 190 is "114 store coat"
When a packet is received, the operation information is first set to "free 1," and then the flag is checked to determine whether or not the test mode is in progress (procedures P321 and P322).If the packet is in the test mode, the process returns to the original routine. If it is in the normal operation mode, change the display by lamps 123 and 163 to the customer waiting state, and then write the "Card Acceptable" function to the RAM.
After making a transmission reservation, the card insertion lamp 1
68 is changed to non-blinking, and then returns to the original routine (procedures P323.P324.P325).

FIG. 184(C) shows the procedure for receiving a "closing code" packet during the packet receiving task.

When the unit controller 190 receives the "closing code" packet, it first checks the operating information and returns to the original routine if the operating information is "playing J" or "suspended". This is because it is sent after the ``end'' packet, so there is no way the ``pachinko closing code'' would be sent even if there is a pachinko machine that is playing or has been suspended. It functions as a safety device in case the game is in test mode.Also, if the operating information is not "gaming" or "interrupted", change it to "forced termination", then check the flag to determine whether or not it is in test mode ( Procedures P331-P333). Then, if you are in test mode, return to the original routine, and if you are in normal operation mode, turn off all lamps, write the "Card not accepted" function to RAM, make a transmission reservation, and return to original routine (procedure P334). .P2S
5).

In addition, the test mode judgment (P333) is performed after changing the operation information to "forced termination" in procedure P2S5, when the test mode is "closed" while the online test mode is running.
This is to quickly transition the pachinko machine to the forced termination state after receiving the packet and ending the test mode.

FIG. 184(D) shows the procedure of the "forced termination" packet reception process in the packet reception task of FIG. 183.

When the unit controller 190 receives the "forced termination" packet, it first clears the card text data in the transmission data area of the unit memory 550, and then changes the operation information to "forced termination" (procedures P341 and P342).
). Then, in the blowing procedure P343, "test mode"
If the flag is checked and the test mode is in progress, the program returns to the original routine, and after the test mode ends, it is possible to quickly shift to the forced termination state. On the other hand, in the normal operation mode, sensor detection and control of the batted ball launcher 1O3 are stopped, all lamps are turned off, and the internal R
Write data specifying the type of sound to a predetermined address in AM, reserve the output of the forced termination sound, and return to the original routine (first
83) (procedures P344 to P348). As a result, if the pachinko machine is in the middle of a game, it will eject cards and become unable to play, and in other cases it will not accept cards.

FIG. 184(E) shows the processing procedure when a "forced termination cancellation" packet is received.

When the unit controller 190 receives the "forced termination release" packet, it first checks the operation information and determines whether or not it is being forcedly terminated, and if not, it does nothing and returns to the original routine (procedure P2S5).

Furthermore, if it is being forcibly terminated, the operation information is changed to "free", and then the flag is checked to determine whether or not the test mode is in progress (procedures P2S5.P2S5). Here, if the test mode is in progress, the machine returns to the original routine and the pachinko machine can be quickly transferred to the free state after the test mode ends.

On the other hand, when it is not in the test mode, the lamp display is changed to a customer waiting state, a "card reception ready" function is scheduled to be sent to the card reader, the card insertion lamp 168 is changed to a blinking state, and the original routine is resumed. (1st
83) (procedures P354 to P356).

FIG. 184(F) shows the procedure for receiving a "cancel cancellation" packet.

This procedure is almost the same as the procedure for canceling forced termination shown in FIG. 184(E). The only difference is that after the operation information is set to "free" in procedure P362, the abort calculation register in the unit memory 550 is cleared and then the test mode is determined.

Further, FIG. 184(G) shows the procedure of the 11-interruption-end packet reception process.

This procedure is almost the same as the procedure for canceling forced termination shown in FIG. 184(E). The difference is that the test mode is determined after the operation information is set to "free" in procedure P372 and the card text data in the unit memory 550 is cleared, and cards can now be accepted even during suspension. Therefore, the transmission reservation of the "Card Receivable" function corresponding to procedure P2S5 is not performed.

FIG. 184(H) shows the procedure for receiving the "unit recovery" packet in the packet receiving task of FIG. 183.

When this packet is received, the unit controller ↓9
0 first copies the packet head of the reception data area to the transmission data area, and then clears the initial value setting j bit of the monitor information technology (procedure P2S5.P382).

The ``unit recovery'' packet is sent when an abnormality is detected during regular data collection or when a power outage is restored, but in the former case, the unit controller has already received and retained the initial value. Further, when power is restored, a "unit recovery" packet is sent after the "initial value setting" packet is sent.

After clearing the bit of monitor information 1, the control of the batted ball launcher 103 and the detection of the sensor are stopped.

After canceling the packet or function transmission reservation that occurred before the abnormality was discovered and clearing the flags related to packet transmission and card reader control to stop the operation, the reservation for transmitting the "ACK" packet to the management device 400 is made. (P 383-P 387).

Next, check the operating information of the restored transmission data area, and if the original operating state is not playing, return to the original routine (Fig. 183), and if playing, change the operating information to "free". to return to the original routine. This is to match the actual state and to smoothly execute the process according to the operation information in the process of the "restart" packet that is sent thereafter.

FIG. 184(I) shows a procedure for receiving a "restart" packet.

When the unit controller 190 receives the 1'restart'' packet, it first starts communication control with the card reader and reserves the transmission of the ``initial value setting'' function (procedures P391 and P392).

Next, check the operation information and if it is "forced termination", the same figure (D)
Proceed to procedure P341 and return the pachinko machine to the same state as before the operation was stopped by the "unit recovery" packet according to the same procedure as the forced termination request process (procedure P393
).

Also, if the operation information is "discontinued", the procedure P2S5 described below
to stop the pachinko machine (Procedure P
394), when the operation information is "suspended", a reservation is made to transmit the "card reception possible" function to the card reader, and then the process proceeds to procedure P427 described later in FIG. 184 (K) to interrupt the pachinko machine. state (procedures P395, P396).

On the other hand, when the operation information is other than "forced termination,""stopped," or "interrupted," the 18th
4 (H), the operation information is not "gaming" because there is a unit recovery processing procedure P2S5). ” function is scheduled to be sent, the card insertion lamp 168 is blinked, and the process returns to the original routine (Fig. 183) (Procedures P397 to P397)
399).

FIG. 84 (J) shows the processing procedure when a response to the "card-in" packet is received in the packet reception task of FIG. 183.

When the unit controller 190 receives a response to the "Card-in" packet, it checks whether the controller was in the ACK waiting state (procedure P2O3), and if an ACK packet containing the card text arrives even though it is not waiting for an ACK, it is judged as an error. Clear the card text data in the received data area (procedure P2O3)
. On the other hand, when a packet comes in while waiting for an ACK, the packet is checked to see if it is a NAK (negative response) (procedure P2O3). Then, the sound output that generates the sound indicating that the card reception is unsuccessful is reserved and the original routine returns (
Procedure P2O3, P2O3). In addition, even if the response is not a NAK, if the card number in the "ACK" packet does not match the card number sent previously, the process will proceed to procedures P2O3 and P2O3 and the card will be rejected (procedure P2O3 ).

Also, if the cart numbers match in procedure P2O3, “
Copy the card text data in the reception data area sent by the A CK packet to the corresponding position in the transmission data area, and copy the number of balls in the card text to the "Number of balls held" column in the operating data area. Copy (Procedure P2O3゜P4.08).

After that, check the card status in the cart text (procedure P2O3), and if the card is in the "discontinued" state, change the card status to "Free J" and change the operation information of the pachinko machine to "playing". Management device 400 after rewriting
A reservation is made to send a 5' end switch packet to the management device (procedures P421 to P423).As a result, a 5' end switch packet is sent to the management device, and the
When the A CK' packet is returned, the
The card is ejected by the end switch processing shown in FIG. 84 (L)), and the game with the stop card is disabled.

On the other hand, if the cart is not discontinued, procedures P2O3 to P41
0, check the operation information, and if it is "free", update the number of customers column in the transmission data area (Procedure P4
], 1), or when it is not “free” (when it is suspended)
Proceed directly to procedure P412, change the operating information to "gaming", change the lamp display to the gaming state, clear the floating ball number counter in the internal RAM, and start detection by the sensor (procedure P413 - P415). Next, check the number of balls in the card text, and if it is "O", leave it as is, and if it is not "0", start drive control of the batted ball launcher 103, then proceed to procedure P418, and reserve the output of the card acceptance success sound. (Procedures P416-P418)
.

It should be noted that when a response "ACK" packet is received from the management device to the "card-in" packet for pausing interruption, the same procedure as shown in FIG. 184 (J) for the response packet to "card-in" is processed. Ru.

FIG. 184(K) shows a processing procedure when a response to the "interrupt switch" packet is received in the packet reception task of FIG. 183.

When the unit controller 190 receives a response to the "interrupt switch" packet, it checks whether the controller was in the ACK waiting state (procedure P425), and if an "ACK" packet arrives even though it is not waiting for an ACK, it does nothing and returns to the original routine. Return to

Next, check whether the response packet is a NAK or not (P246), and if it is not a NAK, change the operation information to "suspended".
In addition, after changing the lamp display to the interrupted display state and stopping the detection by the sensor and the rotation control of the batted ball firing device 103, the transmission reservation of the card ejection function and the output reservation of the card ejection sound are performed (procedure P427~ P
432).

On the other hand, when it is determined in procedure P426 that a NAK has been received, the process moves to procedure P2S5, where it is determined whether the pachinko machine operation information in the received data is "playing", and if it is not "playing", it is the response to the interrupt switch itself. is strange, so we return to the original routine (Fig. 183) without doing anything, and if the game was in progress, change the card status to ``in play'' and then start detection by the sensor and ball launch control (procedure P433). -P436), that is, even if the end switch is pressed, if a NAK is returned from the management device 400 and the operation information indicates that the game is in progress, the card state is returned to the state of the game and the transition of the pachinko machine to the suspended state is refused. If you want to interrupt, press the interrupt switch again.

FIG. 184(L) shows the processing procedure when an "ACK" packet is received in response to an "end switch" packet.

This process is performed by "A" of the "interrupt switch" in the same figure (K).
CK" is executed in substantially the same flow as the reception process.

The difference is that the card text in the sending data area is cleared (procedure P443), and the operation information is set to "suspended".
Instead, the lamp display is changed to "Free J" and the lamp display is changed to the customer waiting display (procedures P444 and P445).In this process as well, if the operation information is "Playing" when the NAK is received, the card status is changed to "Playing". Then, the end processing is canceled (procedures P451 to P454).

FIG. 184(M) shows “A” for the “Return to zero” packet.
CK” packet is received.

This process is performed by pressing the A C end switch in the same figure (L).
This is executed according to the same flow as the K'″ reception process (procedures P461 to P474).

The receiving process of the "A CK" packet for the "A TERMINATION" packet shown in FIG. 184 (N) is shown in FIG. 184 (K).
It is executed according to almost the same flow as the "A CK" reception process of the "interrupt switch" (procedures P2S5-P494).
), the difference is that in addition to the card ejection function, there is also a transmission reservation for the function that does not accept cards (procedure P488).
) are included.

FIG. 185 shows the processing procedure of the card reader control task among the ten types of main tasks of the unit controller 190.

In this task, first, the flag in the internal RAM is checked to determine whether or not the card reader can be controlled, and if no, serial transmission interrupts and reception interrupts are prohibited (procedures P131 to P133).

On the other hand, when the card reader is in a state where it can be controlled,
The process moves from procedure P2S5 to P2S5, and it is determined whether the function is being transmitted. Next, it is determined whether the function is being received, and if the function is being received, it is checked whether the reception is completed within the set time (procedures P135 and P140). Also, internal RAM
Check whether there is a function in the reception buffer area of , and if there is a reception function (procedure P)
, 36) After restoring the received data that has been transformed into a form that is easy to transmit, and checking whether there are any parity errors or whether the code length is correct (procedure P141), the type of function is determined. Procedure P143
~P150), corresponding processing (Fig. 186(A)~
Execute (H)).

Furthermore, when it is determined in procedure P136 that there is no reception function, the process moves to procedure P2S5, and it is determined whether the card reader controller is waiting for a response function from the card reader controller CPU2, and the time required to receive the response is checked ( Procedure P 142). When not waiting for a response function, it is determined whether the function can be sent or not, and when it is possible to send, it is determined whether there is a function to be sent (procedure P139).If there is a function to be sent, the function sending process (
(See FIG. 186(I)).

FIG. 186(A) shows the procedure for receiving the "test card" function in the card reader control task.

When this function is received, it first checks the flag and determines whether it is in the "test card" function wait state (
Procedure P2O3). This flag is set when the test switch 179 is turned on in the switch detection task (see FIG. 191(E)). If it is waiting for a function, then check whether the operation information is "free", and if it is free, check whether it is offline (procedures P2O3, P
2O3). If you are offline, program ROM
The number of prize balls for the test game that is the same or different from that stored in the online management device 400 is set (procedure P2O3). This is because the number of prize balls is not sent from the management device when offline. After setting the number of prize balls, the initial number of balls (0) and amount (1000 yen) fixedly given to the test card are set (procedure P2O3).

Note that when online, the process jumps from procedure P2O3 to P505, skips the setting of the number of prize balls in procedure P2O3, and sets the number of balls and amount. After that, clear the counter that counts the number of floating balls, change the lamp display state, and then
Control of the batted ball launcher 103 and sensor detection are started, a reservation is made to output a sound that indicates successful card reception, the operation information in the test mode operation data area is changed during the game, and the process returns to the original routine (procedure). P506~P
511).

On the other hand, if a test card function is received without waiting for a test card function, the process moves from procedure P2O3 to procedure P512, and it is determined whether or not the operation information in the test mode operation data area (see topsoil) is "suspended". Interrupt switch 114 during play in test mode
If the game is interrupted by pressing , the interruption will be canceled by inserting the test cart without pressing the test switch, so that the game can be resumed.If the operation information is interrupted, the number of prize balls has already been set, so you can immediately proceed It is possible to move to P2O3 and restart the test game.

If it is determined in the above procedure P512 that the operation information is not suspended, the process moves to procedure PbI2 and it is determined whether or not it is offline. Here, when it is determined that the game is offline, the process moves to the above-mentioned procedure P2O3, and the number of prize balls and the like are set and preparations for the test game are executed. This assumes unexpected situations, and there is no particular support for entering test mode if you have a test card when offline.

On the other hand, when it is determined in procedure PbI2 that it is online, a transmission reservation for the "card ejection" function and a reservation for discharging the card before the card reception is unsuccessful are performed (procedure P514.
P515). That is, if a test card is inserted without pressing the test switch 179 while online, the test card will be ejected and the test game will not begin. This makes it possible to prevent illegal games by players.

FIG. 186(B) shows the processing procedure when accepting the "send card number" function in the card reader control task of FIG. 185.

Here, first, the flag is checked to determine whether or not the r test card j function is in a waiting state, and then it is determined whether or not the test mode is in progress (procedures P521 and P522). Here, if it is determined that the function is waiting for reception or is in test mode, the process jumps to procedure P525 and the message ``Reserve card ejection j function transmission, and then reserve the ejection before card reception is unsuccessful (procedure P526).In other words, the test switch Even if a regular game card is inserted immediately after turning on or during an interruption of the test mode, it is immediately ejected to prohibit the transition to the normal game.

On the other hand, if it is neither in the "test card" function reception waiting state nor in the test mode, the process moves to procedure P523 and it is determined whether the operation information is suspended, and if it is not suspended, the transmission of the "'card-in" packet is reserved ( Procedure P
527), if it is suspended, compare the card number read in procedure P524 with the card number in the transmission data area, and if they do not match, proceed to procedure P525 and reserve the card ejection, and when the card numbers match is procedure P
The process moves to 528 to reserve the transmission of an "interrupt card-in" packet.

FIG. 186(C) shows the procedure for receiving the "status" function in the card reader control task of FIG. 185.

When this function is received, the "abnormal end" flag is cleared first, and then the statuses 1 and 2 in the receive buffer are cleared.
Save in internal RAM (procedure P2S5.P532
). The "abnormal end" flag is referenced in the error control task procedure Pi70 in FIG. 188.

Next, it is determined whether the "card reception sound" function was transmitted in the previous transmission, whether the card is present in the reader, and whether the operating information is "playing" (procedures P533 to P535). , here, the previous transmission was the "Card Acceptance Sound" function, and if there are cards in the reader and the game is not in progress, it is not in a normal state.
After sending the "card ejection" function and reserving the ejection sound output, determine whether the end of the test mode is online or offline, and if it is still offline, proceed to procedure P98 in Figure 182 to receive the "line test" packet. Wait (procedures P536 to P538).

On the other hand, if the previous card acceptance sound function has not been sent, or if the card is not in the reader even after sending it, or even if the card is in the reader after sending the card acceptance function, it is still "playing". If so, proceed to procedure P2S5 without making a card ejection reservation and determine whether the end of the test mode is online or offline, and if offline, jump to "line test" packet waiting.

FIG. 186(D) shows the processing procedure when a "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 a retransmission request is returned in response to a retransmission request, so a reader error flag is set (procedure P543). When a retransmission request is returned in response to a retransmission request, this process is repeated continuously,
This is because other function transmissions cannot be performed. On the other hand, if the result in procedure P541 is NO, the retransmission reservation (procedure P542) of the already transmitted function is made again, and the process returns to the original routine. Note that the reader error flag is referred to in procedure P2S5 in the error control task in FIG. 188.

In FIG. 186(E), the unit controller 19o is
The process procedure when receiving the "Normal End" function and the "Abnormal End" function is shown in FIG.

When the "normal end" function is received, the error flag is cleared (procedure P545), and the process moves to procedure P2S5 in FIG. on the other hand,
``When receiving the abnormal termination J function, check the status 1 sent at the same time, and if the initial value for the card reader is not set, proceed directly to the procedure P532 in (C) in the same figure.
If the initial value is not set, the "abnormal end" flag is set, and the process jumps to procedure P532 to execute the same process as the status reception process (procedures P546 and P547).

The "abnormal end" flag is referenced during the error control task shown in FIG. 188, and subsequent card acceptance becomes impossible.

FIG. 186(G) shows the procedure for receiving the "initial value request" function in the card reader control task of FIG. 185.

When receiving this function, first make a reservation to send the "Initial value setting" function.

Check the flag to determine whether transmission is prohibited (procedure P2S5.P2S5). Here, if sending is prohibited, proceed to P.
2S5 allows transmission, and if transmission is not prohibited, proceed to procedure P
Check the operation information of the pachinko machine with 2S5 and check whether it is "free" or "
When the game is in progress or suspended, a transmission reservation for the card reception possible function is made (procedure P2S5). on the other hand,
If the judgment in procedure P2S5 is other than "free", "gaming", or "interrupted" (abort or forced termination), reserve the transmission of the "card acceptance not possible" function (procedure P
2S5).

During the task in Figure 185, if it is determined that the self-ejection j function has been received, the output of the card reception failure sound is reserved as shown in Figure 186 (H) and the process returns to the original routine (procedure P558). ).

Next, FIG. 186 (I) shows the transmission processing procedure when it is determined that there is a transmission function in one procedure P2S5 during the processing of the card reader control task of FIG. 185.

To send the function, first set the number of retries (for example, 3 times) in the internal RAM, set the ACK reception timer (5 seconds), and send the call signal ENQ to the card reader (procedure P560~ P562)
. Then, if no ACK is received, it is determined whether the timer set in procedure P561 has exceeded (procedure P56
3゜P564). Even if a timeout occurs, the number of retries is checked and if the predetermined number of times (three times) has not been reached, the process returns to procedure P561, the timer is reset, and the ENQ transmission is repeated. If an ACK still does not come and the number of retries is exceeded, an error flag is set and function transmission is canceled (Procedures P565 and P56).
6, P567).

On the other hand, if ACK is returned within the number of retries, after creating transmission data, the STX code is first put into the transmission buffer to start transmission, and the transmission flag is set (procedures P568 to P570).

FIG. 187 shows the processing procedure for the packet transmission task among the ten types of main tasks of the unit controller 190.

In this task, it is first determined whether there is a packet to be transmitted, and if so, the packet type name is written in the packet head part of the transmission data area of the unit memory 550, and then the packet type name is written in the command register CRI in the communication area. and set the packet transmission timer (
Procedures P151 to P154). Command register CRI
By writing the packet type name to , the data transmission controller 551 starts transmitting the corresponding packet, and when the transmission is completed, clears the command register CR].

When there is no transmission packet in procedure P2S5 or after setting the transmission timer in procedure P2S5, procedure P2S
In step 5, it is determined whether the transmission timer is set, and if it is set, the process moves to procedure P2S5, and if it is not set, the process returns to P2S5.

In procedure P2S5, it is determined whether the command register CRI has become "O" due to the end of transmission, and if it has not become "0" yet, it is checked whether the transmission timer has exceeded (procedure P2S5). Here, if the transmission timer has not exceeded, proceed! Return to P151. On the other hand, when the transmission timer exceeds, set the "Z-80 error" flag and then reset the transmission timer (Procedure P1
60, P2S5).

Also, in procedure P2S5, command register CR1 is set to “0”.
'', if the transmitted packet is of the type that receives ``ACK'' such as ``Packard In'', reset the transmission timer while setting the ACK wait timer (10 seconds) (procedure). P2S5.P2S
5) The 1m+71 ACK wait timer is referenced in procedures P2O3 and P2O3 in the packet reception task in FIG. 183.

FIG. 188 shows the procedure of the error control task among the main tasks of the unit controller 1-roller 190.

In this task, we first set the "Z -80 error flag" (
Please check the procedure P2S5. P162), if either flag is set, proceed to procedure P174 to disable timer interrupts and serial interrupts, stop the task processing, and then power down the CPU (procedures P175, P176). ). The above procedure (P1
74 to P176) can be executed, for example, by fixing the level of the common signal for the segment display serving as a watchdog pulse and resetting the unit controller by the reset circuit 555.

On the other hand, when neither the "Z-80 error" flag nor the "packet ACK error" flag is set, the "reader error" flag (P543, P545, P56 in Figure 186) is set.
If the flag is not set, the "reader abnormality" bit of monitor information 2 in the unit memory 550 is reset and the process returns to procedure P2S5 (procedures P163 and P164). If the "reader error" flag is set, proceed to procedure P2S5, set the "reader error" bit in monitor information 2, clear all the reader control flags, and then control the reader. enable (procedure P166, P2S5), L
After that, check whether you are in test mode and whether the initial values have been set. P169), in the test mode or when the initial value is not set, the test mode ending process shown in FIG. 189 is executed.

If the test mode is not set and the initial value is also set, check the "abnormal end" flag (see procedure P547 in FIG. 186(F)) in procedure P170, and set the flag to
31, return to procedure P2S5, and if the "abnormal termination" flag is set, proceed to procedure P171, change the operation information to "forced termination", and then schedule the transmission of the "card not accepted" function. Then, clear the 'abnormal end' flag and return to procedure P2S5 (procedure P17).
2, P173).

FIG. 189 shows the procedure of the man-hour calculation task among the ten types of main tasks of the unit controller 190.

In this task, first, the flag or signal is checked to determine whether the sensor is being detected, that is, the game is being played (P2S5),
If the sensor is not being detected, clear the counter that counts the number of times each sensor is turned on (P2S5); if the sensor is being detected, clear the counter 181 according to procedures P183 to P199.
The firing sensor 5NS5, the safe sensor 5NS2, and the second safety sensor 5NS2 obtained by the process shown in FIG. Second safe sensor 5NS3, foul sensor 5NS4. Read the number of ON times of each sensor of Out Sensor 5NSI and calculate the total number of balls awarded, number of balls out, number of out balls,
The difference number is calculated, and finally the total number of prize balls is added to the stop calculation register (procedure P2O0).

FIG. 190 shows the procedure of the switch detection task among the main tasks of the unit controller 190.

In this task, first check the flag or signal to determine whether or not the sensor is being detected (Procedure P2O1). If not, the interrupt switch 114, the purchase switch 113, the end switch 115, the call switch 165a, or the test switch ↓79 is turned on. (Procedures P2O2 to P2O6). Then, if any switch is turned on, the corresponding process (191st
(See Figures (b) to (e)). Incidentally, when the call switch among the above-mentioned switches is turned on, the status display lamp 162 of the pachinko machine is changed to blinking and the output of the switch operation sound is reserved (procedure P219).

On the other hand, when the sensor is being detected in procedure P2O1, the process moves to procedure P2O7 and the search timer described later (procedure P21
6) is in operation, and if it is not in operation, proceed to procedure P2.
13. On P214, the number of balls and amount of cards being played are "
0" or not.

Then, when the number of balls is rOJ and the amount is rQJ (none), a purchase request process (procedure P217) is performed. Specifically, a reservation is made to output a sound that prompts the user to turn on the purchase switch 113, and a reservation is made to update the display to blink the lamp built into the purchase switch.

However, when the number of balls and the amount are both rQJ, the search timer (10 seconds) is activated to start the return to zero determination, and the output of a sound to notify that the search timer is operating is scheduled to be output before returning to procedure P2O1 (procedure P215.P21
6).

Then, it is determined again in procedure P2O7 whether the search timer is in operation, and if it is in operation, the process proceeds to procedure P2O3, in which it is determined whether there are any floating balls remaining on the game board. Here, if there is no floating ball, the process moves to procedure P212, determines the occurrence of a return to zero, and makes a reservation for transmission of a "return to zero" packet.

Further, in this return to zero determination procedure, a test mode termination process as shown in FIG. 191(f) is performed, and if a return to zero occurs during the test mode, the test mode is terminated.

On the other hand, while the search timer is operating and floating balls remain, proceed from procedure P2O3 to P2O9 and start the search timer (10
If the time is over, even if there is a floating ball number, proceed to procedure P2128 and return to zero. This is because it is normally impossible for floating balls to still exist even after 10 seconds have passed since the number of balls became "0".

Also, if the search timer has not exceeded, proceed from procedure P2O9 to P210, and again determine whether the number of man-hours is "○" or not. If it is not "0", stop the search timer and cancel the determination of return to zero. (Procedure P211). This takes into consideration the case where a floating ball enters the winning slot during the operation of the search timer and the number of balls held is added, and thereby the game control is continued again. In addition, if the number of balls is not rOJ while the search timer is not operating, the process moves to procedure P218 and it is determined whether or not the value of the stop calculation register has become greater than the predetermined number of stops. Figure 191 (a
) will now execute the abort process shown below. The number of stops may be determined by preparing a plurality of stopping modes in advance, selecting the mode using a program, etc., and comparing the stopping number corresponding to the mode with the value of the stopping calculation register.

FIG. 191(a) shows the procedure of the termination process during the process of FIG. 190.

When entering this abort process, the flag is first checked to determine whether or not the test mode is in progress (P2S5). Update the number of stops (+1.)
L. After changing the card state to "stopping and free J," stop the sensor detection and motion control of the ball launcher 103, and reserve the output of the stopping sound (procedures P582 to P58).
7).

Although the card ejection command is not performed here, the above-mentioned "stop" packet is sent to the management device 400, and when the ACK is returned, the reception processing there (18th
In FIG. 4 (N)), the "card eject" function is sent to the card reader (procedure P2S5), so when a stop occurs, the card is ejected, as described above.

On the other hand, if an abort occurs during the test mode, procedure P2
Shifting from S5 to P2S5, abort by executing procedures P591 to P597 that are almost the same as procedures P483 to P489 (excluding P488) in FIG. The test mode is designed to be executed offline even when the management device is not connected.If termination occurs during the test mode, the end switch 115
By turning on, the process shifts to test mode termination processing, and the subsequent state is determined depending on whether it is online or offline (see FIGS. 191(e) and 191(f)).

FIG. 191(b) shows the procedure for interrupt switch processing during the switch detection task of FIG. 190.

This process starts when it is detected that the interrupt switch 114 is turned on, and first, it is determined whether or not the test mode is in progress (procedure P2).
O3). Here, if it is not test mode, procedure P2
Proceed to O3, schedule the transmission of the "suspension switch" packet, change the card status to "suspended", detect the sensor and fire the ball! ! ! 1030 Stop the driving control and return to the original routine (procedures P603 to P605). Card ejection, etc. caused by turning on the interrupt switch is performed at the time when the ACK packet for the above packet is received (see FIG. 184(K)). On the other hand, when the interrupt switch is turned on during the test mode, the operation information is updated, the card ejection function is reserved for transmission, and
The display of the control stop lamp is changed (procedures P611 to P616). This takes offline test mode into consideration.

FIG. 191(C) shows the procedure for purchasing switch processing during the switch detection task of FIG. 190.

When the purchase switch 113 is turned on, an instruction is first given to turn off the lamp 121 (hereinafter referred to as the purchase lamp) built into the purchase switch (procedure P621). This lamp is
It remains lit while the amount does not reach "0", and the number of balls is r.
It is driven to blink by the purchase request procedure P217 in FIG. 190, which is performed when OJ is reached. Then, the blinking is stopped at the same time as the purchase switch is turned on. Next, determine whether the amount on the card is rQl, and if it is rQJ, do nothing and
Return to the routine shown in the figure (procedure P622).

On the other hand, if the amount remains, proceed to procedure P623,
After reading the conversion rate of the purchased balls, the number of balls equivalent to 200 yen is added to the number of balls in the unit memory 550 and the number of held balls (procedure P624).

Then, the frequency of the amount (remaining amount) is "-2", the number of purchases is "+1", the frequency of sales is "+2", and then the amount is r
Q" is determined (Procedures P625 to P6
28). Here, if the amount is "0", the purchase lamp is not turned on, and if there is a balance remaining, the purchase lamp is turned on and then drive control of the batted ball launching device 103 is started (procedures P628 to P630). Therefore, the purchase lamp is temporarily turned off when the purchase switch 113 is turned on, but it is immediately turned on as long as there is remaining money. Further, when the player turns on the purchase switch based on the display before making a purchase request, the purchase lamp changes from blinking to on or from blinking to off depending on the amount of the card.

After starting control of the batted ball launcher, the output before the purchase request is canceled, the output of the switch operation sound is reserved, and the process ends (procedures P631 and P632).

FIG. 191(d) shows the procedure of the end switch processing in the switch detection task of FIG. 190.

When it is detected that the end switch 115 is turned on, the sensor detection is first stopped, and then the drive control of the batted ball launching device 103 is stopped (procedures P64.1.P642). Then, in step P643, it is determined whether the mode is a test mode, and if it is a test mode, the process moves to the test mode termination process shown in FIG. Change the card status to "free" (procedures P644 and P645).

Card ejection commands, lamp display changes, etc. are performed by receiving a response packet ACK to the "interrupt switch" (184th
This is done in Figure (L)).

FIG. 191(e) shows the test switch processing procedure in the switch detection task of FIG. 190.

When it is detected that the test switch 179 is turned on, the output of the switch operation sound is reserved and the test card function wait flag is set (Procedure P2S5.P2S5
). This flag is the first flag indicating the test card processing procedure.
It is referred to by procedure P2O3 in FIG. 86(A).

Then, it is determined whether or not the device is offline, and if the device is offline, a reservation is made to send the "Card Acceptable" function to the card reader, and if it is online, nothing is done. In other words"
"Card Accepted" function is not sent. Therefore, when online, the test mode is entered only when card acceptance is enabled. However, even if cards can actually be accepted online (MC is suspended), test cards are ejected when the operation information is other than "free" (see Figure 186 (A)). (See P2O3, P513).

In addition, the above test switch processing (procedures P651 to P6
In 54), it is also possible to set a timer to return to the original state if no test card is inserted within a certain period of time after the test switch is turned on.

FIG. 191(f) shows the specific procedure of the test mode termination process during the error control task of FIG. 188 and the termination switch process of FIG. 191(d).

When this process starts, first all lamps are turned off, sensor detection and drive control of the batted ball launcher 103 are stopped, and then it is determined whether it is offline or online (Procedure P
661-P664). Here, if you are online, check whether the operation information of the pachinko machine is "forced termination" (procedure P2S5)
If the termination is forced, the transmission reservation of the "Card not accepted" function and the output reservation of the card ejection sound are made, and the process returns to the original routine (Procedures P671 and P672). Note that when the card reader receives the "card not accepted" function, it ejects the card it is holding and then enters a state in which it does not accept cards. In cases other than forced termination, the lamp 123
, 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 "discontinued" (procedures P666, P2S5). Then, if it is canceled, jump directly to procedure P670, and if it is other than cancelled, the transmission reservation of the "card ejection" function and the output reservation of the card ejection sound (procedures P6S8, P669)
), then proceed to procedure P670, change the display of the cart insertion lamp to blinking, and return to the original routine. Therefore, the pachinko machine returns from the test mode to the "free" state of the normal operating mode.

As mentioned above, in the aborted state, procedure P6S8 (card ejection function transmission reservation) is omitted and procedure P2S
The jump from 5 to P670 is shown in Figure 191 (
This is done in the a) termination process (procedure P591)
This is to avoid duplication of procedures. Furthermore, the reason why procedure P669 (card ejection sound output reservation) is omitted when canceling is to prevent the ejection sound from being output even though the card is not ejected. In other words, in the test mode, when termination occurs, the card is ejected, and then when the termination switch 115 is turned on, the process shifts to the test mode termination process (Fig. 191).
d) Procedure P642), outputting the card ejection sound here would be inconsistent with reality.

On the other hand, if it is determined that it is offline in the above procedure P664, the process moves to procedure P673, and after reserving the transmission of the "Card not accepted" function and reserving the output of the card ejection sound, the "Offline at end of test mode" flag is set. and checks whether the "Pallider Error" flag is set (procedures P673 to P676).

Here, if there is no reader error, return to the original routine,
If there is a reader error, proceed to procedure P677, clear the ``Offline at end of test mode'' flag, and then wait for ``line test'' packet (Procedure P in Figure 82).
98). The above flag is used in the procedure P2S during the "Status" function reception process (Fig. 186(C)).
5, and when the status is sent, this flag is checked and the process shifts to waiting for a line test. In other words, if there is no reader error, the process returns to the original routine after completing procedures P673 to P676, and then transitions to waiting for a line test when statuses 1 and 2 are received along with the "normal completion" function after the card is ejected from the card reader. .

On the other hand, if there is a reader error, procedure P673
When the card ejection process is executed in response to the function, if the card reader sends the status 1゜2 along with "abnormal end", the process moves to wait for line test in procedure P2S5 of FIG. 186(c). To prevent the cart from becoming impossible to take out, the "offline at end of test mode" flag is cleared in procedure P677.

FIG. 192 shows the processing hand j@ of the sound control task among the ten types of main tasks of the unit controller 190.

In this task, we will introduce "hit sound", "switch operation sound", "
Check whether there is a reservation to output the "Card ejection sound", "Card reception success sound", or "Card reception failure sound" (procedures P221 to P2.25), and if there is a reservation, select the sound to be output. After setting the data indicating the type and the output time in the internal RAM, the voice synthesis circuit (sound IC) 582 is reset and the sound being output is stopped (procedure P23).
1°P232). Then, the process moves to procedure P2S5, where a control signal is given to the sound IC to output the selected sound. Then, determine whether the set output time has elapsed,
If the output is exceeded, stop the output (procedure P2
S5. P2S5). On the other hand, if the output time has not been exceeded, it is determined whether the output sound is a repeating sound, and if it is not a repeating sound, the sound output is stopped (Procedure P236.P2
S5).

However, even if a sound output stop command is issued in procedure P2S5, 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.

If there is no output reservation for any of the above five types of sounds, it is checked in procedure P226 whether the sound is being outputted, and if it is being outputted, the process moves to procedure P2S5 to check whether the output time has exceeded. On the other hand, if the sound is not being output, check whether there is an output reservation for "Search timer sound", "Purchase requester", "Stop sound J" or "Forced end sound" (Procedure P227~
P230), in some cases, after setting the data and time specifying the sound to be output (procedure P233), procedure P
The process moves to 2S5 to start outputting the sound, and when a timeout occurs, the outputting the sound is stopped. In other words, these four sounds are output after waiting for the output of the other sounds to finish.

FIG. 193 shows the procedure of the timer control task among the main tasks of the unit controller.

In this task, 10m5 and 100m are used as standards for lamp blinking, packet transmission timer, ACK reception timer, etc.
The 10 m S timer is updated (decremented) every 10 m seconds, and the 10 m S timer is managed every 10 m seconds.
Update the 100mS timer every 00ms (Procedure P
241-P 244).

FIG. 194 shows the processing procedure of the lamp display control task among the main tasks of the unit controller 190.

In this task, during the above various processes, the safe bulb lamp 164, the P machine status display lamp 162, the built-in purchase switch lamp 121. When the card insertion lamp 168 and gaming status lamp 123 are updated, their display status is changed (procedures P251 to P255). Next, determine whether it is necessary to display a “waiting for customers” or “discontinued display.”2
When the customer waiting display is displayed, the analog display 163 is scrolled, and when the stop display is displayed, all the lamps on the analog display 163 are blinked at the same time (Procedures P256 to P259
). Furthermore, the necessity of displaying the number of balls is determined, and if necessary, the lamps of the analog display 163 are lit up in order from the left side according to the number of balls (procedures P260 and P261).
. Moreover, this analog display of the number of balls is performed using a so-called logarithmic display in which the number of steps displayed by one lamp increases as the number of lamps lit increases. moreover,"
When any of the displays of "Customer Waiting Display", "Stopping Display" and "Number of Balls Display" are unnecessary, the analog lamp 163 is turned off (procedure P2S5).

Table 35 below shows an example of the display state of each lamp depending on the state of the pachinko machine.

In the same table, the X mark is off, the 0 mark is on, the Δ mark is blinking,
S indicates a scroll display, and A indicates an analog logarithmic display according to the number of pitches. Further, in the "Search" column during the game, the amount of money and the number of balls become zero, indicating a display state in which the search timer (10 seconds) is in operation, and after 10 seconds have passed, it shifts to the zero state.

X: Off, O: On, △:, =, ts Niss Roll, A
: In addition to the nine types of tasks mentioned above, the main tasks of the analog display unit controller include a port output control task. This task executes a process of outputting the output state determined in each of the above tasks to the corresponding I10 port (not shown).

FIG. 195 shows the timing of input and output signals when controlling the pachinko machine according to the above control flow.

The numbers representing the number of balls are calculated assuming, for example, that the purchase ball rate is 50 balls/200 yen, the number of main prize balls is 13 balls, and the number of sub prize balls is 7 balls.

After receiving the response packet ACK to the "card-in" packet at timing t1, when the ON signal of the purchase switch 113 comes in at timing t2, the 1-shot driving control signal is changed to high level, and the batted ball firing device 103 is activated. It becomes possible to drive. At the same time, the frequency of the remaining balance on the card is subtracted by "2", and the number of balls worth 200 yen is added,
The amount display and number of balls display will be updated.

Thereafter, when detection pulses are received from each sensor, the number of floating balls and the number of balls held are calculated in real time within the unit controller 190, and the number of balls and their display are changed one after another. In addition, when the number of floating balls is "0" inside the controller, even if there is a detection pulse of the safe sensor (see P-work), it is invalidated and the number of prize balls corresponding to that is not added.

During such game control, when the on signal of the interruption switch 114 is input (timing ta), the firing drive control signal is turned off. However, the display remains as it was at the time of interruption. After that, when the ACK packet for 'interrupt card-in' is received (timing t4), game control is started again, and the game is ended when the end switch 115 turns on signal (timing ts), 'end switch' A of
At the time when the CK is received (timing ts), the display, number of balls, and amount data are cleared to "O".

On the other hand, when a zero state occurs during the game where the card amount and the number of balls are both "O" (timing t7)
, the search timer is activated, and if there is no detection pulse of safe sensor 1 or 2 within 10 seconds, a "return" packet is sent, and at the time (t,) when the person receives CK, the number of floating balls becomes "o". ” will be cleared. If the number of floating balls reaches rQJ while the search timer is in operation, a ``Packing Zero'' packet is transmitted at that point.

In the above embodiment, when the suspended cart is settled at the payment machine, the management device is notified of the payment of the suspended card, and the management device reads the machine number of the suspended Pachinko machine from the card file and sends the "suspended" card to the corresponding Pachinko machine. Instead of automatically releasing the pachinko machine, for example, when a suspended card is paid, the machine number of the suspended machine is displayed on a CRT display, etc., and the pachinko machine is released. The pachinko machine may be configured to release an interrupted pachinko machine by giving an instruction from the console.

Furthermore, the above embodiment is applied to a gaming system in which only the card number is recorded on the card as a storage medium, and the purchase amount and man-hours are stored in the storage device of the management device in correspondence with the card number. Although described above, the present invention is not limited thereto, and can also be applied to a system in which a game can be played using a card that records the purchase amount or the number of balls.

Further, the cart issuing machine and the payment machine do not necessarily need to be connected to the management device via a transmission medium, and may issue cards or make payment based on their own judgment.

[Effects of the Invention] As explained above, the present invention provides a gaming machine in which a game can be played only with a card on which an identification code is recorded, an issuing device for issuing the card, and a memory for settling the valuable data of the card. The media payment device and their management device are connected through a transmission means, and the management device manages valuable data substantially equivalent to the amount of money or the number of balls for each identification code given to the card, and is a card-type gaming system that allows games to be played within the range of valuable data obtained from the management device based on the identification code read from the card, and the payment machine is in a free state and during suspension. In addition to being configured to execute payment processing for cards, when payment processing for a suspended card is executed, the management device is notified, and the management device is configured to issue a command to cancel the suspension to the corresponding gaming machine. , the player or the game parlor staff does not have to go to the trouble of returning to the suspended game machine to cancel the suspended state.
The game machine can be automatically released at the same time as payment,
This has the effect of making it possible to save labor at the game parlor.

[Brief explanation of drawings]

FIG. 1 is a system configuration diagram showing the overall configuration of a pachinko gaming system to which the present invention is applied, and FIGS. 2 (A) and (B) are front views showing an example of a card used in the system according to the present invention. Internal configuration diagram. FIG. 2(C) is an explanatory diagram showing an example of the configuration of the authenticity identification area in the card. FIG. 2(D) is a cross-sectional view showing an example of the cross-sectional structure of the card, and FIG. 2(E) is an explanatory diagram showing an example of the configuration of the magnetic recording section within the card. FIG. 3 is a perspective view showing an example of the overall configuration of the pachinko machine that constitutes the gaming system; FIGS. 4(A) and (B) are cross-sectional side views showing an example of the configuration of the operation panel on the front of the pachinko machine; FIG. FIG. 6 is an exploded perspective view of the operation panel, FIG. 6 is a perspective view showing the internal structure of the operation panel, and FIG. 7 is a perspective view showing an example of the structure of the enclosed ball circulation device on the back of the pachinko machine. Figure 8 is a perspective view showing the enclosed ball circulation device attached to a pachinko machine, Figure 9 is a perspective view showing details of the base of the ball launch rail, and Figure 10 is a view of the pachinko machine with its front panel opened. Figure 11 is a perspective view showing an example of the configuration of a frame board that includes a frame that holds a game board and a firing rail coupled to the frame; Figure 12 is a perspective view showing the back configuration of the front frame of the pachinko machine. Figure 13 is a rear perspective view showing an example of the configuration of the back side of the pachinko machine. FIG. 14 is a perspective view showing a configuration example of a pachinko machine control unit. FIG. 15 is a perspective view showing the internal structure of the control unit, FIG. 16 is a perspective view showing the structure of the front panel of the control unit, and FIG. 17 is a perspective view showing the mounting positional relationship between the pachinko machine and the control unit. Figure 18 is a perspective view showing the framework of the island equipment where the pachinko machine is installed, Figure 9 is a perspective view showing the pachinko machine and control unit installed on the island equipment, and Figure 20 is the rear view of the island equipment. 21 is a block diagram showing the control system of the entire pachinko machine, FIG. 22 is a block diagram showing an example of the circuit configuration of the pachinko machine control device, and FIG. 23 is a block diagram showing an example of the circuit configuration of the pachinko machine control unit. Block diagram, Figure 24 is a memory map showing the area configuration of the unit memory, Figure 25 is a perspective view showing an example of the configuration of a card reader for a pachinko machine, Figure 26 is an exploded perspective view of the card reader, and Figure 27 is a card reader. 28(A) and 28(B) are exploded perspective views showing details of the card insertion portion of the reader; FIGS. 29(A) and CB are cross-sectional side views also showing details of the card insertion portion of the card reader;
) is a cross-sectional side view showing details of the shutter portion at the card reader entrance, FIG.
Figure (B) is a sensor detection timing chart when a card is inserted. FIG. 31 is a block diagram showing an example of the circuit configuration of a card reader control device, and FIG. 32 is a block diagram showing an interface circuit of the card reader. FIG. 33 is a timing chart showing the data reading and writing timing of the card reader, FIG. 34 is a perspective view showing a configuration example of a card issuing machine used in the gaming system according to the present invention, and FIG. 35 is a front view of the issuing machine. FIG. 36 is a perspective view of the card issuing device installed in the issuing machine; FIG. 37 is a schematic configuration diagram of the card issuing device;
FIG. 39 is a perspective view showing the configuration of a card ejecting device constituting the card issuing device, FIG. 39 is a perspective view showing the configuration of the card ejecting device also constituting the card issuing device, and FIG. 41 is a block diagram showing a configuration example of a unit control device of a card issuing machine; FIG. 42(A) is a perspective view showing a configuration example of a payment machine; FIG.
Figure (B) is a perspective view showing the top panel and front panel of the payment machine in an open state, Figure 43 is a perspective view showing an example of the configuration of the card payment device that constitutes the payment machine, and Figure 44 is a perspective view of the present embodiment. A perspective view of a pachinko parlor counter configured using a payment machine, Figures 45 (A) and (B)
46 is an explanatory diagram showing an example of the configuration of a receipt issued by the payment machine, FIG. 46 is a block diagram showing an example of the configuration of the control device of the payment machine, and FIG. 47 is a block diagram showing an example of the configuration of the unit control device of the payment machine. . FIG. 48 is a perspective view showing an example of the overall configuration of the management device;
The figure is a block diagram showing an example of the system configuration of the management device itself. FIG. 50 shows an example of the configuration of the console of the management device. (A) is a plan view, (B) is a rear view, and FIG. Memory map showing an example of the structure of files in the device. FIG. 52 is an explanatory diagram showing the state transition of cards in the gaming system of the present invention, and FIG. 53(A) is a block diagram showing an example of the configuration of a transmission system in the gaming system of the present invention. Figure 53 (B) is a block diagram showing the connection method of the transmission system when the transmission line is composed of optical cables, and Figure 53 (C) is a block diagram showing the connection method of the transmission system when the transmission route is composed of coaxial cables. Block diagram, Fig. 54 (A) is a block diagram showing a configuration example of a NAU (network adapter unit) that controls data transfer on the network, Fig. 54 (B) is a perspective view showing the external appearance of the NAU, Fig. 55 Figures (A) and (B) show the management device-N on the high-rise network.
FIG. 3 is a configuration diagram showing a packet structure between AUs and between a management device and a unit. Figure 55 (C) shows the management device-N on the low layer network.
Configuration diagrams showing the packet structure between AUs and between the management device and the unit, FIGS. 56 to 61 show examples of the structure of packets transmitted and received on the high-rise network. Figures 56 (A) and (B) are configuration diagrams of the "line test" packet and its response "ACK" packet, Figure 57 (A),
(B) is a configuration diagram of a "unit table request" packet and its response packet, FIGS. 58 (A) and (B) are configuration diagrams of an "initial value setting" packet and its response packet, FIG. 59 (A), (B) is a configuration diagram of the “regular data request” from the management device to the pachinko machine and its response packet, and Figures 60 (A) and (B) are the configuration of the “various command” packet and its response “ACK” packet. Figure, Figure 61 (A),
(B) and (C) are “card-in” packet and its response.
ACK ”Packet and Negative Acknowledgment”NAK
``Packet configuration diagram, Figure 62 is the NAU from the pachinko machine.
Figures 63 (A) and (B) are diagrams showing the configuration of the "unit recovery data" and its response packets for pachinko machines on the low-layer network, and Figure 64 (A ), (B), and (C) are the “Card Purchase” packet and its response “ACK” packet and negative response “NAK” between the issuer and NAU on the low-layer network.
Packet configuration diagram. Figure 65 is a configuration diagram of a "regular data transmission" packet from the issuing machine to the NAU. Figure 66 (A), CB) is a diagram of the "unit recovery data" packet sent to the issuing machine on the low-layer network and its Configuration diagram of response “ACK’” packet, Fig. 67 (A), (B
) and (C) are configuration diagrams of a "card payment" packet and its response "ACK" and negative response "NAK" packet to the payment machine on the low-layer network. Figures 68 (A), (B), and (c) also show the "Card payment completed" packet and its responses "ACK" and negative response.
Figure 69 is a diagram showing the configuration of a "periodic data transmission" packet from the payment machine to NAU. Figures 70 (A) and (B) are the "unit recovery data" packet sent to the payment machine and its A configuration diagram of a response "ACK" packet. Figure 71 is a flowchart showing the data transmission control procedure in the data transmission controller of NAU.
Flowchart showing the control procedure for token bus abnormality detection by timer interrupt in U. Figure 73 is a flowchart showing the procedure for initializing the entire system. Figure 74 is the procedure from requesting a unit table by the management device to setting initial values for the unit. FIG. 75 is a system flowchart showing the procedure for periodic data collection from each terminal by the management device. Fig. 76 is a system flowchart showing the processing procedure for issuing a store opening command to each terminal by the management device, and Fig. 77 shows the processing procedure when a card issuance reservation is made and a banknote is inserted into the card issuing machine and the purchase switch is turned on. System Flowchart FIG. 78 is a system flowchart showing the processing procedure when a Su2 card is inserted in an interrupted pachinko machine. FIG. 79 is a system flowchart showing the processing procedure when the interrupt switch of the pachinko machine is turned on during gaming; FIG. 80 is a system flowchart showing the processing procedure when a card is inserted into the pachinko machine during play; Figure 81 is a system flowchart showing the processing procedure when the game end switch of the pachinko machine is turned on during a game, and Figure 82 is the process when both the number of balls held and the amount of money on the card become zero during a game. 83 is a system flowchart showing the processing procedure when a stop occurs during a game; FIG. 84 is a system flowchart showing the processing procedure when a card is inserted into the payment machine; FIG. 85 is a system flowchart showing the suspension termination processing procedure when the suspended card is settled at the payment machine. Fig. 86 is a system flowchart showing the processing procedure when a cancellation cancellation command is entered from the console of the management device. Fig. 87 is a system flowchart showing the processing procedure when a forced termination command for the pachinko machine is entered from the console of the management device. Flowchart. Figure 88 is a system flowchart showing the processing procedure when a forced termination command is input from the console of the management device to the issuing machine or payment machine. Figure 89 is the process for canceling the termination of a terminal that is being forcibly terminated. Figure 90 is a system flowchart showing the procedure for detecting when a unit goes down; the upper figure in Figure 9 shows unit recovery processing in which the management device restores the data on the terminal when the downed unit recovers. A system flowchart showing the procedure, Figure 92 is a system flowchart showing the data recovery processing procedure for each terminal when it detects that the NAU is down, and then the NAU recovers, and Figure 93 is a system flowchart showing the data recovery processing procedure for each terminal by the management device. 94 is a system flowchart showing the system termination processing procedure from a closing command of Figure 96(A)-(
D) is a flowchart showing the initialization procedure of the central processing unit and local processing unit Lf in the management device; FIG. 97 is a flowchart showing the processing procedure when the built-in switch on the back of the console is turned on in the management device; FIG. 98 The figure is a flowchart showing the processing procedure when the setting update switch on the top surface of the console is turned on in the management device, Figure 99 is a flowchart showing the procedure for processing a scheduled data request by a timer interrupt, and Figure 100 is the reception of scheduled data as a response. FIG. 101 is a flowchart showing the processing procedure when the management device receives a “card purchase” packet; FIG. 102 is a flowchart showing the processing procedure when the management device receives a “card in” packet. FIG. 103 is a flowchart showing the processing procedure when the management device receives the "suspension card-in" packet, and FIG. 104 is a flowchart showing the processing procedure when the management device receives the "pause interrupt switch" packet. Fig. 105 is a flowchart showing the processing procedure when the management device receives a “termination switch” packet. Fig. 106 is a flowchart showing the processing procedure when the management device receives a “return to zero” packet. Fig. 107 is a flowchart showing the processing procedure when the management device receives a “return switch” packet. FIG. 108 is a flowchart showing the processing procedure when the management device receives a “cancellation” packet. FIG. 109 is a flowchart showing the processing procedure when the management device receives a “card payment” packet. Flowchart showing the processing procedure when the termination release switch on the top surface is turned on. FIGS. 110, 111, and 112 are flowcharts showing the processing procedure when the forced termination switch on the top surface of the console in the management device is turned on. , Fig. 113, Fig. 114, and Fig. 115 are flowcharts showing the processing procedure when the forced termination release switch on the top surface of the console is turned on in the management device. Fig. 116 shows the power outage processing in the management device when a power outage occurs. 117 is a flowchart showing the procedure for network error recovery processing in the management device, and FIG. 118 (A)
is a flowchart showing the specific steps of the NAU recovery process in the process flow of FIG. 117, FIG. 118(B) is a flowchart showing the specific steps of the token bus recovery process in the process flow of FIG. 117, and FIG. 120 is a flowchart 1 showing the specific steps of the hot code recovery process in the process flow of FIG. 117, FIG. 121 is a flowchart showing the specific steps of the unit recovery process in the process flow of FIG. 117, and FIG. 122 is a flowchart showing the processing procedure when the closing switch on the top of the console is turned on in the management device; FIG. 122 is a flowchart showing the processing procedure when the card restoration switch on the top of the console is turned on in the management device; FIG. A flowchart showing the processing procedure when the test card issuing switch on the back of the console is turned on in the management device. Fig. 124 is a flowchart showing the processing procedure for interrupting sales statistical data display processing using a timer interrupt. Fig. 125 shows the processing procedure when the test card issuing switch on the back of the console is turned on. 5 is a flowchart showing the procedure of data display processing. FIG. 126 is a flowchart showing the procedure of data display processing for a specific machine; FIG. 127 is a flowchart showing the procedure of data display processing for all machines; FIG. 128 is a flowchart showing the procedure of data display processing for red machines; Figure 130 is a flowchart showing the procedure of data display processing for the black balance, Figure 130 is a flowchart showing the procedure of data display processing of the issuing machine, Figure 131 is a flowchart showing the procedure of data display processing of the payment machine, and Figure 132 is a flowchart showing the procedure of data display processing of the payment machine. FIG. 133 is a flowchart showing the procedure for displaying all business data; FIG. 133 is a flowchart showing the procedure for displaying data on a specific card; and FIG. 134 is a flowchart showing the procedure for displaying card total data. FIG. 135 is a flowchart showing the procedure for displaying all card details data; FIG. 136 is a flowchart showing the procedure for displaying data for suspended cards; FIG. 137 is a flowchart showing the procedure for generating card number in the management device; FIG. 138 139 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. 139 is a display screen configuration diagram showing a configuration example of an abnormal terminal display screen displayed on a CRT display device in the management device , FIG. 140 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, and FIGS. 141, 142, and 143 are displayed on a CRT display device in the management device. 144 is a display screen configuration diagram showing an example of the configuration of the initial value setting screen, FIG. 144 is a display screen configuration diagram showing an example of the configuration of the discontinuation number setting screen displayed on the CRT display device in the management device, and FIG. 146 is a display screen configuration diagram showing an example of the configuration of a stop mode setting screen displayed on a CRT display device; FIG. Figure 147 is a display screen configuration diagram showing an example of the configuration of a normal display screen during business hours displayed on a CRT display device in the management device, and Figure 148 is a configuration example of a cancellation cancellation screen displayed on a CRT display device in the management device. 149 is a display screen configuration diagram showing an example of the configuration of a pachinko machine forced termination screen displayed on a CRT display device in the management device; FIG. 150 is a display screen configuration diagram showing a configuration example of a pachinko machine forced termination screen displayed on a CRT display device in the management device FIG. 151 is a display screen configuration diagram showing an example of the configuration of a pachinko machine forced termination cancellation screen; FIG. 153 is a display screen configuration diagram showing an example of the configuration of a payment machine forced termination cancellation screen displayed on a CRT display device in the management device; FIG. 153 is a display screen showing an example configuration of a system termination screen displayed on the CRT display device in the management device 154 is a display screen configuration diagram showing a configuration example of a card recovery screen displayed on a CRT display device in the management device; FIG. 155 is a configuration diagram of a display menu selection screen displayed on a CRT display device in the management device FIG. 156 is a display screen configuration diagram showing an example of the configuration of a stop table display screen displayed on a CRT display device in the management device; FIG. 158 is a display screen configuration diagram showing an example of the configuration of a specific unit display screen displayed on a CRT display device in the management device; FIG. 160 is a display screen configuration diagram showing an example of the configuration of a red line data display screen displayed on a CRT display device in the management device; FIG. Figure 161 is a display screen configuration diagram showing an example of the configuration of the payment machine data display screen displayed on the CRT display device in the management device; A display screen configuration diagram showing a configuration example; FIG. 163 is a display screen configuration diagram showing a configuration example of a specific card data display screen displayed on a CRT display device in a management device; FIG. 164 is a display screen configuration diagram showing a configuration example of a specific card data display screen displayed on a CRT display device in a management device. 165 is a display screen configuration diagram showing an example of the configuration of a card details data display screen displayed on the CRT display device in the management device; FIG. FIG. 167, FIG. 168, and FIG. 169 are flowcharts showing the procedure of packet transmission and reception control in NAU. 170(A) to 170(C) show the transition of the operating state of the pachinko machine, in which FIG. 170(A) shows the normal operating mode;
B) is a state transition diagram in online test mode, and (C) is a state transition diagram in offline test mode. Figures 171 to 178 show the transmission/reception and processing procedures between each controller in the control unit of a pachinko machine. Figure 171 is a flowchart when initialization and opening packets are received, and Figure 172 is a flowchart for receiving a card to a card reader. Flowchart when inserting. FIG. 173 is a flowchart when the interruption switch is turned on, FIG. 174 is a flowchart when the settlement switch is turned on, and FIG. 175 is a flowchart when a zero state occurs. Fig. 176 is a flowchart when a termination state occurs, Fig. 177 is a flowchart when a ``forced termination'' packet is received, and Fig. 178 is a flowchart when the unit is restored after a power outage is recovered. Fig. 179 ~ Figure 192 shows the task processing flow of the unit controller. Figure 179 is a flowchart showing the procedure of timer interrupt processing, Figure 180 is a flowchart showing the procedure of serial interrupt processing, and Figure 181 (A). (B) is a flowchart showing the specific steps of sensor and switch detection processing and switch invalidation processing in the interrupt processing flow of FIG. 179. FIG. 182 shows the procedure of the initialization task, which is one of the main tasks of the unit controller. Flowchart, FIG. 183 is a flowchart showing the procedure of the packet reception task, FIG. ) is a flowchart showing the specific procedure for receiving the "opening code" packet. FIG. 184(C) is a flowchart showing the specific procedure for receiving the "closing code" packet. FIG. 184(D)
184(E) is a flowchart showing a specific procedure for receiving a "forced termination request" packet, and FIG. 184(E) is a flowchart showing a specific procedure for receiving a "forced termination cancellation" packet. Flowchart showing the specific procedure of “release” packet reception processing, FIG. 184 (G)
184(H) is a flowchart showing the specific procedure for receiving a "unit recovery data" packet, and FIG. 184(I) is a flowchart showing the specific procedure for receiving a "suspension end" packet. A flowchart showing the specific procedure of packet reception processing, FIG.
184 (K) is a flowchart showing the specific steps of the packet reception process. FIG. 184 (L) is the flow chart of the "termination switch ACK" packet reception process. FIG. 184 (M) is a flowchart showing the specific steps of the “return ACK” packet reception process, and FIG. 184 (N) is the specific procedure of the “stop ACK” packet reception process. FIG. 185 is a flowchart showing the procedure of the reader control task, which is one of the main tasks of the unit controller, and FIG. FIG. 186(B) is a flowchart showing the specific procedure for receiving the "card number" function during the reader control task. FIG. 186(C) is a flowchart showing the specific procedure for receiving the "card number" function during the reader control task. FIG. 186(D) is a flowchart showing a specific procedure for receiving a "retransmission request" function during the reader control task; FIG. 186(E) is a flowchart showing a specific procedure for receiving a "status"function; 3 is a flowchart showing a specific procedure for receiving a "normal end" function during the reader control task. FIG. 186(F) is a flowchart showing the specific procedure for receiving the "abnormal end" function during the reader control task, and FIG. 186(G) is a flowchart showing the "initial value request" function receiving process during the reader control task. 186(H) is a flowchart showing the specific steps of the "self-ejection" function reception process in the reader control task; FIG. 186(I) is the reader control task 3 is a flowchart showing a specific procedure of function transmission processing in the process. FIG. 187 is a flowchart showing the procedure of the packet transmission task, which is one of the main tasks of the unit controller. FIG. 188 is a flowchart showing the procedure of the error control task, which is one of the main tasks of the unit controller. FIG. 190 is a flowchart showing the procedure of the pitch count calculation task, which is one of the main tasks of the unit controller. FIG. 191 is a flowchart showing the procedure of the switch detection task, which is one of the main tasks of the unit controller. 190 is a flowchart showing the specific procedure of the abort process during the switch detection task; FIG. 191(b) is a flowchart showing the specific procedure of the abort switch process during the switch detection task of FIG. 190; 191(d) is a flowchart showing the specific steps of the end switch processing during the switch detection task of FIG. 190. 1. Fig. 191(e) is a flowchart showing the specific procedure of the test switch processing during the switch detection task of Fig. 190, and Fig. 191(f) is a flowchart showing the specific procedure of the test switch processing during the switch detection task of Fig. 190(d). 192 is a flowchart showing the steps of the sound control task which is one of the main tasks of the unit controller; FIG. 193 is a flowchart showing the steps of the sound control task which is one of the main tasks of the unit controller; FIG. 193 is the timer control which is one of the main tasks of the unit controller. 194 is a flowchart showing the procedure of a lamp display control task which is one of the main tasks of the unit controller; FIG. 195 is an input/output timing chart of the unit controller. 100...Pachinko machine, 110...Operation panel, 113...Purchase switch, 114...Interrupt switch, 115...End switch, 130...
Ball circulation device, ↓60... Control unit, 180...
... Unit control device, 188 ... Card reader control device, 195 ... Pachinko machine control device, ↓90.
...Unit controller, 200...Card issuing machine, 700...Card issuing device, 710...
Card ejecting device, 740...Card reversing device, 75
0...Printing device, 770...Card extraction device,
300...Payment machine, 400...Management device, 55
0...Unit memory, 551...Data transmission controller, 553...Network controller, 800...Card reader, 802...Card insertion/ejection opening, 807...Transportation motor , 809...
Shutter solenoid, 820... Punch device, 82
1...Magnetic head. 5rjE':' Fig. 2 (B) Fig. 2 (C) S in the 1st direction → & 81 atas 84at86By day aB9111
111111 1 o 10 +001 Direct (D) (A) Figure (B) 846 (A) 28 Figure 29 (B) 84kodυ→ (B) Gu G) CJ OLI LL (Ri (A) 4th Figure (B) Figure 60 Figure (A) (B) Various command packets CK 818 Figure 62 "Periodical data transmission" packet Figure 61 (A) "Card-in" packet configuration Management device ← NAU (Card N0) NAU ←Control unit (card No.) Fig. 6↓ (C) “Card-in” packet configuration (negative response) Management device → NAU (NAK) NAU → Control unit (NAK) (A) Fig. 6 “Card purchase” ” packet (at the time of issuance reservation) (B) Figure (A) Figure “Unit recovery data” packet (B) Transmission data area (A) (A) Figure “Card payment completed” packet (B) Unit U Recovery data” packet (B) -26・Figure 1 37 JP-A-3-242183 (200) Figure J1170 Figure 170 (B) (C) “Offline” Parking Figure 1 79 Figure 1 80 Figure 1 82 91 98 Fig. 184 (D) (E) 2703- Fig. 184 IGI (H) (K) Fig. 184 (G) Fig. 186 Fig. 1 91〇- Low Yamaguchi.

Claims (1)

[Claims] (1) Transmission of a gaming machine in which games can only be played with a card on which an identification code is recorded, an issuing device that issues the card, a storage medium settlement device that settles the valuable data of the card, and a management device thereof. Valuable data substantially equivalent to the amount of money or the number of balls is managed in a management device for each identification code given to the card, and the gaming machine uses the identification code read from the card. In a card-type gaming system that allows games to be played within the range of valuable data obtained from the above-mentioned management device, the above-mentioned payment machine is equipped with means for determining the status of the card, and performs payment processing for suspended cards. A card-type game system characterized in that it is configured to perform settlement only for cards that are rejected and are in a free state.