JPH03242182A - Card type game system - Google Patents

Abstract

PURPOSE:To impartially give a game chance to all game customers by providing a switch for stopping the game control by discharging a card and migrating to a state the game can be executed again only by throwing in the same card, on a game machine. CONSTITUTION:When a game customer operates an interruption switch 114 for taking a rest although he has no mind to stop the game, a controller 180 of a unit controller 160 drives a card reader 800 and discharges temporarily a card through a pinball machine controller 195, and the machine becomes a holding state until the same card is inserted again, and does not receive other card during that time. Simultaneously, a managing device connected through a low layer network monitors an elapsed time in the course of interruption, and releases the pinball machine 100 being in the course of interruption to other game customer, when the time exceeds a prescribed time and becomes long. In such a way, the game chance can be given impartially to all the game customers without spoiling profits of the game customer.

Description

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

[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-1.7106).

[Problem to be solved by the invention] By the way, in current pachinko parlors that do not use cards, when a player is away from the game machine for a long time, the staff member removes the game balls from the tray and gives them to other players. For this reason, it is released.

However, in cart-type gaming systems, games cannot be played without the presence of cards, so if you leave the gaming machine without cards, there is a risk that your cart will be stolen, and if you do not have cards with you, you may If the player leaves the gaming machine, there is a risk that other players may take away the right to play at the gaming 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 this is done, if the suspended state of a particular gaming machine is viewed for a long time, the suspension by the gaming parlor staff, which was normally done in the past, because the player has a card. As a result, the game parlor's desire to provide fair gaming opportunities to all players cannot be achieved. In addition, for game machines that have been interrupted for a long time, it may be possible to turn off the power and restart the machine, but this would erase the data up to that point, which would be inconvenient to the player in question.

The present invention was made against the above-mentioned background, and is designed to improve the interests of players in a card-based gaming system that allows players to leave the gaming machine while retaining their gaming rights. To provide a fair gaming opportunity to all players without compromising the quality of the game.

[Means for Solving the Problem] In order to achieve the above object, the present invention connects a plurality of gaming machines and a management device through a transmission line, and transmits valuable data substantially equivalent to the amount of money or the number of balls to the card. The management device manages each identification code given to the game machine, and 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 inserted into the gaming machine. In the card-based gaming system, the gaming machine is equipped with a switch for discharging the card, stopping the gaming control, and returning to a state where the game can be played again only by inserting the same card, and the management device is equipped with the above-mentioned switch. A means for counting the duration of interruption after the switch is turned on is provided, and the interruption duration can be displayed externally according to an instruction from the console.

[Function] According to the above-described means, it is possible to leave the gaming machine in which the game is being played while retaining the gaming rights, and it is also possible to monitor the elapsed time of the gaming machine during the suspension using the management device. If the time interruption continues, the suspended gaming machine can be forcibly released for other players by commands from the management device, so that the game machine can be forcibly released for use by other players, without harming the interests of some players. It becomes possible to provide fair gaming opportunities to players at

[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 device 400 and this management device 14
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 100, the issuing machine 200, the payment fi 300, and the management device 4°, which are the components of the organic combination, are each equipped with a cart reader (in this specification).

A device that writes on the magnetic surface of the card is also called a cart reader), and information on the card and information on each terminal is stored in the form of a file in the storage device of the management device [400]. It looks like this.

Next, before going into a specific explanation of each component of the above-mentioned organic composite, the cart 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 reviving a damaged cart
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 cart status without having to read and check the number of balls data from the management device 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 MO 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 cart of this embodiment, between the print display part PRT and the magnetic recording part MG, that is, in the center of the card, there is a belt-shaped roller running area RRA that is slightly wider than the transport 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 are designed so that the legs of each letter are located at positions corresponding to the detection bit patterns B, -B9, which are provided at a pitch of 3°5-, etc., as shown in Figure 2 (C). Print it out. And the character width is 0.5~1゜5
m, the distance between each bit is 3.5 digits, and each bit's "1" or "O" is expressed by the shading of the character.Moreover, 1
Among the 0 bits, the fifth bit B4 from the left and the last bit Bg are bit B.

The shading of the characters is determined in advance to represent the parity of ~B3, B, and ~B9. Note that it is more preferable that the security bit hidden in this character string be formed using a special ink that can be detected only by a sensor and is indistinguishable to the human eye.

Further, on the surface of the game cart 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 section MG is provided, it is arranged as shown in FIG. 2(D).

A white layer 3 is formed on a magnetic layer 12 made by uniformly coating magnetic particles on a base material 1 made of plastic such as polyester, and then a pattern printing layer 14 is placed on top of that. A thermosensitive coloring layer 15 is formed in the area (corresponding to the print display area PRT), and a transparent protective film 16 is formed above it.
It is coated with. In addition, the cleaning area HC
A cleaning agent of the same color as the white layer ↓ 3 is applied to N, and the surface is exposed so that the protective film 16 is not coated, so that the cleaning area is hardly different in color from other parts. , aiming to improve the aesthetic appearance. Further, a pattern printing layer 17 is formed on the back surface of the base material 11 of the cart, and the top thereof is coated with a protective film L8.

In a card with the above structure in which the white layer 13 is formed on the surface of the magnetic layer 2, the magnetic layer 12 made of black magnetic particles is covered with the white layer 13, so the picture It becomes possible to provide fashionable carts by printing
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 susceptible to destruction, improving the reliability of the cart.

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 MO of the card of this embodiment is composed of two tracks, of which clock data providing sampling timing is recorded in the first track TRCl. 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 Game parlor identification code DSC1Year month date data DATE, card number N
o Text field T containing the issuance command code FNC given by the card reader when issuing the card and the security data SDC read from the authenticity discrimination area
XT, a field ETX containing a text end code, a field LRC containing an exclusive OR value (detection code) of the text data and the end code, and a field STX containing a start code. Moreover, date data D
ATE has a bit P indicating parity for each 4 bits, and the first 4 bits
The month is recorded using the 6th to 9th bits and the 1st bit of the clock, and the 12th to 14th bits and the 16th to 19th bits are used to convert the last two digits of the year into binary code. It is supposed to be done.

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.

Further, as described above, the information recorded in the magnetic recording section of the card of this embodiment is the identification code DSC for specifying the usable space of the card.

Issue date DATE and 1 to indicate the validity period of the card
Only the power number as an identification code obtained from the issued serial number n using an appropriate function or conversion method and a check code for error detection are recorded, and the purchase price 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 1400 based on 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 13.

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 lOO, and mainly controls the display and card reader and controls the operation data during the game. and a control unit 160 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 OO, there is a ball launcher ↓03 that launches the enclosed balls one by one into the game area, and its operation dial 104. Also, above the operation dial 104, the above-mentioned card is used. an amount display 111, a number of balls display 112, a purchase switch 113, an interruption switch 114,
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 two-knit controller 190 once ejects the card and enters a standby state until the same card is inserted again.

During this time, no other cards will be accepted. Incidentally, among the above-mentioned switches, the purchase switch 113 has a built-in lamp, and when the number of balls held reaches rOJ, the lamp inside the purchase switch 113 blinks.

As shown in FIG. 4, the operation panel 110
It is attached to the front panel 105 that can be opened and closed at the bottom of the OO,
The operation panel 110 has a hollow shape with a triangular cross section, and its upper surface is sloped downward toward the front to make the display easy to read.
Wiring boards 12OA 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 120A, 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
A portion corresponding to 15 is an opening 117b (see FIG. 5). An operation button 118 is mounted inside this opening ↓17b so as to cover the upper part of each of the switches ↓3-115. [Eng. 2], is the purchase switch 11
It is a built-in lamp compatible with 3.

Further, at the front end of the operation panel 110, there is provided a game status display section 116 in which a display lamp ↓ 23 is covered with a translucent Fresnel lens 119 or the like.
3 is a batted ball launcher]-03 is turned on by turning the operation dial 104.

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 120C disposed within 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 195 disposed at the bottom of the back of the pachinko machine by connectors 127A to 127C coupled to their ends.

On the other hand, a pachinko machine constituting the gaming machine of this embodiment], O
O is configured as a closed game machine that circulates game balls sealed inside the machine, and has an enclosed ball circulation device ↓30 on the back side that circulates the enclosed balls.

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 gathering gutter 131 is sloped downward toward the center to form a guide shelf 131a, and below that, as shown in FIG. An integrally formed guide @132 is provided. A photoelectric out sensor 5NS consisting of a pair of light emitters and a light receiver is installed in each part of the guide gutter 132.
I, first safe sensor 5NS2, second safe sensor 5N
S3 is installed. In addition, the guide @ 182 is equipped with a merging machine part 132d that collects the balls that have flowed into each type into one place, and the end of the merging machine part 132d has a gentle shape that allows the pachinko balls to line up in a line, as shown in FIG. It is connected to the upstream side of the inclined guide @133, thereby forming an enclosed ball circulation system W130. And information @13
On the upstream side of 3, there is a foul ball receiving port 134 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 (see Figure 9). A foul line gutter 133a is formed integrally with the foul line gutter 133a, which is arranged so as to face the foul ball, so that the foul ball is merged with the ball that has flown down onto the guide @133 via the guide @132. foul line gutter 133
A foul sensor 5NS4 is disposed in the middle of a.

Then, facing the lower end of the guide @133, a ball -
A ball feeder 135 is swingably mounted to separate the balls on the guide @ 133 one by one and cause them to flow downward.

A stopper 136 is fixed to the rear of the ball feeder 135, and prevents the ball feeder 135 from rotating more than necessary, so that when the ball feeder 135 rotates downward due to the weight of the inflowing balls, the upper end surface of the stopper 136 serves as the guide 4ii133. It is designed to prevent the balls above 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 circulating 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 ball removal mechanism 138 can be slid to remove the ball.

Furthermore, an elastic locking piece 133a is fixed to the end of the guide gutter 133, and by engaging this with the engagement step 149 of the frame boat 109, the enclosed ball circulation device 130 can be prevented from rotating. It can be fixed.

The pachinko balls separated by the ball feeder 135.

Frame board 1 arranged behind the front panel 105
One ball passes through a ball passing hole L39 (see FIG. 9) formed in 09 and flows down to the base of a firing rail 140 diagonally fixed to the front surface of the frame board. A firing rod 103a is arranged so as to face the base of this firing rail 140 (see FIG. 10). Along with this, launch rail 1
An interlocking member 141 is disposed below the base of the ball 40 and has a push-up piece 141a that is rotated in conjunction with the firing rod 103a and pushes up the ball feeder 135 upward.

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 rear of the frame boat on the frame board 109 corresponding to the upper end of the first 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 of the frame board 109. 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 ↓06 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 08 so that it can be opened and closed using one end (left end) as a fulcrum, and the firing rail 14 is attached to the back side of the opening.
0 and is located above the launch rail frame 15.
A notch 51a is provided in the middle of the firing rail frame 151 so that the firing sensor 5NS5 can face inside the frame. Also.

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 in the front frame 10'8 so as to be openable and closable. On the other hand, the front frame 10
On one side opposite to the hinge part 102 on the back side of 8, there is a 12th
As shown in the figure, a locking tool 156 and a locking device 157 for locking the front surface to the machine frame 101 are attached. Further, 155 is a lever for opening the glass frame 154.

The frame 106 holding the game board (see the first upper figure) and the frame board 109 are placed on the back side of the front frame 108, and the fitting protrusion 106b on the back side of the frame is inserted into the fitting receiving part 108b on the back side of the front frame, and the fitting protrusion 106b on the back side of the frame board is placed on the back side of the frame board. The front frame 108, the frame 106 holding the game board, and the frame board 109 are integrated by aligning the fitting protrusions 109b, joining them, and screwing them together.

FIG. 13 shows a state where the frame 106 and frame boat 109 are attached to the back side of the front frame 108 in this way, and the winning ball collection 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.

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

4 to 16 show an embodiment of a control unit 160 configured separately from the pachinko machine 100.

The control unit 160 of this embodiment includes a status display 162 on the front side of a storage frame 61 that shows the status of the pachinko machine, and an analog display 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 cart holding indicator lamp 167 (LED↓) that indicates whether there is a cart in the card reader.
A card insertion indicator lamp 168 is arranged below the card insertion/ejection opening 802a to indicate whether or not a card can be inserted into the control unit 160.

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 having L32 (see Figure 6)
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, a card reader 800 is installed.
A unit controller 190 that controls the entire control unit 160, transmission means, monitor display devices 174, 175,
Unit controller 180 and card reader controller with 176! ! 188 and a power supply device 177 are built in. Further, below the card reader 800, a storage box 178 for storing punched pieces produced when punching is performed by a punching device (described later) in the card reader 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 1.8 in the control unit 160
0 is connected to the control bag [195] of the pachinko machine 100 via a transmission line such as an optical fiber or coaxial cable, and also to the transmission controller and local network (described later).
transmission cable) to the management device 400.

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 16 (the 20th (see figure).

18 to 20 show an example of an island facility on which a gaming machine consisting of the pachinko machine 100 and the control unit 160 is mounted, and a state in which the gaming machine is installed therein.

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
At a height of about 00, a horizontal mounting table 23 is mounted on a support 22.
It is fixed at . Further, above this mounting table 23, a first installation shelf 24 is located at a distance corresponding to the height of the machine frame 101, and further above that, a second installation shelf 25 is fixed with a support 22. At the same time, a top plate 26 is fixed above the second installation shelf 25 so as to cover the upper end of the support column 22. Note that the front end of the above-mentioned mounting table 23 is connected to the support 2.
The first installation stand 2 is made to protrude slightly in front of the
4 is arranged so that its front end is located behind the support column 22 by the thickness of the machine frame 101.

Each pachinko machine 100 is placed on the mounting table 23 between the supports 22 together with the machine frame 101, 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! be done. Further, a transmission path (not shown) constituting a local network is extended on the second installation stand 25, and data is transmitted between each support 22 and the management device 400 via the transmission path. A transceiver 185 is mounted for the purpose. Note that the front of the transceiver 185 is closed by an upper plate 27, and the lower part of the mounting table 22 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 a control system for the entire gaming machine consisting of a pachinko machine 100 and a control unit 60.

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 perforated bag [820]. Various switches 171, 179 and displays 162, 163, 164, 168, . The speaker 166 is controlled by a unit control device 1180.

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 bag [180 and the optical fiber cable 191 and at the connection portion between the optical fiber cable 191 and the pachinko machine control bag W195 (described later).

The optical fiber cable 191 is connected to the unit control devices 1 and 80.
By using it for data communication between the machine control bag W195 and the Pachinko machine control bag W195, it simplifies the large number of wires that were conventionally arranged in a complicated manner on the back of the Pachinko machine, making maintenance and management easier, and reducing the noise caused by noise. Malfunctions can be prevented.

Under the control of the pachinko machine control device 195, the control device 1 controls the amount display 111, the number of balls display 112, the purchase lamp 121, the game status display lamp 123, and the ball launcher 103.
94 and the accessory control device 58 are placed, as well as a purchase switch 113, an interrupt switch 114. Ball detection sensor 5NSI such as end switch 115 and out sensor
The signal from the 5NS5 is waveform-shaped by the pachinko machine control device 195 and then supplied to the unit control device 180. In this embodiment, the power supply system is two systems, AC24V and AClooV, and the pachinko machine 1
Supply AC24V to the 00 side.

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 above pachinko machine control device 95.

The pachinko machine control device 195 includes a pachinko machine controller CPTJ↓ consisting of a microcomputer, and a reset circuit R3T1 that monitors periodic watchdog pulses output from this controller CPU1 and generates a reset signal when the pulses are interrupted. , a multiplex transmission system equipped with a parallel-to-serial conversion means for converting parallel transmission data into serial data and a serial-to-parallel conversion means for converting serial reception data into parallel data in order to enable optical data transmission with the unit control device 'L80. Controller CN
T1 and optical cable ↑91 via optical connector 193
The photoelectric conversion circuit connected to ○ET.

A filter circuit FLT that cuts noise in detection signals from various sensors, and decoders DEC1, DE that decodes display data on the amount display 111 and ball number display 112.
It is composed of drivers DRVI and DRV2 that form drive signals for the display based on C2 and its output, and a driver DRV3 that forms drive signals for the purchase lamp 121, game status display lamp 123, and batted ball firing device 103.

Regarding the processing of the detection signal from the sensor in this pachinko machine control device 1195, 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 180 as detection data of launching 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.
It is supposed to be done on the 80's side.

In addition, pachinko machines tend to generate noise due to static electricity, etc., but the reset circuit R that monitors the watchdog pulse
Because of the presence of 5Tl, even if the pachinko machine controller CPUI goes out of control due to noise or the like, when 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 collectively controls the cart reader control device 188 and the pachinko machine control device 195 to enable pachinko games using cards. It is composed of a transmission controller 551, a network controller 553, etc., which establishes receivables in the network and performs serial/parallel conversion of 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). It has a buffer function to measure the speed (2.5 Mbps).

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. 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.

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

Furthermore, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store the data reception result in response to a request from the 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 LEDs for indicating an abnormality in the communication control state within the unit control device 180. Monitor display 55 consisting of a lamp
A latch circuit 564 is provided to store display data for 6. A decoder 557 decodes the address given to each of the latch circuits 561 to 564 and generates a selection signal.

On the other hand, between the unit controller 190 and the cart reader control device 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 573 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 signals, places input signals from various switches provided in the pachinko machine ↓00 and control unit 160 on the data bus 581 at predetermined timing, and latches output signals that display various lamps. an input/output controller 576;
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 and improves the sound quality, and 584 is an amplifier that adjusts the volume. Among these, the audio sound 4LSI 582 stores multiple audio data in its built-in EPROM. ,
Selection signal given from unit controller 190 (
So to S3), select the audio data 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 controls the management device 40
0, the card reader control device 188, and the pachinko machine control device 195, which have information exchange windows on three sides, and control the pachinko game using cards under the control of the management device 400, as well as control the game. It has software that periodically sends the resulting pachinko machine game information to the management device. Furthermore, in the unit control device 180 of this embodiment, among the display data output from the unit controller 190 to drive the amount and number of balls display, the digit select signal (common signal) is, for example, 2 m s. Focusing on the point that is periodically output at intervals, 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.

In addition, the unit controller]-90 has an internal timer counter, and if an ACK (affirmative) or NAK (negative) as a response to a transmission request is not returned within a certain period of time (ex, 10 seconds). ,ACK
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 easily resolved by, for example, writing a specific code (A55A, etc.) to a predetermined address in the memory during initialization, and checking it every 1 millisecond using interrupt processing. can be detected.

Furthermore, the unit control device ↓80 of the embodiment.

Even when the data transmission controller 553 cannot transmit data within a certain period of time (5°12 seconds), the unit controller 190 is initialized, and abnormal data is transmitted to the management device 140.
Measures are taken to prevent the data from being sent to 0. That is, in the embodiment, a watchdog counter area is provided in the unit memory 550, and the data transmission controller 551
sets a predetermined coat FF each time it sends data to the management device, and the unit controller 190
This counter is counted down by "work" every m5. Therefore, if the data transmission controller is 5.1
If the state in which transmission is not possible continues for more than 2 seconds, the watchdog counter of the unit memory 550 becomes rOJ, so monitor this counter and say, ``If it becomes OJ, it is determined that the data transmission controller 551 has gone down. You can reset it yourself.

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 predetermined location, turns on the terminal INT, and inputs the signal from that terminal 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 bag w400 at the time of system startup is performed by the data transmission controller 551. This is done by sending to.

By the way, as mentioned above, the pachinko machine control device 195 side does not calculate the number of safe balls, etc., but such calculations are performed on the unit control @l1l180 side. Detection signals related to game balls, such as signals, and signals from the purchase switch 113 are input.

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. Then, they are written in 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, the data sent from the management device 400 is also temporarily written in the reception data area RDA in the unit memory 550, and the unit controller ↓90 reads this 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 DWA for each controller, and area C3A for synchronization between controllers. is provided.

Pachinko machine surface unit memory Table 3 Table 4 Figure 24 shows the overall configuration of the unit memory, and Table t, Table 2 and Table 3 show the transmission data area SD A
, shows a configuration example of a reception data area RDA and a communication area CCA.

