JP2663203B2 - Storage media type game equipment - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial Application Field] The present invention relates to a storage medium type game facility using a game machine such as a pachinko machine, an arrangement ball, a slot machine, etc., and particularly to a storage medium in which required data is written. In addition, the present invention relates to a technology that is effective when used as a management device in a storage medium type game facility capable of playing a game.

[Prior Art] In recent years, a card-type pachinko game system has been proposed as an example of a storage medium-type game facility in which a game is played using a card-shaped storage medium as a medium. The card method is
The player only needs to carry the card that is the storage medium,
There is an advantage that it is possible to reduce the trouble of carrying a large amount of pachinko balls that easily fall. Conventionally proposed card-type pachinko gaming systems are roughly divided into the following two types.

In the first method, when issuing a card, the number of balls held corresponding to the purchase amount is stored in the card, a pachinko game is performed within the range of the number of balls held, and the number of balls held is increased or decreased in the game process. (See JP-B-47-42227).

The second method of the card method is to issue a card in which only the code number is recorded at the time of card purchase, store the number of balls held in a central management device, and insert the card into a card reader of a pachinko machine. The stored number of balls is called so that a game can be played. In such a case, when the card is issued, all the purchase amount is converted to possessed balls, and the number of possessed balls is stored in the management device side (Japanese Utility Model 61-61).
No. 32709, JP-B-51-17106).

[Problem to be Solved by the Invention] Among the above conventional card systems, in the first card system in which the number of balls held is stored in the card itself, the card itself or its magnetic surface is damaged, If the data on the magnetic surface is destroyed by the noise, it becomes impossible to read the ball number data. In this case, even if the damaged card is shown to a game store clerk, there is no way for the game store to check the number of balls held. Therefore, if countermeasures are taken to restore the number of balls possessed by relying on the player's offer, there is a risk that the game shop will suffer a great deal of damage due to the illegal offer of the player. For this reason, in this method, it is inevitable to take measures for not compensating for a damaged card. As a result, the player is entirely liable for the card damage, and if the card is accidentally damaged, the player has to be willing to enjoy the damage. Further, in order to avoid such an unexpected disadvantage of the player, the only option is to make the card highly durable or to keep the maximum issue amount of the card low. However, this increases the cost of issuing cards for amusement stores, and increases the number of times a card is purchased for a game player. there were.

On the other hand, in the second card system in which a 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, the card or its magnetic surface is damaged or magnetic data is lost. If destroyed, the code number on the card cannot be read. Therefore, even if there is a number of balls in the memory of the management device, it is difficult to retrieve the data.

Therefore, in a conventional card system in which a code number is stored in a card, it is virtually impossible to recover a damaged card. As a result, the same problem as in the method of storing the number of possessed balls on a card has occurred.

However, letting the player take full responsibility for the card damage is monetary, and if the card is damaged in an unexpected situation, trouble may occur between the player and the game store. Is high. In particular, in the method of storing the number of possessed balls in the memory of the management device, if the card is damaged when the player acquires a large prize ball, the damage to the player becomes extremely large. Therefore, it is desired that a card-type gaming system be provided with means for recovering cards. However, if you open the way to resurrection of cards easily, you have to be careful because there is a risk that the game store will be damaged by fraud.

Also, in the case of a gaming system in which all terminals (pachinko machines, card issuing machines, payment machines) are managed under the control of a management device in a card-type system, the pachinko machine is connected between the management devices. Then, the state shifts to the operable state by exchanging the card number and the like, and the terminal alone becomes inoperable. However, since pachinko machines are frequently used, jamming and so-called tulips and other accessories often break down, and it is necessary to adjust the nails in the game area to adjust the ball launch rate. In that case, a trial shot is performed after repair or nail adjustment. Therefore, a test card that enables trial hitting is required separately from a normal game card.

The present invention has been made under the above background,
Paving the way for the recovery of damaged storage media while preventing fraud,
Effectively protect the interests of the game players without causing disadvantages to the game stores, thereby preventing troubles between the players and the game stores and improving the reliability of the storage media type game equipment, The management device can issue a special storage medium that allows the game device to operate independently and enable trial hitting even when disconnected from the management device, thereby improving the flexibility of the card-type gaming system. The purpose is to let them.

Means for Solving the Problems In order to achieve the above object, the present invention provides a terminal device such as a storage medium type game device capable of playing a game in relation to a storage medium on which required data is written, and the terminal device. Storage device provided with a management device that manages the data, the management device includes a storage medium writing unit that can write data into at least an information storage unit of the storage medium, and information storage by the storage medium writing unit. Storage medium issuing means for issuing a storage medium which can be used by writing data to the storage unit, wherein the storage medium issuing means transmits data of the storage medium which has become unusable to an information storage unit of a new storage medium. To a reissue storage medium which is made to have a playable qualification by writing to the storage medium, or a storage medium device in a state where the storage medium type gaming device and the management device are electrically disconnected. The special storage medium which is qualified to test the device independently can be issued.

[Operation] According to the above-described means, for example, by writing data of a storage medium that has become unusable to a recording information section of a new storage medium, it is possible to reissue a storage medium having a qualification for play, Even if an accident such as breakage of a storage medium occurs, the profit of the player can be effectively protected. In addition, a special storage medium capable of operating the storage medium-type gaming device alone when the storage medium-type gaming device and the management device are not electrically connected can be issued. The test operation of the gaming device can be performed without operating the whole. In addition, since the management device is provided with the storage medium issuing means, the clerk of the game store can issue the reissued storage medium or the special storage medium while the business is open, and execute the respective processes. It becomes possible.

[Embodiment] FIG. 1 shows an embodiment of a card-type pachinko gaming system as an example of a storage medium-type gaming facility to which the present invention is applied.

The pachinko gaming system of this embodiment is a pachinko machine 100 as a storage medium type gaming device and a storage medium issuing device for issuing a card CD as a storage medium having a local value in order to start a game in each pachinko machine. Centralized management of the above issuing terminals 200, the prize balls obtained as a result of the game and the payment machine 300 as a storage medium payment device for payment of the remaining purchase money not used in the game Management device 400 that controls and controls
00 and a data transmission path 500 as a transmission means for organically coupling each terminal, and these constitute an organic coupling unit. This organic combination can be interposed only by the card CD, and the card can be operated and its valuable data can be converted only by the organic combination. Therefore, the pachinko machine 100, the issuing machine 200, the settlement machine 300, and the management device 400, which are the respective components of the organic binder,
Are provided with a card reader as a storage medium reader (in this specification, a card reader which writes data on a magnetic surface of a card is also referred to as a card reader), as well as information on the card and information on each terminal. The management device 40
0 is stored in the form of a file in the storage device.

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

Card CD used in the storage medium type game facility of this embodiment
Is, for example, as shown in FIG.
The information required for the player, such as the date of issue (= valid date), DATE, and the issue serial number n, etc., required when the damaged card is restored, are printed at the time of issuance. (Longitudinal direction).
Therefore, there is no need to prepare a plurality of types of cards on which different amounts of money are printed in advance.

Immediately above the print display unit PRT, a punch as a punch forming unit for recording the status of the card, that is, issued, resurrected, playing, returning to zero (zero), and settlement or status transition of the card in the form of a punch. A hole forming area PH is also provided along the card insertion direction.

By detecting the above-mentioned perforations formed in the card with the photoelectric detector, the number of balls held is read from the file of the management device using the code recorded on the magnetic surface, and the state of the card can be easily checked without checking. Thus, it is possible to reduce the burden on the controller and the management device of the card reader required to determine the processing corresponding to the state of the card.

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

Further, in the card of this embodiment, a belt-like roller running area RRA slightly wider than the transport roller in the card reader is provided between the print display section PRT and the magnetic recording section MG, that is, in the center of the card, in the longitudinal direction of the card. The magnetic recording unit MG, the print display unit PRT, and the authenticity discrimination area TF, which have important information used for determining the card, are damaged due to contact with the transport rollers. To prevent the information from becoming unreadable.

In the card of this embodiment, a true / false discrimination area TF including a security mark concealed in characters such as a hole name printed on the surface of the card is provided below the magnetic recording unit MG. In other words, "PLAZ" printed on the surface of the card
The A "as the character, the legs of each character as shown in FIG. 2 (C) is then designed to come to a position corresponding to the detection bit pattern B ₀ .about.B ₉ provided at a pitch of 3.5mm, etc. Print it out. And the character width is 0.5-1.5mm,
It is set to 3.5 mm, and "1" or "0" of each bit is represented by shading of characters. Moreover, 10 5 th bit B ₄ from left of the bit and the last bit B _9, the bit B ₀ .about.B ₃
Previously determining the shading of text to represent the parity of the B ₅ .about.B ₈ and. It is more preferable that the security bits concealed in the character string be formed using a special ink that can be detected only by the sensor and cannot be distinguished by human eyes.

Further, on the surface of the game card of this embodiment, a head cleaning area HCN is provided in which a cleaning agent for removing dirt on the magnetic head is applied to a band-shaped area continuous with the magnetic recording section MG. At the same time, in the card of the embodiment, as shown in FIG. 2 (D), the magnetic recording portion MG is placed on a base material 11 made of a plastic such as polyester so as not to know where it is provided. A white layer 13 is formed on the magnetic layer 12 by uniformly applying the particles, and a pattern printing layer 14 is further placed thereon, and then a part thereof (a portion corresponding to the print display part PRT) is subjected to heat-sensitive coloring. A layer 15 is formed, and a transparent protective film 16 is coated thereon. A cleaning agent of the same color as that of the white layer 13 is applied to the cleaning area HCN, and the surface thereof is exposed so that the protective film 16 is not coated, and the cleaning area hardly changes in color from other parts. In this way, the beauty is improved. Also,
A pattern printing layer 17 is formed on the back surface of the base material 11 of the card, and is coated with a protective film 18 thereon.

In the 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 white layer 13, so that the pattern is It is possible to provide a card with rich fashion by printing, and has a function of concealing the magnetic recording unit MG.

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

FIG. 2 (E) shows a magnetic recording section MG provided on the card.
An example of the configuration will be described.

The magnetic recording unit MG of the card of this embodiment is composed of two tracks, of which the first track TRC1 records clock data for giving a sampling timing.
The second track TRC2 includes, starting from the left, a 4-bit start code and a field STX containing the parity bit, a company code MKC indicating the card reader manufacturer, a device code MCC indicating the model of the card reader, and an identification code DSC of the game store. , Date DATE, card number No, issuance command code FNC given from the card reader when the card is issued, text field TXT containing security data SDC read from the authenticity discrimination area, field ETX containing text end code, text It is composed of a field LRC containing an exclusive OR value (detection code) of data and an end code, and a field STX containing a start code. In addition, the date P is provided with a bit P indicating each parity every four bits, and the first four bits represent "month" and the sixth to ninth bits and the eleventh bit represent "month". The date, and the 12th to 14th bits and the 16th to 19th bits are recorded by binary coding the last two digits of the year.

In the case of a card having a magnetic recording section, it is generally easiest to decode the recording format and recording data from the date. However, in the card of the above embodiment, the order of the date is changed, and the parity is set every 4 bits. Put a bit,
Further, since the correspondence of the recording bits is changed, forgery of the card becomes extremely difficult. The issue serial number n
Is printed on the print display unit PRT, so that the card can be restored from the file information of the management device even if the information in the magnetic recording unit MG cannot be read due to damage to the card or the like.

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

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

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

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

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

The operation panel 110 is, as shown in FIG.
The inside of the operation panel 110 which is attached to the openable front panel 105 at the bottom of the lower part and has a hollow shape with a triangular cross section, and the upper surface is inclined downward toward the front so that the display is easy to read. Wiring boards 120A and 120B are provided in parallel with the display surface 110a, a money amount indicator 111 and a sphere indicator 112 each composed of a 7-segment LED on the board 120A, and the switches 113 to 112 on a board 120B. 115 and a built-in lamp are attached and covered with a display plate 117. A portion of the display plate 117 corresponding to the indicators 111 and 112 is a transparent window 117a, and a portion corresponding to the switches 113 to 115 is an opening 117b (see FIG. 5). And
An operation button 118 is mounted in the opening 117b so as to cover above the switches 113 to 115. Reference numeral 121 denotes a built-in lamp corresponding to the purchase switch 113.

Further, at the front end of the operation panel 110, a game state display section 116 in which a display lamp 123 is covered with a translucent Fresnel lens 119 or the like is provided, and the display lamp 123 operates the operation dial 104 of the hitting ball firing device 103. It is lit when turned.

Further, an operation button 125 having a built-in stop switch 124 is mounted on a side portion (the left side in the embodiment) of the operation panel 110, and when the switch 124 is turned on, an accessory provided in the game section is activated. Commands relating to the game, such as stopping the operation, can be given. The stop switch 124 is mounted on a wiring board 120C provided in the operation panel 110, and a wiring group 126C extending from the wiring board 120C and a wiring group 126A extending from each of the boards 120A and 120B. 126B is pulled out to the outside, and can be connected to a pachinko machine control device 195 arranged at the lower part of the back of the pachinko machine via connectors 127A to 127C connected to its ends.

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

 FIG. 13 shows a configuration example of the back surface of the pachinko machine 100.

A game board in which a plurality of winning ball collecting troughs 131 covering a plurality of winning ball derivation holes formed so as to penetrate the game board corresponding to a winning area provided in a game area on the front of the game board are held by a frame 106. It is attached to the back of. Winning ball assembly gutter 13
The bottom wall 1 is inclined downward toward the center to form a guide shelf 131a, below which an out ball gutter 132a, a first safe ball gutter 132b, and a second safe ball gutter 132c are integrally formed as shown in FIG. The formed guiding gutter 132 is provided. This gutter 132
In the middle of each gutter, a photoelectric out sensor SNS1, a first safe sensor SNS2, and a second safe sensor SNS3 each comprising a pair of light emitting and receiving devices are mounted. In addition, guide gutter 13
2 is a merging gutter section 132d that collects the balls flowing into each gutter at one place
The end of the merging gutter section 132d is connected to the upstream side of the guide gutter 133 which is gently inclined to align the pachinko balls in a line as shown in FIG. 7, thereby forming the sealed ball circulation device 130. Have been. On the upstream side of the guide gutter 133, a foul ball receiving port 13 provided at an upper end of the firing rail to collect a so-called foul ball in which a hit ball hit along the firing rail returns toward the rail base.
Foul ball gutter 1 installed facing 4 (see Fig. 9)
The ball 33a is formed integrally, and the foul ball merges with the ball that has flowed down onto the guide gutter 133 via the guide gutter 132. Fal sensor in the middle of fal ball gutter 133a
SNS4 is provided.

And, at the lower end of the guide gutter 133, there is a storage portion 135a for one ball, facing the lower end of the guide gutter 133, and a ball feed 135 for separating the balls on the guide gutter 133 one by one and allowing the balls to flow downward can swing. Mounted on A stopper 136 is fixed behind the ball feeder 135 to prevent the ball feeder 135 from rotating more than necessary.
When the ball 35 rotates downward by the weight of the ball that has flowed in, the upper end surface can prevent the ball from flowing down on the guide gutter 133. Further, a rotatable ball leveler 137 is attached in the middle of the guide gutter 133, and a slide type ball removing mechanism 138 is provided downstream.

As shown in FIG. 8, when the enclosing ball circulation device 130 is mounted on the back surface of the frame board 109, the ball removing mechanism 138 slides laterally by a blocking piece 148 protruding from the back surface of the frame board. He was blocked and could not remove the ball. The enclosed ball circulating device 130 is mounted so as to be able to rotate as a whole by a hinge portion 139 provided on one side (the right side in FIG. 8), and is rotated backward around the hinge portion 139. When moved, the ball removal mechanism 138
Slide to remove the ball. Moreover, the guide gutter 133
An elastic locking piece 133a is fixed to the end of the frame board 109. By engaging this with the engaging step portion 149 of the frame board 109, the sealed ball circulation device 130 can be fixed so as not to rotate. .

The pachinko balls separated by the ball feed 135 pass through ball passage holes 139 (see FIG. 9) formed in the frame board 109 disposed behind the front panel 105 and are fixed to the front of the frame board at an angle. One of them flows down to the base of the fired rail 140. Then, the firing rod 103a is disposed so as to face the base of the firing rail 140 (see FIG. 10). At the same time, below the base of the firing rail 140, there is provided an interlocking member 141 having a push-up piece 141a which is rotated in conjunction with the firing rod 103a and pushes up the ball feed 135 upward.

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

In addition, on the upper end of the frame board 109, the mounting portion 1 of the game board
09a is provided, and game board positioning projections 145 are provided upright at both ends. Also, along the upper end of the frame board 109, a frame engaging portion 146 having a groove with which the frame 106 for holding the game board can be engaged is formed. As shown in FIG.
By lowering the frame 106 along the positioning protrusion 145 from above, and engaging the lower end with the groove of the frame engaging portion 146, the two can be connected. On the side wall of the frame 106, four locking members 106a for detachably engaging a game board are provided.
The game board held on the mounting portion 109a of the frame board 109
The fastening device 147 is tightened and fixed in a state of being placed on the fixing device.
Note that a speaker 150 for generating sound effects related to the game is provided on one side of the front of the frame board 109 (the left side in FIG. 9).
Is attached.

On the other hand, a front panel 105 covering the front of the frame board 109
As shown in FIG. 10, is mounted at the lower part of the opening framed by the holding frame 108c inside the front frame 108 so as to be openable and closable with one end (left end) as a fulcrum.
A firing rail frame 151 positioned above is fixed, and a cutout 151a is provided in the middle of the firing rail frame 151 so that the firing sensor SNS5 can face the inside of 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. Above the front panel 105 in the front frame 108, a glass frame 154 is similarly openably opened. on the other hand,
On one side of the rear surface of the front frame 108 opposite to the hinge portion 102, a
As shown in FIG. 12, a locking device 156 for locking the front surface to the machine frame 101 and a locking device 157 thereof are mounted. Reference numeral 155 denotes an opening lever of the glass frame 154.

On the back of this front frame 108, a frame 1 holding a game board
06 (see FIG. 11) and the frame board 109 are joined to the fitting receiving portion 108b on the back of the front frame so that the fitting projection 106b on the back of the frame and the fitting projection 109b on the back of the frame board are aligned, and screwed. By doing so, the front frame 108, the frame 106 holding the game board, and the frame board 109 are integrated.

FIG. 13 shows the frame 1 on the back of the front frame 108 in this way.
06 and a state where the frame board 109 is attached, a winning ball collecting gutter 131 is further mounted on the back of the game board held by the frame 106, and a pachinko machine control device 195 is provided below the frame board 109. It is arranged. Further, a game control device 158 and a relay board 159 are mounted on the back surfaces of the frame 106 and the winning ball collecting gutter 131.

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

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

In the storage frame 161, a speaker 166 and a card reader 80 are provided.
0 is built in, and a card insertion / ejection opening 802a of the card reader 800 is exposed on the front surface of the storage frame. A card holding display lamp 167 above the insertion / ejection opening 802a indicates whether or not there is a card in the card reader. Below the card insertion / ejection opening 802a, a card insertion indicator lamp 168 for indicating whether or not a card can be inserted into the control unit 160 is arranged.

Furthermore, the front panel 16 of the storage frame 161 of the control unit 160
Inside 1a, a test switch 179 for enabling a game operation using a test card described later is arranged in a peculiar state in which the pachinko machine 100 is separated from the management device 400, and the test switch 179 is provided on the front of the storage frame. Pin insertion hole 169 for enabling the switch to be turned on externally using a pin
And a nameplate indicating the machine number given to the pachinko machine
170 are provided respectively.

Then, inside the front panel 161a of the control unit 160, a setting switch 171 for the machine number displayed on the machine name plate 170 as shown in FIG. 15, the status indicator 162, the analog indicator 163, and the safe Built-in lamp group L11 to L of lamp 164
A lamp substrate 172 having 15, L21 to L28, L31, L32 (see FIG. 16), the speaker 166 and the card insertion lamp 168
The holding substrate 173 is mounted. Also, call button 1
A call switch 165a is provided behind 65.

Further, a card reader 800 and a unit controller 190 for controlling the entire control unit 160 are provided in the storage frame 161.
The control unit 180 includes a unit control unit 180 having a communication unit, a transmission unit, and monitor displays 174, 175, and 176, a card reader control unit 188, and a power supply unit 177. Further, below the card reader 800, a storage box 178 for perforated pieces generated when a perforation is performed by a perforation device (described later) in the card reader is detachably arranged. A card ejection switch (not shown) for instructing the card reader to forcibly eject a card is provided on a substrate constituting the card reader control device 188.

The control unit 160 has a locking tool 179a and a release lever 179b provided on a free end side of the front panel 161a,
The release lever 179b faces the opening 161b formed at the lower end of the front panel 161a. The control unit 160 is mounted on the machine frame 101 of the panel machine 100 and the unit mount 24 at the same height as the frame 101, as shown in FIG. Are arranged so as to be flush with the front frame 108 of the pachinko machine. Therefore, the opening 161b of the front panel 161 facing the release lever 179b is normally closed on the upper surface of the front frame 108, and the front frame 1
By opening 08, the opening 161b is exposed, and the release lever 179b can be operated. This eliminates the need for the control unit 160 to be provided with a locking device.

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

In the control unit 160 of the embodiment, an optical fiber connector 186 and a coaxial cable connector 187 are provided on the back surface of the storage frame 161 in order to perform data transmission using any transmission path (FIG. 20). reference).

FIGS. 18 to 20 show an example of an island facility on which a gaming machine including the pachinko machine 100 and the control unit 160 is mounted, and a state in which the gaming machine is equipped therewith.

In the island facility of this embodiment, a plurality of pillars 22 are erected on the base 21 at intervals equal to the width of the gaming machine, and 60 cm from the floor.
A horizontal mounting table 23 is fixed at a height of about a level by a column 22. In addition, above the mounting table 23,
A first equipment shelf 24 is fixed at a position separated by the height of 101, and a second mounting shelf 25 is further fixed above the first mounting shelf 25 by a column 22, and a first mounting shelf 25 is fixed above the second installation shelf 25. Is pillar 22
A top plate 26 is fixed so as to cover the upper end of the top plate. In addition, the front end of the mounting table 23 is configured to protrude slightly forward from the support 22, and the first mounting table 24 has a front end that is closer to the machine frame than the support 22.
It is configured to be located rearward by the thickness of 101.

Then, the pachinko machines 100 are mounted together with the machine frames 101 on the mounting tables 23 between the columns 22, and the control unit 1 extends from the first mounting table 24 to the machine frames 101 on the same plane as this.
60 is placed. A transmission line (not shown) constituting a local network extends on the second installation table 25,
In addition, a transceiver 185 for transmitting data to and from the management device 400 via the transmission path is mounted between the columns 22. The front of the transceiver 185 is closed by the upper plate 27, and the lower part of the mounting table 23 is closed by the lower plate 28.

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

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

In the figure, reference numeral 188 denotes a transport motor 807 and a magnetic head 82, each of which is a component of the card reader 800 shown in FIG.
1. A card reader control device for controlling the punching device 820 and the like. Then, various switches 171, 179, indicators 162, 163, 164, 168, and speakers 16 provided in the card reader controller 188, the pachinko machine controller 195 and the control unit 160 are provided.
6 is controlled by the unit controller 180.

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

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

Under the control of the pachinko machine control device 195, the amount indicator 1
11, a ball number display 112, a purchase lamp 121, a game state display lamp 123, a control device 194 of the hit ball launching device 103, and an accessory control device 158 are placed, and a purchase switch 113, an interruption switch 114, and an end switch 115. Signals from ball detection sensors SNS1 to SNS5 such as pachinko machine
The waveform is shaped by 195 and supplied to the unit controller 180. In this embodiment, the power supply system is set to two systems of 24 V AC and 100 V AC, and the pachinko machine 100 side
24 V AC is supplied, and 100 V AC is supplied to the control unit 160 side. Separating the power supply in this way prevents the pachinko machine control unit from being inadvertently destroyed by the influence of the power supply in a pachinko parlor having many problems in the power supply system.

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

The pachinko machine control device 195 includes a pachinko machine controller CPU1 composed of a microcomputer, a reset circuit RST1 that monitors a regular watchdog pulse output from the controller CPU1 and generates a reset signal when the pulse is interrupted, A multiplex transmission controller CNT1 provided with parallel-to-parallel conversion means for converting parallel transmission data to serial data and serial-to-parallel conversion means for converting serial reception data to parallel data in order to enable optical data transmission with the unit controller 180. And a photoelectric conversion circuit OET connected to the optical cable 191 via the optical connector 193,
A filter circuit FLT that cuts noise of detection signals from various sensors, decoders DEC1 and DEC2 that decode display data to the money amount display 111 and the ball number display 112, and a display driving signal are formed based on the output thereof. Driver DRV1, DRV2
And a driver DRV3 for generating a drive signal for the hitting ball launching device 103.

Regarding the processing of the detection signal from the sensor in the pachinko machine control device 195, the noise is simply removed from the detection signal, shaped into a fixed pulse width, and then sent to the unit control device 180 as detection data of a launch sphere, a safe sphere, or the like. . In other words, the pachinko machine control device 195 does not calculate the number of safe balls or the like, and such calculation is performed on the unit control device 180 side.

In pachinko machines, noise is likely to occur due to static electricity, but a reset circuit that monitors watchdog pulses
Pachinko machine controller due to noise etc. due to RST1
Even if CPU1 goes out of control, a reset signal is generated and the CPU
Is initialized, runaway can be prevented.

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

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

The unit controller 180 is a unit controller 190 that comprehensively controls the card reader controller 188 and the pachinko machine controller 195 to enable pachinko gaming with cards, and data that performs control related to data transmission with the management device 400. The transmission controller 551 includes a network controller 553 for establishing a transmission / reception right in a network and performing serial / parallel conversion of data under the control of the data transmission controller. And the transfer of data between each controller 190 and 551 and between 551 and 553,
It is configured to run via dual port memory (RAM) 550 and 552. Of which, memory 552
Is divided into a transmission data storage area and a reception data storage area. An adjustment function for equalizing all transmission / reception data lengths (packetization) and a high-speed data transmission (2.
It has a buffer function to measure 5Mbps).

The 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 regular data transmission packet. On the other hand, pages 2 and 3 are used alternately for data packet reception. The data transmission controller 551 instructs the network controller 553 on which page to use. Data transmission controller 5
Even if the next packet data is sent during the processing of the received packet data by 51, all the packets can be received reliably because they are received by another page. A common reset circuit 555 is provided so that the controllers 551 and 553 can be initialized at the same time.

On the connection side of the network controller 553 with the management device 400, an optical connector is provided via a signal conversion circuit 554 and a changeover switch 542 which perform waveform shaping of received data and level conversion of a signal in order to increase the drive capability of transmitted data. A branch circuit 540 which is connectable to 186 and separates and couples a transmission signal and a reception signal via a changeover switch 542 so as to cope with a case where the transmission line of the low-layer network is constituted by a coaxial cable. Can be connected to The optical transceiver 185 shown in FIG. 20 is connected to the optical connector 186.

Further, a data transmission controller 5 is provided between the data transmission controller 551 and the network controller 553.
A latch circuit 561 for the network controller 553 to store the data reception result in response to a request from 51,
A data transmission controller 551 displays a latch circuit 562 for storing a command such as a data transmission command to the network controller 553 and a latch circuit 563 for storing a low-layer network address, and displays an abnormality in a communication control state in the unit control device 180. Is provided with a latch circuit 564 for storing display data to the monitor display 556 composed of three LED lamps. A decoder 557 decodes an address given to each of the latch circuits 561 to 564 and generates a selection signal.

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

Furthermore, the unit controller 190 has a data bus 5
Latch circuit that latches the display data (segment data and common data) of the monetary value and number of balls display via 81
574, a purchase lamp, a game state display lamp, a latch circuit 575 for latching a control signal for the hit ball launching device, and input signals from various switches provided in the pachinko machine 100 and the control unit 160 at a predetermined timing on the data bus 581.
An input / output controller 576 for latching output signals for mounting on top or displaying various lamps, and a control unit 160
A latch circuit 577 for latching audio data and the like generated from the speaker 166 is connected.

582 is a voice 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.The voice synthesis LSI 582 stores multiple voice data in a built-in EPROM. In response to the selection signal (S0 to S3) given from the unit controller 190, the audio data is selected, the audio signal is output in synchronization with the start signal ST, and the output is stopped by the reset signal R.

558 is a program ROM storing a control program of the unit controller 190, and 559 is a transmission controller 55
This is a program ROM storing the control program of No. 1. 58
Reference numeral 5 denotes a decoder that decodes an address signal output from the unit controller 190 and forms a selection signal for the program memory 558, the unit memory 550, the latch circuits 574, 575, 577, and the input / output controller 576.

As described above, the unit control device 180 includes the management device 400,
The three sides of the card reader control device 188 and the pachinko machine control device 195 have information exchange windows, and under the control of the management device 400, perform control for causing a pachinko game to be played with a card, and as a game result It has software for periodically transmitting generated pachinko machine game information to the management device. Further, in the unit control device 180 of this embodiment, the digit select signal (common signal) of the display data output from the unit controller 190 for driving the monetary value and the number of balls is periodically changed at intervals of, for example, 2 ms. Paying attention to the point that is output
555 is input as a watchdog pulse. The reset circuit 555 has a power-on reset,
The watchdog pulse is monitored and a reset signal is generated when the pulse disappears.

Therefore, even if the unit controller 190 runs away due to noise or the like, the common signal is not output at regular intervals when the runaway occurs, so that the reset 555 operates to activate the unit controller 190 and the data transmission controller 551.
Is initialized, and runaway is avoided.

