JPH0473080A - Apparatus for managing card type game system - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

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

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

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

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

The second card method is to issue a card with only a code number recorded at the time of card purchase, store the number of balls held in a central management device, and insert the card into the card reader of the pachinko machine. This allows you to play a game by calling up the stored number of balls you have. In that case, when the card was issued, the entire purchase amount was converted into balls held, and the number of balls held was stored in the management device (Jikko Sho 61-
No. 32709, Special Publication No. 51-171 (J No. 6 IFR
eL＞.

[Problems to be Solved by the Invention] Among the conventional card systems described above, in the first card system in which the number of balls held is stored in the card eye, the card itself or its magnetic surface may be damaged, If the data on the magnetic surface is destroyed by magnetic noise, it becomes impossible to read the ball count data. In this case, even if you show the damaged card to an attendant at the gaming parlor, there is no way for the gaming parlor to confirm the number of balls you have.

Therefore, if measures are taken to restore the number of balls held by relying on the player's request, there is a risk that the game parlor will suffer great damage due to the player's fraudulent request.

Therefore, in this system, it is necessary to take measures such as not providing compensation for damaged cards. As a result, the player is responsible for any damage to the card, and if the card is accidentally damaged, the player has no choice but to accept the loss. Also,
In order to avoid such unexpected disadvantages for players, the only way to avoid such unexpected disadvantages for players was to keep the maximum issue amount of Ricard cards, which are made of highly durable cards, to a low level. However, this increases the cost of issuing cards for the game parlor, and increases the number of times the player must purchase cards.
There was a problem in that the game was interrupted each time, resulting in a loss of interest.

On the other hand, in the second card system, in which the code number is recorded on the magnetic surface of the card, and information such as the number of balls held is stored in the memory of the management device, if the card or its magnetic surface is damaged or the magnetic data is If the card is destroyed, the code number on the card cannot be read. Therefore, even if the management device has the number of balls in its memory, it is difficult to retrieve the data.

Therefore, in the conventional card system in which a code number is stored on the card, it is virtually impossible to restore a damaged card. As a result, the same problem as the system that stores the number of balls held on a card has arisen.

However, placing all responsibility on the player for damage to the card is not only financial, but may cause problems between the player and the game arcade if the card is damaged due to unforeseen circumstances. is high.

In particular, in a system in which the number of balls held is stored in the memory of the management device, if the card is damaged when the player wins a large number of prize balls, the damage to the player will be very large.

Therefore, it is desirable for card-based gaming systems to have means for restoring cards. However, if you open the door to card restoration too easily, there is a risk that the game parlor will suffer damage due to fraud, so you must proceed with caution.

In addition, if a gaming system is configured in which all terminal machines (pachinko machines, card issuing machines, payment machines) are centrally managed under the control of a management device in a card-based system, the pachinko machines are placed between the management devices. After exchanging cart numbers, etc., the device becomes operational, and the device becomes inoperable 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 launch rate. In that case, a test drive will be performed after repair or nail adjustment. Therefore, apart from the normal game cards, there is a need for test cards that allow trial playing.

This invention was made against the above-mentioned background, and it paves the way for the restoration of damaged cards while preventing fraud, and effectively protects the interests of players without causing any disadvantages to game arcades. This prevents troubles between players and game parlors, improves the reliability of card-based gaming systems, and allows pachinko machines to operate independently even when disconnected from the management device. To improve the flexibility of a card-type game system by making it possible to issue test cards that enable trial play.

[Means for Solving the Problems] In order to achieve the above object, the present invention provides a card-type game in which a card with only a code recorded at the time of card purchase is issued, and the number of balls held is stored in a management device. In the system, the management device is equipped with a card issuing device having at least a card reader capable of writing magnetic data into the magnetic recording section of the card and a printing device capable of printing characters etc. on the surface of the card. It was configured so that special cards such as resurrection cards and test cards can be issued by commands from the console.

[Function] According to the above-mentioned means, it is possible to check the history data of the player on the screen of the CRT display device of the management device and decide whether or not to reinstate the card. It will be possible to revive the system and effectively protect the interests of players. In addition, since the management device is equipped with a card issuing device, there is no need to use a issuing machine to issue resurrection cards or test cards, and there is no need to bother players who are trying to purchase cards for playing games. There is no.

[Example 1] Fig. 1 shows an example of a pachinko game 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. This management device 400
0 and a data transmission path 500 that organically connects each terminal, and these constitute an organic combination. 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 10 which is each component of the organic combination
0° issuing machine 200, payment machine 300 and management device [400
Each is equipped with a card reader (in this specification, a device that writes on the magnetic surface of a card is also referred to as a card reader), and information on the card and information on each terminal device is stored in a management system. 400 storage devices in the form of files.

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

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

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

By inspecting the perforations formed on the card with a photoelectric detector, you can easily check the card's condition without having to check the number of balls held by reading data from a file on the management device using a code recorded on the magnetic surface. As a result, it is possible to reduce the burden on the card reader controller and management device required to determine the processing corresponding to the card status.

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

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

Further, in the card of this embodiment, an authenticity discrimination area TF consisting of a security mark hidden in characters such as hole names printed on the surface of the card is provided below the magnetic recording section MG. That is, the rPL printed on the front of the card
Design and print the characters AZAJ so that the legs of each character are located at positions corresponding to the detection bit patterns Bo-B provided at a pitch of 3°51, etc., as shown in Figure 2 (C). I'll keep it. And the width of one character is 0.5~1°5
m+, so that the distance between each bit is 3.5no, and each bit's "1" or '0' is expressed by the shading of the character.Moreover, among the 10 bits, the fifth bit from the left, B4, and the last Bit B is Bit B.

The shading of the characters is determined in advance to represent the parity of ~B3 and BS-B. 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 card of this embodiment, a head cleaning area HCN is provided in which a cleaning agent for removing dirt from the magnetic head is applied to a band-shaped area continuous with the magnetic recording part MG. At the same time, in order to make it impossible to tell where the magnetic recording part MG is provided in the card of the embodiment, as shown in FIG. 2(D), a base material 1 made of plastic such as polyester
A white layer 13 is formed on a magnetic layer 12 formed by uniformly coating magnetic particles on the white layer 1, and a pattern printing layer 1 is further formed on top of the magnetic layer 12.
4, a heat-sensitive coloring layer 15 is formed on a portion thereof (a portion corresponding to the print display section PRT), and a transparent protective film 16 is coated above it. A cleaning agent of the same color as the white layer 13 is applied to the cleaning area HCN, and the protective film 16 is not coated on its surface so that it is exposed, so that the cleaning area is hardly different in color from other areas. In this way, we are trying to improve the aesthetic appearance. Further, a pattern printing layer 17 is formed on the back surface of the base material 11 of the card, and a protective film 18 is coated on top of the pattern printing layer 17.

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

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

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

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

For cards with a magnetic recording section, it is generally easiest to decipher the recording format and recorded data from the date, but in the card of the above example, the order of the year, month, and day is changed, and the parity is set every 4 bits. The presence of pits and the variable correspondence between recording bits make it extremely difficult to counterfeit cards. In addition, since the issued 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, the card can be recovered from the file information on the management device. can.

Furthermore, as described above, the information recorded in the magnetic recording section of the card of this embodiment includes the identification code DSC for specifying the usable space of the card, and the date of issue for indicating the validity period of the card. Only the DATE, the card number as an identification code obtained from the issuing serial number n using an appropriate function or conversion method, and a check code for error detection are recorded, and the purchase amount and number of balls held are not recorded. . These are configured so that the data files of the management device 400 can be withdrawn in real time depending on the card number number. 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 100, and is mainly used to control the display and card reader, and to control 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 is fixed to the lower part of the machine frame 101 and has an operation dial reinforcing member 107a that can withstand the weight of the pachinko machine 100 and absorbs vibrations of the ball firing bag W103. At the bottom of the pachinko machine 100, a ball launcher 103 that launches enclosed balls one by one into the game area and its operation dial 104 are provided. Amount display 111, number of balls display 112, purchase switch 113, interruption switch 114, for enabling the start procedure.
An operation panel 110 is provided that includes an end switch 115, a game status display 116, and the like. The configuration of the playing area on the front of the pachinko machine is the same as the conventional one. The purchase switch 113 provides an instruction to convert the card into game balls in units of 200 yen, etc., 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. With the switch, the converted game ball becomes 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 sides and number of balls (sum of purchased balls and acquired balls) in the file of the management device 400, and then inserts the card into the slot 802a of the card reader 800. Emit more.

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

The operation panel 110 is connected to the pachinko machine 1 as shown in FIG.
It is attached to the front panel 105 that can be opened and closed at the bottom of 00,
The operation panel 110 has a hollow shape with a triangular cross section, and its top surface is sloped downward toward the front to make the display easy to read.
Wiring boards 12OA and 120B are arranged in parallel with the circuit boards 12OA and 120B, and on the board 12OA are an amount display 111 and a ball number display 112 made up of 7-segment LEDs, and on the board 120B are the above-mentioned switches 113 to 115 and a built-in lamp. is attached and covered with a 1 display plate 117. The part of this display plate 117 corresponding to the above-mentioned indicators 111 and 112 is a transparent affected part 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 within this opening 117b so as to cover the upper part of each of the switches 113 to 115. 121 is the purchase switch 113
It is a built-in lamp that is compatible with

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

Furthermore, an operation button 12 with a built-in stop switch 124 is provided on the side of the operation panel 110 (on the left side in the embodiment).
5 is attached, and when this switch 124 is turned on, commands related to the game can be given, such as stopping the operation of accessories arranged in the game section. The stop switch 124 is connected to the operation panel 110.
A wiring group 126C installed on a wiring board 12OC disposed inside and extending from this wiring board 120C and wiring groups 126A and 126B extending from each of the boards 120A and 120B are pulled out to the outside. Connectors 127A to 127C connected to the ends can connect the lower part of the back surface of the pachinko machine to a pachinko machine control device W195.

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

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

A game board in which a winning ball collection gutter 131 covering a plurality of winning ball outlet holes formed to penetrate the game board corresponding to a winning area provided in a playing area on the front side of the game board is held on a frame 106. is attached to the back of the The bottom wall of the winning ball collection @131 is sloped downward toward the center to form a guide shelf 131a, and below that, as shown in Fig. 7, out balls @132a, a first safe ball gutter 132b, and a second safe ball gutter 132c are placed. A guide gutter 132 is provided which is integrally formed with the guide gutter 132 and the guide gutter 132. In the middle of each machine in this guide gutter 132, a photoelectric out sensor 5NS consisting of a pair of light emitters and a light receiver is installed.
1, first safe sensor 5NS2, second safe sensor 5N
S3 is installed. In addition, the guide gutter 182 includes a merger section 132d that collects the balls that have flowed into each machine in one place, and the end of the merger section 132d has a gentle slope to align the pachinko balls in a line, as shown in FIG. It is connected to the upstream side of the inclined guide trough 133, thereby forming an enclosed ball circulation device 130. And guide gutter 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 ball @ 133 a disposed so as to face the guide gutter 133 is integrally formed, and the foul ball is merged with the ball flown down onto the guide gutter 133 via the guide @ 132 . Foul ball gutter 1
A foul sensor 5NS4 is disposed in the middle of 33a.

Then, a ball is placed opposite the lower end of the guide gutter 133.
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 at 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, its upper end face guides the ball feeder 133. 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 single ball extracting mechanism 138 is slid and the ball can be extracted.

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 board 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 passage hole 139 (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 having a push-up piece 141a that is rotated in conjunction with the firing rod 103a and pushes up the edge feed 135 upward is disposed below the base of the feeder 40.

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, a foul ball receiving port 134 is formed in the frame board 109 corresponding to the upper end of the firing rail 140 to guide the return ball into the guiding gutter 132 at the rear of the frame board, and an edge is formed along the lower side of the foul ball receiving port 134. The receiver is piece 14
4 is provided protrudingly.

A game board mounting portion 109a is provided at the upper end of the frame board 109, and game board positioning protrusions 145 are erected at both ends. Further, a frame engaging portion 146 having a groove in which the frame 106 for holding the game board can be engaged is formed along the upper end of the frame board 109, and as shown in FIG. By lowering the frame 106 from above along the positioning protrusion 145 and engaging the lower end with the groove of the frame engaging portion 146, the two can be coupled. On the side wall of the frame 106, there are four locking tools 106a that removably engage the game board.
The game board held by the frame 106 is placed on the mounting portion 109a of the frame board 109 and fixed by tightening the fasteners 147. 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 108 so that it can be opened and closed using one end (left end) as a fulcrum, and the firing rail 14 is mounted on the back side.
0 and is located above the launch rail frame 15.
1 is fixed thereto, and a cutout 151a is provided in the middle of this firing rail frame 151 so that the firing sensor 5NS5 can face inside the frame. Further, a lock lever 152 is provided on the back surface of the end of the front panel 105 opposite to the hinge. A glass frame 154 is attached above the front panel 105 within the front frame 108 so as to be openable and closable. On the other hand, on one side of the back side of the front frame 108 opposite to the hinge part 102, as shown in FIG. It is installed. Further, 155 is a lever for opening the glass frame 154.

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

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

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.

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

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

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

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

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

Furthermore, inside the storage frame 161, a card reader 800 is installed.
A unit controller 190 that controls the entire control unit 160, transmission means, monitor displays 174, 175 .
A unit control device W180 having a 176, a card reader control device 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.

Note that 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 118 in the control unit 160
0 is connected to the control device 195 of the pachinko machine 100 via a transmission line such as an optical fiber or a coaxial cable, and to the 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 161 so that data can be transmitted using any transmission path (see FIG. 20). reference).

18 to 20 show an example of an island facility on which a gaming machine consisting of the pachinko machine 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
A horizontal mounting table 23 is placed on a support 22 at a height of about 0°.
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 together with a machine frame 101 on the mounting table 23 between the pillars 22, and the control unit 160 is placed from the first installation table 24 onto the machine frame 101 which is on the same plane as the first installation table 24. . In addition, the second installation stand 2
A transmission path (not shown) constituting a local network is extended on the top of the support 5, and a transceiver 185 is installed between each support 22 to transmit data to and from the management device 400 via the transmission path. be placed. In addition, the transceiver μ
The front side of 185 is closed with an upper plate 27, and the lower side of the mounting table 22 is closed with 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 located on the top surface of the mounting table 23 at a position corresponding to each game machine, and a 100V power outlet 31 is located on the crosspiece 29 on the bottom surface of the top plate 26, corresponding to each game machine. Three of them are provided (see Fig. 20).

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

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

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

By using the optical fiber cable 191 for data communication between the unit control device 180 and the pachinko machine control device 195, the large number of wires that were conventionally arranged in a complicated manner on the back side of the pachinko machine can be cleaned up, and maintenance and Management is facilitated and malfunctions due to noise 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 accessory control device 158 are placed, as well as a purchase switch 113, an interruption switch 114, an end switch 115, and ball detection sensors 5NSI such as an out sensor.
The signal from the 5NS5 is waveform-shaped by the pachinko machine control device w195 and then supplied to the unit control device 180. In this embodiment, the power supply system is made up of two systems, AC24V and AClooV (7), and AC24V is supplied to the pachinko machine 100 side, and the control unit 160
AClooV is supplied to the side. Separating the power supply in this way prevents the pachinko machine control unit from being inadvertently destroyed due to the influence of the power supply in pachinko parlors where power supply problems often occur.

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

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

Regarding the processing of the detection signal from the sensor in this pachinko machine control device 195, the noise is simply removed from the detection signal, the signal is shaped into a constant pulse width, and then sent to the unit control device 180 as detection data for shooting balls, safe balls, etc. . In other words, calculations such as the number of safe balls are not performed on the pachinko machine control device 195 side, and such calculations are performed by the unit control device w18.
This is done on the 0 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 [1180].

The unit control device 180 includes a card reader control device i [188 and a pachinko machine control device!] to enable pachinko games using cards. 195, a data transmission controller 551 that controls data transmission with the management device 400, and establishes transmission/reception rights in the network and performs serial/parallel conversion of data under the control of the data transmission controller. It is composed of a network controller 553 and the like that perform the following operations.

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 memory 552 is divided into a transmission data storage area and a reception data storage area.
Adjustment function to make all sent and received data the same length (packetization) and faster data transmission (2.5Mbp)
It has a buffer function to measure s).

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

Further, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store a data reception result in response to a request from the data transmission controller 551, and a data transmission controller 551. A latch circuit 562 that stores commands such as data transmission commands to the network controller 553, a latch circuit 563 that stores low-layer network addresses, and three LED lamps that display abnormalities in the communication control state within the unit control device 180. A monitor display 55 consisting of
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 card 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 a latch circuit 574 that latches the display data (segment data and common data) of the amount and number of balls display via the data bus 581. A latch circuit 575 that latches a purchase lamp, a game status display lamp, a control signal for batted ball firing, and input signals from various switches provided in the pachinko machine 100 and control unit 160 are placed on the data bus 581 at a predetermined timing. an input/output controller 576 that latches an output signal to display a lamp;
A latch circuit 577 that latches audio data generated from the speaker 166 in the control unit 160 is connected.

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

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

As described above, the unit control device 180 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 1180 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 sent at intervals of, for example, 2 ms. Focusing on the periodic output, this is input to the reset circuit 555 as a watchdog pulse. Reset circuit 555
In addition to power-on reset, the device is configured to monitor this watchdog pulse and generate a reset signal when the pulse disappears.

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

Along with this, the unit controller 190 has an internal timer counter, and if AC)K (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 sent within a certain period of time (ex, 2 seconds) after receiving it, or when a disturbance in the internal memory (RAM) is detected.

By forcibly fixing the common signal to a low or high level, it is possible to reset the device itself. Note that the above-mentioned internal memory disturbance is caused by 1. For example, when initializing, a specific code (
A55A, etc.) can be written and checked by interrupt processing every 1 msec.

Furthermore, the unit controller 1180 of the embodiment also controls the unit controller 19 even when the data transmission controller 553 cannot transmit data within a certain period of time (5°12 seconds).
0 is initialized to prevent abnormal data from being sent to the management device 400. That is, in the embodiment, a watchdog counter area is provided in the unit memory 550, the data transmission controller 551 sets a predetermined code FF every time data is transmitted to the management device, and the unit controller 190 sets a predetermined code FF for 20 m s.
This counter is counted down by "1" each time. Therefore, if the data transmission controller continues to be unable to send data for 5.12 seconds or more, the watchdog counter in the unit memory 550 will become rOJ, so monitor this counter, and if it reaches rO, the data will be transmitted. It is possible to determine that the controller 551 is down and reset it by itself.

Moreover, in this embodiment, a special RAM is used as the unit memory 190 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 and raises the terminal INT, and the signal from that terminal is input to the unit controller 190 to synchronize the use of the unit memory between the controllers. Note that the specific terminal INT falls when the unit controller 190 reads data at the predetermined address.

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

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

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

The operating data etc. written to the unit memory 550 are
The data is sent to the management device through data communication between the transmission controller 551 and the management device 400 . Further, data sent from the management device @400 is also temporarily written to the reception data area RDA in the unit memory 550, and the unit controller 190 reads the data to receive the data. In the unit memory 550,
There is a communication area ccA that contains commands and status information to notify the other controller that other transmitted data and received data are in the memory, working areas UWA and DWA for each controller, and an area csA for synchronization between controllers. It is being

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

Pachinko machine table 1 Unit memory table 6 From Table 6 above, the actual state of the pachinko machine is: ■Free state is 0000000000000001■During game is oooooooooooooooi
.

■When receiving forced termination, 0000000000000
100 ■ At the time of interruption, 000000000
0001000 ■ When a stop occurs, 000000
It can be seen that it is expressed as 0000010000.

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

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

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

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

As shown in FIG. 26, inside the case body 801, a pace plate 804, which serves as a card transport path, is arranged. 806 can be installed.

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

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

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

On the other hand, a tenth-ra shaft 819 is rotatably disposed on the support substrate 806 disposed on the opposite side of the card insertion/ejection opening 802a, and a punch device 820 using a solenoid as a driving means and a magnetic head 821 can be installed. For mounting the magnetic head, a through hole 82 is formed in the support substrate 806 in accordance with the position so that the head surface can face downward when the magnetic head is inserted downward from above.
2 is formed. Further, a conveyance roller 823 is fixed to the center of the tenth-ra shaft 819, and both ends of the shaft can protrude outside from the side wall of the case, and pulleys 824 and 825 are respectively attached. A belt 826 is placed between the pulleys 818 and 825.
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 188 provided in the control unit 160 and passes read signals from sensors and magnetic heads 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 812 and 8
Auxiliary rollers 836 and 83 are biased upward by torsion springs 834 and 835 at positions corresponding to 23.
7 are openings 841 and 84 formed in the base plate.
It is attached so that the face is slightly exposed than 2. Also,
On the base plate 804, an auxiliary roller 83 is also biased upward by a torsion spring 836 at a position corresponding to a magnetic head 821 attached so as to face downward from a through hole 822 provided in a support substrate 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 bottom surface of the base plate 804 with screws, and on this second interface board 848 there is a circuit for interfacing with the card reader controller 188, as well as a light emitter. 816,828,829
and 831, first to fourth position detection sensors 5N81.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, which 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 cavity 851 so as to be vertically movable. In addition, an opening 853 is provided on the rear wall of the frame 852 constituting the empty space 851.
is formed, behind which the insertion detection switch 808 is arranged, and its movable contact 808a protrudes into the cavity 851 from the opening 853. The tip of this movable contact 808a is normally positioned above the shielding member 846 as shown in FIG.
When the card CD is inserted from point a, the card CD pushes up the shielding member 846 as shown in FIG.
is now turned on.

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

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

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

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

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

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

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

In addition, the relative distances between various sensors and punch pins are important for accurate processing such as card reading and punching, so each component must be installed with precision so that it has a predetermined positional relationship. There is.

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

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

Furthermore, 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 engraving diodes that make up the monitor display 176 include a power-on indicator LED II that lights up while the power is on, and a card-in indicator 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 card reader controller CPU2 operates according to the control program in the built-in ROM, and the unit control device 18
Based on the commands from 0, it executes card running control, card data reading, card data checking, etc., and transmits the card number and card reader control information to the unit control device.

Communication with the unit control unit [180 is via the built-in serial communication circuit, and the serial ports TX and RX
Do this using The output of control signals to the components constituting the card reader 800 and the input of detection signals from various sensors are performed by an interface circuit 198t! as shown in FIG.
- It is designed to be carried out through

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:
It is operated using the red clock b which is read from the top of track TR(?, 1 and triggers the flip-flop FFI) as a sampling clock.Flip-flop FF
I outputs a periodic signal C by being triggered by the read clock b and reset by the pulse e output from the CPU 2.

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

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

The read clock signal of the read data read by the two magnetic heads MHDI and MHD2 corresponding to the two tracks TRC1 and TRC2, respectively, is sent to the amplifier AM.
After being amplified by PI and AMP3, the rectifier circuit REC
I, rectified by REC2, and further waveform shaping circuit SMGI
, 5MG3 as a square wave to the card reader control device 188. On the other hand, the card reader control device 188
The write data and write clock supplied from the magnetizing current switching circuit M pass through the waveform shaping circuits 5MG2 and 5MG4.
Input to CCl, MCC2, write data P1”,
The direction of the head drive current is switched in accordance with the output of the magnetic head MHDI, which is amplified by amplifiers AMP2 and AMP4.
, 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 DRV 21 based on the forward rotation signal and reverse rotation signal given from the driver DRV 2 according to the speed switching signal.
1 to switch the voltage applied to the motor.

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

Among the signals in the figure, (A) to (D) are write data information, (
E) to (G) relate to write clock information, and (H)
- (J) show read data information, and (K) - (M) show signal waveforms of various parts related to read clock information. In addition, the card reader control group W1 of FIG. 31 is shown in (N) to (R) of the same figure.
At 88, the timing of each signal indicated by symbols a to e is shown.

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

In this embodiment, the write method is so-called NRZ, in which the polarity is inverted when the data is "1", and the previous state is maintained without inverting the polarity when the data is "0" or no signal.
The I method is adopted.

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 tt O'' to 111 P+.

On the other hand, when the data written in the above manner is read by the magnetic head MHD2, the output of the amplifier AMPI changes to + or - depending on the direction of magnetization when the magnetization state (D) changes, so the card reader controller C.P.
U2 outputs a signal a(N
) is high level, it is recognized as data It 1 tl, and if signal a is low level, data is tI O
II (see FIG. 33(S)).

In this example, the recording density of magnetic data on the card is 4.134 bit/mm (=105 BPI) and the card transport speed is 300 mm/sec, so the pulse period of the read clock data is about 806 μs. Therefore, when writing magnetic data by CPU'U2, 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.
, a bill dispensing device 230 for dispensing bills as change, and a unit control device 280 that performs data communication between various displays 221 to 225 and the overall control and management device 400 of the card issuing machine 200. has been done. 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 a switch corresponding to a desired purchase amount from the purchase selection switch group 212, a card corresponding to the desired purchase amount is issued to the issuing device 7.
It is issued from the card ejection port 202 of 0o. The purchase selection switch group 212 is composed of switches each with a built-in lamp, and when a banknote is inserted, there are switches that can be selected within the range of the inserted amount (3 for 3,000 yen, 3 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, the banknote dispensing device 230 for discharging the remaining amount stores one banknote. 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 display 223 that indicates whether or not bills can be accepted into the bill insertion slot 211, a card issue display 224 that indicates the issuing status of the cart, and a bill dispensing display 225 that indicates the status of the remaining balance. In addition, card issuing machine 2
On the inside of the front panel 201 of the 00, there is a monitor display 206 for displaying the type of abnormality (number) in the issuing machine as a two-digit number, and a reset button for resetting the display on the monitor display 206. 2o7 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 internally for this purpose, and the machine number set by this setting device 205 is sent to the management device 400 to generate a transmission address during data communication and to handle the generation of a transmission address for each issuing device. Used for creating data files.

On the other hand, the issuing device 700 takes out the blank cards stocked in the card tank 701 one by one and first sends them to the card reader 800. Record the card number, identification code (store code) 1, issue date code, check code, etc., and punch a hole at the issued punching position PH1 (see Figure 2) using the punch device 820 in the card reader 800. , printing device! At 750, the date of issue, serial number n, and purchase amount are printed and the card is ejected from the card issuing slot 202 provided on the front panel 201. The above issuing serial number 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.
The reception process sequentially determines the issuing serial number n, which is a number given to each card issuing machine, and the code obtained by performing code conversion processing such as rearranging the bits mentioned above based on this issuing serial number n. 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 serial number n.

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

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

The issuing device 700 of this embodiment includes a card ejecting device 710 for ejecting cards one by one from a card tank 701 containing a large number of cards whose magnetic recording section MG and print display section PRT are blank; 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 700 of this embodiment may have substantially the same structure and function as the card reader 800 for a pachinko machine.

The card reader for issuing machines is different from the card reader for pachinko machines. The points are that (1) it needs to have a magnetic data recording function, and (2) it needs to have a structure that allows the card to be ejected backwards. Among these, (1)
For the interface circuit 1 as shown in FIG.
98 is a waveform shaping circuit 5 that shapes the waveform of the write data signal.
MG2゜5MG4 and magnetic current switching circuit MCCl, MCC
2, and the magnetic heads MHDI and MHD2 can not only read magnetic data but also write magnetic data, so there is no problem. In addition, card reader 800 for pachinko machines
As mentioned in the explanation of the structure, Figures 25 to 2
In the card reader 800 shown in Figure 8, the rear wall of the case is open so that the inserted card can be ejected to the rear. Therefore, the issuing device 700 of this embodiment
The same card reader 800 for pachinko machines can be used.

On the other hand, the card 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 pressing member 702 is placed on top of the card stored in the card tank 701 to apply a certain pressure to the card to ensure removal of the card. Notches 702a are formed on the left and right sides of this pressing member 702 so as not to be detected by a sensor 703 that detects the presence or absence of a card in the tank. Further, the blank card CD stored in the card tank 701 is placed on the front half of the base substrate 711 of the card ejecting device 710 as shown in FIG.

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

Further, a support plate 715 is disposed approximately in the upper center of the base substrate 711 and is oriented perpendicularly thereto, 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 rotational force,
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 first conveying roller 712.
is being wound. Therefore, the rotational force of the take-out motor 719 is transmitted to the first conveyance roller 712 via the clutch mechanism (725, 726) only while the clutch solenoid 729 is energized.

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

In the issuing device 700 of this embodiment, when the purchase selection switch 212 is operated after 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 now possible to do so.

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

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

Note that a running position detection sensor CPSL 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 is written with an identification code, card number, etc. in the magnetic recording section by the card reader 800, and punched at the issuing hole punching position by the internal punching device 820. After the card is opened, it is delivered to the card reversing device 740 at the rear. 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 188 of the card reader 800 for a pachinko machine, is provided inside the card issuing control bag [790].

The card sent to the card reversing device 740 is first transferred to a belt 742 wound around transport rollers 741a, 741b, and 741c, and a transport roller 743a.

S is sandwiched between belt 744 wound around belt 743b.
The belt 74 is conveyed along a shaped traveling path and is wound around conveying rollers 746a, 746b, and 746C while pushing the traveling path switching piece 745 disposed at the exit thereof as shown by the broken line A.
7 and the belt 742, and is once sent upward. When the card passes the running path switching piece 745, the switching piece 745 is rotated back from the position indicated by the broken line A to the position indicated by the solid line by the tension of the spring 745a, and the running position sensor CPS2 disposed above moves the switching piece 745 back to the position indicated by the solid line. When the end is detected, the traveling motor 706 that drives the belt 742 is reversely rotated. This causes the cart to change direction and begin to be transported 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 a card derivation group [770
It is also wound around a pulley integrated with the transport roller 771, and the card is ejected by the driving force of the travel motor 706.

Furthermore, the rotation shaft 709 of the conveyance roller 748C is protruded to the side, and a knob 7 is provided at the end thereof as shown in FIG.
By turning this knob 709a by hand, the card can be manually moved while the travel motor 706 is stopped, and a jammed card can be removed. A running position sensor CPS3 is disposed at the end of the card reversing device 740, and when this sensor detects the rear end of the card, the running motor 7.6 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 travel path, and above them a print head 756 such as a thermal head is arranged so as to be movable up and down along a guide 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 this driven shaft 759, and rotational position sensors 761a and 761b are arranged opposite the periphery of this detection piece 760. Although not shown, the rotational force of the lifting motor 758 is transmitted to the print head 756 via, for example, a cam fixed to the driven shaft 759 and a tappet in contact with the outer periphery of the cam, thereby raising and lowering the print head 756. At this time, the lifting motor 758 rotates the driven shaft 759 by 18° 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 moves to the running position sensor CP.
It is lowered when the card is detected in S4, and when printing is completed, the lifting motor 758 is operated again to move the driven shaft 759 to 180 degrees.
'By rotating, the print head 756 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 front card delivery bag w770.

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

Furthermore, a travel path switching member 777 that is rotatable about a support shaft 776 is disposed between the conveyance rollers 773 and 774b. This running path switching member 777 has a spring 778.
Normally, the tip is positioned downward as shown by the broken line 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 card issuing port 202. Transfer field 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 781a.
is formed, and a sensor 782 is arranged so as to face this notch 781a. This sensor 782 is a light receiver, and the corresponding light emitter 783 is placed between the pair of belts 775 and set so that the detection optical axis is oblique, and detects cards entering the confiscation tank 780. Additionally, when the number of carts in the tank exceeds a certain level, the upper end of the card blocks the detection optical axis, making it possible to detect that the 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 on 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 cart passes and the running position sensor CPS6 or the confiscated card detection sensor changes from on to off, the running motor 706 is turned off and the ejecting or confiscating operation is stopped.

Note that an issuing device 700 is installed above the card issuing port 202.
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 unit, and on the front of this power supply box 794 there is a counter 795 for displaying the number of issued cards, and a counter 795 for displaying the number of confiscated cards, etc. There is a spare counter 796 available.

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

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

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

The control system of this embodiment is roughly divided into a control system based on the unit control device 280 and a control system based on the card issuing control device 790.
However, there is a means for accepting money, a means for selecting the desired purchase amount, a communication means for transmitting valuable data to the management device and receiving and receiving a card number in place of the valuable data, a means for dispensing change coins, and an issuance processing state. The card issuance control device 790 is in charge of controlling the status display means that indicates the above-mentioned card issue device 710, card reversing device 740, printing device W750, and card ejecting device 770 that constitute the above-mentioned issuing device 700, and the card checking device 790. It is also in charge of overall control of the control device 288 of the card reader 800, which is in charge of recording magnetic data. And the unit control device 28
Communication between 0 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 40o. There is.

In the card issuing machine 200 of this embodiment, a unit controller 280 lights up or blinks status display means including various indicators 221 to 225 provided on the front panel 201 in accordance with the card issuing procedure, so that the user can be guided through the operation procedure. In addition to teaching students about this, the system also prevents them from forgetting to eject cards or forgetting change.

That is, when the power of the card issuing machine 200 is turned on and the preparation for card issuing is completed, the unit control device 280
First, the 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 f280 causes the amount display 213 to display a number corresponding to the amount inserted, and also displays a purchase lamp LMP built in the purchase selection switch 212.
1 to LMP5 are lit up to the amount equivalent to the amount invested. In other words, for 1,000 yen, only lamp LMP1, and for 3,000 yen, lamp LM
If PI~LMP is 3,500 yen then lamp LMPl~LMP5
lights up to clearly indicate which switches can be operated.

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

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

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

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

Table 8 In the same figure, ◯ means lighting, × means lights off, Δ means blinking, D means numerical display according to the input amount, and B means lighting the lamp corresponding to the amount.

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

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

The unit control device 280 of the issuing machine includes a unit controller 290 that centrally controls the card reader control device 288 and the card issuance control device 79o, and a management device 40.
0, and a network controller 553 that establishes transmission/reception rights in the network and performs serial/parallel conversion of data under the control of the data transmission controller. has exactly the same configuration as the unit control device w180 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. 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. The data transmission controller 551 instructs the network controller 553 as to which page to use. Even if the data transmission controller 551 is processing received packet data, even if the next packet data is sent, it will be received by another page, so all packets can be reliably received.

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

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

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

Further, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store a data reception result in response to a request from the data transmission controller 551, and a latch circuit 561 for storing the data reception result by the network controller 553 in response to a request from the data transmission controller 551; A latch circuit 562 that stores commands such as a data transmission command to the network controller 553, and a latch circuit 563 that stores 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 280
A latch circuit 564 for storing display data to 56 is provided. 557 each of the above latch circuits 561 to 564
This decoder generates a selection signal by decoding the address given to the .

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 card 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 drive signals for placing input signals from the machine number setter 205 and the reset switch 207 on the data bus 581 at predetermined timings, and for displaying various lamps such as the issue empty 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.

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

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

On the other hand, from the unit controller 290 to the bill dispenser 23
The control signals for 0 include an instruction signal to set the number of banknotes to be paid out in binary code, an instruction signal to execute the payout of banknotes based on the set value of the number of banknotes, and a monitor display to display 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 one banknote is dispensed, and an alarm signal that is output when an abnormality occurs in the device during dispensing and the dispensing operation cannot be executed.
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 has been completed and the bills in the bill issuing slot have been removed. There is a signal to indicate that the

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

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

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

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

Furthermore, in the unit control device 280 of this embodiment, two of the display data output from the unit controller 290 to drive the amount display 213 are
A digit select signal (common signal) that is periodically output at intervals such as ms is input to the reset circuit 555 as a watchdog pulse. In addition to power-on reset, the reset circuit 555 monitors this watchdog pulse and generates a reset signal to each controller 290, 551, 553 when the pulse disappears.

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

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

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

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

The pot code shown on the cover 10 is stored in the unit memory 550 by the management device 400 when the system is started up.
For example, write a code such as 010101...01 in the transmission area of the controller, and periodically send it 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 1 shown on the clothing 10 is as shown in Table 1.
As shown in Figure 2, a bit indicates that a test is being executed when the system starts up, a bit indicates that the initial value is set/not set, a bit indicates a hot code error, and a bit indicates an abnormality in the local network (transmission cable 500) (low layer and high layer). It consists of a bit indicating a problem with the issuing machine, etc.

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

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

The payment machine 300 of this embodiment has a built-in card reader that reads the card number recorded on the magnetic recording section of the inserted card CD and checks the code. A card 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 350 that controls the entire payment machine 300.

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

A punch hole (accounting flow hole) is formed in the card, and then the card is discharged into the internal card collection tank 314.

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

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

At the same time, money corresponding to the unused amount is paid out from the balance payout device. The balance dispensing device includes a bill dispenser 321 that dispenses banknotes and a coin dispenser 325 that dispenses 100 yen coins. 32
A coin dispensing port 326 is provided corresponding to No. 5. In addition, during settlement, since a fraction of less than 1000 yen is generated as unused money, the coin dispensing device 325, which is comprised 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, which can be opened and closed, there is a 42nd
As shown in Figure (B), a monitor display 343 that displays an error in the payment machine such as a shortage of banknotes using an error number, and a reset switch 351 that resets the display on the monitor display 343 are installed at the game parlor. A machine number setter 352 is provided to distinguish between each of the plurality of payment machines so that the management device 400 can identify the payment machine that has made the payment for a particular card, and a machine number setter 352 is provided in the tank of the coin dispensing device 325 at the time of closing. Coin extraction switch 35 for ejecting remaining coins
3, and a print changeover switch 354 for giving an instruction as to whether history data is to be printed on the receipt issued by the printer 330.

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

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 a card collection tank 314 arranged behind the power supply unit W313 and the auxiliary transport device 311. It is composed of

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 316 fixed to a frame 315 of No. 10. In addition, two counters 31 are provided on the side of the frame 315.
7 and 318, one of which displays the number of collected cards. The other counter is unused.

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

Although not shown in FIG. 43, the card collection tank 3
14 indicates that the card has been ejected into the tank, or -
A card sensor 319 is provided to detect whether the cup 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 player is guided to the card and confiscated it, and in other cases, the card is ejected to the front after payment and returned to the player.

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

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

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

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

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

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

In addition, in the payment machine of the above embodiment, the card collection mode is set by setting the most significant digit of the machine number setting device 352 to "9", and in other cases, the cart after payment is ejected to the front. By checking the cart status at the time of checkout, if the amount used is rOJ and the entire purchase price is refunded, the software is configured to discharge the card to the collection tank 314 at the rear 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 33'
It is in charge of controlling O and accepting inputs from various switches 351 to 354, 305.
is in charge of overall control of the auxiliary conveyance device 311, the counter 317 as means for counting and displaying collected cards, and the control device 388 of the card reader 800 that checks cards and 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 coaxial cable via an optical transceiver 185 in order to send and receive data such as a card number to and from the management device 400. There is.

FIG. 47 shows the configuration of the unit control device 350 of the payment machine 300. 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 establishes transmission/reception rights in the network and performs serial/parallel conversion of data 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. The data transmission controller 551 instructs the network controller 553 as to which page to use. Even if the data transmission controller 551 is processing received packet data, even if the next packet data is sent, it will be received by another page, so all packets can be reliably received.

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

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

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

Further, between the data transmission controller 551 and the network controller 553, there is a latch circuit 561 for the network controller 553 to store a data reception result in response to a request from the data transmission controller 551, and a data transmission controller 551. A latch circuit 562 that stores commands such as data transmission commands to the network controller 553, a latch circuit 563 that stores low-layer network addresses, and three LED lamps that display abnormalities in the communication control state within the unit control device w350. A monitor display 55 consisting of
A latch circuit 564 is provided to store display data for 6. A decoder 557 decodes the addresses given to the upper latch circuits 561 to 564 and generates a selection signal.

On the other hand, the unit control device 350 of the payment machine differs from the unit control device w180 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. It is. 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,
Reset switch 351 of monitor display 343. an input/output controller 576 that places input signals from the coin extraction switch 353 and the print changeover switch 354 on the data bus 581 at a predetermined timing, and latches the drive signals of the payment in progress display 341 and the payment cancellation display 342; The input signals from the bill dispenser 321, the coin dispenser 325, and the printer 330 are placed on the data bus 581 at a predetermined timing, and the bill dispenser 321 and the coin dispenser 3
Control signals from the unit controller 390 to the banknote dispenser 321 include an instruction signal for setting the number of banknotes to be dispensed in binary code; There are an instruction signal for executing the payout of banknotes based on the set value of the number of bills, and an instruction signal for clearing the display on a monitor display (not shown) for displaying the result of the payout execution.

Also, from the bill dispenser 230 to the unit controller 39
The input signals for 0 include a signal that is output each time a bill is dispensed, an alarm signal that is output when an abnormality occurs in the device during dispensing and the dispensing operation cannot be executed, and a signal that is output when the dispensing operation cannot be executed. A signal indicating that the remaining amount is 20 or less, a signal indicating that the bill dispensing operation is in progress, and a signal indicating that the bill dispensing operation has ended and the bill has been removed from the bill issuing slot. There is a signal for this.

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

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

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

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

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

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

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

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

As described above, the unit control device 350 controls the management device 40
0. It has a window for information exchange in two directions of the card payment control device W312, and performs control for issuing cards under the control of the management device 400, and also performs payment processing that occurs 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-mentioned components, checking the card number, displaying the received card data, etc.
Collects operating data and sends it to the transmission data area SDA in the unit memory 550 consisting of dual port memory.
write to. The operating data written in the unit memory 550 is sent to the management device through data communication between the data transmission controller 551 and the management device 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 ODA that contains commands and 5 status information for informing the controller of the other party that transmission data and reception data are in the memory.

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

Table 15 As shown in Table 16, this embodiment also receives card history data, prints this on a receipt together with time data, and then outputs it, thereby informing the player 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 l shown on the clothing 15 is as shown in Table 1.
As shown in 7, a bit indicates that a test is being executed at system start-up, a bit indicates initial value setting/unsetting, 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 an error in the payment machine, etc.

Table 17 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 card reader, a bit indicating the state inside the card tank, and a bit indicating the coin in the coin dispenser. A bit indicating the presence or absence of a coin dispenser, a bit indicating an abnormality in the coin dispenser, a bit indicating the state inside the bill tank of the bill dispenser, a bit indicating an abnormality in the bill dispenser, etc.

Table 18 Next, the pachinko machine 1°O, the card issuing machine 200, and the payment machine 300 configured as described above are controlled in an integrated manner, and operating data is collected in real time to monitor the operating status of all terminals. Even if a power outage or breakdown occurs, the original data state is immediately restored upon recovery, allowing each part of the system to resume operation. It also enables the aggregation of data necessary for the management of an amusement arcade, and also allows for recovery in the event that a card is damaged. The management device 400 that issues reinstatement cards with the same qualification will be described.

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 device M-M consisting of U and semiconductor memory (RAM)
A master control device 401 in which EM, transmission control device SCC, etc. are stored, and a floppy disk storage device 4 as an auxiliary storage device provided above the master 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. 1 of these
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 400 includes a restoration card that has the same qualifications as the damaged card and a test card that can start up the pachinko machine while being disconnected from the system, as unique to the pachinko gaming system. A box 420 with a built-in auxiliary printer 408 that prints out emergency information generated in the system, such as the card issuing device 700 and "stoppage" generated in pachinko machines, in real time, and the auxiliary power supply device 409 are the master control device. 401.Card issuing device 70
0 and auxiliary printer 408 are each communication control device 40
It is connected to the central processing unit CPU via 6c and 406d. Further, the card issuing device 700 has exactly the same configuration as the card issuing device 700 for the issuing machine 200 shown in FIG. 36. 202 is the card issuing port.

The auxiliary power supply device 409 powers up the main storage device M-M when a power outage occurs.
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 stored in the EM in a volatile manner by transferring them to the hard disk storage device 403. Back up like this.

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

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

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

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

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 opening switch 421 is turned on, closing switch 422 is turned on. Cards can be used at each terminal until the end of the transaction. Further, 423 is a system termination switch for storing the operating data of all terminals in the floppy disk storage device 402 after business hours and instructing the management device to stop control, and 424 is for instructing restoration processing of a damaged card. It is a card resurrection switch.

In addition, the above-mentioned opening switch 421, closing switch 422,
The four switches, the system termination switch 423 and the card recovery switch 424, are particularly important switches for this system, and are provided behind them (at the top in the figure) to prevent them from being easily operated while the system is running. It is linked to the key switch 420, and if the key switch 420 is not turned on, each switch 420
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 these switches are turned on and 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 set to the midpoint of the buzzer sound, and is turned off when the stop switch 436 is pressed.

Additionally, the console 412 in this embodiment includes:

On the back side, there is a test card switch 437 for giving a test card issuing command, and setting values such as the exchange rate for purchase, store code, total number of terminals, and number of prize balls per winning ball when the system is installed. A built-in switch 438 is provided for instructing settings and changes to the set values. These switches 437 and 438, unlike other switches, are switches that are rarely used and only need to be known to a specific person (such as the manager of an amusement arcade), so they are placed on the back of the console. It is set in.

Here, the above test card will be mentioned.

As is clear from the configuration already explained, in the gaming system of this embodiment, all terminal machines (pachinko machine, card issuing machine, payment machine) are under the control of the management device, and can be operated by exchanging card numbers, etc. The terminal is now in a state where it cannot operate on its own. However,
Since pachinko machines are frequently used, balls often get jammed or accessories such as so-called tulips break down, and it is necessary to adjust the nails in the game area to adjust the ball payout rate. In that case, a 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 performed independently.

As a result, there is no need to start up the entire system during trial runs 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 card reader 800. However, instead of having a blank card inside, a method may be adopted in which a blank card is inserted from the outside, a code is recorded on the magnetic surface, and the card is ejected. In that case, card tank 70
1 can be omitted. Further, since the test card and the revival card issued by the management device 400 do not necessarily have to clearly indicate the date of use, serial number of issue, etc. like other general cards, the printing device 750 may be omitted. Note that when issuing a resurrection cart, a punching device 807 punches a hole at a predetermined punching position PH2 (resurrection hole) of the card.

As mentioned above, the terminals 100, 200.3 of this embodiment
00 are all 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 to give setting values to all terminals and initialize them. 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 memory M-MEM, files FLI to FL5, excluding the transmission address file FL6, are saved in the hard disk HDD (auxiliary) storage device 403 in the event of a power outage. In addition, data files related to terminal machines, that is, pachinko machine file (hereinafter referred to as P machine file) FL2, issuing machine file FL3, and payment machine file FL4, are stored in the floppy disk FDD (auxiliary storage device 402) as daily report files at the end of business hours. ,
Used for monthly operation data aggregation, etc.

Furthermore, the setting value file FL5 and the transmission address file FL6 are stored on the hard disk HHD at system startup.
The data is loaded into the main memory 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 unit CPU.
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 card number, etc. are stored here.

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

The setting value file FL5 in the same table is set according to the characteristics and configuration of the system, such as the exchange rate at the time of purchase, store code, number of terminals, number of prize balls, number of shots, etc., which 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 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.

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=1 to Y, in this embodiment, all pachinko machines in the game parlor are
The number of prize balls for each group can be set separately for the main and sub prize balls.

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

Furthermore, the number of stops and the stop mode are set in the table indicated by k. Here, the stop mode refers to the method (arithmetic formula) for calculating the number of balls to be played.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 played, or a mode in which 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 of two groups, as shown by =1 to Z.

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

In Table 21, the 1 type flag is a flag to indicate the type of terminal, where "1" indicates a pachinko machine, "2" indicates a card issuing machine, "4" indicates a payment machine, and "0" indicates a terminal. Each indicates the absence of . The NAU status indicates the state of the NAU, and as shown in Table 22, bit B4 is set to 1.
Bit B1 indicates that the token bus is abnormal, and bit B1 indicates that the store opening code packet has already been received. When &l I Jr is set,
Each indicates that the NAU is normal.

Table 21 Table 22 The unit number and serial number are the number of the terminal created by excluding "4" and "9" and its serial number, and the unit number is one NAU (network adapter unit) regardless of the type of terminal. The number of each terminal placed under the network is the number that becomes the address on the low-layer network (described later), and the channel number is the address of each terminal as seen from the management device, that is, the number that becomes the address on the high-level network (described later). It is. 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 "258" is written as r247J.

Table 23 If this is expressed in binary code using the binary coded octal system, it becomes "01o.100.111".

This code shows the decimal system r167J.

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 are taken, and this is regarded as the code rl O10.0111 expressed in binary coded octal notation, and this is converted into HEX.
When expressed as A, it becomes rA7HJ. Furthermore, one NA
In addition to pachinko machines, terminals such as issuing machines and payment machines are also connected under U, and in order to give them 8-bit unit numbers, the number of pachinko machines under one NAU is 64.
Limited to the above code rA7HJ and code r3FHJ
By performing a logical product with , r27HJ is obtained. In this embodiment, this is used as the unit number. Then, the NAU number is added to the beginning of this unit number to form an rNAU number, 10, 2, unit number, and 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, but NAU itself also creates an address file (unit table) for the units under its control based on input from the machine number setter when the system is started up. and is held in memory1
After the line test, the management device makes a unit table request to the NAU, compares it with the response data, and if it does not match, it is automatically changed (described later). Also, the transmission address file is set to the built-in switch 4 on the back of the console.
It can also be changed by 38.

In addition, consecutive serial numbers starting from "1" are given to each type of NAU, issuing machine, and payment machine as machine numbers.
For AUs and payment machines, their machine numbers are used as they are as addresses (unit numbers), and for 1-issue machines, the machine number plus r128J is used as the address (unit number) on the lower layer network. This is to avoid address duplication when a pachinko machine and an issuing machine with the same machine number coexist 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.

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

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

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

The card file FLI contains information for each card.

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

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

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

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

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

First, when a card is issued in the card issuing machine 200, the card is ejected and the card shifts from an unissued (blank) state SSo to a free state SS1. Then, when the card is inserted into a desired pachinko machine 100, the game state shifts to gaming state SS2. When the number of balls and the amount of money on the card become zero due to the game, the card is ejected and the state shifts to zero return state SS3. Also, during the game, the interrupt switch 11
When 5 is pressed, the card is ejected and the suspended state SS4
By re-inserting the same card, 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 card is ejected and the game shifts to the free state SSI.

If the CPU forcibly terminates the game or aborts, the card is also ejected and the game state moves from the game state SS2 to the free state S81. 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 card is transferred to fiSS5 with the payment completed status. In the system of this embodiment, it is also possible to take the card in the suspended state SS4 and go directly to the payment machine 300 and perform payment processing without returning to the pachinko machine, and in that case, it is possible to move from the suspended state SS4 to the completed payment state SS5. .

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

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

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

Table 26 Data marked with an O 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, Tables 27 and 28 show the issuing machine file FL3 and the payment machine file FL4, respectively. The data items shown in Table 27 are the data held in the sending data area of the issuing machine shown in Table 10, Further, the data items shown in Table 28 each match the data held in the transmission data area shown in Table 15. These are sampled by the management device once per second.

Umbrella total capacity 64 x 506 = 32384 = approximately 32 bytes * Total capacity 64 x 50 = 3200 = 3.2 bytes Umbrella total capacity 64 x lO = 640 = 0.64 bytes Table 26, Table 2
In 7, the data marked with a circle in the save column is
This data is saved on a floppy disk FDD at the end of business hours.

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

Furthermore, the operating information of the issuing machine and the operating information of the payment machine are 000.
0 0000 0000 0001 (7) 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 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 obtains the access right called has the right to send and receive data in the form of packets. 53
Connected to 0.

The plural +7) NAUs 530 that control each low-layer network (token bus) 510 are connected to the CSMA/CD
The management device 400 via the high-level network 520 of the system
It is connected to the.

The lower layer network 510 has a transmission rate of 2.5 Mbps (megabits per second), the higher layer network 520 is controlled to have a transmission rate of 10 Mbps, and the NAU 530 has a transmission rate of 2.5 Mbps (megabits per second). It acts as a buffer that absorbs speed differences and enables smooth data transmission, thereby reducing the burden on the management device 400 and making it possible to collect a large amount of operational data.

In FIG. 53, the symbol P indicates a pachinko machine as a terminal, the symbol H indicates a cart issuing machine, and the symbol S indicates a payment 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. 52, reference numeral U indicates a control unit of each terminal.

FIG. 54 shows the NAU that buffers data transmission between the low layer network 510 and the high layer network 520.
An example of the circuit configuration of (network adapter unit) 530 is shown.

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

The packet memories 534, 53.6 are constituted by dual port memories and have a transmission data area and a reception data area. In addition, the low layer network controller 533 and the low layer network (talks bus) 51
0, a branch circuit 531 that separates and combines the transmitted signal and the received signal, and a level conversion circuit 532 that converts the level of the transmitted and received data signal are connected. Similarly, a level conversion circuit 53 is provided between the high-rise network controller 537 and the high-rise network 520.
8 and a branch circuit 539 are connected.

Furthermore, the NAU 530 of this embodiment includes a NAU number setting device 561 for setting a number to distinguish between a plurality of NAUs connected to each other, and a terminal device existing on the low layer network 510 under the control of each NAU 530. Of these, a minimum device number setting device 562 for setting the minimum device number and a device number setting device 563 for setting the number of terminal devices existing on the low layer network are provided. Each setting device 561-5
63 settings are input to the data transmission controller 535 within the NAU 530 and the NAU number is used to form the transmission address for 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 the above hierarchical local network (FIG. 53), the management device 400 controls each NAU 53 at system start-up.
In addition to performing line tests and setting values for each terminal through NAU530 during system operation,
uses the low-layer network 510 to access terminals P and H once per second.

Collects operating data from S and stores it in its own memory. The accumulated data is sent to the high-rise network 520 once per second in response to a request from the management device 400.
The information is stored from each NAU 530 in a data file in the management device 400 through the NAU 530.

As described above, the communication network has a hierarchical configuration using the NAU 530 as a buffer, and the high-rise network 520
has a transmission speed that is four times the transmission speed of the low-layer network 510, which is 2.5 Mbps, so 100
Even in a system having ~1000 terminals, a large amount of operating data as shown in Tables 1, 10, and 15 can be collected from each terminal to the management device once per second.

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

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

Furthermore, the "Card In" to "Suspension End" packets listed in Table 29 are packets specific to the Pachinko machine 100, and among these packets, the "Card In" packet indicates that the card is in the control unit 160 of the Pachinko machine. when inserted,
This is a packet for requesting information (card text) regarding the card from the unit side to the management device [400].

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

On the other hand, the packet 'Suspension Ended' 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 packet is used by the management device to issue a command to cancel the suspended state of the pachinko machine.This allows the player to pay the bill without having to go back to the suspended pachinko machine and press the game end switch 115. be able to do it.

Further, the "1 card purchase" packet listed in Table 29 is a packet specific to the card issuing machine 200, and is generated when a bill is inserted into the bill insertion slot 211 of the issuing machine and the purchase selection switch 212 is turned on.

This is a packet for the unit control device 280 to request the management device 400 for the card number and issue serial number regarding the card.

In the system of this embodiment, the cart 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 ``0'' in the card amount field. When the packet is received, the management device 400 determines that it 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 with the issuance serial number and card number. The packet is returned to the card issuing machine.On the other hand, when a banknote is inserted, the card issuing machine sends a ``card purchase type packet'' to the management device with the actual purchase amount entered in the card amount field.Then, The management device looks at the card number column, determines that the card has been reserved for issue, searches the card file, writes data such as the purchase amount and issue time in the data area of the card, and sends an ACK packet to the issuing machine. It is designed to return to

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

In addition, the "Card Settlement Completed" packet is a packet to notify the management device 400 that the card settlement has been completed, and when the management device receives this packet, the card status of the card in the card file is changed to "Settled". ", and write the data at the time of payment in the i counter (i = m) column of the history data. In response to this "card payment completed" packet, the management device 400 sends an "ACK" packet to the payment machine 300. The card payment process is completed and the next card can be inserted into the payment machine.

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

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

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

FIG. 55(A) shows the basic configuration of packets transmitted and received between the management device 400 and the NAU 530 via the high-rise network 520, and FIG. Packets sent and received between (A
55 (excluding command packets that do not require CK) on the high-rise network 520;
) 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.

In other words, a packet in the format shown in FIG. 55(B) sent from the management device ff1400 to the unit is N
The AU 530 removes the high-layer packet head HHD and sends out onto the low-layer network 510, and the packets sent and received from each unit to the management device 400 using only the low-layer packet head LHD are sent to the LH in 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.

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

Figures 56 to 61 show the management device 400 and NAU in the data transmission system (local network).
Pachinko machine 100 via 530 or NAU530
, shows an example of a typical format of a packet transmitted and received between the card issuing machine 200 and the payment machine 300.

In the "line test" packet shown in Figure 56 (A), the transmission data field contains the date code, identification code (parlor code), and the number and minimum number of pachinko machines, issuing machines, and payment machines belonging to the destination NAU530. Please enter the machine number and send. Then,
The NAU 530 stores the date code and identification code, and compares it with the number calculated based on the settings of the single unit number setting switch 562, etc., and sends the information to the management device 400 as shown in FIG. 56(B). ACK packet is returned.

Furthermore, when the NAU 530 receives a "line test" packet from the management device, it sends a "line test" packet with only the low-layer network packet head LHD attached using the transmission address it calculated for all units under its control. form and send while updating the address. Then, an "ACK" containing a machine number, serial number, and channel number is received from each unit, and a unit table as a transmission address file is created and stored based on the received data.

FIG. 57(A) shows the structure of a "unit table request" packet sent from the management device 400 to the NAU 530, and FIG. 57(B) shows the structure of an "ACK" packet as a response thereto. When the NAU 530 receives a ``Unit Table Request'' packet, 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 an ``initial value setting'' packet sent from the management device 400 to the pachinko machine 100 and an ``ACK'' packet as a response thereto. In the data 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 and the date code are shown in the data column. The ID code and hot code are included and sent.

Furthermore, FIGS. 59(A) and 59(B) show the structure of a "periodic data request" packet and its response packet to a pachinko machine.

In the response packet to the regular data request shown in FIG. 59(B), the operation data of all the pachinko machines belonging to one NAU 530 are concatenated under the packet head LHD, and x1 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 in the file and send.

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

The packet type IIPACKET$TYPE in the same figure contains 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", "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" that are sent to the management device when a card is inserted into a pachinko machine. An example of the configuration of K'' is shown below.

Note that the packets shown in FIGS. 56 to 61 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 part that consists of 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.

Furthermore, the part "PADDIHG" added to the end of each packet in FIGS. 59 to 61 is a dummy data field added to adjust the length of the packet data to a predetermined length.

Next, the central processing unit CP is used when the management device 400 controls the entire system while communicating with the pachinko machine 100, the issuing machine 200, and the payment machine 300 using the various packets described above.
The control procedure of U and the local processing device 413 will be explained using FIGS. 62 to 103.

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

When the central processing unit CPU and the local processing unit 413 are reset by power-on, they initialize internal registers, internal memory, etc., and the central processing unit sets a file framework in the main memory IM-MEM. , the local processing device displays an initial screen (first and second lines only) as shown in FIG. 104 indicating that preparation is in progress (steps 51001 and 52001). Then, the local processing unit 413 reads the date and time from its own timer and sends it to the central processing unit CPU (step 510
02). The timer included in the local processing unit w413 is backed up by a battery, and does not stop even when the power is turned off, so it 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 M-MEM and transmits an ACK to the local processing unit. If the local processing device does not receive this ACK, it returns to step 51002 and transmits the date and time again.

After receiving the date and time and returning ACK, the central processing unit checks the power outage backup file in the hard disk HDD and checks whether the power outage flag in that file is set to "1" 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. 62(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 520O5 where the mode is set to preparation, and the setting value file FL5 is read from the hard disk HDD and stored in the main memory [M-MEM]. The address position is set (step 52006).

Then, the transmission address file FL6 created at the time of system installation is similarly loaded from the hard disk HDD to the main storage device 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). After that, the transmission address file F
Each issuing machine 200 and payment machine 3 that make up the system from L6
Read out the serial number 00 and create each issuing machine file FL3.
in the specified column of the payment machine file FL4, and write "0" in the other columns (steps 52009, 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), the process moves to step 52012.

In step 52012, after executing the random number generation process (see FIG. 103) 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 = ``preparing'''' to the local processing device 413 (steps 51004, 52013, 52014). , the local processing device receives this and displays the message MSGI indicating "line test in progress" on the screen of FIG. [
1413 is the line test request command hair central processing unit CP
Send to U (step 51006).

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

Then, upon receiving the response “ACK” packet from NAU530, the NAU in the transmission address file FLe
1" (NAU normal) is written in bit O of status 2 (step 52017). Then, it is determined whether transmission to all NAUs has been completed or not. Step 82018
), upon completion, the central processing unit forms a unit table request string packet and sends it to each NAU 530;
When receiving “ACK” packet from NAU, all NA
Determine whether there is a response from U (step 520
19-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.
The address in the transmission address file loaded from the hard disk HDD to the main storage M-MEM in step 7 is compared with the address in the transmission address file (step 52022). Then, it is determined whether or not there is a unit not registered in the file in the received unit table (step 52023), if not, it is left as is, and if there is an unregistered unit, step 52
At step 024, the unit is added to the transmission address file, and then the process proceeds to step 52025.

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

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

After that, the central processing unit CPU is transferred to the local processing unit 413.
The line test result is sent to (step 32028).

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

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

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

However, even when the terminal abnormality screen (Fig. 105) 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 51010, the process jumps to step 81006 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, when the central processing unit CPU receives the initial value setting request command from the local processing unit 413 (step 5
2029), 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). Then, when a response "A CK" packet is received, it is determined whether initial value settings for all units have been completed (step 5).
2031.52032). Once the initial value settings have been completed for all units, display data for a store opening request screen as shown in FIG. 106 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 51012, 5lO13). 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). Next, “ACK” from NAU
” is received, it is checked whether or not the packet transmission to all NAUs has been completed, and when it has been completed, the normal display screen data indicating that the business is open as shown in FIG. 113 is sent to the local processing device 413 to control the business operation. (Steps 52036 to 52038).Meanwhile, when the local processing device receives the above screen data, it displays it on the CRT display device 4.
11 and shift to operating control (Step 5)
105).

FIG. 62(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 mentioned above, when a power outage occurs, the management device 400 saves the card file FLI, pachinko machine file FL2, issuing machine file FL3, payment machine file FL4, and common data in the main storage device M-MEM to the hard disk HD.
D, and the power outage flag is set to "1" before the system goes down. Therefore, when the power is restored and the power is turned on, the initialization process shown in FIG. 62(A) is started, and when it reaches step 52004, it is determined that there is a power outage file and step 5 in FIG. 62(D) is started.
2041 Hejijump. In step 52041, the mode is set to "J" during power outage startup. On the other hand, when the local processing unit 413 displays the initial screen, transmits the date and time, and receives the ACK from the central processing unit, step 510
04 to inquire about the mode. At this time, the mode in the central processing unit is already set to "starting up from power outage", so when the mode inquiry is received,
The mode is “Respond J during power outage startup (step 5)”
2042, 52043), and when the local processing unit receives this mode, it determines whether it is "starting up a power outage" or not, and if yes, the fourth screen on the preparation screen in Figure 104 is displayed.
The message "System recovery in progress" is displayed on the second line (step 51021). Then, a timer is set, and when the timer times out and a certain period of time has passed (steps 51022, 51023, 5IO24),
Returning to step 51004, the mode inquiry is made again.

On the other hand, when the central processing unit [CPU responds with the mode,
Load the power outage file from the hard disk and restore the main memory [M-MEM common data area (steps 52044, 52045). While waiting for the timer, send a "unit recovery" packet to each unit, The operating data in the unit memory of the unit is restored to the state before the power outage (step 52046). Then, after receiving the "ACK" packet from each unit and completing the process for all units, "restart (type)" packets are sent to the NAU 530 one after another to restart the units for each type (step 52047). ~5204
9). Then, “ACK” from each NAU530
is received and completed for all NAUs, the mode of the central processing unit is changed to "open for business" and data on the normal display screen (FIG. 113) indicating "open for business" is transmitted (steps S2050-52053). At this point, the timer that the local processing unit 413 set in step 51023 times out, and the process returns to step 51004 to inquire about the mode. Since "business" is returned as the mode, it is determined as NO in step 51021. Then, the process jumps to step 51025, and the normal display screen sent from the central processing unit is displayed on the CRT display device 4.
11 and then transitions to control during business hours.

FIG. 63 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. 62(C) of the initialization flow described above
The store opening request screen (Fig. 106) 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 413 sends an initial setting value request command to the central processing unit CPU (step 51031).Then, the central processing unit transmits the contents of the setting value file loaded from the hard disk. It is sent to the local processing device 413 (step 8.2061). In response to this, the local processing device displays a setting value change screen as shown in FIG. 107 on the screen of the CRT display device 411 (step S1032).

Here, the operator inputs a new setting value for the purchase rate or identification code using the numeric keypad 425 on the console according to the instructions on the screen.

The local processing device stores the updated value in its internal memory, and then displays the next setting value change screen (see FIG. 108) (step 51033). 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. 109) (step 51034). Also.

At this time, if the return key 426 is suddenly pressed without inputting the set value, the screen moves to the next change screen without updating the set value.

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

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

When waiting for switch input in step 51013 of the initialization flow in FIG. 62, the setting update switch 432
When turned on, the local processing unit 413 sends a setting value change request command to the central processing units C and PU (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 52071). In response to this, the local processing device displays the 11th
Display the setting value change screen as shown in Figure 0 (step 51).
042).

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 111) (step 5).
1043).

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

When the central processing unit receives this command, it first updates the setting value file in the main memory M-MEM, then updates the pachinko machine file, and then updates all "initial value setting" packets containing the updated setting values. Send to unit (step 5)
2072 to 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. A change screen (see FIG. 112) is displayed (step 51045). Then, when the operator follows the instructions on this screen and enters the date and time using the numeric keypad 425,
The local processing device sends the updated date and time to the central processing device (step 81046). 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 sends the updated year, month, and day data to all units (other settings remain as they were) to initial values. "setting" packet is transmitted (steps 52075, 52076).

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

When the central processing unit CPU receives an interrupt every second from the timer, it starts this periodic data request processing and first checks whether the operation mode is "in business" or not in step 52.
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
is returned, and if there is an ACK, the process moves to scheduled data reception processing 52121 to 52135 in FIG. 66 (step S2105). 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 NAU530
If a time-over occurs before receiving the response ACK from the main memory [
Among the error counters provided for each NAU in the common data area CDA of M-MEM, N
After incrementing the error counter corresponding to the AU, it is determined in step 82108 whether the error counter has become 3 or more, that is, whether an error has occurred three times in a row.If it is 2 or less, the process returns to step 52103 and repeats the process again. - Send a "periodic data request" packet to the NAU. Then, a timeout occurs again before receiving A(, K, and if this is repeated three times, step 52
Proceeding from 108 to 52109, here, among the NAU status prepared for each NAU in the transmission address file, bit O (NORMAL) of the status information corresponding to the NAU without ACK is set to "O" L: IJ7,
An interrupt display command is sent to the local processing device 413 to display an interrupt message informing that the NAU is down on the screen of the CRT display device 411, and the printer 40
8 is given a command to print out the same content.

In addition, the local processing device outputs a buzzer 440 after displaying the interrupt.
(Steps 52110, 51051, 51
052).

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 (steps 32 and 11).
2) If L or No, end the interrupt processing; if Yes, clear bit O of all NAU statuses to it Ot+, then set bit 7 (CHIEPA) of monitor information in files FL2 to FL4 of all units to tz 1 +
Set to 1 to memorize that the high-level network is abnormal (steps 52113 and 521).
14).

FIG. 66 shows N as a response to the above regular data request.
The processing procedure when an "80K" packet containing fixed time data is received from the AU 530 is shown.

When regular data is received, the central processing unit CPU first checks the monitor information for each unit at the beginning of the data field of the received packet (step 52121), and if there is no abnormality, jumps to step 82128, and if there is an abnormality. If so, the process advances to the next step 52123, and it is determined whether the abnormality is the same as the previous abnormality (step 52122). Here, if the detected abnormality is the same as the previous time, step 821
28, and if it is a different abnormality, the new abnormality is printed by the printer 408 in step 52124. Then, unit abnormality 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 first checks the hot code at the end of the received scheduled data (step 52126). Here, if there is no hot code error, step 32128
If there is an error, the error recovery processing task (see FIG. 83) is notified of the abnormality of the unit in step 52127, and the process moves to step 52128, where the monitor information 2 in the regular data is inspected. And monitor information 2
If there is an abnormality, perform steps 52122 to 521 above.
The abnormality is displayed on the printer and CRT display device using the same procedure as in step 25 (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 steps 52121 to 52133 have been completed for all units in the received packet, and if not, the process returns to step 52121 (step 5
2134), and if all units are finished,
In the next step 52135, it is determined whether or not "ACK" packets of scheduled data from all NAUs 530 have been processed, and if no, the process returns to step 52121 and all "ACK" packets have been processed.
Steps 52121-521 until finished for K”
Repeat step 34.

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

When the central processing unit receives the “Card Purchase” packet,
Extract the card number from the data field in the packet and determine whether the number is "0" (steps 52141, 52
142). In the system of this embodiment, before the issuing machine 200 actually issues a cart, the issuing machine itself may send a "card purchase" packet with the card number set to "0" to reserve a card. , 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 rOJ, that is, a purchase packet for issuance 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 "
0'' (step 82146). the result,
If the amount≠0, jump to step 52149 and set the amount to 0.
If so, in the next step 52147, the reservation flag is read from the issuer file and it is checked whether it is "1", that is, reserved (step 82148). Here, if the reservation flag is not "1", step 521
At step 49, the cart issue serial number in the packet and the number of issues in the file are incremented. Step 3214 above
6, when the amount is not "O", the reservation flag is not checked and the card issuing serial number is incremented by jumping to step 52149.The reason why 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 cart, it is sucked up by regular data collection and the number of issuances in the issuing machine file is updated). , the card issuing serial number is used to search the cart file, the file for the card is cleared, and the cart number is calculated from the card issuing serial number (step 524).
50.52151). Then, in step 52152, the calculated value is written in the card number column in the card file, the value in the received packet is written in the number of balls and amount column, the card status is set to "free", and the 1 counter is set to "1". ” and write the received data and current time in the history data of i = 1, then step 52
In step 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 + 1 in the file do not match, the process moves to step 52154 and the issuance acceptance number and the issuance acceptance number are compared. Compare the number of issues and if they match, step S
Step 2155 calculates the card number from the card issued serial number, the next step 82156 searches the card file using the card issued serial number and reads the corresponding file, and then moves to step 52152 described above to update the card file. After that, it transmits an "ACK" packet (step 52153). For example, when a “card purchase” packet is received for issuance reservation, step 5214
This takes into consideration the case where the ``ACK'' packet transmitted by executing steps 1 to 52153 does not reach the issuing machine within a predetermined time and the same ``Card Purchase'' packet is sent from the issuing machine.

On the other hand, if the card number in the "card purchase" packet received in step 52142 is not "O", that is, if there is a genuine purchase application for a reserved card, step 52157 is hejumped and the packet is Compare the issuance acceptance number and the number of card issuances in the issuing machine file plus "1", and if they match, search the card file using the received card issuing serial number and read the corresponding file ( Step 82158)
The process moves 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, “
ACK” packet.

If it is determined in step 52142 that the card number is not O, and then 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 the process jumps to step 52159. , sends a NAK.

FIG. 68 shows the processing procedure of the central processing unit CPU when receiving a "card-in" packet sent to the management device 400 when a card is inserted into the control unit 160 of the pachinko machine 100. Upon receiving the "Card-in" packet, the central processing unit first calculates the card issuing serial number backward from the card number in the packet (step 82161), then searches 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 52165, and the card status of the card in the file is changed to "free". Check if it is. Here, if the cart status is "free", the cart 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.
A CK” packet is sent to the pachinko machine 100, and the card number in the received packet is written in the card number field in the pachinko machine file, and the process ends (step 5).
2167.52168).

Note that if the card number in the packet and the card number in the file are compared in step 32164 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 packet is not "playing". ”, and if the card status is not “playing”, it is determined that an inappropriate card has been inserted, and the process proceeds to step 52174, where it jumps and transmits a “N A K” packet. By comparing the card number in the packet with the card number in the file in this way, counterfeit cards can be eliminated. Also, if the inserted card is the one that was interrupted at another pachinko machine, step 52165,
52171, both are determined as NO, and step 521
74 hejump and send "N A K".

When it is determined in step 52165 that the card status is not "free" and it is determined in step 52171 that it is "playing", the process moves to step 52172 and the P machine number in the received packet matches the machine number in the card file. The reason for returning "ACK" when doing so is to deal with the fact that after the power is restored, the pachinko machine will reread the card and if there is a cart, it will send two "Card In" packets. .

FIG. 69 shows a central processing bag [CPU processing Show the steps.

Upon receiving the "suspended cart-in" packet, the central processing unit first calculates back the card issuing serial number from the card number in the packet (step 82181). Next, the card file is searched using the calculated card issuing serial number and the file of the corresponding card is read (step 821).
82). Then, extract the card number from the loaded card file and compare it with the card number in the received packet (steps 52183, 52184). If they match, proceed to step 32185 and check if the card status of the card in the file is "suspended". Find out whether or not. Here, if the card status is "suspended", update the card text in the card file, rewrite the card status to "playing",
Also, after writing the data and time at the time of interruption in the i-th column of history data, the i counter is decremented (steps 52186, 52187). When an interruption occurs, the data and time at the time of interruption are temporarily recorded in the history column indicated by one counter in the card file, but when the interruption is canceled, the j counter is decremented and the same column is recorded when writing the next history data. By overwriting the history data field, 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 setting the j counter to "-1" in step 52187, the process advances to step 52188 and sends an "A CK" packet containing the card text read from the card file to the relevant pachinko machine. do.

Note that if the card number in the packet and the card number in the file are compared in step 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. It is determined whether or not the card is "playing", and if it is not "playing", it is determined that an inappropriate card has been inserted, and the process jumps to step 52193 and transmits a "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 card file are When the two match, the process moves to step 82187, 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 an "ACK", but the pachinko machine cannot receive it and sends the "interrupt card-in" packet again.

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

FIG. 70 shows that when the interrupt switch provided on the pachinko machine 100 is turned on during a game, the management device 4
2 shows the processing procedure of the central processing unit CPU when receiving the "interrupt switch" packet sent to 00.

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 (step 52201.5).
2202).

Next, the card status of the card data read from the card file is checked to determine whether or not it is "playing" (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 card file (card number, number of balls, amount, card status, The location terminal serial number and location terminal number) are rewritten into data in the packet (step 52205). Then, check whether the i counter in the corresponding card file is less than 19 or not in step 5.
2206), if it is less than 19, increment the i counter in step 52207, write the machine number, number of balls, amount, and current time of the timer in the packet in the next history data field, and then write the card text in the "ACK" packet. is sent to the pachinko machine (step 52208.
52209). If it is determined in step 32206 that the i counter is 19, the i counter is not updated, but jumps to step 32208, and the data in the packet is written in the 19th 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
Then, it is determined whether the card status is "suspended" or not.

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

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

This takes into consideration the case where the same ``Suspend Switch'' packet is sent again after sending ``ACK'' in Step 52209. Note that even if the card status is ``Suspended'' in Step 52211, the machine number is If they do not match, a 'NAK' packet is sent (step 5221).
2-52214).

FIG. 71 shows that when the end switch provided on the pachinko machine 100 is turned on during a game, the management device 4
The processing procedure of the central processing unit CPU when receiving the "termination switch" packet sent to 00 is shown.

The processing procedure when this packet is received is the processing procedure when the "interrupt switch" packet is received in Figure 70 (
Steps 52201 to 52214) are almost the same.

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

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

FIG. 72 shows the return to zero (
The processing procedure of the central processing unit CPU when receiving a "return to zero" packet transmitted from the pachinko machine to the management device 400 when a state in which the number of balls held and the unused amount are both zero is generated is shown.

The processing procedure when this packet is received is the processing procedure when the "interrupt switch" packet is received in Fig. 70 (
Steps 52201 to 52214) are almost the same.

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. 73 shows the processing procedure of the central processing unit CPU when receiving a "return to zero" packet transmitted from the pachinko machine 100 to the management device 400 when a stop state occurs during a game in the pachinko machine 100.

Steps 52261 to 52268 in the processing procedure when this packet is received are steps 52201 to 52208 in the processing flow of FIG.
Steps 52275 to 52278 in FIG. 3 are steps S, 2211 to 52214 in the processing flow in FIG.
and Roma-.

The difference is that "discontinued" is written as the card status when updating the cart file in step 52265.
The point is that in step 52275, it is determined whether the card status is "free" or "discontinued" rather than whether it is "suspended."

Furthermore, in this packet reception process, immediately after writing the data and time in the received packet to the history data column of the card file in step 52268,
ACK” packet instead of sending the 73rd
As shown in the figure, the machine number in the received packet is also used to
After searching the machine file and rewriting the operation information in the data of the corresponding pachinko machine to "stop", send an interrupt command containing the stop interrupt display screen data to the local processing unit w413, and also send it to the printer 408. After printing out the fact that a stop has occurred together with the machine number, an "ACK" packet is sent to the pachinko machine (steps 52269 to 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 (steps 51061~
51063).

FIG. 74 shows a "Card Settlement" packet sent to the management device 400 when a card is inserted into the Settlement Machine 300, and a packet sent after the Settlement Machine executes card settlement based on the "ACK". The processing procedure of the central processing unit CPTJ when receiving the "Payment Completed" packet is shown.

When the central processing unit receives a "Pacard payment" packet, the central processing unit first calculates the card issuing serial number backward from the card number in the packet, searches the cart file using the card issuing serial number, reads the data of the card, and checks the card status. Determine if is "free" or "suspended" (
Steps 52281-S2283). Here, if the card status is "free j" or "suspended", in step 82284, the current time of the timer is set as the payment reception time, and the card number, number of balls held, and amount of money 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, if the card status read from the card file is neither "free" nor "interrupted", the process moves from step 52283 to step 52285, and a "NAK" packet is transmitted. The payment machine 300 uses the above “ACK”
Upon receiving the packet, it issues a receipt with the payment data in the packet printed, refunds any unused money, and then sends a ``Payment Completed'' packet.

When the management device 400 receives this “payment completion” 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. The data is read and it is determined whether the card status is "suspended" (steps 52291 to 52293). Here, if the card status is "suspended", a "suspension completed" packet is sent to the pachinko machine corresponding to the card location terminal number read from the card file in step 52274,
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.
Proceed to ``20'' and set the i counter in the card file to ``20''.
Update (or increment) to . Then, change the card status in the card file to "settled", write the settlement data in the i-th (=20) of the history data column, and send an "ACK" packet to the settlement machine 300 (step 82295.S2296).

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

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 the P machine files from the main storage M-MEM, checks whether the operation information is "discontinued", and if it is "discontinued", displays the discontinued status. Among the machine numbers and operation data of the pachinko machines located in
-52303).

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

On the other hand, after transmitting the operation data of the stopping machine, the central processing unit determines in step 52305 whether or not it has finished checking the operation information in the P machine file 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 52304). Then, the local processing device
On the 16th and 17th lines of the stop-stop release display screen in FIG. 14, a message prompting the operator to input the machine number for which stop-stop cancellation is to be performed is displayed (step 51073).

The operator sees this message and presses the numeric keypad 425 to enter the machine number of the pachinko machine or "○J (rO
If J is input, all machines are specified), the local processing device sends a cancellation cancellation request command (step 51074). When the central processing unit receives the command, it determines whether or not to cancel the suspension of all pachinko machines that have been suspended (steps 52306, 52307).
.

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

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

FIG. 76 shows the processing procedure in the central processing unit and local processing unit when turning on the forced termination switch 434 provided on the console 412 to forcefully terminate the pachinko machine.

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 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. 115 shows the forced termination screen of the pachinko machine. In addition, on the issuing machine forced termination screen and the payment machine forced termination screen, the characters "Pachinko machine" displayed on the fifth line of the Pachinko machine forced termination screen in Figure 115 are changed to "Issuing machine" or "Pachinko machine" respectively. It will simply change to a "payment machine".

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

When the central processing unit receives a pachinko machine forced termination request command from the local processing unit, it determines whether all pachinko machines are specified, and if yes, reads the P machine files in order, and the operation information in the file indicates that the game is in progress or has been interrupted. It is checked whether it is inside or not (steps S2341 to S52343). 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). Then, the number of balls in the file,
Enter the data read from the P machine file in the amount column,
After changing the card status to "free" (step 523)
46), it is determined whether or not the process has been completed for all units (step 52347); if no, the process returns to step 52342 and the above procedure is repeated.

After checking the operating information and updating the card files for all machines, the process moves to step 52348 and sends a "forced termination request (type)" packet to all NAUs, and then receives a response from the NAU. If so, send the result to the local processing device (step 52348
~S 2350). Then, when the operator looks at the display menu selection screen in FIG. 121 and selects the specific machine display, the local processing device displays the specific machine display screen in FIG. 123 or the first
When the all-machine display screen in Figure 24 is displayed, the characters “1+” are displayed in the last column of the corresponding pachinko machine to indicate that it is being forcibly terminated (steps 51085 and 510).
86).

On the other hand, if it is determined in step 52341 that all the machines are not designated, a "Pachinko forced termination request (individual)" packet is sent to the designated pachinko machine (step 52351). Then, "ACK" is returned from that pachinko machine. If the ACK is not returned, the process jumps to step 52350. If the ACK is returned, the data of the pachinko machine in question is read from the P machine file, and the operation information is "playing" or "interrupted."During"
Check if it is, and if yes, follow the procedure 52344 above.
After updating the cart file according to the same procedure as steps 52346 to 52346, proceed to step 52350 and send the forced termination result to the local processing device (steps 52353 to 52353).
52357).

FIG. 77 shows the processing procedure in the central processing unit and the local processing unit when turning on the forced termination switch 434 provided on the console 412 to forcefully terminate the issuing machine.

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 the Pachinko machine 1 issuing machine and payment machine, 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 issuing machine forced termination screen, the characters "Pachinko machine" displayed on the fifth line of the Pachinko machine forced termination screen in FIG. 115 are changed to "Issuing machine".

While looking at this screen, use the console's numeric keypad 425 to enter the machine number or "○" (to specify all machines) of the issuing machine that you want to forcefully terminate, and the local processing unit will send a issuing machine forced termination request command to the central processing unit. The display is changed from 51083 to 51084 to a normal display screen (FIG. 113) 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 121 and selects the issuing machine data display screen to display the issuing machine data display screen in Figure 126, the local processing device displays the information in the last column of the corresponding issuing machine. , displays the character "strong" indicating that it is being forcibly terminated (step 51095,
51096).

On the other hand, if it is determined in step 52341 that all machines are not specified, a "forced termination request (individual)" is sent to the specified issuing machine.
Send the packet (step 82365). Then, it is determined whether or not "ACK" has been returned from the issuing machine (step 52366). If not, the process jumps to step 52364, and when the ACK has been returned, the operation in the file of the issuing machine is checked in step 82367. After the information is changed to forced termination, the process moves to step 82360 and the forced termination result is sent to the local processing device.

FIG. 78 shows the processing procedure in the central processing unit and local processing unit when turning on the forced termination switch 434 provided on the console 412 to forcefully terminate the payment machine.

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 51101). 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 payment machine corresponding to the specified terminal type. A screen is displayed (step 51102). The subsequent procedure is the same as in the case of forced termination of the issuing machine in FIG. 77.

FIG. 79 shows the processing procedure of the central processing unit and the local processing unit when canceling the forced termination state of the pachinko machine that has been forcibly terminated by the process of FIG. 76.

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

When the central processing unit receives this command, it reads the pachinko machine files in order, checks whether the operation information is "forced termination", and if it is forced termination, it 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 52383). 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. 116 (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), and if no, step 8238).
1, and if the answer is YES, the process moves to the next step 52385, and a display data end command is sent to the local processing device. Then, the local processing device displays a forced termination cancellation message on lines 17 and 18 of the screen shown in FIG. 116, prompting the user to input the machine number for which the forced termination is to be canceled (step 51114). When the operator inputs the machine number or "0" to designate all machines using the numeric keypad 425 while looking at this screen, a pachinko machine forced termination cancellation request command is sent to the central processing unit (step 51115).

When the central processing unit receives this command, it determines whether or not all units are specified, and if all units are specified, it sends a ``Parcel forced termination release (type)'' packet to all NAUs 530, and then
Receive the response (A'CK or NAK) from tJ and send the result to the local processing device (step 52386
~52389).

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

Then, it is determined whether or not "ACK" has been received (step 52392), and if yes, step 52393).
"Free" the operation information in the file of the relevant pachinko machine.
If it is No again, go to step 323.
89 and sends the result to the local processing unit. When the local processing unit receives a message from the central processing unit that the forced termination has been successfully canceled, the local processing unit changes the status display in the last column of the display data line of the pachinko machine from ``strong'' to ``empty'' indicating free. (Step 81116).

Figure 80 shows the case where the forced termination state of the issuing machine that was forcibly terminated by the process of Figure 77 is canceled, and Figure 81 shows the forced termination status of the payment machine that was forcibly terminated by the process of Figure 78. The processing procedure of the central processing unit and local processing unit when canceling is shown.

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

On the other hand, in the process shown in FIG. 81, 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 to the CRT display device as shown in FIG. 118. Display the screen for canceling forced termination of the payment machine as shown in .

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

FIG. 82 shows the processing procedure of the central processing unit CPL' 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 operation mode is "open" or "closed" (steps 52441, 52442)+ If the operation mode of the central processing unit 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", after stopping the collection of regular data from each unit and changing the mode to "Under power outage countermeasures",
Sends a message to the local processing device that power outage measures are in progress (
Steps 52443-52445). Then, the local processing device displays a power outage message on the CRT display device (step 5l141). 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 cart number in the P machine file and uses that to search the card file. and rewrites the card status to "free" (steps 52446 to 52450). After that, the operation information in the P machine file is rewritten to "free", and it is determined whether all pachinko machines are finished. If yes, the data in the common data area (including the setting value file and power outage flag)
Then, the two card files, the issuing machine file, and the payment machine file are saved on the hard disk HDD, and the mode is changed to "closed" before the system goes down (steps 52450 to 52458).

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

FIG. 83 shows a procedure for error recovery processing of the system by the central processing unit WCPU.

When the central processing unit receives an interrupt every 30 seconds from the internal timer, it starts the error recovery process shown in FIG.
．． 1) If the business is not open, do nothing; if the business is open, proceed to step 32462, read the NAU status from the transmission address file, and set the bit N○RMAL, which indicates whether the NAU is normal or abnormal, to II O'' (=abnormal). Determine whether or not (steps 52462, 52463)
.

Note that the NORMAL bit of the NAU status is
Steps 52016 and 5201 in the initialization flow in Figure 2
If there is a response to the "line test" packet in step 7, it will be set to 01++ (= normal), so NA without a response
The NORMAL focus of U remains at LL O”.

If the NORMAL bit is determined to be 11 Q II, the NAU recovery processing step 5247 in FIG. 84(A) is performed.
Execute 1 to 52475. On the other hand, if the NORMAL bit of the NAU status is LL I II, step 52
Proceed to step 464, read monitor information 1 in the unit file, and check whether the bit indicating token bus abnormality is 1". If LL I II, read out the monitor information 1 in the unit file and check whether the bit indicating token bus abnormality is 1".
B) Token bus recovery processing steps 52481-52
Execute 486, and if re O", next step 5246
At step 6, it is checked whether the bit indicating a hot code error in monitor information 1 is 1'', and if it is '1', hot code recovery processing 52491 to 52498 in FIG. 85 is executed.

On the other hand, if it is determined in step 52466 that there is no hot code error (no hot code error), the process advances to step 82467, where the unit abnormality bit in monitor information 1 is It1.
If it is 1'', unit recovery processing 52501 to 52509 in FIG. 86 is executed.

In the NAU recovery process shown in FIG. 84(A), first the NAU
Send a ``line monitor check'' packet to a NAU whose status NORMAL bit is 110'', set its timer, and if a response ``ACK'' is received before the timeout, the NAU status will be set to NORMAL. Change the bit to It I P+, then send an interrupt display command to the local processing unit and CR
Display a message on the T display screen informing that the NAU has recovered, print out the same message on the printer 408, and send "ACK" within a certain period of time.
If it does not return, the routine returns to the original routine without doing anything (steps 52471 to 52474).

In the token bus recovery process shown in FIG. 84(B), first, a "unit monitor check" packet is sent to the unit whose token bus error bit is 1", and a timer is set (steps 52481, 52482).
). Then respond before the timeout occurs” A
Step 52483,
52484), when "A CK" is received within the time, clear the token bus error bit of monitor information 1 in the relevant unit file to 0" and then send it to the relevant unit"
A “restart” packet is sent to restart the device (steps 52485 and 52486).

In the hot code recovery process shown in FIG. 85, first, a "unit recovery data" packet is sent to the unit in which the hot code error occurred, and a timer is set (steps 52491, 52492).

Then, before the time is over” A CK
” is received, compare the hot code placed in the “Unit Recovery Data” packet with the hot code sent back in the “A CK” packet (Suite 5
2493″-82495), and when the bot codes do not match, the process moves to step 32498 and sets tt 1 P+ to the hot code error bit of monitor information 1 in the unit file, and when the hot codes match, the corresponding After sending a “restart” packet to the unit, clear the hot code error bit of monitor information 1 of the unit (steps 52496, 52
497).

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

In the unit recovery process shown in FIG. 86, first, a "unit monitor check" packet is sent to the unit with the unit abnormality and a timer is set (step 5250).
1,52502), if "ACK" is received before a time-over occurs, a 1' unit recovery data" packet is transmitted and the timer is set again (steps 52503 to 52506). If "ACK" is returned within a predetermined time, a "restart" packet is sent to the unit to restart the unit (step 5).
2507-52509).

FIG. 87 shows the central processing unit C when the closing switch 422 and the system closing switch 423 are turned on.
The processing procedure of the PU and the local processing device 413 is shown.

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 operation information is "r 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 ended, and if the answer is NO, the process returns to step 32511 and the above procedure is repeated (steps 82512 to 52514). After checking the operation information for all machines, step 525
Step 15, it is determined whether or not there is a pachinko machine in play, and if there is, the machine number of that pachinko machine is sent to the local processing device, and if there is no pachinko machine in play, ACK is sent.
is sent to the local processing unit and “closed” to all NAUs.
The packet is transmitted and the state waits for a command from the local processing device (steps 52516 to 2518). On the other hand, when the local processing device receives the machine number or "ACK", it disables the system end switch if there is a pachinko machine in play, displays the machine number in play, and then displays the normal display screen (No. 113) and waits for key personnel (steps 51153 to 51156)
. 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 (first to fourth lines) in FIG. 119 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 (step 52).
520-52522). The local processing device receives this and displays a message (see line 7 in FIG. 119) instructing to turn off the power on the system termination screen (step 51159).

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

When the card restoration switch is turned on, the local processing device 413 displays a message (first to third lines) prompting the user to input the card number on the card restoration screen as shown in FIG. 81161). 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 52531 and 52532).

Here, if the card status is "playing", search the pachinko machine file using the location terminal number in the card file, read the data of the pachinko machine, and transfer the number of balls and amount data in the pachinko machine file to the card. Let the current value of
Also, when the card status is other than "playing", the number of balls and amount data in the card file are used as the current value of the card, and these values are sent as card data to the local processing device along with the history data read from the card file. (
Steps 52533-52536).

Then, the local processing device displays the card revival screen (first
The received card data and history are displayed on the top (Figure 20) (step 81163). Therefore, when the card restoration switch 424 is turned on again, a card restoration request command is transmitted (step 81164). When the central processing unit receives this command, it first sends an "initial value transmission" function containing initial values such as date, identification code, etc. to the card issuing device 700, and receives a response ("normal completion" function). Then, enter the cart number, card issuing serial number, and amount at the time of issue.
A function is sent to start the process of issuing a resurrection card (steps 52537 to 52339). When the card issuing device 700 finishes issuing the resurrection card, it sends the result (normal completion function), so the central processing unit receives it and then transmits the completion of the resurrection to the local processing device (steps 52540, 52541). .

Then, the local processing device displays the result on the card restoration screen and then changes the screen to the normal display screen (step 51165). Note that the card issuing device 700 that has received the above-mentioned "card restoration" function prints the date of issue and the serial number of issue, and issues a reinstatement card with a reissue hole (the amount is not printed).

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

When the test card switch 437 is turned on, the local processing unit 413 displays a test card issue message on the screen of the CRT display unit 411, 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 an "initial value transmission" function containing initial values such as date, identification code, etc. to the card issuing device 700, and responds to it (
``Normal completion'' function) is received, the ``test card issue'' function is sent (step 52).
542-52544). When the test card issuance process in the card issuing device 700 is completed, the result is transmitted. 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 51).
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. 90 shows a flow of displaying sales statistical data using a timer interrupt.

In the management device 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. It is transmitted to the CPU (step 51181). 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 (step 5).
2551, 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", add 1 to the number of discontinued machines (steps 52553 to 52556); Then, in step 5, check whether the search for all pachinko machines has been completed.
2557) If it is a no, return to step 52551 and repeat the above procedure, and when it is completed for all machines, in the next step 82558, divide the cumulative value of the number of balls out and the number of balls out by dividing the number (
After calculating the operating rate (number of pachinko machines ÷ total number of pachinko machines) from the cumulative value of the number of gaming machines, we calculate sales, percentage, operating rate, and discontinuance as business statistical data. Send the number to the local processing device (step 5)
2558°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 device 411 (see FIG. 113) (step 81182). .

FIG. 91 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. 121 (step 51201).

When the operator selects the stop table display using the numeric keypad 425 while looking at this screen, the local processing unit transmits a stop table display data request command to the central processing unit (step 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 as stop machine data together with the machine number (steps 52561 to 52563).

Then, the local processing device stores each stop table data as the 122nd
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 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 5256
5, 51204).

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

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

When the operator selects specific machine display using the numeric keypad while looking at this screen, the local processing unit transmits a specific machine display data request command to the central processing unit (step 51211). On the CRT display device 411, the 12th
A message prompting to specify (input) a machine number is displayed on the first to third lines of the specific machine data display screen shown in FIG. 3 (step S1212). When the operator inputs the machine number using the numeric keypad 425 while looking at this screen, the local processing unit sends a specific machine display data request command including the machine number to the central processing unit (step 5121).
3).

When the central processing unit receives this command, it calculates a serial number from the machine number, searches the pachinko machine file using the serial number, and reads out the operation data of the corresponding pachinko machine (steps 52571, 52572). Of this operating data, we calculate the number of balls stopped, the number of balls out, the number of out balls, the number of differences,
The number of balls held, sales, and number of customers are transmitted to the local processing device (step 52573). Then, the local processing device displays the received data on the fifth and sixth lines of the specific machine data display screen (Fig. 123) (step 5121).
4). Thereafter, a data end command is sent from the central processing unit to the local processing unit and the process ends (step 525).
74,51215).

FIG. 93 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 device displays the CRT display device 411.
A display menu selection screen as shown in FIG. 121 is displayed (step 51221).

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

Then, the local processing device sequentially displays the data of all the pachinko machines on the all-machine display screen, one line per machine, as shown in FIG. 124 (step 51223). On the other hand, when the central processing unit finishes searching for all the pachinko machines in the pachinko machine file (step 82583), 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 5258).
4°51224).

FIG. 94 shows the procedure for data display processing for so-called red and white (red line), in which 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 displays the CRT display device 411.
A display menu selection screen as shown in FIG. 121 is displayed (step 51231).

When the operator selects red and white display using the numeric keypad 425 while looking at this screen, the local processing unit transmits a red and white display data request command to the central processing unit (step 51232). Upon receiving this command, the central processing unit reads the pachinko machine files in order (step 52591), and the number of differences in the file is negative (minus).
It is determined whether or not (step 52592). Then, only the operation data of pachinko machines with negative difference numbers are transmitted to the local processing device (step 52593).

Then, the local processing device sequentially displays each red and white data on the red and white display screen, one line per unit, as shown in FIG. 125 (step 51233).

On the other hand, when the central processing unit finishes searching for red and white 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. 95 shows the procedure of data display processing for so-called black and white (black) where the number of balls out is smaller than the number of out balls.

This black and white display flow is performed according to almost the same procedure as the red and white display flow shown in FIG. The difference is step 52
Instead of determining whether the difference number is negative or not in step 592, it is determined whether the difference number is positive (plus) and only the operation data of the positive pachinko machine is transmitted (step 82602). The configuration of the display screen is also the same as the red and white display screen shown in FIG. 125.

Figure 96 shows the issuing machine data display processing procedure, and Figure 12 shows the issuing machine data display processing procedure.
FIG. 6 shows an example of the structure of the issuing machine data display screen displayed on the CRT display device 411.

This issuing machine data display processing flow is executed according to almost the same procedure as the entire pachinko machine data display processing flow shown in FIG. Along with the machine number, the issuing machine data displayed on the screen includes the received amount, deposited amount, and withdrawn 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 5
2623).

Figure 97 shows the procedure for displaying payment machine data, and Figure 12 shows the procedure for displaying payment machine data.
FIG. 7 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 shown in FIG. 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.

Figure 98 shows the sales data display processing procedure for displaying the sales data for the entire pachinko parlor, that is, the total of the main pieces of operating data for all units, and Figure 128 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. 121 (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 (step 51272).

Upon receiving this command, the central processing unit sequentially reads the pachinko machine files and calculates the totals of the number of balls played, number of balls out, number of differences, and number of balls held among the operating data (steps 52641-32643). Next, the issuance machine files are read out in order and the totals of the deposited amount and the number of issuances are calculated from the operating data (steps 52644 to 5).
2646), the payment machine files are read out in order, and the sum of the payment amount, number of coins paid, and number of payments among the operating data is calculated (steps 52647 to 52649). After that, the calculated total data is sent to the local processing device as sales data, and after all the data is sent, a display data end command is sent (steps 52650, 52
651).

On the other hand, when the local processing device receives the sales data,
The business data display screen shown in FIG. 128 is displayed on the CRT display device 411, and a display data end command is received to wait for key human power (steps 51273, 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. 99 shows the procedure of a specific card data display process for displaying data of a specific card.

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

When the operator selects a specific card display using the numeric keypad 425 while looking at this screen, the machine number is specified in the first to third lines of the specific card data display screen shown in FIG.
51282). When the operator inputs the machine number using the numeric keypad 425 while looking at this screen, the local processing unit transmits a specific card display data request command including the machine number to the central processing unit (step 81283).

Then, the central processing unit calculates the card issuing serial number from the card number, reads the card file using the issuing serial number, and determines whether the card status in the card file is "playing" (steps 52661 to 52663).
). When the card status is other than ``Playing'', the number of balls and amount in the card file are used as the current value of the card, and when the card status is ``Playing'', the card location terminal number in the card file is used as the current value of the card. to search the pachinko machine file and set the data (number of balls, amount) in the pachinko machine file as the current value of the card (step 52664
~52666). This is because the card file is rewritten when the card status changes, so the operating data in the card file does not match the actual value during the game.

Next, the central processing unit performs steps 52664 and 52666.
The card current value determined in step 5 is sent to the local processing device together with the card history data read from the card file, and then a display data end command is sent (step 5).
2667.52668). 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. 129, receives the display data end command, and waits for key input (step 81284, 51285).

FIG. 100 shows a procedure for displaying all card details displaying data regarding all issued cards, and FIG. 130 shows an example of the structure of the all card details display screen displayed thereby.

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

When the operator selects card statement display using the numeric keypad while looking at this screen, the local processing unit transmits a card statement display data request command to the central processing unit (step 51292).

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 the card status is "Canceled" or not, and whether the card status is "Playing" (Steps 52671, 52672)
). Then, when the card status is other than ``playing'', the number of man-hours 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. Search for a pachinko machine file and use the data in the pachinko machine file (number of balls,
amount) as the current value of the cart (steps 52673-5
2675).

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 32676). Then, as shown in Section 5, the local processing device displays the remaining amount, number of balls, location terminal number, or card status of each card in one line per card (step 5129).
3).

On the other hand, after transmitting the card data in step 82676, 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, send the card total data to the local processing device in step 52679 and display it on the all card details display screen in FIG. 130. Send display data end command (steps 52379, 52680, 5129
4,51295).

FIG. 101 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. 100 (step 51).
301-81304, 52681-82689). The only difference is that step 52676 is omitted, that is, data for each card is not transmitted, but only the total data of all cards is transmitted (step 82686). On the other hand, correspondingly, total data is displayed on the screen of the CRT display device 411 (same as the lower half of the all card details display screen in FIG. 130).
only.

FIG. 102 shows the procedure for displaying interrupted card data and the machine number of the interrupted pachinko machine, and FIG. 131 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. 121 (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 (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" (step 51691).
, 51692). Here, for cards whose card status is "suspended", the history data column 1 of the card concerned
The elapsed time (difference) is calculated by comparing the time read from the time (interruption occurrence time) with the current time of the timer (step 52693). Then, the elapsed time, the card number, the amount of money, the number of balls held in the card data, the location terminal number, and the interruption time in the history data field are transmitted to the local processing device (step 51694). Then, the local processing unit displays the data of each card in one line as shown in FIG. 131 (step 51313), and when the central processing unit finishes extracting the data of the interrupted card for all cards in the file. , sends a display data end command, and when the local processing device receives it, it waits for key input (steps 52695, 52696, 5131).
4).

In the management device of this embodiment, by displaying the interruption card data, the management device sends a "forced termination request" packet to the pachinko machine whose interruption elapsed time is too long. Then, by transmitting a "forced termination release" packet, the suspended state can be canceled and the system can transition to a free state. This makes it possible to avoid a situation in which -1 player uses multiple cards to monopolize multiple pachinko machines, and to make the game fair by opening up all the pachinko machines to as many players as possible. . Moreover, in the system of this embodiment, the data of the suspended card is stored in the card file, so even if the pachinko machine that is suspended is released to another player, the interests of the player will not be harmed at all. do not have.

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. 103 shows more specific details of the random number generation process 52012 in the initialization flow of FIG. 62 and the card number calculation process 5215'l in the flow of FIG. 67 that calculates a card number using the random number obtained thereby. The following steps are shown in sequence.

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

Next, using the random number generation command RND (n), which is one of the commands of the FORTRAN programming language, enter the random number 1 generated in step S1 above into (n) to obtain a random number (7 digit or more) and convert it to 10
'Multiply to obtain a random number 2 (step 52702).

Then, use the same FORTRAN command INT(n) to round off the decimal part of the random number 2 (step S
2703).

After that, in step 52704, the random number A is determined to be O≦A.
Check whether the condition ≦10000 is satisfied, that is, whether A is greater than 0 and smaller than 10000. If A<O or A>10000, return to step S1 and set the random number A.
redo the occurrence. Then, in step 52705, 10,000 is added to the random number A that satisfies the above conditions. As a result, the random number A becomes any number between 10,000 and 20,000. Therefore, next, the FORTRAN command MO
Use D to find the remainder when random number A is divided by the integer "5",
This is set as random number B (step 52706). Therefore,
Random number B is 0, 1, 2, 3. ．． It will be one of 4 numbers.

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 seven (7). The reason why we set the upper limit of
This is to reserve the code with 1 for special cards (test cards) that are different from normal game cards.

In the next step 52708, the primary cart 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.

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

Table 31 shows an example of a focus switching pattern corresponding to random number B.

Table 31 Table 32 Next, the actual conversion of the card number using the above bit replacement pattern will be explained, taking as an example the case where the random number A is 14297, the random number B is 2, and the issued serial number n is 635. In this case, the -next card number X is.

From X=A+n, it becomes r14932J. If this is expressed in hexadecimal numbers, it becomes r3A54J, and if expressed in binary numbers, it becomes rOOllllooolololooJ. This-
When the next card number is converted using the third conversion pattern corresponding to random number B=2, it becomes as shown in Table 32 below, and the secondary card number becomes rlE13J in hexadecimal notation and r7699J in decimal notation.

On the other hand, the process of calculating the card issuing serial number from the card number (steps 52151, 52161, 52181
．． 52201, 52221゜82241.52261,
52281) etc., the specific method is the above step 52707.
, 52708, first convert the card number into a binary number, then inversely transform each bit using the conversion pattern determined by random number B (see Table 32) to obtain X.
The issue serial number can be obtained by subtracting the random number A from .

Next, the card issuing device 70 provided in the management device 400
The card issuance control procedure in the card issuance control bag fi790 and the card reader control device 288 in 0 will be explained.

In the card issuing device of this embodiment, the central processing unit CPTJ can communicate only with the card issuing control device [790] and cannot directly communicate with the card reader control device 288. In other words, the card reader control device 288 can communicate only with the card issue control device 790. Therefore, communication between the central processing unit CPU and the card issuance control device 790 is performed using function codes, and communication between the card issuance control device 790 and the card reader control device 288 is performed using commands. Incidentally, the function codes from the central processing unit CPU to the card issuance control device 790 include an "initial value setting" function for giving the card reader the date code and identification code to be recorded in the magnetic recording section of the card; The "card issue" function commands the issuance of a card, and the "card issue" function commands the issuance of a card.
"Card Revival" function, "Test Card Issue" function that commands the issuance of a test card, and "Test Card Issue" function that requests resending of the function code sent just before.
"resend request" function, card issue control device 790
Six types of commands are available, including a "status request" function that requests transmission of the status indicating the status of the card reader received from the card reader control device @288.

However, only the "cart revival" and "test card issue" functions are used in the management device, and the other functions are used in the issuing machine 2.
This is prepared for the card issuing device built into the 00.

Also, from the card issuance control bag @790, the central processing unit cp
Function codes for u include the "initial value request" function, which requests initial values such as date and identification code at the time of reset, and the "normal completion" function, which notifies the central processing unit that the instructed process has completed normally. Conversely, there is an "abnormal end" function that notifies that the process has not ended normally, and a "resend request" function that requests the central processing unit to resend the function code sent just before. Issuing machine 20
In addition, in 0, " from the unit controller 299
There is a ``send status'' function to send the card reader's status in response to a ``status request''.

Although not particularly limited, the function code is transmitted between a start code STX and an end code ETX, and in addition to the function code, a status or data to be transmitted may be inserted between STX and ETX.

Specifically, the 8-bit status 1 and status 2 indicating the card reader status as shown in Table 33 and Table 34 are included in the above-mentioned "normal end" function, "abnormal end" function, and "status transmission" function.
The status is sent to the central processing unit CPU along with the function code.

In status 1 of Table 33, the transport unit sensor abnormality bit is the traveling position sensor CPS2 of the card issuing device 700.
[1] is set when any of the CPSs 6 fails.

Table 33 Table 34 On the other hand, the communication commands from the card issuing control device 790 to the card reader control device 288 include a "magnetic write" command that instructs to record magnetic data on the card, and a "magnetic write" command that instructs the card to record magnetic data, security code, and ``Magnetic read'' command that instructs to read each information of punch hole and send magnetic data, and ``Security request'' to instruct to send read security data.
command, a "bunch hole request" command that instructs to send the read punch hole data, a "reload" command that instructs to reread the card data held in the card reader, and a punch hole in the card. The "Punch Hole" command instructs to eject the card in the card reader toward the front insertion slot, and the "Card Front Eject" command instructs to eject the card in the card reader toward the front insertion slot. There are nine types of commands: a "card rear ejection" command, a "cancel" command for canceling a card reading command, and a "status request" command for instructing transmission of status information indicating the status of the card reader.

Further, when the card reader control device N288 receives the above command from the card issue control device 790, it executes the corresponding process and always returns a response. The types of responses are normal, communication error, command error, no magnetically recorded data, unable to read magnetic data,
Magnetic recording data abnormality, security and magnetic data match, company code or equipment code mismatch, magnetic write error punch error, punch hole reading error, security reading error, punch waste full, motor abnormality, RAM abnormality, sensor abnormality, card reader abnormality, There is a card length error or card jam.

Although not particularly limited, the code indicating the above command is transmitted between a start code called ESC and an end code called CR, and data to be sent in addition to the command code may be inserted between ESC and CR. Also, the card issuing control device is connected to the card reader control device 288! A response to the nearer 90 is transmitted by sandwiching a code indicating the type of error or an error code and the requested data between a start code STX and an end code CR.

FIG. 132 shows a control procedure for card restoration, etc. in the card issuing control device 790 of the management device.

When the card issuance control device 790 is reset, it first clears and initializes the internal memory, registers, I10 port, etc., then sets a timer (ex, 10 seconds) and sends the "initial value request" function to the central processing unit. Send to the CPU (routines RNIOI to RN103). next,
Checks whether a function has been received from the central processing unit/CPU. If not, routine RN102 is executed.
It is determined whether the timer set in has exceeded (routines RN104 and RN105). Then, routines RN104 and 10'5 are repeated until the time is over, and when the time is over, return to routine RN102, reset the timer, and send the "Initial value request J function" again.First, the "Initial value request" function is sent. This is because the central processing unit gcpu may not be ready for reception at this time.

When a function is received from the central processing unit 1cPU after transmitting the function, the routine moves from RN104 to RN106 to check whether the received function is an "initial value transmission" function or not. After transmitting the request, the routine returns to routine RN102 and retransmits the "initial value request" function. This is to first obtain the initial value and then accurately execute specific processing such as card issuance.

However, the management device does not send the initial value at the time of initialization, but instead sends the ``send initial value'' function immediately before the ``card revival'' or ``test card issue'' function.

If the received function is "Initial value transmission" as determined in routine RN106, the process advances to routine RN108, stores the date and identification code sent together with the function code in internal memory, and then repeats the same procedure. Clears the initial value unset bit of the status register stored in the internal memory and sends the "normal completion" function to the central processing unit CPU (routine RN109.
RNIIO).

After that, routine RNIII waits for reception of the next function from the central processing unit CPU, and when the function is received, routines RN112 to RN1 are executed.
Proceed to step 15, determine which function has been received, and if it is an "initial value transmission" function, store the date and identification code, and then transmit the "normal end" function. Routine RNI 16. RNI 17)
, if it is a "card revival" function, the 13th
Execute the card restoration process shown in Figure 3 (routine RN113
), and when the received function is "test card issue", a test card issue process is executed (not shown) according to the same procedure as the card restoration process in FIG. 104 (routine RN114). The reason why routine RN112 judges again whether or not it is the "initial value transmission" function is to take into consideration the case where the routine returns to routine RNIII (symbol V1) after executing an error process (see FIG. 106), which will be described later.

FIG. 133 shows the specific procedure of the card restoration process (common to the test card issuing process) in the flow of FIG. 132.

When the card issuance control device 790 receives the ``Card Restoration J Function'' or the ``Test Cart Issuance'' function from the central processing unit CPU, it first receives the function shown in FIG.
Card removal processing routine RN201 shown in A)
~ After executing RN212, the reader control processing routines RN213 to RN227 in FIG. 134(B) and the card reversal processing routines RN228 to RN24 in FIG. 134(C) are executed.
3. Printing 1 processing routine RN245 in Figure 134 (D)
After executing steps RN266 to RN266, the card ejecting processes RN268 to RN280 shown in FIG.゜RN119).

FIG. 134(A) shows the specific procedure of the card ejecting process in the card restoration (or test card issuing) process flow of FIG. 133.

Here, first, the card presence/absence sensor 703 is checked to see if there is a card in the card tank 701 (routine R2
01), when the sensor is off, that is, when the tank is empty, jump to routine RN212, set the ejector error bit of status 2 in the internal memory to "1", and then
The process moves to the error handling routine shown in FIG. 135.

Furthermore, when there is a card in the card tank 701, the routine moves from RN201 to RN202 and sends a "magnetic write" command to the card reader control device 288. Then, after setting the timer, clutch solenoid 729
is turned on and the take-out motor 719 is rotated (routines RN203 and RN204), whereby one card is sent out from the card tank.

Next, it is checked whether the timer set in routine RN203 has timed out, and if no, it is checked whether the first traveling position sensor CPSL is turned on (routine RN205.
RN206), when the first traveling position sensor CPSI is off, the routine returns to RN206 and the timer check is repeated. In this way, it waits for the first traveling position sensor CPSL to turn on, and if the time is over before the sensor turns on, it jumps to routine RN211 and status 1.
The traveling position sensor 1 abnormality bit of the status 2 is set to "1", and the ejector abnormality bit of the status 2 is then set to "1", and then the process moves to the error processing routine shown in FIG. 135.

On the other hand, before the time is over, the first traveling position sensor CP
When the SL is turned on, the routine advances to routine RN207, where the clutch solenoid 729 is turned off to stop the rotational force of the take-out motor 719 from being transmitted to the roller 712 that sends out the cards from the tank, thereby preventing two cards from being fed. ,
Check again whether the timer set in routine RN203 has timed out (routine RN208).
.

Next, it is checked whether the first traveling position sensor CPSL has turned off or not. If the sensor turns off within a predetermined time, it is determined that the card has been taken out from the card tank 701 and sent out normally, and the take-out motor 719 is stopped. The process is then terminated and the process returns to the original routine (FIG. 133). If the traveling position sensor CPSL is not turned off within a predetermined period of time, it is determined that the card has become jammed, and the routine proceeds to routine RN211, where the traveling position sensor 1 abnormality bit of status 1 is set.

FIG. 134(B) shows the specific procedure of the reader control process during the card restoration process flow of FIG. 133.

In this flow, first set the timer.

Before the timer times out, it is checked whether there is a response to the "magnetic write" command sent in routine RN202 in the card removal process flow (routines RN213 to RN215). If there is no response within the time, the routine RN227 jumps and sets the card reader error bit of status 2 to "1".
After setting this, the process moves to the error handling routine shown in FIG. 135.

Further, when a response is received from the card reader control device 288 within a predetermined time, the routine advances to routine RN216a and checks whether the response is normal or not.If there is an abnormality, the routine jumps to routine RN227 in the same way as when the time is over. Perform error handling. On the other hand, if the response is normal, the receiving function determines whether or not the "card restoration" function is used (routine RN216b). When "test card issuance" is performed, a "punch hole" command containing data indicating the issuing hole position is sent, and a timer is set (routines RN217a, RN217b,
RN218).

Then, it is checked whether there is a response from the card reader control device 288 before the timer times out (routines RN219 and RN220). If there is no response within the time, routine RN227
After jumping and setting the status 20 card reader error bit to "1", the process moves to the error processing routine shown in FIG. 135.

Further, when a response is received from the card reader control device 288 within a predetermined time, the process proceeds to routine RN221, and checks whether the response is normal or not. If there is an abnormality, the routine RN227 jumps in the same way as when the time is over.
Perform error handling. On the other hand, if the response is normal, a "card rear ejection" command is sent to the card reader control device 288 and a timer is set (routines RN222 to RN223). It then checks to see if there was a response from card reader controller 288 before that timer times out (routine RN224.RN
225). If there is no response within the time, the routine jumps to RN227, sets the card reader error bit of status 2 to ``1'', and then proceeds to the error processing routine shown in FIG. 135.

Further, when a response is received from the card reader control device 288 within a predetermined time, the routine advances to routine RN226 and checks whether the response is normal or not. If there is an abnormality, the routine jumps to routine RN227 in the same way as when the time is over.
Perform error handling. On the other hand, if the response is normal, the process returns to the original routine (FIG. 133).

FIG. 134(C) shows a specific procedure for card reversal processing in the card restoration processing flow of FIG. 133.

In this process, first, the transport motor 706 is rotated forward, and then a timer is set, and before the timer times out, it is checked whether the second travel position sensor CPS2 is turned on (routines RN228 to RN231). If the second traveling position sensor CPS2 does not turn on within the time, jump to routine RN242 and set "1" to the jam error bit of status 1, and routine R
At N243, the status 2 card transport error bit is set to “1”.
” are set respectively, and then the process moves to the error handling routine shown in FIG. 135.

On the other hand, when the second traveling position sensor cps2 is turned on within the predetermined time, the routine RN232. The routine moves to RN233 and checks whether or not the second travel position sensor CPS2 is turned off before the timer set in routine RN229 times out.

If the second travel position sensor CPS2 turns off, it means that the card has passed the travel path switching piece 745. Therefore, if the second traveling position sensor CPS2 does not turn off within the time, jump to routine RN242 and set "1" to the jam error bit of status 1, and set "1" to the card transport error bit of status 2 in routine RN243. are set respectively, and then the process moves to the error handling routine shown in FIG. 135.

Furthermore, when the second traveling position sensor CPS2 turns off within a predetermined time, the process moves to routine RN234, sets a new timer, and then reversely rotates the transport motor 706 (
routine RN235). As a result, the card is transferred in the opposite direction, and the printing device 750 is moved by the path switching piece 745.
You will be guided to the route heading towards.

After the conveyance motor is reversed, the card issuing control device 790 checks whether the second travel position sensor CPS2 is turned on again before the timer set in routine RN234 times out (routines RN236 and RN237).
). If the second travel position sensor CPS2 does not turn on within the time, jump to routine RN242 and set "1" to the jam error bit of status 1, and set "1" to the card conveyance error bit of status 2 in routine RN243. are set respectively, and then the process moves to the error handling routine shown in FIG. 135.

On the other hand, when the second traveling position sensor CPS2 is turned on within the predetermined time, the routine RN238. The routine moves to RN239 and checks whether the second travel position sensor CPS2 has turned off before the timer set in routine RN234 times out.

If the second traveling position sensor CPS2 does not turn off within the time, jump to routine RN242 and set "1" to the jam error bit of status 1, and set "1" to the card transport error bit of status 2 in routine RN243.
1'' respectively, and then proceeds to the error handling routine shown in FIG. 135.

Further, when the second travel position sensor CPS2 is turned off within a predetermined time, the routine RN240. Move to RN241 and check whether the third traveling position sensor CPS3 is turned on before the timer set in routine RN234 times out. If the sensor is turned on within the time, return to the original routine (Fig. 133). return.

FIG. 134(D) shows a specific procedure of printing processing in the card restoration processing flow of FIG. 133.

Here, we first set the timer, and then before the timer times out, the fourth travel position sensor CPS
4 is turned on (routine RN245
~RN267). If a time over occurs before the fourth traveling position sensor CPS4 turns on, routine RN2
65. After jumping to R266 and setting the jam error bit of status 1 to "1" and setting rlJ to the printer error bit of status 2, the process moves to the error processing shown in FIG. 67.

In addition, if the fourth traveling position sensor CPS4 is turned on before a time-over occurs, the process proceeds to routine RN248, rotates the printing motor 751, and then checks whether the third traveling position sensor CPS3 is turned off before a time-over occurs. (routine RN249.RN250)
). Here, if a time-over occurs, routine RN2
65 to proceed to error processing, and if the third travel position sensor CPS3 turns off within the predetermined time, the 13th
After stopping the driven transport motor 706 in the routine RN235 of FIG. 4(C), it is checked whether the fourth traveling position sensor CPS4 has been turned off before a time-over occurs (routines RN251 to RN253). If a time-over occurs here, the same routine RN as above
Jump to 265. On the other hand, if the fourth traveling position sensor CPS4 turns off before the time is over, routine RN2
Proceed to step 54 and turn the print head lift motor 758 to 180°.
Rotate and lower the head. Then, it is determined whether the received function is "cart revival" (routine RN255), and if yes, print head 756 prints the issue serial number and date; The date and characters rTESTJ indicating that it is a test card are printed (routines RN256 to RN259).

Thereafter, the head lifting motor 758 is rotated 180 degrees again to raise the print head 756, and a new timer is set (routines RN261 and RN262). After that, routines RN263 and RN264) check whether the fifth travel position sensor CPS5 was turned on before this timer times out, and if a time over occurs, the routine moves to routine RN265 and sets the jam error bit in status 1 to "1" and the printer abnormality bit of status 2 is set to "1", and then the process moves to the error processing shown in FIG. 135. On the other hand, if the fifth travel position sensor CPS5 is turned on before the timeout occurs, the process returns to the original routine (FIG. 133).

FIG. 134(E) shows the specific procedure of the card ejection process in the card issuing process flow of FIG. 133.

When this process is started, first, the extraction solenoid 779 in the card extraction device 770 is turned on, and the lane switching member 77 is turned on.
7 downward, the transport motor 706 starts to rotate in reverse, and the timer is set (routine RN268~
RN270). As a result, the card sent out from the printing device 750 is transferred toward the card issuing port 202 through the inside of the drawing device 770. And routine RN
If the fifth traveling position sensor cps5 turns off before the timer set in step 270 times out, the printing motor 751 in the printing device 750 is stopped (routines RN271 to RN273).

This is because the card has already been sent out from the printing device 750. In addition, if a time over occurs before the fifth traveling position sensor CPS5 turns off, routine R279
, moves to the RN280 and sets the status 1 jam error bit and the status 2 card transport error bit as ".
1" and then moves to the error processing shown in FIG. 135.

After stopping the printing motor 751 in the above routine RN273, check the timer set in the routine RN270 again, and if the sixth traveling position sensor CPS6 located immediately before the card issuing port 202 turns on before a timeout occurs, Turn off the lead-out solenoid 779 (routines RN274 to RN276), 6th traveling position sensor C
If the timer times out before the PS6 is turned on, the process moves to routine RN279.

After turning off the lead-out solenoid 779 in routine RN276, a new timer is set and the conveyance motor 706 is stopped after waiting 0.5 seconds. The above 0.5 seconds is determined from the relationship with the rotation speed of the transport motor 706.
This is sufficient time for the conveyor belt 772 of the cart extractor 770 to move the card a distance corresponding to its total length Q0. By waiting 0.5 seconds after the sixth running position sensor CPS6 detects the card, the card stops with about two thirds protruding from the card issuing slot 202.

The sixth running position sensor CPS6 is turned off when the player manually pulls out the card from the issuing slot 202.

Figure 135 shows various sensors CPS that detect the position of the card during each processing flow of Figures 134 (A) to (E).
A specific procedure for error handling that is executed when a time-over occurs before I to CPS6 etc. are turned on or off is shown.

In this process, first, all motors in the card issuing device 700 (eject motor 719, transport motor 706, printing motor 751, and head lift motor 758) are stopped, and then an "abnormal end" function is sent to the central processing unit. (routine RN151.RN152). next,
Routine RN153) determines whether a function has been sent from the central processing unit; if no function has been received, routine RN154 determines whether the error has been recovered by checking the sensor in the card issuing device 700. ), if the error has not been recovered, the process returns to routine RN153 to wait for the error to be recovered. While waiting for recovery, if the cause of the error disappears, such as by removing the card stuck in the cart issuing device 700, the process moves to routine RN155 and the statuses 1 and 2 are returned.
After clearing each error bit to "O", routine R
The process moves to N156, where the counters 795 and 796 for counting the number of cards taken out and the number of cards confiscated are updated, and the process returns to routine RNIII in the main processing flow (FIG. 132) (see symbol 1).

On the other hand, routine RN153. When RN154 receives a function from the central processing unit while waiting for error recovery, it moves to routine RNI57 to determine whether the received function is a "status request" function, and if yes, the next routine RN158 is executed. After sending the status transmission J function, return to routine RN153 and wait for the error to be recovered.

This flow is common to the card issuing device for the issuing machine, and is prepared assuming a "status request" from the unit controller 290 of the issuing machine. Also, if the function received while waiting for error recovery is not a "status request", it is determined in routine RN159 whether the received function is an "initial value transmission" function, and if it is "initial value transmission", that function is Store the date and identification code in the internal memory, send the "normal completion" function, and execute the routine RN.
Return to step 153 and wait for error recovery again (routine RN
160. RN161).

Also, the function received while waiting for error recovery is
If neither "Status Request" nor "Initial Value Send" is selected, the routine returns from RN159 to RN152, sends the "Abnormal End" function, and then waits for error recovery.

Next, the card reader 800 is operated by the card reader control device 288 based on the command from the card issuing control device 790.
An example of the control procedure will be explained using FIGS. 136 to 141. Note that the flow of this embodiment can be used in common as either control flow assuming that the same card reader as the management bag W400 is used in the payment machine 300 and the issuing machine 200.

The major difference from the control flow related to the card reader in the control unit 160 of a pachinko machine is that it has a control flow for writing a magnetic code and its verification, and a flow for ejecting the card to the rear of the card reader instead of the front. be.

As described above, communication between the card reader control device 288 and the card issuance control device 790 is performed by sending commands as described above, and the communication between the card reader control device 288 and the card reader control device 790 is performed by sending commands.
The communication commands for this include the "magnetic write" command, which instructs to record the magnetic data on the card, and the "magnetic write" command, which instructs to read the magnetic data, security code, and punch hole information of the card and send the magnetic data.
"magnetic read" command, "security request" command that instructs to send the read security data, "punch hole request" command that instructs to send the read punch hole data, and the "magnetic read" command that instructs to send the read security data. "Reload" command instructs to reread the data, and "Reload" command instructs to punch a hole in the card.
"Punch Hole" command, "Card Front Ejection" command that instructs to eject the card in the card reader toward the front insertion slot, and "Card Front Ejection" command that instructs to eject the card in the card reader toward the rear. ” command and
There are nine types of commands: a "cancel" command for canceling a card reading command and a "status request" command for instructing transmission of status information indicating the status of the card reader.

Of these, the "magnetic read" and "reload" commands are not used by the issuing machine 200, and the "magnetic write" command is not used by the payment machine 300 or the management device 400. In addition,"
The "magnetic read" command instructs the card reader 800 to read not only magnetic data but all data on the card, and requests transmission of only the magnetic data. Separate data request commands are provided for security data and punch hole data.

Fig. 136 shows the entire main control procedure by the card reader control device 288, Figs. 137 to 139 show the detailed procedure, and Figs. 140 and 141 show the main control procedure separately from the main control described above. 2 shows a control procedure for interrupt processing caused by an interrupt.

When the card reader control device 288 is reset,
That is, when the reset input terminal changes to low level, as shown in FIG. 136, first, the internal memory containing various flags, counters, buffers, work areas, registers, etc. is cleared (routine RIIOI). Then, after setting the stack pointer when an interrupt occurs, initializing the ■/○ port, and setting the status of the input/output terminal, 1.
Relay R that supplies power to the card transport motor 807
Turn on LY 1 (routine R1102 to R110
5).

Next, the monitor display 175 that displays the cause of the error is set to the off state, and the power-on lamp L that indicates the power-on state is turned off.
After lighting ED21, set the “Card insertion prohibited” flag in the built-in RAM to “1” (routines R11○6 to R
1108). Then, after allowing the reception buffer to receive commands from the card issuance control device 790,
Check whether a command has been received (routine R1109
, RIIIO). Here, if there is no received command,
Proceed to routine R1117 and check whether the "When card is inserted" flag is set to II II II.
II O", returns to routine RIIIO and waits for reception of a command; if "card inserted" flag is 1, executes card reading process shown in FIG. 137 (A) and then returns to routine RIIIO. return. The card reading process is the same as the process when a "magnetic reading" command is received. The flowchart of this embodiment is as follows:
00 and the management device 400 as well as the pachinko machine 100 and the issuing machine 2.
It is designed so that it can be used in common when the same card reader 800 as 00 is used, and the routine R111
The flow from 7 to "Card reading process" is intended to control the payment machine and management device, and in the flow of this issuing machine, the 1' Waiting for card insertion' flag is always t.
t O”, which makes no sense.

In the payment machine 300, the "Card Acceptable" function is sent to the card payment control device 312 based on the reception of the "store opening code" packet, and the card payment control device M3
When a "magnetic read" command is sent from 12 to the card reader control unit W388, it is determined in routine R1110 that there has been reception, and the process proceeds to routine R1111.When "ESC" at the beginning of the command is detected, the process jumps to routine R1118. Proceeding to R1121, the type of command is determined, and the process moves to the magnetic reading process shown in FIG. 137(A). From routine R1202, the card reading process shown in FIG. 138(a) is further executed. While the insertion detection switch is off, the card is not read and the "card not read" flag is set and routines R1203 to R
The process moves to step 1204, sets the "wait for card insertion" flag, moves to the routine R1122→R1117 in FIG. 136, and then moves to the process in FIG. 137(A) again.

In other words, it waits for a long time until the card is inserted, and at the time of insertion, the card reading process shown in FIG. 138(b) is executed.

On the other hand, if routine RIIIO determines that a command has been received, and routine R11l determines that the received data is not "ESC", which indicates the beginning of the command, routine R1112 determines that the command is the same as the previously sent command. It is determined whether the cancel command is "CAN". This kind of determination can be made because the cancel command "CAN", unlike other communication commands, is sent as the command code itself, which has a start code ESC and an end code C8. If the received command is not “CAM” in routine R112, routine R1117
If it is "CA N", proceed to the next routine R1113, set the "card insertion prohibited" flag, turn off the card holding lamp, and set a code indicating normal completion in the transmission buffer. 138(h) and sends the code to the card issuing control unit W7.
90, the "1 card insertion wait" flag is cleared and the process returns to routine RIIIO. As a result, the card insertion wait state caused by the "a-read" command previously sent from the card issue control device 1790 is canceled. Ru.

After that, the command is received again and the process proceeds to routine R1111, and if it is determined that the command head code has been received, the process jumps to routine R1-118, which prohibits the reception of subsequent commands, and then displays the monitor display 206 of the card reader.
is turned off, and the OK clamp indicating the reception status of the card reader control device 288 is turned off (routines R1119, R1
120).

Then, in routine R1121, it is checked whether the received command corresponds to any of the nine commands mentioned above, and
If the command does not apply, a code indicating "command abnormality" is written in the memory as error information in routine R1124, and then the process moves to the error processing routine shown in Figure 139. If the command corresponds to the registered command, the corresponding process is executed. After executing the OK clamp, turn on the OK clamp and start the routine RII.
Return to O9 and repeat the above procedure (routine R1122
, R1123).

Figure 137 (A) shows the processing procedure when a "magnetic read" command is received, and Figure 137 (B) shows the "reload" command.
The processing procedure when a command is received is shown. These command processes are unrelated to the card issuing machine 200, so their explanation will be omitted.

FIG. 137(C) shows the processing procedure of the card reader controller 288 when receiving the "magnetic write" command.

When this command is received, the magnetic recording data sent in the form of ASCII code along with the "magnetic write" command is first converted into a binary code suitable for internal processing and stored in the magnetic data buffer of the internal memory. Insert the head code 5TX (see Figure 2 (E)) indicating the head of the magnetic data at the head of the magnetic data buffer, and write the next code (21 if the number of magnetic data is 20) after the above magnetic recording data in the magnetic data buffer. ET indicating the end of data at
Enter the X code (routines R1231 to R1233)
. Next, after setting the number of magnetic data to be written (22 including the LRC calculated in the next routine), set the address for sequentially reading the magnetic recording data from the saved magnetic data buffer in the address counter ( routines R1234, R1235).

After that, in routine R1236, S is stored in a predetermined register A.
After setting the TX code (OBH) in advance, the process of calculating the exclusive OR of the data in register A and the next magnetic data in routines R1237 to R1244 and putting it back into register A is as follows: By repeating this process until no magnetic data is left, the LRC code, which is an error check code for all magnetic data, remains in register A.

Note that in routine R1236, STX is first stored in register A.
Since the code (OBH) is set, the first exclusive OR operation (routine R1238) operates on the same data, and the result is all 110'', so STX is used for LRC calculation. The same result as if it were not included is obtained, and the initial purpose can be achieved.Also, in the processing of routines R1237 to R1248, at the same time as calculating the LRC, the number of on bits (11111 bits) in each read data is odd or even. If the number is even, the parity bit in each data is set to 1711+ and saved in the data buffer, thereby adding a parity (odd parity) bit (routine R1).
239-R1241). After the above RC and parity bit calculation processing, the last (24th) magnetic data buffer
Insert the code indicating STX into (routine R1245)
. In other words, magnetic data, ETX and LRC are stored in two S
Make it sandwiched by the TX code (see Figure 2 (E)).

Next, it is determined whether the number of on-pits in the data (LCR) remaining in register A is an even number or an odd number, and only when the number is even, the parity bit is set to "1" and the parity bit is added to the LRC itself, and the magnetic data is At a given position in the buffer (23
character) (routines R1246 to R1248)
.

After that, the write process shown in FIG. 138(d) (
After executing the routines R1301 to R1337) to output the magnetic data and write clock, execute the verify process (routines R1341 to R1361) shown in FIG. , it is determined whether or not a verify error has been detected (routine R1249), and if there is an error, a magnetic write abnormality is set as error information in the memory, and then the process moves to the error handling routine shown in FIG. 139 (routine R1249).
1251). In addition, if there is no verification error, a "normal" response command is set in the transmission buffer, and then the transmission processing (routines R1421 to R1
426) and returns to the main flow in FIG. 136.

FIG. 137(D) shows the control procedure of the card reader control device 288 when receiving the "status request" command from the card issuing control device [790].

When a "status request" command is received, the device code and the contents of status 1 held in the internal memory are moved to the transmission buffer, and a code CR indicating the end of the command is set to the address next to the last data in the transmission buffer. Then, STX is set as transmission data and first transmitted (routines R1261 to R1264). After that,
The address of the transmission buffer is set in a counter, and then one byte of data is read from the transmission buffer using the address and transmitted, after which the address of the transmission buffer is updated (routines R1265 to R1268).

Then, it is determined whether or not CR Coco has been transmitted, and if it is no, it returns to routine R1266, transmits the next data, and
The processing for the "status request" command ends with the transmission of R Coco (routine R1269).

Furthermore, FIG. 137(E) also shows the control procedure when the "punch hole request" command is received.
) shows the control procedure when receiving the security request J command.

Response processing for these commands (R1271 to R1
279 and R1281 to R1289)
This is exactly the same as the response process to the "status request" command in FIG. 7(D). The only difference is that punch hole data or security data read from the card and held in internal memory is first transferred to the transmission buffer instead of the device code and status 1 contents.

Furthermore, FIG. 137(G) shows a card issuing control device [79
The control procedure of the card reader control device 288 when receiving the "punch hole" command from 0 is shown.

When this command is received, the hole punch sent with the command is moved from the reference position based on the punch hole position set in RAM in the initialization routine etc. based on the data indicating the location (in this case, the issued hole). After reading the distance from the ROM and storing it in the buffer (routine R1291), the hole drilling shown in FIG. 138(g) is processed (R311 to R35).
Execute 2). Then, check the ``Punch OK I+'' flag to determine whether the hole was punched properly (Routine R1292) - If yes, set a normal response command to the transmission buffer (Routine R1293),
Execute the transmission process in Figure 8 (h), and if it is no, the status is 1.
After setting tL I P+ in the punch failure bit of , and writing punch abnormality in the error information, the process moves to the error processing routine shown in FIG. 139 (routines R1294 and R1294).
1295).

FIG. 137(H) shows the control procedure in the card reader control device 288 when the "card rear ejection" command is received.

When this command is received, a 1-second timer is first set, and then the motor 807 is rotated forward at high speed (routine R14).
01, R1402). Then, it is checked whether the timer set in routine R1401 has timed out, and then it is checked whether the rearmost position detection sensor 5NS4 in the card reader has turned on (routine R1403).
, R1404). If a time-over occurs before the position detection sensor 5NS4 turns off, routine R
1413 Hejjump to stop the motor 807 and then check whether all sensors are off (routine R1414
). Here, if even one of the sensors in the card reader is on, set the cart jam bit of status 1 to 1'1'', write the card jam error as error information, and then process the error as shown in Figure 139. Proceed to routine R1114.If all sensors are off in routine R1114, it is assumed that the discharge has ended and routine R14 is executed.
07 Hejijump.

On the other hand, if the position detection sensor 5NS4 turns off before the timer set in routine R1401 times out, the motor 807 is stopped after waiting 0.4 seconds (routine R1403).

The card reversing device 740 behind the card reader is driven,
This is to wait for the card sent out from the cart reader 800 to start being conveyed by the card reversing device 740.

After stopping the motor 807, the card jam bit of status 1 is cleared and the routine R of FIG. 138(e) is executed.
After clearing the "verify error" flag set in step 1351, the card holding LED is turned off (routine R1
407-R1409).

After that, after setting the packart insertion prohibition flag to prohibit the insertion of the next cart, and setting the code of the "normal" response command in the sending buffer, the process shown in FIG. 138 (h
) (routines R1410, R14
11).

FIG. 137(I) shows the processing procedure of the card reader control device 288 when it receives the "card forward eject j command" from the card issuance control device 790.

This process is a flow prepared because it is necessary in the card payment machine 300, and is not executed in the card issuing machine 200, so a description thereof will be omitted.

In addition, FIGS. 138(a) and (b) also include FIG. 137(A).
The specific procedures of the card reading process, parity, and LRC inspection process during the "magnetic read" command reception flow are shown in FIG. 138(c). Although specific processing steps are shown, since these processes are also executed by the card payment machine and not by the card issuing machine, their explanation will be omitted.

On the other hand, FIG. 138(d) shows the specific procedure of the write process in the flow of FIG. 137(C). In this process, the rear end of the card is first moved to the position of the position detection sensors SN and SL on the entrance side of the card reader 800, and then the number of magnetic data (eX, 24 pieces) is set in the counter (routine R1301, R1302). At this time, the head of the card has not reached the position of the magnetic head 821.

Then, after setting the start address of the magnetic data buffer containing the magnetic recording data in the address counter, the motor 807 is rotated at high speed and the write permission signal for the magnetic head 821 is turned on (high level) (routine R1
303-R1305).

After that, erase data tt for providing a non-data area at the beginning and end of the track TRC2 of the magnetic data recording section.
Set it to On, set a 200ms timer, and then
Set the "write side write" flag to o 1 pr and 80
Start a write interrupt every 6 μs (routine R13
06-R1308). The write interrupt is generated by the detection signal from the encoder that detects the rotation of the motor 807.
It comes in every second (assuming the card transport speed is 300 mm/s).

Next, after checking the timer set in routine R1307, the write clock data is inverted and the "wait for writing" flag II 1 t+ is set.

Wait for this flag to be cleared to 110" in the write interrupt process shown in FIG. 141 (routines R1309 to R131).
2). Then, it is checked whether or not the position detection sensor 5NS3 located slightly behind the magnetic head 821 is turned on (routine R1313), and if it is turned off, routine R1
Returning to step 309, the above procedure is repeated until the sensor 5NS3 is turned on.

By repeating the above loop, the write clock data is inverted every time a write interrupt is executed once every 806 microseconds. As a result, the direction of magnetization of the magnetic part of the card by the magnetic head is reversed every 806 μs, and 2
Clock data with one period of 1.612 msec is written to the track TRC1 of the card. Note that the position detection sensor SNS 3 detects the end of the card when the magnetic head moves to the ST position of the track TRC2.
The mounting position is determined to be at the X code writing start position, and when the sensor 5NS3 is turned on, the process advances to the next routine R1314 and starts writing magnetic data. Note that before this sensor 5NS3 is turned on, routine R13 is executed.
When the timer set in 07 times out,
It is determined that the card is jammed, the routine jumps from R1309 to R1336, sets 1" in the card jam pit of status 1, writes the card jam in the error information, and then moves to the error handling routine shown in FIG. 139 (routine R1337). ).

If the position detection sensor 5NS3 turns on before a time-over occurs, the process advances to routine R1314, where the number of bits (5 bits) of each data (including parity) is set in a counter, and then the address set in routine R1303 is used. One byte (8 bits) of magnetic recording data is read from the magnetic data buffer and input into a shift register serving as parallel-to-serial conversion means, and an address counter is incremented (routines R1315 and R1316).

Then, add 2 bits of data in the output sofa and 1
Shift a total of 3 bits to the left (routine R131
7, R1318), this places the most significant bit of the 5-bit magnetic data at the left end of the shift register.

Then, in routine R1319, it is determined whether the bit at the left end of the shift register is on, that is, "1". If tr Otr, the write data is inverted in the next routine R1320, and if it is 11", it is not inverted and the write data is transferred to routine R13.
21 Heji Jump. With this, it is possible to form and output an NRZI type write signal. Also,
Following the output of write data, the routine R1310
~Execute the output of the write clock using the same procedure as performed in R1312 (routines R1321 to R1323)
). Of these, the write data is stored on the second track T of the card.
RC2, and the write clock is the first track TRC1.
Write each.

After outputting the above 1-bit data, the bit counter is decremented and it is determined whether the counter has reached rQJ.
If it is not J, return to routine R1318, shift the magnetic data in the shift register to the left by 1 bit, and repeat the process of outputting it until the bit counter reaches rQJ, thereby converting the 5-bit parallel magnetic data into serial data. Converted to write data and output (routine R
1324, R1325). When the output of 1 byte of magnetic data is completed, the process proceeds to routine R], 326, subtracts the number of magnetic data by one, and then returns to routine R131.
Returning to step 4, the parallel-to-serial conversion and output of the next magnetic data are repeated, and when the output of all magnetic data is completed, the process moves to routine R1328 (routine R1327).

In the routine R1328, a 100 msec timer is set, and then the same steps as in the routines R1309 to R1313 are performed until the position detection sensor 5NS4 is turned on.
Outputs write clock data (routine R13
29-R1333).

In other words, the first track TRC1 of the card has STX as the final data of the magnetic data transferred to the second track TRC2.
Even after writing the code, tarok data continues to be written until the end of the card (see Figure 2 (E)).
. On the second track side, since the magnetic data is not reversed after writing of the magnetic data is completed, the direction of magnetization is kept constant and the data is erased.

On the other hand, if the position detection sensor 5NS4 turns on before the timer overflows in routine R1329, the process advances to routine R1334, turns off (low level) the write permission signal to the magnetic head 821, and then stops the rotation of the motor 807. The process ends (routine R1335). Also,
If the timer set in routine R1328 times out before the position detection sensor S N 'S 4 is turned on, the routine jumps to R1336, sets the card jam in status 1 and error information, and then returns the 13th timer.
The process moves to the error handling routine shown in FIG.

FIG. 138(e) shows the specific procedure of the verify process performed subsequent to the write process in FIG. 138(d).

Here, first, the motor 8 is operated until the rear end of the card is detected by the first position detection sensor 5NSI in the card reader.
After reversing 07 and retracting the card, set a 1 second timer (routines R1341, R1342),
Then, the motor 807 is rotated forward at high speed, the number of magnetic data is set (here, 23 is sufficient since the STX code following LRC is not checked), and the second address of the magnetic data buffer is set in the address counter ( routines R1343-R1344). This is to exclude the first STX code from being verified.

After setting the address, execute the 1-bit read process shown in FIG. 138(f), determine whether the data read in routine R1346 and stored in the work area matches the STX code, wait until they match, and - when it does. Then the next routine R
Proceed to 1347. In routine R1347, 5 bits are set in the bit counter, and then 1 bit of magnetic data is read in the 1-bit read process shown in FIG. 138(f), shifted into the lowest bit of the work area, and then the bit counter is decremented. This process is repeated until the bit counter reaches "0", that is, until 5 bits are read (routines R1347 to R1349).

Then, using the address set in the counter in routine R1345, the magnetic data read from the magnetic data buffer is compared with the magnetic data read from the card and stored in the shift register (routine R1350).
. Here, if the two data do not match, routine R
After setting the verify error in the error information in step 1351, when the data matches again, the routine jumps from R1350 to R1352, increments the address counter of the magnetic data buffer, and sets the number of magnetic data to "1".
” and repeats the above routines R1347 to R1353 until the number of magnetic data reaches rQJ (routine R1
354).

When the number of magnetic data reaches rQJ, the routine advances to routine R1355 to clear the 1-bit read latch and erase the read data.

Routine R1356) is used to determine whether the one second timer set in routine R1342 has timed out, and the next routine R1357 is to determine whether the one second timer set in routine R1342 has timed out.
4 is turned on.

If the position detection sensor 5NS4 is turned on before a time-over occurs, proceed to routine R1358, clear the card jam pit in status 1, and then turn on the motor 8.
07 (routine R1359). On the other hand, if a time-over occurs before the position detection sensor 5NS4 is turned on, "1" is set in the "card jam pit" of the status 1, a card jam is written in the error information, and the process shifts to the error handling routine shown in FIG. 139. (routines R1360, R1361).

FIG. 138(f) shows a specific procedure of 1-bit reading processing common to the verify processing flow of FIG. 138(e) and the magnetic processing flow of FIG. 138(c).

In this process, first the 1-bit reading latch is cleared (routine R581), and then the size of the card is inspected based on the outputs of the sensors 5NSI to 5NS4 in the card reader (routines R582 to R588). Then, it is checked whether magnetic data is loaded in the read latch cleared in routine R581, and if it is, the work area to which the latch data is transferred is shifted to the left by one pin, and the least significant bit O is set as above. Transfer the latch data and end (routines R589 to R59)
0).

In the card reader of this embodiment, the distance Q3 between the first and third position detection sensors 5NS2 and 5NS3 is the normal card length Ω. longer than the second and third position detection sensors 5N
The distance Is Q4 between SI and 5NS3 is the regular card length Q.

The distance between sensors is set so that it is shorter than (
(See FIG. 30(A)).

Therefore, during the 1-bit reading process shown in FIG. 138(f), the first to third position detection sensors 5NS1 to 5NS
Card size defects are detected by checking the output of step 3 (routines R584 to R587).
).

FIG. 138(g) shows a specific procedure for punching a hole in the "punch hole" command reception flow shown in FIG. 137(G).

In this hole punching process, first the card is inserted into the card reader 800.
Move to the farthest end (routine R311) and punch ○
After clearing the Kt+ flag (routine R312),
Reverse the motor, start the timer (3 seconds) (routine R313), set the 'travel amount detection' flag, and clear the travel amount counter (routines R314 to R3).
18). Then, the "timer 2 operation" flag is set to enable a timer interrupt, the amount of movement is detected by the timer interrupt, and the rotation of the motor is stopped when the hole punching position is reached (routines R319 to R322). For 150m seconds to wait for complete stop - Chin R
323) and then activates the punch device 820 (routines R324 to R327).

After repeating the above routines R323 to R327 twice to ensure six openings (routine R328), the movement amount counter is cleared and the motor is reversed at high speed to direct the opened punched hole to the punched hole detection sensor 5NSp. move the card to Then, it is determined whether the punch hole detection sensor is on, and if the punch hole is in the correct position, the "Punch ○K tT flag is set, and then the first
When the position detection sensor SNS1 turns on and detects the rear end of the card, the timer interrupt is stopped and the motor is stopped (routines R329 to R340).
.

If a time-over occurs during card movement in the above routine, it is determined that a card jam (paper jam) has occurred, and error processing is entered (routines R315 and R332).

FIG. 138(h) shows the processing flow when receiving the "magnetic write" command in FIG. 137(C), the processing flow when receiving the "punch hole" command in FIG. 137(G),
137(H) and the processing flow when receiving the "card front ejection" command in FIG. 137(I).

In the transmission process, first, the reception buffer is prohibited from receiving data, and then the start address of the transmission buffer is set in the counter (routines R1421, R1422).6 Next, the transmission data saved in the transmission buffer during each of the above flows is After reading and transmitting 1 byte, increment the address counter of the transmit buffer (routine R14).
23°R1424). After that, it is determined whether the code CR indicating the end of the response command has been transmitted (routine R14).
25) If not yet, return to routine R1423 and proceed to the next step
Byte data is transmitted sequentially, and after transmitting the IL CRFl code, reception permission is given to the reception buffer, and the process returns to the original routine (routine R1426).

On the other hand, in Fig. 139, Fig. 136 and Fig. 137 (A)
138 (I) and FIGS. 138(a) to (g), specific procedures for error processing to be executed when an error occurs are shown.

In this error processing, the monitor display data, that is, the error display code (see Table 7) corresponding to the error information written according to the content of the error that occurred in each flow is read from the internal memory and displayed on the monitor display 175. to display the type of error (routine R1131
, R1132). Then, the OK clamp light is turned off, the "write inhibit" flag is set to "1" to inhibit magnetic data write processing, and the timer 2 interrupt is stopped to inhibit magnetic read processing (routines R1133 to R1135).
). After that, the motor 807 in the card reader 800 is stopped, the shutter solenoid 809 is turned off, the shutter is closed, and the entry of the card is prohibited, and then the response code corresponding to the type of error (see the right column of Table 7) is sent. transmission (routines R1136 to R1138) and returns to routine R1109 in the main flow of FIG. 136 (see reference numeral v2) Next, in FIGS. The figure shows the processing procedure when a write interrupt occurs.

As already mentioned, in the card reader 800 of this embodiment, the detection signal from the sensor 832 that detects the rotational speed of the motor 807 is input to the card reader control device 288 as an interrupt signal.

"Timer 2 operation" inside the controller in routine R524 during the card reading processing flow in FIG. 138(a).
If this signal comes in when the flag is set to Kl I I+, FIG. 139(A).

Execute the timer 2 interrupt processing in (B) and
), when the "write side write start" flag is set in routine R1308 during the write process flow, the 140th
The write interrupt processing shown in the figure is executed.

Note that the speed sensor 832 is provided opposite the rotary encoder 817 attached to the rotating shaft of the motor 807, and receives an interrupt signal every time the card moves 0.1 mm regardless of the rotation speed.

In the timer 2 interrupt processing, first, in routine R701, the "security read" flag and the "punch hole read" flag are checked, and if both are 'O', the mode is set to movement amount detection mode, and the process moves to routine R710, where the movement amount counter is incremented. The interrupt processing ends.The movement detection mode is set during the magnetic processing (routine R) shown in FIG. 138(C).
572) and FIG. 138(g) are performed when it is desired to know the amount of movement of the card from the reference position during processing (routine R317), and the "security reading" flag and the "punch hole reading" flag are set. By clearing, the movement amount detection mode is set. Also, timer 2
Interrupt processing is started and the ``movement amount detection'' flag is set to II O.
If jl, proceed to routine R702, increment the movement amount counter, and then check in routine R703 whether the ``Security reading'' flag is set. If it is set, proceed to routine R704, and if the movement amount is 4°8Wn or more. (If the "security reading in progress" flag is 0, the process moves to the punch hole reading routine shown in FIG. 140(B)). The "Pass security reading in progress" flag is set by the punch hole sensor SN in routine R523 during card reading processing in FIG. 138(a).
This is when Sp is turned on, and at this time the security code reading sensor 810a reads the security area of the card (
TF). Therefore, the first security mark is provided at a position 4.8 mm or more away from the starting edge of the security area. Therefore, in routine R704, it is determined that the amount of movement has become 4.8- or more. If 4.8■ or less, the interrupt processing is terminated and the movement amount counter is incremented again at the next timer 2 interrupt. Then, when the movement amount reaches 4.8 mm, the routine R
711, where first the movement amount and routine R519
Compares the reading range set in RAM with the reading range, and if it is within the reading range, determines whether the security code reading sensor is on, and if it is on, increments the counter that counts the width of the security code and interrupts. The process is ended (routines R712, R713), and when the code reading sensor is turned off, the counter value is checked (routine R714) and the width of the security code is “O”.
If it is P+, it is determined that there is no code, and the interrupt processing is terminated.

On the other hand, if the security width is not 0'', the counter width is moved to the buffer, the counter is cleared, and it is determined whether the security width is 0.5I or more (routine R
715, R716), here, if the width is 0.5 mm or less, it is regarded as abnormal, and if it is 0.5 m+ or more, tL I II is set in the most significant (or least significant) bit of the security buffer operated as a shift register. after that,
When the next timer interrupt is entered and the code goes out of the reading range in routine R711, it is assumed that the reading of the first code has been completed and the process moves to routine R721, where the number of security readings (counter) is decremented. Then, the security buffer storing the read code is shifted by one bit in routine R723, and the read range is added by the pitch (3, 5a++) of the security coat, and the process ends. By shifting the security buffer every time one security bit is detected, the serially read security code is converted into parallel data. By repeating the above routine, when the number of security reads reaches rQJ, the process proceeds from routine R722 to R714, and when the read security width is 0.5 nin, II 1'' is written to the most significant bit of the security buffer. After that, the process moves to magnetic data reading processing, and in routine R553 of FIG. 138(c), the "punch hole reading" flag is set to in 1 P+, the "security reading" flag is cleared to II OII, and then this FIG. When the timer 2 interrupt in (A) is started, the routine moves from routine R703 to routine R731 in FIG. 140 (B), and it is checked whether the punch hole detection sensor is on. The interrupt processing is ended by incrementing the counter that counts the number of punches.If the punch hole detection sensor is turned off at the next interrupt, the process moves to routine R733 to check the punch size. If the width of the hole is 0.8 mm or more, it is regarded as a regular punched hole, and 111 Pl is set to the most significant (or least significant) bit of the buffer (operated as a shift register) that stores the presence or absence of a punched hole in routine R734. After writing, if the width of the punched hole is less than 0.8mm+, the punched hole width counter is cleared in routine R735, and then the flow advances to routine R736.

Here, it is determined whether the card movement amount is within the reading range, and if it is, the above procedure is repeated, and if it is out of the reading range, the process moves to routine R741 and subsequent steps.

In routines R741 to R745, the number of read punch holes is first subtracted, the buffer containing the read bits is shifted by one bit, the punch six-width counter is cleared, the reading range is reset, and the process ends. And the number of reads is rQ
When the timer reaches J, the "timer 2 operation" flag is cleared and subsequent timer 2 interrupt operations are stopped (routine R7).
42°R746).

On the other hand, after the "write interrupt start" flag is set in routine R1308 during the write process flow shown in FIG. Then, the write interrupt process shown in FIG. 141 is started, and first, the write clock data set in routine R1310 or routine R1330 in the flow shown in FIG. 138(d) or the write data and write clock set in routines R1320 and R132 are Output the data (routine R751). After that, routine R1311, R1
“Waiting for writing” set with 322 or R1331
The flag is cleared and the write interrupt processing is ended (routine R752).

Note that in the above embodiment, the issuing machine 20 is included in the management device 400.
Although the same issuing device as the card issuing device 700 in 0 is provided, test cards and resurrection cards only need to be issued by punching holes and recording magnetic data without printing the amount or the like. (e.g. when using pre-printed or handwritten cards),
A magnetic head 821 and a punch device 8 as shown in FIG.
02 may be incorporated, and the card tank 901, card ejecting device 710, printing device 750, etc. may be omitted.

Furthermore, instead of incorporating the card issuing device 700 in the management device 400, the management device @ 400 sends a ``card recovery type packet ``test card issue'' packet to the issuing machine 200, and the issuing machine issues a resurrection card or a test card. You may also do so.

However, if it is installed in the management device, it will not interfere with purchases by general players.

[Effects of the Invention] As explained above, the present invention provides a card-type gaming system in which a card with only a code recorded at the time of card purchase is issued, and the number of balls held is stored in a management device.
The management device is equipped with a card issuing device having at least a card reader capable of writing magnetic data to the magnetic recording section of the card and a printing device capable of printing characters etc. on the surface of the card, and Since the configuration is such that special cards such as resurrection cards and test cards can be issued according to instructions, it is possible to check the history data of the player on the screen of the CRT display device of the management device and decide whether or not to reinstate the card. , while preventing fraud, restoring damaged cards, effectively protecting the interests of players without causing any disadvantage to gaming parlors, and thereby preventing troubles between players and gaming parlors. This makes it possible to improve the reliability of the card-based gaming system. Further, even when the machine is disconnected from the management device, it is possible to issue a test card that allows the pachinko machine to operate independently and to make a trial play, thereby improving the flexibility of the card-based gaming system. Furthermore, since the management device is equipped with a card issuing device, there is no need to use a issuing machine to issue resurrection cards or test cards, and there is no need to bother players who are trying to purchase cards for playing games. The effect is that there is no

[Brief explanation of the drawing]

FIG. 1 is a system configuration diagram showing the overall configuration of a pachinko gaming system to which the present invention is applied, and FIGS. 2 (A) and (B) are front views showing an example of a card used in the system according to the present invention. Internal configuration diagram, 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) FIG. 2 is an explanatory diagram showing an example of the configuration of a magnetic recording section in a card. FIG. 3 is a perspective view showing an example of the overall configuration of the pachinko machine that constitutes the gaming system; FIGS. 4(A) and (B) are cross-sectional side views showing an example of the configuration of the operation panel on the front of the pachinko machine; FIG. is an exploded perspective view of the operation panel section, FIG. 6 is a perspective view showing the internal structure of the operation panel section, FIG. 7 is a perspective view showing an example of the structure of the enclosed ball circulation device on the back of the pachinko machine, and FIG. Figure 9 is a perspective view showing details of the base of the ball launch rail, Figure 10 is a perspective view showing the pachinko machine with its front panel 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, Fig. 12 is a perspective view showing the configuration of the back side of the front frame of a pachinko machine, FIG. 13 is a rear perspective view showing an example of the configuration of the back side of a pachinko machine, FIG. 14 is a perspective view showing an example of the configuration of a pachinko machine control unit, FIG. 15 is a perspective view showing the internal configuration of the control unit, and FIG. Figure 17 is a perspective view showing the configuration of the front panel of the control unit, Figure 17 is a perspective view showing the mounting positional relationship between the pachinko machine and the control unit, and Figure 18 is a perspective view showing the framework of the island equipment where the pachinko machine is installed. , Fig. 19 is a perspective view showing the state in which a pachinko machine and a control unit are installed in the island equipment, Fig. 20 is a perspective view showing the back side of the island equipment, and Fig. 21 is a block diagram showing the control system of the entire pachinko machine. FIG. 22 is a block diagram showing an example of the circuit configuration of a pachinko machine control device, 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, and FIG. 26 is an exploded perspective view of the card reader; FIG. 27 is an exploded perspective view showing details of the card insertion section of the card reader; FIG. 28 (A) , (B) are cross-sectional side views showing the details of the card insertion part of the card reader, and FIGS. 29(A) and (B) are
) is a cross-sectional side view showing details of the shutter portion at the card reader entrance, FIG.
Figure (B) is a sensor detection timing chart when a card is inserted, Figure 31 is a block diagram showing an example of the circuit configuration of the card reader control device, Figure 32 is a block diagram showing the card reader interface circuit, and Figure 33 is a block diagram showing an example of the circuit configuration of the card reader control device. 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 shows the front panel of the issuing machine opened. FIG. 36 is a perspective view of the card issuing device installed in the issuing machine; FIG. 37 is a schematic configuration diagram of the card issuing device; FIG. 38 is a perspective view showing the state.
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. FIG. 2 is a perspective view of a pachinko parlor counter configured using a payment machine. Figures 45 (A) and (B) are explanatory diagrams showing an example of the configuration of a receipt issued by the payment machine, Figure 46 is a block diagram showing an example of the configuration of the control device of the payment machine, and Figure 47 is an explanatory diagram showing an example of the configuration of a receipt issued by the payment machine. FIG. 48 is a block diagram showing an example of the configuration of the unit control device; FIG. 48 is a perspective view showing an example of the overall configuration of the management device; FIG.
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 configuration of files in the device, FIG. 52 is an explanatory diagram showing the state transition of cards in the gaming system of the invention, and FIG. 53 is a block diagram showing an example of the configuration of the transmission system in the gaming system of the invention. Figure 54 shows N which controls data transfer on the network.
A block diagram showing an example of the configuration of an AU (network adapter unit); FIGS. Figure 55 (C) shows the management device-N on the low-layer network.
Block diagrams showing the packet structure between AUs and between the management device and the unit, FIGS.
B) is a configuration diagram of the “line test” packet, Figures 57 (A) and (B) are configuration diagrams of the “unit table request” packet, and Figures 58 (A) and (B) are the “initial value setting” packet. 59 (A) and (B) are configuration diagrams of "regular data requests" from the management device to the pachinko machine and their response packets, and FIGS. 60 (A) and (B) are "for various commands" Packet and its response “A CK” packet configuration diagram, Figure 61 (
A), (B), and (C) are the "card-in" packet and its response "A CK" and negative response "NAK"
"Packet configuration diagram, Figures 62 (A) to (D) are flowcharts showing the initialization procedure of the central processing unit and local processing unit in the management device, and Figure 63 is a flowchart showing the initialization procedure of the central processing unit and local processing unit in the management device. 64 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. 65 is a flowchart showing the processing procedure for periodic data request by timer interrupt; FIG. 66 is a flowchart showing the procedure for receiving scheduled data as a response, FIG. 67 is a flowchart showing the processing procedure when the management device receives the "Cart Purchase" packet, and FIG. 68 is a flowchart showing the processing procedure when the management device receives the "Cart Purchase" packet. Figure 69 is a flowchart showing the processing procedure when the management device receives the interrupt card-in packet. Figure 70 is a flow chart showing the processing procedure when the management device receives the interrupt switch packet FIG. 71 is a flowchart showing the processing procedure when the management device receives the "Paper Termination Switch" packet, and FIG. 72 is the flowchart showing the processing procedure when the management device receives the "Return to Zero" packet. FIG. 73 is a flowchart showing the processing procedure when the management device receives a “cancellation” packet, and FIG. 74 is a flowchart showing the processing procedure when the management device receives a “card payment” packet. FIG. 75 is a flowchart showing the processing procedure when the termination release switch on the top surface of the console is turned on in the management device, and FIGS. 79, 80, and 81 are flowcharts showing the processing procedure when the forced termination release switch on the top surface of the console is turned on in the management device, and FIG. 82 is a flowchart showing the processing procedure when the A flowchart showing the procedure for power outage processing in the management device when a power outage occurs. FIG. 83 is a flowchart showing the procedure for network error recovery processing in the management device, and FIG. FIG. 84 CB) is a flowchart showing the specific steps of the token bus recovery process in the process flow of FIG. 83. FIG. FIG. 86 is a flowchart showing the specific steps of the unit recovery process in the process flow of FIG. 83. FIG. 87 is a flowchart showing the specific steps of the code recovery process. Figure 88 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, and Figure 89 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. FIG. 90 is a flowchart showing the procedure for interrupt display processing of sales statistical data by timer interrupt; FIG. 91 is a flowchart showing the procedure for displaying data on the stop table; Figure 93 is a flowchart showing the procedure for data display processing for a specific machine, Figure 94 is a flowchart showing the procedure for displaying data for a red machine, and Figure 95 is a flowchart for a black machine. Figure 96 is a flowchart showing the procedure of data display processing of the issuing machine, Figure 97 is a flowchart of the procedure of data display processing of the payment machine, and Figure 98 is display of all business data. FIG. 99 is a flowchart showing the procedure for displaying data on a specific card; FIG. 100 is a flowchart showing the procedure for displaying total card data; FIG. 101 is a flowchart for displaying all card details data. FIG. 102 is a flowchart showing the procedure for displaying data of an interrupted card; FIG. 103 is a flowchart showing the procedure for generating a card number in the management device; FIG. A display screen configuration diagram showing an example of the screen configuration; FIG. 105 is a display screen configuration diagram showing a configuration example of an abnormal terminal display screen displayed on a CRT display device in the management device; FIG. 106 is a display screen configuration diagram showing a configuration example of an abnormal terminal display screen displayed on a CRT display device in the management device 107, 108, and 109 are display screens showing an example of the structure of the initial value setting screen displayed on the CRT display device in the management device. 110 is a display screen configuration diagram showing an example of the configuration of the discontinuation number setting screen displayed on the CRT display device in the management device; FIG. 111 is a display screen configuration diagram showing the discontinuation mode setting displayed on the CRT display device in the management device A display screen configuration diagram showing an example of the screen configuration; FIG. 112 is a display screen configuration diagram showing an example of the configuration of a date and time setting screen displayed on a CRT display device in the management device; FIG. 113 is a display screen configuration diagram showing a configuration example of a date and time setting screen displayed on a CRT display device in the management device FIG. 114 is a display screen configuration diagram showing an example of the configuration of a normal display screen during business operations, FIG. 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. 116 shows an example configuration of a pachinko machine forced termination cancel screen displayed on the CRT display device in the management device Display screen configuration diagram; Figure 117 is a display screen configuration diagram showing a configuration example of the issuing machine forced termination cancellation screen displayed on the CRT display device in the management device; 119 is a display screen configuration diagram showing a configuration example of a system termination screen displayed on a CRT display device in the management device; FIG. 120 is a display screen configuration diagram showing a configuration example of a system termination screen displayed on a CRT display device in the management device; FIG. FIG. 121 is a display screen configuration diagram showing an example of the configuration of a card restoration screen displayed on a display device; FIG. 121 is a display screen configuration diagram showing an example configuration of a display menu selection screen displayed on a CRT display device in the management device; FIG. 123 is a display screen configuration diagram showing an example of the configuration of a stopping platform display screen displayed on a CRT display device in the management device, and FIG. 123 is a display showing a configuration example of a specific platform display screen displayed on a CRT display device in the management device Screen configuration diagram. Figure 124 is a display screen configuration diagram showing an example of the configuration of an all-device data display screen displayed on a CRT display device in the management device. Figure 125 is a display screen configuration diagram showing red line data displayed on a CRT display device in the management device. 126 is a display screen configuration diagram showing an example of the configuration of a display screen; FIG. 126 is a display screen configuration diagram showing an example of the configuration of an issuer data display screen displayed on a CRT display device in the management device; FIG. 127 is a CRT display in the management device 128 is a display screen configuration diagram showing a configuration example of a payment machine data display screen displayed on the device; FIG. 128 is a display screen configuration diagram showing a configuration example of a business data display screen displayed on a CRT display device in the management device; Figure 130 is a display screen configuration diagram showing an example of the configuration of a specific card data display screen displayed on a CRT display device in the management device, and Figure 130 is a configuration example of a card details data display screen displayed on the CRT display device in the management device. FIG. 131 is a display screen configuration diagram showing an example of the configuration of an interrupted card data display screen displayed on a CRT display device in the management device; FIG. 132 is a control procedure by the card issuance control device in the management device 133 is a flowchart showing the first
134 is a flowchart showing a specific control procedure when a "card restoration" function is received in the flow of FIG. 32; FIG. 134. FIG. 134 (B) is a flowchart showing the specific steps of the reader control process in the flow of FIG. 133. FIG. 134 (C) is a flowchart showing the specific steps of the card reversal process in the flow of FIG. Figure (D) is a flowchart showing the specific steps of the printing process in the flow of Figure 133, and Figure 134 (
E) is a flowchart showing the specific procedure of card ejection processing in the flow of Fig. 133, and Fig. 135 is executed when an error occurs during each processing flow of Fig. 134 (A) to (E). A flowchart showing the specific procedure for error handling. Fig. 136 is a flowchart showing a common control procedure for the card reader control device in the management device, issuing machine, and payment machine. Fig. 137 (A) shows the flow when receiving a "magnetic read" command. 3 is a flowchart showing a specific control procedure of the card reader control device. Fig. 137 (B) is a flowchart showing the specific control procedure of the card reader control device when receiving the "reload" command, and Fig. 137 (C) is the specific control procedure of the card reader control device when receiving the "magnetic write" command. Flowchart showing the procedure, FIG. 137(D) is a flowchart showing the specific control procedure of the card reader control device when receiving the "Status request" command, FIG. 137(E) shows the card when receiving the "Punch hole request" command 137 (F) is a flowchart showing the specific control procedure of the card reader control device when receiving the "Y Security Request"command; FIG. 137 (G) is the "Punch Hole FIG. 137 (H) is a flowchart showing the specific control procedure of the card reader control device when receiving the "open card"command; Figure (I) is a flowchart showing the specific control procedure of the card reader control device when receiving the "r card forward ejection" command. 138(b) is a flowchart showing the specific procedure of the parity/(, LRC inspection process in the flow of FIG. 137(A), FIG. 138(c) is the flowchart of FIG. 137(B) 138(d) is a flowchart showing specific steps of magnetic processing in the flow of FIG. 137(C), FIG. 138(e) is a flowchart showing specific steps of magnetic processing in the flow of FIG. FIG. 138(f) is a flowchart showing the specific steps of the verify process in the flow of FIG. 138(c) and FIG. 138(e); Figure 138 (g) is a flowchart showing the specific procedure for drilling holes in the flow of Figure 137 (G), Figure 138 (h) is a control flow of Figures 137 (A) to (I), etc. FIG. 139 is a flowchart showing specific steps for error processing when an error occurs in the control flow of FIGS. 137(A) to (I). FIG. ), (B) is a flowchart showing the timer interrupt processing procedure for magnetic reading in the card reader controller, and FIG. 141 is a flowchart showing the procedure for write interrupt processing during magnetic writing in the card reader 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 ... Cart reader control device, 195 ... Pachinko machine control device, 190゛° ... Unit controller, 200 ... Card issuing machine, 700 ... Card issuing Device, 710...
Card ejecting device, 740... Cart reversing device, 75
0... Printing device, 770... Cart deriving 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 port, 807... Conveyance motor, 809...
Shutter solenoid, 820... Punch device, 82
1...Magnetic head. lz-1+10 , ], ・:1'' 2nd (A) Fig. 24 (B) Fig. 24 Fig. 34 (A) Fig. 28 (B) (A) No. 29 (B) ΦU-t QOuJ L (One) Σ (A) Figure 45 (B) Figure (A) (B) Various command packets CK Figure 61 (A) "Card-in" packet configuration Management device ← NAU (Card No.) NAU ←Control unit (card NO) Figure 61 (B) "Card-in" packet configuration (affirmative response) Management device → NAU (ACK 10 card text) NAU → Control unit (ACK 10 card text) Figure 61 (C ) "Card-in" packet configuration (negative response) Management device → NAU (NAK) NAU → Control unit (NAK) Figure 103 Figure 133 Figure 137 (Japanese)

Claims (1)

[Claims] (1) Valuable data substantially equivalent to the amount of money or the number of balls is managed in a management device for each identification code given to the card, and in pachinko gaming machines, the above data is managed based on the identification code read from the card. In a pachinko gaming system that enables gaming within the range of valuable data obtained from a management device, the management device is connected to a master control device, a local processing device, an input operation device, a display device, a magnetic storage device, and a printing device. , an auxiliary power supply device, and a transmission control device, and a key for issuing a test card issuance command is provided on the back of the input operation device, and a key for issuing a card restoration command is provided on the top surface of the input operation device. Management device for formula game system.