The monitor information shown in Table 1↓ is based on Table 4.
As shown in the figure, 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 (2 pins for low layer and 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, ooooooo
ooooo toooo.

It can be seen that it is expressed as

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

A box-shaped case body 80 (
A front M802 having a card holding display section LED1 and a card insertion/ejection port 802a is attached to the front end of the case body 801, and a single character is provided on the side wall of the case body 801 for fixing it in the storage frame 161 of the control unit 160. Brackets 803 are fixed at the four corners.

As shown in FIG. 26, a base plate 804 serving as a cart 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 cart. is ready to be installed.

On the support substrate 805, located on the side of the cart insertion opening, there are mounted a cart insertion detection sensor 808 consisting of a motor 807 and a microswitch, a cart 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 sensor 810a) is used, and the other sensor (8↓Ob) is provisionally provided so that the number of security coats 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 in the center of the 0-Ra shaft 81↓, and one end of the 20-Ra shaft 81↓ is made to be able to protrude outward from the side wall 801a of the case body, and a pulley 813 is provided at the protruding end. is fixed. In addition, a card position detection sensor 5NS is installed near the shutter solenoid 809.
A light projector 814 is attached to irradiate detection light to the 20th-L shaft 811 and the motor 807, and a light-transmitting part 8 through which the detection light of the second position detection sensor 5NS2 can pass.
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 conveying roller 823 is fixed to the center of the first roller 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.
Further, a belt 827 is wound between pulleys 824 and 813, and the rotational driving force of the motor 807 is applied 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 801a, 801b of the case. This interface board 830 receives various control signals from the card reader controller L88 provided in the control unit 160, and passes read signals from the sensor and magnetic head provided on the card 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 8 2 and 8.
Auxiliary rollers 836 and 83 are biased upward by torsion springs 834 and 835 at positions corresponding to 23.
7 is an opening 84↓, 84 formed in the head plate.
It is attached so that the face is slightly exposed than 2. Also,
On the base plate 804, there is an auxiliary roller 83, which is similarly biased upward by a torsion spring 836, at a position corresponding to the magnetic head 821 attached so as to face downward from the through hole 822 provided in the support base @806.
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 lower surface of the base plate 804 with screws, and on this second interface board 848 there are a circuit for interfacing with the card reader controller 188, and the projector 81. 6,828,829
and 831, first to fourth position detection sensors 5NSl, 5NS2, 5NS3, 5NS4 and punch hole detection sensor 5NSp are attached.

Further, relief holes 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 that is slightly larger than the shielding member 846 is formed at the front end of the upper support substrate 805. Support substrate 8
05, the shielding member 846 is housed in the empty space 85↓ 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 projects into the cavity 851 from the opening 853. The tip of the movable contact 808a is normally shown in FIG. 28(A). It is 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 cart reader 800 of this embodiment has a structure in which the rear wall of the case is open and cards 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
The security code reading sensor s10a t810b is arranged between the first position detection sensor 5N and the first position detection sensor 5N.
It is located almost right next to the SI. Further, the second position detection sensor 5NS2 is arranged behind the transport roller 812, the third position detection sensor SNS 3 is arranged behind the transport roller 823, and the fourth position detection sensor SNS 4 is arranged at the innermost part of the cart leader. , and the first to fourth position detection sensors 5NS1
~S N S 4 are located on the same straight line.

Furthermore, the punch hole detection sensor 3NSp and the punch pin PP are connected to the second position detection sensor 5NS2 and the conveyance roller 82.
3, and the magnetic head 821 is placed between the transport roller 8
23 and the third position detection sensor 5NS3.

FIG. 30(B) shows the cart detection timing when a card is inserted by various sensors arranged in the positional relationship as shown in FIG. 30(A), and the timing of control signals 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 card and drives the motor and shutter.
4, the information on the cart 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 cart reader control device 188 includes a card reader controller CPU2 consisting of a microcomputer, a transceiver TRV that performs level conversion of data signals transmitted and received between the unit control device 180, and a control unit 1.
Drivers DRVI L and DRVI 2 form drive signals for the monitor display 175 and 1-76 provided in the monitor 60.
and inside card reader 800 +7)-11=-9807
driver DRV13 that forms control signals that drive the perforation device 1820, magnetic head 821, LED lamp 167, and shutter solenoid 809; driver DRV14 that drives relay RLY that turns on and off the power supplied to motor 807; A waveform shaping circuit SM consisting of a Schmitt trigger circuit that shapes the waveforms of data read by the magnetic head in the reader 800 and detection signals from various sensors.
G, flip-flop circuit F/Fl, F that latches each read data of two tracks read by the magnetic head;
/F2, a power-on reset circuit, and a watchdog timer are built in, and the pulse periodically output from the controller CPU2 (shared with the reset pulse of latch LTI and LT2) is monitored as a watchdog pulse, and when the pulse is interrupted, Reset circuit R that generates a reset signal
3T2.

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 LED1.1 that lights up while the power is on, and a card-in display that indicates that the card is in the card reader. It is used as an OK display LED 13 that lights up when control by the card reader controller is normally executed.
The LED 14 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 contents of the card reader abnormality 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 cart 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 cart running control, card data reading, card data checking, etc., and transmits the cart 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 cart reader 800 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 same figure, the symbols SMGI to SMG 5 are waveform shaping circuits consisting of Schmitt trigger gates, etc. RECI and RFC2 are rectifier circuits, and MCCl and MC
C2 is the magnetizing current switching circuit, AMP↓~AMP4 is the amplifier, MHDI, MHD2 is the magnetic head, MT is the motor, 5
OLI, 5OL2 are solenoids, LEDI is light emitting diodes, DRV21, DRV22 are drivers, 5NSII
, 5NS1.2, 5NSp, 5NS1. ~SNS
5 is a sensor. 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 SMG]
, , is sent to the card reader control device 188 as a rectangular wave through the MG3. 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 5MG2 and 5MG4, and the write data l(I
The direction of the head drive current is switched according to TT, l(OTT, amplified by amplifiers AMP2 and AMP4, and supplied to magnetic heads MHDI and MHD2.

In order to drive 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 (
810a), 5NS12 (unused), punch hole detection sensor 5NSp, position detection sensor SNS↓~5NS4, speed detection sensor 5NS5 (821) The detection signals are waveform-shaped by the waveform shaping circuit 5MG5 and then sent to the card reader control device↓ 88, the detection signal of the insertion detection switch 808 is noise-cut by a low-pass 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 card reader control device ↓88.

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 tally information. In addition, the card reader control device 1 of FIG. 31 is shown in (N) to (R) of the same figure.
At 88, the timing of each signal is indicated by the symbols a''-e.

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 output signals, and the (J) and (M) signals are waveform shaping circuits SM, G1 and 5MG3.
The output signals of are shown respectively.

In this embodiment, the so-called NRZI method is adopted as a write method, in which the polarity is inverted when the data is u1'', and the previous state is maintained without inverting the polarity when the data is ii O11 or there is no signal. .

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

On the other hand, when the data written in the above manner is read by the magnetic head MHD2, when the magnetization state (D) changes, the output of the amplifier AMPI changes to + or - depending on the direction of magnetization, so the cart reader Controller CP
U2 outputs a signal a (
If the signal N) is at a high level, it is recognized as data "'1", and if the signal a is at a low level, it is recognized as data 1101t (see FIG. 33(S)).

In this example, the recording density of magnetic data on the card is 4.134 bit/mm (=1058 PI), and the card transport speed is 300 mm/sec, so the pulse period of the read clock data is approximately bO6 μs. Therefore, when writing magnetic data by the CPU 2, the cycle T of the CPU output (E) with respect 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 210 that identifies bills for card purchase, and an issuing device 700 that prints an amount corresponding to the inserted bill and issues a card.
and a unit control bag [280 etc. for data communication between the banknote dispensing device 230 for dispensing banknotes 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, a front panel 201 that can be opened and closed is provided with a banknote insertion slot 211, a group of purchase selection switches 212, and an amount display 213. Therefore, when a player first inserts a bill into the bill insertion slot 211, the amount of money inserted is displayed on the amount display 213. By pressing the switch corresponding to the desired purchase amount from the purchase selection switch group 2, the card corresponding to the desired purchase amount is issued to the issuing device 7.
00 is issued from the card ejection port 202. The purchase selection switch group 212 is composed of switches each with a built-in lamp, and when nine banknotes are inserted, there are switches that can be selected within the range of the inserted amount (three for 3,000 yen, three for 5,000 yen). The built-in lamps corresponding to 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, there is an issuing lamp 221 indicating that the card is in a state where the card can be issued, and an issuance stop lamp 22 that indicates the state where 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 the remaining balance. In addition, cart 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 cent button for resetting the display on the monitor display 206. 207 is provided.

Furthermore, the card issuing machine 200 of this embodiment is configured such that each of the plurality of issuing machines (several tens of machines) installed in the game parlor can be distinguished from each other so that the management device 400 can grasp which issuing machine has issued a particular card. A machine number setting device 205 is provided inside for this purpose.

The machine number set by this setting device 205 is
00, and is used to generate a transmission address during data communication and create a data file for each issuing machine.

On the other hand, the issuing device 700 takes out the blank cart stocked in the card tank 701 sheet by sheet, first sends them to the card reader 800, and the cards are calculated by the management device 400 and sent to the magnetic recording section of the cart. Record the card number, identification code (store code), issue date code, check code, etc., and punch a hole at the issued hole position PH1 (see Figure 2) using the punch device 1820 in the card reader soo. 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 cylinder panel 201. The above issuing serial number n is determined by the management device 400, which receives a card purchase application from the card issuing machine 200, when the management device 400 receives a purchase application from a plurality of card issuing machines under its control.
At the reception, the issuing serial number is determined in order, and the number is given to each cart issuing machine.The code obtained by performing code conversion processing such as rearranging the bits mentioned above based on this issuing serial number n is applied to the card. A number is recorded on the magnetic surface of the card and issued, and information regarding the card is stored in the management device 4.
It is designed to be recorded in a file within 00.

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 the issue 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.
The card is kept on standby with one rOJ printed on it, and when the purchase switch is pressed, a thousands digit number is printed and ejected, thereby reducing the apparent time required for issuance.

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 700 of this embodiment includes a card ejecting device 710 that takes out cards one by one from a card tank 701 in which a large number of carts each having a blank magnetic recording section MG and a print display section PRT are stored; 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. card issuance control device 790 disposed above the card reader 800.
It is now controlled by. The card reader in the issuing device 7'00 of this embodiment may have the same structure and function as the cart reader 800 for pachinko machines.

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. Among these, (top)
For the interface circuit 1 as shown in FIG.
98 is a waveform shaping circuit S that shapes the waveform of the write data signal.
MG2.

5MG4 and magnetic current switching circuits MCCl and MCC2, and the magnetic heads MHDl and MHD2 can read and write magnetic data, so there is no problem. Furthermore, as mentioned in the structural description of the card reader 800 for pachinko machines, the cart reader 800 shown in FIGS. It can be discharged. Therefore, for the issuing bag ff1700 of this embodiment, the same card reader 800 for pachinko machines can be used.

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

This base board 7↓↓ 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 in a direction that intersects with the base substrate 711, and is fixed to a side wall 716 of the 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, there is a take-out motor 7 for driving the conveyance rollers 712 to 714.
19 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, 714a
, 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 is swingably attached to the side wall 716 and has a roller 726 at one end that can come into contact with the outer periphery of the clutch lever 725b. And this clutch lever 727
The other end is connected to a plunger 729a of a clutch solenoid 729 via a spring 728. When the solenoid 729 is energized, the clutch lever 727 is rotated and the roller 726 is connected to the clutch disc 725a.
and the outer periphery of 725b at the same time, transmitting two rotational forces,
When the solenoid 729 is turned off, the rotational force is cut off. Further, a pulley 730 is fixed to the rotating shaft of the clutch disc 725b, and a belt 732 is connected between this pulley 730 and a pulley 731 fixed to one end of the rotating shaft 712a of the second conveying roller 712.
is being wound. Therefore, the rotational force of the take-out motor 719 is transmitted to the 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 inserting a bill, 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 supposed to be done.

As a result, the first conveyance roller 712 is rotated eccentrically,
The card tank 701 above the transport roller 712
Push up the card inside and send it out to the rear. At this time, since the suppressing member 702 is placed on the card CD and applying a constant pressure, the bottom cart is separated from the group of carts in the tank due to the frictional force with the rollers. Moreover,
A stopper 7 is provided at the rear with a distance from the base board 711 for one cart, 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 cart 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 taking out device 710 has an identification code, card number, etc. written on the magnetic recording section by the card reader 800, and an internal punch device 820 punches a hole at the issuing hole punching position. After being opened, the cart is sent to the rear cart reversing device 740. A case 705 is arranged below the cart 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 t188 of the card reader 800 for a pachinko machine, is provided in the card issuing control device 790.The card sent to the cart reversing device 740 is first transferred to a conveyor roller. A belt 742 wound around 741a, 741b, and 741c and five conveyance rollers 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 through 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 traveling motor 706 that drives 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.
09a is fixed, and by turning this knob 709a by hand, it is possible to manually move the card while the travel motor 706 is stopped and remove a card that has caused a paper jam. A running position sensor CPS3 is arranged at the end of the card reversing device [740], and when this sensor detects the rear end of the card, the running motor 706 is stopped.

The card sent out from the cart reversing device 740 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, 752b via the belt 762 and gear group 763, and the press rollers 753a, 753 disposed above the transfer rollers 752a, 752b.
53b and move the cart forward. In front of the transfer rollers 752a and 752b, the transfer roller 7
54 and 755 are arranged along the running path.

Above it is a print head 756 like a thermal head.
is arranged so as to be movable up and down along the guide pin 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 the driven shaft 759, and rotational position sensors 761a and 76↓b 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 stops rotating at a position where the notch of the detection piece 760 faces the sensor 761a or 761b, and the traveling position sensor CPS4 detects the card and operates the lifting motor 758. When the sensor 761a or 761b detects the notch in the detection piece 760, the rotation of the motor is stopped.

As a result, the print head 756 is connected to the traveling 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 making six revolutions, 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 770 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. Furthermore, in this embodiment, only this cart 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 port in FIG. 37, and the card sent from the printing device 750 is guided toward the card issuing port 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 guided to a confiscation tank 780 below by the lane switching member 777. 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 cart issuing port 202. Conveyance roller 774
A confiscation tank 780 is arranged below 774b, and the runway switching member 77, which is located above in the normal state, is disposed below.
Cards guided downward by 7 are confiscated in tank 7.
It is housed within 80.

The rear wall 781 of this confiscated tank 780 has a notch 78 above a.
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 helmets 775 and set so that the detection optical axis is oblique, and detects carts entering the confiscation tank 780. At the same time, when the cart in the tank reaches a certain amount or more, the upper end of the cart blocks the detection optical axis, making it possible to detect that the cart is full. Further, this confiscation tank 780 is placed on a plate 784 diagonally arranged below it so as to be slidable in the front and back direction, and a long hole 784a formed in the plate 784 is formed in the lower surface of the tank 780.
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 detection sensor of the confiscated cart changes from on to off, the running motor 706 is turned off and the ejection or confiscation operation is stopped5. Above the card issuing slot 202, an issuing device 700 is installed.
A card issuance display 787 is provided to show the progress status of card issuance work.

Further, as shown in FIG. 36, the issuing device 700 of this embodiment has left and right rails 79 on a fixed base 791.
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 box, 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 cards confiscated, 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 cart 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 lamps indicated by symbols LMP1 to LMP5 are built-in lamps in the purchase amount selection switch group 212, and when the switch is turned on, The corresponding lamp is lit to illuminate the operation button 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 1790.
0 is a means for accepting money, a means for selecting a desired purchase amount,
It is in charge of controlling the communication means for transmitting valuable data to the management device and receiving a card number in place of the valuable data, the means for dispensing change coins, and the status display means for indicating the issuance processing status, and is responsible for controlling card issuance. The device 790 includes the card ejecting device 710, card reversing device 740, printing device 750, and card ejecting device 770 that constitute the issuing device 700 described above, and the control device 288 of the card reader 800 that is in charge of checking the card and recording magnetic data. Responsible for overall control. And unit control device 2
Communication between 80 and card issue control device 790 is performed by serial communication.

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

The card issuing machine 200 of this embodiment is a unit control device! The f280 instructs the user on the operating procedure by lighting or blinking the status display means consisting of various indicators 221 to 225 etc. provided on the front panel 201 according to the card issuing procedure, and also prevents 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 issuing a cart is completed, the unit control device 280
First, the issuance display 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 LMPI 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, only lamp LMP1 is available.

If it is 3,000 yen, the lamp is LMPI-LMP; if it is 3,500 yen, the lamp is L M P l = L M P5.
Operable switches are clearly displayed.

In this state, when any one of the valid purchase selection switches 2 and 2 is turned on, 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 according to the unit control bag W280.

Table 8 In the figure, ○ is lit, × is off, and Δ is blinking.

D means to display a numerical value according to the input amount, and B means to light up a 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 includes a unit controller 290 that centrally controls the card reader control device 288 and the card issuance control device 790, and a management bag [40
It is composed of a data transmission controller 551 that controls data transmission with 0, and a network controller 553 that performs the establishment of receivables in the network and serial/parallel conversion of data under the control of the data transmission controller. has exactly the same configuration as the unit control device 80 of 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. Of 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 a function for increasing the speed of data transmission (2). , 5MbpS).

This packet memory 552 is composed of four pages each having a capacity of 256 bytes, of which page 0 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 55↓ 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 56 (and a latch circuit 56 for the network controller 553 to store the data reception result in response to a request from the data transmission controller 551). The latch circuit 562 stores a command such as a data transmission command to the network controller 553, the latch circuit 563 stores a low-layer network address, and three circuits are used to display an abnormality in the communication control state within the unit control device 280. Monitor display 55 consisting of an LED lamp
A latch circuit 564 is provided to store display data for 6. A decoder 557 decodes the address given to each of the latch circuits 561 to 564 and generates a selection signal.

On the other hand, the unit controller 280 of the issuing machine differs from the unit controller 180 of the pachinko machine in that the unit controller 290 does not communicate directly with the card reader controller 288, but communicates via the cart issuing controller 790. It is. Therefore, the unit controller 29
A transceiver 571 that performs level conversion of transmitted and received data is connected between the card issuing control device 790 and the card issuing control device 790 .

The unit controller 290 also latches a drive signal that puts input signals from the machine number setter 205 and reset switch 207 onto the data bus 581 at predetermined timing and displays various lamps such as the issuing indicator 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.

As a control signal from the unit controller 290 to the banknote validator 210, the banknotes determined to be genuine banknotes are
O yen, 5000 yen, tOOOP [There is an instruction signal for distinguishing and storing the bills in the safe, and an instruction signal for allowing or disabling the insertion of bills into the bill insertion slot.

In addition, from the banknote validator 210 to the unit controller 29
For the input signal for 0, the inserted banknote is true ↓00000
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 are 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
The input signals for 0 include a signal that is output every time a banknote 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 5.
A signal indicating that the remaining amount of bills in the bill storage section has become 20 or less, a signal indicating that a bill dispensing operation is being executed, and a signal indicating that the bill dispensing operation is completed and one bill from the bill issuing slot is removed. There is a signal to indicate that the

Further, the unit controller 290 includes decoders 586 and 587 and a decoder driver 588 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. 589 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 3 Punch scum: Removal of punch scum In Table 9 above, if an error marked with an asterisk (*) 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, crowd controller 596
, 598, decoders 586, 587, and decoder drivers 588, 889.

Furthermore, in the unit control device 280 of this embodiment, 2 ms of the display data output from the unit controller 290 that drives the amount display 213 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 290
．． Generates a reset signal for 551 and 553.

As described above, the unit control device 280 controls the management device 40
0. It has a window for exchanging information in two directions of the card issuing M control device 290, and performs control for issuing cards under the control of the management device 400, as well as information generated as a result of the issuing process. It has software that periodically sends operating information on the issuing 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 Table 3).

Table 10 In the hot coat shown in Table 10 above, the management device 400 stores the unit memory 550 at system startup.
For example, write a code such as 010101...-01 in the transmission area, and send it periodically to the management device to check for damage to RAM data due to noise such as static electricity, and to detect abnormalities in the transmitted data. It can be detected quickly.

The monitor information shown in Table 10 above 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 of the banknote 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 cart number recorded in the magnetic recording section of the inserted card CD to check the coat. A card settlement device 310 that collects the amount of money, a balance payout device 321, 325 that refunds the amount equivalent to the unused amount that remains unused with respect to the card, and issues a receipt on which the number of balls acquired in the game is printed. printer 330 and various displays 3
03, 304, 341, 342, and a unit control device 35 that controls the entire payment machine 300.

This payment machine 300 has a two-sided panel 301 that can be rotated in the vertical direction, and a card insertion slot 302 at the front end of the top panel 301 corresponding to the cart payment device 310.
Further, on the top surface of the top panel 301, there are provided a ball number display 303 that displays the number of prize balls won (number of balls held) and an amount display 304 that displays the unused amount. Moreover,
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.
In addition, two sets of ball number display 303 and amount display 304 are provided, one of which is tilted forward so that it is easy for the player to read, and the other is tilted backward so that it is easy for the staff inside the counter to read. It has become. 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 set to rO.
A display reset switch 305 is provided to clear the display to J. When a player first inserts a card into the card insertion slot 302, the card reader 800 in the payment machine 300
reads the cart number recorded on the magnetic surface of the card CD, sends it to the management device 400, and receives and receives data regarding the card. 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 discharged into the internal card collection tank 314 after a punch hole (account liquid hole) is formed at a predetermined punching position PH5 by a punching device.

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 payment liquid card and eject it. 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.
Like a card reader for an issuing machine, cards can be ejected to the rear, and a card collection tank 314 is arranged behind the card reader. 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 it on the surface of the blank sheet, and prints the card history, etc. It is discharged from the receipt issuing port 33 opened inside.

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, in settlement, since a fraction of less than 1000 yen is generated as unused money, the coin dispensing device 325 is composed of a coin dispensing port 325 that dispenses coins in units of <100 yen as described above.
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.

Also, inside the front panel 306 that can be opened and closed.

As shown in FIG. 42(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 setting device 352 for distinguishing between each of the plurality of payment machines to enable the management device 400 to know which payment machine has made the payment for a particular cart; and a tank for the coin dispensing device 325 at the time of closing. A coin extraction switch 353 for ejecting the remaining coins, and a print changeover switch 354 for giving an instruction as to whether history data should be printed on the receipt issued by the printer 330 are provided.

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

As shown in FIG. 43, the card payment device 310 includes a card reader 800 and an auxiliary conveyance device 3 disposed behind the card reader 800.
11, a card payment control device 312 that controls the card reader 800 and the auxiliary transport device 311 according to instructions from the unit control device 350, and their power supply bags [1313
and a card collection tank 314 located behind the auxiliary transport device 311.

Note that the card collection tank 314 is connected to the card payment device 3.
It is designed to be removably inserted into a vertically elongated tank storage frame 31-6 fixed to a frame 315 of No. 10.

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 36↓, 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 cells, and the cart discharged from the rear end of the cart leader 800 is sandwiched between a pair of belts 363 and 364 and transported 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 cart sensor 319 is provided to detect when the cart 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 setter 352 is set to "9", and the card inserted for payment is returned to the cart recovery tank after payment. The card is guided and confiscated, and in other cases, after payment is made, the card is put out 411: 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 cart reader (not shown) for reading inserted cards, and a CRT display 910 as a game device that provides games using used cards is placed on the top surface. .

FIG. 45 shows an example of the print format of a receipt printed out on two print sheets 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 changeover 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 (J, NT,
Message MSG is 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 AM1 at the time of card issuance is shown. , history data in the cart file (unused amount of money and number of balls held at each point in time when the card status changed during the game) CRR are printed.

In addition, in the payment machine of the above embodiment, the cart collection mode is set by setting the most significant digit of the machine number setting device 352 to r9J, and in other cases, the cart is ejected forward after payment. By checking the cart status, if the amount spent is rOJ and the purchase price 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 device 312.
However, bill and coin dispensers 321, 325, various displays 303, 304, 341 to 343, and printer 330
The cart payment control device 312 controls the auxiliary conveyance device 311, the counter 317 as a means for displaying the number of collected cards, and the control of the card checking and receiving inputs from various switches 351 to 354, 305. 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 device 350 and the issue 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 a coaxial cable via an optical transceiver 185 in order to send and receive data such as a cart 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. The configuration of this unit control device 35O is almost the same as the unit control device 280 of the issuing machine 200 shown in FIG. Controller 390 and management device 400
It consists of a data transmission controller 551 that controls data transmission with the data transmission controller, and a network controller 553 that performs the establishment of receivables and serial/parallel data conversion in the network under the control of the data transmission controller. It has exactly the same configuration as the unit control device 180 of a pachinko machine. In other words, data is exchanged between each controller 390 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 and 3 are used alternately for receiving data packets. Which page should I use?

Data transmission controller 551 instructs network controller 553. Data transmission controller 55
Even if the next packet data is sent while 1 is processing the received packet data, it will be received by another page, so all the 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 a selector switch 54 is also provided to accommodate the case where the transmission line of the low-level network is connected to the bottom of the gutter with a coaxial cable.
2, it 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.

Furthermore, between the data transmission controller 55↓ and the network controller 553, there is a launch circuit 561 for the network controller 553 to store data reception results in response to a request from the data transmission controller 551, and a launch circuit 561 for storing data reception results in response to a request from the data transmission controller 551. The transmission controller 551 includes a latch circuit 562 for storing a command such as a data transmission command for the network controller 553, and a latch circuit 563 for storing a low-layer network address.
A monitor display 5 consisting of three LED lamps for displaying abnormalities in the communication control state within the unit control device 350
A latch circuit 564 for storing display data to 56 is provided. 557 each of the above latch circuits 561 to 564
This is a decoder that decodes the address given to the decoder and generates a selection signal.

On the other hand, the unit controller 350 of the payment machine differs from the unit control device 180 of the pachinko machine in that the unit controller 390 does not communicate directly with the card reader control device 388, but communicates via the card payment control device 312. That's true. Therefore, the unit controller 39
A transceiver 571 that converts the level of transmitted and received data is connected between the card payment control device 312 and the card payment control device 312 .

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 35 ↓ of the monitor display 343, the coin extraction switch 353, and the print changeover switch 354 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 An input/output controller 576 that latches, input signals from the bill dispenser 32, coin dispenser 325, and printer 330 are transferred onto the data bus 581 at a predetermined timing, and the bill dispenser 321 and the coin dispenser 3
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 every time one banknote 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 the banknotes in the 1 bill storage section. A signal indicating that the remaining amount is less than 20 sheets.

There is a signal for indicating that the bill dispensing operation is being executed, and a signal for indicating that the bill dispensing operation has been completed and the bill from one bill issuing slot has been removed.

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 with a disclosure statement 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 Cart reader inspection (ne) Cart reader error Network error □ Received command error 1 Cart reader sensor F - Remove clogged cart.
585 decodes the address signal output from the unit controller 390 and sends it to the program memory 558, unit memory 550, and input/output controllers 596 and 59.
8 and decoder 586.587, decoder driver 5
This is a decoder that forms 88 and 889 selection signals.

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 mentioned above, the unit control device 1f350 has a management system [
400 has a window for exchanging information in two directions of the card payment control device 312, and performs control for issuing cards under the control of the management device 400, as well as processing payments that occur as a result of payment processing. It has software that periodically sends operating data on the machine 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 as follows.

The data is sent to the management device through data communication between the data transmission controller 551 and the management device 400 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 transmitted data and received data are in the memory.

Topsoil 5 and Table 186, respectively, above unit notes 1 and J.
5 shows a configuration example of a transmission data area SDA and a reception data area RDA in 550. The configuration of the communication area CCA is exactly the same as that of the unit memory of a pachinko machine (see Table 3).

Table 5 As shown in Table 16, in this embodiment, the history data of the card is also received, and by printing this on the receipt along with the time data and discharging it, the player is informed that the payment data is highly reliable. You can make an impression. However, the provenance data can be up to 20 items in the cart file.
This is the data up to the time.

In addition, the monitor information 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 local network bit as shown in Table 17. It consists of a pin point (2 bits for low-rise and high-rise) indicating an abnormality in the transmission cable 500, a bit indicating an error in the payment machine, etc.

Table ↓7 Table 18 In addition, as shown in Table 18, monitor information 2 includes a bit indicating paper out, a bit indicating a printer error, a bit indicating an error in the cart reader, a bit indicating the state inside the card tank, and a bit indicating coin dispensing. It is composed of a bit that indicates the presence of coins in the dispenser, 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.

Next, it centrally controls the pachinko machine 100, cart issuing machine 200, and payment machine 300 configured as described above, collects operating data in real time, monitors the operating status of all terminals, and prevents power outages and breakdowns. Even if an occurrence occurs, it will immediately restore the original data state and restart the operation of each part of the system, and it will also be possible to aggregate the data necessary for the management of the game parlor, as well as reinstate the same qualifications if the card is damaged. The management device 400 that issues carts 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 CP of a minicomputer class.
Main memory unit consisting of U and semiconductor memory (RAM) [M-M
A mask control device 401 in which an EM, a transmission control device SCC, etc. are stored, and a floppy disk storage device 4 as an auxiliary storage device provided above the mask control device 401.
02, a hard disk storage device [403] and a personal computer 410. The personal computer 410 also has a CRT display device 411 for displaying messages and collected data, and a console 412 for an operator to give commands and setting data.
A local processing device 413 that includes a built-in PU and a timer TMR (including a calendar) and is connected to the central processing unit in the master control device 401 via a communication line and an interrupt line;
It also includes a printer 414 for printing collected data and the like.

Serial communication control devices 406a and 406b are provided within master control device 401 to couple local processing device 413 and central processing unit CPU. this house,
The communication control device 406a is used for normal communication, and the communication control device 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 1400 includes a restoration card that has the same qualifications as the damaged card and a test card that can start the pachinko machine in a state that is disconnected from the system, as unique to the pachinko gaming system. The mask control device 401 includes a box 420 that includes an auxiliary printer 408 that prints out emergency information generated in the system in real time, such as the card issuing device 1700 that issues cards and pachinko machine stoppages, etc., and an auxiliary power supply device 409. Card issuing device 7
00 and the auxiliary printer 408 are each connected to the communication control device 4.
It is connected to the central processing bag [CPU] via 06c and 406d. Further, the cart issuing device 700 has exactly the same configuration as the cart issuing device 700 for the issuing machine 200 shown in FIG. 36. 202 is the cart issuing port.

The auxiliary power supply device 409 serves as the main memory when a power outage occurs! M-
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, the pachinko machine 100 is mainly used.
and card issuing machine 200, payment machine 300 and management bag [4
Although a system consisting of the management device 4.00 will be described, 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 4.00. 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 4↓2 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.

Figure (B) shows the top surface of the console, that is, the panel surface.

Figure (A) shows the back side 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 the card is turned on, the card can be used at each terminal until the closing switch 422 is turned on. Also.

423 is a system termination switch for storing the operating data of all terminals in the floppy disk storage device 402 after business hours and instructing the management device to stop control, and 424 is a card for instructing restoration processing of a damaged card. It's a 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
1 to 424 cannot be turned on by operating them.

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 411, and 429 is a CRT clear switch that requests deletion 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 card, operating data of each terminal, etc. by the printer 414. 432
433 is a setting switch for requesting settings such as the number of strokes and the stopping mode of the pachinko machine, and 433 indicates that the set number of prize balls have been paid out and the game has stopped, that is, the game cannot be continued. The cancellation release switch 434 is used to issue a command to cancel the pachinko machine's suspension state, and is used to forcefully terminate terminals of each type at the end of business hours, or to disable normal control or data collection due to abnormalities in the communication network, etc. 435 is a forced termination switch for forcibly shutting down all terminals when the situation occurs, 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 stop switch 436 is pressed.

Furthermore, the console 412 of this embodiment has a test card switch 437 on its back for giving a test card issuance command, the exchange rate for purchase at the time of system introduction, the store court, 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 the terminal machines (pachinko machine, cart 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 trial 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 opening 802a of the control unit 160, a certain number of balls are given to the pachinko machine so that the game operation can be executed 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 700 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 cart 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, the card tank 7.1 can be omitted. Furthermore, since the test card and 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 it P H2 (resurrection hole) of the card.

As mentioned above, the terminal of this example ↓00.200.3
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 and a transmission address is formed for each terminal.

While the system is in operation, operating data of all terminals is collected in real time and stored in the main memory M-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. Then, data from all terminals was collected through regular data collection, and the operating status was monitored.

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

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) PL2, 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 M-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 RCPU.
In addition to the setting file FL5, the system mode, the latest card issuing serial number, a power outage flag, a random number for creating a cart number, etc. are stored here.

Table ■9 Setting value file FL5 in the same table contains system characteristics such as the exchange rate for purchase, store code, number of terminals, number of prize balls, number of balls stopped, 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 configuration. This setting value file is loaded from the hard disk HDD into 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.

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

In the same table, the purchased ball 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;
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 term "stopping mode" refers to the method (arithmetic formula) for calculating the number of balls to be struck; for example, there is a mode in which the game is simply stopped when the number of prize balls to be paid out reaches the number to be batted, or the number of prize balls to be paid out There is a mode in which the game stops when the number of batted balls subtracted from the number of batted balls reaches the number of hits. Although not particularly limited, in this embodiment, the number of stops and the stop mode can be set independently for each group, as shown by =l-Z.

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 the pachinko machine, "2" indicates the card issuing machine, "4" indicates the payment machine, and "O" indicates the terminal. Each indicates the absence of . The NAU status indicates the state of the NAU, and as shown in Table 22, “
If "■" is set, it indicates that the token bus is abnormal, and if "1" is set to bit B□,
Further bit B indicates that the "Opening Code" packet has already been received. is set to “1”, NAU
Indicates that each is normal.

Table 21 Table 22 The unit number and serial number are the numbers and serial numbers of terminals made excluding r4J and r9J, and the unit number is for one NAU (Network 1-Work Adapter Unit) regardless of the type of terminal. The number of each terminal placed below, that is, the number that becomes the address on the lower layer network described later, and the channel number, the number that becomes the address of each terminal seen from the management device, that is, the address on the higher layer network that will be described later. be. However, in the system of the embodiment, the number of pachinko machines connected under one NAU is 64 or less.

As mentioned above, the NAU number and machine number are set using the setting switch (
171, 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 r247J.

Table 23 This is expressed in binary code using the binary coded octal system as rOlo-100.llll.

This code indicates "r167" in decimal notation, and as a result, the pachinko machine machine numbers without "4" and "9" become consecutive serial numbers. On the other hand, in order to keep the address on the low-layer network to 8 bits, the lower 8 bits of the above code
Take the bits, consider this as the code rioio-oi11J expressed in binary coded octal system, and write this as HEX,
When expressed in A, it becomes rA7H. Furthermore, one N
In addition to pachinko machines, terminals such as issuing machines and payment machines are also connected under the AU, and in order to give them 8-bit unit numbers, the number of pachinko machines under one NAU is reduced to 6.
Limited to 4 units, above code rA7HJ and code r3FH
J (equivalent to 64 in decimal) and logical product r
27H” is obtained. Performing logical product with r3FHJ means calculating the remainder after dividing by 64. In this embodiment, this is used as the unit number. Then, rNAU with the NAU number added to the beginning of this unit number.
Number + number unit number channel number. This method enables efficient address processing that matches the characteristics of microcomputers that process data using only binary notation, which is customary in pachinko parlors that have machine numbers that do not use "4" and "9". becomes possible.

The above transmission address file is created by input from the console when the system is installed.

The NAU itself also creates an address file (unit table) for the units under its control based on the input from the unit number setter when the system is started up and stores it in memory, and after a line test, the management device returns to the NAU. A unit table request is made to the unit table and compared with the response data, and if they do not match, the unit table is automatically changed (described later).

The transmission address file can also be changed using a built-in switch 438 on the back of the console.

In addition, consecutive serial numbers starting from "1" are given to each type of NAU, issuing machine, and payment machine as machine numbers.
For the AU and the payment machine, the machine number is used as is as the address (unit number), and for the issuing machine, 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 under the same NAU. Duplication of addresses between the pachinko machine and the payment machine is avoided by not allowing both machines to coexist under the same NAU.

In addition, the 1-issuing machine and the payment machine can be placed under the same NAU (because we decided to use "machine number 10-28" as the address of the issuing machine).

Furthermore, the address of NAtJ530 on the high-level network uses the NAtJ number set by the setting device 544, and the address of N'AU on the low-level network is r.
A fixed address of 255J is used. Further, the address of the management device is set to "0".

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

The card file FLI contains information for each card.

Table 4 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 current number of the card specified by the issuing serial number n and the card number. This information indicates the status, and is hereinafter referred to as cart text in this embodiment. 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 already in the suspended state. A bit indicating that the card was used for payment at the payment machine.
A bit that indicates that both the number of balls and balance of the card have become zero, a bit that indicates that the card has been stopped more than once (in the past), and a bit that indicates that the card was used in a pachinko machine that has been forcibly terminated. , a bit indicating that the card is a revived card, etc.

Table 5 On the other hand, returning to Table 24, in the card file FLL, the location terminal serial number indicating the location of the terminal where the card currently exists and the location terminal number are registered. As is customary in pachinko machine parlors, the numbers "4" and r9J 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 1
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 cart 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, so that the value of the l counter is changed to the actual game. It matches the number of units.

Here, the cart status and actions and the registration of card information in the card file 8FL↓ will be explained using FIG. 52.

First, when a card is issued by the cart issuing machine 200, the cart is ejected and the cart shifts from an unissued (blank) state SSO to a free state SS1. Then, when the card is inserted into the desired pachinko machine 1°O, the game state shifts to 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 SS4
By re-inserting the same cart, the game state returns to SS.
Return to 2. Then, when the end switch 114 is pressed to end the game during the game, the cards are ejected and the game shifts to the free state SSI.

Even if the CPU terminates the game forcibly or the game stops, the card is ejected and the game state moves from the game state SS2 to the free state SSI. When the card in the free state is brought to the payment machine 300 and payment processing is performed, an invalid mark is attached to the card, the card is collected, and the process moves to the payment completed state SS5. In the system of this embodiment, it is also possible to go directly to the payment machine 300 without returning to the pachinko machine with the cart with the suspension state GSS4 and perform payment processing, and in that case, the state shifts from the suspension state SS4 to the payment completed state SS5. .

In the above state transition diagram, the arrows indicating the transition direction with 0 attached are actions that involve recording card information in the cart file FL3. In addition, in each block, the code indicated by XXH represents the corresponding state in hexadecimal digits using the code indicating the card state in Table 25 (1).
HEXA expression).

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 by the management device 400 once every ↓ seconds 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.

Table 26 Total Capacity 64 x 506 = 32384 = Approximately 32 Bytes The data marked with a circle in Table 26 means data that will be saved on the floppy disk as a daily report file when the system is terminated.

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

Next, Table 27 and Table 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.

Table 27 Total damage 6) x50 = 3200 = 3.2 bytes Total damage 64
, In Table 27, data marked with a circle in the save column is data that is saved on the floppy disk FDD at the end of business hours.

Furthermore, regarding the monitor information in the issuing machine file, 2 is shown in Table Y2 and Table ↓3, 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.
00000 0000 0001 indicates that it is in operation.

Next, the card issuing machine 100, the pachinko machine 200, the payment machine 300 as terminals configured as described above, and the management device 400 that performs centralized control of these terminals are organically combined to perform data transmission and card processing. The data transmission path (local area network) that enables this operation will be explained.

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. ) 53o.

The plurality of NAUs 530 that control each low-layer network (token bus) 510 control the CSMA/CD (
Carrier 5ence Multiple
Access with Co11ision
The management device 400 is connected to the management device 400 via a high-rise network 520 using the Detect method.

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 networks and a data logical collection and distribution function. in this way,
The reason for the hierarchical configuration of the data transmission path 5o○ is that if more than 500 terminals are connected to one management device and you want to collect regular data from each terminal every second, the host computer will need to connect all the terminal units. A system that communicates directly would place too much burden on the host computer.

Although the transmission speed of Chiba Nenodo is as fast as 10 Mbps, the controller LSI is expensive, so the cost is too high 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, both the transmission line constituting the high-rise network 5↓O and the transmission line constituting the low-level network 520 are configured so that either a coaxial cable or an optical fiber cable can be used.

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

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. ing.

In addition, the low-layer network consists of one issuing machine and 22 pachinko machines.
Form of machine■, form of 10 issuing machines and 1!15 machines for payment■
There is. In this way, each low-layer network has at least one issuing device, so in this embodiment, the NAU 530 is installed in the issuing device 200 in the form (3). The reason for providing 10 issuing machines and 5 payment machines is to enable issuing machines or payment machines to be arranged in rows in a concentrated manner.

Figure 53 (B) shows an example of a network configuration when using a coaxial cable as a transmission path, and 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 NAU5
30 are connected to the high-rise network cable 515 in parallel form by the T-shaped connector 505, and each unit (terminal) H, P, P2゜--...P22 is connected in parallel by the T-shaped connector 505. and is connected to the low-layer network cable 525.

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
□, P□, P2. ...For P2□.

Optical transceivers 508 for performing token bus type data communication in the low-layer network are provided, and are connected by a two-core optical fiber cable 522. 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 NAU
530 or unit H,, Pl, P,...P
2□ is connected by a coaxial cable. The above-mentioned high-rise network 510 and low-level network 520
Although data transmission and reception both use a packet switching method, 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, bucket type i (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. for” A CK
"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 It has an address field indicating the source and destination, a field indicating the length of 5 data, a data field, and a field containing an error correction code.In addition, on this low layer network 520, the data is RZ (
It is transmitted using a return-to-zero (return-to-zero) system 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 510 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 into serial/parallel data;
A high-rise network controller 537 that establishes transmission/reception credits and performs serial/parallel conversion of data in an A/CD high-rise network, and a data transmission controller 535 that controls data transfer between these network controllers 533 and 537. There is. Among the above controllers, the low-layer network controller 533 is composed of a communication LSI dedicated to token passing, and the high-level network controller 537 and data transmission controller 535 are composed of general-purpose microcomputers. A buffer packet memory 534 and a data memory are provided between these controllers 533 and 535 and between 535 and 537 to absorb the difference in data transmission speed between the low layer network 5]-〇 and the high layer network 520. 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. data memory 536
In addition to the transmission/reception data area, it 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. The regular data area contains data in the transmission data areas of all units (see Tables ↓, ↓0 and Table 15), and the unit table area has the same configuration as the transmission address file of the management device. In addition, the low layer network controller 5
33 is connected to a transceiver 508 that performs 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 circuit 541 separates and combines the transmit signal and the receive signal via a 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. It is possible to connect to the 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
NAU number setter 544 sets a number to distinguish AUs from each other, and sets the minimum number of pachinko machines or payment machines among the terminals existing on the low layer network S↓0 under the control of each NAU 530. A minimum machine 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 a setting device 547 for setting the minimum machine number and the number of connected machines for issuing machines. , 548, 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 built into the NAU unit main body 539 shown in FIG. 54(B).

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 1.86 and high-rise and low-rise network coaxial cable compatible connectors 187, respectively. Furthermore, the various setting devices 54 are provided on the upper surface of the unit main body 539.
5 to 549 are provided. NAU number setter 544
is provided on the board inside the case.

Note that 50↓ 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 is used to collect operating data from terminals P, H, and S at a rate exceeding 1 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 operational 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 the management device W in the above data transmission system.
40o, NAU530 questions, and management device 400, pachinko machine 100, and card issuing machine 200 through NAU530.
, unit controllers 190, 290 of the payment machine 300
, 390 are shown.

In the same table, Units 1- refers to each terminal (pachinko machine,
This refers to the control unit for card issuing machines and payment machines.

Also, the “unit table request I+” packet is a packet used by the management device to confirm the connection and address of the units connected to each NAU at system startup. Connection is confirmed.The address information in the packet is compared with the value in the unit table file, and if there is a mismatch, the data in the packet is changed.For units for which connection cannot be confirmed, the following initial values are Confirmation is taken again by the configuration packet.

Furthermore, the "Card In" - Pachinko Interruption End packet depicted in Table 31 is a packet specific to the Pachinko machine 100, and among these, the "Card In" packet is a packet that is used to send a card to the control unit 60 of the Pachinko machine. This is a packet for requesting information (card text) regarding the cart from the unit side to the management device 400 when the cart is inserted.

Here, the card text is text containing four pieces of information: cart number, number of balls held, amount (unused amount), and cart status. Also, the packet "Return to Zero" is used to send cart 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 while playing a game at the pachinko machine. This is a packet of

On the other hand, the "suspension end" 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 where the game 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 1'Card Purchase'' packet depicted in Table 31 is a packet specific to the card issuing machine 200, and is generated when a bill is inserted into the bill insertion slot 2↓1 of the issuing machine and the purchase selection switch 212 is turned on. This is a packet for the unit control device 280 to request 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 the card amount field set to "0". When this happens, the management device 400 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 banknote is inserted, the card issuing machine sends a "card purchase" packet to the management device in which the actual purchase amount is entered in the card amount column. Then, the management device looks at the cart number column, determines that the cart has been reserved for issue, searches the cart file, writes data such as the purchase amount and issue time in the data area of the cart, and then sends an ACK packet. It is to be returned to the issuing machine.

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

In addition, the "Cart payment completed" packet is a packet to notify the management device 400 that the card payment has been completed. When the management device receives this packet, the management device changes the cart status of the cart in the card file to "Payment""Completed" and write the data at the time of payment in the 1=20 column of history data.The management device 400 sends an "ACK" packet to the payment machine 300 in response to this "Pakart payment completed" packet, and the card payment is completed. Once the process is complete, the first cart 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 by receiving the packet, and the NAU and units are restored by transmitting the operation data of all units under the control of the NAU using the "Parunit recovery data" packet.In addition, the "Unit monitor check" packet is sent at regular intervals. If a unit is determined to be abnormal based on the data, this is a packet to confirm that the unit has recovered.It is sent periodically until the unit recovers, and recovery is confirmed by receiving an ACK packet from the NAU.This packet is sent periodically until the unit recovers. The received NAU executes a connection check with the network controller of the corresponding unit, and when the connection is confirmed, sends an ACK packet to the management device.

Furthermore, in Table 31, “ACK” and “JINAK”
The packets are sent to the management device W400, the network adapter unit 530, and each terminal 100, 200, 30.
0, and is 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. Of these, "A"
CK", 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.

In FIG. 55(A), a management device is connected via a high-level network 520! 1400 and the 'NAU 530, and FIG. Furthermore, FIG. 55C shows the basic configuration of packets transmitted and received between the NAU 530 and each unit via the low layer network 510.

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, 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 approach, the management device only needs to communicate with 25 NAUs, and the NAUs only need to communicate with 25 NAUs.
Since it is only necessary to communicate with three 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-layer packet head HHD is removed and the packet is sent onto the low-layer network 510, and the packet sent and received from each unit to the management device 400 using only the low-layer packet head LHD is sent to the management device 400 by the NAU 530.
A high-rise packet head HHD is added to the head of D and the fifth
5 High-rise network 5 as a packet in the format shown in Figure (B)
20 is sent out on top.

Note that Table 32 describes the definitions of the unique data laid out in the head portion of each of the above packets.

56 to 61 show the above-mentioned high-rise network 1-51.
2 shows an example of a typical format of a packet transmitted and received between the management device 400 and the NAU 530 on the NAU 530.

In the "line test" packet shown in FIG. 56(A).

Date code and identification code (store code) in the sending data field
Then, send the number of pachinko machines, issuing machines, and payment machines belonging to the destination NAU 530 and the minimum machine number of each machine. Then, the NAU 530 stores the year/month code and identification code, compares it with the number calculated based on the settings of the machine number setting switch 562, etc., and sends it to the management device 400.
In response, an "ACK" packet as shown in FIG. 56(B) is returned. Note that when the NAU 530 receives a "line test" packet from the management device, it sends the unit number setter and number setter 544 to 5 for all units under its control.
Using the transmission address that I had calculated in advance based on the setting value of 48, I sent out a "PLAN TEST" packet with only the low-layer network packet head LHD attached, and sent it 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 based on the received data, a unit table as a transmission address file is created and stored.

FIG. 57(A) shows the structure of the "unit table request" packet sent from the management device 400 to the NAU 530, and FIG. 57(B) shows the structure of the "ACK" packet that is the response. NAU530 requests unit table''
When a packet is received, it returns an "ACK" packet containing the NAU number, NAU status, and data about all units in the unit table.

FIGS. 58(A) and 58(B) show the structure of the "initial value setting" packet for the pachinko machine 100 from the management device 400 and the "ACK" packet as its response on the high-rise network. In the column of this packet, initial values such as the purchase ball rate and the number of prize balls required for operation of the pachinko machine are entered and transmitted.

FIG. 58(A) is an "initial value setting" packet for the pachinko machine, and in the "initial value setting" packet (not shown) for the issuing machine 200 or the payment machine 300, the date code is written in the data column. and an identification code and hot code.

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 column 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 10) or the transmission data of all the payment machines. Area (see table 15)
Enter all the data inside and send.

FIG. 60 shows an example of the configuration of various command packets without data and their response packets sent from the management device 400 to the payment machine 3°O.

Packet type 1iPAcKET$TYPE in the same figure has codes 90H (opening code) and 91H (closing code).
, 95H (forced termination request), 96H (forced termination cancellation),
Either 8CH (line monitor check) or BIH (restart) code is entered. Furthermore, among the above-mentioned "forced termination request", 6 "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 a "card-in" packet, its acknowledgment packet "A CK", and its negative response packet 'NA' which are sent to the management device when a card is inserted into a pachinko machine. This figure shows the format of packets on the high-rise network 5 of ``K''.

In the data field of the "Card-in" transmission packet, the cart 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 card 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"
The structure of the transmitted/received packet when r-stop J occurs is also 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 "Number of balls", "Amount", and "Card status" fields of the card text are rOJ, whereas in other packets of the same type, these fields also have information about the card. It is designed to enter the data to be sent.

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

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

Among these, the "regular data transmission" packet contains the unit memory transmission of the relevant pachinko machine and the data of the person in the data area, and the management device receives this data and stores the relevant data in the P machine file. Update the pachinko machine 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 real 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 ite card issuing machine 200 and the NAU 530 on the low layer network 520.

Of these, FIGS. 64(A) to (C) show a "card purchase" packet requesting the management device to reserve a card, its response packet "A CK", and a negative response "N".
An example of the configuration of AK'' is shown below.

In the data column of the "Card Purchase" packet when making a reservation for card issuance, enter only the issuance acceptance number m, which indicates the number of the issued card in the relevant issuing machine, and the cart amount, cart number, and issuance serial number. Send as "0".

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 Jm 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.

Further, FIG. 65 shows an example of the structure of a "periodic data transmission" packet, and FIGS. 66(A) and (B) show an example of the structure 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 cart 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, the "unit recovery data" packet contains all the data in the issuing machine file of the management device and the date, identification code, and real code read from the setting value file.
It is sent in accordance with the configuration of the data area of the unit memory 550. However, for the receive data packet head and card text that overlap with the transmit data area of the unit memory, duplicate transmissions are omitted, and the unit controller 2
The data is copied from the transmission data area to the reception data area on the 90 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 7o 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 (C) show a "Card Settlement" packet requesting the management device to settle the card, and its response bucket i~ "A CK" and "NAK".
” is shown below.

At the time of card payment, only the card number read by the card reader of the payment machine is sent in the data field of the "card payment" packet. On the other hand, in the data column of the response "ACK" packet, data of the card read out by searching the card file using the issuing serial number n calculated backward from the card number in the management device 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 balls printed, if the unused money is refunded, the management device i! FIG. 68 shows the structure of "Card payment completed" sent to 400 and its response packet. 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 a packet is also shown in FIG. 70(A).

(B) shows an example of the structure of a transmission/reception packet of "par unit recovery data" regarding the payment machine.

Among these, the "periodic data transmission" packet contains all the data in the transmission data area of the unit memory of the payment machine, and the management device receives this data and stores it in the payment machine file. Update data. 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 contains all the data in the payment machine file of the management device [400], the date, identification code, and hot code read from the setting value file, and the configuration of the data area of the unit memory 550. It will be sent according to the .

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, the NA U 530 is located between the two networks 510 and 520 and mediates data transmission.
The control procedure of the data transmission controller 535 and the procedure of low-layer network abnormality detection processing using a timer interrupt will be explained using FIG. 71 and FIG. 72.

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 setting device 544, Pachinko machine or payment machine minimum 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 (step 5L-56). Then, based on the machine number and number read in step 31, 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).
), the machine number calculated in step S7 above in the monitor table (regular data storage type #c) in the data memory 536,
Write the serial number and channel number, as well as the NA
The type of each unit (pachinko machine, issuing machine) is determined and written from the setting value of the U type setting device, and other operating data is cleared to "o" (step S9).

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

Next, the data transmission controller 535 waits for a packet to be sent from the master control device 401 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". It is determined whether or not (step SL2.513).

And the received packet is ``unit table request''
If it is determined that this is the case, the process moves from step S13 to step S814, and an "ACK" packet containing the unit table data read from the data memory 536 is sent to the management device, and then a one-second timer for timer interrupt is activated. After setting and starting the timer interrupt, step 311
and waits 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 521, where the "A CK" 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, when the timer is checked and an "ACK" packet is returned from each unit within a predetermined period of time, the token bus error bit B6 of the monitor information module for the corresponding unit in the monitor table is cleared to rOJ (steps 825 to 825). 527). Also, within a predetermined time, “ACK”
”If the packet is not returned, the above monitor information 1
The token bus abnormality bit B6 of is set to rlJ (step 828). Then, by subtracting (-1) the counter set in step S22 above and determining whether it has reached rOJ, it is determined whether transmission of the "Pal line test" packet has been completed for all units, and uncompleted If so, return to step S23 and move the bucket to the next unit.
- is sent, and when the process is completed for all units, the process returns to step Sll and waits for reception of a "unit table request" bucket.

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

Note that the processing of N A and U corresponding to each received packet is a simple mediation process for data transmission between the management device and the unit (removal or addition of a packet head), or sending a command packet to each unit on behalf of the management device. These are auxiliary processes, and will become clearer in the following explanation of the overall flow of the system, so their explanation will be omitted here.

On the other hand, when an interrupt signal is received every second from the interrupt timer set in step S15, 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 in the column of the unit in the regular data storage area of the data memory 536 is set to "1" in step S33.
After setting it to J, the process moves to step S33. and,
Subtract the counter set in step S3↓ and
'', it is determined whether the check for all units has been completed. 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 3↓ 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 or not there is a power outage file, 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 11) 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 52504)
. Then, 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, a "line test" packet is sent 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 date and identification code (store number) are added to the packet header along with the packet header and transmitted.

On the other hand, when the power is turned on, NAU530 first
The setting values (NAU number, minimum unit number, number of terminals, etc.) are read from the AU number setters 544 to 549, the network transmission address of each terminal is calculated, a unit table is created, and each unit (terminal) and the NAU itself are In addition to recognizing the transmission address, the monitor table containing the operation data of each unit is cleared (step 535).
01-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 NATIJ based on the setting value read from the setting device should match the NAU address loaded by the management device 400 from the data of the setting value file F L 1 in step 52503. Mutual communication becomes possible because each party recognizes the same address.

In addition, when the management device 400 receives an "ACK" packet from the NAU 530, it can be recognized that there is no line abnormality with the corresponding NAU, and the above procedure (steps 52505 to S2506) can be performed based on the number of NAUs. By repeating this, the check for all lines is completed,
Thereafter, the process moves to unit table request processing (FIG. 74).

On the other hand, the unit control device 1i180, 280 of each terminal
．． 350, when the power is turned on, the data transmission controller 55 in the unit first transfers data to the unit memory 55.
After clearing all data areas of 0, 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. Unit controller 190, 290, 390 of each terminal
After turning on the power, the unit initializes the internal memory, registers, and I10 board, and when it detects the rising edge of the initialization signal INT from the unit memory, it reads out the set value (machine number) from the machine number setter and sets the serial number and the lower order of the channel number. is calculated and then written into the transmission data area of the unit memory (steps 55501 to 5550).
4). When the data transmission controller 551 reads it, the unit address is recognized 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 "Pal line test" packet to each unit (terminal) to which data (date and identification code) already received from the management device 400 is added, and the data transmission controller 551 on the unit side receives it. When received, the received date and identification code are written in the unit memory, and then an "ACK" packet is sent to the NAU 530 (steps 54504, 54505).The unit controller writes the date and identification code through the unit memory.
When the identification code is received, the process waits for receiving the initial value (steps 55505 and 55506). In addition, when the NAU receives "ACK" from the data transmission controller 551, it transmits "line test" to the next unit, and by repeating this for all units, the low layer network 510
The line test is completed, and a unit table 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 device 400 starts unit table request processing and requests the central processing unit CP.
U makes “unit table request” to each NAU530
Send the packet (step 52511). Then,
NAU 530 receives the packet and sends PACKET
Next to the head section with "ACK" (=08H) in $TYPE11, the NAU number, NAU status (consisting of bits indicating token bus error, opening code received, NAU normal, etc.), and the unit table data mentioned above. (Unit number, type flag, unit number, serial number, channel number and monitor information 1 for each unit)
An "ACK" packet with the same number of units added as the "ACK" packet is transmitted (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 FL2, 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 result to the local processing device, and waits for a command (steps S25E2 to S52514).

When the local processing unit 413 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 will be displayed on the screen of the CRT display LJN7t4LL, wait for the store opening switch on the console to be turned on, and then issue the initial value setting command when a store opening request is received. Send to central processing unit (steps 51511--S
L 513).

When the initial value setting command is received, the central processing unit CPU
reads the initial value of each unit from the setting value file FLL in the main memory @M-MEM and stores the initial value in the data section (for pachinko machines, the date, identification code, purchased ball exchange rate,
An ``initial value setting'' packet containing initial values such as the number of main prize balls, the number of sub-prize balls, the number of batted balls, the number of batted balls, and a hot code) is transmitted (steps 32515, 52516).

Then, NA, U330 receives the packet and
Remove the high-level network head unit and send an "initial value setting" packet to each unit via the low-level network, and when a heart ACK (response signal) is received from the network controller of each unit, send an ``ACK'' to the management device. ”Send packet (step 535)
13-53515). When the central processing unit CPU confirms that "ACK" has been received from all units, it transmits an initial value transmission completion message to the local processing unit 413 and waits for a store opening request command to be sent (step 52517).
, 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 specified 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 (170°270.370) and receives the packet. Write the received initial value to the 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 I-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), the initial value request from the card reader is If there is, a function containing the initial value is returned (step S55↓1
~55514). On the other hand, the data transmission controller 5 indicates that the initial value unset bit on the monitor information has been set to "0".
51 sets a regular timer and starts transmitting regular 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 each piece of earth and sand using an interrupt from its own timer, the transmission controller 551 in the unit memory 170° 270. The operating data written in 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 S3523). This is to prevent data from being rewritten during regular data transmission to the management device 400. Note that the regular data collected by the NAU 530 is stored in the unit memories 170, 27 one after another by the unit controllers 190, 290, 390 of each terminal sucking up the operation data of the terminal in real time.
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 53528).