At the same time, the unit controller 190 has a timer counter inside, and ACK (positive) or NAK (negative) as a response to the transmission request is transmitted for a fixed time (ex. 1).
0 seconds), or after a certain time (e
x.2 seconds), when a packet cannot be transmitted, or when a disturbance in the internal memory (RAM) is detected, the common signal can be forcibly fixed to a low or high level to reset itself. I can do it. Note that the disturbance of the internal memory can be easily performed by writing a specific code (A55A or the like) at a predetermined address in the memory at the time of initialization, for example, and checking it by interrupt processing every 1 ms. Can be detected.

Further, the unit control device 180 of the embodiment initializes the unit controller 190 even when the data transmission controller 551 cannot transmit data within a certain time (5.12 seconds), so that abnormal data is not transmitted to the management device 400. Is being dealt with. 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 counts down this counter by “1” every 20 ms. Therefore, if the state in which the data transmission controller cannot transmit for 5.12 seconds or more continues, the watchdog counter of the unit memory 550 becomes “0”, and this counter is monitored. It can be determined that the transmission controller 551 has gone down and reset itself.

Moreover, in this embodiment, a special RAM is used as the unit memory 550 such that when data is written at a certain predetermined address (7FE), a predetermined terminal INT rises.
Using this function, at the time of system startup, the data transmission controller 551 writes data to the above-mentioned predetermined address to start up the terminal INT, and inputs the signal of the terminal to the unit controller 190 so that the controller for use of the unit memory can be used. Synchronize. Note that the specific terminal INT falls when the unit controller 190 reads data at the predetermined address.

On the other hand, at the time of system startup, synchronization with the management device 400 is performed by the data transmission controller 551.
This is performed by the data transmission controller receiving a line test command (described below) transmitted from the management device 400 and transmitting a reception response to the management device 400.

By the way, as described above, the pachinko machine control device 195 does not calculate the number of safe balls or the like, and such calculation is performed on the unit control device 180 side. A detection signal relating to a game ball, such as a signal, and a signal from the purchase switch 113 are input. Based on these signals, the unit controller 190 calculates operation data such as the number of payout balls, the number of outgoing balls, the number of held balls, and the sales amount, and generates the operation information (game state) and the monitor information related to the pachinko machine. Then, they are written in the transmission data area SDA (see FIG. 24) of the unit memory 550 composed of a dual port memory.

Operation data and the like written in the unit memory 550
The data is transmitted to the management device by data communication with the management device 400 by the transmission controller 551. Also, the management device 400
Is also once written in the reception data area RDA in the unit memory 550, and the unit controller 190 reads the data to receive the data. The unit memory 550 includes a communication area CCA for storing commands and status information for notifying the other controller that other transmission data and reception data are in the memory, a working area UWA and DWA for each controller, and a communication area between the controllers. A synchronization area CSA is provided.

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

The monitor information 1 shown in Table 1 includes a bit indicating that a test is being executed at the time of system startup, a bit indicating whether an initial value is set / not set, a bit indicating a hot code error, and a local network, as shown in Table 4. (Two bits for low-rise and high-rise), a bit indicating a game machine abnormality, and the like. Further, the monitor information 2 has bits indicating an abnormality of the card reader as shown in Table 5.

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

From the above Table 6, it can be seen that the actual state of the pachinko machine is represented by the free state, 0000000000000001 during the game, 0000000000000010 when the forced termination is received, 0000000000000100 when interrupted, and 0000000000001000 when the stop is generated is represented by 0000000000010000.

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

At the front end of a box-shaped case main body 801 constituting the card reader 800, a front lid 802 having a card holding display LED1 and a card insertion / ejection opening 802a is attached, and the side wall of the case main body 801 houses the control unit 160. L-shaped brackets 803 for fixing in the frame 161 are fixed to the four corners.

As shown in FIG. 26, a base plate 804 serving as a card transport path is disposed in the case body 801. Supporting substrates 805 and 806 are mounted above the base plate 804 with a gap slightly larger than the thickness of the card. It is supposed to be.

The support substrate 805 is located on the card insertion port side and has a card insertion detection sensor 808 including a motor 807 and a micro switch thereon, a card insertion detection sensor 808 including a shutter solenoid 809 and a micro switch, a shutter solenoid 809, and security. Reflection type optical sensors 810a and 810b for reading codes are attached. In this embodiment, only one of the sensors 810a and 810b (810a) is used, and the other sensor (810b) is provided as a spare so that the security code may be increased in the future.

A second roller shaft 811 is rotatably mounted between the motor 807 and the shutter solenoid 809. A transport roller 812 is provided at the center of the second roller shaft 811. Is protrudable from the side wall 801a of the case body to the outside, and a pulley 813 is fixed to the protruding end. Further, a projector 814 for irradiating the card position detection sensor SNS1 with detection light is attached near the shutter solenoid 809, and a second roller shaft 811 and a motor 807 are provided.
A light-transmitting portion 815 through which the detection light of the second position detection sensor SNS2 can pass is formed between them. Furthermore, the motor 8
A projector 816 for irradiating the detection light to the punch hole detection sensor SNSp is attached to the side of 07, and a rotary encoder 817 is provided at one end of a rotating shaft 807a of the motor 807.
Is fixed, and the other end of the rotating shaft 807a protrudes outside from the side wall 801b of the case body 801 to which a pulley 818 having a small diameter is fixed.

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

Further, on the lower surface of the support substrate 806, light projectors 828 and 829 for irradiating the third and fourth card position detection sensors SNS3 and SNS4 with detection light are attached.

A first interface board 830 is disposed above the support boards 805 and 806 so as to cover the support boards 805 and 806, and is fixed to the side walls 801a and 801b of the case. This interface board 830
An interface circuit for receiving various control signals from a card reader controller 188 provided in the control unit 160 and for passing a read signal from a sensor or a magnetic head provided on the card reader side to the card reader controller 188 It has. Further, on the lower surface of the interface board 830, a light projector 831 is provided at a position corresponding to the light transmitting portion 815, and a speed detection sensor 832 is provided at a position corresponding to the encoder 817.

On the other hand, auxiliary rollers 836 and 837 urged upward by torsion springs 834 and 835 are provided on the base plate 804 at positions corresponding to the transport rollers 812 and 823 on the base plate 804 disposed below the support substrates 805 and 806. It is mounted so that the face slightly emerges from the formed openings 841,842. Further, the base plate 804 has an auxiliary roller 838 urged upward by a torsion spring 836 at a position corresponding to the magnetic head 821 attached so as to face below the through hole 822 provided in the support substrate 806, It is mounted so that its face is slightly above the opening 843. Along with this, the base plate 804
Has through holes 844 at positions corresponding to the projectors 814, 816, 828, 829 and 831 respectively. Further, the front end of the base plate 804 has a concave portion 845 (the
28 is formed, and there is a cylindrical shielding member 846
Is placed. The shielding member 846 closes the card insertion / ejection opening 802a to prevent ingress of dust, and acts so as to accept only cards having a certain rigidity or more due to its weight.

On the lower surface of the base plate 804, a second interface board 848 is attached by screws. On this second interface board 848, together with a circuit for interfacing with the card reader controller 188, light emitters 816, 828, 829 and 831 are provided. The first to fourth position detection sensors SNS1, SNS2, SNS3, S
NS4 and punch hole detection sensor SNSp are installed. Also, at positions corresponding to the auxiliary rollers 836, 837, 838,
A relief hole 849 for preventing contact with the roller is provided.

Corresponding to the cylindrical shielding member 846 placed on the front end of the base plate 804, an empty space 851 slightly larger than the shielding member 846 is formed at the front end of the upper support substrate 805, and on the base plate 804 When the support substrate 805 is arranged, the shielding member 846 is housed in the empty space 851 so as to be vertically movable. In addition, the frame 8 constituting the empty space 851
An opening 853 is formed on the rear wall of the 52, and the insertion detection switch 808 is disposed behind the opening 853, and the movable contact 808a projects from the opening 853 into the space 851. This movable setting 808a
Is normally positioned above the shielding member 846 as shown in FIG. 28 (A), and when a card CD is inserted through the card insertion / ejection opening 802a, as shown in FIG. 28 (B). The movable contact 808 is used because the card CD pushes the shielding member 846 upward.
is rotated, and the insertion detection sensor 808 is turned on.

Shutter solenoid 8 mounted on support substrate 805
29 is disposed downward as shown in FIG. 29 (A), and the pin 809b formed at the tip of the plunger 809a passes through the insertion hole 854 provided in the support substrate 805 in the solenoid demagnetized state, and As shown in FIG. 7B, the card CD is prevented from being inserted by engaging with a corresponding recessed hole 855 formed on the upper surface of the base plate 804.

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 backward so that the card reader 800 can be used in a card issuing machine. ing.

FIG. 30 (A) shows the mounting positional relationship of various sensors and a magnetic head 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 SNS1 is disposed immediately before the transport roller. The shutter pin 809b is disposed between the insertion detection sensor 808 and the first position detection sensor SNS1, and the security code reading sensors 810a and 810b are
It is arranged almost right beside the position detection sensor SNS1. The second position detection sensor SNS2 is located behind the transport roller 812, the third position detection sensor SNS3 is located behind the transport roller 823, the fourth position detection sensor SNS4 is located at the innermost part of the card reader, and To the fourth position detection sensors SNS1 to SNS4 are located on the same straight line.

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

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

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

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

The card reader control device 188 includes a card reader controller CPU 2 composed of a microcomputer, a transceiver TRV that performs level conversion of data signals transmitted and received between the unit control device 180, and a monitor display provided in the control unit 160. Drivers DRV11 and DRV12 forming the drive signals of 175 and 176 and motor 807 in card reader 800
And a driver DRV13 for generating a control signal for driving a punching device 820, a magnetic head 821, an LED lamp 167, a shutter solenoid 809, a driver DRV14 for driving a relay RLY for turning on / off a power supplied to a motor 807, and a card. leader
A waveform shaping circuit SMG consisting of a Schmitt trigger circuit for shaping the read data of the magnetic head in 800 and detection signals from various sensors, and a flip-flop circuit F / for latching each read data of two tracks read by the magnetic head Built-in F1, F / F2, power-on reset circuit and watchdog timer, monitor pulses periodically output from controller CPU2 (shared with reset pulses of latches LT1 and LT2) as watchdog pulses, and the pulses are interrupted Reset circuit RST2 that generates a reset signal when
It is composed of

The card reader controller CPU2 receives ON / OFF signals from a setting device 171 of a device provided in the control unit 160 and a card ejection switch SWc.

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

On the other hand, the segment-type monitor display 175 combines the seven segments representing numbers and one dot display segment DT to display the contents of abnormalities of the card reader with codes as shown in Table 7 below. It has become. The error code in the right column of Table 7 is a code used when the card reader controller CPU2 notifies a higher-level control device of the content of the abnormality when a corresponding abnormality occurs. By manually turning the 709a, the card can be manually moved while the traveling motor 706 is stopped, and the card having a paper jam can be removed. Run at the end of the card reversing device 740 The card reader controller CPU 2 operates in accordance with the control program in the built-in ROM, executes card travel control, reads card data, checks card data, and the like based on commands from the unit controller 180, and executes the card number and card reader Is transmitted to the unit controller. Communication with the unit controller 180 is performed by the built-in serial communication circuit using the serial ports TX and R.
Do this using X. Output of control signals to the components that make up the card reader 800 and input of detection signals from various sensors
This is performed via an interface circuit 198 as shown in FIG.

The flip-flop FF2 that latches the magnetic data a on the track TRC2 of the magnetic recording unit MG of the card is operated using the read clock b read from the track TRC1 and triggering the flip-flop FF1 as a sampling clock. The flip-flop FF1 outputs a periodic signal c by being triggered by a read clock b and reset by a 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 in the card reader.

In the figure, reference numerals SMG1 to SMG5 denote waveform shaping circuits including Schmitt trigger gates and the like, REC1, R
EC2 is a rectifier circuit, MCC1 and MCC2 are magnetizing current switching circuits, and AMP1 to
AMP4 is amplifier, MHD1 and MHD2 are magnetic head, MT is motor, S
OL1 and SOL2 are solenoids, LED1 is a light emitting diode, DRV21,
DRV22 is a driver, and SNS11, SNS12, SNSp, and SNS1 to SNS5 are sensors. CCC is a current switching circuit for switching the rotation direction of the motor MT, and VCC is a voltage switching circuit for switching the rotation speed of the motor MT.

Read clock signals of read data read by the two magnetic heads MHD1 and MHD2 respectively corresponding to the two tracks TRC1 and TRC2 are amplified by the amplifiers AMP1 and AMP3, and then rectified by the rectifier circuits REC1 and REC2. The rectangular wave is sent to the card reader control device 188 through the waveform rectifier circuits SMG1 and SMG3. On the other hand, the write data and write clock supplied from the card reader controller 188 pass through the waveform shaping circuits SMG2 and SMG4, and the magnetization current switching circuit MCC.
1, input to MCC2, the direction of head drive current is switched according to write data “1”, “0”, and amplifier AMP2, AMP2
It is amplified by 4 and supplied to the magnetic heads MHD1 and MHD2.

Card reader controller 188 to drive motor MT
The current switching circuit CCC changes the direction of the current flowing to the driver DRV21 based on the forward rotation signal and the reverse rotation signal given from the controller, and switches the voltage applied to the motor by the driver DRV21 according to the speed switching signal.

On the other hand, the security code reading sensor SNS11 (810
a) The detection signals of SNS12 (unused), punch hole detection sensor SNSp, position detection sensors SNS1 to SNS4, and speed detection sensor SNS5 (821) are waveform-shaped by the waveform shaping circuit SMG5, and then to the card reader controller 188. Supplied and inserted detection switch 8
The detection signal of 08 is noise-cut by the low-pass filter LPF, and then the waveform is shaped by the waveform shaping circuit SMG5.

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

In the signals shown in FIG. 3, (A) to (D) indicate write data information,
(E) to (G) show write clock information, (H) to (J) show read data information, and (K) to (M) show signal waveforms of various parts related to read clock information. 31 (N) to (R) show timings of signals indicated by reference symbols a to e in the card reader control device 188 of FIG.

Of these, the signals (H) and (K) represent the output signals of the amplifiers AMP1 and AMP3 constituting the interface circuit of FIG. 32, and the signals (I) and (L) represent the rectifier circuit REC1.
And REC2, and the signals (J) and (M) indicate the output signals of the waveform rectifier circuits SMG1 and SMG3, respectively.

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

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

On the other hand, when the data written as described above is read by the magnetic head MHD2, when the magnetization state (D) changes, the output of the amplifier AMP1 changes to + or-depending on the direction of magnetization.
At the rising edge of the read clock b, the read data a corresponding to the signal (J) obtained by shaping the output of the amplifier AMP1 is latched by the latch F / F2.
When the signal a (N) is at a high level, it is recognized that the data is "1". When the signal a is at a low level, the data is recognized as "0". 33
(See FIG. (S)).

In this embodiment, the recording density of magnetic data on the card is 4.13 bit / mm (= 105 BPI), and the card transport speed is
Since the speed is 300 mm / sec, the pulse period of the read clock data is about 806 μS. Therefore, when the magnetic data write by CPU2 is adapted to output a period T ₀ of the CPU output (E) about the write clock twice the clock pulse as (1.612mS).

34 and 35 show examples of the structure of the card issuing machine 200.

The card issuing machine 200 of this embodiment includes a bill identifying device 210 that identifies bills for card purchase, an issuing device 700 that prints an amount corresponding to an inserted bill, and issues a card.
Bill dispensing device 230 for dispensing bills as change
And a unit control device 280 for performing data communication between the various displays 221 to 225 and the control and management device 400 of the entire card issuing machine 200. The front panel 201, which can be freely opened and closed, is provided with a bill insertion slot 211, a purchase selection switch group 212, and a money amount display 213, corresponding to the bill recognition device 210. Therefore, when the player first inserts a bill from the bill insertion slot 211, the inserted amount is displayed on the amount display 213. Then, the purchase selection switch group 212
By pressing a switch corresponding to the desired purchase price from among the cards, a card corresponding to the desired purchase price is issued from the card ejection port 202 of the issuing device 700. Each of the purchase selection switch groups 212 is constituted by a switch with a built-in lamp, and when a bill is inserted, switches that can be selected within the range of the inserted amount (three for 3,000 yen, three for 5,000 yen) (5) built-in lamps are turned on.

When a bill is inserted from the bill insertion slot 211 of the card issuing machine 200, the purchase amount is determined by the purchase selection switch 212, and a balance is generated, the bill dispensing device 230 for refunding the balance stores the bill. It has a bill tank, and is configured to discharge bills in charge of the balance from a bill payout port 232 provided on the front panel 201.

A front panel 201 of the card issuing machine 200 has an issuing lamp 22 indicating that the card is ready to be issued.
1, an issuance stop lamp 222 indicating a card issue disabled state, a bill insertion indicator 2 indicating whether or not a bill can be accepted into the bill insertion slot 211
23, card issuance display to notify card issuance status 22
4. A bill dispensing indicator 225 is provided to inform the dispensing state of the balance. Also, inside the front panel 201 of the card issuer 200, a monitor display 206 for displaying the type (number) of the abnormality of the issuer with a two-digit number, and resetting the display of the monitor display 206 And a reset button 207 for resetting.

Further, the card issuing machine 200 of this embodiment is capable of distinguishing each of a plurality (several tens) of issuing machines installed in a game arcade so that the managing device 400 can identify the issuing machine that has issued a specific card. The setting unit 205 is provided internally, and the unit number set by the setting unit 205 is sent to the management device 400 to generate a transmission address at the time of data communication and for each issuing machine. Used to create data files.

On the other hand, the issuing device 700 takes out the blank cards stored in the card tank 701 one by one and sends them to the card reader 800 first, and the calculated data is sent to the magnetic recording unit of the card by the management device 400. The card number and identification code (store code), issue date code, check code, etc. are recorded, and the punch device 8 in the card reader 800 is recorded.
After punching a punch hole at the issued punching position PH ₁ (see FIG. 2) at 20, the printing device 750 issues the issue date and issue serial number n.
And the purchase price is printed and discharged from a card issuing port 202 provided in the front panel 201. Issuing serial number n
Means that the management device 400, which has received an application for card purchase from the card issuing machine 200, determines the issue serial number n in the order of acceptance for purchase applications from a plurality of card issuing machines under its control, and issues each card. Number given to the machine,
The code obtained by performing the code conversion processing such as the above-described bit rearrangement based on the issuance serial number n is recorded as a card number on the magnetic surface of the card and issued, and information on the card is stored in a file in the management device 400. To be recorded.

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

The card issuing machine 200 of this embodiment records magnetic data with a card reader 800 and prints three “0” s except for a serial number n, an issue date, and a thousand digit of a purchase amount with a printing device. In this state, the card is put on standby, and when a purchase switch is pressed, a thousand-digit number is printed and discharged, thereby shortening the apparent issuance required time.

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

The issuing device 700 according to this embodiment includes a card removal device 710 that removes cards one by one from a card tank 701 in which a large number of cards whose magnetic recording unit MG and print display unit PRT are blank are stored. Card reader 800, a card reversing device 740 further disposed behind the card reader 800, and a printing device disposed below the card reader 800.
750, and a card deriving device 770 disposed in front of the card reader 750, and is controlled by a card issuing control device 790 disposed above the card reader 800. The card reader in the issuing device 700 of this embodiment may have the same structure and function as the card reader 800 for the pachinko machine.

A card reader for an issuing machine is different from a card reader for a pachinko machine in that (1) it is necessary to have a magnetic data recording function, and (2) it is necessary to have a structure capable of ejecting a card backward. There is a point. (1)
For the interface circuit 198 as shown in FIG.
Waveform shaping circuit SMG2, S that shapes the write data signal
MG4 and magnetic current switching circuits MCC1 and MCC2, and magnetic heads MHD1 and MHD2 not only read magnetic data, but also
There is no problem because writing can be performed. In addition, as mentioned in the description of the structure of the card reader 800 for the pachinko machine, the card reader 800 shown in FIGS. 25 to 28 has an opened rear wall of the case, and the inserted card can be moved backward. It can be discharged. Therefore, as the issuing device 700 of this embodiment, the same device as the card reader 800 for the pachinko machine can be used.

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

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

A drive pulley 712 is connected to the rotation shaft of the take-out motor 719 via a speed reduction mechanism 720, and the drive pulley 721 and a driven pulley attached to the ends of the rotation shafts 713a and 714a of the transport rollers 713 and 714. A timing belt 724 is wound between 722 and 723. Further, the second transport roller 7
A clutch disc 725a is mounted on the rotation shaft of the thirteen, and a second clutch disc 725b is rotatably arranged facing the disc 725a. Further, a clutch lever 727 having a roller 726 at one end that can contact the outer circumference of the pair of clutch disks 725a and 725b is swingably attached to the side wall 716. The other end of the clutch lever 727 is connected to a plunger 729a of the clutch solenoid 729 via a spring 728. When the solenoid 729 is excited, the clutch lever 727 is turned on.
Is rotated so that the rollers 726 are moved to the clutch disks 725a and 725.
At the same time, it contacts the outer circumference of b and transmits the torque, and when the solenoid 729 is turned off, the torque is shut off. Further, a pulley 730 is fixed to the rotating shaft of the clutch disk 725b, and a belt 732 is wound between the pulley 730 and the pulley 731 fixed to one end of the rotating shaft 712a of the first transport roller 712. Has been turned. Therefore, the rotational force of the take-out motor 710 is only transmitted through the clutch mechanism (725, 726) while the clutch solenoid 729 is being excited.
The light is transmitted to the transport roller 712.

In addition, the first transport roller 712 has its rotating shaft 712a
Is mounted eccentrically with respect to the base substrate 711.
When it is rotated by 180 °, it slightly projects upward from the opening 711a.

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

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

In addition, a traveling position detection sensor CPS1 is provided at the rear end of the card removal device 710, and detects the sent card.

In addition, a pressing roller 734 for preventing the card from floating is disposed above the third transport roller 714.

The card removed from the tank 710 by the card removal device 710 is subjected to writing of an identification code and a card number to a magnetic recording unit by a card reader 800, and a punching hole is formed at an issue hole punching position by an internal punching device 820. Is opened and then sent out to the rear card reversing device 740. Below the card reader 800, a case 705 for accommodating perforated pieces, that is, punch waste is arranged.

The card reader controller 288 for the issuing machine corresponding to the controller 188 of the card reader 800 for the pachinko machine is provided in the card issuing controller 790.

The card sent to the card reversing device 740 is narrowed between the belt 742 wound around the transport rollers 741a, 741b, 741c and the belt 744 wound around the transport rollers 743a, 743b, and travels in an S-shape. The transport roller 7 is transported along the road and pushes the runway switching piece 745 arranged at the exit as shown by the broken line a.
The belt 747 wound around 46a, 746b, and 746c and the belt 742 above
It is narrowed and sent upward once. Then, when the card passes the runway switching piece 745, the switching piece 745 is pivotally returned from the position shown by the broken line A to the position shown by the solid line by the tension of the spring 745a, and the running position sensor CPS2 disposed above the When the end is detected, the traveling motor 706 for driving the belt 742 is rotated in the reverse direction. As a result, the card changes its direction and starts to be conveyed downward. Then, the belt 749 wound around the transport rollers 748a, 748b, 748c
Then, the direction is gradually changed by being sandwiched between the belts 747, and finally, the sheet is fed forward in the horizontal direction.

The belts 742 and 749 are a belt 707 directly driven by a traveling motor 706 and a belt 708 linked therewith.
And is driven by. Belts 744 and 7
The driving force of the traveling motor 706 is not transmitted to 49, and the card rotates with the frictional force as the card moves.

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

Further, a rotary shaft 709 of the transport roller 748c is protruded to the side, and a knob 709a is fixed to an end portion thereof as shown in FIG. 36. The card can be manually moved while the printer is stopped to remove the jammed card. Running position sensor C at the end of card reversing device 740
PS3 is arranged, and when this sensor detects the rear end of the card, the traveling motor 706 is stopped.

The card sent from the card reversing device 740 enters the printing device 750, and is first detected by the traveling device sensor CPS4. Then, the transfer motor 751 in the printing device 750 is driven, and the driving force is transmitted to the transfer rollers 752a and 752b via the belt 762 and the gear group 763, and is transmitted to the pressing rollers 753a and 753b disposed thereabove. Hold the card in between and move it forward. In front of the transfer rollers 752a and 752b, transfer rollers 754 and 755 are arranged along the traveling path, and a print head 756 such as a thermal head is provided with guide pins 7 above the transfer rollers 754 and 755.
It can be moved up and down along 57. A return spring 758 is inserted around the guide pin 757.

Reference numeral 758 denotes a print head raising / lowering motor. The rotation of the motor 758 is reduced and transmitted to the driven shaft 759. This driven shaft 759
A detection piece 760 having a notch is fixedly attached thereto, and rotation position sensors 761a and 761b are arranged to face the periphery of the detection piece 760. Although not shown, 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, and moves the cam up and down. At this time, the lifting motor
758 rotates the driven shaft 759 by 180 ° in one operation.
That is, the lift motor 58 always stops rotating at the position where the notch of the detection frame 760 faces the sensor 761a or 761b, and the traveling position sensor CPS4 detects the card and operates the lift motor 758. Then, when the sensor 761a or 761b detects the notch of the detection piece 760, the rotation of the motor is stopped. This allows the printhead 756
Is lowered when the card is detected by the traveling position sensor CPS4, and when printing is completed, the elevating motor 758 is operated again to drive the driven shaft 7
By rotating 59 by 180 °, print head 756 is raised and stopped. At the exit of the printing device 750, a traveling position sensor CPS5 is provided, and when the sensor CPS5 detects the leading end of the card, the traveling motor 706 is operated in the same direction (reverse direction) as before, so that the transport rollers 771a, The belt 772 wound around 771b, 771c is driven, and when the sensor CPS5 detects the rear end of the card, the transport motor 751 in the printing device is stopped. As a result, the card sent from the printing device 750 is quickly conveyed into the card leading device 770 in front.

In the card dispensing device 770, as shown in detail in FIG. 39, conveying rollers 773 and 774 are provided below the belt 772.
a and 774b, of which a belt 775 is wound around the transport rollers 774a and 774b. In addition, in this embodiment, only the transporting roller and its belt 77
2,775 are provided in two rows so that discharge can be reliably performed. A card issuing port 202 is arranged in front of the conveyance path constituted by the belts 772 and 775, and a traveling position sensor CPS6 is arranged immediately before the card issuing port.

A runway switching member 777 rotatable around a support shaft 776 is provided between the transport rollers 773 and 774b.
This runway switching member 777 is normally in the first position by a spring 778.
The leading end is positioned below as indicated by the broken line opening in FIG. 37, and guides the card sent from the printing device 750 toward the card issuing opening 202. If the card is not valid or cannot be recorded correctly on the magnetic recording unit due to damage, the card is guided to the confiscation tank 780 below by the runway switching member 777. When the card is correctly written, the switching member 777 is rotated downward as shown by the solid line in FIG. Then, the card sent from the printing device 750 is guided to the card issuing port 202. A confiscation tank 780 is disposed below the transport rollers 774a and 774b.
The card guided down by 7 is the confiscated tank 780
Is stored inside.

A notch 781a is formed in the rear wall 781 of the confiscation tank 780, and a sensor 782 is provided so as to face the notch 781a. The sensor 782 is a light receiver and the corresponding light projector 783 is disposed between the pair of belts 775, the detection optical axis is set to be oblique, and the confiscation tank
When the card in the tank reaches a certain amount or more while detecting the card entering the 780, the upper end of the card blocks the detection optical axis to detect that the card is full. Further, the confiscation tank 780 is slidably mounted on a plate 784 disposed obliquely below the tank 780, and a guide pin 785 for engaging with a long hole 784a formed in the plate 784 is fixed to a lower surface thereof. The spring 786 is stretched between the guide pin 785 and the rear end of the plate 784, and is always urged rearward.

This card deriving device 770 is, when the end of the card passes and the traveling position sensor CPS6 or the detection sensor of the confiscated card changes from on to off, the traveling motor 706 is turned off,
Stop the discharge or confiscation operation.

Note that a card issuance display is provided above the card issuance slot 202 to indicate the progress of card issuance work in the issuance device 700.
There are 787s.

Further, as shown in FIG. 36, the issuing device 700 of this embodiment has left and right rails 792a, 792b on a fixed base 791.
A power supply box 794 with an auxiliary power supply is mounted on the left half of the base 793. Is provided with a counter 795 for displaying the number of issued cards and a spare counter 796 that can be used for displaying the number of confiscated cards and the like.

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

FIG. 40 shows a card issuing machine 20 configured as described above.
A configuration example of a control system of 0 is shown.

In the same figure, 790 is a card issuing control device, 280
Is a unit control device, and 288 is a transport motor 807, a magnetic head 821, and a punching device 82, each component of the card reader 800.
It is a card reader control device that controls 0, etc.
~ LMP5 indicates the purchase price selection switches
The lamp corresponding to the turned on switch is turned on by a lamp built in 212, and the operation button is illuminated from behind.

The control system of this embodiment is roughly divided into a control system by the unit control device 280 and a control system by the card issuance control device 790, and the unit control device 280 is a means for receiving money and a means for selecting a desired purchase amount. Communication means for transmitting valuable data to the management device and receiving a card number in place of the valuable data, means for paying out coins,
The card issuing control device 790 controls the status display means indicating the issuing process status.
, A card reversing device 740, a printing device 750, and a card deriving device 770, and a card reader 800 for checking a card and recording magnetic data.
Of the control unit 288. Communication between the unit controller 280 and the card issuing controller 790 is performed by serial communication.

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

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

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

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

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

In the figure, ○ means on, × means off, Δ means blinking, D means numerical display according to the amount of money, and B means turning on a lamp corresponding to the amount. Table 8 also shows how the bill insertion state of the bill insertion slot 221 is in each state. This indicates that the next bill cannot be inserted until the card and change are removed.

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

The unit controller 280 of the issuing machine, a unit controller 290 that comprehensively controls the card reader controller 288 and the card issuance controller 790, and a data transmission controller 551 that performs control related to data transmission with the management device 400,
It is composed of a network controller 553 and the like for establishing a transmission / reception right in a network and performing serial / parallel conversion of data under the control of a data transmission controller. The communication system is completely the same as the unit control device 180 of the pachinko machine. That is, each controller 290 and 551
The transfer of data between and between 551 and 553 is configured to be performed via 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,
It has an adjustment function to make all transmission / reception data lengths the same (packetization) and a buffer function to measure high-speed data transmission (2.5 Mbps).

The 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 regular data transmission packet. On the other hand, pages 2 and 3 are used alternately for data packet reception. The data transmission controller 551 instructs the network controller 553 on which page to use. Data transmission controller 5
Even if the next packet data is sent during the processing of the received packet data by 51, all the packets can be received reliably because they are received by another page. A common reset circuit 555 is provided so that the controllers 551 and 553 can be initialized at the same time.

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

Further, a data transmission controller 5 is provided between the data transmission controller 551 and the network controller 553.
A latch circuit 561 for the network controller 553 to store the data reception result in response to a request from 51,
A data transmission controller 551 displays a latch circuit 562 for storing a command such as a data transmission command to the network controller 553 and a latch circuit 563 for storing a low-layer network address, and displays an abnormality in the communication control state in the unit control device 280. Is provided with a latch circuit 564 for storing display data to the monitor display 556 composed of three LED lamps. A decoder 557 decodes an address given to each of the latch circuits 561 to 564 and generates a selection signal.

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

The unit controller 290 has a unit number setting device 2
An input / output controller 576 that puts an input signal from the reset switch 207 on the data bus 581 at a predetermined timing or latches a drive signal for displaying various lamps such as the issuing indicator 211, and a bill validator 210 , Bill dispenser
The input signals from 230 and the purchase selection switch 212 are placed on the data bus 581 at a predetermined timing, and the bill validator 2
10 and an input / output controller 578 for latching control signals to the bill dispenser 230 are connected.

As a control signal from the unit controller 290 to the bill validator 210, the bill determined to be a true bill is 10,000 yen, 500
There is an instruction signal for discriminating between 0 yen and 1000 yen to be stored in a safe, and an instruction signal for enabling or disabling insertion of a bill into a bill insertion slot.

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

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

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

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

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

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

Reference numeral 585 denotes a decoder that decodes an address signal output from the unit controller 290 and forms a selection signal for the program memory 558, the unit memory 550, the input / output controllers 596 and 598, the decoders 586 and 587, and the decoder drivers 588 and 889.

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

As described above, the unit control device 280 includes the management device 400,
The card issuance control device 290 has an information exchange window in two directions, controls the issuance of a card under the control of the management device 400, and controls the issuance machine generated as a result of the issuance process. Software for periodically transmitting operation information to the management device is provided.

Transmission and reception of data with the management device is performed via the unit memory 550 as in the case of the pachinko machine. Unit memory 5
The configuration of the 50 is exactly the same as that of the pachinko machine (see Fig. 24)
The transmission data area SDA and the reception data area RDA
And a shared data area CDA for storing commands and status information for notifying the other controller that transmission data and reception data are in the memory.

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

The hot code shown in Table 10 above is stored in the transmission area of the unit memory 550 by the management device 400 at the start of the system, for example, by writing a code such as 010101 ‥‥ 01, and periodically writing the code to the management device. The data is sent to check whether or not the RAM data has been destroyed due to noise such as static electricity, so that abnormalities in the transmitted data can be detected quickly.

Note that the monitor information 1 shown in Table 10 above corresponds to Table 12
As shown in the figure, a bit indicating that a test is being executed at system startup, a bit indicating initial value setting / unset, a bit indicating a hot code error, and a bit indicating a local network (transmission cable 500) error (for low and high layers) 2 bits), a bit indicating an issuer abnormality, and the like.

Further, as shown in Table 13, the monitor information 2 indicates a bit indicating an abnormality of the card reader, a bit indicating the presence or absence of a card, a bit indicating a state in the banknote tank, a bit indicating a banknote jam, and a forcible withdrawal of the banknote. It comprises a bit, a bit indicating the state of the balance dispenser in the bill tank, a bit indicating an abnormality of the balance dispenser, and the like.

42 to 44 show examples of the structure of the above-described settlement machine 300.

The payment machine 300 of this embodiment has a built-in card reader that reads the card number recorded in the magnetic recording section of the inserted card CD and checks the code, and collects the card after receiving data from the management device. And a bill dispenser 321 for refunding an amount corresponding to an unused amount remaining unused for the card.
And a coin dispenser 325, a printer 330 for issuing a receipt printed with the number of balls held by the game, and various display devices 3
03, 304, 341 and 342 and a unit control device 350 for controlling the entire settlement machine 300.

The payment machine 300 is configured such that an upper panel 301 is rotatable in the vertical direction. A card insertion slot 302 is provided at the front end of the upper panel 301, and the upper panel 301 corresponds to the card payment device 310.
On the upper surface of 301, a ball number display 303 for displaying the number of awarded balls (the number of balls held) and an amount display 3 for displaying an unused amount.
04 is provided. Moreover, the settlement machine 300 of this embodiment
Has a flat top surface so that it can form a counter installed in a pachinko parlor, and has two sets of ball number display 303 and money amount display 304, one of which is inclined forward and Is easy to read, and the other is inclined backward to make it easy for a staff member inside the counter to read. Moreover, the number of balls indicator 303 and the amount indicator 304
Is covered by a transparent plate such as a glass plate. In addition, a display reset switch for clearing the display of the above-mentioned display unit to “0” is provided on the rear side of the upper surface of the upper panel 301.
305 is provided. The player first enters the card slot 302
When you insert a card, the card reader 8 in the checkout machine 300
00 reads the card number recorded on the magnetic surface of the card CD, sends it to the management device 400, and receives data on the card. Then, the unused amount is displayed on the amount display 304, the acquired number of balls is displayed on the ball number display 303, and the printer 330 issues a receipt on which the unused amount, the acquired number of balls, the history data and the like are printed. Further, the inserted card in the card reader by drilling device, and is discharged to the inside of the card collecting tank 314 after formation of the punched holes (settlement Sumiana) is performed at a predetermined punching position PH _5.

In this embodiment, a recording head is not necessary for the card reader of the checkout machine, but a recording head is provided.
The data on the magnetic surface may be erased and ejected from the settlement card to make it impossible to decode the card number conversion method and to prevent the card from being forged.

As the card reader, the card reader 800 of the pachinko machine 100 (see FIG. 25) is used as it is, and the card can be ejected backward like the card reader for the issuing machine. A collection tank 314 is arranged. The printer 330 pulls out a blank sheet of paper stocked in a roll state, prints the date of issue, the number of obtained balls, the amount of unused money, and the card history, etc. on the surface thereof, and prints the concave portion 301a of the upper panel 301. It is discharged from the receipt issuing port 331 opened inside.

At the same time, money corresponding to the unused amount is paid out from the balance payout device. The balance dispensing device includes a bill dispenser 321 for dispensing bills and a coin dispenser 325 for dispensing 100 yen coins.
The front panel 306 has a bill outlet 322 corresponding to the bill dispenser 321, and a coin outlet 326 corresponding to the coin dispenser 325. In addition, in the settlement, a fraction of less than 1,000 yen is generated as unused money, and therefore, a coin dispenser 325 that pays out coins of 100 yen unit as described above is required.

Further, on the upper surface of the upper panel 301 of the payment machine 300,
A checkout lamp 341 indicating that the card is being settled and a settlement stop lamp 342 indicating that the card cannot be settled are provided.

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

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

The card settlement device 310 has a card reader 800 as shown in FIG. 43, an auxiliary transport device 311 disposed behind the card reader 800,
Card reader 8 according to the instruction from unit controller 350
00 and a card settlement controller 3 that controls the auxiliary transport device 311
12 and a card collection tank 314 arranged behind the power supply device 313 and the auxiliary transport device 311.

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

The auxiliary transport device 311 includes transport rollers 361 and 362, a pair of upper and lower transport belts 363 and 364 wound therearound, and a transport motor 365 that drives the lower transport belt 364, and is discharged from the rear end of the card reader 800. The card is sandwiched between a pair of belts 363 and 364 and is transported toward the collection tank 314 at the rear.

Although not shown in FIG. 43, the card collection tank 31
4 is provided with a card sensor 319 for detecting that the card is discharged into the tank or becomes full (see FIG. 46). However, the payment machine 300 of this embodiment
Is set to the card confiscation mode only when the highest digit of the unit number setting device 352 is set to “9”, and the card inserted for settlement is guided to the card collection tank after settlement and is forfeited. In other cases, the card is ejected forward after the settlement and returned to the player.

Moreover, as shown in FIG. 44, the checkout machine 300 of this embodiment has a plurality of counters arranged in combination with the corner unit 50 and the card collection machine 900 to form a counter provided in a prize exchange corner of a pachinko parlor. Is available.

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

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

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

Among them, FIG. (A) shows an example of a receipt format when printing of only the settlement data is designated by the print changeover switch 354. The hall name HALL of the pachinko parlor, the serial number n of the card, the settlement date, and Reception time TIME,
The settlement amount AM _s , the number of settlement balls CNT, and the message MSG are printed.

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

In the settlement machine of the embodiment, the card collection mode is set by setting the highest digit of the unit number setting unit 352 to “9”, and in other cases, the card after settlement is ejected forward. By checking the card status at the time of settlement, if the card used is "0" and the purchase amount is refunded, the software will discharge the card to the collection tank 314 at the back after refunding the unused money. Can also be controlled by by this,
In a case where a system in which a game is played with a cleared card by a collecting machine is used, it is possible to avoid abuse of purchasing a card only for the game.

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

The control system of this embodiment is roughly divided into a control system by the unit control device 350 and a control system by the card settlement control device 312, and the unit control device 350 has bill and coin dispensers 321, 325 and various displays 303, 304, 341. ~
Control of 343 and printer 330 and various switches 351 to 35
The card settlement controller 312 is in charge of receiving an input of 4,305, and the card settlement controller 312 is provided with an auxiliary transport device 311, a counter 317 as a counting and displaying means of collected cards, and a card reader 800 for checking cards and reading magnetic data. It is in charge of overall control of the control device 388. Communication between the unit control device 350 and the issuance control device 312 is performed by serial communication.

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

FIG. 47 shows the configuration of the unit control device 350 of the checkout machine 300. The configuration of the unit control device 350 is almost the same as the unit control device 280 of the issuing machine 200 shown in FIG. 41, and is a unit for controlling the card reader control device 388 and the card settlement control device 312 in an integrated manner. A controller 390, a data transmission controller 551 for controlling data transmission with the management device 400, and a network controller 553 for establishing a transmission / reception right in a network and performing serial / parallel conversion of data under the control of the data transmission controller. The communication system has exactly the same configuration as the unit control device 180 of the pachinko machine. That is, between each controller 390 and 551 and 551 and 5
Data transfer between the 53
M) is configured to run via 550 and 552. Of these, the memory 552 is divided into a transmission data storage area and a reception data storage area, and has an adjustment function for making all transmission / reception data lengths the same (packetization), and a high speed data transmission (2.5 Mbps).

The 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 regular data transmission packet. On the other hand, pages 2 and 3 are used alternately for data packet reception. The data transmission controller 551 instructs the network controller 553 on which page to use. Data transmission controller 5
During the processing of the received packet data, the packet 51 is received by another page even if the next packet data is sent, so that all packets can be received without fail. A common reset circuit 555 is provided so that the controllers 551 and 553 can be initialized at the same time.

On the connection side of the network controller 553 with the management device 400, an optical connector is provided via a signal conversion circuit 554 and a changeover switch 542 which perform waveform shaping of received data and level conversion of a signal in order to increase the drive capability of transmitted data. 186, and via a changeover switch 542, a branch circuit 540 that separates and couples a transmission signal and a reception signal so as to cope with a case where the transmission line of the low-layer network is formed of a coaxial cable. Connectable. An optical transceiver 185 is connected to the optical connector 186.

Further, a data transmission controller 5 is provided between the data transmission controller 551 and the network controller 553.
A latch circuit 561 for the network controller 553 to store the data reception result in response to a request from 51,
A data transmission controller 551 displays a latch circuit 562 for storing a command such as a data transmission command to the network controller 553 and a latch circuit 563 for storing an address for a low-layer network, and displays an abnormality in a communication control state in the unit control device 350. Is provided with a latch circuit 564 for storing display data to the monitor display 556 composed of three LED lamps. A decoder 557 decodes an address given to each of the latch circuits 561 to 564 and generates a selection signal.

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

The unit controller 390 includes a ball number display 303
The input signals from the reset switch 305, the unit number setting unit 352, the reset switch 351 of the monitor display 343, the coin removal switch 353, and the print changeover switch 354 are placed on the data bus 581 at a predetermined timing, or the display 341 is displayed. And an input / output controller 576 for latching the drive signal of the payment stop display 342, the bill dispenser 321 and the coin dispenser 325.
Also, an input / output controller 578 for inputting a signal from the printer 330 onto the data bus 581 at a predetermined timing and for latching control signals to the bill dispenser 321 and the coin dispenser 325 and the printer 330 is connected.

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

Further, as an input signal from the bill dispenser 321 to the unit controller 390, a signal output every time one bill is dispensed and a signal output when an abnormality occurs in the dispensing device and the dispensing operation cannot be performed. Alarm signal,
A signal indicating that the remaining amount of bills in the bill storage unit has become 20 or less, a signal indicating that the bill dispensing operation is being performed, and the bill dispensing operation is completed, and the bill in the bill issuing port is removed. And a signal to indicate that the

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

Further, the unit controller 390 dynamically displays a ball number display 303 for displaying the number of settlement balls, an amount display 304 for displaying the settlement amount, and a monitor display 343 for displaying a number indicating the type of abnormality of the settlement machine. 586a, 586b, 587 and decoder drivers 588, 589 are connected via a data bus 581.

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

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

Reference numeral 585 denotes a decoder that decodes an address signal output from the unit controller 390 and forms a selection signal for the program memory 558 and the unit memory 550, the input / output controllers 596 and 598, the decoders 586 and 587, and the decoder drivers 588 and 889.

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

As described above, the unit control device 350 includes the management device 400,
It has a window for exchanging information in two directions of the card settlement controller 312, controls the card settlement under the control of the management device 400, and controls the settlement machine generated as a result of the settlement process. Software for periodically transmitting operation data to the management device is provided.

The unit controller 390 of the checkout machine 300 controls the above components, checks the card number, receives and displays the card data, executes the checkout process, collects the operation data, and configures it as a dual port memory. Write to the transmission data area SDA in the unit memory 550. The operation data written to the unit memory 550 is
The data is transmitted to the management device by data communication between the data transmission controller 551 and the management device 400 via the transmission cable. Data sent from the management device is also temporarily written to the received data area RDA in the unit memory 550,
The unit controller 390 reads this to receive data. Unit memory 550 is provided with a shared data area CDA for storing commands and status information for notifying the other controller that transmission data and reception data are in the memory.

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

As shown in Table 16, in this embodiment, the card history data is also received, printed on a receipt together with the time data and ejected, thereby impressing the player with the highly reliable settlement data. Can be. However, the history data is up to 20 in the card file
It is data up to times.

Note that the monitor information 1 shown in Table 15 above corresponds to Table 17
As shown in the figure, a bit indicating that a test is being executed at system startup, a bit indicating initial value setting / unset, a bit indicating a hot code error, and a bit indicating a local network (transmission cable 500) error (for low and high layers) , 2 bits), a bit indicating an abnormality of the payment apparatus, and the like.

Further, as shown in Table 18, the monitor information 2 includes a bit indicating a paper out condition, a bit indicating a printer error, a bit indicating a card reader error, a bit indicating a state in the card tank, and the presence or absence of a coin in the coin dispenser. , A bit indicating an abnormality of the coin dispenser, a bit indicating a state of the bill dispenser in the bill tank, a bit indicating an abnormality of the bill dispenser, and the like.

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

FIG. 48 shows a specific configuration of the management device 400, and FIG. 49 shows a system configuration of the management device.

The management device 400 includes a central processing unit CPU of a mini-con class, a main storage device M-MEM including a semiconductor memory (RAM), a master control device 401 in which a transmission control device SCC and the like are stored, and an upper part of the master control device 401. It comprises a floppy disk storage device 402 as a provided auxiliary storage device, a hard disk storage device 403, and a personal computer 410. The personal computer 410 has a CRT display device 411 for displaying messages and collected data, and a console for giving commands and setting data by an operator.
A local processing unit 413 having a CPU, a timer TMR (including a calendar), and being connected to a central processing unit in the master control unit 401 via a communication line and an interrupt line;
And a printer 414 for printing collected data and the like.

To couple the local processing device 413 and the central processing unit CPU, serial communication control devices 406a and 406b are provided in the master control device 401. Among them, the communication control device 406
a is used for normal communication, and the communication control device 406b is used for emergency interrupt communication.

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

Further, the management device 400 can be used to start a pachinko machine in a state where the pachinko machine is separated from the system as a reissue card as a reissue storage medium having the same qualification as the damaged card, which is unique to the pachinko gaming system. A built-in auxiliary printer 408 that prints in real time emergency information generated by the system, such as a card issuing device 700 as a storage medium issuing means for issuing a test card as a special storage medium and a "stop" generated by a pachinko machine Box 420 and auxiliary power supply 409 are the master control
It is provided adjacent to 401. The card issuing device 700 and the auxiliary printer 408 are connected to the central processing unit CPU via the communication control devices 406c and 406d, respectively. The card issuing device 700 has exactly the same configuration as the card issuing device 700 for the issuing machine 200 shown in FIG. 202 is the card issuing port.

The auxiliary power supply 409 is provided when the power failure occurs.
Operating data of all terminals volatilely stored in
In order to transfer all issued card data to the hard disk storage device 403 for protection, at least 10
Backup for about a minute so that the management device can operate.

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

In this embodiment, the pachinko machine 100 is mainly used.
And a system including a card issuing machine 200, a checkout machine 300, and a management device 400 will be described. However, the present invention provides a system in which an in-store broadcast device, a prize exchange device, a vending machine, and the like are also controlled by the management device 400. Can be extended to In particular, the prize exchange device uses a card to
There is a possibility that a system that can be exchanged for a prize directly without passing through 0 may be easily applied.

Further, the console 412 configuring the management device 400 also has a unique key configuration most suitable for the pachinko gaming system of the present embodiment.

FIG. 50 shows a configuration example of the console 412. FIG. 1B shows the upper surface of the console, that is, the panel surface, and FIG. 1A shows the rear surface of the console.

In FIG. 50, reference numeral 421 denotes a store opening switch for instructing the start of business for each terminal of the system, and reference numeral 422 denotes a store close switch for instructing the end of business.
After the 421 is turned on, the card can be operated in each terminal until the store closing switch 422 is turned on. Also, 423 is a system end switch for storing operation data of all terminals in the floppy disk storage device 402 after business closing, and instructing the management device to stop control, and 424 is for instructing a recovery process of a damaged card. Is a card revival system.

Note that four of the above-mentioned store opening switch 421, store closing switch 422, system end switch 423, and card recovery switch 424
The two switches are particularly important switches for the present system, and are interlocked with a key switch 420 provided behind (upward in the figure) a key switch 420 in order to prevent easy operation during system operation. If the switch 420 is not turned on, the switches 421 to 424 cannot be operated to be turned on.

Reference numerals 425, 426, and 427 denote ten keys, a return key, and a delete key similar to those provided on a console of a normal personal computer or the like.

On the other hand, reference numeral 428 denotes a display menu switch for giving an instruction to display data related to the card and operation data of each terminal on the screen of the CRT display device 411, and reference numeral 429 denotes a CRT clear switch for requesting deletion of data displayed on the CRT display device. It is. Reference numeral 430 denotes a print menu switch for giving a command to cause the printer 414 to print data on the card, operation data of each terminal, and the like. 432 is a setting switch for requesting setting of a hitting machine and a hitting mode in a pachinko machine, and 433 is a hitting, that is, a game continuation impossible state in which a set number of hitting prize balls are paid out. A stop release switch 434 for giving a command to release the stop state of pachinko machines that have been shut down, forcibly shuts down terminals by type at the end of business, normal control and data collection due to communication network abnormalities, etc. Forced termination switch for forcibly terminating all terminals if disabled, or forcibly stopping a specific terminal if a player is found to be fraudulent, 43
Reference numeral 5 denotes an end release switch for releasing the forcibly stopped terminal, and reference numeral 439 denotes a date and time setting switch. Further, the console 412 of the embodiment is provided with a buzzer 440 that generates a sound to urge the operator to wake up when an emergency such as a pachinko machine is hit and a buzzer stop switch 436 that instructs to stop the sound generation. Have been. 431a and 431
b is a spare switch prepared in anticipation that the function of the management device 400 will be expanded in the future, and can be used as a switch for instructing interruption of printing by the printer 414, for example.

Of the above switches, the switches 421 to 424 and 432 to 436 indicated by double frames in the figure are switches with built-in lamps. Lights up. However, the lamp in the buzzer stop switch 436 is linked with the buzzer, lights up while the buzzer is sounding, and the stop switch 43
Turns off when 6 is pressed.

Further, the console 412 of this embodiment has a test card switch 437 for giving a test card issuance command on the back thereof, an exchange rate of purchased balls and store codes, a total number of terminals, a winning ball 1 when the system is introduced. A built-in switch 438 is provided for instructing setting of a set value such as the number of prize balls per unit and a change of the set value. Unlike other switches, these switches 437 and 438 are switches that are rarely used, and are switches that only need to be known to a specific person (such as a game manager). It is provided in.

Here, the test card will be described. As is clear from the configuration already described, the gaming system of this embodiment includes all terminals (pachinko machines, card issuing machines,
The settlement machine is under the control of the management device, and shifts to an operable state by exchanging card numbers and the like, and cannot be operated by the terminal alone. However, since pachinko machines are frequently used, ball jams and so-called tulip accessories often break down, and it is necessary to adjust nails in the game area to adjust the payout rate. In this case, a test drive is performed after repair or nail adjustment. In this embodiment, the test switch 179 in the control unit 160 of each pachinko machine described above is turned on, and a special device issued by the management device is used. When a test card is inserted through the card insertion / ejection port 802a of the control unit 160, a certain number of balls is given, and the pachinko machine can execute a game operation alone. As a result, it is not necessary to start up the entire system in trial running during non-business hours. In addition, during business hours, a trial hit can be performed without impairing the operation data during the game.

In the embodiment, the same card issuing device 700 as that used in the issuing device 200 is used as the card issuing device 700 provided in the management device 400, and a card tank 701 storing a blank card and a card reader 800 are built therein. However, a method may be adopted in which a blank card is inserted from outside, a code is recorded on a magnetic surface, and the code is ejected, without a blank card inside. In that case, the card tank 701 can be omitted. In addition, since the test card and the resurrection card issued by the management device 400 do not necessarily need to specify the date of use or the serial number of issue like other general cards,
The printing device 750 may be omitted. When a resurrection card is issued, a predetermined punching position P of the card is
A punch hole is made in H ₂ (Resurrection hole).

As described above, the terminals 100, 200, and 300 of this embodiment are all under the control of the management device 400, and cannot operate independently unless the management device 400 is activated. Therefore, when the system is started up, the management apparatus 400 gives setting values to all terminals and initializes them.
In addition, prior to this initialization, the terminal number is collected from each terminal to enable data transmission, and one by one.
Form two transmission addresses. During operation of the system, operation data of all terminals is collected in real time and stored in the main storage M-MEM.

In other words, since the number of terminals under the control of the management device 400 is large, the response is slow if all control is performed by the management device, so a distributed processing method in which some processing is left to the unit control device of the terminal is adopted. Then, on a regular basis, data for all terminals was collected and the operating status was monitored.

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

FIG. 51 shows a main storage device M in which a data file is set.
-MEM configuration and Table 19 shows the function and save location of each file.

Of the files in the main storage device M-MEM, the files FL1 to FL5 except for the transmission address file FL6 are saved in the hard disk HDD (auxiliary) storage device 403 at the time of power failure. Further, data files relating to the terminals, that is, pachinko machine files (hereinafter referred to as P machine files) FL2, issuing machine files FL3 and settlement machine files FL4 are stored in the floppy disk FDD (auxiliary storage device 402) at the end of business hours as daily report files. , And monthly operation data.

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

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 an area that becomes a working area of the central processing unit CPU, and includes the above-mentioned setting file.
In addition to the FL5, a system mode, the latest card issue serial number, a power failure flag, a random number for creating a card number, and the like are stored.

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

The setting value file FL5 in the table is based on the system characteristics and configuration, such as the exchange rate of purchased balls, the store code, the number of terminals, the number of prize balls, the number of hits, etc. Is a setting value that fluctuates. This setting value file is normally loaded from the hard disk HDD to the main storage device at the start of business.
Further, the setting value file FL5 can be updated by the console 412 by pressing the built-in switch 438 when replacing a pachinko machine or the like.

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

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

Further, the number of hits and the hit mode are set in a table indicated by k. Here, the hit mode indicates a method of calculating the number of hits (arithmetic formula). For example, a mode in which hitting is performed when the number of payout prize balls reaches the hit number,
There is a mode in which the number of hit balls is subtracted from the number of payout prize balls and the number of hit balls reaches the number of hits. Although not particularly limited, in this embodiment, as shown by k = 1 to Z, the number of hits and the hitting mode can be set independently for each of Z groups.

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

In Table 21, the type flag is a flag for indicating the type of terminal. "1" indicates a pachinko machine, "2" indicates a card issuing machine, "4" indicates a checkout machine, and "0" indicates a terminal. Indicates the absence of each. NAU status indicates the status of the NAU, as shown in Table 22, when the "1" in bit B ₄ is set to the token bus is abnormal, is "1" in Matabitto B ₁ set "Opening code"
When the packet has already been received and the bit _R0 is set to "1", it indicates that the NAU is normal.

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

The NAU number and the unit number are set by the setting switches (1
71, 205, 305, 561), and in the case of a pachinko parlor, the pachinko machine numbers are customarily "4" and "9".
It is a jump number given by a number excluding. Here, the fact that "4" and "9" are not used indicates that an octal representation is possible. Therefore, using a conversion number shown in Table 23 and a base number displayed in decimal notation, it is expressed only with numerals 0 to 7. According to this, for example, a stand number of “258” is described as “247”.

If this is represented by a binary code in a binary octal system, it will be "010/100/111". This code indicates the decimal "167", which results in "4" and "9"
Pachinko machine numbers that are missing are consecutive serial numbers.
On the other hand, in order to reduce the address on the low-layer network to 8 bits, the lower 8 bits of the above code are taken, and this is taken as 2 bits.
Assuming the code "1010-0111" expressed in the octal evolution system,
If this is expressed in HEXA, it will be "A7H". Further, besides pachinko machines, terminals such as issuing machines and checkout machines are also provided under one NAU. To give them an 8-bit unit number, the number of pachinko machines under one NAU is reduced by 64.
The number is limited to the platform, and the logical product of the code "A7H" and the code "3FH" is obtained to obtain "27H". In this embodiment, this is used as the unit number. Then, “NAU number + unit number” in which an NAU number is prefixed to the unit number is used as a channel number. In this way,
In the practice of pachinko game arcades having a machine number that does not use “4” and “9”, efficient address processing that matches the characteristics of a microcomputer that performs data processing using only the binary system can be performed.

The above transmission address file is created by input from the console when the system is installed, but NAU itself creates an address file (unit table) for the unit under its control based on the input from the serial number setting device when the system starts up. And keep it in memory,
After the line test, the management device makes a unit table request to the NAU, compares it with the response data, and if it does not match, automatically changes (described later). The transmission address file is stored in the built-in switch 438 on the back of the console.
Can also be changed.

In addition, NAU, issuing machine and checkout machine are given consecutive serial numbers starting from "1" for each type as machine numbers.
For U and the payment machine, the machine number is used as it is as the address (unit number), and for the issuing machine, the machine number plus "128" is used as the address (unit number) on the low-layer network. This is to avoid address duplication when a pachinko machine having the same machine number and an issuing machine coexist under the same NAU. Duplication of pachinko machine and checkout machine addresses is avoided by not allowing both to coexist under the same NAU. Also, the issuing machine and the checkout machine can be placed under the same NAU (because the machine number +128 is used as the issuing machine address).

Furthermore, the address of the NAU 530 on the high-layer network uses the NAU number set by the setting unit 544, and the address of the NAU on the low-layer network uses a fixed address of “255”. The address of the management device is “0”.

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

In Table 24, the card number is a number obtained from the issue serial number n using the function f (n), and the number of balls held, the amount, and the card status indicate the current status of the card specified by the issue serial number n and the card number. This information is referred to as a card text in this embodiment. Here, the card state is, as shown in the following Table 25, a bit indicating a free state that is not used for a game, a bit indicating a game, a bit indicating a pause temporarily moving away from the gaming machine, A bit indicating that the card has been settled at the checkout machine, a bit indicating that the number of balls held and the balance of the card have both become zero, a bit indicating that one or more hits have occurred in the past, and a forced termination And a bit indicating that the card has been used in the pachinko machine that has been used.

Returning to Table 24, the terminal file serial number indicating the position of the terminal where the card is currently located and the terminal number are registered in the card file FL1. Since pachinko machine gaming stores do not use the numbers “4” and “9” as unit numbers as a convention, two types of terminal numbers, back and front, are generated.

In Table 24, the number of actions taken by the i-counter and the card, that is, the number of times the card has been ejected from the organic binding system to the outside, corresponds to this number. Number, number of balls, amount,
Card information such as time, that is, card history is recorded. Statistically, most players play with less than 20 pachinko machines per day.
It is decided to record the card history up to 20 times. However, 20
If the number of times exceeds the number of times, the information is recorded in a form updating the table indicated by i = 20. In the above case, the i counter does not count the interruption of the game. That is, each card information is recorded in a new area at the time of interruption, but the value of the i-counter is substantially updated by recording the card information in the same area without updating the counter when the game end switch is turned on after the interruption is released, and recording the card information in the same area. Algebra matches.

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

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

In the state transition diagram described above, an action accompanied by recording of card information in the card file FL3 is indicated by a circle in the arrow indicating the transition direction. In each block, the code indicated by XXH represents the corresponding state in hexadecimal using the code indicating the card state in Table 25 (HE
XA expression).

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

In the table, items from the machine number to the card status are as follows:
The data held in the transmission data area shown in Table 1 is sampled once a second by the management device 400 and registered in a file. In addition, the number of main prize balls, the number of sub prize balls, the number of hits, and the hit mode,
Setting value file shown in Table 20 at system startup
It is registered in the P machine file FL2 based on FL5.

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

Next, Table 27 and Table 28 show the issuing machine file FL3 and the settlement machine file FL4, respectively. The data items shown in Table 27 are stored in the transmission data area of the issuing machine shown in Table 10, and the data items shown in Table 28 are stored in the transmission data area shown in Table 15. And each of the data matches. These are sampled by the management device once a second.

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

Further, the monitor information 1 and 2 in the issuing machine file are shown in Tables 12 and 13, and the monitor information 1 and 2 of the checkout machine file are shown in Tables 17 and 18. Further, when the operation information of the issuing machine and the operation information of the settlement machine are 0000 0000 0000 0001, it indicates that the machine is in operation.

Next, the card issuing machine 100 as a terminal configured as described above, the pachinko machine 200, the settlement machine 300, and a management device 400 that performs centralized control of those terminals are organically connected to perform data transmission and card transfer. A data transmission path (local area network) that enables operation will be described. FIG. 53 shows a configuration example of a pachinko game system using a hierarchical data transmission path.

That is, 100 to 1000 terminals are grouped in units of 20 to 40, for example, in units such as amusement park island facilities, and each group of terminals is a token that circulates at high speed on a ring-shaped transmission path. The node (terminal) that has obtained the access right has a right to transmit and receive data in the form of a packet, and a network passing unit (hereinafter referred to as NAU) is provided by a low-layer network (token bus) 510 of the token passing method. ) 530 connected.