On the other hand, on the side of the management device 400, the central processing unit CPU checks the scheduled time every second by an interrupt from its own timer, starts the scheduled data request process, and processes each N A
Sends a "Paper Scheduled Data Request" packet to U 530 (32521, 52522).Specified NAU5
When 30 receives the packet, it sets the write flag and then sends an “ACK” with the monitor table data.
”Send packet and reset write flag (
Steps 53524-S3527). When the management device 400 receives this, it checks the monitor information and if there is an abnormal terminal, it notifies the local processing device and displays the CRT.
After the unit abnormality is displayed on the screen of the display device, the operation data in each unit file is rewritten with regular data (steps 52523 to 52525).

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. The central processing unit then forms an “opening code” packet and sends it to each NAU 530 (step 51531,
52531). When the N A U 530 receives and 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 the "opening code" to each unit via the lower layer network. ″Send packet (step 5353
1-S 3533).

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 S2532). Then, the local processing device performs a normal display on the screen of the CRT display device 411, which displays a message that the business is open, and the names and operating methods of switches on the console that can be operated (step 51532).

On the other hand, "Opening coat" sent from NAU 530
The packet is sent to the data transmission controller 551 of each terminal.
When the receiver is removed, each unit control device 180.280,3
A store opening code "1" is written in the command register CR2 of the unit memory 170, 270, and 370 in the unit controller 190, 290, and 390.
By reading, the card reader control device 188, 28
8,388, permits card acceptance and issuance, sets the banknote validator 210 of the card issuing machine to a state where banknote reception is possible, and displays 64.221 on the display outside each terminal.
, 341 to inform the player that the terminal is in operation (step 54).
531~54533° Step 55531~S 553
3).

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