A plurality of NAUs 530 that control each low-layer network (token bus) 510 are connected to the management device 400 via a high-level network 520 of the CSMA / CD system.

The low-layer network 510 is 2.5Mbps (megabit /
Second) and have a high-speed network 520
Is controlled to have a transmission rate such as 10 Mbps,
The NAU530 acts as a buffer that absorbs the difference between the two transmission rates and enables smooth data transmission,
The burden on the management device 400 is reduced, and a large amount of operation data can be collected.

In FIG. 53, a pachinko machine as a terminal is indicated by a symbol P, a card issuing machine is indicated by a symbol H, and a checkout machine is indicated by a symbol S.

Each of the terminals P, H, S is connected to a branch line branched from the network 510. The control units 160, 250 and 350 of each terminal are connected to the end of each branch line. No.
In FIG. 52, a control unit of each terminal is indicated by reference numeral U.

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

The NAU 530 of this embodiment includes a low-layer network controller 533 that establishes a transmission / reception right in the low-layer network 510 and performs serial-parallel conversion of data, and a high-layer network that establishes a transmission / reception right and serial-parallel conversion of data in a CSMA / CD high-layer network. Network controller 537
And a data transmission controller 535 for controlling data transfer between these network controllers 533 and 537. Among the above controllers, the low-layer network controller 533 is composed of a communication LSI dedicated to token passing, and the high-layer network controller 537 and the data transmission controller 535 are composed of general-purpose microcomputers. Further, between these controllers 533 and 535 and between 535 and 537, buffer packet memories 534 and 536 for absorbing a difference in data transmission speed between the low-layer network 510 and the high-layer network 520 are provided.
And are connected respectively. The above packet memory 534,
536 is constituted by a dual port memory and has a transmission data area and a reception data area. Further, between the low-layer network controller 533 and the low-layer network (token bus) 510, a branch circuit 531 for separating and coupling a transmission signal and a reception signal, and a level conversion circuit 532 for converting the level of a transmission / reception data signal are provided. It is connected. Similarly, a level conversion circuit 538 and a branch circuit 539 are connected between the high-layer network controller 537 and the high-layer network 520.

Further, the NAU 530 of this embodiment includes a NAU number setting unit 561 for setting a number for distinguishing a plurality of connected NAUs from each other, and a terminal existing on the low-layer network 510 under the control of each NAU 530. And a number setting device 563 for setting the number of terminals existing on the low-layer network. The set values of the setting units 561 to 563 are input to the data transmission controller 535 in the NAU 530, and the NAU number is used for forming the transmission address of each NAU in the high-layer network 520. Also, the transmission address of each terminal in the low-layer network 510 is formed by the minimum number and the number.

In the hierarchical local network (FIG. 53), when the system starts up, the management device 400 performs a line test through each NAU 530 and sets a set value for each terminal, and the NAU 530 connects the low-layer network 510 during system operation. It collects operation data from the terminals P, H, and S once a second and stores it in its own memory. The stored data is transmitted to each N through the high-layer network 520 once a second in response to a request from the management device 400.
The data is stored in the data file in the management device 400 from the AU 530.

As described above, since the communication network has a hierarchical configuration using the NAU 530 as a buffer and the high-layer network 520 has a transmission speed four times the transmission speed of the low-layer network 510 of 2.5 Mbps, 100 to 1000 In a system having terminals, Table 1, Table 10,
A large amount of operation data as shown in Table 15 can be collected in the management device once a second.

Table 29 shows the management devices in the data transmission system.
While setting the setting values between 400 and NAU530 and for 5 NAUs, NAU530 collects operation data from terminals P, H, S once a second using low-layer network 510 during system operation. Store in its own memory. The stored data is transmitted to each N through the high-layer network 520 once a second in response to a request from the management device 400.
The data is stored in the data file in the management device 400 from the AU 530.

As described above, since the communication network has a hierarchical configuration using the NAU 530 as a buffer and the high-layer network 520 has a transmission speed four times the transmission speed of the low-layer network 510 of 2.5 Mbps, 100 to 1000 In a system having terminals, Table 1, Table 10,
A large amount of operation data as shown in Table 15 can be collected in the management device once a second.

Table 29 shows the management devices in the data transmission system.
The types of packets transmitted and received between the management device 400 and the pachinko machine 100, the card issuing machine 200, and the unit controllers 190, 290, and 390 of the payment machine 300 between the NAU 530 and the NAU 530, respectively, are shown.

In the table, a unit is a terminal (pachinko,
Control unit of a card issuing machine or a payment machine).
A packet called "unit table request" is used by the management device to confirm the connection and address of the unit connected to each NAU when the system is started. The unit receives the ACK packet monitor information 1 from the NAU. Connection is confirmed. Also, the address information in the packet is compared with the value of the unit table file, and if they do not match, the data is changed to the data in the packet. The unit whose connection cannot be confirmed is confirmed again by the subsequent initial value setting packet.

The “card-in” to “interruption end” packets described in Table 29 are packets specific to the pachinko machine 100, and the “card-in” packets are transmitted to the control unit 160 of the pachinko machine. When inserted, this is a packet for requesting information (card text) on the card from the unit side to the management device 400. Here, the card text is the card number, the number of balls,
This is a text containing four pieces of information of the amount (unused portion) and the card status. The packet “return to zero” is used to transmit the 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 the card become zero during the game with the pachinko machine. Packet.

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

The “card purchase” packet listed in Table 29 is a packet specific to the card issuing machine 200, and when a bill is inserted into the bill insertion slot 211 of the issuing machine and the purchase selection switch 212 is turned on, the unit is purchased. Control device 280 to management device 400
Is a packet for requesting a card number and a serial number for the card.

In the system of this embodiment, the card issuing machine 200
Make a reservation such as a card number before the bill is inserted into
A card issuing machine to prepare for printing and issuing money when bills are actually inserted
When 200 transmits a "card purchase" packet in which the card amount column is "0", the management device 400 determines that the packet is an issuance reservation packet, determines an issuance serial number and a card number, and stores it in the card file. After securing the area of the card, an ACK packet containing the serial number and the card number is returned to the card issuing machine. On the other hand, when a bill is inserted, the card issuing machine transmits a “card purchase” packet in which the actual purchase amount is entered in the card amount column to the management device. Then, the management device looks at the card number column, determines that the card is reserved for issuance, searches the card file, writes data such as the purchase amount and the issuance time in the data area of the card, and then transmits the ACK packet. It is to be returned to the issuing machine.

The “card settlement” and “card settlement end” packets described in Table 29 are packets unique to the card settlement machine 300 and are transmitted from the unit control device 350 when a card is inserted into the card insertion slot 302 of the settlement machine. This is a packet for sending the card number of the card to the management device 400 and requesting the unused amount, the number of balls, and the history of the card.

The “card settlement completed” packet is a packet for notifying the management device 400 that the card settlement has been completed. When the management device receives this packet, the card status of the card in the card file is set to “payment completed”. And write the data at the time of settlement in the column of i-counter (i = m) of the history data. By transmitting the "ACK" packet from the management apparatus 400 to the "card payment end" packet, the payment processing of the card is completed, and the next card can be inserted into the payment apparatus.

The “line monitor check” packet in Table 29 indicates the NAU
This is a packet to confirm the recovery of the NAU. It is transmitted periodically (every 30 seconds) until the recovery, and the recovery is confirmed by receiving the ACK packet from the NAU. The operation data of all the units is transmitted, and the NAU and the units are restored. The “unit monitor check” packet is a packet for confirming the recovery of a unit when the unit is determined to be abnormal based on the scheduled data. The packet is transmitted periodically until the unit is recovered, and an ACK packet is received from the NAU. Confirm recovery with. Upon receiving this packet, the NAU performs a connection check with the network controller of the unit, and when the connection is confirmed, transmits an ACK packet to the management device.

Further, in Table 29, the packets “ACK” and “NAK” correspond to the management device 400 and the network adapter unit 530.
And between each of the terminals 100, 200, and 300, when receiving a transmission request, when responding to the request to the other party when responding to the request and when responding to not responding to the request. When returning "ACK", requested data such as a card text may be added.

Note that the packet codes 80H, 81H,.
... are displayed in hexadecimal notation, and the code is an example, and it goes without saying that the present invention is not limited to this.

FIG. 55 (A) shows the basic configuration of a packet transmitted and received between the management device 400 and the NAU 530 via the high-layer network 520, and FIG. 55 (B) shows the relationship between the management device 400 and each unit. The basic configuration of the packets transmitted and received between the units (excluding command packets that do not require ACK) on the high-layer network 520, and FIG. 55 (C) shows the configuration between the NAU 530 and each unit via the low-layer network 510. 2 shows a basic configuration of a packet transmitted and received.

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

That is, the packet of the format as shown in FIG. 55 (B) transmitted from the management device 400 to the unit is removed from the high-layer packet head HHD by the NAU 530 and the low-layer network 5
The NAU530 sends a packet to the management device 400 using only the low-layer packet head LHD and sends it to the management device 400.
Is added and sent out on the high-layer network 520 as a packet in the format of FIG. 55 (B).

Table 30 shows the definition of the unique data laid out in the head of each packet.

56 to 61 show representative data transmitted and received between the management apparatus 400 and the pachinko machine 100, the card issuing machine 200, and the checkout machine 300 via the NAU 530 or the NAU 530 in the data transmission system (local network). Here is an example of the format of a simple packet.

In the “line test” packet shown in FIG. 56 (A), the date and time code, the identification code (store code), the number of pachinko machines, issuing machines, and payment machines belonging to the destination NAU 530 and the minimum of each Enter the machine number and send. Then NAU530
Stores the identification code in the date code, compares it with the number calculated based on the set value of the unit number setting switch 562 and the like, and sends it to the management device 400 as shown in FIG. 56 (B). Returns “ACK” packet. When the NAU530 receives the "line test" packet from the management device, the "line test" in which only the low-layer network packet head LHD is attached to all units under its control using the transmission address calculated by itself. A packet is formed and transmitted while updating the address. Then, "ACK" containing the unit number, the serial number, and the channel number is received from each unit, and a unit table as a transmission address file is created and stored based on the received data.

FIG. 57 (A) shows the structure of a “unit table request” packet from the management device 400 to the NAU 530, and FIG. 57 (B) shows the structure of an “ACK” packet as a response.
Upon receiving the "unit table request" packet, NAU 530 returns an "ACK" packet containing the NAU number, NAU status, and data on all units in the unit table.

FIGS. 58 (A) and 58 (B) show the structures of an “initial value setting” packet 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 purchased ball rate and the number of prize balls required for operation of the pachinko machine are entered and transmitted.

FIG. 58 (A) shows an “initial value setting” packet for the pachinko machine. In an “initial value setting” packet (not shown) for the issuing machine 200 and the settlement machine 300, the date and time code and An identification code and a hot code are inserted and transmitted.

Further, FIGS. 59 (A) and 59 (B) show the structures of a “periodic data request” packet to the pachinko machine and its response packet.

In the response packet to the scheduled data request shown in FIG. 59 (B), below the packet head LHD,
The operation data of all pachinko machines belonging to one NAU530 is linked, and the head and data indicated by * 1 relate to the first pachinko machine, and the head and data indicated by * 2 relate to the second pachinko machine. The data for all pachinko machines continue in the same manner.

The data column of the response packet (not shown) of the scheduled data request to the issuing machine 200 or the payment machine 300 includes all data in the transmission data area of all the issuing machines (see Table 10) or the transmission data of all the payment machines. Send all data in the area (see Table 15).

FIG. 60 shows an example of the configuration of various instruction packets without data from the management device 400 to the settlement machine 300 and their response packets.

In the packet type column PACKET ＄ TYPE in the figure, code 90
One of H (Opening code), 91H (Closed code), 95H (Forced termination request), 96H (Forced termination release), 8CH (Line monitor check) and B1H (Restart) are entered. In addition, the “forced termination request”, “forced termination release”,
Among the “restart” packets, the type (for the entire unit) packet has a column for entering a code indicating the unit type.

FIGS. 61 (A) to 61 (C) show the “card-in” packet, its acknowledgment packet “ACK” and its negative acknowledgment packet “NAK” transmitted to the management device when a card is inserted into the pachinko machine. An example of the configuration is shown.

Incidentally, the packets shown in FIGS. 56 to 61 are not all of the original packets to be put on the network but only the main part, and in addition to the above-mentioned packets, an alert burst for finding the head of data is also provided. , A header section including a source address field indicating a transmission source, a synchronization data, a count section indicating a data length, and a check code section for error detection. These are automatically generated and added by the network controller 553 in the unit control device of each terminal.

The portion "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 control procedure of the central processing unit CPU and the local processing unit 413 when the management unit 400 controls the entire system while communicating with the pachinko machine 100, the issuing machine 200, and the settlement machine 300 using the above various packets will be described. This will be described with reference to FIGS. 62 to 103.

62 (A) to 62 (D) show flowcharts of the initialization process.

When the central processing unit CPU and the local processing unit 413 are reset by turning on the power, the central processing unit initializes the internal registers and the internal memory and the like, and the central processing unit operates in the main memory M.
Along with setting the file framework in the MEM, the local processing device displays an initial screen (only the first and second lines) as shown in FIG. 104 indicating preparation (step S100).
1, S2001). Then, the local treatment device 413 reads the date and time from its own timer and transmits it to the central processing unit CPU (step S1002). The timer of the local processing device 413 is backed up by a battery, does not stop even when the power is turned off, and operates constantly to function as a clock.

Upon receiving the date and time, the central processing unit CPU stores the date and time in the common data area of the main storage device M-MEM and transmits an ACK to the local processing device. If the ACK has not been received, the local processing device returns to step S1002 and transmits the date and time again. After receiving the date and time and returning an ACK, the central processing unit checks the power failure backup file on the hard disk HDD and checks whether the power failure flag in the file is “1” to determine whether the power failure file exists. When the power failure file exists, it is determined that the power is turned on after the recovery from the power failure, and the flow shifts to step S2041 in FIG. 62 (D) (steps S1003, S2002 to S2004).

Therefore, if it is determined in step S2004 that there is no power failure file, the process proceeds to step S2005, where the mode is being prepared, and the setting value file FL5 is read from the hard disk HDD.
Is read and set to a predetermined address position in the main storage device M-MEM (step S2006). Then, the transmission address file FL6 created when the system is installed is similarly loaded from the hard disk HDD to the main storage device M-MEM (step S2007).

Next, the central processing unit forms a pachinko machine file PL2 in the main storage device M-MEN, the serial number of the pachinko machine constituting the system from the transmission address file FL6, and the number of award balls and hits from the set value file PL5. Read out the number and hitting mode and enter them in the designated fields of the pachinko machine file PL2.
“0” is written in the other fields (step S2008). Thereafter, similarly, read the serial numbers of the issuing machine 200 and the settlement machine 300 constituting the system from the transmission address file FL6, and fill in the predetermined columns of the issuing machine file FL3 and the settlement machine file FL4, respectively. Write "0" (step S2
009, S2010).

Also, a card file F provided in the main memory M-MEM is provided.
After "0" is entered for all items in L1 (step S2011), the process proceeds to step S2012.

In step S2012, after performing a process of generating random numbers required to calculate a card number (see FIG. 103), it is checked whether or not there is a mode inquiry from the local processing device 413. A response “mode =“ preparing ”” is transmitted to the local processing device 413 (steps S1004, S2013, S2014). Then, the local processing device receives this, and displays a message MSG1 indicating “line test” on the screen of FIG. 104 of the CRT display device 411 indicating “preparing” (step S1005). Then, the local processing device 413 sends a line test request command to the central processing unit CPU (step S1006).

When the central processing unit CPU receives and confirms the line test request command, it forms a "line test" packet and transmits it to all the NAUs 530 via the high-layer network 520 in order (steps S2015, S2016). Then, upon receiving a response "ACK" packet from the NAU 530, "1" (NAU normal) is entered in bit 0 of the NAU status 2 in the transmission address file FL6 (step S2017). Then, it is determined whether or not transmission to all NAUs has been completed (step S201).
8) When completed, the central processing unit forms a “unit table request” packet, transmits it to each NAU 530, and upon receiving an “ACK” packet from the NAU, determines whether there is a response from all NAUs (step S2019). ~ S2021). And all
When the ACK for the “unit table request” is received for the NAU, the transmission address of the unit table contained in the packet and the hard disk H
The address in the transmission address file loaded from the DD to the main storage device M-MEM is compared (step S2022).
Then, it is determined whether or not a unit not registered in the file exists in the received unit table (step S2).
023) If not, or if there is an unregistered unit, add that unit to the transmission address file in step S2024, and then proceed to step S2025.

In step S2025, it is determined whether there is a unit that does not exist in the received unit table among the units registered in the transmission address file.If there is no unit, the unit is not changed. After storing as an uncommunicable unit, the flow shifts to step S2027.

In step S2027, the transmission address file is saved on the hard disk HDD. Thereby, step S2024
If the transmission address file is changed, the changed transmission address file is read out and compared at the time of system startup after restoration from power failure or at the time of system startup the next day.

After that, the central processing unit CPU transmits the line test result to the local processing unit 413 (step S2028). 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 the line test result (step S1007), it determines whether or not there is an abnormal terminal (step S1008). If not, the process directly proceeds to step S1011. Proceeding to S1009, the screen of FIG. 105 for displaying the terminal number of the abnormal terminal is displayed on the screen of the CRT display device 411.

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

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

On the other hand, the central processing unit CPU transmits an initial value setting request command from the local processing unit 413 (step S202).
9) A "initial value setting" packet is formed, the contents of the setting value file are entered in the data column, and transmitted to each unit (step S2030). Then, if a response "ACK" packet is transmitted, it is determined whether the setting of the initial values for all units has been completed (steps S2031, S2032). When the initial value setting is completed for all units, the display data of the opening request screen as shown in FIG.
Send to 3 (step S2033).

When the local processing device receives this screen data, it is displayed on the CPT display device 411, and then waits for the store opening switch 421 to be turned on according to the message (steps S1012, S1013). Here, when the store opening switch is turned on, the local processing device transmits a store opening request command to the central processing unit (step S1014). When the central processing unit receives this command, it transmits a store opening packet to NAU 530 (steps S2034 and S2035). Next, when an "ACK" is received from the NAU, it is checked whether or not transmission of packets to all NAUs has been completed. When the packet transmission has been completed, normal display screen data indicating business operation in FIG. 113 is transmitted to the local processing device 413. Then, the control is shifted to the control during business (steps S2036 to S2038). On the other hand, when receiving the screen data, the local processing device displays the screen data on the CRT display device 411 and shifts to control during business (step S105).

FIG. 62 (D) shows a control procedure of the central processing unit CPU and the local processing unit 413 at the time of system startup after recovery from power failure.

As described above, when a power failure occurs, the management device 400 saves the card file FL1, the pachinko machine file FL2, the issuing machine file FL3, the settlement machine file FL4, and the common data in the main storage device M-MEM in the hard disk HDD,
The system goes down after the power failure flag is set to "1". Therefore, when the power failure is recovered and the power is turned on, the initialization processing of FIG. 62 (A) is started, and when it comes to step S2004, it is determined that there is a power failure file and the process jumps to step S2041 of FIG. 62 (D). I do. In step S2041, the mode is set to “starting power outage”. On the other hand, when the local processing device 413 displays the initial screen, transmits the date and time and receives the ACK from the central processing device, the process proceeds to step S1004 to inquire about the mode. Then, at this time, since the mode is already set to “power-on startup” in the central processing unit, when a mode inquiry is received, the mode is responded as “power-off power-up” (steps S2042, S2043). Then, when the local processing device receives this mode, it determines whether or not it is "starting power outage". If yes, a message "system recovery" is displayed on the fourth line of the preparation screen in FIG. 104. It is displayed (step S1021). Then, a timer is set, and when a predetermined time elapses after the timer expires (steps S1022, S1023, S1024), the flow returns to step S1004 to inquire again about the mode.

On the other hand, when the central processing unit CPU responds to the mode,
The power failure file is read from the hard disk and returned to the common data area of the main storage device M-MEM (step S
2044, S2045), while waiting for the timer, a “unit recovery” packet is transmitted to each unit, and the operation data in the unit memory of each unit is returned to the state before the power failure (step S2046). And “ACK” from each unit
When a packet is received and all units are finished, NA
The “restart (type)” packet is transmitted to the U530 one after another, and the unit is restarted for each type (steps S2047 to S2049). Then, when "ACK" is received from each NAU 530 and the process is completed for all NAUs, the mode of the central processing unit is changed to "business" and data of the normal display screen (FIG. 113) indicating business is transmitted. Yes (Step S2050
~ S2053). At this point, the local processing unit 413
When the timer set in S1023 has timed out and returns to step S1004, and the mode is inquired, the mode returns to `` in business '', so the judgment of step S1021 is determined and the process jumps to step S1025.
Normal display screen sent from central processing unit to CRT
After the display is displayed on the display device 411, the control is shifted to the control during business.

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

Step S101 in FIG. 62 (C) of the initialization flow described above.
In step 2, a store opening request screen (FIG. 106) is displayed, and step S101 is performed.
When the built-in switch 438 is turned on while waiting for a switch input in step 3, the local processing device 413 transmits a request command for an initial set value to the central processing unit CPU (step S1031). Then, the central processing unit sends the contents of the setting value file loaded from the hard disk to the local processing unit 413 (step S2061). 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 S103).
2).

Here, when the operator inputs a new set value of the purchase ball rate or the identification code using the numeric keypad 425 on the console according to the instructions on the screen, the local processing device stores the updated value in the internal memory, and then stores the updated value in the internal memory. Display the setting value change screen (see FIG. 108) (step S103)
3). At this time, if the return key 426 is pressed immediately without inputting the set value, the screen shifts to the next change screen without updating the set value.

When the car number and the number of prize balls are input from the numeric keypad in accordance with the instructions on this screen, the local processing device stores the updated value and then displays the next set value change screen (see FIG. 109) (step S1034). At this time, if the return key 426 is pressed immediately without inputting the set value, the screen shifts to the next change screen without updating the set value.

While inputting the number of NAUs, the number of pachinko machines, the number of issuing machines or the number of payment machines from the numeric keypad while looking at the change screen, the local processing device 413 issues a setting value file update request command containing the update value stored in the internal memory. The data is transmitted to the central processing unit (step S1035). When the central processing unit CPU receives this command, it first updates the setting value file in the main storage device M-MAM, then updates the pachinko machine file, and then sends an "initial value setting" packet containing the updated setting value. The message is transmitted to all units (steps S2062 to S2064).

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

When the setting update switch 432 is turned on while waiting for a switch input in step S1013 of the initialization flow of FIG. 62, the local processing device 413 transmits a setting value change request command to the central processing unit CPU ( Step S1041).
Then, the central processing unit sends the contents of the setting value file loaded from the hard disk to the local processing unit (step S2071). In response, the local processing device displays a setting value change screen as shown in FIG. 110 on the screen of the CRT display 411 (step S1042).

At this point, the operator operates the numeric keypad 42 according to the instructions on the screen.
When the machine number and the number of hits are input from 5, the local processing device stores the updated value in the internal memory and then displays the next setting value change screen (see FIG. 111) (step S104).
3).

When the operator looks at this screen and enters the stop mode using the numeric keypad according to the instructions on the screen, the local processing device stores the updated value in the internal memory, and then stores the updated value stored in the internal memory. Is transmitted to the central processing unit (step S1044). When the central processing unit receives this command, it first updates the setting value file in the main storage device M-MEM, then updates the pachinko machine file, and then transmits the “initial value setting” packet containing the updated setting value. The data is transmitted to the unit (steps S2072 to S2074).

On the other hand, if the date / time setting switch 439 on the console 412 is turned on while waiting for a switch input in step S1013 of FIG. 62 (C), the local processing device displays a date / time change screen ( Is displayed (see FIG. 112) (step S1045). Then, when the operator inputs the date and time from ten keys 425 according to the instructions on this screen, the local processing device transmits the updated date and time to the central processing device (step S1046). 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 inserts the updated date and time data (all other setting values remain unchanged) in all units. A "setting" packet is transmitted (steps S2075, S2076).

FIG. 65 shows a procedure of a routine data request process from the management device 400 to the NAU 530.

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

If it is determined in step S2101 that the business is open, the flow advances to step S2103 to transmit a "periodic data request" packet to the NAU 530, and set a timer (step S2104). Then, it is checked whether a response ACK has been returned from the NAU 530, and if there is an ACK, the flow shifts to the regular data reception processing S2121 to S2135 in FIG. 66 (step S2105). If it is determined in step S210 that there is no ACK, the timer set in step S2104 is checked to determine whether a time-over has occurred (step S2106). If a time-out occurs before receiving the response ACK from NAU530, step S2
The process proceeds to 107, and among the error counters provided for each NAU in the common data area CDA of the main storage device M-MEM, the error counter corresponding to the NAU that does not respond is incremented, and then the error is determined in step S2108. It is determined whether or not the counter has become 3 or more, that is, whether an error has occurred three times in a row. If the value is 2 or less, the process returns to step S2103 to transmit a “periodic data request” packet to the same NAU again. Then, a time-over occurs before the ACK is received again, and when this is repeated three times, step S210 is performed.
8 to S2109, where the NA in the transmission address file
After clearing bit 0 (NORMAL) of the status information corresponding to the NAU without ACK among the NAU statuses prepared for each U to “0”, the interrupt display command is transmitted to the local processing device 413 to display the CRT. Display an interrupt message indicating NAU down on the screen of the device 411, and
A command to print out the same contents is given to 408. In addition, the local processing unit has the number of interrupt displays, buzzer 44
0 is sounded (steps S2110, S1051, S1052).

Thereafter, it is determined whether or not a periodic data request has been made to all NAUs 530, and if no, the process returns to step S2103 to return to the next NAU 530.
A “periodic data request” packet is transmitted to the AU (step S2111). Then, it is determined whether there is no ACK for all NAUs (step S2112). If no, interrupt processing is terminated. If yes, all NAU status bits 0 are cleared to "0", and then files FL2 to FL4 of all units are cleared.
The bit 7 (CHIEPA) of the monitor information in is set to "1" to store that the Q-packet (high-layer network) is abnormal (steps S2113 and S2114).

Figure 66 shows the NA as a response to the above
The following describes the processing procedure when an “ACK” packet containing regular data is received from U530.

Upon receiving the scheduled data, the central processing unit CPU first checks the monitor information of each unit at the beginning of the data column of the received packet (step S2121). If there is no abnormality, the process jumps to step S2128. If there is, the process proceeds to the next step S2123, and it is determined whether or not it is the same as the previous abnormality (step S2122). If the detected abnormality is the same as the previous one, the process jumps to step S2128. If the detected abnormality is different, the new abnormality is printed by the printer 408 in step S2124. Then, display the unit error interrupt display screen data to the local processing unit 41.
Transmit to 3 (step S2125). When the local processing device receives the screen data, the local processing device displays the 19th screen of the CRT display device.
An interrupt message notifying the unit error is displayed on the line.

On the other hand, after transmitting the screen data in step S2125, the central processing unit next checks the received hot code for a tail hot code (step S2126). If there is no hot code error, the process jumps to step S2128. If there is an error, the error recovery processing task (see FIG. 83) is notified of the unit abnormality in step S2127, and then the process proceeds to step S2128, where the time data is stored. The monitor information 2 is inspected. If there is an abnormality in the monitor information 2, the printer and the CR are executed in the same procedure as in steps S2122 to S2125.
Display an abnormality on the T display device (Steps S2129 to S213)
2).