The unit controller 290 of the card issuing machine 200 is
Once the initialization process is complete, the issuance reservation process starts even before the purchased banknote is actually inserted into the issuing machine, and the amount is first
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. Form a “Card Purchase” packet (20) 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 unit CPU checks whether the card number in the packet is rOJ or not, then reads the number of issuances from the file of the issuing machine that sent the packet, compares it with the issuance acceptance number, and confirms the purchase for reservation. If it is determined that it is a packet,
Calculates the issuing serial number and card number, creates a card file, and sends an "ACK" packet containing the card number to NAU (steps 52541 to 5254)
4). The issue serial number is the sum of the number of issues issued by all issuing machines.

The NAU that received "ACK" removes the high-level packet head from the packet and transmits it to the unit controller 280 of the issuer (step 53542). The data transmission controller 55 in the Unisito control device is the
When receiving CK ''', the unit controller 290 is notified of this via the unit memory (step 54542).Then, the unit controller sends a "card issue" function containing the card number to the cart issuing device 700. In response to this, the card issuing device takes out one card from the card tank, supplies it to the cart 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 213. Then, when one of the purchase selection switches 212 is turned on and the purchase amount is specified, the unit controller 290 confirms the amount and sends a "card purchase" command to the command register CRI in the unit memory 550.
The purchase amount of the card is written in the transmission data area (step 55543).

Next, the data transmission controller 551 reads this and forms a "cart 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 it is an actual card purchase, the amount is stored in the card file searched using the issued serial number. , and then sends an 'ACK I+ packet (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 20.
0 data transmission controller 55 (steps 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 700
An issue function containing the purchase amount is sent to (step 55544). Then, the purchase amount is printed on the waiting card and the card is ejected. Also, if there is change at this time, the unit controller 290 sends the remaining money dispenser 230
At the same time as giving a change payout command, the lamps L1 to L5 in the purchase selection switch are turned off, and the amount display 21.3 is turned off.
clears the display of rOJ, and also updates monetary data such as deposit amount in the transmission data area (step 55
545, 55546).

As mentioned above, when issuing a card, a reservation is made in advance for the card to be issued, the card number is recorded and the card is placed on standby, and when the actual bill is inserted, only the purchase amount is printed and ejected, so from the time the bill is inserted to the cart is issued. The waiting time can be significantly reduced.

FIG. 78 shows the procedure from when the card CD is inserted into the pachinko machine ↓00 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 punch hole and the magnetic surface of the card, and releases the payment liquid or return zero. Cards are excluded, and for other cards, the date and identification code (
If the date or code does not match, the card is ejected as is, and if they match, the card number is transferred to the unit controller 190.

Then, the unit controller 190 receives the card number and stores it in the command register C in the unit memory 550.
Writes a command indicating that the card has been inserted into the RI and the card number in the transmission data area, and requests the transmission of a "card-in" packet (step 55551).
). The data transmission controller 551 has a "card-in" code in the head section and sends a packet with a cart number in the data section to the NAU 530 via the low layer network.
and when NAU 530 receives it.

Management device 4- with a head for high-rise network attached to its head
Send to 00 (step 54551..53551)
.

Management device 400 h'XN A U 530 Color power'
When the number f "3-" is received, the issuing serial number n is calculated from the cart number, and data of the corresponding cart is read from the cart file FL3 in the main storage device M-MEM (steps S2551. to S52553). , If the card number in the file and the received cart number are checked and the card numbers do not match, or if the card status in the cart file is checked and it is determined that it is not appropriate to start playing (checkout (in the case of a completed cart, etc.), a 'NAK' packet, which is a response rejection signal, is transmitted (steps 52554 to 52556). Then, N
The AU 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 55 of the designated unit receives "NAK" and stores it in the unit memory 550.
A command indicating that the response has been rejected is written to command register CR2 in Steps 53552 and 545.
52). The unit controller 190 reads this, confirms the response rejection, and ejects the card from the card reader 800 (step S5552).

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 24, Table 26) is updated.

In other words, update the card status from ``free status'' to ``playing''. number of balls, etc.) and transmits an 'ACK' packet as a response signal (steps 52557, 52558).

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

Then, 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 1 of the pachinko machine 100 during the game.
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 an "interrupt switch" packet, puts the card text in the data part, and sends it to the NAU 530 (step 54561). When the NAU 530 receives the packet, it attaches a head for the high-rise network to its head and sends it to the management device 400 (step 53561).

When the management device 400 receives it, it calculates the issuing serial number n from the card number in the card text, reads the cart file FL1 in the main storage device M-MEM, and calculates the location machine number in the file and the machine number in the packet. collate and
If the machine numbers do not match, or if the card status in the file is not in progress or interrupted, a NAK is transmitted (steps 52561 to 52566). On the other hand, if the numbers match and the card status is in play, the data of the corresponding cart is updated, and then an "ACK" packet is sent as a response signal with the cart text attached (step 52).
567.52568). NAU530 “N.A.K.
” or “ACK”, the high layer network head is removed and sent onto the low layer network 510 (steps 53562 and 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 is received and N A, K or ACK is written to command register CR2 in unit memory 550.
and when it is ACK, further write the card text in the reception data area (steps 54562, 54563
). When the unit controller 190 confirms the reception of the NAK, it returns the card status to the original "Playing J" and restarts the game control (step S5562). When the unit controller 190 confirms the reception of the ACK, the card is ejected from the cart reader 800. After that, the operation information in the transmission data area SDA of the unit memory is changed to "suspended", the lamp 121 built in the purchase switch 113 provided in the pachinko machine 100 is turned off, and the game status display lamp 123, etc. Change the status to suspended display (flashing) (step 555)
63,55564).

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 cart-in shown in FIG. That is, the processing steps 55571-32571 that notify that the card has been inserted from the pachinko machine to the management device 400 correspond to the processing steps 55551-52551 in FIG.
573 indicates processing steps 52552 to 555 in FIG.
53, and processing steps 52572 to 55572 for transmitting "NAK" as a negative response correspond to processing steps 52552 to 55552 in FIG. 78, 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).

The upper diagram of FIG. 8 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", and also sends a command to the command register CR1 in the unit memory 550 indicating that the end switch has been turned on. Write (step 55581). Then,
The data transmission controller 551 reads this, inserts the card text, forms an "end switch" packet, and sends it to the NAU 530 via the lower layer network 510 (step S4581). , attaching a head for the high-rise network to the management device 400 (step 835).
81), and then press the interrupt switch 1 of the pachinko machine 100.
Processing procedure when 15 is turned on (Fig. 79 Step 5
2561-52568)), "ACK" is returned to the unit control device 180 (steps 52581 to S2588), and the card reader 800
The card is ejected from the machine (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 111 and the amount display 112 are cleared to rOJ, and the lamp 121 indicating purchase 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 CRI (step 55591). Then, the data transmission controller 551 forms a "return to zero" packet, includes the card text in the transmission data area of the unit memory, and transmits it to the NAU 530 (step 54591).
When the U 530 receives this "return to zero" packet, it adds a high-level packet head and sends it to the management device 400 (step 5359L). When the management device receives a "return to zero" packet, it calculates the issuing serial number from the card number in the packet and uses the issuing serial number to store the main memory bag fiM.
Read the file of the card from the file in MEM, check the card status and location terminal number, and if the cart status is other than "playing" or the machine number does not match, NA
Send K (steps 52591-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 cart history data. Send ACK (step 5259
6-S25'98).

Upon receiving the ACK, the NAU 530 removes the high-layer packet head and sends it to the designated unit (step s
a 593). Unit data transmission controller 55
1 receives the 'ACK' packet, it writes the ACK reception command to the command register CR2 of the unit memory 550 and the card text to the reception data area (step 54593).Then, the unit controller 190 confirms the ACK reception and writes the ACK reception command to the command register CR2 of the unit memory 550 and the card text to the reception data area. 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 163 is changed to a display indicating "free" (steps 55593, 55594).

FIG. 83 shows that during the game, the unit controller 90
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.

That is, processing steps 35601 to 82601 for notifying the management device 400 that a processing factor (termination) has occurred on the pachinko machine 100 side correspond to processing steps 55591 to 52591 in FIG. Processing steps 52602 to 82609 for updating the file and transmitting the response "ACK" correspond to processing steps 52592 to 52598 in FIG. 82. The difference is that the unit controller ↓9 indicates that a stop has occurred.
If it is determined to be 0, a "stop" command is entered in the unit memory 550 and the card status is changed to "stop" (step 85601), and a "stop" packet is used for transmission (step 84601). Then, after confirming the ACK, change the operation information in the transmission data area SDA of the unit memory to "Cancelled" instead of "Free", turn off the purchase ready lamp 121-, and clear the display of the number of cancellations and the amount to zero. At the same time, the status display lamp 123 and the analog display 163 are displayed as a stop indication (flashing).

In addition, the card reader 800 disables the acceptance of the next card after ejecting the card, and the management device updates the card file and changes the operation information in the pachinko machine file to "Stop J" (step 52606), C
The RT display device 411 displays the interrupt message of the stop table, and the printer 408 prints the stop information (step 32608). 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 cart payment processing in the payment machine 300. When a cart CD is inserted into the cart reader 800 of the payment machine 300, it reads the information recorded on the magnetic surface of the cart, checks the date and identification code, and if they match, sends the card number to the unit controller 390. Forward. The unit controller 390 writes “Cart checkout J” in the command register CRI in the unit memory 550.
55611), the data transmission controller 551 reads it, forms a Packard payment request packet, and transmits the card number to the lower layer network 510. (Step 54611)
. Then, the NAU 530 receives it, attaches the high-level network head to the head of the packet, and sends it to the management bag [400] (step 53611). When the management device 400 receives the packet, it calculates the issued serial number (n) from the card number and, based on that, stores the card file FLI.
, read the corresponding card text (card information), and check the card status (step 52611
~52614). 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 "NA" indicating the refusal of payment will be displayed.
K” packet is formed and transmitted (step 82615)
). Then, the NAU 530 receives it, removes the high-level network head, and transmits it to the unit controller 350 of the requesting payment machine 300 (step 83612).

Then, the data transmission controller 551 receives the command register CR2 in the unit memory 550.
, the unit controller 390 reads and confirms it, and ejects the card from the card reader 800 (steps 54612 and 55612).
).

On the other hand, if the management device 400 determines in the above processing step 82614 that the card status is appropriate,
Forms an "ACK" packet as a response signal, and sends it with payment data (number of balls held and unused amount) read from the card file, card history, payment acceptance time, etc., and NAU 530 transmits the packet from the packet to the high-rise network. The head is removed and transmitted to the unit controller 350 (steps 52616 and 53613). Then,
The data transmission controller 551 receives it and writes ACK to the command register CR2 in the unit memory 550, and writes the received data such as payment data to the reception data area RDA (step 54613), and the unit controller 390 reads it and confirms it. After confirming that there is a response, the number of balls (including acquired balls) is displayed on the number of balls display 303 and the unused amount is displayed on the amount display 304, and details such as payment data are displayed on the printer 330. In addition to issuing a receipt (prize exchange ticket) with a printed amount, if there is unused money, the bill dispenser 321
And the unused balance is discharged from 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.
Also, the card text is written in the transmission data area (step 55617). Then, the data transmission controller 551 reads this, forms a "payment completion" packet, and transmits it, and the NAU 530 adds a high-rise network head to the beginning of the packet and sends it to the management device 400 (steps 54614 and 53614).

The management device 400 that received the “Payment Completed” packet,
The issuing serial number n is calculated backwards again from the card number in the packet, and based on that, the card file FLI is searched, the card data is read, and the card status is checked. If the card status is "suspended", it is shown in Fig. 85. Pachinko machine 1. After executing the OO interruption end process, changing the card status to "paid" and updating the card history, transmitting an 'ACK' packet to the NAU 530 (steps 52618 to 5262↓), .

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 3'90 via the unit memory 550, and sends it to the unit controller 3'90 via the unit memory 550. When the controller confirms the reception of “ACK”, it enables acceptance of the next card (step 53).
615-55618).

As mentioned above, in response to a card payment request from the payment machine 300, payment data is sent from the management bag [400], and when the payment is completed, the management device is again notified of the completion of payment, and only at that point is the payment processed. Even if an accident such as a power outage occurs during the payment process at the payment machine 300, the payment data will be saved to the FLI card file.
The system is maintained internally, allowing payment processing to continue quickly after a power outage returns. 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 cards is released from the interruption machine. When the card is inserted into the payment machine 300 and the payment process is performed, the suspension is canceled by a command from the management device 400.

The suspended card is inserted into the payment machine, data is transmitted between the payment machine 300 and the management device 400, and the payment process (see FIG. 84) is executed.
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 52622). This packet is once received by the NAU 530, and after the high-level network head is removed, it is sent to the unit controller 180 of the corresponding pachinko machine 100 (step 536).
21). This packet is sent to the data transmission controller 551.
When received, a command “Suspension End” is written to the command register CR2 in the unit memory 550,
When the unit controller 190 reads and confirms this, the card reader 800 is enabled to accept the card, and the operating information regarding the nozuki dick machine in the unit memory 550 is changed from "suspended J" to "free state".
(Steps 54621, 55621.556
22). In addition, the number of balls display ↓11 and amount display 112 on the front of the pachinko machine are cleared to "0",
Flashing a lamp 168 indicating whether or not the card can be inserted, and
The display on the analog display 163 is set to a customer waiting state (scrolling) (steps 55623 to S5625).

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

FIG. 86 shows a procedure for cancellation cancellation processing based on a cancellation cancellation command from the console 4 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 machines on the screen of the CR7 display device 411 (step 52631). , 52632°51632). While looking at this, the operator inputs the machine number of the pachinko machine he wants to cancel the suspension using the numeric keypad 425 on the console 4 (2), 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 "cancellation cancellation" packet containing the serial number and channel number along with the unit number by the communication control unit SCC of the management device. The information is sent to all pachinko machines or to a designated pachinko machine (step 52633). When the designated NAU 530 receives the packet, it removes the head section for the high-level network and sends it onto the low-level network 510, and the data transmission controller 5 of the unit control device 180 that receives and receives the packet.
51 is a command register CR in the unit memory 550
Write a “cancellation cancellation” command to 2 (step 526
34.53631.54631). When the unit controller 190 of the pachinko machine reads this and confirms that the cancellation cancellation command has been entered, the pachinko machine operating information in the transmission data area of the unit memory is set to "free".
At the same time, after clearing the stop calculation register in the transmission data area to zero, the analog display 163 and card insertion lamp 168 are changed to the customer waiting display, and the card reader 800 is instructed to accept the card. (steps 55631 to 55)
634).

On the other hand, when the NAU 530 receives the "cancellation cancellation" packet, it sends a response packet "A" upon receiving a hard ACK from the network controller of the unit controller [180].
CK” to the management device 400. Step 5
3632, 53633), when the management device receives this, it changes the operation information in the P machine file FL2 to "free state" and notifies the result to the local processing device (steps 52635 to 52637), then the local processing device Step 413 changes the status display at the end of the stop table data on the CRT display screen from ``stop'' indicating ``stop'' to ``blank'' indicating ``free'' (step 51634).

FIG. 87 shows a processing procedure when the terminal is forcibly terminated from the management device 400 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 repeatedly operating the force termination switch 434 on the console 412 and selecting the type. The card issuing machine 200 stops issuing cards, all pachinko machines stop operating at the end of business hours, and the payment machine 300 stops operating when the last player has finished paying, thereby ending the business. It can be done smoothly.

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 CR7 display device 411 (step S164).
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 51642). In this embodiment, it is possible to terminate the electronics simultaneously for each type of terminal machine (pachinko machine, card issuing machine, payment machine), or to terminate only one specific terminal machine. When "0" or the machine number that specifies batch termination for each type is input from the console, a forced termination command is sent to the central processing bag @CPU (step 5164).
3).

When the central processing unit CPU 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 cart in which the game is being played or is being interrupted is read out, and the issued serial number is calculated backwards (steps 52641 to 52).
644). Then, using that issuing serial number, rewrite the number of balls and amount in the card file to the data in the pachinko machine file, and change the card status to "free" (
Step 52645). After this is executed for all units, a ``Parcel Forced Termination'' packet is sent to the NAU 530 (step 52646).

When the NAU 530 receives this packet, it removes the high-level network head and sends a "forced termination" packet to all machines, and when it receives a hard ACK from the network controller, it sends a response signal to the management device 400. ACK” (step 53641
．． ．． 53642). When the management device receives the ACK, it sends the result to the local processing device (step 52647).
, 52648). Then, the local processing device displays the status of the display data on the CRT display screen to indicate "free".
The status is changed from "empty" to "strong" indicating a forced termination state (step 51644).

On the other hand, the unit control device 180.280,3 of each terminal that received the "forced termination" packet from the NAU530
50, 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 19
When 0 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, 55641).
). Then, after stopping the detection of the sensor and the firing motor, and turning off all the lamps to stop the game control, a command is given to eject the card from the card reader 800, and it becomes impossible to accept cards from now on (step 85642, 556
43).

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 the process immediately moves to step 52646, where it sends a "forced termination" packet to the designated pachinko machine (see broken line).

Then, when an ACK is returned from the NAU 530, the process moves from step 52647 to step 52642.

At this point, the relevant pachinko machine file is read for the first time, the operation information is checked, and the card file is read and updated only when the game is in progress or interrupted, and step 52645
52648 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 51651).
). 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 example.

Type of each terminal machine (pachinko machine, card issuing machine, payment machine)
It is now possible to terminate all types of terminals at the same time or to terminate only one specific terminal, and if you enter "O" or the machine number from the console to specify batch termination for each type, A forced termination command is sent to the central processing unit WCPU (step 81653).

When the central processing unit CPU 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 ACK from NAU530
When it receives this, it immediately changes the operation information in the file of the terminal to "forced termination" if all terminals are specified, or if a specific terminal is specified, and then sends the result to the local processing device (step 52652, 52653).

On the other hand, the card issuing machine 2 that received the "forced termination" packet
At 00, the operating bit of the operating information in the unit memory 550 is cleared (step 55651), and
The issue stop lamp 222 is turned on (S5652).

In addition, if the 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 card reader 800 to (steps 55652, 5)
5653).

Furthermore, in the transmission system of this embodiment, the management device 40
There is also a packet called ``Parcel Forced Termination Cancellation'' which is used to transmit a command to cancel the suspension of operation of a terminal device that is being forcibly terminated from the 0 side.
There are different types.

FIG. 89 shows the procedure of forced termination cancellation processing common to the pachinko machine 1 issuing machine and payment machine.

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
console 41 while looking at the CRT display device 411 of 00.
When the forced termination release switch 435 is turned on from 2, the local processing device 413 displays a forced termination cancellation menu (step 81661). While looking at this screen, use the numeric keypad to select the type (pachinko machine, issuing machine, or payment machine).
When specified, a command is sent from the local processing device to the central processing unit CPU to request data of the unit that is being forcibly terminated (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 you input all units designation (rOJ) or the unit number using the numeric keypad while looking at the screen, a forced termination cancellation command is sent (
Steps 51663, 51664). Then, the central processing unit first determines whether or not 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 sent to the data transmission controller 55.
1 to the unit controllers 190, 290, 390, and an 'ACK' packet is sent to the management device (steps 53661, 54661, 5366).
2) When the management device receives an ACK, it immediately changes the operation information in the unit file to "free" (pachinko machines) or "
"In operation" (issuing machine, payment machine) (step 526)
65, 52666), then jumps to step 52667 and notifies the result to the local processing device (step 51665).

On the other hand, the unit that receives the "forced termination release" packet changes the operation information in the unit memory 550 to "free" or "in operation" and then lights up the status display lamp 123 in the pachinko machine, or The display 163 is changed to a customer waiting display, and the card reader 800 is enabled to accept the card (steps 55661 to 5).
5663). 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. moreover.

In the payment machine 300, 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 and determine that the unit is down, and the monitor information for the unit in the monitor table will indicate a token bus error. 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, prints out the occurrence of the unit abnormality and the details of the abnormality using the printer 408. At the same time, a command is sent to the local display device 413 to interrupt display of the abnormality of the unit (steps 52672 to 52674).
).

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

On the other hand, after issuing a command to display a unit abnormality, the central processing unit changes the operation information in the unit file to RIJA or "free", changes the card status in the card file to "free", and changes the operation information in the unit file to "free", and changes the card status in the card file to "free". Save the number of balls and amount in the cart file, form a ``Purity 1 Par Unit Check'' packet, and send it to the NAU 530 (Step 5267
5,52676). When the NAU 530 receives this packet, it removes the high-rise head and sends a "unit check" packet to each unit (step 53675).
). If the unit to which the packet was sent is down or a low-layer network error occurs, the heart ACK from the network controller will not be returned to the NAU 530, so the NAU 530 will respond with "A CK" or "N" depending on the presence or absence of the hard ACK. A K” packet is sent to the management device (steps 53676 and 5367)
7).

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 5267 of the unit down detection process in FIG.
While periodically sending "Unit Check" packets in step 52677, the unit recovers as the power is turned on or the low-layer network is connected, and when it confirms the reception of ACK from the NAU in step 52677, the central The processing device 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 53681, 53682).

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).

The unit controller executes 'unit recovery y'-ta'
When the reception of the packet is confirmed, the packet head is copied to the transmission data area, and the pachinko machine 100 transmits the date and identification code to the card reader, and then transmits the "ACK" transmission request via the unit memory. to the controller (steps 55681, 55682
). The data transmission controller sends an 'ACK' packet to N
The packet is sent to the AU, and the NAU adds a high-layer head to the beginning of the packet and sends "ACK" to the management device (steps 54682 and 53683).

When the central processing unit CPU of the management device 400 receives the 'ACK', it forms a 'PARISTART' packet and sends it to the NAU.
Send to 530 (steps 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 53684, 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 executes the same process as in the card-in case of FIG. 78, transmits the cart number, and receives and receives the corresponding cart text.

In addition, the NAU 530 that received the "restart" packet in step 53684 confirms the hardware A and CK from the screw 1-work controller of the unit and sends an "ACK" packet to the management device (step 33685). .

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.

After that, the central processing unit sends a ``Line Monitor Check'' packet to the NAU (step 52695).While the above procedure is repeated every second due to a timer interrupt, the staff member sees the interrupt display and the emergency printout and sends a packet to the NAU. When the NAU recovers by checking the network and high-level network, a "line monitor check" packet is received by the NAU and the ACK is sent to the management device (steps 53691 and 53692).This causes the central processing unit to send the ACK. Check and learn about NAU's recovery.

Sends an interrupt display command to the local processing device 413 and an emergency print command to the printer 408 (step 5)
2696-52698). Then, local processing device 4
13 is a NA at a predetermined position on the screen of the CRT display device 411.
An interrupt message is displayed notifying that U has recovered, and the printer 408 prints on paper that NAU has recovered.

On the other hand, on the unit side, when a transmission cause occurs due to an external action, etc., and a transmission request is made to the data transmission controller 55↓ via the command register CRI of the unit memory 550, the data transmission controller forms a corresponding packet. and transmits it to the 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 54692), returns to step 84691, 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 55694).
. As a result, the external reset circuit 555 generates a reset signal, and the unit controller and other controllers 551, 553 in the unit control bag [180, 280, 350] are all reset to stop the control operation.

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 it went 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 reads the P machine files from the main memory in order, checks whether the operation information is "playing", and if there is no pachinko machine in play, the AC
K to the local processing unit and to all N A U''
Send “Closed Store” packet (Steps 52701-52
704). 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 5).
1704).

On the other hand, when the central processing unit that sent the ``Closed'' packet in step 52704 receives ``ACK'' from the NAU 530, it receives a system termination command from the local processing unit (steps 52704 and 52705). When it 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 52706 to 52708). is received by the local processing unit, and a message instructing the user to turn off the power is displayed on the system shutdown screen (
Step 51705).

NAU53 that received the "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 and 52712). Then, the local processing device displays a power outage message on the CRT display device 411 (step 5171↓). 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 "Closing store J" from the central processing device displays a termination message on the CRT display device (step 51712).

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 on again, in the management bag @400, the central processing unit CPU first clears all files FL1 to FL6 in the main memory M-MEM, and then clears the files (framework ) (Step 5
2721).

On the other hand, the local processing device 413 first uses the CRT display 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 device 1) and loaded into the main storage device, and the local processing device 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).

Furthermore, 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 S2).
725).

On the other hand, when the power is turned on, in the NAU 530, the set value (N
AU number, minimum unit number, number of terminals, etc.), calculate the network transmission address of each terminal, create a unit table, recognize the transmission address of each unit (terminal) and NAU itself, and Clear the unit table containing operating data (steps 53721 to S3724). Then, upon receiving the "unit recovery data" packet from the management device, the NA
After putting the recovery data in the packet into the monitor table, U removes the high-level head and sends a ``unit recovery data'' packet containing the recovery data in the data section to each unit (steps 53725 and 53726).

In addition, unit control devices 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 "r27FF" 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 board, and detect the rising edge of the initialization signal INT from the unit memory from the set value (device number ) is read out 1
After calculating the lower order of serial number and channel number,
Write it to the transmit data area of the unit memory (
Steps 55721-85724). 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 400 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 controllers 190, 2 write the recovery data to the reception data area.
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, "A" is sent via the unit memory. CK" is sent to the data transmission controller (steps 55725, 55726). The data transmission controller sends an “ACK” packet to the NAU, and the NAU adds a high-layer head to the beginning of the packet and sends an “ACK” packet to the NAU.
CK” to the management device (step 54725.5)
3727).

When the central processing unit of the management device receives the "ACK", it forms a "PARISTART" packet and sends it to the NAU53.
Q (steps 52726 and 52728).

When this packet is transmitted from the NAU 530 to the unit controller via the data transmission controller 551 (step 53728), the unit controller restores the display lamps, number of balls, amount display, etc. to the state before the failure (step 55727). ), The pachinko machine then sends a "reload" command to the card reader (step 55728). 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 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 the NAU 530, which received the "restart" packet in step 53684, sends an "ACK" packet to the management device after confirming the hard ACK from the unit's network controller (step 53729).

Next, the central processing unit CPU and local processing when controlling the entire system while communicating with the pachinko machine 100, issuing machine 200, and payment machine 300 using the various packets shown in Table 31 in the management bag [400] The control procedure for bag W4↓3 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 turning on the power, they initialize the internal registers, internal memory, etc., and the central processing unit sets the file framework in the main memory M-MEM. At the same time, the local processing device 413 displays an initial screen (first and second lines only) as shown in FIG. Read the date and time from the central processing bag [CPU (step 5100)
2). 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 bag [M-MEM] and sends 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 "l" 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 has been recovered, and the process moves to step 52041 in FIG. 96(D) (steps 51003, 52002 to 52004).
.

If it is determined in step 52004 that there is no power outage file, the process proceeds to step 52005 where the mode is set to preparation, and the setting value file FL5 is read out from the hard disk HDD and stored in the main memory bag [predetermined file in M-MEM]. The address position is set (step 82006).

Then, the transmission address file FL6 created at the time of system installation is similarly loaded from the hard disk HDD to the main memory bag [M-MEM (step 52007).
).

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 "0" in the other columns (Step 8
2008), and then 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.
and enter it in the specified column of the payment machine file FL4, and write rOJ in the other fences (steps 52009 and 52010).
).

In addition, rOJ is entered in all items in the card file FLI provided in the main storage device M-MEM (step 520).
11) 7) 1 and the like, proceed to step 52012.

In step 52012, after performing the random number generation process (see FIG. 137) necessary to calculate the card number,
It checks whether there is a mode inquiry from the local processing device 413, and if there is a mode inquiry, it sends a response of ``Mode 2 ``Preparing'''' to the local processing device 413 (steps 51004, 52013, and 52014). .