After that, if there is no abnormality in the monitor information, the file (pachinko machine file, issuing machine file or payment machine file) of the unit in the main storage device M-MEM is rewritten to the received regular data in step S2133. Also, if there is an abnormality, clear the operation information of the unit file or change it to "free", and when receiving regular data from the pachinko machine, change the card state to "free" and change the number of balls and the amount of money in the P machine file Steps for all units in the received packet after saving to a card file
It is determined whether the processes of S2121 to S2133 have been completed, and if not completed, the process returns to step S2121 (step S2134). When the processing has been completed for all units, in the next step S2135, all N
It is determined whether the “ACK” packet of the scheduled data from the AU530 has been processed, and if no, the process returns to step S2121 to return all “AC” packets.
Steps S2121 to S2134 are repeated until K "is completed.

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

Upon receiving the "card purchase" packet, the central processing unit extracts the card number from the data column in the packet and determines whether or not the number is "0" (steps S2141, S214).
2). In the system of this embodiment, before the actual card issuance is performed in the issuance machine 200, the issuance machine itself may transmit a "card purchase" packet in which the card number is set to "0" for card issuance reservation. This is for discriminating between such a packet for reservation and a reserved original "card purchase" packet.

If the card number in the packet is "0", that is, if the packet is a purchase packet for issuing reservation, step S2
Proceeding to 143, the issuing number is read from the issuing machine file of the main storage device M-MEM, and it is checked whether the issuing acceptance number in the packet matches the number obtained by adding "1" to the issuing number in the file (step) S2144). If the issuance acceptance number matches the number of issuances + 1, the flow advances to step S2145 to check whether or not the card amount in the packet is "0" (step
S2146). As a result, if the amount is $ 0, the process jumps to step S2149. If the amount is 0, the reservation flag is read from the issuing machine file in the next step S2147, and it is checked whether it is "1", that is, reserved (step S214).
8). If the reservation flag is not "1", the card issue serial number in the packet and the number of times of issue in the file are incremented in step S2149. Step S214 above
When the amount is not “0” in step 6 and the reservation flag is not checked, the process jumps to step S2149 to increment the card issuing serial number because the card number is “0” without making a reservation and the card amount is immediately changed to “0”. This is so that a card can be issued even if a packet whose purchase price is included in the column is received.

After incrementing the card issue serial number in step S2149 (the issue count is updated in the unit memory when the issuer ejects the card, and it is collected by the scheduled data collection to update the issue count in the issuer file) Retrieves the card file using the card issuing serial number, clears the file of the card, and calculates the card number from the card issuing serial number (steps S2150 and S215)
1). Then, in step S2152, the calculated value is written in the column of the card number in the card file, the value in the received packet is written in the column of the number of balls and the amount of money, the card state is set to “free”, and the i counter is set to “1”. And write the received data and the current time in the log data with i = 1, and then transmit an “ACK” packet to the issuing device 200 in step S2153.

Further, when the card number is determined to be “0” in step S2142 and the issuance reception number received in step S2144 is compared with the number of issuances in the file +1 and do not match,
Proceed to step S2154 to compare the issuance receipt number and the number of issuances, and when they match, proceed to step S2155 to calculate the card number from the card issuance serial number, and in the next step S2156 use the card issuance serial number to After searching for the file and reading out the file, the process proceeds to step S2152 described above to update the card file.
An “ACK” packet is transmitted (step S2153). For example, an “ACK” packet transmitted by executing steps S2141 to S2153 after receiving a “card purchase” packet for issuance reservation does not reach the issuer within a predetermined time, and the same “card purchase” is issued from the issuer. This is in consideration of a case where a packet is transmitted.

On the other hand, when the card number in the “card purchase” packet received in step S2142 is not “0”, that is, when there is a real purchase application for the reserved card, the process jumps to step S2157. It compares the issue receipt number in the packet with the number of card issuances added in the issuer file plus "1", and if they match, searches for the card file using the received card issue serial number and reads out the file Then, the process moves from step S2158 to step S2152 to update the file. At this time, the actual card purchase amount in the received packet is written in the card file. After updating the file, send an “ACK” packet.

If it is determined in step S2142 that the card number is not equal to 0, and then in step S2157 it is determined that the issuance reception number and the number of issuances do not match, the packet is determined to be an erroneous “card purchase” packet, and the process jumps to step S2159. Send a NAK.

FIG. 68 shows the CPU of the central processing unit when a “card-in” packet transmitted to the management device 400 is received when the control unit 160 of the pachinko machine 100 is inserted.
The following shows the processing procedure.

Upon receiving the "card-in" packet, the central processing unit first calculates the card issue serial number from the card number in the packet (step S2161). Next, a card file is searched using the calculated card issuing serial number, and the file of the card is read (step S2162). Then, the card number is extracted from the read card file and compared with the card number in the received packet (steps S2163 and S2164). If the card numbers match, the process proceeds to step S2165, and the card state of the card in the file is “free”.
Check if it is. Here, if the card status is "free", the card status in the card file is rewritten to "playing", and the numbers in the received packet are written in the columns of the terminal number and serial number of the terminal (step
S2166).

Thereafter, an “ACK” packet containing the card text (card number, number of balls, amount, and card) read from the card file is transmitted to the pachinko machine 100, and then the received packet is entered in the card number column in the pachinko machine file. (Steps S2167, S216)
8).

When the card number in the packet is not compared with the card number in the file in step S2164, or when the card numbers match but the card state is not "free", the step "Single game" Or not, and if the card status is not "playing",
It is determined that an inappropriate card has been inserted and step S2
Jump to 174 and send a “NAK” packet. In this way, by comparing the card number in the packet with the card number in the file, a forged card can be eliminated. If the inserted card is interrupted by another pachinko machine, it is determined that the card is no in steps S2165 and S2171, and the process jumps to step S2174 to eliminate the card by transmitting "NAK".

If it is determined in step S2165 that the card status is not "free" and if it is determined in step S2171 that "playing", the process proceeds to step S2172, where the P machine number in the received packet matches the machine number in the card file. “ACK” when done
Is returned after a power failure recovery, the card is re-read in the pachinko machine, and if there is a card, the "card in"
This is because packets are sent, and it must be dealt with.

FIG. 69 shows the processing procedure of the central processing unit CPU when a “pause card in” packet transmitted from the pachinko machine 100 to the management apparatus 400 is received when a pause card is inserted into the pachinko machine that is suspended. Is shown.

Upon receiving the “interrupted card-in” packet, the central processing unit first calculates the card issue serial number from the card number in the packet (step S2181). Next, a card file is searched using the calculated card issue serial number, and the file of the card is read (step S218).
2). Then, the card number is extracted from the read card file and compared with the card number in the received packet (steps S2183 and S2184).
Proceed to 85 to check whether the card status of the card in the file is "suspended". Here, the card status is "Suspended"
If so, the card text in the card file is updated, the card status is rewritten to "playing", the data and time at the time of interruption are written in the i-th data column, and then the i counter is decremented (step S2186, S2187).
When the interruption occurs, the data and time at the time of the interruption are temporarily recorded in the history column indicated by the i-counter in the card file, but when the interruption is released, the i-counter is decremented, and the same column is written when the next history data is written. By writing over the data, it is possible to prevent the history data column from becoming full due to frequent interruptions, and to effectively use the memory.

In step S2186, the card file is updated. After the i counter is set to "-1" in step S2187, the process proceeds to step S21.
Proceed to 88 to transmit an "ACK" packet containing the card text read from the card file to the pachinko machine.

When the card number in the packet is not compared with the card number in the file in step S2184 and the card numbers do not match, or when the card number is not "interrupted", the card state in step S2191 Is "playing" or not, and if it is not "playing",
It is determined that an inappropriate card has been inserted and step S2
Jump to 193 and send a “NAK” packet.

However, although the card status is not "suspending",
If it is determined in step S2191 that it is "playing", the flow proceeds to step S2192 to compare the P machine number in the received packet with the machine number in the card file, and when they match, the flow proceeds to step S2187. And send the “ACK” packet with the card text. This also considers the case where, for example, the management device first executes steps S2181 to S2197 and transmits "ACK", but the pachinko machine cannot receive it and transmits the "suspended card-in" packet again. It is.

If the unit numbers do not match in step S2192, the inserted card is incompatible, so the flow shifts to step S2193 to return “NAK”.
Send a packet.

FIG. 70 shows that when the interruption switch provided on the pachinko machine 100 is turned on during the game, the pachinko machine 400
5 shows a processing procedure of the central processing unit CPU when a “suspension switch” packet transmitted to the CPU is received.

Upon receiving this packet, the central processing unit first calculates the card issue serial number from the card number in the packet, searches the card file using the card issue serial number, and reads the corresponding card data (steps S2201, S220).
2).

Next, the state of the card in the card data read from the card file is checked to determine whether or not the game is "playing" (step S2203). If the card status is "playing", the flow advances to step S2204 to compare the card location terminal number in the packet with the location terminal number of the card read from the file. (Card number, number of balls, amount of money, card status, terminal serial number and terminal terminal number) are rewritten to data in the packet (step S2205). Then, it is checked whether or not the i counter in the corresponding card file is less than 19 (step S2206).
In step 07, the i-counter is incremented, and the unit number, the number of balls and the amount of money in the packet and the current time of the timer are written in the next log data column, and the "ACK" packet containing the card text is transmitted to the pachinko machine (step). S2208, S220
9). If it is determined in step S2206 that the i counter is 19, the i counter is not updated and the step
The process jumps to S2208 and writes the data in the packet so as to overlap the 19th log data column. In this embodiment, the number of history data columns is 20, and the twentieth data column is to be left for writing adjustment data.

On the other hand, if it is determined in step S2203 that the card status in the card file is not "playing" and if the card status is "playing" but it is determined in step S2204 that the machine numbers do not match, step S2211 Then, it is determined whether or not the card state is “interrupted”. here,
If NO, that is, if the card status is neither "playing" nor "suspending", the flow jumps to step S2214 to transmit a "NAK" packet to the pachinko machine.

If it is determined in step S2211 that the card status is "suspended", the flow advances to step S2212 to compare the location terminal number in the packet with the location terminal number in the file. (Step S221
3). This takes into consideration the case where the same “interruption switch” packet is transmitted again after transmitting “ACK” in step S2209. If the card numbers do not match in step S2211 even if the card status is "interrupted intermediate", "NA
A K "packet is transmitted (steps S2212 to S2214).

FIG. 71 shows that when the end switch is turned on after being provided on the pachinko machine 100 during the game, the pachinko machine 40
The processing procedure of the central processing unit CPU when the "end switch" packet transmitted to 0 is received is shown.

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

The difference is that when updating the card file in step S2225, "free" is written as the card state,
In step S2231, the card number in the file is "suspending"
This is not the case, but only the point of determining whether or not it is “free”.

FIG. 72 shows that the pachinko machine 100 receives a “return to zero” packet transmitted from the pachinko machine to the management device 400 when a state of zero return (both the number of balls held and the amount of unused money is zero) occurs during the game. The processing procedure of the central processing unit CPU when the processing is performed is shown.

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

The difference is that when the card file is updated in step S2225, "return to zero" is written as the card status, and in step S2251, the card number in the file is not "interrupted" but not "return to zero" It is only a point to determine whether

FIG. 73 shows a central processing unit CP which receives a “pause” packet transmitted from the pachinko machine to the management device 400 when the pachinko machine 100 is hit during a game.
The processing procedure of U is shown.

Steps S2261 to S2268 in the processing procedure when this packet is received include steps S2201 to S2208 in the processing flow in FIG. 70 and steps S2275 to S2208 in FIG. 73.
2278 represents steps S2211 to S221 in the processing flow of FIG. 70.
It is almost the same as 2214. The difference is that when updating the card file in step S2265, the card status is "stopped"
And the point in step S2275 in which it is determined whether the card status is "free" or "stop", not whether the card status is "interrupted".

Further, in this "stop" packet receiving process, the data and time in the received packet are written in the log data column of the card file in step S2268, and then the "AC
Instead of transmitting the K "packet, as shown in FIG. 73, the P machine file is searched using the machine number in the received packet, and the operation information in the data of the corresponding pachinko machine is" stopped ". After sending the interrupt command containing the stop interrupt display screen data to the local processing unit 413, and printing out the occurrence of the stop by the printer 408 with the machine number, the "ACK" packet is sent to the pachinko machine. (Step S2
269-S2273).

When the local processing device receives the hit interrupt command transmitted by the central processing unit in step S2271, the hit message (time, hit table and hit count) is interrupted on the 19th line of the screen of the CRT display device 411. The display is turned on and the buzzer is turned on (steps S1061 to S1063).

FIG. 74 shows a “card settlement” packet transmitted to the management device 400 when a card is inserted into the settlement machine 300 and a packet transmitted after the settlement machine executes the card settlement based on the “ACK” thereof. The processing procedure of the central processing unit CPU when the incoming “payment end” packet is received will be described.

Upon receiving the "card settlement" packet, the central processing unit first calculates the card issue serial number from the card number in the packet, searches for the card file using the card issue serial number, reads the data of the card, and reads the card data. It is determined whether the state is “free” or “interrupted” (steps S2281 to S2283). Here, if the card state is “free” or “suspended”, step S2284
The "ACK" packet containing the current time of the timer as the settlement acceptance time and the card number and the number of balls, the amount, the card issuing serial number and the card history data of the card data in the card file as the settlement data (Step S2284). On the other hand, if the card state read from the card file is neither “free” nor “suspended”, the process proceeds from step S2283 to S2285 to transmit a “NAK” packet. When receiving the "ACK" packet, the payment machine 300 issues a receipt on which the payment data in the packet is printed, refunds the unused money, and transmits a "payment complete" packet.

When the management device 400 receives the “payment end” packet, the central processing unit first calculates the card issue serial number from the card number in the packet, searches the card file using the card issue serial number, and searches for a card file using the card issue serial number. The data is read, and it is determined whether or not the card status is “interrupted” (steps S2291 to S2293). Here, if the card state is “suspended”, the “pause end” packet is transmitted to the pachinko machine corresponding to the terminal terminal number of the card read from the card file in step S2274, and the suspended pachinko machine is played. After the state is changed to a possible free state and the card state is not "suspended", step S229.
The program jumps to step S2295 and jumps to step S2295 to update (or increment) the i counter in the card file to “20”. Then, the status of the card in the card file is changed to “payment completed”, the payment data is written in the i-th (= 20) of the log data column, and then an “ACK” packet is transmitted to the payment machine 300 (step S2295). , S2296).

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

When the hit release switch 433 is turned on, the local processing device transmits a hit table data request command to the central processing device (step S1071). When the central processing unit receives this command, the P machine files are sequentially read from the main storage device M-MEM, and it is checked whether the operation information is "stopped". The number of hits, the number of balls, the number of balls out, the number of balls, the number of balls, the number of balls, the sales and the number of pachinko machines are transmitted to the local processing device among the machine numbers and operation data of the pachinko machines (steps S2301 to S2303).

Then, the local processing apparatus displays a percussion table release display screen as shown in FIG. 114, and displays percussion tables and their operation data on a line by line basis (step S107).
2).

On the other hand, the central processing unit, after transmitting the operation data of the percussion table,
In step S2305, it is determined whether the check of the operation information in the P machine file has been completed for all the pachinko machines, and if not completed, the process returns to step S2301 to check whether the operation information of the next pachinko machine is "stop". Go. When the operation information check is completed for all the units, a stop table data end command is transmitted to the local processing device (step S2).
304). Then, the local processing device displays a message prompting the user to input the number of the table to be released from the hitting on the 16th and 17th lines of the hitting table release display screen in FIG. 114 (step S1073). .

The operator sees this message, and uses the numeric keypad 425 to cancel the pachinko machine number or “0”
When ("0" is entered, all units are designated), the local processing device transmits a stop release request command (step S1074). When the central processing unit receives the command, it is determined whether or not the stopping is released for all pachinko machines that are being stopped (steps S2306 and S2307).

If all the machines cannot be designated, the flow advances to step S2308 to read the file of the designated pachinko machine and determine whether or not the operation information is "stop" (step S2309).
And when the operation information is other than "stop", step S231
Jump to 4 and send the result. If the operation information is "stop", send a "cancel release" packet to the designated pachinko machine, and then determine whether or not "ACK" has been received. Is received, the operation information of the P machine file is changed from "stop" to "free", and the stop cancellation result is transmitted to the local processing device (steps S2310 to S2314).

On the other hand, if it is determined in step S2307 that all units have been designated,
The process proceeds to step S2315 to sequentially read the P machine files and determine whether or not the operation information therein is “stop”. If it is not "stop", the process jumps to step S2320. If it is "stop", whether "ACK" was received after transmitting the "stop release" packet to the corresponding pachinko machine in steps S2316 to S2319. Is determined, and if "ACK" is received, the P
After changing the operation information of the machine file from "stop" to "free", the process proceeds to step S2320 to determine whether or not all the machines have been completed. If not completed, the flow returns to step S2315 to repeat the above-described procedure. If the processing has been completed for all the units, the flow shifts to step S2314 to transmit a stop release result. Then
The local processing device receives the hit release result, changes the character “hit” displayed in the last column of the corresponding pachinko machine on the hit table release display screen in FIG. 114 to “empty”, and ends the processing. (Step S1075).

FIG. 76 shows a processing procedure in the central processing unit and the local processing unit when the pachinko machine is forcibly terminated by turning on the forced termination switch 434 provided on the console 412.

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 S1081). While looking at this screen, use the numeric keypad 425 to enter the number indicating the type of terminal that you want to forcibly terminate among pachinko machines, issuing machines, and checkout machines, and the local processing device will forcibly terminate the unit corresponding to the specified terminal type Display the screen (step S108
2).

FIG. 115 shows a forced termination screen of the pachinko machine. In the forced termination screen of the issuing machine and the forced termination screen of the checkout machine, the characters "Pachinko machine" displayed on the fifth line of the pachinko machine forced termination screen in FIG. It just changes to a “payment machine”.

While viewing this screen, enter the machine number of the pachinko machine to be forcibly terminated using the numeric keypad 425 or “0” (designate all machines), and the local processing device 413 sends a pachinko machine forced termination request command to the central processing unit CPU. And then display the normal display screen (No. 113
(Steps S1083, S1084).

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

Then, when the operation information check and the card file update are completed for all the units, the process proceeds to step S2348 to transmit a “forced termination request (type)” packet to all NAUs, and then receive a response from the NAU. If so, the result is transmitted to the local processing device (steps S2348 to S2350).
Then, the local processing device displays the display menu selection screen shown in FIG.
When the specific display screen shown in the figure or the all-vehicles display screen shown in FIG. 124 is displayed, the character “strong” indicating that forced termination is in progress is displayed in the last column of the corresponding pachinko machine (step S1085). , S1086).

On the other hand, if it is determined in step S2341 that all the units have not been designated, a “forced termination request (individual)” packet is transmitted to the designated pachinko machine (step S2351). Then, it is determined whether or not “ACK” is returned from the pachinko machine (step S2352), and if not, step S2350 is performed.
When the ACK is returned, the data of the pachinko machine is read from the file of the P machine, and it is checked whether the operation information is "playing" or "interrupted". If yes, the above procedures S2344 to S2346 After updating the card file according to the same procedure as above, proceed to step S2350 and send the forced termination result to the local processing device (step
S2353 to S2357).

FIG. 77 shows a processing procedure in the central processing unit and the local processing unit when the forcible termination switch 434 provided on the console 412 is turned on to forcibly terminate the issuing machine.

When the forced termination switch 434 is turned on, the local processing device 413 displays a forced termination menu screen on the CRT display device 411 (step S1091). While viewing this screen, use the numeric keypad 425 to enter the number indicating the type of terminal that you want to forcibly terminate among pachinko machines, issuing machines, and settlement machines, and the local processing device will forcibly terminate the issuing machine corresponding to the specified terminal type A screen is displayed (step S1092).

In addition, the forced termination screen of the issuing machine is displayed in the “Pachinko machine” displayed on the fifth line of the pachinko machine termination screen in FIG. 115.
Only changes to "Issuer".

While viewing this screen, enter the machine number or “0” (designate all machines) of the issuing machine that you want to forcibly terminate using the numeric keypad 425 of the console, and the local processing device sends the issuing machine forced termination request command to the central processing unit. Is changed to the normal display screen (FIG. 113) indicating that the business is open (steps S1083, S1084).

When the central processing unit receives the issuer forcible termination request command from the local processing unit, it determines whether or not all units have been designated, and if yes, transmits a "forcible termination request (type)" packet to all NAUs. If a response is received, the result is transmitted to the local processing device (steps S2361 to S2361).
2364). Then, the local processing device is
When the issuer data display screen of FIG. 126 is displayed by selecting the issuer data display while viewing the menu selection screen of FIG. 1, the last column of the corresponding issuer indicates that the forced termination is in progress. Display the character "Strong" (step S1095,
S1096).

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

FIG. 78 shows the processing procedure in the central processing unit and the local processing unit when the forced termination switch 434 provided on the console 412 is turned on to terminate the control of the settlement machine.

When the forced termination switch 434 is turned on, the local processing device 413 displays a forced termination menu screen on the CRT display device 411 (step S1101). While looking at this screen, use the numeric keypad 425 to enter the number indicating the type of terminal that you want to forcibly terminate among pachinko machines, issuing machines and payment machines, and the local processing device will forcibly terminate the payment machine corresponding to the specified terminal type A screen is displayed (step S1102).
The subsequent procedure is the same as in the case of the forced termination of the issuing machine in FIG.

FIG. 79 shows the processing procedure of the central processing unit and the local processing unit when the forced termination state of the pachinko machine forcibly terminated by the processing of FIG. 76 is released.

When the termination release switch 435 on the console 412 is turned on, the local processing device 413 displays a forced termination release menu screen similar to the forced termination menu screen on the CRT display device 411 (step S1111). While looking at this screen, numeric keypad 4
When the number for designating the pachinko machine is input in step 25, the local processing device transmits a forced termination table data request command to the central processing unit CPU (step S1112).

Upon receiving this command, the central processing unit reads the pachinko machine files in order, checks whether the operation information is "forcibly terminated", and if the forcible termination is in progress, stops the pachinko machine file data with the machine number and stop. The number of balls, the number of balls, the number of balls out, the number of balls, the number of balls, the number of sales, and the number of customers are transmitted to the local processing device (steps S2381 to S2383). Then, the local processing device displays the data of the forced termination pachinko machine on a line-by-line basis on the pachinko machine termination release screen as shown in FIG. 116 (step S1113).

On the other hand, the central processing unit determines whether or not the operation information check has been completed for all units after transmitting the forced termination unit data (step S2384), and if no, returns to step S2381.
If yes, the process moves to the next step S2385 to transmit a display data end command to the local processing device. Then, the local processing device displays a forced termination release message urging the operator to input a machine number to be released from the forced termination on lines 17 and 18 of the screen in FIG. 116 (step S1114). When the operator inputs a machine number or “0” for designating all machines from the numeric keypad 425 while viewing this screen, a pachinko machine forced termination release request command is transmitted to the central processing unit (step
S1115).

When the central processing unit receives this command, it determines whether or not all the units have been designated. If all the units have been designated, a "forced termination release (type)" packet is transmitted to all NAUs 530, and then a response (ACK) Or NAK) and transmits the result to the local processing device (steps S2386 to S2389).

On the other hand, if it is determined in step S2386 that not all the devices have been designated, the process proceeds to step S2391 to transmit the designated pachinko machine “forced termination release (individual)” packet, and then determine whether or not “ACK” has been received. (Step S239
2). If yes, the operation information in the file of the pachinko machine is changed to "free" in step S2393, and if no, the process directly jumps to step S2389 and the result is transmitted to the local processing device. Upon receiving the transmission from the central processing unit that the forced termination release has been successful, the local processing device changes the status display in the last column of the display data line of the pachinko machine from “strong” to “empty” indicating free. (Step S1116).

FIG. 80 shows the case where the forced termination state of the issuing machine that has been forcibly terminated by the processing of FIG. 77 is released, and FIG. 81 shows the forced termination state of the settlement machine that is forcibly terminated by the processing of FIG. 78. The processing procedure of the central processing unit and the local processing unit when canceling will be described.

These procedures are substantially the same as the pachinko machine forced termination release procedure in FIG. 79. In the processing shown in FIG. 80, the issuing machine file is searched, and the machine number of the issuing machine is transmitted as the forced termination machine data, and the acceptance amount, the deposit amount, the expenditure amount, the number of issuances, and the monta information 2 are transmitted to the CRT display device. The screen for canceling the forced termination of the issuing machine as shown in (1) is displayed.

On the other hand, in the process shown in FIG. 81, the settlement machine file is searched, and the machine number of the settlement machine, the settlement amount, the number of settlement balls, the number of settlements, and the monitor information 2 are transmitted as forced termination unit data, and the monitor information 2 is sent to the CRT display device. Display the screen for canceling the forced termination of the settlement machine as shown in (1).

Note that if the forced termination cancellation process of the issuing machine and the settlement machine succeeds, the status display at the end of each line on the display screen is changed from "stop" indicating that operation is stopped to blank (no display). I have.

FIG. 82 shows a processing procedure of the central processing unit CPU when a stop occurs.

When a power failure occurs, the power is switched, and the central processing unit operates backed up by the auxiliary power supply 409. First, it is determined whether the operation mode is “business” or “closed” (steps S2441, S2442), When the operation mode of the processing device is other than “business” or “closed” (during preparation, during power outage start-up), the system goes down without any operation. On the other hand, when the mode is “open” or “closed”, the local processing unit stops collecting scheduled data from each unit, changes the mode to “under power failure countermeasures”, and reports that the power outage countermeasures are underway. Send to (step
S2443-S2445). Then, the local processing device displays a power failure message on the CRT display device (step S1141).
On the other hand, the central processing unit checks the operation information read from the file of the P machine, and if the operation information is “playing”, the issuing serial number is calculated backward from the card number in the file of the P machine, and the card file is searched using the calculated number. To change the card state to "free" (steps S2446 to S2450). afterwards,
After rewriting the operation information in the P machine file to "free", it is determined whether or not all pachinko machines have been completed. If yes, the data in the common data area (including the set value file and the power failure flag) and the card file P machine file Then, the issuing machine file and the checkout machine mode are saved on the hard disk HDD, and the mode is changed to "closed" before the system goes down (steps S2450 to S2458).

During the display of the power failure message, the local processing device inquires of the central processing unit about the mode, and when the mode is “closed”, displays an end message on the CRT display device (steps S1142 to S1144).

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

When an interrupt is received from the internal timer every 30 seconds from the internal timer, the central processing unit starts the error recovery processing of FIG. 83, and first determines whether the mode is “in business” (step S2461).
Nothing is done except when it is open, and if it is open, step S246
Proceed to 2 to read the NAU status from the transmission address file and set the bit NORMAL that indicates whether the NAU is normal or abnormal to “0”
(= Abnormal) (step S246)
2, S2463). The NORMAL bit of the NAU status is
The response to the "line test" packet in steps S2016 and S2017 in the initialization flow in Fig. 62 is "1".
(= Normal), the NORMAL bit of the NAU with no response remains “0”.

Then, if the NORMAL bit is determined to be "0", the NAU recovery processing steps S2471 to S2475 of FIG. 84 (A) are executed. On the other hand, if the NORMAL bit of the NAU status is "1", the flow advances to step S2464 to read the monitor information 1 in the unit file and check whether the bit indicating the token bus abnormality is "1". If "1", the token bus recovery processing steps S2481 to S2486 of FIG. 84 (B) are executed,
If “0”, it is checked in the next step S2466 whether the bit indicating the hot code error in the monitor information 1 is “1”,
If "1", the hot code recovery processing S2491 to S2498 in FIG. 85 is executed. On the other hand, if it is determined in step S2466 that there is no error (no hot code error), the flow advances to step S2467 to check whether the unit abnormality bit in the monitor information 1 is "1". Unit recovery processing S2
Execute steps 501 to S2509.

In the NAU recovery process shown in FIG. 84 (A), first, for the NAU whose NORMAL bit of the NAU status is “0”,
Send a “line monitor check” packet, set its timer, and if the response “ACK” is received before the time expires, change the NORMAL bit of the NAU status to “1” and then locally process the interrupt display command Send to device
A message notifying that the NAU has been recovered is displayed on the CRT display screen, and the same contents are printed out by the printer 408. If "ACK" does not return within a certain period of time, the routine returns without performing any operation. Return to (Step
S2471-S2474).

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

In the hot code recovery processing shown in FIG. 85, first, a “unit recovery data” packet is transmitted to a unit having a hot code error, and a timer is set (step
S2491, S2492). Then, if "ACK" is received before the time is over, the hot code included in the "unit recovery data" packet is compared with the hot code returned in the "ACK" packet (steps S2493 to S2493).
2495). If the hot codes do not match, the flow shifts to step S2498 to set "1" in the hot code error bit of monitor information 1 in the unit file, and if the hot codes match, "restart" to the unit. After transmitting the packet, clear the hot code error bit of monitor information 1 of the unit (step
S2496, S2497).

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

In the unit recovery processing shown in FIG. 86, first, a "unit monitor check" packet is transmitted to the unit having the unit abnormality to set a timer (steps S2501, S2
502). Then, before the time over occurs, “ACK”
Is received, a "unit recovery data" packet is transmitted and the timer is set again (steps S2503 to S250
6). If "ACK" is returned within a predetermined time for this packet transmission, a "restart" packet is transmitted to the unit and the unit is restarted (steps S2507 to S2509).

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