The local processing device receives this and displays the CRT display device 4.
A message MSGI indicating "1 line test in progress" is displayed on the screen of FIG. 138 indicating "Preparing" in step 51005. Then, the local processing unit 413 transmits 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 nine line test'' packets and sends them sequentially to all NAUs 530 via the high-level network 520 (steps 52015 and 52016).
. When the response "A CK" packet is received from the NAU530, the N in the transmission address file FLe is
Write “1” (NAU normal) in bit 0 of AU status 2 (step 8201.7). And all NAU
In step 82, it is determined whether the transmission to the
018), upon completion, the central processing unit forms a 'Unit Table Request' packet and sends it to each NAU 530, and upon receiving an 'ACK' packet from NAT, J, checks whether there is a response from all NAUs. Determination is made (steps 52019 to 52021).

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.
In step 7, the address in the transmission address file loaded from the hard disk HDD to the main memory bag [M-MEM is compared with the address in the transmission address file (step 52022), and it is determined whether or not there is a unit not registered in the file in the received unit table. If there is no unregistered unit (step 52023), leave it as is, or if there is an unregistered unit, proceed to step 520
At step 24, 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 unit 1CPU is transferred to the local processing unit 41.
Send the line test results to 3 (step 52028)
. Moreover, at this time, if there is an abnormal terminal (unit),
The line test result is transmitted along with screen data for displaying the serial number of the abnormal terminal on the CRT screen.

When the local processing bag M413 receives this line test result (step 51007), it determines whether or not there is an abnormal terminal (step 31008), and if not, it directly proceeds to step 31011, and if there is an abnormal terminal, it proceeds to step 5IO09. 139, which displays the serial number of the abnormal terminal on the screen of the CRT display 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 store opening switch is off in step 81010, the process jumps to step 5I006 and the line test request command is sent 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, the central processing unit 1cPU is the local processing unit 413
Upon receiving the initial value setting request command from Step 52029), it forms 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). When a response "ACK" packet is received, it is determined whether initial value settings for all units have been completed (step 520).
31.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 52033).

When the local processing device receives this screen data, it displays it on the CRT display device 411 and then waits for the store opening switch 421 to be turned on according to the message (
Step SIO↓2,5tO13). 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 510).
14).

When the central processing unit receives this command, the NA
Send a store opening packet to U530 (step 5
2034.52035), then “A C
When it receives "K", it checks whether or not the packet transmission to all NAUs has been completed, and when it has finished, it transmits the normal display screen data indicating that it is open 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 device 1.
411 and shifts to control during business hours (step 5105).

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 in the main memory bag [M-MEM, the pachinko machine file PL2, the issuing machine file FL3. The payment machine file FL4 and common data are saved in the hard disk HDD, and the power outage flag is set to "■" before the system is brought down. Therefore, when the power is restored and the power is turned on, as shown in Figure 96 (A
), and when it reaches step 52004, it is determined that there is a power outage file and the process jumps to step 5204 in FIG. 96(D). 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 an ACK from the central processing device, the process moves to step 51004 and inquires about the mode. Then,
At this time, the central processing unit has already set the mode to "starting up from power outage", so upon receiving the mode inquiry, it responds with "starting up from power outage" as the mode (steps 32042, 52043). When the local processing unit receives this mote, 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 51021). Then set the timer.

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

On the other hand, when the central processing bag [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 and 52045), and while waiting for the timer, a "unit recovery" packet is sent to each unit, and each unit's The operating data in the unit memory is restored to the state before the power outage (step 82046). Then, when the "ACK" packet from each unit is received and all units are finished, "μ restart (type)" packets are sent to the NAU 530 one after another to restart the units for each type ( Steps 52047-52
049). Then, “ACK” from each NAU 530
” and when all N A U are completed, the mode of the central processing unit is changed to “open for business” and the data on the normal display screen (Fig. 147) indicating that the central processing unit is open for business is transmitted (
Step S 2050-82053). At this point, the timer set by the local processing bag [413 in step 51023 has timed out and the timer is set in step 51004.
When the mode is returned and the mode is queried, "Business" is returned as the mode, so it is determined as NO in step 51021, and the process jumps to step 5IO25, where the normal display screen sent from the central processing unit is displayed on the CRT display device. 411 and then transitions 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 (Figure 40) 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 unit 4 (3) sends a request command for initial setting values to the central processing unit CP t, J (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 4]3 (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, use the numeric keypad to enter the NAU number.

Number of pachinko machines 5 Input the number of issuing machines or the number of payment machines Local processing bag [41, 3 sends a setting value file update request command containing the updated values stored in the internal memory to the central processing unit (step 51035) ). When the central processing unit CPU receives this command, it first updates the setting value file in the main memory M-MEM, then updates the pachinko machine file, and then sends an "initial value setting" packet containing the updated setting values. Send to all units (step 52
062-82064).

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 8101.3 of the initialization flow in FIG.
2 is turned on, the local processing unit 413 transmits a setting value change request command to the central processing unit 1cPU (step 51041). Then, the central processing unit sends the contents of the setting value file loaded from the hard disk to the local processing unit (step 5207L).
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 stop mode using the numeric keypad according to the instructions on both screens, the local processing unit stores the updated values in internal memory, and then updates the values stored in internal memory. A setting value file update request command containing the value is sent to the central processing unit (step 51044).

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

On the other hand, when the date and time setting switch 439 on the console 412 is turned on while waiting for a switch input in step 51013 of FIG. 146) is displayed (step 51045), and when the operator enters the date and time using the numeric keypad 425 according to the instructions on this screen, the local processing device sends the updated date and time to the central processing device (step 51045). S104
6). When the central processing unit receives the date and time, it changes the current time of the internal timer to the received time, and then sets the "initial value" containing the updated year, month, and day data (other settings remain as they were) to all units. Set “Send packet” (step 32)
075,52076).

In FIG. 99, N A U 530 from the management device 400
The following shows the procedure for periodic data request processing for .

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.
101), if the store is not open for business, the process moves to step 52102 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 S21○5). 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 Q, the process moves to step 52107, and the NA
Among the error counters provided for each U, the error counter corresponding to the non-responsive NAU is incremented, and then in step 52108, the error counter becomes 3.
It is determined whether the error has occurred three times in a row or not, and if it is 2 or less, the process returns to step 52103 and the ``periodic data request'' packet is sent again to the same NAU.Then, the ACK is sent again. If a time-over occurs before the ACK is received, and this is repeated three times, the process proceeds from step 82108 to step 52109, where the status information corresponding to the NAU without ACK among the NAU status prepared for each NAU in the transmission address file is After clearing bit O (NORMAL) to "0", 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 device 411, and the printer 4
08 is given a command to print out the same content. In addition, the local processing device outputs a buzzer 44 after displaying the interrupt.
0 is sounded (step 5211.O, 51051°51052).

Thereafter, it is determined whether or not regular data requests have been made to all NAUs 530, and if no, the process returns to step 52103 and transmits a "regular data request" packet to the next NAU (step 52111). Then, it is determined whether there is no ACK for all NAUs (step 52112).
) L, if no, end the interrupt processing, if yes, clear bit O of all NAU statuses to "On", and then set bit 7 (CHIEPA) of monitor information in files FL2 to FL4 of all units to 1". It is set to memorize that the higher network (high-rise network) is abnormal (steps 52113, 52114).

FIG. 100 shows a processing procedure when an "ACK" packet containing scheduled data is received from the NAU 530 as a response to the scheduled data request.

When regular data is received, the central processing bag [CPU first inspects 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 no 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 521
28, and if it is a different abnormality, the new abnormality is printed by the printer 408 in step 52124. Then, the unit abnormal interrupt display screen data is transmitted to the local processing device 413 (step 52125). When the local processing device receives the above screen data, it displays an interrupt message notifying unit abnormality on the 19th line of the screen of the CRT display device.

On the other hand, when the central processing unit transmits the screen data in step 52125, it next checks the hot code at the end of the received scheduled data (step 52126), and if there is no hot code error, step 82128
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 82128, where the monitor information 2 in the regular data is inspected. Then, if there is an abnormality in the monitor information 2, the steps 52122 to 52 described above are performed.
The abnormality is displayed on the printer and CRT display device using the same procedure as step 125 (steps 52129 to S2132).

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 the processing of steps 5212↓ to 52133 has been completed for all units in the received packet, and if it has not been completed, the process returns to step 52121 (step 5
2134). Also, once all units are finished,
In the next step 52135, 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.
Steps 52121-521 until finished for K”
Repeat step 34.

FIG. 101 shows the processing procedure of the central processing unit [11 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 field in the packet and determine whether the number is rOJ (steps 52141, 52
142). In the system of this embodiment, before the issuing machine 200 actually issues a card, the issuing machine itself may send a "card purchase" packet with the card number set to "0" to reserve the card issuance. , the packet or reserved original “card purchase” for such reservation.
This is to distinguish between packets.

Here, if the card number in the packet is "0", that is, it is a purchase packet for issue reservation.

Proceed to step 52143, 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 issues in the file plus "1" ( Step 52144). Then, when the issuance acceptance number matches the number of issuances + 1, the process advances to step 52145, and the card amount in the packet is r.
Check whether it is OJ or not (step S2↓46). the result,
If amount≠0, step 52149 hedge jump, amount =
If O, the next step 52147 reads the reservation flag from the issuer file and checks whether it is "1", that is, reserved (step 82148).

Here, if the reservation flag is not "1", step 52
At step 149, the card issue serial number in the packet and the number of issues in the file are incremented. Step 521 above
When the amount is not "o" in step 46, the reservation flag is not checked and the card issuing serial number is incremented in step 52149. This is because the card number is "0" and the card amount is incremented without making a reservation. This is to enable a card to be issued even if a packet containing the purchase amount in the 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 for the card, and then calculate the card number from the card issue serial number (step 521).
50, 52151). Then, in step 52152, write the calculated value in the cart number column in the card file, write the values in the received packet in the number of balls and amount columns, set the card status to rfree J, and set the i counter to rlJ. , and after writing the received data and the current time into the history data of i = 1, step 52
153, an ACK” packet is transmitted to the issuing device 200.

Furthermore, if it is determined in step 52142 that the card number is rOJ, and the issuance acceptance number received in step 52144 and the number of issuances in the file do not match, the process moves to step S2↓54. Compare the issuance acceptance number and the number of issuances, and if they match, step S
2. Proceed to L 55 to calculate the card number from the card issued serial number, and in the next step 52156 search the card file using the card issued serial number and read the corresponding file, then proceed to step 52152 described above to calculate the card number. After updating the file, send an "ACK" packet (step 521.53). For example, to make an issuance reservation, a "card purchase" packet was received, steps 52141 to 52153 were executed, and then sent.
CK” packet did not reach the issuing machine within the specified time 1
This takes into consideration the case where the same "card purchase" packet is sent from the issuing machine.

On the other hand, if the card number in the "card purchase" packet received in step 52142 is not rOJ, that is, if there is a genuine purchase application for a reserved card, step 52157 is performed and the issuance acceptance in the packet is performed. The number is compared with the card issuance count plus rlJ in the issuing machine file, and if they match, the card file is searched using the received card issuing 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 “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 hejumps. Send NAK.

The control unit 16 of the pachinko machine 100 is located at the 1102f.
The processing procedure of the central processing unit 1CPU when receiving a "card-in" packet transmitted to the management bag W400 when a card is inserted into the storage bag W400 is shown.

Upon receiving the "card-in" packet, the central processing unit first calculates the card issuing serial number from the card number in the packet (step 52161). Next, search the card file using the calculated card issuing serial number,
Load the file of the corresponding card (step 52162
). 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 82165, and the card status of the card in the file is changed to "free". Check if it is. 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, enter the card text (card number, number of balls, amount and card) read from the card file.
After transmitting the A CK packet to the pachinko machine 100, the card number in the received packet is written in the card number fence 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, jumps to step 52174, and transmits an “NAK” packet. By comparing the card number in the packet with the card number in the file in this way, counterfeit carts can be eliminated. If the inserted card is the one that was interrupted at another pachinko machine, step 52165.
52171, both are determined as NO, and step 521
74 hejymb and sends "NAK".

When it is determined in step 82165 that the card status is not "free" and it is determined in step 32171 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 cart file. The reason why ``ACK'' is returned when the pachinko machine returns after the power is restored is to deal with this, since if the card is reread in the pachinko machine and there is a card, it will send a ``card in'' packet.

FIG. 103 shows that when the interruption card is inserted into the pachinko machine that is being interrupted, the management bag W400 is transferred from the pachinko machine 100.
This shows the processing procedure of the central processing bag [CPU] when it receives the "Interrupt Card-in" packet sent to the CPU.

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 s2↓81). 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 (steps 52183, 52184). Check whether J is false 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 82186.52187). When an interruption occurs, the data and time at the time of interruption are temporarily recorded in the history layer 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 column when writing the primary history data, it is possible to prevent the history data column from becoming full due to frequently occurring interruptions and to make effective use of the memory.

After updating the card file in step 82186 and decrementing the i counter to "-1" in step 52187, proceed to step 82188 and send an "ACK" packet containing the card text read from the card file to the relevant pachinko machine. .

In addition, if the card number in the packet and the card number in the file are compared in step 82184 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. If it is not "playing", it is determined that an inappropriate card has been inserted, and in step 52193 it jumps and sends an "NAK" 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 cart file are checked. 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 ``pachinko 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 52193 and a "NA K" packet is transmitted.

FIG. 104 shows that when the interrupt switch provided on the pachinko machine 1oo is turned on during a game, the management bag W is sent from the pachinko machine to the management bag W.
14 shows the processing procedure of the central processing unit wCPU when it receives an "interrupt switch" packet sent to the CPU 1400.

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 card data (steps 52201, 3).
2202).

Next, the card status of the card data read from the card file is checked to determine whether it is ``J'' during the game (step 52203).

Here, if the card status is "playing", step 5220
Proceed to step 4, compare the card location terminal number in the packet and the card location terminal number read from the file, and if they match, the data in the cart 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 S2205). Then, check whether the counter 1 in the corresponding card file is less than 19 (step 52206), and if it is less than 19, increment the counter 1 in step 52207, and write the machine number, number of balls, and amount in the packet to the next history data layer. 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 step 82206 that the 1 counter is 19, the i counter is not updated, and the data in the packet is written in the step 52208 by jumping to the 9th history data field. 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
to determine whether the cart status is "suspended."

Here, if the card status is neither "gaming" nor "suspended", the game jumps to step 52214 and sends a "N A K" 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, the II ACK "packet" is sent. is returned (step 52213).

This takes into consideration the case where the same "interrupt switch" packet is sent again after "ACK" is sent in step 52209. Note that even if the card status is "suspended" in step 52211, if the machine numbers do not match, "
NAK” packet (step 52212-3)
2214).

FIG. 105 shows the processing procedure of the central processing unit CPU when it receives an "end switch" packet transmitted 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 82201 to 52214) in FIG. 104.

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

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

FIG. 106 shows the reception of a “return” packet that is sent from the pachinko machine to the management device 400 when a zero return (both the number of balls held and the unused amount are zero) occurs in the pachinko machine 100 during a game. The processing procedure of the central processing unit CPU 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 52251, 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 a management device from the pachinko machine when a stoppage occurs during a game in the pachinko machine 100. 400
The processing procedure of the central processing unit CPU when receiving the "return packet" transmitted to the CPU is shown.

Steps 52261 to 52268 in the processing procedure when this packet is received are the same as steps 52201 to 52208 in the processing flow of FIG.
Steps 52211 to 5 in the processing flow of Figure 04
It is almost the same as 2214. The difference is step 5226
When updating the card file in Step 5, "Discontinued" is written as the card status, and in Step 32275, it is not determined whether the card status is "Suspended", but whether it is "Free" or "
This is the point at which it is determined whether or not the game is stopped.

Furthermore, in this "stop" packet reception process, the data and time in the received packet are written in the history data field of the card file in step 52268, and then the
Instead of sending an A CK packet,
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 5L061~
51063).

FIG. 108 shows the flowchart after the payment machine has executed the card payment based on the "Powered Payment" packet and its "ACK" that are sent to the management device 400 when the card is inserted into the payment machine 300. The processing procedure of the central processing unit CPU when receiving the transmitted "payment completion" packet 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 card, and processes the card. Determine whether the state 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 82284, and the card number, number of balls held, and amount are set as the payment acceptance time in the card file. , I entered the card issuing serial number and card history data as payment data.” A CK
”Send the packet to the payment machine (step 52284)
. On the other hand, the card status read from the card file is "
If it is neither "free" nor "suspended", the process moves from step 52283 to step 52285, and a "NAK" packet is transmitted. When the payment machine 300 receives the above "ACK" packet, it issues a receipt with the payment data in the packet printed, refunds the unused money, and then completes the payment.
Send a packet.

When the management device 400 receives this "payment completed" packet, the central processing device 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 searches the card file for the card. Read the data and determine whether the card status is "suspended" (steps 52291-52293); if the card status is "suspended", the location terminal number of the card read from the card file in step 52274 Sends a Pachinko machine that corresponds to the pachinko machine “pachinko end” packet,
After changing the suspended pachinko machine to a free state where you can play, and if the card status is not "suspended", jump to step 52294 and proceed to step 52295.
The i counter in the card file is updated (incremented). Then, change the card status in the card file to "Settled" and check the 1 in the history data column.
After writing the payment data for the second time, the "A CK" packet is sent to the payment 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 51071). When the central processing unit receives this command, it sequentially reads out 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. The machine number and operation data of the pachinko machine in the state, the number of times it has been discontinued.

Send the number of balls out, number of out balls, number of differences, number of balls held, sales, and number of customers to the local processing device (steps 5230↓~5
2303).

Then, the local processing device displays a stop table release display screen as shown in FIG. 148, and displays the stop table and its operation data on one line for each stop table (step S1).
072).

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 the two machine files for all pachinko machines, and if it has not finished, returns to step 52301 to proceed to the next step. 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 32304). Then, the local processing device
．． On the 16th and 17th lines of the stop-stop release display screen in FIG. 48, a message prompting the operator to input the machine number for which stop-stop cancellation is to be performed is displayed (step S1073).

When the operator sees this message, press the numeric keypad 425 to press the machine number or "0"("0") of the pachinko machine you wish to cancel.
If you input "O", all machines are designated), the local processing device transmits a cancellation cancellation request command (step S1074). When the central processing unit receives the command, it determines whether or not to cancel the suspension of all pachinko machines that have been suspended (steps 52306 and 5230).
7).

Here, if all machines are not specified, proceed to step 52308, read the file of the specified pachinko machine, and determine whether the operation information is "discontinued" (step 52309).
). Then, if the operation information is other than "Stop J", jump to step 52314 and send the result, and the operation information will be "
In the case of "Cancellation", after transmitting a "Cancel Cancellation" packet to the designated pachinko machine, determine whether or not "ACK" has been received;
When "ACK" is received, the operation information of the P machine file is changed from "discontinued" to "free" and the discontinuation cancellation result is sent to the local processing device (step 52310).
~52314).

On the other hand, if it is determined in step 52307 that all machines are specified, the process moves to step 52315, reads the P machine files in order, and determines whether the operation information therein is "discontinued j". Otherwise, jump to step 52320, and if "Stop J", jump to steps 52316-5.
2319, after sending a "cancellation cancellation" packet to the corresponding pachinko machine, it is determined whether or not "A CK" has been received;
ACK" is received, change the operation information of the P machine file from "discontinued" to "free" and then step 52
Proceeding to step 320, it is determined whether the processing has been completed for all units. Here, if it is not completed, return to step 52315 and repeat the above procedure, and if it is completed for all units, step 52314
, and send the cancellation cancellation result. Then, the local processing device receives the cancellation cancellation result and changes the character "r stroke" displayed in the last column of the corresponding pachinko machine on the cancellation table display screen in FIG. 148 to "blank". The process ends (step 51075).

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

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 51081). 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. Display the screen (
Step 51082).

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

While looking at this screen, use the console's numeric keypad 425 to press the machine number or "O" (
When the local processing bag W413 sends a forced termination request command to the central processing bag [CPU, specifying all machines), the local processing bag W413 changes the display to the normal display screen (Fig. 147) indicating that the machine is in operation (step 51083, 8108
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 52347, 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.

After entering the data read from the P machine file into the number of balls and amount fields in the file and changing the card status to "free" (step 52346), it is determined whether or not it has been completed for all machines (step 52347), and if it is no. Step 52
Return to step 342 and repeat the above procedure.

Then, after checking the operation information and updating the card files for all machines, the process moves to step 52348, and after transmitting the "1 force forced termination screen type" packet to all NAUs, a response is received from the NAUs. If so, send the result to the local processing device (step 5234
8-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. 157 or the first
When the all-machine display screen in Figure 58 is displayed, the characters 1 r strong j indicating that the machine is being forcibly terminated are displayed in the last column of the corresponding pachinko machine (steps 51085 and 510).
86).

On the other hand, if it is determined in step 52341 that all the pachinko machines are not designated, a "forced termination request (individual)" packet is sent to the designated pachinko machines (step 52351). Then, it is determined whether "ACK" has been returned from the pachinko machine (step 52352), and if not, the process jumps to step 52350, and when the ACK has been returned, the data of the pachinko machine is read from the P machine file. Check whether the operation information is "Playing" or "Interrupted", and if yes, follow the steps 52344-823 above.
After updating the card file according to the same procedure as in step 46, the process moves to step 52350 and sends the forced termination result to the local processing device (steps 52353 to 5235).
7).

FIG. 111 shows the central processing bag WCPU and the local processing bag W41 when turning on the forced termination switch 434 provided on the console 412 to forcefully terminate the issuing machine 200.
3 shows the processing procedure in step 3.

When the forced termination switch 434 is turned on, the local processing device 413 causes the CRT display device 411 to display a forced termination menu screen (step 51091). While looking at this screen, use the numeric keypad 425 to enter the number that indicates 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 issuing machine corresponding to the specified terminal type. The screen is displayed (step 51092).

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

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 changed from 51083 to 51084 to a normal display screen (FIG. 147) indicating that business is open.

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,
5LO96).

On the other hand, if it is determined in step 52341 that all machines are not specified, a forced termination request (individual) to the specified issuing machine
Send the packet (step 82365). and,
It is determined whether or not 'ACK' has been returned from the issuing machine (Step S2366). If not, the process jumps to Step 52364. If ACK has been returned, the operating information in the file of the issuing machine is checked in Step S2366). After changing to forced termination, the process moves to step 52360, and the forced termination result is sent to the local processing device.

FIG. 112 shows a central processing unit [CPU and local processing unit 41
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 of the issuing machine 200 and the payment machine 300 is desired to be forcibly terminated 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 4↓2 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 511.11). When a number specifying a pachinko machine is entered 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 S1112).

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 records the machine number and termination among the file data of the relevant pachinko machine. The number of times, the number of balls put out, 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 S2383).

Then, the local processing device displays the data of the forced termination pachinko machines in one line for each pachinko machine on the pachinko machine termination cancellation screen as shown in FIG. 150 (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 52381).
If the answer is YES, the process moves to the next step 52385 and sends a display data end command 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 "O" to designate all machines from 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, it sends a "forced termination cancellation (type)" packet to all N A U 330, and then
Receive a response (ACK or NAK) from the NAU and send the result to the local processing unit (step 52386)
~52389).

On the other hand, if it is determined in step 52386 that all machines are not specified, the process moves to step 52391 and a ``forced termination cancellation (individual)'' packet is sent to the specified pachinko machines.Then, it is determined whether or not ``ACK'' has been received. If yes, step 52392), if yes, step 5239
Change the operation information in the file of the relevant pachinko machine to "free" in step 3, and then proceed to step 82 if it is no.
389 hejump and send 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 81116).