When the closing switch 422 on the console 412 is turned on,
The local processor has a reception enable switch (display menu switch, print menu switch, and end switch)
Is displayed, and a store closing request command is transmitted to the central processing unit (steps S1151 and S115).
2).

When this command is received by the central processing unit, the P machine files are read in order, the operation information is checked whether or not the game is "playing", the machine number of the pachinko machine of "playing" is stored, and then all machines are searched. Is completed, and if no, the process returns to step S2511 to repeat the above procedure (steps S2512 to S2514). Then, when the operation information check is completed for all the machines, the process proceeds to step S2515 to determine whether there is a pachinko machine in play, and if so, transmits the machine number of the pachinko machine to the local processing device, and If there is no pachinko machine inside, an ACK is transmitted to the local processing device, and a "closed" packet is transmitted to all NAUs, and a command from the local processing device is awaited (steps S2516 to 2518). On the other hand, when the local processing device receives the machine number or “ACK”, if there is a pachinko machine being played, the system end switch is invalidated, and the machine number being played is displayed, and then the normal display screen (No. 113) (Fig.)
To wait for key input (steps S1153 to S115
6). If the operator accidentally turns on the store closing switch during business hours, the operator can notice the error by looking at this display. When there is no pachinko machine in play, the screen does not change, and when the system end switch 423 is turned on, a system end screen (first to fourth lines) in FIG. 119 is displayed (step S1157). When "1" is input from the numeric keypad 425 in accordance with the instruction on this side, the local processing device transmits a system termination request command to the central processing device (step S1158). 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 drive, deletes the power failure save file from the hard disk drive, and transmits the system end message data (steps S2520 to S2522). ). The local processing device receives this, and displays a message (see FIG. 119, line 7) instructing to turn off the current on the system end screen (step S1159).

FIG. 88 shows the procedure of a card recovery process when the card recovery switch 424 provided on the console 412 is turned on.

When the card recovery switch is turned on, the local processing device 413 prompts the user to input a card number on the card recovery screen as shown in FIG. 120 (first to third lines).
Is displayed (step S1161). When viewing this screen and inputting the issue serial number of the damaged card (printed on the card) using the numeric keypad 425, the local processing unit transmits a card recovery data request command containing the card issue serial number to the central processing unit (step S1162). Then, the central processing unit searches the card file by using the sent card issuing serial number, reads the data of the card, and determines whether the card state is “playing” (steps S2531, S2532).

Here, if the card status is "playing", the pachinko machine file is searched using the terminal number in the card file, the data of the pachinko machine is read, and the number of balls and the amount data in the pachinko machine file are stored in the card. When the card status is other than "playing", the number of balls and the amount data in the card file are used as the current value of the card,
These values are transmitted to the local processing device together with the log data read from the card file as card data (steps S2533 to S2536).

Then, the local processing device displays the card resurrection screen (No.
The received card data and history are displayed on the upper part of FIG. 120) (step S1163). Therefore, when the card recovery switch 424 is turned on again, a card recovery request command is transmitted (step S1164). When this command is received by the central processing unit, first, an "initial value transmission" function including an initial value such as a date and an identification code is sent to the card issuing device 700, and a corresponding response ("normal end" function) is received. Then, a “card resurrection” function including the card number, the card issuance serial number, and the amount at the time of issuance is sent, and the resurrection card issuance process is started (steps S2537 to S2339). When the issuance of the resurrection card is completed in the card issuing device 700, a result (normal end function) is transmitted, so the central processing unit receives the resend card and transmits the resurrection end to the local processing device (steps S2540, S2541). . Then, the local processing device displays the result on the card recovery screen, and then changes the screen to the normal display screen (step S1165). Note that the card issuing device 700 that has received the "card resurrection" function
Prints the issue date and serial number, and issues a resurrection 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 device 413 displays a test card issuance message on the screen of the CRT display device 411, and then transmits a test card issuance request command to the central processing unit CPU (step S117).
1, S1172).

Upon receiving this command, the central processing unit sends an "initial value transmission" function in which the initial values such as the date and the identification code are entered to the card issuing device 700, and upon receiving a response ("normal end" function) to the card issuing device 700, Send “Test card issuance” function (step S2
542-S2544). After the test card issuance processing 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 (steps S2545 and S2546). Then, the local processing unit displays the test card issuance result on the CRT.
After the display on the display device, the display screen is changed to the normal display, and the process ends (step S1173).

When the card issuing device receives the "test card issuance" function, it prints a test card character instead of the issue date and amount, and issues a test card in which the test card issuance function is recorded in the magnetic recording unit. (Do not punch holes).

FIG. 90 shows a display flow of the sales statistical data by the timer interrupt.

In the management device of this embodiment, when an interrupt signal comes in at a predetermined cycle from the timer TMR, the sales statistics data display flow of FIG. 90 is started, and first, the local processing device 413 sends a sales statistics data request command to the central processing device. The data is transmitted to the CPU (step S1181). The pachinko machine file received by the central processing unit is sequentially read from the central processing unit, and the number of payout balls, the number of outgoing balls, and the total sales are calculated from the operation data collected as the regular data (steps S2551, S255).
2). Next, check the operation information in the file and "playing"
If it is, the number of games is incremented by one, and if the operation information is "being hit", the number of hits is incremented by one (steps S2553-S
2556). Then, it is determined whether the search has been completed for all the pachinko machines (step S2557).
And the above procedure is repeated. When the processing is completed for all the units, in the next step S2558, the dividing number (the number of out-balls / the number of out-balls) is calculated from the accumulated value of the number of balls and the number of out-balls, and the accumulated value of the number of games Then, after calculating the operating rate (the number of gaming machines / the total number of pachinko machines), the sales and the division, the operating rate, and the number of hits are transmitted to the local processing device as sales statistical data (steps S2558 and S2559).

On the other hand, when the local processing device receives the sales statistical data from the central processing device, the local processing device displays the data on the twentieth line of the screen (see FIG. 113) displayed on the CRT display device 411 (step S1182).

 FIG. 91 shows the procedure of the hit table display processing.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 displays the 121st display on the CRT display device 411.
A display menu selection screen as shown in the figure is displayed (step S1201).

When the operator selects the percussion table display using the numeric keypad 425 while viewing this screen, the local processing unit transmits a percussion table display data request command to the central processing unit (step S1202). When this command is received, the central processing unit reads the pachinko machine files in order, checks whether the operation information in the file is "stopped", and only reads the operation data for those that are "stopped". Among them, the number of hits and the number of balls, the number of out balls, the number of differences,
The sales and the number of customers are transmitted to the local processing device together with the machine number as stop table data (steps S2561 to S2563).

Then, the local processing device stores each percussion table data in the 122nd.
As shown in the figure, the driving table is sequentially displayed on the driving table display screen, one line at a time (step S1203). On the other hand, when the central processing unit completes the search for the percussion table for all the pachinko machine files in the pachinko machine file (step S2564), it transmits the end of the display data to the local processing unit. (Steps S2565 and S1204).

 FIG. 92 shows the procedure of the specific-unit display processing.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 displays the 121st display on the CRT display device 411.
A display menu selection screen as shown in the figure is displayed (step S1201).

When the operator selects the specific-unit display using the numeric keypad while viewing this screen, the local processing device transmits a specific-unit display data request command to the central processing unit (step S1211). On the CRT display device 411, a message prompting to specify (input) a unit number is displayed on the first to third lines of the specific unit data display screen shown in FIG. 123 (step S1212). While viewing this screen, the operator inputs a machine number using the numeric keypad 425. The local processor sends a specific machine display data request command containing the machine number to the central processor (step S1213).

Upon receiving the command, the central processing unit calculates a serial number from the machine number, searches the pachinko machine file using the serial number, and reads the operation data of the corresponding pachinko machine (steps S2571, S2572). Then, the number of hits, the number of outgoing balls, the number of outgoing balls, the number of balls, the number of balls, the number of sales, and the number of customers in the operation data are transmitted to the local processing device (step S2573). Then, the local processing device displays the received data on the fifth and sixth lines of the specific-unit data display screen (FIG. 123) (step S1214). Thereafter, the central processing unit transmits a data end command to the local processing unit, and the processing ends (steps S2574, S1215).

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

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

When the operator selects all-unit display using the numeric keypad while viewing this screen, the local processing device transmits an all-unit display data request command to the central processing unit (step S1222). Upon receiving this command, the central processing unit reads the pachinko machine file in order, and among the operation data in the file, the number of hits, the number of balls, the number of balls out, the difference number,
The number of balls, the number of sales, and the number of customers are transmitted together with the vehicle number (steps S2581, S2582).

Then, the local processing device sequentially displays the data of all the pachinko machines on the display screen of all the pachinko machines with one line and one arm as shown in FIG. 124 (step S1223). On the other hand, when the central processing unit completes the search for all the units in the pachinko machine file (step S2583), it transmits the display data end to the local processing unit, and when the local processing unit receives this, it waits for a key input (step S2584). , S1224).

FIG. 94 shows the procedure of data display processing of a so-called red platform (red platform) in which the number of payout balls is larger than the number of outgoing balls.

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

When the operator selects red display using the numeric keypad 425 while viewing this screen, the local processing device transmits a red display display data request command to the central processing unit (step S1232). Upon receiving this command, the central processing unit reads the pachinko machine files in order (step
(S2591), it is determined whether the difference number in the file is negative (minus) (step S2592). Then, only the operation data of the pachinko machine having the negative difference is transmitted to the local processing device (step S2593).

Then, the local processing device sequentially displays each red stand data on the red stand display screen, one by one, as shown in FIG. 125 (step S1233). On the other hand, when the central processing unit finishes the search for the red stand for all the units in the pachinko machine file (step S2594), it transmits a display data end to the local processing unit, and when the local processing unit receives this, it waits for key input ( Steps S2595, S1234).

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

This black stand display flow is performed according to almost the same procedure as the red stand display flow of FIG. 94. The difference is step S259
Instead of determining whether the difference number is negative in step 2, it is determined whether the difference number is positive (plus) and only the operation data of the positive pachinko machine is transmitted (step S2602). The configuration of the display screen is the same as the red platform display screen in FIG. 125.

FIG. 96 shows the procedure for issuing machine data display processing, and FIG.
The figure shows a configuration example of the issuing machine data display screen displayed on the CRT display device 411 by this.

This issuing machine data display processing flow is executed in accordance with almost the same procedure as the pachinko machine data display processing flow of FIG. 93. What is displayed on the screen as issuer data together with the machine number is the amount of money received, the amount of money deposited, the amount of money to be paid out, the number of issuances, and the monitor. Here, the monitor corresponds to the monitor information 1. After displaying the data of all the issuing machines, their total is displayed on the 18th line. The calculation of the total data is performed by the central processing unit (step S262).
3).

FIG. 97 shows the procedure of the settlement machine data display processing, and FIG.
The figure shows a configuration example of the checkout machine data display screen displayed on the CRT display device 411 by this.

This payment machine data display processing flow is executed according to substantially the same procedure as the data display processing flow of the issuing machine in FIG. 96. What is displayed on the screen as the payment machine data together with the machine number is the payment amount, the number of payment balls, the number of payments, and the monitor.

FIG. 98 shows the procedure of the sales data display processing for displaying the sales data of the entire pachinko parlor, that is, the total of the main operation data of all the units, and FIG.
FIG. 128 shows a configuration example of the sales data display screen displayed by this.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 displays the 121st display on the CRT display device 411.
A display menu selection screen as shown in the figure is displayed (step S1271).

When the operator selects sales data display using the numeric keypad while viewing this screen, the local processing device transmits a sales data display data request command to the central processing device (step S1272). When this command is sent, the central processing unit reads the pachinko machine files in order,
The sum of the number of payout balls, the number of outgoing balls, the difference number, and the number of possessed balls among the operation data is calculated (steps S2641 to S2643). Next, the issuing machine files are read out in order, and the total of the deposit amount and the number of times of issue are calculated from the operation data (step
From S2644 to S2646), the settlement machine files are sequentially read out, and the total of the settlement amount, the number of settlement balls and the number of settlements in the operation data is calculated (steps S2647 to S2649). Thereafter, the calculated total data is transmitted to the local processing equipment as business data, and after transmitting all data, a display data end command is transmitted (steps S2650 and S2651).

On the other hand, when receiving the sales data, the local processing device displays the sales data display screen shown in FIG. 128 on the CRT display device 41.
1 is displayed, and a display data end command is received to wait for key input (steps S1273 and S1274). In the sales data, the number of issued cards is displayed as the number of issued cards, and the number of payments is displayed as the number of paid cards.

FIG. 99 shows a 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 displays the 121st display on the CRT display device 411.
A display menu selection screen as shown in the figure is displayed (step S1281).

When the operator selects a specific card display using the numeric keypad 425 while viewing this screen, a message prompting to specify (input) a card number on the first to third lines of the specific card data display screen shown in FIG. 129 is displayed. (Step S1282). When the operator inputs a card number from the ten keys 425 while viewing this screen, the local processing device transmits a specific card display data request command including the card number to the central processing device (step S1283). Then, the central processing unit calculates the card issuing serial number back from the card number, reads the card file using the issued serial number, and changes the card state in the card file to “playing”.
It is determined whether or not (steps S2661 to S2663). When the card status is other than "playing", the number of balls and the amount in the card file are used as the current value of the card, and when the card status is "playing", the card location terminal number in the card file is used. The pachinko machine file is searched for using the data (number of balls, amount) in the pachinko machine file as the current value of the card (steps S2664 to S2666). This is because the operation data in the card file does not match the actual value during the game because the card file is rewritten when the card state changes.

Next, the central processing unit transmits the card current value determined in steps S2664 and S2666 to the local processing unit together with the card history data read from the card file, and then transmits a display data end command (steps S2667 and S266).
8). Then, the local processing device displays the data of the designated card in the fourth line or lower of the specific card data display screen of FIG. 129, receives a display data end command, and waits for key input (step S1284, S1285).

FIG. 100 shows a procedure of an all-card details display process for displaying data on all issued cards, and FIG. 130 shows an example of a configuration of an all-card details display screen displayed by this.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 displays the 121st display on the CRT display device 411.
A display menu selection screen as shown in the figure is displayed (step S1291).

When the operator selects card statement display using the numeric keypad while viewing this screen, the local processing device transmits a card statement display data request command to the central processing unit (step S1292). Upon receiving this command, the central processing unit reads the pachinko machine files in order,
It is checked whether the operation information in the file is "under play" and whether the card status is "playing" (steps S2671, S2672). When the card status is other than "playing", the number of balls and the amount in the card file are set as the present of the card, and when the card status is "playing", the card location terminal number in the card file is used. The pachinko machine file is searched for, and the data (the number of balls and the amount) in the pachinko machine file is set as the present of the card (steps S2673 to S2675).

Next, the central processing unit transmits the current card value determined in steps S2673 and S2675, the card status read from the card file, and the card location terminal number to the local processing unit (step S2676). Then, as shown in FIG. 130, the local processing device displays the remaining amount, the number of balls, the terminal number, or the card status of the data of each card in one line for each card (step S1293).

On the other hand, after transmitting the card data in step S2676, the central processing unit adds the total number of issued cards by “1”, calculates the remaining amount of the card and the total number of balls held, and further sets each card state. After calculating the number of cards, it is determined whether or not the processing has been completed for all card states (steps S2677 and S2678). Then, if the end is over, the procedure returns to step S2671 to repeat the above procedure.If the end is completed, the total data of the card is transmitted to the local processing device in the next step S2679 and displayed on the all card detail display screen of FIG. 130, Send display data end command (step
S2379, S2680, S1294, S1295).

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

This total display processing is executed according to substantially the same procedure as the card statement display processing shown in FIG. 100 (step S130).
1 to S1304, S2681 to S2689). The only difference is that step S2676 is omitted, that is, the data of each card is not transmitted, and only the total data of all cards is transmitted (step S2686). On the other hand, in response to this, only the total data (same as the lower half of the all card details display screen in FIG. 130) is displayed on the screen of the CRT display device 411.

FIG. 102 shows the procedure of the interrupted card data display processing for displaying the data of the interrupted card and the machine number of the interrupted pachinko machine, and FIG. 131 shows the CRT display 41.
1 shows a configuration example of a suspended card data display screen displayed in FIG.

When the display menu switch 428 on the console 412 is turned on, the local processing device 413 displays the 121st display on the CRT display device 411.
A display menu selection screen as shown in the figure is displayed (step S1311).

When the operator selects the interrupted card display using the numeric keypad while viewing this screen, the local processing device transmits an interrupted card display data request command to the central processing unit (step S1312). Upon receiving this command, the central processing unit reads the pachinko machine files in order,
It is checked whether the card status in the file is "suspending" (steps S1691, S1692). Here, when the card status is "suspending", the time read from the i-th log data column of the card (interruption occurrence time) is compared with the current time of the timer to determine the elapsed time (difference). Is calculated (step S2693). Then, the elapsed time, the card number and the card data, the amount of money, the number of balls, the terminal number, and the interruption time in the log data section are transmitted to the local processing device (step S1694). Then, the local processing device displays the data of each card to one line as shown in FIG. 131 (step S1313). When the data extraction of the interrupted cards is completed for all the cards in the file, the central processing unit transmits a display data end command, and when the local processing unit receives this, it waits for a key input (steps S2695, S2696, S1314). .

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

In the above embodiment, the elapsed time of the suspended pachinko machine is displayed on the suspended card data display screen, but the data of the pachinko machine file in which the operation information is “suspended” is It is also possible to prepare an interruption stand 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 being interrupted, calculate the elapsed time, and display it.

Although not shown, in the above-described embodiment, if there is too much data to be displayed as in the all-unit display screen shown in FIG. Columns are scrolled up.

FIG. 103 is a more specific example of the random number generation processing S2012 in the initialization flow of FIG. 62 and the card number calculation processing S2151 in the flow of FIG. 67 for calculating the card number using the random numbers obtained thereby. The procedure is shown sequentially.

First, a random number A of 0 or more and 10000 or less is generated. Specifically, for example, "Month" and "Sun"
And the sum of “the number of the last digit of the current time (in hundredths of a second)” and obtains it as random number 1 (step S2701).

Next, using a random number generation instruction RND (n), which is one of the FORTRAN instructions as a programming language, the random number 1 generated in step S1 is added to (n), and a random number (0 to 1) represented by a decimal point (7) Is generated and multiplied by 10 ⁷ to obtain a random number 2 (step S2702).

Then, the decimal point of the random number 2 is truncated using the FORTRAN instruction INT (n) (step S2703).

Thereafter, in step S2704, the random number A is set to 0 ≦ A ≦ 1
It is checked whether the condition of 0000 is satisfied, that is, whether A is larger than 0 and smaller than 10000. If A <0 or A> 10000, the flow returns to step S1 to repeat the generation of the random number A. Then, in step S2705, 100 is added to the random number A satisfying the above conditions.
Add 00. Thereby, the random number A becomes any one number between 10,000 and 20,000. So next, FORTRAN instruction M
Using OD, find the remainder of the random number A divided by the integer "5",
This is set as a random number B (step S2706). Therefore, the random number B is any one of 0, 1, 2, 3, and 4.

Thereafter, the random number A obtained in step S2705 is added to the serial number n of the card in the card purchase packet reception flow, and the addition result X is set as the primary card number (step S2707). However, the issuance serial number n given here is a number from 1 to 12767, and it is assumed that cards are not issued such that the number of issued cards exceeds 12767. Thus, the primary card number X is 10001-3
It is a number between 2767. The upper limit of X is 32767, because 327
This is because 67 is the largest number that can be represented by 15 bits in the binary system, and in a gaming system described below that handles 16-bit data, a code with “1” in the most significant bit is
This is to make a reservation for a special card (test card) different from a normal game card.

Then, in the next step S2708, the above-described step S27
The primary card number X obtained in 07 is subjected to code conversion by exchanging the first to fifteenth bits excluding the most significant bit using a bit operation instruction or the like.

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

If the bit exchange pattern is 15 bits, (15! −
Although there are 1) possible ways, any five of them may be selected to create a program for performing such bit replacement. As the number of bit replacements increases, the execution time increases, but the conversion pattern becomes difficult to predict. Therefore, it is preferable to select a pattern in which all 15 bits are replaced.

Table 31 shows an example of a bit replacement pattern corresponding to the random number B.

Next, the actual conversion of the card number using the above-mentioned bit replacement pattern will be described by taking as an example a case where the random number A is 14297, the random number B is 2, and the issue serial number n is 635. In this case, the primary card number X is “14932” from X = A + n. This is expressed as "3A54" in hexadecimal, and becomes "0011110001010100" in binary. When this primary card number is converted with the third conversion pattern for the random number B = 2, it becomes as shown in the following Table 32, and the secondary card number is “1E13” in hexadecimal notation and “7699” in decimal notation. Become.

On the other hand, the process of calculating the card issuing serial number from the card number performed in the flow of FIGS. 67 and 68 to 74 (steps S2151, S2161, S2181, S2201, S2221, S2241,
Specific methods such as S2261, S2281) are described in steps S2707, S27 above.
The operation is the reverse of 08. First, the card number is converted into a binary number, and then each bit is inversely converted with a conversion pattern (see Table 32) determined by the random number B to obtain X.
The serial number can be obtained by subtracting.

Next, the card issuance control device 790 and the card reader control device 2 in the card issuance device 700 provided in the management device 400
The card issuing control procedure in 88 will be described.

In the card issuing device of this embodiment, the central processing unit CPU can communicate only with the card issuing control device 790 and cannot directly communicate with the card reader control device 288. That is, the card reader control device 288 can communicate only with the card issue control device 790. Therefore, communication between the central processing unit CPU and the card issuing control device 790 is performed by a function code, and communication between the card issuing control device 790 and the card reader control device 288 is performed by a command. Incidentally, as the function code from the central processing unit CPU to the card issuance control device 790, an "initial value setting" function for giving the card reader a date code and an identification code to be recorded in the magnetic recording unit of the card, a card "Card issue" function to instruct the issuance of the card, "card resurrection" function to instruct the reinstatement of the card,
A "test card issuance" function for instructing the issuance of a test card and a "retransmission request" function for requesting retransmission of the function code sent immediately before, the state of the card reader received by the card issuance controller 790 from the card reader controller 288. There are prepared six types of commands of a "status request" function for requesting the transmission of a status indicating the status.

However, of these, the management device uses the “card resurrection” function and “test card issue”
Only the functions are provided, and the other functions are prepared for the card issuing device built in the issuing machine 200.

Also, as the function code from the card issuing control device 790 to the central processing unit CPU, an “initial value request” for requesting an initial value such as a date and an identification code at the time of reset is provided.
Function, "Normal end" function to notify the central processing unit that the specified processing has been completed normally, and conversely, "Abnormal termination" function to notify that the processing has not been completed normally, immediately before the central processing unit There is a "retransmission request" function for requesting retransmission of the function code sent to the user. The issuer 200 also has a “status transmission” function for transmitting the status of the card reader in response to a “status request” from the unit controller 299.

Note that, although not particularly limited, the function code is transmitted between a start code of STX and an end code of ETX, and between the STX and ETX, there may be a status and data to be transmitted in addition to the function code.

Specifically, in the “normal end” function, the “abnormal end” function, and the “status transmission” function, an 8-bit status 1 and a status 2 indicating the status of the card reader as shown in Tables 33 and 34 are provided. An entry column is provided, and the status is sent to the central processing unit CPU together with the function code.

In the status 1 of Table 33, the transport unit sensor abnormality bit is set to “1” when any of the traveling position sensors CPS2 to CPS6 of the card issuing device 700 has failed.

On the other hand, the communication commands from the card issuing control device 790 to the card reader control device 288 include a “magnetic write” command instructing recording of magnetic data on the card, and information on the magnetic data, security code, and punch holes of the card. A "magnetic read" command instructing to read and send magnetic data, a "security request" command instructing to send read security data, and a "punch hole request" command instructing to send read punch data. A "reload" command for instructing the card reader to reread the data held in the card reader, a "punch hole" command for instructing the card to make a punch hole, and "Card ejection in front" command instructing ejection in the direction of the insertion slot A "card backward ejection" command for instructing ejection of the card in the card reader backward, a "cancel" command for canceling the card reading command, and a "status" for instructing transmission of status information indicating the status of the card reader. There are nine types of "request" commands.

When the card reader control device 288 receives the above-mentioned command from the card issuance control device 790, it performs a corresponding process and always returns a response.
The types of response include: normal, communication error, command error, no magnetic recording data, magnetic data read failure, magnetic recording data abnormality, security and magnetic data mismatch,
Company code or device code mismatch, magnetic write error, punch error, punch hole read error, security read error, punch dust full, motor error, RAM error, sensor error, card reader error, card length error,
There is a card jam.

Although not particularly limited, a code indicating the command is transmitted between a start code of ESC and an end code of CR, and data to be transmitted may be inserted between the ESC and the CR in addition to the command code. Also, a response from the card reader control device 288 to the card issuance control device 790 is transmitted with a code indicating the type of error or an error code and the requested data between the start code STX and the end code CR. It is supposed to.

FIG. 132 shows a control procedure such as card recovery 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, I / O ports, etc., sets a timer (ex. 10 seconds), and sets the "initial value request" function This is transmitted to the processing device CPU (routines RN101 to RN103). Next, the central processing unit CPU
It is checked whether a function has been received from the CPU, and if not, it is determined whether the timer set in the routine RN102 has expired (routines RN104 and RN105). Then, the routines RN104 and RN105 are repeated until the time is over. If the time is over, the routine returns to the routine RN102, resets the timer, and transmits the "initial value request" function again. This is because when the "initial value request" function is first transmitted, the central processing unit CPU may not be ready for reception yet.

When a function from the central processing unit CPU is received after transmitting the function, the routine shifts from the routine RN104 to the RN106, and checks whether the received function is the “initial value transmission” function. Routine RN after sending
Returning to 102, the "initial value request" function is retransmitted. First, after receiving an initial value, specific processing such as card issuance is accurately executed.

However, the management apparatus does not send the initial value at the time of initialization, but sends the "initial value transmission" function immediately before the "card recovery" or "test card issuance" function.

If the function received in the determination of the routine RN106 is "transmission of the initial value", the routine proceeds to the routine RN108, where the date and the identification code sent together with the function code are stored in the internal memory, and The initial value unset bit of the status register prepared in the internal memory is cleared, and a "normal end" function is transmitted to the central processing unit CPU (routines RN109 and RN110).

Thereafter, the routine RN111 waits for the reception of the next function from the central processing unit CPU, and upon receiving the function, proceeds to routines RN112 to RN115, determines which function has been received, If the function is "function", the identification code is stored, and then the "normal end" function is transmitted (routines RN116 and RN117). Is executed (routine RN113). If the received function is “Issue test card”,
The test card issuance processing is executed according to the same procedure as the card restoration processing in FIG. 104 (routine RN114). Routine R
The reason why the determination of whether or not the function is the “initial value transmission” function in N112 is made in consideration of the case where the routine returns to the routine RN111 after the execution of error processing (see FIG. 106) described later (reference numeral V1).

FIG. 133 shows a 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 resurrection” function or the “test card issuance” function from the central processing unit CPU, first, FIG. 134 (A)
After executing the card removal processing routines RN201 to RN212 shown in FIG.
N213 to RN227, card inversion processing routine in FIG. 134 (C)
RN228 to RN243, print 1 processing routine RN2 in FIG. 134 (D)
After the execution of 45 to RN266, the card ejection processing RN268 to RN280 of FIG. 134 (E) is executed, the counter 795 for counting the number of cards to be removed is counted up, and the "normal end" function is transmitted (routine). RN118, RN119).

FIG. 134 (A) shows a specific procedure of card ejection processing in the card recovery (or test card issuance) processing flow of FIG. 133.

Here, first, it is checked whether there is a card in the card tank 701 by looking at the card presence / absence sensor 703 (routine R20).
1) When the sensor is off, that is, when the tank is empty, the routine jumps to the routine RN212 to return to the status 2 in the internal memory.
Set the extraction device error bit of the
The process proceeds to the error processing routine shown in FIG.

If there is a card in the card tank 701, the routine shifts from the routine RN201 to RN202 and proceeds to the card reader control device 28.
Send a "magnetic write" command to 8. Then, after setting the timer, the clutch solenoid 792 is turned on, and the take-out motor 719 is rotated (routines RN203 and RN203).
N204). Thereby, one card is sent out from the card tank.

Next, it is checked whether or not the timer set in the routine RN203 has timed out.
Check whether CPS1 is turned on (routines RN205, RN206). When the first traveling position sensor CPS1 is off, the process returns to the routine RN206 and repeats the timer check. In this way, it waits for the first traveling position sensor CPS1 to be turned on, and if the time is over before the sensor is turned on, the routine jumps to the routine RN211 and sets the traveling position sensor 1 abnormality bit of status 1 to “1”. After setting the take-out device abnormal bit of No. 2 to “1”, the process proceeds to the error processing routine of FIG. 135.

On the other hand, before the time is over, the first traveling position sensor
When the CPS1 is turned on, the routine proceeds to the routine RN207, in which the clutch solenoid 729 is turned off to stop the rotation force of the take-out motor 719 from being transmitted to the roller 712 that sends out the card from the tank, thereby preventing the two cards from being fed. And the routine again
It is checked whether the timer set in RN203 has timed out (routine RN208). Then, in the future, it is checked whether or not the first traveling position sensor CPS1 is turned off. If the sensor is turned off within a predetermined time, the card is removed from the card tank 701, it is determined that the card is normally sent out, and the removal motor 719 is stopped. Then, the processing ends and the original routine (No. 133
Return to figure). If the traveling position sensor CPS1 is not turned off within a predetermined time, it is determined that the card is jammed halfway, and the routine shifts to the routine RN211 to set the traveling position sensor 1 abnormality bit of the status 1.

FIG. 134 (B) shows a specific procedure of the reader control process in the card recovery process flow of FIG. 133.