Fig. 4 of the 1st work shows the case of canceling the forced termination state of the issuing machine 200 which was forcibly terminated by the process of Fig. 111, and Fig. 115 shows the case of canceling the forced termination state of the issuing machine 200 which was forcibly terminated by the process of Fig. 112. The processing procedure of the central processing unit CPU and the local processing unit 413 when canceling the forced termination state is shown.

These procedures are approximately the same as the pachinko machine forced termination cancellation procedure shown in FIG. In the process shown in FIG. 114, the issuing machine file is searched and the machine number of the issuing machine, received amount, deposited amount, payout amount 1 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, in the process of canceling the forced termination of the issuing machine and payment machine, if the process is successful, the status display at the end of each line on the single display screen will change from ``Stop,'' indicating that the operation is stopped, to blank (no display). There is.

FIG. 116 shows the processing procedure of the central processing unit cpU when a power outage occurs.

When a power outage occurs, the power is switched and the central processing unit operates with backup from the auxiliary power supply 409. First, it is determined whether the operating mode is "open" or "closed" (steps 52441 and 52442), and the central processing unit 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. On the other hand, when the mode is "Open" or "Closed," regular data collection from each unit is stopped, the mode is changed to "Power outage countermeasures in progress," and then the local processing unit (Steps 52443 to 52445). The local processing unit then displays a power outage message on the CRT display (
Step 5l141). Meanwhile, the central processing unit reads the two machine files and checks the operating information, and the operating information is "
If the card is currently being played, calculate the issued serial number from the card number in the P machine file, use it to search the cart file, and rewrite the card status to ``Free'' (Step 8).
2446-52450). After that, after rewriting the operation information in the P machine file to "free", it is determined whether or not all pachinko machines are finished. If yes, the data in the common data area (including the setting value file and power outage flag) and the card file 2 The machine file, issuing machine file, and payment machine file are saved on the hard disk HDD, the mode is changed to "closed", and the system goes down (steps 52450-82458).

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 (
Step S142-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 30 seconds, it starts the error recovery process shown in Figure 117.
First, it is determined whether the mode is "in business" or not in step 524.
6↓), do nothing when it is not in business, and if it is in business, proceed to step 52462, read the NAU status from the transmission address file, and set the bit NORMAL, which indicates whether the NAU is normal or abnormal, to "O" (= abnormal). It is determined whether or not (steps 52462, 52463). Note that the NORMAL bit of the NAU status is the 96th
Steps 52016.32017 during the initialization flow in the diagram
If there is a response to the ``Line Test'' packet, it will be marked as ulu (=: normal), so if there is no response, NA
The NORMAL bit of U remains "O".

Therefore, if the NORMAL bit is determined to be “0”, the first
↓NAU recovery processing steps 52471 to 5 in Figure 8 (A)
2475. On the other hand, NOR of NAU status
If the MAL bit is "1pa", proceed to step 52464, read monitor information 1 in the unit file, and check whether the bit indicating the 1-1 Kunbus abnormality is "1".If the MAL bit is "41", then the process shown in FIG. 118 ( Execute token bus recovery processing steps 82481 to 52486 of B),
If 'O', then in the next step 52466, it is checked whether the bit indicating a hot code error in the monitor information processing is set to '1', and if '1', hot code recovery processing 52491 to 52498 in FIG. 119 is executed. On the other hand, step 5
If it is determined in step 2466 that there is no hot code error (no hot code error), the process advances to step 52467, where the monitor information 1 is
Check whether the unit error bit in “
1″, unit recovery processing 52501 to 5 in Figure 120
Execute 2509.

In the NAU recovery process shown in FIG. 118(A), first
If a 6-line monitor check packet is sent to a NAU whose U status NORMAL bit is set to "O" and the timer is set, and a response "ACK" is received before the timeout, the corresponding NAU status is After changing the NORMAL bit to 11111, an interrupt display command is sent to the local processing unit to display a message informing that the NAU has been recovered on the CRT display screen, and print out the same content on the printer 408, and If "ACK" is not returned within a certain period of time, 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 "L" and a timer is set (steps 52481 and 524).
82). Then respond “A” before causing a timeout.
Step 52483 to determine whether or not CK'' has been received;
52484), when receiving "ACK" within the time, clears the token bus error bit of monitor information 1 in the relevant unit file to 110 F+, then sends a "restart" packet to the relevant unit and restarts it. (Steps 52485, 52486)+In the hot code recovery process shown in FIG.
2492),.

Then, if "ACK" is received before a time-over occurs, the hot code placed in the "unit recovery data" packet is compared with the hot code returned in the "ACK" packet (step 52493).
~52495). If the hot codes do not match, the process moves to step 32498 and the hot code error bit of monitor information 1 in the unit file is set to 111.
It is set, and when the hot codes match, a "restart" 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, 52497).

The reason why the "restart" packet is transmitted in step 52496 is that the unit that has received the "unit recovery data" packet transmitted in step 52491 is forced to terminate.

In the unit recovery process shown in FIG. 120, first, a "unit monitor check" packet is sent to the unit in which the unit has an abnormality, and a timer is set (step 525).
01,52502). Then, if "ACK" is received before a time-over occurs, the unit recovery data'' packet is transmitted and the timer is set again (steps 52503 to 52506). When "A CK" is returned, a "restart" packet is sent to the unit to restart the unit (step 5).
2507-52509).

FIG. 121 shows the processing procedure of the central processing unit CPU and local processing unit 4↓3 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 S2511° and the above procedure is repeated (steps S25 and 2 to 52514). Once the operation information has been checked for all machines, step 5
2515, it is determined whether there is a pachinko machine in use, 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 use, it is determined whether or not there is a pachinko machine in use.
CK to the local processing device, and a "close" packet to all NAUs to wait for a command from the local processing device (steps 52516-2518).

On the other hand, the local processing device has a machine number or “ACK”
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 ( Steps 51153-5115
6). If an 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 (from the fourth line to the fourth line) shown in FIG. 153 is displayed (step 51157). 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 of card restoration processing when the cart restoration switch 424 provided on the console 412 is turned on.

When the card restoration switch is turned on, the local processing device 413 displays a message (first to third lines) prompting the user to input the cart number on the card restoration screen as shown in FIG. 154 (step 51161). 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 511
62). 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, 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
In addition, when the card status is other than "playing", the number of balls and amount data in the card file are used as the card's current value, and these values are sent as card data to the local processing device along with the history data read from the card file. (Steps 52533-52536).

Then, the local processing device displays the card revival screen (first
5411ffl), the received cart data and history are displayed (step 31163). Therefore, when the card restoration switch 424 is turned on again, a cart restoration request command is transmitted (step 51164). When the central processing unit receives this command, it first sends the "Initial value transmission" function containing initial values such as date, identification code, etc. to the card issuing bag [1700], and then takes a response ("Normal end" function). When received, a "card restoration" function containing the card 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, 52).
541). Then, the local processing device displays the result on the card restoration screen and then changes the screen to the normal display screen (step S↓165). Note that the card issuing device 700 that has received the above-mentioned "card revival" function,
A reinstatement card will be issued with the date of issue and serial number printed and a reissue hole punched (the amount will not be 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 the test card switch 437 is turned on, the local processing unit 413 displays a test card issue message on the screen of the CRT display unit 41↓, and then sends a test card issue request command to the central processing unit CPU (step 51171).゜51172) Upon receiving this command, the central processing unit sends the "Initial value transmission" function containing initial values such as date, identification code, etc. to the card issuing device 700, and sends a response (
``Successful completion'' function) is received, ``Send test card issue function'' (step 82) is received.
542-52544). When the test card issuance processing in the card issuance bag W700 is completed, the result is sent. After receiving the result, the test card issuance completion is transmitted to the local processing device (step 52545).
．． 52546). Then, 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 31).
173).

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 device 400 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. 124 is started.

First, the local processing module 413 sends a sales statistics data request command to the central processing module 413 (step 511).
81) When the central processing unit receives this command, it reads the pachinko machine files in order and first calculates the cumulative total of the number of balls played, number of balls out, and sales from the operation data collected as regular data (steps 52551 and 52552). )
. Next, check the operating information in the file and if it is "playing", add 1 to the number of gaming machines, and if the operating information is "discontinued"
If so, add 1 to the number of discontinued units (step S2553~
52556). Then, it is determined whether the search has been completed for all pachinko machines (step 52557), and if no, the process returns to step 52551 and the above procedure is repeated, and when the search is completed for all pachinko machines, the next step 52558 is to accumulate the number of balls played and the number of balls out. Divide the value (number of out balls ÷ number of balls out)
After calculating the operating rate (number of gaming machines ÷ total number of pachinko machines) from the cumulative value of the number of gaming machines, the sales, percentage, operating rate, and number of discontinued machines are sent to the local processing device as business statistical data. (step 52558.52559
).

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

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 device 413 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step 5L201).

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 51202).

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 whether it is marked as "Closed", and check the operation data for those that are marked as "Canceled", including the number of balls stopped, number of balls played, number of balls out, number of differences, number of balls held, sales, and number of customers. is transmitted to the local processing device together with the machine number as stop machine data (steps 52561 to S2563).

Then, the local processing device stores each stop table data as the 156th
As shown in the figure, each vehicle is sequentially displayed in one line on the stop table display screen (step 51203). On the other hand, when the central processing unit finishes searching for a stopping machine for all the pachinko machines in the pachinko machine file (step 52564), 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 825
65, 5L204).

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 1413 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 411.
Display a message prompting you to do so (Step S)
L 212). When the operator inputs the machine number using the numeric keypad 425 while looking at this screen, the local processing unit transmits a specific machine display data request command including the machine number to the central processing unit (step S1213).

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, the number of balls stopped, the number of balls out, the number of out balls 5 difference,
The number of balls held, sales, and number of customers are transmitted to the local processing device (step S2573). Then, the local processing device displays the received data on the fifth line of the specific machine data display screen (Fig. 157) (step 5L214).
. Thereafter, a data end command is sent from the central processing unit to the local processing unit and the process ends (step 52574).
, 5L215).

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 module 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 display the central processing bag [CP
An all-machine display data request command is sent to U (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 5258L, 52582).

Then, the local processing device sequentially displays the data of all the pachinko machines on the all-machine display screen, one line per machine, 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).
゜51224).

FIG. 128 shows the procedure for displaying data in the so-called red range (red range), 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 device 4↓3 causes the CRT display 411 to display a display menu selection screen as shown in FIG. 155 (step 51231).

When the operator selects red stand display using the numeric keypad 425 while looking at this screen, the local processing unit transmits a red stand 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), determines whether the number of differences in the file is negative (step 52592), and Send only the operating data of
593).

Then, the local processing device sequentially displays each red stand data on the red stand display screen in order of the one above the red stand as shown in FIG. 159 (step 51233).

On the other hand, when the central processing unit finishes searching for red machines 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 input (steps 52595, 51234).

FIG. 129 shows the procedure of data display processing for a so-called hot table (black table) in which the number of balls put out is smaller than the number of out balls.

This texture display flow is performed according to almost the same procedure as the red 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 red stand 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 issuing machine data display screen displayed on the CRT display device 4 and 1.

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 1. 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 8
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. Displayed on the screen as payment machine data along with the machine number are the payment amount, number of coins paid, number of payments, and 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 device 413 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 in the operating data (steps 52641 to 52641).
52643). Next, the issuance machine files are read in order to calculate the deposited amount and the number of issuances among the operating data (steps 32644 to 52646), and then the payment machine files are read in order and the total amount of deposit and number of issuances are calculated among the operating data. The total number of balls and the number of payments are calculated (steps 52647 to 52649). After that, the calculated total data is sent to the local processing device as sales dataff
After transmitting all 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 411, a 1 display data end command is received, and the key is awaited (steps 31273 and 51274).
). Of the above business data, the number of cards issued is displayed as the number of cards issued, and the number of payments is displayed as the number of cards cleared.

FIG. 133 shows the procedure of a specific cart 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 device 413 causes the CRT display device 411 to display a display menu selection screen as shown in FIG. 155 (step 5L281).

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 3rd to 3rd lines of the specific card data display screen shown in FIG.
51282). When the operator inputs the machine number using the numeric keypad 425 while looking at this screen, the local processing unit sends a specific card display data request command containing the central processing unit CPUA machine number (step 51283).
. Then, the central processing unit calculates the cart issued serial number from the card number, reads the card file using the issued serial number, and determines whether the card status in the card file is "playing" (steps 52661 to 5266).
3). 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 for a pachinko machine file and set the data (number of balls, amount) in the relevant pachinko machine file as the current value of the cart (step 5266
4-S 2666). This is because the card file is rewritten when the card state 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 current cart value determined in step 5 is sent to the local processing device along with the card history data read from the card file, and then a display data end command is sent (step 5).
2667.52668). Then, 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 (step 51284. 51285).

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

When the operator selects cart 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 cart 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 cart 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 cart status of each card in one line for each card (step 5L293).

On the other hand, after transmitting the card data in step 52676, the central processing unit adds "1" to the total number of cards issued, calculates the remaining amount of the card and the cumulative total of the number of balls held, and further updates 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 52679 transmits 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.5L295).

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 5L).
301-51304, 52681-S 2689). 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, only the total data (same as the lower half of the all card details display screen in FIG. 164) is displayed on the screen of the CRT display device 411.

FIG. 136 shows the procedure for displaying 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 device 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 device 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 51312). 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 calculated by comparing the time read from the first history data column of the card (interruption occurrence time) and the current time of the timer. is calculated (step 52693). Then, the elapsed time, cart number, amount of money, number of balls held in the cart data, location terminal number, and interruption time in the history data field are transmitted to the local processing device (step 5
1694). Then, the local processing device displays the data of each card to the construction company as shown in Figure 165.
(Step Sl 313). Furthermore, when the central processing unit finishes extracting data of the suspended carts for all carts 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,
Send a “forced termination request” packet from the management device, then “
By sending a ``forced termination release'' packet, the suspended state can be canceled and the transition to a 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, 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 (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 1 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 a random number 2 (step 52702).

Then, the same < FORTRAN instruction INT(n)
to round down the decimal places of random number 2 (Step 5
2703).

After that, in step 52704, the random number A is determined.

Check whether the condition 0≦A≦↓o000 is satisfied, that is, whether A is thicker than O and smaller than 10000, and
If 0 or A>10000, the process returns to step S1 and the random number A is generated again. Then, step 5270
5, add 10,000 to the random number A that satisfies the above conditions. As a result, the random number A becomes one number between 10,000 and 20,000. Therefore, first, the FORTRAN command MOD is used to find the remainder when the random number A is divided by the integer "5", and this is set 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-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 a gaming system that handles 16-bit data, which will be described later, a code with rlJ in the most significant bit can be used for special cards that are different from normal gaming cards. This is to reserve it for the test cart.

In the primary step 52708, the primary card number Let's do it.

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.

The bit replacement pattern is 15 bits.

There are (15!-1) possible ways, but you can select any 5 ways out 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 the upper five 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 or.

M4932 from X = A + n. This is 1
When expressed in hexadecimal numbers, it becomes r3A54J, and when expressed in binary numbers, it becomes rOOllloooololoooJ.

If this -next card number is converted using the third conversion pattern corresponding to random number B=2, it will be as shown in Table 34 below,
The secondary cart number is 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,5228L) 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 family 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 (
Steps 5101, 5201, 5301). Then, the data transmission controller 55↓ unit memory 550
Appropriate data is written to a predetermined address (27FF) within (step 5202). Then, the unit memory 55
0 raises the level of the signal INT output from a predetermined terminal. This signal TNT is used as an initialization signal by the unit controller 190 (290,
390).

On the other hand, the unit controller 190 (290°390
) clears the internal register and RAM, clears the I10 port (step SI O2), monitors whether the initialization signal INT from the unit memory 550 rises (step 5103), and clears the I10 port.
When the NT starts up, the machine number setter 17.1 (205,
After reading the value set in 352), 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 "O" (steps 8203 and 5204), and if it is no longer rOJ due to writing by the unit controller, the read channel number Latch LT3 (56
3), and then writes a command to latch LT2 (562) that specifies the page configuration in the packet memory used for transmitting and receiving data (steps 8205 and 5206). Then, the network controller 553
reads the channel number in latch LTa and
It stores it in AM to determine its own address in the lower layer network (step 5302), and reads and stores the page configuration of the packet memory from the next latch LTZ (step 5303). This determines the configuration of the send/receive page.

After that, the data transmission controller 551 writes the page number to be used for next data reception into the latch LT2 (
Step 5207). This then becomes a reception permission command to the network controller 553. Therefore,
The network controller checks whether there is a reception page number in the latch LT2, and if there is a page number, it determines that there is reception permission, and step 5305 (
FIG. 167) Move to the following transmission process (step 53)
04). 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 83
06 to 5308), the network controller 553 latches the received command LTI (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 and 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 5210).

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
While 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 3214).

Then, the unit controller 190 (290°39
0) monitors the command register CR2 and determines that the packet type has been written, 5 starts processing corresponding to the 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 3214.
After writing the received packet type name to the command register CR2, it is determined whether or not the packet is a "Pa initial value setting" packet, and if it is a "Pa initial value setting" packet, scheduled data transmission is started. Set a fixed timer (1 second) (steps 5215, 52L6)
. If the received packet is not a ``initial value setting'' packet, it is determined in step 5217 whether it is a ``line test'' packet. If it is a ``line test'' packet, the response is returned in step 8218. C.K.
``Execute processing to send packets and test 4 lines''
If the data is not a packet, the process directly proceeds to other processing.

Next, the packet transmission process will be explained using FIG. 168.

j---t:1n)-0-ra190 (290,39
0), when a packet transmission factor such as "card-in" or 'interrupt switch' occurs, first write the packet type name in the "packet type JIS" in the transmission data area of the unit memory 550. In other words, create a packet head ( Step 5121). Then.

Checks 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, the command register CRI is checked.
Write the name of the packet type to be sent to the RI and then set the send timer (steps 8122 to 5124).
). Writing the packet type name to the command register CRI becomes a transmission command to the data transmission controller 551. On the other hand, the data transmission controller 551 monitors whether the packet type has entered the command register CR1 (step 5221), and when it learns that the packet type has entered, it transfers the transmission data corresponding to the transmission packet type into the unit memory. The data is read from the transmission data area of , and written to page O 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 (steps 5222 and 5223).

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 l of the packet memory, the transmission result is written to latch LT↓ (steps 5324..5325). In response to this, the data transmission controller checks the latch LTI to see if the transmission has been successful, 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 $228 described above, the data transmission controller 55 sets the command register CRI.
If a time-over occurs before the is cleared, the common signal (watchdog pulse) of the display data sent to the pachinko machine control bag W195 is fixed at low level,
Stop the watchdog pulse (step 5L27)
), this causes a reset by the reset circuit 555, and the process proceeds to step S L OL .

5201 and 3301 are initialized.

Next, the scheduled data transmission process will be explained using FIG. 169. The data transmission controller 551 checks the regular timer set in step 5216 (step S23 above), and when 1 second has elapsed,
2, all data in the transmission data area of the unit memory 550 is read out and written into the working area (step 5233). Then, compare the data again with the data in the transmission data area (step 5234), and if the data is correct, 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) is sent along with the sending data.
), the length (number of bytes) of the transmitted data, and the packet type name are written on the page in the packet memory. In addition,
In step 5235, if the command register CRI contains another packet name b), that packet is sent (S2
36) and then proceeds to step 5237.

The reason why the data match is determined in step 5234 is that when the unit controller rewrites the 2-byte data portion of the 2-byte data area for the transmission data area, if the scheduled data is transmitted, undefined data will be detected. This is because data will be transmitted. 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 8238), the data transmission controller 551 writes a transmission command for the data in the pager to the latch LT2 (step 5239).

Then, this becomes a transmission command to the network controller 553, and the network controller 1: I-RA 55
Step 3 checks to see if there is a sending command, and if there is a command, it waits for the transmission right to be acquired on the network, and if it has acquired the transmission right, it waits for transmission permission from NAU force 1 and others (step 8).
331-S 333).

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 5Sil in which no games can be played, a free state fiss12 that is open to all players, a gaming state 5S13 in which a game is being played by a specific player, and a state in which a game is not allowed to be played by a specific player. There are six states: a suspended state SS14 in which the game is stopped with the rights reserved, and a stopped state 5S15 in which a predetermined number of prize balls have been ejected and the game is stopped. Of these, free state 5S12 and suspended state 5S14
Only in the state where cards can be accepted, not only the reset state 5SIO, but also the forced termination state 5Sll, the discontinued state 5
At S15, the cart 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 Figure 1.
No other state transitions are allowed to occur.

That is, the reset state 5SIO transitions to the forced termination state 5S11 only when the "initial value" packet is received. However, if a "unit recovery" packet is received in the reset state after a 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 5SII, it is possible to transition only to the free state jIlSS12, and this transition occurs when a "store opening" packet or a "forced termination release" packet is received. Furthermore, it is possible to shift from the free state 5S12 to the gaming state 5S13 or the forced termination state 5S11, and the game card @5S1 can be changed by receiving the "card-in" packet.
3, ``Closing'' packet or ``Forced termination''
Upon reception of the packet, the state shifts to forced termination state 5SII.

In the game state S S 1.3, when the end switch is turned on or the zero state occurs, the free state 5S12 is entered.
Returns to the suspend state 5S14 when the suspend switch is turned on during the game, and returns to the halt state 5S15 when the halt condition is met.
respectively. A transition is made from the suspended state SS14 or the suspended state 5S15 to the free fiSS12 when a "pause suspended" packet (when payment is made at the payment machine) or a "cancel suspension" packet is received, and the suspended state 5S1
When the cart that caused the interruption in step 4 is reinserted, the game returns to the gaming state 5S13.

Furthermore, in the free state 5S12, in all states of the game state SS 3, the suspended state SS 14, and the abort state 5S15, when a "forced termination request" packet is received from the management device 400, the forced termination state SS↓1 is immediately received. Move to.

Moreover, the system of this embodiment has a test mode that enables games with test cards, 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 5SI2 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 gaming 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 game state 5513' 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 to the free state 5S12' is not due to reception of a "cancellation cancellation" packet but by turning on the end switch,
Also, if you insert the original test card or another test card in the suspended state 5S14', the test game card jllss1
3' and presses the end switch in the suspended state 5814' to shift 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 card 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 f400 in each state of the test mode, the unit control device 180 stores this, and when the termination switch is turned on, each state 5S13 A transition is made from '5S14' and '5S15' to the forced termination state 5S11.

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 5S1 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 the "line test" and ``initial value setting'' packets are received in the standby state 5S20, a transition is made to the forced termination state 5511 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 card 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, maintains control independence for predetermined processing while avoiding malfunctions due to communication errors, and allows prompt responses to player actions.

Hereinafter, processing in the unit controller 190 using the pachinko machine operating information and card status will be explained.

First, before explaining the processing by the unit controller 190, a first explanation will be given regarding mutual data transmission and mutually related operation procedures between the unit controller 190, the pachinko machine control device 195, and the card reader control device 188.
This will be explained using FIGS. 71 to 188.

17] Figure 5 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 J function'' to give the card reader the date code and identification code for the card, ``Card reception possible'' function to allow the card reader to accept the card, ``Card reception possible'' function to allow the card reader to accept the card "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'' which gives a command to drill the return zero hole PH, which indicates that the ball and amount have 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;
The "test card" function notifies the unit controller that a test card has been inserted, the "initial value request" function requests initial values such as date and identification code at the time of reset, and the requested processing has completed normally. "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 "Reload"
There are eight types of "status transmission" functions for transmitting the card reader's status in response to requests and "status requests."

However, communication between the card reader controller 88 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, and pachinko machine controller CPUI are
Initialize internal registers, etc. (steps 5401, 5
501.5601).

When the initialization is completed, the pachinko machine controller CPU
is in 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 F1, calculates the serial number and channel number,
Store in unit memory 55'O (step 5602
). Then, the management device waits for a line test packet to be sent (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 card reader controller CPU2 (
Steps 3604-s6゜6).

On the other hand, upon completion of the initialization, the card reader controller CPL12 transmits a call signal ENQ to the unit controller E90 and receives a response signal ACK.
(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 3504 to S506).

When the two-nit controller receives the transmission of the call signal ENQ from the card reader controller in step 5502 in step 5606, 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 55).
14).

When the unit controller receives the "normal end" function (step 5611), it waits for a "store 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 operation information of is changed to "free" (steps 8612 to 5614). The unit controller then sends a "card accepted" 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 5518), and the process 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 completion J 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, then read the magnetic data and 1
Inspect the year, month, day, and m code (steps 5522 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 190 receives the card number, it sends a "card-in" packet to the management bag W400,
The existence of the card is confirmed by the "A CK" packet and the operating information is changed to "Playing J" (step 8621~
5625), then.

After turning on the status display lamp 162 to notify the outside that the game is in progress, the ball firing bag [103 is enabled to be driven and the system waits for the input of detection signals from each sensor (step 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 5410), and after starting the firing control of the ball firing device, the firing sensor 5N
S5, safe sensor SNS2.5NS3- When detecting the detection signal from foul sensor 5NS4 and out sensor 5NSI, it notifies the unit controller (
Steps 8411-341.6). Moreover, 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, calculates the number of balls being played, and updates the unit memory (
At the same time as steps 8626 to S 630), upon receiving the detection signal of the purchase switch ■]-3, a 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 launcher 103 and transmits an "interrupt switch" packet to the management device 400 (steps 8632 to 5634). Then, when "A CK" is returned from the management device, the operation information in the unit memory 550 is changed to "suspended", and the game status display lamp 123 is driven to blink to display the suspension, and then, Send 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 5
532).

On the other hand, after receiving the "normal end" function (step 5638), the unit controller waits to receive a packet or function (step S620).

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 5533 to 5527). 538). on the other hand,
The unit controller compares the received card number with the card number in the unit memory to check whether the card is a suspended card, and if they match, sends a "suspended card-in" packet to the management device (steps 8639 to 8639). 564
1). When the response "ACK" is received, the operating state is changed to "game in progress", the game state display lamp is changed to a continuous lighting game display, and then control of the batted ball firing device 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 56 in Fig. 173
When the management device sends an "interruption end" packet while waiting to receive 20 packets or functions, 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).
20).

FIG. 174 shows the operating procedure when the end switch 115 is turned on.

When the unit controller 190 detects that the end switch is turned on, it stops driving the batted ball launcher 103, and then sends the "end switch" packet to the management bag W400 (
Steps 5645-5647). And the response “A
CK" is received, the operation information is changed to "Free", the game status display lamp 123 is turned off, and the analog display 1 is turned off.
Scroll 63 to change to the customer waiting display, and then click "
A "card ejection" function is sent to the card reader controller (steps 5648 to S650).

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 541).
0).

Next, we will explain the procedure when a zero return situation occurs during the game in Figure 172, where both the number of balls held and the amount of money are "0".
This will be explained using Figure 75.

As a result of the calculation of the number of balls and the amount of money in steps 5626 to 5631, it is determined whether the number of balls and the amount of money are "O", and if it is "0", the search timer is set for 10 seconds after the drive control of the batted ball launcher 103 is stopped. Turn on (steps 8652-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 "○", and it is further determined whether the search timer has elapsed for 10 seconds (steps 5655, 5656). ), when the number of floating balls reaches rOJ or the search timer has elapsed for 10 seconds, sends a "return to zero" packet to the management device 400 (step 565).
8). Also, if there are floating balls within 10 seconds after the firing device stops, there is a safe ball, foul ball, out ball or WR person, if there is, step 8626 to 5631
The process returns to step 5657 and calculates the man-hours again (step 5657).

When receiving the "ACK" packet from the management device, it changes the operation information to "free", changes the lamps 123 and 163 to the customer waiting display, and sends the "return to zero" function to the card reader controller. (Steps 8659-5662).

When the cart 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 5546).

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 5620).

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, 8665).

When the number of hits has been reached, the drive control of the batted ball launcher 103 is stopped, and then the "stop" button is sent to the management bag [400].
Send the packet (steps 5666.5667).

When receiving an "ACK" packet from the management device, the operation information is changed to "stopped", the gaming status display lamp 123 is turned off, and the analog display 163 is changed to a stopped display (blinking drive). 5668-5670), L
After that, a stop sound is output from the speaker 166, and then
Sends the "Card not accepted" function to the card reader controller CPU2 (step 5671)
゜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, the "normal end" function is sent to the unit controller 190, and the unit controller 190 waits to receive the function (steps S55-5556).Then, the unit controller receives the "normal end" function and enters the packet waiting state (steps 5673, 5556). 5674).

After that, when a "termination release" packet is sent from the management device, 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 accepted" function to the card reader controller (steps 8675 to 5678).
).

Then, the card reader controller opens the shutter, starts card insertion detection, sends a "normal end" function (steps S557 to 5560), and waits for the function or card insertion (step 5520).
). On the other hand, the unit controller displays "Normal completion J".
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. 177 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 notice @ (step 5620) shown in FIGS. 171, 174, 175, and 176.

The unit controller 190 changes the operation information to "forced termination", turns off the lamps 123 and 163, clears the number of balls and amount display to "O", and then sends the "Card not accepted J function" to the card reader controller CPU.
2 (steps 8681 to 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 a "normal end" function, and waits for reception of the function (steps 8561 to 5567).

On the other hand, when the unit controller receives the "normal end" function from the card reader controller, it waits for packet reception (steps 5685 and 8686).

After that, when a "forced termination cancellation" 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 the card reader controller. Send “Acceptable” function (steps 8687 to 56
90),.

Then, the card reader controller opens the shutter, starts card insertion detection, sends a "normal completion" function (steps 3568 to 5571), and then waits for the function or card insertion (step 5520).
). On the other hand, the unit controller is "normally completed"
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 5410).

FIG. 178 shows the procedure for unit recovery processing after a power outage occurs.

When the power outage is restored, each controller CPUL, CP
U2, 190 initialize their internal registers, etc. (steps 5421, 5581, 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. It stores and waits for reception of a "line test" packet (steps 5702 and 5703).

On the other hand, after initialization, the pachinko machine controller CPUI waits for input of detection signals from sensors and switches (step 5410).
), the card reader controller CPU 2 performs steps 3502 to 3502 during power-on reset in FIG. 171.
Do the same as 5506.

After transmitting the call signal ENQ, it is determined whether the signals ACK and ENQ have been received from the unit controller, and when ENQ is received, AC and K are returned, and the function waits for reception (steps 8582 to 8586).

When the unit controller 190 receives the "line test" packet in step 5703, the unit controller 190 then sends the "line test" packet to the management device 40.
Receives the "unit recovery data" packet sent from 0, returns the data in the unit memory to the state before the power outage, and returns an "ACK" packet (step 5
704, 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 870).
8-S 710).

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 and 5714).
. In other words, the original display state is restored except when the original operating state is "gaming". Next, the unit controller transmits a function corresponding to the operation information (step 5715).
). In other words, if it is "free", you can use the cart's "reload" function, and if it is "suspended", you can "accept cards".
function, and otherwise a ``card not accepted'' function.

Then, the card 7 node controller executes the process corresponding to the sent function, then 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, steps 5522 to 5522
After determining the authenticity of the card corresponding to step 525 and transmitting the card number in a function, the process enters a state of waiting for function reception or card insertion corresponding to step 5520.

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 "cart-in" packet corresponding to step 5622 is sent to the management device, and then steps 8623 to 8623 in Figure 72 are sent.
Game processing is started according to the procedure of S63↓.

In this way, if the operating status before the power outage is "Playing", the game is restarted after rereading and checking the card, 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. 79 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 between the card 7 and the controller 88. .

Among 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 number 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 checks the watchdog counter in the unit memory, which sets rFFHJ every time it is transmitted and is refreshed every 20m5. (Procedure P3.P4
). Here, if the watchdog counter is "0", 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 applied 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 81 (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 11-2 are formed and output, and the amount and number of balls are dynamically displayed (procedures P7 and P8).

On the other hand, in the serial interrupt processing shown in FIG. 180, when an interrupt is received from the internal transmission buffer or reception buffer of the unit controller 190.

First, it is determined whether it is a receive interrupt or not, and if it is a receive interrupt, 1 byte of received data is transferred to the internal RAM (procedures pH, P
I3). If the serial interrupt is an interrupt from the transmission buffer, 1-byte transmission processing is executed in which 1-byte transmission data is converted to serial data and output by shifting the transmission buffer (Procedure PI3.
PI3). Note that the above serial interrupt is automatically triggered when transmit/receive data enters the receive buffer or transmit buffer.
An interrupt signal is input to the PU.

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. Interrupt switch 11
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., P52). Comparison of states is performed using a logical operation such as exclusive OR, for example. By doing this, you can easily tell if the condition has changed. Here, if there is a switch that is newly turned on, save the on state of that switch in the internal RAM (
Procedure Pb0).

Next, check whether the sensor is being detected (procedure Pb0).
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
b7).

After that, it is determined whether or not the drive control of the batted ball launcher 103 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 launch sensor saved in the RAM is invalidated in procedure Pb7. (Procedure P
58. 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 1 firing sensor is off, proceed to the next procedure P62 without incrementing the number of floating balls.
Then, it is determined whether the number of floating balls is rOJ. Here, if the number of floating balls is rOJ, disable the ON state of the first safe sensor 5NS2 saved in RAM.
If it is not 0, check whether the 1st t-fusensor is on or not, and if it is on, subtract the number of floating balls (procedures P63 and P64).
After that, 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 "0" or not.

Then, if the number of floating balls is rOJ, the second
Procedure P to disable the on state of safe sensor 5NS3
77), if it is not rOJ, 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 rOJ. 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. (Procedure P69.P2O) After L, if the foul sensor is off again, the process directly proceeds to procedure P71, and it is determined again whether the number of floating balls is "O" or not. Here, if the number of floating balls is "O", disable the on state of the out sensor 5NSI saved in RAM (procedure P79), and if it is not "0", check whether the out sensor is on or not. If it is on with Masato, then the number of floating balls After subtracting (procedures P72 and P73), if the out sensor is off, proceed directly to procedure P74, and if either safe sensor 1 or 2 is enabled, instruct to reserve the output of the hit sound and light the safe ball indicator lamp. Then, the on-count counter for the valid on-state sensor saved in the RAM is incremented (+l) (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", and if it is "gaming", disable the on state of the test switch saved in the RAM (P81). P82), if it is not "playing", press the interrupt switch 114 and the purchase switch 113.
After disabling the on state of the cart (procedure P83), it is determined whether the cart state is "return to zero", and if it is "return to zero", the on state of the saved purchase switch, interrupt switch, and end switch 115 is disabled (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,
Winning balls, etc. that reduce the number of floating balls to 0 or less by deducting the number of winning balls, out balls, and foul balls from the number of launched balls are considered to exist on the game board as floating balls. If it is detected, 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 ten 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 CPU waits for the rise of the initialization signal INT output by writing to the unit memory 550 by the data transmission controller 551 (procedures P94 and P95). Then, when the INT signal rises, the setting number of the unit number setting switch 171 is read, the serial number and the channel number are calculated, and after writing them to the transmission data area of the unit memory, the management device 400 issues a "line test". Wait for the packet to be sent (procedure P96~
P98) and check the test switch 179. And if you receive a “line test” packet, then “
ACK ``Return the packet to the management device, then go to the main task, and if the test switch is turned on before receiving the PA line test'' packet, set the test mode flag and then go 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, the unit memory 550 is checked to determine whether a packet has been sent from the management device 400, and if there is no received packet, it is determined whether the state is waiting for the return of a +t"AcK" packet (procedure P King○1.
, P2O3). and.

If no (no), return to procedure PIOI and repeat the above steps.When the 'ACK' packet is waited for in procedure P2O3, the process moves to procedure PIO3 and is set in procedure P2S5 in the packet transmission task in Figure 187. Reads the timer waiting for ACK.

The first step is to check whether or not the timer has timed out, and if a timeout has occurred, the ACK reception error flag in the internal RAM is set (procedure P2O
3, PtO2). This flag will be referenced in the error control task (Figure 1.88), which will be described later.

On the other hand, if it is determined that there is a received packet in the above procedure Plot, 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 (procedures P2O3, P2O
3). If it is "NAK", it sets the NAK flag prepared in the RAM (procedure P2O3), and if it is not "NAK", it directly proceeds to procedure P2O3, and the received packet is registered. Determine whether it is something. If the packet is unregistered, procedure P1. 1 Clears the packet type name in command register CR2 of the unit memory to "O" with O, and returns to procedure PIO1. 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 is a registered one, it is determined which packet it is in procedures 1 to 125, and processing is performed according to the type of packet found (FIGS. 184 (A) to (184)). N)).

FIG. 184(A) shows the procedure of the ``initial value setting'' packet reception process in the packet reception task.

When the unit controller 190 receives the ``initial value setting'' packet, it copies the hot code into the corresponding column in the reception data area of the unit memory 550, and also copies the hot code into the transmission data area (procedure P2O3,
P2O3). 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 of the transmission data area by the unit controller. Next, check the "initial value not set" bit in the monitor information to determine whether the initial value has been received.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 (reception) 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 in normal operation mode, check the flag to see if the initial value has been sent to the cart reader in procedure P2O3, and if it has been sent, clear the initial value received flag (procedure P2O3), then proceed to procedure P2O3. The process then moves to P310 to permit transmission 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
If it is determined in step 312 that the initial value packet has not been received, the process advances to step P313 and the monitor information
If the "initial value setting" bit is cleared and it is determined that the initial value has been received, proceed from procedure P312 to P314, reserve the transmission of the "initial value setting" function, and then return to the original processing routine (Figure 183). return.

FIG. 184(B) shows the procedure of "store opening code" packet reception processing in the packet reception task.

When the unit controller 190 receives the "opening code" packet, it first sets the operation information to "free", then looks at the flag and determines whether it is in test mode (procedures P321 and P322), and then, in test mode. If so, return to the original routine, change the display on the lamps 123 and 163 to the customer waiting state if it is in the normal operation mode, write the "Card Acceptable" function to the RAM, make a transmission reservation, and then turn on the card insertion lamp 168. After changing to blinking drive, return to the original routine (Procedure P32
3. P324. P325).

FIG. 184(C) shows the procedure for the "Packet closing code" packet reception process during the packet reception task.

When the unit controller 190 receives the "closing code" packet, it first checks the operating information, and if the operating information is "gaming" or "interrupted", it returns to the original routine. The ``Closing Code'' packet is usually sent after the ``Forced Termination'' packet, so there is no way the ``Closing Code'' would be sent even if there is a Pachinko machine that is playing or has been suspended. , functions as a safety device in case you accidentally turn on the closing switch. Also, if the operation information is not "gaming" or "interrupted", change it to "forced termination", then look at the flag. It is determined whether the test mode is in progress (procedures P331 to P333). and,
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 the original routine (Procedure P334.P2
S5).

In addition, the test mode judgment (P333) is performed after changing the operation information to "forced termination" in procedure P2S5. This is to quickly shift the pachinko machine to a forced termination state after the termination.

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 next procedure P343, select "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, after stopping sensor detection and control of the ball launcher ↓ O3, turning off all lamps, and sending the "Card not accepted" function to the card reader, 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 cancellation" packet, it first examines the operating information and determines whether or not it is being forcibly terminated, and if it is not being forcibly terminated, it does nothing and returns to the original routine (procedure P351). .

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 original routine is returned to, and the pachinko machine can be transferred to the free state as soon as the test mode ends.

On the other hand, when it is not in the test mode, the lamp display is changed to the customer waiting state, a "card accepted" function is scheduled to be transmitted 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 of the "1 abort cancellation" packet reception process.

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 P2S5, 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 "suspension 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 in procedure P372, the operation information is set to "free j", the card text data in the unit memory 550 is cleared, and then the test mode is determined, and it is now possible to accept cards 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.

Upon receiving this packet, the unit controller 19
0 first copies the packet head of the reception data area to the transmission data area, and then clears the "initial value setting" focus on the monitor information (procedure P2S5.F'382).
. The ``Par Unit Recovery'' packet is sent when an abnormality is detected during regular data collection or when a power outage is restored; however, in the former case, the unit controller has already received and retained the initial value; This is because when power is restored, a ``unit recovery'' packet is sent after an ``initial value setting'' packet is sent.

After clearing the bit of monitor information 1, control of the batted ball launcher 103 and sensor detection are stopped, and then the transmission reservation of packets and functions that occurred before the abnormality was discovered is canceled and the flags related to packet transmission and card reader control are cleared. After stopping the operation, a reservation is made to send an “ACK” packet to the management device 400 (P3
83-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". then 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 "restart" packet, it first starts communication control with the card reader and "reserves transmission of the initial value setting J function" (procedures P 391 and P 392).

Next, check the operating 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 P39).
3).

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", that is, when it is "free" (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. 184 (J) shows a processing procedure when a response to the ``cart-in'' packet is received in the packet reception task of FIG. 183.

When there is a response to the card-in TI packet, the unit controller 190 checks (procedure P2O process) that the controller was in the ACK waiting state and receives an ACK.
“A CK” with card text even though it is not waiting
When a packet arrives, treat it as an error and clear the card text data in the reception data area (procedure p402).
). On the other hand, when a packet comes in while waiting for an ACK, it is checked whether the packet is a NAK (negative response) or not (procedure P2O3). If it is a NAK, it is assumed that the card does not exist and a "card ejection" function is sent to the card reader. Then, a sound output method for generating a sound representing failure of card acceptance is reserved and the process returns to the original routine (procedures P2O3, P2O3). In addition, even if the response is not a NAK, if the cart 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 not be accepted (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゜P2O3).

After that, check the card status in the card text (procedure P2O3), and if the cart is in the "stopped" state, change the cart state to "free" and change the operation information of the pachinko machine to "playing". Management device 400 after rewriting
A reservation is made to send a "1 termination switch" packet to the management device (procedures P421 to P423).As a result, the "termination switch" packet is transmitted to the management device, and the 'A
CK” packet is returned (described later) (184th
The card is ejected by the end switch processing shown in Figure (L)), and the game with the stop card is disabled.

On the other hand, if it is not a discontinued card, 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
11), and if it is not "Free" (when the game is suspended), proceed directly to procedure P412 and change the operating information to "Playing".
After changing the lamp display to the gaming state, the internal R
The floating ball number counter in the AM is cleared and detection by the sensor is started (procedures P413 to P415). next,
Check the number of balls in the card text and if it is "0", leave it as is.
Also, if it is not OJ, start drive control of the ball firing bag [103], proceed to procedure P4I8, and reserve the output of the card acceptance success sound (procedures P416 to P418).

Furthermore, when the response "ACK" packet from the management device to the "interrupt card-in" packet is received, it is processed according to the same procedure as the response packet to "card-in" shown in FIG. 184 (J). 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 waits for ACK.
If an "ACK" packet arrives even though it is not waiting, it does nothing and returns to the original routine.

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 drive 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 (procedures P427 to P427).
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). In other words, even if the end switch is pressed, if a NAK is returned from the management bag [400 and the operation information is "gaming", the card state is returned to "gaming" and the pachinko machine is refused to shift to the suspended state. If you want to interrupt, press the interrupt switch again.

FIG. 184 (L) shows the processing procedure when an "ACK" packet for a packet is received by the end switch.

This process is performed by the "interrupt switch" in the same figure (K).
This process is executed in substantially the same manner as the ACK'' 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" and the lamp display is changed to a customer waiting display (procedures P444 and P445). In this process as well, if the operation information indicates that the game is in progress when a NAK is received, the card status is returned to the game and the end process is canceled (procedures P451 to P454).

FIG. 184 (M) shows “Return to zero” packet
ACK” packet is received.

This process is performed at the "A C" of the "End Y switch" in the same figure (L).
K'' is executed according to the same flow as the reception process (procedures P461 to P474).

184 (K) shows the "A CK '" packet reception process for the "ACK" packet shown in FIG. 184 (N).
It is executed according to almost the same flow as the "A CK" reception process of the "interrupt switch" (procedures P2S5--P4
94). The only difference is the card ejection function,
Reservation for sending functions that do not accept cards (procedure P4)
88) is 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, a flag in the internal RAM is checked to determine whether the card reader is in a controllable state, and if no, serial transmission interrupts and reception interrupts are prohibited (procedures PI31 to P133).

On the other hand, when the card reader is in a state where it can be controlled,
The process moves from procedure PI31 to P2S5, and it is determined whether the function is being transmitted. Next, it is determined whether the function is being received, and if it is, it is checked whether the reception is completed within the set time (procedures PI35, PI40). Also, internal RAM
Check if there is a function in the receive buffer area of the process (Procedure PI3)
6) 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 PI3.1),
Procedure for determining the type of function P143-P1
50), corresponding processing (Fig. 186 (A) to (H)
).

Furthermore, when it is determined in the procedure PI36 that there is no reception function, the process moves to the procedure PI37, and it is determined whether or not it is in the state of waiting for a response function from the cart reader controller CPU2, and the time required to receive the response is checked ( Procedure PI42). 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, it is determined whether there is a function to be sent (Procedure PI39). (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 P2O1 to procedure P512, and it is determined whether the operation information in the test mode operation data area (see Table 1) is "suspended." Interrupt switch 1↓4 while playing in test mode
If the game is interrupted by pressing , the interruption will be canceled by inserting the test card without pressing the test switch, so that the game can be resumed. 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 P513 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 P513 that it is online, the transmission reservation of the "card ejection" function and the output reservation of the card reception failure sound are performed (procedure P514.
P515). In other words, when online, if a test card is inserted without pressing the test switch (79), the test cart is ejected and the test game cannot be started. This prevents fraudulent games by the player.

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 "test card" function reception wait state is established, and then whether or not the test mode is in progress is determined (procedures P521 and P522). If it is determined that the function is waiting for reception or is in test mode, jump to procedure P525 and "Eject card"
After the function transmission reservation is made, the output reservation of the card acceptance failure sound is made (procedure P526). In other words, even if a regular game card is inserted immediately after the test switch is turned 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 to determine whether the operation information is suspended, and if it is not suspended, a "card-in" packet is reserved for transmission ( Procedure P5
27) If it is suspended, compare the card number read in procedure P524 with the card number in the transmission data area,
If the card numbers do not match, proceed to procedure P525 and make a reservation for card ejection; if the card numbers match, proceed to procedure P5.
The process moves to step 28 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, it first clears the ``abnormal end'' flag and then saves statuses ``E'' and ``2'' in the receive buffer to internal RAM (Procedure P531.P53).
2). The "abnormal end" flag is referred to in the error control task procedure P170 of FIG. 188.

Next, it is determined whether the "Card Receivable" function was sent 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 a "Card Receivable" 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 11-line test packet. Wait (procedures P536 to P538).

On the other hand, if you have not sent the previous card reception function - or if you have sent it but the card is not in the reader, or if you have sent the card reception function and the card is in the reader but it is not "playing". If so, the process moves to procedure P2S5 without making a card ejection reservation, and determines whether the end of the test mode is online or offline, and if offline, jumps to waiting for a "line test" packet.

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 referenced in procedure P163 in the error control task in FIG. 188.

In FIG. 186(E), the unit controller 190 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 the "abnormal end" function is received, check the status 1 sent at the same time, and if the initial value for the card reader has not been set, proceed directly to procedure P532 in the same figure (C).
If the initial value is not set, an "abnormal end" flag is set, and then 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. 1-85.

When this function is received, the "Initial value setting" function is first reserved for transmission, and then the flag is checked to determine whether transmission is prohibited (Procedure P2S5.P2
S5). Here, if transmission is prohibited, allow transmission in procedure P2S5, and if transmission is not prohibited, check the operation information of the pachinko machine in procedure P2S5, and if it is "free", "playing", or "suspended", "cards accepted". ” function transmission reservation is made (procedure P2S5). On the other hand, procedure P2S5
If the determination is other than ``free'', ``gaming'', or ``interrupted'' (stopped or forced termination), a transmission reservation of the ``card acceptance not possible'' function is made (procedure P2S5).

If it is determined that the "self-ejection" function has been received during the task shown in Figure 185, 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 P2S5). .

Next, FIG. 186 CI) shows a transmission processing procedure when it is determined in procedure P2S5 that there is a transmission function 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, then set the ACK reception timer (5 seconds), and send the call signal ENQ to the card reader (procedure P 560). -P 56
2). Then, if ACK is not received, it is determined whether the timer set in procedure P561 has exceeded (procedure P
563°P564). Even if a timeout occurs, check the number of retries and if the predetermined number of times (3 times) has not been reached, return to procedure P561, reset the timer, and press EN.
Repeat transmission of Q. If an ACK still does not come and the retry count is exceeded, an error flag is set and function transmission is canceled (Procedure P565.P
566, 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 of the packet transmission task among the ten types of main tasks of the unit controller 190. In the task, first, it is determined whether or not there is a packet to be transmitted, and if there is, the transmission data in the unit memory 550 is After writing the packet type name in the packet head portion of the area, the packet type name is entered in the command register CRI in the communication area, and the packet transmission timer is set (procedures P1.51 to P154). Command register CR
By writing the packet type name to I, the data transmission controller 55L starts transmitting the corresponding packet.

When the transmission is completed, the command register CRI is cleared.

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 has been set, and if it has been sent, the process moves to procedure P2S5, and if it has not been set, the process returns to P2S5.

In procedure P2S5, it is determined whether the command register CRI has reached rOJ due to the end of transmission, and if it has not yet reached rOJ, it is checked whether the transmission timer has exceeded (procedure P↓59). Here, if the transmission timer has not exceeded, the process returns to procedure P2S5. 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 a type that receives an ACK, such as a card-in, set the ACK wait timer (10 seconds) and then reset the transmission timer ( Procedure P2S5.P2S5).

This 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 190.

In this task, we first set the “Z-80 error” flag (see
Check the "Packet ACK error" flag (see P105 in Fig. 183) and the "Packet ACK error" flag (see P105 in Fig. 183).
2S5. P2S5) If either flag is set, proceed to procedure P174 to disable timer interrupts and serial interrupts, and also power down the CPU after stopping the task processing (procedures P175 and P176). . The above procedures (P174-P17
6) can be executed by, for example, 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, the "z-s o error" flag also
If the "ACK error" flag is also not set, the "Pallider error" flag (P543, P545 in Figure 186) is set.
．． If the flag is not set, reset the "reader error" bit of monitor information 2 in the unit memory 550, and then proceed to procedure P2S.
Return to step 5 (procedure P2S5.P164). If the 'reader error' flag is set, procedure P2S
5, set the "reader error" bit in monitor information 2, clear all reader control flags, and enable reader control (procedures P↓66, P2
S5). After that, check whether you are in test mode or not and whether initial values have been set.Procedure P2S5. P1
69), in the test mode or when the initial value has not been set, the following test mode termination 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
If it is, 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. After clearing the "abnormal end" flag, return to procedure P2S5 (procedure P17
2, P173).

FIG. 189 shows the procedure of the ball number calculation task among the ten types of main tasks of the unit controller 190.