In this flow, first, after setting a timer, it is checked whether or not there is a response to the "magnetic write" command transmitted in the routine RN202 in the card removal processing flow before the timer times out (routines RN213 to RN215). ). If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormality bit of the status 2 to "1", and shifts to the error processing routine of FIG. 135.

Further, when a response from the card reader control device 288 is received within a predetermined time, the process proceeds to the routine RN216a, and checks whether the response is normal. Perform error handling. On the other hand, if the response is normal, it is determined whether or not the reception function is a "card resurrection" function (routine RN216b).
8 and send a `` punch hole '' command containing the data indicating the reissued hole position and the data indicating the issued hole position when the reception function is `` test card issue ''. Set (routines RN217a, RN217b, RN218). Then, before the timer times out, the card reader controller 288
Check whether there is a response from the routine (routine RN21
9, RN220). If there is no response within the time, the flow jumps to the routine RN227, sets the card reader abnormal bit of the status 2 to "1", and shifts to the error processing routine in FIG. 135.

When a response from the card reader control device 288 is received within a predetermined time, the process proceeds to the routine RN221, and checks whether the response is normal.If there is an abnormality, the process jumps to the routine RN227 as in the case of time over, Perform error handling. On the other hand, if the response is normal, a "card rear ejection" command is transmitted to the card reader control device 288 to set a time (routines RN222, RN223). Then, it is checked whether or not there is a response from the card reader control device 288 before the time is over (routine RN224, RN225). If there is no response within the time, the process jumps to the routine RN227, sets the status 2 of the card reader abnormal bit to "1", and shifts to the error processing routine of FIG. 135.

When a response from the card reader control device 288 is received within a predetermined time, the process proceeds to the routine RN226 to check whether the response is normal.If there is an abnormality, the process jumps to the routine RN227 as in the case of time over, Perform error handling. On the other hand, if the response is normal, the original routine (No.
Return to Fig. 133).

FIG. 134 (C) shows a specific procedure of the card reversal process in the card recovery process flow of FIG. 133.

In this process, the timer is set after the transport motor 706 is first rotated forward, and it is checked whether the second traveling position sensor CPS2 is turned on before the timer times out (routines RN228 to RN231). If the second traveling position sensor CPS2 is not turned on within the time, the routine jumps to the routine RN242 to set the jam abnormality bit of the status 1 to "1", and the routine RN243 sets the card abnormality bit of the status 2 to "1". After setting each
The error processing routine shown in FIG. 135 is shifted.

On the other hand, when the second traveling position sensor CPS2 is turned on within the predetermined time, the routine proceeds to routines RN232 and RN233, and proceeds to routine RN2.
Before the timer set in 29 times out, the second
Check whether the traveling position sensor CPS2 is turned off. When the second traveling position sensor CPS2 is turned off, it means that the card has passed the traveling path switching piece 745. Therefore, if the second traveling position sensor CPS2 does not turn off within the time, the routine RN24
Jump to 2 and set the status 1 jam error bit to “1”, and set the status 2 card transport error bit to “1” in routine RN243, and then set the 135
The process proceeds to the error processing routine shown in FIG.

If the second traveling position sensor CPS2 is turned off within a predetermined time, the process proceeds to the routine RN234, a new timer is set, and then the transport motor 706 is rotated in the reverse direction (routine R
N235). As a result, the card is transported in the reverse direction, and guided by the track switching piece 745 to the track toward the printing device 750.

After the reverse rotation of the transport motor, the card issuing control device 790 checks whether the second traveling position sensor CPS2 is turned on again before the timer set in the routine RN234 times out (routines RN236 and RN237). If the second traveling position sensor CPS2 is not turned on within the time, the routine jumps to the routine RN242 to set the jam abnormality bit of the status 1 to "1", and the routine RN243 sets the card abnormality bit of the status 2 to "1". Are set, and then the process proceeds to the error processing routine of FIG. 135.

On the other hand, when the second traveling position sensor CPS2 is turned on within the predetermined time, the routine shifts to the routines RN238 and RN239 and proceeds to the routine RN2.
Before the timer set in 34 times out, the second
Check whether the traveling position sensor CPS2 is turned off. If the second traveling position sensor CPS2 is not turned off within the time, the routine jumps to the routine RN242 to set the jam abnormality bit of the status 1 to "1", and the routine RN243 sets the card transport abnormality bit of the status 2 to "1". Are set, and then the process proceeds to the error processing routine of FIG. 135. Further, when the second traveling position sensor CPS2 is turned off within a predetermined time, the process proceeds to the routines RN240 and RN241, and whether or not the third traveling position sensor CPS3 is turned on before the timer set in the routine RN234 times out. Check if the sensor is turned on within the time, the original routine (No. 133
Return to figure).

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

Here, after setting the timer first, the fourth traveling position sensor CPS4
Check whether or not is turned on (routines RN245 to RN26
7). If the time runs out before the fourth traveling position sensor CPS4 is turned on, the routine jumps to the routines RN265 and R266, sets the status 1 jam error bit to "1", and sets the status 2 printer error bit to "1". After "1" is set, the flow shifts to the error processing in FIG. 67.

If the fourth traveling position sensor CPS4 is turned on before the time is over, the process proceeds to the routine RN248 to rotate the printing motor 751, and then determines whether the third traveling position sensor CPS3 is turned off before the time is over. Is checked (routines RN249 to RN250). Here, if the time is over, the routine jumps to the routine RN265 and shifts to error processing. If the third traveling position sensor CPS3 is turned off within a predetermined time, the transport motor driven by the routine RN235 in FIG. After stopping the 706, it is checked whether or not the fourth traveling position sensor CPS4 is turned off before the time is over (routines RN251 to RN253). Here, when the time is over, the process jumps to the routine RN265 as described above. On the other hand, if the fourth traveling position sensor CPS4 is turned off before the time is over, the routine proceeds to a routine RN254, in which the printhead elevating motor 758 is rotated by 180 ° to lower the head. Then, it is determined whether or not the received function is “card resurrection” (routine RN255). If yes, the serial number and date are issued by the print head 756. "TEST" indicating the date and test card
Is printed (routines RN256 to RN259).

Thereafter, the head lifting motor 758 is again rotated by 180 ° to raise the print head 756, and a new timer is set (routines RN261 and RN262). Thereafter, it is checked whether or not the fifth traveling position sensor CPS5 is turned on before the timer times out (routines RN263, RN264). If the time over occurs, the process proceeds to the routine RN265 to reset the status 1 jam error bit. After setting "1" to "1" and the printer error bit of status 2 to "1", the process proceeds to the error processing of FIG. 135. On the other hand, if the fifth traveling position sensor CPS5 is turned on before the time is over, the process returns to the original routine (FIG. 133).

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

When this process is started, first, the lead-out solenoid 779 in the card lead-out device 770 is turned on to rotate the track switching member 777 downward, and then the reverse rotation of the transport motor 706 is started, and a timer is set (routine RN268). ~ RN270). As a result, the card sent from the printing device 750 is transferred toward the card issuing port 201 through the inside of the deriving device 770. When the fifth traveling position sensor CPS5 is turned off before the timer set in the routine RN270 times out, the printing motor 751 in the printing device 750 is stopped (routines RN271 to RN273). Card already printing device
Because it is sent from 750. If the time is over before the fifth traveling position sensor CPS5 is turned off, the process proceeds to the routines R279 and RN280 to set “1” to the jam error bit of status 1 and the card transport error bit of status 2 respectively. Then, the processing shifts to the error processing in FIG. 135.

After the printing motor 751 is stopped in the above routine RN273, the timer set in the routine RN270 is checked again, and if the sixth traveling position sensor CPS6 in front of the card issuing port 202 is turned on before the time is over, it is derived. Turn off solenoid 779 (routines RN274 to RN27
6). If the timer times out before the fifth traveling position sensor CPS6 is turned on, the process shifts to the routine RN279.

After turning off the derived solenoid 779 in routine RN276,
Set a new timer and wait 0.5 seconds before feeding motor 7
Stop 06. The above 0.5 second is determined from the relationship with the rotation speed of the transport motor 706, and
Transfer belt 772 is sufficient time to move by a distance corresponding to the card its entire length l _0. By waiting 0.5 seconds after the sixth traveling position sensor CPS6 detects the card, the card is stopped in a state where it is protruded from the card issuing port 202 by about two thirds. The sixth traveling position sensor CPS6 is turned off when the player manually pulls out the card from the issuing port 202.

FIG. 135 shows various sensors CPS1 to CPS6 for detecting the position of the card during the processing flows of FIGS. 134 (A) to (E).
A specific procedure of error processing executed when a time-out occurs before turning ON or OFF of the like is shown.

In this processing, first, all the motors in the card issuing device 700 (the take-out motor 719, the transport motor 706, the printing motor
751 and the head elevating motor 758) are stopped, and then the "abnormal termination" function is transmitted to the central processing unit (routines RN151 and RN152). Next, it is determined whether a function has been transmitted from the central processing unit (routine RN15).
3) If the function has not been received, it is determined whether or not the error has been recovered by checking a sensor in the card issuing device 700 (routine RN154). If the error has not been recovered, the process returns to the routine RN153. Wait for the error to recover. While waiting for recovery, the card issuing device 70
When the cause of the error disappears, for example, when the card stuck in 0 is removed, the process proceeds to the routine RN155 to clear each abnormal bit of the status 1 and 2 to “0”, and then proceeds to the routine RN156 to remove the card. The counters 795 and 796 for counting the number of cards and the number of confiscated cards are updated, and the process returns to the routine RN111 in the main processing flow (FIG. 132) (see reference numeral V1).

On the other hand, when a function from the central processing unit is received while waiting for error recovery in the routines RN153 and RN154, the process proceeds to the routine RN157, and it is determined whether or not the received function is a “status request” function. After transmitting the "status transmission" function in the next routine RN158, the process returns to the routine RN153 and waits for an error recovery again. This flow is common to that of the issuing-card issuing device, and is prepared on the assumption of a “status request” from the unit controller 290 of the issuing machine. If the function received while waiting for error recovery is not a "status request", the routine RN159 determines whether the received function is a "send initial value" function. Is stored in the internal memory, the "normal end" function is transmitted, and the process returns to the routine RN153, and waits for the error recovery again (routines RN160 and RN161).

If the function received during the error recovery wait is neither “status request” nor “initial value transmission”, the routine returns from the routine RN159 to RN152 to transmit the “abnormal end” function, and then waits for error recovery.

Next, an example of a control procedure of the card reader 800 by the card reader control device 288 based on a command from the card issue control device 790 will be described with reference to FIGS. 136 to 141. Note that the flow of this embodiment can be commonly used as any control flow on the assumption that the same card reader as that of the management device 400 is used for the settlement machine 300 and the issuing machine 200.

The major difference from the control flow relating to the card reader in the control unit 160 of the pachinko machine is that it has a control flow for writing and verifying the magnetic code and a flow for discharging the card to the rear of the card reader instead of to the front. is there.

As described above, the communication between the card reader control device 288 and the card issuance control device 790 is performed by transmitting a command as described above. As communication commands, a "magnetic write" command instructing to record the magnetic data of the card, and a "magnetic read" instructing to read the magnetic data of the card, the security code, and the information of the punch holes, and to send the magnetic data. Command, a "security request" command to send the read security data, a "punch hole request" command to send the read punch hole data, and the re-reading of the card data held in the card reader. "Reload" command to read and punch holes in the card Command to instruct the card reader to eject the card in the card reader toward the front insertion slot, and instruct the card reader to eject the card in the card reader backward. There are nine types of commands, a "card rear ejection" command, a "cancel" command for canceling a card reading command, and a "status request" command for instructing transmission of status information indicating the status of the card reader.

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 checkout machine 300 or the management device 400. The “magnetic read” command instructs the card reader 800 to read not only magnetic data but also all data on the card, and requests transmission of only magnetic data. Data request commands are separately prepared for security data and punch hole data.

FIG. 136 shows the entire procedure of the main control by the card reader control device 288, FIGS. 137 to 139 show the detailed procedure thereof, and FIGS. 140 and 141 separately show the main control. 2 shows a control procedure of an interrupt process generated 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 including various flags, counters, buffers, work areas, registers, etc. is cleared (routine R1101). Then, after setting the stack pointer when an interrupt occurs, initializing the I / O port and setting the state of the input / output terminals, the setting code is read and stored from the device code setting MCS, and then the card transport motor 807 is set. The relay RLY1 for supplying power to the power supply is turned on (routines R1102 to R1105).

Next, the monitor display 175 for displaying the cause of the error is set to the OFF state, and the power-on lamp LE indicating the power-on state is set.
After turning on D21, the "card insertion prohibition" flag in the internal RAM is set to "1" (routines 1106 to R1108). Then, after permitting the reception buffer to receive the command from the card issuing control device 790, it is checked whether or not the command has been received (routines R1109, R1110). If there is no received command, the flow shifts to the routine R1117 to check whether the "card insertion wait" flag is set to "1". If "0", the flow returns to the routine R1110 to wait for the reception of the command. 13th when the “waiting for card insertion” flag is “1”
7 After executing the card reading process shown in FIG. 7A, the process returns to the routine R1110. The card reading process is the same as the process when the “magnetic reading” command is received. The flowchart of this embodiment is designed so that it can be used in common when the same card reader 800 as the pachinko machine 100 or the issuing machine 200 is used for the checkout machine 300 or the management device 400. The flow to the "read process" is conscious of the control in the settlement machine or the management device. In the flow of the issuing machine, the "card insertion wait" flag is always set to "0" and has no meaning.

In the payment machine 3000, a “card accepted” 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 31
The "magnetic read" command is sent from the card reader controller 3
When it is sent to 88, it is determined that there is a reception in the routine R1110, and proceeds to the routine R1111. The "ESC" at the head of the command is detected, and the routine jumps to the routine R1118, proceeds to R1121, and the type of the command is determined. The flow shifts to the magnetic reading process in FIG. 137 (A), and the routine R1202 further shifts to the 138th.
The card reading process shown in FIG. 9A is executed. In this flow, while the insertion detection switch is off, the card is not read and the "card not read" flag is set, and the routine R120 is executed.
The process proceeds from R3 to R1204, sets the “card insertion wait” flag, and proceeds to the routine R1122 → R1117 in FIG. 136, where the process again proceeds to FIG. 137 (A). That is, it waits for the card to be inserted forever, and at the time of the insertion, the card reading process of FIG. 138 (b) is executed.

On the other hand, in the routine R1110, it is determined that the command is received,
If it is determined in the routine R111 that the received data is not “ESC” indicating the head of the command, it is determined in a routine R1112 whether the command is a cancel command “CAN” of the previously transmitted command. Unlike the other communication commands, the cancel command "CAN" does not have the start code ESC and the end code CS, and is transmitted by the command code itself, so that such determination can be made. When the received command is not “CAN” in the routine R112, the process proceeds to the routine R117. When the received command is “CAN”, the process proceeds to the next routine R1113 to set the “card insertion prohibition” flag and then turn on the card holding lamp. After turning off the light, setting a code indicating a normal end in the transmission buffer, executing the transmission processing of FIG. 138 (h) and transmitting the code to the card issuing control device 790,
Routine R1110 after clearing the "card insertion wait" flag
Return to This allows the card issuance control device 79
The card insertion waiting state by the “magnetic read” command transmitted from 0 is canceled.

Thereafter, the command is received again and the process proceeds to the routine R1111.If it is determined that the command head code is received, the process jumps to the routine R1118 to prohibit the reception of the subsequent command, and then turns off the monitor display 206 of the card reader, The OK lamp indicating the reception state of the card reader control device 288 is turned off (routines R1119 and R1120). Then, in a routine R1121, it is checked whether the received command corresponds to any of the above-mentioned nine commands. If not, a code indicating "command error" is written as error information in a memory in a routine R1124, and then the 139th command is written. The flow proceeds to the error processing routine shown in the figure. If the command corresponds to the registered command, the corresponding process is executed, the OK lamp is turned on, the process returns to the routine R1109, and the above procedure is repeated (routines R1122, R1123).

FIG. 137 (A) shows a processing procedure when a “magnetic read” command is received, and FIG. 137 (B) shows a “reload”.
The processing procedure when a command is received is shown. Since these command processes are irrelevant in the card issuing machine 200, the description is omitted.

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

When this command is received, first, the magnetic recording data sent in the form of ASCII code together with the “magnetic write” command is converted into a binary code suitable for internal processing and stored in the magnetic data buffer of the internal memory. A head code STX (see FIG. 2E) indicating the head of the magnetic data is inserted at the head of the magnetic data buffer, and the next magnetic recording data in the magnetic data buffer (the number of magnetic data is
The ETX code indicating the end of the data is entered in the 21st (in the case of 20) (routine R1231 to R1233). Next, after setting the number of magnetic data to be written (22 including the LRC calculated in the next routine), an address for sequentially reading magnetic recording data from the saved magnetic data buffer is set in the address counter ( Routine R1234, R123
Five).

Thereafter, the STX code (OBH) is set in a predetermined register A in advance in the routine R1236, and then the routine R12 is executed.
The process of exclusive-ORing the data of the register A with the next magnetic data in 37 to R1244 and then re-entering the result in the register A is repeated until the magnetic data is exhausted. Data error check code
LRC code is kept. Note that the routine R1236
First, the STX code (OBH) is set in the register A, so the first exclusive OR operation (routine R1238)
Then, the same data is calculated, the result is all “0”, and the same result as when STX is not included in the LRC calculation is obtained, so that the initial purpose can be achieved. In the processing of the routines R1237 to R1248, it is determined whether the number of ON bits (bits of “1”) in each read data is odd or even at the same time as the calculation of the LRC, and if it is even, the parity bit in each data is set to “ By setting it to 1 "and saving it in the data buffer, the addition of a parity (odd parity) bit is also performed (routines R1239 to R1241). LR above
After the C and parity bit calculation processing, a code indicating STX is inserted at the end (24th) of the magnetic data buffer (routine R1245). In other words, magnetic data and ETX and LRC are 2
Between two STX codes (see Fig. 2 (E)).

Next, it is determined whether the number of ON bits of the data (LCR) remaining in the register A is even or odd. Only when the number is even, the parity bit is set to “1” and the parity bit is added to the LRC itself. It is placed in a predetermined position (23rd character) in the data buffer (routines RR1246 to R1248).

Thereafter, the write processing (routines R1301 to R1337) shown in FIG. 138 (d) is executed to output the magnetic data and the write clock, and the verify processing (routines R1341 to R1361) of FIG. After executing and checking whether or not the magnetic data has been written correctly, it is determined whether or not a verify error has been detected (routine R1249).
If there is an error, a magnetic write error is set as error information in the memory, and then the process proceeds to the error processing routine of FIG. 139 (routine R1251). If there is no verify error, a "normal" response command is set in the transmission buffer, and then the transmission processing (routines R1421 to R1426) of FIG. 138 (h) is executed, and the process returns to the main flow of FIG. 136.

FIG. 137 (D) shows a control procedure of the card reader control device 288 when receiving a “status request” command from the card issuance control device 790.

When a "status request" command is received, the device code stored in the internal memory and the contents of status 1 are transferred to the transmission buffer, and a code CR indicating the end of the command is set to the address next to the last data in the transmission buffer. After that, STX is set as transmission data, and the STX is transmitted first (routines R1261 to R1264). Thereafter, the address of the transmission buffer is set in the counter, and after reading 1-byte data from the transmission buffer using the address and transmitting them, the address of the transmission buffer is updated (routines R1265 to R1268). Then, it is determined whether or not the CR code has been transmitted. If no, the process returns to the routine R1266 to transmit the next data, and the transmission of the CR code ends the processing for the “status request” command (routine R1269).

Further, FIG. 137 (E) shows a control procedure when a “pachinko hole request” command is received, and FIG. 137 (F) shows a control procedure when a “security request” command is received. The procedure of the response processing (R1271 to R1279 and R1281 to R1289) for these commands is exactly the same as the response processing for the "status request" command in FIG. 137 (D). The only difference is that first, instead of the device code and the contents of status 1, punch hole data or security data read from the card and held in the internal memory is transferred to the transmission buffer.

Further, FIG. 137 (G) shows a control procedure of the card reader control device 288 when a “punch hole” command is received from the card issue control device 790.

When this command is received, data indicating the hole to be drilled sent with the command (in this case, the issued hole)
The distance from the reference position is read from the ROM based on the punch hole position set in the RAM in the initialization routine or the like based on the ROM, and stored in the buffer (routine R1291).
The drilling process (R311 to R352) shown in FIG. 38 (g) is executed. Then, the "punch OK" flag is checked to determine whether or not the punching has been correctly performed (routine R1292). If yes, a normal response command is set in the transmission buffer (routine R1293), and then the process shown in FIG. The transmission process is executed, and if no, the punch failure bit of status 1 is set to "1", a punch error is written in the error information, and the process proceeds to the error processing routine of FIG. 139 (routines R1294, R129).
Five).

FIG. 137 (H) shows a control procedure in the card reader control device 288 when receiving the “card backward ejection” command.

When this command is received, the 1-second timer is set first, and then the motor 807 is rotated forward at high speed (routine R1401, R
1402). Then, it checks whether or not the timer set in the routine R1401 has timed out, and then checks whether or not the rearmost position detection sensor SNS4 in the card reader has been turned on (routines R1403, R1404). If the time-out occurs before the position detection sensor SNS4 is turned off, the process jumps to the routine R1413 to stop the motor 807 and then checks whether all the sensors are off (routine R1).
414). Here, if at least one of the sensors in the card reader is turned on, the card jam bit of status 1 is set to "1", and a card jam error is written as error information. Move to. If all the sensors are turned off in the routine R1414, it is determined that the discharge is completed, and the process jumps to the routine R1407.

On the other hand, if the position detection sensor SNS4 is turned off before the timer set in the routine R1401 times out, the motor 807 is stopped after waiting 0.4 seconds (routine
R1403). This is to wait for the card reversing device 740 behind the card reader to be driven and the card sent from the card reader 800 to be conveyed by the card reversing device 740.

After stopping the motor 807, the status 1 card jam bit is cleared and the routine R1351 shown in FIG.
After clearing the "verify error" flag set in step (1), the card holding LED is turned off (routines R1407 to R140
9). Thereafter, the "card insertion prohibition" flag is set to prohibit the insertion of the next card, and after setting the code of the "normal" response command in the transmission buffer, the transmission processing of FIG. 138 (h) is executed. Yes (routines R1410, R141
1).

FIG. 137 (I) shows a processing procedure of the card reader control device 288 when receiving a “card forward ejection” command from the card issuance control device 790.

This processing is a flow prepared because it is necessary in the card settlement machine 300, and is not executed in the card issuing machine 200, so that the description is omitted.

138 (a) and (b) show the specific procedures of the card reading process, the parity, and the LRC check process in the “magnetic read” command reception flow in FIG. 137 (A).
FIG. 138 (c) shows the specific procedure of the magnetic processing during the "reload" command reception flow of FIG. 137 (B). These processings are also executed by the card settlement machine, Since it is not executed, the description is omitted.

On the other hand, FIG. 138 (d) shows a specific procedure of the writing process in the flow of FIG. 137 (C). In this process, first, the rear end of the card is moved to the position of the position detection sensor SNS1 on the entrance side of the card reader 800, and then the number of magnetic data (ex. 24) is set in the counter (routine R
1301, R1302). At this time, the head of the card is the magnetic head 821
Has not reached the position. Then, after setting the head address of the magnetic data buffer containing the magnetic recording data in the address counter, the motor 807 is rotated at high speed to turn on the write enable signal for the magnetic head 821 (high level).
(Routines R1303 to R1305). After that, set the erase data “0” for providing a non-data area at the end of the track TRC2 of the magnetic data recording unit, set the 200 ms timer, and set the “write interrupt” flag to “1”. To start a write interrupt every 806 μsec (routines R1306 to R1308). The write interrupt is set to occur every 806 μsec (when the card transport speed is 300 mm / S) according to a detection signal from an encoder that detects the rotation of the motor 807.

Next, after checking the timer set in the routine R1307, the write crack data is inverted and the “write waiting” flag is set to “1”, and this flag is set to “0” in the write interrupt processing of FIG. 141. (Routines R1309 to R1312). Then, it is checked whether or not the position detection sensor SNS3 arranged slightly behind the magnetic head 821 is turned on (routine R1313).
Returning to 1309, the above procedure is repeated until the sensor SNS3 is turned on. By repeating the above loop, the write clock data is inverted every time the write interrupt is executed once every 806 μsec. As a result, the direction of magnetization of the magnetic portion of the card by the magnetic head is reversed every 806 μs, and clock data twice as long as 1.612 ms is written to the track TRC1 of the card. The position of the position detection sensor SNS3 is determined so that the magnetic head comes to the STX code writing start position of the track TRC2 when this sensor detects the end of the card. The routine proceeds to the routine R1314 to start writing magnetic data. If the timer set in the routine R1307 times out before the sensor SNS3 is turned on, it is determined that the card is jammed, and the routine jumps from the routine R1309 to R1336 to set the status 1 card jam bit to “1”. Then, a card jam is written in the error information, and then the flow shifts to an error processing routine of FIG. 139 (routine R1337).

If the position detection sensor SNS3 is turned on before the time is over, the process proceeds to the routine R1314, where the number of bits (5 bits) of each data (including parity) is first set in the counter, and then the address set in the routine R1303 is used. One-byte (8-bit) magnetic recording data is read from the magnetic data buffer and put into a shift register as a parallel-to-serial conversion means, and the address counter is incremented (routines R1315 and R1316). Then, the data in the output buffer is shifted to the left by two bits and one bit for a total of three bits (routines R1317 and R1318). This places the most significant bit of the 5-bit magnetic data at the left end of the shift register.

Then, next, in the routine R1319, it is determined whether or not the bit at the left end of the shift register is on, that is, whether it is “1”.
If “0”, the write data is inverted in the next routine R1320,
If “1”, the process jumps to the routine R1321 without inversion.
Thus, a write signal of the NRZI method can be formed and output. Following the output of the write data, the output of the write clock is also executed in the same procedure as that performed in the routines R1310 to R1312 (routine R1321).
~ R1323). Of these, the write data is on the second track TRC2 of the card, and the write clock is on the first track TRC1.
Write to each.

After the output of the 1-bit data, the bit counter is decremented to determine whether the counter has become "0",
If it is not "0", the process returns to the routine R1318, and the process of shifting the magnetic data in the shift register to the left by one bit and outputting the same is repeated until the bit counter becomes "0". Data is converted to serial write data and output (routine R1
324, R1325). When the output of the 1-byte magnetic data is completed, the process proceeds to the routine R1326, in which the number of magnetic data is decremented by 1, and then returns to the routine R1314 to repeatedly perform the parallel-to-direct conversion and output of the next magnetic data. When the output of all magnetic data is completed, the flow shifts to routine R1328 (routine R1327).

In the routine R1328, write clock data is output until the position detection sensor SNS4 is turned on in accordance with the same procedure as the routines R1309 to R1313 after setting the timer for 100 ms (routines R1329 to R1333). That is,
After writing the STX code as the last data of the magnetic data on the second track TRC2 on the first track TRC1 of the card, the clock data is continuously written until the end of the card (see FIG. 2E). ). Since the magnetic data is not inverted on the second track after the writing of the magnetic data is completed, the direction of the magnetization is fixed and the data is erased.

On the other hand, if the position detection sensor SNS4 is turned on before the timer over occurs in the routine R1329, the routine R1334
Then, the write permission signal to the magnetic head 821 is turned off (low level), and then the rotation of the motor 807 is stopped and the routine is terminated (routine R1335). Also, the position detection sensor SNS4
If the timer set in the routine R1328 causes a time-over before turning on, the program jumps to the routine R1336, sets a card jam in the status 1 and the error information, and proceeds to the error processing routine in FIG. 139.

FIG. 138 (e) shows a specific procedure of the verify process performed after the write process of FIG.

Here, first, the rear end of the card is the first in the card reader.
Motor 807 until detected by position detection sensor SNS1
Is reversed to retract the card, and then a one second timer is set (routine R1341, R1342). Then, motor 8
07 is rotated at high speed, the number of magnetic data is set (here, the STX code next to the LRC is not checked, so 23 is sufficient), and the second address of the magnetic data buffer is set in the address counter (routines R1343 to R1343). R1344). This is to exclude the first STX code from the target of verification.

After the address is set, the 1-bit read process shown in FIG. 138 (f) is executed to determine whether the data read in the routine R1346 and stored in the work area matches the STX code, and waits for a match. Proceed to the next routine R1347. In the routine R1347, 5 bits are set in the bit counter, 1 bit of the magnetic data is read in the 1-bit read processing shown in FIG. 138 (f), the bit is shifted into the least significant bit of the work area, and then the bit counter is decremented. This is repeated until the bit counter becomes "0", that is, until 5 bits are read (routine R1
347-R1349).

Then, the magnetic data read from the magnetic data buffer is compared with the magnetic data read from the card and stored in the shift register using the address set in the counter in the routine R1345 (routine R1350). Here, when the two data do not match, a verify error is set in the error information in the routine R1351, and when the data matches, the routine jumps from the routine R1350 to R1352 to increment the address counter of the magnetic data buffer, The routines R1347 to R1353 are repeated until the number of magnetic data is reduced by "1" and the number of magnetic data becomes "0" (routine R1354).

When the number of magnetic data becomes "0", the process proceeds to the routine R1355, where the 1-bit read latch is cleared to erase the read data, and then the 1-second timer set in the routine R1342 times out. (Routine R1356), and in the next routine R1357, it is determined whether the position detection sensor SNS4 is turned on. If the position detection sensor SNS4 is turned on before the time is over, the routine proceeds to routine R1358, where the card jam bit of status 1 is cleared, and then the motor 807 is stopped (routine R1359). On the other hand, if a time-out occurs before the position detection sensor SNS4 is turned on, the "card jam" bit of status 1 is set to "1", and then the card jam is written in the error information. The routine goes to (routines R1360, R1361).

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