In this task, first, check the flag or signal to determine whether the sensor is being detected, that is, if the game is being played (P181),
If the sensor is not being detected, clear the counter that counts the number of times each sensor is turned on.
Read the number of ON times of each sensor of firing sensor 5NS5, safe sensor 5NS2, second safe sensor 5NS3, foul sensor 5NS4, and out sensor 5NSI obtained by the process in Figure (A), and calculate the total number of balls awarded and the ball output. number, 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, a flag or signal is checked to determine whether or not the sensor is being detected (Procedure P2O1). (Procedures P2O2 to P2O6). When 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 "O" and the amount is not rOJ, purchase request processing (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, if both the man-hours and the amount are "0", the search timer (10 seconds) is activated to start the zero-return 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 zero, and makes a reservation for transmission of a "pareturn 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, the process moves to procedure P212 and returns to zero even if there is a floating ball number. This is because it is normally impossible for floating balls to still exist even after 10 seconds have passed since the number of balls reached rOJ.

Also, if the search timer has not exceeded, the process moves from procedure P2O9 to P210, and it is determined again whether the number of balls is "0" or not, and if it is not "O", the search timer is stopped and the return to zero is determined. Cancel (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 "O" 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. When is 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). If the test mode is not, a "stop" packet is scheduled to be sent.
Update the number of stops in the unit memory 550 (+1) L,
After setting the card state to "stopped and free", sensor detection and drive control of the batted ball launcher 103 are stopped,
Make a reservation to output the stop sound (procedures P582 to P587)
.

Note that although the card ejection command is not performed here, the above-mentioned "stop" packet is sent to the management bag [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
Procedure P in FIG. 184 (N) when transitioning from S5 to P2S5 and receiving ACK for the "stop" packet
483 to P489 (excluding P2S5), procedures P591 to P597 are executed, and the state is stopped. The test mode is designed to be executed even when the system is offline and not connected to the management device. If termination occurs during the test mode, turning on the termination switch 115 shifts to the test mode termination process, and the subsequent state is determined depending on whether it is online or offline (FIG. 191(e)) , (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, reserve the transmission of an "interrupt switch" packet, change the card status to "interrupted", stop sensor detection and drive control of the batted ball launcher 103, and return to the original routine (procedure P603 to P605), ejection of the card due to turning on the interrupt switch is performed at the time of receiving the ACK packet for the above packet (18th
(See Figure 4 (K)). On the other hand, when the interrupt switch is turned on during the test mode, the operation information is updated, the transmission of the card ejection function is reserved, and the display of the control stop lamp is changed during the interrupt switch processing (Procedure P611~ P6 6). 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 21 (hereinafter referred to as a purchase lamp) built into the purchase switch (procedure P621). This lamp is
It is lit until the amount does not reach rOJ, and the number of balls is r
It is driven to blink by the purchase request procedure P2]7 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, it is determined whether the amount on the card is rOJ, and if it is rOJ, the 190th
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 and the number of balls in the unit memory 550 (procedure P624).

Then, the frequency of the amount (remaining amount) is "-2" and the number of purchases is r+14. After the sales frequency is “+2”, the amount is r
It is determined whether or not the OJ has become OJ (Procedures P625 to P6
28). Here, if the amount is rOJ, 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. Additionally, if the player turns on the purchase switch based on the purchase request sound and display,
The purchase lamp changes from flashing to on or from flashing to off depending on the amount of money on the card.

After starting control of the batted ball launcher, the output of the purchase request sound is canceled, and 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 P641 and P642). after that,
In procedure P643, it is determined whether the mode is test mode or not. If the test mode is the test mode, the process moves to the test mode termination process shown in FIG. Change the status to "free" (procedures P644 and P645).

Card ejection commands, lamp display changes, etc. are performed during the processing of receiving the response packet ACK on the interruption switch (18th step).
This is done in Figure 4 (L)).

FIG. 191(e) shows the test switch processing procedure in the switch detection task of FIG. 190.

When the test switch]79 is detected to be on, first, the output of the switch operation sound is reserved and the test card function wait flag is set (procedure P65↓, 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 user is offline, and if offline, a reservation is made to send a "cart acceptance" function to the cart reader, and if 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 it is actually possible to accept cards online (suspended), if the operation information is other than "free", the test card will be ejected (see Figure 186 (A) Procedure (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 P665)
If the process is forcibly terminated, a transmission reservation for the "card not accepted" function and an output reservation for the card ejection sound are made, and the process returns to the original routine (procedures P671 and P872). In addition, when the card reader receives the "Card not accepted function", it will eject the card it is holding and then go into a state where it will not accept any cards.In cases other than forced termination, the lamp 123
, 163 to the customer waiting state, and then checks whether the operation information in the operation data area in the test mode is "discontinued" (procedures P666, P667). If it is canceled, jump directly to procedure P670, and if it is not canceled, "Card ejection J function transmission reservation and card ejection sound output reservation (procedure P2S5, P669
) to proceed to procedure P67o, change the display of the card 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, when the status is canceled, procedure P2S5 (card ejection function transmission reservation) is omitted and procedure P66 is executed.
The jump from 7 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, when termination occurs in the test mode, 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).

The reason for outputting the card ejection sound here is that it does not match reality.

On the other hand, if it is determined that the process is offline in the above procedure P2S5, 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 "reader 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 and follow the steps above.
Clear the "Offline" flag at the end of the test mode and wait for the "Line test" packet (Figure 182 Procedure P9)
8). The above flag is used in procedure P2S5 during the "Status" function reception process (Figure 86 (C)).
When the status is sent, this flag is referenced and the process goes to wait for 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 it receives the "normal end" function after ejecting the cart from the card reader and receives status 2. . On the other hand, when there is a reader error, when the card ejection process is executed in response to the function of procedure P673, if the card reader sends "abnormal end" and status 1°2, the process shown in FIG. 186(c) Procedure P
In order to prevent the card from becoming impossible to take out due to a transition to line test standby in 2S5, the "offline at end of test mode" flag is cleared in procedure P677.

FIG. 192 shows the processing procedure 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 "Card ejection sound", "Successful card reception sound", or "Before unsuccessful cart reception sound" (procedures P221 to P225), and if there is a reservation, select the type of sound to be output. After setting the indicated data and output time in the internal RAM, the voice synthesis circuit (sound IC) 582 is reset and the sound being output is stopped (Procedure P231
゜P232). Then, proceeding to procedure P2S5, a control signal is given to the sound IC to output the selected sound. Then, it is determined whether the set output time has elapsed, and if it has exceeded, the output is stopped (procedure P2S
5. P2S5), On the other hand, if the output time has not exceeded, determine whether the output sound is a repeating sound, and if it is not a repeating sound, stop the sound output (Procedure P236.P2S
5).

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 the "search timer sound,""purchase request sound,""stopsound," 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 100m5 are used as standards for lamp blinking, packet transmission timer, ACK reception timer, etc.
It manages two reference timers for mS, updates (decrements) the loms timer every Ion seconds, and
Update the 100mS timer every 00ms (Procedure P
241-P244).

FIG. 194 shows the processing procedure of the lamp display control task among the main tasks of the unit controller 9o.

In this task, during the above various processes, the safe bulb lamp 164, the number of P machine status display lamps lit, the built-in purchase switch lamp 121, the card insertion lamp 168. When the game status lamp 123 is updated, its display status is changed (procedures P251 to P255). Next, determine whether it is necessary to display a "waiting for customers" or "discontinued display",
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 in order from the left side according to the number of balls (procedure P260.P2S5).
. Moreover, this analog display of the number of balls is performed using a so-called logarithmic display in which the number of balls 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 logarithm display 63 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 × mark is off, the ○ 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, ○: On, △:, =W, 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 ■/○ 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 for the 4-card-in'' packet at timing t□, when the ON signal of the purchase switch 113 comes in at timing t2, the firing drive control signal is changed to a high level, and the batted ball firing device 1103
becomes drivable. At the same time, the frequency of the balance of the card is subtracted by "2", the number of balls worth 200 yen is added, and the amount display and the number of balls display are 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, the detection pulse of the safe sensor (p x
(see), this will be considered invalid and the number of prize balls will not be added accordingly.

During such game control, when the on signal of the interruption switch 114 is input (timing ti), 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), the game control is started again, and the game is terminated when the end switch 115 is turned on (timing ts), the '' end switch At the time when the ACK of "" is received (timing tc), the display, number of balls, and amount data are cleared to "0".

On the other hand, when a zero state occurs during the game where the card amount and man-hours both become rOJ (timing t7)
, the search timer is activated, and if there is no detection pulse of safe sensor or 2 within 10 seconds, a "return to zero" packet is transmitted, and the number of floating balls is cleared to rQJ when the ACK is received (t8). If the number of floating balls reaches rQJ while the search timer is operating, a "return to zero" packet is transmitted at that point.

In addition, in the above embodiment, when forcibly releasing a pachinko machine that has been in a suspended state for a long time, first send a "forced termination" packet to the pachinko machine to terminate it, and then force the pachinko machine to release the pachinko machine again. We are trying to release a pachinko machine that is currently suspended by sending a "termination release" packet, but for example, we can prepare a work menu and its processing program for releasing the suspended table in the management device, and then pay the suspended cart at the payment machine. The pachinko machine that is currently suspended may be released by using a "pause suspension end" packet that is sent to the pachinko machine when the pachinko machine is suspended.

Furthermore, the above embodiment is applied to a gaming system in which only the card number is recorded in the cart as a storage medium, and the purchase amount and number of balls are stored in the storage device of the management device in correspondence with the card number. Although the invention has been described above, the present invention is not limited thereto, and can also be applied to a system in which a game is made possible using a card that records the purchase amount or the number of balls.

Further, the card 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 perform payment based on their own judgment.

[Effect of the invention] As explained above, the present invention connects a plurality of gaming machines and a management device through a transmission line, and provides valuable data substantially equivalent to the amount of money or the number of balls to the card. A card-type game in which each identification code is managed in a management device, and games can be played within the range of valuable data obtained from the management device based on the identification code read from a card inserted into a gaming machine. In the system, the gaming machine is equipped with a switch that ejects the cards, stops gaming control, and returns to a state where the game can be played again only by inserting the same cart, and the management device is equipped with a switch that allows the game to be played again only when the same cart is inserted. provide a means for counting the duration of the interruption;
Since the above-mentioned suspension duration time can be displayed externally based on an instruction from the console, it is possible to leave the gaming machine while retaining the right to play on the gaming machine, and the management device can also display the interrupted gaming time. It is possible to monitor the elapsed time of a game machine, and if the game machine has been interrupted for a long time, the suspended game machine can be forcibly released for other players by commands from the management device. without compromising customer interests.

This has the effect of allowing all players to be given fair gaming opportunities.

[Brief explanation of drawings]

1@ is a system configuration diagram showing the overall configuration of the 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, Figure 2 (C) is an explanatory diagram showing an example of the configuration of the authenticity identification area in the card, Figure 2 (D) is a sectional view showing an example of the cross-sectional structure of the card, Figure 2 (E) is an explanatory diagram showing an example of the configuration of the magnetic recording section in the card, Figure 3 is a perspective view showing an example of the overall configuration of the pachinko machine that constitutes the gaming system, and Figures 4 (A) and (B) are the front side of the pachinko machine. 5 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 side view of the back of the pachinko machine. FIG. 8 is a perspective view showing the enclosed ball circulation device installed in a pachinko machine; FIG. 9 is a perspective view showing details of the base of the ball launch rail; FIG. 10 The figure is a perspective view showing the state where the front panel of the pachinko machine is opened. FIG. 11 is a perspective view showing an example of the configuration of a frame board that includes a frame for holding a game board and a firing rail coupled to the frame, and FIG. 12 is a perspective view showing the back configuration of the front frame of the pachinko machine. FIG. 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 an example of the configuration of the pachinko machine control unit, and FIG. 15 is a perspective view showing the internal configuration of the control unit. FIG. 16 is a perspective view showing the configuration of the front panel of the control unit. Fig. 17 is a perspective view showing the installation positional relationship between the pachinko machine and the control unit, Fig. 18 is a perspective view showing the framework of the island equipment where the pachinko machine is installed, and Fig. 19 is the installation position of the pachinko machine and the control unit on the island equipment. Fig. 20 is a perspective view showing the back of the island equipment; Fig. 21 is a block diagram showing the control system of the entire pachinko machine; Fig. 22 shows an example of the circuit configuration of the pachinko machine control device. Block Diagram FIG. 23 is a block diagram showing an example of the circuit configuration of a pachinko machine control unit. Fig. 24 is a memory map showing the area configuration of the unit memory, Fig. 25 is a perspective view showing an example of the structure of a card reader of a pachinko machine, Fig. 26 is an exploded perspective view of the card reader, and Fig. 27 is a card reader card reader. 28(A) and (B) are exploded perspective views showing details of the card insertion portion of the cart reader; FIGS. 29(A) and 29(B) are cross-sectional side views showing details of the card insertion portion of the cart reader;
) is a cross-sectional side view showing details of the shutter portion at the entrance of the card reader, FIG.
Figure (B) is a sensor detection timing chart when a card is inserted, Figure 31 is a block diagram showing an example of the circuit configuration of the card 7 node control device, Figure 32 is a block diagram showing the card reader interface circuit, Figure 33 34 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 diagram showing the front panel of the issuing machine opened. Figure 36 is a perspective view of the card issuing device installed in the issuing machine, Figure 37 is a schematic configuration diagram of the card issuing device, and Figure 38 is a perspective view showing 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. A 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. FIG. 53(A) is a block diagram showing an example of the configuration of the transmission system in the gaming system of the present invention; FIG. FIG. 53(C) is a block diagram showing a method of connecting a transmission system when the transmission line is configured with a coaxial cable. FIG. 54(A) is a block diagram showing a configuration example of a NAU (network adapter unit) that controls data transfer on a network. Figure 54 ('B) is a perspective view showing the external appearance of NAU, Figure 55
Figures (A) and (B) are management devices on a high-rise network.
A configuration diagram showing the packet structure between NAUs and between the management device and the unit, FIG.
Block diagrams showing the packet structure between AUs and between the management device and the unit, FIGS.
B) is ``Line test ``Packet and its response'' A C
K ``Packet configuration diagram. Figure 57 (A) and (B) are the configuration diagrams of the ``unit table request'' packet and its response packet. Figure 58 (A),
(B) is a configuration diagram of an "initial value setting" packet and its response packet; FIGS. Figures (A) and (B) are configuration diagrams of the ``packet'' for various commands and its response ``ACK'' packet, and Figure 61 (
A), (B), and (C) are "card-in" packet and its response "A CK" packet and negative response" N A
K ``packet configuration diagram. Figure 62 is a configuration diagram of a ``periodic data transmission'' packet from a pachinko machine to NAU. The configuration diagram of the response packet on the recovery data, Figures 64 (A), (B), and (C) are the "Purchase Cart" packet and its response "A CK" packet between the issuer and NAU on the low-layer network. Negative response” N
A K” packet configuration diagram, Figure 65 shows the N packet from the issuing machine.
A configuration diagram of a “periodic data transmission” packet to the AU; FIGS. 66 (A) and (B) are configuration diagrams of a “unit recovery data” packet and its response “A CK” packet to the issuer on the low-layer network; Figure 67 (A)
, (B) and (C) are block diagrams of the "card payment" packet and its response "ACK" and negative response "NAK" packet sent to the payment machine on the low-layer network. ), (C) is a diagram of the configuration of the Packard payment completion packet, its response "ACK" and negative response "NAK" packet, and Figure 69 is the configuration of the Packard payment machine's regular data transmission to NAU packet. Figures 70 (A) and 70 (B) are configuration diagrams of the "unit recovery data" packet and its response A CK packet sent to the payment machine, and Figure 71 is the data transmission control procedure in the data transmission controller of the NAU. FIG. 72 is a flowchart showing the control procedure for token bus abnormality detection by timer interrupt in NAU, FIG. 73 is a flowchart showing the procedure for initializing the entire system, and FIG. 74 is the unit table by the management device. A system flowchart showing the procedure from a request to setting an initial value for the unit. Figure 75 is a system flowchart showing the procedure for periodic data collection from each terminal by the management device. Figure 76 is a system flowchart showing the procedure for the management device to collect data from each terminal. Figure 77 is a system flowchart showing the processing procedure for a command, and Figure 77 is a system flowchart showing the processing procedure when a banknote is inserted into the card issuing machine and the purchase switch is turned on. A system flowchart showing the processing procedure when a card is inserted. 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 shows the pachinko machine during an interruption. Figure 81 is a system flowchart showing the processing procedure when a card is inserted into the pachinko machine, Figure 82 is a system flowchart showing the processing procedure when the game end switch of the pachinko machine is turned on during a game, Figure 83 is a system flowchart showing the processing procedure when the number of balls held and the amount of money are both zero, Figure 83 is a system flowchart showing the processing procedure when a stop occurs during the game, and Figure 84 is the payment machine Fig. 85 is a system flowchart showing the processing procedure when a card is inserted into the machine, Fig. 85 is a system flowchart showing the processing procedure to end the interruption when the suspended card is settled at the M machine, and Fig. 86 is the console of the management device. Figure 87 is a system flowchart showing the processing procedure when a command to cancel pachinko is received from the console of the management device, Figure 88 is a system flowchart showing the processing procedure when a forced termination command is received from the console of the management device FIG. 89 is a system flowchart showing the processing procedure when a forced termination command is entered from the console of the issuing machine or the payment machine; FIG. The figure is a system flowchart showing the detection processing procedure when a unit goes down. Figure 91 is a system flowchart showing the unit recovery processing procedure in which the management device restores the data of the terminal when the down unit recovers, and Figure 92 shows the case where it is detected that the NAU is down and then the NAU recovers. Figure 93 is a system flowchart showing the data recovery processing procedure for each terminal, Figure 93 is a system flowchart showing the system termination processing procedure from the management device's closing command to each terminal, and Figure 94 is the processing when a power outage is detected. System flowchart showing the procedure, Figure 95 is a system flowchart showing the procedure of system startup processing after power outage recovery, No. 9611il (A
) to (D) are flowcharts showing the initialization procedure of the central processing unit and local processing unit 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 99 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; FIG. 99 is a flowchart showing the processing procedure for periodic data request by timer interrupt. FIG. 100 is a flowchart showing the procedure for receiving the scheduled data as a response, FIG. 101 is a flowchart showing the processing procedure when the management device receives the "Card Purchase" packet, and FIG. FIG. 103 is a flowchart showing the processing procedure when the management device receives the "suspension card-in" packet. FIG. 104 is a flowchart showing the processing procedure when the management device receives the "suspension switch" packet. 10 is a flowchart showing a processing procedure when receiving a message. FIG. 105 is a flowchart showing the processing procedure when the management device receives the "termination switch" packet, FIG. 106 is a flowchart showing the processing procedure when the management device receives the "return to zero" packet, and FIG. 107 108 is a flowchart showing the processing procedure when the management device receives a "cancellation" packet, and FIG. 108 is a flowchart showing the processing procedure when the management device receives a "card payment" packet. A flowchart showing the processing procedure when the termination release switch on the top surface of the console is turned on. Figures 110, 111, and 112 show the processing procedure when the forced termination switch on the top surface of the console is turned on in the management device. Flowcharts, Figures 113, 1↓4, and 1/5 are flowcharts showing the processing procedure when the forced termination release switch on the top of the console is turned on in the management device, and Figure 116 is the procedure when a power outage occurs FIG. 117 is a flowchart showing the procedure for power outage processing in the management device. FIG. 117 is a flowchart showing the procedure for network error recovery processing in the management device. 118(B) is a flowchart showing specific steps of the token bus recovery process in the process flow of FIG. 117; FIG. 119 is a hot code recovery process in the process flow of FIG. 117 FIG. 120 is a flowchart showing the specific steps of the unit recovery process in the process flow of FIG. 117. FIG. 121 is the process when the closing switch on the top of the console is turned on in the management device. A flowchart showing the procedure. Fig. 122 is a flowchart showing the processing procedure when the card recovery switch on the top of the console is turned on in the management device. Fig. 123 is 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. Flowchart showing the processing procedure. Fig. 124 is a flowchart showing the procedure for interrupt display processing of sales statistical data by timer interrupt. Fig. 125 is a flowchart showing the procedure for displaying data of the stop table. Flowchart showing the procedure for data display processing. Fig. 127 is a flowchart showing the procedure for data display processing for all machines. Fig. 128 is a flowchart showing the procedure for displaying data in the red section. Fig. 129 is a flowchart showing the procedure for displaying data in the black section. Flowchart showing processing steps. Fig. 130 is a flowchart showing the procedure of data display processing of the issuing machine, Fig. 131 is a flowchart showing the procedure of data display processing of the payment machine, Fig. 132 is a flowchart showing the procedure of all business data display processing, Fig. 133 134 is a flowchart showing the procedure for displaying data of a specific card, 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, and FIG. 136 is a suspended card. Flowchart 5 showing the procedure of data display processing of FIG. 137 is a flowchart showing the procedure of card number generation in the management device. FIG. 138 is a display screen configuration diagram showing an example of the configuration of an initial screen displayed on a CRT display device in the management device; FIG. 139 is a display screen showing a configuration example of an abnormal terminal display screen displayed on a CRT display device in the management device Screen configuration diagram; Figure 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; Figures 141, 142, and 143 are CRT display devices in the management device; 144 is a display screen configuration diagram showing an example of the configuration of the initial value setting screen displayed on the CRT display device in the management device; FIG. 146 is a display screen configuration diagram showing a configuration example of a stop mode setting screen displayed on a CRT display device in the management device, and FIG. 146 is a display screen showing a configuration example of a date and time setting screen displayed on a CRT display device in the management device. Diagram. FIG. 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 FIG. 148 is a configuration of a cancellation cancellation screen displayed on a CRT display device in the management device FIG. 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. FIG. 3 is a display screen configuration diagram showing an example of the configuration of a pachinko machine forced termination cancellation screen. Fig. 151 is a display screen configuration diagram showing an example of the configuration of a issuing machine forced termination cancellation screen displayed on a CRT display device in the management device, and Fig. 152 is a payment machine forced termination cancellation screen displayed on a CRT display device in the management device. 153 is a display screen configuration diagram showing an example of the configuration of a system termination screen displayed on a CRT display device in the management device; FIG. 154 is a display screen configuration diagram showing a configuration example of a system end screen displayed on a CRT display device in the management device FIG. 155 is a display screen configuration diagram showing an example of the configuration of a card restoration screen displayed on a CRT display device in the management device; FIG. 157 is a display screen configuration diagram showing a configuration example of a stopping platform display screen displayed on a display device; FIG. Figure 158 is a display screen configuration diagram showing an example of the configuration of an all-machine data display screen displayed on a CRT display device in the management device, and Figure 159 is a configuration example of a red-machine data display screen displayed on a CRT display device in the management device. 160 is a display screen configuration diagram showing an example of the issuing machine data display screen displayed on the CRT display device in the management device, and FIG. 161 is a display screen configuration diagram showing an example of the issuing machine data display screen displayed on the CRT display device in the management device. FIG. 3 is a display screen configuration diagram showing an example of the configuration of a payment machine data display screen. FIG. 162 is a display screen configuration diagram showing an example of the configuration of a sales data display screen displayed on a CRT display device in the management device; FIG. 163 is a configuration example of a specific card data display screen displayed on a CRT display device in the management device 164 is a display screen configuration diagram showing an example of the configuration of a card details data display screen displayed on a CRT display device in the management device; FIG. 166, 167, 168, and 69 are flowcharts illustrating packet transmission/reception control procedures in NAU; FIG. 170 (A) ~(C) shows the transition of the operating state of the pachinko machine, where (A) is the normal operation mode, and (
B) is a state S transition diagram in online test mode, and (C) is a state S 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 at the time of insertion, Figure 173 is the flowchart when the interruption switch is turned on, Figure 174 is the flowchart when the settlement switch is turned on, Figure 175 is the flowchart when the return to zero state occurs, Figure 176 177 is a flowchart when a termination state occurs, and FIG. 177 is a flowchart when a "forced termination" packet is received. FIG. 178 is a flowchart for unit recovery after power outage recovery. 179 to 192 show the task processing flow of the unit controller, and FIG. 179 is a flowchart showing the procedure of timer interrupt processing. FIG. 180 is a flowchart showing the procedure of serial interrupt processing; FIGS. 181 (A) and (B) are flowcharts showing specific steps of sensor, switch detection processing, and switch invalidation processing in the interrupt processing flow of FIG. 179; Step 82@ is a flowchart showing the procedure of the initialization task, which is one of the main tasks of the unit controller. Fig. 183 is a flowchart showing the procedure of the packet reception task. Fig. 184 (A) shows the procedure during the packet reception task. 184(B) is a flowchart showing the specific procedure for receiving the "Initial value setting" packet. FIG. 184(C) is a flowchart showing the specific procedure for receiving the "Park store opening code" packet. FIG. 184 (D) is a flowchart showing the specific procedure of receiving a "forced termination request" packet, and FIG. 184 (E) is a flowchart showing the specific procedure of receiving a "forced termination request" packet. FIG. 184 (F) is a flowchart showing the specific procedure of the "stop cancellation" packet reception process. FIG. 184 (G) is a flowchart showing the specific procedure of the "suspension end" packet reception process. , FIG. 184(H) is a flowchart showing the specific procedure of the "unit recovery data" packet reception process. FIG. 184 (I) is a flowchart showing the specific procedure of "restart" packet reception processing, and FIG.
184(K) is a flowchart showing the specific procedure for receiving the "K" packet. FIG. 184(K) is a flowchart showing the specific procedure for receiving the "interrupt switch ACK" packet. FIG. 184(L) is for receiving the "end switch ACK" packet. FIG. 184 (M) is a flowchart showing the specific steps of the “return ACK” packet reception process; FIG. 184 (N) is the specific flow chart of the “stop ACK” packet reception process. 185 is a flowchart showing the procedure of the reader I11 control task, which is one of the main tasks of the unit controller, and FIG. FIG. 186 (B) is a flowchart showing the specific steps of the process, and FIG.
FIG. 6(C) is a flowchart showing a specific procedure for receiving the "status" function during the reader control task, and FIG. 186(D) is a flowchart showing the specific procedure for receiving the "retransmission request" function during the reader control task. FIG. 186(E) 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(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 Fig. 187 is a flowchart showing the procedure of the packet sending task, which is one of the main tasks of the unit controller, and Fig. 188 is a flowchart showing the procedure of the packet sending task, which is one of the main tasks of the unit controller. 189 is a flowchart showing the procedure of the control task, FIG. 189 is a flowchart showing the procedure of the pitch count calculation task, which is one of the main tasks of the unit controller, and FIG. 190 is a flowchart showing the procedure of the switch detection task, which is one of the main tasks of the unit controller. FIG. 191(a) is a flowchart showing the specific procedure of the abort process during the switch detection task in FIG. 190; FIG. 191(c) is a flowchart showing the specific steps of the purchase switch process during the switch detection task of FIG. 190; FIG. 191(d) is the switch of FIG. 190. 191(e) is a flowchart showing the specific procedure of the end switch processing during the detection task; FIG. 191(f) is a flowchart showing the specific procedure of the test switch processing during the switch detection task of FIG. 190; FIG. 190 is a flowchart showing the specific procedure of the test mode termination process during the end switch processing in FIG. 192 is a flowchart showing the procedure of the sound control task which is one of the main tasks of the unit controller. 194 is a flowchart showing the procedure of a timer control task, which is one of the main tasks of the unit controller; FIG. 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 in the unit control device. 100...Pachinko machine, 110...Operation panel, 113...Purchase switch, 114...Interrupt switch, 115...End switch, 130...
Ball circulation device, 160...control unit, 180...
... Unit control device, 188 ... Card reader control device, 195 ... Pachinko machine control device, 190.
...Unit controller, 200...Cart 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 , 80'9...
・Shutter solenoid, 82o...Punch device, 82
1...Magnetic head.

Claims (1)

[Claims] (1) A plurality of gaming machines and a management device are connected via a transmission line, and valuable data substantially equivalent to the amount of money or the number of balls is managed in the management device for each identification code given to the card, and gaming In a card-type gaming system that allows games to be played within the range of valuable data obtained from the management device based on an identification code read from a card inserted into the machine, the card is ejected into the gaming machine. A card-type game system characterized by being provided with a switch for stopping game control and shifting to a state where the game can be played again only by inserting the same card.