In this process, the 1-bit read latch is first cleared (routine R581), and then each sensor in the card reader is cleared.
The size of the card is detected based on the outputs of SNS1 to SNS4 (routines R582 to R588). Then the routine R581
Check if magnetic data is latched in the read latch cleared in step 2. If yes, shift the work area to which the latch data is to be transferred by one bit to the left, and place the data of the latch into the least significant bit 0. Transfer and end (routines R589 to R590).

Incidentally, the card reader embodiment is longer than the card length l ₀ distance l ₃ is normal between the first and third position detection sensor SNS2, SNS3, second and third position detection sensor SNS1, SNS3 between the distance between the sensors as the distance l ₄ is shorter than the card length l ₀ of the normal is set (see Figure 30 (a)). Therefore, during the 1-bit reading process shown in FIG. 138 (f), the output of the first to third position detection sensors SNS1 to SNS3 is checked to detect a card size defect (routine R584). ~ R587).

FIG. 138 (g) shows a specific procedure of the drilling process in the “pachinko drilling” command reception flow of FIG. 137 (G).

In this hole punching process, first insert the card into the card reader 800
Move to the innermost part (Routine R311) and press "Punch OK"
After clearing the flag (Routine R312), the motor is reversed to start a timer (3 seconds) (Routine R313),
After setting the "movement amount detection" flag, the movement amount counter is cleared (routines R314 to R318). Then, the "timer 2 operation" flag is set to permit the timer interrupt, and the amount of movement is detected by the timer interrupt, and when the punching position is reached, the rotation of the motor is stopped (routine R319).
To R322), and waits for 150 msec to wait for the motor to completely stop (routine R323) before operating the punch device 820 (routines R324 to R327). The above routines R323 to R327
To make sure the holes are drilled (Routine R32
8) Clear the moving amount counter and reverse the motor at high speed to move the card in the direction where the punched hole that opens is facing the punched hole detection sensor SNSp. Then, it is determined whether or not the punch hole detection sensor is turned on. If the punch hole is opened at a regular position, the “punch OK” flag is set, and then the first position detection sensor SNS1 is turned on to turn on the card. When the rear end is detected, the timer interrupt and the motor are stopped (routines R329 to R340).

In the above routine, if a time-out occurs during the movement of the card, it is determined that a card jam (paper jam) has occurred, and error processing is started (routines R315, R332).

FIG. 138 (h) shows the “magnetic writing” of FIG. 137 (C).
FIG. 137 (H) shows the processing flow when receiving the “punch hole” command, FIG. 137 (H) shows the processing flow when receiving the “card backward ejection” command, and FIG. 137 (I). The specific procedure of the response command transmission processing in the processing flow at the time of receiving the “card forward ejection” command in () is shown below.

In the transmission process, first, the reception of the reception buffer is prohibited, and then the start address of the transmission buffer is set in the counter (routine R1421, R1422). Next, in each of the above flows, one byte of the transmission data saved in the transmission buffer is read and transmitted, and then the address counter of the transmission buffer is incremented (routines R1423, R142).
Four). Thereafter, it is determined whether the code CR indicating the end of the response command has been transmitted (routine R1425). If not, the process returns to the routine R1423 to sequentially transmit the next one-byte data, and returns to "C
If the "R" code has been transmitted, reception permission is given to the reception buffer, and then the process returns to the original routine (routine R142).
6).

On the other hand, FIG. 139 shows FIGS. 136 and 137 (A)-
A specific procedure of the error processing executed when an error occurs in the processing flows of (I) and FIGS. 138 (a) to (g) is shown.

In this error processing, monitor table data corresponding to the error information written according to the content of the error generated in each flow, that is, an error display code (see Table 7) is read out from the internal memory and is read out by the monitor display 175. To display the type of error (Routine R1131, R113
2). Then, the OK lamp is turned off, the "write inhibit" flag is set to "1" to inhibit the magnetic data write process, and then the timer 2 interrupt is stopped to inhibit the magnetic read process (routines R1133 to R1135). Thereafter, the motor 807 in the card reader 800 is stopped, the shutter solenoid 809 is turned off, the shutter is closed, and entry of the card is prohibited. Then, a response command corresponding to the type of error (see the right column of Table 7) is issued. Send (routines R1136 to R1138) and
The process returns to the routine R1109 in the main flow shown in the figure (reference numeral V2). Next, FIGS. 140 (A) and (B) show the procedure of processing when a read interrupt occurs, and FIG. 141 shows the processing procedure when a write interrupt occurs.

As described above, in the card reader 800 of this embodiment, the detection signal from the sensor 832 for detecting the rotation speed of the motor 807 is input to the card reader control device 288 as an interrupt signal, and FIG. When this signal comes in when the "timer 2 operation" flag inside the controller is set to "1" in the routine R524 in the card reading process flow of FIG. 140, the timer 2 shown in FIGS. When the "write interrupt start" flag is set in the routine R1308 in the write processing flow of FIG. 138 (d) after executing the interrupt processing, the write interrupt processing of FIG. 141 is executed. .

The speed sensor 832 is provided to face 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 rotating speed.

In the timer 2 interrupt processing, first, the routine reads the "security read" flag and the "punch hole read" flag in the routine R701, and when both are "0", enters the movement amount detection mode.
The flow shifts to R710, where the movement counter is incremented, and the interrupt processing ends. The movement detection mode is set during the magnetic processing shown in FIG. 138 (c) (routine R572) and during the punching processing shown in FIG. 138 (g) (routine R317). This is a case where the user wants to know the amount, and clears the “security reading” flag and the “punch hole reading” flag to set the movement amount detection mode. If the "movement amount detection" flag is "0" after entering the timer 2 interrupt processing, the process proceeds to the routine R702, where the movement amount counter is incremented, and then the routine is executed.
In R703, it is checked whether the "security reading" flag is set, and if it is set, the routine proceeds to the routine R704, and it is determined whether the movement amount is 4.8 mm or more (when the "security reading" flag is "0"). Shifts to the punch hole reading routine of FIG. 140 (B)). The "security reading" flag is set by the punch hole sensor SNSp in the routine R523 during the card reading process of FIG. 138 (a).
Is turned on, and at this time, the security code reading sensor 810a is located at the beginning of the security area (TF) of the card. Thus, the first security mark is provided at a position at least 4.8 mm away from the beginning of the security area. Therefore, it is determined in the routine R704 that the movement amount has become 4.8 mm or more. If it is 4.8 mm or less, the interrupt processing is terminated, and the movement amount counter is incremented again by the next timer 2 interrupt. And the movement amount is 4.8mm
When it reaches the routine R711, it first compares the movement amount with the read range set in the RMA in the routine R519, and if it is within the read range, determines whether the security code reading sensor is on. If ON, the counter for counting the width of the security code is incremented, and the interrupt processing is terminated (routines R712, R713). Then, when the code reading sensor is turned off, the value of the counter is checked (routine R714). If the width of the security code is "0", it is determined that there is no code, and the interrupt processing ends.
On the other hand, if the security width is not "0", the counter width is transferred to the buffer, the counter is cleared, and it is determined whether the security width is 0.5 mm or more (routine R71).
5, R716). Here, if the width is 0.5mm or less, it is regarded as abnormal,
If it is 0.5mm or more, the most significant (or least significant) bit of the security buffer operated as a shift register is set to "1"
Stand up. Then, when the next timer interrupt is entered and the reading is out of the reading range in the routine R711, the process proceeds to the routine R721 as the end of reading the first code, and the security reading number (counter) is decremented. Then, the security buffer storing the read code is shifted by one bit in the routine R723, and then the read range is added by the security code pitch (3.5 mm), and the processing is terminated. By shifting the security buffer every time one bit of security is detected, the serially read security code is converted into parallel data. By repeating the above routine, when the number of security readings becomes "0", the process proceeds from the routine R722 to R714. When the read security width is 0.5 mm, "1" is written to the most significant bit of the security buffer. Then, after the security reading, the process proceeds to the magnetic data reading process and proceeds to the thirteenth.
8 In the routine R553 of FIG. 8C, the "punch hole reading" flag is set to "1", and the "security reading" flag is set to "0".
When the timer 2 interrupt shown in FIG. 140 (A) is started after the timer is cleared, the routine shifts from the routine R703 to the routine R731 shown in FIG. 140 (B), and it is checked whether the punch hole detection sensor is on. If it is on, the counter for counting the punch hole width is incremented in the routine R732, and the interrupt processing ends. Then, if the punch hole detection sensor is turned off at the next interruption, the process proceeds to routine R733 to check the punch hole width. Here, the width of the detected punch hole is
If it is 0.8 mm or more, it is regarded as a regular punch hole and routine R
After writing “1” to the most significant (or least significant) bit of the buffer (operating as a shift register) that stores the presence or absence of a punch hole at 734, the width of the punch hole is again 0.8 mm
In the following cases, the punch hole width counter is cleared in the routine R735, and the process proceeds to the routine R736.

Here, it is determined whether or not the card moving amount is within the reading range. If the moving amount is within the reading range, the above procedure is repeated.

In the routines R741 to R745, the buffer containing the read bits is shifted by one bit by subtracting the number of punched holes read, the punched hole width counter is cleared, the read range is set again, and the processing ends. Then, when the number of readings becomes "0", the "timer 2 operation" flag is cleared and the subsequent timer 2 interrupt operation is stopped (routines R742 and R74).
6).

On the other hand, during the write processing flow of FIG. 138 (d), after the “write interrupt start” flag is set in the routine R1308, the rotation detection sensor 832 of the motor 807 of the card reader is set.
When a detection signal comes in at every 806 μS, the write interrupt process shown in FIG. 141 is started. First, the write clock data or the routine R1320, The write data and write clock data set in R1321 are output (routine R751). After a while, the routine R1311, R132
The "write waiting" flag set in 2 or R1331 is cleared, and the write interrupt processing ends (routine R752).

In the above embodiment, the same issuing device as the card issuing device 700 in the issuing device 200 is provided in the management device 400.However, the test card and the resurrection card are not printed with the amount of money, etc. In the case where it is sufficient to issue only the perforations and recording of magnetic data (for example, when using a preprinted card or a handwritten card), a card reader having a magnetic head 821 and a punch device 802 as shown in FIG. Only the 800 may be incorporated, and the card tank 901, the card removal device 710, the printing device 750, and the like may be omitted.

Furthermore, instead of having the card issuing device 700 built into the management device 400, the management device 400 sends a “card resurrection” packet or a “test card issuance” packet to the issuing device 200, and issues a resurrection card or test card at the issuing device. You may make it do. However, if it is provided in the management device, it does not generally hinder the purchase of the player.

Further, in the above-described embodiment, the case where the present invention is applied to a game machine provided with a pachinko game machine of an enclosed ball circulation system as an example of a game machine has been described. However, the present invention is not limited to this, and for example, A game machine equipped with a gaming machine configured to convert data into a real ball at each gaming machine and supply it to the inside of the gaming machine from a supply plate on the front of the gaming machine and play the game, and other storage media and the like. The present invention can be applied to a game facility provided with a game machine having any configuration (including a game machine other than a pachinko game machine) as long as the game can be played. In the above embodiment, a card having a magnetic storage unit is used as a game storage medium, but a so-called semiconductor memory is used as an information storage unit.
The present invention can also be applied to a game equipment management device using an IC card.

[Effects of the Invention] As described above, the present invention provides a terminal device such as a storage medium type game device capable of playing a game in relation to a storage medium in which required data is written, and a management device for managing the terminal device. In the storage-medium type gaming facility comprising: a storage medium writing means capable of writing data to at least an information storage unit of the storage medium; and a storage medium writing means for writing data to the information storage unit by the storage medium writing means. Storage medium issuing means capable of issuing a storage medium that can be used by writing,
The upper storage medium issuing means writes the data of the storage medium that has become unusable to the information storage section of the new storage medium so that the storage medium issuing means has the qualification to play the game. Since the device and the management device are configured to be able to issue a special storage medium that is qualified to test-operate the storage medium-type gaming device alone in a state where the device is not electrically connected, data of the storage medium that has become unusable can be deleted. By newly writing to the recording information section of the storage medium, a storage medium having a qualification for play can be reissued, so that even if an accident such as damage to the storage medium occurs, it is possible to effectively protect the profit of the player. it can. In addition, a special storage medium capable of operating the storage medium-type gaming device alone when the storage medium-type gaming device and the management device are not electrically connected can be issued. The test operation of the gaming device can be performed without operating the whole. In addition, since the management device is provided with the storage medium issuing means, the clerk of the game store can issue the reissued storage medium or the special storage medium while the business is open, and execute the respective processes. There is an effect that it becomes possible.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram showing an overall configuration of a pachinko gaming system to which the present invention is applied, and FIGS. 2A and 2B are front views showing an example of a card used in the system according to the present invention; FIG. 2 (C) is an explanatory view showing a configuration example of a true / false identification area in the card, FIG. 2 (D) is a cross-sectional view showing an example of a cross-sectional structure of the card, and FIG. 2 (E). Is an explanatory view showing a configuration example of a magnetic recording unit in the card, FIG. 3 is a perspective view showing a configuration example of the whole pachinko machine constituting the gaming system, and FIGS. 4 (A) and (B) are front views of the pachinko machine. FIG. 5 is an exploded perspective view of the operation panel unit, FIG. 6 is a perspective view of the inside of the operation panel unit, and FIG. 7 is a rear view of the pachinko machine. FIG. 8 is a perspective view showing a configuration example of a sealed ball circulating device, and FIG. 9 is a perspective view showing the details of the base of the hitting ball launching rail, FIG. 10 is a perspective view showing a state where the front panel of the pachinko machine is opened, and FIG. 11 is a game board. FIG. 12 is a perspective view showing a configuration example of a frame board provided with a frame holding a frame and a firing rail coupled thereto, FIG. 12 is a perspective view showing a rear configuration of a front frame of a pachinko machine, and FIG. 14 is a perspective view showing a configuration example of a pachinko machine control unit, FIG. 15 is a perspective view showing the internal configuration of the control unit, and FIG. 16 is a front panel of the control unit. 17 is a perspective view showing a positional relationship between a pachinko machine and a control unit, FIG. 18 is a perspective view showing a framework of an island facility in which the pachinko machine is installed, and FIG. 19 is an island facility. Pachinko machine and control unit FIG. 20 is a perspective view showing the back of the island equipment, FIG. 21 is a block diagram showing a control system of the entire pachinko machine, and FIG. 22 shows a circuit configuration example of the pachinko machine control device. Block diagram, FIG. 23 is a block diagram showing a circuit configuration example of the pachinko machine control unit, FIG. 24 is a memory map showing an area configuration of the unit memory, and FIG. 25 is a perspective view showing a configuration example of a card reader of the pachinko machine. FIG. 26 is an exploded perspective view of the card reader, FIG. 27 is an exploded perspective view showing details of a card insertion portion of the card reader, and FIGS. 29 (A) and (B) are cross-sectional side views showing details of a shutter portion at the entrance of the card reader, and FIG. 30 (A) is mounting of various sensors provided in the card reader. Plan view showing a positional relationship, FIG. 30 (B) is a detection timing chart of a sensor when a card is inserted, FIG. 31 is a block diagram showing a circuit configuration example of a card reader control device, FIG. 32 is a block diagram showing an interface circuit of the card reader, FIG. Figure is a timing chart showing the data reading and writing timing of the card reader, FIG. 34 is a perspective view showing a configuration example of a card issuing machine used in the gaming system according to the present invention, FIG. 35 is a front panel of the issuing machine FIG. 36 is a perspective view of a card issuing device provided in the issuing machine, FIG. 37 is a schematic configuration diagram of the same card issuing device, and FIG. 38 is a card removal device constituting the card issuing device. FIG. 39 is a perspective view showing a configuration of a card dispensing device which also constitutes a card issuing device, and FIG. 40 is a block diagram showing a configuration example of a control device of the card issuing machine. 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 checkout machine, and FIG. 42 (B) is a top panel of the checkout machine. FIG. 43 is a perspective view showing a state in which the front panel is opened, FIG. 43 is a perspective view showing an example of the structure of a card settlement apparatus which constitutes a checkout machine, and FIG. 44 is a view showing a counter of a pachinko parlor using the checkout machine of this embodiment. 45 (A) and (B) are explanatory diagrams showing an example of the structure of a receipt issued by a checkout machine, FIG. 46 is a block diagram showing an example of the structure of a control device of the checkout machine, FIG. FIG. 47 is a block diagram showing a configuration example of a unit control device of a checkout machine. FIG. 48 is a perspective view showing a configuration example of the entire management device. FIG. 49 is a block diagram showing a system configuration example of the management device itself. The figure shows a configuration example of the console of the management device.
(A) is a plan view, (B) is a rear view, FIG. 51 is a memory map showing a configuration example of a file in a main storage device, and FIG. 52 is a description showing a card state transition in the gaming system of the present invention. FIG. 53 is a block diagram showing a configuration example of a transmission system in the gaming system of the present invention. FIG. 54 is a NAU for controlling data transfer on a network.
55 (A) and (B) are block diagrams showing a packet structure between a management device and a NAU and between a management device and a unit on a high-layer network. Figure (C) shows a management device-NAU on a low-layer network.
FIG. 56 to FIG. 60 show configuration examples of packets transmitted and received on a high-layer network. FIG. 56 (A) and FIG. 57 (A) and (B) show the configuration of a “unit table request” packet, and FIGS. 58 (A) and (B) show the configuration of an “initial value setting” packet. 59 (A) and 59 (B) are diagrams showing the structure of the “periodic data request” from the management device to the pachinko machine and its response packet, and FIGS. 60 (A) and (B) are the “various command” packets and their FIG. 61 (A), (B) and (C) show the configuration of the “card-in” packet and its response “ACK” and negative acknowledgment “NAK” packet, and FIG. 62 ( A) to (D) show initialization procedures of the central processing unit and the local processing unit in the management device. FIG. 63 is a flowchart showing a processing procedure when the built-in switch on the back of the console is turned on in the management device. FIG. 64 is a flowchart showing a processing procedure when the setting update switch on the console upper surface is turned on in the management device. FIG. 65 is a flowchart showing a routine data request processing procedure by a timer interrupt, FIG. 66 is a flowchart showing a routine data reception processing procedure as a response, and FIG. 67 is a flowchart showing a procedure in which the management device transmits a “card purchase” packet. FIG. 68 is a flowchart showing a processing procedure when the management apparatus receives a “card in” packet. FIG. 69 is a flowchart showing a processing procedure when the management apparatus receives a “card in” packet. 70 is a flowchart showing the processing procedure of FIG. 70. FIG. 71 is a flowchart showing a processing procedure when a packet is received. FIG. 71 is a flowchart showing a processing procedure when the management apparatus receives an “end switch” packet. FIG. 72 is a flowchart showing a processing procedure when the management apparatus receives a “return-to-zero” packet. 73 is a flowchart showing a processing procedure when the management apparatus receives a "stop" packet, and FIG. 74 is a flowchart showing a processing procedure when the management apparatus receives a "card settlement" packet. FIG. 75 is a flowchart showing a processing procedure when the release switch on the upper surface of the console is turned on in the management device. FIGS. 76, 77 and 78 are forcible termination of the upper surface of the console in the management device. FIG. 79, FIG. 80, and FIG. 81 are flowcharts showing the processing procedure when the switch is turned on. FIG. 82 is a flowchart showing a procedure when the forced termination release switch on the upper surface is turned on. FIG. 82 is a flowchart showing a procedure of a power failure process in the management device when a power failure occurs. FIG. 83 is a network error recovery in the management device. FIG. 84 (A) is a flowchart showing a specific procedure of the NAU recovery processing in the processing flow of FIG. 83, and FIG. 84 (B) is a token bus in the processing flow of FIG. 83. FIG. 85 is a flowchart showing a specific procedure of the recovery processing. FIG. 85 is a flowchart showing a specific procedure of the hot code recovery processing in the processing flow of FIG. 83. FIG. 86 is a flowchart of the unit recovery processing in the processing flow of FIG. 83. FIG. 87 is a flowchart showing a specific procedure. FIG. 87 shows a processing procedure when the closing switch on the upper surface of the console is turned on in the management device. 88 is a flowchart showing a processing procedure when the card recovery switch on the upper surface of the console is turned on in the management apparatus, and FIG. 89 is a processing when the test card issuing switch on the back of the console is turned on in the management apparatus. A flowchart showing the procedure, FIG. 90 is a flowchart showing a procedure of an interruption display processing of business statistical data by a timer interruption, FIG. 91 is a flowchart showing a procedure of a data display processing of a hit table, and FIG. 92 is a data of a specific table A flowchart showing the procedure of the display processing, FIG. 93 is a flowchart showing the procedure of the data display processing of all the cars, FIG. 94 is a flowchart showing the procedure of the data display processing of the car in the red, and FIG. 95 is the data display processing of the black car FIG. 96 is a flowchart showing a procedure of a data display process of the issuing machine. 97, a flowchart showing the procedure of the data display processing of the checkout machine, FIG. 98 is a flowchart showing the procedure of all business data display processing, FIG. 99 is a flowchart showing the procedure of the data display processing of the specific card, FIG. 100 is a flowchart showing a procedure of a card total data display process, FIG. 101 is a flowchart showing a procedure of an all card detail data display process, FIG. 102 is a flowchart showing a procedure of a suspended card data display process, FIG. FIG. 104 is a flowchart showing a card number generation procedure in the management device, FIG. 104 is a display screen configuration diagram showing a configuration example of an initial screen displayed on the CRT display device in the management device, and FIG. 105 is displayed on the CRT display device in the management device. 106 is a display screen configuration diagram showing a configuration example of an abnormal terminal display screen. FIG. 107, FIG. 108, and FIG. 109 are display screen configuration diagrams showing a configuration example of an initial value setting screen displayed on a CRT display device in the management device. FIG. 111 is a display screen configuration diagram showing a configuration example of a hit count setting screen displayed on the CRT display device in the management device. FIG. 111 is a display showing a configuration example of a hit mode setting screen displayed on the CRT display device in the management device. Screen configuration diagram, FIG. 112 is a display screen configuration diagram showing a configuration example of a date and time setting screen displayed on the CRT display device in the management device, and FIG. 113 is a normal display during operation displayed on the CRT display device in the management device FIG. 114 is a display screen configuration diagram showing a configuration example of a hit release screen displayed on the CRT display device in the management device, and FIG. 115 is a display screen configuration diagram showing a configuration example of the CRT display device in the management device. Pachinko machine forced termination displayed FIG. 116 is a display screen configuration diagram showing a configuration example of a pachinko machine forced termination release screen displayed on the CRT display device in the management device, and FIG. 117 is a CRT display in the management device. FIG. 118 is a display screen configuration diagram showing a configuration example of an issuer forced termination release screen displayed on the device. FIG. 118 is a display screen configuration diagram showing a configuration example of a checkout machine forced termination release screen displayed on the CRT display device in the management device. FIG. 119 is a display screen configuration diagram showing a configuration example of a system end screen displayed on the CRT display device in the management device,
The figure shows a display screen configuration example of a card resurrection screen displayed on the CRT display device in the management device. FIG. 121 shows a display screen showing a configuration example of a display menu selection screen displayed on the CRT display device in the management device. Configuration diagram, FIG. 122 is a display screen configuration diagram showing a configuration example of a hitting table display screen displayed on the CRT display device in the management device, and FIG. 123 is a specific table display screen displayed on the CRT display device in the management device. 124 is a display screen configuration diagram showing a configuration example of an all-unit data display screen displayed on the CRT display device in the management device, and FIG. 125 is a display screen configuration diagram showing a configuration example of the CRT display device in the management device. FIG. 126 is a display screen configuration diagram showing a configuration example of a displayed redemption stand data display screen, FIG. 126 is a display screen configuration diagram showing a configuration example of an issuer data display screen displayed on a CRT display device in the management device, and FIG. 127. Is the management equipment 128 is a display screen configuration diagram showing a configuration example of a settlement machine data display screen displayed on a CRT display device in a display device. FIG. 128 is a display screen configuration showing a configuration example of a sales data display screen displayed on a CRT display device in a management device. Fig. 129 is a display screen configuration diagram showing a configuration example of a specific card data display screen displayed on the CRT display device in the management device. Fig. 130 is a card detail data display screen displayed on the CRT display device in the management device. 131 is a display screen configuration diagram showing a configuration example of a suspended card data display screen displayed on the CRT display device in the management device. FIG. 132 is a card issue control device in the management device. FIG. 133 is a flowchart showing a specific control procedure when the “card recovery” function is received in the flow of FIG. 132. FIG. 134 (A) is a flowchart showing a specific procedure of card ejection processing in the flow of FIG. 133, and FIG. 134 (B) is a specific procedure of reader control processing in the flow of FIG. 133. FIG. 134 (C) is a flowchart showing a specific procedure of the card reversing process in the flow of FIG. 133, and FIG. 134 (D) is a specific procedure of a printing process in the flow of FIG. 133. FIG. 134 (E) is a flowchart showing a specific procedure of the card ejection processing in the flow of FIG. 133, and FIG. 135 is an error in each processing flow of FIGS. 134 (A) to (E). FIG. 136 is a flowchart showing a specific procedure of error processing executed when the error occurs. FIG. 136 is a flowchart showing a control procedure common to the management device, the issuing machine, and the card reader control device in the checkout machine. A) is a flowchart showing a specific control procedure of the card reader control device when receiving the “magnetic read” command, and FIG. 137 (B) is a flowchart showing a specific control procedure of the card reader control device when receiving the “reload” command. FIG. 137 (C) is a flowchart showing a specific control procedure of the card reader control device at the time of receiving the “magnetic write” command, and FIG. 137 (D) is a specific example of the card reader control device at the time of receiving the “status request” command. 137 (E) is a flowchart showing a specific control procedure of the card reader control device when a “pachinko hole request” command is received, and FIG. 137 (F) is a flowchart showing a “security request” command. FIG. 137 (G) is a flowchart showing a specific control procedure of the card reader control device of FIG. 137 (H) is a flowchart showing a specific control procedure of the card reader control device at the time of receiving the “card backward ejection” command, and FIG. 137 (I) is a flowchart showing a specific control procedure of the card reader control device. FIG. 138 (a) is a flowchart showing the specific procedure of the card reading process in the flow of FIG. 137 (A), and FIG. 138 (a) is a flowchart showing the specific procedure of the card reading process when receiving the “forward ejection” command. FIG. (B) is a flowchart showing a specific procedure of the parity and LRC inspection processing in the flow of FIG. 137 (A), and FIG. 138 (c) is a specific processing of magnetic processing in the flow of FIG. 137 (B). 138 (d) is a flowchart showing a specific procedure of the writing process in the flow of FIG. 137 (C), and FIG. 138 (e) is a flowchart of FIG. 138 (C). FIG. 138 (f) is a flowchart showing a specific procedure of the verifying process in the flow, FIG. 138 (f) is a flowchart showing a 1-bit reading process in the flow of FIGS. 137 (c) and (e), and FIG. 138 (g). 137 is a flowchart showing a specific procedure of the hole making process in the flow of FIG. 137 (G), and FIG. 138 (h) is a concrete example of the transmission process in the control flow of FIGS. 137 (A) to (I). FIG. 139 is a flowchart showing a procedure. FIG. 139 is a flowchart showing a specific procedure of error processing when an error occurs in the control flow of FIGS. 137 (A) to (I). FIGS. 140 (A) and (B) are FIG. 141 is a flowchart showing a timer interrupt processing procedure for magnetic reading in the card reader controller. FIG. 141 is a flowchart showing a procedure for write interrupt processing during magnetic writing in the card reader control device. It is a door. 100 ... Pachinko machine, 110 ... Operation panel, 113 ... Purchase switch, 114 ... Pause switch, 115 ... End switch, 130 ... Ball circulation device, 160 ... Control unit, 180 ...
… Unit controller, 188 …… Card reader controller, 1
95… Pachinko machine controller, 190… Unit controller, 200… Card issuer, 700… Card issuer,
710 …… Card removal device, 740 …… Card reversing device, 750
…… Printing device, 770 …… Card dispensing device, 300 …… Checkout machine, 400 …… Management device, 550 …… Unit memory, 551…
... Data transmission controller, 553 ... Network controller, 800 ... Card reader, 802 ... Card insertion / ejection port, 807 ... Convey motor, 809 ... Shutter solenoid,
820: Punch device, 821: Magnetic head.

Claims (2)

(57) [Claims] 1. A storage medium type game facility comprising a terminal device such as a storage medium type game device capable of playing a game in relation to a storage medium in which required data is written, and a management device for managing the terminal device. In the above, the management device may include at least a storage medium writing unit that can write data to an information storage unit of the storage medium, and a storage medium that can be used by writing data to the information storage unit by the storage medium writing unit. And an issuable storage medium issuing means, wherein the upper storage medium issuing means has a playable qualification by writing data of the unusable storage medium to the information storage section of the new storage medium. A storage-medium-type gaming facility characterized in that a reissue storage medium can be issued. 2. A terminal device such as a storage-medium type game device capable of playing a game in connection with a storage medium in which required data is written, and a management device for managing the terminal device are connected by transmission means. In a storage-medium gaming facility in which the storage-medium type gaming device is capable of providing a regular game in a state where it is electrically connected to the management device by the transmission means, the management device includes at least information on a storage medium. A storage medium writing unit that can write data to the storage unit; and a storage medium issuing unit that can issue a storage medium that can be used by writing data to the information storage unit by the storage medium writing unit. The storage medium issuance means is a special storage device having a qualification for performing a test operation of the storage medium-type gaming device alone when the storage-type gaming device and the management device are not electrically connected to each other. Storage medium type game equipment, characterized in that it is enabling issue a medium.