JP7780098B2 - gaming machines - Google Patents

Description

The present invention relates to an amusement machine.

Gaming machines that use electronic information (electronic medals) as gaming value (gaming media) rather than physical (tangible) medals (also known as "smart gaming machines," "medalless gaming machines," "managed gaming machines," "sealed gaming machines," etc.) have been known for some time (see, for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 2022-053709

The problem that this invention aims to solve is to enable appropriate information processing in gaming machines that use electronic information as gaming value.

The present invention solves the above-mentioned problems by the following means (the configuration of the corresponding embodiment is shown in parentheses).
The present invention (tenth embodiment) is
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a game media number control means (a medal number control CPU 520, a medal number control means 520) having a game media number storage means;
A counting switch (47) and
the game medium number control means is capable of executing a counting process of subtracting a specific number of game media ("1") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time ("500" ms) (when the counting switch 47 is short-pressed);
The game media number control means is capable of executing a rental process of adding a predetermined number of game media ("50") to the total number of game media stored in the game media number storage means based on a game media rental operation (operation of the rental switch 202) performed in the dedicated unit (rental unit 200),
When the time from when the counting switch is turned on to when it is turned off is less than a predetermined time and a counting process is executed to subtract a specific number of game media, a counting sound having a length of time "T1" (200 ms) from the start to the end can be output (in FIG. 166, when the counting switch 47 is pressed briefly at the timing of "X182", a counting sound for a short press having a length of "200" ms from the start to the end is output at the timing of "X183").
When a lending process is executed in the dedicated unit to add a predetermined number of game media based on the lending operation of game media, a lending sound having a length of time "T2" (450 ms) from start to finish can be output (in FIG. 166, when the lending switch 202 is operated at the timing of "X187", a lending sound having a length of "450" ms from start to finish is output at the timing of "X188").
Time "T2" is longer than time "T1",
The time “T2” is equal to or greater than a specific time,
The lending process for adding a predetermined number of game media can be continuously executed at intervals of at least time "T3"("300" ms),
Time “T3” is a specific time,
When the lending process for adding a predetermined number of game media is executed consecutively at time intervals of "T3", even if the lending process for adding a predetermined number of game media is executed before one lending sound is output to its end, the output of the one lending sound that is currently being output continues and a new lending sound is not output from the beginning, and when the lending process for adding a predetermined number of game media is executed after one lending sound is output to its end, a new lending sound can be output from the beginning (Fig. 168).
It is characterized by:

The present invention makes it possible to perform appropriate information processing.

1 is a block diagram showing an outline of control of a slot machine, which is an example of a gaming machine, in a first embodiment. FIG. 2 is a diagram illustrating a first example of a power supply path in the first embodiment. FIG. 10 is a diagram illustrating a second example of a power supply path in the first embodiment. A figure showing a list of commands (main control commands) sent from the main control board to the dispensing control board in the first embodiment. A figure showing a list of commands (dispensing control commands) sent from the dispensing control board to the main control board in the first embodiment. A figure showing a list of commands (management device commands) sent from the management device to the dispensing control board in the first embodiment. A figure showing a list of commands (gaming machine commands) sent from the payout control board to the management device in the first embodiment. A flowchart showing the processing flow of the main routine in the dispensing control board in the first embodiment. 10 is a flowchart showing the flow of the main control command analysis process in step S110 of FIG. 8. 10 is a flowchart showing the flow of the main control command analysis process in step S110 of FIG. 8, and is a flowchart continuing from FIG. 9. 10 is a flowchart showing the flow of the lending process in step S119 of FIG. 8. 10 is a flowchart showing the flow of the counting process in step S117 of FIG. 8. 4 is a flowchart showing the flow of processing of a main routine on a main control board in the first embodiment. A flowchart showing the flow of power-on processing in the main control board and the payout control board in the first embodiment. A flowchart showing the flow of setting change processing in the main control board and the payout control board in the first embodiment. 10 is a flowchart showing the flow of three-coin bet processing on the main control board and payout control board in the first embodiment. 10 is a flowchart showing the flow of one-coin bet processing on the main control board and the payout control board in the first embodiment. 10 is a flowchart showing the flow of game start processing on the main control board and the payout control board in the first embodiment. 10 is a flowchart showing the flow of game termination processing on the main control board and the payout control board in the first embodiment. A flowchart showing the flow of the payout process in the main control board and the payout control board in the first embodiment. This is a flowchart showing the flow of the return process in the main control board and the dispensing control board in the first embodiment. A flowchart showing the flow of power-on processing in the dispensing control board and management device in the first embodiment. 10 is a flowchart showing the flow of the lending process in the dispensing control board and management device in the first embodiment. A flowchart showing the flow of counting processing in the dispensing control board and management device in the first embodiment. This is a flowchart showing the flow of the counting process in the dispensing control board and management device in the first embodiment, and is a flowchart continuing from Figure 24. A figure showing the waveforms of the data signal and strobe signal in serial communication between the dispensing control board and the management device in the first embodiment. 10 is a timing chart showing the on/off of each signal when an electronic medal is lent in the first embodiment. 10 is a timing chart showing the on/off of each signal during counting (refunding) of electronic medals in the first embodiment. FIG. 11 is a block diagram showing an outline of the control of the gaming machine in the second embodiment. FIG. 11 is a diagram illustrating the telegram between the gaming machine and the rental unit in the second embodiment. 10 is a diagram illustrating gaming machine performance information, gaming machine installation information, and hall control/fraud monitoring information in the second embodiment. FIG. 10 is a time chart showing a basic communication sequence in the second embodiment. 10 is a time chart showing Example 1 of a startup sequence (when the gaming machine is started first) in the second embodiment. 10 is a time chart showing an example 2 of a startup sequence (when the rental unit starts up first) in the second embodiment. 10 is a time chart showing a basic sequence of gaming machine information notification in the second embodiment. 10 is a time chart showing a counting notification sequence in the second embodiment. 10 is a flowchart showing a counting process in the second embodiment. 10 is a time chart showing a lending notification sequence in the second embodiment. FIG. 11 is a diagram showing a gaming machine information notification timer and a gaming machine information notification request flag in the second embodiment. 10 is a time chart showing an update sequence of a gaming machine information notification timer in the second embodiment. 10 is a flowchart showing gaming machine information management in the second embodiment. 10A and 10B are diagrams showing the internal memory of the main CPU 55 in the third embodiment, in which FIG. 10A shows an outline of the internal memory and FIG. 10B shows the internal register area. FIG. 2 is a diagram showing a detailed configuration of an F register. FIG. 11 is a diagram illustrating a stack area in the third embodiment. FIG. 11 is a diagram illustrating main instructions in the third embodiment. FIG. 10 is a diagram illustrating aspects of an LDF instruction and an LD instruction. FIG. 10 illustrates aspects of a CALLEX instruction. FIG. 1 is a diagram illustrating an example of a conventional CALL instruction and a RET instruction. 13 is a flowchart showing a program start (M_PRG_SET) in the third embodiment. FIG. 10 is a diagram showing an example in which a callex instruction and a jump instruction are used. FIG. 13 is a block diagram showing an outline of the control of the gaming machine in the fourth embodiment. FIG. 13 is a diagram showing a memory map of an internal memory in the fourth embodiment. 10A and 10B are diagrams showing division of regions in the fourth embodiment, in which (A) shows Example 1 and (B) shows Example 2. FIG. 13 is a diagram illustrating communication between areas in the fourth embodiment. FIG. 10 is a diagram showing an example of a program (example 1) for control areas 1 to 3. FIG. 10 is a diagram showing an example of a program (example 2) for control areas 1 to 3. FIG. 10 is a diagram showing an example of a program (example 3) for control areas 1 to 3. FIG. 10 is a diagram showing a modified example of the programs of control areas 1 to 3. 13 is a flowchart showing the game media number awarding process of the main control means in the fifth embodiment. 13 is a flowchart showing a game media number providing process of the game media number control means in the fifth embodiment. 13 is a flowchart showing an interrupt process (I_INTR) of the game media number control means in the fifth embodiment. 62 is a flowchart showing input port read processing (I_IN_READ) in step S801 of FIG. 61. 62 is a flowchart showing gaming machine information management (I_INF_CTL) in step S802 of FIG. 61. 64 is a flowchart showing hole control/fraud monitoring information set (I_INF_INJ) in step S823 of FIG. 63. A flowchart showing the gaming machine performance information set (I_INF_ABI) in step S824 of Figure 63. 64 is a flowchart showing the gaming machine installation information set (I_INF_INS) in step S825 of FIG. 63. A diagram showing the update sequence of the gaming machine information notification timer in the fifth embodiment. 62 is a flowchart showing count control (I_CAL_CTL) in step S803 of FIG. 61. 62 is a flowchart showing Example 1 of lending control (I_LEN_CTL) in step S805 of FIG. 61. 62 is a flowchart showing Example 2 of lending control (I_LEN_CTL) in step S805 of FIG. 61. 62 is a flowchart showing Example 3 of lending control (I_LEN_CTL) in step S805 of FIG. 61. 62 is a flowchart showing Example 4 of lending control (I_LEN_CTL) in step S805 of FIG. 61. 13 is a flowchart showing a first example of threshold processing by the main control unit in the fifth embodiment. 13 is a flowchart showing a second example of threshold processing by the main control unit in the fifth embodiment. 13 is a flowchart illustrating a first example of a threshold notification process of the sub-control means in the fifth embodiment. 13 is a flowchart illustrating a second example of a threshold notification process of the sub-control means in the fifth embodiment. FIG. 13 is a block diagram showing a gaming machine in a sixth embodiment. A diagram showing a memory area provided in the medal count control RWM in the sixth embodiment. A diagram showing a memory area provided in the medal count control RWM in the sixth embodiment. 13 is a flowchart showing a ratio calculation process in the sixth embodiment. 13 is a flowchart showing a ratio calculation process in the sixth embodiment. This is a flowchart showing the calculation of the ratio per 400 games in step S691 in Figure 81. This is a flowchart showing the calculation of the ratio per 400 games in step S691 in Figure 81. FIG. 20 is a diagram showing the transition of the difference number and MY in the sixth embodiment. FIG. 20 is a diagram showing the relationship between the transition of the difference counter and the MY counter and the power on/off in the sixth embodiment. 13 is a flowchart showing the flow from power-on to main processing in the sixth embodiment. 87 is a flowchart showing the error processing in step S543 of FIG. 86. 87 is a flowchart showing a complete function calculation process in step S555 of FIG. 86. In the sixth embodiment, (a) is a diagram showing an image that notifies the user of the activation of the complete function, and (b) is a diagram showing an example of an image displaying the activation of the complete function. FIG. 20 is a diagram showing a memory area for transmitting gaming machine performance information and a memory area for transmitting gaming machine installation information in the sixth embodiment. A diagram showing a memory area for transmitting hole control and fraud monitoring information in the sixth embodiment. 13 is a flowchart showing main processing of a medal count control CPU in the sixth embodiment. 13 is a flowchart showing interrupt processing by a medal count control CPU in the sixth embodiment. This is a flowchart showing the gaming machine information management in step S244 in Figure 93. 13 is a time chart showing an update sequence of a gaming machine information notification timer in the sixth embodiment. 13 is a time chart showing an update sequence of a gaming machine information notification timer in the sixth embodiment. 13 is a flowchart showing the generation of gaming machine performance information in the sixth embodiment. 13 is a flowchart showing the processing performed when storing a ratio in a memory area for transmitting gaming machine performance information in the sixth embodiment. 99 is a flowchart showing the ratio update process in step S524 of FIG. 98. 13A and 13B are diagrams showing the transmission and reception of commands between the main control CPU and the medal count control CPU in the seventh embodiment, where (a) shows an overview and (b) shows the content of the command. FIG. 20 is a diagram showing an example of transmission and reception of a bet request command and a bet request response command in the seventh embodiment. FIG. 20 is a diagram showing an example of transmission and reception of a bet request command and a bet request response command in the seventh embodiment. FIG. 23 is a diagram showing an example in which a bet request command is not transmitted in the seventh embodiment. 13A and 13B are diagrams illustrating an example of sending and receiving a settlement request command and a settlement request response command in the seventh embodiment. 13A and 13B are diagrams illustrating an example of sending and receiving a settlement request command and a settlement request response command in the seventh embodiment. 13A and 13B are diagrams illustrating an example of transmission and reception of an grant request command and a grant request response command in the seventh embodiment. 13A and 13B are diagrams illustrating an example of transmission and reception of an grant request command and a grant request response command in the seventh embodiment. 13 is a flowchart showing a main control process in the seventh embodiment. A flowchart showing the game start setting processing in step S932 of Figure 108. 109 is a flowchart showing the bet waiting process in step S933 of FIG. 108. 109 is a flowchart showing the settlement process in step S935 of FIG. 108. 113 is a flowchart showing the waiting time for receiving a request response command from the medal count control CPU 520 in step S975 of FIG. 111. 109 is a flowchart showing the bet process in step S936 of FIG. 108. 109 is a flowchart showing the assignment process in step S945 of FIG. 108. 13 is a flowchart showing main control interrupt processing by the main control CPU in the seventh embodiment. 13 is a flowchart showing the main processing of the medal count control CPU (medal count control main processing) in the seventh embodiment. 117 is a flowchart showing the main control command receiving process in step S1062 of FIG. 116. 118 is a flowchart showing the bet request command receiving process in step S1077 of FIG. 117. 118 is a flowchart showing the settlement request command reception processing in step S1078 of FIG. 117. 118 is a flowchart showing the grant request command reception process in step S1079 of FIG. 117. 13 is a flowchart showing medal count control interrupt processing by a medal count control CPU in the seventh embodiment. 13A and 13B are diagrams showing examples of image displays when the VL signal is off and when a communication error occurs in the seventh embodiment. FIG. 23 is a diagram showing an example of an image displayed when the complete function is activated while the VL signal is off in the seventh embodiment. 13 is a flowchart showing a main control program start process in the eighth embodiment. 13 is a flowchart showing a process of waiting for a request response from medal count control in the eighth embodiment. 126 is a flowchart showing the error display processing in step S1164 of FIG. 125. 13 is a flowchart showing main control interrupt processing in the eighth embodiment. 13 is a flowchart showing medal count control program start processing in the eighth embodiment. A flowchart showing the medal count control error display processing in step S1183 of Figure 128. 13 is a flowchart showing a medal count control main process in the eighth embodiment. 130. A flowchart showing the main control command receiving process in step S1188 of FIG. 13 is a flowchart showing medal count control interrupt processing in the eighth embodiment. 133 is a flowchart showing the input port check process (counting switch process) in step S1211 of FIG. 132. 133 is a flowchart showing the counting control process in step S1212 of FIG. 132. FIG. 13 is a block diagram of a gaming machine according to a ninth embodiment. FIG. 13 is a diagram showing an example of electrical connection between a gaming machine and a test firing test machine in the ninth embodiment. FIG. 13 is a diagram (1) showing data stored in the main control RWM described in the ninth embodiment. FIG. 22 shows data stored in the main control RWM described in the ninth embodiment. FIG. 13 is a diagram (3) showing data stored in the main control RWM described in the ninth embodiment. 13 is a flowchart showing a main control process in the ninth embodiment. A flowchart showing the game start setting processing of step S932 in Figure 140. 141 is a flowchart showing the bet waiting process in step S933 of FIG. 140. 140. This is a flowchart showing the settlement process of step S935 of FIG. 141 is a flowchart showing the bet processing in step S936 of FIG. 140. 140. This is a flowchart showing the start switch reception process in step S1241 in FIG. This is a flowchart showing the payout count signal setting process of step S1245 in Figure 140. 141 is a flowchart showing the assignment process in step S1246 in FIG. 140. This is a flowchart showing the game end check processing of step S1247 in Figure 140. This is a flowchart showing the LED display control of step S1052 during the main control interrupt processing (Figure 127) in the ninth embodiment. This is a flowchart showing test signal management in step S1053 during main control interrupt processing (Figure 127) in the ninth embodiment. 13 is a time chart showing the timing of the output of the payout count signal and the input request lamp signal, the lighting process of the input request lamp, and the lighting signal output process in the ninth embodiment. 13 is a time chart showing an example in which a specified number of bets are executed before the output of a payout count signal is completed in the ninth embodiment. 13 is a time chart showing an example in which the next game is started before the output of the payout count signal is completed in the ninth embodiment. 13 is a time chart showing an example in which the number of times the payout count signal is to be output for the next game is determined before the output of the payout count signal for the current game is completed in the ninth embodiment. FIG. 23 is a block diagram of a gaming machine according to a tenth embodiment. FIG. 23 is a front view of the gaming machine according to the tenth embodiment. 13 is a time chart showing the relationship between the display of the medal count display unit and the start timing of count notification in the tenth embodiment. 13 is a time chart showing the relationship between the display of the medal count display unit and the timing of the end of count notification in the tenth embodiment. 20 is a time chart showing the output of images and sounds for counting notification in the tenth embodiment. 13 is a time chart showing the relationship between the operation of the bet switch and the settlement switch, the total number of medals, and the count notification in the tenth embodiment. 20 is a time chart (1) showing the operation mode when the counting switch is pressed for a short time and when it is pressed for a long time in the tenth embodiment. 23 is a time chart (2) showing the operation mode when the counting switch is pressed for a short time and when it is pressed for a long time in the tenth embodiment. 13 is a time chart (1) showing the operation mode when the counting switch and the lending switch are operated in the tenth embodiment. 20 is a time chart (2) showing the operation mode when the counting switch and the lending switch are operated in the tenth embodiment. 20 is a time chart (1) showing the operation mode when the counting switch is pressed and held down and when the door is detected to be open in the tenth embodiment. 13 is a time chart showing the relationship between the counting sound and the lending sound when the counting switch is shortly pressed in the tenth embodiment. 13 is a time chart (1) showing the output mode of the lending sound when the lending switch is operated continuously in the tenth embodiment. 13 is a time chart (2) showing the output mode of the lending sound when the lending switch is operated continuously in the tenth embodiment. 13 is a time chart showing the relationship between the on/off of the settlement switch and the validity/invalidity of operation acceptance of the 3 bet switch and the like in the tenth embodiment. 13 is a time chart showing the screen display mode when the counting switch, lending switch, and 3-bet switch are operated in the tenth embodiment. A figure showing the relationship between the counting notification image and the recommended press order notification image in the 10th embodiment. 23 is a time chart showing the relationship between the 1 bet sound, the 3 bet sound, and the payment sound in the tenth embodiment. 19A and 19B are diagrams showing a menu screen and a counting notification image in the tenth embodiment. 19 is a time chart showing the display mode of the counting notification image and the menu screen when the 3-bet switch is operated in the tenth embodiment. 19A and 19B are diagrams showing a volume change image and a count notification image in the tenth embodiment. 20 is a time chart showing the display mode of a counting notification image and a volume change image during display of a demo screen in the tenth embodiment. 20 is a time chart showing a change in the counting sound when a volume change operation is performed during output of the counting sound in the tenth embodiment.

In this specification, the meanings of the terms are as follows:
"Game value (game medium)" refers to a medium used for games, and in this embodiment, it is "electronic information (electronic medal)."
Furthermore, "electronic information (electronic medals)" refers to money (banknotes) that, when inserted into the management device (CR unit) 200, is converted into electronic information corresponding to the amount, and part or all of that electronic information can be credited to the gaming machine as gaming value for playing games on the gaming machine.

Furthermore, the "management device (CR unit) 200" is a device for managing the lending and refunding of electronic information as gaming value, and is provided for each gaming machine and placed adjacent to that gaming machine. In a hall, the management device 200 is called a "sand" because it is placed between gaming machines. Furthermore, a gaming machine and the management device 200 corresponding to that gaming machine constitute a "gaming system."
Furthermore, "renting" refers to transferring electronic information as gaming value from the management device 200 to the gaming machine and crediting it inside the gaming machine.

Furthermore, "counting" refers to returning electronic information as the gaming value credited inside the gaming machine to the management device 200. When the counting switch 47 is operated, electronic information as the gaming value credited inside the gaming machine is returned to the management device 200. At this time, the number of credits becomes "0", and the electronic information managed by the management device 200 is increased accordingly.
Furthermore, "credit" refers to the storage of electronic information as gaming value inside a gaming machine.
Furthermore, the term "bet" refers to placing a bet on electronic information as gaming value to play a game. When the bet switch 40 is operated, electronic information as credited gaming value is bet.

The "prescribed number" refers to the number of bets that can be made to start (execute) a game in question.
Further, "payout" refers to adding electronic information representing a gaming value in a quantity corresponding to the payout of a winning combination to the number of credits based on the winning combination.
Furthermore, "bet medals" refer to electronic information representing the gaming value betted to play a game.
Furthermore, "reserved medals" refers to electronic information representing credited (reserved) gaming value.

In addition, a "reserved bet" means that by operating the bet switch 40, part or all of the electronic information as the gaming value credited inside the gaming machine is bet in order to play the game, within the range that can be bet on the game.
Furthermore, "automatic bet" means that when a replay wins, electronic information representing the gaming value of the number bet in the previous game is automatically bet by the control processing of the slot machine 10 as a gaming machine.

Furthermore, "cancel" refers to returning the electronic information (bet medals) representing the betted game value to credits by operating the cancel switch 46. When the cancel switch 46 is operated, the electronic information representing the betted game value is returned to credits. At this time, the number of bet medals becomes "0" and is added to the number of credits accordingly.
Furthermore, "return" refers to storing electronic information as game value stored inside the management device 200 on a card (such as a magnetic card or IC card) and ejecting the card from the card reader/writer 205. When the return switch 203 is operated, the electronic information is stored on the card and the card is ejected from the card reader/writer 205.

Furthermore, when a game progresses from the "N-1"th game, to the "N"th game, to the "N+1"th game, ... (where "N" is an integer of 2 or greater), and the current game is the "N"th game, the "N"th game is referred to as the "current game." The "N-1"th game is referred to as the "previous game." Furthermore, the "N+1"th game is referred to as the "next game."

In this specification, a number with "(B)" added to the end (especially 8-bit numbers) means a binary number. Similarly, a number with "(H)" added to the end means a hexadecimal number. Specifically, for example, a number representing "16" in decimal is written as "00010000(B)" in binary and as "10(H)" in hexadecimal. Furthermore, a number representing a decimal number is written as "16(D)" as necessary.
However, when it is clear whether the number is binary, decimal, or hexadecimal, the final symbols "(B)", "(D)", and "(H)" may be omitted.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
First Embodiment
The slot machine 10, which is an example of a gaming machine in the first embodiment, does not use physical (tangible) medals as gaming value (gaming medium) but uses electronic information (electronic medals). For this reason, the slot machine 10 of this embodiment does not include a medal insertion slot, a medal selector, a medal payout device, etc.

In addition, in the first embodiment, a management device (CR unit) 200 is placed adjacent to the slot machine 10, and the slot machine 10 and management device 200 are connected to enable two-way communication. Electronic medals can be transferred between the slot machine 10 and management device 200 through communication, and games can be played on the slot machine 10 using electronic medals transferred from the management device 200.

1 is a block diagram showing an outline of the control of a slot machine 10, which is an example of a gaming machine according to the first embodiment. In FIG. 1, the slot machine 10, a management device (CR unit) 200, and a hall computer 300 are shown.
As shown in FIG. 1, in this embodiment, the slot machine 10 includes, as representative control boards, a main control board 50, a sub-control board 80, and a payout control board 100 (credit number management board).

In Figure 1, the solid lines indicate communication lines for data exchange, and the direction of the arrows indicates the direction of data flow. For example, the main control board 50 and the dispensing control board 100 are configured to be able to communicate bidirectionally. In contrast, the main control board 50 and the sub-control board 80 communicate in one direction, from the main control board 50 to the sub-control board 80.
As shown in FIG. 1, the main control board 50 has an input port 51 and an output port 52, and is equipped with an RWM 53, a ROM 54, a main CPU 55, etc. (this does not mean that it is equipped with only those shown in FIG. 1).

Furthermore, as shown in FIG. 1, the main control board 50 and peripheral devices for game progression, including operation switches such as the bet switch 40, are electrically connected via an input port 51 or an output port 52.
The input port 51 is a connection part to which signals from an operation switch or the like are input, and the output port 52 is a connection part to which signals are transmitted to peripheral devices such as the motor 32 .
In Figure 1, input peripheral devices are indicated by arrows pointing from the signals from the peripheral devices to the main control board 50, and output peripheral devices are indicated by arrows pointing from the main control board 50 to the peripheral devices (the same applies to the sub-control board 80).

The RWM 53 is also a storage medium that can store (update) various data (variables) based on the progress of the game, etc.
Furthermore, the ROM 54 is a storage medium that stores programs and various data (for example, data tables) necessary for the progress of the game.
Furthermore, the main CPU 55 refers to a CPU (an IC with calculation functions) provided on the main control board 50, which executes programs and performs calculations necessary for the progress of the game, and specifically performs the drawing of winning roles, the drive control of the reels 31, and the payout when a prize is won.

An MPU including an RWM 53, a ROM 54, a main CPU 55, and a register is mounted on the main control board 50. The RWM 53 and the ROM 54 may be mounted inside the MPU or may be provided externally.
An MPU including an RWM 83, a ROM 84, and a sub-CPU 85 is also mounted on a sub-control board 80, which will be described later. The RWM 83 and ROM 84 may be provided externally instead of being mounted inside the MPU.

Also, as shown in FIG. 1, in this embodiment, the slot machine 10 is provided with operation switches operated by the player, including a bet switch 40, a start switch 41, (left, center, right) stop switches 42, a cancel switch 46, and a counting switch 47.
The bet switch 40, start switch 41, (left, center, right) stop switch 42, and cancel switch 46 are electrically connected to the main control board 50, and the counting switch 47 is electrically connected not to the main control board 50 but to the payout control board 100 (credit number management board) described later.

Here, "operation switch (or simply "switch")" refers to a device (including an electrical circuit and/or electrical components) that switches an electrical signal on/off based on (receiving external force from) the operation of an operating body by a player (operator), and does not limit the shape of the operating body operated by the player.
When the operation switch is in the OFF state, for example, light from the light-emitting element continues to be incident on the light-receiving element (when the light-receiving element continues to detect light, the operation switch is in the OFF state). Then, when the operation switch (the operating object) is operated by a player or the like, the light from the light-emitting element is no longer incident on the light-receiving element. When this state is detected, an electrical signal indicating that the operation switch has been turned ON is sent to the main control board 50. Note that, conversely to the above, the operation switch may be configured so that when the operation switch is in the OFF state, light from the light-emitting element does not enter the light-receiving element, and the switch is turned ON when light from the light-emitting element enters the light-receiving element.

In this embodiment, the operating body of the start switch 41 is lever-shaped (for this reason, it is also referred to as the "start lever (switch) 41"), and the operating bodies of the bet switch 40, stop switch 42, cancel switch 46, and counting switch 47 are push-button-shaped (for this reason, they are also referred to as the "bet button (switch) 40," "stop button (switch) 42," "cancel button (switch) 46," and "counting button (switch) 47").

In addition, although not shown in Figure 1, an LED (light emitting means) is provided on the operating body of the operation switch and/or around or near it. When the operation acceptance of that operation switch is in an permitted state, the LED corresponding to that operation switch, for example, emits blue light, and when the operation acceptance of that operation switch is in a prohibited state, the LED of that operation switch, for example, emits red light, thereby indicating to the player the permitted/prohibited state of that operation switch.

The bet switch 40 is an operation switch that is operated by the player when betting the electronic medals credited inside the slot machine 10 for the current game.
In this embodiment, the bet switches 40 include a 1 bet switch 40a for betting one electronic medal with one operation, and a 3 bet switch 40b for betting three (maximum number, specified number) electronic medals with one operation.
Alternatively, only one bet switch 40 may be provided, and three (the maximum number, a specified number) of the credited electronic medals may be bet by operating this bet switch 40 once.

The start switch 41 is an operating switch that is operated by the player when starting the reels 31 (left, center, and right reels) (to start the rotation of the reels 31).
Furthermore, three stop switches 42 are provided corresponding to the three reels 31 (left, center, and right), and are operation switches that are operated by the player when stopping the corresponding reel 31.

Furthermore, the cancel switch 46 is an operation switch that is operated by the player when returning the bet electronic medals (bet medals) to credits.
When the cancel switch 46 is operated, the bet electronic medals are returned to credits. At this time, the number of bets becomes "0" and the corresponding amount is added to the number of credits. For example, when three electronic medals have been bet, if the cancel switch 46 is operated, the number of bets becomes "0" from "3" and "3" is added to the number of credits.

The power switch 11 is a switch that is operated to turn the power of the slot machine 10 on or off.
The setting key switch 12 is a switch that is operated when changing or checking settings.
When the setting key is inserted into the setting key insertion slot and rotated clockwise by 90 degrees, the setting key switch 12 is turned on.
Furthermore, when the power switch 11 is turned off (power-off state), the setting key switch 12 is turned on, and then the power switch 11 is turned on in this state, the setting is being changed, i.e., the setting change mode is entered.
Furthermore, when the setting key switch 12 is turned on while the power switch 11 is on, the setting confirmation mode is entered.

The setting switch 13 is a switch that is operated when changing a setting value.
Each time the setting switch 13 is operated during the setting change, the setting value is incremented by "1".
In this embodiment, the setting values range from setting 1 to setting 6, and when changing the setting, each time the setting switch 13 is operated, the setting value changes from "1" → "2" → ... → "6" → "1" → ...
During the setting change, one of the setting values is displayed on a predetermined display device, and when the start switch 41 is operated, the displayed setting value is confirmed.

The reset switch 14 is a switch that is operated when initializing the RWM 53 or when clearing an error.
When the power switch 11 is turned on with the reset switch 14 turned on, an initialization process is performed and the predetermined data stored in the RWM 53 is cleared.
Furthermore, if the cause of the error is removed and the reset switch 14 is operated (turned on), the error is cleared.

In addition, the main control board 50 outputs an external signal (external end signal) from a part of the output port 52 to the external centralized terminal board 190 .
Here, the "external signal" is a signal to be output to the outside of the slot machine 10 (such as the hall computer 300 or a data counter installed in the hall) via the external centralized terminal board 190.
1, the main control board 50 is electrically connected to the hall computer 300 via the external centralized terminal board 190. Signals are transmitted unidirectionally from the main control board 50 to the external centralized terminal board 190, and signals are transmitted unidirectionally from the external centralized terminal board 190 to the hall computer 300.

As shown in FIG. 1, in this embodiment, the slot machine 10 is provided with an acquired number display LED 78 and a credit number display LED 76 as coin number display devices.
The winning number display LED 78 is electrically connected to the main control board 50, and the credit number display LED 76 is electrically connected not to the main control board 50 but to the payout control board 100 (credit number management board) described later.
The winning number display LED 78 is an LED that displays the number of electronic medals paid out (the number of medals won by the player) when a winning combination is achieved, and is composed of two digits, an upper digit and a lower digit.
The acquired number display LED 78 may be controlled to be turned off when there are no electronic medals to be paid out. Alternatively, the upper digits may be turned off and only the lower digits may be displayed as "0".

The acquired number display LED 78 normally displays the number of electronic medals paid out (acquired number), but when an error occurs, it also functions as an LED that displays the content (type) of the error.
Furthermore, in games where the order in which buttons are pressed is notified during AT, the winning number display LED 78 functions as an LED that displays button press instruction information (notifies the advantageous button press order).
Therefore, the winning number display LED 78 in this embodiment is an LED that also displays the number of payouts (winning numbers), error details, and push order instruction information. However, it is not limited to this, and it goes without saying that a dedicated LED or the like may be provided to display the push order instruction information.
During the AT, notification of the advantageous pressing order is also performed by the image display device 23 connected to the sub-control board 80.

As shown in FIG. 1, the main control board 50 is electrically connected to a motor 32 (a stepping motor in this embodiment) of the symbol display device.
The symbol display device includes reels 31 (three in this embodiment) that display symbols, motors 32 that drive each of the reels 31 , and a reel sensor 33 that detects the position of the reels 31 .

The motor 32 serves as a driving means for rotating the reels 31 , is connected to the rotation center of each reel 31 , and is controlled by the reel control means 65 .
Here, the reels 31 consist of a left reel 31, a center reel 31, and a right reel 31, and the stop switch 42 operated to stop the left reel 31 is the left stop switch 42, the stop switch 42 operated to stop the center reel 31 is the center stop switch 42, and the stop switch 42 operated to stop the right reel 31 is the right stop switch 42.

The reel 31 is ring-shaped, and has a reel tape attached to its outer periphery on which a plurality of types of symbols (symbols that make up symbol combinations corresponding to winning combinations) are printed.
Each reel 31 is provided with one index (or two or more). The index is provided in a convex shape on the circumferential surface of the reel 31, for example, and is used to detect whether the reel 31 has passed a predetermined position, whether it has made one rotation, etc. Each index is detected by a reel sensor 33.

The reel sensor 33 is electrically connected to the main control board 50. When the reel sensor 33 detects an index, the input signal is sent to the main control board 50, which detects that the reel 31 has passed a predetermined position.
In addition, the symbols on the reference position at the moment when the reel sensor 33 detects the index of the reel 31 are stored in advance in the ROM 54. This makes it possible to detect the symbols on the reference position at the moment when the index is detected. Furthermore, it becomes possible to identify how many pulses the (stepping) motor 32 needs to be driven from the moment when the reel sensor 33 detects the index of the reel 31 to stop the symbol on the pay line, counting from the symbol on the reference position.

When a player starts a game, they bet their credited electronic medals by operating the bet switch 40. When the start switch 41 is operated with the specified number of electronic medals bet for that game, the signal generated at that time is input to the main control board 50. Upon receiving this signal, the main control board 50 performs a lottery using the role lottery means 61 (internal lottery means) and controls the drive of all motors 32 to rotate all reels 31. As the reels 31 are rotated by the motors 32 in this way, the symbols on the reels 31 are displayed moving up and down within the display window at a predetermined speed.

Then, the player operates a stop switch 42 to stop the rotation of the reel 31 corresponding to that stop switch 42 (for example, the left reel 31 corresponding to the left stop switch 42).
When the stop switch 42 is operated, a signal generated at that time is input to the main control board 50. When the main control board 50 receives this signal, it drives and controls the motor 32 corresponding to that stop switch 42, and controls the stop of the reel 31 related to that motor 32 so as to correspond to the lottery result of the role lottery means 61 (the result determined by the internal lottery means). The game result of the current game is then displayed based on the symbol combination when all the reels 31 have stopped. Furthermore, when a symbol combination corresponding to any role stops on an active line (when that role wins), electronic medals corresponding to the winning role are paid out, etc.

Next, the specific configuration of the main control board 50 will be described.
1, the main CPU 55 of the main control board 50 includes the following role selection means 61. The following means in this embodiment are merely examples, and are not limited to the means shown in this embodiment.
The role lottery means 61 performs lottery (determination, selection) of winning numbers. Here, "lottery of winning numbers by the role lottery means 61" is the same as "internal lottery" in the Amusement and Entertainment Act Regulations (regulations regarding the certification and model inspection of gaming machines, etc.; hereinafter simply referred to as "the Regulations"). The lottery result by the role lottery means 61 is the same as "the result determined by internal lottery" in the Regulations. Therefore, the role lottery means 61 is also referred to as "internal lottery means 61" in accordance with the Regulations.

When the winning number is determined by the role lottery means 61, the winning and replay condition device number and the role condition device number are determined based on the winning number, and the winning and replay condition devices and role condition devices that will be operable in the game are determined. For this reason, the role lottery means 61 is also called a condition device number determination (lottery or selection) means, a winning role determination (lottery or selection) means, etc.
The winning lottery means 61 includes, for example, a random number generating means for the lottery (such as a hardware random number generator), a random number extracting means for extracting the random numbers generated by the random number generating means, and a winning number determining means for determining the winning number based on the random number value extracted by the random number extracting means.

The random number generating means generates random numbers in a predetermined range (for example, "0" to "65535" in decimal notation). The random numbers are generated by a counter that counts one cycle, for example, every 200 n (nano) seconds, from "0" to "65535," and continues to count random numbers while the slot machine 10 is powered on.
The random number extracting means extracts the random number generated by the random number generating means at a predetermined time, in this embodiment, when the start switch 41 is operated (turned on) by the player.
The winning number determination means checks the random number extracted by the random number extraction means against the lottery table to determine the winning number corresponding to the area to which the random number belongs.

The winning flag control means 62 controls the on/off of a winning flag corresponding to each winning combination based on the lottery result by the winning combination lottery means 61 .
In this embodiment, a winning flag is provided for each of all winning roles. When any of the winning roles is selected by the winning role selection means 61, the winning flag for that role is turned on (the winning flag is set). Winning roles include a case where there is one winning role (single winning) and a case where there are multiple winning roles (multiple winning).

When the reel control means 65 receives a command to start the rotation of the reels 31, particularly in this embodiment when it detects that the start switch 41 has been operated (on), it controls all (three) reels 31 to start rotating.
In addition, after the winning number is determined by the role lottery means 61, the reel control means 65 refers to the on/off status of the winning flag for the current game and selects a stop position determination table corresponding to the on/off status of the winning flag, and when the stop switch 42 is operated, determines the stop position of the reel 31 corresponding to the stop switch 42 based on the timing when the operation (on) of the stop switch 42 is detected, and drives and controls the motor 32 to stop the reel 31 at the determined position.

For example, in a game in which at least one winning flag is on, the reel control means 65 controls the reel 31 to stop so that a symbol combination corresponding to a winning role (a role for which the winning flag is on) can be stopped on an effective line within the range of the stop control of the reel 31, and also controls the reel 31 to stop so that a symbol combination corresponding to a role other than the winning role (a role for which the winning flag is off) cannot be stopped on an effective line.
Here, "within the range of the stop control of the reel 31" means the range of the time from the moment the stop switch 42 is operated until the reel 31 actually stops or the range of the amount of rotation of the reel 31 (number of moving symbols (frames)).

In this embodiment, the reel 31 rotates at a constant speed of approximately 80 rotations per minute.
When the stop switch 42 is operated, the time from the moment the stop switch 42 is operated until the reels 31 are stopped is set to within 190 ms, except for a predetermined reel 31 during MB operation (for example, the center reel 31). As a result, in this embodiment, the maximum number of moving symbols from the symbol at the moment the stop switch 42 is operated until the reels 31 are stopped is set to four symbols, except for a predetermined reel 31 during MB operation.
On the other hand, for a predetermined reel 31 during MB operation, the time from the moment the stop switch 42 is operated until the reel 31 is stopped is set to within 75 ms. As a result, for a predetermined reel 31 during MB operation, the maximum number of moving symbols from the symbol at the moment the stop switch 42 is operated until the reel 31 stops is set to one symbol.

Then, at the moment when the operation of the stop switch 42 is detected, if any of the symbols within the range of the stop control of the reel 31 is a symbol that should be stopped on a predetermined effective line, the symbol is controlled to stop on the predetermined effective line when the stop switch 42 is operated.
That is, if the reel 31 is stopped immediately at the moment the stop switch 42 is operated and the symbol of the winning combination corresponding to the winning number does not stop on the predetermined effective line, the reel 31 is controlled to rotate and move within the range of the stop control of the reel 31 until the reel 31 is stopped, thereby controlling the symbol of the winning combination corresponding to the winning number to stop on the predetermined effective line as much as possible (pull-in stop control).

Conversely, if the reel 31 is stopped immediately at the moment the stop switch 42 is operated, and a symbol combination of a winning combination not corresponding to the winning number stops on an effective line, the reel 31 is controlled to rotate and move within the range of the stop control of the reel 31 when the reel 31 stops, so that the symbol combination of a winning combination not corresponding to the winning number does not stop on an effective line (kick-off stop control).
Furthermore, in a game in which multiple winning combinations are achieved (for example, when the push order bell is achieved), the priority of the winning combinations is predetermined according to the order in which the stop switch 42 is pressed and the timing of operation of the stop switch 42, and the pulling-in stop control of the symbol associated with the most prioritized combination is performed according to the predetermined priority.

The winning determination means 66 determines whether or not the symbol combination of the reels 31 that has stopped on the pay line corresponds to any winning combination when the reels 31 have stopped.
Here, the winning determination means 66 does not actually detect whether the symbol combination corresponding to the winning combination has stopped on an active line. Specifically, based on the condition device operated in the game and the pressing order of the stop switch 42 and/or the operation timing of the stop switch 42, the winning determination means 66 determines in advance the symbol combination that will stop on an active line before the reels 31 actually stop, or determines in advance the symbol combination that will stop on an active line after the reels 31 have stopped.

When the winning determination means 66 determines that the symbol combination stopped on the effective line when the reels 31 stop matches a symbol combination corresponding to any winning combination and the winning combination is achieved, the payout means 67 performs processing to add the number of electronic medals corresponding to the winning combination to the credit amount.
Furthermore, when a replay wins, the payout means 67 performs control so that the electronic medals are automatically inserted (automatically bet) in the number inserted in the current game without adding the electronic medals to the credit amount.

The main control board 50 transmits to the sub-control board 80 information (control commands) necessary for the performance to be output by the sub-control board 80 .
Control commands include, for example, information when the bet switch 40 is operated, information when the start switch 41 is operated, information about the results of the role lottery (results determined by internal lottery), information when the stop switch 42 is operated, and information about the winning role.

The sub-control board 80 controls the selection and output of effects (information) during play and while waiting for play.
Here, the main control board 50 and the sub-control board 80 are electrically connected, and the main control board 50 transmits the information (control commands) necessary for outputting the performance to the sub-control board 80 in one direction via serial communication.
The main control board 50 and the sub-control board 80 are not limited to being electrically connected, but may be connected using optical communication means. Furthermore, in both the electrical connection and the optical communication connection, the communication is not limited to serial communication, but may be parallel communication, or both serial communication and parallel communication may be used.

Similar to the main control board 50, the sub-control board 80 includes an input port 81, an output port 82, an RWM 83, a ROM 84, a sub-CPU 85, and the like.
The sub-control board 80 is electrically connected to the following performance peripherals such as the performance lamps 21 shown in Fig. 1 via the input port 81 or the output port 82. However, the performance peripherals are not limited to these.

The RWM 83 is a storage medium that can temporarily store data, etc., that the sub-CPU 85 acquires when controlling the presentation.
The ROM 84 is a storage medium that stores programs and various data, such as those used when drawing lots for effects, as performance data.
Furthermore, the sub-CPU 85 refers to a CPU (an IC with calculation functions) provided on the sub-control board 80, which executes programs and performs calculations necessary for outputting effects during gameplay and game standby.

The effect lamps 21 are made up of, for example, LEDs, and light up or flash in a predetermined pattern when predetermined conditions are met.
The effect lamps 21 include a back lamp that is arranged on the inner periphery of each reel 31 and illuminates the patterns displayed on the reels 31 (three consecutive patterns visible from above and below through the display window) from behind, a fluorescent lamp that illuminates the patterns on the reels 31 from above the reels 31, and a frame lamp that is arranged in front of the front door of the slot machine 10 and flashes when a winning combination is achieved, etc.
Furthermore, the speaker 22 outputs a predetermined sound when a predetermined condition is met in order to perform various effects during the game.

Furthermore, the image display device 23 consists of an LCD display, an organic EL display, a dot display, etc., and displays various presentation images during play (such as the correct button press sequence, presentations corresponding to the conditional devices activated in the game), game information (such as the number of plays and number of coins won when the device is activated or during the advantageous zone (AT)), etc.
The sub-CPU 85 of the sub-control board 80 also includes a performance output control means 91. The performance output control means 91 determines what kind of performance should be output and at what timing based on the control command sent from the main control board 50, and controls the output of various performances from the peripheral devices for performance based on this determination.

As shown in FIG. 1, in this embodiment, the slot machine 10 includes a payout control board 100 (credit number management board).
The payout control board 100 also manages the number of credits of electronic medals.
Here, the main control board 50 and the dispensing control board 100 are electrically connected and configured to enable two-way communication.
In addition, the main control board 50 and the dispensing control board 100 are not limited to being electrically connected, but may also be connected using optical communication means.
In addition, in both electrical connection and optical communication connection, serial communication may be used, parallel communication may be used, or serial communication and parallel communication may be used in combination.

The payout control board 100, like the main control board 50 and the sub-control board 80, comprises an input port 101, an output port 102, an RWM 103, a ROM 104, and a credit number management CPU 105, etc.
In addition, the payout control board 100 is electrically connected to the main control board 50, the counting switch 47 as an operation switch, the credit number display LED 76 as a number display device, and a management device (CR unit) 200 external to the slot machine 10 via the input port 101 or the output port 102.

The RWM 103 is a storage medium capable of temporarily storing data and the like that is captured when the credit number management CPU 105 manages the credit number.
The ROM 104 is a storage medium that stores programs for managing the number of credits, various data, and the like.
Furthermore, the credit number management CPU 105 refers to a CPU (IC with a calculation function) provided on the payout control board 100, and executes programs and performs calculations required for managing the credit number.

The counting switch 47 is an operation switch that is operated by the player when returning the electronic medals credited inside the slot machine 10 to the management device 200 .
When the counting switch 47 is operated, the electronic medals credited inside the slot machine 10 are returned to the management device 200. At this time, the number of credits becomes "0", and the number of electronic medals managed by the management device 200 is increased accordingly.
For example, when 100 electronic medals are credited inside the slot machine 10, operating the counting switch 47 changes the number of credits from "100" to "0," and "100" is added to the number of electronic medals managed by the management device 200.

Also, for example, when three electronic medals have been bet and 100 electronic medals have been credited, operating the cancel switch 46 returns the bet electronic medals to credits. At this time, the number of bets changes from "3" to "0," and the number of credits changes from "100" to "103." After that, when the counting switch 47 is operated, the number of credits changes from "103" to "0," and "103" is added to the number of electronic medals managed by the management device 200.
In this embodiment, when a player stops playing, if there are electronic medals that have been bet, he or she first operates the cancel switch 46 to return the betted electronic medals to credits, and then operates the counting switch 47 to return the credited electronic medals to the management device 200.

However, when a replay is won in the previous game and the same number of electronic medals as bet in the previous game are automatically bet, the system is set so that the automatically bet electronic medals cannot be returned to credits even if the cancel switch 46 is operated. In other words, the system is set so that the automatically bet electronic medals cannot be returned to credits even if the cancel switch 46 is operated.
It is also possible to configure the system so that both the electronic medals bet based on the operation of the bet switch 40 and the electronic medals automatically bet based on a replay win can be returned to credits by operating the cancel switch 46 .

Furthermore, the betted electronic medals and the credited electronic medals may be returned to the management device 200 by operating the counting switch 47 .
For example, when three electronic medals have been bet and 100 electronic medals have been credited, operating the counting switch 47 may return the bet and credited electronic medals to the management device 200, causing the number of bets and the number of credits to become "0," and adding "103" to the number of electronic medals managed by the management device 200.
In this case, the cancel switch 46 may or may not be provided.

The credit number display LED 76 is an LED that displays the number of electronic medals credited inside the slot machine 10 .
In this embodiment, a maximum of 10,000 electronic medals can be credited. That is, the upper limit of the number of credits is set to "10,000." Therefore, the credit number display LED 76 is configured with five digits.
The upper limit of the number of credits is not limited to "10,000" and may be, for example, "15,000", "30,000", or "50,000".
Furthermore, the number of digits of the credit number display LED 76 is not limited to five digits, but can be set appropriately in accordance with the upper limit of the credit number.

In addition, an enable signal can be sent from the dispensing control board 100 to the main control board 50. The main control board 50 is set so that when the enable signal is on, it can execute various processes, and when the enable signal is off, it cannot execute certain processes.
In this embodiment, when the number of credits reaches the upper limit, that is, when the display of the credit number display LED 76 reaches "10000," the enable signal is turned off. Then, when the enable signal is turned off, the main control board 50 performs control so that operations of the bet switch 40 and the start switch 41 cannot be accepted.
The enable signal may be turned off when the number of credits reaches "15,000,""30,000," or "50,000."

Also, for example, it may be possible to play a normal game and a special game (1BB game; first-class big bonus game; activation of a first-class consecutive game device) that is more advantageous to the player than the normal game, and when a transition is made from normal game to special game, the game may be stopped at the end of the special game, and the game may no longer progress. In other words, a stop function may be provided. The conditions for stopping the game are not limited to the end of the special game, and can be set as appropriate. The enable signal may then be turned off when the conditions for stopping the game are met.

In this case, a stop/no stop setting switch can be provided to set (switch) whether the stop function is enabled (with stop) or disabled (without stop). A stop release switch can also be provided to release the stop function. When the conditions for a stop are met, the stop release switch can be operated to release the stop, allowing the game to continue and turning on the enable signal. The stop release switch can also be used in conjunction with other switches, such as the setting switch 13 or reset switch 14.

The credit number management CPU 105 of the payout control board 100 also includes credit number management means 111. The credit number management means 111 manages (adds or subtracts) the number of credits based on control commands sent from the main control board 50, control commands sent from the management device 200, and operation of the counting switch 47, and controls the display of the number of credits on the credit number display LED 76.

The management device (CR unit) 200 is a device for managing the lending and payout of electronic medals. One management device 200 is installed for each slot machine 10. In a hall, the management devices 200 are called "sands" because they are placed between the slot machines 10. A single gaming system is made up of a slot machine 10 and the management device 200 corresponding to that slot machine 10.

As shown in FIG. 1, the payout control board 100 of the slot machine 10 and the management device 200 are electrically connected to each other and configured to enable two-way communication.
The payout control board 100 and the management device 200 are connected via a game ball lending device connection terminal board.
Furthermore, the dispensing control board 100 and the management device 200 are not limited to being electrically connected, but may be connected using optical communication means.
Furthermore, in both electrical and optical communication connections, serial communication may be used, parallel communication may be used, or both serial and parallel communication may be used.

As shown in FIG. 1, the dispensing control board 100 is capable of two-way communication with the main control board 50, and is also capable of two-way communication with the management device 200.
Furthermore, through communication between the management device 200 and the payout control board 100, electronic medals can be transferred (lend) from the management device 200 to the payout control board 100, and the lent electronic medals can be credited to the payout control board 100.

Furthermore, by communication between the payout control board 100 and the main control board 50, it is possible to bet electronic medals credited to the payout control board 100 and play games, and when a winning combination is achieved, the paid-out electronic medals can be credited to the payout control board 100.
Furthermore, when a player stops playing, the electronic medals credited to the payout control board 100 can be transferred (refunded) to the management device 200 through communication between the management device 200 and the payout control board 100.

As shown in FIG. 1, the management device 200 includes a bill insertion slot 201, a loan switch 202, a return switch 203, a credit display unit 204, a card reader/writer 205, and the like.
The bill insertion slot 201 is an insertion slot for inserting bills (for example, 1,000 yen bills) required for lending electronic medals.
When a banknote inserted into the management device 200 through the banknote insertion slot 201 is correctly recognized, the credit corresponding to the inserted banknote is displayed on the credit display unit 204. The credit display unit 204 is configured, for example, with a three-digit seven-segment display. For example, when a 1,000 yen bill is inserted, the credit is displayed as "10," and when a 10,000 yen bill is inserted, the credit is displayed as "100."

The lending switch 202 is a switch that is operated by the player when lending an electronic medal, provided that the remaining number of times is displayed on the number display section 204.
For example, each time the lending switch 202 is pressed, electronic medals equivalent to the number "10" can be lent.
For example, when a 1,000 yen bill is inserted into management device 200 through bill insertion slot 201, the number of points displayed on point display unit 204 is "10," and the number of electronic medals loaned out per point of "1" is 5. In this case, if loan switch 202 is operated when the number displayed on point display unit 204 is "10," 50 electronic medals will be loaned out. Then, through communication between management device 200 and payout control board 100, the 50 loaned electronic medals are credited to payout control board 100.

The number of electronic medals credited to the payout control board 100 is displayed on the credit number display LED 76. For example, if 50 electronic medals are lent when the credit number is "0", the display on the credit number display LED 76 changes from "0" to "50".
In this way, in this embodiment, physical (tangible) medals are not loaned to players, but rather, through communication between the management device 200 and the payout control board 100, the loaned electronic medals are transferred from the management device 200 to the payout control board 100 and credited.

The return switch 203 is a switch that is operated by the player when he or she wishes to stop playing.
When the counting switch 47 of the slot machine 10 is operated, electronic medals are returned from the slot machine 10 to the management device. Then, when the return switch 203 of the management device 200 is operated, the number of electronic medals returned from the slot machine 10 to the management device 200 and the number of electronic medals corresponding to the frequency displayed on the frequency display unit 204 are stored as electronic data on a card (such as a magnetic card or IC card), and the card is ejected from the ejection port of the card reader/writer 205.

For example, suppose that the number of electronic medals displayed on the number display unit 204 of the management device 200 is "10" (equivalent to 50 electronic medals). Furthermore, suppose that 150 electronic medals are returned from the slot machine 10 to the management device 200 by operating the counting switch 47 of the slot machine 10. At this time, if the return switch 203 of the management device 200 is operated, electronic data equivalent to 200 electronic medals is stored in a card and is discharged from the discharge port of the card reader/writer 205.
1, the management device 200 is electrically connected to the hall computer 300. Information relating to the lending and refunding of electronic medals is transmitted unidirectionally from the management device 200 to the hall computer 300.

FIG. 2 is a diagram illustrating a first example of a power supply path.
Although not shown in Fig. 1, as shown in Fig. 2, the slot machine 10 is equipped with a power supply board 150. The power supply board 150 is also equipped with a capacitor 151 for storing electricity, and the payout control board 100 is also equipped with a capacitor 106 for storing electricity.
Furthermore, the power supply board 150 and the main control board 50 are connected by a harness A161, and power can be supplied from the power supply board 150 to the main control board 50 through this harness A161.

Furthermore, the power supply board 150 and the dispensing control board 100 are connected by a harness C163, and power can be supplied from the power supply board 150 to the dispensing control board 100 through this harness C163.
The power supply board 150 is supplied with AC power from the outside. The power supply board 150 then converts the AC to DC and supplies the power to the main control board 50 and the dispensing control board 100.
In addition, the main control board 50 and the dispensing control board 100 are connected by a harness B162, and power can be supplied from the main control board 50 to the dispensing control board 100, or from the dispensing control board 100 to the main control board 50, through this harness B162.

Furthermore, the main control board 50 and the dispensing control board 100 are connected by a harness D164, and through this harness D164, commands can be communicated in both directions between the main control board 50 and the dispensing control board 100.
The payout control board 100 is a control board that manages the number of credits of electronic medals, and since its stability has a significant impact on the player's profits, power is supplied directly to the payout control board 100 from the power supply board 150 via harness C163.

In addition, if harness C163 is broken, power can be supplied from the power supply board 150 to the dispensing control board 100 via harness A161, the main control board 50, and harness B162.
Furthermore, the dispensing control board 100 is equipped with a capacitor 106 for storing electricity, so that when the power supply from the power supply board 150 is cut off, power can be supplied to the dispensing control board 100 from the capacitor 106.

Furthermore, when harness A161 and harness C163 are broken, power can be supplied from capacitor 106 to the dispensing control board 100, and power can be supplied from the dispensing control board 100 to the main control board 50 through harness B162.
In this way, in Example 1, the payout control board 100 is equipped with a capacitor 106 for backup power supply, so that even if the power supply from the power supply board 150 is cut off due to the disconnection of harness A161 or harness C163, the payout control board 100 and the main control board 50 will continue to operate, ensuring that processing can be carried out in the event of a power outage, and preventing any disadvantage to the player.

FIG. 3 is a diagram illustrating a second example of a power supply path.
As shown in Figure 3, in example 2, the power supply board 150 is not equipped with a capacitor, and the dispensing control board 100 is equipped with a capacitor A107 and a capacitor B108 for storing electricity.
The power supply board 150 and the main control board 50 are connected by a harness E165, and power can be supplied from the power supply board 150 to the main control board 50 through this harness E165.

Furthermore, the power supply board 150 and the dispensing control board 100 are connected by a harness G167, and power can be supplied from the power supply board 150 to the dispensing control board 100 through this harness G167.
Furthermore, the main control board 50 and the dispensing control board 100 are connected by a harness F166, and power can be supplied from the main control board 50 to the dispensing control board 100, or from the dispensing control board 100 to the main control board 50, through this harness F166.

In addition, the main control board 50 and the dispensing control board 100 are connected by a harness H168, and through this harness H168, commands can be communicated in both directions between the main control board 50 and the dispensing control board 100.
In the event that harness G167 is broken, power can be supplied from the power supply board 150 to the dispensing control board 100 via harness E165, the main control board 50, and harness F166.

In addition, the dispensing control board 100 is equipped with capacitors A107 and B108 for storing electricity, and when the power supply from the power supply board 150 is cut off, power can be supplied to the dispensing control board 100 from capacitors A107 and B108.
Furthermore, when harness E165 and harness G167 are broken, power can be supplied from capacitor A107 and capacitor B108 to the dispensing control board 100, and power can be supplied from capacitor A107 to the main control board 50 through harness F166.

In Example 2, as in Example 1, when the power supply from the power supply board 150 is cut off, power is supplied to the dispensing control board 100 and the main control board 50 from a backup power supply capacitor mounted on the dispensing control board 100.
However, in Example 2, capacitor B108 is used as a backup power supply exclusively for payout control board 100. This ensures that even if the power supply from power supply board 150 is cut off due to, for example, the disconnection of harness E165 or harness G167, payout control board 100, which manages the number of credits of electronic medals, can be reliably driven, and processing can be reliably executed in the event of a power outage, preventing any disadvantage to the player.

In Example 2, it is preferable to set the capacitance of capacitor B 108 larger than the capacitance of capacitor A 107. This ensures that backup power is supplied to the payout control board 100, which is closely related to the player's profit, and that processing can be reliably executed in the event of a power outage.
In addition, in this embodiment, when the power is turned off, the program on the dispensing control board 100 is set to stop before the program on the main control board 50.
Furthermore, in this embodiment, when power is restored after a power outage, the program on the dispensing control board 100 is set to start before the program on the main control board 50.

4 to 7 are diagrams showing command lists.
Figure 4 is a diagram showing a list of commands sent from the main control board 50 to the dispensing control board 100, and Figure 5 is a diagram showing a list of commands sent from the dispensing control board 100 to the main control board 50.
In addition, Figure 6 is a diagram showing a list of commands sent from the management device 200 to the dispensing control board 100, and Figure 7 is a diagram showing a list of commands sent from the dispensing control board 100 to the management device 200.

Here, the commands sent from the main control board 50 to the dispensing control board 100 are collectively referred to as "main control commands."
In addition, the commands sent from the dispensing control board 100 to the main control board 50 are collectively referred to as "dispensing control commands."
Furthermore, the commands sent from the payout control board 100 to the management device 200 are collectively referred to as "gaming machine commands."
Furthermore, commands sent from the management device 200 to the dispensing control board 100 are collectively referred to as "management device commands."

In this embodiment, the main control command, payout control command, gaming machine command, and management device command are all composed of 16-bit (2-byte) data.
Furthermore, the main control command, payout control command, gaming machine command, and management device command are all composed of a preceding command (upper 8 bits) and a subsequent command (lower 8 bits).
That is, one main control command, payout control command, gaming machine command, and management device command is made up of 16 bits (2 bytes) of data consisting of a preceding command and a subsequent command.
Furthermore, the preceding command is data indicating the type of command, and the subsequent command is data indicating parameters (variables).
In this embodiment, commands are sent and received via serial communication between the main control board 50 and the dispensing control board 100, and between the dispensing control board 100 and the management device 200.

4 to 7, the data in the "Preceding" column indicates the preceding command (upper 8 bits), and the data in the "Subsequent" column indicates the subsequent command (lower 8 bits). Both the preceding command and the subsequent command are expressed in hexadecimal.
The main control commands include eight types of commands listed in the "Contents" column in Figure 4. Of these eight types of commands, the setting change start command, setting change end command, game start + RT state command, and game end + game state command are collectively referred to as "game information commands." Furthermore, the input request command, payout request command, and return request command are collectively referred to as "calculation request commands."

The payout control commands include the 12 types of commands listed in the "Contents" column in Figure 5. An ACK response to a deposit request command is also referred to as an "enter repeat command," and a NAK response to a deposit request command is also referred to as an "unavailable deposit command." Similarly, an ACK response to a payout request command, a NAK response to the same, and an ACK response to a return request command, a NAK response to the same are also referred to as a "payout repeat command," a "unavailable payout command," a "return repeat command," and a "unavailable return command," respectively. Furthermore, a NAK response in the event of an abnormality is also referred to as an "error command."

The management device commands include the five types of commands listed in the "Contents" column in Fig. 6. In addition, an ACK response to a lower-order count request command is also called a "lower-order count repeat command," and an ACK response to an upper-order count request command is also called a "upper-order count repeat command."
The gaming machine commands include 13 types of commands listed in the "Contents" column in Figure 7. The ACK response to the loan request command is also called a "loan repeat command."

In Figure 4, the startup confirmation command is a command used by the main control board 50 to confirm whether communication between the main control board 50 and the dispensing control board 100 is normal, and is a command sent from the main control board 50 to the dispensing control board 100 when the power is turned on.
When the power is turned on, the main control board 50 sends a startup confirmation command to the dispensing control board 100. When the dispensing control board 100 receives the startup confirmation command, it sends it back to the main control board 50 as is (ACK response to the startup confirmation command shown in Figure 5).
Then, on the main control board 50 side, the sent startup confirmation command is sent back directly from the dispensing control board 100, so it can be determined that communication between the main control board 50 and the dispensing control board 100 is normal.

Also, as mentioned above, when the power is cut off, the program on the dispensing control board 100 stops before the program on the main control board 50, and when the power is restored from the power cut, the program on the dispensing control board 100 starts before the program on the main control board 50.
When the power is turned on, i.e., when the power is restored after a power outage, the main control board 50 sends a startup confirmation command to the dispensing control board 100, but since the program on the dispensing control board 100 starts first, the startup confirmation command can be received reliably. The main control board 50 is then set to proceed with subsequent processing when it determines that communication between the main control board 50 and the dispensing control board 100 is normal, as the startup confirmation command it sent is returned from the dispensing control board 100 as is.

In Figure 4, the setting change start command is a command to notify the dispensing control board 100 that the setting change mode has been entered, and is a command sent from the main control board 50 to the dispensing control board 100 when the setting change mode is entered. The subsequent "01H" indicates that the setting key switch 12 is in the on state.
When the main control board 50 transitions to the setting change mode, it sends a setting change start command to the dispensing control board 100. Furthermore, when the dispensing control board 100 receives the setting change start command, it sends it back to the main control board 50 as is (ACK response to the setting change start command shown in FIG. 5), and also sends a setting change start command to the management device 200 (FIG. 7). In other words, the dispensing control board 100 sends the setting change start command to both the main control board 50 and the management device 200.

As a result, the dispensing control board 100 can determine that it has transitioned to setting change mode. Furthermore, the main control board 50 can determine that it has communicated the transition to setting change mode to the dispensing control board 100, as the sent setting change start command is returned unchanged from the dispensing control board 100. Furthermore, the management device 200 can also determine that it has transitioned to setting change mode.

In Figure 4, the setting change end command is a command to notify the dispensing control board 100 that the setting change mode has ended, and is a command sent from the main control board 50 to the dispensing control board 100 when the setting change mode has ended. The subsequent "00H" indicates that the setting key switch 12 is in the off state.
When the setting change mode ends, the main control board 50 sends a setting change end command to the dispensing control board 100. Also, when the dispensing control board 100 receives the setting change end command, it sends it back to the main control board 50 as is (ACK response to the setting change end command shown in Figure 5), and also sends a setting change end command to the management device 200 (Figure 7). In other words, the dispensing control board 100 sends the setting change end command to both the main control board 50 and the management device 200.

As a result, the dispensing control board 100 can determine that the setting change mode has ended. Furthermore, the main control board 50 can determine that the end of the setting change mode has been communicated to the dispensing control board 100, as the sent setting change end command is returned unchanged from the dispensing control board 100. Furthermore, the management device 200 can also determine that the setting change mode has ended.

In Figure 4, the game start + RT status command is a command to communicate that the game has started and the RT status to the payout control board 100, and is a command sent from the main control board 50 to the payout control board 100 when the start switch 41 is turned on.
When the start switch 41 is turned on, the main control board 50 transmits a game start + RT status command to the payout control board 100. Also, when the payout control board 100 receives the game start + RT status command, it sends it back to the main control board 50 as is (the ACK response of the game start + RT status command shown in FIG. 5), and further transmits a game start + RT status command to the management device 200 (FIG. 7). That is, the payout control board 100 transmits the game start + RT status command to both the main control board 50 and the management device 200.

This allows the payout control board 100 to determine that a game has started and that the RT state is in effect. Furthermore, the main control board 50 can determine that the game start and RT state have been communicated to the payout control board 100, as the sent game start + RT state command is returned unchanged from the payout control board 100. Furthermore, the management device 200 can also determine that a game has started and that the RT state is in effect.

In Figure 4, the game end + game status command is a command for communicating that the game has ended and the game status to the payout control board 100, and is a command sent from the main control board 50 to the payout control board 100 when the third stop switch 42 (the stop switch 42 corresponding to the reel 31 that stops last) changes from on to off.
When the third stop switch 42 changes from on to off (the player releases the third stop switch 42), the main control board 50 transmits a game end + game status command to the payout control board 100. Furthermore, when the payout control board 100 receives the game end + game status command, it sends it back to the main control board 50 as is (the ACK response to the game end + game status command shown in FIG. 5), and also transmits the game end + game status command to the management device 200 (FIG. 7). In other words, the payout control board 100 transmits the game end + game status command to both the main control board 50 and the management device 200.

This allows the payout control board 100 to determine that the game has ended and the game status. Furthermore, the main control board 50 can determine that the game has ended and the game status have been communicated to the payout control board 100, as the sent game end + game status command is returned as is from the payout control board 100. Furthermore, the management device 200 can also determine that the game has ended and the game status.

In Figure 4, the input request command is a command requesting the payout control board 100 to subtract the number of bets from the number of credits, and is a command sent from the main control board 50 to the payout control board 100 when the bet switch 40 is turned on.
The command following the input request command indicates the bet amount (the amount to be subtracted from the credit amount based on the operation of the bet switch 40).

In this embodiment, when the 1 bet switch 40a is turned on, the main control board 50 sends an input request command "2001H" (1 coin input request command) to the payout control board 100, requesting that the bet number "1" be subtracted from the number of credits.
In addition, when the 3-bet switch 40b is turned on, the main control board 50 sends an input request command "2003H" (3-coin input request command) to the payout control board 100, requesting that the bet number "3" be subtracted from the number of credits.
In addition, when the 3-bet switch 40b is turned on, a 1-coin insertion request command may be sent three times to the payout control board 100 as an insertion request command.

In addition, when the payout control board 100 receives an input request command, it determines whether it can accept the input request, specifically, whether the number of credits is greater than or equal to the number of bets (the number indicated by the command following the input request command).
Then, when it determines that the deposit request can be accepted, i.e., when it determines that the number of credits is equal to or greater than the number of bets, the payout control board 100 executes a process to subtract the number of bets from the number of credits, executes a process to update the display of the credit number display LED 76, and sends a deposit repeat command to the main control board 50 (it sends the received deposit request command back to the main control board 50 as is (ACK response to the deposit request command shown in Figure 5)).

For example, when the number of credits is "50" and a three-coin insertion request command "2003H" is received, the payout control board 100 executes a process to subtract the bet number "3" indicated by the command subsequent to the three-coin insertion request command "2003H" from the number of credits "50", changes the display on the credit number display LED 76 from "50" to "47", and sends an insertion repetition command to the main control board 50.
On the other hand, when it determines that the deposit request cannot be accepted, that is, when it determines that the number of credits is less than the number of bets (for example, when the number of credits is "2" and a command requesting the deposit of 3 coins, "2003H", is received), the payout control board 100 does not perform the process of subtracting the number of bets from the number of credits, but instead sends a deposit not permitted command to the main control board 50 (NAK response to the deposit request command shown in Figure 5).

Furthermore, when a deposit repeat command is received (the sent deposit request command is sent back as is from the payout control board 100), the main control board 50 determines that the request to subtract the number of bets from the number of credits has been granted, and executes processing according to the electronic medal bet (for example, processing to light up the 1 bet display LED to 3 bet display LED, and processing to enable operation of the start switch 41).
On the other hand, when the main control board 50 receives the insertion prohibition command, it determines that the request to subtract the number of bets from the number of credits is not permitted, and does not execute the process according to the electronic medal bet.
Furthermore, if a predetermined time has passed after sending the deposit request command and neither the deposit repeat command nor the deposit not possible command is received, a timeout occurs and the main control board 50 sends the deposit request command again to the dispensing control board 100.

In this way, when the payout control board 100 is requested to subtract the number of bets from the number of credits, one round trip of command communication is carried out between the main control board 50 and the payout control board 100 .
This allows the processing relating to electronic medal bets to be reliably executed by both the main control board 50 and the payout control board 100, and the number of credits to be managed accurately, so that no disadvantage is caused to the player.

Also, as mentioned above, when the power is cut off, the program on the dispensing control board 100 stops before the program on the main control board 50, and when the power is restored from the power cut, the program on the dispensing control board 100 starts before the program on the main control board 50.
Furthermore, when the bet switch 40 is turned on, the main control board 50 sends a deposit request command to the dispensing control board 100, and when the dispensing control board 100 receives the deposit request command, if it can accept the deposit request, it sends a deposit repeat command to the main control board 50, and if it cannot accept the deposit request, it sends a deposit not possible command to the main control board 50.

Furthermore, when the main control board 50 receives a deposit repeat command, it executes processing according to the bet of electronic medals, and when it receives a deposit disable command, it does not execute processing according to the bet of electronic medals, and when it receives neither a deposit repeat command nor a deposit disable command, it sends a deposit request command again to the payout control board 100.
Here, let us assume that after the main control board 50 sends a deposit request command to the dispensing control board 100, a power outage occurs and the program on the dispensing control board 100 stops before the dispensing control board 100 receives the deposit request command. In this case, the main control board 50 will not receive either the deposit repeat command or the deposit not possible command, and after the power is restored from the power outage, it will again send the deposit request command to the dispensing control board 100, so commands can be sent and received reliably between the main control board 50 and the dispensing control board 100.

Also, suppose that the main control board 50 sends a deposit request command to the dispensing control board 100, and the dispensing control board 100 receives the deposit request command, but before the deposit repeat command or the deposit disable command can be sent to the main control board 50, a power outage occurs and the program on the dispensing control board 100 stops. In this case, after the power is restored from the power outage, the dispensing control board 100 sends the deposit repeat command or the deposit disable command to the main control board 50, so commands can be sent and received reliably between the main control board 50 and the dispensing control board 100.

When the power is turned on, i.e., when recovering from a power outage, the main control board 50 sends a startup confirmation command to the dispensing control board 100. When the dispensing control board 100 receives the startup confirmation command, it returns it to the main control board 50 as is. When the dispensing control board 100 returns the startup confirmation command it sent as is, the main control board 50 determines that communication between the main control board 50 and the dispensing control board 100 is normal. The dispensing control board 100 then sends a deposit repeat command or a deposit disable command to the main control board 50. Therefore, when recovering from a power outage, the program on the dispensing control board 100 starts before the program on the main control board 50, but the main control board 50 can reliably receive the deposit repeat command or the deposit disable command.

Also, suppose that the main control board 50 sends a deposit request command to the dispensing control board 100, the dispensing control board 100 receives the deposit request command, and then sends a deposit repeat command or a deposit disable command to the main control board 50, after which a power outage occurs and the program on the dispensing control board 100 stops. In this case, the program on the dispensing control board 100 stops after the program on the main control board 50 stops, so the main control board 50 can receive the deposit repeat command or the deposit disable command sent by the dispensing control board 100, thereby ensuring reliable transmission and reception of commands between the main control board 50 and the dispensing control board 100.

In Figure 4, the payout request command is a command requesting the payout control board 100 to add the number of payouts to the number of credits, and is a command sent from the main control board 50 to the payout control board 100 when the third stop switch 42 changes from on to off.
Furthermore, the command following the payout request command indicates the payout amount (the amount requested to be added to the credit amount based on the winning combination).

For example, when a 10-coin winning combination is achieved, the main control board 50 sends a payout request command "210AH" to the payout control board 100 when the third stop switch 42 changes from on to off, requesting that the payout number "10" be added to the credit count.
Even when no winning combination is achieved, when the third stop switch 42 changes from on to off, the main control board 50 sends a payout request command to the payout control board 100. In this case, the number of payout coins is "0", so the payout request command is "2100H".

In addition, when the payout control board 100 receives a payout request command, it determines whether it is possible to accept the payout request, specifically, whether the upper limit of the number of credits ("10,000" in this embodiment) will be exceeded by adding the number of payouts (the number indicated by the command following the payout request command) to the number of credits.
Then, when it is determined that the payout request can be accepted, that is, when it is determined that adding the payout number to the credit count still results in the credit count being below the upper limit, the payout control board 100 executes a process to add the payout number to the credit count, executes a process to update the display of the credit count display LED 76, and sends a payout repetition command to the main control board 50 (sends the received payout request command back to the main control board 50 as is (ACK response to the payout request command shown in Figure 5)).

For example, when the number of credits is "50" and a payout request command "210AH" (payout of 10 coins) is received, the payout control board 100 executes a process to add the payout number "10" indicated by the command subsequent to the payout request command "210AH" to the number of credits "50", changes the display on the credit number display LED from "50" to "60", and sends a payout repeat command to the main control board 50.

On the other hand, when it determines that the payout request cannot be accepted, that is, when it determines that adding the payout number to the credit count would exceed the upper limit of the credit count (for example, when the credit count is 9995 and a payout request command "210AH" (payout of 10 coins) is received), the payout control board 100 will not perform the process of adding the payout number to the credit count, but will send a payout unacceptable command to the main control board 50 (NAK response to the payout request command shown in Figure 5).

Furthermore, when a payout repeat command is received (the sent payout request command is sent back as is from the payout control board 100), the main control board 50 determines that the request to add the payout number to the credit count has been granted, and executes processing according to the payout of electronic medals based on the winning combination (for example, processing to display the number of electronic medals to be paid out on the winning number display LED 78).
On the other hand, when a payout impossible command is received, the main control board 50 judges that the request to add the payout number to the credit number is not permitted, and does not execute processing according to the payout of electronic medals based on the winning combination.

In this way, when the payout control board 100 is requested to add the number of payout coins corresponding to the winning combination to the credit amount, one round trip of command communication is performed between the main control board 50 and the payout control board 100.
As a result, processing related to the payout of electronic medals based on winning combinations is reliably executed on both the main control board 50 and the payout control board 100, and the number of credits is accurately managed, so that no disadvantage is caused to the player.

In Figure 4, the return request command is a command that requests the payout control board 100 to return the betted electronic medals to credits, and is a command that is sent from the main control board 50 to the payout control board 100 when the cancel switch 46 is turned on.
Furthermore, the command following the return request command indicates the number of medals to be returned (the number of medals to be added to the credits based on the return of the medals).
For example, when the cancel switch 46 is operated with three electronic medals bet, the main control board 50, when the cancel switch 46 is turned on, sends a return request command "2203H" to the payout control board 100 requesting that the return number "3" be added to the credit amount.

In addition, when the payout control board 100 receives a return request command, it determines whether the return request can be accepted, specifically, whether the upper limit of the number of credits ("10,000" in this embodiment) will be exceeded by adding the number of credits to the number of return coins (the number indicated by the command following the return request command).
Then, when it is determined that the return request can be accepted, that is, when it is determined that adding the return number to the credit count still results in the credit count being below the upper limit, the payout control board 100 executes a process to add the return number to the credit count, executes a process to update the display of the credit count display LED 76, and sends a return readback command to the main control board 50 (it sends the received return request command back to the main control board 50 as is (ACK response to the return request command shown in Figure 5)).

For example, when the number of credits is "100" and a return request command "2203H" is received, the payout control board 100 executes a process to add the return number "3" indicated by the command following the return request command "2203H" to the number of credits "100," changes the display on the credit number display LED from "100" to "103," and sends a return repetition command to the main control board 50.

On the other hand, when it is determined that the return request cannot be accepted, that is, when it is determined that adding the number of return medals to the number of credits would exceed the upper limit of the number of credits (for example, when the number of credits is 9999 and the return request command "2203H" is received (a return request for three electronic medals has been made)), the payout control board 100 will not perform the process of adding the number of return medals to the number of credits, but will send a return unacceptable command to the main control board 50 (NAK response to the return request command shown in Figure 5).

Furthermore, when a return repeat command is received (the returned request command sent is returned as is from the payout control board 100), the main control board 50 determines that the request to add the number of returned medals to the number of credits has been permitted, and executes processing according to the return of the electronic medals (for example, processing to turn off the 1 bet display LED to 3 bet display LED, and processing to make operation of the start switch 41 unacceptable).
On the other hand, when a non-returnable command is received, the main control board 50 determines that the request to add the number of returned medals to the number of credits is not permitted, and does not execute the process corresponding to the return of the electronic medals.

In this way, when a request is made to the payout control board 100 to return the betted electronic medals to credits, one round trip of command communication is carried out between the main control board 50 and the payout control board 100 .
This ensures that the process for returning electronic medals is executed reliably on both the main control board 50 and the payout control board 100, and the number of credits is managed accurately, so that the player is not disadvantaged.

In Figure 6, the loan request command is a command requesting the dispensing control board 100 to add the number of loaned cards to the number of credits, and is a command sent from the management device (CR unit) 200 to the dispensing control board 100 when the loan switch 202 is turned on.
Furthermore, the command following the lending request command indicates the number of medals to be lent (the number of medals to be lent that is requested to be added to the credit number based on the lending of the electronic medals).

For example, when a 1,000 yen bill is inserted into the bill slot 201 of the management device 200 and the point display unit 204 displays the point number "10", and the lending switch 202 is operated, the management device 200, when the lending switch 202 is turned on, sends a lending request command "4032H" to the dispensing control board 100 requesting that the lending number "50" be added to the credit amount.

In addition, when the dispensing control board 100 receives a loan request command, it determines whether the loan request can be accepted, specifically, whether the credit count exceeds the upper limit (10,000 in this embodiment) by adding the loan count (the number indicated by the command following the loan request command) to the credit count.
Then, when it is determined that the loan request can be accepted, that is, when it is determined that adding the number of loaned cards to the number of credits still results in an amount below the upper limit of the number of credits, the dispensing control board 100 sends a loan repeat command to the management device 200 (sends the received loan request command back to the management device 200 as is (ACK response to the loan request command shown in Figure 7)).

On the other hand, if it determines that the loan request cannot be accepted, that is, if it determines that adding the loan number to the credit count would exceed the upper limit of the credit count (for example, if the loan request command "4032H" (loan count "50") is received when the credit count is "9955"), the dispensing control board 100 will send the error command "E000H" to the management device 200 (NAK response in the event of an abnormality as shown in Figure 7).

Furthermore, when a loan repeat command is received (the loan request command sent is returned as is from the dispensing control board 100), the management device 200 sends a loan instruction command to the dispensing control board 100 to instruct it to execute the loan request, and further performs a process to update the display of the number display unit 204 according to the number of loans.

For example, when the management device 200 sends "4032H" (lend number "50") to the dispensing control board 100 as a loan request command, and then the dispensing control board 100 sends "4032H" (ACK response to the loan request command) to the management device 200 as a loan repeat command, the management device 200 sends "4132H" to the dispensing control board 100 as a loan instruction command, instructing it to add the loan number "50" to the credit count. Furthermore, the management device 200 executes a process to subtract "10" points corresponding to the loan number "50" from the value displayed on the point display unit 204.

On the other hand, when an error command is received, the management device 200 controls the device to return to the standby state.
Furthermore, when a lending instruction command is received, the payout control board 100 executes a process of adding the number of loaned coins to the number of credits, and executes a process of updating the display of the credit number display LED 76 .
For example, when the number of credits is "50" and a loan instruction command "4132H" (number of credits to be loaned "50") is received, the payout control board 100 executes a process to add the number of credits "50" to the number of credits "50" by the loan number "50" indicated by the command subsequent to the loan instruction command "4132H", and changes the display of the credit number display LED from "50" to "100".

In this way, when the management device 200 lends electronic medals to the payout control board 100 of the slot machine 10, command communication is carried out between the management device 200 and the payout control board 100 in one and a half round trips.
This ensures that processing related to the lending of electronic medals is executed reliably by both the management device 200 and the payout control board 100, and the number of credits is managed accurately, so that no disadvantage is caused to the player.

In Figure 7, the lower counting request command and the upper counting request command are commands that request the management device (CR unit) 200 to refund electronic medals, and are commands that are sent from the payout control board 100 to the management device 200 when the counting switch 47 is turned on.
Furthermore, the command following the lower-order count request command indicates the lower 8 bits when the payout number (number of credits) is expressed in 16 bits (2 bytes).
Furthermore, the command following the higher-order count request command indicates the upper 8 bits when the payout number (number of credits) is expressed in 16 bits.
That is, the number of coins to be paid out is determined from the command subsequent to the lower-order count request command and the command subsequent to the higher-order count request command.

As described above, in this embodiment, the upper limit on the number of credits is set to "10000 (D)." Furthermore, the upper limit on the number of credits, "10000 (D)," is expressed as "10011100010000 (B)" in binary, and "2710 (H)" in hexadecimal. Thus, the upper limit on the number of credits, "10000 (D)," cannot be expressed in 8 bits (1 byte). For this reason, in this embodiment, the payout number (number of credits) is specified using 16 bits (2 bytes) in the commands following the lower-order count request command and the upper-order count request command.

For example, suppose the counting switch 47 is operated when 1,000 electronic medals are credited to the payout control board 100 (credit number "1,000 (D)"). Here, the credit number "1,000 (D)" is expressed in binary as "1111101000 (B)" and in hexadecimal as "03E8 (H)". In this case, the lower-order counting request command is "50E8 (H)" and the upper-order counting request command is "5103 (H)". Then, when the counting switch 47 is turned on, the payout control board 100 sends "50E8 (H)" to the management device 200 as the lower-order counting request command.

Furthermore, when the management device 200 receives a lower-level counting request command, it determines whether or not it is possible to accept a refund request.
Then, when it is determined that the refund request can be accepted, the management device 200 sends a lower-level counting repeat command to the dispensing control board 100 (sends the received lower-level counting request command back to the dispensing control board 100 as is (ACK response to the lower-level counting request command shown in Figure 6)).
On the other hand, if the management device 200 determines that the withdrawal request cannot be accepted, it sends an error command "E000H" to the dispensing control board 100 (NAK response in the event of an abnormality as shown in Figure 6). In this case, the management device 200 controls the board to return to a standby state.

Also, when a lower-order counting repeat command is received (the sent lower-order counting request command is sent back as is from the management device 200), the dispensing control board 100 sends "5103 (H)" to the management device 200 as an upper-order counting request command.
In contrast, when an error command is received, the dispensing control board 100 controls the board to return to a standby state without sending a higher-level counting request command.

In addition, upon receiving the upper counting request command, the management device 200 sends an upper counting repeat command to the dispensing control board 100 (sends the received upper counting request command back to the dispensing control board 100 as is (ACK response to the upper counting request command shown in Figure 6)).
Furthermore, when a higher-order counting repeat command is received (the sent higher-order counting request command is sent back as is from the management device 200), the payout control board 100 sends a counting instruction command to the management device 200, and further executes a process to clear the number of credits (set it to "0") and update the display of the credit number display LED 76 (set it to "0").

Furthermore, when a counting instruction command is received, the management device 200 controls the process to reflect the number of payouts identified from the lower-level counting request command and the upper-level counting request command in the number of electronic medals managed by the management device 200.
Thereafter, when the return switch 203 is operated, the management device 200 stores the number of electronic medals returned to the management device 200 from the slot machine 10 (payout control board 100) by operation of the counting switch 47, and the number of electronic medals corresponding to the degree displayed on the degree display unit 204, as electronic data on a card (magnetic card, IC card, etc.), and ejects the card from the ejection port of the card reader/writer 205.

In this way, when electronic medals are paid out from the payout control board 100 of the slot machine 10 to the management device 200, command communication is carried out between the payout control board 100 and the management device 200 in one and a half round trips.
This ensures that the process for paying back electronic medals is executed reliably by both the payout control board 100 and the management device 200, and the number of credits is managed accurately, so that the player is not disadvantaged.

In this embodiment, a unique ID consisting of 4 bytes of data is set in the credit number management CPU 105. In Fig. 7, the first to fourth bytes of the CPU unique ID are a command for transmitting the first to fourth bytes of the ID unique to the credit number management CPU 105 to the management device 200.
When the dispensing control board 100 is powered on, it sequentially transmits the first to fourth bytes of the CPU unique ID to the management device 200.

Furthermore, when the management device 200 receives the first to fourth bytes of the CPU unique ID, it stores (preserves) them in a predetermined storage area and transmits them to the hall computer 300 in sequence.
Furthermore, when the hall computer 300 receives the first to fourth bytes of the CPU unique ID, it stores (preserves) them in a predetermined storage area.
Furthermore, the management device 200 and the hall computer 300 are capable of keeping the first to fourth bytes of the stored CPU unique ID as history.

For example, if the payout control board 100 is fraudulently replaced, the credit number management CPU 105 installed on the payout control board 100 will change, and the first to fourth bytes of the CPU unique ID stored in the management device 200 and the hall computer 300 will also change from the point of replacement.
Therefore, by checking whether the first to fourth bytes of the CPU unique ID stored in the management device 200 and the hall computer 300 have changed along the way, it is possible to determine whether the payout control board 100 has been fraudulently replaced.

FIG. 8 is a flowchart showing the flow of processing of the main routine in the dispensing control board 100.
In the main routine of the dispensing control board 100, when any signal is input to the input port 101 in step S101, the process proceeds to the next step S102, and the dispensing control board 100 executes a determination process to determine whether the input signal is an on signal for the counting switch 47.
If it is determined that the signal is an ON signal from the count switch 47, the process proceeds to the next step S103, where the count request flag is set to ON, and then the process proceeds to the next step S104.
On the other hand, if it is determined that the counting switch 47 is not an ON signal, step S103 is skipped and the process proceeds to step S104.

In step S104, the dispensing control board 100 executes a process to determine whether the VL signal is on or not.
If a VL signal (18V DC signal) is supplied from the management device (CR unit) 200 to the dispensing control board 100, step S104 determines that the VL signal is ON, and determines that the management device 200 and the dispensing control board 100 are connected normally, and proceeds to step S105, where the VL error flag is cleared. Then, proceeds to step S107.
On the other hand, if the VL signal is not supplied from the management device 200 to the dispensing control board 100, in step S104, it is determined that the VL signal is off, and it is determined that the management device 200 and the dispensing control board 100 are not properly connected, and the process proceeds to step S106, where a process of setting a VL error flag is executed, and then the process proceeds to step S107.

In step S107, the dispensing control board 100 performs a determination process to determine whether the signal input (received) to the input port 101 is a main control command.
If it is determined that the input signal is a main control command, the process proceeds to the next step S108, where the dispensing control board 100 stores (saves) the input main control command in a predetermined storage area of the RWM 103. Then, the process proceeds to the next step S109.
On the other hand, if it is determined that the input signal is not a main control command, step S108 is skipped and the process proceeds to step S109.

In step S109, the dispensing control board 100 executes a process to determine whether the stored command is a main control command.
If it is determined that the stored command is a main control command, the process proceeds to step S110, where the dispensing control board 100 executes a main control command analysis process (FIGS. 9 and 10). The details of the main control command analysis process will be described later. After the main control command analysis process is executed, the process proceeds to step S111.

In step S111, the dispensing control board 100 performs a determination process to determine whether or not the counting process (Figure 12) is being performed.
Here, the counting process is a process that starts when the answer to step S116, which will be described later, is "Yes," and details thereof will be described later. Furthermore, while the counting process is being executed, the main routine of the dispensing control board 100 can be executed in parallel with this counting process. Therefore, in step S111 of the main routine of the dispensing control board 100, a determination process is executed as to whether the counting process is being executed.
The counting process in progress flag is set when the counting process starts, and is cleared when the counting process ends. By checking whether the counting process in progress flag is on or off, it is possible to determine whether the counting process is being executed.

If it is determined in step S111 that the counting process is being executed, the process according to this flowchart is terminated without executing the processes from step S113 onwards.
If it is determined in step S111 that the counting process is currently being executed, the counting process is continued thereafter.
On the other hand, if it is determined in step S111 that the counting process is not currently being executed, the process proceeds to step S113, and the dispensing control board 100 executes a process to determine whether the lending process (Figure 11) is currently being executed.

Here, the lending process is a process that starts when the result of step S118, which will be described later, is "Yes," and details thereof will be described later. Furthermore, while the lending process is being executed, the main routine of the dispensing control board 100 can be executed in parallel with this lending process. Therefore, in step S113 of the main routine of the dispensing control board 100, a determination process is executed as to whether the lending process is being executed.
At the start of the lending process, a lending process in progress flag is set, and at the end of the lending process, the lending process in progress flag is cleared. By checking whether the lending process in progress flag is on or off, it is possible to determine whether the lending process is in progress.

If it is determined in step S113 that the lending process is currently being executed, the process according to this flowchart is terminated without executing the processes from step S115 onwards.
If it is determined in step S113 that the lending process is currently being executed, the lending process is continued thereafter.
On the other hand, if it is determined in step S113 that the lending process is not currently being executed, the process proceeds to step S115, and the payout control board 100 executes a process of determining whether or not a gaming machine command is currently being transmitted.

Here, the gaming machine command transmission process is a process that is executed when the result of step S118, which will be described later, is "No." Also, while the gaming machine command transmission process is being executed, the main routine of the payout control board 100 can be executed in parallel with this gaming machine command transmission process. Therefore, in step S115 of the main routine of the payout control board 100, a process is executed to determine whether the gaming machine command transmission process is being executed.
If it is determined in step S115 that the gaming machine command transmission process is being executed, the process according to this flowchart is terminated without executing the processes in step S116 and thereafter.
On the other hand, if it is determined in step S115 that the gaming machine command transmission process is not currently being executed, the process proceeds to step S116, and the payout control board 100 executes a process of determining whether the count request flag is on or not.

If it is determined in step S116 that the count request flag is on, the process proceeds to step S117, where the dispensing control board 100 starts the counting process (FIG. 12), and the process according to this flowchart is then terminated.
On the other hand, if it is determined in step S116 that the counting request flag is off, the process proceeds to step S118, and the dispensing control board 100 executes a process to determine whether the signal input (received) to the input port 101 is a loan request command.

If it is determined that the input (received) signal is a loan request command, the process proceeds to step S119, where the dispensing control board 100 starts the loan process (FIG. 11). Then, the process according to this flowchart ends.
On the other hand, if it is determined that the input signal is not a loan request command, the process proceeds to step S120, where the payout control board 100 executes a gaming machine command transmission process. This process is a process of transmitting a gaming machine command to the management device 200. Then, the process according to this flowchart ends.

As described above, in step S111, it is determined whether or not the counting process is currently being performed, and if it is determined that the counting process is currently being performed, the counting process currently being performed is continued without performing the processes from step S113 onwards, and if it is determined that the counting process is not currently being performed, the process proceeds to step S113 and it is determined whether or not the lending process is currently being performed.
In addition, in step S116, it is determined whether the counting request flag is on, and if it is determined that the counting request flag is on, the process proceeds to step S117 to start the counting process, and if it is determined that the counting request flag is off, the process proceeds to step S118 to determine whether a loan request command has been received.

In this way, the payout control board 100 is capable of performing counting processing (processing related to the refund of electronic medals) and lending processing (processing related to the lending of electronic medals), and is configured to perform the process of determining whether counting processing is being performed before the process of determining whether lending processing is being performed, and to perform the process of determining whether the counting request flag is on before the process of determining whether a lending request command has been received, thereby giving priority to counting processing over lending processing.
Here, when the counting switch 47 is operated, the dispensing control board 100 executes the counting process.
In addition, when the loan switch 202 is operated and a loan request command is sent from the management device 200 to the dispensing control board 100, the dispensing control board 100 executes the loan process.

Furthermore, when the counting switch 47 and the dispensing switch 202 are operated simultaneously, the dispensing control board 100 prioritizes the counting process, so it executes the counting process but does not execute the dispensing process.
If the electronic medals once lent out are refunded and cannot be exchanged for currency at an equivalent value, the player will be disadvantaged, but by prioritizing the counting process and executing the counting process without executing the lending process, the player can be prevented from being disadvantaged.

Furthermore, when the counting switch 47 is operated while the lending process is being executed, the dispensing control board 100 accepts the operation of the counting switch 47, continues the lending process being executed, and executes the counting process when the lending process is completed.
In other words, the payout control board 100 can accept operation of the counting switch 47 at any time, including while the lending process is being executed or while the reel 31 is rotating, and by accepting operation of the counting switch 47, it can execute the counting process at an appropriate timing thereafter.
As a result, the electronic medals can be paid back without fail by operating the counting switch 47 once, and the need to operate the counting switch 47 again can be eliminated, thereby preventing the player from feeling bothered.

9 and 10 show the subroutine of the main control command analysis process in step S110 of Fig. 8. Fig. 10 is a flowchart following Fig. 9.
As mentioned above, the commands sent from the main control board 50 to the dispensing control board 100 are collectively referred to as main control commands.
Furthermore, the main control commands include the eight types of commands listed in the "Contents" column in FIG.
Then, in the main control command analysis process, it is determined which of the eight types of commands has been received, and a process corresponding to the received command is executed.

Specifically, in the main control command analysis process, in step S131, a determination process is executed as to whether or not an error flag is on (whether or not an error has occurred).
If it is determined that the error flag is on, the process proceeds to step S132, where the dispensing control board 100 executes a process of sending an error command to the main control board 50. Then, the process according to this flowchart ends.
On the other hand, if it is determined that the error flag is off, the process proceeds to step S133.

In step S133, the dispensing control board 100 executes a determination process to determine whether the received command is a startup confirmation command.
If it is determined that the received command is a startup confirmation command, the process proceeds to step S134, and the dispensing control board 100 executes a process of sending the received startup confirmation command back to the main control board 50 as is (ACK response to the startup confirmation command).
On the other hand, if it is determined that the received command is not a start confirmation command, the process proceeds to step S135.

When proceeding to step S135, the dispensing control board 100 executes a determination process to determine whether the received command is a deposit request command, a return request command, or a dispensing request command, i.e., whether it is a calculation request command.
If it is determined that the received command is either an input request command, a return request command, or a withdrawal request command, that is, if it is determined that the command is a calculation request command, the process proceeds to step S138 in FIG.
On the other hand, if it is determined that the received command is neither an input request command, a return request command nor a withdrawal request command, that is, if it is determined that the received command is not a calculation request command, the process proceeds to step S136.

If the received command is a startup confirmation command, step S133 returns "Yes" and the process proceeds to step S134. If the received command is a calculation request command (deposit request command, return request command, or payout request command), step S135 returns "Yes" and the process proceeds to step S138 in Figure 10. Therefore, step S135 returns "No" and the process proceeds to step S136 when one of the eight types of commands shown in the "Contents" column in Figure 4, a setting change start command, setting change end command, game start + RT status command, or game end + game status command, is received, i.e., when a game information command is received.

Then, in step S136, the payout control board 100 executes a process of setting the received game information command (setting change start command, setting change end command, game start + RT status command, or game end + game status command) in the management device transmission command buffer, and in the next step S137, executes a process of sending the received game information command directly back to the main control board 50 (ACK response of the game information command). Then, the process according to this flowchart ends.
In addition, when the process of setting the game information command in the command buffer for transmission to the management device is executed in step S136, the game information command stored in the command buffer for transmission to the management device will be transmitted to the management device 200 by an interrupt process on the payout control board 100 executed after this process.

Also, when proceeding to step S138 in Figure 10, the dispensing control board 100 executes a determination process to determine whether the received command is a deposit request command.
If it is determined that the received command is a deposit request command, the process proceeds to step S139, and the dispensing control board 100 executes a process of masking the subsequent command (lower 8 bits) of the deposit request command with "03H (00000011B)."
As mentioned above, the command following the input request command indicates the number of bets. The maximum number of bets is set to "3," so when three coins are input, the command following the input request command will be "03H (00000011B)." In other words, the maximum number of bets can be represented by bits D0 to D1 in the command following the input request command.

Therefore, in step S139, the command following the input request command is masked with "03H (00000011B)." That is, an AND operation is performed on the command following the input request command and "03H (00000011B)."
This allows bits other than D0 to D1 in the command following the input request command to be set to "0", and even if noise causes "1" to enter bits D2 to D7 in the command following the input request command, this can be set to "0", preventing a number exceeding "3" from being erroneously subtracted from the number of credits when inputting.

Also, after executing the processing of step S139, the payout control board 100 proceeds to step S140 and executes a determination process to determine whether "(number of credits - number of bets) <0" or not, that is, whether the number of credits is less than the number of bets or not.
If it is determined that the number of credits is less than the number of bets, the process proceeds to step S141, where the payout control board 100 executes a process of sending a deposit prohibition command to the main control board 50 (NAK response to the deposit request command), and then ends the process according to this flowchart.

On the other hand, if it is determined that the number of credits is equal to or greater than the number of bets, the payout control board 100 proceeds to step S142, where it subtracts the number of bets from the number of credits. In the next step S143, it sends a deposit readback command to the main control board 50 (sends the received deposit request command back to the main control board 50 as is) (ACK response to the deposit request command). Then, it ends the processing according to this flowchart.

Also, if it is determined in step S138 that the received command is not a deposit request command, the process proceeds to step S144, and the dispensing control board 100 executes a process to determine whether the received command is a dispensing request command.
If it is determined that the received command is a dispensing request command, the dispensing control board 100 proceeds to step S145 and executes a process of masking the subsequent command (lower 8 bits) of the dispensing request command with "0FH (00001111B)."
As mentioned above, the command following the dispense request command indicates the number of coins to be dispensed. The maximum number of coins to be dispensed is set to "15," and when dispensing 15 coins, the command following the dispense request command is "0EH (00001110B)." In other words, the maximum number of coins to be dispensed can be represented by bits D0 to D3 in the command following the dispense request command.

For this reason, in step S145, the command following the payout request command is masked with "0FH (00001111B)." That is, an AND operation is performed on the command following the payout request command and "0FH (00001111B)." This allows bits other than D0 to D3 in the command following the payout request command to be set to "0." Even if bits D4 to D7 in the command following the payout request command contain a "1" due to noise, this can be set to "0," preventing the number of credits from being mistakenly increased by more than "15" when paying out.

Also, after executing the processing of step S145, the process proceeds to step S146, and the payout control board 100 executes a determination process to determine whether "(number of credits + number of payouts) > upper limit", i.e., whether adding the number of credits to the number of payouts exceeds the upper limit of the number of credits ("10,000" in this embodiment).
If it is determined that adding the payout number to the credit count will exceed the upper limit of the credit count, the process proceeds to step S147, where the payout control board 100 executes processing to send a payout disable command to the main control board 50 (NAK response to the payout request command), and the processing according to this flowchart is then terminated.

On the other hand, if it is determined that adding the payout number to the credit count will not exceed the upper limit of the credit count, the payout control board 100 proceeds to step S148 and executes the process of adding the payout number to the credit count, and then in the next step S149, executes the process of sending a payout readback command to the main control board 50 (sending the received payout request command back to the main control board 50 as is) (ACK response to the payout request command). Then, processing according to this flowchart ends.

Also, if it is determined in step S144 that the received command is not a dispensing request command, the dispensing control board 100 proceeds to step S150 and executes a process to determine whether the received command is a return request command.
If it is determined that the received command is a return request command, the process proceeds to step S151, and the dispensing control board 100 executes a process to mask the subsequent command (lower 8 bits) of the return request command with "03H (00000011B)."
As mentioned above, the command following the return request command indicates the number of coins to be returned. Also, since the maximum number of bets is "3," the maximum number of coins to be returned is also "3." When returning three coins, the command following the return request command will be "03H (00000011B)." In other words, the maximum number of coins to be returned can be represented by bits D0 to D1 in the command following the return request command, just like the maximum number of bets.

For this reason, in step S151, the command following the return request command is masked with "03H (00000011B)." That is, an AND operation is performed on the command following the return request command and "03H (00000011B)." This allows bits other than D0 to D1 in the command following the return request command to be set to "0." Even if noise causes bits D2 to D7 in the command following the return request command to contain a "1," this can be set to "0," preventing the number of credits from being mistakenly increased by more than "3" when returning the credits.

Also, after executing the processing of step S151, the process proceeds to step S152, and the payout control board 100 executes a determination process to determine whether "(number of credits + number of returned coins) > upper limit value", that is, whether adding the number of returned coins to the number of credits exceeds the upper limit value of the number of credits ("10,000" in this embodiment).
If it is determined that adding the number of returned coins to the number of credits will exceed the upper limit of the number of credits, the process proceeds to step S153, where the payout control board 100 executes processing to send a non-returnable command to the main control board 50 (NAK response to the return request command), and the processing according to this flowchart is then terminated.

On the other hand, if it is determined that adding the number of return coins to the number of credits does not exceed the upper limit of the number of credits, the payout control board 100 proceeds to step S154, where it executes a process of adding the number of return coins to the number of credits, and then in the next step S155, it executes a process of sending a return readback command to the main control board 50 (sending the received return request command back to the main control board 50 as is) (ACK response to the return request command), and then ends the process according to this flowchart.
When the process according to this flowchart is completed, the process proceeds to step S111 shown in FIG.

Fig. 11 shows a subroutine of the lending process in step S119 of Fig. 8. Note that "lending process 1" in Fig. 11 indicates a part of the lending process in step S119 of Fig. 8. Another part of the lending process is shown in Fig. 23 (referred to as "lending process 2"), which will be described later.
If it is determined in step S118 of Fig. 8 that a loan request command has been received, the process proceeds to step S119 of Fig. 8. This starts the loan process of Fig. 11. Also, in the loan process, in step S161, the dispensing control board 100 executes a process of sending a loan readback command to the management device 200 (sending the received loan request command back to the management device 200 as is) (ACK response to the loan request command). Then, the process proceeds to the next step S162.

In step S162, the dispensing control board 100 repeatedly executes the process of determining whether the sending of the loan replay command has been completed until the result is "Yes", and when the result is "Yes" in step S162, the process proceeds to step S163.
When the process proceeds to step S163, the dispensing control board 100 executes a process to determine whether or not a management device command has been received. As described above, a management device command is a general term for a command sent from the management device 200 to the dispensing control board 100.
If it is determined in step S163 that a management apparatus command has been received, the process proceeds to step S164, where a determination process is executed as to whether or not the received management apparatus command is a lending instruction command.

On the other hand, if it is determined in step S163 that the management device command has not been received, the process proceeds to step S168, and the dispensing control board 100 executes a process to determine whether a timeout has occurred (a predetermined time has elapsed since the loan recitation command was sent).
If it is determined in step S168 that a timeout has occurred, the process proceeds to step S169, where the dispensing control board 100 sets an error flag, and the process according to this flowchart is then terminated.
On the other hand, if it is determined in step S168 that the timeout has not occurred, the process of step S163 is executed again.

Also, in step S164, if it is determined that the received management device command is a lending instruction command, the process proceeds to step S165, and the dispensing control board 100 executes a determination process to determine whether the number of sheets to be lent (the subsequent command (lower 8 bits) of the lending request command and the subsequent command (lower 8 bits) of the lending instruction command match).
If it is determined in step S165 that there is no match, the process proceeds to the next step S166, where the dispensing control board 100 stores (preserves) the command following the lending instruction command (lower 8 bits) as the number of cards to be dispensed in a predetermined storage area of the RWM 103. Then, the process proceeds to the next step S167.
On the other hand, if it is determined in step S165 that they match, step S166 is skipped and the process proceeds to step S167.

In step S167, the payout control board 100 executes a process of adding the number of loaned coins to the number of credits, and then ends the process according to this flowchart.
If it is determined in step S164 that the received management device command is not a lending instruction command, the dispensing control board 100 proceeds to step S169, where it sets an error flag, and then ends the processing according to this flowchart.
If the error flag is set in step S169, the determination in step S131 of the main control command analysis process in Fig. 9 executed after this process is "Yes," and the process proceeds to step S132. Then, an error command is sent to the main control board 50.

Fig. 12 shows a subroutine of the counting process in step S117 of Fig. 8. Note that "counting process 1" in Fig. 12 indicates a part of the counting process in step S117 of Fig. 8. Another part of the counting process is shown in Fig. 24 (referred to as "counting process 2"), which will be described later.
If it is determined in step S116 of Fig. 8 that the counting request flag is on, the process proceeds to step S117 of Fig. 8. This starts the counting process of Fig. 12. Also, in the counting process, in step S181, the dispensing control board 100 executes a process of sending a subordinate counting request command to the management device 200. Then, the process proceeds to the next step S182.

In step S182, the dispensing control board 100 repeatedly executes the process of determining whether the transmission of the lower-level counting request command has been completed until the result is "Yes", and when the result is "Yes" in step S182, the process proceeds to step S183.
When proceeding to step S183, the dispensing control board 100 executes a process to determine whether or not a management device command has been received.
If it is determined in step S183 that a management device command has been received, the process proceeds to step S184, where a determination process is performed to determine whether the received command matches the transmitted command, i.e., whether the transmitted lower-order count request command has been returned unchanged from the management device 200 (whether a lower-order count repeat command has been received).

On the other hand, if it is determined in step S183 that the management device command has not been received, the process proceeds to step S192, and the dispensing control board 100 executes a process to determine whether a timeout has occurred (a predetermined time has elapsed since the lower-level counting request command was sent).
If it is determined in step S192 that a timeout has occurred, the process proceeds to step S194, where the dispensing control board 100 sets an error flag, and the process according to this flowchart is then terminated.
On the other hand, if it is determined in step S192 that the timeout has not occurred, the process of step S183 is executed again.

Furthermore, if it is determined in step S184 that the received command matches the transmitted command (the transmitted lower-order count request command was returned unchanged from the management device 200), the process proceeds to step S185, where the dispensing control board 100 executes processing to transmit the upper-order count request command to the management device 200. Then, the process proceeds to the next step, S186.
On the other hand, if it is determined in step S184 that the received command does not match the transmitted command, the dispensing control board 100 proceeds to step S194, where it sets an error flag, and ends the processing according to this flowchart.

When proceeding to step S186, the dispensing control board 100 repeatedly executes the process of determining whether or not the transmission of the higher-level counting request command has been completed until the answer is "Yes", and when the answer is "Yes" in step S186, the process proceeds to step S187.
When proceeding to step S187, the dispensing control board 100 executes a process to determine whether or not a management device command has been received.
If it is determined in step S187 that a management device command has been received, the process proceeds to step S188, where a determination is made as to whether the received command matches the transmitted command, i.e., whether the transmitted higher-order count request command has been returned unchanged from the management device 200 (the higher-order count repeat command has been received).

On the other hand, if it is determined in step S187 that the management device command has not been received, the process proceeds to step S193, and the dispensing control board 100 executes a process to determine whether a timeout has occurred (a predetermined time has elapsed since the upper counting request command was sent).
If it is determined in step S193 that a timeout has occurred, the process proceeds to step S194, where the dispensing control board 100 sets an error flag, and the process according to this flowchart is then terminated.
On the other hand, if it is determined in step S193 that the timeout has not occurred, the process of step S187 is executed again.

Furthermore, if it is determined in step S188 that the received command matches the transmitted command (the transmitted higher-level count request command was returned unchanged from management device 200), the process proceeds to step S189, where dispensing control board 100 executes processing to transmit a count instruction command to management device 200. Then, the process proceeds to the next step, S190.
On the other hand, if it is determined in step S188 that the received command does not match the transmitted command, the process proceeds to step S194, where the dispensing control board 100 sets an error flag, and the process according to this flowchart is then terminated.

When proceeding to step S190, the dispensing control board 100 repeatedly executes the process of determining whether the transmission of the counting instruction command has been completed until the answer is "Yes", and when the answer is "Yes" in step S190, the process proceeds to step S191.
When the process proceeds to step S191, the payout control board 100 executes a process of clearing the number of credits (setting it to "0"), and then ends the process according to this flowchart.
If the error flag is set in step S194, the determination in step S131 of the main control command analysis process in Fig. 9 executed after this process is "Yes," and the process proceeds to step S132. Then, an error command is sent to the main control board 50.

FIG. 13 is a flowchart showing the flow of processing of a main routine in the main control board 50.
When power is turned on, the main control board 50 performs a power-on process in step S201, and then proceeds to the next step S202.
In step S202, a determination is made as to whether the setting key switch 12 is on.

If it is determined in step S202 that the setting key switch 12 is on, the process proceeds to step S203, where the setting change process is executed, and when the setting change process is completed, the process proceeds to step S211.
On the other hand, if it is determined in step S202 that the setting key switch 12 is off, the process proceeds to step S204, where a game return process is executed. Then, when the game return process is completed, the process proceeds to step S211.
When the process proceeds to step S211, a process of determining whether to bet three coins or one coin is executed. If it is determined that three coins are to be bet, the process proceeds to step S205, and if it is determined that one coin is to bet, the process proceeds to step S206.

When the process proceeds to step S205, a three-bet process (FIG. 16) is executed. This process involves betting three of the credited electronic medals based on the operation of the three-bet switch 40b. The three-bet process will be described in detail later. When the three-bet process is completed, the process proceeds to step S212.
When the process proceeds to step S206, the one-coin bet process (FIG. 17) is executed. This process is a process in which one of the credited electronic medals is bet based on the operation of the one-coin bet switch 40a. The one-coin bet process will be described in detail later. Then, when the one-coin bet process is completed, the process proceeds to step S212.

When the process proceeds to step S212, a start or cancel determination process is executed. If the process determines that the process should start, the process proceeds to step S207, and if the process determines that the process should be canceled, the process proceeds to step S210.
When the process proceeds to step S207, a game start process (FIG. 18) is executed. This process is a process for starting a game based on the operation of the start switch 41. The game start process will be described in detail later. Then, when the game start process is completed, the process proceeds to the next step S208.

In step S208, a game termination process (FIG. 19) is executed. This process is a process for terminating a game when the stop switch 42 is operated and the rotation of all the reels 31 has stopped. The game termination process will be described in detail later. Then, when the game termination process is completed, the process proceeds to the next step S209, where a payout process (FIG. 20) is executed. This process is a process for paying out electronic medals based on the winning combination. Then, when the payout process is completed, the process returns to step S211.
When the process proceeds to step S210, a return process (FIG. 21) is executed. This process is a process for returning the betted electronic medals to credits based on the operation of the cancel switch 46. Then, when the return process is completed, the process returns to step S211.

Figure 14 is a flowchart showing the flow of the power-on process in the main control board 50 and the dispensing control board 100.
In Figure 14, the flowchart on the left shows the flow of the power-on process on the main control board 50, and the flowchart on the right shows the flow of power-on process 1 on the dispensing control board 100. Note that "power-on process 1" in Figure 14 indicates that this is a part of the power-on process on the dispensing control board 100. Another part of this power-on process is illustrated in Figure 22 (referred to as "power-on process 2"), which will be described later. Also, in Figure 14, the arrows between the left and right flowcharts indicate the direction of command transmission between the main control board 50 and the dispensing control board 100 during the power-on process.
14 and FIGS. 15 to 21 described later show the command transmission and reception status between the main control board 50 and the dispensing control board 100.
23 to 25, which will be described later, show the command transmission and reception status between the dispensing control board 100 and the management device 200.

When the slot machine 10 is powered on, power is supplied from the power supply board 150 to the main control board 50 and the payout control board 100. Then, the program on the main control board 50 is started, and the program on the payout control board 100 is started. At this time, the power-on process is executed on the main control board 50, and power-on process 1 is executed on the payout control board 100.

First, a description will be given of the power-on process in the main control board 50 shown on the left side of Fig. 14. The flowchart shown on the left side of Fig. 14 shows the subroutine of the power-on process in step S201 of Fig. 13.
In step S301, the main control board 50 executes an initialization process. When the initialization process is completed, the process proceeds to the next step S302.
When the process proceeds to step S302, the main control board 50 executes a process of sending a startup confirmation command to the dispensing control board 100. Then, the process proceeds to the next step S303.
In step S303, the main control board 50 executes a response waiting process, which is a process of waiting for an ACK response to the startup confirmation command from the dispensing control board 100.

Then, when the transmitted startup confirmation command is returned as is from the dispensing control board 100 (an ACK response is received), the processing according to this flowchart is terminated. Note that, when the processing according to this flowchart is terminated, the processing proceeds to step S202 shown in FIG.
In contrast, if a predetermined time has passed since the start-up confirmation command was sent and there is no ACK response to the start-up confirmation command (a timeout occurs), or if an error command is sent from the dispensing control board 100 (a NAK response is received), the process proceeds to step S304, and the main control board 50 executes a process to decrement the retransmission counter.
The retransmission counter is a counter for counting the number of times the start confirmation command is retransmitted, and is set to an initial value of "2" when the start confirmation command is first transmitted.
The initial value of the retransmission counter is not limited to "2" and may be, for example, "3".

Also, when the process of decrementing the retransmission counter is completed, the process proceeds to the next step S305, where the main control board 50 executes a process of determining whether the retransmission counter is "0" or not.
If it is determined that the retransmission counter is "0", the process proceeds to the next step S306, where the main control board 50 executes error processing.
On the other hand, if it is determined that the retransmission counter is not "0", step S302 is executed again.

Next, the power-on process 1 in the dispensing control board 100 shown on the right side of Figure 14 will be described.
In step S401, the dispensing control board 100 executes an initialization process. When the initialization process is completed, the process proceeds to the next step S402.
In step S402, the dispensing control board 100 executes a command reception process. This process receives a startup confirmation command sent from the main control board 50. When the startup confirmation command is received, the process proceeds to the next step S403, where the dispensing control board 100 executes a process of sending the received startup confirmation command back to the main control board 50 as is (ACK response to the startup confirmation command). When the received startup confirmation command is sent back to the main control board 50 as is, the process according to this flowchart ends.

Figure 15 is a flowchart showing the flow of setting change processing in the main control board 50 and the dispensing control board 100.
In Figure 15, the flowchart on the left shows the flow of the setting change processing on the main control board 50, and the flowchart on the right shows the flow of the setting change processing on the dispensing control board 100. Also, in Figure 15, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the main control board 50 and the dispensing control board 100 during the setting change processing.

First, a description will be given of the setting change processing in the main control board 50 shown on the left side of Fig. 15. The flowchart shown on the left side of Fig. 15 shows the subroutine of the setting change processing in step S203 of Fig. 13.
If the setting key switch 12 is on when the power is turned on, the main control board 50 executes a setting change process. In this setting change process, in step S311, a setting change start command is sent to the dispensing control board 100. Then, the process proceeds to the next step S312.
In step S312, the main control board 50 executes a response waiting process, which is a process of waiting for an ACK response to the setting change start command from the dispensing control board 100.
Here, when the transmitted setting change start command is returned unchanged from the dispensing control board 100, the main control board 50 determines that an ACK response to the setting change start command from the dispensing control board 100 has been received, and proceeds to the setting value change processing in step S203. This processing switches the display of the setting value from "1" → "2" → ... → "6" → "1" → ... each time the setting switch 13 is operated, and when the start switch 41 is operated, the displayed setting value is confirmed. Then, when the setting value change processing is completed, the processing proceeds to step S313.

In contrast, if a predetermined time has passed since the setting change start command was sent and there is no ACK response to the setting change start command (a timeout occurs), or if an error command is sent from the dispensing control board 100 (a NAK response is received), the process returns to step S311, and the main control board 50 again executes the process of sending the setting change start command to the dispensing control board 100.
Also, when the process proceeds to step S313, the main control board 50 executes a process of sending a setting change end command to the dispensing control board 100. Then, the process proceeds to the next step S314.

In step S314, the main control board 50 executes a response waiting process, which is a process of waiting for an ACK response to the setting change end command from the dispensing control board 100.
If the command to end the setting change is returned as is from the dispensing control board 100, the main control board 50 determines that an ACK response has been received for the command to end the setting change from the dispensing control board 100, and ends the processing according to this flowchart. When the processing according to this flowchart ends, the processing proceeds to step S211 shown in FIG. 13.
In contrast, if a predetermined time has passed since the setting change end command was sent and there is no ACK response to the setting change end command (a timeout occurs), or if an error command is sent from the dispensing control board 100 (a NAK response is received), the process returns to step S313, and the main control board 50 again executes the process of sending the setting change end command to the dispensing control board 100.

Next, the flow of the setting change process in the dispensing control board 100 shown on the right side of Figure 15 will be explained.
In step S411, the dispensing control board 100 executes a command reception process. This process receives a setting change start command sent from the main control board 50. When the setting change start command is received, the process proceeds to the next step S412, where the dispensing control board 100 executes a process of sending the received setting change start command back to the main control board 50 as is (ACK response to the setting change start command). The process then proceeds to the next step S413.

When the process proceeds to step S413, the dispensing control board 100 executes a command reception process. This process receives the setting change end command sent from the main control board 50. When the setting change end command is received, the process proceeds to the next step S414, where the dispensing control board 100 executes a process of sending the received setting change end command back to the main control board 50 as is (ACK response to the setting change end command). When the received setting change end command is sent back to the main control board 50 as is, the process according to this flowchart ends.

FIG. 16 is a flowchart showing the flow of three-coin bet processing in the main control board 50 and the payout control board 100.
In Figure 16, the flowchart on the left shows the flow of three-coin bet processing on the main control board 50, and the flowchart on the right shows the flow of three-coin bet processing on the payout control board 100. Also, in Figure 16, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the main control board 50 and the payout control board 100 during three-coin bet processing.

Also, Figure 16 shows an example in which, during a three-coin bet process, a one-coin insertion request command ("2001H") is sent three times as an insertion request command requesting that the bet number "1" be subtracted from the credit number.
In addition, when processing a three-coin bet, it is not necessary to send a one-coin insertion request command three times; it is also possible to send a three-coin insertion request command ("2003H") once, which requests that the bet number "3" be subtracted from the number of credits.

First, a description will be given of the three-coin bet process in the main control board 50 shown on the left side of Fig. 16. The flowchart shown on the left side of Fig. 16 shows the subroutine of the three-coin bet process in step S205 of Fig. 13.
In step S321, the main control board 50 executes a process of determining whether or not a specified number of electronic medals have been bet. If it is determined that the specified number of electronic medals have been bet, the process according to this flowchart ends. On the other hand, if it is determined that the specified number of electronic medals have not been bet, the process proceeds to the next step S323 when operation (ON) of the 3-bet switch 40b is detected in the next step S322.
In step S323, the main control board 50 executes a process of transmitting a one-coin insertion request command to the dispensing control board 100. Then, the process proceeds to the next step S324.

In step S324, the main control board 50 executes a response waiting process. This process waits for a one-coin insertion repeat command to be sent from the dispensing control board 100 (an ACK response to the one-coin insertion request command).
Then, when the one-coin insertion repeat command is received (the sent one-coin insertion request command is sent back as is from the dispensing control board 100), the main control board 50 determines that an ACK response to the one-coin insertion request command has been received from the dispensing control board 100, and proceeds to step S325.

In contrast, if a predetermined time has passed since the one-coin insertion request command was sent in step S323 but the one-coin insertion repeat command is not received (a timeout occurs), or an error command is sent from the dispensing control board 100 (a NAK response is received), the process returns to step S323 and the main control board 50 again executes the process of sending the one-coin insertion request command to the dispensing control board 100.
Thereafter, the main control board 50 executes the same processes as steps S323 and S324 in steps S325 and S326, and steps S327 and S328. That is, the same processes as steps S323 and S324 are executed three times. Then, the processing according to this flowchart ends. Note that, after the processing according to this flowchart ends, the processing proceeds to step S212 shown in FIG. 13.

Next, the three-coin bet process on the payout control board 100 shown on the right side of FIG. 16 will be described.
In step S421, the dispensing control board 100 executes a command reception process. This process receives a one-coin insertion request command sent from the main control board 50. When the one-coin insertion request command is received, the process proceeds to the next step S422, where the dispensing control board 100 executes a process of sending a one-coin insertion repeat command to the main control board 50 (sending the received one-coin insertion request command back to the main control board 50 as is (ACK response to the one-coin insertion request command)). The process then proceeds to the next step S423.
Thereafter, the dispensing control board 100 executes the same processes as steps S421 and S422 in steps S423 and S424, and steps S425 and S426. That is, the same processes as steps S421 and S422 are executed three times. Then, the processing according to this flowchart is terminated.

FIG. 17 is a flowchart showing the flow of single coin bet processing in the main control board 50 and the payout control board 100.
In Figure 17, the flowchart on the left shows the flow of single bet processing on the main control board 50, and the flowchart on the right shows the flow of single bet processing on the payout control board 100. Also, in Figure 17, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the main control board 50 and the payout control board 100 during single bet processing.

First, a description will be given of the one-coin bet process in the main control board 50 shown on the left side of Fig. 17. The flowchart shown on the left side of Fig. 17 shows the subroutine of the one-coin bet process in step S206 of Fig. 13.
In step S331, the main control board 50 executes a process of determining whether or not a specified number of electronic medals have been bet. If it is determined that the specified number of electronic medals have been bet, the process according to this flowchart ends. On the other hand, if it is determined that the specified number of electronic medals have not been bet, the process proceeds to the next step S333 when operation (ON) of the 1-bet switch 40a is detected in the next step S332.
In step S333, the main control board 50 executes a process of transmitting a one-coin insertion request command to the dispensing control board 100. Then, the process proceeds to the next step S334.

In step S334, the main control board 50 executes a response waiting process. This process waits for the dispensing control board 100 to send a one-coin insertion repeat command (an ACK response to the one-coin insertion request command).
Then, when the one-coin insertion repeat command is received (the sent one-coin insertion request command is returned as is from the dispensing control board 100), the main control board 50 determines that an ACK response to the one-coin insertion request command has been received from the dispensing control board 100, and ends the processing according to this flowchart. Note that when the processing according to this flowchart ends, the processing proceeds to step S212 shown in FIG.

In contrast, if a predetermined time has elapsed since the one-coin insertion request command was sent in step S333 but the one-coin insertion repeat command is not received (a timeout occurs), or an error command is sent from the dispensing control board 100 (a NAK response is received), the process returns to step S333, and the main control board 50 again executes the process of sending the one-coin insertion request command to the dispensing control board 100.

Next, the one-coin bet process in the payout control board 100 shown on the right side of FIG. 17 will be described.
In step S431, the dispensing control board 100 executes a command reception process. This process receives a one-coin insertion request command sent from the main control board 50. When the one-coin insertion request command is received, the process proceeds to the next step S432, where the dispensing control board 100 executes a process of sending a one-coin insertion repeat command to the main control board 50 (sending the received one-coin insertion request command back to the main control board 50 as is) (ACK response to the one-coin insertion request command). The process according to this flowchart then ends.

FIG. 18 is a flowchart showing the flow of game start processing in the main control board 50 and the payout control board 100.
18, the flowchart on the left side shows the flow of game start processing on the main control board 50, and the flowchart on the right side shows the flow of game start processing on the payout control board 100. Also, in FIG. 18, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the main control board 50 and the payout control board 100 during game start processing.

First, a description will be given of the game start processing in the main control board 50 shown on the left side of Fig. 18. The flowchart shown on the left side of Fig. 18 shows the subroutine of the game start processing in step S207 of Fig. 13.
In step S351, the main control board 50 executes a process of determining whether or not a specified number of electronic medals have been bet. If it is determined that the specified number of electronic medals have not been bet, the process according to this flowchart ends. In contrast, if it is determined that the specified number of electronic medals have been bet, the process proceeds to the next step S353 when operation (ON) of the start switch 41 is detected in the next step S352.
In step S353, the main control board 50 executes a process of transmitting a game start + RT state command to the payout control board 100. Then, the process proceeds to the next step S354.
In step S354, the main control board 50 executes a response waiting process. This process waits for a game start + RT status command to be sent back from the payout control board 100 (ACK response).

Then, when the transmitted game start + RT status command is returned as is from the payout control board 100, the main control board 50 determines that an ACK response has been received from the payout control board 100, and ends the processing according to this flowchart. Note that when the processing according to this flowchart ends, the processing proceeds to step S208 shown in FIG.
In contrast, if a predetermined time has passed since the start game + RT status command was sent in step S353 and no ACK response is received (a timeout occurs), or an error command is sent from the payout control board 100 (a NAK response is received), the process returns to step S353, and the main control board 50 again executes the process of sending the start game + RT status command to the payout control board 100.

Next, the game start processing in the payout control board 100 shown on the right side of Figure 18 will be described.
In step S451, the payout control board 100 executes a command reception process. This process is a process for receiving a game start + RT status command transmitted from the main control board 50. Then, upon receiving the game start + RT status command, the payout control board 100 proceeds to the next step S452, where it executes a process for sending the received game start + RT status command back to the main control board 50 as is (ACK response). Then, the process according to this flowchart ends.

FIG. 19 is a flowchart showing the flow of game termination processing in the main control board 50 and the payout control board 100.
19, the flowchart on the left side shows the flow of game termination processing in the main control board 50, and the flowchart on the right side shows the flow of game termination processing in the payout control board 100. Also, in FIG. 19, the arrows between the left and right flowcharts indicate the transmission direction of commands transmitted and received between the main control board 50 and the payout control board 100 during game termination processing.

First, a description will be given of the game ending process in the main control board 50 shown on the left side of Fig. 19. The flowchart shown on the left side of Fig. 19 shows the subroutine of the game ending process in step S208 of Fig. 13.
In step S361, the main control board 50 executes a process to determine whether the third stop switch 42 (the stop switch 42 corresponding to the reel 31 that will stop last) has changed from on to off. If it is determined that the third stop switch 42 has not turned off, the process according to this flowchart ends. On the other hand, if it is determined that the third stop switch 42 has turned off, the process proceeds to step S362.
In step S362, the main control board 50 executes a process of transmitting a game end+game status command to the payout control board 100. Then, the process proceeds to the next step S363.
In step S363, the main control board 50 executes a response waiting process. This process waits for a game end + game status command to be sent back from the payout control board 100 (ACK response).

Then, when the transmitted game end + game status command is returned as is from the payout control board 100, the main control board 50 determines that an ACK response has been received from the payout control board 100, and ends the processing according to this flowchart. Note that when the processing according to this flowchart ends, the processing proceeds to step S209 shown in FIG.
In contrast, if a predetermined time has passed since the game end + game status command was sent in step S362 and no ACK response is received (a timeout occurs), or an error command is sent from the payout control board 100 (a NAK response is received), the process returns to step S362, and the main control board 50 again executes the process of sending the game end + game status command to the payout control board 100.

Next, the game end processing in the payout control board 100 shown on the right side of Figure 19 will be described.
In step S461, the payout control board 100 executes a command reception process. This process is a process for receiving a game end + game status command transmitted from the main control board 50. Then, upon receiving the game end + game status command, the payout control board 100 proceeds to the next step S462, where it executes a process for sending the received game end + game status command back to the main control board 50 as is (ACK response). Then, the process according to this flowchart ends.

Figure 20 is a flowchart showing the flow of the payout process in the main control board 50 and the payout control board 100.
In Figure 20, the flowchart on the left shows the flow of the dispensing process on the main control board 50, and the flowchart on the right shows the flow of the dispensing process on the dispensing control board 100. Also, in Figure 20, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the main control board 50 and the dispensing control board 100 during the dispensing process.

First, a description will be given of the payout process in the main control board 50 shown on the left side of Fig. 20. The flowchart shown on the left side of Fig. 20 shows the subroutine of the payout process in step S209 of Fig. 13.
In step S371, the main control board 50 executes a process of transmitting a dispensing request command to the dispensing control board 100. Then, the process proceeds to the next step S372.
In step S372, the main control board 50 executes a response waiting process. This process waits for a payout repeat command to be sent from the payout control board 100 (an ACK response to the payout request command).

Then, when the payout repeat command is received (the payout request command sent is returned as is from the payout control board 100), the main control board 50 determines that an ACK response to the payout request command has been received from the payout control board 100, and ends the processing according to this flowchart. Note that when the processing according to this flowchart ends, the processing returns to step S211 shown in FIG.
In contrast, if a predetermined time has passed since the dispensing request command was sent in step S371 and the dispensing repeat command is not received (a timeout occurs), or an error command is sent from the dispensing control board 100 (a NAK response is received), the process returns to step S371 and the main control board 50 again executes the process of sending a dispensing request command to the dispensing control board 100.

Next, the dispensing process in the dispensing control board 100 shown on the right side of Figure 20 will be described.
In step S471, the dispensing control board 100 executes a command reception process. This process receives a dispensing request command sent from the main control board 50. When the dispensing request command is received, the process proceeds to the next step S472, where the dispensing control board 100 executes a process of sending a dispensing read command to the main control board 50 (sending the received dispensing request command back to the main control board 50 as is (ACK response to the dispensing request command)). The process according to this flowchart then ends.

Figure 21 is a flowchart showing the flow of the return process in the main control board 50 and the dispensing control board 100.
In Figure 21, the flowchart on the left shows the flow of the return process on the main control board 50, and the flowchart on the right shows the flow of the return process on the dispensing control board 100. Also, in Figure 21, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the main control board 50 and the dispensing control board 100 during the return process.

First, a description will be given of the return process in the main control board 50 shown on the left side of Fig. 21. The flowchart shown on the left side of Fig. 20 shows the subroutine of the return process in step S210 of Fig. 13.
In step S341, the main control board 50 executes a process of determining whether or not any electronic medals have been bet. If it is determined that no electronic medals have been bet, the process according to this flowchart ends. On the other hand, if it is determined that electronic medals have been bet, the process proceeds to the next step S343 when operation (ON) of the cancel switch 46 is detected in the next step S342.
In step S343, the main control board 50 executes a process of sending a return request command to the dispensing control board 100. Then, the process proceeds to the next step S344.
In step S344, the main control board 50 executes a response waiting process. This process waits for a return repeat command to be sent from the dispensing control board 100 (an ACK response to the return request command).

Then, when the return repeat command is received (the returned return request command is returned as is from the dispensing control board 100), the main control board 50 determines that an ACK response to the return request command has been received from the dispensing control board 100, and ends the processing according to this flowchart. Note that when the processing according to this flowchart ends, the processing returns to step S211 shown in FIG.
In contrast, if a predetermined time has passed since the return request command was sent in step S343 and the return repeat command is not received (a timeout occurs), or an error command is sent from the dispensing control board 100 (a NAK response is received), the process returns to step S343 and the main control board 50 again executes the process of sending a return request command to the dispensing control board 100.

Next, the return process in the dispensing control board 100 shown on the right side of Figure 21 will be described.
In step S441, the dispensing control board 100 executes a command reception process. This process receives a return request command sent from the main control board 50. When the return request command is received, the process proceeds to the next step S442, where the dispensing control board 100 executes a process of sending a return read command to the main control board 50 (sending the received return request command back to the main control board 50 as is) (ACK response to the return request command). The process according to this flowchart then ends.

Figure 22 is a flowchart showing the flow of the power-on process in the dispensing control board 100 and the management device 200.
In Figure 22, the flowchart on the left shows the flow of power-on process 2 in the dispensing control board 100, and the flowchart on the right shows the flow of power-on process in the management device 200. Also, in Figure 22, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the dispensing control board 100 and the management device 200 during the power-on process.
When the slot machine 10 and the management device 200 are powered on, the program on the payout control board 100 of the slot machine 10 is started, and the program on the management device 200 is started. At this time, the power-on process is executed on the payout control board 100 of the slot machine 10, and the power-on process is executed on the management device 200.

Here, power-on process 1 on the dispensing control board 100 shown on the right side of Figure 14 and power-on process 2 on the dispensing control board 100 shown on the left side of Figure 22 are both processes executed on the dispensing control board 100 when the power is turned on, and some of the processes overlap. Processes with the same content are assigned the same step numbers.
However, in the power-on process 1 on the dispensing control board 100 shown on the right side of Figure 14, only the processes necessary to explain the sending and receiving of commands between the main control board 50 and the dispensing control board 100 are extracted and illustrated, and other processes are omitted from the illustration.
In contrast, in the power-on process 2 in the dispensing control board 100 shown on the left side of Figure 22, the processes necessary to explain the sending and receiving of commands between the dispensing control board 100 and the management device 200 are extracted and illustrated, and other processes are omitted from the illustration.

First, we will explain the power-on process 2 in the dispensing control board 100 shown on the left side of Figure 22.
In step S401, the dispensing control board 100 executes an initialization process. When the initialization process is completed, the process proceeds to the next step S502. Note that step S401 in FIG. 22 and step S401 in FIG. 14 are identical processes.
When the process proceeds to step S502, the dispensing control board 100 executes a process of sequentially transmitting the first byte to the fourth byte of the CPU unique ID to the dispensing control board 100. Then, the process proceeds to the next step S503.
In step S503, the main control board 50 executes a process to determine whether or not transmission of the fourth byte of the CPU unique ID has been completed. If it is determined that transmission of the fourth byte of the CPU unique ID has been completed, the process according to this flowchart ends. On the other hand, if it is determined that transmission of the fourth byte of the CPU unique ID has not been completed, the process returns to step S502, and the dispensing control board 100 executes a process to transmit the first byte through the fourth byte of the CPU unique ID to the dispensing control board 100 again in sequence.

Next, the power-on process in the management device 200 shown on the right side of FIG. 22 will be described.
In step S601, the management device 200 executes initialization processing. When the initialization processing is completed, the management device 200 proceeds to the next step S602.
In step S602, the management device 200 executes a command reception process. This process receives the first through fourth bytes of the CPU unique ID transmitted from the dispensing control board 100. When the first through fourth bytes of the CPU unique ID are received, the process proceeds to the next step S603, where the management device 200 executes a determination process to determine whether the received command is a CPU unique ID.

If it is determined in step S603 that the received command is a CPU unique ID, the process proceeds to the next step S604, where the management device 200 executes a process of storing (saving) the first through fourth bytes of the received CPU unique ID in a predetermined storage area, and then proceeds to the next step S605.
On the other hand, if it is determined in step S603 that the received command is not a CPU unique ID, the process according to this flowchart ends.

In step S605, the management device 200 executes a process of determining whether or not reception of the fourth byte of the CPU unique ID has been completed.
If it is determined in step S605 that reception of the fourth byte of the CPU unique ID has been completed, the process proceeds to the next step S606, where the management device 200 executes processing to transmit the first through fourth bytes of the CPU unique ID to the hall computer 300. Then, the processing according to this flowchart ends.
On the other hand, if it is determined in step S605 that reception of the fourth byte of the CPU unique ID has not been completed, step S606 is skipped and the process according to this flowchart is terminated.

FIG. 23 is a flowchart showing the flow of the lending process in the dispensing control board 100 and the management device 200.
In Figure 23, the flowchart on the left shows the flow of lending process 2 in the dispensing control board 100, and the flowchart on the right shows the flow of lending process in the management device 200. Also, in Figure 23, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the dispensing control board 100 and the management device 200 during the lending process.

Here, the lending process 1 in the dispensing control board 100 shown in Figure 11 and the lending process 2 in the dispensing control board 100 shown on the left side of Figure 23 both show subroutines of the lending process in step S119 in Figure 8, and some of the processing overlaps. The same step number is assigned to processing with the same content.
However, in the lending process 1 in the dispensing control board 100 shown in Figure 11, the processing during the lending process is illustrated in detail.
In contrast, in the loan process 2 on the dispensing control board 100 shown on the left side of Figure 23, the processes necessary to explain the sending and receiving of commands between the dispensing control board 100 and the management device 200 are extracted and illustrated, and other processes are omitted from the illustration.

First, the lending process in the management device 200 shown on the right side of FIG. 23 will be described.
In step S611, when operation (ON) of the lending switch 202 is detected, the process proceeds to the next step S612, where the management device 200 executes processing to turn off the lending available LED, processing to invalidate (unaccept) the operation of the lending switch 202, and processing to invalidate (unaccept) the operation of the return switch 203. Then, the process proceeds to the next step S613.
The loanable LED is an LED that indicates whether or not the electronic medal can be loaned. When lit, it indicates that the electronic medal can be loaned, and when unlit, it indicates that the electronic medal cannot be loaned.

In step S613, the management device 200 transmits a lending request command to the dispensing control board 100. Then, the process proceeds to the next step S614.
In step S614, the management device 200 executes a response waiting process, which is a process of waiting for a loan repeat command to be sent from the dispensing control board 100 (an ACK response to the loan request command).

Then, when the loan repeat command is received (the loan request command that was sent is sent back as is from the dispensing control board 100), the management device 200 determines that an ACK response to the loan request command has been received from the dispensing control board 100, and proceeds to the next step S615.
Also, if an error command is sent from the dispensing control board 100 (a NAK response is received), the process proceeds to step S617.
Furthermore, if the lending repeat command is not received within a predetermined time period after the lending request command was sent in step S613 (timeout occurs), the management device 200 proceeds to step S618 and executes error processing.

In step S615, the management device 200 transmits a lending instruction command to the dispensing control board 100. Then, the process proceeds to step S616.
In step S616, the management device 200 executes a process of subtracting the number of sheets lent, and then proceeds to the next step S617.
In step S617, the management device 200 executes the process of turning on the lending available LED, the process of enabling (enabling) operation of the lending switch 202, and the process of enabling (enabling) operation of the return switch 203. Then, the process according to this flowchart ends.

Next, we will explain the lending process 2 in the dispensing control board 100 shown on the left side of Figure 23.
In step S511, the dispensing control board 100 executes a command reception process. This process is a process for receiving a loan request command transmitted from the management device 200. Then, when the loan request command is received, the process proceeds to step S118.

In step S118, the dispensing control board 100 executes a process to determine whether the received command is a loan request command. Note that step S118 in FIG. 23 and step S118 in FIG. 8 are the same process.
If it is determined that the received command is a loan request command, the process proceeds to step S513, where the dispensing control board 100 executes a process to store (save) the received loan request command in a predetermined storage area of the RWM 103. Then, the process proceeds to the next step, S514.
On the other hand, if it is determined that the received command is not a loan request command, the process according to this flowchart ends.

When proceeding to step S514, the dispensing control board 100 executes a process to determine whether the loan request can be accepted, specifically, whether the upper limit of the number of credits will be exceeded by adding the number of loans (the number indicated by the command subsequent to the loan request command) to the number of credits.
If it is determined in step S514 that the loan request can be accepted, that is, if it is determined that the total number of credits plus the loan number is equal to or less than the upper limit of the total number of credits, the process proceeds to step S161, where the payout control board 100 transmits a loan readback command to the management device 200 (returning the received loan request command to the management device 200 as is) (ACK response to the loan request command).Then, the process proceeds to step S164.

On the other hand, if it is determined in step S514 that the loan request cannot be accepted, that is, if it is determined that adding the loan number to the credit count would exceed the upper limit of the credit count, the process proceeds to step S515, where the dispensing control board 100 sends an error command to the management device 200 (NAK response). Then, the process proceeds to step S169, where the dispensing control board 100 executes processing to set an error flag. Processing according to this flowchart then ends.

When proceeding to step S164, the dispensing control board 100 executes a process to determine whether or not a lending instruction command has been received.
If it is determined in step S164 that a lending instruction command has been received, the process proceeds to step S167, where the payout control board 100 adds the number of loaned coins to the number of credits, and then the process according to this flowchart ends.

On the other hand, if it is determined in step S164 that a lending instruction command has not been received, the dispensing control board 100 proceeds to step S169, where it executes a process of setting an error flag, and then ends the process according to this flowchart.
Note that steps S161, S164, S167, and S169 in FIG. 23 and steps S161, S164, S167, and S169 in FIG. 11 are the same processes.

24 and 25 are flowcharts showing the flow of the counting process in the dispensing control board 100 and the management device 200. FIG. 25 is a flowchart following FIG.
24 and 25, the flowchart on the left shows the flow of the counting process in the dispensing control board 100, and the flowchart on the right shows the flow of the counting process in the management device 200. Also, in Figures 24 and 25, the arrows between the left and right flowcharts indicate the transmission direction of commands sent and received between the dispensing control board 100 and the management device 200 during the counting process.

Here, counting process 1 in the dispensing control board 100 shown in Figure 12 and counting process 2 in the dispensing control board 100 shown on the left side in Figures 24 and 25 both show subroutines of the counting process in step S117 in Figure 8, and some of the processing is overlapping. Processing with the same content is assigned the same step number.
However, counting process 1 in the dispensing control board 100 shown in Figure 12 illustrates the processing during counting process in detail.
In contrast, in counting process 2 in the dispensing control board 100 shown on the left side of Figures 24 and 25, the processes necessary to explain the sending and receiving of commands between the dispensing control board 100 and the management device 200 are extracted and illustrated, and other processes are omitted from the illustration.

First, the counting process in the dispensing control board 100 shown on the left side in Figures 24 and 25 will be described.
In step S181, the dispensing control board 100 transmits a lower-level counting request command to the management device 200. Then, the process proceeds to step S533.
In step S533, the dispensing control board 100 executes a response waiting process. This process waits for a lower-order count repeat command to be sent from the management device 200 (an ACK response to the lower-order count request command).

Then, when the lower-level counting repeat command is received (the lower-level counting request command that was sent is sent back as is from the management device 200), the dispensing control board 100 determines that an ACK response to the lower-level counting request command has been received from the management device 200, and proceeds to step S185.
Furthermore, if an error command is sent from the management device 200 (a NAK response is received), the process according to this flowchart ends.
Furthermore, if the lower count repeat command is not received within a predetermined time after the lower count request command is sent in step S181 (a timeout occurs), the process proceeds to step S194, where the dispensing control board 100 executes a process to set an error flag, and the process according to this flowchart is then terminated.

In step S185, the dispensing control board 100 sends a higher-order count request command to the management device 200. Then, the process proceeds to step S535 in FIG.
In step S535, the dispensing control board 100 executes a response waiting process. This process waits for a higher-order count repeat command to be sent from the management device 200 (an ACK response to the higher-order count request command).

Then, when the higher-order counting repeat command is received (the higher-order counting request command that was sent is sent back as is from the management device 200), the dispensing control board 100 determines that an ACK response to the higher-order counting request command has been received from the management device 200, and proceeds to step S189.
In response to this, if an error command is sent from the management device 200 (there is a NAK response), or if the upper count repeat command is not received within a predetermined time after sending the upper count request command in step S185 of Figure 24 (a timeout occurs), the process proceeds to step S194, where the dispensing control board 100 executes processing to set an error flag, and then ends the processing according to this flowchart.
The error processing in step S538 in FIG. 24 and the error processing in step S538 in FIG. 25 are the same processing.

When proceeding to step S189, the dispensing control board 100 sends a counting instruction command to the management device 200 and proceeds to step S191.
In step S191, the credit count is cleared (set to "0"), and the process according to this flowchart is then terminated.
Note that steps S181, S185, S189, S191 and S194 in FIGS. 24 and 25 and steps S181, S185, S189, S191 and S194 in FIG. 12 are the same processes.

Next, the counting process in the management device 200 shown on the right side in FIGS. 24 and 25 will be described.
In step S631, the management device 200 executes a command reception process. This process is a process for receiving a sub-count request command transmitted from the dispensing control board 100. Then, when the sub-count request command is received, the process proceeds to the next step S632.

In step S632, the management device 200 executes a process of determining whether the received command is a lower-level count request command.
If it is determined in step S632 that the received command is a lower-level count request command, the process proceeds to the next step S633, where the management device 200 executes a process of storing (saving) the received lower-level count request command in a predetermined storage area, and then proceeds to the next step S634.
On the other hand, if it is determined in step S632 that the received command is not a lower-order count request command, the process according to this flowchart ends.

In step S634, the management device 200 executes a process of determining whether or not a counting (refund) request can be accepted.
If it is determined in step S634 that the counting (refund) request can be accepted, the process proceeds to step S636, where the management device 200 executes the process of turning off the loanable LED, the process of invalidating (not accepting) the operation of the loan switch 202, and the process of invalidating (not accepting) the operation of the return switch 203. Then, the process proceeds to the next step S637.
On the other hand, if it is determined in step S634 that the counting (withdrawal) request cannot be accepted, the process proceeds to step S635, where the management device 200 sends an error command to the dispensing control board 100 (NAK response), and the process according to this flowchart is then terminated.

In step S637, the management device 200 executes a process of transmitting a lower-order count readback command to the dispensing control board 100 (sending the received lower-order count request command back to the dispensing control board 100 as is) (ACK response to the lower-order count request command), and then proceeds to the next step S638.
In step S638, the management device 200 executes a command reception process. This process is a process for receiving a higher-order count request command transmitted from the dispensing control board 100. Then, when the higher-order count request command is received, the process proceeds to step S639 in FIG. 25.

In step S639, the management device 200 executes a process of determining whether the received command is a higher-order count request command.
If it is determined in step S639 that the received command is a higher-order count request command, the process proceeds to step S641, where the management device 200 stores (saves) the received higher-order count request command in a predetermined storage area, and then proceeds to step S642.
On the other hand, if it is determined in step S639 that the received command is not a higher-order count request command, the process proceeds to step S640, where the management device 200 transmits an error command (NAK response) to the dispensing control board 100. Then, the process proceeds to step S647, where the management device 200 executes error processing.

In step S642, the management device 200 executes a process of transmitting a higher-order count readback command to the dispensing control board 100 (sending the received higher-order count request command back to the dispensing control board 100 as is) (ACK response), and then proceeds to the next step S643.
In step S643, the management device 200 executes a command reception process. This process is a process for receiving a counting instruction command transmitted from the dispensing control board 100. Then, when the counting instruction command is received, the process proceeds to the next step S644.

In step S644, the management device 200 executes a process of determining whether the received command is a count instruction command.
If it is determined that the received command is a count instruction command, the process proceeds to the next step S645, where the management device 200 executes a process to reflect the payout number specified from the lower-level count request command and the upper-level count request command in the number of electronic medals managed by the management device 200. Then, the process proceeds to the next step S646.
On the other hand, if it is determined that the received command is not a count instruction command, the management device 200 proceeds to step S647, where it executes error processing.

When processing proceeds to step S646, the management device 200 performs the following processes: turning on the loan-ready LED; enabling (enabling) operation of the loan switch 202; and enabling (enabling) operation of the return switch 203. Processing according to this flowchart then ends.

Figure 26 is a diagram showing the waveforms of the data signal and strobe signal of the serial communication between the dispensing control board 100 and the management device 200.
Figures 23 to 25 show commands such as a loan request command, a lower counting request command, and an upper counting request command as commands sent and received between the dispensing control board 100 and the management device 200, but as described above, these commands are composed of a preceding command (upper 8 bits) and a subsequent command (lower 8 bits).

In FIG. 26, the preceding command and the subsequent command that make up these commands are treated as one unit, and the waveforms of the data signals and strobe signals are shown.
As shown in Figure 26, data signals are transmitted one bit at a time between the dispensing control board 100 and the management device 200, from bit D0 (DB0) to bit D7 (DB7), and these are read one bit at a time when the strobe signal is on.

FIG. 27 is a timing chart showing the on/off states of each signal when an electronic medal is lent.
Figure 23 shows the commands sent and received between the payout control board 100 and the management device 200 when electronic medals are lent, while Figure 27 shows the on/off timing of each signal of the payout control board 100 and the management device 200 when electronic medals are lent.

As shown in FIG. 27, when the slot machine 10 and the management device 200 are powered on, the management device 200 is then ready to accept operation of the return switch 203 .
Thereafter, the data signals of the payout control board 100 of the slot machine 10 and the management device 200 become "0", and the strobe signals of the payout control board 100 of the slot machine 10 and the management device 200 turn off.
Thereafter, the management device 200 becomes able to accept operation of the lending switch 202, and the operating state changes from the standby state to the normal state. The normal state means that the management device 200 can lend out electronic medals, and the slot machine 10 can play games.

Then, when operation (on) of the loan switch 202 of the management device 200 is detected, first, operation of the loan switch 202 and return switch 203 of the management device 200 becomes unacceptable, and then the preceding command and succeeding command of the loan request command are sent sequentially from the management device 200 to the payout control board 100 of the slot machine 10.
Thereafter, the preceding command and the succeeding command of the loan replay command are sequentially transmitted from the payout control board 100 of the slot machine 10 to the management device 200 .
Thereafter, the management device 200 sequentially transmits the preceding command and the succeeding command of the lending instruction command to the payout control board 100 of the slot machine 10 .
Then, when the transmission of the lending instruction command is completed, the management device 200 becomes ready to accept operations of the lending switch 202 and the return switch 203 .

FIG. 28 is a timing chart showing the on/off states of each signal during counting (refunding) of electronic medals.
Figures 24 and 25 show the commands sent and received between the payout control board 100 and the management device 200 when counting electronic medals, while Figure 28 shows the on/off timing of each signal of the payout control board 100 and the management device 200 when counting electronic medals.

As shown in FIG. 28, when the slot machine 10 and the management device 200 are powered on, the management device 200 is then ready to accept operation of the return switch 203 .
Thereafter, the data signals of the payout control board 100 of the slot machine 10 and the management device 200 become "0", and the strobe signals of the payout control board 100 of the slot machine 10 and the management device 200 turn off.
Thereafter, the management device 200 becomes ready to accept operations of the lending switch 202, and the operating state changes from the standby state to the normal state. Up to this point, the process is the same as in FIG.

Then, when operation (ON) of the counting switch 47 of the slot machine 10 is detected, first, operation of the lending switch 202 and return switch 203 of the management device 200 becomes unacceptable, and then the preceding command and succeeding command of the lower-level counting request command are sequentially sent from the payout control board 100 of the slot machine 10 to the management device 200.
Thereafter, the management device 200 sequentially transmits the preceding command and the succeeding command of the lower count replay command to the payout control board 100 of the slot machine 10 .

Thereafter, the payout control board 100 of the slot machine 10 sequentially transmits the preceding command and the succeeding command of the higher-order count request command to the management device 200 .
Thereafter, the management device 200 sequentially transmits the preceding command and the succeeding command of the higher-order count replay command to the payout control board 100 of the slot machine 10 .
Thereafter, the payout control board 100 of the slot machine 10 sequentially transmits the preceding command and the succeeding command of the count instruction command to the management device 200 .
Then, when the transmission of the count instruction command is completed, the management device 200 becomes ready to accept operations of the lending switch 202 and the return switch 203 .

Although the first embodiment of the present invention has been described above, the present invention is not limited to the above-described content, and various modifications such as those described below are possible.
(1) In this embodiment, the various commands shown in Figures 4 to 7 are configured as 16-bit data consisting of a preceding command (upper 8 bits) and a subsequent command (lower 8 bits). However, this is not limited to this, and the data may be, for example, 8 bits or 32 bits.

(2) In this embodiment, commands are sent and received via serial communication between the main control board 50 and the dispensing control board 100, and between the dispensing control board 100 and the management device 200, but this is not limited to this, and parallel communication may also be used, or serial communication and parallel communication may be used together.
(3) In this embodiment, the main control board 50 sends a one-coin insertion request command three times to the payout control board 100 when the three-bet switch 40b is turned on, but this is not limited to this, and the main control board 50 may also send a three-coin insertion request command once.

(4) In this embodiment, the main control board 50 sent a payout request command to the payout control board 100 when the third stop switch 42 changed from on to off, but this is not limited to this, and the payout request command may also be sent when all reels 31 stop.
(5) In this embodiment, even when no winning combination is achieved, when the third stop switch 42 changes from on to off, the main control board 50 sends a payout request command to the payout control board 100 specifying the number of coins to be paid out as “0.” However, this is not limited to this, and it is not necessary to send a payout request command when no winning combination is achieved.

(6) In this embodiment, a slot machine 10 is used as an example of a gaming machine, but the slot machine 10 is not limited to a "reel-type gaming machine" (so-called "pachislot gaming machine") installed in a Type 4 business establishment that is subject to the Entertainment and Amusement Act, and can also be applied to, for example, a casino machine. Furthermore, the present invention may also be applied to a pachinko gaming machine.
(7) All of the embodiments and various modifications described in this specification are not limited to being implemented alone, but can also be implemented in appropriate combinations.

Second Embodiment
The gaming machine 10 of the second embodiment is a medal-less gaming machine that does not use medals as tangible objects, similar to the first embodiment.
Here, the term "medalless" in the term "medalless gaming machine" means that no tangible medals are used.
For this reason, even though it is a "medalless gaming machine," it is the same as conventional gaming machines in that it uses gaming media (gaming value) for gaming, and the gaming media used for gaming in medalless gaming machines are sometimes simply referred to as "medals."
Therefore, when referring to a "medal," it does not only refer to a tangible object, but also to an intangible object (for example, electronic data).
Furthermore, medals as intangible objects may be referred to as game media, game value, points (or simply "points"), electronic medals, electronic data, electronic information, electronic game media, electronic game value, etc. In the following description of the second embodiment, "medals" as intangible objects used in the gaming machine 10 (medalless gaming machine) will be referred to as "game media."

"Renting" refers to transmitting gaming media required for playing from the rental unit 200 to the gaming machine 10.
The term "credit" refers to storing (accumulating, crediting) gaming media in the gaming machine 10. The term "credited gaming media" corresponds to data stored in the RWM 103 of the gaming media count control board 100.
A "bet" refers to placing a bet on gaming media to play a game. When the bet switch 40 (the 1-bet switch 40a or the 3-bet switch 40b) is operated, a predetermined number of gaming media is bet from the gaming media corresponding to the data stored in the RWM 103 of the gaming media count control board 100.
"Bet" is also called "insertion." Note that "insertion" does not only refer to inserting actual medals into the gaming machine through the medal insertion slot, but also includes betting gaming media (electronic medals) by operating the bet switch 40.

"Settlement" refers to returning the betted gaming media to the RWM 103 of the gaming media count control board 100 (to credits), and is performed by operating the settlement switch 46. "Settlement" may also be called "return" or "cancellation." Therefore, the "settlement switch 46" may also be called the "return switch 46" or the "cancel switch 46."
When the bet switch 40 is operated while gaming media are stored as data (credits) in the RWM 103 of the gaming media count control board 100, a predetermined number of gaming media are bet (added as the number of bets), and the data (number of credits) in the RWM 103 of the gaming media count control board 100 is decremented by the number of bets. On the other hand, when the settlement switch 46 is operated while gaming media have been bet, the number of bets (number of gaming media) up to that point becomes "0," and the number of bets up to that point is added to the RWM 103 of the gaming media count control board 100 (returned to credits).

The term "awarding" refers to adding a number of gaming media corresponding to the payout of a winning combination to the credit amount stored in the gaming machine 10 based on the winning combination.
"Awarding" is also called "payout." Note that "payout" does not only refer to the discharge of actual medals from the medal return port, but also includes the process of adding the number of game media corresponding to the winning of a small prize to the number of game media stored in the RWM 103 of the game media count control board 100 when the small prize is won.
In the second embodiment, the "payout means 67" in the first embodiment is referred to as "amount of award control means 67".
"Counting" refers to returning the gaming media stored (credited) in the gaming machine 10 (RWM 103 of the gaming media count control board 100) to the lending unit 200, and is performed by operating the counting switch 47. When the counting switch 47 is operated, a predetermined number of gaming media stored in the gaming machine 10 is subtracted, and the subtracted number of gaming media is added to the lending unit 300 side.

"Returning" game media from the rental unit 200 means storing the number of game media stored in the rental unit 200 in a game media number storage medium (magnetic card, IC card, IC coin, etc.) and discharging it to the outside (player). When storing the number of game media stored in the rental unit 200 in the game media number storage medium, a reader/writer is used (the rental unit 200 has a built-in reader/writer).
As mentioned above, "settlement" may be referred to as "return," but in the second embodiment, "return" refers to storing the number of gaming media stored in the rental unit 200 in a gaming media number storage medium and discharging it to the outside (player).

The LEDs used in the second embodiment, such as the set value display means 73 and the role ratio monitor 113, have each digit made up of seven segments. "Seven segments" means that in addition to seven segment elements, they also have a DP (decimal point) segment.

"Notification" corresponds to sending (outputting) a message from the gaming machine 10 to the rental unit 200, or from the rental unit 200 to the gaming machine 10, and is synonymous with "transmission" and "output."
Hereinafter, it may be said that the gaming machine information notification is "sent," or that the gaming machine information is "notified."

At least a part of the storage area of the RWM or ROM may be referred to as a "storage area" or a "storage means," and both terms have the same meaning.
Also, the control board (main, sub, etc.) may be referred to as "control means." Furthermore, the CPU may be referred to as "control means."

29 is a block diagram of the gaming machine 10 (slot machine) in the second embodiment. Note that while the first embodiment referred to it as the "slot machine 10," the second embodiment will refer to it as the "gaming machine 10."
Furthermore, in the first embodiment, the term "main control board 50" is used, but in the second embodiment, it is referred to as "main control board 50." Similarly, in the first embodiment, the term "sub-control board 80" is used, but in the second embodiment, it is referred to as "sub-control board 80." However, the main control board may be referred to as the main control board, and the sub-control board may be referred to as the sub-control board (both have the same meaning).
In addition, while in the first embodiment it is referred to as the "payout control board 100," in the second embodiment it is referred to as the "game media number control board 100." However, the game media number control board may also be referred to as the payout control board, and both have the same meaning.

Furthermore, in the first embodiment, it was called the "credit number display LED 76," but in the second embodiment it is called the "game media number display unit 121." Both have the same function and are composed of, for example, a five-digit LED.
Furthermore, in the first embodiment, it is called the "acquired number display LED 78", but in the second embodiment it is called the "award number display unit 78". Both have the same function and are composed of, for example, a two-digit LED.

When the main control board 50 is viewed as one of the main control boards, the game media number control board 100 is another of the main control boards. For this reason, the RWM 53, ROM 54, and CPU 55 of the main control board 50 may be referred to as the first main control RWM 53, the first main control ROM 54, and the first main control CPU 55, respectively.
Furthermore, the RWM 103, ROM 104, and CPU 105 of the game media count control board 100 may be referred to as the second main control RWM 103, the second main control ROM 14, and the second main control CPU 105, respectively.

Furthermore, in the first embodiment, the unit was referred to as the "management device (CR unit) 200," but in the second embodiment, it is referred to as the "rental unit 200." Both units have the same functions. The renting unit 200 may also be referred to as the "dedicated unit 200."
One rental unit 200 is provided for one gaming machine 10. In other words, one rental unit 200 is a device dedicated to one gaming machine 10.
In contrast, the hall computer 300 electrically connected to the rental unit 200 may be provided for each rental unit 200, or one hall computer 300 may be provided for multiple rental units 200.
Similarly, the management computer 400 electrically connected to the rental unit 200 may be provided for each rental unit 200 (the rental unit 200 and the management computer 400 may be connected one-to-one), or one management computer 400 may be provided for multiple rental units 200.

The hall computer 300 is a computer used to collect data for the operation of the hall, such as the number of games played on the day, the number of ins (throws), the number of outs (winnings), MY (number of differences, number of coins), the number of times a special device was activated, the number of loans, etc.
The control computer 400 is a computer for transmitting information to an external party (for example, an external center outside the hall). Like the hall computer 300, the control computer 400 is also installed in the hall.
In FIG. 29, the hall computer 300 and the control computer 400 are provided separately, but they may also be integrated into one computer.

In the main control board 50, as part of the storage area of the RWM 53, a bet number storage means 53a and an award number storage means 53b are provided.
The bet number storage means 53a stores the current number of bets.
On the other hand, a bet number display unit 77 is connected to the main control board 50. The bet number display unit 77 is a device that displays the bet number stored in the bet number storage means 53a, and is composed of, for example, a two-digit LED.
The awarded number storage means 53b stores the number of awarded game media when a predetermined number of game media are awarded based on the winning of a small winning combination.
On the other hand, a grant number display unit 78 is connected to the main control board 50. The grant number display unit 78 is a device that displays the grant number stored in the grant number storage means 53b, and is composed of, for example, a two-digit LED.

Furthermore, although not shown in the first embodiment (Figure 1), a setting value display means 73 is mounted on the main control board 50. The setting value display means 73 is composed of, for example, a single-digit LED, and is capable of displaying the current setting value when the setting is being changed or when the setting is being confirmed. Meanwhile, the role ratio monitor 113, which will be described later, is mounted on the gaming media count control board 100, not the main control board 50. However, this is not a limitation, and the role ratio monitor 113 may also be mounted on the main control board 50.

The gaming media count control board 100 is also referred to as the second main control board (means), payout control board (means), medal count control board (means), medal count display control board (means), or gaming media count display control board (means). Like the main control board 50, the gaming media count control board 100 requires security to prevent fraud, and is therefore housed in a board case and sealed with a crimp (sealing member) to make it difficult to open the board case (access to the gaming media count control board 100).

Like the main control board 50, the game media count control board 100 has an independent RWM 103, ROM 104, and CPU 105. The RWM 103, ROM 104, and CPU 105 may be built into a single chip. The game media count control board 100 is configured to control the display of the game media count display unit 121, send information to the lending unit 200 via the connection terminal board 130, and receive information from the lending unit 200 via the connection terminal board 130. It is also configured to send information to the main control board 50 and receive information from the main control board 50. In Figure 29, the arrows between each board indicate the direction of information transmission and reception. Therefore, the main control board 50 and game media count control board 100 are configured to be able to communicate bidirectionally.

In Figure 29, the main control board 50 and the game media number control board 100 are configured as separate units, but they can also be configured as a single main control board. However, in this case too, the first main control RWM 53, first main control ROM 54, first main control CPU 55, second main control RWM 103, second main control ROM 104, and second main control CPU 105 will be provided on one board.

The RWM 103 of the game medium count control board 100 is provided with game medium count storage means 103a (also referred to as "game medium count storage area (_NB_MEDAL)") that stores the number of game media (number of credits). When game media are awarded as a result of winning a small winning combination, the number of game media (data) in the game medium count storage means 103a is updated (added).
Furthermore, when gaming media are bet to start a game, the gaming media (data) in the gaming media number storage means 103a is updated (subtracted) by the number of gaming media corresponding to the number of bets.

A game media number display board 120 is electrically connected to the game media number control board 100. A game media number display unit 121 is mounted on this game media number display board 120. The game media number display unit 121 displays the number of game media stored in the game media number storage means 103a, and is composed of, for example, a five-digit LED.
For example, assume that the number of game media stored in the game medium number storage means 103a is "100." In this case, the game medium number display unit 121 displays "100."

When the 3-bet switch 40b is operated to start play, a bet operation signal is sent from the main control board 50 to the gaming media count control board 100. The gaming media count control board 100 determines whether the bet is possible based on the number of gaming media stored in the gaming media count storage means 103a, and if it determines that the bet is possible, it sends a bet signal to the main control board 50. Upon receiving the bet signal, the main control board 50 executes bet processing and stores the number of bets in the bet number storage means 53a. When the number of bets stored in the bet number storage means 53a is updated from "0" to "3," the display (lowest digit) of the bet number display unit 77 is also updated from "0" to "3."

Furthermore, when the gaming media count control board 100 sends a bet signal to the main control board 50 as described above, it updates the number of gaming media stored in the gaming media count storage means 103a. In this example, the number of gaming media is updated from "100" to "97". When the number of gaming media stored in the gaming media count storage means 103a is updated from "100" to "97", the display on the gaming media count display unit 121 is also updated from "100" to "97".

A settlement switch 46 is connected to the main control board 50. The settlement switch 46 is a switch that is operated to return the gaming media that have been bet (in other words, to reset the number of bets to "0").
When the number of bets is stored in a bet number storage means 53a and is displayed on a bet number display part 77, if a settlement switch 46 is operated before a start switch 41 is operated (before a game is started), the number of bets is returned (returned to the original state).
For example, as in the above example, when "3" is stored in the bet number storage means 53a and "97" is stored in the game media number storage means 103a, if the settlement switch 46 is operated, the number of bets stored in the bet number storage means 53a is updated from "3" to "0." As a result, the display on the bet number display unit 77 is updated from "3" to "0."

Furthermore, when the settlement switch 46 is operated, a settlement signal (a signal corresponding to returning the bet number "3") is sent from the main control board 50 to the gaming media count control board 100. Upon receiving this settlement signal, the gaming media count control board 100 updates the number of gaming media stored in the gaming media count storage means 103a from "97" to "100". As a result, the display on the gaming media count display unit 121 is updated from "97" to "100".

In this way, the settlement switch 46 is used to reset the betted gaming media (to "0") Therefore, even if the settlement switch 46 is operated, the number of gaming media stored in the gaming media number storage means 103a is not subtracted.
Furthermore, even if the settlement switch 46 is operated when the number of bets is not stored in the bet number storage means 53a, the number of bets stored in the bet number storage means 53a remains "0", and the number of gaming media stored in the gaming media number storage means 103a also remains the same.
In order to start such a settlement process, it is determined whether or not the settlement switch 46 has been operated, and if the settlement switch 46 has not been operated, the settlement process is not started, and if the settlement switch 46 has been operated, it is determined whether or not the number of bets stored in the bet number storage means 53a is "0." Furthermore, if the number of bets stored in the bet number storage means 53a is "0," the settlement process is not started, and if the number of bets stored in the bet number storage means 53a is not "0," the settlement process is started.
As a result, when comparing a situation in which the settlement switch 46 is operated with a situation in which the number of bets stored in the bet number storage means 53a is "0", the number of situations in which the settlement switch 46 is operated is relatively less, so by first determining whether the settlement switch 46 is operated or not, it is possible to reduce the processing load.

When the start switch 41 is operated when the number of bets is "3," the number of bets for that game is confirmed and the game begins (the reels 31 start spinning). In this case, the number of bets stored in the bet number storage means 53a may be cleared when the start switch 41 is operated (when the game begins), or may be cleared when all reels 31 have stopped. When the number of bets stored in the bet number storage means 53a is cleared, the display on the bet number display unit 77 is also updated to "0."

In the game, for example, when a small combination with a prize number of "8" is won, the main control board 50 stores "8" in the prize number storage means 53b. When the value stored in the prize number storage means 53b is updated to "8", the display (the last digit) of the prize number display unit 78 is also updated from "0" to "8".
Furthermore, when game media are awarded, an award (payout) signal is transmitted from the main control board 50 to the game media count control board 100. When the game media count control board 100 receives the award signal, it adds the number of game media corresponding to the award signal to the number of game media stored in the game media count storage means 103a. In this example, the number of game media stored in the game media count storage means 103a is updated from "97" to "105." When the number of game media stored in the game media count storage means 103a is updated from "97" to "105," the display on the game media count display unit 121 is also updated from "97" to "105."

In addition, after the number of awards is stored in the award number storage means 53b, the number of awards stored in the award number storage means 53b is cleared when the start switch 41 for the next game is operated (at the start of the game) or when all reels 31 for the next game are stopped. When the number of awards stored in the award number storage means 53b is cleared, the display in the award number display unit 78 is also updated to "0."

The game medium number display unit 121 is configured to display error information corresponding to the error that has occurred.
In this case, error information may be displayed instead of the number of game media displayed on the game medium number display unit 121, or the number of game media and the error information may be displayed alternately. For example, the number of game media may be displayed for "3" seconds, the error information may be displayed for "3" seconds, the number of game media may be displayed for "3" seconds, and so on. Note that if the game medium number display unit 121 is configured with a five-digit LED, when the error information to be displayed is, for example, "E1," it may be displayed as "000E1,""---E1,""E1000,""E1---," or the like.

Here, if the game medium count display unit 121 does not display error information corresponding to the error that occurred, the error information corresponding to the error that occurred may be displayed on the awarded number display unit 78. In this case, the awarded number display unit 78 may display the error information after displaying the number of awarded game media. For example, as described above, if the awarded number is "8", the awarded number display unit 78 may display (count up) "00" → "01" → "02" → ... "07" → "08", and then display "E1" (an example of an error code).

The counting switch 47 is electrically connected to the game media number control board 100. Although not shown, the counting switch 47 is provided on the control panel of the gaming machine 10, for example, in the same manner as the bet switch 40, etc.
When the counting switch 47 is operated, the game media (information) stored in the game media number storage means 103a can be transmitted to the rental unit 200 via the connection terminal board 130. For example, when the game media number storage means 103a stores the number of game media "200," when the counting switch 47 is operated, the information "200" is transmitted as a count value to the connection terminal board 130, and then the information "200" can be transmitted as a count value to the rental unit 200. When the counting switch 47 is operated and the count value is transmitted, "0" is stored in the game media number storage means 103a.

Furthermore, when the counting switch 47 is operated and the gaming medium count display unit 121 displays "200," if the counting switch 47 is operated and the count value "200" is sent to the lending unit 200, the display on the gaming medium count display unit 121 is updated to "0."

The game media count control board 100 is provided with a total game media count clear switch 112. When the total game media count clear switch 112 is operated, the (total) number of game media stored in the game media count storage means 103a of the game media count control board 100 can be cleared (stored as "0"). When the number of game media stored in the game media count storage means 103a is cleared, the number of game media displayed on the game media count display unit 121 is also updated to "0."
Note that the information that is cleared by operating the total number of game media clear switch 112 is only the total number of game media stored in the game media number storage means 103a, and other information is not cleared.

For example, when the number of bets stored in the bet number storage means 53a is "3" and the number of game media stored in the game media number storage means 103a is "1000," if the total game media number clear switch 112 is operated, the number of bets stored in the bet number storage means 53a will remain "3," but the number of game media stored in the game media number storage means 103a will become "0." In other words, operating the total game media number clear switch 112 does not clear the number of bets stored in the bet number storage means 53a.
Similarly, when "50" is stored as the number of game media available for lending in the number of game media storage means 206 of the lending unit 200 and the number of game media stored in the number of game media storage means 103a is "1000," if the total number of game media clear switch 112 is operated, the number of game media available for lending stored in the number of game media storage means 206 remains "50," but the number of game media stored in the number of game media storage means 103a becomes "0." In other words, operating the total number of game media clear switch 112 does not clear the number of game media available for lending stored in the number of game media storage means 206.

The total game medium count clear switch 112 may be operated by pressing it once, by pressing and holding it for a predetermined period of time, or by turning on the power while the switch is pressed. The total game medium count clear switch 112 is located in a position where it cannot be operated by the player, such as on the game medium count control board 100, inside the cabinet of the gaming machine 10, or on the back of the front door of the gaming machine 10.
When the number of game media is cleared by operating a total game media number clear switch 112, a total game media number clear status is turned on, the on state of the total game media number clear status is maintained until one game ends, and the total game media number clear status is turned off after the one game ends.
Information on the total number of game media clear status may be transmitted to the lending unit 200. When the lending unit 200 receives information that the total number of game media clear status is on, it clears the total number of game media stored in the lending unit 200. Also, when the total number of game media clear status is on in the gaming machine 10 and lending game media are provided from the lending unit 200, the total number of game media clear status remains on and the number of lending game media is newly added to the number of game media storage means 103a.

Furthermore, the total game media count clear switch 112 is invalid even if operated during game play, and becomes valid when the total game media count clear switch 112 is operated while game play is in standby mode (before game play begins or after game play ends). In this case, the game media count control board 100 determines whether game play is in progress based on game start information and game end information sent from the main control board 50, and invalidates operation of the total game media count clear switch 112 when game play is in progress.

However, the total gaming media count clear switch 112 may also be enabled by operation during play. In this case, the total gaming media count clear status is changed from ON to OFF based on the end of the next game following the game in which the total gaming media count clear switch 112 was operated. In other words, the total gaming media count clear status remains ON at the end of the game in which the total gaming media count clear switch 112 was operated, and is turned OFF when the next game ends. This allows the total gaming media count clear status to remain ON for the next game even if the total gaming media count clear status is only ON for a short time (for example, if the total gaming media count clear switch 112 is operated just before the end of the game), thereby preventing fraudulent attempts to clear the total gaming media count.

The total game media count clear status may be turned off after the end of a game in which the total game media count clear switch 112 was operated. In this case, capacity can be reduced by sharing the program that updates the total game media count clear status.

The role ratio monitor 113 displays a predetermined ratio and is composed of, for example, a 4-digit LED (7 segments (including a DP segment)). In the second embodiment, the interrupt period of the game media number control board 100 is set to "1" ms. The interrupt period of the main control board 50 is "2.235" ms.
Four interrupts constitute one cycle, and the four-digit LED of the winning combination monitor 113 is dynamically lit. Specifically, for example, an LED display counter is provided, and for each interrupt,
"00000001(B)"
"00000010(B)"
"00000100(B)"
"00001000(B)"
Configure it to cycle through.

When the LED display counter is "00000001 (B)", the LED in the ones digit of the role ratio monitor 113 can be turned on (other LEDs are off), when the LED display counter is "00000010 (B)", the LED in the tens digit of the role ratio monitor 113 can be turned on (other LEDs are off), when the LED display counter is "00000100 (B)", the LED in the hundreds digit of the role ratio monitor 113 can be turned on (other LEDs are off), and when the LED display counter is "00001000 (B)", the LED in the thousands digit of the role ratio monitor 113 can be turned on (other LEDs are off).

Of the four LEDs that make up the winning ratio monitor 113, the two LEDs on the left (thousands and hundreds) are called "identification segments" and display the type of information. The two LEDs on the right (tens and ones) are called "ratio segments" and display the calculated ratio.
In the second embodiment, the role ratio monitor 113 repeatedly displays the following six items of information (1) to (6) as ratios at predetermined intervals.
(1) Indicated role ratio (cumulative) (7P.), or advantageous zone ratio (cumulative) (7U.)
(2) Ratio of consecutive games (6000 games) (6 years)
(3) Ratio of special features (6000 games) (7 years)
(4) Ratio of consecutive wins (cumulative) (6A.)
(5) Ratio of special features (cumulative) (7A.)
(6) Ratio of the condition of special features (cumulative) (5H.)

When either the discrimination segment or the ratio segment is used to display a ratio, the DP segment in the ones digit of the discrimination segment is lit to clearly distinguish between the discrimination segment and the ratio segment. In this case, the DP segments in the tens digit of the discrimination segment and the tens and ones digits of the ratio segment are not lit.
In the above notation, for example, "P." means that "P" is displayed by the seven segments in the ones digit of the identification segment, and the DP segment of the seven segments is lit.

For example, when displaying the command-inclusive reel ratio (cumulative), if the ratio is "50"%, the symbol "7P." indicating the command-inclusive reel ratio (cumulative) is displayed in the identification segment, and "50" is displayed in the ratio segment.
Here, "cumulative total" refers to the total sum of the values that have been counted up to that point, and in this embodiment, counting continues until the number of games reaches at least "175,000."
Even after the number of games reaches "175,000," the count continues to be added until it reaches the value (upper limit) that can be stored in the storage area of a specified address of RWM 103.
In addition, "6000 games" refers to the total number of games played over 15 sets, each set consisting of "400" games.

The ratios of the above six items are explained below.
(1) Ratio of accessories with instructions (cumulative total)
"Instruction-included device ratio (cumulative)" is a ratio in which the cumulative number of awards ("award number" refers to the number of gaming media awarded; the same applies below) is used as the denominator and the sum of the cumulative number of awards when devices are activated that are awarded by the operation of devices (RB, CB, SB) and the cumulative number of instruction awards that are awarded by the operation of instruction functions is used as the numerator.
The above "total" refers to, first, when a memory area for storing the number of awards when a reel is activated and a memory area for storing the number of awards by instruction are provided separately, the total corresponds to the sum of the values stored in both memory areas. Second, when a single memory area (a reel counter with instruction) is provided for storing both the number of awards when a reel is activated and the number of awards when an instruction function is activated (hereinafter referred to as "number of awards by instruction-included reel"), the total corresponds to the value of that single memory area.

For example, if the number of plays is 175,000 or more, the cumulative number of awards is 200,000, and the cumulative number of command-based device awards is 100,000, the command-based device ratio is calculated as 50. Note that "cumulative" does not necessarily refer to the cumulative total for all plays. For example, if the cumulative number of awards reaches a predetermined upper limit (e.g., 1,677,215), or if adding the number of plays of the current game to the cumulative number of plays exceeds the upper limit, the cumulative number of awards and the sum of the cumulative number of awards when devices are activated and the cumulative number of command awards will not be updated in subsequent plays.

Furthermore, the "activation of the instruction function" corresponds to a game in which the operation mode of the stop switch 42 to obtain a favorable game result is notified (instructed) in a game in which the lottery results in a combination (winning number) that will be advantageous/disadvantageous to the game result depending on the operation mode of the stop switch 42. For example, it corresponds to a game in which the correct push order is notified when the so-called push order bell is won.
In addition, in a gaming machine 10 that is not equipped with a special feature, the "special feature ratio including instructions" is the cumulative number of instructions granted by the activation of the instruction function divided by the total number of instructions granted.

Regarding the "number of awards in a game in which the instruction function is activated," when a small prize of, for example, "15" is won based on the stop switch 42 being operated in the displayed pressing order in a game in which the instruction function is activated, "15" is added to the number of awards for the instructed role and the total number of awards.
On the other hand, in a game in which the instruction function is activated, if the stop switch 42 is operated in a different pressing order from the displayed pressing order, and a small prize of, for example, "3" is won, "3" is added to the number of instructed role prizes and the total number of prizes.
In addition, in a game in which the instruction function is activated, if the stop switch 42 is operated in a different pressing order from the displayed order and a winning combination is missed (when the combination is not won), the number of instructed combinations awarded and the total number of combinations awarded will be the same as in the previous game.

In addition, if a winning combination is missed during a game in which the instruction function is activated because the stop switch 42 is operated in a different order from the displayed order, a process of adding "0" to the number of instructed game bonuses and the total number of bonuses may be executed, so that the values of both bonuses (counters) are the same as in the previous game.

(2) Favorable zone ratio (cumulative)
The "profitable zone ratio (cumulative)" is a ratio where the cumulative number of plays is the denominator and the cumulative number of plays in the profitable zone is the numerator. For example, if the cumulative number of plays is "20,000" and the cumulative number of plays in the profitable zone is "18,000," the profitable zone ratio is calculated as "90."
It should be noted that "cumulative" does not necessarily mean the cumulative total for all games. For example, when the cumulative number of games reaches a predetermined upper limit (for example, "65535"), the cumulative number of games and the number of games in the advantageous zone are not updated in subsequent games.
Either the "instruction-included feature ratio (cumulative)" or the "advantageous zone ratio (cumulative)" is displayed depending on the specifications of the gaming machine 10. Specifically, a gaming machine equipped with an instruction function displays the "instruction-included feature ratio (cumulative)" and does not need to display the "advantageous zone ratio (cumulative)." In contrast, a gaming machine not equipped with an instruction function displays the "advantageous zone ratio (cumulative)" and does not display the "instruction-included feature ratio (cumulative)."

(3) Ratio of consecutive games (6,000 games), Ratio of consecutive games (cumulative)
"Continuous feature ratio (6000 games)" is a ratio in which the number of prizes awarded for 6000 games is the denominator and the number of prizes awarded when a continuous feature (RB) is activated during 6000 games is the numerator.
Furthermore, the "continuous feature ratio (cumulative)" is a ratio in which the number of awards in the cumulative number of games is the denominator and the number of awards when the continuous feature (RB) is activated in the cumulative number of games is the numerator. For example, if the cumulative number of games is a predetermined number (for example, 17,500 times) or more, the number of awards in the cumulative number of games is "20,000," and the cumulative number of awards when the continuous feature is activated is "10,000," the continuous feature ratio (cumulative) is calculated as "50."
It should be noted that "cumulative" does not necessarily mean the cumulative total for all games. For example, if the cumulative number of awarded prizes reaches a predetermined upper limit (for example, "65535"), or if the cumulative number of awarded prizes added to the current game result in the upper limit being exceeded, the cumulative number of awarded prizes and the cumulative number of awarded game media when consecutive game devices are activated are not updated in subsequent games.

(4) Ratio of bonuses (6,000 games), Ratio of bonuses (cumulative)
"Gem ratio (6000 games)" is a ratio in which the number of prizes awarded for 6000 games is the denominator and the number of prizes awarded when the gems (RB, CB, SB) are activated during 6000 games is the numerator.
Furthermore, the "reel ratio (cumulative)" is a ratio in which the number of awards in the cumulative number of games is the denominator and the number of awards when the reels (RB, CB, SB) are activated in the cumulative number of games is the numerator. For example, if the cumulative number of games is a predetermined number (for example, 17,500 times) or more, the cumulative number of awards is "20,000", and the cumulative number of awards when the reels are activated is "10,000", the reel ratio (cumulative) is calculated as "50".
It should be noted that "cumulative" does not necessarily mean the cumulative total for all games. For example, if the cumulative number of awarded prizes reaches a predetermined upper limit (for example, "65535"), or if the cumulative number of awarded prizes added to the current game exceeds the upper limit, the cumulative number of awarded prizes and the cumulative number of awarded game media when the game device is activated are not updated in subsequent games.

(5) Ratio of the condition of special features (cumulative)
The "reel state ratio (cumulative)" is a ratio where the cumulative number of games is the denominator and the number of games in which a reel (RB, CB, SB) is activated or the number of games in which a consecutive reel (1BB, 2BB) is activated is the numerator. For example, if the cumulative number of games is "20,000" and the cumulative number of games when a reel is activated or when a consecutive reel is activated is "5,000," the reel state ratio (cumulative) is calculated as "25."
For example, when the cumulative number of times of play reaches a predetermined upper limit (for example, "175,000"), the cumulative number of times of play and the number of times of play when a special device is activated and when a consecutive special device is activated are not updated in subsequent games.

In addition, for gaming machines that do not have the function corresponding to the above six items, the ratio segment will be displayed as "--".
For example, if the machine is not equipped with an "RB (first-class special feature)," there is no consecutive feature ratio, so when the "consecutive feature ratio (6000 games)" and "consecutive feature ratio (cumulative)" are displayed, the ratio segment is displayed as "--."

Furthermore, if the result of calculating the ratio contains decimal points, the decimal points are rounded down before displaying. For example, if the result of calculating the ratio is "49.99", it is displayed as "49".
Furthermore, when the ratio is calculated to be "100", it is displayed as "99".
Furthermore, if the calculated ratio is less than 10, a 0 will be displayed in the tens place. Specifically, if the calculated ratio is 9%, it will be displayed as 09.

The identification segment and ratio segment of the role ratio monitor 113 may be displayed in a flashing manner.
First, if the ratio is equal to or greater than a threshold, the ratio segment is displayed blinking.
The threshold values (%) for each ratio are as follows:
(1) Indicated role ratio (cumulative) or advantageous zone ratio (cumulative): 70
(2) Continuous feature ratio (6000 games): 60
(3) Ratio of bonuses (6000 games): 70
(4) Continuous feature ratio (cumulative): 60
(5) Ratio of special features (cumulative): 70
(6) Status ratio of special items (cumulative): 50
Therefore, for example, when the command-included reel ratio (cumulative) is "69," the "69" in the ratio segment will be displayed lit up when the command-included reel ratio (cumulative) is displayed, but when it is "70," it will be displayed flashing.

Secondly, when the cumulative number of games is less than the reference number of games, the identification segment is displayed in a flashing manner.
The standard number of games for each ratio is as follows:
(1) Indicated role ratio (cumulative) or advantageous zone ratio (cumulative): 175,000
(2) Continuous feature ratio (6000 games): 6000
(3) Ratio of bonuses (6000 games): 6000
(4) Continuous feature ratio (cumulative): 17,500
(5) Ratio of special features (cumulative): 17,500
(6) Status ratio of special items (cumulative): 175,000

Therefore, for example, when the cumulative number of plays is "6000", the identification segment (6y.) is displayed in a lit state when the consecutive feature ratio (6000 plays) is displayed. On the other hand, when the cumulative number of plays is "5999", the identification segment (6y.) is displayed in a flashing state when the consecutive feature ratio (6000 plays) is displayed.
Also, if the cumulative number of games played is less than "400" per set of counting units, "00" is displayed in the ratio segment.

Furthermore, when the identification segment or ratio segment is displayed in a flashing manner, it is preferable that one flashing cycle consisting of a lighting time of 0.3 seconds and a lighting time of 0.3 seconds be 0.6 seconds, with a tolerance of ±10%.
In the second embodiment, switching between on and off in the blinking display is managed (controlled) as follows.
First, the RWM 103 has a "blinking switching time (_TM_CHG_FLS)" (2 bytes) as a timer area for managing the blinking switching time.

The blinking switching time is initialized (stored as "0") when the gaming machine 10 is powered on, and is incremented by "1" for each interrupt. As described above, one interrupt time is "1" ms. Furthermore, the blinking switching time is configured to cycle between "0" and "299."
Furthermore, the RWM 103 includes a "blinking switch flag (_FL_CHG_FLS)" (1 byte) as a flag for determining whether the light is on or off.
The blinking switch flag is initialized (stores "0") when the power is turned on, and then switches between "0" and "1" every "300" ms. "0" indicates that the light is on, and "1" indicates that the light is off.

To update the blinking switching time, the process of subtracting "299" from the current timer value is performed. Specifically, the process is as follows.
Example 1) When the initial value is "0" and an update process is performed, the result becomes "0-299=298". At this time, a borrow occurs, so the carry flag becomes "1".
Example 2) When the blinking switching time is "298" and an update process is performed, the result is "298 - 299 = 1." At this time, a borrow occurs, so the carry flag becomes "1."
Example 3) When the blinking switching time is "299" and update processing is performed, the result is "299 - 299 = 0." In this case, since no borrow occurs, the carry flag becomes "0."

Then, as a result of updating the blinking switching time, if the carry flag is "1", the blinking switching flag is not updated, but if the carry flag is "0", the blinking switching flag is updated. As a result, the blinking switching flag is switched every "300" ms. Specifically, it is as follows.
Example 1) When the blinking switch flag is "0" (on), performing an update process changes it to "1" (off).
Example 2) When the blinking switch flag is "1" (off), performing update processing changes it to "0" (on).

Furthermore, the role ratio monitor 113 displays a test pattern to enable confirmation of whether the segment elements of each LED are operating normally.
The test pattern displays "8.8.8.8." (all segment elements of all LEDs (including segment DP)) until the number of times the carry flag has become "0" reaches "16" after power is turned on, i.e., until "300 ms x 16 times = 4800 ms" has elapsed.
Note that each of the four digit LEDs on the role ratio monitor 113 is dynamically lit every interrupt (1 ms), so strictly speaking, not all four LEDs are lit at the same time.

After the test pattern is displayed for 4800 ms, the display transitions to the above-mentioned (1) advantageous zone ratio (cumulative) or instructed feature ratio (cumulative) to (6) feature state ratio (cumulative), and (1) to (6) are each displayed for 4800 ms, and this is repeated.
Therefore,
Power on ↓
(0) Test pattern display (4800 ms)
↓
(1) Display of the ratio of the indicated role (cumulative) or the ratio of the advantageous zone (cumulative) (4800 ms)
↓
(2) Continuous feature ratio (6000 games) display (4800 ms)
↓
(3) Display of the ratio of the winning combination (6000 games) (4800 ms)
↓
(4) Continuous feature ratio (cumulative) display (4800 ms)
↓
(5) Display of the ratio of the winning combination (cumulative) (4800 ms)
↓
(6) Display of the status ratio (cumulative) of the reels, etc. (4800 ms)
↓
(1) Display of the ratio of the indicated role (cumulative) or the ratio of the advantageous zone (cumulative) (4800 ms)
↓
:
This becomes:
As with the test pattern, the ratios (1) to (6) are displayed until the number of times the carry flag becomes "0" reaches "16" (300 ms x 16 times = 4800 ms).

As described above, when the discrimination segment or ratio segment is displayed in a flashing manner, the segment is repeatedly turned on for 300 ms and turned off for 300 ms (one cycle is 600 ms).
Then, when the time for turning on or off the light is T1 and the time for displaying the test pattern or ratio is T2,
T2 = T1 x 2 x n (n is a natural number)
By setting it to this, the timing of switching between lighting and extinguishing can be made to coincide with the timing of switching between the test pattern display or the ratio display, making it possible to provide a good-looking display and preventing a person looking at the role ratio monitor 113 from mistakenly thinking that there may be a malfunction.
In the above, when "T1" is set to "300" ms, "T2" is a multiple of "600" ms, but in order to set each ratio display time to "5000 ms ± 10%", "T2" should be set to "4800" ms.

For example, if you want to flash the favorable zone ratio after flashing the test pattern,
Test pattern (lights on for 300 ms. Total 300 ms.)
↓
Test pattern (lights off for 300 ms. Total 600 ms.)
↓
:
↓
Test pattern (lights on for 300 ms. Total 4500 ms.)
↓
Test pattern (lights off for 300 ms. Total 4800 ms. Test pattern display ends.)
↓
Advantageous zone ratio (lights up for 300 ms)
↓
Advantageous zone ratio (lights off for 300 ms)
↓
:
This becomes:

In this way, when lighting up some kind of information, the light can be maintained for 300 ms. In other words, it is possible to prevent the light from going out before 300 ms has elapsed after starting to light up the display of some kind of information. Furthermore, it is possible to prevent the information from disappearing immediately after starting to light up the display of some kind of information (which could lead to the mistaken belief that there may be a malfunction).

Returning to the block diagram of FIG.
The sub-control board 80 is similar to the sub-control board 80 of the first embodiment (FIG. 1), and therefore a description thereof will be omitted. However, the RWM 83, ROM 84, and CPU 85 of the sub-control board 80 may be referred to as the sub-control RWM 83, the sub-control ROM 84, and the sub-control CPU 85, respectively.
The performance lamp 21, speaker 22, and image display device 23 electrically connected to the sub-control board 80 are also the same as those in the first embodiment.
The connection terminal board (also referred to as the "game ball lending device connection terminal board") 130 serves as a relay board for two-way communication between the gaming machine 10 and the lending unit 200.

The lending unit 200 corresponds to the management device 200 in the first embodiment (FIG. 1). As in the first embodiment, a lending switch 202, a return switch 203, and the like are provided.
In addition, the loanable gaming media number display unit 204 corresponds to the degree display unit 204 in the first embodiment, and displays the maximum number of gaming media that can be loaned from the loan unit 200 to the gaming machine 10, and is composed of, for example, a three-digit LED.

Furthermore, the lendable gaming media number storage means 206 stores the maximum number of gaming media that can be loaned from the lending unit 200 to the gaming machine 10, and is composed of, for example, an RWM provided inside the lending unit 200. The number of lendable gaming media stored in the lendable gaming media number storage means 206 is displayed on the lendable gaming media number display unit 204.

When the number of lendable gaming media stored in the lendable gaming media number storage means 206 is "400," and the lending switch 202 is operated, and the specifications are such that "50" gaming media are lent from the lending unit 200 to the gaming machine 10 with each operation of the lending switch 202, after a lending notification is sent, "50" is added to the number of gaming media stored in the gaming media number storage means 103a. Meanwhile, the number of lendable gaming media stored in the lendable gaming media number storage means 206 is updated from "400" to "350."

In addition, when the return switch 203 is operated, the number of gaming media stored in the rental-available gaming media number storage means 206 of the rental unit 200 is stored in a gaming media number storage medium (magnetic card, IC card, IC coin, etc.), and the gaming media number storage medium is ejected from the rental unit 200.
In addition, in a situation where the number of game media stored in the game media number storage means 103a of the game media number control board 100 is greater than "0" and the number of game media is not stored in the lendable game media number storage means 206 of the lending unit 200, the game media number storage medium will not be ejected even if the return switch 203 is operated. In other words, even if the number of game media is stored in the game media number storage means 103a of the game media number control board 100, if the number of game media is not stored in the lendable game media number storage means 206 of the lending unit 200, the game media number storage medium will not be ejected even if the return switch 203 is operated.

In the above case, therefore, by operating the counting switch 47, the number of gaming media stored in the gaming media number storage means 103a is sent to the lending unit 200, and the number of gaming media is stored in the lendable gaming media number storage means 206. Then, by operating the return switch 203, the number of gaming media stored in the lendable gaming media number storage means 206 is stored in the gaming media number storage medium, which is then ejected from the lending unit 200. Once the number of gaming media stored in the lendable gaming media number storage means 206 is stored in the gaming media number storage medium, the number of lendable gaming media stored in the lendable gaming media number storage means 206 is updated to "0".

FIG. 30 is a diagram illustrating the telegrams used for communication between the gaming machine 10 and the rental unit 200.
As shown in FIG. 30, the types of messages are:
The following messages are provided: 1. Gaming machine information notification 2. Counting notification 3. Loan notification 4. Loan receipt result response.
Of these messages, the gaming machine information notification, counting notification, and rental receipt result response are messages sent from the gaming machine 10 to the rental unit 200.
On the other hand, the rental notification is a message sent from the rental unit 200 to the gaming machine 10.

Each message is composed of the following five pieces of data:
(1) Message length (2) Command (3) Serial number, counting serial number, or loan serial number (4) Data section (5) Checksum A group of data consisting of the above five items is called a "message" and is sent in one transmission. In other words, it is not sent in parts.

(1) Message Length "Message length" refers to the length of the data consisting of five parts: message length, command, serial number (serial number, count serial number, or loan serial number), data section, and checksum, and is composed of 1 byte of data. For example, if the message length is 1 byte, the command is 1 byte, the serial number is 1 byte, the data section is 14 bytes, and the checksum is 1 byte, the message will be 18 bytes, and the message length will be the data corresponding to 18 bytes (12h).

(2) Command A "command" is data for notifying the type of message, among gaming machine information notification, counting notification, loan notification, and loan receipt result response, and is composed of 1 byte of data.
For example, as shown in Figure 30, the command for gaming machine information notification is set to "01h", the command for counting notification is set to "02h", the command for loan notification is set to "13h", and the command for loan receipt result response is set to "03h".
The receiver of the message can identify the type of message by determining the command value.

(3) Serial Number "Serial number" is data that refers to the number contained in the gaming machine information notification, counting notification, loan notification, and loan receipt result response. The serial number contained in the gaming machine information notification is called the "serial number," the serial number contained in the counting notification is called the "counting serial number," the serial number contained in the loan notification is called the "loan serial number," and the serial number contained in the loan receipt result response is called the "loan serial number." These various serial numbers are numbers in the range of "0" to "FFh" and are composed of 1-byte data.
When the gaming machine 10 is turned on, the serial number is controlled to notify "00h".
After the power is turned on, the serial number is updated (+1) every time a notification is sent.
The value following the serial number "FFh" is updated to "01h" (+1 twice) (it will not become "0").

(4) Data Section The "data section" corresponds to data corresponding to the gaming machine information notification, counting notification, loan notification, and loan receipt result response. Details of the data section of each message will be described later.
(5) Checksum A "checksum" is a value indicating the lowest byte of the total obtained by adding up five pieces of data: message length, command, serial number, data section, and checksum. Using this checksum, the receiving side can determine whether data has been corrupted during communication. For example, the gaming machine 10 or the rental unit 200 can count the number of messages whose checksums do not match and check the status of communication problems, etc. For example, in the gaming machine 10, the number of messages whose checksums do not match may be displayed on the image display device 23 or the like in a specified situation (such as during a setting confirmation mode in which setting values can be confirmed or during a setting change mode in which setting values can be changed).

Next, each of the data sections of the gaming machine information notification, counting notification, loan notification, and loan receipt result response will be explained.
1. Data Section of Gaming Machine Information Notification The data section of the gaming machine information notification is made up of gaming machine type, gaming machine information type, and gaming machine information, as shown in FIG.
a) Gaming Machine Type "Gaming machine type" is information for identifying the type of gaming machine 10. This information is data notifying, for example, the management medium, group classification, gaming machine type, etc.

b) Gaming machine information type "Gaming machine information type" is information for identifying whether the gaming machine information in the gaming machine information notification being notified this time is gaming machine performance information, gaming machine installation information, or hall control/fraud monitoring information. When notifying gaming machine performance information, "00h" is notified, when notifying gaming machine installation information, "01h" is notified, and when notifying hall control/fraud monitoring information, "02h" is notified.

c) Gaming Machine Information "Gaming Machine Information" consists of gaming machine performance information, gaming machine installation information, and hall control/fraud monitoring information. As gaming machine information, any one of gaming machine performance information, gaming machine installation information, and hall control/fraud monitoring information is transmitted.
Here, the hall control and fraud monitoring information is transmitted, in principle, every 300 ms (each time a gaming machine information notification is transmitted).
In addition, gaming machine installation information is transmitted every "60" seconds.
Furthermore, gaming machine performance information is generally transmitted every 180 seconds.
In the above, "as a general rule" means that if the transmission timings of multiple pieces of gaming machine information overlap, the gaming machine information with the higher priority is transmitted. In other words, if the transmission timings of gaming machine performance information, gaming machine installation information, and hall control/fraud monitoring information overlap, one of them is transmitted according to priority. As shown in Figure 30, gaming machine installation information transmitted every "60" seconds has the first priority, and gaming machine performance information transmitted every "180" seconds has the second priority.

Furthermore, the transmission period of hole control and fraud monitoring information, 300 ms, may be within the range of 300 to 310 ms.
Similarly, the transmission cycle of the gaming machine installation information, "60" seconds, may be within the range of "60" to "62" seconds.
Similarly, the transmission period of the gaming machine performance information, 180 seconds, may be within the range of 180 to 186 seconds.
However, the range of the transmission period described above does not take a random value each time, but is a predetermined value.

FIG. 31 is a diagram for explaining the specific configuration of gaming machine information in the gaming machine information notification, including gaming machine performance information, gaming machine installation information, and hall control/fraud monitoring information.
(a) Gaming machine performance information Gaming machine performance information consists of the following information such as the total number of inserts.
a) Total Insertion Number The "total insertion number" is the cumulative number of gaming media inserted since the power was turned on. Note that if a power outage occurs and the power is then turned on, "0" may be output as the total insertion number. For example, if the cumulative number of gaming media inserted is "2000" after a total of "1000" games, the total insertion number will be "2000," and "2000" may be output as the total insertion number. If a power outage occurs and the power is then turned on, "0" may be output as the total insertion number. Note that if a replay is won by the winning combination lottery and the symbol combination corresponding to the replay is stopped and displayed, the number of bets for the next game of that game is not included in the total insertion number.

b) Total Number of Awards The "total number of awards" is the cumulative number of game media awarded since the power was turned on. If a power outage occurs and the power is then turned on, "0" may be output as the total number of awards. For example, if the cumulative number of game media awarded is "2000" after a total of "1000" games, the total number of awards will be "2000," and "2000" may be output as the total number of awards. If a power outage occurs and the power is then turned on, "0" may be output as the total number of awards.
In addition, if the number of gaming media bet in a game is automatically bet based on the stopped display of a pattern combination corresponding to a replay, the automatically bet gaming media will not be included in the "number of awarded games."

c) MY (number of differences)
"MY" is also called "difference number" or "difference number of sheets."
"MY" is information about the maximum difference that can be calculated from the number of gaming media awarded and the number of gaming media inserted since the power was turned on. If a power outage occurs and the power is then turned on, "0" may be output as MY. Specifically, the maximum difference is the increase in the number of gaming media from the reference point where the number of gaming media was lowest when the game result was obtained (the total number awarded minus the total number inserted). For example, if, in a total of "1000" games, the "100th" game has the smallest difference in the number of gaming media, with the number of gaming media at that time being "-200," and the "800th" game from that point has the largest difference in the number of gaming media, with the number of gaming media at that time being "+800," then MY becomes "+1000," and "1000" may be output as MY. If a power outage occurs and the power is then turned on, then "0" may be output as MY.

d) Total number of granted reels The "total number of granted reels" is the total number (cumulative number) of game media granted by the operation of reels (single bonus (SB), regular bonus (RB), and challenge bonus (CB)) since the power was turned on. If a power outage occurs and the power is then turned on, "0" may be output as the total number of granted reels. For example, if the total number of game media obtained by the operation of reels is "100" after a total of "1000" games, the total number of granted reels will be "100," and "100" may be output as the total number of granted reels. If a power outage occurs and the power is then turned on, "0" may be output as the total number of granted reels.

e) Total number of consecutive game devices awarded The "total number of consecutive game devices awarded" is the total number (cumulative number) of game media awarded by the operation of consecutive game devices (first-class special game devices, also called regular bonuses (RB)) since the power was turned on. If a power outage occurs and the power is then turned on, "0" may be output as the total number of consecutive game devices awarded. For example, if the total number of game media obtained by the operation of consecutive game devices is "100" after a total of "1000" games have been played, the total number of consecutive game devices awarded will be "100," and "100" may be output as the total number of consecutive game devices awarded. If a power outage occurs and the power is then turned on, "0" may be output as the total number of consecutive game devices awarded.
In addition, the number of game media awarded by the operation of a first-class special feature by a first-class special feature continuous operation device (also referred to as "Type 1 BB") is also accumulated as the total number of consecutive feature awards.

f) Role Ratio As described above, this is the role ratio (cumulative) value displayed by the role ratio monitor 113. When the cumulative number of games is less than a predetermined number (for example, 17,500 times), "FFh" is output as the role ratio (cumulative).
g) Continuous feature ratio As described above, this is the value of the continuous feature ratio (cumulative) displayed by the feature ratio monitor 113. When the cumulative number of games is less than a predetermined number (for example, 17,500 times), it is configured to output "FFh" as the continuous feature ratio (cumulative).

h) Advantageous Zone Ratio As described above, this is the value of the advantageous zone ratio (cumulative) displayed by the role ratio monitor 113. When the cumulative number of games is less than a predetermined number (for example, 175,000 games), "FFh" is output as the advantageous zone ratio. Also, gaming machines that do not have advantageous zones are configured to output "FFh."
i) Indication-Included Role Ratio As described above, this is the value of the instruction-included role ratio (cumulative) displayed by the role ratio monitor 113. When the cumulative number of games is less than a predetermined number (for example, 175,000 times), "FFh" is output as the instruction-included role ratio. Also, gaming machines that do not have roles or instruction functions are configured to output "FFh."

j) Gambling Device State Ratio As described above, this is the value of the gaming device state ratio (cumulative) displayed by the gaming device ratio monitor 113. When the cumulative number of games is less than a predetermined number (for example, 175,000 games), "FFh" is output as the gaming device state ratio. Also, gaming machines that do not have a gaming device are configured to output "FFh".
k) Number of Games The "number of games" is the cumulative number of games played since the gaming machine 10 was powered on. It is cleared ("0" is stored) when the gaming machine 10 is powered on.
l) Others Other information includes multiple types of information, such as information used in the rental unit 200, but description thereof will be omitted in this embodiment.

(i) Gaming Machine Installation Information The gaming machine installation information is composed of the following information such as the main control chip ID number.
a) Main control chip ID number The "main control chip ID number" is information including an individual chip number for identifying the main control chip that integrates the CPU 55, RWM 53, and ROM 54 provided on the main control board 50, and is different information for each gaming machine 10 even if they are the same model.
b) Main Control Chip Manufacturer Code The "main control chip manufacturer code" is information that indicates the gaming machine manufacturer stored in the built-in memory of the main control chip.

c) Main Control Chip Product Code The "main control chip product code" is information indicating the model name of the gaming machine 10 stored in the built-in memory of the main control chip.
The above-mentioned main control chip ID number, main control chip manufacturer code, and main control chip product code are configured to be transmitted from the main control board 50 to the gaming media count control board 100 during power-on processing when the gaming machine 10 is powered on. The RWM 103 of the gaming media count control board 100 is configured to store the main control chip ID number, main control chip manufacturer code, and main control chip product code, respectively.

d) Game Media Count Control Chip ID Number The "game media count control chip ID number" is information including an individual chip number for identifying the game media count control chip that is an integrated unit of the CPU 105, RWM 103, and ROM 104 provided on the game media count control board 100, and is different information for each game machine 10 even if they are the same model.
In the case of a gaming machine that does not have the gaming media count control board 100 mounted thereon, "000000000000000000h" can be output to the lending unit 200 as the gaming media count control chip ID number.

e) Game Medium Number Control Chip Manufacturer Code The "game medium number control chip manufacturer code" is information indicating the game machine manufacturer stored in the built-in memory (ROM 54) of the game medium number control chip.
In the case of a gaming machine that does not have the gaming media count control board 100 mounted thereon, "000000h" can be output to the lending unit 200 as the gaming media count control chip manufacturer code.
f) Game Medium Count Control Chip Product Code The "game medium count control chip product code" is information indicating the model name of the game machine 10 stored in the built-in memory (ROM 54) of the main control chip.
In the case of a gaming machine that does not have the gaming media count control board 100 mounted thereon, the gaming media count control chip product code "0000000000000000h" can be output to the rental unit.

(c) Hall control and fraud monitoring information Hall control and fraud monitoring information consists of the following information such as the number of gaming media.
a) Number of gaming media The "number of gaming media" is information indicating the current number of gaming media (total number) stored in the gaming media number control board 100, and is deducted by the insertion (betting) of gaming media and added by the awarding of gaming media based on the winning of a minor winning combination. The current number of gaming media is stored in the gaming media number storage means 103a and displayed on the gaming media number display unit 121. For example, if "2000" is stored as the number of gaming media, "0007D0h" can be output to the lending unit 200 as the number of gaming media. The upper limit of the number of gaming media that can be stored in the gaming media number control board 100 is "16383 (D)."
In addition, by transmitting the current number of game media to the rental unit 200 (every 300 ms), it becomes possible for the rental unit 200 to manage the number of game media as well. This further enhances security.

b) Inserted Number "Inserted Number" is information indicating the number of gaming media inserted (betted). For example, if "3" gaming media is inserted (betted), "03h" can be output to the lending unit 200. Furthermore, if "3" is inserted and the inserted number "3" is returned to the gaming media number control board 100 by operating the settlement switch 46 before starting the game (before the start switch 41 is operated), "FDh" corresponding to "-3" can be output to the lending unit 200. In other words, information from "-3" (FDh) to +3 (03h) can be output to the lending unit 200.

c) Number of Awards The "number of awards" is information indicating the number of game media (payouts) awarded depending on the pattern combination that stops on the pay line (winning) after all reels 31 have stopped. For example, if the number of game media "8" is awarded, information "08h" can be output, and if the number of game media "15" is awarded, information "0Fh" can be output to the lending unit 200.
In this way, the gaming machine 10 transmits the above-mentioned "number of gaming media,""numberinserted," and "number awarded" to the lending unit 200, thereby enabling the lending unit 200 to detect abnormalities in the number of gaming media.

d) Main Control State 1
"Main control status 1" is information indicating a status related to the gaming status. Specifically, each bit of the 1-byte data is assigned a gaming status. For example, when the D0 bit is "1", it indicates the RB status, and when the D1 bit is "1", it indicates the BB status, and when the D2 bit is "1", it indicates the AT status. The gaming machine 10 is then able to output this information to the lending unit 200.

Bits D3 to D6 correspond to gaming machine status signals 1 to 4. The usage of gaming machine status signals 1 to 4 can be changed or not used depending on the type of gaming machine 10. For example, gaming machine status signal 1 can be output each time the number of gaming media awarded in AT reaches "100." Bit D7 is unused and is configured to output "0" regardless of the type of gaming machine 10. By configuring it in this way, for example, to notify that the gaming machine is in AT state, "00000100B" can be output to the lending unit 200.

e) Main Control State 2
"Main control state 2", like main control state 1, is information indicating a state related to the gaming state. Bits D0 to D2 correspond to gaming machine state signals 5 to 7. The usage of gaming state signals 5 to 7 can be changed or not used depending on the type of gaming machine 10. For example, gaming state signal 5 can be output when a specific RT state (a state with variable replay probability (high probability)) is entered. Bits D3 to D7 are unused and are configured to be able to output "0" regardless of the type of gaming machine 10. By configuring in this way, for example, when a specific RT state is entered, "00000001B" can be output to the lending unit 200.

f) Gaming Machine Error Status The “gaming machine error status” is information including an error code indicating an error occurring in the gaming machine 10 .
Specifically, bits D0 to D5 indicate an error code. Bit D6 indicates whether the error is in the game media count control board 100 (in this case, bit D6 is "0") or in the main control board 50 (in this case, bit D6 is "1"). Bit D7 indicates whether the lending unit 200 will only notify the error (in this case, bit D7 is "0"), or whether the lending unit 200 will notify the error and also notify the hall computer 300 of the error code via the lending unit 200 (in this case, bit D7 is "1").

For example, suppose the gaming machine 10 is capable of detecting two types of errors: a random number anomaly error and a radio wave anomaly error. In this case, the error code can be set to "00001B" for the random number anomaly error and "00010B" for the radio wave anomaly error, and information including these error codes can be output. Specifically, if the random number anomaly error is an error in the main control board 50 and the lending unit 200 only issues an error notification, "01000001B" can be output to the lending unit 200. Furthermore, if the radio wave anomaly error is an error in the gaming media count control board 100 and the lending unit 200 issues an error notification and also notifies the hall computer 300 of the error code, "10000010B" can be output to the lending unit 200. Note that if no error has occurred or the gaming machine does not have an error code, "00000000B" can be output to the lending unit 200.

g) Gaming machine fraud 1 (main control)
"Gaming Machine Irregularity 1 (Main Control)" is information relating to the detection of irregularities related to the main control board 50 and the status of the main control board 50. The gaming machine irregularity 1 (main control) signal is treated as a signal for the hall computer 300. In other words, each gaming machine irregularity 1 (main control) signal output from the gaming machine 10 is output to the hall computer 300 via the lending unit 200.

The signals that make up gaming machine fraud 1 (main control) are as follows.
First, a setting change signal is assigned to bit D0. When bit D0 is "1", it indicates that the setting is being changed (in setting change mode) and that the setting has been changed. The setting change signal is set to bit D0 "1" from the time the setting is being changed until the end of one game after the setting change (for example, when all reels 31 have stopped and the awarding process of game media has ended). In situations other than the time from the time the setting is being changed until the end of one game after the setting change, bit D0 is set to "0".
The D1 bit is assigned a setting confirmation signal. When the setting is being confirmed (in setting confirmation mode), the D1 bit is set to "1," and when the setting is not being confirmed, the D1 bit is set to "0."

The D2 bit is assigned to fraud detection signal 1, the D3 bit to fraud detection signal 2, and the D4 bit to fraud detection signal 3. For example, in a gaming machine 10 in which random number abnormalities are considered to be fraud, if detection of a random number abnormality is assigned to fraud detection signal 1, the D2 bit will be "1" if a random number abnormality is detected, and will be "0" if a random number abnormality is not detected.
The D5 bit is assigned a security signal. Specifically, the D5 bit is set to "1" when a fraud detection signal is being output, a setting change signal is being output, or a setting confirmation signal is being output, and is set to "0" in all other cases.
Bits D6 and D7 are unused and are both set to "0".

h) Gaming machine fraud 2 (main control or control of the number of gaming media)
"Gaming machine fraud 2 (main control or gaming media number control)" is information indicating the detection of fraud related to the main control board 50 or gaming media number control board 100, or the status related to the main control board 50 or gaming media number control board 100. The gaming machine fraud 2 (main control or gaming media number control) signal is treated as a signal for the hall computer 300. In other words, each gaming machine fraud 2 (main control or gaming media number control) signal output from the gaming machine 10 is output to the hall computer 300 via the lending unit 200.

The signals that make up gaming machine fraud 2 (main control or gaming media number control) are as follows.
The D0 bit is assigned a setting door open signal. The "setting door open signal" is a signal that indicates whether the setting key switch cover that covers the setting key switch 12 for changing settings is open or not. When the setting key switch cover is open, the D0 bit is "1," and when the setting key switch cover is closed, the D0 bit is "0." In gaming machines that do not have a setting key switch cover or a gaming machine that does not have a function to detect when the setting key switch cover is open, the D0 bit is "0."

The D1 bit is assigned a door open signal. The "door open signal" is information indicating whether the door (also called the "front door") of the gaming machine 10 is open or not. When the door of the gaming machine 10 is open, the D1 bit is "1," and when the door of the gaming machine 10 is closed, the D1 bit is "0."
The D2 bit is unused and is set to "0".
The D3 bit is assigned to game media count clear detection. "Game media count clear detection" refers to the detection that the total game media count clear switch 112 provided on the game media count control board 100 has been operated (the total game media count has been cleared).
If operation of the total number of game media clear switch 112 is detected, the D3 bit becomes "1," and if operation of the total number of game media clear switch 112 is not detected, the D3 bit becomes "0." In the case of a gaming machine that does not have the total number of game media clear switch 112, the D3 bit becomes "0."
Bits D4 to D7 are unused and are set to "0".

i) Gaming machine fraud 3 (main control or control of the number of gaming media)
"Gaming Machine Fraud 3" is provided as a backup and indicates the detection of fraud relating to the main control board 50 or the gaming media number control board 100, and information on the status of the main control board 50 or the gaming media number control board 100.
In the gaming machine 10 of this embodiment, gaming machine fraud 3 (main control or gaming media number control) is unused, and bits D0 to D7 are "0".
Furthermore, although not shown in FIG. 31, other information is provided as hole control/fraud monitoring information, but the description thereof will be omitted in this embodiment.

Returning to the explanation of FIG.
2. Data Section of Counting Notification The data section of the counting notification is composed of the counted number of gaming media and the counted cumulative number of gaming media.
a) Number of Counted Game Media The "number of counted game media" is the number of game media sent (returned) from the gaming machine 10 to the lending unit 200 upon operation of the counting switch 47. The number of counted game media ranges from "0x00h" to "0x32h," and a maximum of "50 (D)" can be sent to the lending unit 200 in one count notification. Furthermore, if the number of game media stored in the game media count control board 100 is "50" or more, data "0x32h" indicating "50" is sent. However, if the number of game media stored in the game media count control board 100 is less than "50," data corresponding to the current number of game media stored in the game media count control board 100 is sent. For example, if the number of game media stored in the game media count control board 100 is "30 (D)," data "0x1Eh" is sent.

Note that the above-mentioned example of the number of counted gaming media is an example in which "50" is notified when the counting switch 47 is operated only once (hereinafter referred to as a "short press operation"). However, it is also possible to notify "1" as the number of counted gaming media when the counting switch 47 is operated only once, and to notify "50" as the number of counted gaming media when the counting switch 47 is operated for a long time.
Here, "accepting a short press of the counting switch 47" means, for example, that the period during which the level data relating to the operation acceptance of the counting switch 47 on the game media number control board 100 is a value indicating ON (the period during which the operation acceptance of the counting switch 47 is a value indicating ON in the interrupt processing) is less than a predetermined period (for example, less than "1" second). In other words, if the operation of the counting switch 47 is accepted for a time less than the predetermined period, it is determined that a short press of the counting switch 47 has been accepted, and the number of counted game media is set to "1."

If the counting switch 47 were to count the number of gaming media to "50" uniformly when operated once, the player would not be able to withdraw less than "50" gaming media, for example, "1" gaming medium, at their own will. Therefore, if it were possible to withdraw the smallest unit of gaming media, "1," by briefly pressing the counting switch 47, this would be in line with the purpose of the counting switch 47, which is to "have the ability to freely withdraw gaming media."

On the other hand, "a long press of the counting switch 47 has been accepted" refers to, for example, a period during which the level data relating to the acceptance of the counting switch 47 operation on the gaming media count control board 100 is at a value indicating ON (the period during which the acceptance of the counting switch 47 operation is at a value indicating ON in the interrupt processing) that is longer than a predetermined period (for example, 1 second or longer). In other words, if the operation of the counting switch 47 is accepted for a period of time that is longer than the predetermined period, it is deemed that a long press of the counting switch 47 has been accepted, and the number of counted gaming media is set to 50.

In addition, after the number of counted gaming media "50" is sent to the rental unit 200 in the counting notification, if the counting switch 47 is still being pressed and held at the time the next counting notification is sent, the number of counted gaming media "50" will be sent to the rental unit 200 as a counting notification. In other words, once a long press is determined, the number of counted gaming media "50" will continue to be sent to the rental unit 200 in the counting notification until the counting switch 47 is no longer operated (until the level data related to the operation acceptance of the counting switch 47 becomes a value indicating off). In this case, counting will not occur until it is determined that the counting switch 47 is being pressed and held (for example, for "1" second).

b) Counted Cumulative Number of Gaming Media The "counted cumulative number of gaming media" is the cumulative value of the counted number of gaming media since the gaming machine 10 was powered on. The counted cumulative number of gaming media ranges from "0x0000h" to "0xFFFFh", and the counted number of gaming media is added each time counting is performed. Note that if the counted cumulative number of gaming media exceeds "0xFFFFh", the value next to "0x0000h" is set to "0x0000h". Furthermore, when the gaming machine 10 is powered on, the counted cumulative number of gaming media is cleared (set to "0").

3. Data Section of the Lending Notification The "Number of Lending Game Media" data section of the lending notification is the number of lending game media transmitted from the lending unit 200 to the gaming machine 10 when the lending switch 202 of the lending unit 200 is operated. The number of lending game media ranges from "0x00h" to "0x32h," and a maximum of "50 (D)" can be transmitted to the gaming machine 10 in one lending notification. Furthermore, if the number of lendable game media stored in the lending unit 200 is "50" or more, data "0x32h" indicating "50" is transmitted to the gaming machine 10. In contrast, if the number of lendable game media stored in the lending unit 200 is less than "50," data corresponding to the current number of lendable game media stored in the lending unit 200 is transmitted. For example, if the number of lendable game media is "20," data "0x14h" indicating "20" is transmitted.

4. Data section of the loan receipt result response The "number of loaned gaming media received result," which is the data section of the loan receipt result response, is data sent from the gaming machine 10 to the loan unit 200 based on the reception of data on the number of loaned gaming media sent from the loan unit 200 to the gaming machine 10. If the data received from the loan unit 200 is normal, it will be "0x00h," and if it is abnormal, it will be "0x01h."
Examples of abnormal cases include:
a) If the rental serial numbers notified from the rental unit 200 are not consecutive,
b) When the gaming machine 10 is in a state where it cannot be rented out due to an abnormality in the RWM 103 of the gaming media count control board 100,
c) When the value obtained by adding the total number of game media stored in the game media count control board 100 and the number of loaned game media exceeds the upper limit of the number of game media stored in the game media count control board 100.
Furthermore, if the value becomes other than "0x00h" or "0x01h" due to other factors, the rental unit 200 will also determine that an abnormality has occurred.

Next, communication between the gaming machine 10 and the rental unit 200 will be described.
FIG. 32 is a time chart showing the basic communication sequence between the gaming machine 10 and the rental unit 200.
The gaming machine 10 transmits a gaming machine information notification to the rental unit 200 every 300 ms from the time when the startup of the gaming machine 10 is completed. In the example of Fig. 32, after transmitting the gaming machine information notification of serial number "n", after 300 ms has elapsed, the gaming machine information notification of serial number "n+1" is transmitted.
As shown in Figure 30, among the gaming machine information in the gaming machine information notification, gaming machine performance information is sent every "180" seconds, gaming machine installation information is sent every "60" seconds, and hall control/fraud monitoring information is sent every "300"ms; more on this later.

Furthermore, the gaming machine 10 transmits a counting notification to the rental unit 200 after "100" ms has elapsed since transmitting the gaming machine information notification.
In addition, the rental unit 200 transmits a rental notification to the gaming machine 10 within 170 ms after receiving the counting notification. Then, the gaming machine 10 transmits a rental receipt result response to the rental unit 200 within 10 ms after receiving the rental notification.
Since the gaming machine 10 sends the next gaming machine information notification 300 ms after sending the gaming machine information notification, the time between sending the loan receipt result response and sending the next gaming machine information notification is 20 ms or more.

FIG. 33 is a time chart illustrating an example 1 of the startup sequence of the gaming machine 10 and the rental unit 200, showing the case where the gaming machine 10 starts up first.
When the power supply to both the gaming machine 10 and the rental unit 200 is off (synonymous with "power off"; same below), the VL signal and PSI signal between the gaming machine 10 and the rental unit 200 are off.
The VL signal is a signal that is turned on when the gaming machine 10 is playable (gaming media can be bet), and is a signal that is kept off until the lending unit 200 is activated.
In addition, the PSI signal is a connection signal between the gaming machine 10 and the rental unit 200, and is a signal that is off until the rental unit 200 is started up.

After the power is turned on, when the start-up of the gaming machine 10 is completed, the start-up of the rental unit 200 is not yet completed.
In this situation, the gaming machine 10 sends the first message, i.e., a gaming machine information notification, to the rental unit 200 in accordance with the message notification program, and then, as described above, sends a counting notification 100 ms after sending the gaming machine information notification. However, since the rental unit 200 has not yet completed startup when the gaming machine information notification and counting notification are sent, the rental unit 200 cannot receive these gaming machine information notification and counting notification. In the figure, the "?" mark indicates that although the gaming machine 10 has sent the gaming machine information notification and counting notification, the rental unit 200 cannot receive these notifications.
Furthermore, since the rental unit 200 has not yet started up and has not yet received the counting notification, the rental unit 200 will not send a rental notification to the gaming machine 10. Therefore, the gaming machine 10 will not send a rental receipt result response.

After the gaming machine 10 has completed booting, the serial number of the first gaming machine information notification and the counting serial number of the counting notification sent will be "0x00h". Furthermore, since the serial number and counting serial number are updated regardless of whether the gaming machine 10 and the rental unit 200 are connected, the serial number and counting serial number will be "0x01h" at the next transmission timing (the timing transmitted "300" ms after the first gaming machine information notification sent after the gaming machine 10 has completed booting).

After that, when the startup of the lending unit 200 is completed, the VL signal and the PSI signal are turned on, and the operation of the bet switch 40 and the counting switch 47 of the gaming machine 10 becomes valid. In addition, the lending unit 200 becomes able to receive information transmitted from the gaming machine 10. After startup, the lending unit 200 becomes able to transmit a lending notification to the gaming machine 10 based on the reception of the counting notification. The example of Figure 33 shows an example in which the gaming machine 10 transmits a counting notification of counting serial number "m" to the lending unit 200, and when the lending unit 200 receives the notification, it transmits a lending notification of lending serial number "k" to the gaming machine 10.
Furthermore, the gaming machine 10 becomes able to transmit a rental receipt result response to the rental unit 200 based on the received rental notification. The example of Figure 33 shows an example in which the gaming machine 10 transmits a rental receipt result response for rental serial number "k" to the rental unit 200 based on receiving a rental notification for rental serial number "k".

As described above, the gaming machine 10 sends gaming machine information notifications and counting notifications regardless of whether the rental unit 200 is activated or not, and the rental unit 200 manages the serial number of the gaming machine information notification and the counting serial number of the counting notification sent from the gaming machine 10 after the rental unit 200 has completed activation. By configuring it in this way, the gaming machine 10 can send messages without determining the status of the rental unit 200, thereby reducing the program capacity required to determine the status of the rental unit 200.

FIG. 34 is a time chart illustrating an example 2 of the startup sequence of the gaming machine 10 and the rental unit 200, showing the case where the rental unit 200 starts up first.
When the power of the gaming machine 10 is turned off and only the power of the rental unit 200 is turned on, only the rental unit 200 starts to start up. While the rental unit 200 is starting up, the VL signal and the PSI signal are off.
Then, when the startup of the rental unit 200 is completed, the VL signal and PSI signal of the rental unit 200 are turned on.

FIG. 34 shows an example in which the power supply of the gaming machine 10 is turned on after the VL signal and PSI signal of the lending unit 200 are turned on.
Then, when the start-up of the gaming machine 10 is completed, the VL signal and PSI signal of both the gaming machine 10 and the lending unit 200 are turned on, and the operation of the bet switch 40 and the operation of the counting switch 47 of the gaming machine 10 become valid.

33, the gaming machine 10 transmits the first message, i.e., a gaming machine information notification, to the rental unit 200 in accordance with the message notification program, and then transmits a counting notification 100 ms after transmitting the gaming machine information notification. At this point, the startup of the rental unit 200 is complete, so the rental unit 200 can receive the first gaming machine information notification and counting notification.
When the rental unit 200 receives the counting notification, it transmits a rental notification to the gaming machine 10 within 170 ms. Furthermore, when the gaming machine 10 receives the rental notification, it transmits a rental receipt result response to the rental unit 200 within 10 ms.
In this way, if the rental unit 200 has already completed startup when the gaming machine 10 has completed startup, the rental unit 200 can receive the first message (gaming machine information notification with serial number "0") sent from the gaming machine 10.

FIG. 35 is a time chart illustrating the basic sequence of gaming machine information notification.
In FIG. 35, after the start-up of the gaming machine 10 is completed, the first gaming machine information notification is referred to as "A0", and subsequent gaming machine information notifications are referred to as "A1", "A2", . . .
Similarly, the counting notifications are referred to as "B0", "B1", "B2", ..., the loan notifications are referred to as "C0", "C1", "C2", ..., and the loan receipt result responses are referred to as "D0", "D1", "D2", ....
As shown in FIG. 32, the gaming machine 10 transmits a gaming machine information notification to the rental unit 200 every "300" ms.
Here, as shown in FIG.
(1) Gaming machine performance information: every 180 seconds (second priority)
(2) Gaming machine installation information: every 60 seconds (first priority)
(3) Hall control/fraud monitoring information: A gaming machine information notification including information on any one of the gaming machines is transmitted every 300 ms.

In principle, hall control and fraud monitoring information is transmitted every 300 ms, but if the transmission cycle overlaps with the transmission cycle of gaming machine installation information, which is transmitted every 60 seconds, but does not overlap with the transmission cycle of gaming machine performance information, which is transmitted every 180 seconds, the gaming machine installation information is transmitted first at that transmission timing, and the hall control and fraud monitoring information is transmitted at the next transmission timing (300 ms later) after the transmission of the gaming machine installation information.
In Figure 35, after the gaming machine 10 is started, the 200th gaming machine information notification (in the figure, "A199") is sent 60 seconds after the first gaming machine information notification is sent (300 ms x 200 = 60,000 ms).
Therefore, at the timing of transmitting the gaming machine information notification "A199", the gaming machine information notification including the gaming machine installation information is transmitted in priority over the hall control and fraud monitoring information. Then, at the timing of transmitting the gaming machine information notification "A200" 300 ms after the transmission of the gaming machine information notification "A199", the gaming machine information notification including the hall control and fraud monitoring information is transmitted.

Furthermore, if the transmission period overlaps with the 60-second transmission period of gaming machine installation information and the 180-second transmission period of gaming machine performance information, the gaming machine installation information is transmitted as the first priority, and the gaming machine performance information is transmitted as the second priority in the next transmission period (300 ms after the transmission of the gaming machine installation information). Furthermore, the hall control and fraud monitoring information is transmitted in the next transmission period (300 ms after the transmission of the gaming machine performance information).
35, the timing of transmission of the gaming machine information notification "A599" is when "60" seconds have elapsed and when "180" seconds have elapsed from the time of transmission of the first gaming machine information notification (300 ms x 600 = 180,000 ms). Note that "180" seconds always corresponds to "60" seconds.

Therefore, when the gaming machine information notification "A599" is sent, gaming machine installation information is sent as the first priority. Furthermore, when the gaming machine information notification "A600" is sent 300 ms later, gaming machine performance information is sent as the second priority. Furthermore, when the gaming machine information notification "A601" is sent 300 ms later, hall control and fraud monitoring information is sent.

When sending a gaming machine information notification, gaming machine information (hall control/fraud monitoring information, gaming machine installation information, gaming machine performance information) is obtained (read from RWM, ROM, etc.), stored in a transmission register, and transmitted from a specified output port.
Therefore, the latest information immediately before transmission is transmitted for hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information.
Among the gaming machine information notifications, the gaming machine installation information is the main control chip ID number, etc., and is therefore fixed information that does not change over time (as the game progresses).
On the other hand, the hall control/fraud monitoring information includes the number of game media, the number of inserted game media, the number of awarded game media, etc., as shown in FIG. 31, and therefore is information that changes as the game progresses (as time passes).

When the transmission cycles for gaming machine installation information, gaming machine performance information, and hall control/fraud monitoring information all overlap, the information is transmitted in the following order of priority: gaming machine installation information, gaming machine performance information, hall control/fraud monitoring information. Therefore, the transmission of hall control/fraud monitoring information will be delayed by up to 600 ms from the time the transmission cycle for gaming machine information notifications (300 ms) arrives.

In this case, if hall control and fraud monitoring information is obtained at the time when the gaming machine installation information is transmitted, and the hall control and fraud monitoring information is transmitted 600 ms after the time when the gaming machine installation information is transmitted (after the gaming machine installation information is transmitted and after the gaming machine performance information is transmitted), the hall control and fraud monitoring information from 600 ms ago will be transmitted.
Therefore, when transmitting the hole control/falsehood monitoring information, the hole control/falsehood monitoring information is acquired and stored in a transmission register immediately before the actual transmission.

The same applies when the transmission cycles of the gaming machine installation information and the hall control/fraud monitoring information overlap. In this case, the hall control/fraud monitoring information is transmitted 300 ms after the transmission cycle (300 ms) of the gaming machine information notification arrives.
Here, if the hall control and fraud monitoring information is obtained at the time when the gaming machine installation information is transmitted, and the hall control and fraud monitoring information is transmitted 300 ms after the time when the gaming machine installation information is transmitted, the hall control and fraud monitoring information from 300 ms ago will be transmitted.
Therefore, when transmitting the hole control/falsehood monitoring information, the hole control/falsehood monitoring information is acquired and stored in a transmission register immediately before the actual transmission.

Furthermore, as shown in FIG. 31, the gaming machine performance information includes the total number of coins inserted, the total number of coins awarded, MY, etc., and therefore changes as the game progresses (as time passes).
When the transmission cycles of the gaming machine installation information and the gaming machine performance information overlap, the gaming machine installation information is transmitted in priority to the gaming machine performance information, and the gaming machine performance information is transmitted 300 ms after the transmission cycle (300 ms) of the gaming machine information notification arrives.
In this case, if gaming machine performance information is obtained at the time of transmitting the gaming machine installation information, and the gaming machine performance information is transmitted 300 ms after the time of transmitting the gaming machine installation information, gaming machine performance information from 300 ms ago will be transmitted.
Therefore, when transmitting gaming machine performance information, the gaming machine performance information is acquired immediately before the actual transmission and stored in a transmission register.
In other words, when the gaming machine information notification is sent every 300 ms, only the gaming machine information (either hall control/fraud monitoring information, gaming machine installation information, or gaming machine performance information) of the gaming machine information notification sent in this interrupt processing is stored in the sending register.

FIG. 36 is a time chart illustrating the count notification sequence.
When the player ends the game, for example, and the counting switch 47 is operated, a process is executed to transmit (return, return) the gaming medium on the gaming machine 10 side to the rental unit 200.
Note that the counting process does not actually transmit or transfer the gaming media data from the gaming machine 10 to the lending unit 200, but rather performs a subtraction process of the number of gaming media stored in the gaming media number storage means 103a of the gaming machine 10, and performs an addition process of the number of gaming media stored in the lendable gaming media number storage means 206 of the lending unit 200.
In the example of Figure 36, the situation before accepting operation of the counting switch 47 is that the (total) number of gaming media stored in the gaming media number control board 100 (gaming media number storage means 103a) is "200", and the number of gaming media available for lending stored in the lending unit 200 is "20".

When the startup of the gaming machine 10 and the rental unit 200 is complete and communication between the gaming machine 10 and the rental unit 200 is possible, the serial number of the gaming machine information notification is assumed to be "n" at the timing when the first gaming machine information notification is sent to the rental unit 200 after detecting the operation (on) of the counting switch 47. Also, since the number of gaming media stored in the gaming media count control board 100 at this point is "200", the number of gaming media "200" is sent to the rental unit 200.
Furthermore, the gaming machine 10 updates the counting notification to the rental unit 200. The counting serial number of the counting notification at this time is assumed to be "m." The number of counted gaming media in the counting notification at this time is assumed to be "50." In this example, when operation of the counting switch 47 is detected, the number of counted gaming media "50" is transmitted in one counting notification.

Furthermore, if this counting process is the first counting process since the gaming machine 10 has been started up, the gaming machine 10 transmits a counting notification indicating a cumulative counted number of gaming media of "50." The gaming machine 10 subtracts the number of counted gaming media from the number of gaming media before transmitting the counting notification. Therefore, before transmitting the counting notification, the number of gaming media stored in the gaming media number control board 100 is updated from "200" to "150." Furthermore, upon receiving the counting notification, the lending unit 200 adds the counted gaming media to the number of lendable gaming media stored in the lendable gaming media number storage means 206 of the lending unit 200. Therefore, in the example of FIG. 36, the number of lendable gaming media is updated from "20" to "70."
Next, the lending unit 200 transmits a lending notification to the gaming machine 10. The lending serial number of this lending notification is assumed to be "k." The number of lending game media in this lending notification is also "0." Here, the reason for transmitting the number of lending game media "0" is because the lending switch 202 has not been operated.

Furthermore, when the gaming machine 10 receives a rental notice from the rental unit 200, it checks the consistency between the information indicated in the rental notice and the information indicated in the previous rental notice.
Then, after checking the consistency between the information indicated in the loan notification and the information indicated in the previous loan notification, if it is determined that the information is normal, the gaming machine 10 sends a loan receipt result response to the loan unit 200 indicating that the loan serial number is "k" and the loan point receipt result is "normal."

When transmitting the gaming machine information notification for the next serial number "n+1", the serial number "n+1" and the number of gaming media "150" are transmitted.
36 shows an example in which the counting switch 47 remains on (the counting switch 47 is pressed and held down) even after 300 ms have elapsed since the gaming machine information notification for serial number "n" was sent, and the next gaming machine information notification for serial number "n+1" is sent. Therefore, the counting notification transmits the counting serial number "m+1," the number of counted gaming media "50," and the cumulative number of counted gaming media "100." As a result, the number of available gaming media for lending on the lending unit 200 side is updated to "120."
Furthermore, the lending unit 200 transmits the lending serial number "k+1" and the number of lending gaming media "0" to the gaming machine 10 as a lending notification. Furthermore, upon receiving the lending notification, the gaming machine 10 transmits the lending serial number "k+1" and the lending point receipt result "normal" to the lending unit 200 as a lending receipt result response.

In this way, when gaming media are stored in the gaming machine 10, from the time when the counting switch 47 is detected to be on until it is detected to be off (while the counting switch 47 is being pressed and held), the gaming machine 10 continues to send a counting notification including a predetermined number of counted gaming media to the lending unit 200 every 300 ms. By configuring in this way, a fixed amount (50 in this example) of counted gaming media can be sent to the lending unit 200 every 300 ms without requiring complicated operations (simply pressing and holding the switch), thereby reducing the burden of the counting operation.
Since the counting switch 47 is connected to the game media count control board 100, the input port 101 is checked for each interrupt process of the game media count control board 100, and if information indicating ON has been input to the input port 101 indicating the counting switch 47, the counting switch 47 is accepted for operation. If information indicating OFF has subsequently been input to the input port 101 indicating the counting switch 47, the acceptance of operation of the counting switch 47 is terminated.

The example in Figure 36 shows an example in which the counting switch 47 is detected as being off after the gaming machine information notification for serial number "n+1" is sent and before the gaming machine information notification for serial number "n+2" is sent.
In this case, when transmitting a gaming machine information notification with serial number "n+2", the gaming machine 10 transmits the number of gaming media "100".
Furthermore, as a counting notification, the counting serial number "m+2", the number of counted gaming media "0", and the cumulative number of counted gaming media "100" are transmitted. Furthermore, as a lending notification from the lending unit 200 to the gaming machine 10, the lending serial number "k+2" and the number of lending gaming media "0" are transmitted to the gaming machine 10. Furthermore, as a lending receipt result response from the gaming machine 10 to the lending unit 200, the lending serial number "k+2" and the lending point receipt result "normal" are transmitted.

The counting notification is transmitted 100 ms after the transmission of the gaming machine information notification. In other words, the counting notification is transmitted every 300 ms. Therefore, even when the counting switch 47 is not operated, a counting notification in which the number of counted gaming media is 0 is transmitted every 300 ms.
In addition, when no gaming media are stored in the gaming media number storage means 103a of the gaming machine 10, even if the counting switch 47 is operated, a counting notification indicating that the number of counted gaming media is "0" is sent every "300" ms.

Next, the counting process will be described using a flowchart.
FIG. 37 is a flowchart showing the counting process in the second embodiment.
Although not shown in FIG. 29, the RWM 103 of the game media count control board 100 has the following storage areas.
The counting flag (_FL_CAL_EXE) is a storage area that stores data indicating whether or not counting is in progress.
The count value storage area (_CT_CAL_VAL) is a storage area for storing the count value (number of counted gaming media) to be transmitted when counting is notified.
The count accumulation value storage area (_CT_CAL_ALL) is a storage area for storing the count accumulation value (count accumulation number of gaming media).
The counting serial number storage area (_NB_CAL_NUM) is a storage area for storing the counting serial number.
In the case of a gaming machine that does not have the gaming media count control board 100, the RWM 53 of the main control board 50 may be provided with each of the above memory areas.

First, in step S701, it is determined whether or not it is the count notification timing. Here, the "count notification timing" refers to the timing after "100" ms has elapsed since the gaming machine information notification was transmitted. Note that "100" ms may be within the range of "90" ms to "100" ms.
If it is determined that it is the timing for counting notification, the process proceeds to step S702, and if it is determined that it is not the timing for counting notification, the process according to this flowchart ends.

When it is determined that it is time to notify the count, and the process proceeds to step S702, the game media count control board 100 clears the counting flag (to "0"). Next, the process proceeds to step S703, where it is determined whether or not to execute counting. Here, it is determined whether or not the counting switch 47 has been operated.
When the counting switch 47 is operated, a counting switch signal is turned on and input to the input port 101 of the game media count control board 100. When the counting switch signal is turned on and input to the input port 101, information indicating that the counting switch signal has been turned on and input (the counting switch 47 has been operated) ("1" if operated, "0" if not operated) is stored in a predetermined storage area within the RWM 103 of the game media count control board 100. The signal input to the input port 101 is stored in the RWM 103 by a timer interrupt process every 1 ms.
If it is determined in step S703 that the counting switch 47 has been operated, the process proceeds to step S704, and if it is determined that the counting switch 47 has not been operated, the process proceeds to step S712.

In step S704, it is determined whether the (total) number of game media stored in the game media number storage means 103a of the game media number control board 100 is "0." If it is determined that the number of game media is not "0," the process proceeds to step S705; if it is determined that the number is "0," the process proceeds to step S712.
In this way, it is first determined whether or not the counting switch 47 has been operated, and if the counting switch 47 has not been operated, the counting process is not started, and if the counting switch 47 has been operated, it is determined whether or not the (total) number of game media stored in the game medium number storage means 103a is "0." Then, if the (total) number of game media stored in the game medium number storage means 103a is "0," the counting process is not started, and if the (total) number of game media is not "0," the counting process is started.
As a result, when comparing a situation in which the counting switch 47 is operated with a situation in which the (total) number of game media stored in the game media number storage means 103a is "0", the number of situations in which the counting switch 47 is operated is relatively less, so by first determining whether the counting switch 47 is operated or not, it is possible to reduce the processing burden in the counting process.

In step S705, the count value (number of counted game media) is set to "50".
Next, the process proceeds to step S706, where an arithmetic operation (subtraction operation) is performed to compare the number of game media stored in the game media number storage means 103a with the count value "50." If the result of this arithmetic operation is that the number of game media stored in the game media number storage means 103a is equal to or greater than the count value, the process proceeds to step S708, and if the result is that the number of game media stored in the game media number storage means 103a is less than the count value, the process proceeds to step S707.
In step S707, the number of game media stored in the game media number storage means 103a is obtained.
In the next step S708, the count value is stored. In this process, if the determination in step S706 is "Yes" (the number of gaming media is determined to be equal to or greater than the count value), the count value "50" set in step S705 is stored in the count value storage area. On the other hand, if the determination in step S706 is "No" (the number of gaming media is less than the count value), the number of gaming media stored in the gaming medium number storage means 103a obtained in step S707 is stored as the count value in the count value storage area.

In the next step S709, the (total) number of game media stored in the game media number storage means 103a is updated. This process subtracts the count value saved in the count value storage area from the number of game media stored in the game media number storage means 103a. Therefore, if it is determined that the number of game media stored in the game media number storage means 103a is equal to or greater than "50" and "50" is stored in the count value storage area, "50" is subtracted from the number of game media stored in the game media number storage means 103a to update the number of game media. On the other hand, if the number of game media stored in the game media number storage means 103a is less than "50" and the number of game media stored in the game media number storage means 103a is stored in the count value storage area, the number of game media stored in the game media number storage means 103a is updated to "0."
Next, the process proceeds to step S710, where the count value stored in the count value storage area is added to the count cumulative value storage area to update the value stored in the count cumulative value storage area.
Next, the process proceeds to step S711, where it has been decided that counting will be performed, and the counting flag is set ("FFh" is stored).

Then, the process proceeds to step S712 and outputs the count notification. Specifically, "0x07h" is output as the message length, "0x02h" is output as the command, the count serial number stored in the count serial number storage area is output as the count serial number, the count value stored in the count value storage area is output as the count value, the count cumulative value stored in the count cumulative value storage area is output as the count cumulative value, and the checksum value (1 byte) of the various output data is output.
Thereafter, the process proceeds to step S713, where the count value stored in the count value storage area is cleared. Note that the value stored in the count cumulative value storage area is not cleared when the count notification is output (or has been output).

Next, proceed to step S714, where the process of updating the count serial number (the process of adding "+1") is executed. Note that when the count serial number is "255(D)," the result of adding "+1" is "0," so if it becomes "0," the process of updating the count serial number (the process of adding "+1") is executed again. In other words, when the count serial number is "255," the process of updating the count serial number is executed twice, updating the count serial number to "1." Furthermore, when the count serial number is a value less than "255" (for example, "10"), the result of executing the process of updating the count serial number (the process of adding "+1") does not become "0," so the process of updating the count serial number is executed only once. In the above example, the count serial number is updated to "11."

In addition, information based on the counting flag is sent to the main control board 50. This allows the main control board 50 to determine that counting is in progress. Furthermore, for example, by sending information indicating that counting is in progress from the main control board 50 to the sub-control board 80, the sub-control board 80 can perform a performance corresponding to the counting in progress.

In this embodiment, counting based on the operation of the counting switch 47 is possible even during the setting change mode or the setting confirmation mode.
However, when the counting switch 47 is operated under circumstances where gaming media can be bet, an effect based on the operation of the counting switch 47 is executed, but when the counting switch 47 is operated during the setting change mode or the setting confirmation mode, it is possible not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during the setting change mode or the setting confirmation mode, it is highly likely that a hall staff member is counting (and not a player).

On the other hand, if the counting switch 47 is operated during setting change mode or setting confirmation mode, a dedicated screen for setting change mode or setting confirmation mode may be displayed on the image display device 23, or a sound may be output. In this way, necessary information can be provided to the hall staff. Furthermore, while a dedicated screen for setting change mode or setting confirmation mode is displayed, a notification indicating that counting is in progress (for example, "Counting in progress" may be displayed on the screen) may be made. In this case, the notification is configured to be different from the counting effect (for the player) described above. Such a notification can be used to draw attention.

Furthermore, in this embodiment, even during an error (which may be a predetermined (predetermined) portion of the error or all errors), counting based on operation of the counting switch 47 is possible.
However, when the counting switch 47 is operated under the circumstances where gaming media can be bet, an effect based on the operation of the counting switch 47 is executed, but when the counting switch 47 is operated during an error, it is possible not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during an error, there is a risk that fraudulent activity is being committed.
Errors include unrecoverable errors (for example, errors that require resetting of set values (including turning the power on and off), such as RWM abnormality errors and random number update errors) and recoverable errors (for example, a front door open error), but it is also possible to provide situations in which counting processing is impossible and situations in which it is possible, depending on the type of error. For example, counting processing can be made impossible when an unrecoverable error occurs, and made possible when a recoverable error occurs.

On the other hand, if the counting switch 47 is operated during an error, a dedicated screen for the error may be displayed on the image display device 23, or a sound may be output. In this way, necessary information can be provided to the hall staff. Furthermore, while the dedicated screen for the error is displayed, a notification indicating that counting is in progress (for example, "Counting in progress" may be displayed on the screen) may be made. In this case, the notification is configured to be different from the presentation during counting (for the player) described above. Such a notification can be used to draw attention. Note that at this time, the system may be configured so that the number of bets cannot be returned using the settlement switch 46.

In addition, in this embodiment, counting based on the operation of the counting switch 47 is possible even during a game (for example, while the reel 31 is spinning).
However, when the counting switch 47 is operated under circumstances where gaming media can be bet, an effect based on the operation of the counting switch 47 is executed, but when the counting switch 47 is operated during a game, it may be configured not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during a game, there is a risk that fraudulent activity is being committed.

FIG. 38 is a time chart illustrating the lending notification sequence between the gaming machine 10 and the lending unit 200.
38, the situation before the on-state of the lending switch 202 is detected (before the operation of the lending switch 202 is accepted) is that the number of game media stored in the game media number storage means 103a of the game media number control board 100 is "10," and the number of game media available for lending "120" is stored in the number of game media available for lending storage means 206 of the lending unit 200. Note that, since the number of game media stored in the game media number storage means 103a of the game media number control board 100 is less than "50," the count will be "10" when the counting switch 47 is operated.

This shows an example in which the gaming machine 10 and the rental unit 200 have completed startup and are able to communicate with each other, and after detecting that the rental switch 202 of the rental unit 200 has been turned on (after accepting the operation), the gaming machine 10 sends a gaming machine information notification with serial number "n" and number of gaming media "10".
Next, the counting notification is sent with the counting serial number "m" and the number of counted game media "0". After receiving this counting notification, the lending notification is sent with the lending serial number "k" and the number of lending game media "50". After sending the number of lending game media "50", the lending unit 200 updates the number of lendable game media to "120-50=70". Note that the timing when the lending unit 200 updates the number of lendable game media may be when it receives the lending receipt result response.

When the gaming machine 10 receives a loan notification, it checks the consistency between the information indicated in the loan notification and the information indicated in the previous loan notification, and if the check result is normal (assuming it is normal in this example), it sends the loan serial number "k" and the loan point receipt result "normal" to the loan unit 200 as a loan receipt result response.
Next, the gaming machine 10 updates the number of gaming media to "10+50=60" during the period from when it receives the rental notification to when it transmits the rental receipt result response.
When the gaming machine 10 next transmits a gaming machine information notification to the rental unit 200, it transmits the serial number "n+1" and the number of gaming media "60" as the gaming machine information notification to the rental unit 200. Furthermore, it transmits the counting serial number "m+1", the number of counted gaming media "0", and the cumulative number of counted gaming media "0" as the counting notification.

At this point, if the on state of the rental switch 202 of the rental unit 200 is continuously detected, the rental unit 200 transmits the rental serial number "k+1" and the number of rental game media "50" to the gaming machine 10 as a rental notification to the gaming machine 10 ("*1" in the figure). The number of rental game media available for rental is then updated to "70-50=20". Furthermore, the gaming machine 10 transmits the rental serial number "k+1" and the rental point receipt result "normal" (assuming the check result was normal) as a rental receipt result response to the rental unit 200. The gaming machine 10 also updates the number of game media to "60+50=110" between receiving the rental notification and transmitting the rental receipt result response.
On the other hand, if the rental switch 202 is detected as off at the time when the rental unit 200 sends a rental notification for rental serial number "k+1" to the gaming machine 10, a rental notification indicating the number of rental game media "0" is sent to the gaming machine 10 ("*2" in the figure). In this case, the number of rental game media remains "70". The number of game media in the gaming machine 10 also remains "60".

The lending unit 200 may detect when the lending switch 202 has changed from off to on by determining whether the level data of the lending switch 202 is on/off each time a lending notification is sent (i.e., every 300 ms). In contrast, in this embodiment, the on/off state of the rising edge data of the lending switch 202 is determined each time a lending notification is sent. Therefore, in this case, even if the lending switch 202 is continuously on, the lending operation will only be accepted at the timing of the first operation. Therefore, even if the lending switch 202 is continuously on, the number of lending media sent when the second or subsequent lending notifications are sent will be set to "0". Therefore, in the example of Figure 38, even if the lending switch 202 is continuously detected as being on at the timing when the lending notification for lending serial number "k+1" is sent, a lending notification with the number of lending media "0" is sent to the gaming machine 10.

Furthermore, when the number of counted game media in the counting notification sent from the gaming machine 10 upon detecting that the lending switch 202 is turned on is "1" or greater (i.e., when both the lending switch 202 and the counting switch 47 are operated), the lending unit 200 sets the number of loaned game media in the lending notification sent immediately after the counting notification to "0." The lending switch 202 accepted at this time may be invalidated, or the lending unit 200 may store an operation acceptance flag for the lending switch 202 and send the number of loaned game media as "50" in the lending notification sent after the number of counted game media in the counting notification has become "0."
Furthermore, when the lending unit 200 stores an operation acceptance flag for the lending switch 202, if the lending switch 202 is operated again while a flag relating to operation acceptance for the lending switch 202 is stored, the flag may be rewritten to a flag indicating that the lending switch 202 has been operated twice, or the second and subsequent operations may be invalidated.

Furthermore, when the lending unit 200 transmits a lending notification to the gaming machine 10 and the gaming machine 10 receives the lending notification, all information in the lending notification is stored in a lending notification information storage area provided in the RWM 103 of the gaming media count control board 100. This allows the gaming machine 10 to determine whether the information on the lending point receipt result is "normal" or "abnormal" when transmitting a lending receipt result response.
Specifically, "k" is stored as the lending serial number in the lending notification information storage area, and if the lending serial number in the lending notification sent from the lending unit 200 is "k+1", the stored "k" is incremented to generate "k+1" and compared with the received lending serial number "k+1". In this case, since the generated lending serial number matches the received lending serial number, the received lending serial number "k+1" is stored in the lending notification information storage area.

In addition, if "k" is stored as the lending serial number in the lending notification information storage area and the lending serial number in the lending notification sent from the lending unit 200 is "k+2", the stored "k" is incremented to generate "k+1" and compared with the received lending serial number "k+2".In this case, since the generated lending serial number does not match the received lending serial number, the received lending serial number "k+2" is not stored (the lending serial number in the lending notification information storage area remains "k").
Furthermore, since the upper limit of the rental serial number is "255," if the rental serial number is incremented when it is "255," the rental serial number becomes "0." However, since the rental serial number "0" can only be sent to the gaming machine 10 immediately after the rental unit 200 is started, the rental serial number is incremented again to become "1." In other words, when updating the rental serial number when it is "255," the next rental serial number is made "1" by incrementing it twice.

In the above example, the method for comparing the rental serial number stored in the gaming machine 10 with the rental serial number in the received rental notification is to increment the rental serial number stored in the gaming machine 10 and then determine whether it matches the rental serial number received from the rental unit 200. However, this is not limiting, and it is also possible to decrement the rental serial number received from the rental unit 200 and then compare whether it matches the rental serial number stored in the gaming machine 10.
Alternatively, the rental serial number stored in the gaming machine 10 may be subtracted from the rental serial number received from the rental unit 200, and the determination may be made based on whether the result is "1".

Next, a timer for transmitting a gaming machine information notification (hereinafter referred to as a "gaming machine information notification timer") will be described.
FIG. 39 is a diagram showing the gaming machine information notification timer and the gaming machine information notification request flag.
The gaming machine information notification timer includes a gaming machine information notification timer A (_TM_INF_CTL_A), a gaming machine information notification timer B (_TM_INF_CTL_B), and a gaming machine information notification timer C (_TM_INF_CTL_C).
The gaming machine information notification timer A is a timer for determining the timing to transmit hall control and fraud monitoring information every 300 ms.
The gaming machine information notification timer B is a timer for determining the timing to transmit the gaming machine installation information every "60" seconds.
The gaming machine information notification timer C is a timer for determining the timing to transmit gaming machine performance information every "180" seconds.

The RWM 103 of the game media count control board 100 is provided with memory areas for game machine information notification timers A to C, and timer values are stored in each memory area.
The memory area of gaming machine information notification timer A is "2" bytes, and gaming machine information notification timers B and C are "1" byte.
Each storage area of the gaming machine information notification timers A to C is initialized (cleared and stores "0") when the power is turned on.
As mentioned above, the blinking switching period of the role ratio monitor 113 is "300" ms, and RWM 103 has a "blinking switching time (_TM_CHG_FLS)" as a timer area that manages the blinking switching time, and further has a "blinking switching flag (_FL_CHG_FLS)" as a flag that determines whether the light is on or off.
On the other hand, although the gaming machine information notification timer A measures "300" ms, which is the same as the blinking switching period, it is in a timer area separate from the blinking switching time.

In the following explanation, the memory areas of gaming machine information notification timer A, gaming machine information notification timer B, and gaming machine information notification timer C will be abbreviated as gaming machine information notification timer A, gaming machine information notification timer B, and gaming machine information notification timer C, respectively.
Furthermore, the values stored in the memory areas of gaming machine information notification timer A, gaming machine information notification timer B, and gaming machine information notification timer C will be abbreviated as the values of gaming machine information notification timer A, gaming machine information notification timer B, and gaming machine information notification timer C, respectively.

In the second embodiment, the CPU 105 of the game media count control board 100 executes a timer interrupt process every 1 ms. Each time this timer interrupt is executed (every 1 ms), the value of the game machine information notification timer A is updated.
The gaming machine information notification timer A is a decrement timer, and as described above, when the power is turned on, the value stored therein is "0." The value of the gaming machine information notification timer A cycles between "0" and "300(D)."
Therefore, the value of the gaming machine information notification timer A is set to "0" when the power is turned on, and is updated to "300" when the first timer interrupt is executed, and is further updated to "299" when the next timer interrupt is executed.
Furthermore, when "1" is subtracted during interrupt processing in a situation where the value before the update is "0", such as when the power is turned on, the value is updated to "300", and when "1" is subtracted during the next interrupt processing, the value is updated to "299".
In contrast, in an interrupt process in which the value before updating is "1", if "1" is subtracted, the subtraction result becomes "0", but in this case "300" is immediately stored in the interrupt process.
therefore,
"0" → "300" → "299" → ... → "2" → "1" → ("0" →) "300" → "299" → ...
It will be updated as follows.

The gaming machine information notification timer B is an increment timer, and as described above, when the power is turned on, the value "0" is stored. The value of the gaming machine information notification timer B cycles within the range of "0" to "199(D)".
therefore,
"0" → "1" → "2" → ... → "198" → "199" → "0" → "1" → ...
It will be updated as follows.
The value of gaming machine information notification timer B is incremented by "1" when the value of gaming machine information notification timer A reaches "300." However, when the power is turned on, the value of gaming machine information notification timer A is initialized to "0" and, when the value of gaming machine information notification timer A reaches "300" in the first timer interrupt process, the value of gaming machine information notification timer B is not updated and remains at "0." This control will be described later.

The gaming machine information notification timer C is an increment timer, and as described above, when the power is turned on, the value "0" is stored. The value of the gaming machine information notification timer C cycles within the range of "0" to "2(D)."
therefore,
"0" → "1" → "2" → "0" → "1" → ...
It will be updated as follows.
The value of gaming machine information notification timer C is incremented by "1" when the value of gaming machine information notification timer B becomes "0." However, when the value of gaming machine information notification timer B is initialized to "0" when the power is turned on, the value of gaming machine information notification timer C also remains at the initialized "0" and is not updated to "1" at this point.

The gaming machine information notification request flag (_FL_INF_CTL) is a flag indicating whether it is the timing to notify gaming machine performance information (every 180 seconds) or not, and whether it is the timing to notify gaming machine installation information (every 60 seconds), and is provided as a 1-byte memory area in RWM 103 of the gaming media number control board 100.
The gaming machine information notification request flag is initialized to an initial value (all bits "0") by initialization processing when the power is turned on.
The gaming machine information notification request flags include a gaming machine performance information notification request flag and a gaming machine installation information notification request flag.

The gaming machine performance information notification request flag is a flag that changes from "0" to "1" when the period (timing) for transmitting gaming machine performance information among the gaming machine information notifications arrives, and uses the "D0" bit of the gaming machine information notification request flag. When the "D0" bit is "1", it indicates that the period for transmitting gaming machine performance information has arrived, and when it is "0", it indicates that the period for transmitting gaming machine performance information has not arrived. Furthermore, when a gaming machine performance information notification is transmitted, it is updated from "1" to "0".
Furthermore, the gaming machine installation information notification request flag is a flag that changes from "0" to "1" when the period (timing) for transmitting gaming machine installation information among the gaming machine information notifications arrives, and uses the "D1" bit of the gaming machine information notification request flag. When the "D0" bit is "1", it indicates that the period for transmitting gaming machine installation information has arrived, and when it is "0", it indicates that the period for transmitting gaming machine installation information has not arrived. Furthermore, when a gaming machine installation information notification is transmitted, it is updated from "1" to "0".
It is also possible to use a 1-byte storage area for the gaming machine performance information notification request flag and another 1-byte storage area for the gaming machine installation information notification request flag. However, if the gaming machine information notification request flag is provided as a 1-byte storage area as in this embodiment and the gaming machine performance information notification request flag and the gaming machine installation information notification request flag are assigned to bits of this 1-byte storage area, the storage capacity can be reduced.

FIG. 40 is a time chart showing the update sequence of the values of the gaming machine information notification timers A, B, and C.
In Figure 40, a gaming machine information notification including hall control and fraud monitoring information based on the value of gaming machine information notification timer A is referred to as "Notification A," a gaming machine information notification including gaming machine installation information based on the value of gaming machine information notification timer B is referred to as "Notification B," and a gaming machine information notification including gaming machine performance information based on the value of gaming machine information notification timer C is referred to as "Notification C."
First, when the power of the gaming machine 10 is turned on, an initialization process of the RWM 103 of the gaming media number control board 100 is executed, thereby clearing the values of the gaming machine information notification timers A, B, and C ("0" is stored).

The CPU 105 of the game media count control board 100 has a flag register (F register). The flag register has a carry flag (CY) and a zero flag (Z). The flag register also has flags other than these flags, but the description of these flags will be omitted in this embodiment.
The carry flag is a flag that becomes "1" when the result of the arithmetic operation is less than "0", in other words, when a borrow occurs.
The zero flag is a flag that becomes "1" when the result of the calculation process becomes "0".

Specific examples of the carry flag and the zero flag are as follows:
Example 1) When the value of gaming machine information notification timer A is "10" and "1" is subtracted, the value of gaming machine information notification timer A is updated to "9". At this time, the zero flag and carry flag do not change (they remain "0").
Example 2) When the value of gaming machine information notification timer A is "1" and is decremented by "1", the value of gaming machine information notification timer A is updated to "0". As a result, the zero flag becomes "1". On the other hand, the carry flag does not change (it remains at "0"). Here, in the calculation process of this embodiment, when the value of gaming machine information notification timer A is updated from "1" to "0" and the zero flag becomes "1", it is updated to "300" immediately thereafter (during the interrupt processing in which it was updated to "0" as a result of decrementing "1").

Example 3) When the value of gaming machine information notification timer A is "0" and "1" is subtracted, the value of gaming machine information notification timer A is updated to "300". At this time, the zero flag does not change (it remains "0"). Meanwhile, the carry flag becomes "1".
The value of the gaming machine information notification timer A before subtraction is "0" only when it is initialized after power-on. Therefore, the carry flag becomes "1" when the value of the gaming machine information notification timer A is updated from "0" to "300" in the first interrupt process after power-on.

When the value of gaming machine information notification timer A is updated and either the carry flag or the zero flag becomes "1," it is determined that the time to send notification A has arrived. This enables the gaming machine 10 to send notification A to the rental unit 200. Figure 40 shows that after gaming machine information notification timer A is initialized to "0" when the power is turned on, the value of gaming machine information notification timer A is updated from "0" to "300" by the first interrupt processing, and notification A is sent when the carry flag (CY) becomes "1" ("*1" in the figure).

Next, an interrupt is executed every 1 ms, and the value of gaming machine information notification timer A is updated to 299, 298, ..., but unless either the carry flag or the zero flag becomes 1, it is not determined that the timing to send notification A has arrived, so notification A is not sent. Since 60 seconds and 180 seconds are also multiples of 300 ms, naturally notification B and notification C are not sent either.
As mentioned above, the carry flag becomes "1" only during the first interrupt processing after power-on due to an update of the value of the gaming machine information notification timer A, but thereafter the carry flag does not become "1" due to an update of the value of the gaming machine information notification timer A.

When the number of interrupts reaches 300 (i.e., 300 ms have passed since the first notification A was sent ("*1" in the figure), the value of gaming machine information notification timer A is updated from 1 to 0 (and then updated to 300), and the zero flag (Z) becomes 1. Therefore, it is determined that the time to send notification A has arrived. As a result, the gaming machine 10 sends notification A to the rental unit 200 ("*2" in the figure).

Next, when the number of interrupts reaches 6000 since the first notification A was sent ("*1" in the figure), that is, when 60 seconds have passed, the timer value etc. is updated as follows:
First, the value of the gaming machine information notification timer A is updated from "1" to "0" (and further updated to "300"), and the zero flag (Z) becomes "1"("*3" in the figure). Therefore, it is determined that the timing for sending notification A has arrived.
Second, the gaming machine information notification timer B is updated from "199" to "0." When the value of the gaming machine information notification timer B is updated to "0," it is determined that the timing for sending notification B has arrived, and the gaming machine installation information notification request flag (D1 bit) is updated to "1."

At this point, the timing for sending notification A has arrived, and the timing for sending notification B has also arrived. Therefore, notification B is sent at this timing because it takes priority over notification A (in the figure, "*4"). When notification B is sent, the gaming machine installation information notification request flag (D1 bit) is updated to "0."
Then, after 300 ms has elapsed from that timing, the value of gaming machine information notification timer A is updated again from 1 to 0 (and further updated to 300), and the zero flag (Z) becomes 1. Based on the fact that the zero flag (Z) has become 1, it is determined that the timing for sending notification A has arrived, and notification A is sent (in the figure, "*5").

In this way, when the transmission of notification B is given priority at the transmission timing of "*3" in the figure, notification A is not transmitted at that timing, and notification A is transmitted at the timing of "*5" after "300" ms have elapsed from that timing.
Here, when notification A is sent at the timing of "*5" in the figure, the hall control/fraud monitoring information acquired immediately before the transmission is stored in a designated transmission register, and a gaming machine information notification including the hall control/fraud monitoring information is sent.
In other words, the hole control/fraud monitoring information is not acquired at the transmission timing of "*3" in the figure, stored in a designated transmission register, and then the hole control/fraud monitoring information is not transmitted at the timing of "*5" in the figure.

If it is determined that notification A will not be sent at the transmission timing of "*3" in the diagram, the hole control and fraud monitoring information at that time may be configured not to be stored in the designated transmission register. However, to simplify processing, when the transmission timing for notification A arrives, the hole control and fraud monitoring information at that time is uniformly stored in the designated transmission register. Then, every "300" ms, in other words, every time the zero flag (Z) becomes "1", the hole control and fraud monitoring information at that time is stored (overwritten) in the designated transmission register.

Next, when the number of interrupts reaches 18,000 since the first notification A was sent ("*1" in the figure), that is, when 180 seconds have passed, the timer values etc. are updated as follows:
First, the value of the gaming machine information notification timer A is updated from "1" to "0" (and further updated to "300"), and the zero flag (Z) becomes "1"("*6" in the figure). Based on the fact that the zero flag (Z) has become "1", it is determined that the timing for sending notification A has arrived.

Second, the gaming machine information notification timer B is updated from "199" to "0." When the value of the gaming machine information notification timer B is updated to "0," it is determined that the timing for sending notification B has arrived, and the gaming machine installation information notification request flag (D1 bit) is updated to "1"("*7" in the figure).
Third, the gaming machine information notification timer C is updated from "2" to "0." When the value of the gaming machine information notification timer C is updated to "0," it is determined that the timing for sending notification C has arrived, and the gaming machine performance information notification request flag (D0 bit) is updated to "1"("*8" in the figure).

At this point, the timing for sending notification A has arrived, the timing for sending notification B has arrived, and the timing for sending notification C has arrived. Therefore, the timing for sending notifications A, B, and C all overlap. In this case, notification B has the highest priority, so it is sent at this timing ("*7" in the diagram). In other words, notifications A and C will not be sent at this timing. When notification B is sent, the gaming machine installation information notification request flag (D1 bit) is updated to "0." Note that notification C has not been sent at this point, so the gaming machine performance information notification request flag (D0 bit) remains at "1."

When 300 ms have elapsed since this timing and the timing for transmitting the gaming machine information notification has arrived, the value of gaming machine information notification timer A is updated from 1 to 0 (and further updated to 300), and the zero flag (Z) becomes 1 (in the figure, "*9"). Based on the fact that the zero flag (Z) has become 1, it is determined that the timing for transmitting notification A has arrived.
Also, at this timing, the gaming machine performance information notification request flag (D0 bit) is "1". Therefore, the timing for sending notification C has arrived. When the timing for sending notification A and notification C overlap, notification C takes priority, so notification C is sent ("*10" in the figure). In other words, notification A will not be sent at this timing. When notification C is sent, the gaming machine performance information notification request flag (D0 bit) is updated to "0".

After 300 ms have elapsed from this point, the value of gaming machine information notification timer A is updated from 1 to 0 (and further updated to 300), and the zero flag (Z) becomes 1 (denoted by *11 in the diagram). Based on the zero flag (Z) becoming 1, it is determined that the timing for sending notification A has arrived. Furthermore, at this point, the gaming machine installation information notification request flag (bit D1) and the gaming machine performance information notification request flag (bit D0) are both 0, so it is neither the time to send notification B nor the time to send notification C. Therefore, notification A is sent at this timing (denoted by *11 in the diagram).

When Notification A is sent at "*11" in the diagram, the hall control and fraud monitoring information acquired immediately prior to that transmission is stored in a designated transmission register, and a gaming machine information notification containing that hall control and fraud monitoring information is sent. In other words, it is not the hall control and fraud monitoring information acquired at "*6" or "*9" in the diagram.

As described above, when either the carry flag or the zero flag becomes "1", it is determined that the timing for sending notification A has arrived.
Therefore, this is different from the control in the above-mentioned role ratio monitor 113, which switches between lighting and extinguishing when the carry flag becomes "0" as a result of updating the blinking switching time.

FIG. 41 is a flowchart showing gaming machine information management.
Here, "gaming machine information management" refers to a control process for transmitting a gaming machine information notification from the gaming machine 10 to the rental unit 200. The process of Fig. 41 is one subroutine in the timer interrupt process executed by the gaming media count control board 100. In other words, gaming machine information management is executed each time the timer interrupt process is executed (at a cycle of "1" ms).
First, in step S721, "1" is subtracted from gaming machine information notification timer A (gaming machine information notification timer A is updated). Next, the process proceeds to step S722, where it is determined whether the value of gaming machine information notification timer A before the update is "0." If the carry flag becomes "1" in the subtraction process of step S721, it is determined that the value of gaming machine information notification timer A before the update is "0." Note that the carry flag becoming "1" because the value of gaming machine information notification timer A before the update was "0" corresponds to the case where the value of gaming machine information notification timer A was set to "0" (initialized) when the power was turned on and then "1" was subtracted. If it is determined that the value of gaming machine information notification timer A before the update is "0," the process proceeds to step S733; if it is determined that the value is not "0," the process proceeds to step S723.

In step S723, it is determined whether the value of gaming machine information notification timer A before the update is "1." In other words, it is determined whether the value of gaming machine information notification timer A has become "0" as a result of the update, or in other words, whether the zero flag has become "1" as a result of the update. If it is determined that the value of gaming machine information notification timer A before the update is "1," the process proceeds to step S724, and if it is determined that the value is not "0," the process according to this flowchart is terminated.
When the value of gaming machine information notification timer A before updating is "1", it means that it is the timing of a "300" ms cycle, that is, the timing to send a gaming machine information notification including hall control and fraud monitoring information.

On the other hand, when it is not the timing to send notification A, it is not a timing with a 300 ms cycle, so it is not a timing with a 60-second cycle, and it is not a timing with a 180-second cycle. In other words, it is not the timing to send a gaming machine information notification including gaming machine installation information, nor is it the timing to send gaming machine installation information including gaming machine performance information. Therefore, when it is determined that it is not the timing to send gaming machine installation information including hall control and fraud monitoring information, gaming machine information management is terminated without determining whether it is the timing to send a gaming machine information notification including gaming machine installation information or whether it is the timing to send gaming machine installation information including gaming machine performance information. This simplifies program processing and speeds up gaming machine information management.

In step S724, an initial value is saved in the value of gaming machine information notification timer A. Here, the initial value is "300(D)." In this embodiment, the timer interrupt period of the gaming media count control board 100 is "1" ms, so by storing "300(D)" as the value of gaming machine information notification timer A, it is possible to count "300" ms. Therefore, when the calculation result becomes "0" after the subtraction in step S721, "300" is immediately saved in step S724.
For example, if the timer interrupt period of the game media count control board 100 is "2" ms, then "150(D)" should be stored in the game machine information notification timer A.
Furthermore, for example, if the timer interrupt period of the gaming media count control board 100 is set to "2.235" ms, any value in the range of "135" to "138" can be stored in the gaming machine information notification timer A. In this way, if the "gaming machine information notification transmission period/timer interrupt period" is not an integer (cannot be divided), any value that makes the gaming machine information notification transmission timing between "300" ms and "310" ms can be set as the initial value.

An example of the calculation instruction in step S721 described above is the DCPWLD instruction. The DCPWLD instruction is an instruction to store a predetermined value when the carry flag becomes "1" as a result of subtracting "1". In this embodiment, the predetermined value is "300". Therefore, after power is turned on, the gaming machine information notification timer A is initialized to "0", and then in the gaming machine information management process in the first interrupt process, when "1" is subtracted in step S721, the carry flag becomes "1" and the predetermined value "300" is stored.
In this way, the initialization process when the power is turned on sets the value of the gaming machine information notification timer A to "0", but otherwise, the value of the gaming machine information notification timer A will never become "0" (except in the event of an abnormality) except for the period after processing step S721 and before processing step S724.

In the next step S725, a process is executed to increment the value of gaming machine information notification timer B by "1." A special increment command is used for this increment process. Specifically, if a value less than "199" is stored in gaming machine information notification timer B, "1" is added to the value of gaming machine information notification timer B; if the value of gaming machine information notification timer B is not less than "199" (i.e., if "199" is stored under normal operating conditions), "0" is stored in gaming machine information notification timer B.

Specific examples are as follows:
Example 1) When "0" is stored in gaming machine information notification timer B, when an arithmetic process is performed using a special addition instruction to add "1", the value becomes "1".
Example 2) If "100" is stored in gaming machine information notification timer B, when an arithmetic process is performed using a special addition instruction to add "1", gaming machine information notification timer B becomes "101".
Example 3) When "199" is stored in gaming machine information notification timer B, if a calculation process is performed using a special addition instruction that adds "1", the value of gaming machine information notification timer B will become "0" instead of "200". For example, this corresponds to the calculation at the timing of "*4" in Figure 40 mentioned above.

In this way, by performing calculation processing using a special addition instruction that adds "1" to gaming machine information notification timer B, the value of gaming machine information notification timer B can be cycled between "0" and "199".
Furthermore, the situation in which "1" is added when "199" is stored in gaming machine information notification timer B corresponds to the situation in which the gaming machine information notification timer A has reached "0" 200 times. In other words, since gaming machine information notification timer B is incremented by "1" every time the interrupt process is executed 300 times, this is a situation in which the interrupt process has been executed 300 times x 200 times = 60,000 times (60 seconds have passed).

Normally, a memory area of 2 bytes would be required to measure whether or not the interrupt process has been executed 60,000 times. However, by updating the gaming machine information notification timer B based on the value of the gaming machine information notification timer A, the memory area of the gaming machine information notification timer B can be reduced to 1 byte, thereby reducing the memory capacity of the RWM 103.
Furthermore, an example of an arithmetic instruction for adding "1" to the gaming machine information notification timer B is the ICPLD instruction.
In the above example, an instruction to add "1" to gaming machine information notification timer B is executed, but an instruction to subtract "1" may also be executed. In the case of a subtraction instruction, "200" may be stored as an initial value in gaming machine information notification timer B when the power is turned on, and "200" may be stored when the value later becomes "0". Alternatively, "199" may be stored as an initial value in gaming machine information notification timer B when the power is turned on, and "200" may be stored when the carry flag later becomes "1".

In addition, because gaming machine information notification timer B is updated using an addition command, the process of setting the initial value can be omitted compared to when a subtraction command is used (the initial value is set to "0" during initialization processing when the power is turned on), which improves processing speed and reduces program size.

In step S726, it is determined whether or not the time on the gaming machine information notification timer B has elapsed. Here, when the value of the gaming machine information notification timer B becomes "0" by adding "1", it is determined that the time on the gaming machine information notification timer B has elapsed. On the other hand, when the value of the gaming machine information notification timer B does not become "0" by adding "1", it is determined that the time on the gaming machine information notification timer B has not elapsed.
If it is determined that the time set by the gaming machine information notification timer B has elapsed, the process proceeds to step S727, and if it is determined that the time has not elapsed, the process proceeds to step S731.
In step S727, a process of adding "1" to the gaming machine information notification timer C is executed.
A special addition instruction is used for the addition process here. Specifically, when a value less than "2" is stored in gaming machine information notification timer B, "1" is added to the value of gaming machine information notification timer C, and when the value of gaming machine information notification timer C is not less than "2" (i.e., when "3" is stored under normal operating conditions), "0" is stored in gaming machine information notification timer C.

Specific examples are as follows:
Example 1) When "0" is stored in gaming machine information notification timer C, when an arithmetic process is performed using a special addition instruction to add "1", the value becomes "1".
Example 2) If "1" is stored in gaming machine information notification timer C, when an arithmetic process is performed using a special addition instruction that adds "1", gaming machine information notification timer C becomes "2".
Example 3) When "2" is stored in gaming machine information notification timer C, if a calculation process is performed using a special addition instruction that adds "1", the value of gaming machine information notification timer B will become "0" instead of "3". For example, this corresponds to the calculation at the timing of "*8" in Figure 40 mentioned above.

In this way, by performing calculation processing using a special addition instruction that adds "1" to the gaming machine information notification timer C, the value of the gaming machine information notification timer C can be cycled between "0" and "2".
Furthermore, the situation in which "1" is added when "2" is stored in gaming machine information notification timer C corresponds to the situation in which the trigger for gaming machine information notification timer B to become "0" has occurred "three" times. In other words, gaming machine information notification timer B is incremented by "1" every time the interrupt process is executed "300" times, and gaming machine information notification timer C is incremented by "1" every time gaming machine information notification timer B is updated "200" times, so this is a situation in which the interrupt process has been executed "300 times x 200 times x 3 times = 180,000 times" (180 seconds have passed).

Normally, a memory area of 3 bytes would be required to measure whether or not the interrupt process has been executed 180,000 times, but since the value of gaming machine information notification timer B is updated based on the value of gaming machine information notification timer A, and the value of gaming machine information notification timer C is further updated based on the value of gaming machine information notification timer B, the memory area of gaming machine information notification timer C can be 1 byte, thereby reducing the memory capacity of RWM103.
Furthermore, an example of an arithmetic instruction for adding "1" to the gaming machine information notification timer C is the above-mentioned ICPLD instruction.
In the above example, an instruction to add "1" to the gaming machine information notification timer C is executed, but a subtraction instruction may also be executed. In the case of a subtraction instruction, an initial value of "3" may be stored as the value of the gaming machine information notification timer C when the power is turned on, and "3" may be stored when the value later becomes "0". Alternatively, an initial value of "2" may be stored as the value of the gaming machine information notification timer C when the power is turned on, and "3" may be stored when the carry flag later becomes "1".

However, if the gaming machine information notification timer C is updated with an addition command, as in this embodiment, the process of setting the initial value can be omitted compared to when a subtraction command is used (the initial value is set to "0" by the initialization process when the power is turned on), which allows for improved processing speed and reduced program capacity.

In step S728, it is determined whether or not the time has elapsed on the gaming machine information notification timer C. Here, when the value of the gaming machine information notification timer C becomes "0" by adding "1", it is determined that the time on the gaming machine information notification timer C has elapsed. On the other hand, when the value of the gaming machine information notification timer C does not become "0" by adding "1", it is determined that the time on the gaming machine information notification timer C has not elapsed.
If it is determined that the time set by the gaming machine information notification timer C has elapsed, the process proceeds to step S729, and if it is determined that the time has not elapsed, the process proceeds to step S730.

Note that step S727 is executed only when step S726 returns "Yes." This is because gaming machine information notification timer C is updated only when gaming machine information notification timer B reaches "0." Furthermore, the next step, S728, determines whether gaming machine information notification timer C has elapsed only when step S726 returns "Yes." Whether gaming machine information notification timer C has elapsed depends on whether a 180-second cycle has arrived, and a 180-second cycle always occurs when a 60-second cycle has arrived (the time on gaming machine information notification timer B has elapsed).

In step S729, a gaming machine performance information notification request flag is set. This process stores "1" in the "D0" bit of the gaming machine information notification request flag. In the next step S730, a gaming machine installation information notification request flag is set. This process stores "1" in the "D1" bit of the gaming machine information notification request flag.
That is, when it is determined that the time of the gaming machine information notification timer C has elapsed, a period of 180 seconds has arrived, and since a period of 180 seconds includes a period of 60 seconds, the timing for notifying the gaming machine performance information and the timing for notifying the gaming machine installation information have arrived. Therefore, both the "D0" and "D1" bits of the gaming machine information notification request flag are set to "1."

In contrast, if it is determined in step S726 that the time set by gaming machine information notification timer B has elapsed, and it is determined that the time set by gaming machine information notification timer C has not elapsed, then the 60-second cycle (the timing for notifying gaming machine installation information) has arrived, but the 180-second cycle (the timing for notifying gaming machine performance information) has not yet arrived. Therefore, in this case, the processing of step S729 is not executed, and only the processing of step S730 is executed, setting only the "D1" bit of the gaming machine information notification request flag to "1."

In this way, the timing for transmitting gaming machine installation information and the timing for transmitting gaming machine performance information are managed using flags, which simplifies the process of transmitting hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information. In other words, by linking the timers corresponding to each type of information, transmission is possible without the need for individual management. Furthermore, there is no discrepancy in the start timing of the timers used to transmit hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information, allowing for accurate transmission.

In the next step S731, it is determined whether or not there is a request for notification of gaming machine installation information. Here, it is determined whether or not the gaming machine installation information notification request flag is set. Therefore, if the "D1" bit of the gaming machine information notification request flag is "1", it is determined that there is a request for notification of gaming machine installation information, and if the "D1" bit of the gaming machine information notification request flag is not "1", it is determined that there is no request for notification of gaming machine installation information.
If it is determined that there is a request for notification of gaming machine installation information, the process proceeds to step S734, and if it is determined that there is no request for notification of gaming machine installation information, the process proceeds to step S732.
In step S732, it is determined whether or not there is a request for notification of gaming machine performance information. Here, it is determined whether or not the gaming machine performance information notification request flag is set. Therefore, if the "D0" bit of the gaming machine information notification request flag is "1", it is determined that there is a request for notification of gaming machine performance information, and if the "D0" bit of the gaming machine information notification request flag is not "1", it is determined that there is no request for notification of gaming machine performance information.
If it is determined that there is a request for notification of gaming machine performance information, the process proceeds to step S736, and if it is determined that there is no request for notification of gaming machine performance information, the process proceeds to step S733.

In step S733, the process of transmitting the hole control and fraud monitoring information is executed. Here, the hole control and fraud monitoring information stored in the RWM 103 of the game media count control board 100 is acquired, the information is stored in the transmission register, and the information is transmitted. After transmission, the process according to this flowchart is terminated.
In step S722, if it is determined that the pre-update value of gaming machine information notification timer A is "0," the transmission process of the hall control/fraud monitoring information is executed without determining whether the time of gaming machine information notification timer B or gaming machine information notification timer C has elapsed (the processing of step S726 or step S728). The reason for this is that the pre-update value of gaming machine information notification timer A is "0" only during the subtraction process in the first interrupt processing immediately after power-on. In other words, it is impossible for "60" or "180" seconds to have elapsed during the subtraction process in the first interrupt processing immediately after power-on. In such a case, the transmission process of the hall control/fraud monitoring information is executed without determining whether the time of gaming machine information notification timer B or gaming machine information notification timer C has elapsed, thereby enabling faster processing (faster transmission processing).

In addition, in step S731, it is determined whether or not there is a request for notification of gaming machine installation information. If it is determined that there is no request for notification of gaming machine installation information, the processing proceeds to step S732, where it is determined whether or not there is a request for notification of gaming machine performance information. By using this processing order, in a situation where both the gaming machine installation information notification request flag and the gaming machine performance information notification request flag are set (a situation where the 180-second cycle has arrived), it is first determined whether or not there is a request for notification of gaming machine installation information, so that the processing for transmitting the gaming machine installation information can be executed (given priority) before the processing for transmitting the gaming machine performance information.

Furthermore, as described above, when the hole control and fraud monitoring information is transmitted in step S733, the latest information at that time is transmitted.
For example, the (total) number of gaming media included in the hall control/fraud monitoring information is transmitted as the information stored in the gaming medium number storage means 103a (_NB_MEDAL) at the time of transmission. In other words, if the transmission timing of the hall control/fraud monitoring information, which is the transmission timing every "300" ms, overlaps with the transmission timing of gaming machine installation information or gaming machine performance information, the transmission of the gaming machine installation information and gaming machine performance information takes priority, so the hall control/fraud monitoring information is not transmitted at that timing, and the hall control/fraud monitoring information is transmitted after the next "300" ms has elapsed (if it overlaps with the transmission timing of the gaming machine installation information) or after "600" ms has elapsed (if it overlaps with the transmission timing of the gaming machine installation information and gaming machine performance information). This "hall control/fraud monitoring information to be transmitted after 300 ms or 600 ms" is not the hall control/fraud monitoring information at the time when it overlaps with the timing of transmitting the gaming machine installation information, but the hall control/fraud monitoring information obtained at the time when the hall control/fraud monitoring information is transmitted after 300 ms or 600 ms. Therefore, even if the timing of transmitting the hall control/fraud monitoring information is delayed, it is possible to transmit the latest information.

Furthermore, after the transmission process for hall control and fraud monitoring information is completed, the serial number is updated (incremented by "1"). Like counting serial numbers, this serial number is transmitted as "0" when transmitting immediately after power is restored, and is updated thereafter so that any value between "1" and "255" can be transmitted (by cycling through "1" and "255"). This serial number is updated when any of the following three pieces of information is transmitted: hall control and fraud monitoring information, gaming machine installation information, and gaming machine performance information. In other words, because the same serial number is used for hall control and fraud monitoring information, gaming machine installation information, and gaming machine performance information, the serial number is configured to be updated every 300 ms while the power is on.

When the process proceeds from step S731 to step S734, a transmission process of gaming machine installation information is executed. The content to be transmitted at this time is the information stored in the gaming media count control board 100 that was acquired at this timing. Next, the process proceeds to step S735, where the gaming machine installation information notification request flag is cleared. Specifically, the "D1" bit of the gaming machine information notification request flag is set to "0." Furthermore, after the transmission process of the gaming machine installation information is completed, the serial number is updated ("1" is added). Then, the process according to this flowchart ends.
On the other hand, when the process proceeds from step S732 to step S736, a transmission process of gaming machine performance information is executed. The content to be transmitted at this time is the information stored in the gaming media count control board 100 that was acquired at this timing. Next, the process proceeds to step S735, where the gaming machine performance information notification request flag is cleared. Specifically, the "D0" bit of the gaming machine information notification request flag is set to "0." Furthermore, after the transmission process of gaming machine performance information is completed, the serial number is updated ("1" is added). Then, the process according to this flowchart ends.

Next, the relationship between the gaming machine information notification timers A to C and the information stored in the RWM 53 of the main control board 50 will be described.
As described above, the memory areas of the gaming machine information notification timers A to C are provided in the RWM 103 of the gaming media count control board 100. These memory areas are cleared ("0" is stored) by the initialization process when the power is turned on.
On the other hand, in the RWM 103 of the game medium number control board 100, in addition to the data storage areas described above, the following data storage areas are provided as data storage areas necessary for controlling the lighting of the role ratio monitor 113.
"400" game number counter (counter for counting "400" games)
Total award number ring buffer "0" to "14" (each a buffer that counts the total award number between "400" games)
Consecutive feature award number ring buffer "0" to "14" (each a buffer that counts the number of consecutive feature awards between "400" games)
Ring buffer for number of games awarded "0" to "14" (each a buffer that counts the number of games awarded between "400")
Total number of games played counter (storage area for the count value of the total number of games played)
Counter for number of games played in advantageous zone (storage area for number of games played in advantageous zone)
Total number of grants counter (storage area for the count value of the total number of grants)
Instruction count counter (storage area for the number of instructions given when the instruction function is activated)
Consecutive feature grant number counter (storage area for the number of grants when continuous features are activated)
Number of bonuses given counter (storage area for the number of bonuses given when bonuses are activated)
Indication-included role ratio data (storage area for calculated instruction-included role ratio)
Advantageous zone ratio data (storage area for calculated advantageous zone ratio)
Continuous feature ratio data (calculated continuous feature ratio storage area)
Feature ratio data (calculated feature ratio storage area)
Reel state ratio data (storage area for calculated reel state ratio)
Blinking switching time (storage area for count value related to blinking switching time) (described above)
Flashing switch flag (storage area for flag to determine whether the light is on or off) (described above)
The above data storage area is a part of the data storage area required for lighting control of the role ratio monitor 113, and is not limited to the above.

Of the above storage areas, the ring buffer, game count counter, award counter, and ratio data storage areas are not initialized by turning the power on/off or changing the settings. This is because even if the power is turned on/off or the settings are changed, the correct ratio is displayed, reflecting the past game history.
However, if an unrecoverable error such as an RWM abnormal error occurs, all of the above storage areas are initialized to prevent any invalid data from remaining after recovery.
On the other hand, the blinking switching time and blinking switching flag are initialized (cleared) when the power is turned on/off or when the settings are changed. This allows the test pattern to be displayed for 4800 ms each time the power is turned on. Also, even if blinking is performed after power is turned on, it can start from the first 3 seconds of lighting.

In addition to the bet number storage means 53a and the award number storage means 53b shown in FIG. 29, the RWM 53 of the main control board 50 is provided with storage areas for the following data, for example.
Input port level data (storage area for data that determines whether each switch is in an operating state)
Input port rising edge data (storage area for data to determine whether each switch has been operated)
Section type number (storage area for numbers to manage advantageous sections)
MY counter (storage area for difference number)
Winning and replay condition device number (storage area for the winning and replay condition device numbers that operate in the game)
Device condition number (storage area for the number of the device condition that operates in the game)
Minimum play period (storage area for timer value to monitor the minimum play period (4.1 seconds) of one game)
Game standby display time (storage area for the timer value that measures the time until transition to game standby)
The above data storage area is a part of the data storage area of the RWM 53, and is not limited to the above.

Furthermore, since the gaming machine 10 of the second embodiment is a medal-less gaming machine, it does not have the following memory areas, for example, which are provided in gaming machines that use medals as tangible objects.
Blocker signal (blocker on/off storage area)
Hopper motor drive signal (hopper motor on/off storage area)
Payout sensor check time (storage area for timer value to detect medal jams)
Blocker monitoring time (storage area for the timer value indicating the waiting time for the blocker to turn on/off)
Medal payout control time (storage area for timer values indicating the control time of the medal payout device)

In the memory area of the RWM 53, for example, the minimum play time is not initialized by turning the power on or off. Therefore, if the power is turned off during the measurement of the initial play time, the measurement of the minimum play time is resumed when the power is turned on thereafter, and when it is determined that the minimum play time has elapsed, the start of play (the start of rotation of the reels 31) is permitted.
Therefore, the minimum playing time and gaming machine information notification timers A to C are common in that they both store timer values for measuring time, but differ in whether they are initialized by turning the power on/off.

Although the second embodiment of the present invention has been described above, the present invention is not limited to the above-described content, and various modifications such as those described below are possible.
(1) In the second embodiment, the gaming machine 10 and the rental unit 200 are capable of communicating with each other via the game media count control board 100 and the connection terminal board 130, but this is not limiting. The main control board 50 and the connection terminal board 130 may be connected, and the gaming machine 10 and the rental unit 200 may be capable of communicating with each other via the main control board 50 and the connection terminal board 130. If the above configuration is adopted and the game media count control board 100 is not installed, production costs can be reduced.
In this case, all of the processing controlled by the game media count control board 100 will be performed by the main control board 50. Furthermore, when the functions of the main control board 50 and the game media count control board 100 are realized on the same board, it is possible to realize processing similar to that of the above-described embodiment by separately providing a CPU 55 that controls the functions of the main control board 50 and a CPU 105 that controls the functions of the game media count control board 100.

(2) In the above embodiment, gaming machine installation information transmitted every 60 seconds was given first priority, followed by gaming machine performance information transmitted every 180 seconds. However, this is merely an example, and for example, if there is gaming machine information notification 1 transmitted every T1 seconds and gaming machine information notification 2 transmitted every T2 seconds (T2 > T1), gaming machine information notification 2 may be transmitted with priority over gaming machine information notification 1.

(3) The storage areas of the RWM 53 of the main control board 50 and the RWM 103 of the game media count control board 100 are generally divided into an in-use area and an outside-use area.
Here, "within the area in use" refers to an area in the memory area of the RWM for storing data related to the progress of the game.
On the other hand, "outside the area in use" refers to an area in the memory area of the RWM for storing data that is not related to the progress of the game.
Therefore, since data relating to the display control of the role ratio monitor 113 is data that is not related to the progress of the game, it is generally stored outside the area used by the RWM.
For example, when the main control board 50 executes display control of the role ratio monitor, data related to the display control of the role ratio monitor is stored outside the use area of the RWM 53. This makes it possible to reduce the storage capacity within the use area of the RWM 53.

However, not limited to this, when the display control of the role ratio monitor 113 is performed by the gaming medium number control board 100, since there is little risk that the data related to the display control of the role ratio monitor 113 will put a strain on the memory capacity in the usage area of the RWM 103, it is also possible to provide a data memory area related to the display control of the role ratio monitor 113 within the usage area of the RWM 103.
(4) In the above embodiment, a slot machine (a reel-type gaming machine) was used as an example of the gaming machine 10, but the present invention is not limited to this and can be applied to various gaming machines such as casino machines.

Third Embodiment
The third embodiment relates to the structure and instructions of the main CPU 55. In the third embodiment, the RWM 53, the ROM 54, and the main CPU 55 are provided on the main control board 50, as in the first embodiment.
42 is a diagram showing the built-in memory of the main CPU 55 in the third embodiment. In the diagram, (A) is a diagram showing an overview of the built-in memory, and (B) is a diagram showing the built-in register area of the storage area in the built-in memory. In FIG. 42, only the part of the built-in memory that is related to this embodiment is shown, and not the entire built-in memory.
Within the areas of ROM 54, the first program area and the first data area correspond to areas within the usage area (areas for storing programs and data related to the progress of the game), and the second program area and the second data area correspond to areas outside the usage area (areas for storing programs and data not related to the progress of the game. For example, areas for storing programs and data related to the display control of the role ratio monitor, and programs and data related to the output control of the test signal).
The "program area" is also called the "control area."

The ROM 54 has an address range of 0000h to 2FFFh and a storage area of 12K bytes. Within this storage area, the first program area is set to 4.5K bytes, and the first data area is set to 3.0K bytes.
Furthermore, in the RWM 53, the first working area and the first stack area are storage areas used (updated, referenced) during the execution of a first program (a program related to the progress of a game) stored in the first program area. Similarly, the second working area and the second stack area are storage areas used (updated, referenced) during the execution of a second program (a program not related to the progress of a game, for example, a program related to the display of a winning ratio monitor) stored in the second program area.
Furthermore, the first program stored in the first program area cannot update the data in the second work area and the second stack area, but can refer to the data in the second work area and the second stack area.
Similarly, the second program stored in the second program area cannot update the data in the first working area and the first stack area, but can refer to the data in the first working area and the first stack area.

The internal register area (synonymous with the internal register area) includes register bank 0 and register bank 1. Each register bank includes a main register (front register) and a sub-register (back register). The main register includes a general-purpose register.
In the following description, the sub-registers will be omitted, and the term "register" will refer to the main register.

The registers in register bank 0 are used when executing a program stored in the first program area. Similarly, the registers in register bank 1 are used when executing a program stored in the second program area. For example, the A register, F register, etc. are each provided in both register bank 0 and register bank 1. In other words, the A register in register bank 0 and the A register in register bank 1 are different registers.

The A register is an accumulator.
The F register is a flag register, the structure of which will be described later.
The B, C, D, E, H, and L registers are general purpose registers.
The IX and IY registers are index registers, and are used, for example, when specifying an address.
The SP register is a stack pointer register that specifies the address to which data is saved when data is saved to the stack area, and also specifies the address from which data is restored when data is restored from the stack area.
Specifically, the SP register of register bank 0 specifies an address in the first stack area (ranging from "F1D0h" to "F1FFh"). Similarly, the SP register of register bank 1 specifies an address in the second stack area (ranging from "F3E8h" to "F3FFh").

In addition to register banks 0 and 1, there are I, R, PC, and IFF registers.
The I register is an interrupt register and is used when executing interrupt processing.
The R register is a refresh register and is used to refresh the RWM 53 .
The PC register is a program counter, which holds the address of the currently executing program in memory.

The IFF register is an interrupt enable register. The IFF register consists of an IFF1 register that determines whether a maskable interrupt (INT) is enabled or disabled, and an IFF2 register that restores IFF1 after processing a non-maskable interrupt (NMI). In addition to restoring from non-maskable interrupt processing, the IFF2 register is also used for restoring by a RETEX instruction (described later) after executing a CALLEX instruction (described later).
Furthermore, when a non-markable interrupt is accepted or when the CALLEX instruction is executed, the IFF1 register is cleared (set to a value ("0") that prohibits interrupt processing), maskable interrupts are prohibited, and the IFF2 register holds the state at that time (whether the interrupts were in the interrupt disabled state or interrupt enabled state when the non-markable interrupt was accepted or the CALLEX instruction was executed). Furthermore, when the RET instruction or RETEX instruction is executed, the value of the IFF2 register is moved to the IFF1 register, and the maskable interrupt acceptance state is restored to the previous state.

Figure 43 shows the detailed configuration of the F register. The F register consists of one byte (8 bits, shown as "D0" to "D7" in the figure). The structure of the F register is as follows:
(1) D0 bit: Carry flag (C)
The carry flag is a flag that becomes "1" if a carry or borrow occurs as a result of the operation, and becomes "0" if no carry or borrow occurs.
(2) D1 bit: Subtraction flag (N)
The subtraction flag is also called a subtract flag, and is a flag that is set to "1" if the immediately preceding instruction is a subtraction instruction, and is set to "0" if it is not a subtraction instruction.

(3) D2 bit: Parity/Overflow Flag (P/V)
The parity/overflow flag is a flag that becomes "1" if the number of "1" bits (parity) in the calculation result is even, and becomes "0" if it is odd. Also, this flag becomes "1" if an overflow occurs as a result of the calculation, and becomes "0" if no overflow occurs.
(4) D3 bit: Register bank monitor (RB)
The register bank monitor is a flag that is set to "0" when register bank 0 is in use and to "1" when register bank 1 is in use. Therefore, by referencing the D3 bit of the F register, it is possible to determine whether register bank 0 or 1 is in use.

(5) D4 bit: Half carry flag (H)
The half carry flag is a flag that becomes "1" when there is a carry from the lower 4 bits to the upper 4 bits during an operation, and becomes "0" when there is no carry.
(6) D5 bit: Second Zero Flag (TZ)
The second zero flag is a flag that becomes "1" when the operation result is "0" and becomes "0" if the operation result is not "0".
(7) D6 bit: Zero flag (Z)
As in the above, the zero flag is a flag that becomes "1" when the operation result is "0" and becomes "0" if the operation result is not "0".
(8) D7 bit: Sign flag (S)
The sign flag is a flag that becomes "0" if the calculation result is positive, and becomes "1" if the calculation result is negative.

Fig. 44 is a diagram showing stack areas in the third embodiment. As shown in Fig. 42, the RWM 53 has a first stack area ("F1D0h" to "F1FFh") for the first program and a second stack area ("F3E8h" to "F3FFh") for the second program.
As described above, when storing (also referred to as piling, saving, stacking, etc.) data in the first stack area, the data is piled in ascending (reverse) order from the last address. For example, when first piling two bytes of data in the first stack area, the data is stored at "F1FFh" and "F1FEh."
The same applies to the second stack area, with data being stacked in order from the final address (F3FFh).

The SP register stores a value indicating which address in the stack area data will be stored at. As shown in Figure 42, SP registers are provided in both register banks 0 and 1, and the SP register in register bank 0 stores which address in the first stack area data will be stored at. Similarly, the SP register in register bank 1 stores which address in the second stack area data will be stored at.

As shown in FIG. 44, when power is turned on, the SP register of register bank 0 stores the initial value "F200h" in accordance with the instruction "LD SP, F200h."
Next, when some program (such as a CALL instruction (also referred to as a "first call instruction"), a CALLEX instruction (also referred to as a "second call instruction"), or a PUSH instruction (also referred to as a "register save instruction")) is executed and data is stored in the two-byte area of "F1FFh" and "F1FEh" in the first stack area, the SP register value of register bank 0 is updated to "F1FEh". Note that the example in FIG. 44 shows an example in which "CALL mn" is executed.
Next, when calling the data stored in "F1FFh" and "F1FEh" of the first stack area, some program (such as a RET instruction (also referred to as the "first return instruction"), a RETEX instruction (also referred to as the "second return instruction"), or a POP instruction (also referred to as the "register restore instruction")) is executed. Then, this instruction calls the data stored in the 2-byte storage area of "F1FEh" and "F1FFh". For example, the RET instruction (example in FIG. 44) returns to the instruction after CALL (returns to the program of the program counter saved in the stack area (returns to the program at the return address)), and the SP register value of register bank 0 is updated from "F1FEh" to "F200h".

The same applies to the second stack area.
When power is turned on, the SP register of register bank 1 stores the initial value "F400h" in response to the instruction "LD SP, F400h."
Next, when some program (CALL instruction, PUSH instruction, etc.) is executed and data is pushed to "F3FFh" in the second stack area, the SP register value of register bank 1 is updated to "F1FFh".
Next, to call the data stored at "F3FFh" in the second stack area, some program (RET instruction, RETEX instruction, POP instruction, etc.) is executed. Then, the data stored in the 1-byte storage area at "F3FFh" is called by this instruction, and the instruction after the CALL is returned to by the RET instruction or RETEX instruction, and the SP register value of register bank 1 is updated from "F3FFh" to "F400h".

Details of the instruction will be described later, but in this embodiment, the CALLEX instruction is an instruction that is included in the first program (when register bank 0) but is not included in the second program (when register bank 1).
The RETEX instruction is not included in the first program (when register bank 0 is used) but is included in the second program (when register bank 1 is used).

Fig. 45 is a diagram showing main commands in the third embodiment. In the third embodiment, there are several thousand types of commands, but Fig. 45 shows three representative types.
In the figure, (A) indicates an LDF instruction.
In FIG. 45, first, the operation code and operands in the instruction statement will be explained.
As shown in (A) in the figure, when the instruction is "LDF HL, mn," the first half "LDF" is sometimes called the opcode (function), and the second half "HL, mn" is sometimes called the operand (argument). The LDF instruction is a type of LD (load) instruction (a special form; the reason why it is special will be explained later). Furthermore, "HL" indicates the HL register, and "mn" indicates the address. The instruction "LDF HL, mn" is an instruction that instructs storing the value of address "mn" in the HL register.
As will be described later, the LDF instruction is not limited to an instruction to store an address value in a specified register, but may also be an instruction to store a specified value (however, the "specified value" is limited to a specified range (described later)) in a specified register.

Specifically, for example, when "LDF HL, 1200h" is executed,
1200h = 0001/0010/0000/0000 ("/" is inserted every four bits. The same applies below.)
Therefore,
H register value = 0001/0010
L register value = 0000/0000
This becomes:

Furthermore, the LDF instruction is limited to instructions that store values in the range of "1200h" to "1DFF" in a register (the HL register in this example). The opcode for other load instructions is "LD" instead of "LDF".
That is,
LDF HL, mn (mn=1200h~1DFFh)
LD HL, mn (mn≠1200h~1DFFh)
is.

Figure 46 shows the modes of the LDF instruction and the LD instruction. As shown in Figure 42, the range of the first data area is addresses "1200h" to "1DF3h." Therefore, all load instructions that specify an address in the first data area can be executed with the LDF instruction.
In contrast, the second data area is in the address range of "2600h" to "2FBEh." Therefore, in the case of a load instruction that specifies an address in the second data area, the opcode "LDF" cannot be used, and the opcode "LD" is used.
In Figure 46, (A) shows an LDF command that specifies the address range from "1200h" to "1DF3h" (first data area), and (B) shows an LD command that specifies the address range from "2600h" to "2FBEh" (second data area).

Furthermore, the load instruction is not limited to an instruction to store a predetermined address value in a predetermined register, but is also used as an instruction to store, for example, any register value in any other register.
46C shows "LDF HL, xy," an instruction that uses the LDF instruction to store a predetermined value "xy" (within the range of "1200h" to "1DFFh") in the HL register. In this way, when the value of "xy" is within the range of "1200h" to "1DFFh," the LDF instruction can also be used to store the value in a predetermined register.
For example, in the case of an instruction to store the timer value "5000 (D)" (1388h) in the HL register, it would be "LDF HL, 1388h".
46(D) shows "LD A, (HL)," an instruction that uses the LD instruction to store a specified register value (the HL register value in this example) in another specified register (the A register in this example). In an instruction that copies a specified register value to another specified register, if the specified register value or value to be copied is outside the range of "1200h" to "1DFFh," the LD instruction (rather than the LDF instruction) is used.

Also, all instructions such as "LDF HL,mn" and "LD HL,mn" are actually coded and stored in the program area of the ROM 54.
In the third embodiment, the code size of "LDF HL, mn" is 2 bytes, and the code size of "LD HL, mn" is 3 bytes.
First, in the case of the instruction "LDF HL, mn", the range of "mn" is "1200h" to "1DFFh". When "1200h" and "1DFFh" (both in hexadecimal) are expressed in decimal and binary, respectively, they become
1200h=4608(D)=0001/0010/0000/0000(B)
1DFFh=7679(D)=0001/1101/1111/1111(B)
This becomes:

When "1200h" is set as the reference value "0", "1DFFh" becomes "3070(D)" or "1011/1111/1110(B)" (12 bits).
Therefore, in the opcode for specifying the address value in the LDF instruction, "1200h" is set to the value "0." This means that 12 bits are sufficient to specify the address value "mn" (mn = "1200h" to "1DFFh").

Also, assume that the total number of instructions is, for example, "3000," and that a unique value is assigned to each instruction.
in this case,
3000(D) = 1011/1011/1000(B) (12 bits)
Therefore, it can be assigned to "0000/0000/0000(B)" to "1011/1011/1000(B)".
A small value is assigned to a particularly important instruction, specifically, an instruction that is used frequently. In this embodiment, the code value of "LDF HL" is assigned to "1101" (4 bits).
Therefore, "LDF HL" is 4 bits and "mn" is 12 bits, for a total of 16 bits, or 2 bytes. Therefore, the code size of "LDF HL, mn (mn=1200h to 1DFFh)" is 2 bytes.

On the other hand, if the range of "mn" in the load command is outside the range of "1200h" to "1DFFh", particularly if the range of the second data area "2600h" to "2FBEh" is specified, the following occurs:
The largest address value in the range of the second data area is "2FBEh", so
"2FBEh" - "1200h"
= 1 DBEh
=1/1101/1011/1110(B)
This results in 13 bits.
That is, when "1200h" is set as the reference value "0" as described above, "2FBEh" can be expressed in 13 bits.
Therefore, when "LD HL" is coded, it is coded using 4 bits, just like the above "LDF HL," and "LD HL, mn" (mn ≠ 1200h to 1DFFh) is expressed using "4 + 13 = 17 bits (3 bytes)."

Furthermore, in the case of other load instructions such as "LD A, (HL)" mentioned above, the code size is also set to 3 bytes.
If the code size of "LD HL, mn" is 3 bytes, then "LD HL" does not necessarily have to be 4 bits, and if it is 11 bits or less, then "mn" (mn ≠ 1200h to 1DFFh) is 13 bits, so the total can be kept within 24 bits (3 bytes).

From the above, in the third embodiment, the code size of the load instruction is
LDF HL, mn (mn = 1200h to 1DFFh): 2 bytes (16 bits)
LD HL, mn (mn ≠ 1200h to 1DFFh): 3 bytes (17 bits)
LD A, (HL) ("A" and "HL" are optional): 3 bytes.
As a result, the code size of "LDF HL, mn (mn = 1200h to 1DFFh)", which specifies an address in the first data area and stores it in the HL register, is one byte less than the code size of other load instructions, making it possible to save storage capacity in the first program area.

In particular, since the first program area stores programs related to the progress of the game, it is more likely to have a larger capacity than programs stored in the second program area, in other words, programs unrelated to the progress of the game (programs related to the winning combination monitor). For example, the first program executes lottery processing related to the game, processing for transitioning the game state, processing for driving the reels, and processing for awarding game value (game media) according to the game result (the combination of symbols that are stopped and displayed). Therefore, by reducing the code size of the load instructions that call addresses "1200h" to "1DFFh" among the load instructions stored in the first program area, it becomes possible to store more programs in the first program area.
On the other hand, for programs stored in the second program area, the opcodes of load instructions that specify addresses within the second data area are all standardized to "LD." This makes it easier to verify the validity of the program source for programs stored in the second program area. In other words, it becomes possible to design programs that prioritize readability over reducing program capacity (code size).

The data area of ROM 54 referenced by the second program is outside the range of "1200h" to "1DFFh." Therefore, when specifying the address of the data area of ROM 54 referenced by the second program, use "LD HL, mn" (mn ≠ 1200h to 1DFF).

There are multiple LD instructions (an instruction with LD as the opcode, also called the "first load instruction") as instructions that make up the first program, and there are also multiple LDF instructions (an instruction with LDF as the opcode, also called the "second load instruction" or "special load instruction") as instructions that make up the first program, but there are no LDF instructions (an instruction with LDF as the opcode, also called the "second load instruction" or "special load instruction") as instructions that make up the second program.
The LD instruction can also be used to store two bytes of data in the HL register. However, storing two bytes of data in the HL register using the LDF instruction can reduce the code size. However, the LDF instruction has limitations on the range of two bytes of data.

The above-mentioned LDF command and LD command are not commands that are only applicable to various processes in slot machines (for example, reel-type gaming machines under the Entertainment and Amusement Act), but can also be applied without any problems to various general-purpose processes in pachinko gaming machines.
Pachinko gaming machines, like slot machines, are equipped with a first program area and a second program area, with the first program area storing programs related to the progress of the game and the second program area storing programs unrelated to the progress of the game (for example, a program related to a base monitor that displays the base (which normally refers to the value calculated by "number of prize balls paid out / total number of balls dispensed x 100"; the same applies below). For this reason, the first program area tends to be larger in capacity than the second program area. Therefore, a capacity compression effect can be expected by adopting LDF commands in the programs stored in the first program area.

In addition, the programs stored in the first program area of a pachinko gaming machine include, for example, processing related to the lottery for winning or losing, processing related to the control of stopping the variation of special symbols, processing related to the display of special symbols or normal symbols, processing related to the display of game information (game status, error status, base, etc.), processing related to jackpot control, processing related to the movement control of various movable objects (such as a big prize opening or an electric device that activates an opening extension function), processing related to payout control, etc. LDF commands can be used for these programs.
In particular, although there are differences in the process of calculating the display content between the display control of the base monitor of a pachinko gaming machine and the display control of the role ratio monitor of a slot machine, the display control is similar in that the game information is ultimately displayed as data.
It should be noted that, not limited to the above, it is of course possible to use the LDF command in other processes controlled by the main CPU in both slot machines and pachinko games.

Returning to the explanation of FIG.
45B shows the CALLEX instruction, which is one of the call instructions.
When the "CALLEX mn" command is executed,
(1) Disable non-maskable interrupts (NMI) and maskable interrupts (INT) regardless of whether the interrupt is enabled or disabled at that time.
(2) Switch the register bank to "1",
(3) Call the address specified by mn
Do this.
In this embodiment, when a program in the first program area is to be executed from a program in the second program area, the program in the second program area can be executed by executing a CALLEX instruction.

In the above-described load instruction, either an LDF instruction or an LD instruction is used depending on the range of mn, but in the call instruction of the third embodiment, a CALLEX instruction is used regardless of the range of mn. The CALLEX instruction is used when reading the second program from the first program.
Here, the second program area is in the address range of "2000h" to "25FFh" as shown in Fig. 42. The CALLEX instruction is configured so that when calling the address range of "2000h" to "20FFh" among the addresses "2000h" to "25FFh", the code size of "CALLEX mn" is 2 bytes, and when calling a range other than the addresses "2000h" to "20FFh", the code size of "CALLEX mn" is 4 bytes.

Here, the range of addresses "2000h" to "20FFh" is "FFh", i.e., 1 byte. In this case, the code value of the address value "2000h" is set to "0h". This allows the code value when calling the address value "20FFh" to be "FFh", so the code size of "mn" can be set to 1 byte regardless of which address in the range of addresses "2000h" to "20FFh" is called.
Furthermore, when encoding the opcode of "CALLEX," in the third embodiment, the code is set to "0100/1000," i.e., 1 byte. This allows the code size of "CALLEX mn" (mn=2000h to 20FFh) to be set to 2 bytes.

FIG. 47 shows the form of the CALLEX instruction.
In the figure, (A) shows "CALLEX 2000h". In this case, the code value corresponding to "2000h" is "0000/0000" as mentioned above. Also, when the range of "mn" is "2000h" to "20FFh", the code value of "CALLEX" is "0100/1000". Therefore, the code of "CALLEX 2000h" is
0100/1000/0000/0000
This becomes:
When this instruction is executed, it calls the instruction at address "2000h" in the second program area.

Also, (B) in the figure shows "CALLEX 20FFh". In this case, the code value corresponding to "20FFh" is "1111/1111". Also, as mentioned above, when the range of "mn" is "2000h" to "20FFh", the code value of "CALLEX" is "0100/1000". Therefore, the code of "CALLEX 20FFh" is
0100/1000/1111/1111
This becomes:
When this instruction is executed, the instruction at address "20FFh" in the second program area is called.

Furthermore, (C) in the figure shows "CALLEX 2100h". Here, when "mn" changes from "20FFh" to "2100h", a carry occurs, and "mn" cannot be expressed in one byte, so the code size of "mn" becomes two bytes. When "mn" = "2100h", the code of "mn" is
0000/0001/0000/0000
This becomes:

Furthermore, the "CALLEX" code in this case is also different. When the "mn" range is "2000h" to "20FFh", the "CALLEX" code is one byte, but when the "mn" range is "2100h" to "25FFh", the "CALLEX" code is two bytes instead of one byte. As mentioned above, when the opcode is composed of one byte, only 256 out of several thousand instructions are available. Therefore, when the "mn" range is "2000h" to "20FFh", a one-byte code is assigned as the "CALLEX" code, but when the "mn" range is not "2000h" to "20FFh", a two-byte code is assigned as the "CALLEX" code. In the example of FIG. 47, the "CALLEX" code in this case is as follows:
1010/0000/1000/0000
It states that:
Therefore, the code for "CALLEX mn" when "mn" = "2100h" is:
1010/0000/1000/0000/0000/0001/0000/0000
This becomes:
When this command is executed, it calls the command at address "2100h" in the second program area.

Furthermore, (D) in the figure indicates "CALLEX 25FFh" (a command specifying the last address of the second program area). The maximum value when specifying an address in the second program area is "25FFh".
When the code for "2000h" is "0", "25FFh" is
0000/0101/1111/1111
This becomes:
Therefore, the code for "CALLEX 25FFh" is:
1010/0000/1000/0000/0000/0101/1111/1111
This becomes:
When this instruction is executed, the instruction at address "25FFh" in the second program area is called.

As described above, in the "CALLEX mn" instruction of the third embodiment, if the range of "mn" is within the range of "2000h" to "20FFh", the instruction will have a code size of 2 bytes, and if the range of "mn" is outside this range, the instruction will have a code size of 4 bytes.
Therefore, if instructions that are called more frequently are concentrated within the address range of "2000h" to "20FFh", more of the instructions will have a code size of just 2 bytes. This makes it possible to save the storage capacity of the ROM 54 that stores the instructions.
Furthermore, by storing the address used when calling the second program from the first program in the address range "2000h" to "20FFh" within the address range "2000h" to "25FFh" of the second program area, it is possible to easily determine when checking the second program that it is a program called from the first program.

Returning to the explanation of FIG.
45(C) shows the RETEX instruction, which corresponds to the conventional return instruction.
The RETEX command is
(1) The non-maskable interrupt (NMI) and the maskable interrupt (INT) are set to the state before the CALLEX instruction.
(2) Switch the register bank to "0",
(3) Return (RET) (return to the state before the CALLEX (the next instruction after the CALLEX (the program at the return address))
Do this.
This makes it possible to execute the program in the first program area.
If the state at the time of the CALLEX instruction is an interrupt enabled state, the RETEX instruction puts the state into an interrupt enabled state. On the other hand, if the state at the time of the CALLEX instruction is an interrupt disabled state, the RETEX instruction puts the state into an interrupt disabled state.

In a conventional general call (CALL)/return (RET) instruction, a program is called by a call instruction, and after the program is executed, a return instruction is used to return to the state after the call instruction.
In contrast to this, in this embodiment, a program is called by a CALLEX instruction, and after the program is executed, a RETEX instruction is used to return to the state after the CALLEX instruction.
The above points will be explained in more detail below.

FIG. 48 is a diagram showing an example of a conventional CALL instruction and a RET instruction.
In this example, a second program is called while a first program is being executed.
When a second program is called while a first program is running, at least the following processing must be performed.
"1" Interrupt Management Processing To prevent the processing from becoming complicated, interrupt processing is prevented from being executed while the second program is being executed.
[2] SP Register Switching Process The stack area used in the second program is different from the stack area used in the first program, so it is necessary to switch the SP register.
[3] Register Management Processing When a register is used during execution of the second program, it is necessary to take over the register value and prevent the first program from returning.

To comply with the above, the program shown in FIG. 48 includes the following instructions:
First, when the second program is executed while the first program is being executed, interrupt processing is prohibited. The interrupt prohibit instruction is the DI instruction in the diagram. This is the instruction corresponding to "1" above. The DI instruction, which is an interrupt prohibit instruction, is paired with the EI instruction, which is an interrupt enable instruction. Note that the DI instruction can prohibit maskable interrupt processing, but cannot prohibit non-maskable interrupt processing (NMI).

After executing the DI instruction, "PUSH AF" is executed to save the AF register. This instruction corresponds to the above "3". The PUSH instruction is an instruction to store data in the stack area. In other words, an instruction to store the A register value and the F register value in the stack area is executed.
The next "CALL S_CHERR_CHK" command is a command to call "S_CHERR_CHK" (feed-in/feed-out sensor abnormality management), which is one of the second programs. In this example, "S_CHERR_CHK" is listed as the second program.
When "S_CHERR_CHK" (second program) is finished, the "POP AF" instruction is used to restore the saved AF register. This instruction is used to call data from the stack area, and corresponds to "3" above. Next, the EI instruction is used to enable interrupt processing (corresponding to "1" above).

In "S_CHERR_CHK" (second program), "LD (_SB_STACK2), SP" is an instruction (the instruction corresponding to "2" above) to save (store) the SP register value for the first program to a specified address in the second stack area.
The next "LD SP, @STACK2" is an instruction to set the SP register for the second program (an instruction corresponding to the above "2").
Next, "PUSH GPR" and "PUSH QI" are executed to save the registers. Here, "GPR" indicates the type of register to be saved, and corresponds to the A, F, B, C, D, E, H, and L registers. Furthermore, since "GPR" does not include the Q and I registers, "PUSH QI" is executed in addition to "PUSH GPR" to save the Q and I registers (the instruction corresponding to "3" above).

After the second program is executed, the registers and SP register are restored. The Q and I registers are restored by "POP QI." Furthermore, the A, F, B, C, D, E, H, and L registers are restored by "POP GPR" (these are instructions corresponding to "3" above).
Next, the SP register is restored by "LD SP, (_SB_STACK2)" (the instruction corresponding to "2" above).
Then, RET is used to return to the state before the CALL instruction.

As described above, in a general call/return instruction, the instructions corresponding to the above "1" to "3" are as follows in the first program:
D.I.
PUSH AF
POP AF
EI
It is necessary to execute
In addition, in the second program,
LD (), SP
PUSH GPR
PUSH QI
POP QI
POP GPR
LD SP, ()
It is necessary to execute

In contrast to this, as described above, the CALLEX instruction in this embodiment includes the process of disabling interrupts and the process of switching the register bank from 0 to 1. Therefore, the program in the second program area can be executed by the CALLEX instruction (one instruction), and there is no need to provide a separate interrupt disable instruction (DI instruction) or register save instruction (PUSH instruction).
The RETEX instruction also includes a process to return the interrupt to the state before the CALLEX instruction and a process to switch the register bank from 1 to 0. Therefore, the RETEX instruction (1 instruction) can return to the program in the first program area, and there is no need to separately provide an interrupt enable instruction (EI instruction) to return the interrupt to its original state or an instruction to restore the register (POP instruction).
Therefore, it is possible to reduce the program capacity.

Furthermore, the CALLEX and RETEX instructions allow the program to return to the interrupt state of the first program immediately before the second program is executed.
Therefore, if the state immediately before the CALLEX instruction is an interrupt-enabled state, after the second program is executed, the RETEX instruction can return to the first program in an interrupt-enabled state.
On the other hand, if the state immediately before the CALLEX instruction is an interrupt disabled state, after the second program is executed, the RETEX instruction can be used to return to the first program in an interrupt disabled state.

Furthermore, when a CALLEX instruction is executed, the register bank is switched from 0 to 1. Furthermore, when a RETEX instruction is executed, the register bank is switched from 1 to 0.
Therefore, when the CALLEX instruction is executed, the D3 bits of the F registers of register banks 0 and 1 are updated from "0" to "1." Also, when the RETEX instruction is executed, the D3 bits of the F registers of register banks 0 and 1 are updated from "1" to "0."
When the CALLEX instruction is executed, the D3 bit of the F register of either register bank 0 or 1 may be updated from "0" to "1."

Furthermore, the data stored in each register of register banks 0 and 1, except for the D3 bit of the F register, is not updated by the CALLEX instruction or RETEX instruction itself.
This point will be explained using a specific example.
In the following description, the A, B, H, and L registers of register bank 0 will be referred to as 0A, 0B, 0H, and 0L registers, respectively.
The A, B, H, and L registers of register bank 1 are referred to as 1A, 1B, 1H, and 1L registers, respectively.
Assume that the following data is currently stored in the registers of register banks 0 and 1.
0A register: 00000001 (B)
0B register: 00000000 (B)
0H register: 11110001 (B)
0L register: 00000001 (B)
1A register: 00000000 (B)
1B register: 00000011 (B)
1H register: 11110010 (B)
1L register: 00000001 (B)

In this state, when the CALLEX instruction is executed, the state switches from using the 0A, 0B, 0H, and 0L registers to using the 1A, 1B, 1H, and 1L registers. The register values of the 0A, 0B, 0H, 0L, 1A, 1B, 1H, and 1L registers do not change immediately before or after the CALLEX instruction. As mentioned above, only the D3 bit of the F register is updated.
Next, execution of the second program uses the 1A, 1H, and 1L registers, e.g.,
1A register: 00000011 (B)
1B register: 00000011 (B)
1H register: 11110001 (B)
1L register: 00000000 (B)
Let us assume that:

Then, when the RETEX instruction is executed upon completion of the second program, the values of the 1A, 1B, 1H, and 1L registers remain the same, and the state switches to using the 0A, 0B, 0H, and 0L registers. At this point, the values of the 0A, 0B, 0H, and 0L registers are the values immediately before the CALLEX instruction, i.e.,
0A register: 00000001 (B)
0B register: 00000000 (B)
0H register: 11110001 (B)
0L register: 00000001 (B)
is.
The value of the 0H register is the value that was present immediately before the CALLEX instruction, and has not been replaced with the value of the 1H register.
Then, when the first program is executed and, for example, the process of adding "1" to the value of the OA register is executed,
0A register: 00000010 (B)
This becomes:

From the above, if we focus on a specific register (for example, register A), if the value of the specific register immediately before the CALLEX instruction is "x", the value of the specific register will become "y" when the CALLEX instruction is executed. This is because the value of the specific register does not change due to the CALLEX instruction, but because the specific register being used has changed from the specific register in register bank 0 to the specific register in register bank 1.

Let's assume that the program in the second program area is executed, causing the special register to be used and the special register value to be updated from "y" to "y'". When the RETEX instruction is then executed, the special register used switches from the special register in register bank 1 to the special register in register bank 0. Therefore, the special register value immediately after the RETEX instruction becomes the value it had immediately before the CALLEX instruction, i.e., "x". Note that the special register value in register bank 1 remains "y'" even immediately after the RETEX instruction.

Specifically, the above-mentioned CALLEX instruction and RETEX instruction are used, for example, as follows.
Fig. 49 is a flowchart showing the program start (M_PRG_START) in the third embodiment. In Fig. 49, step numbers specific to the third embodiment are underlined.
Program start (M_PRG_START) is a program of the main control board 50 that is executed first after power is turned on, and determines whether the conditions for transitioning to the setting change mode are met, whether there is a power outage recovery abnormality, etc.
If it is determined that a power failure recovery error has occurred, the process proceeds to step S2801 for unrecoverable error processing (C_ERROR_STOP) or step S2731 for initialization processing (M_INI_SET).
If it is determined that the mode can be changed to the setting change mode, the process proceeds to the initialization process in step S2731, and after this initialization process, the mode can be changed to the setting change mode.
On the other hand, if it is determined that the setting change mode has not been entered and that there is no power interruption recovery abnormality, the process proceeds to power recovery processing (M_POWER_ON) in step S2721.

In Figure 49, when the program start (M_PRG_START) process begins, first, in step S2851, an initial value is set in the SP register of register bank 0. When power is turned on, the SP register value of register bank 0 is "0." Here, the instruction "LD SP, F200h" stores "F200h" in the SP register of register bank 0.

The value "F200h" stored here is the last address of the first stack area plus "1", as shown in Figure 44. When the SP register value of register bank 0 is "F200h", this indicates that data is to be stored (pile) in "F1FFh".
Secondly, in step S2851, "CALLEX 2000h" is executed. In this example, it is assumed that the start address of the RWM checksum calculation command in step S2852 is "2000h".
Next, the process proceeds to step S2852, where the second program (calculating the RWM checksum) is started based on "CALLEX 2000h." When the second program is started for the first time after power-on, an initial value is set in the SP register of register bank 1. At power-on, the SP register value of register bank 1 is "0." Here, "F400h" is stored in the SP register of register bank 1 by the instruction "LD SP, F400h."

The value "F400h" stored here is the value obtained by adding "1" to the last address "F3FFh" of the second stack area, as shown in Figure 44. When the SP register value of register bank 1 is "F400h", this indicates that data is to be stored (pile) in "F3FFh".
Furthermore, when the RWM checksum calculation is completed, RETEX is executed, and the program (instruction) in the first program is returned to the program (S2705) after the CALLEX in step S2851. Then, the process proceeds to step S2075 and subsequent steps. The description of the process from step S2705 onward is omitted.
As described above, in the third embodiment, since the CALLEX instruction is an instruction including register saving, there is no need to define separate register save instructions ("PUSH AF", "PUSH GPR", and "PUSH QI"). Similarly, since the RETEX instruction is an instruction including register restoring, there is no need to define separate register restore instructions ("POP AF", "POP GPR", and "POP QI").

Furthermore, after storing the initial value "F400h" in the SP register of register bank 1 when the second program is executed for the first time after power-on (step S2852), when returning to the first program and executing the second program again, there is no need to store the initial value "F400h" in the SP register of register bank 1 again.
In other words, starting from power-on, the first time the second program is executed, a process (instruction) is executed to store the initial value "F400h" in the SP register of register bank 1, but subsequent times the second program is executed, it is not necessary to execute the process (instruction) to store the initial value "F400h" in the SP register of register bank 1. This makes it possible to reduce the size of the second program.

However, this is not limiting, and a process (instruction) for storing the initial value "F400h" in the SP register of register bank 1 may be executed each time the second program is executed. Alternatively, a process (instruction) for storing the initial value "F400h" in the SP register of register bank 1 may be executed when a specific condition is satisfied during execution of the second program.
Assume that the first time the second program is executed after power-on, the initial value "F400h" is stored in the SP register of register bank 1, and the second program is executed. If data is stored in the second stack area during execution of the second program, the SP register value of register bank 1 is updated.

As described above, for example, when two bytes of data are initially stored in the second stack area, the SP register value of register bank 1 is updated from "F400h" to "F3FEh." After that, the data is usually restored from the second stack area before the second program ends. Therefore, when the second program ends, the SP register value of register bank 1 is usually "F400h."
When the second program ends and the program returns to the first program, the SP register of register bank 0 is used. The SP register value of register bank 0 maintains the value it had immediately before the program started. For example, if the SP register value of register bank 0 was "F1FDh" immediately before the program started, the SP register value of register bank 0 will be "F1FDh" when the program ends and the program returns to the first program.

Next, a method of using the CALLEX instruction (application example) will be described.
FIG. 50 shows an example in which a CALLEX instruction and a JR instruction (jump instruction) are used.
As mentioned above, the CALLEX instruction can be a two-byte instruction if the address range to be called is "2000h" to "20FFh." Therefore, when calling a second program from a first program, the more CALLEX instructions you use, the more memory capacity you can save on instructions.

For example, if a "CALLEX 2000h" instruction is set and executed, the program stored at address 2000h will be called. However, if the program begins to be written (stored) at address 2000h and occupies most of the addresses from 2000h to 20FDh, it will be impossible to set many CALLEX instructions. To put it in extreme terms, if a program starts at address 2000h and continues to address 20FFh, in other words, if there is only one program in the range from 2000h to 20FFh, then only one 2-byte CALLEX instruction will be possible.

Therefore, in the example of Figure 50, a JR (jump) instruction is placed in the range of addresses "2000h" to "20FFh", the destination of the JR instruction is specified to be outside the range of addresses "2000h" to "20FFh", and the actual program is stored at the destination of the JR instruction.
For example, "JR 2200h" is stored at address "2000h." The instruction "JR 2200h" means to jump to address "2200h." When "CALLEX 2000h" is executed, address "2000h" is called, but because "JR 2200h" is stored at address "2000h," a jump to address "2200h" is also performed. If an actual program ("Program A" in FIG. 50) is stored at address "2200h" or later, the actual program (Program A) can be placed outside the range of addresses "2000h" to "20FFh."

In this embodiment, the code size required for the "JR mn (mn=2000h to 20FFh)" instruction is 3 bytes.
2000h JR mn1 (in the example of FIG. 50, mn1=2200h)
2003h JR mn2 (in the example of FIG. 50, mn2 = 2250h)
2006h JR mn3 (in the example of FIG. 50, mn3 = 22A0h)
:
JR instructions are placed in 3-byte increments, as shown below.

However, this is not limiting, and if the code size required for the "JR mn (mn = 2000h to 20FFh)" instruction can be configured from 2 bytes,
2000h JR mn1
2002h JR mn2
2004h JR mn3
:
This becomes:
Also, if the code size required for the "JR mn (mn = 2000h to 20FFh)" instruction is 4 bytes,
2000h JR mn1
2004h JR mn2
2008h JR mn3
:
This becomes:

In the example of Figure 50, it would be possible to place JR instructions in the address range from "2000h" to "20FFh".
(1) 2000h JR mn1
(2) 2003h JR mn2
(3) 2006h JR mn3
:
(84)20F9h JR mn84
(85) 20FCh JR mn85
(86)20FFh JR mn86
Therefore, a total of 86 JR instructions, each consisting of 3 bytes, can be stored within the address range of "2000h" to "20FFh."

In the example of FIG.
2000h JR 2200h
The actual program (program A) at address "2000h" was stored in the range of addresses "2200h" to "224Fh".
Also,
2003h JR 2250h
The actual program (program B) at address "2003h" was stored in the range of addresses "2250h" to "229Fh".

Furthermore,
2006h JR 22A0h
The actual program (program C) at address "2006h" was stored at address "22A0h" and onward.
In this way, it is desirable to store almost no actual program to be executed by a CALLEX instruction in the address range "2000h" to "20FFh" of the CALLEX instruction, which allows for a code size of 2 bytes. In other words, the address of the second program called by the CALLEX instruction is contained in the address range "2000h" to "20FFh." However, as will be described later, the JR instruction does not need to be used for the second program called by the CALLEX instruction that is closest to address "20FFh" in the address range "2000h" to "20FFh." In this way, by using the JR instruction for the majority (including "almost" or "all") of the instructions of the second program called by the CALLEX instruction and storing the actual program at address "2100h" or later, the second program area can be used efficiently.

For example, if there are only 10 CALLEX instructions, JR instructions are stored in the addresses corresponding to the first through ninth CALLEX instructions, but the actual program may be stored directly in the address corresponding to the tenth CALLEX instruction without using the JR instruction.
On the other hand, regardless of the number of CALLEX instructions, it may be determined that only JR instructions are stored in the address range "2000h" to "20FFh," and even if the number of JR instructions (CALLEX instructions) is significantly less than the upper limit of 86, the memory area before address "20FFh" may be left free as a spare.

As mentioned above, the code size of the CALLEX instruction is 2 bytes when calling within the address range of "2000h" to "20FFh", and 4 bytes when calling outside the address range of "2000h" to "20FFh".
Therefore, the total is 5 bytes, which is 2 bytes for the CALLEX instruction and 3 bytes for the JR instruction, and is larger than the code size (4 bytes) of the CALLEX instruction that calls an address outside the range of 2000h to 20FFh.

However, in the case of chips for gaming machines that comply with the Entertainment and Amusement Business Act regulations (such as slot machines and pachinko machines), the first program area does not have sufficient memory capacity, but the second program area does.
Therefore, even if the JR instruction stored in the second program area increases by 3 bytes, it is more advantageous in terms of efficient use of the first program area to keep the code size of the CALLEX instruction stored in the first program area to 2 bytes.

Also, near the end approaching address "20FFh", the program itself may be stored without providing a JR instruction.
As described above, if 3-byte JR instructions are sequentially placed after address "2000h", the "JR mn86" instruction will be stored at address "20FFh". In this case, the "JR mn86" instruction will be stored in the 3-byte storage area from address "20FFh" to "2101h".

However, storing the JR instruction in the 3-byte memory area after address "20FFh" and storing the actual program for that instruction in another memory area saves memory capacity by storing the program directly from address "20FFh".
For this reason, in the example shown in FIG. 50, the JR instruction is not placed at address "20FFh", and a program (program D) is stored starting from address "20FFh".
As a result, when "CALLEX 20FFh" is executed, program D stored at address "20FFh" and after will be executed.

Although the address "20FFh" is used as an example above, the same applies to cases where the JR instruction is placed at addresses "20FDh" or "20FEh."
Specifically, it is preferable to store the JR instruction in the 3-byte memory area from address "20FDh" to "20FFh" and store the program directly at address "20FDh" and after, in terms of saving memory capacity, rather than storing the program in another memory area.
Similarly, it can be said that storing the JR instruction in the 3-byte memory area from address "20FEh" to "2100h" and storing the program directly at address "20FEh" and after is preferable in terms of saving memory capacity, rather than storing the JR instruction in the 3-byte memory area from address "20FEh" to "2100h" and storing the program in another memory area.

Although the third embodiment of the present invention has been described above, the present invention is not limited to the above embodiment and various modifications such as those described below are possible.
(1) In Fig. 42, the ROM 54 is shown to have a program management area and an unused area, but this is not limiting, and the ROM 54 may have at least a first program area, a first data area, a second program area, and a second data area. Furthermore, while Fig. 42 shows the start address and end address for each of these storage areas, the storage capacity shown in Fig. 42 is merely an example and is not limited to this. Therefore, the start address and end address of each storage area shown in Fig. 42 are merely an example and can be set arbitrarily.

Therefore, in the example of Figure 42, since the address range of the second program area is "2000h" to "25FFh", "2000h" to "20FFh" is shown as an example of an address range in which the code size of the CALLEX instruction can be set to 2 bytes, but if the address range of the second program area changes, the address range in which the code size of the CALLEX instruction can be set to 2 bytes will also change.
For example, if the address range of the second program area is "2150h" to "264Fh", the address range in which the code size of the CALLEX instruction can be set to 2 bytes is "2150h" to "224Fh".

(2) In the example of Fig. 42, the first program area, the first data area, the second program area, and the second data area are arranged in this order in the ROM 54, but this is not limiting, and for example, the second program area and the second data area may be arranged before the first program area and the first data area. Also, a predetermined management area or the like may be arranged at the top address of the ROM 54 (before the first program area in Fig. 42).
Similarly, the RWM 53 is not limited to being arranged in the order of the work area and stack area, but may be arranged in the order of the stack area and work area. Furthermore, although the first work area, first stack area, second work area, and second stack area are arranged in this order, this is not limiting, and for example, the second work area and second stack area may be arranged before the first work area and first stack area. Furthermore, a predetermined management area or the like may be arranged at the top address of the RWM 53 (before the first work area in FIG. 42).

(3) In the built-in register area, each register bank is provided with a main register and a sub-register, but this is not limiting, and any register bank may be provided with at least a main register.
(4) In Figure 43, the register bank monitor is assigned to bit D3 of the F register, but this is not a limitation and it may be assigned to any bit. For example, if the second zero flag is not used, it may be assigned to bit D5.
It is also possible to provide a register dedicated to the register bank monitor rather than assigning the register bank monitor to a specific bit in the F register.

(5) In the example of FIG. 42, the address range of the first data area is set to "1200h" to "1DF3h," and it has been explained that the range of "mn" can be expressed in 12 bits within this range.
where:
1200h=0000/0000/0000(B)
When
1111/1111/1111(B)=FFFh
is.
and,
1200h+FFFh=21FFh
is.
Therefore, if the range of the first data area is within the range of "1200h" to "21FFh", the range of "mn" can be expressed in 12 bits, and the code size of "LDF HL, mn" can be configured in 2 bytes.

(6) The address ranges and sizes of the first and second stack areas shown in Figure 42 are examples and are not limited to these. For example, if the range of the first stack area is addresses "F1D0h" to "F2FFh," step S2851 in Figure 49 would result in "LD SP, F300h."

(7) The third embodiment can be applied not only to medalless gaming machines but also to slot machines and pachinko gaming machines under the Entertainment and Amusement Act. Furthermore, it can also be applied to parrot and casino machines that use gaming balls.
(8) The first to third embodiments and the various modifications shown in the first to third embodiments are not limited to being implemented alone, but can also be implemented in appropriate combinations.

Fourth Embodiment
The gaming machine 10 in the fourth embodiment is a medal-less gaming machine (managed gaming machine, enclosed gaming machine) similar to the first and second embodiments.
In the fourth embodiment, a one-chip microprocessor 500 provided on the main control board 50 executes control including control of the number of game media.
In addition, the fourth embodiment uses the CALLEX instruction, RETEX instruction, register bank, etc., which are explained in the third embodiment.
FIG. 51 is a block diagram showing the gaming machine 10 in the fourth embodiment, and corresponds to FIG. 29 (second embodiment).
29, the gaming machine 10 of the second embodiment is provided with a game media count control board 100 in addition to the main control board 50. In contrast, the gaming machine 10 of the fourth embodiment is not provided with the game media count control board 100.

In Figure 51, the main control board 50 is equipped with a one-chip microprocessor 500. The one-chip microprocessor 500 integrates a CPU (microprocessor, referred to as the "main CPU 501" in Figure 51), ROM (read-on-memory), and RWM (read-write memory) into a single chip, thereby blocking unauthorized access from outside and ensuring high security.

In Figure 51, the main CPU 501 corresponds to the "first main control CPU 55" in Figure 29 (second embodiment). Here, the first main control CPU 55 in Figure 29 did not perform control related to the number of gaming media. In the second embodiment, control related to the number of gaming media was performed by the second main control CPU 105 provided on the gaming media number control board 100.

In contrast, in the fourth embodiment, as described above, the game media count control board 100, i.e., the second main control CPU 105, is not provided. Therefore, in the fourth embodiment, the main CPU 501 executes control related to the number of game media. Note that, like the CPU 55 on the main control board 50 in the other embodiments (main CPU 55 in the first embodiment, first main control CPU 55 in the second embodiment), the main CPU 501 naturally performs control related to the progress of the game (reel drive control, role lottery, etc.) and other controls (output control of test signals to the test machine, display control of the role ratio monitor 113, etc.).

In Figure 51, the main control ROM 502 is a storage means for storing programs and data for controlling the progress of the game, and the main control RWM 503 is a storage means for temporarily storing data when controlling the progress of the game.
Furthermore, the game media number control ROM 502 is a storage means for storing programs and data for controlling the number of game media (calculating the number of game media to be awarded, processing the awarding of game media, etc.), and the game media number control RWM 503 is a storage means for temporarily storing data when controlling the number of game media.

"Controlling the number of gaming media" means:
(1) Control for sending game media (medals, etc.) that have been loaned or won by winning to a tray (when the game media (medals) are tangible objects);
Or,
(2) Control for transmitting a signal indicating the number of game media loaned or won by winning to a game media number display device (game ball number display device or medal number display device) (when game media (medals) are intangible assets)
This refers to
The programs stored in the game media number control ROM 504, and the data stored in the game media number control ROM 504 and the game media number control RWM 505 are provided only for controlling the number of game media, and do not perform any control other than controlling the number of game media.

Note that "game media count control" is sometimes referred to as "medal count control." In this case, it is referred to as "medal count control ROM," "medal count control RWM," etc. However, as explained in the second embodiment, medal-less gaming machines do not use medals as tangible objects. Therefore, "medals" in medal-less gaming machines refer to gaming media (gaming value) used for gaming. Therefore, when referring to "medals," it can refer to medals (gaming medals) used in slot machines under the current Entertainment and Amusement Act, or to medals as intangible objects (for example, electronic data). Note that medals as intangible objects may also be referred to as gaming media, gaming value, points (or simply "points"), electronic medals, electronic data, electronic information, electronic gaming media, electronic gaming value, etc.

Furthermore, the "gaming media" in "gaming media number control" includes gaming media (gaming balls) used in pachinko gaming machines under the Entertainment and Amusement Act. In other words, the "gaming media number control" in the fourth embodiment is, of course, applicable to pachinko gaming machines.

The current Entertainment and Amusement Business Act regulations stipulate that "the total number of ROMs and RWMs installed on the main control board 50 must not exceed one each across all main boards (excluding those stipulated in the control of the number of gaming media)."
Furthermore, it is stipulated that "the total number of ROMs and RWMs mounted on the main control board 50 for controlling the number of gaming media shall not exceed one each across all main boards."
Therefore,
The number of game media control ROMs is determined as follows: main control ROM 502: 1 main control RWM 503: 1 game media number control ROM 504: 1 game media number control RWM 505: 1.
It should be noted that the four storage means are not meant to be physically separate, but are provided in a single built-in memory, as will be described later.

The out-of-use ROM 506 is a storage means for storing programs or data other than those stored in the in-use ROM, and the out-of-use RWM 507 is a storage means for storing data other than those stored in the in-use RWM.
Here, "outside the area of use" refers to a storage area used for the purpose of controlling the output of signals necessary for testing the gaming machine 10 and preventing cheating. Furthermore, programs and data "used for the purpose of preventing cheating" include, for example, programs and data necessary for display control of the winning ratio monitor 113. Programs and data placed in ROM or RWM outside the area of use must not impair the fairness of the game.
The area other than the "usage area" is called "outside the use area," and the "usage area" is also called "inside the use area."
Therefore, the main control ROM 502 and the game media number control ROM 504 are ROMs within the used area.
Furthermore, the main control RWM 503 and the game media count control RWM 505 are RWMs within the use area.

The main control ROM 502, main control RWM 503, game media count control ROM 504, game media count control RWM 505, out-of-use area ROM 506, and out-of-use area RWM 507 are provided as built-in memories within the one-chip microprocessor 500. As will be described in detail later, these ROMs and RWMs are arranged in a predetermined order in address sequence.
In other words, the built-in memory is divided and arranged into a main control ROM 502, a main control RWM 503, a game media number control ROM 504, a game media number control RWM 505, an outside-usage area ROM 506, and an outside-usage area RWM 507.
However, the main control ROM 502, the game media number control ROM 504, and the ROM outside the use area 506 are each located in an area that is clearly separated.
Similarly, the main control RWM 503, the game media count control RWM 505, and the outside-of-use-area RWM 507 are each arranged in an explicitly separated area.

In the fourth embodiment, the game media count control board 100 of the second embodiment is not provided, and therefore the total game media count clear switch 112 and the role ratio monitor 113 that were provided on the game media count control board 100 in the second embodiment are provided on the main control board 50. As described above, the control for displaying a predetermined ratio on the role ratio monitor 113 is executed based on the programs and data stored in the out-of-use ROM 506 and the out-of-use RWM 507. The total game media count clear switch 112 may be provided directly on the main control board 50, or may be configured to be electrically connected to the main control board 50 (for example, the board on which the total game media count clear switch 112 is mounted is electrically connected to the main control board 50).
Furthermore, the game media number display board (game media number display device) 120 is electrically connected to the game media number control board 100 in the second embodiment, but is electrically connected to the main control board 50 in the fourth embodiment. Control for displaying the number of game media on the game media number display unit 121 is executed based on programs and data stored in the game media number control ROM 504 and the game media number control RWM 505.

The counting switch 47 is electrically connected to the game media number control board 100 in the second embodiment, but is electrically connected to the main control board 50 in the fourth embodiment.
The connection terminal board 130 is electrically connected to the game media count control board 100 in the second embodiment, but is electrically connected to the main control board 50 in the fourth embodiment.
29 of the second embodiment shows the sub-control RWM 83, sub-control ROM 84, and sub-control CPU 85 of the sub-control board 80, which are built into the one-chip microprocessor of the sub-control board 80, just like the main control board 50. For this reason, in FIG. 51, the one-chip microprocessor 80a of the sub-control board 80 is shown, just like the one-chip microprocessor 500 of the main control board 50.

Fig. 52 is a diagram showing a memory map of the built-in memory (ROM, RWM, etc.) provided in the one-chip microprocessor 500 of the main control board 50. Fig. 52 shows only the part of the built-in memory that is related to this embodiment, and does not show all of the built-in memory.
It should be noted that the "program area" in FIG. 42 of the third embodiment and the "control area" in FIG. 52 etc. are called differently, but have the same function.

52, the main control ROM 502 and the game media number control ROM 504 are used area ROMs, and in addition to these, there is provided an out-of-use area ROM 506. Similarly, the main control RWM 503 and the game media number control RWM 505 are used area RWMs, and in addition to these, there is provided an out-of-use area RWM 507.
The main control ROM 502 and the number of game media control ROM 504 are ROMs in the usage area, and therefore correspond to areas for storing programs and data related to the progress of the game (including control of the number of game media). In contrast, the non-usage area ROM 506 is ROM outside the usage area, and therefore corresponds to an area for storing programs and data unrelated to the progress of the game. In particular, in this embodiment, the non-usage area ROM 506 corresponds to a memory area for storing programs and data related to display control of the winning ratio monitor 113, and a memory area for storing programs and data related to output control of test signals.

Each of the storage areas of the main control ROM 502, the game media count control ROM 504, and the out-of-use ROM 506 includes a control area and a data area.
Here, the "data area" refers to a storage area in which only information other than programs is stored or will be stored.
In the fourth embodiment, the memory area related to main control is referred to as "area 1," the memory area related to game media count control is referred to as "area 2," and the memory area outside the use area is referred to as "area 3."

The ROM has at least an address range of 0000h to 2FFFh and a storage area of 16K bytes or less. Within this storage area, the control area 1 of the main control ROM 502 is set to 4.5K bytes or less, and the data area 1 is set to 3.0K bytes or less.
The storage area of the game media number control ROM 504 is set to a total of 2.5K bytes or less for the control area 2 and the data area 2.

Furthermore, during the RWM, RWM area 1, which is the storage area of the main control RWM 503, is a storage area used (updated, referenced) during execution of the program (program related to the progress of the game) stored in control area 1. Similarly, RWM area 2, which is the storage area of the number of game media control RWM 505, is a storage area used (updated, referenced) during execution of the program (program related to control of the number of game media) stored in control area 2. Furthermore, RWM area 3, which is the storage area of the outside-usage-area RWM 507, is a storage area used (updated, referenced) during execution of the program stored in control area 3.
The RWM area is set to 1024K bytes or less as a whole. Furthermore, RWM area 1 and RWM area 2 are each set to 512K bytes or less.

An unused area may be interposed between the main control ROM 502, the game media number control ROM 504, and the ROM outside the used area 506 (example of Figure 52), or the main control ROM 502, the game media number control ROM 504, and the ROM outside the used area 506 may be arranged at consecutive addresses.
Similarly, the main control RWM 503, the game media number control RWM 505, and the RWM outside the used area 507 may be arranged at consecutive addresses (example of Figure 52), or an unused area or the like may be interposed between the main control RWM 503, the game media number control RWM 505, and the RWM outside the used area 507.

The internal memory also contains one internal register area. This internal register area further contains register bank 0 and register bank 1. Register bank 0 and register bank 1 are similar to register bank 0 and register bank 1 described in Figure 42 (third embodiment), and each register bank contains various registers (see Figure 42 (B)).

As will be described in detail later, each register in register bank 0 or register bank 1 is used when a program stored in either control area 1, control area 2, or control area 3 is being executed.
Specifically, for example, the allocation can be as follows:
(1) Pattern 1
Register bank 0: Used when executing a program stored in control area 1. Register bank 1: Used when executing programs stored in control area 2 and control area 3. (2) Pattern 2
Register bank 0: Used when executing programs stored in control area 1 and control area 2. Register bank 1: Used when executing programs stored in control area 3.

(3) Pattern 3
Register bank 0: Used when executing the programs stored in control area 1 and control area 3. Register bank 1: Used when executing the program stored in control area 2. (4) Other patterns In this embodiment, two register banks are provided. However, for example, three register banks (one for each control area) may be provided,
It is also possible to configure the following: Register bank 0: Used when a program stored in control area 1 is being executed Register bank 1: Used when a program stored in control area 2 is being executed Register bank 2: Used when a program stored in control area 3 is being executed

52, RWM area 1, RWM area 2, and RWM area 3 are provided with their own stack areas 1, 2, and 3, respectively. The program in main control ROM 502 uses stack area 1, the program in number of game media control ROM 504 uses stack area 2, and the program in outside-usage-area ROM 506 uses stack area 3. The programs in main control ROM 502, number of game media control ROM 504, and outside-usage-area ROM 506 are configured not to share stack areas. Specifically, for example, stack area 1 is not shared between the program in main control ROM 502 and the program in number of game media control ROM 504.
Furthermore, the programs in the main control ROM 502, the game media count control ROM 504, and the programs in the out-of-use area ROM 506 are all configured not to use stack areas other than the corresponding stack areas (for example, stack area 1 for the programs in the main control ROM 502). Specifically, for example, the programs in the main control ROM 502 will not use stack area 3.

As described above, in the fourth embodiment,
(1) "Control Area 1" and "Data Area 1" refer to the storage areas of the main control ROM 502 (usage area).
(2) “Control Area 2” and “Data Area 2” refer to the storage areas of the game media count control ROM 504 (usage area),
(3) “Control Area 3” and “Data Area 3” refer to the storage areas of the ROM 506 outside the area of use.
(4) "RWM area 1" refers to the storage area of the main control RWM 503 (usage area), and "stack area 1" refers to the stack area of RWM area 1.
(5) “RWM area 2” refers to the storage area of the game media count control RWM 505 (usage area), and “stack area 2” refers to the stack area of RWM area 2.
(6) “RWM area 3” refers to the storage area of the RWM 507 outside the area of use, and “stack area 3” refers to the stack area of the RWM area 3.

FIG. 53 shows examples of divisions into the main control area, the game media number control area, and the area outside the use area, where (A) shows Example 1 and (B) shows Example 2.
In Example 1 (A) in the figure, no outside use area is provided within the main control area. In other words, an outside use area is provided outside the main control area and the game media count control area.
In this case,
(1) Main control area: Includes memory areas (main control ROM 502 and main control RWM 503) for storing programs and data related to the progress of the game, but does not include memory areas (outside use area ROM 506 and outside use area RWM 507) used for the purpose of controlling the output of signals necessary for testing the gaming machine 10 and preventing fraud.
(2) Game Media Count Control Area: A storage area for storing programs and data related to controlling the number of game media (game media count control ROM 504, game media count control RWM 505).
(3) Area outside the use area: A storage area used for controlling the output of signals necessary for testing the gaming machine 10 and for preventing fraud (outside the use area ROM 506 and outside the use area RWM 507).
This becomes:

In addition, in Example 2 in the figure (B), a use area and an outside use area are provided in the main control area. Note that the game media count control area is only a use area and does not have an outside use area. As described above, the game media count control area is a storage area that stores programs and data for executing only control related to the number of game media. Furthermore, there is no outside use area outside the main control area and the game media count control area.
In this case,
(1) Main control area: A storage area for storing programs and data related to the progress of games (main control ROM 502 and main control RWM 503), and a storage area used for controlling the output of signals necessary for testing the gaming machine 10 and for preventing fraud (outside use area ROM 506 and outside use area RWM 507).
(2) Game Media Count Control Area: A storage area for storing programs and data related to controlling the number of game media (game media count control ROM 504, game media count control RWM 505).
This becomes:

Figure 54 is a diagram showing communication between the main control area (usage area, non-usage area) and the game media count control area. In the example of Figure 54, the storage area is divided according to Example 2 of Figure 53 (B). In other words, the main control area has a usage area and a non-usage area.
Program execution in one main CPU 501 of one-chip microprocessor 500 mounted on main control board 50 is mainly the program in control area 1 of main control ROM 502. In addition, programs in the used area of game media count control ROM 504 and the program in the area of out-of-use area ROM 506 are executed by calling a predetermined address (in other words, "statically") from the program in control area 1 of main control ROM 502. The program list in this case is configured so that the called address is clearly written.
In addition, the programs in the game media count control ROM 504 and the programs in the out-of-use area ROM 506 are modularized by function, and are configured so that when called by the program in the main control ROM 502, all registers used by the program in the main control ROM 502 ("all registers" refers to multiple registers, so they are also referred to as "multiple registers"; the same applies below) are protected. The following methods can be used to protect all registers.

(1) First Method: The register bank used by the program in main control ROM 502 is made different from the register bank used by the program in number of game media control ROM 504 and the program in outside-usage area ROM 506. In other words, when the program in main control ROM 502 calls the program in number of game media control ROM 504 or the program in outside-usage area ROM 506, and executes the program in number of game media control ROM 504 or the program in outside-usage area ROM 506, the register bank is switched.

(2) Second Method The register bank used by the program in main control ROM 502 is the same as the register bank used by the program in number of game media control ROM 504 or the program in out-of-use area ROM 506. In this case, when the program in main control ROM 502 calls and executes the program in number of game media control ROM 504 or the program in out-of-use area ROM 506, a command to save all registers is executed.
The program for protecting all registers will be described later.

In the use area of the main control area, the programs stored in the control area 1 can refer to the data stored in the data area 1. In addition, the programs stored in the control area 1 can refer to and update the data stored in the RWM area 1.
Similarly, the programs stored in the control area 2 can refer to the data stored in the data area 2 and can refer to and update the data stored in the RWM area 2.
Furthermore, the programs stored in the control area 3 can refer to the data stored in the data area 3, and can refer to and update the data stored in the RWM area 3.

On the other hand, the program in control area 1 can call the program in control area 2, and can call the program in control area 3. Specifically, it is possible to call and execute the program in control area 2 based on a CALLEX or CALL instruction in the program in control area 1. Furthermore, based on a RETEX or RET instruction in the program in control area 2, after the program in control area 2 is executed, it is possible to return to the point immediately after the CALLEX or CALL instruction in the program in control area 1.
Similarly, a program in control area 3 can be called and executed based on a CALLEX or CALL instruction in the program in control area 1. Also, based on a RETEX or RET instruction in the program in control area 3, after the program in control area 3 is executed, it is possible to return to the point immediately after the CALLEX or CALL instruction in the program in control area 1.

In contrast, the system is configured so that a program in control area 2 cannot call a program (subroutine) in control area 1, nor can a program in control area 2 call a program (subroutine) in control area 3. This is because if it were possible for a program in control area 2 to call a program (subroutine) in control area 1 or control area 3, the program configuration would become complicated. Also, this would risk deviating from the purpose of setting an upper limit on the storage capacity of main control ROM 502 and game media count control ROM 504.

Similarly, the system is configured so that a program in control area 3 cannot call a program (subroutine) in control area 1, and a program in control area 3 cannot call a program (subroutine) in control area 2. This is because if it were possible for a program in control area 3 to call a program (subroutine) in control area 1 or control area 2, the program configuration would become complicated. Also, this would risk deviating from the purpose of setting an upper limit on the storage capacity of main control ROM 502 and game media number control ROM 504.

Furthermore, the program in control area 1 cannot directly reference the data in data area 2. In this case, the program in control area 1 calls the program in control area 2, and the program in control area 2 references the data in data area 2.
Similarly, the program in control area 1 cannot directly reference the data in data area 3. In this case, the program in control area 1 calls the program in control area 3, and the program in control area 3 references the data in data area 3.

Furthermore, the program in the control area 1 cannot update the data in the RWM area 2, but can refer to the data in the RWM area 2.
Similarly, the program in the control area 2 cannot update the data in the RWM area 1, but can refer to the data in the RWM area 1.
Furthermore, the program in the control area 1 cannot update the data in the RWM area 3, but is configured to be able to refer to the data in the RWM area 3.
Similarly, the program in the control area 3 cannot update the data in the RWM area 1, but can refer to the data in the RWM area 1.

Furthermore, the program in the control area 2 is configured so that it cannot update the data in the RWM area 3, but can refer to the data in the RWM area 3.
Similarly, the program in the control area 3 cannot update the data in the RWM area 2, but can refer to the data in the RWM area 2.

As described above, the program in the control area "N" (where "N" is either "1,""2," or "3") is configured so that the data in the RWM area "M" (where "M" is any number other than "N") cannot be updated (but can be referenced).
If it were possible to update the data in RWM area "M" using a program in control area "N", this would deviate from the purpose of setting the upper limit of the capacity of RWM area 1 and RWM area 2 at "512K" bytes, as shown in Figure 52.

Furthermore, in order to reduce the amount of program usage in control area 1, control area 2 or control area 3 are configured not to have common general-purpose subroutines. If general-purpose subroutines that can be used by programs in control area 1 were provided in control area 2 or control area 3, programs that should be stored in control area 1 would essentially be able to be stored in control area 2 or control area 3, which could deviate from the purpose of setting an upper limit on the storage capacity of control area 1 (4.5K bytes or less).

Furthermore, each program module in control area 1, control area 2, and control area 3 is always called in subroutine format, and after the subroutine ends, the RETEX or RET command is used to return to the program immediately after the call. Furthermore, one module is provided for each purpose. This configuration clarifies the program structure.
The term "module" refers to a group of programs for each purpose.
Furthermore, a "subroutine" refers to a group of programs that are called from the main routine by a CALLEX instruction, CALL instruction, etc., and always return immediately after the call by a RETEX instruction, RET instruction, etc. Therefore, a subroutine can be said to be a subordinate concept to a module.

Next, specific examples of the programs in control area 1, control area 2, and control area 3 will be described.
In the examples shown in Figures 55 to 57 below,
Control area 1: Main control area usage area Control area 2: Game media number control area (usage area)
Control area 3: Outside the area used by the main control area.
55 is a diagram showing example 1 of programs in control area 1, control area 2, and control area 3. In example 1, the program in control area 1 uses register bank 0, and the programs in control area 2 and control area 3 use register bank 1. Therefore, when a program in control area 1 calls a program in control area 2 or control area 3 and then executes the program in control area 2 or control area 3, it is necessary to switch the register bank from register bank 0 to register bank 1.
Furthermore, when the program in control area 2 or control area 3 is terminated and the program in control area 1 is returned to, the register bank must be switched (returned) from register bank 1 to register bank 0.

In addition, when a program other than the program in control area 1 (a program in control area 2 or a program in control area 3) is being executed, interrupt processing is prohibited so that data in the RWM area of other areas is not updated due to interrupt processing.
Also, the system is configured not to use interrupts that cannot be disabled (NMI).

In FIG. 55, the program in control area 1 is as follows:
The first "ORG 0000h" indicates that the start address of the control area 1 is "0000h".
The next "M1_aaaaa" indicates the first program in control area 1.
In this program, the first "LD SP, @STACK1" indicates that stack 1 is set in the SP register (stack pointer register; in this case, this indicates the SP register of register bank 0). The initial value of stack 1 (@STACK1) is "F200h" as shown in FIG. 55, and this value is written to the SP register of register bank 0.

"CALLEX M2_nnnnn" is a command to call the program "M2_nnnnn." In this example, the program "M2_nnnnn" is stored in the control area 2.
When the "CALLEX mn" command is executed,
(1) Disable interrupts regardless of whether the interrupt is enabled or disabled at that time.
(2) Switch the register bank from register bank 0 to register bank 1,
(3) Call the specified address
Do this.
In this way, when executing a program in the second or third control area from a program in the first control area, the program in the second or third control area can be executed by executing a CALLEX command.

Here, the CALLEX command is used instead of the general CALL command because the program "M1_aaaaa" in control area 1 calls (executes) the program "M2_nnnnn" in control area 2, which requires switching register banks.
In other words, by using different register banks (different registers) when executing the program in control area 1 and when executing the program in control area 2, when returning to the program in control area 1 after the program in control area 2 has finished, the register values can be restored to those immediately before the program in control area 2 was called.

Furthermore, as described above, the CALLEX instruction does not include a DI (disable interrupt) instruction because interrupts are disabled before the target program is called.
Furthermore, another program is executed by the CALLEX instruction, and the RETEX instruction executed when the other program ends includes an instruction to permit an interrupt, so no EI (enable interrupt) instruction is provided when the other program ends.

Execution of "CALLEX M2_nnnnn" jumps to the start address of "M2_nnnnn" in control area 2. Note that "ORG 2000h" at the beginning of the program in control area 2 indicates that the start address of control area 2 is "2000h".
In the program "M2_nnnnn" in control area 2, the first address "LD SP, @STACK2" indicates that stack 2 is set in the SP register (here, this means the SP register of register bank 1 after the register bank has been switched). The initial value of stack 2 (@STACK2) is "F300h" as shown in FIG. 55, and this value is written to the SP register of register bank 1.

The next "CALL M2_ooooo" is an instruction to call program "M2_ooooo." Program "M2_ooooo" is stored in control area 2 (the same area). Here, because the call is to program "M2_ooooo" in the same control area 2, there is no need to switch register banks. For this reason, the CALL instruction is used instead of the CALLEX instruction (unlike the CALL instruction, the register bank is not switched). In Example 1 in Figure 55, register bank 1 is used when executing programs in control area 2 and control area 3. The switch from register bank 0 to register bank 1 has already been executed by the "CALLEX M2_nnnnn" described above.

After the program "M2_oooooo" is terminated (RET command), the RETEX command is executed. This RETEX command corresponds to the "CALLEX M2_nnnnn" command executed in the program of the control area 1.
The RETEX command is
(1) The interrupt state is set to the state before the CALLEX instruction.
(2) Switch the register bank from register bank 1 to register bank 0,
(3) Return (RET) (return to the next instruction after "CALLEX M2_nnnnn" (the program at the return address))
Do this.
On the other hand, the RET instruction, unlike the RETEX instruction, does not change the interrupt state and does not switch register banks.

This returns the program to control area 1 again.
If the state at the time of the CALLEX instruction is an interrupt enabled state, the RETEX instruction puts the state into an interrupt enabled state. On the other hand, if the state at the time of the CALLEX instruction is an interrupt disabled state, the RETEX instruction puts the state into an interrupt disabled state.

In the above program flow, for example, the SP registers of register bank 0 and register bank 1 are as follows:
In the program "M1_aaaaa" in control area 1, "LD SP, @STACK1" executes
SP = F200h (register bank 0)
This becomes:

Next, when some program is executed and, for example, 2 bytes of data are loaded into stack area 1,
SP=F1FEh (register bank 0)
will be updated to.
When "CALLEX M2_nnnnn" is executed with this SP register value, "LD SP, @STACK2" in the program "M2_nnnnn" in control area 2 executes the following:
SP=F300h (register bank 1)
This becomes:

Then, when the program "M2_ooooo" in control area 2 is executed and a stack of, for example, 4 bytes is filled in stack area 2,
SP = F2FCh (register bank 1)
will be updated to.
When the program "M2_ooooo" ends with this SP register value and the RETEX instruction is used to return to the program in control area 1, the register bank used in the program in control area 1 becomes register bank 0, and the SP register value at that point becomes "F1FEh."
Even when the program "M2_ooooo" in control area 2 ends and returns to the program in control area 1 by the RETEX instruction, the SP register value in register bank 1 remains "F2FCh."

Next, in the program "M1_aaaaa" in the control area 1, "CALLEX M3_xxxxx" is a command to call the program "M3_xxxxx." In this example, the program "M3_xxxxx" is stored in the control area 3.
Note that this "CALLEX M3_xxxxx" switches the register bank from register bank 0 to register bank 1 again.
Execution of "CALLEX M3_xxxxx" jumps to the start address of "M3_xxxxx" in control area 3. Note that "ORG 2A00h" at the beginning of control area 3 indicates that the start address of control area 3 is "2A00h".

In the program "M3_xxxxx" in control area 3, "LD SP, @STACK3" indicates that stack 3 is set in the SP register (here, this means the SP register of register bank 1). The initial value of stack 3 (@STACK3) is "F400h" as shown in FIG. 55, and this value is written to the SP register of register bank 1. Therefore, as described above, the value of the SP register of register bank 1 immediately before "LD SP, @STACK3" is "F2FCh", but this value is overwritten with "F400h".
The following "CALL M3_yyyyy" is an instruction to call the program "M3_yyyyy." The program "M3_yyyyy" is stored in control area 3. As in the above, this CALL instruction does not switch register banks.

Then, after program "M3_yyyyy" ends (RET instruction), the RETEX instruction returns the interrupt state to the state before the "CALLEX M3_xxxxx" instruction, switches the register bank from register bank 1 to register bank 0, and returns (RET). This causes the program to return to the instruction next to "CALLEX M3_xxxxx" (the program at the return address).

In this way, when jumping from a program in control area 1 to a program in control area 2 or control area 3, the register bank is switched by the CALLEX instruction, thereby protecting the registers in register bank 0 that were used in the program in control area 1.
On the other hand, in Example 1, after the program "M2_nnnnn" in control area 2 is executed, the program "M3_xxxxx" in control area 3 is executed. Both the program in control area 2 and the program in control area 3 use register bank 1. Therefore, there is a risk that the register values used in the program in control area 2 may change when the program in control area 3 is executed.

If there is no need to protect register values when moving between the programs in control area 2 and control area 3, no instructions to protect register values are required. On the other hand, if you want to protect registers so that they do not change when a program in control area 3 is executed after a program in control area 2 is executed, or when a program in control area 2 is executed after a program in control area 3 is executed, add instructions to protect the registers before and after the program "CALL M2_ooooo" in control area 2, or before and after the program "CALL M3_yyyyy" in control area 3.

in particular,
In the control area 2 program:
PUSH ALL
CALL M2_ooooo
POP ALL
Or,
In the program of control area 3,
PUSH ALL
CALL M3_yyyyy
POP ALL
Let's say.
Here, as in the third embodiment, "PUSH ALL" is a command statement that saves all registers to the stack area, and "POP ALL" is a command statement that restores all saved registers from the stack area.
Furthermore, "PUSH AF," which will be described later, is a command statement for saving the AF register to the stack area, and "POP AF" is a command statement for restoring the saved AF register from the stack area.
The stack area when saving to or restoring from a stack area refers to stack area 1 shown in FIG. 52 when "PUSH ALL", "POP ALL", "PUSH AF", or "POP AF" is issued as an instruction in control area 1; stack area 2 shown in FIG. 52 when "PUSH ALL", "POP ALL", "PUSH AF", or "POP AF" is issued as an instruction in control area 2; and stack area 3 shown in FIG. 52 when "PUSH ALL", "POP ALL", "PUSH AF", or "POP AF" is issued as an instruction in control area 3.

Figure 56 shows example 2 of programs in control area 1, control area 2, and control area 3. In example 2, the programs in control area 1 and control area 2 use register bank 0, and the program in control area 3 uses register bank 1. Therefore, when a program in control area 1 calls and executes a program in control area 2, register bank 0 remains. In contrast, when a program in control area 1 calls and executes a program in control area 3, the register bank switches from register bank 0 to register bank 1. Then, when the program in control area 3 is terminated and the program in control area 1 is returned to, the register bank switches (back) from register bank 1 to register bank 0.

In FIG. 56, the program in control area 1 is as follows:
The initial "ORG 0000h" is the same as in Example 1.
"M1_aaaaa" indicates the program at the first address of control area 1.
In this program, "LD SP, @STACK1" is an instruction to set stack 1 in the SP register, similar to Example 1.
After that, the program "M2_nnnnn" in control area 2 is executed, but since both the program in control area 1 and the program in control area 2 use register bank 0, the CALLEX instruction, which involves switching register banks, is not used. In other words, the CALL instruction is used in this case. The CALL instruction does not switch register banks.

When a program in control area 2 is executed while a program in control area 1 is being executed, interrupt processing is prohibited. The interrupt prohibit instruction is the DI instruction in the figure.
After the DI instruction is executed, "PUSH AF" is executed to save the AF register (store it in the stack area). After that, "CALL M2_nnnnn" is executed to execute the program "M2_nnnnn" in control area 2.
The reason for saving the AF register is as follows. When jumping to the program "M2_nnnnn" in control area 2, the instruction "LD SP, @STACK2" that sets the stack pointer is executed, as will be described later. When this LD instruction is executed, the value of the second zero flag (see FIG. 43) in the flag (F) register changes, or there is a risk that it will change. Therefore, the AF register is saved before jumping to the program in control area 2.

The "ORG 2000h" at the beginning of control area 2 is the same as in Example 1.
In "M2_nnnnn" in control area 2, "LD (BF_STACK), SP" is an instruction to save the stack pointer. This process corresponds to the process of storing the current SP register value in a specified memory area (BF_STACK) in RWM area 2 shown in FIG. 52. Because the same register bank 0 is used for the programs in control area 1 and control area 2, when jumping from the program in control area 1 to the program in control area 2, the stack pointer used when the program in control area 1 was being executed is saved and a stack pointer for the program in control area 2 is set.

In other words, the CALL instruction does not switch register banks, and the programs in control area 1 and control area 2 use registers from the same register bank (for example, the SP register). Therefore, if the registers are not saved using "LD (BF_STACK), SP," the register pointers used by the program in control area 1 will be overwritten by the execution of the program in control area 2, and when the program in control area 1 is returned to after the program in control area 2 has finished, the correct stack pointer in the program in control area 1 will no longer be specified.

The next "LD SP, @STACK2" indicates that stack 2 (F300h) is to be set in the SP register, as in Example 1 above.
As described above, "PUSH ALL" is an instruction to save all registers.
The next "CALL M2_ooooo" is an instruction to call the program "M2_ooooo." The program "M2_ooooo" is stored in control area 2. A normal CALL instruction does not switch register banks, so register bank 0 remains the same even while the program "M2_ooooo" is being executed.
When the program "M2_ooooo" is finished, all saved registers are restored by "POP ALL."

The next instruction, "LD SP, (BF_STACK)," is a command to restore the saved stack pointer. This process corresponds to the process of storing the data stored in a specific storage area (BF_STACK) in the RWM area 2 shown in FIG. 52 in the SP register (setting it as the SP register value). As a result, the stack pointer returns to the value it had before the "LD (BF_STACK), SP" instruction, in other words, the value it had when the program in the control area 1 was being executed.
Thereafter, the RET command is used to return to the program in control area 1.
When returning to the program in control area 1, the saved AF register is restored by "POP AF", which returns the AF register to the value it had before the program "M2_nnnnn" was executed.
Next, the EI instruction is used to resume the interrupts that were previously disabled.

The setting, saving, and restoring of the stack pointer will now be explained using a specific example.
First, in the program "M1_aaaaa" in the control area 1, "LD SP, @STACK1" executes
SP = F200h (register bank 0)
This becomes:
Next, when some program is executed and 1 byte of data is stored in "F200h",
SP=F1FFh (register bank 0)
will be updated to.
With this SP register value, "CALL M2_nnnnn" is executed, and when the program "M2_nnnnn" in control area 2 is executed, "LD (BF_STACK), SP" saves the stack pointer "F1FFh" in the program in control area 1. In this case, "F1FFh" is stored in a specified storage area in RWM area 2.

Next, "LD SP, @STACK2"
SP=F300h (register bank 0)
This becomes:
Therefore, the SP is updated from the previous "F1FFh" to "F300h".
Then, when the program "M2_ooooo" is executed and a stack of, for example, 2 bytes is added,
SP=F2FEh (register bank 0)
will be updated to.

Next, when the program "M2_ooooo" is terminated and "LD SP, (BF_STACK)" is executed, "F1FFh" stored in the predetermined storage area is read and stored (overwritten) in SP. In other words, SP is updated from "F2FEh" to "F1FFh".
Therefore,
SP=F1FFh (register bank 0)
This becomes:

Next, in the program of control area 1, execution of "CALLEX M3_xxxxx" causes a jump to "M3_xxxxx" in control area 3. This CALLEX instruction also disables interrupts and switches the register bank from register bank 0 to register bank 1.
"ORG 2A00h" at the beginning of control area 3 is the same as in Example 1.
In "M3_xxxx" of control area 3, "LD SP, @STACK3" sets stack 3 (F400h) in the SP register (SP register of register bank 1).
The following "CALL M3_yyyyy" is an instruction to call the program "M3_yyyyy." The program "M3_yyyyy" is stored in control area 3. As in the above, this CALL instruction does not switch register banks.

Then, after program "M3_yyyyy" ends (RET instruction), the RETEX instruction returns the interrupt state to the state before the "CALLEX M3_xxxxx" instruction, switches the register bank from register bank 1 to register bank 0, and returns (RET). This causes the program to return to the instruction next to "CALLEX M3_xxxxx" (the program at the return address).

Figure 57 shows example 3 of programs in control area 1, control area 2, and control area 3. In example 3, the programs in control area 1 and control area 3 use register bank 0, and the program in control area 2 uses register bank 1. Therefore, when a program in control area 1 calls and executes a program in control area 3, register bank 0 remains. In contrast, when a program in control area 1 calls and executes a program in control area 2, the register bank switches from register bank 0 to register bank 1. Then, when the program in control area 2 is terminated and the program in control area 1 is returned to, the register bank switches (back) from register bank 1 to register bank 0.

In FIG. 56, the program in control area 1 is as follows:
The initial "ORG 0000h" is the same as in Example 1.
In the next "M1_aaaaa", "LD SP, @STACK1" is an instruction to set stack 1 (F200h) in the SP register, similar to Example 1.
The next "CALLEX M2_nnnnn" is an instruction to call the program "M2_nnnnn" in control area 2. This CALLEX instruction disables interrupts and switches the register bank from register bank 0 to register bank 1.
Execution of "CALLEX M2_nnnnn" jumps to program "M2_nnnnn" in control area 2. Note that "ORG 2000h" at the beginning of control area 2 is the same as in Example 1.
In "M2_nnnnn" of control area 2, "LD SP, @STACK2" is an instruction to set stack 2 (F300h) in the SP register (SP register of register bank 1), similar to example 1.

The next "CALL M2_ooooo" is an instruction to call the program "M2_ooooo." The program "M2_ooooo" is stored in control area 2. The CALL instruction does not switch register banks.
After the program "M2_ooooo" is terminated (RET instruction), the RETEX instruction is executed. The RETEX instruction returns the interrupt state to the state before the CALLEX instruction, switches the register bank from register bank 1 to register bank 0, and returns (RET). This returns to the instruction (program at the return address) next to "CALLEX M2_nnnnn" in control area 1. Then, the program in the first control area becomes executable again.

In control area 1, after the program "M2_nnnnn" is executed, the program "M3_xxxxx" in control area 3 is executed.
Since both the program in control area 1 and the program in control area 3 use register bank 0, the CALLEX instruction that involves switching of register banks is not used.
When a program in control area 3 is executed while a program in control area 1 is being executed, first, interrupt processing is inhibited by a DI instruction.
After the DI instruction is executed, the AF register is saved (stored in the stack area) by the "PUSH AF" instruction. Then, the program "M3_xxxxx" in the control area 3 is executed by "CALL M3_xxxxx".

"ORG 2A00h" at the beginning of control area 3 is the same as in Example 1.
In "M3_xxxxx" in control area 3, "LD (BF_STACK), SP" is an instruction to save the stack pointer. This process corresponds to the process of storing the current SP register value in a specified memory area (BF_STACK) in RWM area 3 shown in FIG. 52. Because the same register bank 0 is used for the programs in control area 1 and control area 3, when jumping from the program in control area 1 to the program in control area 3, the stack pointer used when the program in control area 1 was being executed is saved and a stack pointer for the program in control area 3 is set.

"LD SP, @STACK3" indicates that stack 3 (F400h) is set in the SP register, similar to Example 1 above.
Next, all registers are saved by "PUSH ALL".
The next "CALL M3_yyyyy" is an instruction to call the program "M3_yyyyy." The program "M3_yyyyy" is stored in control area 3. The CALL instruction does not switch register banks, so register bank 0 remains the same even during execution of the program "M3_yyyyy."
When the program "M3_yyyyy" is finished, all saved registers are restored by "POP ALL."

The next instruction, "LD SP, (BF_STACK)," is a command to restore the saved stack pointer. This process corresponds to the process of storing the data stored in a specific storage area (BF_STACK) in the RWM area 3 shown in FIG. 52 in the SP register (setting it as the SP register value). As a result, the stack pointer returns to the value it had before the "LD (BF_STACK), SP" instruction, in other words, the value it had when the program in the control area 1 was being executed.
Thereafter, the RET command is used to return to the program in control area 1.
When returning to the program in control area 1, the saved AF register is restored by "POP AF", which returns the AF register to the value it had before the program "M2_nnnnn" was executed.
Then, the EI instruction resumes the interrupts that were previously disabled.

Next, we will explain the code size of the program.
In the fourth embodiment, the code search for each instruction is as follows:
CALLEX mn (mn = 2000h to 20FFh): 2 bytes CALLEX mn (mn ≠ 2000h to 20FFh): 4 bytes RETEX: 2 bytes CALL mn: 3 bytes RET: 1 byte DI: 1 byte EI: 1 byte PUSH AF: 1 byte POP AF: 1 byte

The code size of the CALLEX instruction is the same as in the third embodiment, but will be explained again.
In the CALLEX instruction, the code size of "CALLEX mn" when calling an address range of "2000h" to "20FFh" is 2 bytes, and the code size of "CALLEX mn" when calling an address range other than "2000h" to "20FFh" is 4 bytes.

The range of addresses "2000h" to "20FFh" is "FFh", i.e., 1 byte. In this case, the code value of the address value "2000h" is set to "0h". This allows the code value when calling the address value "20FFh" to be "FFh", so the code size of "mn" can be set to 1 byte regardless of which address in the range of addresses "2000h" to "20FFh" is called.
Furthermore, when encoding the opcode of "CALLEX," the code is set to 1 byte. This allows the code size of "CALLEX mn" (mn=2000h to 20FFh) to be set to 2 bytes.

On the other hand, when "mn" is "2100h" or greater, the code size of "mn" becomes 2 bytes. Furthermore, if "mn" is not in the range of "2000h" to "20FFh," the "CALLEX" code is composed of 2 bytes. If the opcode were composed of 1 byte, there would be a limit of 256 out of several thousand instructions, so a 1-byte code is assigned as the "CALLEX" code when "mn" is in the range of "2000h" to "20FFh," but a 2-byte code is assigned as the "CALLEX" code when "mn" is not in the range of "2000h" to "20FFh."

As described above, the "CALLEX mn" instruction has a code size of 2 bytes if "mn" is in the range of "2000h" to "20FFh," and a code size of 4 bytes if "mn" is outside the above range.
Therefore, if instructions that are called more frequently are concentrated within the address range of "2000h" to "20FFh" in the control area 2, more of the instructions will have a code size of just 2 bytes. This makes it possible to save memory capacity in the control area 1.
Furthermore, by storing as many addresses as possible in the range of addresses "2000h" to "20FFh" of the second control area, which are used when a program in control area 1 calls a program in control area 2, within the range of addresses "2000h" to "25FFh," it is possible to easily determine when checking control area 2 that it is a program called from a program in control area 1.

A specific explanation will be given using Figure 55 (Example 1) as an example.
As shown in Figure 55, the starting address of control area 2 is "2000h." The starting address of control area 3 is "2A00h." Therefore, for example, if the program "M2_nnnnn" of control area 2 is located within the address range of "2000h" to "20FFh," the program "CALLEX M2_nnnnn" of control area 1 can be composed of 2 bytes.
In addition, in the program "M2_nnnnn" in control area 2, after "LD SP, @STACK2", "CALL M2_oooooo" is executed to call the program "M2_oooooo" in control area 2. Note that the program "M2_oooooo" does not need to be within the address range of "2000h" to "20FFh".

Here, in the program of control area 1, it is also conceivable to directly use "CALLEX M2_ooooo" instead of "CALLEX M2_nnnnn".
However, if the program in control area 2 places the program "M2_ooooo" that is actually executed after address "2100h" and places many of the top programs called by the CALLEX instruction in control area 1 in the address range from "2000h" to "20FFh," it becomes possible to provide many 2-byte CALLEX instructions in the program in control area 1. This makes it possible to save the program capacity of control area 1. In other words, the program in control area 1 does not need to call the program in control area 2 only once, but may be configured to be called multiple times.

The starting address of the program in control area 3 is "2A00h", which is after "20FFh". Therefore, the program "M3_xxxxx" in control area 3 is located at address "20FFh" and after. As a result, the program "CALLEX M3_xxxxx" in control area 1 is 4 bytes. In other words, since there is no address range between "2000h" and "20FFh" in control area 3, the code size of the CALLEX instruction when calling a program in control area 3 from a program in control area 1 is always 4 bytes. Note that the program in control area 3 is not limited to being called once from the program in control area 1, and may be configured to be called multiple times.

Here, when calling the program "M3_xxxxx" using a normal CALL command,
DI (1 byte)
PUSH AF (1 byte)
CALL M3_xxxxxx (3 bytes)
POP AF (1 byte)
EI (1 byte)
This amounts to a total of 7 bytes, which is larger than the 4-byte CALLEX instruction. Therefore, even when a program in control area 1 calls a program in control area 3, using the CALLEX instruction rather than the CALL instruction can reduce the size.

Although the fourth embodiment of the present invention has been described above, the present invention is not limited to the above embodiment and various modifications such as those described below are possible.
(1) In order to provide more 2-byte "CALLEX mn (mn=2000h to 20FFh)" in the program of the control area 1, the JR (jump) instruction shown in FIG. 50 of the third embodiment may be used.
58 shows an example of a program in this case. The code size of the JR instruction is assumed to be 3 bytes, as in the third embodiment.

Then, a JR instruction is placed at the address in control area 2 specified by the CALLEX instruction in control area 1. For example, if "CALLEX 2000h" is specified in the program in control area 1, "JR 2100h" is placed at address "2000h" in control area 2. In other words, the jump destination address is set to "2100h" or later.
Since the "JR mn" instruction requires three bytes, "JR mn" is arranged in 3-byte increments from address "2000h" onwards in the control area 2.
The actual program can then be placed in the control area 2 from address 2100h onwards.
By setting it in this way, it is possible to provide as many 2-byte CALLEX instructions as possible in the program in the control area 1.

(2) In Example 1 of Figure 55 to Example 3 of Figure 57, control area 1 calls the program "M2_nnnnn" of control area 2, and after this "M2_nnnnn" is terminated, it calls the program "M3_xxxxx" of control area 3 and executes this "M3_xxxxx". However, the order and timing of the processes for executing the programs of control area 2 and control area 3 can be redesigned as appropriate.
For example, after executing a program in control area 2, a program in control area 1 may be executed, and then a program in control area 3 may be executed at a certain processing timing, or after executing a program in control area 3, a program in control area 1 may be executed, and then a program in control area 2 may be executed at a certain processing timing.
As described above, the number of times that a program in control area 1 calls a program in control area 2 is not limited to one time, but may be multiple times. Similarly, the number of times that a program in control area 1 calls a program in control area 3 is not limited to one time, but may be multiple times.

(3) The fourth embodiment can be applied not only to medalless gaming machines but also to slot machines and pachinko gaming machines under the Entertainment and Amusement Act. Furthermore, it can also be applied to Parrot and casino machines that use gaming balls.
(4) The first to fourth embodiments and the various modifications shown in the first to fourth embodiments are not limited to being implemented alone, but can also be implemented in appropriate combinations.

Fifth Embodiment
Next, a fifth embodiment of the present invention will be described. In the fifth embodiment, the terms "main control means" and "game media number control means" are used.
In the fifth embodiment, the main control board (for example, "main control board 50" in Figure 29), the gaming media number control board (for example, "gaming media number control board 100" in Figure 29), and the CPUs mounted on these control boards, and the main control means and gaming media number control means in each case, can be exemplified by the following first to third examples.
(1) First Example As shown in Figure 29 (second embodiment), an example is one in which the system is divided into a main control board 50 and a game media number control board 100, with a main control CPU (corresponding to "first main control CPU 55" in Figure 29) mounted on the main control board 50 and a game media number control CPU (corresponding to "second main control CPU 105" in Figure 29) mounted on the game media number control board 100.
In this case, the main control CPU corresponds to the "main control means" in this embodiment, and the gaming media number control CPU corresponds to the "gaming media number control means."

(2) Second Example As shown in Figure 51 (fourth embodiment), a game media number control board is not provided, but a main control board 50 is provided, and further, although different from the configuration in Figure 51, a main control CPU and a game media number control CPU may be mounted separately on the main control board 50.
In this case, the main control CPU corresponds to the "main control means" of this embodiment, and the game media number control CPU corresponds to the "game media number control means" of this embodiment.

(3) Third Example As shown in Figure 51 (fourth embodiment), there is no game media number control board, but a main control board 50 is provided, and further, as shown in Figure 51, there is an example in which only one CPU (corresponding to "main CPU 501" in Figure 51) is mounted on the main control board 50 (no game media number control CPU is mounted).
In this case, among the means possessed by the main CPU 501, the means for controlling the progress of the game corresponds to the "main control means" in this embodiment. Also, among the means possessed by the main CPU 501, the means for controlling the game media corresponds to the "game media number control means" in this embodiment.

Furthermore, the term "main control RWM" refers to an RWM that stores data related to main control and can be accessed by main control means, and corresponds to, for example, main control RWM 503 in Fig. 51. The term "main control ROM" refers to a ROM that stores data and programs related to main control and can be accessed by main control means, and corresponds to, for example, main control ROM 502 in Fig. 51.
Furthermore, "game media number control RWM" refers to an RWM that stores data related to the control of the number of game media and can be accessed by a game media number control means, and corresponds, for example, to the second main control RWM 103 in Figure 29 or the game media number control RWM 505 in Figure 51.
In addition, "game media number control ROM" refers to a ROM that stores data and programs related to controlling the number of game media and can be accessed by a game media number control means, and corresponds, for example, to the second main control ROM 104 in Figure 29 or the game media number control ROM 504 in Figure 51.

Furthermore, in the explanation of the fifth embodiment, the sub-control CPU 85 (means for controlling the performance) in Fig. 29 and Fig. 51 is referred to as "sub-control means." Also, "sub-control RWM" refers to an RWM that stores data related to sub-control (performance) and can be accessed by the sub-control means, and corresponds to the sub-control RWM 83 in Fig. 51, for example.
Furthermore, "sub-control ROM" refers to a ROM that stores data and programs related to sub-control (performance) and can be accessed by the sub-control means, and corresponds to, for example, sub-control ROM 84 in Figure 51.

The gaming media number control means manages the total number of gaming media (credited (accumulated)).
In the fifth embodiment, the game media count control means determines whether the total number of game media has exceeded the upper limit and reached the threshold, and executes a predetermined process based on the determination result. In other words, the game media count control means determines whether the total number of game media has fallen below the upper limit and below the threshold, and executes a predetermined process based on the determination result.
The game media number control means determines whether or not an upper limit value and a threshold value have been reached when adding a predetermined number of game media to the total number of game media.
Here, "addition of the total number of gaming media" is performed firstly when gaming media corresponding to the winning small combination are awarded. Secondly, it is performed when the settlement switch 46 is operated when gaming media have been bet. And thirdly, it is performed when gaming media are loaned from the loan unit 200. Here, the determination of whether the upper limit value and the threshold value have been reached may be made when "1" is added to the gaming media, or when the process of adding a predetermined number of gaming media has been completed.
Furthermore, "subtraction of the total number of gaming media" is firstly performed based on betting processing, and secondly performed based on counting processing. Furthermore, the determination of whether the upper limit value and the threshold value have been exceeded may be made when subtracting "1" from the gaming media, or when the betting processing or counting processing of a predetermined number of gaming media has been completed.

In the following description, the upper limit value is assumed to be "16383". However, the upper limit value "16383" is merely an example and is not limited to this. For example, the upper limit value may be "32767" or "65535".
Furthermore, in the following explanation, the threshold value is assumed to be "15000". However, the threshold value "15000" is an example, and any value less than the upper limit value can be set. For example, the threshold value can be set to any value less than "upper limit value (16383) - one count value (50)" (less than "16333").

In the fifth embodiment, when the total number of game media reaches the upper limit, the total number of game media is not further increased. Specifically, when the total number of game media reaches the upper limit during the game media granting process, the granting process is suspended until the total number of game media falls below the upper limit. Furthermore, when the total number of game media reaches the upper limit, the game media lending process is not performed until the total number of game media falls below the upper limit.
For example, when the total number of game media before adding "1" to the game media is "16,382," it is possible to add "1" to the game media and update the total number of game media to "16,383 (upper limit)." On the other hand, when the total number of game media before adding "1" to the game media is "16,383 (upper limit)," the process of adding "1" to the game media is not performed.
In addition, in the fifth embodiment, when the total number of gaming media reaches the threshold value of "15,000", a predetermined control process (for example, an alarm process or a process prohibiting the lending of gaming media) can be executed, and when the total number of gaming media falls below the threshold value, the predetermined control process can be terminated.

Next, a specific control process for the upper limit of the number of game media will be described.
The main control means and the game media count control means each have an upper limit flag for determining whether the total number of game media has reached (is equal to or greater than) the upper limit. The upper limit flag is provided in a predetermined storage area of the main control RWM and the game media count control RWM.
When the gaming media count control means determines that the upper limit has been reached as a result of adding "1" to the total number of gaming media, it sets an upper limit reached flag to "1." When the gaming media count control means sets the upper limit reached flag to "1," it transmits upper limit reached information to the main control means.

When the main control means receives the upper limit value reaching information from the game medium count control means, the main control means sets the upper limit value reaching flag to "1." When the main control means sets the upper limit value reaching flag to "1," the main control means transmits upper limit value reaching information (also referred to as "notification request information"; the same applies hereinafter) to the sub-control means.
The sub-control means has an upper limit notification flag. The upper limit notification flag is provided in a predetermined storage area of the sub-control RWM. When the sub-control means receives upper limit reaching information from the main control means, the sub-control means sets the upper limit notification flag to "1."
When the upper limit notification flag is "1", the sub-control means issues a notification (hereinafter referred to as "upper limit reached notification", also referred to as "error notification") that the total number of gaming media has reached the upper limit using at least one of the effect lamp 21, speaker 22, or image display device 23.

On the other hand, when the game medium number control means detects the operation of the counting switch 47, it subtracts the number of game media corresponding to the operation of the counting switch 47 from the total number of game media.
The game media number control means subtracts "1" from the total number of game media based on the operation of the counting switch 47, and when it determines that the total number of game media is less than the upper limit, it sets the upper limit reached flag to "0." When the game media number control means sets the upper limit reached flag to "0," it transmits upper limit not reached information to the main control means.
When the main control means receives the upper limit value not reached information from the game medium count control means, the main control means sets the upper limit value reached flag to "0." When the main control means sets the upper limit value reached flag to "0," the main control means transmits the upper limit value not reached information to the sub-control means.

When the sub-control means receives the upper limit not reached information from the main control means, the sub-control means sets the upper limit notification flag to "0." When the upper limit notification flag is "0," the sub-control means does not need to issue an upper limit reached notification (error notification). Therefore, when the upper limit notification flag changes from "1" to "0," the sub-control means can terminate the upper limit reached notification.
The sub-control means may immediately terminate the upper limit value reaching notification when the upper limit value notification flag changes from "1" to "0", or may continue the upper limit value reaching notification immediately after the upper limit value notification flag changes from "1" to "0", and terminate the upper limit value reaching notification when a predetermined condition is met, such as after a predetermined period has passed since the upper limit value notification flag changed from "1" to "0".

Specifically, when the sub-control means determines that the upper limit notification flag has changed from "1" to "0", it stores a predetermined value in a predetermined timer value storage area provided in the sub-control RWM, and executes a process of subtracting "1" for each interrupt process in the sub-control means (for example, every "1" ms).
The sub-control means continues the upper limit value reaching notification when the value in the predetermined timer value storage area is not 0. When the value in the predetermined timer value storage area becomes 0, the sub-control means determines that the predetermined termination condition for the upper limit value reaching notification is satisfied and terminates the upper limit value reaching notification.

Next, the process of providing game media will be described.
FIG. 59 is a flowchart showing the game media providing process by the main control means.
This game medium awarding process is executed after determining the symbol combination that has stopped on the pay line and determining the number of game media to be awarded based on the determination result. For example, when it is determined that a predetermined (minor winning) symbol combination that can award the number of game media "8" has stopped on the pay line, "8" is stored in the number of awarded game media storage area described later, and then this game medium awarding process is executed.

In Figure 59, in step S741, the main control means determines whether there are any gaming media to be awarded (whether a symbol combination that can award gaming media has stopped and displayed), and if it determines that there are no gaming media to be awarded, it terminates processing according to this flowchart. Specifically, the main control RWM has an award number memory area in which the award number is stored when the award number is determined, and determines whether the value in this award number memory area is "0". If it determines that the value in the award number memory area is "0", it terminates processing according to this flowchart. On the other hand, if it determines that the value in the award number memory area is not "0", it proceeds to step S742.

In step S742, it is determined whether the gaming medium provision timer value is 0. The gaming medium provision timer is provided in a predetermined storage area of the main control RWM.
If the gaming medium provision timer value is not "0", the determination in step S742 is looped until it becomes "0", and if it is determined that it is "0", the process proceeds to step S743. In other words, the process in step S742 is a process that delays the process from step S743 onwards (the provision request command set in step S744, which will be described later).

When the game media dispensing timer value is determined to be "0" and processing proceeds to step S743, the main control means stores the initial value "27" as the game media dispensing timer value. The game media dispensing timer value is configured to be updatable in response to the execution of timer interrupt processing by the main control means (for example, it is configured to subtract "1" each time timer interrupt processing is executed). Note that timer interrupts by the main control means are configured to be executed at intervals of approximately "2.235" ms. Therefore, storing "27" as the game media dispensing timer value is equivalent to saving a time corresponding to approximately "60" ms. Furthermore, even if timer interrupt processing is executed when the game media dispensing timer value is "0," the game media dispensing timer value will remain "0."

In this way, by executing the processing for saving the game media granting time in step S743 after determining whether the game media granting time in step S742 has elapsed, when multiple game media are granted, the grant request command set processing in step S744 described below will be executed at predetermined intervals (in the above example, approximately every 60 ms).
For example, when the number of game media to be awarded is "8," when the first game medium "1" is awarded, the standby process based on the game medium awarding timer value is not executed. At the time of transition to the process of the flowchart of FIG. 59, the game medium awarding timer value is "0," and the determination in step S742 is "Yes," so the awarding process of the first game medium "1" is executed immediately. This allows the main control means to promptly cause the game medium count control means to execute the process of adding the first game medium "1" to the total number of game media.

On the other hand, when the first game medium "1" is awarded, "27" is stored as the game medium award timer value in step S743. Therefore, each award request command set corresponding to game media "2" through "8" can be executed after the game medium award timer value changes from "27" to "0." In other words, each award request command set corresponding to game media "2" through "8" (step S744) can be executed approximately every "60" ms. In other words, the total game media can be updated by the game media count control means based on the award request command set approximately every "60" ms, and the display of the game media number display unit 121, which can display the total number of game media, can also be updated approximately every "60" ms. This configuration allows the player to visually see the total number of game media displayed on the game media number display unit 121 being updated (counted up) by "1" at a time.

59, after the game medium granting time is saved in step S743, a process of determining whether the game medium granting time has elapsed in step S742 may be executed. In this case, even when granting the first game medium in a case where multiple game media are granted, the main control means executes a standby process corresponding to the game medium granting time (game medium granting timer value), and then the game medium number control means adds "1" to the total number of game media.
Also, in the above example, "27" was stored as the gaming media granting timer value in the processing of step S743, but any number (for example, a number in the range of approximately "10" to "200") that allows the player to visually see how the total gaming media displayed on the gaming media number display unit 121 is updated by "1" may also be stored.

In the next step S744, the main control means stores an award request command indicating that the number of gaming media "1" is to be awarded in the command buffer of the main control means. The command stored in the command buffer of the main control means is configured to be sent to the gaming media count control means by timer interrupt processing on the main control means side. Therefore, the processing of step S744 is equivalent to sending an award request command indicating that the number of gaming media "1" is to be awarded from the main control means to the gaming media count control means.

For example, if a symbol combination capable of awarding eight game media is displayed, the total number of game media is updated by sending eight award request commands to the game media count control means indicating that one game medium should be awarded. By updating the total number of game media by one in this way, game media can be awarded until the total number of game media reaches the upper limit (16,383) even if adding all the game media to be awarded would exceed the upper limit (16,383) for the total number of game media.

In the next step S745, the main control means receives a response command. In step S744, the main control means transmits a grant request command to the game media count control means. When the game media count control means receives the command, the main control means transmits a response command corresponding to the grant request command.
In the fifth embodiment, the game media count control means has at least the following two response commands.
1) Grant permission command The grant permission command is a command that indicates (permits) the addition of "1" to the number of game media.
Specifically, after receiving an award request command indicating that the number of game media "1" should be awarded, if the game media number control means determines that the total number of game media before the addition has not reached the upper limit value when adding "1" to the total number of game media, it sends an award permission command to the main control means indicating that "1" should be added to the total number of game media.

2) Grant Refusal Command The grant refusal command is a command indicating that the number of game media "1" should not be added (addition is not permitted, addition is prohibited).
Specifically, after receiving an award request command indicating that the number of game media "1" should be awarded, if the game media count control means determines that the total number of game media before the addition has reached the upper limit when adding "1" to the total number of game media, it sends an award refusal command to the main control means indicating that "1" cannot be added to the total number of game media. Here, when the game media count control means receives the award request command and determines that the total number of game media before the addition has reached the upper limit, it sends an award refusal command to the main control means without adding "1" to the total number of game media.

In the next step S746, the main control means determines whether the command received from the gaming medium count control means is a grant refusal command, and if it is a grant refusal command, proceeds to step S742, and if it is not a grant refusal command, proceeds to step S747. Note that in step S746, the main control means may also determine whether the command received from the gaming medium count control means is a grant permission command, and if it is not a grant permission command, proceeds to step S742, and if it is a grant permission command, proceeds to step S747.

By configuring in this manner, if the main control means determines in step S746 that gaming media cannot be awarded, the gaming media count control means executes a counting process (counting some or all of the total number of gaming media), and loops between steps S742 and S746 until the total number of gaming media falls below the upper limit. As a result, the system does not proceed to betting processing to start the next game (betting processing cannot be performed). Even if such a loop situation occurs, the gaming media count control means executes a counting process, and if the total number of gaming media falls below the upper limit, the gaming media count control means sends an award permission command to the main control means, so that the determination in step S746 becomes "No", making it possible to proceed to processing in step S747.

In other words, even if the total number of game media reaches the upper limit of 16,383 during the game media dispensing process (when some of the game media to be dispensed remain), the game media dispensing process will not terminate, resulting in a loop. Even in this loop, the player can operate the counting switch 47 to execute the counting process, making it possible to reduce the total number of game media to less than the upper limit of 16,383. In other words, if the total number of game media falls below the upper limit of 16,383, the game media dispensing process can be released from the loop (step S746 returns "No"), allowing the game media dispensing process to continue. This configuration prevents the game media to be dispensed from being discarded, even if the total number of game media reaches the upper limit of 16,383 during the game media dispensing process, thereby preventing any disadvantage to the player.

Note that the above-mentioned loop status is not limited to this example. For example, if the answer is "Yes" in step S746, the system may loop through step S744 (set grant request command), step S745 (receive command), and step S746 (determine whether grant is not possible).

In step S747, the main control means subtracts "1" from the value in the grant count storage area. For example, if the value stored in the grant count storage area is "8," this process will change the value in the grant count storage area to "7." Also, if the value stored in the grant count storage area is "1," this process will change the value in the grant count storage area to "0."

Next, the process proceeds to step S748, where the main control means determines whether the value in the grant count storage area is "0." If the value in the grant count storage area is not "0," the process returns to step S742. On the other hand, if it is determined in step S748 that the value in the grant count storage area is "0," the process according to this flowchart ends.

By executing the game media providing process as described above, the total number of game media can be controlled to be equal to or less than the upper limit value.
Furthermore, if the process of awarding game media one by one is performed at high speed, the player will not be able to recognize that game media have been awarded one by one. For this reason, after awarding one game medium, the game medium awarding timer value is set to 60.35 ms (27 interrupt processes), and the game medium awarding timer value is updated each time one game medium is awarded, and one game medium is again awarded after 60.35 ms has elapsed. This configuration allows the player to recognize that one game medium has been awarded one by one, thereby increasing the player's interest in the game.

FIG. 60 is a flowchart showing the game media providing process of the game media number control means.
First, in step S751, the game media count control means determines whether or not it has received a grant request command transmitted from the main control means. In Figure 59, when a grant request command is transmitted in step S744, the game media count control means receives the grant request command in step S751.
If a grant request command has been received, the process proceeds to step S752. In step S752, the game media count control means determines whether the total number of game media before adding "1" to the number of game media is at the upper limit. If it is determined that the total number of game media is not at the upper limit, the process proceeds to step S753. If it is determined that the total number of game media is already at the upper limit, the process proceeds to step S755.

In step S753, the game media count control means transmits a grant permission command to the main control means. Next, the process proceeds to step S754, where "1" is added to the total number of game media, updating the total number of game media. The process according to this flowchart then ends. Note that the processes in steps S753 and S754 may be reversed.
On the other hand, if the process proceeds to step S755, the game media count control means sends a grant refusal command to the main control means, and the process according to this flowchart ends. Therefore, in this case, the total game media count is not updated (adding "1").

In the above example, the number of game media is incremented by "1", but this is not limiting, and "2" or more (plural) game media may be incremented together.
For example, when the main control means awards the number of game media "8," it transmits to the game media count control means a grant request command as to whether or not the number of game media "8" can be added to the total number of game media. Upon receiving the grant request command, the game media count control means determines whether or not adding "8" to the total number of game media will exceed the upper limit (determines whether "total number of game media + number of awarded media >16,383" is "Yes"), and if the upper limit is exceeded (determines "Yes"), it transmits to the main control means a command (a grant refusal command) indicating that "8" cannot be added to the total number of game media. Upon receiving the grant refusal command, the main control means again transmits to the game media count control means a grant request command as to whether or not "8" can be added to the total number of game media.

Here, if the counting process has not been performed, the total number of game media has not decreased, so the game media count control means again sends a command to the main control means indicating that it is not possible to add "8" to the total number of game media, and the game media granting process loops between the main control means and the game media count control means. In other words, the loop continues until the number of game media "8" is added. By using this configuration, the granted game media are not discarded, preventing any disadvantage to the player.
On the other hand, if it is determined that the upper limit is not exceeded, a grant permission command indicating that "8" can be added to the total number of game media is sent to the main control means. The game media count control means then adds "8" to the total number of game media and terminates the game media granting process.

Next, the threshold value for the number of game media (15,000) will be explained.
The game media number control means and the main control means each have a threshold value arrival flag for determining whether the total number of game media has reached a threshold value. The threshold value arrival flag of the main control means is provided in the main control RWM, and the threshold value arrival flag of the game media number control means is provided in the game media number control RWM.
The game media number control means adds "1" to the total number of game media, and when it determines that the threshold value has been reached, sets a threshold value reached flag to "1".
When the game media count control means sets the threshold value arrival flag to "1", it transmits threshold value arrival information (command) to the main control means.
When the main control means receives the threshold value reaching information from the game media number control means, the main control means sets the threshold value reaching flag to "1".
When the main control means sets the threshold value arrival flag to "1", it transmits threshold value arrival information (command) to the sub-control means. In other words, the "threshold value arrival information" here is notification request information.

On the other hand, the sub-control means has a threshold notification flag, which is provided in the sub-control RWM.
When the sub-control means receives threshold value reaching information from the main control means, the sub-control means sets the threshold value notification flag to "1".
When the threshold notification flag is "1", the sub-control means can issue a threshold reaching notification by at least one of the performance lamp 21, the speaker 22, and the image display device 23. The "threshold reaching notification" here is, in other words, a warning notification.
In addition, when the total number of game media has reached the threshold value, the game media count control means transmits an abnormality as a rental receipt result response to the rental unit 200.

When the game medium number control means detects the operation of the counting switch 47, it subtracts the number of game media corresponding to the operation of the counting switch 47 from the total number of game media.
When the game media number control means determines that the result of subtracting "1" from the total number of game media is less than the threshold, it sets the threshold reach flag to "0".
When the threshold value reached flag is "0", the game media count control means transmits threshold value not reached information to the main control means.
When the main control means receives the threshold not reached information from the game media number control means, the main control means sets the threshold reached flag to "0".
When the threshold value reached flag is "0", the main control means transmits threshold value not reached information to the sub-control means.
When the sub-control means receives the threshold unreached information from the main control means, the sub-control means sets the threshold notification flag to "0".
When the threshold notification flag is "0", the sub-control means does not need to notify the user that the threshold has been reached.

The sub-control means may terminate the threshold reach notification immediately when the threshold reach notification flag changes from "1" to "0", or may terminate the threshold reach notification after a predetermined period has elapsed since the threshold reach notification flag changed from "1" to "0". Therefore, the threshold reach notification continues until the predetermined period has elapsed since the threshold reach notification flag changed to "0".
In this case, when the sub-control means determines that the threshold notification flag has changed from "1" to "0", it stores a predetermined value in a predetermined timer value storage area provided in the sub-control RWM, and executes a process of subtracting "1" for each interrupt processing in the sub-control means (for example, every "1" ms).
The sub-control means continues to notify the threshold value reaching notification when the predetermined timer value is not "0".
When the predetermined timer value reaches "0", the sub-control means determines that the condition for terminating the threshold value reaching notification is satisfied, and enables the threshold value reaching notification to be terminated.

The upper limit value reaching information and threshold value reaching information sent from the main control means to the sub-control means may be sent, for example, as one-byte reaching information (command), with specific bits of the reaching information being the upper limit value reaching information and other specific bits being the threshold value reaching information.
For example, among the reach information, the threshold reach information is set to bit D0, which indicates that the threshold has been reached when it is set to "1." Also, the upper limit reach information is set to bit D1, which indicates that the upper limit has been reached when it is set to "1."
In this case, when the reach information is "00000001 (B)", the threshold reach information is "1" and the upper limit reach information is "0", so the information indicates that the threshold has been reached but the upper limit has not been reached.
Furthermore, when the reach information is "00000011(B)", the threshold reach information is "1" and the upper limit reach information is "1", so this is information indicating that the threshold and upper limit have been reached.
It is clear that when the upper limit value is reached, the threshold value is also reached, so the reach information when the upper limit value (and threshold value) is reached may be set to "00000010(B)".

In this way, by differentiating the bit corresponding to the upper limit reaching information from the bit corresponding to the threshold reaching information, the sub-control means can make different notifications based on the value of the reaching information. For example, when the sub-control means receives reaching information in which the threshold reaching information is "1" and the upper limit reaching information is "0", it can display on the image display device 23, "The upper limit will be reached in XX minutes. Please operate the counting switch." Furthermore, when the sub-control means receives reaching information in which the threshold reaching information is "1" and the upper limit reaching information is "1", it can display on the image display device 23, "The upper limit has been reached, so play will be interrupted. Please operate the counting switch."

In addition, when different notifications are made when the threshold value is reached and when the upper limit value is reached, the sub-control means can also display an image of the number of game media remaining until the upper limit value is reached.
For example, the main control means calculates "upper limit value (16383) - current total number of game media = surplus number" and transmits the surplus number to the sub-control means. The sub-control means displays the received surplus number as an image. Alternatively, the main control means transmits only information about the current total number of game media to the sub-control means. When the sub-control means receives the current total number of game media transmitted from the main control means and the threshold reaching information is "1", the sub-control means calculates "upper limit value (16383) - current total number of game media = surplus number" and displays the calculation result (surplus number) as an image.
However, the present invention is not limited to this, and the sub-control means may determine whether the arrival information transmitted from the main control means is "0" or not, and if it determines that the arrival information is not "0", may issue a notification to prompt the user to press the counting switch. In this case, it does not determine whether the upper limit value has been reached, but determines that at least the threshold value has been reached.

Furthermore, the main control means may transmit to the sub-control means arrival information of "1" or "0." When the threshold value has not been reached, the main control means transmits arrival information of "0," and when the threshold value has been reached (regardless of whether the upper limit value has been reached), the main control means transmits arrival information of "1."
In this case, even if the sub-control means receives the arrival information, it can determine that the threshold value has been reached, but cannot determine whether the upper limit value has been reached. Therefore, the sub-control means cannot differentiate the notification effects (notification content) when the threshold value is reached and when the upper limit value is reached. Therefore, when the sub-control means receives the arrival information of "1," it issues a notification that is the same for both when the threshold value is reached and when the upper limit value is reached. In this case, the sub-control means may simply display "Please operate the counting switch" on the image display device 23. This reduces the size of the commands sent from the main control means to the sub-control means, thereby reducing the program size.

If the secondary control means performs the same notification effect when the threshold value is reached and when the upper limit value is reached, it will perform the notification effect based on the threshold value being reached, and then will not suddenly change the nature of the notification effect when the upper limit value is reached. This prevents the player from mistaking that they have lost the amount of gaming media that exceeded the upper limit value, even if gaming media is awarded as a result of a small winning combination and the upper limit value is exceeded (this makes it appear that there is no urgency).

Next, the overflow signal and the overflow test signal will be described.
When the game media count control means determines that the total number of game media has reached the threshold, it turns on the overflow signal (raises the overflow signal). The on state of the overflow signal is maintained until the total number of game media falls below the threshold. When the game media count control means determines that the total number of game media has fallen below the threshold, it turns off the overflow signal (lowers the overflow signal).
The game media count control means transmits an overflow signal to the main control means, and when the main control means determines that the overflow signal is on, it performs processing to output an overflow test signal to a test IF (interface) board.

In the test firing test, when the total number of game media reaches the threshold value, the test IF board is controlled so that it becomes less than the threshold value.
When the process for outputting the overflow test signal to the test IF board is being executed, it is assumed that the counting switch 47 has been operated, and the counting process is executed.
When the main control means starts the process for outputting the overflow test signal, in other words, when it turns on the overflow test signal, it stores the overflow test signal timer value. The overflow test signal timer value is provided in the main control RWM and is used to manage the time for which the overflow test signal is turned on. The process for outputting the overflow test signal is executed until it is determined that the overflow test signal timer value is "0".

When the main control means starts the process of outputting the overflow test signal, it stores an initial value as the overflow test signal timer value and does not subtract from the overflow test signal timer value until it determines that the overflow test signal has turned off. While the overflow signal is being output during a sight firing test, the counting switch signal does not turn off.
When the game media count control means determines that the total number of game media has fallen below the threshold value, it terminates the process of transmitting an overflow signal to the main control means.
When the main control means determines that the overflow signal has turned off (when it detects the falling edge of the overflow signal), it starts decrementing the overflow test signal timer value. The overflow test signal remains on even after the overflow signal has turned off until the overflow test signal timer value reaches "0", at which point it turns off. The overflow test signal timer value can be decremented by "1" for each interrupt process (every "2.235" ms) in the main control means, for example.

The main control means determines whether the overflow test signal timer value before subtraction is "0" or not, and when it determines that the overflow test signal timer value before subtraction is not "0", it turns on the overflow test signal, and when it determines that the overflow test signal timer value before subtraction is "0", it turns off the overflow test signal.
In the above example, the main control means determines whether the overflow test signal timer value before subtraction is "0" or not, and turns on the overflow test signal when it determines that the overflow test signal timer value before subtraction is not "0." However, the present invention is not limited to this, and the main control means may determine whether the overflow test signal timer value after subtraction is "0" or not, and turn on the overflow test signal when it determines that the overflow test signal timer value after subtraction is not "0."

The initial value of the overflow test signal timer value stored when the overflow test signal is turned on can be set to "1209," for example. Because the main control means interrupt time interval is 2.235 ms, 2702.115 ms will pass if the interrupt process is executed 1209 times. Therefore, after the overflow signal is turned off, the overflow test signal will be output for 2702.115 ms.

The transmission interval of the gaming machine information notification transmitted by the gaming media number control means to the lending unit 200 is "300" ms. Therefore, the gaming machine information notification is transmitted nine times during "2702.115" ms.
In other words, when the gaming media number control means turns on the overflow signal and the main control means turns on the overflow test signal, the counting switch signal turns on, the number of counted gaming media is counted as "50", and then the counting process is executed by the gaming media number control means, causing the total number of gaming media to fall below the threshold value of "15,000".
Furthermore, even after the game media count control means turns off the overflow signal, the overflow test signal remains on for 1209 interrupt processes of the main control means, so that the counting switch 47 is in a pseudo-on state for 2702.115 ms. As a result, 450 game media are counted for the nine gaming machine information notifications.

Therefore, when the test IF board and the main control means are connected (when a test firing test is being carried out), when the game medium number control means turns on the overflow signal once, the counting switch signal also turns on, and in addition to the one counting process (counted game medium number of "50") that is performed when the overflow signal is turned on, the counting process can be performed nine times even after the overflow signal is turned off, so the counted number of game media will be "500".
This allows the counted number of gaming media "500" to be subtracted from the total number of gaming media after the total number of gaming media reaches or exceeds the threshold value "15,000" during the test firing, thereby preventing the overflow signal from turning on immediately after it has turned off (preventing the total number of gaming media from reaching the threshold value again immediately after falling below it).This reduces the frequency with which the counting process is performed when the total number of gaming media reaches or exceeds the threshold value "15,000" even when the gaming machine 10 is in an advantageous state during the test firing, such as when the AT or device is operating, thereby reducing the frequency with which the gaming machine 10 malfunctions and the output of error sounds during the test firing machine.

The overflow test signal timer value is not limited to the above-mentioned value, and can be set to any value equal to or greater than the time required to send one gaming machine information notification (300 ms). In other words, if the overflow test signal timer value is updated (decremented) for each interrupt process, the overflow test signal timer value can be set to any value equal to or greater than 135 (2.235 ms x 135 = 301.725 ms).
In the above example, the main control means updates the overflow test signal timer value for each interrupt process. However, this is not limiting. The overflow test signal timer value may be updated once every two or three interrupts. In this case, the overflow test signal timer value can be set to a smaller value. For example, if the main control means updates the overflow test signal timer value once every five interrupts, the overflow test signal timer value can be set to "242" instead of "1209" in the above example. This allows the overflow test signal timer value to be kept within one byte (saving the capacity of the main control RWM), and the time for turning on the overflow test signal can be set to "2704.35" ms.

In addition, the gaming machine 10 is capable of continuing the game even during the counting process (betting, lottery processing and game start based on operation of the start switch 41, stop control processing of the reels 31 based on operation of the stop switch 42, etc.), so even if the total number of gaming media reaches the threshold during the test firing machine test and the counting process is performed, the test firing test will not be interrupted. This allows the test firing test to be carried out smoothly.

Next, the (timer) interrupt process of the game media number control means will be described.
The game media count control means executes interrupt processing every 1 ms, but is not limited to this and may execute it every 2.235 ms, the same as the main control means.
61 is a flowchart showing the interrupt process (I_INTR) of the game media count control means. Note that Fig. 61 shows an excerpt of the process related to the fifth embodiment, and is not limited to the process described in Fig. 61.
61, in step S801, the game media count control means executes input port read processing (I_IN_READ). This processing is the processing shown in Fig. 62, which will be described later, and in particular in the fifth embodiment, detects whether or not the counting switch 47 has been operated, and executes processing according to the operation mode of the counting switch 47.

In the next step S802, the gaming media count control means executes gaming machine information management (I_INF_CTL). This process is the process shown in Fig. 63, which will be described later, and corresponds to Fig. 41 of the second embodiment. This process determines whether the timing for transmitting a gaming machine information notification has arrived, and if it is determined that the timing for transmitting the gaming machine information notification has arrived, executes processing for transmitting the gaming machine information notification, etc.
In the next step S803, the game media count control means executes count control (I_CAL_CTL). This process is the process shown in Fig. 68, which will be described later, and determines whether or not the timing for transmitting the count notification has arrived, and when it is determined that the timing for transmitting the count notification has arrived, executes the process for transmitting the count notification.

In the next step S804, the game media count control means receives the rental notification. After transmitting the count notification in step S803, the rental notification is transmitted from the rental unit 200 within 170 ms as shown in FIG. 32, and the means executes the process of receiving the notification.
In the next step S805, the game media count control means executes the lending control (I_LEN_CTL). This process corresponds to any one of the processes shown in Fig. 69 (Example 1) to Fig. 72 (Example 4) described later, and executes the process of updating the total number of game media and the process of sending a loan receipt response based on the received loan notification.

Fig. 62 is a flowchart showing input port reading (I_IN_READ) in step S801 of Fig. 61. The process shown in Fig. 61 is an excerpt of the main part of the input port reading process that is related to counting. Therefore, various processes other than the process shown in Fig. 62 are executed in the input port reading process. Furthermore, the process related to counting in the input port reading process is not limited to the process shown in Fig. 62.
62, in step S811, the game media number control means determines whether or not the counting switch 47 has been operated. Here, it determines whether or not the level data (counting switch signal) that is turned on when the counting switch 47 is operated is "1." If it is determined that the counting switch 47 has not been operated, the process proceeds to step S812, and if it is determined that the counting switch 47 has been operated, the process proceeds to step S816.

In step S812, the gaming medium number control means determines whether the counting execution timer value is "0". The counting execution timer is provided in the gaming medium number control RWM, and determines whether the counting execution timer value is "0". When the counting switch 47 is not operated, the counting execution timer value is "0", and when it is determined that the counting switch 47 is operated, "1" is added to the counting execution timer value. The counting execution timer value is then added until it reaches "500".
If it is determined in step S812 that the count execution timer value is "0", the process proceeds to step S815, and if it is determined that the count execution timer value is not "0", the process proceeds to step S813.

In step S813, the gaming media number control means determines whether the counting execution flag is "0." Here, the counting execution flag is provided in the gaming media number control RWM, and determines whether the value of the counting execution flag is "0." The counting execution flag is a flag that is "0" when the counting switch 47 is not operated, is "1" when the counting switch 47 is pressed for a short time (approximately "500" ms or less), and is "2" when the counting switch 47 is pressed for a long time (approximately "500" ms or more).
More specifically, if the counting switch 47 is operated (turned on) and then turned off before the counting execution timer value reaches "500", the counting execution flag becomes "1" in step S814. Since the counting execution timer value is incremented by "1" in step S817 for each timer interrupt process by the game media number control means (every "1" ms), it takes approximately "500" ms for the counting switch 47 to be turned on before the counting execution timer value reaches "500".

If it is determined in step S813 that the counting execution flag is not "0", the process proceeds to step S815, and if it is determined that the counting execution flag is "0", the process proceeds to step S814.
In step S814, the game media number control means saves "1" in the counting execution flag. In other words, when the counting switch 47 turns off (from on), the counting execution timer value is not "0", and the counting execution flag is "0", this means that the counting switch 47 has been pressed briefly, so the counting execution flag is set to "1". Next, the process proceeds to step S815, where the counting execution timer is cleared. Then, the process according to this flowchart ends.
When the counting process described later is executed, the counting execution flag is cleared (step S846 in FIG. 68).

On the other hand, if it is determined in step S811 that the counting switch 47 is on and the process proceeds to step S816, the game media number control means determines whether the counting execution timer value has reached 500. If it is determined that the counting execution timer value has not reached 500, the process proceeds to step S817, and if it is determined that the counting execution timer value has reached 500, the process proceeds to step S819.
In step S817, the gaming media number control means adds "1" to the counting execution timer value. Next, the process proceeds to step S818, where the gaming media number control means saves the counting execution timer value (the value after adding "1" in step S817). Then, the process according to this flowchart ends.
On the other hand, if it is determined in step S816 that the count execution timer value has reached "500" and the process proceeds to step S819, the game media number control means stores "2" in the count execution flag, and then ends the process according to this flowchart.

As described above, when the counting switch signal is on (when the on state of the counting switch 47 is detected), the counting execution flag is not changed and the counting execution timer value continues to be updated until the counting execution timer value reaches "500." When the on state of the counting switch 47 is detected and the counting execution timer value reaches "500," the counting execution flag becomes "2" and the counting execution timer value is not updated thereafter. When the counting switch 47 is then turned off, "No" is determined in step S811, "No" in step S812, and "Yes" in step S813, the process proceeds to step S815, where the counting execution timer value is cleared.
On the other hand, if the counting switch signal is turned on and then turned off before the counting execution timer value reaches "500", the counting execution flag becomes "1". After that, the counting execution timer value is not updated.

FIG. 63 is a flowchart showing the gaming machine information management (I_INF_CTL) shown in step S802 of FIG.
Here, we will explain the differences between the gaming machine information management in the second embodiment (Figure 41) and the gaming machine information management in the fifth embodiment (Figure 631).
In the second embodiment, the priority of gaming machine information in gaming machine information notifications was, without exception, first priority gaming machine installation information (every 60 seconds), second priority gaming machine performance information (every 180 seconds), and finally hall control/fraud monitoring information (every 300 ms).
In contrast to this, in the fifth embodiment,
(a) When there is no change in the main control state, no gaming media are bet (inserted), and no gaming media are given (paid out),
First priority: gaming machine installation information Second priority: gaming machine performance information Last priority: hall control and fraud monitoring information (same as in the second embodiment).
(b) When there is a change in the main control state, when a gaming medium is bet (inserted), or when a gaming medium is given (paid out),
First priority: hall control and fraud monitoring information; second priority: gaming machine installation information; last priority: gaming machine performance information.

In FIG. 63, the same steps as those in FIG. 41 are assigned the same step numbers, and step numbers that differ from those in FIG. 41 are underlined.
Below, the gaming machine information management in Figure 63 will be explained again, including parts that overlap with the second embodiment (Figure 41).
First, in step S721, "1" is subtracted from gaming machine information notification timer A (gaming machine information notification timer A is updated). Next, the process proceeds to step S722, where it is determined whether the value of gaming machine information notification timer A before the update is "0." If the carry flag becomes "1" in the subtraction process of step S721, it is determined that the value of gaming machine information notification timer A before the update is "0." Note that the carry flag becoming "1" because the value of gaming machine information notification timer A before the update was "0" corresponds to the case where the value of gaming machine information notification timer A was set to "0" (initialized) when the power was turned on and then "1" was subtracted. If it is determined that the gaming machine information notification timer A before the update is "0," the process proceeds to step S823; if it is determined that the value is not "0," the process proceeds to step S723.

In step S723, it is determined whether the value of gaming machine information notification timer A before the update is "1." In other words, it is determined whether the value of gaming machine information notification timer A has become "0" as a result of the update, or in other words, whether the zero flag has become "1" as a result of the update. If it is determined that the value of gaming machine information notification timer A before the update is "1," the process proceeds to step S724, and if it is determined that the value is not "0," the process according to this flowchart is terminated.
When the value of gaming machine information notification timer A before updating is "1", it means that it is the timing of a "300" ms cycle, that is, the timing to send a gaming machine information notification including hall control and fraud monitoring information.

On the other hand, when it is not the timing to send notification A, it is not a timing with a 300 ms cycle, so it is not a timing with a 60-second cycle, and it is not a timing with a 180-second cycle. In other words, it is not the timing to send a gaming machine information notification including gaming machine installation information, nor is it the timing to send gaming machine installation information including gaming machine performance information. Therefore, when it is determined that it is not the timing to send gaming machine installation information including hall control and fraud monitoring information, gaming machine information management is terminated without determining whether it is the timing to send a gaming machine information notification including gaming machine installation information or whether it is the timing to send gaming machine installation information including gaming machine performance information. This simplifies program processing and speeds up gaming machine information management.

In step S724, an initial value is saved as the value of gaming machine information notification timer A. Here, the initial value is "300." Because the timer interrupt period of the gaming media count control means is "1" ms, storing "300" as the value of gaming machine information notification timer A makes it possible to count "300" ms. Therefore, when the subtraction result in step S721 becomes "0," "300" is immediately saved in step S724.

An example of the calculation instruction in step S721 described above is the DCPWLD instruction. The DCPWLD instruction is an instruction to store a predetermined value when the carry flag becomes "1" as a result of subtracting "1". In this embodiment, the predetermined value is "300". Therefore, after power is turned on, the gaming machine information notification timer A is initialized to "0", and then in the gaming machine information management process in the first interrupt process, when "1" is subtracted in step S721, the carry flag becomes "1" and the predetermined value "300" is stored.
In this way, the initialization process when the power is turned on sets the value of the gaming machine information notification timer A to "0", but otherwise, the value of the gaming machine information notification timer A will never become "0" (except in the event of an abnormality) except for the period after processing step S721 and before processing step S724.

In the next step S725, a process is executed to increment the value of gaming machine information notification timer B by "1." A special increment command is used for this increment process. Specifically, if a value less than "199" is stored in gaming machine information notification timer B, "1" is added to the value of gaming machine information notification timer B; if the value of gaming machine information notification timer B is not less than "199" (i.e., if "199" is stored under normal operating conditions), "0" is stored in gaming machine information notification timer B.

By performing an arithmetic process using a special addition instruction that adds "1" to gaming machine information notification timer B, the value of gaming machine information notification timer B can be cycled between "0" and "199".
Furthermore, the situation in which "1" is added when "199" is stored in gaming machine information notification timer B corresponds to the situation in which the gaming machine information notification timer A has reached "0" 200 times. In other words, since gaming machine information notification timer B is incremented by "1" every time the interrupt process is executed 300 times, this is a situation in which the interrupt process has been executed 300 times x 200 times = 60,000 times (60 seconds have passed).

Normally, a memory area of 2 bytes would be required to measure whether or not the interrupt process has been executed 60,000 times. However, by updating the gaming machine information notification timer B based on the value of the gaming machine information notification timer A, the memory area of the gaming machine information notification timer B can be reduced to 1 byte, thereby reducing the capacity of the gaming media count control RWM.
Furthermore, an example of an arithmetic instruction for adding "1" to the gaming machine information notification timer B is the ICPLD instruction.
In the above example, an instruction to add "1" to gaming machine information notification timer B is executed, but an instruction to subtract "1" may also be executed. In the case of a subtraction instruction, "200" may be stored as an initial value in gaming machine information notification timer B when the power is turned on, and "200" may be stored when the value later becomes "0". Alternatively, "199" may be stored as an initial value in gaming machine information notification timer B when the power is turned on, and "200" may be stored when the carry flag later becomes "1".

In addition, because gaming machine information notification timer B is updated using an addition command, the process of setting the initial value can be omitted compared to when a subtraction command is used (the initial value is set to "0" during initialization processing when the power is turned on), which improves processing speed and reduces program size.

In step S726, it is determined whether or not the time on the gaming machine information notification timer B has elapsed. Here, when the value of the gaming machine information notification timer B becomes "0" by adding "1", it is determined that the time on the gaming machine information notification timer B has elapsed. On the other hand, when the value of the gaming machine information notification timer B does not become "0" by adding "1", it is determined that the time on the gaming machine information notification timer B has not elapsed.
If it is determined that the time set by the gaming machine information notification timer B has elapsed, the process proceeds to step S727, and if it is determined that the time has not elapsed, the process proceeds to step S821.
In step S727, a process of adding "1" to the gaming machine information notification timer C is executed.
A special addition instruction is used for the addition process here. Specifically, when a value less than "2" is stored in gaming machine information notification timer B, "1" is added to the value of gaming machine information notification timer C, and when the value of gaming machine information notification timer C is not less than "2" (i.e., when "3" is stored under normal operating conditions), "0" is stored in gaming machine information notification timer C.

By performing an arithmetic process using a special addition instruction that adds "1" to the gaming machine information notification timer C, the value of the gaming machine information notification timer C can be cycled between "0" and "2".
Furthermore, the situation in which "1" is added when "2" is stored in gaming machine information notification timer C corresponds to the situation in which the trigger for gaming machine information notification timer B to become "0" has occurred "three" times. In other words, gaming machine information notification timer B is incremented by "1" every time the interrupt process is executed "300" times, and gaming machine information notification timer C is incremented by "1" every time gaming machine information notification timer B is updated "200" times, so this is a situation in which the interrupt process has been executed "300 times x 200 times x 3 times = 180,000 times" (180 seconds have passed).

Normally, a memory area of 3 bytes would be required to measure whether or not the interrupt process has been executed 180,000 times, but since the value of gaming machine information notification timer B is updated based on the value of gaming machine information notification timer A, and the value of gaming machine information notification timer C is further updated based on the value of gaming machine information notification timer B, the memory area of gaming machine information notification timer C can be 1 byte, thereby reducing the memory capacity of RWM103.
Furthermore, an example of an arithmetic instruction for adding "1" to the gaming machine information notification timer C is the above-mentioned ICPLD instruction.
In the above example, an instruction to add "1" to the gaming machine information notification timer C is executed, but a subtraction instruction may also be executed. In the case of a subtraction instruction, an initial value of "3" may be stored as the value of the gaming machine information notification timer C when the power is turned on, and "3" may be stored when the value later becomes "0". Alternatively, an initial value of "2" may be stored as the value of the gaming machine information notification timer C when the power is turned on, and "3" may be stored when the carry flag later becomes "1".

However, if the gaming machine information notification timer C is updated with an addition command, as in this embodiment, the process of setting the initial value can be omitted compared to when a subtraction command is used (the initial value is set to "0" by the initialization process when the power is turned on), which allows for improved processing speed and reduced program capacity.

In step S728, it is determined whether or not the time has elapsed on the gaming machine information notification timer C. Here, when the value of the gaming machine information notification timer C becomes "0" by adding "1", it is determined that the time on the gaming machine information notification timer C has elapsed. On the other hand, when the value of the gaming machine information notification timer C does not become "0" by adding "1", it is determined that the time on the gaming machine information notification timer C has not elapsed.
If it is determined that the time set by the gaming machine information notification timer C has elapsed, the process proceeds to step S729, and if it is determined that the time has not elapsed, the process proceeds to step S730.

Note that step S727 is executed only when step S726 returns "Yes." This is because gaming machine information notification timer C is updated only when gaming machine information notification timer B reaches "0." Furthermore, the next step, S728, determines whether gaming machine information notification timer C has elapsed only when step S726 returns "Yes." Whether gaming machine information notification timer C has elapsed depends on whether a 180-second cycle has arrived, and a 180-second cycle always occurs when a 60-second cycle has arrived (the time on gaming machine information notification timer B has elapsed).

In step S729, a gaming machine performance information notification request flag is set. This process stores "1" in the "D0" bit of the gaming machine information notification request flag. In the next step S730, a gaming machine installation information notification request flag is set. This process stores "1" in the "D1" bit of the gaming machine information notification request flag.
That is, when it is determined that the time of the gaming machine information notification timer C has elapsed, a period of 180 seconds has arrived, and since a period of 180 seconds includes a period of 60 seconds, the timing for notifying the gaming machine performance information and the timing for notifying the gaming machine installation information have arrived. Therefore, both the "D0" and "D1" bits of the gaming machine information notification request flag are set to "1."

In contrast, if it is determined in step S726 that the time set by gaming machine information notification timer B has elapsed, and it is determined that the time set by gaming machine information notification timer C has not elapsed, then the 60-second cycle (the timing for notifying gaming machine installation information) has arrived, but the 180-second cycle (the timing for notifying gaming machine performance information) has not yet arrived. Therefore, in this case, the processing of step S729 is not executed, and only the processing of step S730 is executed, setting only the "D1" bit of the gaming machine information notification request flag to "1."

In this way, the timing for transmitting gaming machine installation information and the timing for transmitting gaming machine performance information are managed using flags, which simplifies the process of transmitting hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information. In other words, by linking the timers corresponding to each type of information, transmission is possible without the need for individual management. Furthermore, there is no discrepancy in the start timing of the timers used to transmit hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information, allowing for accurate transmission.

In step S821, the game media number control means determines whether there has been a change in the main control state. Here, in this embodiment, the "main control state" includes when the bonus device is not in operation (non-special (BB, RB, CB, etc.) game) or when the bonus device is in operation (special game). It may also include non-AT and AT.
The main control means transmits information on the main control state to the game medium count control means each time the timing for transmitting the main control state arrives (for example, each time a timer interrupt process occurs).
Meanwhile, the gaming media count control means has a new main control state storage area and an old main control state storage area. When the gaming media count control means receives main control state information from the main control means, it stores the received main control state information in the new main control state storage area. Meanwhile, when the hole control/fraud monitoring information set described below is executed, the gaming media count control means stores the main control state information stored in the new main control state storage area in the old main control state storage area (steps S793 and S794 in FIG. 64 described below). Therefore, at the time of judgment in step S821, main control state information is stored in both the new main control state storage area and the old main control state storage area.
In this way, by storing the main control status information received from the main control means separately in a new main control status memory area and an old main control status memory area, it is possible to determine that there has been no change in the main control status even if main control status information has not been received from the main control means, and the priority of the gaming machine information can be grasped.

Then, in step S821, the gaming media count control means compares the main control state information stored in the new main control state storage area with the main control state information stored in the old main control state storage area, and if the two are the same, it determines that there has been no change in the main control state, and if the two are different, it determines that there has been a change in the main control state. If it determines that there has been a change in the main control state, it proceeds to step S823, and if it determines that there has been no change, it proceeds to step S822.

Here, the processing according to the main control state will be specifically described.
For example, assume that "0" is stored in the new master control state storage area and "0" is stored in the old master control state storage area.
In this state, when the judgment timing of step S821 arrives, the value ("0") of the new main control state memory area and the value ("0") of the old main control state memory area are the same, so it is determined that there is no change in the main control state.
Furthermore, when the hole control/fraud monitoring information set is executed, the value "0" is acquired in the new master control status storage area and saved in the old master control status storage area. However, even after this process is executed, the values in the new master control status storage area and the old master control status storage area remain "0".

When the main control state changes (here, it is assumed that the state changes from "0" to "1"), the main control means transmits main control state information "1" to the gaming media count control means. When the gaming media count control means receives the main control state information "1", it stores it in a new main control state storage area. As a result, the value in the new main control state storage area is updated from "0" to "1".
In this state, when the judgment timing of step S821 arrives, the value of the new main control state storage area ("1") and the value of the old main control state storage area ("0") are different, so it is determined that there has been a change in the main control state.

In addition, when the hole control/fraud monitoring information set is executed, the value "1" is acquired in the new master control status storage area and saved in the old master control status storage area. As a result, the values in the new master control status storage area and the old master control status storage area both become "1".
Therefore, when gaming machine information management is executed again after 300 ms has elapsed, in step S821, it is determined that there is no change in the main control state because the values in the new main control state memory area and the old main control state memory area are both 1.
In this way, when there is a change in the main control state, it is determined that there is a change in the main control state only once.

In the next step S822, the game medium count control means determines whether the bet number information of the game medium is "0" or not, and whether the awarded number information of the game medium is "0" or not.
In the fifth embodiment, the gaming medium count control RWM has a bet number information storage area that stores bet number information for the current game, and an award number information storage area that stores information on the number of awards of gaming media for the current game. These bet number information storage area and award number information storage area are different from the storage areas used in the bet processing and award processing, and the storage areas for the bet number and award number used in the role ratio monitor, and are storage areas used for gaming machine information management.

The gaming medium count control means does not store bet number information in the bet number information storage area just because gaming media are bet. When a game starts, the main control means transmits a start switch acceptance command to the gaming medium count control means. When the start switch acceptance command is received (when the number of bets is determined), the gaming medium count control means generates the number of bets and stores the bet number information in the bet number information storage area.
Furthermore, when the main control means determines that all the reels have stopped, it transmits an all-reel stop command to the game media count control means. Upon receiving the all-reel stop command, the game media count control means generates the number of awarded game media and stores the awarded number information in the award number information storage area.

Then, at the timing of step S822, the gaming media count control means determines whether the value stored in the bet number information storage area is not "0" and whether the value stored in the award number information storage area is not "0". If the value stored in the bet number information storage area is not "0", or if the value stored in the award number information storage area is not "0", the process proceeds to step S823. On the other hand, if the value stored in the bet number information storage area is "0" and the value stored in the award number information storage area is "0", the process proceeds to step S731.

When the hole control/fraud monitoring information setting is executed, the bet number information stored in the bet number information storage area and the award number information stored in the award number information storage area are cleared in step S792 of Fig. 64, which will be described later. Therefore, if it is determined in step S822 that the bet number information or the award number information is not "0", and then "300" ms later, the gaming machine information management is executed again, in step S822, the bet number information and the award number information are both "0", so it is determined as "No".
In addition, if the next game starts within 300 ms after the game media is awarded, or if the game media is awarded within 300 ms after the game starts, the next game machine information management will also result in a "Yes" judgment in step S822, but such an event is considered to be rare.

In step S731, the gaming media number control means determines whether or not there is a request for notification of gaming machine installation information. Here, it determines whether or not the gaming machine installation information notification request flag is set. Therefore, if the "D1" bit of the gaming machine information notification request flag is "1", it is determined that there is a request for notification of gaming machine installation information, and if the "D1" bit of the gaming machine information notification request flag is not "1", it is determined that there is no request for notification of gaming machine installation information.
If it is determined that there is a request for notification of gaming machine installation information, the process proceeds to step S825, and if it is determined that there is no request for notification of gaming machine installation information, the process proceeds to step S732.

In step S732, the gaming media number control means determines whether or not there is a request for notification of gaming machine performance information. Here, it determines whether or not the gaming machine performance information notification request flag is set. Therefore, if the "D0" bit of the gaming machine information notification request flag is "1", it is determined that there is a request for notification of gaming machine performance information, and if the "D0" bit of the gaming machine information notification request flag is not "1", it is determined that there is no request for notification of gaming machine performance information.
If it is determined that there is a request for notification of gaming machine performance information, the process proceeds to step S824, and if it is determined that there is no request for notification of gaming machine performance information, the process proceeds to step S823.

In step S823, the game media number control means executes the hole control/fraud monitoring information set (I_INF_INJ). This process is the process shown in Fig. 64, which will be described later, and is a process for outputting a gaming machine information notification including the hole control/fraud monitoring information.
In step S722, if the gaming media count control means determines that the pre-update value of gaming machine information notification timer A is "0," it executes the hole control/fraud monitoring information set without determining whether the time on gaming machine information notification timer B or gaming machine information notification timer C has elapsed (the processing of steps S726 and S728). This is because the pre-update value of gaming machine information notification timer A is "0" only during the subtraction process in the first interrupt processing immediately after power-on. In other words, it is impossible for "60" or "180" seconds to have elapsed during the subtraction process in the first interrupt processing immediately after power-on. In such a case, by executing the hole control/fraud monitoring information set without determining whether the time on gaming machine information notification timer B or gaming machine information notification timer C has elapsed, it is possible to speed up the processing (speed up the transmission processing).

In addition, in step S731, it is determined whether or not there is a request for notification of gaming machine installation information. If it is determined that there is no request for notification of gaming machine installation information, the processing proceeds to step S732, where it is determined whether or not there is a request for notification of gaming machine performance information. By using this processing order, in a situation where both the gaming machine installation information notification request flag and the gaming machine performance information notification request flag are set (a situation where the 180-second cycle has arrived), it is first determined whether or not there is a request for notification of gaming machine installation information, so that the processing for transmitting the gaming machine installation information can be executed (given priority) before the processing for transmitting the gaming machine performance information.

Furthermore, in the hole control and fraud monitoring information set in step S823, the latest information at that time is transmitted.
For example, the total number of gaming media included in the hall control/fraud monitoring information is transmitted as the information stored in the gaming medium number storage means 103a (_NB_MEDAL) at the time of transmission. In other words, if the transmission timing of the hall control/fraud monitoring information, which is the transmission timing every "300" ms, overlaps with the transmission timing of gaming machine installation information or gaming machine performance information, the transmission of the gaming machine installation information and gaming machine performance information takes priority unless the determination is "Yes" in step S821 or step S822, so the hall control/fraud monitoring information is not transmitted at that timing, and the hall control/fraud monitoring information is transmitted after the next "300" ms has elapsed (if it overlaps with the transmission timing of the gaming machine installation information) or after "600" ms has elapsed (if it overlaps with the transmission timing of the gaming machine installation information and gaming machine performance information).
This "hall control/fraud monitoring information to be transmitted after 300 ms or 600 ms" is not the hall control/fraud monitoring information at the time when it overlaps with the timing of transmitting the gaming machine installation information, but the hall control/fraud monitoring information obtained at the time when the hall control/fraud monitoring information is transmitted after 300 ms or 600 ms. Therefore, even if the timing of transmitting the hall control/fraud monitoring information is delayed, it is possible to transmit the latest information.

When the process proceeds from step S731 to step S825, the gaming media count control means executes a gaming machine installation information set (I_INF_INS). This process is the process shown in FIG. 66, which will be described later, and is a process for outputting a gaming machine information notification including gaming machine installation information. The content transmitted at this time is the information stored in the gaming media count control ROM or the like that was acquired at this time.
On the other hand, when the process proceeds from step S732 to step S824, the gaming medium count control means executes the gaming machine performance information set (I_INF_INJ). This process is the process shown in FIG. 65, which will be described later, and is a process for outputting a gaming machine information notification including gaming machine performance information. The content transmitted at this time is the information stored in the gaming medium count control RWM, etc., acquired at this timing.

In this way, when there is no change in the main control state at the judgment timing of steps S821 and S822, and the bet number information of the gaming medium is "0" and the awarded number information is "0", the gaming machine installation information and gaming machine performance information are transmitted in priority over the hall control and fraud monitoring information.
In contrast, if there is a change in the main control state at the judgment timing of steps S821 and S822, or if the bet number information of the gaming medium is not "0" or the awarded number information is not "0", the hall control/fraud monitoring information is sent in priority over the gaming machine installation information and gaming machine performance information.

By executing the process shown in Figure 63, it becomes possible to send high-priority gaming machine information in the gaming machine information notification. This allows for the transmission of high-priority gaming machine information, while also speeding up processing without complicating the program (without increasing the program capacity).

FIG. 64 is a flowchart showing the hole control/fraud monitoring information set (I_INF_INJ) in step S823 of FIG.
First, in step S791, the gaming media count control means sets the hall control and fraud monitoring information, which is a process for transmitting a gaming machine information notification including the hall control and fraud monitoring information.
In the next step S792, the game media count control means clears the bet number information and the award number information. This process sets the bet number information stored in the bet number information storage area and the award number information stored in the award number information storage area to "0".

In this way, the bet number information is cleared each time the hole control/fraud monitoring information set is executed, so that when the next game information notification is sent, the sending of the hole control/fraud monitoring information is not given priority based on the fact that the bet number information is not "0".
Similarly, the number of awards information is cleared each time the hole control/fraud monitoring information set is executed, so when the next game information notification is sent, the sending of the hole control/fraud monitoring information is not prioritized based on the number of awards information not being "0."

In the next step S793, the gaming media count control means acquires the main control state stored in the new main control state storage area. Then, the process proceeds to the next step S794, where the main control state acquired in step S793 is saved in the old main control state storage area. The processing of steps S793 and S794 updates the main control state stored in the old main control state storage area. In other words, each time the hole control/fraud monitoring information is executed, the main control state stored in the old main control state storage area is updated.

Next, proceeding to step S795, the gaming media count control means updates the serial number (adds "1"). Like the counting serial number, this serial number transmits "0" as the serial number when transmitting immediately after power is restored, and is updated thereafter so that any value between "1" and "255" can be transmitted (cycling between "1" and "255"). This serial number is updated when any of the following three pieces of information is transmitted: hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information. In other words, because the same serial number is used for hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information, the serial number is configured to be updated every 300 ms while the power is on. Processing according to this flowchart then ends.

FIG. 65 is a flowchart showing the gaming machine performance information set (I_INF_ABI) in step S824 of FIG.
First, in step S851, the gaming media count control means sets gaming machine performance information. This process is a process for transmitting a gaming machine information notification including gaming functionality information. Next, in step S852, the gaming media count control means clears the gaming machine performance information notification request flag. Specifically, the "D0" bit of the gaming machine information notification request flag is set to "0." This process is the same as the process in step S737 of FIG. 41. Then, in step S853, the gaming media count control means updates the serial number (adds "1"), and the process according to this flowchart ends.

FIG. 66 is a flowchart showing the gaming machine installation information set (I_INF_INS) in step S825 of FIG.
First, in step S855, the gaming media count control means sets gaming machine installation information. This process is a process for transmitting a gaming machine information notification including the gaming machine installation information. Next, the process proceeds to step S856, where the gaming media count control means clears the gaming machine installation information notification request flag. Specifically, the "D1" bit of the gaming machine information notification request flag is set to "0." This process is the same as the process of step S735 in FIG. 41. Then, the process proceeds to step S857, where the gaming media count control means updates the serial number (adds "1"), and the process according to this flowchart ends.

Next, the transmission of gaming machine information notification in the fifth embodiment will be explained in chronological order.
Fig. 67 is a diagram (time chart) showing the update sequence of the gaming machine information notification timer in the fifth embodiment, and corresponds to Fig. 40 of the second embodiment. In Fig. 63, if the determination in step S821 is "No" and the determination in step S822 is "No", the priority of the gaming machine information notification is the same as in the second embodiment, and the update sequence is the same as that shown in Fig. 40.
In contrast to this, FIG. 67 shows an example in which hall control and fraud monitoring information takes priority over gaming machine installation information and gaming machine performance information.
67 shows an example in which the timer value for transmitting hall control and fraud monitoring information changes from "1" to "300" at the timing of "T1", and furthermore, the main control state changes at this timing. Furthermore, at the timing of "T1", the timer value for transmitting gaming machine installation information changes from "199" to "0", and the gaming machine installation information notification request flag (D1 bit) becomes "1"("*2" in the figure). In other words, at the timing of "T1", the transmission timings for the hall control and fraud monitoring information and the gaming machine installation information arrive at the same time.

Furthermore, between hall control/fraud monitoring information where the main control status has changed and gaming machine installation information, transmission of hall control/fraud monitoring information where the main control status has changed takes priority. Therefore, at timing "T1", hall control/fraud monitoring information is transmitted ("*1" in the diagram). For this reason, at timing "T1", although the gaming machine installation information notification request flag (bit D1) becomes "1", gaming machine installation information is not transmitted ("*2" in the diagram).

Next, when 300 ms have passed since time "T1" and time "T2" has arrived, there will be no change in the main control state, and both the bet number information and the awarded number information will be "0." In this case, between the hall control/fraud monitoring information and the gaming machine installation information, the transmission of the gaming machine installation information takes priority. Therefore, at time "T2," the hall control/fraud monitoring information is not transmitted ("*3" in the diagram), and the gaming machine installation information is transmitted ("*4" in the diagram). After this transmission, the gaming machine installation information notification request flag (bit D1) becomes "0."

Next, an example is shown in which the timer value for transmitting hall control and fraud monitoring information changes from "1" to "300" at time "T3," and the number of awarded points information is not "0" at this time. Also, at time "T3," an example is shown in which the timer value for transmitting gaming machine installation information changes from "199" to "0," and the gaming machine installation information notification request flag (D1 bit) becomes "1" ("*6" in the figure). Also, at time "T3," an example is shown in which the timer value for transmitting gaming machine performance information changes from "2" to "0," and the gaming machine performance information notification request flag (D0 bit) becomes "1" ("*7" in the figure). In other words, at time "T3," the transmission timings for hall control and fraud monitoring information, gaming machine installation information, and gaming machine performance information arrive at the same time.

Among the hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information whose award number information is not "0," transmission of the hall control/fraud monitoring information whose award number information is not "0" takes priority. Therefore, at timing "T3," the hall control/fraud monitoring information is transmitted ("*5" in the figure). Therefore, at timing "T3," although the gaming machine installation information notification request flag (D1 bit) becomes "1," the gaming machine installation information is not transmitted ("*6" in the figure).
Similarly, at timing "T3", the gaming machine performance information notification request flag (D0 bit) becomes "1", but the gaming machine performance information is not transmitted ("*7" in the figure).

Next, when 300 ms have passed since time "T3," and time "T4" has arrived, there will be no change in the main control state, and both the bet number information and the awarded number information will be "0." In this case, among the hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information, transmission of the gaming machine installation information takes priority. Therefore, at time "T4," the hall control/fraud monitoring information is not transmitted ("*8" in the figure), and the gaming machine performance information is not transmitted ("*10" in the figure), and the gaming machine installation information is transmitted ("*9" in the figure). After this transmission, the gaming machine installation information notification request flag (bit D1) becomes "0."

Furthermore, when "300" ms has passed since the timing of "T4" and the timing of "T5" has arrived, there is no change in the main control state, and both the bet number information and the awarded number information are "0". At the timing of "T5", the gaming machine installation information notification request flag (D1 bit) is "0", so it is not the timing to send gaming machine installation information. On the other hand, at the timing of "T5", the gaming machine performance information notification request flag (D0 bit) is "1", so it is the timing to send gaming machine performance information.
In this case, the transmission of the gaming machine performance information takes priority over the hall control/fraud monitoring information and the gaming machine performance information. Therefore, at the timing of "T5", the hall control/fraud monitoring information is not transmitted ("*11" in the figure), and the gaming machine performance information is transmitted ("*12" in the figure). After this transmission, the gaming machine performance information notification request flag (D0 bit) becomes "0".

Fig. 68 is a flowchart showing the counting control (I_CAL_CTL) in step S803 in Fig. 61. This process corresponds to the process in Fig. 37 of the second embodiment. The counting process of the fifth embodiment will be explained again below.
As in the second embodiment, in the fifth embodiment, the game media count control RWM includes the following storage areas.
(a) Counting flag (_FL_CAL_EXE)
This is a storage area for storing data indicating whether or not counting is in progress.
(b) Count value storage area (_CT_CAL_VAL)
This is a storage area for storing the count value (number of counted gaming media) sent when the count is notified.
(c) Count Accumulation Value Storage Area (_CT_CAL_ALL)
This is a storage area for storing the cumulative count value (cumulative count number of gaming media).
(d) Counting serial number storage area (_NB_CAL_NUM)
This is a storage area for storing the counting serial number.

First, in step S831, the gaming media count control means determines whether it is the count notification timing. The "count notification timing" refers to the timing 100 ms after the gaming machine information notification is transmitted, as shown in FIG.
If it is determined that it is the timing for counting notification, the process proceeds to step S832, and if it is determined that it is not the timing for counting notification, the process according to this flowchart ends.

When it is determined that it is the timing for count notification and the process proceeds to step S832, the gaming media number control means clears the counting in progress flag (to "0"). Next, the process proceeds to step S833, where the gaming media number control means determines whether the counting execution flag is "0". If it is determined that the counting execution flag is not "0", the process proceeds to step S834, and if it is determined that the counting execution flag is "0", the process proceeds to step S848. Note that the counting execution flag being "0" means that the counting switch 47 has not been operated.
In step S834, the game media count control means determines whether the total number of game media is 0. If it determines that the total number of game media is not 0, the process proceeds to step S835, and if it determines that the total number of game media is 0, the process proceeds to step S848.

In step S835, the count value (number of counted gaming media) is set to "50".
Next, the process proceeds to step S836, where the game media number control means determines whether the counting execution flag is "2." The counting execution flag being "2" means that the counting switch 47 has been pressed and held. If it is determined that the counting execution flag is "2," the process proceeds to step S837, and if it is determined that the counting execution flag is not "2," the process proceeds to step S847.

In step S837, the game media count control means determines whether the total number of game media is equal to or greater than 50. If it determines that the total number of game media is equal to or greater than 50, the process proceeds to step S839, and if it determines that the total number of game media is not equal to or greater than 50, the process proceeds to step S838.
In step S838, the total number of game media is set as a count value, and the process proceeds to the next step S839, where the count value is saved.
On the other hand, if it is determined in step S833 that the count execution flag is "0" (the count switch 47 has not been operated), and the process proceeds to step S848, the game media number control means sets the count value to "0." The process then proceeds to step S839 and stores the count value "0."

Furthermore, if it is determined in step S836 that the count execution flag is not "2," the process proceeds to step S847, where the count value is set to "1." The process then proceeds to step S839, where the count value "1" is saved. Here, if a "No" determination is made in step S833 and a "No" determination is made in step S836, this means that the count execution flag is "1," and therefore the count switch 47 has been short-pressed.
Before this process is started, the count value is "0" (because the count value was cleared in step S844 of the previous process), so the process of step S848 may be omitted. Therefore, if the determination in step S833 is "Yes," the process may proceed to step S839.

From the above,
(1) When the counting switch 47 is not operated, the count value is set to "0."
(2) Even if the counting switch 47 is operated, if the total number of game media is "0", the count value is set to "0".
(3) When the counting switch 47 is pressed briefly, if the total number of game media is not "0", the count value is set to "1".
(4) When the count switch 47 is pressed and held down, if the total number of game media is "50" or more, the count value "50" is set.
(5) When the count switch 47 is pressed and held down, if the total number of game media is less than "50", the total number of game media is set as the count value.
This will be the case.

In the next step S840, the game media count control means updates the total number of game media by subtracting the count value from the total number of game media.
Next, the process proceeds to step S841, where the game media count control means adds the count value to the value in the count accumulation value storage area to update the value in the count accumulation value storage area.
Next, the process proceeds to step S842, where the game media number control means sets the counting flag (stores "FFh").

Then, the process proceeds to step S843, where the game media count control means outputs a count notification. Specifically, it outputs "0x07h" as the message length, outputs "0x02h" as the command, outputs the count serial number stored in the count serial number storage area as the count serial number, outputs the count value stored in the count value storage area as the count value, outputs the count cumulative value stored in the count cumulative value storage area as the count cumulative value, and outputs a checksum value (1 byte) of the various output data (see FIG. 30).
In the next step S844, the game media count control means clears the count value. Note that the value stored in the count cumulative value storage area is not cleared when the count notification is output (or has been output).

Next, the process proceeds to step S845, where the game media count control means executes a process to update the counting serial number (a process to set it to "+1"). Note that when the counting serial number is "255(D)", the result of adding "+1" is "0", so if it becomes "0", the process to update the counting serial number (a process to add "+1") is executed again.
The game media number control means also transmits information based on the counting flag to the main control means, which allows the main control means to determine that counting is in progress. For example, by transmitting information indicating that counting is in progress from the main control means to the sub-control means, the sub-control means can perform a presentation corresponding to the counting.
Next, the process proceeds to step S846, where the count execution flag is cleared (set to "0"), and the process according to this flowchart ends.

In the fifth embodiment, as in the second embodiment, counting based on the operation of the counting switch 47 is possible even during the setting change mode or the setting confirmation mode.
However, when the counting switch 47 is operated under circumstances where gaming media can be bet, an effect based on the operation of the counting switch 47 is executed, but when the counting switch 47 is operated during the setting change mode or the setting confirmation mode, it is possible not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during the setting change mode or the setting confirmation mode, it is highly likely that a hall staff member is counting (and not a player).

On the other hand, if the counting switch 47 is operated during setting change mode or setting confirmation mode, a dedicated screen for setting change mode or setting confirmation mode may be displayed on the image display device 23, or a sound may be output. In this way, necessary information can be provided to the hall staff. Furthermore, while a dedicated screen for setting change mode or setting confirmation mode is displayed, a notification indicating that counting is in progress (for example, "Counting in progress" may be displayed on the screen) may be made. In this case, the notification is configured to be different from the counting effect (for the player) described above. Such a notification can be used to draw attention.

Furthermore, in this embodiment, even during an error (which may be a predetermined (predetermined) portion of the error or all errors), counting based on operation of the counting switch 47 is possible.
However, when the counting switch 47 is operated under the circumstances where gaming media can be bet, an effect based on the operation of the counting switch 47 is executed, but when the counting switch 47 is operated during an error, it is possible not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during an error, there is a risk that fraudulent activity is being committed.
Furthermore, it is possible to provide situations in which counting is not possible or possible depending on the type of error. For example, counting can be disabled when an unrecoverable error occurs, and enabled when a recoverable error occurs.

On the other hand, if the counting switch 47 is operated during an error, a dedicated screen for the error may be displayed on the image display device 23, or a sound may be output. In this way, necessary information can be provided to the hall staff. Furthermore, while the dedicated screen for the error is displayed, a notification indicating that counting is in progress (for example, "Counting in progress" may be displayed on the screen) may be made. In this case, the notification is configured to be different from the presentation during counting (for the player) described above. Such a notification can be used to draw attention. Note that at this time, the system may be configured so that the number of bets cannot be returned using the settlement switch 46.

Also, in the fifth embodiment, as in the second embodiment, counting based on the operation of the counting switch 47 is possible even during a game (for example, while the reels 31 are spinning).
However, when the counting switch 47 is operated under circumstances where gaming media can be bet, an effect based on the operation of the counting switch 47 is executed, but when the counting switch 47 is operated during a game, it may be configured not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during a game, there is a risk that fraudulent activity is being committed.

69 to 72 are flowcharts showing examples 1, 2, 3, and 4 of the lending control (I_LEN_CTL) in step S805 of FIG. 61, respectively. That is, four examples of lending control in the fifth embodiment are shown. In FIGS. 69 to 72, the same processing is assigned the same step number.
In the fifth embodiment, when the total gaming media reaches the threshold value "15,000", the lending of gaming media by the lending unit 200 is permitted or restricted, and when the total gaming media falls below the threshold value "15,000", the lending of gaming media by the lending unit 200 is permitted again.
The game media count control means, based on the total number of game media reaching the threshold value "15,000," is capable of transmitting "abnormal" as a loan receipt result response corresponding to the loan notification from the loan unit 200. As shown in Fig. 30, when the loaned game media count receipt result is normal, "0" is transmitted as the loan receipt result response, and when the loaned game media count receipt result is abnormal, "1" is transmitted as the loan receipt result response.

If the rental receipt result response is abnormal, the rental unit 200 disables the operation of the rental switch 202. Specifically, even if the rental switch 202 is operated and rental-available gaming media are available, the rental unit 200 will not rent out the gaming media (prohibits rental).
When the game is completed and the total number of game media falls below the threshold value "15,000", the game media number control means sends a normal response as a loan receipt result response corresponding to the loan notification from the loan unit 200.
If the rental receipt result response is normal, the rental unit 200 enables the operation of the rental switch 202 .

First, Example 1 in FIG. 69 will be described.
In step S861, the game media count control means acquires the rental serial number. This process is a process of reading the rental serial number stored in the game media count control RWM (the rental serial number sent in the previous rental receipt result response). Next, the process proceeds to step S862, where "1" is added to the read rental serial number. In the next step S863, it is determined whether the rental serial number to which "1" has been added is "0." If it is not "0," the process proceeds to step S864; if it is "0," the process returns to step S862, where "1" is added again, and the process of step S863 is executed. This is because the rental serial number is "0" only immediately after power-on, and otherwise takes a value of "1" or greater.

In step S864, it is determined whether the rental serial number is normal. This process checks whether the rental serial number in the rental notification sent from the rental unit 200 matches the rental serial number to which "1" was added in step S862. If it is determined that the rental serial number is normal, proceed to step S865; if it is determined that the rental serial number is not normal, proceed to step S873.

In step S865, the serial number abnormality flag is cleared. If it is determined that the lending serial number is abnormal, the serial number abnormality flag "1" is set in the serial number abnormality flag storage area provided in the game media count control RWM (step S873 described later), and therefore the serial number abnormality flag is cleared regardless of whether "1" has already been stored.
In the next step S866, the game media count control means determines whether the number of loaned game media is "0." The number of loaned game media is included in the loan notification sent from the loan unit 200 (FIG. 30). If it is determined that the number of loaned game media is "0," the process proceeds to step S871, and if it is determined that the number of loaned game media is not "0," the process proceeds to step S8671.
In step S867, the game media count control means acquires the total number of game media. Then, in the next step S868, it is determined whether the acquired total number of game media is equal to or greater than the threshold value "15,000." If it is determined that the acquired total number of game media is not equal to or greater than the threshold value "15,000," the process proceeds to step S869, and if it is determined that the acquired total number of game media is equal to or greater than the threshold value "15,000," the process proceeds to step S874.

In step S869, the number of loaned gaming media is added to the total number of gaming media. In the next step S870, the total number of gaming media calculated in step S869 is saved. In the next step S871, the loan serial number updated in step S862 is saved. Furthermore, in the next step S872, normal ("0") is saved as the receipt result for the number of loaned gaming media. The loan serial number saved in step S871 and the receipt result for the number of loaned gaming media saved in step S872 are used in the loan receipt result response.

Next, the process proceeds to step S875, where the message length of the loan receipt result response to be sent next is set. Then, in the next step S876, the loan receipt result response is set. The loan receipt result response has the data structure shown in FIG. 30. Then, the process proceeds to step S877, where loan control command set processing is performed. By this processing, when the gaming media number control means receives a loan notification from the loan unit 200, as shown in FIG. 32, it transmits the loan receipt result response to the loan unit 200 within 10 ms.
On the other hand, if it is determined in step S864 that the lending serial number is not normal, the process proceeds to step S873, where a serial number abnormality flag is set. Furthermore, in the next step S874, an abnormality ("1") is saved as the result of receiving the number of lending game media. Therefore, regardless of the total number of game media, if the lending serial number is abnormal, an abnormality is set as the result of receiving the number of lending game media.

Also, if it is determined in step S868 that the total number of gaming media is greater than or equal to the threshold value of 15,000, the process proceeds to step S874 and an abnormality is set as the result of receiving the number of loaned gaming media. If it is determined in step S868 that the total number of gaming media is greater than or equal to the threshold value of 15,000, the process does not proceed to step S869 or later, and the number of loaned gaming media is not added to the total number of gaming media. Therefore, for example, even if a loan notification indicating that the number of loaned gaming media is 50 is received from the loaning unit 200, if the total number of gaming media at that time is greater than or equal to the threshold, the process of adding the number of loaned gaming media to the total number of gaming media (the process of updating the total number of gaming media) is not performed.

In addition, the game media number control means sends a rental receipt result response to the rental unit 200 indicating that the rental game media number receipt result is abnormal, and when the rental unit 200 receives this, the rental unit 200 does not subtract the number of rental game media sent in the rental notification.
A specific example will be given below.
If the number of game media available for lending from the lending unit 200 at that time is "N" and the lending unit 200 transmits a lending notification including data on the number of game media to be lent "50", the game media number control means, when it determines that the lending serial number is normal and that the total number of game media (the total number of game media at this time is assumed to be "M") is less than the threshold, updates the total number of game media to "M+50" and transmits a loan receipt result response to the lending unit 200 indicating that the receipt result for the number of game media to be lent is normal. When the lending unit 200 receives the loan receipt result response, it updates the number of game media available for lending to "N-50".

In contrast, if the number of game media available for lending from the lending unit 200 at that time is "N" and the lending unit 200 sends a lending notification including data on the number of game media to be lent "50," when the game media number control means determines that the total number of game media "M" is greater than or equal to the threshold, it does not update the total number of game media "M" and sends a loan receipt result response to the lending unit 200 indicating that the receipt result for the number of game media to be lent is abnormal. When the lending unit 200 receives this loan receipt result response, it maintains the number of game media available for lending "N."

Next, Fig. 70 (Example 2) will be described. In Fig. 70, the step numbers of processes that differ from those in Fig. 69 are underlined. The differences from Fig. 69 will be described below.
70, if it is determined in step S868 that the total number of gaming media is not equal to or greater than the threshold value "15,000," the process proceeds to step S881. In step S881, the gaming media number control means determines whether or not a bet process is in progress. When the gaming media number control means starts a bet process, it turns on a bet process in progress flag (provided in the gaming media number control RWM), and when the bet process is completed, it turns off the bet process in progress flag.

In step S881, the game media count control means determines whether the betting processing flag is on. If it determines that a betting process is not in progress, the process proceeds to step S869, and if it determines that a betting process is in progress, the process proceeds to step S882.
In step S882, the total number of gaming media before the bet is obtained. Here, for example, first, the total number of gaming media immediately before the bet process is stored before the bet process starts. Alternatively, second, the number of bets at that time is obtained, and the total number of gaming media before the bet is calculated by adding the number of bets to the total number of gaming media.

Next, the process proceeds to step S883, where it is determined whether the total number of game media before the bet is equal to or greater than the threshold value of 15,000. If it is determined that the total number of game media before the bet is equal to or greater than the threshold value of 15,000, the process proceeds to step S874, and if it is determined that the total number of game media before the bet is not equal to or greater than the threshold value of 15,000, the process proceeds to step S869.
Through the above processing, even if it is determined in step S868 that the total number of gaming media is not equal to or greater than the threshold value "15,000," if a bet is being processed and the total number of gaming media before the bet is equal to or greater than the threshold value "15,000," the number of loaned gaming media is not added to the total number of gaming media, and an abnormality is saved as the result of receiving the number of loaned gaming media and sent to the loaning unit 200. As a result, on the loaning unit 200 side, operation of the loaning switch 202 is disabled, and loaning of gaming media is prohibited. Furthermore, because the loaned gaming media sent in the loan notification are not saved in the gaming machine 10, the number of loanable gaming media is not updated on the loaning unit 200 side either.
On the other hand, when the betting process is completed, step S881 returns "No", so if the total number of gaming media after the betting process is less than the threshold value "15,000", the total number of gaming media is updated (the number of loaned gaming media is added to the total number of gaming media up to that point).

A specific example will be given below.
For example, if the total number of gaming media before the bet is "15001" and the number of gaming media "3" is bet through the bet processing, assume that after the bet processing for the number of gaming media "2" is executed, the processing of Figure 70 is executed before the final bet processing for "1".
In this case, since the number of bets "2" has been subtracted from the total number of gaming media "15001", the total number of gaming media at the time of judgment in step S868 is "14999", and step S868 is judged as "No". Next, when proceeding to step S881, since the bet processing is in progress, it is judged as "Yes". In the next step S882, "15001" is acquired as the total number of gaming media before the bet, and step S883 is judged as "Yes". As a result, data indicating that the receipt result of the number of gaming media to be rented is abnormal is sent to the rental unit 200 as a rental receipt result response, and the rental unit 200 does not permit the rental of gaming media (disables the rental switch 202).
By processing in this manner, it is possible to prevent the loan permission/prohibition from being switched during the betting process, and to accurately grasp the number of loans.

On the other hand, if the total number of gaming media before the bet is "15001" and the number of gaming media "3" is bet through the bet processing, assume that the processing of Figure 70 is executed after the bet processing of the number of gaming media "3".
In this case, since the number of bets "3" has been subtracted from the total number of gaming media "15001", the total number of gaming media at the time of judgment in step S868 is "14998", and step S868 judges "No". Next, when proceeding to step S881, "No" is judged because a bet is not being processed. As a result, data indicating that the receipt result of the number of gaming media to be lent is normal is sent to the lending unit 200 as a lending receipt result response, and the lending unit 200 permits the lending of gaming media.

69, unlike FIG. 70, does not include the processing of steps S881 to S883. Therefore, even during betting processing, when the total number of gaming media falls below the threshold value "15,000", step S868 is judged as "No", and data indicating that the receipt result of the number of gaming media to be lent is normal is sent to the lending unit 200 as a lending receipt result response. As a result, the lending unit 200 permits the lending of gaming media.
For example, if a "3" bet process is initiated when the total number of gaming media is "15,000," the total number of gaming media will be "14,999" after the first "1" bet process, which falls below the threshold. As a result, "No" is determined in step S868 in FIG. 69. Therefore, even if a bet process is in progress, data indicating that the receipt result for the number of gaming media to be loaned is normal is sent to the lending unit 200 as a lending receipt result response when the total number of gaming media falls below the threshold. This allows the lending unit 200 to loan gaming media.
By processing in this manner, permission to lend game media can be given as quickly as possible.

Next, Fig. 71 (Example 3) will be described. In Fig. 71, the step numbers of processes that differ from those in Fig. 69 are underlined. Below, the differences from Fig. 69 will be described.
71, if it is determined in step S868 that the total number of gaming media is not equal to or greater than the threshold value "15,000," the process proceeds to step S884. In step S884, the gaming media number control means determines whether or not there are gaming media bets (whether or not the number of bets is "0"). Here, when gaming media are bet, the bet is stored in the bet number storage means of the gaming media number control RWM (for example, the bet number storage means 53a in FIG. 29), and whether or not there are gaming media bets is determined based on the value of this bet number storage means.
If it is determined that there are gaming media betted, the process proceeds to step S885, and if it is determined that there are no gaming media betted, the process proceeds to step S869.
In step S885, the sum of the number of bets and the total number of gaming media is obtained.

Next, the process proceeds to step S886, where it is determined whether the sum of the number of bets and the total number of gaming media is equal to or greater than the threshold value of 15,000. If it is determined that the sum is equal to or greater than the threshold value of 15,000, the process proceeds to step S874, and if it is determined that the sum is not equal to or greater than the threshold value of 15,000, the process proceeds to step S869.
Through the above processing, even if it is determined in step S868 that the total number of gaming media is not equal to or greater than the threshold value "15,000," if the sum of the number of bets and the total number of gaming media is equal to or greater than the threshold value "15,000," the number of loaned gaming media is not added to the total number of gaming media, and an abnormality is saved as the result of receiving the number of loaned gaming media and sent to the loaning unit 200. As a result, on the loaning unit 200 side, operation of the loaning switch 202 is disabled, and loaning of gaming media is prohibited. Furthermore, because the loaned gaming media sent in the loan notification are not saved in the gaming machine 10, the number of loanable gaming media is not updated on the loaning unit 200 side either.

A specific example will be given below.
For example, if the total number of gaming media is "14,999" and the number of bets is "3," step S868 will be judged as "No." Next, when proceeding to step S884, since there is a bet number, a "Yes" will be judged. In the next step S885, "14,999 + 3 = 15,002" is obtained, and in the next step S886, a "Yes" will be judged. As a result, data indicating that the receipt result of the number of gaming media to be rented is abnormal is sent to the rental unit 200 as a rental receipt result response, so the rental unit 200 prohibits the rental of gaming media (disables the rental switch 202).
By processing in this manner, it is possible to prevent the repetition of lending permission and lending prohibition by repeating the settlement process (processing for returning the bet gaming media to the total gaming media) and the betting process.

On the other hand, the example of Fig. 69, unlike Fig. 71, does not include the processing of steps S884 to S886. Therefore, if the total number of gaming media is "14999" and the number of bets is "3", "No" is determined in step S868 in Fig. 69, and data indicating that the receipt result of the number of gaming media to be lent is normal is sent to the lending unit 200 as a lending receipt result response. As a result, the lending unit 200 permits the lending of gaming media.
By processing in this way, it is possible to permit the lending of game media as much as possible.

Next, Fig. 72 (Example 4) will be described. In Fig. 72, the step numbers of processes that differ from those in Fig. 69 are underlined. The differences from Fig. 69 will be described below.
In FIG. 72, if it is determined in step S868 that the total number of game media is not equal to or greater than the threshold value "15,000", the process proceeds to step S891.
In step S891, it is determined whether the awarding flag is "1." The game medium count control RWM is provided with an awarding flag. The awarding flag is a flag that is turned on when the game medium awarding process starts and is turned off when the awarding process ends.
Therefore, when a small winning combination is achieved and game media are awarded, the awarding flag is set to "1" and then the game media awarding process is executed.
In step S891, if it is determined that the in-provision flag is "1", the process proceeds to step S892, and if it is determined that the in-provision flag is not "1", the process proceeds to step S874.
In step S892, the game media count control means determines whether the total number of game media before the game media were awarded in the current game was less than the threshold value "15,000." If the determination is "Yes," the process proceeds to step S869, and if the determination is "No," the process proceeds to step S874.

As a result, when the total number of game media is equal to or greater than the threshold value "15,000," and game media are not being dispensed, or when game media are being dispensed but the total number of game media before dispense is already equal to or greater than the threshold value "15,000," the number of loaned game media is not added to the total number of game media, and data indicating that the receipt result of the number of loaned game media is abnormal is sent to the loaning unit 200 as a loan receipt result response. As a result, the loaning unit 200 prohibits the loaning of game media.
On the other hand, even if the total number of game media is equal to or greater than the threshold value "15,000," if game media are being dispensed and the dispensing of game media for the current game causes the total number of game media to exceed the threshold value "15,000," the number of loaned game media is added to the total number of game media, and data indicating that the receipt result for the number of loaned game media is normal is sent to the loaning unit 200 as a loan receipt result response. As a result, the loaning unit 200 permits the loaning of game media.

A specific example will be given below.
For example, assume that the total number of game media at the start of the current game is "14,998" and a small win corresponding to "5" game media is won. Then, the process of awarding game media is executed, and the process of awarding "2" game media out of the "5" game media to be awarded is completed, and the total number of game media reaches "15,000." At this point, the total number of game media is equal to or greater than the threshold value "15,000," and step S868 in FIG. 72 returns "Yes." Next, when the process proceeds to step S891, the process of awarding game media is in progress, so the result is "Yes." When the process proceeds to the next step, S892, the total number of game media before the award of game media in the current game is "14,998," which is less than the threshold value, so the result is "Yes." As a result, data indicating that the number of rental game media received is normal is sent to the rental unit 200 as a rental receipt result response, and the rental unit 200 then permits the rental of the game media.
By processing in this manner, it is possible to prevent the permission/prohibition of lending of gaming media from being switched during the process of providing gaming media. Also, if lending is switched from permitted to prohibited during the process of providing gaming media, the player may be misled into thinking that the gaming machine 10 or the lending unit 200 has broken down, but this can prevent such a misunderstanding from occurring.

On the other hand, the example of FIG. 69, unlike FIG. 72, does not include the processing of steps S891 and S892. Therefore, if the total number of game media at the start of the current game (before the game media awarding process) is "14,998" and a small win corresponding to "5" game media is won, the total number of game media will exceed the threshold value of "15,000" when "2" game media is awarded, and the process proceeds from step S868 to step S874. Therefore, data indicating that the receipt result of the number of game media to be loaned is abnormal is sent to the lending unit 200 as a lending receipt result response. As a result, the lending unit 200 prohibits the lending of game media.
By processing in this manner, it is possible to prevent the total number of game media from exceeding the threshold due to lending, and when the total number of game media exceeds the threshold, it is possible to quickly prohibit lending of game media.

Next, the threshold notification by the sub-control means will be described.
In the fifth embodiment, the sub-control means is capable of issuing a predetermined notification when the total number of game media reaches a threshold value.
Figures 73 and 74 are flows showing threshold processing by the main control means, with Figure 73 showing Example 1 and Figure 74 showing Example 2. In Figure 74, step numbers that differ from those in Figure 73 are underlined.
73, in step S901, the main control means determines whether the total number of game media has reached the threshold value of 15,000. If it determines that the total number of game media has not reached the threshold value of 15,000, the process proceeds to step S902, and if it determines that the total number of game media has reached the threshold value of 15,000, the process proceeds to step S904.

In step S902, the main control means sets the threshold value reached flag to "0." The threshold value reached flag is provided in the main control RWM, and stores "0" when the threshold value has not been reached, and stores "1" when the threshold value has been reached. Next, the process proceeds to step S903, where threshold value not reached information is set.
On the other hand, if it is determined in step S901 that the total number of game media has reached the threshold value and the process proceeds to step S904, the main control means sets the threshold value reached flag to 1. Next, the process proceeds to step S905, where threshold value reached information is set.
The main control means transmits threshold unreached information (when the threshold reached flag is "0") or threshold reached information (when the threshold reached flag is "1") to the sub-control means. When the threshold (unreached, reached) information is set in steps S903 and S905, the main control means transmits the threshold (unreached, reached) information to the sub-control means at a predetermined timing. Then, the processing according to this flowchart ends.

Also, in Example 2 of Figure 74, in step S901, the main control means determines whether the total number of gaming media has reached the threshold value of "15,000". If it determines that the total number of gaming media has not reached the threshold value of "15,000", the process proceeds to step S911, and if it determines that the total number of gaming media has reached the threshold value of "15,000", the process proceeds to step S904. The processing after proceeding to step S904 is the same as in Figure 73 (Example 1), so a description thereof will be omitted.

In step S911, the main control means determines whether gaming media have been bet or not. If it is determined that gaming media have been bet, the process proceeds to step S912, and if it is determined that gaming media have not been bet, the process proceeds to step S902.
In step S912, the main control means acquires the value obtained by adding the number of bets and the total number of gaming media. Next, the process proceeds to step S913, where the main control means determines whether the value obtained by adding the number of bets and the total number of gaming media is equal to or greater than the threshold value "15,000." If it is determined that the value obtained by adding the number of bets and the total number of gaming media is not equal to or greater than the threshold value "15,000," the process proceeds to step S902. The processing from step S902 onwards is the same as in Figure 73 (Example 1), so a description thereof will be omitted.
On the other hand, if it is determined in step S913 that the sum of the number of bets and the total number of gaming media is equal to or greater than the threshold value "15,000", the process proceeds to step S904.

73, if the total number of gaming media is less than the threshold value of 15,000, threshold-reached information is not sent to the sub-control means. Therefore, for example, if the number of bets is 3 and the total number of gaming media is 14,999, threshold-unreached information is sent to the sub-control means.
In contrast, in Example 2 of Figure 74, even if the total number of gaming media is less than the threshold value of "15,000", when the number of bets is "3", the sum of both is greater than or equal to the threshold value of "15,000", so threshold reaching information is sent to the sub-control means.
As will be described in detail later, when the threshold reach information is transmitted to the sub-control means, the sub-control means can issue a notification indicating that the total number of gaming media has reached the threshold. Therefore, in Example 1 of Fig. 73, when the number of bets is "3" and the total number of gaming media is "14,999," no notification indicating that the total number of gaming media has reached the threshold is issued. In contrast, in Example 2 of Fig. 74, when the number of bets is "3" and the total number of gaming media is "14,999," a notification indicating that the total number of gaming media has reached the threshold is issued.

Figures 75 and 76 are flowcharts showing threshold notification processing by the sub-control means, with Figure 75 showing Example 1 and Figure 76 showing Example 2. In Figure 76, step numbers that differ from those in Figure 75 are underlined.
Here, "threshold notification" corresponds to a notification (warning) that informs the player that the total number of gaming media has reached the threshold, or a notification that urges the player to operate the counting switch 47 because the total number of gaming media has reached the threshold.
In Example 1 of FIG. 75, in step S921, the sub-control means determines whether the threshold notification flag is "1". Here, the sub-control RWM is provided with a threshold notification flag. The threshold notification flag is a flag that indicates that the threshold has been reached when it is "1", and indicates that the threshold has not been reached when it is "0". When the threshold notification flag is "1", a notification indicating that the threshold has been reached can be executed.

If it is determined in step S921 that the threshold notification flag is not "1", the process proceeds to step S922, and if it is determined that the threshold notification flag is "1", the process proceeds to step S925.
In step S922, the sub-control means determines whether or not threshold value reaching information has been received from the main control means. If threshold value reaching information has not been received (without issuing a notification), the process according to this flowchart ends. If it is determined that threshold value reaching information has been received, the process proceeds to step S923. In step S923, the sub-control means sets the threshold value notification flag to "1." The process then proceeds to step S924, where a notification is output indicating that the total number of gaming media has reached the threshold value, and the process according to this flowchart ends.

On the other hand, if it is determined in step S921 that the threshold reach flag is "1" and the process proceeds to step S925, the sub-control means determines whether or not threshold unreached information has been received from the main control means. If it is determined that threshold unreached information has not been received, the process proceeds to step S924, and if it is determined that threshold unreached information has been received, the process proceeds to step S926. In step S926, the sub-control means sets the threshold notification flag to "0." Then, the process proceeds to step S927, where the notification being output ends, and the process according to this flowchart ends.
As described above, in Example 1, when the total number of game media falls below the threshold value, the notification is immediately terminated.

76, when it is determined in step S925 that threshold non-reach information has been received, the process proceeds to step S928. In step S928, the sub-control means determines whether or not a predetermined condition is met, and when it is determined that the predetermined condition is met, the process proceeds to step S926 and ends the notification. On the other hand, when it is determined that the predetermined condition is not met, the process proceeds to step S924 and continues the notification.
Therefore, in Example 2, the sub-control means receives threshold unreachable information from the main control means and continues to make the alert even when it determines that the total number of gaming media has fallen below the threshold, and then terminates the alert when a predetermined condition is met.

Here, examples of the "predetermined condition" in step S928 include the following conditions.
(1) When a predetermined number (for example, "50") of gaming media have been counted When the main control means determines that the player has operated the counting switch 47 and that a predetermined number of gaming media have been counted, it sends a command to that effect to the sub-control means. After the threshold notification flag is "1" and the sub-control means receives the threshold not-reached information, when it receives a command to the effect that a predetermined number of gaming media have been counted, it determines that the predetermined condition has been met and proceeds to step S926. This ends the notification.
In this way, the notification will not end until the total number of game media falls below the threshold by a certain number. This makes it possible to prevent the total number of game media from falling below the threshold and then immediately reaching the threshold again, causing the notification to be issued again. In other words, it is possible to prevent the notification from being switched on and off repeatedly in a short period of time.

(2) When the total number of game media falls below a predetermined value (for example, "14,500"), the sub-control means receives information on the total number of game media transmitted from the main control means and continues to update the total number of game media. After the threshold notification flag is "1" and the sub-control means receives threshold not-reached information, the sub-control means determines that the predetermined condition is met when the total number of game media falls below the predetermined value, and proceeds to processing from step S926 onwards. This ends the notification.
In this way, when the total number of game media falls below a predetermined value and the notification is terminated, it is possible to prevent the notification from being immediately resumed. In other words, it is possible to prevent the notification from being alternately turned on and off in a short period of time. Furthermore, it is possible to prompt the player to operate the counting switch 47.

(3) When one game ends When one game ends (when all reels 31 have stopped and, if game media are awarded, the awarding process of game media has ended), the main control means sends a game end command to the sub-control means. After the threshold notification flag is "1" and the sub-control means receives the threshold not reached information, when it receives a game end command, it determines that the predetermined condition is met and proceeds to the processing of step S926 and subsequent steps. This ends the notification.
This prevents the notification from continuing even when the player is not playing (while waiting to play).

Although the fifth embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and various modifications such as those described below are possible.
(1) In the above embodiment, it is determined whether the threshold value "15000" has been reached (whether the threshold value "15000" has fallen below the threshold value "15000"). However, this is not limiting, and it may be determined whether the threshold value "15000" has been exceeded (whether the threshold value "15000" has fallen below the threshold value "15000").
Similarly, in this embodiment, it is determined whether or not the upper limit value "16383" has been reached. However, it is not limited to this, and it may be determined whether or not the upper limit value "16383" has been exceeded.
As mentioned above, the threshold value "15000" and the upper limit value "16383" are merely examples, and the present invention is not limited to these values.

(2) Although the lending of game media is prohibited when the total number of game media reaches a threshold value, the lending of game media may be restricted without being prohibited. For example, until the total number of game media reaches the threshold value, control is exercised so that "50" game media are lent out at one time by pressing and holding the lending switch 202. After the total number of game media reaches the threshold value, the number of game media lent out at one time when the lending switch 202 is pressed and held can be limited to, for example, "10" (a number less than the original number "50").
Alternatively, even after the total number of gaming media has reached the threshold, if the lending switch 202 is pressed and held down, 50 gaming media will be lent out at once, but once 50 gaming media have been lent out after the threshold has been reached, it is also possible to control the system so that they will not be lent out again until a predetermined time (for example, 300 seconds) has elapsed.

(3) When the total number of game media reaches a threshold value during the operation of a special device (during a special game) or during an AT, and an announcement is made that the threshold value has been reached, the effects related to the operation of the device or the AT and the announcement (announcement) that the threshold value has been reached overlap. In this case, if the image display (layer) related to the operation of the device or the AT is placed in the front and the image display (layer) indicating that the threshold value has been reached is placed in the back, the image display related to the operation of the device or the AT can be prevented from being obscured by the image display indicating that the threshold value has been reached.
Conversely, if the image display (layer) related to the operation of the role device or the AT is placed at the back and the image display (layer) indicating that the threshold has been reached is placed at the front, the player can be reliably notified that the threshold has been reached. However, even in this case, it is preferable that the display area for the number of wins and the number of remaining plays do not overlap with the display area indicating that the threshold has been reached.

(4) When the total number of game media reaches a threshold or an upper limit, the notification may be made not only with different image display and sound content but also with different volume levels. For example, the notification volume when the threshold is reached may be set to "N1" decibels, and the notification volume when the upper limit is reached may be set to "N2" decibels (N2 > N1).
It is also possible to provide a dedicated effect output device (for example, a rotating light (patrol lamp)) for when the upper limit value is reached, and not activate the effect output device when the threshold value is reached, but activate the effect output device when the upper limit value is reached.

Sixth Embodiment
77 is a block diagram showing the gaming machine 10 according to the sixth embodiment. The same parts as those in FIG. 51 (fourth embodiment) are denoted by the same reference numerals.
In the sixth embodiment, the "game medium" in the fourth embodiment will be referred to as a "medal." However, the sixth embodiment is the same as the other embodiments in that the gaming machine 10 is a medal-less gaming machine (smart gaming machine, smart pachislot) and the gaming medium is an electronic medal (electronic gaming medium).
In the fourth embodiment of Fig. 51, one one-chip microprocessor 500 is mounted on the main control board 50. In contrast to this, in the sixth embodiment of Fig. 77, the main control board 50 is provided with a one-chip microprocessor for main control and a one-chip microprocessor for medal count control.

The one-chip microprocessor for main control includes a main control CPU 510, a main control ROM 511, and a main control RWM 512 (built-in memory). The main control ROM 511 and the main control RWM 512 correspond to the main control ROM 502 and the main control RWM 503 in the fourth embodiment (FIG. 51), respectively.
The one-chip microprocessor for medal count control includes a medal count control CPU 520, a medal count control ROM 521, and a medal count control RWM 522 (built-in memory). The medal count control ROM 521 and the medal count control RWM 522 correspond to the game media count control ROM 504 and the game media count control RWM 505 in the fourth embodiment (FIG. 51), respectively.
The one-chip microprocessor for main control or the main control CPU 510 may be referred to as "main control means 510." Furthermore, the one-chip microprocessor for medal count control or the medal count control CPU 520 may be referred to as "medal count control means 520."

As shown in Figure 29 (second embodiment), two types of control boards may be provided, such as a main control board 50 and a game medium (medal) number control board 100, with a one-chip microprocessor equipped with a main control CPU mounted on the main control board 50 and a one-chip microprocessor equipped with a medal number control CPU mounted on the game medium (medal) number control board 100.
Alternatively, as in the fourth embodiment, the main control board 50 may be equipped with the function of medal count control, and a single one-chip microprocessor (main CPU) may be provided on the main control board 50, with this main CPU having the functions of a main control CPU and a medal count control CPU.
Furthermore, as in this embodiment, a one-chip microprocessor for main control and a one-chip microprocessor for medal count control may be mounted on the main control board 50.
77, a one-chip microprocessor for sub-control is mounted on the sub-control board 80. The one-chip microprocessor for sub-control includes a sub-control CPU 85, a sub-control ROM 84, and a sub-control RWM 83 (built-in memory).
The sixth embodiment in FIG. 77 is otherwise the same as the fourth embodiment in FIG. 51, so a description thereof will be omitted.

In the sixth embodiment, the main control ROM 511, the main control RWM 512, the medal count control ROM 521, and the medal count control RWM 522 all have a use area and an outside use area.
Figures 78 and 79 are diagrams showing a memory area provided in the medal count control RWM 522, which is a memory area for calculating the ratios to be displayed on the role ratio monitor 113.
The storage area for information relating to the display control of the role ratio monitor 113, such as ratios (advantageous zone ratios, instructed role ratios, etc., ratios to be displayed on the role ratio monitor 113), is provided outside the area used by the medal count control RWM 522.
In addition, a memory area for generating and transmitting the gaming machine information notification message is provided in the area used by the medal count control RWM 522.
Therefore, for example, ratio information to be displayed on the winning combination ratio monitor 113 is stored outside the usage area of the medal count control RWM 522, but ratio information transmitted to the rental unit (also called a "dedicated unit") 200 as part of the gaming machine information notification (gaming machine performance information) is stored in the usage area of the medal count control RWM 522. In other words, multiple storage areas are provided for storing ratio information.

The display of the role ratio monitor 113 is basically the same as that described in the second embodiment.
(1) Cumulative indicative role ratio (7P.) or cumulative advantageous zone ratio (7U.)
(2) 6000 consecutive game feature ratio (6y.)
(3) 6,000 gaming device ratio (7 years)
(4) Cumulative consecutive feature ratio (6A.)
(5) Cumulative ratio of special features (7A.)
(6) Cumulative ratio of the status of the game (5H.)
The ratios of the six items are displayed.
The above order is the order in which the winning combinations are displayed on the winning combination monitor 113.

To calculate the ratio between "6000" games, "400" games are counted as one set, and 15 sets are added together to calculate the ratio of "6000" games.
Therefore, for the "400" game, the "400" total payout for the game, the "400" total payout for the game continuous device, the "400" total payout for the game device, and the "400" total payout for the device with game instructions are stored.
In addition, for the "6000" game, the total payout for the "6000" game, the total payout for the "6000" game consecutive accessories, and the total payout for the "6000" game accessories are stored.
Here, the total payout is all payouts paid out during the game (excluding replays).
In addition, the total payout of consecutive special devices is the payout due to the operation of the first type special device (RB).
Furthermore, the total payout of all reels is the payout due to the operation of the reels (all reels including consecutive reels such as RB, CB, SB, etc.).
Furthermore, the total payout of the device with instructions is the payout due to the operation of the device and the instruction function.

Furthermore, for the "400" total payout, the "400" total payout for consecutive game features, and the "400" total payout for consecutive game features, there are "15" buffers of 2 bytes each. Hereinafter, as necessary, these buffers will be referred to as "400" total payout "0" to "400" total payout "14,""400" total payout for consecutive game features "0" to "400" total payout for consecutive game features "14," and "400" total payout for consecutive game features "0" to "400" total payout for consecutive game features "14."
On the other hand, the ring pointer is a pointer for specifying which set to count in the current game. The ring pointer is incremented by "1" for every "400" game, and cycles between "0" and "14." For example, when the ring pointer is "0," the total payout for the current game can be added to the total payout for the "400" game of "0," the total payout for the consecutive "400" games of "0," and the total payout for the "400" games of "0."
On the other hand, since the total payout of the game devices including instructions does not tally up the number of games played (6000), one 2-byte buffer (total payout of the game devices including instructions for 400 games) is provided.
79, the game number counter is a counter that counts the number of games played of "400." When the game number counter is updated from "399" to "0," the ring pointer is incremented by "1."

Specifically, when the number of payouts is being added to the total payout for "400" games of "0", and the number of games counter is updated from "399" to "0" and the ring pointer is incremented by "1", from the next game onwards, the addition of the number of payouts to the total payout for "400" games of "0" is stopped, the total payout for "400" games of "1" is cleared, and the addition of the number of payouts to the total payout for "400" games of "1" begins.
Furthermore, for the total payout of "400" for games, the total payout of "400" for games with continuous game features, and the total payout of "400" for games with continuous game features, the total values of all "15" buffers are calculated as the total payout of "6000" for games, the total payout of "6000" for games with continuous game features, and the total payout of "6000" for games with continuous game features, respectively.
The cumulative total payout, cumulative total consecutive payout, cumulative total payout for special features, and cumulative total payout for special features with instructions correspond to the total payout for the total number of games, the total consecutive payout for the total number of games, the total payout for special features with instructions, and the total payout for special features with instructions. These are the cumulative values of all payouts, regardless of the ring pointer or the number of games played (6000).

In Figure 79, the cumulative ratio of the state of the game device, the cumulative advantageous zone ratio, the cumulative ratio of the game device with instructions, the "6000" game continuous game device ratio, the "6000" game device ratio, the cumulative continuous game device ratio, and the cumulative game device ratio correspond to the ratios of the six items described above, and are buffers for storing the calculated ratios. However, in the case of a "7P" type gaming machine, it is not necessary to calculate the cumulative advantageous zone ratio, and no buffer is required.
In addition, the cumulative ratio of the state of the game devices, etc., and the cumulative ratio of the advantageous zone (if necessary) are calculated for each game.
In contrast, the cumulative instruction-included role ratio, the "6000" game continuous role ratio, the "6000" game role ratio, the cumulative continuous role ratio, and the cumulative role ratio are calculated once for every "400" games.
79 shows the buffer addresses in order. In this embodiment, as shown in FIG. 79, the ratio calculated for each game is arranged first in the buffer address, followed by the ratio calculated once every 400 games. By arranging the buffers in this manner, it is possible to simplify the calculation control of the ratios.
On the other hand, the rotation display order of each ratio on the role ratio monitor 113 is as described above.
(1) Cumulative indication-included role ratio (7P) or cumulative advantageous zone ratio (7U)
(2) "6000" game continuous feature ratio (3) "6000 game" feature ratio (4) Cumulative continuous feature ratio (5) Cumulative feature ratio (6) Cumulative feature etc. state ratio.
The addresses of the ratio buffer are arranged in a cyclic display order, as shown in Fig. 79. By arranging the buffers in this way, it is possible to simplify the lighting control.

79, the total number of games upper limit flag is a flag for determining whether the total number of games has reached a count upper limit value, which will be described later. If the count upper limit value has not been reached, "00h" is stored, and if the count upper limit value has been reached (or has been reached), "FFh" is stored.
In addition, after "FFh" is stored in the total number of games upper limit flag, when it is determined that the total number of games upper limit flag is "FFh", the total number of games upper limit flag does not need to be updated, or the total number of games upper limit flag may be updated again to "FFh".
The total payout number upper limit flag is a flag for determining whether the cumulative total payout has reached the count upper limit. If the count upper limit has not been reached, "00h" is stored, and if the count upper limit has been reached (or has been reached), "FFh" is stored.
Since the cumulative total payout is a buffer of "4" bytes, the count upper limit value is "FFFFFFFFh" (hereinafter also referred to as "4 bytes full"). When the cumulative total payout value reaches "4" bytes full, the total payout number upper limit flag is set to "FFh".
As with the total number of games played upper limit flag, if "FFh" is stored in the total payout upper limit flag and then it is determined that the total payout upper limit flag is "FFh", the total payout upper limit flag does not need to be updated, or the total payout upper limit flag may be updated again to "FFh".

In addition, if the cumulative total payout value is, for example, "FFFFFFFEh," and "3" coins are paid out in the current game, the total payout limit flag may be set to "FFh" without updating the cumulative total payout value (leaving it as "FFFFFFFEh").
Alternatively, the cumulative total payout value may be updated from "FFFFFFFEh" to a full "4" bytes, and the total payout upper limit flag may be set to "FFh".
Alternatively, the cumulative total payout value may be updated from "FFFFFFFEh" to "00000001h" (carried up), and the total payout upper limit flag may be set to "FFh".
Since "4" bytes full is approximately "4.3" billion in decimal notation, it is actually impossible for the cumulative total payout to reach "4" bytes full.

The total number of games is a counter that counts all the number of games played, and is composed of a memory area of "4" bytes. When the total number of games reaches "4" bytes, "FFh" is stored in the total number of games upper limit flag described above.
As mentioned above, a "4" byte full is approximately "4.3" billion in decimal, so it is actually impossible for the total number of games to reach a "4" byte full.
The number of games played in the state of a special feature, etc. is a buffer that stores the total number of games played in which a special feature is activated and the total number of games played in which a continuous special feature is activated.
In addition, the number of plays in the advantageous zone is a buffer that stores the number of plays in the advantageous zone.
The number of games played in the above-mentioned reel state and the number of games played in the winning zone are also in a storage area of "4" bytes, and it is actually impossible for the area to become "4" bytes full.

Also, as shown in FIG. 79, when the ratio is calculated and exceeds "100", "0" is stored. Since the ratio will never exceed "100", when an abnormal value is calculated due to factors such as noise, the abnormal value is not stored, but "0" is stored. As a result, when the ratio is displayed on the role ratio monitor 113, it is displayed as "00". Therefore, when the ratio is displayed as "00", it is possible to determine that the ratio is an abnormal value.
On the other hand, when the calculated ratio is "100,""100" is stored. Then, when the ratio is displayed on the winning combination monitor 113, it is corrected to "99" and displayed. This allows the ratio to be corrected to a two-digit approximate value suitable for display. As will be described later, when transmitting gaming machine information including this ratio, the value before correction, "100," is transmitted, allowing a more accurate value to be transmitted.

As a method other than the above, when the ratio is calculated as an abnormal value due to a factor such as noise, the following configuration may be used, for example.
(1) If the calculated ratio exceeds "100" and is less than "255 (FFh)", the calculated value is stored in the role ratio monitor information calculation/display storage area without correction. In this case, when displaying the ratio, a symbol may be displayed in place of a number in the tens digit of the ratio.
For example, when "110 (D)" is stored as the ratio, it can be configured to be displayed as "y.0" when displayed by the role ratio monitor 113. Therefore, if the ratio to be displayed is, for example, the cumulative instruction-including role ratio, the role ratio monitor 113 displays "7P.y.0".
In this way, if the tenth digit of a ratio is displayed with a symbol, the ratio can be determined to be an abnormal value.
(2) If the calculated ratio exceeds "100" and is less than "255 (FFh)," the ratio may be displayed as a number within the range of "01" to "50."
Let's assume that the calculated ratio is, for example, "200(D)," and that "200(D)" is stored in the storage area for calculating and displaying the ratio monitor information, and that when displaying the ratio based on that value, it is displayed as "40." If the ratio is "40," it would normally be judged to be within the normal range. However, since the stored ratio is "200(D)," it will flash regardless of the ratio. Therefore, even if the ratio is displayed as "40," if it flashes, it can be judged to be an abnormal value.

(3) The ratio is calculated by "dividend/divisor", but if the divisor is "0", the division cannot be performed in theory, and therefore the ratio cannot be calculated. In such a case, the value of the register in which the calculation result is stored can be configured to be "FFh". Then, if the value of the register in which the calculation result is stored is "FFh", the value of the memory area for calculating and displaying the role ratio monitor information can be configured not to be updated.
On the other hand, if the divisor is "0", "0" may be stored in the memory area for calculating and displaying the role ratio monitor information.

In addition to the above, the following methods can be mentioned:
(1) If the result of calculating the ratio is a value other than "0" to "99 (D)", the value in the memory area for calculating and displaying the role ratio monitor information will not be updated.
(2) If the calculated ratio is a value of "100 (D)", it may be corrected to "99 (D)" and stored in a memory area for calculating and displaying role ratio monitor information.
(3) If the calculated ratio exceeds "100 (D)" and is less than "255 (D) (FFh)," it may be corrected to "99 (D)" and stored in the memory area for calculating and displaying the role ratio monitor information.

80 and 81 are flowcharts showing the ratio calculation process. Fig. 81 is a flowchart following Fig. 80.
This processing is performed by the main control CPU 510 and is executed by a program stored outside the area of use.
In the flowchart of the sixth embodiment, the gaming machine 10 that calculates and displays the cumulative advantageous zone ratio is referred to as the "7U" type, and the gaming machine 10 that calculates and displays the cumulative instruction-included feature ratio is referred to as the "7P" type.
In the figure, the steps marked "7U type only" are executed only by the gaming machine 10 that calculates and displays the cumulative advantageous zone ratio. On the other hand, the steps marked "7P type only" are executed only by the gaming machine 10 that calculates and displays the cumulative instruction-included role ratio (the same applies to the following flowcharts).
First, in step S672, the payout number for the current game is added to the total payout for the game "400" corresponding to the ring pointer.
Here, "corresponding to the ring pointer" has the following meaning.
As mentioned above, the ring pointer ranges from "0" to "14." Correspondingly, the "400" total payout is made up of 15 buffers ranging from "400" total payout "0" to "400" total payout "14."
Similarly, the total payout for "400" consecutive games is made up of 15 buffers ranging from "400" consecutive games total payout "0" to "400" consecutive games total payout "14".
Similarly, the total payout of "400" game devices is also made up of 15 buffers ranging from "0" total payout of "400" game devices to "14" total payout of "400" game devices.
In step S672, when the ring pointer is "n (n=0 to 14)", this means that the payout number for the current game is added to the total payout "n" for the game of "400".

In the next step S673, it is determined whether or not the current game is currently in operation of a special device or display on the instruction monitor (instruction function is in operation). If it is determined that the current game is currently in operation of a special device or display on the instruction monitor, the process proceeds to step S674, and if it is determined that the current game is not currently in operation, the process proceeds to step S675.
In step S674, the payout amount for the current game is added to the payout amount for the game instruction "400". Then, the process proceeds to step S675.

In step S675, it is determined whether a first-class special feature (continuous feature) is in operation during the current game. If it is determined that a first-class special feature is in operation, the process proceeds to step S676; if it is determined that a first-class special feature is not in operation, the process proceeds to step S677. In step S676, the payout number for the current game is added to the total payout number for the continuous feature for the game "400" corresponding to the ring pointer. As above, when the ring pointer is "n", the payout number for the current game is added to the total payout number for the continuous feature for the game "400". Then, the process proceeds to step S677.

In step S677, it is determined whether or not the current game is currently in the operation of a special feature. If it is determined that the current game is currently in the operation of a special feature, the process proceeds to step S678, and if it is determined that the current game is not currently in the operation of a special feature, the process proceeds to step S679.
In step S678, the payout number for the current game is added to the total payout of the game device "400" corresponding to the ring pointer. As above, when the ring pointer is "n", the payout number for the current game is added to the total payout of the game device "n" of "400". Then, the process proceeds to step S679.
In step S679, it is determined whether the value of the total game count upper limit flag is "FFh." If it is determined that the value of the total game count upper limit flag is "FFh," the process proceeds to step S687 in Figure 81, and if it is determined that the value is not "FFh," the process proceeds to step S680.
In step S680, "1" is added to the total number of games. In the next step S681, it is determined whether the total number of games after adding "1" to the total number of games exceeds "FFFFFFFFh (full 4 bytes)" (whether an overflow has occurred). If it is determined that the total number of games exceeds "FFFFFFFFh", the process proceeds to step S682, and if it is determined that the total number of games does not exceed "FFFFFFFFh", the process proceeds to step S683 in FIG. 81.
In step S682, the total number of games is set to "FFFFFFFFh," and the total number of games upper limit flag is set to "FFh." Then, the process proceeds to step S687.

In step S683 of Fig. 81, it is determined whether the reel is in operation or the reel continuous operation device is in operation. If it is determined that the reel is in operation or the reel continuous operation device is in operation, the process proceeds to step S684, and if it is determined that the reel is not in operation, the process proceeds to step S685.
In step S684, "1" is added to the number of games in the bonus state, etc. Then, the process proceeds to step S685.
In step S685, it is determined whether the current game is in a favorable zone. If it is determined that the current game is in a favorable zone, the process proceeds to step S686, and if it is determined that the current game is not in a favorable zone, the process proceeds to step S687. In step S686, "1" is added to the number of games in the favorable zone. Then, the process proceeds to step S687.
In step S687, the cumulative reel state ratio is calculated, and the calculated value is stored.
Next, the process proceeds to step S688, where the cumulative advantageous zone ratio is calculated and the calculated value is stored. In this way, the calculation and storage of the cumulative bonus item state ratio and the calculation and storage of the cumulative advantageous zone ratio are performed for each game.
Next, the process proceeds to step S689, where the game number counter is incremented by "1." In the next step S690, it is determined whether the value of the game number counter has reached "400" games. If it is determined that "400" games have been reached, the process proceeds to step S691 (FIG. 82), where a "400" per-game ratio calculation is executed. On the other hand, if it is determined that "400" games have not been reached, the process according to this flowchart is terminated.
As described above, regardless of whether the total number of plays upper limit flag is "FFh" or not, update processing is executed for the "400" total payout for games corresponding to the ring pointer, the "400" total payout for game instructions-including devices, the "400" total payout for game continuous devices corresponding to the ring pointer, and the "400" total payout for game devices corresponding to the ring pointer.
On the other hand, if the total number of plays upper limit flag is "FFh", update processing is not performed for the number of plays in the reel state and the number of plays in the advantageous zone.
Furthermore, even if the total number of plays upper limit flag is "FFh", update processing is executed for the cumulative reel state ratio and cumulative advantageous zone ratio.

As described above, if the ratio calculated in step S687 or S688 is "100 (D)", "100 (D)" is stored. Then, when displayed by the winning ratio monitor 113, "99" is displayed.
On the other hand, if the ratio calculated in step S687 or S688 exceeds "100 (D)", "0" is stored. Then, when displayed by the winning combination ratio monitor 113, "00" is displayed.

Figures 82 and 83 are flowcharts showing the calculation of the ratio per 400 games in step S691 in Figure 81. Figure 83 is a flowchart following Figure 82.
First, in step S760, the game number counter is initialized. The game number counter is a counter that counts in the range of "0" to "399", so the value is set to "0" by initialization.
Next, proceeding to step S761, the total value of 15 sets of "400" total payouts (the total value of "400" total payouts "0" to "400" total payouts "14") is set to a total payout of "6000". In the next step S766, similar to step S765, the total value of 15 sets of "400" total payouts of consecutive game accessories (the total value of "400" total payouts of consecutive game accessories "0" to "400" total payouts of consecutive game accessories "14") is set to a total payout of "6000". Furthermore, in the next step S767, similar to step S761, the total value of 15 sets of "400" total payouts of consecutive game accessories (the total value of "400" total payouts of consecutive game accessories "0" to "400" total payouts of consecutive game accessories "14") is set to a total payout of "6000".
In the next step S764, it is determined whether the total payout number upper limit flag is "FFh". If it is determined that the total payout number upper limit flag is not "FFh", the process proceeds to step S765, and if it is determined that the total payout number upper limit flag is "FFh", the process proceeds to step S772 in FIG.
In step S765, the total payout for the game of "400" corresponding to the ring pointer is provisionally added to the cumulative total payout. Then, in the next step S762, it is determined whether the result of the provisional addition in step S761 exceeds "FFFFFFFFh". If it is determined that it exceeds "FFFFFFFFh", the process proceeds to step S768, and if it is determined that it does not exceed "FFFFFFFFh", the process proceeds to step S767.
In step S768, the total payout upper limit flag is set to "FFh." Then, the process proceeds to step S772.

In step S767, the provisionally added value in step S765 is set to the cumulative total payout. Next, the process proceeds to step S769, where the total payout of "400" consecutive game bonuses corresponding to the ring pointer is added to the cumulative total payout of consecutive game bonuses.
In the next step S770, the total payout of the game device "400" corresponding to the ring pointer is added to the total cumulative payout of the game device.
In the next step S771, the total payout of "400" game instruction-included devices is added to the cumulative total payout of instruction-included devices. Then, the process proceeds to step S772. Note that in this example, the total payout of "400" game instruction-included devices is added to the cumulative total payout of instruction-included devices for each "400" game, but this is not limited to this. For each game, when a device is in operation or when the instruction monitor is displayed (when "Yes" is returned in step S673 of FIG. 80), the payout number for the current game may be added to the cumulative total payout of instruction-included devices.

In step S772, "1" is added to the ring pointer. Next, the process proceeds to step S773, where it is determined whether the ring pointer has become "15" as a result of the addition of "1." If it is determined that it has become "15," the process proceeds to step S774; if it is determined that it has not become "15," the process proceeds to step S775.
In step S774, the value of the ring pointer is initialized (set to "0"), and the process proceeds to step S775.
In step S775, the total payout for the game "400" corresponding to the ring pointer is initialized (set to "0").
In the next step S776, the total payout of the "400" consecutive game bonuses corresponding to the ring pointer is initialized (set to "0").
In the next step S777, the total payout of the game device "400" corresponding to the ring pointer is initialized (set to "0").

In the next step S778, the total payout for the 400 game instructions is initialized (set to "0").
Next, the process proceeds to step S779, where the cumulative instruction-inclusive feature ratio is calculated and the value is stored. In the next step S780, the "6000" game continuous feature ratio is calculated and the value is stored.
In the next step S781, the "6000" game consecutive feature ratio is calculated and the value is stored. In the next step S782, the cumulative consecutive feature ratio is calculated and the value is stored. In the next step S783, the cumulative feature ratio is calculated and the value is stored. Then, the processing according to this flowchart is terminated.
As described above, regardless of whether the total payout upper limit flag is "FFh" or not, update processing is executed for the total payout of "6000" game, the total payout of "6000" game continuous device, and the total payout of "6000" game device.
On the other hand, if the total payout number upper limit flag is "FFh", update processing is not performed for the cumulative total payout, cumulative total payout for consecutive games, cumulative total payout for games, and cumulative total payout for games with instructions.
Furthermore, even if the total payout upper limit flag is "FFh", update processing is executed for the cumulative instruction-included role ratio, the "6000" game continuous role ratio, the "6000" game role ratio, the cumulative continuous role ratio, and the cumulative role ratio.

As described above, if the ratio calculated in steps S779 to S783 is "100 (D)", "100 (D)" is stored. Then, when displayed by the winning ratio monitor 113, "99" is displayed.
On the other hand, if the ratio calculated in steps S779 to S783 exceeds "100 (D)", "0" is stored. Then, when displayed by the winning ratio monitor 113, "00" is displayed.

Next, a description will be given of the complete function in the sixth embodiment. The "complete function" corresponds to the game stopping function of the gaming machine (ending the game from that day onwards).
When the minimum difference number after the power of the gaming machine 10 is turned on is set to "0," and the difference number reaches "+19,000 (coins)," it is determined that the activation condition for the complete function is met, and the complete function is enabled. This makes it possible to prevent excessive gambling.
In the sixth embodiment, first, the difference number in the advantageous zone is counted by a difference number counter.
Here, the "difference number in the advantageous period" refers to the difference in the number of coins when the start of the advantageous period is set to "0." In other words, it is not the minimum value of the difference number during the advantageous period, but the difference number when the start of the advantageous period is set to "0." Therefore, when the difference number becomes a negative value during the advantageous period, the negative value is counted. Also, the difference number counter does not count the difference number during the normal period.
For example, the difference counter is a 2-byte decrement counter. When the difference counter during the advantageous period exceeds "+2400 (pieces)", it is determined that the end condition of the advantageous period is met.

Here, a first example of a difference counter is a method in which the initial value is set to "+2415" (pieces) ("096Fh" in hexadecimal) at the start of the advantageous period, and when the difference number for the current game is negative, the difference number is added to the difference counter, and when the difference number for the current game is positive, the difference number is subtracted from the difference counter.
Specifically, first, "+2415" is set at the start of the advantageous period, and when the difference in the first game is "-3 (pieces)" (number of bets "3", number of payouts "0"), "3" is added to the difference counter and the difference counter is updated to "+2418". On the other hand, when the difference in the first game is "+11 (pieces)" (number of bets "3", number of payouts "14"), "11" is subtracted from the difference counter and the difference counter is updated to "+2404".
When the difference counter reaches "0", it is determined that the difference in the advantageous period has exceeded "+2400 (pieces)", and the advantageous period ends.
In the example of FIG. 85 described later, the difference number counter value increases as the difference number in the current game increases.

As a second example of a difference number counter, the difference number at the start of the advantageous period is set to "0", and when the difference number counter exceeds "+2400 (pieces)" (specifically, when the difference number counter value in hexadecimal is "0961h" or greater), it is determined that the end condition of the advantageous period is met.
In both the first and second examples above, when the advantageous period ends, the difference counter is cleared.

In the sixth embodiment, secondly, an MY counter (also called a "stop counter") counts MY from the time the power is turned on. Here, "MY" is the value when the minimum value of the difference number is set to "0" (the same as the difference number counter in the other embodiments described above).
The MY counter is initialized to "0000h" when the power is turned on.
And, for example, when the power is turned on,
1st game: Number of bets "3", number of payouts "0", MY counter "0000h"
Second game: Number of bets: "3", number of payouts: "14", MY counter: "000Bh"
3rd game: Number of bets "3", number of payouts "0", MY counter "0008h"
4th game: Number of bets "3", number of payouts "0", MY counter "0005h"
5th game: Number of bets "3", number of payouts "0", MY counter "0002h"
6th game: Number of bets "3", number of payouts "0", MY counter "0000h"
:
This becomes:
Here, in the first game, the difference is "-3", so adding the difference "-3" to the initial value "0000h" of the MY counter results in "FFFDh". However, when a borrow occurs, it is corrected to "0000h" each time. In other words, the minimum value is set to "0".
Similarly, for the sixth game, the difference is "-3", so when the difference "-3" is added to the MY counter "0002h", it becomes "FFFFh", but after correction it becomes "0000h".
When the value of the MY counter since power-on reaches "+19000" (4A38h), the complete function is enabled, the gaming machine 10 is stopped, and subsequent play (operation for that day) is terminated.
Furthermore, rather than ending the payout process for that game when the MY counter value reaches "+19000", all payouts for that game are executed.
For example, even if the MY counter value is "+18999", the number of bets for the current game is "3", and the number of payouts is "14", the complete function will be activated after the payout of "14" coins for the current game is executed.
Unlike the difference counter, the MY counter counts MY even in the normal interval.
In the sixth embodiment, the number of games played after the gaming machine 10 is turned on is counted, and even if the number of games reaches the upper limit "65535 (FFFFh)", the MY counter for determining whether or not to activate the complete function continues to be updated. As a result, even if there is a hall that leaves the power of the gaming machine 10 on, for example, the MY counter for determining whether or not to activate the complete function continues to be updated, so even if the number of games played after the power of the gaming machine 10 is turned on reaches the upper limit "65535 (FFFFh)", the complete function can be activated when the value of the MY counter reaches "+19000".
In contrast, as will be described later, MY (see Figure 90 described later) in the memory area for transmitting gaming machine performance information will not be updated if the number of games played after the gaming machine 10 is powered on reaches the upper count limit value of "65535 (FFFFh)."

Figure 84 is a diagram showing the transition of the difference number and MY in the sixth embodiment. In this example, it is assumed that the normal period begins when the power is turned on. In Figure 84, the solid line indicates the favorable period, and the wavy line indicates the normal period. Note that this graph shows the transition of the difference number (MY), not the values of the difference number counter or MY counter.
First, when the power is turned on ("A" in the figure), both the difference number and MY are "0".
Then, assume that the transition from the normal zone to the advantageous zone occurs at point "B" in the figure. Therefore, at this point "B" (the start of the advantageous zone), the difference counter is "0" (because the difference counter is not updated during the normal zone).

Furthermore, the difference number decreases from point "B" in the figure, and when it reaches point "C", the value of the difference number counter at point "C" is "B-C". Also, the MY counter is at its minimum value "0".
Then, when the difference number increases due to the execution of a sub-bonus or the like in the advantageous zone, and when point "D" is reached and the difference number counter (D-B) exceeds "2400", the conditions for ending the advantageous zone are met at point "D", the advantageous zone ends, and the difference number counter is cleared (becomes "0"). The next game will then be in the normal zone, and if the conditions for transitioning to the advantageous zone are met in the normal zone, the game will transition to the advantageous zone again.

On the other hand, after power is turned on, the minimum difference number is at point "C", and thereafter the difference number increases without falling below point "C". When point "E" is eventually reached in the diagram, MY at point "E" is "E-C". Then, when point "E" is reached, the value of the MY counter (E-C) reaches "19000". This enables the complete function to be activated, and the gaming machine 10 can stop playing.

Figure 85 is a diagram showing the relationship between the transitions of the difference counter and MY counter and the power on/off. In the figure, the solid line shows the transition of the difference counter, and the wavy line shows the transition of the MY counter. Note that the power on/off in Figure 85 is a simple power on/off, and no RWM clear (setting change) has been made. Also, in Figure 85, it is assumed that the advantageous zone is in place from the start.
As shown in FIG. 85, the difference counter starts from "0", and even if the value of the difference counter becomes negative, the minimum value of the MY counter is "0".
Furthermore, at point "A" in the figure, when the value of the difference counter exceeds "2400", the advantageous zone ends, and the difference counter is cleared to "0". On the other hand, the MY counter does not change.
In the normal period thereafter, the MY counter is updated, but the difference counter is not updated. Then, when the normal period transitions to the advantageous period, the difference counter also starts to be updated.
Next, when the power is turned off at point "B" in the figure and then turned on at point "C" in the figure, the MY counter is cleared to "0".
On the other hand, the difference counter is not cleared by turning the power on and off. Therefore, the value of the difference counter at point "C" in the figure is the value of the difference counter at point "B" in the figure.

Also, in Figure 85, the bottom table shows the status of the difference counter and MY counter when the power is turned on/off without RWM clearing (for example, when the power is restored without transitioning to setting change mode) and when the RWM is cleared (for example, when the power is restored and transitions to setting change mode).
As described above, when the power is turned on/off without clearing the RWM, the value of the difference counter is maintained but the MY counter is cleared. In contrast, when the power is turned on/off with the RWM cleared (for example, when changing settings), both the difference counter and the MY counter are cleared.

In addition, the "complete function activation flag" is a flag that turns on when the MY counter reaches "19000" and the complete function is activated, and is composed of, for example, 1 byte of data, and is "00h" when off and "FFh" when on.
Furthermore, the "complete function provisional flag" is a flag that is turned on when the MY counter has reached "19000" but the complete function cannot be activated, for example, when the game is in a special game mode (one of the devices is in operation), and is composed of, for example, 1 byte of data, and is "00h" when off and "FFh" when on.
These complete function active flag and complete function provisional flag are configured so as not to be cleared by turning the power on/off without clearing the RWM.

Therefore, when the MY counter reaches "19000" during the special game state, the complete function activation flag remains off, but the complete function provisional flag is turned on. If the power is turned off before the special game state ends and then turned on again, the complete function provisional flag will return to the on state even if the MY counter reaches "0." Therefore, when the special game state ends after power is restored from a power outage, the complete function activation flag can be turned on and the complete function can be activated.
However, when the power is turned on/off (when the setting is changed) with the RWM cleared, both the complete function active flag and the complete function provisional flag are cleared.

Figure 86 is a flowchart showing the flow from when the power is turned on by the main control CPU 510 to the main processing, and includes processing related to the complete function.
First, when the power is turned on in step S541, the next step S542 executes a power-on process. This power-on process includes initialization of a specified storage area. If the power is turned on without clearing the RWM, the initialization process includes initialization (clearing) of the MY counter. However, initialization of the difference counter, the complete function active flag, and the complete function provisional flag is not executed.
On the other hand, when the power is turned on with the RWM cleared, the MY counter, the difference counter, the complete function active flag, and the complete function temporary flag are all initialized.
Next, the flow proceeds to step S543, where error processing (see FIG. 87, which will be described later) is executed. During this error processing, processing relating to the complete function, which will be described later, is executed.

In the next step S545, a deposit/settlement acceptance process is executed. This process involves, for example, transmitting a 3-bet command to the medal count control CPU 520 when operation of the 3-bet switch 40b is detected, and receiving a command from the medal count control CPU 520 to set the number of bets to "3." To give a specific example, if the number of bets is "0" and the number of medals (also referred to as "total points") displayed on the medal count display unit (also referred to as "game medal count display unit,""medal count display device," or "game medal count display device") 121 is "500," and operation of the 3-bet switch 40b is detected, the number of bets will become "3," and the number of medals displayed on the medal count display unit 121 will become "497."
Furthermore, for example, when operation of the settlement switch 46 is detected when the number of bets is "3", the process transmits a settlement command to the medal count control CPU 520 and receives a command to set the number of bets to "0" from the medal count control CPU 520. To give a specific example, if operation of the settlement switch 46 is detected when the number of bets is "3" and the number of medals displayed on the medal count display unit 121 is "497", the number of bets will become "0" and the number of medals displayed on the medal count display unit 121 will become "500".
In the next step S546, it is determined whether or not the start switch 41 has been operated, and if it is determined that the start switch 41 has been operated, the process proceeds to step S547.
In step S547, a lottery for a winning combination (winning number) is carried out, and in the next step S548, the reels 31 start to rotate.
In step S549, it is determined whether or not the stop switch 42 has been operated, and if it is determined that the stop switch 42 has been operated, the process proceeds to step S550, where the reel 31 corresponding to the operated stop switch 42 is controlled to stop.

In the next step S551, it is determined whether all the reels 31 have stopped. If it is determined that all the reels 31 have not stopped, the process returns to step S549, and if it is determined that all the reels 31 have stopped, the process proceeds to step S552. In step S552, a winning combination is determined. Then, the process proceeds to step S553, where medals corresponding to the winning combination are paid out. This process involves transmitting a command corresponding to the number of medals to be paid out to the medal count control CPU 520. Upon receiving the payout command, the medal count control CPU 520 updates the display in the medal count display unit 121. To give a specific example, if the number of medals displayed in the medal count display unit 121 is "497" and the number of medals paid out (number of medals awarded) is "14," the number of medals displayed in the medal count display unit 121 is updated to "511."
The display control of the medal count display unit 121 as described above is executed by the medal count control CPU 520.
Next, the flow proceeds to step S555, where a complete function calculation process is executed. This process involves updating the MY counter, etc., and is the process shown in FIG. 88, which will be described later.
Next, the process proceeds to step S556, where a game status update process is executed, and then the process returns to step S543.

FIG. 87 is a flowchart showing the error processing in step S543 of FIG.
First, in step S561, it is determined whether or not the game is in a special game state (a special device is operating). In this embodiment, the complete function is not activated even if the activation conditions for the complete function (play stop conditions) are met in the special game state. If it is determined that the game is in a special game state, the process proceeds to step S567, where error processing other than processing related to the complete operation is executed. On the other hand, if it is determined in step S561 that the game is not in a special game state, the process proceeds to step S562. In step S562, the complete function activation flag is read. Then, in the next step S563, it is determined whether or not the complete function activation flag is "FFh" (on). If it is determined that the flag is "FFh", the process proceeds to step S564; if it is determined that the flag is not "FFh", the process proceeds to step S567.

In step S564, the activation of the complete function is notified by transmitting an activation signal of the complete function to the sub-control board 80, and notifying the activation of the complete function on the image display device 23 or the like.
Next, the process proceeds to step S566, where a complete signal is output to the outside. This ends the error processing. The complete signal is output for 30 seconds, and then the complete signal is turned off. However, the number of seconds for which the complete signal is output and the timing at which the complete signal is turned off can be set arbitrarily. Furthermore, when the process proceeds to step S566, the process does not proceed to step S545 and subsequent steps in FIG. 86. As a result, the operation switches (bet switch 40, start switch 41, stop switch 42) are not accepted, and the game cannot proceed.
In this example, the processing related to the operation of the complete function is executed within the error processing of step S543, but this is not limited to this. For example, processing related to the operation of the complete function may be provided independently as the processing next to the error processing, and the processing of steps S561 to S566 in Figure 87 may be executed.

FIG. 88 is a flowchart showing the complete function calculation process in step S555 of FIG.
First, in step S571, it is determined whether the complete function provisional flag is on (FFh). If it is determined that the complete function provisional flag is not on, the process proceeds to step S572, and if it is determined that the complete function provisional flag is on, the process proceeds to step S578.
In step S572, it is determined whether the complete function operation flag is on (FFh). If it is determined that the complete function operation flag is on, that is, that the complete function is already operating, the processing according to this flowchart ends. This is because if the complete function is already operating, the MY counter update process and the like will not be executed.
If it is determined in step S572 that the complete function activation flag is not on, and the process proceeds to step S573, it is determined whether or not the replay is in progress. In this embodiment, the MY counter is not updated during the replay operation, so if it is determined that the replay is in progress, the process according to this flowchart is terminated.
If it is determined that the replay is not in progress, the process proceeds to step S574.

In step S574, the MY counter value is updated based on the number of bets and the number of payouts in the current game.
In the process of step S574, the actual MY counter (main control RWM 512) is not updated, but the MY counter value is stored in a register and calculation is performed on the register.
In the next step S575, it is determined whether the MY counter value is less than 0. If it is determined that the MY counter value is not less than 0, the process proceeds to step S576; if it is determined that the MY counter value is less than 0, the process proceeds to step S581.
In step S581, the MY counter (main control RWM 512) is updated to "0." Then, the process according to this flowchart ends.

On the other hand, when the process proceeds from step S575 to step S576, it is determined whether the MY counter value has reached "19000." As described above, if the MY counter value is "4A38h" or greater, it is determined that the MY counter has reached "19000." If it is determined that the MY counter has reached "19000," the process proceeds to step S577; if it is determined that the MY counter has not reached "19000," the process according to this flowchart ends.
Here, if it is determined that the MY counter value has not reached "19000", the calculation result (register value) of step S574 is saved in the MY counter (main control RWM 512) and then the processing according to this flowchart is terminated.
On the other hand, when it is determined that the MY counter value in the register has reached "19000", the register value may or may not be saved in the MY counter thereafter.

In step S577, the complete function provisional flag is set to ON (FFh). Next, the process proceeds to step S578, where it is determined whether the current game is in a special game state (such as 1BB game or RB game). Note that if the special game state has ended in the current game (for example, if it is the final game of 1BB game), the special game state has ended at the time of step S578, so it is determined that the current game is not in a special game state.
If it is determined that the special game state is in effect, the processing according to this flowchart is terminated. Therefore, in the special game state, when the MY counter reaches "19000," the complete function provisional flag is turned on in step S577, but since step S579 is not passed through, the complete function activation flag is not turned on (FFh). Therefore, the complete function does not operate in the special game state.

On the other hand, if it is determined in step S578 that the special game state is not in effect, the process proceeds to step S579. In step S579, the complete function activation flag is set to ON (FFh). Next, the process proceeds to step S580, where the complete function temporary flag is set to OFF (00h). The process according to this flowchart then ends. If the complete function activation flag is set to ON in step S579, the complete function will be activated at the start of the next game according to step S543 in FIG. 86 and FIG. 87.
Also, in the special game state, when the complete function provisional flag is turned on in step S577, the complete function provisional flag remains on (the complete function activation flag is off) until the special game state ends, and when the special game state ends, the complete function activation flag is turned on (step S579) and the complete function provisional flag is turned off (step S580).

Next, image control by the sub-control board 80 regarding the complete function will be described.
If the complete function were suddenly activated when the MY counter reached "19000," it would be a surprise attack on the player. Therefore, when the activation of the complete function is approaching, a notice of the activation of the complete function is given to the player.
FIG. 89(a) is a diagram showing an image giving a notice (advance notification) of the activation of the complete function.
The sub-control board 80 counts MY independently after power is turned on. However, this is not limited to this, and the main control board 50 may transmit the MY counter value to the sub-control board 80 at the end of each game.

The sub-control board 80 notifies the user of the activation of the complete function when MY reaches "18500", in other words, when there are "500" sheets (or less) remaining until the complete function is activated.
As shown in FIG. 89(a), for example, "500 remaining until complete function activation" is displayed.
Then, when MY increases by, for example, "+11" in the next game, the notification image of the complete function activation is updated to display "489 coins remaining until the complete function is activated." In this way, the notification of the complete function activation is made so that the quantitative change until the activation condition of the complete function (the MY counter reaching "19000") is met can be visually recognized.
It should be noted that the notification of the activation of the complete function does not have to start when there are "500" coins remaining, but various settings are possible, such as "300" coins remaining, "100" coins remaining, etc.
In Figure 89(a), the area of the preview image for the activation of the complete function is shown by a dot pattern, and this dot pattern area represents the front layer. Therefore, for example, if there is an area where a predetermined display on the screen and the preview image for the activation of the complete function overlap, the preview image for the activation of the complete function is displayed in the overlapping area, and the predetermined image (back layer) is not displayed. However, the preview image area for the activation of the complete function may be made transparent so that the image behind it (such as a performance image) can be seen.
In the example of FIG. 89(b), the area indicated by the dot pattern also indicates the foremost layer.

89(b) is a diagram showing an example in which the MY counter reaches "19000" and an image indicating that the complete function is activated is displayed. In FIG. 89(a), when the MY counter reaches "19000," the display switches to that shown in FIG. 89(b). Here, the image indicating that the complete function is activated occupies a part of the image display area, but this is not limiting, and the image indicating that the complete function is activated may be arranged to occupy the entire image display area.
Furthermore, when the complete function is activated, it is necessary to operate the counting switch 47 to transmit all medals to the lending unit 200. Therefore, a display urging the player to count is also displayed.

In this example, when the complete function is to be activated when the MY counter reaches "19000", the activation of the complete function is announced when the MY counter reaches "18900".
Here, if the value of the MY counter reaches "19000" without decreasing after the completion function operation is notified, the completion function operation is continuously notified from the time when the MY counter reaches "18900" until it reaches "19000".
On the other hand, if the value of the MY counter decreases after it reaches "18900", when the value of the MY counter reaches a predetermined value, the advance notice of the activation of the complete function is terminated.
If the MY counter fluctuates up and down as the game progresses, with "18900" as the threshold value, the state in which the complete function is activated will frequently alternate between being notified and not being notified, and for example, the image in which the complete function is activated will sometimes be displayed and sometimes not.
Therefore, in this embodiment, once a notice of the activation of the complete function is given, the notice of the activation of the complete function is maintained until the MY counter becomes less than a predetermined value (for example, "18850").

Next, the gaming machine information notification will be described.
In the sixth embodiment, similar to the second embodiment described above, the gaming machine 10 transmits hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information to the rental unit 200 as gaming machine information notifications.
90 and 91 show memory areas provided in the usage area of the medal count control RWM 522, and are memory areas provided for transmitting gaming machine information notifications to the rental unit 200. Some of the memory areas in Fig. 90 and 91 include memory areas that store the same information as the memory areas shown in Fig. 78 and 79 described above, but are provided separately as memory areas for transmission in order to improve the efficiency of the transmission process.
90 shows a memory area for transmitting gaming machine performance information and a memory area for transmitting gaming machine installation information among the gaming machine information notifications. In FIG. 90, the addresses of the memory areas for transmitting gaming machine performance information are assumed to be consecutive numbers. Similarly, the addresses of the memory areas for transmitting gaming machine installation information are assumed to be consecutive numbers.

In the second embodiment, Figure 31 shows the gaming machine performance information, gaming machine installation information, and hall control/fraud monitoring information to be transmitted to the rental unit 200, and the memory areas for generating this transmission information are as shown in Figures 90 and 91 ("Grant" in Figure 31 is written as "Payout" in Figures 90 and 91).
In addition, the hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information shown in Figure 31 are all arranged in the order of the data in the telegram, and a memory area for transmission is provided to correspond to the order of the data in this telegram.
For example, the message for gaming machine performance information begins with:
(1) Total number of coins inserted: 3 bytes (2) Total number of coins paid out: 3 bytes (3) MY: 3 bytes:
The addresses of the storage areas are arranged in a manner that matches this data order, which simplifies the process of generating the gaming machine information notification.
In particular, in the gaming machine performance information, each ratio is arranged in the order shown in Figure 90, but this order differs from the display order of the role ratio monitor 113, and therefore differs from the address order of each ratio shown in Figure 79.

In addition, the memory areas for transmitting gaming machine installation information are also provided in the order of the data of the gaming machine installation information telegrams in FIG.
As described above, by arranging the addresses of the memory area for sending gaming machine information notifications in the order of the data of the gaming machine information notification message, the data of the gaming machine information notification message can be obtained by shifting the addresses of the memory area for sending at predetermined intervals (by "1"), thereby simplifying the sending process.
Furthermore, the storage area for transmitting hole control and fraud monitoring information shown in FIG. 91 is also provided in the data order of the hole control and fraud monitoring information in FIG.
31, the D6 bit of the hall control/fraud monitoring information for gaming machine fraud 1 is unused. In contrast, in this embodiment, this D6 bit is used as a complete signal.
The complete signal is a signal indicating that the complete function has been activated. This signal turns on ("1") after the complete function has been activated and the game has stopped. Furthermore, the complete signal remains on for approximately "30" seconds, and then turns off ("0").
In addition, the D5 bit of gaming machine fraud 1 is a security signal, and indicates that any of the setting change signal (D0), setting confirmation signal (D1), fraud detection signals 1 to 3 (D2 to D4), and complete signal (D6) are on (logical OR output).

In the gaming machine performance information transmission memory area of FIG.
(1) Total number of deposits (2) Total number of withdrawals (3) MY
(4) Total number of payouts for bonus items, (5) Total number of payouts for consecutive bonus items, and (6) Number of games played. Regardless of the data update in the memory area for calculating and displaying bonus item ratio monitor information, the six items are updated independently for sending gaming machine information notifications. The update timing is at the end of each game.
In addition, when the MY counter reaches "19000" or more, the main control CPU 510 needs to activate the complete function (play stop function). The value of the MY counter is used to determine whether or not to activate the complete function. Therefore, the main control RWM 512 of the main control CPU 510 is provided with an MY counter. This MY counter is the value after power is turned on, so it has the same value as the MY in the memory area for transmitting gaming machine performance information. Therefore, rather than counting independently, the MY in the memory area for transmitting gaming machine performance information may receive the value of the MY counter from the main control CPU 510 and store it in the MY in the memory area for transmitting gaming machine performance information.

On the other hand, in the memory area for transmitting gaming machine performance information, the following five items are updated based on the update of the memory area for calculating and displaying the role ratio monitor information (Figure 79): (1) cumulative role ratio, (2) cumulative consecutive role ratio, (3) cumulative advantageous zone ratio, (4) cumulative role ratio with instructions, and (5) cumulative role etc. state ratio.
Details will be described later, but in each ratio of the storage area for calculating and displaying the role ratio monitor information, the cumulative advantageous zone ratio and the cumulative role status ratio are updated every game. On the other hand, the cumulative role ratio, cumulative consecutive role ratio, and cumulative instruction-included role ratio are updated every 400 games.
Therefore, with regard to the cumulative advantageous zone ratio and cumulative role, etc. status ratio, the cumulative advantageous zone ratio and cumulative role, etc. status ratio in the memory area for transmitting gaming machine performance information are updated each time the values in the memory area for calculating and displaying role ratio monitor information are updated.
In contrast, for the cumulative role ratio, cumulative consecutive role ratio, and cumulative role ratio with instructions, the values in the memory area for calculating and displaying role ratio monitor information are updated every 400 plays, and the cumulative role ratio, cumulative consecutive role ratio, and cumulative role ratio with instructions in the memory area for transmitting gaming machine performance information are updated accordingly.

As explained in the second embodiment, when the ratio displayed on the role ratio monitor 113 is such that the cumulative number of games is less than the reference number of games, the identification segment is displayed in a flashing manner.
The standard number of games for each cumulative ratio is as follows:
(1) Cumulative indicative role ratio or cumulative advantageous zone ratio: 175,000
(2) Cumulative consecutive win ratio: 17,500
(3) Cumulative ratio of special features: 17,500
(4) Cumulative status ratio of special features: 175,000
Therefore, the value of the total number of games played in the memory area for calculating and displaying the role ratio monitor information is obtained, and for the cumulative instructed role ratio or cumulative advantageous zone ratio, and cumulative role etc. state ratio, if the total number of games played is less than "175,000", "FFh" is stored, and if the total number of games played is "175,000" or more, the values stored in the memory area for calculating and displaying the role ratio monitor information are stored.
Similarly, for the cumulative consecutive role ratio and cumulative role ratio, if the total number of plays is less than "17,500", "FFh" is stored, and if the total number of plays is "17,500" or more, the value stored in the role ratio monitor information calculation/display memory area is stored.

If the ratio is not a relevant item, "FFh" is stored.
For example, in a gaming machine that does not have any special features (RB, SB, CB), the cumulative special feature ratio and special feature state ratio are non-applicable items and store "FFh."
In addition, in gaming machines that do not have a continuous role (RB), the cumulative continuous role ratio becomes a non-applicable item and stores "FFh."
Furthermore, gaming machines with advantageous zones are either the "7U" type or the "7P" type. The "7U" type is a gaming machine with a specification that sets the advantageous zone ratio to 70% or less, and this gaming machine stores the cumulative advantageous zone ratio (the instructed role ratio is not applicable, so "FFh" is stored).
In contrast, the "7P" type is a gaming machine that is designed to have an instruction-based device ratio (the ratio of the number of payouts paid out due to the activation of the instruction function and the activation of the device to the total number of payouts) of 70% or less, and this gaming machine stores the cumulative instruction-based device ratio (the cumulative advantageous zone ratio is a non-relevant item, so "FFh" is stored).
Furthermore, when the result of calculating the ratio is "100 (D)", "100 (D)" is stored in the memory area for calculating and displaying the role ratio monitor information, and therefore "100 (D)" is also stored for that ratio in the memory area for transmitting gaming machine performance information.
Therefore, in this case, gaming machine performance information including the fact that the ratio is "100(D)" is transmitted. As a result, the ratio is displayed as "99", but when transmitted to the rental unit 200, a ratio of "100(D)" that has not been corrected to "99" (a more accurate value ratio) can be transmitted. As a result, when "99" is displayed on the role ratio monitor 113, it is possible to determine from the gaming machine performance information whether the true ratio is "100(D)" but is being displayed as "99" on the role ratio monitor 113 due to correction, or whether the true ratio is "99(D)" and is being displayed as "99" on the role ratio monitor 113.

As shown in Figure 90, the storage area for the number of games is "2" bytes. Therefore, the range that can be counted as the number of games is "0" to "65535 (FFFFh)". Therefore, until the storage area for the number of games reaches "FFFFh", each value in the storage area for transmitting gaming machine performance information is updated. After the storage area for the number of games reaches "FFFFh",
(1) Total number of deposits (2) Total number of withdrawals (3) MY
(4) Total number of payouts from special devices, (5) Total number of payouts from consecutive special devices, and (6) Number of times played will not be updated.
on the other hand,
The five items of (1) cumulative ratio of reels, (2) cumulative ratio of consecutive reels, (3) cumulative ratio of advantageous zones, (4) cumulative ratio of reels with instructions, and (5) cumulative ratio of reels, etc. status are updated for each game or every 400 games based on the value of the memory area for calculating and displaying the reel ratio monitor information, regardless of the number of games played.
Furthermore, even if the number of games has reached "FFFFh" and the value of the total number of inputs in the memory area for transmitting gaming machine performance information has not been updated, when the timing for transmitting the gaming machine performance information arrives, the gaming machine performance information will be transmitted to the rental unit 200.

Next, information processing by the medal count control CPU 520 (particularly, the transmission processing of gaming machine information notification) will be described.
FIG. 92 is a flowchart showing the main processing of the medal count control CPU 520.
When the power is turned on and the medal count control CPU program is started in step S221, step S222 executes initialization processing for the medal count control RWM 522. This processing is, for example, processing for initializing a storage area for transmitting gaming machine information notifications shown in Figures 90 and 91.
In contrast, the memory area for calculating and displaying the role ratio monitor information shown in Figures 78 and 79 is not initialized.
Next, the process proceeds to step S223, where the main control startup standby timer M1 is set to "3000." After the main control startup standby timer M1 is set to "3000," it is subsequently decremented by "1" for each interrupt process (every "1" ms). Therefore, after "3000" ms, the main control startup standby timer M1 becomes "0."
When the power is turned on, the start-up processes of the main control CPU 510 and the medal count control CPU 520 are executed independently, but in this embodiment, the medal count control CPU 520 is configured to start up before the main control CPU 510. Therefore, the main control start-up wait timer M1 is set to wait until the main control CPU 510 starts up (the wait process is executed for 3000 ms).
In the next step S224, interrupt processing by the medal count control CPU 520 is prohibited. By controlling in this manner, it is possible to prevent the medal count control CPU 520 from executing interrupt processing until the interrupt processing is permitted in step S227, which will be described later. In other words, it is possible to set the main control startup standby timer M1 to "3000" before starting interrupt processing.
In the next step S225, a command reception process is executed, which is a process for receiving various commands transmitted from the main control CPU 510 and the like.

The command reception process includes, for example, the following:
1) When the power is turned on, a command is received from the main control CPU 510 indicating that the main control CPU 510 has started up.
2) When the power is turned on, the main control chip ID number, main control chip manufacturer code, and main control chip product code (commands required to generate gaming machine installation information) are received from the main control CPU 510.
3) When the power is turned on, a command for the role ratio type (either "7U" type or "7P" type) to specify the type of display on the role ratio monitor 113 is received from the main control CPU 510.
4) When the start switch 41 is received, a command for the number of inputs is received from the main control CPU 510.
5) When all reels 31 stop, a command for the payout number is received from the main control CPU 510.
6) When all reels 31 stop, a command for the operation status of reels, etc. is received from the main control CPU 510.
7) Receives main control status 1, main control status 2, gaming machine error status, fraud detection status 1 (gaming machine fraud 1), fraud detection status 2 (gaming machine fraud 2), fraud detection status 3 (gaming machine fraud 3) (commands necessary to generate hall control and fraud monitoring information) from the main control CPU 510 at any time.
8) Receive a rental notification (see FIG. 32) from the rental unit 200 at any time.

In the next step S226, it is determined whether the power-off flag is on. If it is determined that the power-off flag is not on, the process proceeds to step S227, and if it is determined that the power-off flag is on, the process proceeds to step S228.
In step S228, a power-off process is executed, in which a checksum is calculated and then a power-off wait (loop) is executed.
On the other hand, when the process proceeds to step S227, interrupt processing by the medal count control CPU 520 is permitted, and the process then proceeds to step S224.
By permitting interrupt processing in this way, when the process proceeds to the power-off process in step S228, it is possible to prevent the medal count control CPU 520 from executing interrupt processing (the interrupt prohibition in step S224 continues). Therefore, since the process proceeds to the power-off process in step S228 and interrupt processing is not executed when the checksum is being calculated, etc., it is possible to prevent the data in the medal count control RWM 522 from being updated while the checksum is being calculated.

In addition, in Figure 92, after the main control start-up waiting timer M1 is set, if a power outage is detected before the main control start-up waiting timer M1 becomes "0", the power outage processing will proceed to step S228.
Here, after the main control startup standby timer M1 is set, a command may be received from the main control CPU 510 even before 3000 ms have elapsed. Therefore, when a power outage is detected, a power outage process is executed, which includes a process for backing up the command received from the main control CPU 510.

93 is a flowchart showing the interrupt process by the medal count control CPU 520. It is assumed that the interrupt cycle by the medal count control CPU 520 is 1 ms.
When the interrupt process is started in step S231, first, in step S232, it is determined whether or not a power-off signal has been detected. If it is determined that a power-off signal has not been detected, the process proceeds to step S234, and if it is determined that a power-off signal has been detected, the process proceeds to step S233. In step S233, the power-off flag is turned on. Then, the process proceeds to step S234.
The processes of steps S232 and S233 are executed regardless of whether the main control activation wait timer M1 has reached "0," whether the VL signal is on, or whether the post-connection confirmation wait timer M2 has reached "100" or greater. This makes it possible to promptly transition to power-off processing when it is determined that the conditions for executing power-off processing have been met.
In step S234, the main control startup standby timer M1 is updated. This process subtracts "1" from the value of the main control startup standby timer M1. Then, in the next step S235, it is determined whether the main control startup standby timer M1 has reached "0." If it is determined that the main control startup standby timer M1 has reached "0," the process proceeds to step S236 and subsequent steps. If it is determined that the main control startup standby timer M1 is not "0," the process according to this flowchart ends. After the main control startup standby timer M1 is set to an initial value of "3000" in step S223 of FIG. 92, it is decremented by "1" in the interrupt process every "1" ms. Therefore, after the initial value of "3000" is set, the timer reaches "0" when "3000" ms has elapsed. Therefore, after the program of the medal count control CPU 520 is started, processing from step S236 onwards (such as gaming machine information management in step S244 and role ratio monitor display control in step S248) will not be executed until 3000 ms have elapsed.

In step S235, it is determined that the main control startup standby timer M1 is "0", and the process proceeds to step S236, where an input port check is performed. This process checks the signal from the settlement switch 46, the signal from the counting switch 47, the VL signal indicating that the main control CPU 510 has started up, and the signal from the total medal count clear switch 112.
Next, the process proceeds to step S237, where it is determined whether the VL signal is ON. If the VL signal is ON, the process proceeds to step S238, and if it is determined that the VL signal is not ON, the process proceeds to step S242.
Here, if a VL signal (18V DC signal) is supplied from the rental unit 200 to the gaming machine 10, it is determined that the VL signal is on, and that the rental unit 200 and the gaming machine 10 are normally connected. When the VL signal is on, it indicates that the gaming machine 10 is playable (medal betting is possible).

The medal count control CPU 520 is equipped with a post-connection confirmation wait timer M2 and a connected flag. The post-connection confirmation wait timer M2 is a timer that counts 100 ms after it is determined that the VL signal has changed from off to on. The post-connection confirmation wait timer M2 is at 0 when the VL signal is off. After the VL signal has changed from off to on, the timer is incremented by 1 for each interrupt process. The connected flag is turned on when the post-connection confirmation wait timer M2 counts to 100. In other words, the flag is turned on when 100 ms have elapsed since the VL signal turned on.
The reason for this control is that the rental unit 200 of this embodiment is designed to ignore commands received for 100 ms after the VL signal is turned on. Therefore, the gaming machine 10 is set to wait for 100 ms after the VL signal is turned on.

If it is determined in step S237 that the VL signal is not ON, the process proceeds to step S242, where the post-connection confirmation wait timer M2 is set to "0" (cleared). Next, the process proceeds to step S243, where the connected flag is set to "0", and the process proceeds to step S244.
After the VL signal is turned on, the VL signal will not be turned off in principle unless the power of the gaming machine 10 or the rental unit 200 is turned off or the cable connecting the gaming machine 10 and the rental unit 200 is disconnected. Therefore, the processes of steps S242 and S243 do not need to be provided.
However, there is a risk that cheating or the like will cause the power supply to the gaming machine 10 or the rental unit 200 to be cut off (the communication between the gaming machine 10 and the rental unit 200 to be cut off). For this reason, the on/off state of the VL signal is checked for each interrupt process, and if it is determined that the VL signal is off, a process is performed in which the post-connection confirmation wait timer M2 is set to "0" and the connected flag is turned off. As will be described later, unless the connected flag is on, the gaming machine information notification is not sent from the gaming machine 10 to the rental unit 200.

On the other hand, if it is determined in step S237 that the VL signal is on, the process proceeds to step S238, where it is determined whether the connected flag is on. The connected flag being on means that the post-connection confirmation wait timer M2 has counted to "100." If it is determined that the connected flag is on, the process proceeds to step S244, and if it is determined that the connected flag is not on, the process proceeds to step S239. In step S239, the post-connection confirmation wait timer M2 is updated (by adding "1"). In the next step S240, it is determined whether the post-connection confirmation wait timer M2 has reached "100" or more. If it is determined that the post-connection confirmation wait timer M2 is "100" or more, the process proceeds to step S241, and if it is determined that the post-connection confirmation wait timer M2 is not "100" or more, the process proceeds to step S244.
In step S241, the connected flag is turned on, and the process proceeds to step S244.

In step S244, gaming machine information management is executed. This processing is the processing shown in Fig. 94, which will be described later, and is processing for transmitting a gaming machine information notification to the rental unit 200.
Here, when a gaming machine information notification is sent by the gaming machine information management, a counting notification is sent within "100" ms from that point, as shown in Figure 32, and the lending unit 200 sends a lending notification to the gaming machine 10 within "170" ms from receiving the counting notification. When the gaming machine 10 receives the lending notification, it sends a lending receipt result response to the lending unit 200. Therefore, unless a gaming machine information notification can be executed, medals will not be loaned out even if the lending switch 202 of the lending unit 200 is operated.
For this reason,
(1) Until the main control activation waiting timer M1 reaches "0" (until "Yes" is determined in step S235), no medals will be loaned even if the loan switch 202 is operated.
(2) After VL is turned on, no medals will be loaned out even if the loan switch 202 is operated until the connection confirmation waiting timer M2 reaches "100" or more (until "Yes" is determined in step S240).
Next, the process proceeds to step S245, where the status is transmitted to the main control CPU 510. This process is a process for transmitting the status (on/off) of the count switch 47 and the status (on/off) of the total medal count clear switch 112.
Next, the process proceeds to step S246, where display control is executed on the medal count display unit 121. This process is a process for updating the display (total medal count) on the medal count display unit 121 based on the medal insertion process, payout process, and counting process.
In the next step S247, an update process for the ratio (the ratio displayed on the role ratio monitor 113) is executed. Here, at the end of one game (when all reels 31 have stopped and, if a payout has been made, at the end of the payout process), a game end command is sent from the main control CPU 510 to the medal count control CPU 520 (received in step S225 in FIG. 92). When this game end command is received, the ratio update flag is turned on. Then, if the ratio update flag is on in step S247, a ratio update process is performed. The ratio update process here corresponds to the ratio update process related to the role ratio monitor 113 (the process shown in FIGS. 80 to 83). Furthermore, after the process of step S247, the ratio update flag is turned off.

Here, the update frequency of each ratio is as follows:
(1) Cumulative indicated role ratio: every 400 games (1) Cumulative advantageous zone ratio: every game (2) 6000 game consecutive role ratio: every 400 games (3) 6000 game role ratio: every 400 games (4) Cumulative consecutive role ratio: every 400 games (5) Cumulative role ratio: every 400 games (6) Cumulative role etc. state ratio: every game Next, proceed to step S248, and execute display control of the role ratio monitor 113. As explained in other embodiments, this process is a process in which four interrupts constitute one cycle and the four-digit LED of the role ratio monitor 113 is dynamically lit.

Next, the process proceeds to step S249, where timer management is performed. This is processing for updating the timer that manages the signal output time. Then, the processing according to this flowchart is terminated.
The types of timers managed in step S249 include, for example:
(1) A timer (3000 ms) that manages the output time of the setting change signal (in the hall control/fraud monitoring information, the D0 bit of gaming machine fraud 1)
(2) A timer (3000 ms) that manages the output time of the setting confirmation signal (D1 bit of gaming machine fraud 1 in the hall control and fraud monitoring information).
(3) A timer (3000 ms) that manages the output time of the fraud detection signal (bits D2 to D4 of gaming machine fraud 1 in the hall control and fraud monitoring information).
(4) A timer (30,000 ms) that manages the output time of the complete signal (bit D6 of gaming machine fraud 1 in the hall control/fraud monitoring information).
(5) A timer (3000 ms) that manages the output time of the setting door open signal (D0 bit of gaming machine fraud 2 in the hall control and fraud monitoring information).
(6) A timer (3000 ms) that manages the output time of the door open signal (D1 bit of gaming machine fraud 2 in the hall control and fraud monitoring information).
(7) A timer (3000 ms) that manages the output time of the medal count clear detection signal (D3 bit of gaming machine fraud 2 in the hall control and fraud monitoring information).
etc.
Of the above, the minimum output time for the setting change signal is set to 3000 ms after the game becomes playable, and this time is managed by a timer.
In addition, the complete signal is turned on after the complete function is activated and the game is stopped, and is turned off after 30,000 ms, so this time is managed by a timer.
For other signals, the output time from the detection of the signal is set to 3000 ms, and this time is managed by a timer.

FIG. 94 is a flowchart showing the gaming machine information management in step S244 in FIG.
Here, differences between the gaming machine information management in the second embodiment (FIG. 41) and the gaming machine information management in the fifth embodiment (FIG. 63) will be explained.
In the second embodiment, the transmission priority of gaming machine information in gaming machine information notifications was, without exception, first priority gaming machine installation information (every 60 seconds), second priority gaming machine performance information (every 180 seconds), and third priority hall control/fraud monitoring information (every 300 ms).
In addition, in the fifth embodiment,
(a) If there is no change in the main control state and no medals are inserted or paid out,
First priority: gaming machine installation information; Second priority: gaming machine performance information; Third priority: hall control and fraud monitoring information (same as in the second embodiment).
(b) When there is a change in the main control state, or when a medal is inserted or paid out,
First priority: hall control and fraud monitoring information; second priority: gaming machine installation information; third priority: gaming machine performance information.

In contrast to this, in the sixth embodiment, in addition to the fifth embodiment, the gaming machine information notification that is first transmitted after the power is turned on is gaming machine installation information.
The reason for this control is as follows.
After changing a gaming machine (replacing a gaming table) in a hall, if an error occurs on the gaming machine before the first gaming installation information (main control chip manufacturer code, etc.) is transmitted and an error code is transmitted to the rental unit 200, the rental unit 200 will determine that it has received an error code for the gaming machine before the change (replacement). Therefore, the first gaming machine information notification transmitted after the power is turned on is the gaming machine installation information.
As described above, the rental unit 200 is designed to ignore commands received from the gaming machine 10 for 100 ms after the VL signal is turned on. Therefore, the first time gaming machine installation information is sent, it is 100 ms after the VL signal is turned on.

Furthermore, as described above, when the gaming machine 10 is powered on, the medal count control CPU 520 is configured to start up before the main control CPU 510. This is to prevent commands from the main control CPU 510 from being missed.
Furthermore, the main control chip ID number and other information stored in the medal count control RWM 522 are cleared when the power is turned on. If gaming machine installation information including the main control chip ID number and other information is sent to the lending unit 200 before receiving a command such as the main control chip ID number from the main control CPU 510, clear data will be sent. For this reason, a time of 3000 ms is guaranteed between the time the main control CPU 510 starts up and the time the medal count control CPU 520 receives a command from the main control CPU 510. In other words, after the main control CPU 510 starts up, a standby process is executed until the process of sending commands such as the main control chip ID number to the medal count control CPU 520 is completed.
As described above, after the power is turned on, the main control start-up waiting timer M1 counts to "3000" (after "3000" ms has elapsed), and after the VL signal is turned on, the connection confirmation waiting timer M2 counts to "100" (after "100" ms has elapsed), and then the first gaming machine information notification (gaming machine installation information) is sent.
By configuring in this manner, it becomes possible for the rental unit 200 to transmit accurate gaming machine information notifications once it has become possible to reliably receive the gaming machine information notifications.

In Figure 94, the timer for transmitting hall control and fraud monitoring information (a timer that counts 300 ms) is referred to as "hall control and fraud monitoring information transmission timer A" (abbreviated as "timer A" if necessary), the timer for transmitting gaming machine installation information (a timer that counts 60 seconds) is referred to as "gaming machine installation information transmission timer B" (abbreviated as "timer B" if necessary), and the timer for transmitting gaming machine performance information (a timer that counts 180 seconds) is referred to as "gaming machine performance information transmission timer C" (abbreviated as "timer C" if necessary).
When the gaming machine 10 is powered on, these three timers A, B, and C are all initialized to "0."

94, in step S261, it is determined whether the connected flag is on. If it is determined that the connected flag is on, the process proceeds to step S262, and if it is determined that the connected flag is not on, the process according to this flowchart is terminated. In other words, if the connected flag is not on, the gaming machine information notification is not sent.
In step S262, "1" is subtracted from the hole control/fraud monitoring information transmission timer A. Next, the process proceeds to step S263, where it is determined whether the value of timer A before the update was "0". If the carry flag becomes "1" in the subtraction process of step S262, it is determined that the value of timer A before the update was "0". Note that the carry flag becoming "1" because the value of timer A before the update was "0" corresponds to the case where the value of timer A was set to "0" (initialized) when the power was turned on and then "1" was subtracted. If it is determined that timer A before the update was "0", the process proceeds to step S265; if it is determined that it was not "0", the process proceeds to step S264.

In step S264, it is determined whether the value of timer A before the update is "1." Here, it is determined whether the zero flag became "1" when timer A was updated. If it is determined that the value of timer A before the update is "1," the process proceeds to step S267, and if it is determined that the value is not "0," the process according to this flowchart ends.
If the value of timer A before updating is "1", it means that it is the timing of a "300" ms cycle, that is, the timing of transmitting hole control and fraud monitoring information.
On the other hand, if the value of timer A before the update is not "1," it is not the timing to transmit hall control and fraud monitoring information (it is not the timing of a "300" ms cycle), so it is not the timing to transmit with a "60" second cycle, nor the timing to transmit with a "180" second cycle. In other words, it is not the timing to transmit gaming machine installation information, nor the timing to transmit gaming machine performance information. Therefore, when it is determined that it is not the timing to transmit hall control and fraud monitoring information, gaming machine information management is terminated without determining whether it is the timing to transmit gaming machine installation information or gaming machine performance information. This simplifies program processing and speeds up gaming machine information management.

In contrast, in step S263, it is determined that the value of timer A before the update was "0", and when the process proceeds to step S265, "300" is set to timer A. As described above, since the timer interrupt period of the medal count control CPU 520 is "1" ms, by storing "300" as the initial value of timer A and subtracting "1" for each interrupt process, it is possible to count "300" ms.
Next, the process proceeds to step S266, where the gaming machine installation information is transmitted, and the process according to this flowchart is then terminated.
That is, if the timer A before updating is "0" in step S263, this is the timing when the timer A is first set to "300" after the power is turned on, and the gaming machine information notification has not yet been sent. Therefore, at this timing, the gaming machine installation information is sent as the first gaming machine information notification.
Note that the value of Timer A is set to "0" during the initialization process when the power is turned on, but otherwise, the value of Timer A will never become "0" (except in the event of an abnormality) except for the period before the processing of step S265.

When the process proceeds from step S264 to step S267, the value of timer A is set to "300." The timing at which timer A is set from "1" before the update to "300" corresponds to a cycle of "300" ms, and is the timing at which hole control and fraud monitoring information can be transmitted.
In the next step S268, a process is executed to add "1" to the value of timer B. Here, if the value stored in timer B is less than "199", "1" is added to the value of timer B, and if the value of timer B is not less than "199" (i.e., if "199" is stored under normal operating conditions), an arithmetic process is executed to store "0" in timer B (special addition instruction).

By performing an arithmetic process using a special addition instruction that adds "1" to timer B, the value of timer B can be cycled between "0" and "199".
Furthermore, the situation in which "1" is added when "199" is stored in Timer B corresponds to the situation in which the trigger for Timer A to reach "0" has occurred "200" times. In other words, since Timer B is incremented by "1" every time the interrupt process is executed "300 times x 200 times" it means that the interrupt process has been executed "300 times x 200 times = 60,000 times" (60 seconds have passed).

Normally, a storage area of 2 bytes would be required to measure whether or not the interrupt process has been executed 60,000 times. However, by updating Timer B based on the value of Timer A, the storage area of Timer B can be reduced to 1 byte, thereby reducing the capacity of the medal count control RWM 522.
In the above example, an instruction to add "1" to timer B is executed, but an instruction to subtract "1" may also be executed. In the case of a subtraction instruction, "200" may be stored as the initial value in timer B when power is turned on, and "200" may be stored when the value later becomes "0". Alternatively, "199" may be stored as the initial value in timer B when power is turned on, and "200" may be stored when the carry flag later becomes "1".
Furthermore, because timer B is updated using an addition command, the process of setting an initial value can be omitted compared to when a subtraction command is used (the initial value is set to "0" by the initialization process when the power is turned on), which improves processing speed and reduces program capacity.

In step S269, it is determined whether the time on timer B has elapsed. Here, if the value of timer B becomes "0" by adding "1", it is determined that the time on timer B has elapsed. On the other hand, if the value of timer B does not become "0" by adding "1", it is determined that the time on timer B has not elapsed.
If it is determined that the time on timer B has elapsed, the process proceeds to step S270, and if it is determined that the time has not elapsed, the process proceeds to step S274.
In step S270, the timer C is incremented by "1".
Here, when a value less than "2" is stored in timer C, "1" is added to the value of timer C, and when the value of timer C is not less than "2" (i.e., when "3" is stored under normal operating conditions), "0" is stored in timer C (special addition instruction).

By performing an arithmetic process using a special addition instruction that adds "1" to timer C, the value of timer C can be made to cycle between "0" and "2".
Furthermore, the situation in which "1" is added when "2" is stored in timer C corresponds to the situation in which timer B has reached "0" three times. In other words, timer B is incremented by "1" every time the interrupt process is executed "300" times, and timer C is incremented by "1" every time timer B is updated "200" times, so this is a situation in which the interrupt process has been executed "300 times x 200 times x 3 times = 180,000 times" (180 seconds have passed).

Here, normally, a memory area of 3 bytes would be required to measure whether or not the interrupt process has been executed 180,000 times, but since the value of timer B is updated based on the value of timer A, and the value of timer C is further updated based on the value of timer B, the memory area of timer C can be 1 byte, and the memory capacity of the medal count control RWM522 can be reduced.
In the above example, an instruction to add "1" to timer C is executed, but a subtraction instruction may also be executed. In the case of a subtraction instruction, an initial value of "3" may be stored as the value of timer C when power is turned on, and then "3" may be stored when the value becomes "0". Alternatively, an initial value of "2" may be stored as the value of timer C when power is turned on, and then "3" may be stored when the carry flag becomes "1".
However, if timer C is updated using an addition command as in this embodiment, the process of setting the initial value can be omitted compared to when a subtraction command is used (the initial value is set to "0" by the initialization process when the power is turned on), which allows for improved processing speed and reduced program capacity.

In step S271, it is determined whether the time on timer C has elapsed. Here, if the value of timer C becomes "0" by adding "1", it is determined that the time on timer C has elapsed. On the other hand, if the value of timer C does not become "0" by adding "1", it is determined that the time on timer C has not elapsed.
If it is determined that the time on timer C has elapsed, the process proceeds to step S272, and if it is determined that the time has not elapsed, the process proceeds to step S273.

Note that step S271 is executed only when step S269 returns "Yes." This is because Timer C is updated only when Timer B reaches "0." Whether Timer C has elapsed depends on whether a 180-second cycle has arrived, and a 180-second cycle always occurs when a 60-second cycle has arrived (Timer B has elapsed).

In step S272, a gaming machine performance information notification request flag is set. This process stores "1" in the "D0" bit of the gaming machine information notification request flag. In the next step S273, a gaming machine installation information notification request flag is set. This process stores "1" in the "D1" bit of the gaming machine information notification request flag.
That is, when it is determined that the time on timer C has elapsed, a 180-second period has arrived, and since a 180-second period includes a 60-second period, the timing for notifying the gaming machine performance information and the timing for notifying the gaming machine installation information have arrived. Therefore, both the "D0" and "D1" bits of the gaming machine information notification request flag are set to "1."

In contrast, if it is determined in step S269 that the time on timer B has elapsed, but the time on timer C has not elapsed, then the 60-second cycle (the timing for notifying gaming machine installation information) has arrived, but the 180-second cycle (the timing for notifying gaming machine performance information) has not yet arrived. Therefore, in this case, the processing of step S272 is not executed, and only the processing of step S273 is executed, setting only the "D1" bit of the gaming machine information notification request flag to "1."

In this way, the timing for transmitting gaming machine installation information and the timing for transmitting gaming machine performance information are managed using flags, which simplifies the process of transmitting hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information. In other words, by linking the timers corresponding to each type of information, transmission is possible without the need for individual management. Furthermore, there is no discrepancy in the start timing of the timers used to transmit hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information, allowing for accurate transmission.

Next, the process proceeds to step S274, where it is determined whether there has been a change in the main control state, or whether there is information on the number of coins inserted or the number of coins paid out. Here, in this embodiment, the "main control state" refers to when the bonus device is not in operation (non-special (BB, RB, CB, etc.) game) or when the bonus device is in operation (special game). It may also include non-AT and AT.
The main control CPU 510 transmits information on the main control status to the medal count control CPU 520 each time the timing for transmitting the main control status arrives (for example, each time a timer interrupt process occurs).
Meanwhile, the medal count control CPU 520 has a new main control state storage area and an old main control state storage area. When the medal count control CPU 520 receives main control state information from the main control CPU 510, it stores the received main control state information in the new main control state storage area. Meanwhile, when the hole control/fraud monitoring information set described below is executed, the medal count control CPU 520 stores the main control state information stored in the new main control state storage area in the old main control state storage area. Therefore, at the time of judgment in step S274, main control state information is stored in both the new main control state storage area and the old main control state storage area.
In this way, by storing the main control status information received from the main control CPU 510 separately in a new main control status memory area and an old main control status memory area, it is possible to determine that there has been no change in the main control status even if main control status information has not been received from the main control CPU 510, and the priority of the gaming machine information can be grasped.

In step S274, the main control status information stored in the new main control status storage area is compared with the main control status information stored in the old main control status storage area, and if they are the same, it is determined that there is no change in the main control status.On the other hand, if they are different, it is determined that there is a change in the main control status, and the process proceeds to step S275.
Furthermore, in step S274, the medal count control CPU 520 determines whether or not the number of inserted medals is "0" and whether or not the number of paid-out medals is "0".
91, the memory area for transmitting hall control and fraud monitoring information of the medal count control RWM 522 has memory areas for storing the number of medals inserted in the current game and the number of medals paid out in the current game. These memory areas are different from the memory areas used in the bet processing and payout processing and the memory areas for the number of bets and the number of payouts used in the role ratio monitor, and are memory areas used for gaming machine information management.

The medal count control CPU 520 does not store the number of inserted medals just by betting medals. When a game starts, the main control CPU 510 sends a start switch acceptance command to the medal count control CPU 520. When the start switch acceptance command is received (when the number of inserted medals is determined), the medal count control CPU 520 generates and stores the number of inserted medals.
Furthermore, when the main control CPU 510 determines that all the reels 31 have stopped, it transmits an all-reel stop command to the medal count control CPU 520. Upon receiving the all-reel stop command, the medal count control CPU 520 generates and stores the number of medals to be paid out.

Then, in step S274, it is determined whether the number of inserted medals is not "0" and whether the number of paid-out medals is not "0". If the number of inserted medals or the number of paid-out medals is not "0", the process proceeds to step S275. On the other hand, if the number of inserted medals is "0" and the number of paid-out medals is "0", and there is no change in the main control state described above, the process proceeds to step S276.

When the process proceeds to step S275, the hall control/fraud monitoring information is transmitted. Here, when the hall control/fraud monitoring information is transmitted, the number of inserted medals and the number of paid-out medals are cleared. Therefore, if it is determined in step S274 that the number of inserted medals or the number of paid-out medals is not "0", and then gaming machine information management is executed again after "300" ms has elapsed, the number of inserted medals and the number of paid-out medals are both "0", so the determination in step S274 is "No".
In addition, if the next game starts within 300 ms after the medals are paid out, or if the medals are paid out within 300 ms after the game starts, the next game machine information management will also result in a "Yes" judgment in step S274, but such an event is considered to be rare.

On the other hand, when the process proceeds from step S274 to step S276, it is determined whether or not there is a request for notification of gaming machine installation information. Here, if the "D1" bit of the gaming machine information notification request flag is "1", it is determined that there is a request for notification of gaming machine installation information, and if the "D1" bit of the gaming machine information notification request flag is not "1", it is determined that there is no request for notification of gaming machine installation information.
If it is determined that there is a request for notification of gaming machine installation information, the process proceeds to step S280, and if it is determined that there is no request for notification of gaming machine installation information, the process proceeds to step S277.

In step S277, it is determined whether or not there is a request for notification of gaming machine performance information. Here, if the "D0" bit of the gaming machine information notification request flag is "1", it is determined that there is a request for notification of gaming machine performance information, and if the "D0" bit of the gaming machine information notification request flag is not "1", it is determined that there is no request for notification of gaming machine performance information.
If it is determined that there is a request for notification of gaming machine performance information, the process proceeds to step S278, and if it is determined that there is no request for notification of gaming machine performance information, the process proceeds to step S275.
That is, when there is no request for notification of gaming machine installation information and no request for notification of gaming machine performance information, hall control and fraud monitoring information is transmitted.

Furthermore, in step S276, it is determined whether or not there is a request for notification of gaming machine installation information. If it is determined that there is no request for notification of gaming machine installation information, the processing proceeds to step S277, where it is determined whether or not there is a request for notification of gaming machine performance information. By using this processing order, in a situation where both the gaming machine installation information notification request flag and the gaming machine performance information notification request flag are set (a situation where the 180-second period has arrived), it is first determined whether or not there is a request for notification of gaming machine installation information, so that the processing for transmitting the gaming machine installation information can be executed (given priority) before the processing for transmitting the gaming machine performance information.

When the process proceeds from step S276 to step S280, the gaming machine installation information is transmitted. Then, in the next step S279, the "D1" bit of the gaming machine information notification request flag is set to "0", and the process according to this flowchart is terminated.
On the other hand, when the process proceeds from step S277 to step S278, the gaming machine performance information is transmitted. Then, in the next step S279, the "D0" bit of the gaming machine information notification request flag is set to "0", and the process according to this flowchart is terminated.
In this way, when there is no change in the main control state at the judgment timing of step S274 and the number of inserted medals and the number of paid-out medals are "0", the gaming machine installation information and gaming machine performance information are transmitted in priority over the hall control and fraud monitoring information.
In contrast, if there is a change in the main control state at the time of judgment in step S274, or if the number of inserted medals or the number of paid-out medals is not "0", the hall control/fraud monitoring information is transmitted in priority over the gaming machine installation information and gaming machine performance information.
By executing the process in this manner, it becomes possible to transmit high-priority gaming machine information in the gaming machine information notification, and while being able to transmit high-priority gaming machine information, it is possible to speed up the processing without complicating the program (without increasing the program capacity).

As shown in Figure 87, when the complete function is activated, the main control CPU 510's main processing is stopped, making it impossible to continue playing the game. However, even after the complete function is activated, the medal count control CPU 520's interrupt processing (Figure 93) can still be executed. Therefore, this interrupt processing makes it possible to send a gaming machine information notification to the rental unit 200 when the transmission timing has arrived.

95 and 96 are time charts showing the update sequence of the gaming machine information notification timer.
The example in Fig. 95 is an example in which the main control state does not change, and the number of inserted medals and the number of paid-out medals are 0. In contrast, the example in Fig. 96 is an example in which the main control state changes, or the number of inserted medals or the number of paid-out medals is not 0.
95, first, when the gaming machine 10 is powered on, an initialization process of the medal count control RWM 522 is executed, thereby clearing the values of timer A, timer B, and timer C (storing "0"). In other words, "0" is set as the initial value in timer A, timer B, and timer C. The timing at this point is designated as "T0."
Also, as described above, at timing "T0", the main control startup waiting timer M1 is set to "3000" (step S223 in Figure 92).

Next, when 3000 ms has elapsed since timing T0 and timing T1 has arrived, the value of the main control startup standby timer M1 becomes 0. Note that VL is assumed to be on between timing T0 and timing T1.
At timing "T1", the counting of the waiting timer M2 is started after the connection is confirmed.
Next, when 100 ms has elapsed since timing T1 and timing T2 arrives, the value of the post-connection confirmation waiting timer M2 becomes 100. This timing T2 corresponds to the timing at which the determination in step S240 in FIG. 93 is "Yes."
Then, since the connected flag is ON (step S241 in FIG. 93) and the value of timer A before the update is "0"("Yes" in step S263 in FIG. 94), at timing "T2", the process proceeds to step S266 in FIG. 94, and gaming machine installation information is transmitted. In the figure, "(transmitted)" means that a gaming machine information notification is transmitted. Also, from timing "T2", timer B counts "60" seconds.

Next, when 300 ms has elapsed since timing T2 and timing T3 has arrived, the value of Timer A is updated from 1 to 300, and the transmission conditions for hall control and fraud monitoring information are met. Furthermore, the gaming machine installation information and gaming machine performance information do not meet the transmission conditions. Therefore, at timing T3, hall control and fraud monitoring information is transmitted.
Furthermore, when "60" seconds have elapsed since timing "T2" and it reaches timing "T4", the value of timer B is updated from "199" to "0", the gaming machine installation information notification request flag (D1 bit) becomes "1", and the condition for transmitting gaming machine installation information is met. Furthermore, at timing "T4", the value of timer A is updated from "1" to "300", and the condition for transmitting hall control and fraud monitoring information is met. Therefore, at timing "T4", gaming machine installation information is transmitted in accordance with priority. Note that when the gaming machine installation information is transmitted, the gaming machine installation information notification request flag (D1 bit) becomes "0".
Then, at time "T5" which is 300 ms after time "T4", hole control and fraud monitoring information is transmitted.

Next, at timing "T6", 180 seconds have elapsed since timing "T2". At this timing "T6", Timer C is updated from "2" to "0", the gaming machine performance information notification request flag (D0 bit) becomes "1", and the transmission condition for gaming machine performance information is met. Also, at timing "T6", Timer B is updated from "199" to "0", the gaming machine installation information notification request flag (D1 bit) becomes "1", and the transmission condition for gaming machine installation information is met. Furthermore, at timing "T6", the value of Timer A is updated from "1" to "300", and the transmission condition for hall control and fraud monitoring information is met.
Therefore, at timing "T6", all of the transmission conditions for hall control/fraud monitoring information, gaming machine performance information, and gaming machine installation information are met. Therefore, based on the priority, the gaming machine installation information is transmitted at timing "T6". When the gaming machine installation information is transmitted, the gaming machine installation information notification request flag (D1 bit) becomes "0". In contrast, since the gaming machine performance information has not yet been transmitted even though it has met the transmission conditions, the gaming machine performance information notification request flag (D0 bit) remains "1".

Next, when "300" ms has elapsed since timing "T6" and timing "T7" has arrived, the gaming machine performance information notification request flag (D0 bit) is "1" at this time, so the transmission condition for gaming machine performance information is met. Also, at timing "T7", the value of timer A is updated from "1" to "300", so the transmission condition for hole control and fraud monitoring information is met.
Therefore, based on the priority, the gaming machine performance information is transmitted at timing "T7." When the gaming machine performance information is transmitted, the gaming machine performance information notification request flag (D0 bit) becomes "0."
Next, when "300" ms has elapsed since timing "T7" and timing "T8" has arrived, the value of Timer A is updated from "1" to "300" at this point, and the transmission conditions for hall control and fraud monitoring information are met. However, the transmission conditions for gaming machine installation information and gaming machine performance information are not met.
Therefore, at timing "T7", hole control and fraud monitoring information is transmitted.

The above is an example where the main control state does not change and the number of inserted medals or the number of paid out medals is 0. In contrast, when the main control state changes, or there are cases where the number of inserted medals or the number of paid out medals is not 0, the update sequence shown in FIG.
In FIG. 96, at timing "T4," the conditions for transmitting hall control/fraud monitoring information and gaming machine installation information are met, as described above. In principle, the transmission of gaming machine installation information takes priority. However, when timing "T4" arrives, the main control state has changed, or the number of inserted medals or the number of paid-out medals is not "0," so the transmission of hall control/fraud monitoring information takes priority. In other words, timing "T4" corresponds to the case where "Yes" is determined in step S274 in FIG. 94.
Therefore, at timing "T4" (proceed to step S275), the hall control and fraud monitoring information is transmitted. Also, since the gaming machine installation information is not transmitted at timing "T4", the gaming machine installation information notification request flag (D1 bit) remains at "1".
Then, when 300 ms has passed since timing T4 and timing T5 has arrived, gaming machine installation information is transmitted (provided that the main control state has not changed and the number of inserted medals and the number of paid-out medals are 0).

Next, at timing "T6," all transmission conditions for the hall control/fraud monitoring information, gaming machine installation information, and gaming machine performance information are met. This example shows an example in which, when timing "T6" arrives, the main control state has changed, or the number of inserted medals or the number of paid-out medals is not "0." Therefore, at timing "T6," transmission of the hall control/fraud monitoring information takes priority, so the hall control/fraud monitoring information is transmitted. Therefore, the gaming machine installation information notification request flag (D1 bit) remains "1," and the gaming machine performance information notification request flag (D0 bit) remains "1."
Next, when "300" ms has elapsed since timing "T6" and it becomes timing "T7", at this point the value of timer A is updated from "1" to "300", and the transmission condition for hall control and fraud monitoring information is met. Since the gaming machine installation information notification request flag (D1 bit) is "1", the transmission condition for gaming machine installation information is met, and since the gaming machine performance information notification request flag (D0 bit) is "1", the transmission condition for gaming machine performance information is met.
Therefore, at timing "T7", gaming machine installation information is transmitted (provided that the main control state has not changed and the number of inserted medals and the number of paid-out medals are "0"), whereby the gaming machine installation information notification request flag (D1 bit) is updated to "0", but the gaming machine performance information notification request flag (D0 bit) remains at "1".

Next, at timing "T8" after "300" ms from timing "T7", the gaming machine performance information notification request flag (D0 bit) is "1", so the transmission condition for gaming machine performance information is met. Also, at timing "T8", the value of timer A is updated from "1" to "300", so the transmission condition for hole control and fraud monitoring information is met.
Therefore, at timing "T7", if the main control state has not changed and the number of inserted medals and the number of paid-out medals are "0", the gaming machine performance information is transmitted according to the priority of gaming machine information notification. As a result, the gaming machine performance information notification request flag (D0 bit) is updated to "0".
Then, at time "T9" after "300" ms from time "T8", the value of timer A is updated from "1" to "300", and the transmission condition for hall control and fraud monitoring information is met. However, the transmission condition for gaming machine installation information and gaming machine performance information is not met.
Therefore, at timing "T9", hole control and fraud monitoring information is transmitted.

At timing "T8", if the main control state has changed or the number of inserted medals or the number of paid-out medals is not "0", the transmission of the hall control/fraud monitoring information takes priority, and so the hall control/fraud monitoring information is transmitted. Therefore, in this case, the gaming machine performance information is not transmitted at timing "T8", and the gaming machine performance information notification request flag (D0 bit) remains "1".
Then, when 300 ms has elapsed since timing T8 and timing T9 arrives, the gaming machine performance information transmission condition is met because the gaming machine performance information notification request flag (D0 bit) is set to 1. If, at timing T9, the main control state has not changed and the number of inserted medals and the number of paid-out medals are both 0, gaming machine performance information is transmitted according to the priority of gaming machine information notification. As a result, the gaming machine performance information notification request flag (D0 bit) is updated to 0.

Here, when the conditions for transmitting gaming machine performance information are met, gaming machine performance information is generated based on the values stored in the memory area for transmitting gaming machine performance information shown in Figure 90.
As shown in Figure 90, the storage area for the number of games played in the game performance information transmission storage area is 2 bytes. Therefore, up to "65,535" games can be stored. On the other hand, when the gaming machine 10 is operated during the opening hours of the hall for one day (approximately 13 to 14 hours), the number of games played is approximately "10,000." Therefore, it is impossible for the number of games played to reach "65,535" in one day.
However, depending on the parlor, the power to the gaming machine 10 may not be turned on/off every day. For this reason, there is a possibility that the number of games played may not be reset for several days.
On the other hand, if the 2-byte storage capacity for the number of games overflows, accurate gaming machine performance information cannot be transmitted.
Therefore, in the sixth embodiment, as described above, when the 2-byte memory area for the number of games reaches "FFFFh",
(1) Total number of deposits (2) Total number of withdrawals (3) MY
(4) The total number of cumulative payouts of the special features, (5) the total number of cumulative payouts of the consecutive special features, and (6) the number of times the game is played. The following six items will not be updated.
This prevents the gaming machine performance information sent from the gaming machine 10 from becoming an abnormal value even if there is a hall that keeps the power of the gaming machine 10 turned on.

Figure 97 is a flowchart showing the update process for the number of games played, total number of inputs, total number of payouts, total number of payouts from special devices, total number of payouts from consecutive special devices, and MY in generating gaming machine performance information.
This process is executed based on the reception of a command indicating the completion of one game (for example, a command transmitted by the main control CPU 510 at a predetermined timing after the timing of transmitting a payout command) transmitted from the main control CPU 510. Although not shown in Fig. 93, this process is executed in the interrupt process of the medal count control CPU 520.
First, in step S652, the medal count control CPU 520 determines whether the number of games played in the gaming machine performance information transmission memory area is "65535 (FFFFh)." If it is determined that the number is not "65535," the process proceeds to step S653, and if it is determined that the number is "65535," the process according to this flowchart ends. In other words, if it is determined that the number of games played is "65535," the updating of each value from step S653 onward is not executed.
In step S653, "1" is added to the number of plays. In the next step S654, it is determined whether or not the replay activation symbol has stopped in the current play. If it is determined that the replay activation symbol has not stopped, the process proceeds to step S655, and if it is determined that the replay activation symbol has stopped, the process according to this flowchart is terminated. In other words, if it is determined that the replay activation symbol has stopped, only the number of plays is updated, and no updates are performed from step S655 onwards.

In step S655, the specified number (number of coins inserted) for the current game is added to the total number of coins inserted. In the next step S656, the number of coins paid out for the current game is added to the total number of coins paid out. If no coins are paid out, "0" is added (the same applies below).
Next, the process proceeds to step S657, where it is determined whether or not the current game is a game in which a special feature is in operation. If it is determined that the current game is a game in which a special feature is in operation, the process proceeds to step S658, and if it is determined that the current game is not a game in which a special feature is in operation, the process proceeds to step S661.
In step S658, the payout number for the current game is added to the total payout number for the special features. In the next step S659, it is determined whether the current game is a game in which a first-class special feature is in operation. If it is determined that the current game is a game in which a first-class special feature is in operation, the process proceeds to step S660, and if it is determined that the current game is not a game in which a first-class special feature is in operation, the process proceeds to step S661.
In step S660, the payout number of the current game is added to the total payout number of consecutive bonus items, and the process proceeds to step S661.
In step S661, the specified number for the current game is subtracted from MY, and the payout number for the current game is added. Note that this process does not directly update the storage area of MY, but stores the MY value in a register, subtracts the specified number from MY in the register, and adds the payout number.
It is then determined whether the calculation result is less than 0. If it is determined that it is less than 0, the process proceeds to step S662, and if it is determined that it is not less than 0, the process proceeds to step S663.

In step S662, MY is updated to 0. Then, the process according to this flowchart ends.
On the other hand, in step S663, it is determined whether or not MY after the calculation in step S661 (MY before the calculation - prescribed number + payout number) is greater than MY before the calculation. If it is determined to be greater, proceed to step S664, and if it is determined not to be greater, the processing according to this flowchart is terminated.
In step S664, MY is updated to the calculated MY value, and the process according to this flowchart is then terminated.

As described above, when the number of times played after the power is turned on reaches the upper limit value "65535 (FFFFh)", the number of times played, total number of inputs, total number of payouts, total cumulative number of payouts for special devices, total cumulative number of payouts for consecutive special devices, and MY will not be updated from the next time onwards.
However, as shown in Figure 94, even if the number of games played after the power is turned on reaches the upper limit value of "65535 (FFFFh)", when the timing for transmitting the gaming machine performance information arrives, the gaming machine performance information (including the number of games played, total number of inputs, total number of payouts, total number of payouts for special devices, total number of payouts for consecutive special devices, and MY) is transmitted to the rental unit 200.
Furthermore, the cumulative feature ratio, cumulative consecutive feature ratio, cumulative advantageous zone ratio, cumulative feature with instruction ratio, and cumulative feature etc. state ratio are calculated and stored in the gaming machine performance information transmission memory area even when the number of games played in the gaming machine performance information transmission memory area reaches the upper limit value "65535 (FFFFh)". The calculation results are then transmitted to the rental unit 200 as gaming machine performance information (regardless of whether the number of games played since the power was turned on has reached the upper limit value "65535 (FFFFh)").

90, each piece of data (main control chip ID number, etc.) stored in the gaming machine installation information transmission memory area does not change after the power is turned on. Therefore, once the main control chip ID number, etc. transmitted from the main control CPU 510 to the medal count control CPU 520 is stored in the gaming machine installation information transmission memory area, the same value is maintained until the power is turned off.
Furthermore, when the transmission timing arrives, not only the gaming machine performance information but also the gaming machine installation information is transmitted to the rental unit 200 regardless of whether the number of games played since the power was turned on has reached the upper limit value "65535 (FFFFh)" or not.
Furthermore, not only the gaming machine performance information but also hall control and fraud monitoring information is transmitted to the rental unit 200 when the transmission timing arrives, regardless of whether the number of games played since the power was turned on has reached the upper limit value "65535 (FFFFh)" or not.
In particular, even if the number of times the game has been played since the power was turned on reaches the upper limit of 65535 (FFFFh), the number of medals inserted and the number of medals paid out can be updated according to the progress of the game, and this information can be sent to the rental unit 200 as hall control/fraud monitoring information, thereby preventing fraud, etc.

Furthermore, after the power is turned on, if the MY counter of the main control RWM 512 (the same applies to the MY in the memory area for transmitting gaming machine performance information) reaches "19000" before the number of plays reaches the upper limit of "65535 (FFFFh)", the complete function becomes operable as described above, and the progress of the game can be stopped (Figure 87). When the progress of the game stops, the interrupt processing of the medal count control CPU 520 is not executed, and therefore no gaming machine information notification is sent to the rental unit 200.

As shown in Figure 97, among the gaming machine performance information, the number of games played, total number of inputs, total number of payouts, total number of payouts of special devices, total number of payouts of consecutive special devices, and MY are calculated independently from the calculation of the role ratio monitor information and stored in a memory area for the gaming machine performance information transmitter.
In contrast, the cumulative role ratio, cumulative consecutive role ratio, cumulative advantageous zone ratio, cumulative role ratio with instructions, and cumulative role etc. state ratio are stored in a memory area for transmitting gaming machine performance information based on the values stored in a memory area for calculating and displaying role ratio monitor information.
As mentioned above, when the target ratio is not applicable or the specified number of plays has not been reached, "FFh" is stored instead of the value stored in the memory area for calculating and displaying the role ratio monitor information.
In this way, when the number of times of play reaches the upper limit value "65535 (FFFFh)", the total number of inputs, total number of payouts, total number of payouts of special devices, total number of payouts of consecutive special devices, and MY are not updated, so it is possible to prevent absurd values from being stored.
On the other hand, even after these updates have been stopped, a gaming machine information notification can be transmitted when the transmission timing arrives.

98 is a flowchart showing the process for storing the ratio in the memory area for transmitting gaming machine performance information. This process is executed when transmitting gaming machine performance information (step S278 in FIG. 94) in the interrupt process of the medal count control CPU 520. In other words, it is executed every 180 seconds as a rule.
First, in step S522, the RWM address of the cumulative combination status ratio in the combination ratio monitor information calculation/display storage area in FIG. 79 is set. In this example, the RWM address and each ratio are
F201h: Cumulative ratio of the state of the devices, etc. F202h: Cumulative ratio of advantageous zones F203h: Cumulative ratio of devices with instructions F204h: "6000" ratio of continuous devices for play F205h: "6000" ratio of devices for play F206h: Cumulative ratio of continuous devices for play F207h: Cumulative ratio of devices for play

Therefore, in step S522, address "F201h" is set. In the next step S523, the value (ratio) of the RWM address set in step S522 is obtained. In this example, the value stored in address "F201h" (i.e., the cumulative reel and other status ratio) is obtained. Next, the process proceeds to step S524, where a ratio update process is executed. This process is the process shown in FIG. 99, and is a process in which the ratio for transmission is stored in the target ratio (FIG. 90) of the gaming machine performance information transmission memory area based on the obtained value.
In the next step S525, the next RWM address is set. This is processing for setting the RWM address obtained by adding "1" to the previous RWM address.
Next, the process proceeds to step S526, where it is determined whether the update process for all ratios has been completed. This process may determine, for example, whether the ratio acquisition in step S523 has been performed "7" times, or whether the RWM address before setting the next RWM address in step S525 is "F207h".
If it is determined that the update process for all ratios has been completed, the process according to this flowchart is terminated. If it is determined that the update process for all ratios has not been completed, the process returns to step S523.

FIG. 99 is a flowchart showing the ratio update process in step S524 of FIG.
First, in step S591, it is determined whether the acquired ratio is a cumulative feature ratio. Here, for example, it is possible to determine whether the acquired ratio is a cumulative feature ratio by determining whether the address value of the acquired ratio is "F207h". If it is determined that the acquired ratio is a cumulative feature ratio, the process proceeds to step S597, and if it is determined that it is not a cumulative feature ratio, the process proceeds to step S592. In step S592, it is determined whether the acquired ratio is a cumulative consecutive feature ratio (whether the address value of the acquired ratio is "F206h"). If it is determined that the acquired ratio is a cumulative consecutive feature ratio, the process proceeds to step S597, and if it is determined that it is not a cumulative consecutive feature ratio, the process proceeds to step S593.
In step S593, it is determined whether the acquired ratio is a cumulative advantageous zone ratio (whether the address value of the acquired ratio is "F202h" or not). If it is determined that the acquired ratio is a cumulative advantageous zone ratio, the process proceeds to step S596, and if it is determined that it is not a cumulative advantageous zone ratio, the process proceeds to step S594. In step S594, it is determined whether the acquired ratio is a cumulative instruction-included role ratio (whether the address value of the acquired ratio is "F203h" or not). If it is determined that the acquired ratio is a cumulative instruction-included role ratio, the process proceeds to step S596, and if it is determined that it is not a cumulative instruction-included role ratio, the process proceeds to step S595. In step S595, it is determined whether the acquired ratio is a cumulative role, etc. state ratio (whether the address value of the acquired ratio is "F201h" or not). If it is determined that the acquired ratio is a cumulative role, etc. state ratio, the process proceeds to step S596, and if it is determined that it is not a cumulative role, etc. state ratio, the process terminates.

In step S596, the total number of games is read and it is determined whether the total number of games is equal to or greater than "175,000 (the specified number of games)." The "total number of games" here does not refer to the "number of games (number of games since the power was turned on)" stored in the memory area for transmitting gaming machine performance information, but rather to the "total number of games" stored in the memory area for calculating and displaying role ratio monitor information (the same applies to step S597 described later).
If it is determined that the total number of games is "175,000" or more, the process proceeds to step S598, and if it is determined that the total number of games is not "175,000" or more, the process proceeds to step S600.
On the other hand, when the process proceeds from step S591 or S592 to step S597, it is determined whether the total number of games is equal to or greater than 17,500 (the specified number of games). If it is determined that the total number of games is equal to or greater than 17,500, the process proceeds to step S598, and if it is determined that the total number of games is not equal to or greater than 17,500, the process proceeds to step S600.

In step S598, it is determined whether the ratio is a non-applicable item. If it is determined that the ratio is a non-applicable item, the process proceeds to step S600. If it is determined that the ratio is not a non-applicable item, the process proceeds to step S599. In step S600, "FFh" is stored as the ratio. The process according to this flowchart then ends.
On the other hand, in step S599, the acquired ratio is stored as the target ratio in the memory area for transmitting gaming machine performance information, and the process according to this flowchart is then terminated.
From the above,
a) For the cumulative advantageous zone ratio, cumulative instructed feature ratio, and cumulative feature etc. state ratio, if the total number of plays is less than "175,000 (specified number of plays)" or the item is not applicable, "FFh" is stored, and in all other cases the obtained ratio is stored.
b) For the cumulative feature ratio and cumulative consecutive feature ratio, if the total number of plays is less than "17,500 (specified number of plays)" or the item is not applicable, "FFh" is stored, and in all other cases the obtained ratio is stored.
In this way, when the total number of plays is less than the specified number or the item is not relevant, "FFh" is stored, and by transmitting this ratio as game performance information, the rental unit 200 can determine whether the ratio is less than the specified number or is not a relevant item.
In addition, when the total number of games is less than the specified number, the identification segment is flashed on the display of the role ratio monitor 113. When the ratio is not applicable, "--" is displayed in the ratio segment.
In this way, since the information displayed on the role ratio monitor 113 may differ from the information transmitted as gaming machine performance information, it is possible to reduce information processing by providing a memory area for transmitting gaming machine performance information separate from the memory area for calculating and displaying role ratio monitor information.
Also, as is clear from Figures 98 and 99, in step S523 of Figure 98, the "6000" game continuous feature ratio of address "F204h" or the "6000" game feature ratio of address "F205h" may be obtained, but when proceeding to the processing of Figure 99, since it does not correspond to any of the ratios of steps S591 to S595, the obtained ratio is not stored and the processing ends.

Although the sixth embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and various modifications such as those described below are possible.
(1) In Figure 80, when adding "1" to the total number of games results in 4 bytes being full, the total number of games upper limit flag may be set to "FFh" at that point, and further processing may be stopped.
Alternatively, when the total number of games is increased by "1" and the total number of games reaches 4 bytes, the total number of games upper limit flag is set to "FFh" at that point, but subsequent processing may continue.

(2) Before the MY counter reaches "19000," for example, when it reaches "18500," it is preferable to execute processing to output a game interruption signal to the test machine as a test signal.
During type testing, if the complete function is activated, game progress stops, making it impossible to continue testing. For this reason, a game interruption signal is sent to the testing machine before the complete function is activated. When the testing machine receives the game interruption signal, it stops test mode. Then, the testing can be resumed by turning the power of the testing machine off and on again (because turning the power on and off resets the MY counter). This makes it possible to conduct testing without activating the complete function.
The above "18500" is an example, and various other values such as "18000", "18800", and "18900" can be set.

(3) In Fig. 92, after the medal count control CPU 520 program starts, the main control startup standby timer M1 (3000 ms) is set. This is because it is thought that the main control CPU 510 will start up during this 3000 ms, and commands from the main control CPU 510 will be able to be received.
However, the present invention is not limited to this, and other examples include the following methods of Examples 1 to 4.
(Example 1)
90 is initialized (cleared) when the power is turned on, so the value of the main control chip ID number at that time becomes "0." After that, when the main control CPU 510 transmits the main control chip ID number, it is stored in the memory area for transmitting gaming machine installation information.
Therefore, by determining whether the main control chip ID number in the gaming machine installation information transmission memory area is "0," it is possible to determine whether the main control chip ID number has been received from the main control CPU 510. In other words, it is possible to determine whether the main control CPU 510 has started up.
Therefore, without providing the main control startup waiting timer M1, it is possible to determine whether the main control CPU 510 has completed the process (predetermined process) of sending a command (main control chip ID number) (whether the main control CPU 510 has started up) by determining whether the main control chip ID number in the memory area for transmitting gaming machine installation information is not "0".
Furthermore, it may be possible to determine whether the main control CPU 510 has completed the process of sending a command by determining whether at least one of the main control chip manufacturer code or main control chip product code is not "0", not limited to the main control chip ID number in the memory area for transmitting gaming machine installation information.

(Example 2)
In addition, it is also possible to determine whether the main control CPU 510 has completed the process of sending a command (whether the main control CPU 510 has started up) by determining whether the main control startup waiting timer M1 has become "0" and whether at least one of the main control chip ID number, main control chip manufacturer code, or main control chip product code in the memory area for transmitting gaming machine installation information is not "0".
(Example 3)
Furthermore, in the sixth embodiment, after the power is turned on, the main control CPU 510 instructs the medal count control CPU 520 to:
The command is configured to be sent in the following order: 1) Main control chip ID number 2) Main control chip manufacturer code 3) Main control chip product code 4) Role ratio type.
Here, "role ratio type" is data for specifying the type of display of the role ratio monitor, where "0" indicates no role ratio monitor, "1" indicates the "7U" type, and "2" indicates the "7P" type.
Therefore, when a role ratio type command is received from the main control CPU 510, it can be determined that all of the above commands 1) to 4) have been received.
Therefore, without setting up the main control startup waiting timer M1, when a role ratio type is received, it may be determined that the main control CPU 510 has completed the process of sending a command (the main control CPU 510 has started up).
Alternatively, when the main control startup waiting timer M1 becomes "0" and a role ratio type is received, it may be determined that the main control CPU 510 has completed the process of sending a command (the main control CPU 510 has started up).
(Example 4)
When the main control CPU 510 has completed sending all commands at startup, it is configured to send a dedicated command indicating the completion of transmission from the main control CPU 510 to the medal count control CPU 520. In this case, when the medal count control CPU 520 receives the dedicated command, it may determine that the main control CPU 510 has finished the command sending process (the main control CPU 510 has started up).

(4) In the interrupt processing of the medal count control CPU 520 in FIG. 93, various conditions can be set for determining that a power outage has occurred.
For example, it may be determined that a power outage has occurred if a power outage signal is detected even once, or it may be determined that a power outage has occurred if a power outage signal is detected multiple times (for example, two times) in consecutive interrupt processing.
If it is determined that a power outage has occurred if a power outage signal is detected even once, a power outage can be detected earlier, but there is a risk of false detection (executing power outage processing even though a power outage has not actually occurred).
In contrast, if it is determined that a power outage has occurred when a power outage signal is detected during multiple consecutive interrupt processes, the time until the determination is made will be delayed compared to when a power outage is determined to have occurred when a power outage signal is detected only once, but the reliability of the power outage determination can be improved.

(5) In the above embodiment, a temporary complete function flag is provided, but this is not limiting and the temporary complete function flag need not be provided. In this case, the complete function is activated at the end of a game in the special game state when the MY counter reaches "+19000," and the gaming machine 10 comes to a halt. Therefore, even if the special game state is in progress, the game comes to a halt (end) at the end of a game when the MY counter reaches "+19000."
On the other hand, in the above embodiment, when the complete function tentative flag is turned on and then the complete function activation flag is turned on, the complete function tentative flag is turned off. However, this is not limiting, and the complete function tentative flag may remain on even after the complete function activation flag is turned on.
(6) The main control start-up wait timer M1 and the post-connection confirmation wait timer M2 are not necessarily required. For example, the main control start-up wait timer M1 may be included but the post-connection confirmation wait timer M2 may not be included, the main control start-up wait timer M1 may not be included but the post-connection confirmation wait timer M2 may be included, or neither the main control start-up wait timer M1 nor the post-connection confirmation wait timer M2 may be included.
In either case, the gaming machine information notification that is first transmitted after the power is turned on is a gaming machine information notification that includes gaming machine installation information.

(7) The generation of gaming machine performance information shown in Figure 97 (updating the number of games played, total number of coins inserted, total number of payouts, total number of payouts from special devices, total number of payouts from consecutive special devices, and MY in the memory area for transmitting gaming machine performance information) was performed at the end of each game.
In addition, the ratio storage process (updating the cumulative role ratio, cumulative consecutive role ratio, cumulative advantageous zone ratio, cumulative role ratio with instructions, and cumulative role etc. state ratio in the memory area for transmitting gaming machine performance information) shown in Figures 98 and 99 was performed each time gaming machine performance information was transmitted.
However, without being limited to this, any of the above processes may be executed for each interrupt process of the medal count control CPU 520, for each predetermined number of interrupt processes (for example, once every 100 interrupt processes), or at each predetermined timing (for example, at the end of each game).
Furthermore, the processing shown in Figures 98 and 99 may be performed each time the processing (ratio calculation processing) shown in Figures 80 to 83 is executed (after each game or after each 400 games (multiple games)).
(8) In Figure 80, when it is determined that the total number of plays upper limit flag is "FFh", the processing of step S682 is skipped. However, this is not limited to this, and when it is determined that the total number of plays upper limit flag is "FFh", a process of updating the total number of plays upper limit flag to "FFh" may be executed.
Similarly, in FIG. 82, when it is determined that the total payout number upper limit flag is "FFh", the processing of step S768 is skipped, but this is not limited to this, and when it is determined that the total payout number upper limit flag is "FFh", the processing of updating the total payout number upper limit flag to "FFh" may be executed.

(9) The sixth embodiment does not necessarily have to be implemented alone, but can also be implemented in appropriate combination with at least some of the first to fifth embodiments.

Seventh Embodiment
Next, a seventh embodiment will be described.
In the seventh embodiment, as in the sixth embodiment, the "game medium" is referred to as a "medal." However, the seventh embodiment is the same as the other embodiments in that the gaming machine 10 is a medal-less gaming machine (smart gaming machine, smart pachislot), and the game medium is an electronic medal (electronic game medium).
The hardware configuration (block diagram) of the seventh embodiment is the same as that of the sixth embodiment shown in Fig. 77. In other words, two one-chip microprocessors are mounted on the main control board 50, one of which is the main control CPU 510 and the other is the medal count control CPU 520.
Furthermore, the use area of the medal count control RWM 522 is the same as that in Figures 90 to 91 (sixth embodiment).
When the gaming machine 10 is powered on, the medal count control CPU 520 is started up first, and then the main control CPU 510 is started up.
On the other hand, when the power is cut off, the main control CPU 510 is first shut down, and then the medal count control CPU 520 is shut down.

Furthermore, in the seventh embodiment, as in the other embodiments described above, the upper limit of the total number of medals that can be stored in the medal count control RWM 522 is "16383 (decimal number)."
Furthermore, in the seventh embodiment, if the total number of medals stored in the medal count control RWM 522 exceeds "16,368 (decimal)", the main control CPU 510 will enter an error state and the game will not be able to proceed (invalidating operation acceptance of the start switch 41, invalidating operation acceptance of the bet switch 40, and invalidating operation acceptance of the settlement switch 43).
In the following explanation, the total number of medals "16,368" will be referred to as the "upper limit (of the total number of medals) that can be played," and the total number of medals "16,383" will be referred to as the "upper limit (of the total number of medals) that can be stored in the medal number control RWM 522."
Since "16383 >16368", the total number of medals will reach "16368" before reaching "16383", making it impossible to continue playing the game. Therefore, in principle, the total number of medals will not reach "16383". However, there is a possibility that some kind of malfunction, such as noise, will occur and the total number of medals will exceed "16368".

Furthermore, the upper limit of the total number of medals that can be used to progress through a game is designed to be smaller than the upper limit of the total number of medals that can be stored in the medal count control RWM 522. In particular, it is preferable to design the difference between the upper limit of the total number of medals that can be used to progress through a game and the upper limit of the total number of medals that can be stored in the medal count control RWM 522 to be equal to or greater than the maximum number of medals that can be awarded in one game (for example, 15). This makes it possible to prevent the upper limit of the total number of medals that can be stored in the medal count control RWM 522 from being reached even if a game is started when the total number of medals that can be used to progress through a game is equal to or less than the upper limit, and the maximum number of medals that can be awarded in one game has been awarded.
On the other hand, when the total number of medals reaches "15,000" or more, the main control CPU 510 sends a command to the sub-control CPU 85, and the sub-control CPU 85 issues a notification urging the player to count. Because of this configuration, information indicating that the total number of medals is "15,000" or more and below the upper limit for which game progress can be made is sent in the following order: medal count control CPU 520 → main control CPU 510 → sub-control CPU 85 (sub-control board 80). Furthermore, when the total number of medals reaches "15,000" or more, medals cannot be lent out from the lending unit 200 (operation of the lending switch 202 is invalid). In other words, the upper limit for the total number of medals that can be lent out is "14,999."
Even if the total number of medals exceeds 15,000 and a notification prompting counting is being issued, the game can continue as long as the total number of medals is below the upper limit of 16,368, which is the maximum number of medals that can be used to continue the game.
Furthermore, when the total number of medals exceeds the upper limit for game progress, that information is sent to the sub-control CPU 85, and the sub-control CPU 85 may notify the user that game progress has stopped because the total number of medals has exceeded the upper limit for game progress. To achieve this, information indicating that the total number of medals has exceeded the upper limit for game progress is sent in the following order: medal number control CPU 520 → main control CPU 510 → sub-control CPU 85 (sub-control board 80).

The seventh embodiment is an invention relating to the transmission and reception of commands between the main control CPU 510 and the medal count control CPU 520.
Figure 100 is a diagram showing the transmission and reception of commands (bet, settlement, award) between the main control CPU 510 (also referred to as the "main control means 510" or "main control chip 510") and the medal count control CPU 520 (also referred to as the "medal (gaming medium) number control means 520" or "medal (gaming medium) number control chip 520") in the seventh embodiment, where (a) shows an overview and (b) shows the content of the command.
The main control CPU 510 transmits main control commands to the medal count control CPU 520, and the main control commands include request commands. The main request commands in the seventh embodiment are a bet request command, a settlement request command, and a grant request command.
In the following description, unless otherwise specified, the term "request command" refers to at least one of a bet request command, a settlement request command, or a grant request command.
When the main control CPU 510 detects that a bet switch 40 (1 bet switch 40a or 3 bet switch 40b) has been operated, it sends a bet request command to the medal count control CPU 520 requesting a bet (also called "insertion") of the number of medals corresponding to the operated bet switch 40 (subtraction from the total number of medals).
In addition, when the main control CPU 510 detects that the settlement switch 46 has been operated, it sends a settlement request command to the medal count control CPU 520 requesting that the number of medals currently bet be returned to the total number of medals (added to the total number of medals).
Furthermore, when a pattern combination corresponding to a minor role that results in the awarding of medals (also called "payout") is displayed, the main control CPU 510 sends an award request command to the medal count control CPU 520 requesting the awarding of medals (addition to the total number of medals).

In the seventh embodiment, the bet request command and the settlement request command are transmitted in a single command, each command corresponding to the number of bets or the number of settlements.
Specifically, when the operation of the 1 bet switch 40a is detected when the current number of bets is "0", the main control CPU 510 transmits a bet request command for the number of medals "1".
Similarly, when the main control CPU 510 detects operation of the 3 bet switch 40b when the current number of bets is "0", it sends a bet request command for the number of medals "3". Furthermore, when the main control CPU 510 detects operation of the 3 bet switch 40b when the current number of bets is "1", it sends a bet request command for the number of medals "2". Furthermore, when the main control CPU 510 detects operation of the 3 bet switch 40b when the current number of bets is "2", it sends a bet request command for the number of medals "1". Furthermore, when the main control CPU 510 detects operation of the 1 bet switch 40a or the 3 bet switch 40b when the current number of bets is "3", it does not send a bet request command.
Furthermore, when operation of the settlement switch 46 is detected and the current number of bets is "x" (where "x" is any of "1" to "3"), the main control CPU 510 sends a settlement request command for the settlement number "x". Note that when operation of the settlement switch 46 is detected when the current number of bets is "0", the main control CPU 510 does not send a settlement request command.
However, without being limited to the above, the bet request command and the settlement request command may be sent with the medal number "1" each. For example, when the current number of bets is "0" and the operation of the 3-bet switch 40b is detected, the main control CPU 510 may send a bet request command with the medal number "1" three times. Similarly, when the current number of bets is "3" and the operation of the settlement switch 46 is detected, the main control CPU 510 may send a settlement command with the medal number "1" three times.
On the other hand, when a symbol combination corresponding to a minor role with an award number of "x" (where "x" is any of "1" to "15") is stopped and displayed, the main control CPU 510 transmits an award request command for the number of medals "1""x" times. However, this is not limited to this, and when a symbol combination corresponding to a minor role with an award number of "x" is stopped and displayed, the main control CPU 510 may transmit an award request command for the number of medals "x" once. Note that when a symbol combination corresponding to a minor role is not stopped and the number of game media awarded is "0", or when a symbol combination corresponding to a replay is stopped and displayed, the main control CPU 510 does not transmit an award request command.

As shown in Fig. 100(b), the request command is made up of two bytes. In the seventh embodiment, for example, taking the settlement request command "A10xH" as an example, "A1H" is referred to as the upper byte and "0xH" is referred to as the lower byte.
Furthermore, the "0" in the lower byte "0xH" is referred to as the most significant digit of the lower byte, and the "x" is referred to as the least significant digit of the lower byte.
The first byte of the request command is a value that identifies whether the request command is for betting, settlement, or awarding. The first byte of a betting request command is "A0H", the first byte of a settlement request command is "A1H", and the first byte of an award request command is "A2H".
The lowest digit of the lowest byte is a value indicating the medal count "x." For example, if the medal count is "1," it is "1H," and if the medal count is "3," it is "3H."
Therefore, for example, the bet request command for the medal number "1" is "A001H." Also, for example, the settlement request command for the medal number "3" is "A103H."

On the other hand, the medal count control CPU 520 transmits medal count control commands to the main control CPU 510. One of the medal count control commands is a request response command that is a reply to the request command.
When the medal count control CPU 520 receives a request command from the main control CPU 510, it immediately sends a response command to the main control CPU 510 (a bet request response command for a bet request command, a settlement request response command for a settlement request command, and an award request response command for an award request command). The response command consists of two bytes, and the upper byte has the same value as the request command. Therefore, the upper byte of a bet request response command is "A0H", the upper byte of a settlement request response command is "A1H", and the upper byte of an award request response command is "A2H".
Furthermore, if the response command is a request response command indicating that the request command has been successfully received, the lowest byte of the response command will have the same value as the lowest byte of the received request command. Therefore, if the lowest byte of the received request command is "0xH", the lowest byte of the response command will generally be "0xH".

However, noise or other issues may occur during communication between the main control CPU 510 and the medal count control CPU 520, and the value of the request command received by the medal count control CPU 520 may differ from the value of the request command sent by the main control CPU 510. When cheating is committed, the value of the request command received by the medal count control CPU 520 may also differ from the value of the request command sent by the main control CPU 510. For example, the value of the lowest byte of the request command sent by the main control CPU 510 may be "01H," but the value of the lowest byte of the request command received by the medal count control CPU 520 may be "02H." Even in such a case, if the medal count control CPU 520 determines that the number of bets, settlement amount, and awarded amount in the request command received are normal, the response command will send the received value of the lowest byte as is.
Specifically, for example, the main control CPU 510 may send a bet request command "A001H" (bet number "1"), but noise or the like may occur in the communication between the main control CPU 510 and the medal count control CPU 520, and the bet request command received by the medal count control CPU 520 may be "A003H" (bet number "3"). In this case, the medal count control CPU 520 cannot determine that the value of the bet request command sent by the main control CPU 510 is different from the value of the bet request command it received. For this reason, as long as the bet number in the received bet request command is a normal value, it will send the value of the received bet request command to the main control CPU 510 as a bet request response command.

Furthermore, when the medal count control CPU 520 sends the response command, if the VL signal is on (communication is possible) between the medal count control CPU 520 and the lending unit 200, the most significant digit of the lowest byte (in other words, the D7 bit of the lowest byte) is set to "0." In this case, the lowest byte of the response command becomes "0xH." In other words, the data in the lowest byte is not changed.
In contrast, when the medal count control CPU 520 transmits the response command, if the VL signal is off (communication is disabled) between the medal count control CPU 520 and the lending unit 200, the value of the most significant digit of the lower byte is set to "8", in other words, the D7 (most significant) bit of the lower byte is set to "1". Therefore, the lower byte of the response command is set to "8xH".
Therefore, for example, when a bet request response command "A003H" is received and the VL signal is on when the bet request response command is sent, the bet request response command becomes "A003H".
On the other hand, when the bet request response command "A003H" is received and the VL signal is off when the bet request response command is sent, the bet request response command becomes "A083H".

Furthermore, if the number of bets in the received bet request command exceeds the total number of medals, the medal count control CPU 520 sets the D7 bit in the lowest byte of the bet request response command to "1" and transmits it. For example, when the total number of medals is "2," the medal count control CPU 520 may receive a bet request command with a bet number of "3." In such a case, it is not possible to bet the requested number of bets.
Therefore, for example, when the total number of medals is "2", if the medal number control CPU 520 receives a bet request command "A003H", it will send "A083H" as a bet request response command.

Furthermore, if the medal count control CPU 520 executes the settlement process for the settlement number corresponding to the received settlement request command (adding it to the total medal count) and the total medal count exceeds the upper limit of the total medal count that can be stored ("16,383" in decimal), it will deem the medal settlement for the received settlement request command unsettled and send a settlement request response command with the D7 bit in the lowest byte set to "1." For example, if the total medal count is "16,383" (the upper limit that can be stored), the medal count control CPU 520 may receive a settlement request command "A103H" with a settlement number of "3." In such a case, it will send a settlement request response command "A183H" to the main control CPU 510.
As mentioned above, when the total number of medals exceeds "16,368," the game cannot proceed and settlement is also not possible, so no settlement request command is sent from the main control CPU 510 to the medal count control CPU 520. However, there is a possibility that some kind of malfunction may occur and the game may proceed (for example, if information indicating that the total number of medals has exceeded "13,368" is not sent to the main control CPU 510 due to noise, etc.).
Here, if the game can proceed even if the total number of medals exceeds "16368",
Number of bets: "0", total number of medals: "16369"
The bet switch 40 is operated in the case of
Number of bets: "3", total number of medals: "16366"
After this, when the settlement switch 46 is operated, the main control CPU 510 transmits a settlement request command "A103H" to the medal count control CPU 520. When the medal count control CPU 520 receives the settlement request command "A103H", it updates the total medal count (FIG. 91) to "16,369", updates the number of bets (FIG. 91) to "0", and transmits a settlement request response command "A103H" to the main control CPU 510 to the effect that the settlement request command "A103H" has been normally received.
In other words, the medal count control CPU 520 sends the settlement request response command "A183H" when the total medal count exceeds "16,383," except when the VL signal is off. Therefore, even if the total medal count exceeds "16,368," the medal count control CPU 520 does not send the settlement request response command "A183H" as long as it does not exceed "16,383."

Furthermore, if the medal count control CPU 520 executes the granting process for the number of medals corresponding to the received grant request command (adding the number to the total medal count) and the total number of medals that can be stored exceeds the upper limit ("16,383") of the total medal count that can be stored, it determines that the medals corresponding to the received grant request command cannot be granted and transmits the grant request response command with the D7 bit in the lowest byte set to "1." For example, as described above, even if some malfunction occurs and the total medal count exceeds "16,368," game progress is not disabled, and the total medal count reaches "16,383." In this case, the medal count control CPU 520 receives the grant request command "A201H" for the number of medals to be granted of "1." In such a case, it transmits the grant request response command "A281H" to the main control CPU 510.
When the total number of medals is "16,368," the main control CPU 510 can send an award request command "A201H" for an award number of "1" to the medal count control CPU 520. When the medal count control CPU 520 receives the award request command "A201H," it sends an award request response command "A201H" to the main control CPU 510, assuming that the award request command has been received normally. This makes the total number of medals "16,369." When the total number of medals reaches "16,369," the main control CPU 510 stops the progress of the game. In other words, the medal awarding process is executed normally even when the total number of medals becomes "16,369."
Furthermore, if some malfunction occurs and the total number of medals exceeds "16,368", the game continues, a small win with an award number of "1" is won in this game, the main control CPU 510 sends an award request command "A201H" with an award number of "1" to the medal count control CPU 520, and if the medal count control CPU 520 receives the award request command "A201H", it sends an award request response command "A201H" to the main control CPU 510, assuming that it has normally received the award request command. In other words, the medal count control CPU 520 sends the award request command "A281H" when the total number of medals exceeds "16,383", but not when the total number of medals exceeds "16,368", except when the VL signal is off.

Furthermore, the medal count control CPU 520 does not send a response command if the number of bets, the settlement amount, or the awarded amount among the values of the received request command is an abnormal value.
For example, if the value of the lowest byte of the received bet request command or settlement request command is "01H", "02H", or "03H", it is judged to be normal, and if the value is "00H" or "04H" or higher, it is judged to be abnormal.
Furthermore, if the value of the lowest byte of the received grant request command is "01H", it is determined to be normal, and if it is anything other than "01H", it is determined to be abnormal.

101 to 106 are diagrams showing the flow of sending and receiving request commands and request response commands between the main control CPU 510 and the medal count CPU 520.
101(1) is a diagram showing the normal transmission and reception of a bet request command and a bet request response command. The total number of medals before the 3 bet switch 40b is operated is assumed to be "10,000."
101(1), when the main control CPU 510 detects the operation of the 3 bet switch 40b, it sends a bet request command "A003H." In this example, the total number of medals is "10,000," and it is assumed that the player has the number of medals bet corresponding to the operated bet switch 40.
Then, when the medal count control CPU 520 receives the bet request command "A003H",
1) Bet availability judgment (whether the requested number of bets is within the normal range, and whether the total number of medals is equal to or greater than the requested number of bets)
2) Determine whether the VL signal is on. If the requested number of bets is within the normal range, the total number of medals is equal to or greater than the requested number of bets, and the VL signal is on, it is determined that a bet is possible, and the total number of medals is updated from "10,000" to "9,997", and the number of bets is updated from "0" to "3".
The total number of medals and the number of bets, which are updated based on the reception of a bet request command (similar to a settlement request command), are data (see Figure 91) used to generate hall control and fraud monitoring information during the gaming machine information notification sent by the medal count control CPU 520 to the lending unit 200. In Figure 91, the 3-byte number of medals corresponds to the "total number of medals," and the number of inserted medals corresponds to the "number of bets." In the following explanation, when "total number of medals and number of bets (Figure 91)" is mentioned, it refers to the above data.
Then, the medal count control CPU 520 transmits a bet request response command "A003H" indicating that the bet request command has been normally received.
When the main control CPU 510 receives a normal bet request response command "A003H", it executes the three-coin bet process.
Here, the number of bets is managed by the main control CPU 510. The number of bets updated by the medal number control CPU 520 based on the reception of a bet request command is data for notifying gaming machine information (FIG. 91).
In addition, the bet processing here includes the process of updating the bet number data stored in the main control RWM 512 (process of updating from "0" to "3"), the process of updating the display (7-segment LED) of the bet number display unit 77 (see Figure 77), and the process of updating the lighting of the status display LED (not shown).

Here, the status display LEDs are:
1) 1 bet indicator lamp (LED that lights up when the number of bets is "1" to "3")
2) 2-bet indicator lamp (LED that lights up when the number of bets is "2" or "3")
3) 3-bet indicator lamp (LED that lights up when the number of bets is "3")
4) Game start indicator lamp (an LED that lights up when a specified number of medals have been bet and the start switch 41 is ready to be operated. It does not light up during automatic betting on replays, but lights up after automatic betting on replays has been placed.)
5) Bet request indicator lamp (also called "insert lamp" or "insertion indicator lamp." An LED that lights up when medals can be bet (so-called bet waiting state (state where the number of bets is "0" to "2")).
6) Replay indicator lamp (LED that lights up after the replay is stopped.)
Examples include:
The lighting update process of the status display LED in the betting process by the main control CPU 510 includes the lighting process of the bet indicator lamp, the lighting process of the game start indicator lamp, and the extinguishing process of the bet request indicator lamp.

FIG. 101 (2) shows an example in which the VL signal is off at the time when the medal count control CPU 520 transmits the bet request response command.
As will be described in detail later, the bet request command cannot be sent if the VL signal is off at the time the bet switch 40 is operated. The main control CPU 510 determines the state of the VL signal based on the command sent from the medal count CPU 520.
Therefore, in this example, the VL signal was on when the main control CPU 510 sent the bet request command, but the VL signal was off when the medal count control CPU 520 sent the bet request response command.
When the main control CPU 510 detects the operation of the 3-bet switch 40b, it sends a bet request command "A003H".

Next, when the medal count control CPU 520 receives the bet request command "A003H," it determines that the requested bet number "3" is within the normal range and is less than the total medal count. However, it determines that the VL signal is off. In this case, it sends the bet request response command "A083H," which corresponds to the VL signal being off.
In this case, the medal count control CPU 520 does not update the total medal count and the bet count (FIG. 91).
When the main control CPU 510 receives the bet request response command "A083H", it determines that the bet request command was not accepted normally and does not execute the bet processing.
However, in this case, the main control CPU 510 does not execute error processing. In this embodiment, when the VL signal is off or when the requested number of bets exceeds the total number of medals, it is not considered to be an abnormality. In this way, by not executing bet processing but not executing error processing, it is possible to avoid causing discomfort to the player. However, this is not limited to this, and some kind of error processing may be executed even when the VL signal is off.
However, when the main control CPU 510 receives a VL signal OFF from the medal count control CPU 520, no bet request command will be sent even if the bet switch 40 is operated until the main control CPU 510 receives a VL signal ON from the medal count control CPU 520.

101(3) shows an example of a case where the bet number in the bet request command received by the medal count control CPU 520 is an abnormal value. Note that the VL signal in this example is assumed to be ON.
When the main control CPU 510 detects operation of the 3 bet switch 40b while the bet number is "0," it sends a bet request command "A003H." However, noise or other issues may occur before the medal count control CPU 520 receives the bet request command, and the bet number may not be within the normal range ("1" to "3"). In this example, a bet request command of "A004H," meaning a bet number of "4," is received. In this way, when a bet request command with an abnormal bet number is received, the medal count control CPU 520 does not send a bet request response command to the main control CPU 510.
Furthermore, the medal count control CPU 520 does not update the total medal count and the bet count (FIG. 91).
If the main control CPU 510 does not receive a bet request response command within a predetermined period after sending the bet request command "A003H," it determines that an abnormality has occurred and executes error processing. In this case, the main control CPU 510 will of course not execute bet processing.
The error processing performed by the main control CPU 510 here includes the following processing.
(1) The error number is stored (saved) in the main control RWM 512. In this example, since it is an input request error, for example, "E0" is stored. In the case of a settlement request error, "E1" is stored, and in the case of an allocation request error, "E2" is stored. In this way, a different value is stored for each type of error.
(2) An error command is sent to the sub-control CPU 85 to start notifying the error.
(3) Among the status display LEDs, a process of turning off the game start indicator lamp is performed. This process is a process of storing "0", which means turning off the game start indicator lamp, in the lighting data of the game start indicator lamp.
(4) Wait until the reset switch 14 is turned on.
(5) When the rising edge of the reset switch 14 is detected, the value of the error number stored in (1) above is cleared (set to "0").
(6) Next, an error release command is sent to the sub-control CPU 85 to end the error notification.
The above is not limited to when an input request error occurs, but is also performed when a settlement request error occurs (for example, in the case of Figure 104 (3)) or when an allocation request error occurs. In the following explanation, when the error processing shown in (1) to (6) is performed, it will be referred to as the "above-mentioned error processing."
In this way, when the medal count control CPU 520 receives a bet request command with an abnormal value, it does not send a bet request response command to the main control CPU 510, but even if the main control CPU 510 does not receive the bet request response command, it can know that an error related to the bet request command has occurred because it does not receive the bet request response command within a predetermined period of time. The same applies to the settlement request response command and the award request response command, which will be described later.
After the main control CPU 510 executes the error processing, it executes a loop processing in which the game cannot proceed unless the reset switch 14 is operated (the same applies to the other examples of error processing described below).

102(4) shows an example when the medal count control CPU 520 fails to receive a bet request command. In this example, the VL signal is assumed to be ON.
When the main control CPU 510 detects operation of the bet switch 40 while the number of bets is "0", it transmits a bet request command. However, there may be a communication failure between the main control CPU 510 and the medal count control CPU 520, and the bet request command may not be transmitted to the medal count control CPU 520. In this case, the medal count control CPU 520 does not know that a bet request response command has been transmitted from the main control CPU 510, and therefore does not perform the process of transmitting the bet request response command.
In this case, the medal count control CPU 520 does not update the total medal count and the bet count (FIG. 91).
On the other hand, since the main control CPU 510 does not receive a bet request response command within a predetermined period after sending the bet request command, it determines that an abnormality has occurred and executes error processing without executing bet processing.

Figure 102 (5) is an example in which the number of bets in the bet request command sent from the main control CPU 510 is different from the number of bets in the bet request command received by the medal count control CPU 520, and the number of bets in the bet request command received by the medal count control CPU 520 is within the normal value range.
In this example, the total number of medals is assumed to be "3" or more.
When the main control CPU 510 detects operation of the 1 bet switch 40a when the number of bets is "0," it transmits a bet request command "A001H" (bet number "1"). However, suppose noise or the like occurs in the communication between the main control CPU 510 and the medal count control CPU 520, and the bet request command received by the medal count control CPU 520 is "A003H" (bet number "3"). In this case, the medal count control CPU 520 is unaware that the main control CPU 510 has transmitted the bet request command "A001H," and because the total medal count is "3" or greater, a bet is possible. Therefore, the medal count control CPU 520 determines that a bet of "3" is possible and determines that the bet request command "A003H" is normal. Therefore, the medal count control CPU 520 updates the total medal count and the number of bets (Figure 91). Thereafter, the medal count control CPU 520 transmits a bet request response command "A003H" to the main control CPU 510. That is, the main control CPU 510 sends a bet request command of "A001H" to the medal count control CPU 520, but the medal count control CPU 520 sends a bet request response command of "A003H" to the main control CPU 510.
When the main control CPU 510 receives the bet request response command "A003H", it determines that an error has occurred because the number of bets in the transmitted bet request command does not match the number of bets in the received bet request response command, and executes the error processing described above. Note that the main control CPU 510 does not execute the bet processing.

102 (6) shows an example where the number of bets in the bet request command sent from the main control CPU 510 differs from the number of bets in the bet request command received by the medal count control CPU 520, and a bet cannot be made with the number of bets in the bet request command received by the medal count control CPU 520. In this example, the total number of medals is assumed to be "1."
When the main control CPU 510 detects operation of the 1 bet switch 40a, it sends a bet request command "A001H" (bet number "1"). However, suppose noise or the like occurs in the communication between the main control CPU 510 and the medal count control CPU 520, and the bet request command received by the medal count control CPU 520 is "A003H" (bet number "3"). In this case, the total medal count is "1", so a bet of "3" cannot be placed. For this reason, the medal count control CPU 520 does not update the total medal count and the number of bets (Figure 91).
Then, the medal count control CPU 520 sends a bet request response command "A083H" to the main control CPU 510.
When the main control CPU 510 receives the bet request response command "A083H," it determines that the number of bets in the transmitted bet request command is different from the number of bets in the received bet request response command, and executes the error processing described above. Note that the main control CPU 510 does not execute bet processing.

FIG. 103(7) shows an example when the bet switch 40 is operated while the VL signal is off.
If the VL signal turns off during game standby and the main control CPU 510 recognizes that the VL signal is off, the game cannot proceed until the main control CPU 510 recognizes that the VL signal is on. Specifically, even if the bet switch 40 is operated, the operation is invalid, even if the settlement switch 46 is operated, the operation is invalid, and even if the start switch 41 is operated, the operation is invalid.
Therefore, even if the main control CPU 510 detects the operation of the bet switch 40, it does not send a bet request command to the medal count control CPU 520. Therefore, the bet process is not executed. Furthermore, the error process is not executed either.
103(8) shows an example in which a bet operation is made that exceeds the total number of medals. In this example, the VL signal is assumed to be ON.
As will be described in detail later, the medal count control CPU 520 transmits a command (a 2-byte (16-bit) command) including information (2 bits) on the total medal count to the main control CPU 510 for each interrupt process. The 2-bit information on the total medal count is
1) If the total number of medals is "0": "00B" (betting not permitted)
2) If the total number of medals is "1": "01B"("1" bet allowed)
3) If the total number of medals is "2": "10B"("1" or "2" bet allowed)
4) If the total number of medals is "3" or more: "11B" (bet "1" to "3" allowed)
is.
Therefore, the main control CPU 510 is able to grasp the total number of medals.
For example, when the total number of medals is "0", betting is not possible. Also, if the 3 bet switch 40b is operated when the total number of medals is "1" or "2", betting is not possible. In this way, when the number of bet requests exceeds the total number of medals, betting is not possible, and the main control CPU 510 invalidates the operation of the bet switch 40 even if it is operated, and does not send a bet request command to the medal count control CPU 520. Also, the main control CPU 510 does not execute bet processing, nor does it execute error processing.

Figures 104 and 105 are diagrams showing the flow of sending and receiving settlement request commands and settlement request response commands between the main control CPU 510 and the medal count CPU 520.
104(1) shows the normal transmission and reception of the settlement request command and the settlement request response command. In this example, the total number of medals is assumed to be "10,000." Also, the VL signal is assumed to be ON.
When the main control CPU 510 detects that the settlement switch 46 has been operated when the bet number is "3", it sends a settlement request command "A103H" for the settlement number of "3" to the medal count control CPU 520. When the medal count control CPU 520 receives the settlement request command,
1) Judgment on whether settlement is possible (whether the requested settlement number is within the normal range, and whether the total number of medals after settlement will not exceed the medal number upper limit)
2) Determine whether the VL signal is on.
The medal count control CPU 520 determines that settlement is possible when it determines that the requested settlement number is within the normal range, that the total medal count after settlement does not exceed the medal count upper limit, and that the VL signal is ON. As a result, the medal count control CPU 520 updates the total medal count and the number of bets (FIG. 91). Specifically, it updates the total medal count from "10,000" to "10,0003" (adding "3"), and updates the number of bets from "3" to "0" (subtracting "3"). The medal count control CPU 520 then sends the settlement request response command "A103H" (the same value as the settlement request command) to the main control CPU 510, indicating that the settlement request command has been successfully received.
When the main control CPU 510 receives the settlement request response command, it executes settlement processing, such as clearing the display data of the bet indicator lamp and updating (clearing) the bet number data from "3" to "0," as shown in FIG. 111 (described later).

Figure 104 (2) is an example in which the VL signal is off at the time the medal count control CPU 520 sends the settlement request response command.
As in the case of the bet request command described above, if the VL signal is off at the time the main control CPU 510 sends the settlement request command, the settlement request command will not be sent.
Therefore, in this example, the VL signal was on when the main control CPU 510 sent the settlement request command, but the VL signal was off when the medal count control CPU 520 sent the settlement request response command.
When the number of bets is "3", the main control CPU 510 detects operation of the settlement switch 46 and sends a settlement request command "A103H".
Next, the medal count control CPU 520 receives the settlement request command. However, the medal count control CPU 520 determines that the VL signal is off. In this case, the medal count control CPU 520 transmits the bet request response command "A183H" corresponding to the VL signal being off.
When the main control CPU 510 receives the bet request response command "A183H", it determines that the VL signal is off and does not execute the settlement process.
However, the main control CPU 510 does not execute error processing. As with bet processing, when the VL signal is off, it is assumed that no abnormality has occurred. However, this is not a limitation, and error processing may be executed even when the VL signal is off.

104(3) shows an example in which the settlement request command received by the medal count control CPU 520 is an abnormal value. Note that the VL signal in this example is assumed to be ON.
When the main control CPU 510 detects operation of the settlement switch 46 while the bet number is "3," it sends a settlement request command "A103H." However, there are cases where the settlement number is not within the normal range ("1" to "3") due to noise or fraudulent activity (cheating) occurring before the medal count control CPU 520 receives the settlement request command. In this example, it is assumed that the medal count control CPU 520 receives a bet request command "A105H," which indicates a settlement number of "5." In this way, when a settlement request command is received in which the settlement number is an abnormal value, the medal count control CPU 520 does not send a settlement request response command to the main control CPU 510. Naturally, the medal count control CPU 520 does not update the total medal count or the number of bets (FIG. 91).
If the main control CPU 510 does not receive a settlement request response command within a predetermined period after sending the settlement request command, it determines that an abnormality has occurred and executes the error processing described above.

FIG. 105 (4) shows the processing performed when a settlement request command is received when the total number of medals after settlement exceeds the upper limit that can be stored. In this example, the total number of medals before settlement is assumed to be "16,382." As mentioned above, if the total number of medals exceeds "16,368," game progress becomes impossible and settlement becomes impossible. Therefore, although the total number of medals should never reach "16,382," this example illustrates an example of sending the settlement request response command "A183H," and therefore assumes that some kind of malfunction has occurred that causes the total number of medals to reach "16,382."
When the settlement switch 46 is operated with the bet number set to "1," the main control CPU 510 sends a settlement request command "A101H" for a settlement number of "1" to the medal count control CPU 520. However, suppose that noise or the like occurs before the medal count control CPU 520 receives the settlement request command, and the settlement number in the settlement request command received by the medal count control CPU 520 is "A103H," which is "3." In this case, although the settlement number is within the normal range, the total medal count exceeds the upper limit of "16,383" that can be stored, making settlement impossible. Therefore, the medal count control CPU 520 sends a settlement request response command "A183H." Naturally, the medal count control CPU 520 does not update the total medal count or the number of bets (FIG. 91).
When the main control CPU 510 receives the settlement request response command "A183H," it determines that an error has occurred because the settlement number in the sent settlement request command differs from the settlement number in the received settlement request response command. Therefore, it executes the error processing described above. The settlement processing is not executed.

105 (5) shows an example of a case where the settlement number in the settlement request command sent from the main control CPU 510 differs from the settlement number in the settlement request command received by the medal count control CPU 520, making settlement impossible. In this example, the total medal count is assumed to be "10,000."
When the settlement switch 46 is operated when the number of bets is "3," the main control CPU 510 sends a settlement request command "A103H" for the settlement number of "3" to the medal count control CPU 520. However, suppose that noise or the like occurs before the medal count control CPU 520 receives the settlement request command, and the settlement request command received by the medal count control CPU 520 is "A101H," which is for the settlement number of "1." In this case, the medal count control CPU 520 determines that settlement is possible, and updates the total number of medals and the number of bets (Figure 91). Specifically, it adds "1" to the total number of medals and subtracts "1" from the number of bets. Then, it sends a settlement request response command "A101H," which is for the settlement number of "1," to the main control CPU 510.
When the main control CPU 510 receives the settlement request response command "A101H," it determines that an error has occurred because the settlement number in the sent settlement request command differs from the settlement number in the received settlement request response command, and executes the error processing described above. It also does not execute the settlement processing.

105(6) is an example of a case where the medal count control CPU 520 receives a settlement request command that does not allow settlement. In this example, for the same reason as in FIG. 105(4), the total medal count exceeds the upper limit of "16,368" that allows game progress, and becomes "16,381."
When the settlement switch 46 is operated when the bet number is "3", the main control CPU 510 sends a settlement request command "A103H" for the settlement number "3" to the medal count control CPU 520. When the medal count control CPU 520 receives this settlement request command, it determines whether or not settlement is possible, but determines that settlement is not possible because adding the settlement number "3" to the current total medal number "16,381" would cause the total medal number to exceed the upper limit of "16,383" that can be stored. As a result, the medal count control CPU 520 sends a settlement request response command "A183H" to the main control CPU 510 without updating the total medal number.
When the main control CPU 510 receives the settlement request response command "A183H", it does not execute the settlement process. It also does not execute the error processing described above.

106 and 107 are diagrams for explaining transmission and reception of an assignment request command and an assignment request response command.
FIG. 106(1) shows an example in which, when an award request command is sent, the VL signal is off at the time when the medal count control CPU 520 sends an award request response command.
In the seventh embodiment, if the VL signal is off when the start switch 41 is operated, the game does not proceed. However, even if the VL signal turns off after the start switch 41 is operated, and the stop switch 42 is operated while the VL signal is off, the operation is validated and the reels 31 are stopped. Furthermore, even if a symbol combination corresponding to a minor win is displayed in a stopped state when the VL signal is off, the medal awarding process is executed. In this way, when the VL signal turns off after the start switch 41 is operated, the reels 31 are stopped if the stop switch 42 is operated, and the awarding process is executed when a symbol combination corresponding to a minor win is displayed in a stopped state. This makes it possible to prevent disadvantages to the player.
In FIG. 106 (1), if the VL signal is ON when the start switch 41 is operated, the game starts (the reels 31 start spinning). Then, let's assume that the VL signal changes from ON to OFF during the game, and that the VL signal was OFF when the reels were completely stopped. When a symbol combination corresponding to a minor role is displayed as stopped when the reels are completely stopped, the main control CPU 510 executes the award process corresponding to the minor role. Therefore, when the main control CPU 510 determines that a symbol combination corresponding to a minor role is displayed as stopped, it transmits the award request command "A201H" to the medal count control CPU 520. When a symbol combination corresponding to a minor role in which the number of game media awarded is "1" is displayed as stopped, the main control CPU 510 transmits the award request command "A201H" to the one-time medal count control CPU 520. When a symbol combination corresponding to a minor role in which the number of game media awarded is "10" is displayed as stopped, the main control CPU 510 transmits the award request command "A201H" to the ten-time medal count control CPU 520.

When the medal count control CPU 520 receives the award request command "A201H", it updates the number of awards (the number of medals paid out in FIG. 91) (adds "1"), and then sends the award request response command "A201H" to the main control CPU 510.
When the main control CPU 510 receives the award request response command "A201H," it executes the award process. The award process is the process shown in FIG. 114, which will be described later. Furthermore, even if the VL signal is off, no error processing is executed. However, the main control CPU 510 stops the progress of the game after the award process is completed, based on the VL signal being off.
When the medal count control CPU 520 detects that the VL signal is off, it sends a command to the main control CPU 510 in the medal count control interrupt process to the effect that the VL signal is off (step S1146 in FIG. 121, which will be described later). The main control CPU 510 receives the command in the main control interrupt process to the effect that the VL signal is off (step S1042 in FIG. 115, which will be described later).

Furthermore, in the main control interrupt processing, the main control CPU 510 sends a command to the sub-control CPU 85 (synonymous with the "sub-control board 80"; the same applies below in the seventh embodiment) indicating that the VL signal is off (step S1049 in Figure 115). When the sub-control CPU 85 receives a command indicating that the VL signal is off, it executes a VL off notification. As a result, when the VL signal turns off during play, a VL off notification is immediately executed. Therefore, in Figure 106 (1), if the VL signal turns off during the period between when the start switch 41 is operated and when all reels 31 stop, the sub-control CPU 85 immediately notifies the user that VL is off. Even when a VL off notification is issued, the stop switch 42 can be operated.
Furthermore, when the awarding process is executed while the VL signal is off, the sub-control CPU 85 does not output an awarding sound. Although no awarding sound is output, the display of the payout number display unit 78 (7-segment LED) is updated.
In this way, after the start switch 41 is operated, even if the VL signal changes from on to off during the game, the progress of the game can be prevented from being stopped by executing the awarding process. This makes it possible to prevent the player from mistaking that a freeze has occurred during the game, for example. In other words, if the game progress is interrupted the moment the VL signal turns off during the game, the player may mistakenly believe that a freeze has occurred.

106(2) is a diagram showing the transmission and reception of the award request command and the award request response command when the award process is executed normally. In this example, it is assumed that a symbol combination corresponding to a small combination of “3” coins is stopped and displayed.
The bet request command and settlement request command described above are transmitted in a single transmission, each containing a requested bet number and a requested settlement number. For example, if the number of bets is "1", a bet request command "A001H" is transmitted, if the number of bets is "3", a bet request command "A003H" is transmitted, if the number of settlements is "1", a settlement request command "A101H" is transmitted, and if the number of settlements is "3", a settlement request command "A103H" is transmitted.
On the other hand, in the case of an assignment request command, an assignment request command with an assignment number of "1" is sent the same number of times as the assignment number. In other words, if the assignment number is "x", an assignment request command "A201H" is sent "x" times.
Therefore, assuming that all reels 31 have stopped and a 3-coin minor win has been achieved, the main control CPU 510 first transmits the first award request response command "A201H" to the medal count control CPU 520. When the medal count control CPU 520 successfully receives this award request command, it transmits the award request response command "A201H" to the main control CPU 510. When the main control CPU 510 receives the award request response command "A201H", it executes the award process of "1".

Next, after a predetermined period has elapsed, the main control CPU 510 sends a second grant request command "A201H." The start of the predetermined period can be set arbitrarily, such as when the grant request command is sent, when the grant request response command is received, when the grant process begins, or when the grant process ends. The interval between one grant process and the next can be set to, for example, about 0.1 to 0.5 seconds.
When the main control CPU 510 sends the second grant request command "A201H", the medal count control CPU 520, upon successfully receiving the grant request command "A201H", sends a grant request response command "A201H" to the main control CPU 510. When the main control CPU 510 receives the grant request response command "A201H", it executes the second "1" medal granting process.
Furthermore, after a predetermined period of time has elapsed, the main control CPU 510 transmits a third award request command "A201H." When the medal count control CPU 520 successfully receives the award request command "A201H," it transmits an award request response command "A201H" to the main control CPU 510. When the main control CPU 510 receives the award request response command "A201H," it executes the third "1" medal awarding process.
As described above, the awarding process is carried out one medal at a time, and a predetermined period is provided between the awarding process of one medal and the awarding process of the next medal, so the display on the payout number display unit 78 counts up, specifically, from "0" to "1" to (after the predetermined period has elapsed) "2" to (after the predetermined period has elapsed) "3", and does not add from "0" to "3" all at once. Therefore, even in a medalless gaming machine, it is possible to add medals at the same time as medals are paid out from the hopper.

107(3) shows an example of when an award request command that does not allow the award number to be increased is received. In this example, for the same reason as in FIG. 105(4), the total number of medals exceeds the upper limit of "16368" that can be played and becomes "16383" (the upper limit that can be stored).
In a situation where a small win with an award count of "1" has been won, the main control CPU 510 sends an award request command "A201H" to the medal count control CPU 520. When the medal count control CPU 520 receives the award request command "A201H," it determines whether or not it is possible to add to the total medal count. In this example, adding "1" to the total medal count of "16,383" would exceed the upper limit that can be stored, so it determines that addition is not possible. Therefore, the medal count control CPU 520 sends an award request response command "A281H" to the main control CPU 510 without updating the total medal count. When the main control CPU 510 receives the award request response command "A281H," it does not execute the award process. However, it does not execute the error processing described above.

Next, the flow of information processing by the main control CPU 510 and the medal count control CPU 520 will be explained based on a flowchart.
In the flowchart shown below, the main points of the seventh embodiment (request command, request response command, etc.) are mainly explained.
The main control CPU 510 executes a main control main process (also called a main loop) that is executed once per game. In parallel with the main control main process, the main control CPU 510 executes a main control interrupt process every 1.1175 ms.
The medal count control CPU 520 also executes medal count control main processing independently of the main control main processing, and executes medal count control interrupt processing every 1 ms in parallel with the medal count control main processing.
Figure 108 is a flowchart showing the main control main processing in the seventh embodiment.
First, in step S931, the main control CPU 510 executes a game state command set process. This process stores, in a command buffer, control commands to be sent to the sub-control CPU 85, such as a complete function activation flag, RT state, and the number of remaining medals during special play or AT play.
In the next step S932, the main control CPU 510 executes a game start setting process, which is the process shown in FIG.

In the next step S933, the main control CPU 510 executes a bet waiting process, which is the process shown in FIG.
Next, the process proceeds to step S934, where the main control CPU 510 determines whether the current game is a replay operation (whether the symbol combination corresponding to the replay was stopped and displayed in the previous game). If the current game is a replay operation, the process proceeds to step S937, and if the current game is not a replay operation, the process proceeds to step S935.
In step S935, the main control CPU 510 executes settlement processing. This processing is the processing shown in FIG. 111, which will be described later, and is processing to return the bet medals to the total medals based on the operation of the settlement switch 46. In this settlement processing, the above-mentioned processing to send a settlement request command and to receive a settlement request response command is executed. In the next step S934, betting processing is executed. This processing is the processing shown in FIG. 113, which will be described later, and is processing to execute a bet processing based on the operation of the bet switch 40. In this betting processing, the above-mentioned processing to send a bet request command and to receive a bet request response command is executed.
Next, the process proceeds to step S937, where the main control CPU 510 determines whether the number of bets matches the specified number (the number of bets required to start a game). In the seventh embodiment, the specified number is "3." If it is determined that the number of bets matches the specified number, the process proceeds to step S938, and if it is determined that the number of bets does not match the specified number, the process proceeds to step S933.
In step S938, the main control CPU 510 determines whether the start switch signal is rising (whether the start switch 41 has been operated), and if it determines that the start switch signal is rising, proceeds to step S939, and if it determines that the start switch signal is not rising, proceeds to step S933. Note that in the main control interrupt processing, operation of the start switch 41 is detected, and when operation of the start switch 41 is detected, the rising signal of the start switch 41 is turned on ("1").
In step S939, the main control CPU 510 executes a lottery for a winning combination (winning number). Then, in the next step S940, the main control CPU 510 starts the rotation of the reels 31.
In step S941, the main control CPU 510 determines whether the stop switch 42 has been operated, and if it determines that the stop switch 42 has been operated, proceeds to step S942, where the main control CPU 510 controls the reel 31 corresponding to the operated stop switch 42 to stop.

In the next step S943, the main control CPU 510 determines whether all the reels 31 have stopped. If it is determined that all the reels 31 have not stopped, the process returns to step S941. If it is determined that all the reels 31 have stopped, the process proceeds to step S944. In step S944, the main control CPU 510 determines whether a winning combination has occurred. Then, the process proceeds to step S945, where the main control CPU 510 executes a process of awarding medals corresponding to the winning combination. This process is the process shown in FIG. 114, which will be described later, and includes sending an award request command and receiving an award request response command.
Next, the flow advances to step S555, where a complete function calculation process is executed. This process involves updating the MY counter, etc., and is the process shown in FIG.
Next, the process proceeds to step S944, where a game status update process (also referred to as a "game end process") is executed. This process involves updating the operation status flag, etc. Then, the process returns to step S931.

Fig. 109 is a flowchart showing the game start setting process in step S932 of Fig. 108. Note that the game start setting process includes a plurality of processes other than the process shown in Fig. 109, but in the seventh embodiment, the process when a replay is stopped and displayed will be mainly described.
In step S951, the main control CPU 510 determines whether a replay was stopped in the previous game. If it is determined that a replay was stopped, the process proceeds to step S952. If it is determined that a replay was not stopped, the process according to this flowchart ends.
In step S952, the main control CPU 510 determines whether the VL signal is on. If the VL signal is on, the process proceeds to step S953, and if the VL signal is not on, the process loops until the VL signal is on.
In step S953, the number of medals bet in the previous game is read. In the next step S954, automatic bet number data is set. This process stores the number of medals read in step S953 as the automatic bet number (a predetermined storage area of the main control RWM 512). Next, the process proceeds to step S955, where processing to light the replay indicator lamp is executed. This process stores "1" (lit) in the lighting data of the replay indicator lamp (a predetermined storage area of the main control RWM 512). The actual lighting processing of the replay indicator lamp is executed in step S1052 (LED display control) in the main control interrupt processing of FIG. 115, which will be described later.

Next, the process proceeds to step S956, where the main control CPU 510 executes automatic bet processing. This process updates the lighting data for the 1-3 bet indicator lamps (predetermined storage area of the main control RWM 512) to "1" (lit). As above, the actual lighting process for the bet indicator lamps is executed in step S1052 (LED display control) in the main control interrupt process of FIG. 115.
As described above, in the seventh embodiment, when the VL signal is off and a symbol combination corresponding to a small win is displayed, a granting process is executed. In contrast, when a symbol combination corresponding to a replay is displayed, an automatic bet process is executed when the VL signal is on. On the other hand, when a symbol combination corresponding to a replay is displayed, and the VL signal is off, step S952 in FIG. 109 is looped. In other words, no automatic bet is made when the VL signal is off. This prevents the player from mistakenly believing that the next game can be started immediately.

FIG. 110 is a flowchart showing the bet waiting process in step S933 of FIG.
First, in step S961, the main control CPU 510 determines whether medals have been bet. If it is determined that medals have been bet, the process proceeds to step S966, and if it is determined that medals have not been bet, the process proceeds to step S962. In the seventh embodiment, when no bet has been made, the process can transition to the setting confirmation mode.
In step S962, the main control CPU 510 determines whether the front door is open and the setting key is on. If it is determined that the front door is open and the setting key is on, the process proceeds to step S963; otherwise, the process proceeds to step S966. Although not shown in FIG. 77, the gaming machine 10 is configured so that the door switch is turned on when the front door is opened. Furthermore, when the setting key is inserted and turned on (rotated in a predetermined direction), the setting key switch 12 is turned on.
In step S963, the main control CPU 510 executes a setting value display process. Steps S963 to S965 are sometimes referred to as a setting confirmation mode. The process of step S963 performs a setting so that the current setting value can be displayed on the setting value display means 73 (7-segment LED) in FIG. 77. This setting value display is dynamically lit in step S1052 (LED display control) in the main control interrupt process (FIG. 115).
Next, the process proceeds to step S964, where it is determined whether the front door is open and the setting key is off. If it is determined that the front door is open and the setting key is off, the process proceeds to step S965; if not, the process loops to step S964 (setting value display state). When the process proceeds to step S965, the main control CPU 510 performs processing to end the setting value display.
In the next step S966, the main control CPU 510 determines whether the complete function is activated (whether the complete function activation flag is "FFH"), whether the VL signal is off, or whether the total number of medals exceeds the upper limit ("16368") for game progress. If at least one of these conditions is met, step S966 is looped. On the other hand, if the complete function is not activated (the complete function activation flag is "00H"), the VL signal is on, and the total number of medals is equal to or less than the upper limit ("16368") for game progress, processing according to this flowchart is terminated.
As described above, in the complete calculation process after the end of a game (step S555 in FIG. 108), when the MY counter reaches "19000" and the complete function activation flag becomes "FFH" (step S579 in FIG. 88), a loop process is executed in this bet waiting process. Therefore, unless the power is turned on/off, further games cannot be played.
When the VL signal is OFF, a loop process is executed in this bet waiting process, and the game is suspended unless the VL signal is turned ON.
Furthermore, if the total number of medals exceeds the upper limit "16,368" for game progress, a loop process is executed in this bet waiting process. Therefore, unless the counting switch 47 is subsequently operated and the total number of medals becomes equal to or less than the upper limit "16,368" for game progress, the game progress is suspended.

FIG. 111 is a flowchart showing the settlement process in step S935 of FIG.
In step S971, the main control CPU 510 determines whether the settlement switch 46 has been operated (whether the rising signal of the settlement switch has been turned on). If it determines that the settlement switch 46 has been operated, the process proceeds to step S972, and if it determines that the settlement switch 46 has not been operated, the process according to this flowchart ends.
In step S972, the main control CPU 510 reads the bet medals. The current bet number data is stored in the main control RWM 512. Next, the process proceeds to step S973, where it is determined whether or not there are bet medals (whether or not the bet number data is "1" or greater). If it is determined that there are bet medals, the process proceeds to step S974, and if it is determined that there are no bet medals, the process according to this flowchart ends. In other words, if the settlement switch 46 is operated without having any bet medals, the process does not proceed to step S974 and subsequent steps, so a settlement request command is not sent and settlement processing is not executed.
In step S974, the main control CPU 510 sets a settlement request command. This process sets the value of the most significant byte, "A1," in the D register as the settlement request command. Next, the process proceeds to step S975, where processing is performed to wait for reception of a request response command (here, a settlement request response command) from the medal count control CPU 520. This processing is the processing shown in FIG. 112, which will be described later, and after transmitting the set request command, waits for a request response command sent from the medal count control CPU 520 and stores the received request response command in the command buffer.

In the next step S976, the main control CPU 510 determines whether the settlement request response command was received normally. Here, if the sent settlement request command and the received settlement request response command match, it is determined that the command was received normally. In contrast, if the sent settlement request command and the received settlement request response command do not match, it is determined that the command was not received normally. For example, this corresponds to the case where the settlement number in the sent settlement request command and the received settlement request response command do not match, or the most significant digit of the least significant byte of the received settlement request response command is "8" (the D7 bit of the least significant byte is "1"), or the most significant byte of the settlement request response command is not "A1". Furthermore, if the settlement request response command is not received within a predetermined period, it is also determined that the command was not received normally.
If it is determined that the signal has been received normally, the process proceeds to step S977, and if it is determined that the signal has not been received normally, the process according to this flowchart ends.
In step S977, the main control CPU 510 clears the display data of the bet display lamps and clears the bet number data (to "0"). These data are stored in the main control RWM 512. When the display data of the bet display lamps is cleared, the 1 to 3 bet display lamps are turned off by the LED display control of the main control interrupt processing. Also, when the bet number data is cleared, the display of the bet number display unit 77 is set to "0" by the LED display control of the main control interrupt processing.
Next, the process proceeds to step S978, where the main control CPU 510 sets the settlement command to be sent to the sub-control CPU 85. Then, in the next step S979, the main control CPU 510 performs control command set 1 processing. This processing writes the settlement command set in step S978 to the command buffer. As a result of this processing, the settlement command is sent to the sub-control board 80 in the next main control interrupt processing (step S1049 in Figure 115). Then, the processing according to this flowchart ends.

Fig. 112 is a flowchart showing the process of waiting for a request response command to be received from the medal count control CPU 520 in step S975 in Fig. 111. This process is a subroutine that is used not only during the settlement process, but also during the bet process in Fig. 113 and the award process in Fig. 114.
112, in step S981, the main control CPU 510 transmits a request command. In the case of settlement processing, it transmits a settlement request command, in the case of betting processing, it transmits a bet request command, and in the case of award processing, it transmits an award request command.
Next, the process proceeds to step S982, where the main control CPU 510 determines whether transmission of the request command has been completed, and if it determines that transmission has been completed, the process proceeds to step S983. In step S983, the main control CPU 510 executes interrupt wait processing. This processing waits after step S982 until the main control interrupt processing has been executed once. Once the request command is sent in step S982, the request response command is received in the first subsequent main control interrupt processing (step S1042 in FIG. 115).
When a request response command is received, it is stored in the command buffer of the main control RWM 512. Therefore, in the next step S984, the main control CPU 510 obtains the received request response command from the command buffer. In the next step S985, the command buffer is cleared.

In the next step S986, the main control CPU 510 determines whether the settlement request response command has been received normally. Here, "normally received" corresponds to receiving a settlement request response command that is identical to the settlement request command that was sent. If the sent settlement request command and the received settlement request response command do not match, it is determined that the settlement request response command has not been received normally. For example, if the value of the settlement number is different (if the lowest digit of the lowest byte does not match between the settlement request command and the settlement request response command), if the highest digit of the lowest byte is "8", or if the value of the highest byte is not "A1", it is determined that the settlement request response command has not been received normally.
If it is determined that the settlement request response command has been received normally, the process according to this flowchart ends, whereas if it is determined that the command has not been received normally, the process proceeds to step S987.
In step S987, it is determined whether the settlement number in the received settlement request response command is the same as that in the sent settlement request command, and whether it is a settlement request response command corresponding to VL signal off (whether the most significant digit of the lower byte of the settlement request response command is "8H"). If the determination in step S987 is "Yes," this corresponds to the case where the VL signal is off, and the processing according to this flowchart is terminated without executing error processing. On the other hand, if the determination in step S987 is "No," the processing proceeds to step S988, where an error display is executed. The processing according to this flowchart is then terminated.

FIG. 113 is a flowchart showing the bet processing in step S936 of FIG.
In step S991, the main control CPU 510 checks the medal count limit. This process determines whether the current number of bets has reached the limit ("3" in this embodiment). If the medal count is at the limit, betting is not possible, so this flowchart is terminated. If it is determined that the medal count is not at the limit (betting is possible), the process proceeds to step S993. In step S993, processing is performed to light up the bet request indicator lamp. This processing is processing to store data (for example, "1" when lit) that determines whether or not to light up the bet request indicator lamp in the main control RWM 512. Note that the actual lighting of the bet request indicator lamp is performed by LED display control in the main control interrupt processing (step S1052 in FIG. 115).
In the next step S994, the main control CPU 510 determines whether the bet switch 40 has been operated, and if it determines that it has been operated, proceeds to step S995, and if it determines that it has not been operated, terminates processing according to this flowchart.
In step S995, the main control CPU 510 determines whether the 1-bet switch 40a has been operated. If it is determined that the 1-bet switch 40a has been operated, the process proceeds to step S996, and if it is determined that the 1-bet switch 40a has not been operated (the 3-bet switch 40b has been operated), the process proceeds to step S997.
In step S996, the main control CPU 510 sets the requested bet number to "1." In the next step S997, the main control CPU 510 sets the maximum requested bet number to "3" in response to the operation of the 3-bet switch 40b. The bet number for the bet request command is set by the processing of steps S996 and S997.

In the next step S998, a bet request command is set. This processing sets "A0" in the D register. Then, in the next step S975, processing is performed to wait for a bet request response command from the medal count control described above.
Next, the main control CPU 510 proceeds to step S999, where it determines whether the bet request response command has been received normally. If it is determined that the command has been received normally, it proceeds to step S1000, and if it is determined that the command has not been received normally, it ends the processing according to this flowchart.
Here, "normally received" corresponds to the case where the values of the bet request command and the bet request response command match. For example, if the value of the number of bets is different (if the lowest digit of the lowest byte does not match between the bet request command and the bet request response command), if the highest digit of the lowest byte is "8", or if the value of the highest byte is not "A0", it is determined that the bet request response command has not been received normally.

In step S1000, the main control CPU 510 executes the process of adding one medal. This process is a process of adding "1" to the value of the bet number data provided in the main control RWM 512. Next, proceeding to step S1001, the main control CPU 510 determines whether or not the bet processing for the requested number of medals has been completed. If it is determined that the bet processing has been completed, proceed to step S1002, and if it is determined that the bet processing has not been completed, return to step S1000 and execute the process of adding one medal. Here, when processing one bet, the process of step S1000 is performed once, and when processing three bets, the process of step S1000 is performed three times.
However, since the processes of steps S1000 and S1001 are executed in one go (instantly) without any waiting process, from the player's perspective, the bet number appears to change instantaneously from before the update to after the update. Therefore, the display of the bet number display unit 77 does not change, for example, from "0" to "1" to "2" to "3," but appears to change instantaneously from "0" to "3." This is different from the awarding process described above.
In the next step S1002, the main control CPU 510 performs processing to send a bet command to the sub-control CPU 85. Note that the processing to send a bet command to the sub-control CPU 85 refers to storing the command in the command buffer (this also applies when executed in other steps). In the subsequent main control interrupt processing, the bet command is sent to the sub-control CPU 85 by processing in step S1049 of Figure 115. Then, the processing according to this flowchart ends.

FIG. 114 is a flowchart showing the assignment process in step S945 of FIG.
114, in step S1021, the main control CPU 510 transmits a grant command to the sub-control CPU 85 (stores it in the command buffer). The "grant command" here refers to the total number of grants in the current game, and for example, when a 10-coin minor combination is won, the grant command is a command that includes "10" as the number of grants.
In the next step S1022, the main control CPU 510 determines whether or not gaming media have been awarded in the current game. If it is determined that gaming media have been awarded, the process proceeds to step S1023, and if it is determined that gaming media have not been awarded, the process according to this flowchart ends.
In step S1023, the main control CPU 510 executes an interrupt wait process. This process waits until the main control interrupt process is executed once. In the next step S1024, the main control CPU 510 determines whether the grant time has elapsed. Here, the "grant time" is stored in the main control RWM 512 in step S1025. In the process of step S1024, the main control CPU 510 subtracts "1" from the grant time for each main control interrupt process and determines whether the grant time after subtraction has become "0." In step S1024, the main control CPU 510 loops until the grant time after subtraction becomes "0." Then, when the main control CPU 510 determines that the grant time after subtraction has become "0," it determines that the grant time has elapsed and proceeds to step S1025.

In step S1025, the main control CPU 510 saves the grant time of "54" (stores it in the main control RWM 512). After this, when the process returns to step S1024, the grant time is subtracted by "1" from "54" for each main control interrupt process, so that it becomes "0" after approximately "60.345" ms has elapsed. In other words, it is determined in step S1024 that the grant time has elapsed approximately every "60" ms. In other words, the grant (addition) process of "1" is executed for the number of acquisitions. This point is as explained in FIG. 106 (2).
In the next step S1026, the main control CPU 510 sets an award request command. This process sets "A2" in the D register. Then, the process proceeds to step S975, where the main control CPU 510 waits for reception of an award request response command from the medal count control CPU 520.

In step S1027, the main control CPU 510 determines whether the grant response request command was received normally. Here, "normally received" corresponds to a case where the values of the grant request command and the grant request response command match. For example, if the value of the grant number ("1" in the seventh embodiment) is different (the lowest digit of the lowest byte does not match between the grant request command and the grant request response command), if the highest digit of the lowest byte is "8," or if the value of the highest byte is not "A2," it is determined that the grant request response command was not received normally.
If it is determined in step S1027 that the signal has been received normally, the process proceeds to step S1028, and if it is determined that the signal has not been received normally, the process according to this flowchart ends.
In step S1028, the main control CPU 510 adds "1" to the number of wins. This process adds "1" to the number of wins stored in the main control RWM 512. In the next step S1029, "1" is subtracted from the number of wins in the special game state. This process subtracts "1" from the number of wins in the special game state stored in the main control RWM 512.
In the next step S1030, "1" is subtracted from the award number data. This process subtracts "1" from the award number data stored in the main control RWM 512.
The "number of wins" in step S1028 is data to be displayed on the payout number display unit 78.

Furthermore, the "number of medals won in the special game state" in step S1029 corresponds to the remaining number of medals that can be won in the special game. Therefore, in step S1029, the subtraction is performed only when the current game is in the special game state.
Furthermore, the "award number data" in step S1030 is data used in the award process. Although not shown in Figure 114, the number of awards for the current game (for example, "10" when a 10-coin small win is won) is set before the award number data is subtracted.
In step S1031, the main control CPU 510 determines whether the award number data stored in the main control RWM 512 has become "0." If it determines that the award number data is not "0," the process returns to step S1024, and if it determines that the award number data is "0," the process proceeds to step S1032.
In step S1032, the main control CPU 510 sends an assignment command (a command indicating that assignment has been completed) to the sub-control CPU 85 (stores it in the command buffer), and then ends the processing according to this flowchart.
As described above, in the case of the awarding process, the process of adding "1" to the number of wins is executed every time the predetermined awarding time elapses, so the display in the payout number display unit 78 appears to the player to be counting up. In this respect, it differs from the update process of the bet number display unit 77 during the betting process described above.
Specifically, for example, if the display (total number of medals) in the medal count display unit 121 at that time is "10,000," the display in the medal count display unit 121 at the time of three bets is updated all at once from "10,000" to "9,997." Similarly, when three bets are settled, the display in the medal count display unit 121 is updated all at once from "10,000" to "10,003."
In contrast, when adding the awarded number "3", the display of the medal count display unit 121 is updated stepwise from "10000" to "10001" to "10002" to "10003".

Figure 115 is a flowchart showing main control interrupt processing by the main control CPU 510.
First, in step S1041, the main control CPU 510 performs initial processing. This processing includes prohibiting duplicate interrupts, etc. Next, the processing proceeds to step S1042, where the main control CPU 510 receives commands from the medal count control CPU 520 and saves them in the main control RWM 512. Examples of commands received here include request response commands (bet request response command, settlement request response command, and award request response command) and commands (described below) indicating whether the output conditions for the test count signal are met.
Next, the process proceeds to step S1043, where the main control CPU 510 determines whether a power-off signal has been detected. When a power-off occurs, the voltage drops, and a predetermined voltage condition is satisfied, a power-off signal is input to the main control CPU 510. If it is determined that a power-off signal has not been detected, the process proceeds to step S1045, and if it is determined that a power-off signal has been detected, the process proceeds to step S1044, where power-off processing is executed. If the process proceeds to step S1044 and power-off processing is executed, processing from step S1045 onwards is not executed.
In addition, since the process of receiving a command from the medal count control CPU 520 and saving it in the main control RWM 512 is executed before the power-off signal is detected (step S1043), even if a power-off signal is detected during this interrupt processing, it is possible to correctly store the command from the medal count control CPU 520 during this interrupt processing.

In step S1045, the main control CPU 510 performs input port reading processing. This processing reads whether the bet switch 40, settlement switch 46, start switch 41, stop switch 42, etc. have been operated, switch signals, and input signals from various sensors, generates data based on the input port (level data, rising edge data, falling edge data), and stores the data in the main control RWM 512.
For example, when operation of the bet switch 40 is detected, the rising data of the bet switch 40 becomes "1", and a "Yes" determination is made in step S994 of Fig. 113. Also, when operation of the adjustment switch 46 is detected, the rising data of the adjustment switch 46 becomes "1", and a "Yes" determination is made in step S971 of Fig. 111. Furthermore, when operation of the start switch 41 is detected, the rising data of the start switch 41 becomes "1", and a "Yes" determination is made in step S938 of Fig. 108. Similarly, when operation of the stop switch 42 is detected, the rising data of the stop switch 42 becomes "1", and a "Yes" determination is made in step S941 of Fig. 108.

Next, the process proceeds to step S1046, where the main control CPU 510 controls the drive of the reels 31. This control is performed on a reel-by-reel basis (left, center, right), and includes stop, constant speed, acceleration, deceleration, deceleration start, and standby depending on the operating state of each reel 31. When the drive control of the reels 31 is completed, the process proceeds to step S1047, where the main control CPU 510 performs port output processing. This processing includes, for example, excitation output of the (reel) motor 32.
In the next step S1048, the main control CPU 510 transmits a main control status command to the medal count control CPU 520. The "main control status command" transmitted here includes whether or not a complete operation has been performed, whether or not an instruction monitor display has been performed, whether or not the front door has been opened, etc. The main control status command transmitted here is received in step S1062 of FIG.
In the next step S1049, the main control CPU 510 transmits a main control command to the sub-control CPU 85. The "main control command" transmitted here is a command stored (saved) in the command buffer, and one of the commands includes a VL signal (on/off). Furthermore, if no command is stored in the command buffer, information stored in the main control RWM 512 indicating whether or not to prompt counting (for example, information indicating that the total number of medals is equal to or greater than "15,000" and equal to or less than the upper limit of "16,368" for game progress) is transmitted at the timing of this step S1049. Here, the main control RWM 512 stores "information regarding whether or not to prompt counting." The information regarding whether or not to prompt counting is "0" when the total number of medals is less than "15,000" (indicating that counting is not prompted), and is "1" (indicating that counting is prompted) when the total number of medals is equal to or greater than "15,000" and equal to or less than the upper limit of "16,368" for game progress. When the sub-control CPU 85 receives a command corresponding to "prompt counting," it displays an image such as "Please count" on the image display device 23 and outputs a predetermined sound. Even if the total number of medals exceeds the upper limit "16,368" for game progress, the notification prompting counting continues as long as the counting process is not being executed.

In the next step S1050, the main control CPU 510 performs timer measurement. This process subtracts the time set in the main control process. Specifically, this process subtracts the minimum play time for one game.
In the next step S1051, the main control CPU 510 performs an irrecoverable error check. An example of an irrecoverable error check is a setting value error check. The main control RWM 512 stores the current setting value, and determines whether the setting value is within a normal value range. If it is determined that the value is not normal, the process proceeds to an irrecoverable error process (an error that cannot be recovered from without turning off the power and resetting the setting value), which is not shown in FIG. 115.
In the next step S1052, the main control CPU 510 performs LED display control. This process involves dynamically lighting up the setting value display means 73, the bet number display unit 77, the payout number display unit 78, and the above-mentioned status display LEDs according to the status of the gaming machine 10.
In the next step S1053, the main control CPU 510 performs test signal management. This process writes (sets) data to the output port based on the data stored in the main control RWM 512, thereby transmitting a test signal to the testing machine to determine whether the gaming machine 10 is properly designed in accordance with the law. Then, the process according to this flowchart ends.

Here, the following process is executed so that the total number of medals does not exceed the upper limit value that can be stored, "16383".
First, if the total number of medals managed by the medal count control CPU 520 is less than 15,000, the medal count control CPU 520 sends a command to the main control CPU 510 to the effect that the output conditions for the test counting signal are not met (step S1146 in Figure 121).On the other hand, if the total number of medals is 15,000 or more and is less than the upper limit of 16,368 for which the game can progress, the medal count control CPU 520 sends a command to the main control CPU 510 to the effect that the output conditions for the test counting signal are met.
Here, when the total number of medals is between "15,000" and "16,368", it is required to output the test count signal for "3,500" ms.
If the total number of medals is between "15,000" and "16,368," the sub-control board 80 will issue a notification urging the player to count (the notification will be issued, but the player can continue playing). Furthermore, if the total number of medals is "15,000" or more, the medal lending process will be disabled, and an abnormality will be reported in the lending receipt result response.
If the total number of medals exceeds the upper limit of "16,368" for game progress, the game will be disabled due to an error in the main control (the bet switch 40, settlement switch 46, and start switch 41 cannot be accepted).

Although not shown in Figure 115, the main control CPU 510 reads information from the main control RWM 512 regarding whether the test count signal output conditions are met for each main control interrupt process. If "1" (test count signal output conditions met) is stored, the initial output time value of "2418" (number of main control interrupts) (approximately "2700.24" ms) is stored in the main control RWM 512. This process is executed for each main control interrupt process, so if a value that meets the test count signal output conditions is stored in the next main control interrupt process, the initial output time value of "2418" is stored again. Therefore, the test count signal will be output for approximately "2700.24" ms after the value ("0") becomes a value that does not meet the test count signal output conditions.

FIG. 116 is a flowchart showing the main processing of the medal count control CPU 520 (medal count control main processing).
In step S1061, the medal count control CPU 520 prohibits the medal count control interrupt process (FIG. 121). Next, in step S1062, the medal count control CPU 520 executes main control command reception processing. This processing is processing for receiving various commands transmitted from the main control CPU 510.

The main control command reception process in step S1062 may include, for example, the following commands:
1) A command indicating that the main control CPU 510 has started (when the power is turned on)
2) Main control chip ID number, main control chip manufacturer code, main control chip product code (commands required to generate gaming machine installation information) (when power is turned on)
3) A command for specifying the type of role ratio monitor 113 display (whether it is the "7U" type or the "7P" type) (when the power is turned on)
4) The above-mentioned request commands (bet request command, settlement request command, grant request command)
5) Start switch reception command 6) Main control status (operation status of game devices, etc.) command 7) Main control status 1, main control status 2, gaming machine error status, fraud detection status 1 (gaming machine fraud 1), fraud detection status 2 (gaming machine fraud 2), fraud detection status 3 (gaming machine fraud 3) (commands required to generate hall control and fraud monitoring information)
8) End game command, etc.
It should be noted that even if the medal count control CPU 520 receives these commands from the main control CPU 510, it does not send a response command to the main control CPU 510. If there is no risk that the player will lose medals (incur a loss), not sending a response command simplifies program processing and reduces program capacity.
However, this is not limiting, and it is also possible to configure the device so that when an important command is received, a response command is sent regardless of whether or not the player is at risk of losing medals.

In the next step S1063, the medal count control CPU 520 determines whether the power interruption flag is on. If it is determined that the power interruption flag is not on, the process proceeds to step S1064, and if it is determined that the power interruption flag is on, the process proceeds to step S1065.
In step S1064, the medal count control CPU 520 permits medal count control interrupt processing, and then returns to step S1061.
On the other hand, when the process proceeds to step S1065, the medal count control CPU 520 executes a power cutoff process. In the power cutoff process, a checksum is calculated, and then a power cutoff waiting process (loop) is executed.
By permitting the medal count control interrupt process in this way, when the process proceeds to the power-off process in step S1065, it is possible to prevent the medal count control interrupt process by the medal count control CPU 520 from being executed (the medal count control interrupt process remains disabled in step S1061). Therefore, since the process proceeds to the power-off process in step S1065 and the medal count control interrupt process is not executed when the checksum is being calculated, etc., it is possible to prevent the data in the medal count control RWM 522 from being updated while the checksum is being calculated.

Figure 117 is a flowchart showing the main control command reception process in step S1062 of Figure 116. In this example, reception of a bet request command, a settlement request command, and a grant request command will be described, and reception processes for other main control commands will be omitted.
First, in step S1071, the medal count control CPU 520 stores the upper byte data of the received command in register D. Next, proceeding to step S1072, the medal count control CPU 520 stores the lower byte data of the received command in register A. Furthermore, in the next step S1073, the medal count control CPU 520 stores the lower byte data of the received command in register E.
Through the above steps S1071 to S1073,
D register value: upper byte data of the received command A register value: lower byte data of the received command E register value: lower byte data of the received command
In the next step S1074, the medal count control CPU 520 determines whether the D register value is "A0H". The D register value being "A0H" is the case for a bet request command. When it is determined that the D register value is "A0H", the process proceeds to step S1077, where a bet request command reception process (processing in FIG. 118, which will be described later) is executed. On the other hand, when it is determined in step S1074 that the D register value is not "A0H", the process proceeds to step S1075. In step S1075, the medal count control CPU 520 determines whether the D register value is "A1H". The D register value being "A1H" is the case for a settlement request command. When it is determined that the D register value is "A1H", the process proceeds to step S1078, where a settlement request command reception process (processing in FIG. 119, which will be described later) is executed. On the other hand, when it is determined in step S1075 that the D register value is not "A1H", the process proceeds to step S1076. In step S1076, the medal count control CPU 520 determines whether the D register value is "A2H." The D register value being "A2H" is the case for an award request command. If it is determined that the D register value is "A2H," the process proceeds to step S1079, where the award request command reception process (the process in FIG. 120, described later) is executed. On the other hand, if it is determined in step S1076 that the D register value is not "A2H," the process proceeds to another main control command reception process.

As described above, other main control command reception processes include:
1) Command indicating that the main control CPU 510 has started up 2) Main control chip ID number, main control chip manufacturer code, main control chip product code 3) Role ratio type command for specifying the type of role ratio monitor 113 display 4) Start switch reception command 5) Main control status command (operation status of role devices, etc.) 6) Main control status 1, main control status 2, gaming machine error status, fraud detection status 1 (gaming machine fraud 1), fraud detection status 2 (gaming machine fraud 2), fraud detection status 3 (gaming machine fraud 3)
8) Game end command, etc., but the description thereof will be omitted in the seventh embodiment.

118 is a flowchart showing the bet request command receiving process in step S1077 of FIG. 117. As shown in the figure, at the time of step S1077,
D register value = A0
The A register value is equal to the number of bet requests, and the E register value is equal to the number of bet requests.
In step S1081, the medal count control CPU 520 determines whether the A register value is 0. If it is determined that the A register value is 0, the process according to this flowchart ends, and if it is determined that the A register value is not 0, the process proceeds to step S1082.
In step S1082, it is determined whether the A register value is less than "4". If it is determined that it is less than "4", the process proceeds to step S1083, and if it is determined that it is not less than "4", the process according to this flowchart ends. Here, if the A register value is not less than "4", the bet request command is an abnormal value, so the process of sending a bet request response command, etc. is not executed.
In step S1083, the medal count control CPU 520 determines whether the VL value is "0" (VL signal is on). Note that the medal count control CPU 520 and the lending unit 200 are always electrically connected, and the current VL signal state is stored in the medal count control RWM 522, so this value is read and used for determination.
If it is determined that the VL value is "0", the process proceeds to step S1084, and if it is determined that the VL value is not "0" (the VL signal is off), the process proceeds to step S1090.

In step S1084, the medal count control CPU 520 stores the total medal count at this point (corresponding to the "medal count" stored in the medal count control RWM 522 in FIG. 91) in the HL register.
Next, proceeding to step S1085, the medal count control CPU 520 subtracts the A register value, which is the number of requested bets, from the HL register value, which is the total number of medals. Then, in the next step S1086, the medal count control CPU 520 determines whether the total number of medals (before the bet request number has been subtracted) is less than the bet request number. This is because betting is not possible if the total number of medals before the subtraction is less than the bet request number. In this step S1085, as a result of subtracting the bet request number (A register value) from the total number of medals (HL register value), it is determined whether the carry flag (CY) is "1." If the carry flag is not "1" (the total number of medals before the subtraction is equal to or greater than the bet request number), proceed to step S1087. If the carry flag is "1" (the total number of medals before the subtraction is less than the bet request number), proceed to step S1090.

In step S1087, the medal count control CPU 520 updates the value of the total medal count stored in the medal count control RWM 522 (to the value after subtracting the requested bet number). In the next step S1088, the medal count control CPU 520 updates the number of bets (corresponding to the "number of inserted medals" stored in the medal count control RWM 522 in FIG. 91) to be sent as the hall control/fraud monitoring information in the gaming machine information notification. Then, the process proceeds to step S1089. After the hall control/fraud monitoring information in the gaming machine information notification has been sent, the value of this number of bets is cleared.
On the other hand, if the VL value is not "0" (OFF) in step S1083, or if the answer is "Yes" in step S1086 (if the total number of medals before subtraction is less than the requested number of bets), the process proceeds to step S1090, where the medal count control CPU 520 sets "1" to the D7 bit of the E register value. Then, the process proceeds to step S1089.
In step S1089, the medal count control CPU 520 transmits a bet request response command in which the D register value is the upper byte and the E register value is the lower byte to the main control CPU 510. Then, the processing according to this flowchart ends.
Here, the D register value is "A0H" as described above. Also, the E register value is "0xH" or "8xH" when the number of received bet requests is "x". Therefore, the bet request response command is "A00xH" or "A08xH".

Fig. 119 is a flowchart showing the settlement request command reception process in step S1078 of Fig. 117. As shown in the figure, at the time of step S1078,
D register value = A1
The A register value is the number of settlement requests, and the E register value is the number of settlement requests.
In step S1101, the medal count control CPU 520 determines whether the A register value is 0. If it is determined that the A register value is 0, the process according to this flowchart ends, and if it is determined that the A register value is not 0, the process proceeds to step S1102.
In step S1102, it is determined whether the A register value is less than "4." If it is determined that it is less than "4," the process proceeds to step S1103; if it is determined that it is not less than "4," the process according to this flowchart ends. Here, if the A register value is not less than "4," the settlement number in the settlement request command is an abnormal value, so the process of sending the settlement request response command, etc. is not executed.
In step S1103, the medal count control CPU 520 determines whether the VL value is "0" (the VL signal is on). If it determines that the VL value is "0," the process proceeds to step S1104, and if it determines that the VL value is not "0" (the VL signal is off), the process proceeds to step S1110.

In step S1104, the medal count control CPU 520 stores the total medal count at this point in time (corresponding to the "medal count" stored in the medal count control RWM 522 in Figure 91) in the HL register. Next, proceeding to step S1105, the HL register value, which is the total medal count, is added to the A register value, which is the settlement request count. Then, in the next step S1106, it is determined whether the total medal count after adding the settlement request count exceeds the storable upper limit of "16,383". If it is determined that the total medal count after adding the settlement request count does not exceed the storable upper limit of "16,383", proceed to step S1107; if it is determined that the total medal count after adding the settlement request count exceeds the storable upper limit of "16,383", proceed to step S1110.

In step S1107, the medal count control CPU 520 updates the value of the total medal count stored in the medal count control RWM 522 (to the value after adding the settlement request number). In the next step S1108, the medal count control CPU 520 updates (sets to "0") the number of bets to be sent as the hall control/fraud monitoring information in the gaming machine information notification (corresponding to the "number of inserted medals" stored in the medal count control RWM 522 in FIG. 91). Then, the process proceeds to step S1109. After sending the hall control/fraud monitoring information in the gaming machine information notification, the value of this number of bets is cleared.
On the other hand, if the VL value is not "0" (OFF) in step S1103, or if the answer is "No" in step S1106 (if the total medal count plus the requested settlement count exceeds the medal count upper limit), the process proceeds to step S1109, where the medal count control CPU 520 sets "1" to the D7 bit of the E register value. Then, the process proceeds to step S1109.
In step S1109, the medal count control CPU 520 transmits a settlement request response command to the main control CPU 510, with the D register value as the upper byte and the E register value as the lower byte, and then ends the processing according to this flowchart.
Here, the D register value is "A1H" as described above. Also, the E register value is "0xH" or "8xH" when the number of settlement requests received is "x". Therefore, the settlement request response command is "A10xH" or "A18xH".

Fig. 120 is a flowchart showing the grant request command reception process in step S1079 of Fig. 117. As shown in the figure, at the time of step S1079,
D register value = A2
The A register value is the number of requests to grant, and the E register value is the number of requests to grant.
In step S1121, the medal count control CPU 520 determines whether the A register value is 0. If it is determined that the A register value is 0, the process according to this flowchart ends, and if it is determined that the A register value is not 0, the process proceeds to step S1122.
In step S1122, it is determined whether the A register value is less than "2." If it is determined that it is less than "2," the process proceeds to step S1123; if it is determined that it is not less than "2," the process according to this flowchart ends. Here, if the A register value is not less than "2," the number of grants of the grant request command is an abnormal value, so the process of transmitting the grant request response command, etc. is not executed.

In step S1123, the medal count control CPU 520 stores the total medal count at this point in time (corresponding to the "medal count" stored in the medal count control RWM 522 in Figure 91) in the HL register. Next, proceed to step S1124, where the HL register value, which is the total medal count, is added by the A register value ("1"), which is the number of award requests. Then, in the next step S1125, it determines whether the total medal count after adding the number of award requests exceeds the storable upper limit of "16,383". If it determines that the total medal count after adding the number of award requests does not exceed the storable upper limit of "16,383", proceed to step S1126; if it determines that the total medal count after adding the number of award requests will exceed the storable upper limit of "16,383", proceed to step S1129.

In step S1126, the medal count control CPU 520 updates the value of the total medal count stored in the medal count control RWM 522 (to the value after adding the number of medals requested to be awarded). In the next step S1127, the medal count control CPU 520 updates the number of medals awarded (corresponding to the "number of medals paid out" stored in the medal count control RWM 522 in FIG. 91) to be sent as the hall control/fraud monitoring information in the gaming machine information notification. Then, the process proceeds to step S1128. After sending the hall control/fraud monitoring information in the gaming machine information notification, the value of this number of medals awarded is cleared.
On the other hand, in step S1125, adding the requested number of medals to the total number of medals equals or exceeds the upper medal count limit, so when the process proceeds to step S1129, the medal count control CPU 520 sets "1" to the D7 bit of the E register value. Then, the process proceeds to step S1128.
In step S1128, the medal count control CPU 520 transmits an award request response command with the D register value as the upper byte and the E register value as the lower byte to the main control CPU 510. Then, the processing according to this flowchart ends.
Here, the D register value is "A2H" as described above. Also, the E register value is "01H" or "81H." Therefore, the settlement request response command is "A201H" or "A281H."

Figure 121 is a flowchart showing medal count control interrupt processing by the medal count control CPU 520. The medal count control interrupt processing is similar to the processing shown in Figure 93 in the sixth embodiment, but will be explained again. Also, Figure 121 omits the setting processing of the main control start-up wait timer M1 and the update processing of the post-connection confirmation wait timer M2 in the sixth embodiment.
In the seventh embodiment, the cycle of the medal count control interrupt process is "1" ms, just like the main control interrupt process.
When the medal count control interrupt process is started in step S1140, the medal count control CPU 520 determines in step S1141 whether or not a power interruption signal has been detected. If it is determined that a power interruption signal has not been detected, the process proceeds to step S1143, and if it is determined that a power interruption signal has been detected, the process proceeds to step S1142. In step S1142, the power interruption flag is turned on, and the process proceeds to step S1143.
In step S1143, the medal count control CPU 520 checks the input port. This process checks the signal of the count switch 47, the VL signal indicating that the main control CPU 510 has started up, the signal of the total medal count clear switch 112, etc.
Next, the process proceeds to step S1144, where the medal count control CPU 520 determines whether or not the VL signal is on. If the VL signal is on, the process proceeds to step S244, and if it is determined that the VL signal is not on, the process proceeds to step S1145.
Here, if a VL signal (DC 18V signal) is supplied from the rental unit 200 to the gaming machine 10, the VL signal is determined to be on, and it is determined that the rental unit 200 and the gaming machine 10 are connected normally.

If it is determined in step S1144 that the VL signal is not on and the process proceeds to step S1145, the medal count control CPU 520 turns the connected flag off ("0"). Then, the process proceeds to step S244. In step S244, the medal count control CPU 520 executes gaming machine information management. This process is the process shown in FIG. 94, and is a process of transmitting a gaming machine information notification to the rental unit 200.
Here, when a gaming machine information notification is sent by the gaming machine information management, a counting notification is sent within "100" ms from that point, as shown in Figure 32, and the lending unit 200 sends a lending notification to the gaming machine 10 within "170" ms from receiving the counting notification. When the gaming machine 10 receives the lending notification, it sends a lending receipt result response to the lending unit 200. Therefore, unless a gaming machine information notification can be executed, medals will not be loaned out even if the lending switch 202 of the lending unit 200 is operated.
When the connected flag is turned off in step S1145, the process proceeds to step S244, whereupon the determination is made as "No" in step S261 of Fig. 94, and the transmission process of the gaming machine information notification is not executed. In other words, unless the connected flag is on, the gaming machine information notification is not transmitted from the gaming machine 10 to the rental unit 200.

In step S1146, the medal count control CPU 520 transmits a medal count control command to the main control CPU 510. The medal count control command transmitted here may be, for example, information about the VL signal (whether it is on or off), information about the total medal count (specifically, information that the total medal count is equal to or greater than "15,000" and equal to or less than "16,368", or information that the total medal count exceeds "16,368", etc.).
Note that since VL signal information is sent from the medal count control CPU 520 to the main control CPU 510, when the VL signal is off, the operation of the bet switch 40, settlement switch 46, and start switch 41 is ignored. Therefore, even if the bet switch 40 is operated while the VL signal is off, the main control CPU 510 does not send a bet request command (FIG. 103 (7)). Similarly, even if the settlement switch 46 is operated while the VL signal is off, the main control CPU 510 does not send a settlement request command.
Furthermore, information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, so if the total number of medals is "0", for example, the main control CPU 510 will not send a bet request command even if the bet switch 40 is operated (Figure 103 (8). Similarly, if the total number of medals is "2" or less, the main control CPU 510 will not send a bet request command even if the 3 bet switch 40b is operated. The medal count control command sent in step S1146 is received at the timing of step S1042 in Figure 115.

Next, the process proceeds to step S1147, where the medal count control CPU 520 executes display control of the medal count display unit 121. This process is a process for updating the display of the total medal count by the medal count display unit 121 based on medal betting process, settlement process, awarding process, and counting process.
As described above, when the bet switch 40 is operated, the display of the medal count display unit 121 is updated all at once. Similarly, when the settlement switch 46 is operated, the display of the medal count display unit 121 is updated all at once. In contrast, when medals are awarded, the display of the medal count display unit 121 is updated by "1" (sequentially).
In the next step S1148, the medal count control CPU 520 executes a ratio update process (the ratio displayed on the role ratio monitor 113). Here, at the end of one game (when all reels 31 have stopped and, if medals have been awarded, at the end of the awarding process), a game end command is transmitted from the main control CPU 510 to the medal count control CPU 520 (received in step S1062 in FIG. 116). When this game end command is received, the ratio update flag is turned on. Then, if the ratio update flag is on in step S1148, a ratio update process is performed. This ratio update process corresponds to the ratio update process related to the role ratio monitor 113 (the process shown in FIGS. 80 to 83). After the process of step S1148, the ratio update flag is turned off.
Next, the process proceeds to step S1149, where the medal count control CPU 520 executes display control of the role ratio monitor 113. This process is a process in which four interrupts of the medal count control interrupt process constitute one cycle, and the four-digit LED of the role ratio monitor 113 is dynamically lit.
Next, the process proceeds to step S1150, where the medal count control CPU 520 performs timer management. This process updates the timer that manages the signal output time. Then, the process according to this flowchart ends.

Next, an example of an image display when a communication error occurs while the VL signal is off will be described.
FIG. 122 shows an example of an image displayed by the image display device 23 when the VL signal is turned off, and an example of an image displayed by the image display device 23 when a communication error occurs.
122(a) shows a situation when the VL signal is on and no error has occurred, which is a normal game screen (a game standby screen or a game in progress screen). Under this situation, the output sound from the speaker 22 is normal sound, and the frame lamp (a part of the effect lamp 21, which is a lamp provided on the outer frame of the front of the front mask) is in a normal lighting state.
Under these circumstances, when the VL signal changes from ON to OFF, an image display is displayed, for example, displaying a warning message such as "Please check the connection to the rental unit," as shown in FIG. 122(b). When the VL signal changes to OFF, the image display layer when the VL signal is OFF is displayed in front of the layer of the normal game screen, so that, for example, the normal game screen becomes invisible. Here, the normal game screen may be completely invisible, or the image display shown in FIG. 122(b) may be semi-transparent, so that the normal game screen, which is the layer behind it, can be faintly seen. Alternatively, the image display when the VL signal is OFF may be provided in a portion of the image display area, so that part of the normal game screen is visible in the other image display areas excluding the image display area indicating that the VL signal is OFF. In other words, the visibility of the normal game screen may be reduced, or the normal game screen may become difficult to see.
Furthermore, when the VL signal is off, since no error (abnormality) has occurred in the gaming machine 10, the output sound and the illumination of the frame lamp remain in the normal game screen state. However, this is not limited to this, and in addition to the output sound up to that point, or by interrupting the output sound up to that point, the above-mentioned voice message "Please check the connection with the rental unit" may be output from the speaker 22. Furthermore, the illumination mode of the frame lamp may be set to an illumination mode specific to when the VL signal is off.

It should be noted that when the VL signal is turned off after a game has started (during a game), the game can continue until the end. In this case, for example, if a rare combination (such as a rare combination that requires careful timing) is won in the game and an effect image corresponding to the rare combination is selected, an image may be displayed with the VL signal turned off while the effect image is visible to the player. On the other hand, an image may be displayed with the VL signal turned off so that the effect image is not visible.
Furthermore, for example, after the start of AT play, if the VL signal is turned off after an image showing an advantageous (appropriate) operation mode (e.g., a push order) of the stop switch 42 is displayed, an image showing the VL signal being off may be displayed so that the push order image is recognizable to the player. On the other hand, an image showing the VL signal being off may be displayed so that the push order image is not visible. Even if the visibility of the push order image is reduced or becomes difficult to see, the instruction monitor notifies the player of the advantageous operation mode of the stop switch 42, so the player can operate the stop switch 42 in the advantageous operation mode by looking at the instruction monitor. Therefore, no disadvantage is caused to the player.

122(c) shows an example of a case where a communication error occurs under the condition (b) where the VL signal is off. For example, the main control CPU 510 sends a medal count request command to the medal count control CPU 520 but does not receive a medal count response command within a predetermined period, or receives a medal count response command with a different number of medals to be awarded than the medal count request command sent. In such cases, error processing is executed, and the sub-control CPU 85 also issues an error notification.
In such a situation, in addition to announcing that the VL signal is off, an announcement is made that a communication error has occurred. Furthermore, the speaker 22 outputs an alarm sound (error sound, abnormality sound) and the frame lamp flashes. This allows the outside world to be notified that a communication error has occurred.
If a communication error occurs while an audible notification indicating that the VL signal is off is being output, an audible alarm for the communication error may be output in addition to the audible notification indicating that the VL signal is off. In this case, it is preferable to make the volume of the audible alarm for the communication error louder than that of the audible notification indicating that the VL signal is off.
Alternatively, if a communication error occurs while an audible notification indicating that the VL signal is off is being output, the audible notification indicating that the VL signal is off may be stopped and an audible warning of the communication error may be output instead. In this case, it is preferable to output the audible warning of the communication error at a volume louder than the audible notification indicating that the VL signal is off that has been output up until that point.

Also, in the situation of FIG. 122(c), if the communication error is resolved (cleared) by operating the reset switch 14 but the VL signal is still off, the notification mode returns to that of FIG. 122(b).
On the other hand, in the situation shown in Figure 122(c), if the communication error continues but the VL signal changes from OFF to ON, the notification mode shown in Figure 122(d) is entered, and the notification for when the VL signal is OFF is terminated. However, since the communication error continues, the alarm sound continues to be output and the frame lamp continues to flash. Then, if the communication error is resolved by operating the reset switch 14 in the situation shown in Figure 122(d), the state returns to that shown in Figure (a).
As described above, when a communication error or the like occurs while a notification indicating that the VL signal is off is being executed, a notification of the communication error or the like is executed in addition to, or in preference to, the notification indicating that the VL signal is off. As a result, even if someone attempts to cheat by using the notification indicating that the VL signal is off, an error notification is executed when an error is detected, so that such cheating can be suppressed.

FIG. 123 is a diagram showing an example of an image display when the complete function is activated while the VL signal is off.
123(a) is a diagram showing the image display state of the image display device 23 when the complete function is activated and the VL signal is off. As shown in the figure, the image layer when the complete function is activated is configured to be located behind the image layer when the VL signal is off. Therefore, even if the complete function is activated when the VL signal is off, the image indicating that the complete function has been activated is not visible, and only the image when the VL signal is off is visible.
When the VL signal changes from off to on, the image displayed when the VL signal is off ends, and the image displayed when the complete function is activated becomes visible. Figure 123(b) shows the image displayed at this time. The sound played when the VL signal is off also ends, becoming silent, for example. The frame lamp is also configured to turn off when the complete function is activated.
When the VL signal changes from off to on, the state may automatically transition from the state in Figure 123(a) to the state in (b), or the state may transition from the state in Figure 123(a) to the state in (b) by a predetermined operation by a hall staff member.
In this way, when the complete function is activated while the VL signal is off, only the image when the VL signal is off is visible, so that the player is not notified of the activation of the complete function, thereby preventing the player from operating the counting switch 47 based on the notification of the activation of the complete function.
Note that when the VL signal is off, acceptance of operation of the operation switch is disabled. Therefore, even if the counting switch 47 is operated when the VL signal is off, the counting process is not executed. Therefore, even if the counting switch 47 is operated when the VL signal is off, the counting process is not executed, which prevents the player from mistaking that the gaming machine 10 or the rental unit 200 is malfunctioning.

Although the seventh embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and various modifications such as those described below are possible.
(1) The values (2-byte values) of the bet request command, bet request response command, settlement request command, settlement request response command, award request command, and award request response command shown in FIG. 100 are examples and are not limited to these. For example, the values of the number of bets, settlement number, and award number may be set in the upper byte. Also, the value when VL is off is set to "1" in the D7 bit of the lower byte, but this is not limited to this, and a predetermined bit in the upper byte may be set to "1", for example.

(2) As shown in Figure 101 (3) and other figures, when a request command is sent from the main control CPU 510 to the medal count control CPU 520, if the number of bets, the number of settlements, or the number of medals awarded are abnormal values, a request response command is not sent. However, this is not limited to this, and a request response command indicating that a request command with an abnormal value for the number of bets, the number of settlements, or the number of medals awarded has been received may be sent to the main control CPU 510. In this case, for example, the value of the lower byte of the request response command may be set to "FFH."
(3) In Figure 103 (8), information on the total number of medals does not have to be sent from the medal count control CPU 520 to the main control CPU 510. In this case, even if the number of bet requests exceeds the total number of medals, the main control CPU 510 may not determine the total number of medals, but may send a bet request command to the medal count control CPU 520. Then, if the medal count control CPU 520 determines that a bet is not possible, it may send a bet request response command to the main control CPU 510 indicating that a bet is not possible (or that the requested number of bets exceeds the total number of medals).

(4) As shown in Figure 105 (5), there are cases where the main control CPU 510 sends a settlement request command of "A103H", but the medal count control CPU 520 receives a settlement request command of "A101H", and the medal count control CPU 520 determines that the settlement request command of "A101H" is normal. In this case, the medal count control CPU 520 executes a process to add "1" to the total medal count.
In this case, the subsequent processing may involve, for example, the main control CPU 510 receiving the settlement request response command "A101H" and determining that an error has occurred, sending a command to the medal count control CPU 520 indicating that the received settlement request response command is an error (a command to cancel the update of the total medal count).As a result, the medal count control CPU 520 subtracts "1" from the total medal count and executes processing to restore the total medal count to the number before settlement.

(5) In FIG. 109, when a replay is stopped, the on/off state of the VL signal is determined, and when the VL signal is off, an automatic bet is not placed. However, this is not limited to this. After a replay is stopped, an automatic bet may be placed even if the VL signal is off, the replay indicator lamp may be turned on, and an automatic bet process may be executed. In this case, the process of step S952 in FIG. 109 may be omitted. Note that even if an automatic bet is placed, if the VL signal is off, acceptance of operation of the start switch 41 is invalid, and therefore a replay cannot be started (the game cannot be advanced by operating the start switch 41). In this way, by placing an automatic bet even if the VL signal is off when a replay is stopped, it is possible to prevent a player from mistakenly believing that they have been disadvantaged (that an automatic bet has not been placed) because the VL signal is off.
(6) On the other hand, as shown in Figure 106 (1), after the start switch 41 is operated, the awarding process is executed even if the VL signal is turned off during the game. However, this is not limited to this, and the awarding process may not be executed when the VL signal is off at the start of the awarding process of the game medium, and the awarding process may start after the VL signal is turned on.
However, if the VL signal is turned off after the start switch 41 is operated, it is preferable to enable the operation of the stop switch 42 and stop the reels 31 based on the operation of the stop switch 42. This is to avoid causing inconvenience to the player.

(7) In step S938 of FIG. 108, when a rising edge signal of the start switch 412 is detected, the process proceeds to step S939 and game play is started. Here, when a rising edge signal of the start switch 41 is detected, the state of the VL signal is checked (data related to the VL signal stored in the main control RWM 512 is read), and if data indicating that the VL signal is on is stored, the process proceeds to step S939, and if data indicating that the VL signal is off is stored, the process returns to step S933. In this case, when the process proceeds to step S933, the process proceeds to step S966 in FIG. 110, which performs loop processing. This makes it possible to prevent game play from starting (progressing) if the VL signal is off at the moment the rising edge signal of the start switch 41 is detected.
(8) In the bet waiting process in Fig. 110, the explanation of the process when the setting key is detected to be on even though the front door is not open is omitted. If the setting key is detected to be on even though the front door is not open, there is a high possibility of cheating, so error processing (including error notification) may be performed.
(9) The number of medals to be awarded per one medal request command is set to "1." If the number of medals to be awarded is "x," the medal request command for the number of medals to be awarded "1" is sent "x" times. However, this is not limited to this, and a medal request command including information on the number of medals to be awarded "x" may be sent once. This simplifies the processing. However, even in this case, it is preferable that the display of the medal count display unit 121 be updated sequentially using a standby process or the like. For example, if the number of medals to be awarded is "10," the count is increased as follows: "00100" → "00101" → "00102" → ... → "00109" → "00110."

(10) As shown in Fig. 100, the response command sent from the medal count control CPU 520 to the main control CPU 510, if normally received, is the same as the request command received from the main control CPU 510. However, this is not limited to this, and the value of the response command may be any value as long as the main control CPU 510 can recognize that it has been received normally.
for example,
a) If the data is received normally and is acceptable, a response command with the value of the lower byte set to "00" is sent.
b) If the data is received normally and cannot be accepted, a response command with the value of the lower byte set to "01" is sent.
c) When a request command containing an abnormal value (for example, a value outside the range) is received, a response command with the value of the lower byte set to "02" is sent.
These include:
(11) When a response command (bet, settlement, award) is not received within a specified period, as in the example of Figure 101 (3), or when an abnormal response command (bet, settlement, award request command) is received, as in the example of Figure 102 (6), an error command is sent to the sub-control CPU 83.
In this case, the error command to be sent to the sub-control CPU 85 is:
a) The same command is sent as an error command for betting, settlement, and awarding.
b) Send a bet error command, a settlement error command, and an award error command (different commands), respectively.
The following are some of the reasons:
With the configuration as described in a) above, the number of types of error commands can be reduced to one, which makes it possible to reduce the program capacity and simplify the processing.
On the other hand, if configured as in b) above, when the sub-control CPU 85 issues an error notification, it is possible to notify which error (including the type of error) is occurring, among bet, settlement, or award.
Furthermore, when an error that has occurred is displayed on the main control side (for example, on the payout number display unit 78), there are two methods: one in which the same error number is displayed for all bets, settlements, and awards, and the other in which a different error number is displayed for each bet, settlement, and award.
(12) The seventh embodiment is not limited to being implemented alone, but can be implemented in appropriate combination with at least a part of the first to sixth embodiments.

Eighth Embodiment
The eighth embodiment relates to processing when an error occurs.
In the eighth embodiment, as in the sixth and seventh embodiments, the “game medium” is referred to as a “medal.” However, in the eighth embodiment, the gaming machine 10 is also a medal-less gaming machine (smart gaming machine, smart pachislot), and the game medium is an electronic medal (electronic game medium).
The hardware configuration (block diagram) of the eighth embodiment is the same as that of Fig. 77 (sixth embodiment). In other words, two one-chip microprocessors are mounted on the main control board 50, one of which is a one-chip microprocessor for main control and the other is a one-chip microprocessor for medal count control. The sub-control board 85 is also equipped with one one-chip microprocessor for sub-control (performance control).
Unless otherwise specified, the other configurations are the same as those of the sixth and seventh embodiments. However, this does not mean that the configuration of the eighth embodiment is limited to the same configurations as those of the sixth and seventh embodiments, and other embodiments can be appropriately adopted.

124 is a flowchart showing the main control program start process in the eighth embodiment. When the gaming machine 10 is powered on, the main control CPU 510 executes the main control program start process shown in FIG.
124, when the program starts in step S2701, the main control CPU 510 acquires power interruption recovery data from the main control RWM 512 and stores it in a register (e.g., register A).Then, the process proceeds to the next step, S2706.
Here, the main control CPU 510 detects a power outage in the main control interrupt processing of Figure 127 described below (step S1043), and when a power outage is detected, it creates power outage recovery data (also called backup data or checksum data) in the power outage processing of step S1044 and stores it in the main control RWM 512.
Then, the next time the power is turned on, the main control CPU 510 reads the power interruption recovery data stored in the main control RWM 512 and determines whether the power interruption recovery data is a normal value. If the power is turned off normally, correct power interruption recovery data is created and stored in the main control RWM 512. Therefore, the next time the power is turned on, the power interruption recovery data is acquired from the main control RWM 512 and is determined to be a normal value.
On the other hand, if the power failure is abnormal, the power failure recovery data stored may be abnormal, or may not be stored at all. In this case, the next time the power is turned on, the power failure recovery data will be determined to be abnormal.

In step S2706, the main control CPU 510 determines whether the door switch signal is on. In the gaming machine 10 of the eighth embodiment, when the front door is open, the door switch is on and the door switch signal is on. If it is determined that the door switch signal is on (the front door is open), the process proceeds to the next step S2707. On the other hand, if it is determined that the door switch signal is off (the front door is closed), the process proceeds to step S2715.
In step S2707, the main control CPU 510 determines whether the setting key switch signal is on. If it is determined that the setting key switch signal is on, the process proceeds to step S2711. On the other hand, if it is determined that the setting key switch signal is off, the process proceeds to step S2708.

When proceeding to step S2708, the main control CPU 510 determines whether there is a power failure recovery abnormality in the main control. In step S2708, the main control CPU 510 determines whether the power failure recovery data acquired in step S2705 is an abnormal value. If it is determined that the power failure recovery data is not an abnormal value, it is determined that the power failure recovery in the main control is normal, and the process proceeds to step S2709. On the other hand, if it is determined that the power failure recovery data is an abnormal value, it is determined that the power failure recovery in the main control is abnormal, and the process proceeds to unrecoverable error processing in step S2801. Here, the unrecoverable error processing program is stored in the usage area of the main control ROM 511 (first program).

When the process proceeds to the unrecoverable error process in step S2801, the main control interrupt process is not executed thereafter. An unrecoverable error is a serious error that does not normally occur, so in order to prevent the execution of processes based on abnormal data (updating the main control RWM 512 data based on the input signal from the input port 51, sending a control command to the sub-control board 80, and control based on the signal output from the output port 52 based on the data from the main control RWM 512), the main control interrupt process is not executed when the unrecoverable error process is executed.
When an irrecoverable error occurs, the specified display will display that an irrecoverable error has occurred and the system will wait until the power is turned off.When an irrecoverable error occurs, the system will turn the power off, then on, and go through the setting change mode to be able to recover.
When an unrecoverable error occurs, the power is turned off, and the power is turned on in a state in which the mode is changed to the setting change mode, the process proceeds to step S2731, where an initialization process is executed.

In step S2709, the main control CPU 510 sets reset determination data. Specifically, it stores a predetermined value in a predetermined register. Then, the process proceeds to the next step, S2710.
In step S2710, the main control CPU 510 determines whether the reset switch signal is on. In this embodiment, the reset switch 14 is integrated with the RWM clear switch, and when the reset switch 14 (RWM clear switch) is on, the reset switch signal is turned on, and the process proceeds to step S2713. On the other hand, when the reset switch (RWM clear switch) 14 is off, the process proceeds to power restoration processing in step S2721.
The process proceeds to step S2721, where the power restoration process is started, and the main control interrupt process (FIG. 127) is started at a predetermined timing in the power restoration process. Thereafter, the process proceeds to step S930, where the main control main process (FIG. 108) is started.
On the other hand, when proceeding from step S2707 to step S2711, the main control CPU 510 sets the initialization range of the main control RWM 512 for when power failure recovery is abnormal. In this embodiment, when power failure recovery is abnormal, the entire range including the used area and outside the used area, including the setting value data of the addresses of the main control RWM 512, is set as the initialization range. Then, proceeding to the next step S2712.

In step S2712, the main control CPU 510 determines whether the power recovery from a power outage of the main control is abnormal. This process is the same as step S2708. If it is determined that the power recovery from a power outage of the main control is not abnormal, data for determining that the setting has changed is stored in a specified register, and the process proceeds to the next step S2713. On the other hand, if it is determined in step S2712 that the power recovery from a power outage of the main control is abnormal, the process proceeds to initialization processing in step S2731. Similar to step S2711, this initialization processing initializes the entire range of the used area and outside the used area, including the setting value data of the addresses of the main control RWM 512. After this initialization processing is completed, the process proceeds to step S930 and proceeds to main control main processing. Although not shown in Figure 124, main control interrupt processing is started before proceeding to main control main processing.

In contrast, when proceeding from step S2712 to step S2713, the main control CPU 510 sets the initialization range of the main control RWM 512 for normal power-off recovery. In this embodiment, when the power-off recovery data is normal, the addresses of the main control RWM 512 that store the set value data and data related to the role ratio monitor outside the use area are maintained without being initialized (cleared). Then, proceeding to the next step S2714.
In step S2714, the main control CPU 510 determines whether the setting can be changed. In this embodiment, a setting change disable flag is provided, and when the setting change disable flag is on, it is determined that the setting cannot be changed. After the start switch acceptance process is initiated, the setting is set to be unchangeable while the reels 31 are spinning and during the game end check process, and the setting change disable flag is on during this time. However, these situations do not occur immediately after the power is turned on. It is also possible to allow the setting to be changed at all times without providing a period during which the setting cannot be changed (in other words, without providing a setting change disable flag).
If it is determined in step S2714 that the setting cannot be changed, the process proceeds to step S2715, and if it is determined that the setting can be changed, the process proceeds to step S2731.
In step S2715, the main control CPU 510 determines whether the power recovery from the main control power interruption is abnormal. This process is the same as step S2708. If it is determined that the power recovery from the main control power interruption is abnormal, the process proceeds to step S2801 for unrecoverable error processing. If it is determined that the power recovery from the main control power interruption is normal, the process proceeds to step S2721 for power recovery processing.

In the main control program start process, it is determined whether the power failure recovery data is an abnormal value. However, in addition to this process, it may also be determined whether the main control RWM 512 is abnormal. Specifically, it is determined whether data can be written normally to the main control RWM 512, and if data cannot be written normally, it is determined that the main control RWM 512 is abnormal. If it is determined that the main control RWM 512 is abnormal, it is determined that the main control power failure recovery is abnormal, and the process proceeds to step S2801 to execute unrecoverable error processing. On the other hand, if it is determined that the data is normal, the process proceeds to power recovery processing in step S2721.
The determination of whether the main control RWM 512 is abnormal can also be performed during the main control interrupt process shown in Fig. 127, which will be described later.

Figure 125 is a flowchart showing the "waiting to receive request response from medal count control" processing in each step S975 of Figures 111, 113, and 114 in the eighth embodiment (processing in which request commands (bet, settlement, award) are sent from the main control CPU 510 to the medal count control CPU 520, and request response commands to these request commands are waited for to be received from the medal count control CPU 520).
In step S981, the main control CPU 510 transmits a request command: a settlement request command in the case of settlement processing, a bet request command in the case of betting processing, and an award request command in the case of award processing.
Next, the process proceeds to step S982, where the main control CPU 510 determines whether transmission of the request command has been completed, and if it determines that transmission has been completed, the process proceeds to step S983. In step S983, the process waits for main control interrupt processing. This process waits until the main control interrupt processing has been executed once. In this embodiment, the main control interrupt processing is executed at a cycle of 1.12 ms.
Then, after the main control interrupt processing is executed once, the process proceeds to the next step S1163, where the main control CPU 510 determines whether or not a request response command corresponding to the request command sent in step S981 has been received. If it is determined in step S1163 that a request response command has been received, the process proceeds to step S984; if it is determined that a request response command has not been received, the process proceeds to step S1164, where the main control error display processing described below is executed.

Here, the medal count control main processing (Figure 130) by the medal count control CPU 520, which will be described later, executes a loop processing of less than 1 ms. During this loop processing, request command reception processing is executed in step S1188 of Figure 130, and when a request response command is received, the request response command is sent to the main control CPU 510. Therefore, after sending the request command in step S981, the request response command can be received by waiting for main control interrupt processing in step S983. Furthermore, when the main control CPU 510 receives a request response command, it is configured to store the request response command in the command buffer of the main control RWM 512. Therefore, in step S984, the main control CPU 510 obtains the received request response command from the command buffer. In the next step S985, the command buffer is cleared.

In the next step S986, the main control CPU 510 determines whether the request response command was received normally. Here, "received normally" corresponds to receiving a request response command that is identical to the request command that was sent. If the sent request command and the received request response command do not match, it is determined that the request response command was not received normally. For example, if the sent request command is a settlement request command, the lowest digit of the lowest byte of the settlement request response command is the settlement number. If this value does not match the settlement number of the settlement request command, if the highest digit of the lowest byte is "8" (when the VL signal is off), or if the value of the highest byte (the identification value of the request response command) is not "A1" (if it is not a settlement request response command), it is determined that the settlement request response command was not received normally.

If it is determined that the request response command has been received normally, the process according to this flowchart ends, whereas if it is determined that the request response command has not been received normally, the process proceeds to step S987.
In step S987, it is determined whether the value of the upper byte (the identification value of the request response command) and the lower digit of the lower byte (the value related to the number of medals) of the received request response command are normal values and whether the request response command corresponds to the VL signal being off. In the eighth embodiment, as in the seventh embodiment, if the upper digit of the lower byte of the request response command is "8", it is determined that the VL signal is off. If the determination in step S987 is "Yes", this corresponds to the case where the VL signal is off, and the processing according to this flowchart is terminated without executing the main control error display processing. On the other hand, if the determination in step S987 is "No", proceed to step S1164 and execute the main control error display processing. The processing according to this flowchart is then terminated.
As described above, if a request response command is not received or if the received request response command has an abnormal value, the process proceeds to step S1164, where a main control error display process is performed.

FIG. 126 is a flowchart showing the main control error display processing in step S1164 of FIG.
First, in step S1165, the main control CPU 510 generates a number corresponding to the error that has occurred. Next, in step S1166, the main control CPU 510 stores the error number generated in step S1165 in a predetermined storage area of the main control RWM 512.
Next, the process proceeds to step S1167, where the main control CPU 510 transmits an error display command to the sub-control CPU 85. Upon receiving the error display command, the sub-control CPU 85 executes image display, audio output, etc. corresponding to the error display command.
In the next step S1168, the main control CPU 510 executes processing for turning off the game start indicator lamp. This processing updates the data in a predetermined memory area of the main control RWM 512, which stores data indicating whether the game start indicator lamp is on or off, to data corresponding to turning off the lamp.

Next, the process proceeds to step S1169, where the main control CPU 510 determines whether the reset switch signal has been turned on (whether the rising edge signal of the reset switch 14 has become "1"). In the main control interrupt process of FIG. 127, which will be described later, operation of the reset switch 14 is detected in step S1045, and when the turning on of the reset switch 14 is detected here, the rising edge data of the reset switch 14 becomes "1". As a result, a "Yes" determination is made in step S1169.
In step S1169, the main control CPU 510 loops until the reset switch signal is turned on, and when it determines that the reset switch signal is on, it proceeds to step S1170. In step S1170, the main control CPU 510 clears the error number saved in step S1166. Then, the processing according to this flowchart ends.
In this way, when the main control CPU 510 determines that a command communication error with the medal count control CPU 520 has occurred, it displays an error, and ends the error display when the reset switch 14 is operated. In other words, even if a command communication error with the medal count control CPU 520 has occurred, the main control CPU 510 will not interrupt the main control main processing or main control interrupt processing.

Figure 127 is a flowchart showing main control interrupt processing in the eighth embodiment.
In the eighth embodiment, the interrupt period of the main control interrupt process is 1.12 ms. However, this is not the only possible interrupt period. The medal count control interrupt process (see FIG. 132, which will be described later) is executed at a 1 ms interval.
When the main control interrupt process is started, in step S1041, the main control CPU 510 performs initial processing. This processing includes prohibiting duplicate interrupts, etc. Next, in step S1042, the main control CPU 510 receives commands from the medal count control CPU 520 and saves them in the main control RWM 512. Examples of commands received here include request response commands (bet request response commands, settlement request response commands, and award request response commands), test counting commands (commands indicating whether the output conditions for the test counting signal are met), etc.
Next, the process proceeds to step S1043, where the main control CPU 510 determines whether a power-off signal has been detected. When a power-off occurs, the voltage drops, and a predetermined voltage condition is satisfied, a power-off signal is input to the main control CPU 510. If it is determined that a power-off signal has not been detected, the process proceeds to step S1045, and if it is determined that a power-off signal has been detected, the process proceeds to step S1044, where power-off processing is executed. If the process proceeds to step S1044 and power-off processing is executed, processing from step S1045 onwards is not executed.
In addition, since the process of receiving a command from the medal count control CPU 520 and saving it in the main control RWM 512 is executed before the power-off signal is detected (step S1043), even if a power-off signal is detected during this main control interrupt process, it is possible to correctly store the command from the medal count control CPU 520 during this main control interrupt process.

In step S1045, the main control CPU 510 performs input port reading processing. This processing reads whether or not operation switches such as the bet switch 40, settlement switch 46, start switch 41, and stop switch 42, and switches such as the reset switch 14, as well as switch signals and input signals from various sensors, and generates data (level data, rising edge data, falling edge data) based on the input signals and stores them in the main control RWM 512.
For example, when operation of the bet switch 40 is detected, the rising data of the bet switch 40 becomes "1", and a "Yes" determination is made in step S994 of Fig. 113. Also, when operation of the adjustment switch 46 is detected, the rising data of the adjustment switch 46 becomes "1", and a "Yes" determination is made in step S971 of Fig. 111. Furthermore, when operation of the start switch 41 is detected, the rising data of the start switch 41 becomes "1", and a "Yes" determination is made in step S938 of Fig. 108. Similarly, when operation of the stop switch 42 is detected, the rising data of the stop switch 42 becomes "1", and a "Yes" determination is made in step S941 of Fig. 108.
Furthermore, when the operation of the reset switch 14 is detected, the rising data of the reset switch 14 becomes "1", and "Yes" is determined in step S1169 of FIG.

Next, the process proceeds to step S1046, where the main control CPU 510 controls the drive of the reels 31. This control is performed on a reel-by-reel basis (left, center, right), and includes stop, constant speed, acceleration, deceleration, deceleration start, and standby depending on the operating state of each reel 31. When the drive control of the reels 31 is completed, the process proceeds to step S1047, where the main control CPU 510 performs port output processing. This processing includes, for example, excitation output of the (reel) motor 32.
In the next step S1048, the main control CPU 510 transmits a main control status command to the medal count control CPU 520. The "main control status command" transmitted here includes commands such as whether or not a complete operation has been performed, whether or not an instruction monitor display has been performed, and whether or not the front door has been opened. The main control status command transmitted here is received in step S1188 of FIG. 130 (medal count control main processing), which will be described later.

In the next step S1049, the main control CPU 510 transmits a main control command to the sub-control CPU 85. The "main control command" transmitted here is a command stored (saved) in the command buffer, and one of the commands includes the VL signal (on/off). Furthermore, if no command is stored in the command buffer, information stored in the main control RWM 512 regarding whether or not to prompt counting (for example, information indicating that the total number of medals is equal to or greater than 15,000 and equal to or less than the upper limit of 16,368 for game progress) is transmitted at the timing of this step S1049. Here, the main control RWM 512 stores "information regarding whether or not to prompt counting." The information regarding whether or not to prompt counting is "0" when the total number of medals is less than 15,000 (indicating that counting is not prompted), and is "1" (indicating that counting is prompted) when the total number of medals is equal to or greater than 15,000 and equal to or less than the upper limit of 16,368 for game progress. When the sub-control CPU 85 receives a command equivalent to "prompt counting," it displays an image such as "Please count" on the image display device 23 and outputs a predetermined sound. Note that even if the total number of medals exceeds the upper limit of "16,368" for game progress, the notification prompting counting will continue as long as the counting process is not being executed.

In the next step S1050, the main control CPU 510 performs a timer value update process. This process involves subtracting the time set in the main control process. Specifically, this process includes subtracting the minimum play time for one game, the timer value set in step S1161 of FIG. 125, and the like.
In the next step S1172, the main control CPU 510 checks whether there is a setting value error. Here, the main control CPU 510 reads the setting value data stored in the main control RWM 512 and proceeds to step S1173. In step S1173, it is determined whether there is a setting value error. In this process, if the read setting value data is within the range of "0 (setting 1)" to "5 (setting 6)," it is determined that the setting value is normal, and if it is any other value, it is determined that there is a setting value error. If it is determined that there is a setting value error, it proceeds to step S1176, and if it is determined that there is no setting value error, it proceeds to step S1174.
In step S1174, the main control CPU 510 checks for an internal random number error. In this embodiment, a flag is provided that turns on when an error occurs in the internal random number, and it is determined whether this flag is on. Specifically, for example, when an abnormality in the clock frequency of the random number used for role selection (such as slow random number updates) is detected, the error flag is turned on. Next, the main control CPU 510 proceeds to step S1175, where it determines whether an internal random number error has occurred (whether the error flag is on). If it is determined that an internal random number error has not occurred, the process proceeds to step S1052, and if it is determined that an internal random number error has occurred, the process proceeds to step S1176.

When the process proceeds from step S1173 or S1175 to step S1176, the main control CPU 510 executes unrecoverable error processing 2 and ends processing according to this flowchart.
Here, the program for steps S1172 to S1175 is stored outside the usage area of main control ROM 511. For this reason, the program for unrecoverable error processing 2 is stored outside the usage area of main control ROM 511, and when the process proceeds from step S1173 or S1175 to step S1176, unrecoverable error processing 2, which is a program (second program) outside the usage area of main control ROM 511, is executed.
When proceeding to unrecoverable error processing 2, similar to step S2801 in Fig. 124, the occurrence of an unrecoverable error is displayed (for example, an error number is displayed on a predetermined display), and the system waits until the power is turned off. When proceeding to unrecoverable error processing 2, similar to unrecoverable error processing, after the power is turned off, recovery becomes possible by turning the power on, which involves transitioning to setting change mode.
That is, both the unrecoverable error processing and the unrecoverable error processing 2 are configured so that the main control main processing cannot be started unless the power is turned off and the setting change mode is passed through.
Furthermore, when transitioning to main control interrupt processing, duplicate interrupts are prohibited in step S1041, so after transitioning to unrecoverable error processing 2, main control interrupt processing will not be executed unless the power is turned off and the system is restarted via setting change mode.

When the process proceeds from step S1175 to step S1052, the main control CPU 510 performs LED display control. This process performs dynamic lighting of the setting value display means 73, the bet number display unit 77, the payout number display unit 78, and the above-mentioned status display LEDs according to the status of the gaming machine 10.
In the next step S1053, the main control CPU 510 performs test signal management. This process writes (sets) data to the output port 52 based on the data stored in the main control RWM 512, thereby transmitting a test signal to the testing machine to determine whether the gaming machine 10 is properly designed in accordance with the law. Then, the process according to this flowchart ends.

127, when it is determined that a setting value error or a built-in random number error has occurred, the process proceeds to unrecoverable error processing 2. Furthermore, in addition to these errors, it may also be possible to determine whether the main control RWM 512 is normal, and when it is determined that the main control RWM 512 is abnormal, the process proceeds to unrecoverable error processing 2.
Specifically, for example, when the determination in step S1175 is "No," the main control CPU 510 determines whether the main control RWM 512 is normal. Whether the main control RWM 512 is normal can be determined, for example, by determining whether data can be written normally to the main control RWM 512. If it is determined that the main control RWM 512 is normal, the process proceeds to step S1052, and if it is determined that the main control RWM 512 is abnormal, the process proceeds to step S1176.

As described above, when the main control CPU 510 detects a main control power failure recovery abnormality (abnormality in the power failure recovery data), an abnormality in the set value, an abnormality in the built-in random number, or an abnormality in the main control RWM 512, it is considered an irrecoverable error. When an irrecoverable error occurs, the main control main processing and main control interrupt processing are stopped.
In contrast, when the main control CPU 510 detects a communication error with the medal count control CPU 520, it treats this as an error that can be cleared by operating the reset switch 14 (in other words, a recoverable error), and executes the main control main processing and main control interrupt processing even while the error is occurring.

128 is a flowchart showing the start of the medal count control program in the eighth embodiment. When the power of the gaming machine 10 is turned on, the medal count control CPU 520 executes the medal count control program start process shown in FIG.
Here, when the gaming machine 10 is powered on, both the main control CPU 510 and the medal count control CPU 520 start up, but in the eighth embodiment, the medal count control CPU 520 is configured to start up first.
When the main control CPU 510 and the medal count control CPU 520 are started, if the main control CPU 510 proceeds to the unrecoverable error processing in step S2801 in FIG. 124, the main control CPU 510 will enter a state of waiting for power to be cut off. However, even under such circumstances, if no error occurs on the medal count control side, the medal count control CPU 520 will start up normally, start medal count control interrupt processing in step S1186, and proceed to medal count control main processing in step S1187.

In FIG. 128, when the medal count control program start process is executed, in step S1181, the medal count control CPU 520 acquires power interruption recovery data from the medal count control RWM 522 and stores it in a register (for example, register A).
Here, when the medal count control CPU 520 detects a power outage, it executes power outage processing in step S1065 of Figure 130 described below, and in this power outage processing it creates power outage recovery data (also called backup data or checksum data) and stores it in the medal count control RWM 522.
Then, when the power is turned on next time, the medal count control CPU 520 acquires the power interruption recovery data stored in the medal count control RWM 522 .

Next, proceeding to step S1182, the medal count control CPU 520 determines whether the power interruption recovery of the medal count control is abnormal. The medal count control CPU 520 determines whether the power interruption recovery data of the medal count control acquired in step S1181 is an abnormal value. If it is determined that the power interruption recovery data is an abnormal value, it is determined that the power interruption recovery of the medal count control is abnormal, and proceeds to step S1183. On the other hand, if it is determined that the power interruption recovery data is a normal value, it is determined that the power interruption recovery of the medal count control is normal, and proceeds to step S1185.
In step S1183, the medal count control CPU 520 executes medal count control error display processing. This processing is the processing shown in FIG. 129, which will be described later.
After step S1183, the process proceeds to step S1184, where the medal count control CPU 520 executes initialization processing for the medal count control RWM 522 when a power outage recovery abnormality occurs in the medal count control. This initialization processing is processing for initializing predetermined storage areas (for example, all areas) including the storage area for transmitting gaming machine information notifications (FIGS. 90 and 91).
In contrast, if it is determined in step S1182 that the power supply recovery from the medal count control is normal, and the process proceeds to step S1185, the medal count control CPU 520 executes initialization processing for normal power supply recovery. This initialization processing is processing for initializing the memory area for transmitting gaming machine information notifications (FIGS. 90 and 91).
After steps S1184 and S1185, the process proceeds to step S1186, where power restoration processing is executed. At a predetermined timing during this power restoration processing, medal count control interrupt processing (see FIG. 132, which will be described later) is started. The process then proceeds to step S1187, where the medal count control main processing (see FIG. 130, which will be described later) is executed.

In step S1182, it is determined whether the power interruption recovery data of the medal count control is an abnormal value, but in addition to this process, it may also be determined whether the medal count control RWM 522 is abnormal. Specifically, it is determined whether data can be written normally to the medal count control RWM 522, and if data cannot be written normally, it is determined that the medal count control RWM 522 is abnormal. If it is determined that the medal count control RWM 522 is abnormal, it is determined that there is an abnormality in the power recovery of the medal count control, and the process proceeds to step S1183, whereas if it is determined that the medal count control RWM 522 is normal, it is determined that the power recovery of the medal count control is normal, and the process proceeds to step S1185.
The determination of whether or not the medal count control RWM 522 is abnormal can also be made during the medal count control main process in Fig. 130, which will be described later, or during the medal count control interrupt process in Fig. 132. This point will be described later.

FIG. 129 is a flowchart showing the medal count control error display processing in step S1183 of FIG.
First, in step S291, the medal count control CPU 520 generates a number corresponding to the error that has occurred. Next, in step S292, the medal count control CPU 520 stores the error number generated in step S291 in a predetermined storage area of the medal count control RWM 522.
Next, the process proceeds to step S293, where the medal count control CPU 520 transmits an error display command to the sub-control CPU 85. Upon receiving the error display command, the sub-control CPU 85 executes image display, audio output, etc. corresponding to the error display command.
In the next step S294, the medal count control CPU 520 determines whether or not the reset switch signal has been turned on.

In step S294, the medal count control CPU 520 loops until the reset switch signal is turned on, and when it determines that the reset switch signal is on, proceeds to step S295. In step S295, the medal count control CPU 520 clears the error number saved in step S292. Then, the processing according to this flowchart ends.
Therefore, after the power is turned on, if a power outage recovery abnormality in the medal count control is detected during the medal count control program start process, the medal count control error display process of Figure 129 will be performed, and the medal count control program start process will stop until the reset switch 14 is operated.

In the main control program start process (FIG. 124) described above, the main control CPU 510 is configured to transition to unrecoverable error processing when it detects a power outage recovery abnormality in the main control. If the process transitions to unrecoverable error processing, the power must be turned off and the system must transition to setting change mode before normal operation can be restored.
In contrast, in the medal count control program start processing, when the medal count control CPU 520 detects a power outage recovery abnormality in the medal count control, it transitions to medal count control error display processing, waits for the reset switch 14 to be operated, and when the reset switch 14 is operated, initializes the medal count control RWM 522 and returns.
As a result, when the power is turned on, if no power interruption recovery abnormality is detected in the main control and only a power interruption recovery abnormality is detected in the medal count control, the medal count control can be quickly restored by simply operating the reset switch 14 without having to turn the power on/off, and the machine can transition to a game standby state (a state in which game can be started).

In addition, in the examples of Figures 128 and 129, when the medal count control program start processing is executed and a power outage recovery abnormality in the medal count control is detected, the medal count control CPU 520 will not transition to the power recovery processing unless the reset switch 14 is operated, and therefore the medal count control interrupt processing is not started.
However, the present invention is not limited to this, and the following processing can also be performed.
In the first method, when a power interruption recovery abnormality in medal count control is detected in step S1182 of Fig. 128, a power interruption recovery abnormality flag is set and this flag is turned on. However, thereafter, the process proceeds to step S1187 to start the medal count control main process. Furthermore, medal count control interrupt process is also started before the medal count control main process is started.
Then, if a reset switch signal is detected during the medal count control main processing and the power interruption recovery abnormality flag is "1", initialization processing of the medal count control RWM522 is executed in step S1184 of FIG.
Furthermore, while the power interruption recovery abnormality flag is on, a display indicating this may be displayed on a predetermined display. Furthermore, when the reset switch signal is detected and the initialization process proceeds, a display indicating that the initialization process is in progress may be displayed on a predetermined display.
Furthermore, as a second method, when a power interruption recovery abnormality in the medal count control is detected in step S1182 of Fig. 128, the process proceeds to step S1184 without waiting for the operation of the reset switch 14, and initialization processing of the medal count control RWM 522 is executed. In this case, the medal count control CPU 520 may display on a predetermined display device a message indicating that a power interruption recovery abnormality in the medal count control has been detected and that initialization processing is currently being executed.

FIG. 130 is a flowchart showing the main loop processing (main processing for controlling the number of medals) of the medal count control CPU 520.
In step S1061, the medal count control CPU 520 prohibits the medal count control interrupt process (FIG. 132, which will be described later). Next, in step S1188, the medal count control CPU 520 executes main control command reception process. This process receives various commands transmitted from the main control CPU 510, and is the process shown in FIG. 131, which will be described later.

The main control command received in step S1188 is, for example,
1) A command indicating that the main control CPU 510 has started (when the power is turned on)
2) Main control chip ID number, main control chip manufacturer code, main control chip product code (command required to generate gaming machine installation information) (when power is turned on)
3) A command for specifying the type of role ratio monitor 113 display (whether it is the "7U" type or the "7P" type) (when the power is turned on)
4) Request commands (bet request command, settlement request command, grant request command)
5) Start switch reception command 6) Main control status 1, main control status 2, gaming machine error status, gaming machine fraud 1, gaming machine fraud 2, gaming machine fraud 3 (commands necessary to generate hall control and fraud monitoring information. See FIG. 91.)
7) End game command, etc.
The above commands are merely examples and are not limited to these commands.

Here, for the request command 4) among the above commands, the medal count control CPU 520 sends a request response command (bet request response command, settlement request response command, or award request response command) to the main control CPU 510 after receiving it.
Furthermore, even if the medal count control CPU 520 receives a command other than 4) from the main control CPU 510, it will not send a response command corresponding to the received command to the main control CPU 510.

Next, the process proceeds to step S1189, where the medal count control CPU 520 determines whether the error flag is on. Here, in the main control command reception process of step S1188 described above, if the communication confirmation command from the main control CPU 510 is not received within a predetermined time, the error flag is set to on.
If the medal count control CPU 520 determines in step S1189 that the error flag is on, it proceeds to step S1190, and if it determines that the error flag is not on, it proceeds to step S1063.
In step S1190, the medal count control CPU 520 determines whether or not the reset switch signal is on (whether or not the reset switch 14 has been operated). If it is determined that the reset switch signal is on, the process proceeds to step S1191, and if it is determined that the reset switch signal is not on, the process proceeds to step S1163.
In step S1191, the medal count control CPU 520 executes error display end processing. This processing is processing to turn off the error flag stored in the medal count control RWM 522 and to transmit an error display end command to the sub-control CPU 85. Then, the process proceeds to step S1063.

In step S1063, the medal count control CPU 520 determines whether the power interruption flag is on. If it is determined that the power interruption flag is not on, the process proceeds to step S1064, and if it is determined that the power interruption flag is on, the process proceeds to step S1065.
In step S1064, the medal count control CPU 520 permits medal count control interrupt processing, and then returns to step S1061.
On the other hand, when the process proceeds to step S1065, the medal count control CPU 520 executes power cutoff processing. In the power cutoff processing, a checksum is calculated, and power cut recovery data (backup data, checksum data) is stored in the medal count control RWM 522, and then a power cutoff waiting processing (loop) is executed.
By permitting the medal count control interrupt process in this way, when the process proceeds to the power-off process in step S1065, it is possible to prevent the medal count control interrupt process by the medal count control CPU 520 from being executed (the medal count control interrupt process remains disabled in step S1061). Therefore, since the process proceeds to the power-off process in step S1065 and the medal count control interrupt process is not executed when the checksum is being calculated, etc., it is possible to prevent the data in the medal count control RWM 522 from being updated while the checksum is being calculated.
Furthermore, even if a command reception error or the like occurs and the error flag is turned on, the progress of the medal count control main process is not interrupted. Therefore, the medal count control CPU 520 can execute the main control command reception process in step S1188 without interrupting the main process. The loop process between steps S1061 to S1064 takes less than 1 ms.

In addition, although not shown in the example of Figure 130, the medal count control main processing may determine whether the medal count control RWM 522 is abnormal. Specifically, it determines whether data can be written normally to the medal count control RWM 522, and if data cannot be written normally, it determines that the medal count control RWM 522 is abnormal. If it is determined that the medal count control RWM 522 is abnormal, an RWM error is displayed and operation of the reset switch 14 is awaited, and if the reset switch 14 is operated, initialization processing of the medal count control RWM 522 (the same processing as step S1184 in Figure 128) is executed.

FIG. 131 is a flowchart showing the main control command receiving process in step S1188 of FIG.
First, in step S1071, the medal count control CPU 520 stores the upper byte data of the received command in register D. Next, proceeding to step S1072, the medal count control CPU 520 stores the lower byte data of the received command in register A. Furthermore, in the next step S1073, the medal count control CPU 520 stores the lower byte data of the received command in register E.
Through the above steps S1071 to S1073,
D register value: upper byte data of the received command A register value: lower byte data of the received command E register value: lower byte data of the received command
In the next step S1074, the medal count control CPU 520 determines whether the D register value is "A0H". The D register value being "A0H" is the case for a bet request command. When it is determined that the D register value is "A0H", the process proceeds to step S1077, where the bet request command reception process (processing of FIG. 118) is executed. On the other hand, when it is determined in step S1074 that the D register value is not "A0H", the process proceeds to step S1075. In step S1075, the medal count control CPU 520 determines whether the D register value is "A1H". The D register value being "A1H" is the case for a settlement request command. When it is determined that the D register value is "A1H", the process proceeds to step S1078, where the settlement request command reception process (processing of FIG. 119) is executed. On the other hand, when it is determined in step S1075 that the D register value is not "A1H", the process proceeds to step S1076.
In step S1076, the medal count control CPU 520 determines whether the D register value is "A2H." The D register value being "A2H" is the case for an award request command. If it is determined that the D register value is "A2H," the process proceeds to step S1079, where the award request command reception process (processing in FIG. 120) is executed. On the other hand, if it is determined in step S1076 that the D register value is not "A2H," the process proceeds to step S1201.

In step S1201, the medal count control CPU 520 executes a reception process for other main control commands.
Other main control commands include, as mentioned above:
1) A command indicating that the main control CPU 510 has started (when the power is turned on)
2) Main control chip ID number, main control chip manufacturer code, main control chip product code (command required to generate gaming machine installation information) (when power is turned on)
3) A command for specifying the type of role ratio monitor 113 display (whether it is the "7U" type or the "7P" type) (when the power is turned on)
4) Request commands (bet request command, settlement request command, grant request command)
5) Start switch reception command 6) Main control status 1, main control status 2, gaming machine error status, gaming machine fraud 1, gaming machine fraud 2, gaming machine fraud 3 (commands necessary to generate hall control and fraud monitoring information. See FIG. 91.)
7) End game command, etc.
Here, a chip manufacturer code is stored in advance (at the time of shipping from the factory) in the medal count control ROM 521. Meanwhile, the main control ROM 511 also stores the above-mentioned chip manufacturer code.
Then, when the power is turned on, the main control CPU 510 reads the chip manufacturer code stored in the main control ROM 511 and transmits the code data to the medal count control CPU 520. When the medal count control CPU 520 receives the code data, it compares it with the chip manufacturer code stored in the medal count control ROM 521 and determines whether the chip manufacturer codes are the same. If it determines that they are not the same, it determines that an "invalid count error" (an error that should invalidate the counting process), which will be described later, has occurred. If an invalid count error occurs, for example, a count invalid flag is set and the flag is turned on.

Next, the process proceeds to step S1202, where the medal count control CPU 520 determines whether or not there is an unreceived main control command.
If it is determined in step S1202 that there is an unreceived main control command, the process proceeds to step S1203, and if it is determined that there is no unreceived main control command, the process according to this flowchart ends.
In step S1203, the medal count control CPU 520 executes error display start processing. This processing is, for example, processing to store an error number corresponding to an unreceived main control command in a predetermined storage area of the medal count control RWM 522, turn on an error flag, and send a command to start error display to the sub-control CPU 85. Then, the processing according to this flowchart ends.
Here, when the error number is stored in a predetermined storage area of the medal count control RWM 522, an error message corresponding to the error number is displayed on the display device controlled by the medal count control CPU 520. Also, an error message corresponding to the error number is displayed on the image display device 23.

In this way, the medal count control CPU 520 detects a command communication error with the main control through the main control command reception process. Since the main control command reception process is executed as one process (step S1188) of the medal count control main process (FIG. 130), the command communication error can be detected in less than 1 ms (more precisely, within one loop time of steps S1061 to S1064 in FIG. 130).
In response to this, the main control CPU 510 receives the request response command in step S1042 in the main control interrupt process (Fig. 127) which is executed at a cycle of "1.12" ms. Then, in the request response command reception waiting process in Fig. 125, if it determines that the request response command cannot be received normally, it executes main control error display process.
From the above, the time (less than 1 ms, hereinafter referred to as "t1") for the medal count control CPU 520 to detect a command communication error (with the main control CPU 510) is shorter (t1 < t2) than the time (1.12 ms, which is the period of the main control interrupt processing, hereinafter referred to as "t2") for the main control CPU 510 to detect a command communication error (with the medal count control CPU 520).
This means that if a communication error occurs between the main control CPU 510 and the medal count control CPU 520, the medal count control CPU 520 can detect the communication error earlier than the period of the main control interrupt processing by the main control CPU 510.

132 is a flowchart showing medal count control interrupt processing by the medal count control CPU 520. The interrupt period of the medal count control interrupt processing is "1" ms in this embodiment, although it is not limited to this.
First, in step S1141, the medal count control CPU 520 determines whether or not a power interruption signal has been detected. If it determines that a power interruption signal has not been detected, the process proceeds to step S1211, and if it determines that a power interruption signal has been detected, the process proceeds to step S1142. In step S1142, the power interruption flag is turned on, and the process proceeds to step S1211.
In step S1211, the medal count control CPU 520 checks the input port. This process checks the signal of the count switch 47, the VL signal indicating that the main control CPU 510 has started up, the signal of the total medal count clear switch 112, etc.
Next, the process proceeds to step S1144, where the medal count control CPU 520 determines whether or not the VL signal is on. If the VL signal is on, the process proceeds to step S244, and if it is determined that the VL signal is not on, the process proceeds to step S1145.
Here, if a VL signal (DC 18V signal) is supplied from the rental unit 200 to the gaming machine 10, the VL signal is determined to be on, and it is determined that the rental unit 200 and the gaming machine 10 are connected normally.

If it is determined in step S1144 that the VL signal is not on and the process proceeds to step S1145, the medal count control CPU 520 turns the connected flag off ("0"). Then, the process proceeds to step S244. If it is determined that the VL signal is not on and the connected flag is turned off, it is determined that a count invalid error has occurred, and the above-mentioned count invalid flag is turned on.
In step S244, the medal count control CPU 520 executes gaming machine information management. This processing is the processing shown in FIG. 94, and is processing for transmitting a gaming machine information notification to the rental unit 200.
Here, when a gaming machine information notification is sent by the gaming machine information management, a counting notification is sent within 100 ms from that point, as shown in Figure 32, and the lending unit 200 sends a lending notification to the gaming machine 10 within 170 ms from receiving the counting notification. When the gaming machine 10 receives the lending notification, it sends a lending receipt result response to the lending unit 200. Therefore, unless a gaming machine information notification can be executed, medals will not be loaned out even if the lending switch 202 of the lending unit 200 is operated.
When the connected flag is turned off in step S1145, the process proceeds to step S244, whereupon the determination is made as "No" in step S261 of Fig. 94, and the transmission process of the gaming machine information notification is not executed. In other words, unless the connected flag is on, the gaming machine information notification is not transmitted from the gaming machine 10 to the rental unit 200.

In step S1146, the medal count control CPU 520 transmits a medal count control command to the main control CPU 510. The medal count control command transmitted here may be, for example, information about the VL signal (whether it is on or off), information about the total medal count (specifically, information that the total medal count is equal to or greater than "15,000" and equal to or less than "16,368", or information that the total medal count exceeds "16,368", etc.).
Note that since VL signal information is sent from the medal count control CPU 520 to the main control CPU 510, when the VL signal is off, the operation of the bet switch 40, settlement switch 46, and start switch 41 is ignored. Therefore, even if the bet switch 40 is operated while the VL signal is off, the main control CPU 510 does not send a bet request command (FIG. 103 (7)). Similarly, even if the settlement switch 46 is operated while the VL signal is off, the main control CPU 510 does not send a settlement request command.
Furthermore, since information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, if the total number of medals is "0", for example, the main control CPU 510 will not send a bet request command even if the bet switch 40 is operated (FIG. 103 (8)). Similarly, if the total number of medals is "2" or less, the main control CPU 510 will not send a bet request command even if the 3 bet switch 40b is operated. The medal count control command sent in step S1146 is received at the timing of step S1042 in FIG. 127.

Next, the process proceeds to step S1147, where the medal count control CPU 520 executes display control of the medal count display unit 121. This process is a process for updating the display of the total medal count by the medal count display unit 121 based on medal betting process, settlement process, awarding process, and counting process.
As described above, when the bet switch 40 is operated, the display of the medal count display unit 121 is updated all at once. Similarly, when the settlement switch 46 is operated, the display of the medal count display unit 121 is updated all at once. In contrast, when medals are awarded, the display of the medal count display unit 121 is updated by "1" (sequentially).
In the next step S1148, the medal count control CPU 520 executes a ratio update process (the ratio displayed on the role ratio monitor 113). Here, at the end of one game (when all reels 31 have stopped and, if medals have been awarded, at the end of the awarding process), a game end command is transmitted from the main control CPU 510 to the medal count control CPU 520 (received in step S1188 in FIG. 130). When this game end command is received, the ratio update flag is turned on. Then, if the ratio update flag is on in step S1148, a ratio update process is performed. This ratio update process corresponds to the ratio update process related to the role ratio monitor 113 (the process shown in FIGS. 80 to 83). After the process of step S1148, the ratio update flag is turned off.

Next, the process proceeds to step S1149, where the medal count control CPU 520 executes display control of the role ratio monitor 113. This process is a process in which four interrupts of the medal count control interrupt process constitute one cycle, and the four-digit LED of the role ratio monitor 113 is dynamically lit.
Next, the process proceeds to step S1150, where the medal count control CPU 520 performs a timer update process. This process updates (subtracts "1") the timer value stored in a predetermined storage area of the medal count control RWM 522 for each medal count control interrupt process.
In the next step S1212, the medal count control CPU 520 executes counting control. This process is the process shown in Fig. 134, which will be described later, and determines whether or not the timing for transmitting the counting notification has arrived. If it is determined that the timing for transmitting the counting notification has arrived, the medal count control CPU 520 executes the process for transmitting the counting notification.

In the next step S804, the medal count control CPU 520 receives the lending notification. When the counting notification is sent in step S1212, the lending notification is sent from the lending unit 200 within 170 ms as shown in FIG. 32, and the CPU 520 executes the process of receiving the notification.
In the next step S805, the medal count control CPU 520 executes lending control. This process corresponds to any one of the processes shown in Figures 69 to 72, and executes processes such as updating the total number of game media and transmitting a lending receipt result response based on the received lending notification.
Although not shown in the example of Fig. 132, it may be determined whether or not the medal count control RWM 522 is abnormal during medal count control interrupt processing. For example, if data cannot be written normally to the medal count control RWM 522, it is determined that the medal count control RWM 522 is abnormal. When the medal count control CPU 520 determines that the medal count control RWM 522 is abnormal, it turns on a corresponding flag.
On the other hand, in the loop processing of the medal count control main processing, it is determined whether or not a flag corresponding to an abnormality in the medal count control RWM 522 is on, and if it is on, it displays that there is an abnormality in the medal count control RWM 522, waits for the reset switch 14 to be operated, and when the reset switch 14 is operated, executes initialization processing of the medal count control RWM 522 (the same processing as step S1184 in Figure 128).

Fig. 133 is a flowchart showing the processing related to the counting switch 47 during the input port check in step S1211 of Fig. 132. As described above, in the input port check, in addition to the processing related to the counting switch 47, the VL signal, the signal of the total medal count clear switch 112, etc. are checked, but these processings are omitted in Fig. 133.
First, in step S811, the medal count control CPU 520 determines whether or not the count switch signal is on (whether or not the count switch 47 has been operated). If it is determined that the count switch signal is on, the process proceeds to step S1221, and if it is determined that the count switch signal is not on, the process proceeds to step S812.
In step S812, the medal count control CPU 520 determines whether the count execution timer value is "0." The count execution timer is stored in a predetermined storage area of the medal count control RWM 522, and here it is determined whether the value is "0." When the count switch 47 is not operated, the count execution timer value is "0," and when it is determined that the count switch 47 is operated, "1" is added to the count execution timer value. The count execution timer value is then added until it reaches "500."
If it is determined in step S812 that the count execution timer value is "0", the process proceeds to step S815, and if it is determined that the count execution timer value is not "0", the process proceeds to step S813.

In step S813, the medal count control CPU 520 determines whether the count execution flag is "0." Here, the count execution flag is stored in a predetermined storage area of the medal count control RWM 522. The count execution flag is "0" when the count switch 47 is not operated, is "1" when the count switch 47 is pressed for a short time (less than approximately "500" ms), and is "2" when the count switch 47 is pressed for a long time (approximately "500" ms or more).
For this reason, for example, if the counting switch 47 is operated (turned on) and then turned off before the counting execution timer value reaches "500", step S812 will be "No" and step S813 will be "Yes", so the process proceeds to step S814 and the counting execution flag becomes "1". Note that the counting execution timer value is incremented by "1" in step S817 for each medal count control interrupt process (every "1" ms), so after the counting switch 47 is turned on, it will be approximately "500" ms before the counting execution timer value reaches "500".

If it is determined in step S813 that the counting execution flag is not "0", the process proceeds to step S815, and if it is determined that the counting execution flag is "0", the process proceeds to step S814.
In step S814, the medal count control CPU 520 saves "1" in the count execution flag. In other words, when the count switch 47 turns off (from on), the count execution timer value is not "0", and the count execution flag is "0", this means that the count switch 47 has been short-pressed, so the count execution flag is set to "1". Next, the process proceeds to step S815, where the count execution timer is cleared. Then, the process according to this flowchart ends.
When the counting process is executed, the counting execution flag is cleared (step S846 in FIG. 134, which will be described later).

On the other hand, when it is determined in step S811 that the count switch signal is on and the process proceeds to step S1221, the medal count control CPU 520 determines whether or not a count invalid error (an error that should invalidate the counting process) has occurred. Here, if the above-mentioned count invalid flag is on, it is determined that a count invalid error has occurred.
In the eighth embodiment, the invalid counting error is a VL abnormality, a chip manufacturer code error, or a medal count control RWM error.

If it is determined in step S1221 that a counting invalid error has occurred, the process according to this flowchart is terminated, and if it is determined that a counting invalid error has not occurred, the process proceeds to step S816. In other words, even if it is determined in step S811 that the counting switch signal is on, if a counting invalid error has occurred, the counting process is not executed. This makes it possible to prevent the counting process from being executed when a counting invalid error has occurred (a situation in which it is not desirable to execute the counting process).
When proceeding from step S1221 to step S816, the medal count control CPU 520 determines whether or not the count execution timer value has reached 500. If it determines that the count execution timer value has not reached 500, the process proceeds to step S817, and if it determines that the count execution timer value has reached 500, the process proceeds to step S819.
In step S817, the medal count control CPU 520 adds "1" to the counting execution timer value. Next, the process proceeds to step S818, where the medal count control CPU 520 saves the counting execution timer value (the value after adding "1" in step S817). Then, the process according to this flowchart ends.
On the other hand, if it is determined in step S816 that the counting execution timer value has reached "500" and the process proceeds to step S819, the medal count control CPU 520 stores "2" in the counting execution flag. Then, the process according to this flowchart ends.

As described above, when the count switch signal is on (when the on state of the count switch 47 is detected), the count execution flag is not changed and the count execution timer value continues to be updated until the count execution timer value reaches "500." When the on state of the count switch 47 is detected and the count execution timer value reaches "500," the count execution flag becomes "2" and the count execution timer value is not updated thereafter. When the count switch 47 is then turned off, "No" is determined in step S811, "No" in step S812, and "No" in step S813, and the process proceeds to step S815, where the count execution timer value is cleared.
On the other hand, if the counting switch signal is turned on and then turned off before the counting execution timer value reaches "500", the counting execution flag becomes "1". After that, the counting execution timer value is not updated.

The example of Figure 133 above is an example configured so that even if it is detected that the counting switch 47 is on, when an invalid counting error occurs, the counting execution timer update (save) process and the counting execution flag update (save) process are not performed.
In contrast to this, in the example shown in FIG. 134, when an invalid count error occurs, the count value is uniformly set to "0".
FIG. 134 is a flowchart showing the counting control in step S1212 of FIG.
First, in step S831, the medal count control CPU 520 determines whether it is time to notify the medal count. The "count notification timing" refers to the timing 100 ms after the gaming machine information notification is transmitted, as shown in FIG.
If it is determined that it is the timing for counting notification, the process proceeds to step S832, and if it is determined that it is not the timing for counting notification, the process according to this flowchart ends.

When it is determined that it is the timing for count notification and the process proceeds to step S832, the medal count control CPU 520 clears the counting flag (to "0"). Next, the process proceeds to step S1231, where the medal count control CPU 520 determines whether or not an invalid count error has occurred. The "invalid count error" here is the same as step S1221 in FIG. 133 described above. If it is determined that an invalid count error has occurred, the process proceeds to step S848, and if it is determined that an invalid count error has not occurred, the process proceeds to step S833.
In step S833, the medal count control CPU 520 determines whether the count execution flag is "0" (whether the count switch 47 is not operated). If it is determined that the count execution flag is not "0", the process proceeds to step S834, and if it is determined that the count execution flag is "0", the process proceeds to step S848.
In step S834, the medal count control CPU 520 determines whether or not the total medal count is 0. If it determines that the total medal count is not 0, the process proceeds to step S835, and if it determines that the total medal count is 0, the process proceeds to step S848.
In step S835, the medal count control CPU 520 sets the count value (counted medal count) to "50".
Next, the process proceeds to step S836, where the medal count control CPU 520 determines whether the count execution flag is "2" (whether the count switch 47 has been pressed and held). If it is determined that the count execution flag is "2", the process proceeds to step S837, and if it is determined that the count execution flag is not "2", the process proceeds to step S847.

In step S837, the medal count control CPU 520 determines whether or not the total medal count is equal to or greater than 50. If it determines that the total medal count is equal to or greater than 50, the process proceeds to step S839, and if it determines that the total medal count is not equal to or greater than 50, the process proceeds to step S838.
In step S838, the medal count control CPU 520 sets the total medal count as the count value, and then proceeds to the next step S839 to store the count value.
On the other hand, when it is determined in step S1231 that an invalid count error has occurred, when it is determined in step S833 that the count execution flag is "0" (the count switch 47 has not been operated), or when it is determined in step S834 that the total number of medals is "0", the process proceeds to step S848, where the count value is set to "0". Then, the process proceeds to step S839, where the count value "0" is saved.
Furthermore, when it is determined in step S836 that the count execution flag is not "2," the process proceeds to step S847, where the medal count control CPU 520 sets the count value to "1." Then, the process proceeds to step S839, where the medal count control CPU 520 saves the count value "1." Here, when a "No" determination is made in step S833 and a "No" determination is made in step S836, this means that the count execution flag is "1," and therefore the count switch 47 has been short-pressed.

From the above,
(1) When the counting switch 47 is not operated, the count value is set to "0."
(2) Even if the counting switch 47 is operated, if the total number of medals is "0", the count value is set to "0".
(3) When the counting switch 47 is pressed briefly, if the total number of medals is not "0", the count value "1" is set.
(4) When the counting switch 47 is pressed and held down, if the total number of medals is "50" or more, the count value "50" is set.
(5) When the count switch 47 is pressed and held down, if the total number of medals is less than "50", the total number of medals is set as the count value.
(6) When an invalid counting error occurs, the count value is set to "0" regardless of whether the counting switch 47 is operated or not, and regardless of whether the counting switch 47 is pressed for a short time or a long time.
This will be the case.

In the next step S840, the medal count control CPU 520 updates the total medal count by subtracting the count value from the total medal count.
Next, the process proceeds to step S841, where the medal count control CPU 520 adds the count value to the value in the count accumulation value storage area, thereby updating the value in the count accumulation value storage area.
Next, the process proceeds to step S842, where the medal count control CPU 520 sets the counting flag (stores "FFh").

Then, proceeding to step S843, the medal count control CPU 520 outputs a count notification. Specifically, it outputs "0x07h" as the message length, outputs "0x02h" as the command, outputs the count serial number stored in the count serial number storage area as the count serial number, outputs the count value stored in the count value storage area as the count value, outputs the count cumulative value stored in the count cumulative value storage area as the count cumulative value, and outputs a checksum value (1 byte) of the various output data (see FIG. 30).
In the next step S844, the medal count control CPU 520 clears the count value. Note that the value stored in the count cumulative value storage area is not cleared at the timing when the count notification is output (or has been output).

Next, the process proceeds to step S845, where the medal count control CPU 520 executes the process of updating the counting serial number (process of setting it to "+1"). Note that when the counting serial number is "255 (D)", the result of adding "+1" is "0", so if it becomes "0", the process of updating the counting serial number (process of adding "+1") is executed again.
The medal count control CPU 520 also transmits information based on the counting flag to the main control CPU 510. This allows the main control CPU 510 to determine that counting is in progress. Furthermore, for example, by transmitting information indicating that counting is in progress from the main control CPU 510 to the sub-control CPU 85, the sub-control CPU 85 can perform a presentation corresponding to the counting in progress.
Next, the process proceeds to step S846, where the count execution flag is cleared (set to "0"), and the process according to this flowchart ends.

In the eighth embodiment, as in the second embodiment, counting based on the operation of the counting switch 47 is possible even during the setting change mode or the setting confirmation mode.
However, if the counting switch 47 is operated under circumstances where medals can be bet, an effect based on the operation of the counting switch 47 is executed, but if the counting switch 47 is operated during the setting change mode or the setting confirmation mode, it is possible not to execute an effect based on the operation of the counting switch 47. The reason for this configuration is that when the counting switch 47 is operated during the setting change mode or the setting confirmation mode, it is highly likely that a hall staff member is counting (and not a player).

On the other hand, if the counting switch 47 is operated during setting change mode or setting confirmation mode, a dedicated screen for setting change mode or setting confirmation mode may be displayed on the image display device 23, or a sound may be output. In this way, necessary information can be provided to the hall staff. Furthermore, while a dedicated screen for setting change mode or setting confirmation mode is displayed, a notification indicating that counting is in progress (for example, "Counting in progress" may be displayed on the screen) may be made. In this case, the notification is configured to be different from the counting effect (for the player) described above. Such a notification can be used to draw attention.

Furthermore, when an invalid counting error occurs, as shown in FIG. 133, the counting execution timer and counting execution flag may not be updated (in other words, the same processing as when the counting switch 47 is not operated may be performed), or, as shown in FIG. 134, the count value may be set to "0" regardless of the operation of the counting switch 47 (either processing may be performed).
In addition, various settings can be made as to what type of error is deemed to be a counting invalid error (whether or not the counting process is actually performed).

On the other hand, when an error other than the invalid count error (hereinafter referred to as a "predetermined error") is detected, the counting process can be executed as normal. An example of a predetermined error is when a command communication error occurs in the main control command reception process (step S1188) of the medal count control main process (FIG. 130).
For example, if a command communication error occurs, an error display start process (a process to notify that an error has occurred) is executed as shown in step S1203 of Figure 131, but even while the command communication error is occurring, a medal count control interrupt process is executed, and when operation of the counting switch 47 is detected, a counting process is executed.
Therefore, even if a predetermined error occurs, the determination in step S1221 in FIG. 133 is "No," and the determination in step S1231 in FIG. 134 is "No."
If the counting switch 47 is operated while an invalid counting error or a predetermined error is occurring, a predetermined display such as the image display device 23 may display this fact, or a sound may be output from the speaker 22. In this way, a hall staff member can be notified that the counting switch 47 has been operated while an invalid counting error or a predetermined error is occurring. The notification mode when the counting switch 47 is operated while an invalid counting error is occurring and the notification mode when the counting switch 47 is operated while a predetermined error is occurring may be the same or different.

Although the eighth embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and various modifications such as those described below are possible.
(1) In the medal count control program start process, recovery is possible simply by operating the reset switch 14. However, this is not limited to this, and the requirement may be turning the power on/off. The initialization process of step S1184 in FIG. 128 is executed by turning the power on/off.
(2) The period of the main control interrupt process, the period of the medal count control interrupt process, and the loop period of the medal count control main process are not limited to the values shown in this embodiment and can be set to various values. However, as described above, it is preferable that the loop period of the medal count control main process be shorter than the period of the main control interrupt process.
(3) Examples of invalid counting errors (errors that should invalidate the counting process) include VL abnormalities, chip manufacturer code errors, and medal count control RWM errors, but are not limited to these. For example, it is possible not to treat VL abnormalities as invalid counting errors.
Alternatively, other predetermined errors may be treated as one of the invalid count errors.

(4) In the example of Fig. 77, there is one reset switch 14. In the case where there is one reset switch 14, when the reset switch 14 is operated, the signal may be input to the main control CPU 510, and further transmitted from the main control CPU 510 to the medal count control CPU 520. Alternatively, when the reset switch 14 is operated, the signal may be input to both the main control CPU 510 and the medal count control CPU 520.
Furthermore, a reset switch 14 for clearing an error that occurs in the main control (hereinafter referred to as "reset switch 14A") and a reset switch 14 for clearing an error that occurs in the medal count control (hereinafter referred to as "reset switch 14B") may be provided separately. In this case, when the reset switch 14A is operated, its signal is input to the main control CPU 510 but not to the medal count control CPU 520. Similarly, when the reset switch 14B is operated, its signal is input to the medal count control CPU 520 but not to the main control CPU 510.

(5) The total medal count clear switch 112 does not originally have an error reset function, but may have a function that can reset an error that occurs in medal count control (a function equivalent to that of the reset switch 14). In other words, when an error occurs in medal count control and the total medal count clear switch 112 is operated, the error reset process (processing to end the error display) is executed in the same way as when the reset switch 14 is operated.
(6) As described above, when the time at which the medal count control CPU 520 detects a command communication error with the main control CPU 510 is set to "t1" (less than "1" ms) and the time at which the main control CPU 510 detects a command communication error with the medal count control CPU 520 is set to "t2"("1.12" ms, which is the period of the main control interrupt processing), then "t1 <t2".
For this reason, the main control CPU 510 may detect a command communication error with the medal count control CPU 520 once for each of the multiple executions of the main control interrupt process. Even in this case, the time it takes for the medal count control CPU 520 to detect a command communication error with the main control CPU 510 remains shorter than the time it takes for the main control CPU 510 to detect a command communication error with the medal count control CPU 520.
On the other hand, when the medal count control CPU 520 detects a command communication error with the main control CPU 510 during the medal count control main processing, the medal count control CPU 520 may detect a command communication error with the main control CPU 510 once for each multiple execution of the loop processing of the medal count control main processing. If the cycle of the loop processing of the medal count control main processing is, for example, 0.5 ms, even if the command communication error is detected every two loops of the medal count control main processing, the time it takes for the medal count control CPU 520 to detect a command communication error with the main control CPU 510 will be shorter than the time it takes for the main control CPU 510 to detect a command communication error with the medal count control CPU 520.
In the eighth embodiment, the medal count control CPU 520 is configured to detect a command communication error with the main control CPU 510 during medal count control main processing, but this is not limiting, and the medal count control CPU 520 can also detect a command communication error with the main control CPU 510 during medal count control interrupt processing. In this case, when the cycle of the medal count control interrupt processing is "t1" and the cycle of the main control interrupt processing is "t2", if "t1 <t2", the time during which the medal count control CPU 520 detects a command communication error with the main control CPU 510 will be shorter than the time during which the main control CPU 510 detects a command communication error with the medal count control CPU 520.
(7) The eighth embodiment is not limited to being implemented alone, but can be implemented in appropriate combination with at least a part of the first to seventh embodiments.

Ninth Embodiment
In the ninth embodiment, as in the sixth to eighth embodiments, the "game medium" is referred to as a "medal." However, in the eighth embodiment, the gaming machine 10 is also a medal-less gaming machine (smart gaming machine, smart pachislot), and the game medium is an electronic medal (electronic gaming medium). For ease of explanation, the number of medals may be referred to as the "number of medals."
In addition, the "prescribed number" (the number of bets required to start playing, also called the "number of bets") in the ninth embodiment is "3". However, the prescribed number is not limited to "3", and the ninth embodiment can be applied even if the prescribed number is "1", "2", or "4" or more.
Furthermore, in the ninth embodiment, the specified number is one, "3," but the ninth embodiment can also be applied when there are multiple specified numbers (for example, two, "2" and "3," or three, "1" to "3"). When there are multiple specified numbers, the maximum specified number is referred to as the "maximum specified number (also referred to as the "maximum bet number")."
If the gaming machine 10 is a slot machine installed in a Type 4 business establishment that is subject to the Act on the Control and Proper Management of Amusement and Entertainment Businesses, etc., it must comply with a type test conducted by the Security Communications Association (SCA) or other testing organization.
In the model test, the gaming machine 10 is connected to a test firing test machine, and signals are sent and received between the gaming machine 10 and the test firing test machine to determine whether or not they are compatible.
The ninth embodiment relates to a test signal transmitted from the gaming machine 10 to the test firing test machine 600.
In addition, in the main control interrupt processing (Figure 127), processing (step S1053) is executed to send a test signal to the test firing test machine 600, but when the gaming machine 10 and the test firing test device 300 are connected, the test signal is actually input to the test firing test machine 600.
In contrast, when the gaming machine 10 is installed in a hall or the like, the gaming machine 10 and the test firing test machine 600 are not connected, and therefore no test signal is input from the gaming machine 10 to the test firing test machine 600. However, since the gaming machine 10 has the same program as the program that was tested when the gaming machine 10 was connected to the test firing test machine 600, even when the gaming machine 10 is installed in a hall or the like, the process for outputting a test signal in the main control interrupt process (step S1053) is executed as is.

Figure 135 is a block diagram of the gaming machine 10 in the ninth embodiment. In the ninth embodiment, as in Figure 77 (sixth embodiment), two one-chip microprocessors are mounted on the main control board 50, one of which is a one-chip microprocessor for main control and the other is a one-chip microprocessor for medal count control. In addition, one one-chip microprocessor for sub-control (performance control) is mounted on the sub-control board 85.
In the following description, unless otherwise specified, the block diagram of the ninth embodiment is the same as that of Fig. 77. However, this does not mean that the block diagram of the ninth embodiment is limited to the same configuration as that of Fig. 77, and the configurations of other embodiments can be appropriately adopted.
In Figure 135, the winning number display unit 78 is similar to the payout number display unit 78 in Figure 77, and is composed of, for example, a two-digit LED (7-segment LED). Hereinafter, of the two-digit value displayed on the winning number display unit 78, the tens digit will be referred to as the "higher digit" and the ones digit will be referred to as the "lower digit."
When a symbol combination corresponding to a small win is stopped and displayed, the winning number display unit 78 displays the number of medals to be paid out corresponding to the small win (the number of medals won by the player). For example, when a small win with a payout number of "8" medals is won, "08" is displayed.
The winning number display unit 78 also functions as an error number display unit that displays the error number that has occurred when an error occurs in the gaming machine 10. For example, when a recoverable error occurs, it displays "E0,""E1," ... according to the type of error. When an unrecoverable error occurs, it displays "88."
Furthermore, the winning number display unit 78 functions as an instruction monitor that displays instruction numbers (information on advantageous pressing sequences) in games that activate instruction functions such as AT (notifying advantageous pressing sequences). For example, when the advantageous pressing sequence is "213 (center left and right)," it displays "*1"("*" means that the light is off; the same applies below).

On the other hand, in the ninth embodiment, the bet number display section 77 in FIG. 77 is composed of a 1 bet number display lamp (LED) 79a, a 2 bet number display lamp (LED) 79b, and a 3 bet number display lamp (LED) 79c.
Here, in the ninth embodiment, a status indicator lamp 79 is provided. The status indicator lamp 79 includes six LEDs: a 1 bet indicator lamp (LED) 79a, a 2 bet indicator lamp (LED) 79b, a 3 bet indicator lamp (LED) 79c, a deposit request lamp (LED) 79d, a game start indicator lamp (LED) 79e, and a replay indicator lamp (LED) 79f.
When the 1-bet switch 40a is operated once and "1" medal is bet, the 1-bet indicator lamp 79a lights up (the 2-bet indicator lamp 79b and the 3-bet indicator lamp 79c are turned off). When the 1-bet switch 40a is operated twice and "2" medals are bet, the 1-bet indicator lamp 79a and the 2-bet indicator lamp 79b light up (the 3-bet indicator lamp 79c is turned off). When the 1-bet switch 40a is operated three times or the 3-bet switch 40b is operated once and "3" medals are bet, the 1-bet indicator lamp 79a, the 2-bet indicator lamp 79b, and the 3-bet indicator lamp 79c light up.

The insertion request lamp 79d is a lamp that lights up when medals can be bet (inserted) (so-called bet waiting state (state where the number of bets is "0" to "2")).
The game start indicator lamp 79e is a lamp that lights up when a specified number of medals have been bet and it is now possible to operate the start switch 41. It also lights up after an automatic bet for a replay has been placed.
The replay display lamp 79f is a lamp that lights up after the replay has stopped (when replay is activated).
The other configurations of the block diagram are the same as those in FIG. 77, so the explanation will be omitted.

Figure 136 shows an example of the electrical connection between the gaming machine 10 and the test firing test machine 600 during a type test. The gaming machine 10 and the test firing test machine 600 are connected via interface boards 601 and 602 so that signals can be sent and received.

The test signals output from the gaming machine 10 to the test firing test machine 600 mainly include the following test signals (1) to (12) (as described in this embodiment). Note that the test signals are not limited to these. Some test signals may also be output from the interface board 601.
(1) Turn-on Request Lamp Signal The turn-on request lamp signal is a test signal that corresponds to turning on/off the turn-on request lamp 79d.
The insertion request lamp signal is a signal that indicates whether or not it is possible to insert medals, and is always on while it is possible to insert medals. It is turned off when it becomes impossible to insert medals because the start switch 41 is operated, or when the number of bets reaches the maximum specified number and it becomes impossible to insert any more medals. Note that whether or not to turn on the insertion request lamp signal when the specified number of medals has been inserted but is not the maximum specified number is optional.
Although details will be described later, in the ninth embodiment, the on/off of the make-on request lamp 79d does not always correspond to the on/off of the make-on request lamp signal.
For example, even if the power-on request lamp signal is off, the power-on request lamp 79d may be lit.
When replay is activated, the input request lamp signal is turned off.

(2) Start possible lamp signal The start possible lamp signal is a signal indicating whether or not a game can be started when the start switch 41 is operated, and is a test signal corresponding to the lighting/extinguishing of the game start indicator lamp 79e.
The start possible lamp signal is turned on when a specified number of medals have been inserted and the start switch 41 is ready to be operated, and is turned off when it is detected that the start switch 41 is on.
It is optional whether or not to turn on the start possible lamp signal when the specified number of medals has been inserted but is not the maximum specified number.
For the convenience of test firing, the start ready lamp signal may be generated and output by the interface board 601, rather than from the gaming machine 10. However, this is not limiting, and the signal may be output from the gaming machine 10.
Also, when the replay is activated, the input request lamp signal is turned off as described above, but the start possible lamp signal is turned on.

(3) Replay State Identification Signal The replay state identification signal is a signal for identifying the variable state when the probability of winning (lottery) a replay (replay role) has the ability to fluctuate to a value other than "0", and is a signal output for each game state (RT) in which the probability of winning a replay is different. Note that when the probability of winning a replay does not fluctuate, the replay state identification signal outputs "00H" (all off state).
The re-play state identification signal consists of 1 byte of data, with bit 0 assigned to re-play state identification signal 1, bit 1 assigned to re-play state identification signal 2, ..., bit 7 assigned to re-play state identification signal 8. Therefore, 255 types of signals from "00H" to "FFH" can be transmitted as the re-play state identification signal.
(4) Signal during advantageous zone This signal indicates whether or not the game is being played during an advantageous zone, and turns on at the start of play in the advantageous zone (indicating that the game is being played during an advantageous zone), and turns off at the end of play in the advantageous zone (indicating that the game is not being played during an advantageous zone). If the advantageous zone is played multiple times in succession, the signal remains on between those games (it does not turn off between games).
(5) Replay signal This is a signal indicating whether or not replay (replay) is in operation (the symbol combination corresponding to the replay was stopped and displayed in the previous game), and it turns on at the start of a game in which replay is in operation (indicating that the game is in operation with replay), and turns off at the end of a game in which replay operation ends (indicating that the game is not in operation with replay).
In addition, if replay occurs multiple times in a row, the light will remain on between plays (it will not be turned off between plays).

(6) Signal indicating whether the reel continuous operation device is in operation. This signal is turned on at the start of a game when the reel continuous operation device starts to operate (indicating that the reel continuous operation device is operating), and turned off at the end of a game when the reel continuous operation device stops to operate (indicating that the reel continuous operation device is not operating).
Examples of the device for continuously operating a reel include a first type device for continuously operating a reel (1BB) relating to a first type special reel, and a second type device for continuously operating a reel (2BB) relating to a second type special reel.
Therefore, in the above case, the signal from the device for continuous operation of the reel may be a signal from the device for continuous operation of the reel related to the first type special reel, or a signal from the device for continuous operation of the reel related to the second type special reel.
(7) Signals during special functions Examples of special functions include the first type (RB), the second type (CB), and the normal type (SB).
The reel signal is a signal indicating whether or not these reels are in operation. Specifically, it is a first-class special reel signal indicating that a first-class special reel (RB) is in operation, a second-class special reel signal indicating that a second-class special reel (CB) is in operation, and a normal reel signal indicating that a normal reel (SB) is in operation.
These signals turn on (indicating that the reel is operating) at the start of the game when the reel begins to operate, and turn off (indicating that the reel is not operating) at the end of the game when the reel ends to operate.

(8) Condition Device Signal The condition device signal is a signal that indicates the operating status (winning status) of the bonus condition device or the winning and replay condition device. When the condition device is not operating, the condition device signal outputs "00H" (all off). There are various output methods for the condition device signal, but detailed explanations will be omitted in this embodiment.
(9) Stop Enable Lamp Signal The stop enable lamp signal is a signal indicating that the reel 31 has rotated and is ready to be stopped. The stop enable lamp signal turns on when the reel 31 is ready to be stopped, and turns off when it detects that the stop switch signal is on.
(10) Payout Count Signal The payout count signal is a signal that is output when a minor winning combination involving the payout of medals is won, in order to inform the test firing test machine 600 of the number of medals to be paid out. Details will be described later, but for each medal, a signal is output that has one pulse consisting of an on signal for a predetermined time and an off signal for the same time, indicating the payout number as "1", and this signal is output repeatedly for the number of medals to be paid out.
The "predetermined time" can be set to various values, such as 5 ms or 50 ms. However, it is not limited to 5 ms or 50 ms, and can be set to various values such as 10 ms, 20 ms, or a value exceeding 50 ms.
Note that the "predetermined time" is not an exact integer because it is actually set as the number of interrupt processes in the main control interrupt process. In this embodiment, when the predetermined time is written as "T" ms, it means approximately "T" ms.
For example, if the "predetermined time" is "5" ms, and the payout count signal (ON/OFF signal) for the payout number "1" is "10" ms, the payout count signal corresponding to the payout number "3" is
On (5 ms) → Off (5 ms) → On (5 ms) → Off (5 ms) → On (5 ms) → Off (5 ms)
This becomes:
Similarly, when the "predetermined time" is "50" ms, if the payout count signal (ON/OFF signal) for the payout number "1" is "100" ms, the payout count signal corresponding to the payout number "3" is
On (50 ms) → Off (50 ms) → On (50 ms) → Off (50 ms) → On (50 ms) → Off (50 ms)
This becomes:

(11) Phase Signal The phase signal is a signal that indicates the phase of the motor (stepping motor) 32 associated with the left, center, and right reels 31, and is output while the motor 32 is being driven.
(12) Signals, etc. necessary for generating a pattern stop signal, and stop pattern signals, etc. In this embodiment, signals, etc. necessary for generating a pattern stop signal are output from the gaming machine 10 to the interface board 602, and the interface board 602 outputs stop pattern signals, etc. to the test firing test machine 600.
The stop pattern signal is a signal for outputting the order in which the reels 31 are pressed (stop order) and the position at which the stop operation is performed in order for the player to obtain the maximum number of balls in a gaming machine that has the ability to change the probability of winning a replay to a value other than "0".

The test signals output from the test firing test machine 600 to the gaming machine 10 mainly include the following test signals (13) to (15). However, the test signals are not limited to these.
(13) Insert Switch Signal This is a signal indicating the insertion of a medal, and a one-pulse signal is output to the gaming machine 10 in response to the insertion of one medal.
When the gaming machine 10 receives one pulse of the insertion switch signal, it executes the same processing as when the medal number "1" is inserted.
(14) Start Switch Signal This is a signal for starting the rotation of the reel 31 (activating the motor 32 and the symbol display device), and is output when the start possible lamp signal is on.
When the gaming machine 10 receives the start switch signal, it executes the same processing as when the start switch 41 is operated.
(15) Stop Switch Signal This is a signal for stopping the rotation of the reel 31 (stopping the operation of the motor 32 and the symbol display device), and is output when the stop enable lamp signal is on.

During the test firing, the gaming machine 10 is not operated by an operator, and signals corresponding to the player's operations, specifically, an insertion switch signal corresponding to the insertion of a medal, a start switch signal corresponding to the operation of the start switch 41, and a stop switch signal corresponding to the operation of the stop switch 42, are input from the test firing machine 600 to the gaming machine 10. Upon receiving these signals, the gaming machine 10 executes processing corresponding to the insertion of a medal, the operation of the start switch 41, and the operation of the stop switch 42, respectively.
In addition to the above, test signals output from the test firing test machine 600 to the gaming machine 10 include a stop release switch signal, etc., but a description thereof will be omitted in this embodiment.

137 to 139 are diagrams showing data stored in the main control RWM 512 described in the ninth embodiment.
For ease of explanation, the addresses will not be listed in order below, but addresses F000H to F1FFH are in use, and addresses F200H and above are outside the use area. The storage area for data related to test signals is located outside the use area.
In Fig. 137, the operating status flag (_FL_ACTION) at address "F05BH" is an area for storing data on the operating status flag, and is a flag that determines whether the reel is operating or not depending on whether any bit corresponding to the reel is "1." In this embodiment, the operating status flag is updated in the final process (step S1248) of the main control main process (Fig. 140).
In this embodiment, pseudo-game effects are assigned to the D0 bit, 1BB to the D3 bit, and RB to the D4 bit.
For example, while the pseudo game presentation is being executed, the D0 bit is set to "1." When the 1BB is won, the 1BB is activated and the RB is activated, and when the game state is set, the D3 bit and the D4 bit are set to "1." When the 1BB end condition is met, the D3 bit and the D4 bit are set to "0."

Although the pseudo-game effect is not a device itself, it is assigned to the D0 bit in the operation status flag.
Here, "pseudo game effect" refers to an effect in which, after the reels 31 start to rotate, the reels 31 are pseudo-stopped (this stop is also called a "temporary stop" or "pseudo stop"; hereinafter referred to as a "temporary stop") by operating the stop switch 42 to activate the rotation stop device, and an arbitrary symbol combination is displayed, until the rotation speed of the reels 31 becomes constant. "Pseudo game effect" is also called "reel effect".
On the other hand, in contrast to the "pseudo game presentation," the game for displaying a symbol combination (a symbol combination corresponding to the result of the lottery) as the game result is called the "real game."
The symbol combination temporarily stopped by the pseudo game effect does not represent the game result. After the symbol combination is temporarily stopped by the pseudo game effect, the game result is displayed when the symbol combination is stopped and displayed by the actual game.

The replay activation status flag (_FL_REPLAY) at address "F01DH" is a memory area used to record whether replay is in operation. When a replay symbol combination is displayed as a still image at the end of play, the replay activation status flag is turned on ("1"). Furthermore, when the replay activation status flag is on, an automatic bet is placed on the next play, and replay is performed. When the replay symbol combination is not displayed as a still image at the end of the replay, the replay activation status flag is turned off ("0"). Conversely, when the replay symbol combination is displayed as a still image at the end of the replay, the replay activation status flag remains on.

The symbol combination display flag (_FL_WIN) at address "F057H" is a storage area for storing the symbol combination that has stopped and been displayed. In this embodiment, the D0 bit is assigned to the replay activation symbol, and the D3 bit is assigned to the 1BB activation symbol. For example, when it is determined that a symbol combination corresponding to 1BB has stopped and been displayed on an active line, the D3 bit is set to "1." The symbol combination display flag is updated when all reels 31 have stopped and a display determination has been made. The symbol combination display flag is cleared, for example, at the start of the next game.
The LED display data (_PT_STS_LED) at address "F02DH" is a storage area for storing the on/off status of the status indicator lamps 79, i.e., the 1 bet indicator lamp 79a (D0), the 2 bet indicator lamp 79b (D1), the 3 bet indicator lamp 79c (D2), the insertion request lamp 79d (D3), the game start indicator lamp 79e (D4), and the replay indicator lamp 79f (D5). For example, when it is possible to insert medals before the start of a game, the D3 bit of the LED display data becomes "1," and the insertion request lamp 79d becomes lit.
Also, for example, when the replay operation state is reached (the replay symbol is displayed stopped), the D5 bit of the LED display data becomes "1", and the replay display lamp 79f becomes lit.

In Figure 138, the advantageous section flag (_FL_ADV_STS) at address "F062H" is a storage area that stores a value for determining whether the section is a non-advantageous section (normal section) or an advantageous section. If it is a non-advantageous section, "00000000B" is stored, and if it is an advantageous section, "00000010B" is stored.
The instruction number (_NB_ORD_INF) at address "F061H" is a memory area for storing instruction numbers in a game in which the instruction function is activated when a biased role (push order bell) is won. In the figure, "213" indicates the push order of "center left right", "231" indicates the push order of "center right left", "312" indicates the push order of "right left center", and "321" indicates the push order of "right center left".
For example, if you win the biased bell with the push order "213" during AT, "00000001B" is stored.
The bet number data (_NB_PLAY_MEDAL) at address "F02EH" is a storage area where a value corresponding to the current bet number is stored. For example, when the bet number is "0", the bet number data is "0", and when the bet number is "3", the bet number data is stored as "3H".
The automatic bet number data (_NB_REP_MEDAL) at address "F02FH" is a memory area that stores the number of medals to be automatically bet when replay is activated (when a replay symbol combination is stopped and displayed).

The winning number data (_NB_PAYOUT) at address "F01FH" is a storage area for the number of medals won (payouts) when a small winning combination is achieved in the current game. The winning number data is data to be displayed on the winning number display unit 78.
Furthermore, when a predetermined error (a recoverable error or an unrecoverable error) occurs, an error number is displayed in the acquisition number display unit 78. Therefore, when a predetermined error occurs, error number data for displaying the error number is stored in the acquisition number data. For example, when the error number to be displayed is "E0", error number data for displaying "E0" is stored in the acquisition number data.
Furthermore, in a game in which the instruction function is activated during the AT (such as when a biased role is won), the instruction number (of the advantageous push order) is displayed in the acquisition number display unit 78. In other words, in a game in which the instruction function is activated, the acquisition number display unit 78 functions as an instruction monitor. When the instruction number is displayed in the acquisition number display unit 78, the instruction number data is stored in the acquisition number data. For example, in a game in which the advantageous push order is "213 (center left and right)" and the push order bell is won, when the instruction function is activated, the instruction number data "01B" is stored in the acquisition number data. As a result, "*1" is displayed in the acquisition number display unit 78.
Although detailed description will be omitted in this embodiment, a predetermined value (for example, "88") may be displayed in the acquisition count display unit 78 during the setting change mode. In this case, data for displaying "88" as the acquisition count data is stored during the setting change mode. Since the upper limit for the number of medals to be paid out is "15," when "88" is displayed in the acquisition count display unit 78, it can be determined that this is not a display of the payout number.

The payout number buffer (_BF_PAY_MEDAL) at address "F01EH" is a memory area that stores the payout number when a small combination is won in the current game and the number of medals to be paid out is determined. The value stored here is maintained until the end of the next game. For example, if a small combination with a payout number of "8" is won in the current game, "8 (H)" will be stored in the payout number buffer, and if no combination is won in the next game, the payout number buffer will be overwritten with "0".

The stop acceptance information data (_PT_STOP_STS) at address "F011H" is a storage area that stores a value indicating whether operation of the stop switch 42 can be accepted. In this embodiment, the left stop switch 42 is assigned to bit D0, the middle stop switch 42 to bit D1, and the right stop switch 42 to bit D2. Bits D3 to D7 are unused bits and are always "0".
For example, when the reel 31 starts to spin and a game starts, and all the stop switches 42 are ready to be operated, all of the D0, D1, and D2 bits become "1", indicating that they are ready to be operated.
Next, when the left stop switch 42 is operated, for example, the D0 bit is updated from "1" to "0." At this point, the D1 and D2 bits remain "1."

The reel condition device number (_NB_CND_BNS) at address "F025H" is a memory area for storing a number that manages the operating status of the reel condition device, and after a reel is drawn, the number of the reel condition device corresponding to the drawing result is stored.
The winning and replay condition device number (_NB_CND_NOR) at address "F026H" is a memory area that stores a number that manages the operating status of the winning and replay condition device, and after the winning combination is drawn, the winning and replay condition device number corresponding to the drawing result (winning number) is stored.
The replay state identification information flag (_FL_RT_INF) at address "F027H" is a memory area that stores data indicating whether it is time to output a replay state identification signal. When a replay state identification signal is output, the value "FFH (ON)" is stored, and otherwise the value "00H (OFF)" is stored.
The replay state identification information flag is turned on when a game starts, and is turned off when the start switch is accepted.
The RT state number (_NB_RT_STS) at address "F028H" is a memory area that stores a number to identify which RT (replay state) the current RT is. For example, if the RT has non-RT, RT1, ..., when it is non-RT, "00000000B" is stored as the RT number, and when it is RT1, "00000001B" is stored as the RT number. The RT state number becomes the "replay state identification signal" in the test signal.

Address "F029H" is a storage area where LED display counter 1 (_CT_LED_DSP1) is stored.
The LED display counter 1 is a counter for dynamically lighting the upper digits of the acquisition number display section 78, the lower digits of the acquisition number display section 78, and the status display lamp 79, and is continuously updated with each interrupt in the main control interrupt processing (LED display control of step S1052 in Figure 127).
In this embodiment, the LED display counter 1 has a value of "00000100B" as an initial value. Then, the LED display counter 1 is updated by shifting the bit "1" of the LED display counter 1 one digit to the right for each main control interrupt process. Also, when the value of the LED display counter 1 is "00000001B", shifting it one digit to the right results in "00000000B", but during the main control interrupt process, the LED display counter 1 is initialized to set the LED display counter 1 to "00000100B". As a result, for each main control interrupt process, the LED display counter 1
"N" Interrupt: 00000100B
"N+1" interrupt: 00000010B
"N+2" interruption: 00000001B
"N+3" interrupt: 00000000B → 00100000B (Counter initialization process. Same value as "N" interrupt.)
"N+4" interruption: 00000010B
:
This becomes:
Therefore, three interrupts of the main control interrupt process constitute one cycle.
The lamp to be lit corresponding to the value of the LED display counter 1 is:
00000100B: Upper digits of the acquisition number display section 78 00000010B: Lower digits of the acquisition number display section 78 00000001B: Status display lamp 79
Then, in the main control interrupt process, dynamic lighting is performed so that the lamp corresponding to the bit that is set to "1" in the LED display counter 1 is turned on.

Specifically, when the value of LED display counter 1 is "00000100B," a signal is output to light up the upper digits of the acquisition count display unit 78, enabling the upper digits of the acquisition count display unit 78 to light up (the lower digits of the acquisition count display unit 78 and the status display lamp 79 are turned off). Then, at the time of the next main control interrupt processing, LED display counter 1 becomes "00000010B," a signal is output to light up the lower digits of the acquisition count display unit 78, enabling the lower digits of the acquisition count display unit 78 to light up (the upper digits of the acquisition count display unit 78 and the status display lamp 79 are turned off). Furthermore, at the time of the next main control interrupt processing, LED display counter 1 becomes "00000001B," a signal is output to light up the status display lamp 79, enabling a specific lamp of the status display lamp 79 to light up (the upper and lower digits of the acquisition count display unit 78 are turned off).
The signal for lighting up the status indicator lamps 79 is output to the lamps whose bit in the LED display data is "1." For example, when the LED display data is "00110111B" (when a replay stop is displayed), a signal is output to light up the 1 bet indicator lamp 79a, the 2 bet indicator lamp 79b, the 3 bet indicator lamp 79c, the game start indicator lamp 79e, and the replay indicator lamp 79f (the insertion request lamp 79d is turned off).

The payout count signal output time (_ST1_OUT_CNT) at address "F212H" is a storage area for values used to manage the output time of the payout count signal, and a predetermined initial value is stored for each on signal or each off signal, and "1" is subtracted for each main control interrupt process. When the value before subtraction is "0" and "1" is subtracted from "0", the value obtained by subtracting "1" from the predetermined initial value is stored.
The period of the main control interrupt process in this embodiment is 1.12 ms, the same as in the eighth embodiment. Therefore, if one of the on or off signals of the payout count signal is set to approximately 5 ms (but not less than 5 ms), the predetermined initial value can be set to 5D. As a result, the time it takes for the predetermined initial value to change from 5D to 0 is 5.6 ms. In this case, an on signal is output for 5.6 ms as the payout count signal, followed by an off signal for 5.6 ms.
Similarly, if one of the payout count signals is set to an ON signal or OFF signal of approximately 50 ms (but not less than 50 ms), the predetermined initial value can be set to 45D. As a result, the time it takes for the predetermined initial value to change from 45D to 0 is 50.4 ms. In this case, an ON signal is output for 50.4 ms, and then an OFF signal is output for 50.4 ms as the payout count signal.
As described above, when the output time of one on or off signal of the payout count signal is set to approximately "T1" ms (but not less than "T1" ms), if the period of the main control interrupt process is set to "T2" ms, the predetermined initial value "N" is:
N = [T1/T2] + 1 (where [,] is the Gauss symbol representing the quotient of an integer (maximum integer value))
The following points can be mentioned.
For example, if the output time "T1" of one of the on or off signals of the payout count signal is set to approximately "5" ms (but not less than "5" ms), and the cycle "T2" of the main control interrupt process is "1.12" ms,
N=[5/1.12]+1=5
In this case, the output time of one ON or OFF signal of the payout count signal is "5.4" ms.
In addition, when the output time "T1" of one of the on or off signals of the payout count signal is set to approximately "10" ms (however, it should not be less than "10" ms), if the period "T2" of the main control interrupt processing is "1.12" ms,
N=[10/1.12]=9
In this case, the output time of one ON or OFF signal of the payout count signal is "10.08" ms.
Furthermore, when the output time "T1" of one of the on or off signals of the payout count signal is set to approximately "50" ms (but not less than "50" ms), if the cycle "T2" of the main control interrupt process is "1.12" ms,
N=[50/1.12]=45
In this case, the output time of one ON or OFF signal of the payout count signal is "50.4" ms.
Furthermore, when the output time of one on signal or off signal of the payout count signal is set to approximately "T1" ms, and it is acceptable for it to be less than "T1" ms, if the period of the main control interrupt process is set to "T2" ms, the predetermined initial value "N" is set as follows:
N = [T1/T2] (where [,] is the Gauss symbol representing an integer quotient (maximum integer value))
The following points can be mentioned.

The payout count signal output count (_SC_MEDAL_OUT) at address "F213H" is a storage area that stores the value when the payout count signal's ON signal is "1" and OFF signal is "1." The payout count signal's "ON signal "1" + OFF signal "1"" becomes a signal (1 pulse) indicating a payout number of "1." Therefore, when the payout number is determined, the value obtained by multiplying that number by two is stored in the payout count signal output count. For example, if the payout number is "11,""22D" is stored in the payout count signal output count.
When the output of one ON or OFF signal of the payout count signal is completed, "1" is subtracted from the payout count signal output number. As described above, when the value of the payout count signal output time is subtracted from "0" to "1", "1" is subtracted from the value of the payout count signal output number.

The test counting signal output time (_ST2_EXP_CAL) at address "F210H" is a memory area that stores a value corresponding to the (remaining) output time of the test counting signal when the test counting signal is output during a test firing test.
In the gaming machine 10 of this embodiment, when the total number of medals (the total number of medals (the number of medals held by the player) displayed on the medal number display unit 121) becomes "15,000" or more,
(1) A notification is given to the player to encourage counting (although the notification is given, the game itself can continue)
(2) The lending process of the medal by the lending unit 200 is disabled (the lending receipt result response is notified as abnormal).
(3) It is configured to output a test counting signal to the testing machine for 3500 ms.
Furthermore, when the total number of medals reaches 16,369 or more,
(4) An error state of the main control is detected and the game is disabled (the start switch 41, the bet switch 40, and the settlement switch 46 are disabled).
It is structured as follows.
Therefore, when the total number of medals reaches "15,000" or more, a test count signal is output to the testing machine, and a value for managing the output time of the test count signal is stored in the test count signal output time. The initial value stored is "2418D". Then, this value is decremented by "1" for each main control interrupt process, and the test count signal is output until this value becomes "0". As a result, the test count signal is output for "2418 x 1.12 = 2708.16" ms.

In FIG. 139, the medal count control status 1 data (_PT_PSTS1) at address "F012H" is a storage area in which a predetermined value is stored according to the main control status (number of medals, error, communication status, etc.).
The D0 bit (control status signal 1) and D1 bit (control status signal 2) are two bits that indicate the current number of medal bets. For example, if the number of bets is "0", the D0 bit and D1 bit will be "0", if the number of bets is "1", D0 will be "1" and the D1 bit will be "0", if the number of bets is "2", D0 will be "0" and the D1 bit will be "1", and if the number of bets is "3" or more, the D0 bit and D1 bit will be "1".
Bit D2 (control status signal 3) is a memory area in which "1" is stored while the total medal count clear switch 112 is being detected as being on after the initial setting abnormality error is cleared.
The D3 bit (control status signal) is a storage area in which "1" is stored while the counting switch signal is being detected as being on after the initial setting abnormality error has been cleared.
D4 bit (control status signal 5) is a memory area in which "1" is stored from the time a counting notification is sent in which the counted medal number is other than "0" until the time a counting notification in which the counted medal number is "0" is sent.
Bit D5 (control status signal 6) is a memory area in which "1" is stored for "200" ms after the loan medal count receipt result in the loan receipt result response is sent normally when a loan notification is received with the number of loaned medals between "1" and "50".
Bit D6 (control status signal 7) is unused in this embodiment and is a storage area where "0" is always stored.
Bit D7 (control status signal 8) is a storage area in which "1" is stored when an initial setting abnormality error is detected.

The medal count control status 2 data (_PT_PSTS2) at address "F013H" is a storage area in which a predetermined value is stored according to the status of the main control, similar to the medal count control status 1 data.
The D0 bit (control status signal 9) is a storage area in which "1" is stored except when a connection abnormality error with the rental unit 200 is detected.
The D1 bit (control status signal 10) is a memory area in which "1" is stored when an error in the number of non-playable medals is detected.
D2 bit (control status signal 11) is a memory area in which "1" is stored when the total number of medals becomes "15,000" or more.
The D3 bit (control status signal 12) is a memory area in which "1" is stored for "200" ms from the time the abnormal command is received if the received medal count control command is abnormal.
However, if the medal count control command received during the detection of an initial setting abnormality is abnormal, "1" will be stored from the time the abnormal command is received until "200" ms has elapsed after the initial setting abnormality error is cleared.
Bit D4 (control status signal 13) is a storage area in which "1" is stored while a communication error with the rental unit 200 is detected.
Bit D5 (control status signal 14) is a memory area in which "1" is stored when the power is turned on, if the total medal count clear switch signal is on, while an initial setting abnormality is being detected, and while the total medal count clear display is being displayed.
Bit D6 (control status signal 15) is a memory area in which "1" is stored if the RWM check data is abnormal when the power is turned on, from the time the RWM check data is determined to be abnormal until "60,000" ms has passed since the initial setting abnormality error was cleared.
If the power is turned off and then on while this signal is on, "1" will be stored from the time the power is turned on until "60,000" ms has elapsed after the initial setting error is resolved.
Bit D7 (control status signal 16) is a memory area in which "1" is stored for 200 ms from the occurrence of a decrease in the number of medals of "4" or more or an increase in the number of medals of "16" or more in transmission and reception between the main control CPU 510 and the medal count control CPU 520, or a decrease in the number of medals of "51" or more or an increase in the number of medals of "51" or more in transmission and reception between the medal count control CPU 520 and the lending unit 200.

Next, the control process of the ninth embodiment will be described.
The flowchart numbers in the ninth embodiment are as follows:
1. Main control program start processing: FIG. 124 (eighth embodiment)
2. Main control main processing: Figure 140
(1) Game start setting process: FIG. 141
(2) Bet waiting process: FIG. 142
(3) Settlement process: Figure 143
(4) Waiting for a request command from the medal count control: FIG. 125 (Eighth embodiment)
(5) Main control error display process: FIG. 126 (eighth embodiment)
(6) Betting process: Figure 144
(7) Start switch reception process: FIG. 145
(8) Payout count signal set: Figure 146
(9) Assignment process: FIG. 147
(10) Game End Check Processing: FIG. 148
3. Main control interrupt processing: FIG. 127 (eighth embodiment)
(1) LED display control: Figure 149
(2) Test signal management: Figure 150
4. Medal count control program start process: FIG. 128 (eighth embodiment)
5. Token count control error display process: FIG. 129 (eighth embodiment)
6. Main processing for controlling the number of medals: FIG. 130 (eighth embodiment)
(1) Main control command reception process: FIG. 131 (eighth embodiment)
7. Token count control interrupt processing: FIG. 132 (eighth embodiment)

Figure 140 is a flowchart showing the main control main processing in the ninth embodiment.
140, in step S931, the main control CPU 510 executes a game state command set process. This process is a process of storing control commands to be sent to the sub-control CPU 85, such as a complete function activation flag, RT state, the number of remaining medals during special play or AT play, in a command buffer.
In the next step S932, the main control CPU 510 executes a game start setting process, which is the process shown in FIG.

In the next step S933, the main control CPU 510 executes a bet waiting process, which is the process shown in FIG.
Next, the process proceeds to step S934, where the main control CPU 510 determines whether the current game is a replay operation (whether the symbol combination corresponding to the replay was stopped and displayed in the previous game). Here, it determines whether the value of the replay operation status flag (_FL_REPLAY) is "1," and if it is "1," it determines that a replay operation is in progress. If a replay operation is in progress, the process proceeds to step S937, and if a replay operation is not in progress, the process proceeds to step S935.
In step S935, the main control CPU 510 executes settlement processing. This processing is the processing shown in FIG. 143, which will be described later, and is processing to return the bet medals to the total medals based on the operation of the settlement switch 46. In the next step S934, betting processing is executed. This processing is the processing shown in FIG. 143, which will be described later, and is processing to execute betting processing based on the operation of the bet switch 40.
Next, the process proceeds to step S937, where the main control CPU 510 determines whether the number of bets matches the specified number (the number of bets required to start a game). In the seventh embodiment, the specified number is "3." If it is determined that the number of bets matches the specified number, the process proceeds to step S938, and if it is determined that the number of bets does not match the specified number, the process returns to step S933.

In step S938, the main control CPU 510 determines whether the start switch signal is rising (whether the start switch 41 has been operated), and if it determines that the start switch signal is rising, proceeds to step S1241, and if it determines that the start switch signal is not rising, returns to step S933. Note that in the main control interrupt processing, operation of the start switch 41 is detected, and when operation of the start switch 41 is detected, the rising signal of the start switch 41 is turned on ("1").
In step S1241, the main control CPU 510 executes a start switch acceptance process. This process is the process shown in Fig. 145, which will be described later, and includes a lottery process, turning off the status display lamp 79, etc.
In the next step S1243, the main control CPU 510 determines the push order instruction number based on the lottery result in step S1241 and stores it in the instruction number. This process is performed when the current game is during AT, the instruction function is activated, and a role with an advantageous push order (biased role) is won, and the instruction number corresponding to the advantageous push order is obtained and stored in the instruction number (_NB_ORD_INF).
Next, the process proceeds to step S1244, where the main control CPU 510 sets an effect group number. This process obtains the effect group number corresponding to the result of the lottery in step S1241 and stores it in a predetermined area of the main control RWM 512. The obtained effect group number is transmitted to the sub-control board 80.
Then, in the next step S940, the main control CPU 510 starts the rotation of the reels 31. After the rotation of the reels 31 has started, when the stop switch 42 is ready to be accepted, the main control CPU 510 executes a process of setting bits D0 to D2 of the stop acceptance information data (_PT_STOP_STS) to "1."

In step S941, the main control CPU 510 determines whether the stop switch 42 has been operated. If it determines that the stop switch 42 has been operated, the process proceeds to step S942, where the main control CPU 510 controls the reel 31 corresponding to the operated stop switch 42 to stop. Furthermore, the main control CPU 510 executes processing to set the corresponding bit of the stop acceptance information data (_PT_STOP_STS) corresponding to the operated stop switch 42 to "0."

In the next step S943, the main control CPU 510 determines whether all the reels 31 have stopped, and if it is determined that all the reels 31 have not stopped, the process returns to step S941, and if it is determined that all the reels 31 have stopped, the process proceeds to step S944. In step S944, the main control CPU 510 performs a process of determining a winning combination.
Next, the process proceeds to step S1245, where the main control CPU 510 executes a payout count signal setting process. This process is the process shown in FIG. 146, which will be described later, and is a process for setting the number of times and the output time of the payout count signal to be output to the test firing machine 600.
Then, the process proceeds to step S1246, where the main control CPU 510 executes the awarding process corresponding to the winning combination. This process is the process shown in FIG. 147, which will be described later.
Next, the flow advances to step S555, where a complete function calculation process is executed. This process involves updating the MY counter, etc., and is the process shown in FIG.
Next, the process proceeds to step S1247, where the main control CPU 510 executes a game end check process, which is the process shown in FIG.
Next, the process proceeds to step S1248, where the main control CPU 510 sets the operation status flag. This process updates the operation status flag (_FL_ACTION) and the replay operation status flag (_FL_REPLAY) depending on the operation of the reel or replay. Then, the process returns to step S931.

Fig. 141 is a flowchart showing the game start setting process of step S932 in Fig. 140, and clearly shows the process according to this embodiment in comparison with the flowchart of Fig. 109 (seventh embodiment). Note that the game start setting process includes a plurality of processes other than the process shown in Fig. 141.
First, in step S1251, the main control CPU 510 turns on the replay state identification information flag (_FL_RT_INF) (storing "FFH"). Note that in this embodiment, "FFH" is stored, but any value may be stored as long as it is information that can determine whether or not a replay state identification signal is being output.
Next, the main control CPU 510 proceeds to step S1252, where it determines whether the main control interrupt processing has occurred "4" times. If the main control interrupt processing has not occurred "4" times, it waits until the main control interrupt processing has occurred "4" times, and if it determines that the main control interrupt processing has occurred "4" times, it proceeds to step S951.
In other words, step S1252 executes a standby process (also called a "wait process") that waits until four main control interrupt processes have occurred. This process executes a standby process for 4.48 ms or more, and the reason for providing such a standby process is as follows.
In the above example, the number of times the main control interrupt process is performed as the standby process is set to "4", but this is not limited to "4".
The replay state identification signal is output when a game starts. After the output of the replay state identification signal starts, the input request lamp signal or the start ready lamp signal is turned on after a setup time of 2 ms or more has elapsed.
The input request lamp signal turns on when a game starts if the replay function is not activated (if the symbol combination corresponding to the replay was not displayed in a stopped state in the previous game). The start possible lamp signal turns on when a game starts if the replay function is activated (if the symbol combination corresponding to the replay was displayed in a stopped state in the previous game).
By setting the output timing in this way, it is possible to clearly distinguish between the replay state identification signal and the input request lamp signal or start possible lamp signal, and output them to the test firing test machine 600.

In the next step S951, the main control CPU 510 determines whether or not a replay is in progress (whether a replay was stopped and displayed in the previous game). This process is determined by whether or not the replay operation status flag (_FL_REPLAY) is "1." If it is determined that a replay is in progress, the process proceeds to step S952, and if it is determined that a replay is not in progress, the process proceeds to step S1253.
In step S952, the main control CPU 510 determines whether the VL signal is on. If the VL signal is on, the process proceeds to step S953, and if the VL signal is not on, the process loops until the VL signal is on.
In step S953, the number of medals bet in the previous game is read. This process is a process of reading the value of the bet number data (_NB_PLAY_MEDAL) of the main control RM 512. In the next step S954, the automatic bet number data is set. This process is a process of storing the number of medals read in step S953 in the automatic bet number data (_NB_REP_MEDAL) of the main control RM 512.
Next, the process proceeds to step S955, where the main control CPU 510 executes the process of lighting up the replay indicator lamp 79f. This process stores "1" in the D5 bit of the LED display data (_PT_STS_LED). As a result, in the subsequent main control interrupt process, when the LED display counter 1 reaches "00000001B," a lighting signal is output from the output port corresponding to the replay indicator lamp 79f.

Next, the process proceeds to step S956, where the main control CPU 510 executes automatic bet processing. This process stores "1" in each of the D0, D1, and D2 bits of the LED display data (_PT_STS_LED). As a result, in the subsequent main control interrupt process, when the LED display counter is "00000001B," lighting signals corresponding to the 1-bet indicator lamp 79a, 2-bet indicator lamp 79b, and 3-bet indicator lamp 79c are output from the output port.
Note that when the VL signal is off and a symbol combination corresponding to a minor win is displayed, a granting process is executed. In contrast, when a symbol combination corresponding to a replay is displayed, an automatic bet process is executed when the VL signal is on. On the other hand, when a symbol combination corresponding to a replay is displayed, and the VL signal is off, step S952 is looped. In other words, when the VL signal is off, the automatic bet process is not executed. This can prevent the player from mistakenly believing that the next game can be started immediately.
Next, the process proceeds to step S1254, where the main control CPU 510 performs processing to turn on the game start indicator lamp 79e. This processing sets the D4 bit of the LED display data (_PT_STS_LED) to "1." After the processing to turn on the game start indicator lamp 79e is executed in step S1254, when the LED display counter is "00000001B" in the main control interrupt processing, a lighting signal corresponding to the game start indicator lamp 79e is output from the output port. Then, processing according to this flowchart ends.

On the other hand, if it is determined in step S951 that the replay is not displayed as stopped and the process proceeds to step S1253, the main control CPU 510 performs processing to turn on the insertion request lamp 79d. This processing sets the D3 bit of the LED display data (_PT_STS_LED) to "1." After the processing to turn on the insertion request lamp 79d is executed in step S1253, when the LED display counter is "00000001B" in the main control interrupt processing, a lighting signal corresponding to the insertion request lamp 79d is output from the output port. Processing according to this flowchart then ends.

FIG. 142 is a flowchart showing the bet waiting process in step S933 of FIG. 140, and clearly shows the process according to this embodiment in comparison with the flowchart of FIG. 110 (seventh embodiment).
First, in step S961, the main control CPU 510 reads the bet number data (_NB_PLAY_MEDAL) and determines whether it is "1" or greater (whether medals have been bet). If the data is "1" or greater and it is determined that medals have been bet, the process proceeds to step S966. On the other hand, if the data is "0" and it is determined that medals have not been bet, the process proceeds to step S962. In the ninth embodiment, as in the seventh embodiment, it is possible to transition to setting confirmation mode when no bets have been made.
In step S962, the main control CPU 510 determines whether the front door is open and the setting key is on. If it is determined that the front door is open and the setting key is on, the process proceeds to step S1261 and subsequent setting confirmation modes; otherwise, the process proceeds to step S966. Note that the gaming machine 10 is configured so that the door switch is turned on when the front door is opened. Also, when the setting key is inserted and turned on (rotated in a predetermined direction), the setting key switch 12 is turned on.
In step S1261, the main control CPU 510 executes a process to turn off the insertion request lamp 79d. This is to inform the player that medals cannot be bet in the setting confirmation mode. This process sets the D3 bit of the LED display data (_PT_STS_LED) to "0."
In the next step S963, the main control CPU 510 executes a setting value display process. The process of step S963 performs a setting so that the current setting value can be displayed on the setting value display means 73 (7-segment LED) in Fig. 135. This display of the setting value is executed in step S1052 (LED display control) in the main control interrupt process (Fig. 127) (specific processing will be omitted in Fig. 149, which will be described later).
Next, the process proceeds to step S964, where it is determined whether the front door is open and the setting key is off. If it is determined that the front door is open and the setting key is off, the process proceeds to step S965; if not, the process loops to step S964 (setting value display state). When the process proceeds to step S965, the main control CPU 510 performs processing to end the setting value display.

Next, the process proceeds to step S1262, where the main control CPU 510 executes the process of turning on the power-on request lamp 79d. This process sets the D3 bit of the LED display data (_PT_STS_LED) to "1." This process returns the lighting state of the power-on request lamp 79d to the state it was in before the transition to the setting confirmation mode.
In the next step S966, the main control CPU 510 determines whether the complete function is activated (whether the complete function activation flag is "FFH"), whether the VL signal is off, or whether the total number of medals exceeds the upper limit ("16368") for game progress. If at least one of these conditions is met, step S966 is looped. On the other hand, if the complete function is not activated (the complete function activation flag is "00H"), the VL signal is on, and the total number of medals is equal to or less than the upper limit ("16368") for game progress, processing according to this flowchart is terminated.
As a result, when the MY counter reaches "19000" and the complete function activation flag becomes "FFH" (step S579 in FIG. 88) in the complete calculation process after the end of a game (step S555 in FIG. 140), a loop process is executed in this bet waiting process. Therefore, unless the power is turned on/off, further games cannot be played.
When the VL signal is OFF, a loop process is executed in this bet waiting process, and the game is suspended unless the VL signal is turned ON.
Furthermore, if the total number of medals exceeds the upper limit "16,368" for game progress, a loop process is executed in this bet waiting process. Therefore, unless the counting switch 47 is subsequently operated and the total number of medals becomes equal to or less than the upper limit "16,368" for game progress, the game progress is suspended.

FIG. 143 is a flowchart showing the settlement process in step S935 of FIG. 140, and clearly shows the process according to this embodiment in comparison with the flowchart of FIG. 111 (seventh embodiment).
In step S971, the main control CPU 510 determines whether the settlement switch 46 has been operated (whether the rising signal of the settlement switch has been turned on). If it determines that the settlement switch 46 has been operated, the process proceeds to step S972, and if it determines that the settlement switch 46 has not been operated, the process according to this flowchart ends.
In step S972, the main control CPU 510 reads the bet medals. This process is a process of reading the value of the bet number data (_NB_PLAY_MEDAL). Next, the process proceeds to step S973, where it is determined whether or not there are bet medals (whether the bet number data is "1" or greater). If it is determined that there are bet medals, the process proceeds to step S974, and if it is determined that there are no bet medals, the process according to this flowchart ends. In other words, if the settlement switch 46 is operated without having any bet medals, the process does not proceed to step S974 and subsequent steps, so a settlement request command is not sent and settlement processing is not executed.
In step S974, the main control CPU 510 sets a settlement request command. Next, the process proceeds to step S975, where it executes a process of waiting for reception of a request response command (here, a settlement request response command) from the medal count control CPU 520. This process is the process shown in FIG. 125.

In the next step S976, the main control CPU 510 determines whether the settlement request response command was received normally. Here, if the sent settlement request command and the received settlement request response command match, it is determined that the command was received normally. On the other hand, if the sent settlement request command and the received settlement request response command do not match, it is determined that the command was not received normally.
If it is determined that the data has been received normally, the process proceeds to step S1271, and if it is determined that the data has not been received normally, the process according to this flowchart ends.
In addition, if the settlement request response command is not received normally in step S975 (Figure 125) prior to step S976 (if the settlement request response command is not received, or if the settlement request response command is received but is not a normal value (if the VL signal is on and the settlement number is an abnormal value)), the main control error display process is executed in step S1164 (Figure 126) of Figure 125.
In step S1271, the main control CPU 510 clears the bet number data (_NB_PLAY_MEDAL) (storing "0"). In the next step S1272, the main control CPU 510 performs processing to turn off the bet display lamp. This processing sets the D0, D1, and D2 bits of the LED display data (_PT_STS_LED) to "0".
In the next step S1273, the main control CPU 510 performs processing to turn off the game start indicator lamp 79e. This processing stores "0" in the D4 bit of the LED display data (_PT_STS_LED).
Note that steps S1272 and S1273 may be executed at the same time. For example, it is possible to execute an AND operation on the LED display data (_PT_STS_LED) and "11101000B" and clear bits D0 to D2 and D4 at the same time.
Next, the process proceeds to step S1274, where the main control CPU 510 performs processing to turn on the input request lamp 79d. This processing sets the D3 bit of the LED display data (_PT_STS_LED) to "1."
In the next step S978, the main control CPU 510 sets the settlement command to be sent to the sub-control CPU 85. Then, in the next step S979, the main control CPU 510 performs control command set 1 processing. This processing writes the settlement command set in step S978 to the command buffer. As a result of this processing, the settlement command is sent to the sub-control board 80 in the next main control interrupt processing or any subsequent main control interrupt processing. Then, processing according to this flowchart ends.

FIG. 144 is a flowchart showing the bet processing in step S936 of FIG.
First, in step S991, the main control CPU 510 checks the medal count limit. This process involves reading the value of the bet count data (_NB_PLAY_MEDAL). In the next step S992, the main control CPU 510 determines whether the medal count has reached its limit. If the read bet count data is "3," it determines that the medal count has reached its limit, and proceeds to step S1283; if it determines that the medal count has not reached its limit, it proceeds to step S1281.
In step S1281, the input request lamp 79d is turned on. This process sets the D3 bit of the LED display data (_PT_STS_LED) to "1." Next, the process proceeds to step S1282, where the main control CPU 510 turns off the game start indicator lamp 79e. This process sets the D4 bit of the LED display data (_PT_STS_LED) to "0." After steps S1281 and S1282, a turn-on signal corresponding to the input request lamp 79d and a turn-off signal corresponding to the game start indicator lamp 79e are output in the LED display control of the main control interrupt process.
In the next step S994, the main control CPU 510 determines whether the bet switch 40 has been operated, and if it determines that it has been operated, proceeds to step S995, and if it determines that it has not been operated, terminates processing according to this flowchart.
In step S995, the main control CPU 510 determines whether the 1-bet switch 40a has been operated. If it is determined that the 1-bet switch 40a has been operated, the process proceeds to step S996, and if it is determined that the 1-bet switch 40a has not been operated (the 3-bet switch 40b has been operated), the process proceeds to step S997.
In step S996, the main control CPU 510 sets the number of requested bets to "1." In the next step S997, the main control CPU 510 sets the maximum number of requested bets to "3" in response to the operation of the 3-bet switch 40b. The number of bets in the bet request command is set by the processing of steps S996 and S997.

In the next step S998, a bet request command is set. Then, in the next step S975, a waiting process for a bet request response command from the medal count control is performed.
Next, the process proceeds to step S999, where the main control CPU 510 determines whether the bet request response command was received normally. If it is determined that the command was received normally, the process proceeds to step S1285, and if it is determined that the command was not received normally, the process according to this flowchart ends.
In addition, if the bet request response command is not received normally in step S975 (Figure 125) prior to this step S999 (if the bet request response command is not received, or if the bet request response command is received but is not a normal value (if the VL signal is on and the number of bets is an abnormal value)), the main control error display process is executed in step S1164 (Figure 126) of Figure 125.
In step S1285, the main control CPU 510 updates the bet number data. This process adds "1" to the value of the bet number data (_NB_PLAY_MEDAL). Next, proceeding to step S1286, the main control CPU 510 performs processing to update the values of the bet display lamps 79a to 79c. This process updates the values of bits D0 to D2 of the LED display data (_PT_STS_LED) to values corresponding to the added number of bets. For example, if the value of bits D0 to D2 of the LED display data (_PT_STS_LED) before the update was "000B", it is updated to "001B", if the value before the update was "001B", it is updated to "011B", and if the value before the update was "011B", it is updated to "111B".

Next, the process proceeds to step S1001, where the main control CPU 510 determines whether the betting process for the requested number of bets has been completed. If it is determined that the betting process has been completed, the process proceeds to step S1002. If it is determined that the betting process has not been completed, the process returns to step S1000 and continues the addition process. As a result, for example, if the number of bets before the bet was "0" and "3" is bet, the bet number data (_NB_PLAY_MEDAL) is updated sequentially from "1" to "2" to "3." Furthermore, the LED display data (_PT_STS_LED) is updated such that the D0 bit is updated from "0" to "1," then the D1 bit is updated from "0" to "1," and then the D2 bit is updated from "0" to "1."
In step S1002, the main control CPU 510 performs processing to send a bet command to the sub-control CPU 85. Note that the processing to send a bet command to the sub-control CPU 85 refers to storing the command in the command buffer (this also applies when executed in other steps). In the subsequent main control interrupt processing, the bet command is sent to the sub-control CPU 85 by processing in step S1049 of Figure 127. Then, the processing according to this flowchart ends.
On the other hand, if it is determined in step S992 that the number of medals has reached its limit and the process proceeds to step S1283, the main control CPU 510 performs a process to turn off the insertion request lamp 79d. This process is a process to set the D3 bit of the LED display data (_PT_STS_LED) to "0." Next, the process proceeds to step S1284, where the main control CPU 510 performs a process to turn on the game start indicator lamp 79e. This process is a process to set the D4 bit of the LED display data (_PT_STS_LED) to "1." The order of the processes in steps S1283 and S1284 may be reversed. Furthermore, the processes in steps S1283 and S1284 may be performed simultaneously.

FIG. 145 is a flowchart showing the start switch reception process in step S1241 in FIG.
First, in step S1351, the main control CPU 510 acquires a random number value for the lottery of winning combinations. Note that at the time of step S1351, the random number value has only been acquired, and the winning determination based on the acquired random number value has not yet been performed.
Next, the process proceeds to step S1352, where the main control CPU 510 turns off the game start indicator lamp 79e. This process sets the D4 bit in the LED display data (_PT_STS_LED) to "0."
Furthermore, in the next step S1353, the main control CPU 510 turns off the input request lamp 79d. This process sets the D3 bit in the LED display data (_PT_STS_LED) to "0".
In the next step S1354, the main control CPU 510 clears the winning number data (_NB_PAYOUT). By this process, even if the winning number was stored in the winning number data in the previous game, it is cleared at the start of the current game.
Next, the process proceeds to step S1355, where the main control CPU 510 turns off ("0") the re-game state identification information flag (_FL_RT_INF). The re-game state identification information flag is turned on in step S1251 (game start set processing) of FIG. 141. Then, when the start switch signal is detected to be on, the re-game state identification information flag is set to "0" based on the detection of the start switch signal being on, in order to turn off the re-game state identification signal. When the re-game state identification information flag becomes "0", the re-game state identification signal is not output in the main control interrupt processing (step S1343 of FIG. 150, described later).

Next, proceeding to step S1356, the main control CPU 510 executes an internal lottery (determining a winning number based on a random number) using (or based on) the random number value obtained in step S1351. Here, "using (or based on) a random number value" means not only directly using the extracted random number value, but also using the result of performing a predetermined calculation on the extracted random number value, using the result of adding or subtracting a predetermined value to the extracted random number value, or using the result of adding or subtracting another random number value to the extracted random number value. This process is a process in which the determination means of the winning combination lottery means 61 described in the first embodiment compares the random number value extracted by the random number extraction means with the lottery table to determine the winning number corresponding to the area to which the random number value belongs.
In the ninth embodiment, steps S1352 and S1353 are executed between the acquisition of the random number value and the internal lottery (determination of the winning number based on the acquired random number). As a result, when the process proceeds to the start switch acceptance process, the process of turning off the insertion request lamp 79d and the game start indicator lamp 79e is executed as soon as possible. This makes it possible to turn off the insertion request lamp signal and the start possible lamp signal as soon as possible when the start switch signal is detected to be on.

In the next step S1357, the main control CPU 510 determines whether the minimum play time (4.1 seconds) has elapsed. This process determines whether the count value of the minimum play time stored in the main control RWM 512 is 0. If it is determined that the minimum play time has not elapsed (if the count value of the minimum play time is not 0), the process waits until the minimum play time has elapsed (until the count value of the minimum play time becomes 0), and if it is determined that the minimum play time has elapsed, the process proceeds to step S1358.
In step S1358, the main control CPU 510 saves the minimum play time. This process stores "3661D" as the minimum play time of the main control RWM 512. This minimum play time is decremented by "1" for each main control interrupt process. Therefore, the minimum play time becomes "0" after "1.12 ms x 3661 = 4100.32 ms" has elapsed.
Then, the processing according to this flowchart ends.

FIG. 146 is a flowchart showing the payout count signal setting process of step S1245 in FIG.
First, in step S1311, the main control CPU 510 stores a predetermined initial value in the payout count signal output time (_ST1_OUT_CNT). As described above, the "predetermined initial value" is, for example, "5D" if one on or off signal of the payout count signal is set to "5" ms, or "45D" if one on or off signal of the payout count signal is set to "50" ms. Then, proceeding to step S1312, the main control CPU 510 stores the value of the payout number buffer (_BF_PAY_MEDAL) in register A.
In the next step S1313, the main control CPU 510 stores the doubled value of the A register value (A register value + A register value) in the payout count signal output number (_SC_MEDAL_OUT), and then ends the processing of this flowchart.
The payout count signal output time (_ST1_OUT_CNT) stored here is decremented by "1" for each main control interrupt process. Also, the value of the payout number buffer (the number of payouts for the current game) is doubled so that the payout count signal has a payout number of "1" with one pulse of the ON signal and one pulse of the OFF signal.

FIG. 147 is a flowchart showing the assignment process in step S1246 in FIG.
147, in step S1381, the main control CPU 510 acquires the value of the payout number buffer (_BF_PAY_MEDAL). Furthermore, the main control CPU 510 stores the acquired value in the E register.
Next, the process proceeds to step S1382, where the main control CPU 510 transmits a grant command to the sub-control CPU 85 (stores the command in the command buffer). The "grant command" here is a command corresponding to the total number of grants in the current game. For example, when a 10-coin minor combination is won, the grant command is a command including "10" as the number of grants.
In the next step S1383, the main control CPU 510 determines whether or not gaming media have been awarded in the current game. Here, if the E register value is not "0," it is determined that gaming media have been awarded. If it is determined that gaming media have been awarded, the process proceeds to step S1384; if it is determined that gaming media have not been awarded, the process according to this flowchart ends.
In step S1384, the main control CPU 510 sets an award request command. Here, in the seventh embodiment, as shown in FIG. 100, the award request command was "A201H," indicating the award number "1." In contrast, in the ninth embodiment, when the award number for the current game is "N," an award request command of "A20NH" is sent. For example, when the award number for the current game is "10," the command becomes "A20AH." Therefore, the main control CPU 510 sets "A2" in the D register and sends the DE register value as the award request command. Next, the process proceeds to step S975, where the main control CPU 510 waits to receive an award request response command from the medal count control CPU 520 (FIG. 125).

In the next step S1386, the main control CPU 510 determines whether the grant process cannot be accepted. Here, if the main control CPU 510 has successfully received the grant request response command, it determines that the grant process can be accepted. Note that "successfully received" corresponds to the case where the values of the grant request command and the grant request response command match.
If it is determined in step S1386 that the granting process cannot be accepted, the process returns to step S1384, and if it is determined that the granting process can be accepted, the process proceeds to step S1387. If it is determined by this process that the granting process cannot be accepted, the process returns to step S1384 again and the process of transmitting the grant request command is executed.
During the above processing, in the process of waiting for reception of a request response command from the medal count control in step S975 (FIG. 125), if steps S986 and S987 in FIG. 125 are judged as "No," and the process proceeds to step S1164, the process proceeds to the main control error display process (FIG. 126). Then, as shown in step S1169 in FIG. 126, the error state is maintained until the reset switch 14 is operated. When this error state is released, proceeding from step S975 to step S1386 in FIG. 147 is judged as "Yes" (the awarding process cannot be accepted), so the process returns to step S1384 and the awarding request command is set again. In this way, if the awarding request response command cannot be received normally, the awarding request command is repeatedly sent until the awarding request response command is received normally.
In this way, when the grant request response command cannot be received normally, the grant request command can be repeatedly sent until the grant request response command is received normally, thereby preventing the player from being disadvantaged.
In contrast, for betting processing and settlement processing, even if the request response command cannot be received normally and the betting processing or settlement processing is not executed, the player will not be disadvantaged, so there is no need to repeatedly send betting request commands or settlement request commands.

In step S1387, the main control CPU 510 saves the value of the E register in the winning number data (_NB_PAYOUT). As a result, in the main control interrupt process executed thereafter, when the value of the LED display counter 1 is "00000100B" or "00000010B", the winning number of the current game is displayed by controlling the lighting of the upper or lower digit LED of the winning number display unit 78.
Next, the process proceeds to step S1388, where the main control CPU 510 subtracts "1" from the number of wins in the special game state. This process subtracts "1" from the number of wins in the special game state stored in the main control RWM 512.
Furthermore, in the next step S13890, the main control CPU 510 subtracts "1" from the number of awards data. This process subtracts "1" from the E register value.
In the next step S1390, the main control CPU 510 determines whether the E register value has become 0. If it determines that the E register value is not 0, it returns to step S1388, and if it determines that the E register value is 0, it terminates processing according to this flowchart.
As described above, in the ninth embodiment, the value displayed in the acquisition number display section 78 is displayed immediately without being counted up, which is different from the awarding process (FIG. 114) in the seventh embodiment.

FIG. 148 is a flowchart showing the game end check processing of step S1247 in FIG.
First, in step S1291, the main control CPU 510 obtains the action status flag (_FL_ACTION) and stores it in the A register. Next, proceeding to step S1292, the main control CPU 510 generates advantageous zone bit data. This process performs a logical OR operation on the value stored in the advantageous zone flag (_FL_ADV_STS) (the D1 bit is "1" if the zone is in an advantageous zone) and the A register value, and sets the result of the operation as the A register value.
At this point, the value of the A register is
D0: Pseudo game effect in progress D1: Advantageous zone D2: Unused D3: 1BB
D4:RB
D5: Unused D6: Unused D7: Unused
In the next step S1293, the main control CPU 510 determines whether the instruction number for the current game is 0. Here, it determines whether the value of the instruction number (_NB_ORD_INF) is 0, and if it is determined that it is not 0, it proceeds to step S1294, and if it is determined that it is 0, it proceeds to step S1295.

In step S1294, the main control CPU 510 sets the instruction generation bit. This process adds "1" to the A register value (sets the D0 bit to "1"). As a result of this process, the A register value at this point is
D0: Instruction occurs D1: Advantageous zone D2: Unused D3: 1BB
D4:RB
D5: Unused D6: Unused D7: Unused

In the next step S1295, the main control CPU 510 sets a reel operation status command. This process stores "C0H" in the D register and the A register value in the E register.
Next, the process proceeds to step S1296, where the main control CPU 510 transmits two-byte data, with the D register value as the upper byte and the E register value as the lower byte, to the medal count control CPU 520. When the medal count control CPU 520 receives this two-byte data, if the upper byte data is "C0H", it can determine that the lower byte data is data for "instruction generation, advantageous zone, or role."
In the next step S1296, the main control CPU 510 obtains the value of the payout number buffer (_BF_PAY_MEDAL) and stores it in register A. The previous value in register A is cleared, and the payout number buffer value is stored in register A after the clearing.
Next, the process proceeds to step S1298, where the main control CPU 510 determines whether a replay has been stopped and displayed in the current game. This process determines whether the D0 bit of the symbol combination display flag (_FL_WIN) is "1," and if it is "1," it determines that a replay has been stopped and displayed in the current game. If it is determined that a replay has been stopped and displayed in the current game, the process proceeds to step S1299, and if it is determined that a replay has not been stopped and displayed, the process proceeds to step S1301.
In step S1299, the main control CPU 510 reads the number of bets. This process stores the value of the number of bets data (_NB_PLAY_MEDAL) in register A. Note that since the payout number buffer value for the game in which the replay was stopped and displayed is "0," the value of register A remains "0" at that point even after step S1297.

In the next step S1300, the main control CPU 510 sets the replay identification bit. This process sets "1" to bit D7 of register A.
In step S1301, the main control CPU 510 sets a game end command. This process stores the A register value in the E register, and further stores "CFH" in the D register.
Then, proceeding to step S1302, similar to step S1296, the main control CPU 510 transmits two-byte data to the medal count control CPU 520, with the D register value as the upper byte and the E register value as the lower byte.
Therefore, for example, when a game is played with a bet of "3" and a replay is displayed in a stopped state, the 2-byte data becomes "CF83H."
Also, for example, when a 3-coin small win is won, the 2-byte data will be "CF03H".
Furthermore, for example, when a 10-coin small win is won, the 2-byte data becomes "CF0AH".
As a result, when the medal count control CPU 520 receives this 2-byte data, it can determine whether a replay is displayed as stopped (the number of bets when a replay is displayed as stopped) and the number of payouts by reading the lower byte of the 2-byte data.
Next, the process proceeds to step S1303, where the main control CPU 510 performs a stoppage monitoring process. This process turns on the complete function activation flag (FFH) when the MY counter is equal to or greater than 19,000. This process corresponds to step S579 in FIG. 88 (sixth embodiment).
Next, the process proceeds to step S1304, where the main control CPU 510 performs processing to turn off the replay indicator lamp 79f. This processing sets the D5 bit of the LED display data (_PT_STS_LED) to "0." The processing according to this flowchart then ends.

Figure 149 is a flowchart showing the LED display control in step S1052 of Figure 127 (main control interrupt processing).
As described above, the main control main processing executes the lighting and extinguishing processing of the status indicator lamp 79. The lighting processing of the status indicator lamp 79 is processing for storing "1" in a predetermined bit of the LED display data (_PT_STS_LED), and the extinguishing processing of the status indicator lamp 79 is processing for storing "0" in a predetermined bit of the LED display data (_PT_STS_LED).
However, these processes do not immediately turn on or off the status indicator lamp 79. When the LED display control described below is executed in the main control interrupt process, when the LED display counter 1 indicates the timing for turning on the status indicator lamp 79, a turn-on signal and turn-off signal for the status indicator lamp 79 are output from a predetermined output port, thereby controlling the turning on or off of each of the lamps 79a to 79f of the status indicator lamp 79.
The same applies to the acquisition number display unit 78. When the LED display control is executed, when the LED display counter 1 indicates the timing for lighting up the most significant digit of the acquisition number display unit 78, a lighting signal or an extinguishing signal for the most significant digit of the acquisition number display unit 78 is output from a predetermined output port, thereby controlling the lighting up or extinguishing of each segment of the most significant digit of the acquisition number display unit 78.
Similarly, when LED display control is executed, when the LED display counter 1 is at the timing to light up the lower digits of the acquisition number display section 78, a light-up signal and an extinguishing signal for the lower digits of the acquisition number display section 78 are output from a specified output port, thereby controlling the lighting or extinguishing of each segment of the lower digits of the acquisition number display section 78.

In the ninth embodiment, output port 3 is an output port for a digit (LED) signal, and output port 4 is an output port for a segment signal. The digit signal is a signal that specifies which LED (in this embodiment, the LED of the higher digit of the acquisition number display unit 78, the LED of the lower digit of the acquisition number display unit 78, or the status display lamp 79) to light up.
for example,
Digit 1: LED of the most significant digit of the winning number display unit 78
Digit 2: LED of the lower digit of the acquisition number display unit 78
Digit 3: Status indicator lamp 79
Let's say.
The segment signal is a signal that determines which of the seven segments should be lit. The status indicator lamp 79 in this embodiment is made up of six types, and these six lamps are lit as if they were individual segments of the seven segments.
for example,
Segment A: 1 bet indicator lamp 79a
Segment B: 2 bet indicator lamp 79b
Segment C: 3 bet indicator lamp 79c
Segment D: Insertion request lamp 79d
Segment E: Game start indicator lamp 79e
Segment F: Replay indicator lamp 79f
Segment G: Unused.

First, in step S1361, the main control CPU 510 turns off output ports 3 and 4. By outputting "00000000B" from output ports 3 and 4, digit output is temporarily stopped. This prevents different lamps from appearing to be lit simultaneously (overlapping display) even for a moment when switching the lamp display (preventing afterimages).
In the next step S1362, the main control CPU 510 updates LED display counter 1. Updating LED display counter 1 involves shifting bit "1" one digit to the right. This updated value is stored in LED display counter 1 (_CT_LED_DSP1). Then, the process proceeds to step S1363.
In step S1363, the main control CPU 510 determines whether the value of the LED display counter 1 is "00000000B." If it is determined that the value is "00000000B," the process proceeds to step S1364, and if it is determined that the value is not "00000000B," the process proceeds to step S1365.

In step S1364, the main control CPU 510 initializes the LED display counter 1. Here, the value of the LED display counter 1 is set to "00000100B" and stored in the LED display counter 1 (_CT_LED_DSP1). Then, the process proceeds to step S1365.
In step S1365, the main control CPU 510 acquires the value stored in LED display counter 1 (_CT_LED_DSP1). Here, the value of LED display counter 1 is stored in the E register.
Next, proceeding to step S1336, the main control CPU 510 reads the value of the acquisition number data (_NB_PAYOUT) and stores it in register A.
In the next step S1367, the main control CPU 510 determines whether the E register value (value of LED display counter 1) is "00000100B." If it is determined to be "00000100B," the process proceeds to step S1368; otherwise, the process proceeds to step S1369.
In step S1368, the main control CPU 510 acquires the most significant digits of the acquisition count data. This process divides the A register value (acquisition count data) by 10 (decimal) and stores the quotient in the C register. Then, the process proceeds to step S1372.

On the other hand, in step S1369, it is determined whether the value of the E register (the value of the LED display counter 1) is "00000010B." If it is determined that it is "00000010B," the process proceeds to step S1370; if it is determined that it is not "00000010B," the process proceeds to step S1371.
In step S1370, the main control CPU 510 acquires the lower-order data of the number of acquisitions data. This process divides the A register value (acquired number data) by 10 (decimal) and stores the remainder in the C register. Then, the process proceeds to step S1372.
On the other hand, when the process proceeds to step S1371, the main control CPU 510 acquires the value of the LED display data (_PT_STS_LED) and stores it in register C. Then the process proceeds to step S1372.
In step S1372, the main control CPU 510 acquires segment data. Specifically, it uses the C register value and a specified LED segment table (not shown) to convert the data into data indicating which of the seven segments to light up. This segment data is then stored in the D register.

Then, in the next step S1373, the main control CPU 510 outputs a digit signal from output port 3 and a segment signal from output port 4. Specifically, the data stored in the E register (LED display counter 1) is output as a digit signal from output port 3, and the data stored in the D register (segment data) is output as a segment signal from output port 4. Then, processing according to this flowchart ends.
For example, when a digit 2 signal is output from output port 3 and segment B and C signals are output from output port 4, the LED of the lower digit of the acquisition number display unit 78 displays "1".
Also, for example, when a digit 3 signal is output from output port 3 and a segment D signal is output from output port 4, the input request lamp 79d lights up.

FIG. 150 is a flowchart showing the test signal management in step S1053 of FIG. 127 (main control interrupt processing).
First, in step S1321, the main control CPU 510 sets the start possible lamp signal and the power-on request lamp signal. This process stores the value of the LED display data (_PT_STS_LED) in the A register, performs a logical AND operation on the A register value and "00011000" (data with D3 and D4 bits set to "1"), and stores the result of this operation in the A register. As a result, data with all bits except D3 and D4 of the LED display data masked is stored in the A register.
In other words, the start possible lamp signal corresponds to the value of bit D4 of the LED display data (_PT_STS_LED), and the turn-on request lamp signal corresponds to the value of bit D3.
In the next step S1322, the main control CPU 510 determines whether the payout count signal output number (_SC_MEDAL_OUT) is 0. If it is determined that it is not 0, the process proceeds to step S1323, and if it is determined that it is 0, the process proceeds to step S1324.
In step S1323, the main control CPU 510 clears the start-ready lamp signal and the turn-on request lamp signal. This process sets the A register value to "0." For example, the A register value and the A register value are set to "0" by performing an exclusive OR (XOR) on them.
Therefore, when the number of times the payout count signal is output is "0" (when the payout count signal is not output), the start possible lamp signal and the input request lamp signal are in a state where they can be output, and when the number of times the payout count signal is output is not "0" (when the payout count signal is output), the start possible lamp signal and the input request lamp signal are not output.

In the next step S1324, the main control CPU 510 sets stop acceptance information data. The stop acceptance information data corresponds to the stop possible lamp signal described above.
Here, the following processing is executed.
1) Double the A register value (add the A register value and the A register value together, and set the resulting value as the A register value).
2) A logical sum (OR) is calculated between the value of the A register and the value of the stop acceptance information data (_PT_STOP_STS), and the calculation result is stored in the A register.
Here, by doubling the A register value in 1) above, the previous D3 bit value is shifted to D4 bit, and the D4 bit value is shifted to D5 bit. As a result, the A register value at this point is
D0: Left stop possible lamp signal D1: Middle stop possible lamp signal D2: Right stop possible lamp signal D3: 0
D4: Turn-on request lamp signal D5: Start possible lamp signal D6: 0
D7:0
This becomes:

In the next step S1325, the main control CPU 510 determines whether the replay operation status flag (_FL_REPLAY) is on ("1"). If it is determined that it is on, the process proceeds to step S1326, and if it is determined that it is not on, the process proceeds to step S1327.
In step S1326, the main control CPU 510 sets a replay signal, which sets the D6 bit of the A register to "1."
Therefore, the value of the A register at this point is
D0: Left stop possible lamp signal D1: Middle stop possible lamp signal D2: Right stop possible lamp signal D3: 0
D4: Input request lamp signal D5: Start possible lamp signal D6: Replay signal D7: 0
This becomes:
In the next step S1327, the main control CPU 510 determines whether the advantageous zone flag (_FL_ADV_STS) is "0." If it is determined that the flag is not "0," the process proceeds to step S1328; if it is determined that the flag is "0," the process proceeds to step S1329.
In step S1328, the main control CPU 510 sets information during the advantageous period. This process sets the D7 bit of the A register to "1."
Therefore, the value of the A register at this point is
D0: Left stop possible lamp signal D1: Middle stop possible lamp signal D2: Right stop possible lamp signal D3: 0
D4: Input request lamp signal D5: Start possible lamp signal D6: Replay signal D7: Advantageous zone signal
Then, in step S1329, the main control CPU 510 executes processing (OUT command) to output the value of the A register to the output port 10. As a result, the stop possible lamp signal, the input request lamp signal, the start possible lamp signal, the replay in progress signal, and the advantageous zone in progress signal are output as test signals.
After these test signals are output, the A register value is set to 0. For example, an exclusive OR (XOR) is performed between the A register value and the A register value.

In the next step S1330, the main control CPU 510 sets the RWM address of the test count signal output time. This process stores the address "F210H" of the test count signal output time (_ST2_EXP_CAL) in the HL register.
Next, the process proceeds to step S1331, where the main control CPU 510 determines whether the control status signal 11 (bit D2 of the medal count control status 2 data (_PT_PSTS2)) is off ("0"). If it is determined that it is not off, the process proceeds to step S1332; if it is determined that it is off, the process proceeds to step S1333.
In step S1332, the main control CPU 510 saves the test count signal output time. This process stores "2418D" at the address indicated by the HL register value (test count signal output time (_ST2_EXP_CAL)). The value stored here is decremented by "1" for each main control interrupt process. Therefore, the time required for "2418" to become "0" is "2418 x 1.12 (ms) = 2708.16 (ms)."
In the next step S1333, the main control CPU 510 subtracts the test count signal output time. This process subtracts "1" from the value stored in the address indicated by the HL register value (test count signal output time (_ST2_EXP_CAL)). Note that the subtraction here uses an instruction that results in "0" even if "1" is subtracted from "0."

Next, proceeding to step S1334, the main control CPU 510 determines whether the value of the test count signal output time before the subtraction in step S1333 is "0." Here, if the carry flag is "1" as a result of the subtraction in step S1333, it is determined that the value before the subtraction is "0." If it is determined that the value before the subtraction is not "0," proceed to step S1335, and if it is determined that the value before the subtraction is "0," proceed to step S1336.
In step S1335, the main control CPU 510 sets a test count signal. This process sets the D0 bit of the A register to "1."
Therefore, the value of the A register at this point is
D0: Test count signal D1: 0
D2:0
D3:0
D4:0
D5:0
D6:0
D7:0
This becomes:
In the next step S1336, the main control CPU 510 updates the payout count signal output time. This process subtracts "1" from the value stored in the payout count signal output time (_ST1_OUT_CNT). If "1" is subtracted from "0," the payout count signal output time (_ST1_OUT_CNT) is set to "44D."
In the next step S1337, the main control CPU 510 determines whether it is time to update the payout count output number. This process determines that it is time to update if the carry flag is "1" as a result of the update in step S1336 (when it changes from "0" to "44D"). If it is determined that it is time to update, the process proceeds to step S1338, and if it is determined that it is not time to update, the process proceeds to step S1339.

In step S1338, the main control CPU 510 subtracts "1" from the number of times the payout count signal has been output (_SC_MEDAL_OUT). Here, if the number of times the payout count signal has been output (_SC_MEDAL_OUT) before the subtraction is "0", a command is used that subtracts "1" to return it to "0".
Next, the process proceeds to step S1339, where the main control CPU 510 determines whether the value stored in the payout count signal output count (_SC_MEDAL_OUT) is 0. If it is determined to be 0, the process proceeds to step S1342; if it is determined not to be 0, the process proceeds to step S1340.
In step S1340, the main control CPU 510 determines whether it is time to output a payout count signal. Here, when the D0 bit value of the payout count signal output count (_SC_MEDAL_OUT) is 0, it is determined that it is time to output a payout count signal. In other words, when the D0 bit value is 0 (an even value), it is determined that it is time to output a payout count signal, and when the D0 bit value is 1 (an odd value), it is determined that it is not time to output a payout count signal. If it is determined in step S1340 that it is time to output a payout count signal, the process proceeds to step S1341; if it is determined that it is not time to output a payout count signal, the process proceeds to step S1342. In step S1341, the main control CPU 510 sets a payout count signal. This process stores "1" in the D1 bit of the A register.
Therefore, the value of the A register at this point is
D0: Test count signal D1: Dispense count signal D2: 0
D3:0
D4:0
D5:0
D6:0
D7:0
This becomes:
Next, the process proceeds to step S1342, where the main control CPU 510 executes processing (OUT command) to output the A register value to the output port 11.
By this processing, the test count signal and payout count signal are output to the test firing test machine 600 as test signals.

Next, the main control CPU 510 proceeds to step S1343, where it determines whether the replay state identification information flag (_FL_RT_INF) is on (FFH). If it determines that the replay state identification information flag is on, it proceeds to step S1345, and if it determines that the replay state identification information flag is not on (is "0"), it proceeds to step S1344.
In step S1344, the main control CPU 510 sets a condition device signal. Details of this process will be omitted, but "0" data, reel condition device signal data, or winning and replay condition device signal data is set according to a predetermined timer value. When it is time to output reel condition device signal data as a test signal, the data of the reel condition device number (_NB_CND_BNS) is read and stored in the A register. Also, when it is time to output winning and replay condition device signal data, the data of the winning and replay condition device number (_NB_CND_NOR) is read and stored in the A register.
On the other hand, when the process proceeds from step S1343 to step S1345, the main control CPU 510 reads the RT state number (_NB_RT_STS) as a re-play state identification signal and stores it in register A. For example, when the current RT is RT1, the RT state number (_NB_RT_STS) is, for example, "00000001B," so this data is read and stored in register A.
Next, proceeding to step S1346, the main control CPU 510 executes processing (OUT command) to output the A register value to the output port 12.
By this process, the condition device signal or the replay state identification signal is output as a test signal to the test firing test machine 600. Then, the process according to this flowchart ends.

As described above, the payout count signal of this embodiment has the following features.
<Relationship between payout count signal and other processes>
As shown in the main control main processing (FIG. 140), the payout count signal set in step S1245 is executed before the awarding processing in step S1246.
In the awarding process of step S1246 (FIG. 147), an awarding command is sent to the sub-control CPU 85 (step S1382). Also, an awarding request command is sent to the medal count control CPU 520, and when an awarding request response command is normally received ("No" in step S1386), the awarding process is executed.
Therefore, the main control main process for outputting the payout count signal is executed before the main control main process for outputting the award sound by the sub-control CPU 85 and for executing the update process of the medal count display unit 121 by the medal count control CPU 520.

<Relationship between the payout count signal, the start possible lamp signal, and the input request lamp signal>
In the test signal management shown in Figure 150, the start possible lamp signal and the input request lamp signal are first set in step S1321, and when the number of times the payout count signal is output is "0" (when the payout count signal is not output (when the output of the payout count signal has been completed or when the payout count signal is not output)), processing to output the start possible lamp signal and/or the input request lamp signal can be executed, and when the number of times the payout count signal is output is not "0" (when the payout count signal is output (when the output of the payout count signal has not been completed)), processing to output the start possible lamp signal and/or the input request lamp signal is not executed.
Therefore, the payout count signal and the start possible lamp signal or the input request lamp signal are not outputted at the same time.

<When an error occurs because the request response command is not received correctly while the payout count signal is being output>
When a small combination with a payout is won, a granting process is performed in step S1246 in Fig. 140. In the granting process (Fig. 147), a grant request command is set (step S1384), and a grant request response command is awaited in step S975. If the grant request response command is not received normally, a main control error display process is performed in step S1164 in Fig. 125. When the main control error display process is performed, the process waits for the reset switch 14 to be operated in step S1169 in Fig. 126.
In this situation, even while the main control error display processing is being executed because the grant request response command cannot be received normally, the main control interrupt processing (Figure 127) is executed every "1.12" ms, and a payout count signal is output in the test signal management (step S1053).
Therefore, regardless of whether the payout request response command is received normally or not, the process for outputting the payout count signal is executed.
Then, when the award request response command is not received normally, the medal count control CPU 520 does not update the display of the medal count display unit 121. In other words, the process for outputting the payout count signal is executed regardless of whether the display of the medal count display unit 121 is updated or not, thereby reducing the burden on information processing. Similarly, when the award request response command is not received normally, a main control error display state is entered, but the process for outputting the payout count signal is executed even while the main control error display state is entered, thereby reducing the burden on information processing.
The same applies when an error occurs because a bet request response command or a settlement request response command is not received properly while the payout count signal is being output (before the output of the payout count signal is completed). Regardless of whether the bet request response command or the settlement request response command is received properly, the process for outputting the payout count signal is executed.

<When the VL signal turns off while the payout count signal is being output>
After the processing for outputting the payout count signal is started, the loop processing of the main control main processing proceeds to bet waiting processing (step S933 in Figure 140 and Figure 142), and if the VL signal is off, it enters a waiting state of step S966 in Figure 142 (loop processing that waits until the VL signal turns on; in other words, processing that interrupts the progress of the main control main processing).However, even if it enters such a waiting state, the main control interrupt processing is executed, so the processing for outputting the payout count signal is executed.
When the VL signal is turned off and the standby state shown in step S966 in FIG. 142 is entered, the bet process cannot be executed.
<Relationship between payout count signal and unrecoverable error>
If a setting value error or built-in random number error occurs while the payout count signal is being output (before the output of the payout count signal is completed) ("Yes" in step S1173 or S1175 in Figure 127), an unrecoverable error will occur (step S1176).
An unrecoverable error is a serious error that does not normally occur. Therefore, when an unrecoverable error occurs, processing based on abnormal data (such as updating the main control RWM 512 data based on the input signal from the input port 51, sending a control command to the sub-control board 80, or control based on the signal output from the output port 52 based on the data from the main control RWM 512) is not executed. Therefore, when an unrecoverable error occurs, the main control interrupt processing is not executed, and the processing for outputting the payout count signal is stopped.
If an irrecoverable error occurs while the payout count signal is being output as an on signal, the output port for the test signal will not switch unless the power is turned off, and the payout count signal will maintain the signal state (on signal) from the previous main control interrupt processing.
Similarly, if an irrecoverable error occurs while the payout count signal is being output as an off signal, the output port for the test signal will not switch unless the power is turned off, and the payout count signal will maintain the signal state (off signal) from the previous main control interrupt processing.
On the other hand, if a process for clearing the output port of the test signal is executed when an unrecoverable error occurs, the payout count signal becomes an OFF signal.

Also, if an unrecoverable error occurs and processing is performed to set "FFH" to the output port of the test signal, the payout count signal becomes an ON signal.
When an unrecoverable error occurs, the power is turned off, and when the power is then turned on in a state that involves transition to the setting change mode, the process proceeds to step S2731 in FIG. 124 and the initialization process is executed.
When the initialization process is executed, the data stored in the main control RWM 512 is initialized, and the data on the number of times the payout count signal is output (_SC_MEDAL_OUT) and the payout count signal output time (_ST1_OUT_CNT) are also cleared.
In this way, if an irrecoverable error occurs before the output of the payout count signal is completed and the data for the payout count signal output count (_SC_MEDAL_OUT) and payout count signal output time (_ST1_OUT_CNT) are not "0", when you return via the setting change mode, the data for the payout count signal output count (_SC_MEDAL_OUT) and payout count signal output time (_ST1_OUT_CNT) will become "0". Therefore, a payout count signal based on the values of the payout count signal output count (_SC_MEDAL_OUT) and payout count signal output time (_ST1_OUT_CNT) before the irrecoverable error occurred will not be output.
This allows the test firing machine 600 to know that an unrecoverable error has occurred.

In addition, when the normal power-off process is executed while the payout count signal is being output (before the output of the payout count signal is completed), the data for the number of payout count signal outputs (_SC_MEDAL_OUT) and the payout count signal output time (_ST1_OUT_CNT) is maintained (backed up), so when the power is turned on thereafter, the payout count signal is output based on the values of the number of payout count signal outputs (_SC_MEDAL_OUT) and the payout count signal output time (_ST1_OUT_CNT).
However, if an error (RWM abnormality) occurs in the main control RWM 512 when the power is turned on ("Yes" in step S2708 in FIG. 124), an unrecoverable error occurs (step S2801). In this case, the main control interrupt process will not be executed thereafter unless the unrecoverable error is resolved, so the payout count signal will not be output. Furthermore, when the unrecoverable error is resolved, the initialization process is executed as described above before that, so the payout count signal based on the values of the payout count signal output count (_SC_MEDAL_OUT) and payout count signal output time (_ST1_OUT_CNT) before the unrecoverable error occurred will not be output.

<Relationship between payout count signal and setting confirmation mode>
If the bet waiting process is started while the payout count signal is being output (before the output of the payout count signal is completed), and the front door is opened and the setting key is turned on, the process will move to the setting confirmation mode as shown in Figure 142.
In this way, even if the mode is switched to the setting confirmation mode while the payout count signal is being output (before the output of the payout count signal is completed), the process for outputting the payout count signal continues.
In the example of Figure 142, the input request lamp 79d is turned off during the setting confirmation mode, so even if the output of the payout count signal is completed during the setting confirmation mode, the input request lamp signal is not output.
However, this is not limiting, and the input request lamp 79d may remain lit during the setting confirmation mode, in which case the input request lamp signal is output after the output of the payout count signal has been completed in the setting confirmation mode.
Furthermore, if a specified number of coins is bet while the payout count signal is being output, and the game start indicator lamp 79e is turned on, and then the mode shifts to the setting confirmation mode, the game start indicator lamp 79e will be turned off. Therefore, in this case, even after the output of the payout count signal is completed, the start possible indicator lamp signal will not be output.

<If you switch to setting change mode before the payout count signal is fully output>
If the power is turned off while the payout count signal is being output (before the output of the payout count signal is completed) and then turned on with the setting key turned on, the process proceeds to step S2731 via step S2711 in Figure 124, and initialization processing of the main control RWM 512 for when setting changes start is executed. In this initialization processing, the payout count signal output number (_SC_MEDAL_OUT) and payout count signal output time (_ST1_OUT_CNT) of the main control RWM 512 are also initialized.
Therefore, when returning from the setting change mode, the payout count signal output number (_SC_MEDAL_OUT) and the payout count signal output time (_ST1_OUT_CNT) are both stored as "0", so the payout count signal is not output.

<Relationship between payout count signal and replay stop display>
During play when the replay is stopped and displayed, the payout number buffer (_BF_PAY_MEDAL) is "0", so the number of payout count signal outputs (_SC_MEDAL_OUT) is "0" (in Figure 150, step S1322 is "Yes"), and no payout count signal based on that play is output.
Furthermore, during play when the replay is stopped, the payout number buffer (_BF_PAY_MEDAL) is "0," so during the awarding process in Fig. 147, step S1383 becomes "No," and an award request command is not sent to the medal count control CPU 520. As a result, the medal count display unit 121 is not updated (incremented) at the end of play when the replay is stopped.
Furthermore, the main control CPU 510 sends a game end command to the medal count control CPU 520 during the game end check process (step S1301 in Figure 148), and when a replay stop is displayed, it sets the replay identification bit to "1" and sends a game end command with the payout number as the bet number (steps S1298 to S1301 in Figure 148).
On the other hand, based on the stopped display of the replay, the medal count control CPU 520 executes processing to output information on the number of bets for the game as the payout number as game information for the hole control/fraud monitoring information.
Here, the hall control/fraud monitoring information includes "game information" which is not shown in FIG.
Furthermore, one of the game information includes "count information." Here, the count information transmits the payout number. The payout number refers to the payout number for the game. When a replay is activated, the specified number for the game is transmitted as the payout number.
In this way, when the replay is activated, the payout count signal (test signal) does not transmit the specified number as the payout number. On the other hand, when the replay is activated, information is transmitted in which the specified number is the payout number as the game information of the hall control and fraud monitoring information.
Therefore, the output of the test signal when the replay is activated differs from the output of the hall control/fraud monitoring information.
In the ninth embodiment, the transmission of the gaming machine information notification including the hole control and fraud monitoring information is executed in the gaming machine information management of the medal count control interruption process (step S244 in FIG. 132). This process corresponds to the process in FIG. 94, and the hole control and fraud monitoring information is output in step S275 in FIG.

Next, the control process of the payout count signal in this embodiment will be described.
FIG. 151 is a time chart showing the output of the payout count signal and the input request lamp signal, and the timing of the input request lamp lighting process and the lighting signal output process.
As shown in FIG. 151, the payout count signal is a signal consisting of one pulse consisting of an on signal and an off signal, which corresponds to the number of medals "1".
In step S944 of Figure 140, a winning determination process is executed, and if it is determined that a payout has been made (a small winning combination has been made), the number of times and the output time of the payout count signal are set in the next step S1245 (Figure 146).
The number of payout count signal outputs is counted as "1" for one ON signal and "1" for one OFF signal. Therefore, the number of payout count signal outputs per medal number "1" is "2", and the total number of payout count signal outputs is "number of payouts x 2". For example, if a small combination with a payout number of "3" is won, the number of payout count signal outputs will be "6".

A predetermined initial value "N" is also set as the output time of the payout count signal. The number of payout count signal outputs is decremented by "1" for each main control interrupt process, and when the output time of the payout count signal becomes "0" after decrementing by "1," one on signal or one off signal of the payout count signal ends. Therefore, the output time of one on signal or one off signal of the payout count signal is "N x 1.12 (ms)." Note that in Figure 151, the output time of one on signal or one off signal of the payout count signal is illustrated as "50" ms. The predetermined initial value "N" in this case is "45D."

During the main control main processing of Figure 140, when the payout count signal output time and the number of payout count signal outputs are set in step S1245 (Figure 146), the payout count signal is output from output port 11 in the test signal management (Figure 150) of step S1053 of the subsequent main control interrupt processing (Figure 127).
The maximum number of payouts under the Entertainment and Amusement Business Act is 15, so if the output time of one on signal or one off signal of the payout count signal is 50 ms (if the specified initial value N is 45D), the payout count signal output time will be 15 x 2 x 45 x 1.12 (ms) = 1512 (ms).
Similarly, when the maximum payout number is "15" and the output time of one on signal or one off signal of the payout count signal is "5" ms (when the specified initial value "N" is "5D"), the payout count signal output time is "15 x 2 x 5 x 1.12 (ms) = 168 (ms)".
Here, the output of the payout count signal must be completed by the time the next game starts (by the time the throw-in request lamp signal or the start possible lamp signal is turned on) after all reels 31 have stopped. In other words, the output period of the payout count signal and the output period of the throw-in request lamp signal or the start possible lamp signal must not overlap.
Here, if all reels 31 are stopped and the loop process of the main control main process is executed while the payout count signal is being output, the process returns to step S931 in Fig. 140 before the output of the payout count signal is completed. In this case, in Fig. 141 (game start setting process), it is necessary to perform the process of turning on the insertion request lamp 79d in step S1253, but the output of the payout count signal may not be completed at this point.

As described above, the output of the insertion request lamp signal (or start possible lamp signal) must be performed after the output of the payout count signal is completed. Therefore, if the insertion request lamp 79d is turned on in accordance with the output of the insertion request lamp signal, there is a risk that the timing of turning on the insertion request lamp 79d at the start of a game will be delayed.
Similarly, after returning to step S931 in the loop processing of the main control main processing, when the specified number of bets has been placed, it is necessary to turn on the game start indicator lamp 79e.
On the other hand, since the start possible lamp signal needs to be output after the output of the payout count signal for the previous game is completed, there is a possibility that the start possible lamp signal cannot be output when the lighting conditions for the game start indicator lamp 79e are satisfied.

Therefore, in this embodiment, regardless of the output process of the insertion request lamp signal or the output process of the start possible lamp signal, the lighting process of the insertion request lamp 79d and the lighting process of the game start indication lamp 79e are executed.
By doing this, it is possible to prevent delays in the progress of the game (main control main processing).
However, the output process of the input request lamp signal and the start possible lamp signal is executed after the output of the payout count signal is completed, in order to avoid simultaneous output of the payout count signal and the input request lamp signal or the start possible lamp signal.
Specifically, in the test signal management of Figure 150, the start possible lamp signal and the input request lamp signal are set in step S1321, and in step S1322 it is determined whether the number of times the payout count signal has been output is "0", and if it is not "0", the process proceeds to step S1323, where the start possible lamp signal and the input request lamp signal set in step S1321 are cleared.
On the other hand, when the current game ends and the next game starts, a game start setting process is executed in step S932 of Fig. 140 (main control main process), and in the game start setting process, a process of lighting up the insertion request lamp 79d is executed in step S1253, as shown in Fig. 141. This lighting process is independent of whether the payout count signal output number (_SC_MEDAL_OUT) is "0" or not.
When "1" is stored in the D3 bit of the LED display data (_PT_STS_LED) in step S1253, thereafter, in step S1371 of the LED display control (FIG. 149) of the main control interrupt processing (FIG. 127) where the LED display counter 1 is "00000001B", the value of the LED display data (_PT_STS_LED) is acquired and a signal to light up the input request lamp 79d is output.

As a result, as shown in FIG. 151, after the output of the payout count signal is completed, the input request lamp signal is output.
On the other hand, regardless of whether the payout count signal is being output (before the output of the payout count signal is completed), when the main control main processing returns to the beginning of the sleep processing, the lighting process of the input request lamp 79d (the process of storing "1" in the D3 bit of the LED display data (_PT_STS_LED)) is executed.
In the subsequent main control interrupt process, when the LED display counter 1 reaches "00000001B", a process for outputting a lighting signal for the input request lamp 79d is executed.
Therefore, there may be cases where the lighting process of the input request lamp 79d and the output process of the lighting signal are executed before the output of the payout count signal is completed.
On the other hand, as shown in Figure 150, even while the payout count signal is being output (before the output of the payout count signal is completed), it is possible to output the replay signal, the advantageous zone signal, the test counting signal, the condition device signal, and the replay state identification signal.

FIG. 152 is a time chart showing an example in which a specified number of bets are executed while the payout count signal is being output (before the output of the payout count signal is completed).
While the payout count signal is being output (before the output of the payout count signal is completed), the process returns to the beginning of the main control process, and when the specified number of bets is processed, the deposit request lamp 79d is turned off and the game start indicator lamp 79e is turned on. If the output of the payout count signal is then completed, the deposit request lamp 79d is turned off at that point, so the deposit request lamp signal is not output. Also, since the game start indicator lamp 79e is turned on, a start possible lamp signal is output.
When the input request lamp 79d is off and the game start indicator lamp 79e is on, the D3 bit of the LED display data (_PT_STS_LED) becomes "0" and the D4 bit becomes "1", and this LED display data is read in step S1321 of FIG. 150. When the payout count signal is "0"("Yes" in step S1322), a test signal is output in step S1329 indicating that the start possible lamp signal is on (the input request lamp signal is off).

FIG. 153 is a time chart showing an example in which the next game is started while the payout count signal is being output (before the output of the payout count signal is completed).
If a specified number is bet while the payout count signal is being output, "0" is stored in the D3 bit of the LED display data (_PT_STS_LED) in step S1283 of FIG.
When the start switch 41 is operated again, "0" is stored in the D4 bit of the LED display data (_PT_STS_LED) in step S1352 of FIG.
Therefore, when the output of the payout count signal is completed, in step S1321 of Figure 150, the input request lamp signal becomes "0" and the start possible lamp signal becomes "0", so the input request lamp signal becomes an off signal (not output), and the start possible lamp signal also becomes an off signal (not output).

FIG. 154 is a time chart showing an example in which the number of times the payout count signal is to be output for the next game is determined while the payout count signal for the current game is being output (before the output of the payout count signal is completed).
As mentioned above, the maximum number of payouts is "15", and if the output time of one on signal or one off signal of the payout count signal is "50" ms (when the specified initial value "N" is "45D"), the output time of the payout count signal is "15 x 2 x 45 x 1.12 (ms) = 1512 (ms)".
On the other hand, in this embodiment, the shortest time between games is "4.1 seconds," as shown in steps S1357 and S1358 of FIG.
Therefore, in this embodiment, the number of times the payout count signal is output for the next game is not stored before the payout count signal for the current game is completed.
However, for example, if the minimum time between games can be specified to be shorter than 4.1 seconds, or if the time for one on or off signal of the payout count signal is set to be longer than 50 ms, or if the processing behaves in an unintended manner and the main control RWM512 that manages the payout count signal (for example, the number of payout count signal outputs (_SC_MEDAL_OUT) or the payout count signal output time (_ST1_OUT_CNT)) is not updated at the normal timing, there is a possibility that the number of payout count signal outputs for the next game will be stored before the output of the payout count signal for the current game is completed.
If such a case occurs, the new number of times the dispensing count signal is output is overwritten on the previous number of times the dispensing count signal was output. This prevents the number of times the dispensing count signal was output from being added up and the number of dispenses from exceeding "15". In other words, it prevents a dispensing count signal exceeding "15" from being output, thereby preventing the testing institution from becoming suspicious.
If a power outage occurs while the dispense count signal is being output, the number of dispense count signal outputs (_SC_MEDAL_OUT) is backed up, and the next time the power is turned on, the backed up number of dispense count signal outputs (_SC_MEDAL_OUT) is stored. Therefore, after the next power-on, it is possible to output dispense count signals that have not been output. In other words, it is possible to output the correct number of dispense count signals before and after the power outage.

The same applies when the output time of one ON signal or one OFF signal of the payout count signal is "5" ms (when the predetermined initial value "N" is "5D").
In this case, the output time of the payout count signal is "15 x 2 x 5 x 1.12 (ms) = 168 (ms)".
On the other hand, the shortest time between games in this embodiment is "4.1 seconds" as described above.
Therefore, in this embodiment, the number of times the payout count signal is output for the next game is not stored before the payout count signal for the current game is completed.
However, for example, if the specification allows for the shortest time between games to be shorter than "4.1 seconds", or if the processing behaves in an unintended manner and the main control RWM512 that manages the payout count signal (for example, the number of payout count signal outputs (_SC_MEDAL_OUT) and the payout count signal output time (_ST1_OUT_CNT)) is not updated at the normal timing, there is a possibility that the number of payout count signal outputs for the next game will be stored before the output of the payout count signal for the current game is completed.
If such a case occurs, the new number of times the dispensing count signal is output is overwritten on the previous number of times the dispensing count signal was output. This prevents the number of times the dispensing count signal was output from being added up and the number of dispenses from exceeding "15". In other words, it prevents a dispensing count signal exceeding "15" from being output, thereby preventing the testing institution from becoming suspicious.
If a power outage occurs while the payout count signal is being output (before the output of the payout count signal is completed), the number of payout count signal outputs (_SC_MEDAL_OUT) is backed up, and the next time the power is turned on, the backed up number of payout count signal outputs (_SC_MEDAL_OUT) is stored. Therefore, after the next power is turned on, it is possible to output a payout count signal that has not been output. In other words, it is possible to output the correct number of payout count signals, both before and after the power outage.

Although the ninth embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and various modifications such as those described below are possible.
(1) Although not explained in the ninth embodiment, an LED display counter 2 (a counter that completes one cycle in five medal count control interrupt processes) is provided in the usage area of the medal count control RWM 522, and the dynamic lighting of the medal count display unit 121 (a five-digit LED) is performed by the medal count control interrupt process (step S1147 in Figure 132).
In addition, an LED display counter 3 (a counter that completes one cycle in four medal count control interrupt processes) is provided outside the usage area of the medal count control RWM 522, and the dynamic lighting of the role ratio monitor 113 (four-digit LED) is performed by the medal count control interrupt process (step S1149 in Figure 132).

(2) It is also possible to control the lighting of the acquisition number display section 78 and the status display lamp 79 without providing the LED display counter 1.
For example, it is possible to execute all of the following a) to c) in one LED display control.
a) Obtain the most significant digit data of the number of acquisitions, obtain the segment data corresponding to that data, output the most significant digit signal of the number of acquisitions display unit 78 from output port 3, and output the most significant segment signal of the number of acquisitions display unit 78 from output port 4.
b) Obtain the lower digit data of the number of acquisitions, obtain the segment data corresponding to that data, output the lower digit signal of the number of acquisitions display unit 78 from output port 3, and output the lower digit segment signal of the number of acquisitions display unit 78 from output port 4.
c) Obtain the LED display data (_PT_STS_LED), obtain the segment data corresponding to that data, output the digit signal of the status indicator lamp 79 from output port 3, and output the segment signal of the status indicator lamp 79 from output port 4.
By configuring in this manner, there is no need to provide an LED display counter 1, which saves the capacity of the main control RWM 512, and there is no need to provide update processing or initial processing for the LED display counter 1, which simplifies and speeds up main control interrupt processing.

(3) In the bet waiting process of Fig. 142, it is also possible not to turn off the insertion request lamp 79d even when the mode is shifted to the setting confirmation mode. In this case, the processes of steps S1261 and S1262 are not executed.
In addition, the setting confirmation mode may be enabled even when a bet has been placed. In this case, when the setting confirmation mode is entered when less than the specified number of bets has been placed (when the deposit request lamp 79d is lit), the deposit request lamp 79d may or may not be turned off.
Furthermore, if the setting confirmation mode can be entered even when a bet has been placed, and the setting confirmation mode is entered when the specified number of bets has been placed and the game start indicator lamp 79e is on, the game start indicator lamp 79e is turned off. In this case, the game start indicator lamp 79e is turned off in step S1261 (the D4 bit of the LED display data (_PT_STS_LED) is set to "0"), and the game start indicator lamp 79e is turned on in step S1262 (the D4 bit is set to "1").
(4) If an unrecoverable error state occurs during output of the payout count signal, a process may be executed to uniformly turn on the payout count signal.
Alternatively, if an unrecoverable error state occurs during output of the payout count signal, a process may be executed to uniformly turn off the payout count signal.

(5) In the ninth embodiment, the specified number is set to "3," but it is not limited to this and may be set to "1" or "2." Furthermore, the specified number may be different for each gaming state, for example, between the normal gaming state and the special gaming state (the role activation state (bonus activation state)). For example, the specified number may be set to "3" in the normal gaming state and "1" in the special gaming state.
Furthermore, the specified number is not limited to one, and multiple numbers may be set. For example, the specified number in a normal game may be set to "1,""2," or "3," and the game may be started at any of the specified numbers.
Here, when there are multiple types of prescribed numbers, and the maximum number of the prescribed numbers ("3" in the above example) is referred to as the "maximum prescribed number",
a) If the number of bets is less than the maximum specified number, the insertion request lamp 79d is turned on. However, since a game can be started even if the number of bets is less than the maximum specified number, the game start indicator lamp 79e is also turned on.
b) If the number of bets is less than the maximum specified number, the insertion request lamp 79d is turned on. On the other hand, in order to prompt the player to insert the maximum specified number, the game start indicator lamp 79e is turned off, although the game itself can be started.
c) Even if the number of bets is not the maximum specified number, the game itself can be started, so the game start indicator lamp 79e is turned on. On the other hand, when the game start indicator lamp 79e is turned on, the insertion request lamp 79d is turned off.
Either of the above may be used.
The above example is irrelevant to whether or not the payout count signal is being output.
On the other hand, while the payout count signal is being output, the input request lamp signal and the start possible lamp signal are not output.
After the output of the payout count signal is completed, in any of the above examples a) to c), additional medals can be inserted to reach the maximum specified number, and since it is possible to start playing even if the maximum specified number is not reached, both the insertion request lamp signal and the start possible lamp signal are output. In this case, in the test signal management of Figure 150, 1329 outputs a test signal in which both the D3 bit (insertion request lamp signal) and the D4 bit (start possible lamp signal) are "1".

(6) In the ninth embodiment, the terms "insertion request lamp 79d" and "insertion request lamp signal" are used, but "insertion" and "bet" are synonymous. Therefore, the "insertion request lamp 79d" may be referred to as the "bet request lamp 79d," and the "insertion request lamp signal" may be referred to as the "bet request lamp signal."
In other words, a "deposit" may be referred to as a "bet," or a "bet" may be referred to as a "deposit."
Furthermore, a "request" may be referred to as an "indication." This allows the terms "insertion indicator lamp,""bet indicator lamp,""insertion indicator lamp signal," and "bet indicator lamp signal" to be used.
The "closing request lamp 79d" is also referred to as the "insert lamp 79d." Therefore, the "closing request lamp signal" may be referred to as the "insert lamp signal."
Furthermore, the "prescribed number" refers to the number of bets that can be made to start (execute) a game in question, but the "prescribed number" may also be referred to as the "number of bets" or the "number of insertions."
However, "inserting gaming media (electronic medals)" does not mean tossing medals in, but rather refers to betting gaming media (electronic medals) (betting for the current game).
(7) In the ninth embodiment, the lamp is called the "game start indicator lamp 79e," and the test signal corresponding to the game start indicator lamp 79e is called the "start possible lamp signal."
However, the present invention is not limited to this, and the "game start indicator lamp 79e" may be called the "start possible indicator lamp 79e." On the other hand, the "start possible indicator lamp signal" may be called the "game start indicator lamp signal."

(8) Furthermore, "granting" and "paying out" are synonymous. Therefore, the "granting process" may be referred to as the "paying out process," the "granting request command" may be referred to as the "paying out request command," and the "granting request response command" may be referred to as the "paying out request response command."
On the other hand, the "payout number buffer" may be referred to as the "award number buffer," the "payout count signal" may be referred to as the "award count signal," the "payout count signal output time" may be referred to as the "award count signal output time," and the "number of payout count signal outputs" may be referred to as the "number of award count signal outputs."
In other words, "granting" may be referred to as "paying out," and vice versa.
However, "paying out game media (electronic medals)" does not mean paying out medals, but rather means adding the number of game media (electronic medals) awarded (payout number) for the current game to the total number of medals in the medal count control RWM522 (and further, updating the display on the medal count display unit 121).

(9) As described above, even if an error occurs during the process of outputting the payout count signal due to the request response command not being received correctly, or if the VL signal is turned off, the process of outputting the payout count signal can be continued.
Furthermore, not limited to the above errors, when a recoverable error occurs during the execution of the process for outputting the payout count signal, the process for outputting the payout count signal may generally be allowed to continue.
For example, opening the front door of the gaming machine 10 results in a door open error (a recoverable error), but even during the door open error, processing for outputting a payout count signal can be executed.
In the case of gaming machines that use medals as tangible objects, when a recoverable error occurs, the drive of the hopper is stopped, and therefore the process for outputting a medal payout count signal during a recoverable error is not executed.
In contrast, a smart gaming machine such as that of the present invention does not have a hopper, so it is possible to continue processing to output a medal payout count signal even during a recoverable error.

(10) Although not shown in Figure 135, each bet switch (1 bet switch 40a and 3 bet switch 40b in the example of Figure 135) is provided with a bet lamp. Here, the lamp of the 1 bet switch 40a is referred to as the "1 bet lamp," and the lamp of the 3 bet switch 40b is referred to as the "3 bet lamp."
When the operation of the 1-bet switch 40a is valid, the 1-bet lamp is turned on, and when the operation of the 1-bet switch 40a is not possible, the 1-bet lamp is turned off.
Similarly, when the operation of the 3-bet switch 40b is valid, the 3-bet lamp is lit, and when the operation of the 3-bet switch 40b is not possible, the 3-bet lamp is turned off.
In the case where the bed lamps as described above are provided, when the insertion request lamp 79d is lit, at least one of the 1 bed lamp and the 3 bed lamp can be lit.
On the other hand, when the input request lamp 79d is off, both the bed 1 lamp and the bed 3 lamp are turned off.
The bed lamp may be turned on or off by either the main control side or the sub-control side.
(11) After the power supply to the gaming machine 10 is turned on, if the VL signal has not yet been detected as being on (if the VL signal has been detected as being off), the image display device 23 can display an image such as "Preparing for connection." Under these circumstances, no error (warning) sound is output. Thereafter, if the VL signal is detected as being on, the image display can be terminated, and a screen related to the game is displayed. Here, "a screen related to the game" refers to a normal screen, such as a game standby screen, a bet waiting screen, a screen displaying game information (e.g., the number of bets), or, if a power outage occurs during a specific game (in a special game mode or during AT), a specific game screen prior to the power outage (the same applies below).
On the other hand, after the power of the gaming machine 10 is turned on, if the VL signal is detected to be on and then the VL signal is detected to be off, an image such as "Connection Abnormal" can be displayed on the game screen. Furthermore, in this situation, an error (warning) sound can be output.
Thereafter, when it is detected that the VL signal is turned on, the image display and the error (warning) sound are terminated, and the display of the game-related screen is restored. The process of terminating the "Connection Abnormal" image display and the error (warning) sound may be performed automatically, or may be performed by some operation (for example, by operating the reset switch 14).
The main control board 50 detects whether the VL signal is on or off. When the main control board 50 detects whether the VL signal is on or off, it sends a command indicating whether the VL signal is on or off to the sub-control board 80. When the sub-control board 80 receives this command, it executes the notification control described above according to the situation at the time the command was received.

Tenth Embodiment
The tenth embodiment relates to the operation mode when the counting switch 47 is operated.
The tenth embodiment will be described below with reference to the drawings.
Figure 155 is a block diagram of the gaming machine 10 in the tenth embodiment, which adds a door switch 17, a push button 86, a push button lamp 88, and a cross key 87 to Figure 135 (ninth embodiment).
Also, Figure 156 is a front view of the gaming machine 10 in the tenth embodiment.
Note that Figure 156 is a front view of the gaming machine 10, but the control panel 16c is shown in plan view.

In Fig. 155, as in Fig. 135, two one-chip microprocessors are mounted on the main control board 50, one of which is a one-chip microprocessor for main control and the other is a one-chip microprocessor for medal count control. Also, one one-chip microprocessor for sub-control (performance control) is mounted on the sub-control board 80.
The one-chip microprocessor for main control includes a main control CPU 510, a main control ROM 511, and a main control RWM 512 (built-in memory).
The one-chip microprocessor for medal count control includes a medal count control CPU 520, a medal count control ROM 521, and a medal count control RWM 522 (built-in memory).
Furthermore, the one-chip microprocessor for sub-control includes a sub-control CPU 85, a sub-control ROM 84, and a sub-control RWM 83 (built-in memory).

The one-chip microprocessor for main control or the main control CPU 510 may be referred to as "main control means 510."
Furthermore, the one-chip microprocessor for controlling the number of medals or the medal count control CPU 520 may be referred to as the "medal count control means 520."
Furthermore, the one-chip microprocessor for sub-control or the sub-control CPU 85 may be referred to as the "sub-control means 85."

Then, a control command can be sent from the medal count control CPU 520 to the main control CPU 510, and further, a control command can be sent from the main control CPU 510 to the sub-control CPU 85. In other words, a control command can be sent indirectly from the medal count control CPU 520 to the sub-control CPU 85 via the main control CPU 510.
Furthermore, a control command may be sent from the medal count control CPU 520 to the sub-control CPU 85. In other words, a control command may be sent from the medal count control CPU 520 directly to the sub-control CPU 85 without going through the main control CPU 510.

As shown in Figure 29 (second embodiment), two control boards, a main control board 50 and a game medium (medal) number control board 100, may be provided, with a one-chip microprocessor equipped with a main control CPU mounted on the main control board 50, and a one-chip microprocessor equipped with a medal number control CPU mounted on the game medium (medal) number control board 100.
Also, as shown in Figure 51 (fourth embodiment), a main control board 50 may be provided with a medal count control function, and a single one-chip microprocessor (main CPU) may be provided on the main control board 50, with this main CPU having the functions of a main control CPU and a medal count control CPU.
Furthermore, as in this embodiment, a one-chip microprocessor for main control and a one-chip microprocessor for medal count control may be mounted on the main control board 50.

As shown in FIG. 156, the gaming machine 10 is provided with a box-shaped cabinet 15 that is open on the front side, and a front door 16 that is attached to cover the opening on the front side of the cabinet 15.
Specifically, the front end of the left side panel of the cabinet 15 and the left side of the front door 16 are attached via a hinge (not shown). The front door 16 rotates around the hinge, allowing the opening on the front side of the cabinet 15 to be opened and closed.
A locking device (not shown) is provided on the right side of the front door 16 (the side opposite the hinge).
Furthermore, a door key insertion slot (not shown) is provided at a position corresponding to the locking device on the front surface of the front door 16 (the surface facing the player). The door key insertion slot is a portion into which a door key for operating the locking device is inserted.

When the front door 16 is closed and locked, inserting the door key into the door key slot and turning the door key clockwise unlocks the door. When the right side of the front door 16 is pulled toward you while the door is unlocked, the front door 16 rotates around the hinge, opening the front side of the cabinet 15.
The front door 16 is normally closed, but is opened when, for example, the power is turned on, settings are changed, settings are checked, or an error occurs.
Furthermore, the cabinet 15 or the front door 16 is provided with a door switch 17 for detecting when the front door 16 is opened.
That is, the door switch 17 is a switch for detecting the opening of the front door 16 and is provided on the cabinet 15 or the front door 16 .

When the front door 16 is closed, the door switch 17 is turned off, and when the front door 16 is open, the door switch 17 is turned on.
Furthermore, the door switch 17 is electrically connected to the main control board 50 via an input port 51 .
The main control board 50 (main control CPU 510) is configured to determine that the front door 16 is closed when the door switch 17 is off, and to determine that the front door 16 is open when the door switch 17 is on.
In addition, the door switch 17 may be configured to be on when the front door 16 is closed and off when the front door 16 is open, so that when the door switch 17 is on, it is determined that the front door 16 is closed, and when the door switch 17 is off, it is determined that the front door 16 is open.

As shown in Figure 156, a transparent display window 18 is provided in the center of the front door 16. A symbol display device is disposed inside the cabinet 15, and when the front door 16 is closed, the display window 18 is configured to be positioned in front of the symbol display device. The three reels 31 (left/center/right) provided on the symbol display device can be viewed through the display window 18.

A control panel 16c is provided below the display window 18 on the front surface of the front door 16 (the surface facing the player).
The control panel 16c protrudes forward from the front surface of the front door 16. A 1-bet switch 40a, a 3-bet switch 40b, a settlement switch 46, a counting switch 47, a push button 86, a cross key 87, an acquired number display unit 78, a medal number display unit 121, etc. are arranged on the upper surface of the control panel 16c. A push button lamp 88 is also arranged inside the operating body of the push button 86. Furthermore, a start switch 41 and three (left/center/right) stop switches 42 are arranged on the front surface of the control panel 16c.

The push button 86 is also called a sub-button, a performance button, a performance switch, etc., and is a switch that is operated when progressing (developing) the performance, displaying the menu screen, deciding on an item selected on the menu screen, etc.
In addition, the push button 86 is one of the peripheral devices for inputting effects, and is electrically connected to the sub-control board 80 via the input port 81, as shown in Figure 155.
Furthermore, since information (control commands) is transmitted in one direction from the main control board 50 to the sub-control board 80, a signal indicating that the push button 86 has been operated is not input to the main control board 50.

The push button lamp 88 is a lamp that illuminates the operating body of the push button 86, and is disposed inside the operating body of the push button 86. The operating body of the push button 86 is push-button shaped and has translucency.
In addition, the push button lamp 88 is one of the peripheral devices for outputting effects, and is electrically connected to the sub-control board 80 via the output port 82, as shown in Figure 155.
The sub-control board 80 is configured to, for example, light up a push button lamp 88 when prompting the operation of the push button 86 .
When the push button lamp 88 is lit, the operating body of the push button 86 appears to glow.

The cross key 87 is also called a selection button or selection switch, and is a switch used for effects, etc., and is operated when selecting a character or selecting an item on a menu screen, etc.
As shown in FIG. 156, the cross key 87 is provided with an up switch 87a, a down switch 87b, a right switch 87c, and a left switch 87d.
The cross key 87 is one of the peripheral devices for inputting effects, and is electrically connected to the sub-control board 80 via the input port 81 as shown in FIG.
Furthermore, since information (control commands) is transmitted in one direction from the main control board 50 to the sub-control board 80, a signal indicating that the cross key 87 has been operated is not input to the main control board 50.

Next, the relationship between the display of the medal count display unit 121 and the timing of starting count notification will be described.
Here, the gaming machine 10 is equipped with a medal count control CPU 520 (medal count control means, gaming media count control means) that manages the number of medals (gaming media), a medal count control RWM 522 (gaming media count storage means) that can store the total number of medals, a counting switch 47 that is operated when paying back medals, and a medal count display unit 121 (gaming media number display unit) that displays the total number of medals stored in the medal count control RWM 522.

Furthermore, the medal count control CPU 520 executes a lending process to add the number of lending game media "50" to the total number of medals stored in the medal count control RWM 522 based on the operation of the lending switch 202 .
Furthermore, when the total number of medals stored in the medal count control RWM 522 is equal to or greater than "15,000," a count notification is executed to prompt the player to operate the count switch 47.
Then, when the total number of medals stored in the medal count control RWM 522 is less than "15,000" and greater than or equal to "14,950," the loan switch 202 is operated, a loan notification including data on the number of loaned gaming media "50" is sent, and a loan process is executed to add the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM 522, and counting notification begins before the display on the medal count display unit 121 becomes greater than or equal to "15,000."

Figure 157 is a time chart showing the relationship between the display of the medal count display unit 121 and the start timing of the count notification.
Below, based on Figure 157, we will explain the relationship between the display of the medal count display unit 121 and the start timing of the count notification.
157, at the timing of "X01", the total number of medals stored in the medal count control RWM 522 is "14950", and the total number of medals displayed on the medal count display unit 121 is "14950". Furthermore, no count notification is being made by the speaker 22 or the image display device 23, the lending switch 202 is in the OFF state, and the counting switch 47 is also in the OFF state.

Then, in Figure 157, at timing "X10", the lending switch 202 is turned on, and then at timing "X12", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
157, at timing "X12", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "15,000" from "14,950".

157, at the timing of "X12", the medal count control CPU 520 starts incrementing (updating) the display of the medal count display unit 121, and at the timing of "X15", ends the incrementing (updating) of the display of the medal count display unit 121. At this time, the medal count control CPU 520 takes "300" ms from "X12" to "X15" to display the display of the medal count display unit 121 by adding (incrementing) "1" at a time from "14950" to "15000".
Furthermore, at the timing of "X12" in Fig. 157, the sub-control CPU 85 starts outputting the counting notification from the speaker 22 and the image display device 23. As a result, the output of the counting notification starts before the display on the medal count display unit 121 reaches "15000"("15000" or more).

Here, at the timing of "X12" in Figure 157, when the total number of medals in the medal count control RWM522 reaches "15,000", output of the count notification may be started at the same time.
Furthermore, when a control command is sent from the medal count control CPU 520 to the main control CPU 510, and then from the main control CPU 510 to the sub-control CPU 85, it takes about 4 ms to 5 ms to send and receive the control command. For this reason, the sub-control CPU 85 may start outputting a count notification 4 ms to 5 ms after the total medal count in the medal count control RWM 522 reaches 15,000.

Furthermore, when a control command is sent directly from the medal count control CPU 520 to the sub-control CPU 85 without going through the main control CPU 510, it takes about 1 ms to 2 ms to send and receive the control command. For this reason, the sub-control CPU 85 may start outputting a count notification 1 ms to 2 ms after the total medal count in the medal count control RWM 522 reaches 15,000.
In this way, at the timing of "X12" in Figure 157, the output of the count notification may begin approximately at the same time as the total number of medals in the medal count control RWM522 reaches "15,000."
Note that the total medal count of "14,950" is an example, and is not limited to when the total medal count is "14,950." When the total medal count is less than "15,000" and equal to or greater than "14,950," if a lending process is executed to add the number of lending game media "50" to the total medal count, the output of a counting notification will begin before the display on the medal count display unit 121 reaches "15,000" or more.

Next, the relationship between the display of the medal count display unit 121 and the timing of the end of count notification will be described.
Here, when the counting switch 47 is pressed and held (the time from when it is turned on to when it is turned off is 500 ms or more), the medal count control CPU 520 executes a counting process to subtract the number of counted game media, "50", from the total number of medals stored in the medal count control RWM 522.
Furthermore, when the total number of medals stored in the medal count control RWM 522 is equal to or greater than "15,000," a count notification is executed to prompt the player to operate the count switch 47.
When the total number of medals stored in the medal count control RWM 522 is greater than or equal to "15,000" and less than "15,050", and a counting notification is being executed, if the counting switch 47 is pressed and held down to execute a counting process that subtracts the number of counted game media "50" from the total number of medals stored in the medal count control RWM 522, the counting notification is terminated before the display on the medal count display unit 121 becomes less than "15,000".

Figure 158 is a time chart showing the relationship between the display of the medal count display unit 121 and the end timing of the count notification.
Below, based on Figure 158, we will explain the relationship between the display of the medal count display unit 121 and the timing of the end of the count notification.
158, at the timing of "X21", the total number of medals stored in the medal count control RWM 522 is "15049", and the total number of medals displayed on the medal count display unit 121 is "15049". In addition, count notification is being executed on the speaker 22 and the image display device 23, the lending switch 202 is in the OFF state, and the count switch 47 is also in the OFF state.

158, the counting switch 47 is turned on at the timing "X27", thereafter the counting switch 47 is maintained in the on state until the timing "X32", and then the counting switch 47 is turned off at the timing "X32". Also, the time from when the counting switch 47 is turned on at the timing "X27" until when the counting switch 47 is turned off at the timing "X32" is "500" ms or more. In other words, the counting switch 47 is pressed and held.
Also, in Figure 158, at timing "X32", the main control board 50 sends a counting notification including data on the number of counted gaming media "50" to the rental unit 200.
158, at timing "X32", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "14999" from "15049".

158, at the timing of "X32", the medal count control CPU 520 starts subtracting (updating) the display of the medal count display unit 121, and at the timing of "X35", ends the subtraction (updating) of the display of the medal count display unit 121. At this time, the medal count control CPU 520 displays the display of the medal count display unit 121 so that it subtracts (decrements) "1" at a time from "15049" to "14999" over the course of "300" ms from "X32" to "X35".
158, at the timing of "X32", the sub-control CPU 85 ends the output of the count notification from the speaker 22 and the image display device 23. As a result, the output of the count notification is ended before the display on the medal count display unit 121 becomes "14999" (less than "15000").

Here, at the timing of "X32" in Figure 158, the output of the count notification may be terminated at the same time that the total number of medals in the medal count control RWM 522 becomes "14999".
Furthermore, as described above, when a control command is sent from the medal count control CPU 520 to the main control CPU 510, and then a control command is sent from the main control CPU 510 to the sub-control CPU 85, it takes about 4 ms to 5 ms to send and receive the control command. For this reason, the sub-control CPU 85 may end output of the count notification 4 ms to 5 ms after the total medal count in the medal count control RWM 522 reaches 14,999.

Furthermore, as described above, when a control command is sent directly from the medal count control CPU 520 to the sub-control CPU 85 without going through the main control CPU 510, it takes about 1 ms to 2 ms to send and receive the control command. For this reason, the sub-control CPU 85 may end outputting the count notification 1 ms to 2 ms after the total medal count in the medal count control RWM 522 reaches 14,999.
In this way, at the timing of "X32" in Figure 158, the output of the count notification may be terminated at approximately the same time as the total number of medals in the medal count control RWM 522 becomes "14,999."

In addition to the count switch 47, a total count switch can be provided that can count all medals stored in the medal count control RWM 522 with a single operation (turned on). In this case, when the total count switch is operated at the timing of "X27" in FIG. 158, it can be operated in the same way as when the count switch 47 is pressed and held.
Furthermore, if the counting switch 47 is kept on for four seconds or more, a full counting process can be executed to count all medals stored in the medal count control RWM 522, and in this case, the counting switch 47 can be operated in the same way as when it is pressed and held.

The counting process is also carried out while the counting switch 47 is kept on for "4" seconds.
Specifically, the first counting process is executed 500 ms after the counting switch 47 is turned on, and thereafter, the counting process is executed every 300 ms.
Furthermore, since 4 seconds = 4000 ms, and 500 ms + 300 ms x 11 = 3800 ms, while the counting switch 47 is turned on for 4 seconds, a total of 12 counting processes are performed, and a total of 600 medals are counted.
Therefore, since the entire counting process is executed 4 seconds after the counting switch 47 is turned on, in order for the total number of medals in the medal count control RWM 522 to be 14,999 or less at the timing of X32 in Figure 158, the total number of medals in the medal count control RWM 522 must be between 15,550 and 15,599 when the counting switch 47 is turned on from the off state.

Furthermore, the total medal count of "15,049" is an example, and is not limited to when the total medal count is "15,049." When the total medal count is greater than or equal to "15,000" and less than "15,050," if a counting process is executed to subtract the number of counted gaming media "50" from the total medal count, the output of the count notification will end before the display on the medal count display unit 121 becomes less than "15,000."

The relationship between the display of the medal count display unit 121 and the start and end timings of the count notification will be described in more detail below.
155, the main control board 50 is electrically connected to an external lending unit 200 that controls the lending and refunding of medals via the connection terminal board 130. As a result, the medal count control CPU 520 is electrically connected to the lending unit 200.
The lending unit 200 also includes a lending switch 202 that is operated when lending medals.
Then, when the loan switch 202 is operated and a loan notification including data on the number of loaned gaming media "50" is received, the medal count control CPU 520 executes a loan process (processing related to the loan of medals) that adds the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM 522.

The lending process is performed in the medal count control interrupt process by the medal count control CPU 520 shown in FIG.
Specifically, lending control is performed in step S805 of the medal count control interrupt process shown in Fig. 132. In the lending control, for example, the process shown in Fig. 69 is executed. Furthermore, in step S869 in Fig. 69, the process of adding the number of lending game media "50" to the total medal count is executed.

In addition, the medal count control interrupt process is executed every "1" ms (the cycle of the medal count control interrupt process is "1" ms).
Therefore, the time required from receiving a loan notification including data on the number of loaned gaming media "50" to adding the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM522 is approximately "1" ms.
In addition, since the lending notification is sent from the lending unit 200 every "300" ms, the process of adding the number of lending game media "50" to the total number of medals stored in the medal count control RWM 522 can be executed every "300" ms.
The number of lendable game media "50" is an example, and the number of lendable game media is not limited to "50" and can be set appropriately, for example, to "30" or "100".

In addition, the medal count control CPU 520 executes a counting process (a process related to medal payout) that subtracts the number of counted game media from the total number of medals stored in the medal count control RWM 522 based on the operation of the counting switch 47 .
Specifically, when the counting switch 47 is pressed and held (the time from when it is turned on to when it is turned off is 500 ms or more), the medal count control CPU 520 executes a counting process to subtract the number of counted game media, "50", from the total number of medals stored in the medal count control RWM 522.
In addition, when the counting switch 47 is pressed briefly (the time from when it is turned on to when it is turned off is less than 500 ms), the medal count control CPU 520 executes a counting process to subtract the number of counted game media "1" from the total number of medals stored in the medal count control RWM 522.

The counting process is performed in an interrupt process (medal count control interrupt process) by the medal count control CPU 520 shown in FIG.
Also, as described above, the medal count control interrupt process is executed every "1" ms.
Furthermore, whether the count switch 47 is pressed for a long time or for a short time is determined in the input port check process shown in FIG.
Furthermore, the process of subtracting the number of counted game media "50" or "1" from the total number of medals is performed in the counting control process shown in FIG.

Therefore, the time required from determining that the counting switch 47 has been pressed and held until the number of counted game media "50" is subtracted from the total number of medals is about "1" ms.
Similarly, the time required from determining that the counting switch 47 has been pressed for a short time until the number of counted game media "1" is subtracted from the total number of medals is about "1" ms.
134, the medal count control CPU 520 determines whether it is time to notify the counting, which occurs 100 ms after the transmission of the gaming machine information notification, which is transmitted every 300 ms. Therefore, the process of subtracting the number of counted gaming media, 50 or 1, from the total medal count can be executed every 300 ms.

Note that the number of game media counted when the counting switch 47 is pressed and held, "50", is an example, and the number of game media counted when the counting switch 47 is pressed and held is not limited to "50" and can be set appropriately, for example, to "30" or "100".
Furthermore, the number of game media counted when the counting switch 47 is pressed briefly, "1", is an example, and the number of game media counted when the counting switch 47 is pressed briefly is not limited to "1" and can be set appropriately, for example, to "3" or "5".
Furthermore, the time of 500 ms for determining whether the counting switch 47 has been pressed long or short is an example, and the time for determining whether the counting switch 47 has been pressed long or short is not limited to 500 ms and can be set appropriately, for example, to 400 ms, 600 ms, etc.

In addition, when the total number of medals stored in the medal count control RWM 522 is equal to or greater than the threshold value "15,000", a count notification is executed to prompt the player to operate the count switch 47.
Here, "counting notification" is also called "threshold notification," and refers to a notification that informs the player that the total number of medals stored in the medal count control RWM 522 is equal to or greater than the threshold value "15,000," or a notification that prompts the player to operate the counting switch 47 because the total number of medals stored in the medal count control RWM 522 is equal to or greater than the threshold value "15,000."
The threshold value "15000" is an example, and the threshold value is not limited to "15000" and can be set appropriately to, for example, "10000" or "16000".

132, in step S1146, the medal count control CPU 520 transmits a medal count control command to the main control CPU 510. Here, the medal count control command includes information on the total medal count (such as information indicating whether the total medal count is equal to or greater than the threshold value of 15,000).
As a result, information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, and the main control CPU 510 can determine whether the total number of medals is equal to or greater than the threshold value "15,000".

Also, in step S901 of FIG. 73, the main control CPU 510 determines whether the total number of medals is equal to or greater than the threshold value "15,000".
Then, when it is determined that the total number of medals is less than the threshold value "15,000", the process proceeds to step S902 in Figure 73, where the main control CPU 510 sets the threshold reached flag to "0", and in the next step S903, sets threshold not reached information.
On the other hand, if it is determined that the total number of medals is greater than or equal to the threshold value of "15,000", the process proceeds to step S904 in Figure 73, where the main control CPU 510 sets the threshold value reaching flag to "1", and in the next step S905, sets the threshold value reaching information.

In addition, the main control CPU 510 transmits threshold unreached information (when the threshold reached flag is "0") or threshold reached information (when the threshold reached flag is "1") to the sub-control CPU 85. When the threshold (unreached, reached) information is set in steps S903 and S905 of Fig. 73, the main control CPU 510 transmits the threshold (unreached, reached) information to the sub-control CPU 85 at a predetermined timing.
Also, in step S921 of Figure 75, the sub-control CPU 85 determines whether the threshold notification flag is "1". Here, the threshold notification flag is a flag that indicates that the threshold has been reached when it is "1", and indicates that the threshold has not been reached when it is "0". When the threshold notification flag is "1", count notification can be executed.

If it is determined in step S921 of FIG. 75 that the threshold notification flag is not "1", the process proceeds to step S922, and if it is determined that the threshold notification flag is "1", the process proceeds to step S925.
In step S922 of FIG. 75, the sub-control CPU 85 determines whether or not threshold value reaching information has been received from the main control CPU 510. If threshold value reaching information has not been received, the sub-control CPU 85 terminates the processing according to the flowchart shown in FIG. 75 without outputting a counting notification. In contrast, if it is determined that threshold value reaching information has been received, the processing proceeds to step S923, where the sub-control CPU 85 sets the threshold value notification flag to "1." Then, the processing proceeds to step S924 of FIG. 75, where the sub-control CPU 85 outputs a counting notification.

Furthermore, when the sub-control CPU 85 determines in step S921 of FIG. 75 that the threshold reach flag is "1" and proceeds to step S925, it determines whether or not it has received threshold non-reach information from the main control CPU 510. If it determines that it has not received threshold non-reach information, it proceeds to step S924, where the sub-control CPU 85 outputs a counting notification. On the other hand, if it determines that it has received threshold non-reach information, it proceeds to step S926, where the sub-control CPU 85 sets the threshold notification flag to "0." Then, it proceeds to step S927 of FIG. 75, where the sub-control CPU 85 ends the counting notification being output, and ends the processing according to the flowchart shown in FIG. 75.
In this way, in the example shown in Figure 75, when the total number of medals becomes equal to or greater than the threshold value "15,000", the sub-control CPU 85 outputs a counting notification, and when the total number of medals becomes less than the threshold value "15,000", the sub-control CPU 85 terminates the counting notification.

In addition, the threshold processing by the main control CPU 510 shown in Figure 73 is executed by interrupt processing (main control interrupt processing) by the main control CPU 510.
Furthermore, the main control interrupt processing is executed every "2.235" ms (the period of the main control interrupt processing is "2.235" ms).
In addition, the threshold notification (count notification) processing by the sub-control CPU 85 shown in Figure 75 is executed by interrupt processing (sub-control interrupt processing) by the sub-control CPU 85.
Furthermore, the secondary control interrupt process is executed every "1" ms (the cycle of the secondary control interrupt process is "1" ms).

As a result of the above, the total number of medals stored in the medal count control RWM 522 becomes equal to or greater than the threshold value of "15,000", information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, the main control CPU 510 determines that the total number of medals is equal to or greater than the threshold value of "15,000", and the time required for the sub-control CPU 85 to execute the count notification is approximately "4" ms to "5" ms.
Furthermore, when counting notification is being executed by the sub-control CPU 85, the total number of medals stored in the medal count control RWM 522 becomes less than the threshold value "15,000", information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, the main control CPU 510 determines that the total number of medals is less than the threshold value "15,000", and the time required for the counting notification by the sub-control CPU 85 to end is approximately "4" ms to "5" ms.
In addition, the sub-control CPU 85 displays an image including the text "Please press the counting switch" on the image display device 23 as a counting notification.
Furthermore, the sub-control CPU 85 outputs (repeatedly plays) a voice message such as "Please press the counting switch" from the speaker 22 as a counting notification.

In addition, the medal count control CPU 520 controls the display of the total medal count in the medal count display unit 121 .
Display control of the medal count display unit 121 is executed in step S1147 of the medal count control interrupt process shown in FIG.
The display control of the medal count display unit 121 in step S1147 of Figure 132 is a process of updating the display of the total medal count in the medal count display unit 121 based on medal betting processing, settlement processing, awarding processing, counting processing, and lending processing.

Here, when the loan switch 202 is operated, a loan notification including data on the number of loaned gaming media "50" is received, and a loan process is executed to add the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM 522, the medal count control CPU 520 controls the display of the medal count display unit 121 to add (increment) "1" at a time.
For example, when the total number of medals stored in the medal count control RWM 522 is "0" and the display of the medal count display unit 121 is "0", the loan switch 202 is operated, a loan notification including data on the number of loaned gaming media "50" is received, and a loan process is executed to add the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM 522.
In this case, the medal count control CPU 520 changes the total medal count stored in the medal count control RWM 522 from "0" to "50", and also displays the medal count display unit 121 incrementing from "0" to "1" at a time, thereby changing the display of the medal count display unit 121 to "50".

In addition, the process of adding the total number of medals stored in the medal count control RWM 522 from "0" to "50" is executed in approximately "1" ms.
In contrast, the process of displaying the display on the medal count display unit 121 by incrementing "1" from "0" to "50" takes "300" ms. Also, since the process of displaying the display on the medal count display unit 121 by incrementing "1" from "0" to "50" takes "300" ms, the time required to increment the display on the medal count display unit 121 by "1" is "6" ms.
When the lending switch 202 is operated continuously, a lending notification including data indicating the number of lending game media, "50," is transmitted every "300" ms. As a result, the number of lending game media, "50," is added to the total number of medals stored in the medal count control RWM 522 every "300" ms. Then, when the display on the medal count display unit 121 is displayed so that it increases by "1" from "0" to "50" over the course of "300" ms, the display on the medal count display unit 121 appears to be updated smoothly and seamlessly.

For example, suppose that the total number of medals stored in the medal count control RWM 522 is "0" and the display on the medal count display unit 121 is "0," the lending switch 202 is operated repeatedly, a lending notification containing data on the number of lending game media of "50" is sent, and 300 ms later, another lending notification containing data on the number of lending game media of "50" is sent. Then, a lending process is executed to add the number of lending game media of "50" to the total number of medals stored in the medal count control RWM 522, and 300 ms later, another lending process is executed to add another number of lending game media of "50."
In this case, the medal count control CPU 520 takes 300 ms to display the display on the medal count display unit 121 by incrementing "1" from "0" to "50," and then takes another 300 ms to display the display on the medal count display unit 121 by incrementing "1" from "50" to "100." This makes it appear as if the display on the medal count display unit 121 is being updated smoothly and seamlessly from "0" to "100."

Furthermore, when the counting switch 47 is pressed and held (the time from when it is turned on to when it is turned off is 500 ms or more) and a counting process is executed to subtract the number of counted game media "50" from the total number of medals stored in the medal count control RWM 522, the medal count control CPU 520 controls the display of the medal count display unit 121 to be decremented by "1" at a time.
For example, suppose the total number of medals stored in the medal count control RWM 522 is "100" and the display on the medal count display unit 121 is "100," then the counting switch 47 is pressed and held down, and a counting process is executed to subtract the number of counted gaming media "50" from the total number of medals stored in the medal count control RWM 522.
In this case, the medal count control CPU 520 changes the total medal count stored in the medal count control RWM 522 from "100" to "50", and also decrements the display of the medal count display unit 121 by "1" from "100", thereby changing the display of the medal count display unit 121 to "50".

In addition, the process of subtracting the total number of medals stored in the medal count control RWM 522 from "100" to "50" is executed in approximately "1" ms.
In contrast, the process of displaying the display of the medal count display unit 121 by subtracting "1" from "100" to "50" takes "300" ms. Also, since the display of the medal count display unit 121 is displayed by subtracting "1" from "100" to "50" over "300" ms, the time required to subtract "1" from the display of the medal count display unit 121 is "6" ms.
If the count switch 47 is pressed and held, the number of counted game media is decremented by 50 every 300 ms. If the display on the medal count display unit 121 is decremented by 1 from 100 to 50 over 300 ms, the display on the medal count display unit 121 appears to be updated smoothly and seamlessly.

For example, suppose the total number of medals stored in the medal count control RWM 522 is "100" and the display on the medal count display unit 121 is "100," then the counting switch 47 is pressed and held down, a counting process is executed to subtract the number of counted gaming media "50" from the total number of medals stored in the medal count control RWM 522, and then 300 ms later, a counting process is executed to further subtract the number of counted gaming media "50."
In this case, the medal count control CPU 520 takes 300 ms to display the display in the medal count display unit 121 by subtracting 1 from 100 to 50, and then takes another 300 ms to display the display in the medal count display unit 121 by subtracting 1 from 50 to 0. This makes it appear as if the display in the medal count display unit 121 is being updated smoothly and seamlessly from 100 to 0.

Furthermore, as described above, when the total number of medals stored in the medal count control RWM 522 becomes equal to or greater than the threshold value "15,000", information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, the main control CPU 510 determines that the total number of medals is equal to or greater than the threshold value "15,000", and the time required for the sub-control CPU 85 to execute a counting notification is approximately "4" ms to "5" ms.
In contrast, the time required to add "1" to the display of the medal count display unit 121 is "6" ms, and for example, the process of adding "1" at a time to the display of the medal count display unit 121 from "14950" to "15000" takes "300" ms.

Therefore, when the total number of medals stored in the medal count control RWM 522 is less than "15,000" and greater than or equal to "14,950," the loan switch 202 is operated, a loan notification including data on the number of loaned gaming media "50" is sent, and a loan process is executed to add "50" to the number of loaned gaming media, counting notification begins before the display on the medal count display unit 121 reaches "15,000" or greater.
This allows counting notification to begin early, and the player can be informed early that the total number of medals stored in the medal count control RWM 522 has reached 15,000 or more.

Furthermore, as described above, when the counting notification is being executed by the sub-control CPU 85, the total number of medals stored in the medal count control RWM 522 becomes less than the threshold value "15,000", information on the total number of medals is sent from the medal count control CPU 520 to the main control CPU 510, the main control CPU 510 determines that the total number of medals is less than the threshold value "15,000", and the time required for the counting notification by the sub-control CPU 85 to end is approximately "4" ms to "5" ms.
In contrast, it takes 6 ms to decrement the display of the medal count display unit 121 by 1, and for example, the process of decrementing the display of the medal count display unit 121 by 1 from 15049 to 14999 takes 300 ms.

Therefore, when the total number of medals stored in the medal count control RWM 522 is greater than or equal to 15,000 and less than 15,050, and the counting process is executed with the time from when the counting switch 47 is turned on to when it is turned off being greater than 500 ms, the counting notification will end before the display on the medal count display unit 121 becomes less than 15,000.
This allows the counting notification to end early, and the player to be informed early that the total number of medals stored in the medal count control RWM 522 has fallen below "15,000".

In the above explanation, the medal count control CPU 520 transmits information regarding the total medal count to the main control CPU 510, and the main control CPU 510 then transmits information regarding the total medal count to the sub-control CPU 85. In other words, the medal count control CPU 520 indirectly transmits information regarding the total medal count to the sub-control CPU 85 via the main control CPU 510. When the sub-control CPU 85 determines that the total medal count is equal to or greater than the threshold, it issues a count notification.
However, the present invention is not limited to this, and for example, the medal count control CPU 520 may transmit information regarding the total medal count directly to the sub-control CPU 85 without going through the main control CPU 510. Then, when the sub-control CPU 85 determines that the total medal count is equal to or greater than a threshold value, it may issue a count notification.

Next, the manner in which the counting notification images and sounds are output will be described.
Here, the counting notification involves repeatedly playing (outputting) a specified image, which has a length of a specified duration from start to finish, on the image display device 23, and repeatedly playing (outputting) a specified sound, which has a length of a specified duration from start to finish, from the speaker 22.
Then, when the total number of medals stored in the medal count control RWM522 falls below the threshold value "15,000" during the playback of the specified images and sounds that make up the counting notification, the specified images and sounds that make up the counting notification are terminated without being played to the end.

FIG. 159 is a time chart showing the output mode of counting notification images and sounds.
Below, based on Figure 159, we will explain the output mode of counting notification images and sounds.
159, at the timing of "X41", the total medal count stored in the medal count control RWM 522 is "15,049", and the total medal count displayed on the medal count display unit 121 is "15,049". In addition, an image constituting the count notification is being output on the image display device 23, and a sound constituting the count notification is being output on the speaker 22, and the count switch 47 is in the off state.

Here, in the tenth embodiment, the image constituting the counting notification is an image containing the words "Please press the counting switch," and is displayed in the center of the image display device 23 on a layer closer to the front (nearer) than the other images, prompting the player to operate the counting switch 47. The image constituting the counting notification is an image (video or still image) that is "2" seconds long from start to finish. Then, while the total number of medals stored in the medal count control RWM 522 is equal to or greater than the threshold value of "15,000," the sub-control CPU 85 repeatedly plays (loops) the image constituting the counting notification on the image display device 23.

In the tenth embodiment, the audio that constitutes the counting notification is audio that includes the words "Please press the counting switch," and is output from the speaker 22 to prompt the player to operate the counting switch 47. The audio that constitutes the counting notification is audio that is 2 seconds long from start to finish. While the total number of medals stored in the medal count control RWM 522 is equal to or greater than the threshold value of 15,000, the sub-control CPU 85 repeatedly plays (loops) the audio that constitutes the counting notification from the speaker 22.

In the example shown in Fig. 159, the timing "X42" in the figure is the start of the image and sound that make up the counting notification, and the timing "X53" in the figure is the end of the image and sound that make up the counting notification. Note that the timing "X53" in the figure also marks the start of the next image and sound that make up the counting notification.
159, the counting switch 47 is turned on at the timing "X52", thereafter the counting switch 47 is maintained in the on state until the timing "X55", at which time the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at the timing "X52" until when the counting switch 47 is turned off at the timing "X55" is "500" ms or more. In other words, the counting switch 47 is pressed and held.
Also, in Figure 159, at timing "X55", the main control board 50 sends a counting notification including data on the number of counted gaming media "50" to the rental unit 200.
159, at timing "X55", the medal count control CPU 520 executes counting processing to subtract the number of counted game media, "50", from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "14999" from "15049".

159, at the timing of "X55", the medal count control CPU 520 starts subtracting (updating) the display of the medal count display unit 121, and at the timing of "X57", ends the subtraction (updating) of the display of the medal count display unit 121. At this time, the medal count control CPU 520 displays the display of the medal count display unit 121 so that it subtracts (decrements) "1" at a time from "15049" to "14999" over the course of "300" ms from "X55" to "X57".
Then, at the timing of "X55" in Figure 159, the sub-control CPU 85 ends the output of the counting notification on the speaker 22 and the image display device 23. Here, the timing of "X55" in Figure 159 is not the timing of the end of the images and audio that make up the counting notification. As a result, at the timing of "X55" in Figure 159, the sub-control CPU 85 stops the images that make up the counting notification on the image display device 23 halfway through without playing them to the end, and stops the audio that makes up the counting notification on the speaker 22 halfway through without playing them to the end. The audio that makes up the counting notification is stopped halfway through playback, for example, like "counting switch."

Note that the total medal count displayed in the medal count display unit 121 becomes "14,999" at timing "X57" in Fig. 159, but the output of the count notification ends at the previous timing, timing "X55." As a result, the output of the count notification ends before the total medal count displayed in the medal count display unit 121 becomes "14,999" (less than "15,000").
In this way, when the total number of medals stored in the medal count control RWM 522 falls below "15,000," the counting notification can be ended early by stopping the images and sounds that make up the counting notification before they are played to the end, and the player can be informed early that the total number of medals stored in the medal count control RWM 522 has fallen below "15,000."

The counting notification is not limited to outputting both an image and sound, but may instead output only an image on the image display device 23, or output only sound from the speaker 22, for example.
Furthermore, the image constituting the count notification is an image including the text "Please press the count switch," but this is merely an example and can be set as appropriate.
Furthermore, the voice constituting the count notification is a voice including the words "Please press the count switch," but this is merely an example and can be set as appropriate.
Furthermore, the images and sounds that make up the counting notification are set to be 2 seconds long from start to finish, but 2 seconds is an example, and the length from start to finish can be set as appropriate, for example, to 1.5 seconds, 3 seconds, or the like.

Next, the relationship between the operation of the 3-bet switch 40b and the settlement switch 46, the total number of medals, and the count notification will be described.
The gaming machine 10 is provided with a 3-bet switch 40b which is operated when betting medals, and a settlement switch 46 which is operated when returning the bet medals.
Furthermore, the medal count control CPU 520 executes bet processing to subtract the bet number "3" from the total medal count stored in the medal count control RWM 522 based on the operation of the 3 bet switch 40b.

Furthermore, the medal count control CPU 520 executes a settlement process of adding the number of bets to the total number of medals stored in the medal count control RWM 522 based on the operation of the settlement switch 46 .
Furthermore, when the total number of medals stored in the medal count control RWM 522 is equal to or greater than "15,000," a count notification is executed to prompt the player to operate the count switch 47.
When the total number of medals stored in the medal count control RWM 522 is equal to or greater than "15,000" and less than "15,003", the number of medals bet is "0", and counting notification is being executed, if the 3-bet switch 40b is operated, the counting notification is terminated, and if the settlement switch is operated thereafter, the counting notification is executed again.

The bet processing in the medal count control CPU 520 is performed in the bet request command reception processing shown in Fig. 118. The bet request command reception processing is performed in the main control command reception processing (step S1062 in Fig. 116, Fig. 117) in the medal count control main processing shown in Fig. 116.
118, in step S1085, the number of bet requests (number of bets) is subtracted from the total number of medals, and in step S1087, the total number of medals is updated. In this way, the number of bet requests (number of bets) is subtracted from the total number of medals stored in the medal count control RWM 522.

The settlement process in the medal count control CPU 520 is performed in the settlement request command reception process shown in Fig. 119. Like the bet request command reception process, the settlement request command reception process is also performed in the main control command reception process (step S1062 in Fig. 116, Fig. 117) during the medal count control main process shown in Fig. 116.
Specifically, during the settlement request command reception process shown in Fig. 119, in step S1105, a process is executed to add the settlement request number (number of bets) to the total number of medals, and in step S1107, a process is executed to update the total number of medals. In this way, the settlement request number (number of bets) is added to the total number of medals stored in the medal count control RWM 522.

As described above, the medal count control CPU 520 transmits a medal count control command including information on the total medal count to the main control CPU 510 .
Furthermore, the main control CPU 510 determines whether the total number of medals is greater than or equal to the threshold value of 15,000, and if it determines that the total number of medals is less than the threshold value of 15,000, it sends threshold unreached information to the sub-control CPU 85, and if it determines that the total number of medals is greater than or equal to the threshold value of 15,000, it sends threshold reached information to the sub-control CPU 85.
When the sub-control CPU 85 receives threshold not-reached information, it does not output a counting notification, and when it receives threshold reached information, it outputs a counting notification.

As a result, if the total number of medals stored in the medal count control RWM 522 is greater than or equal to 15,000 but less than 15,003, the number of medals bet is 0, and the count notification is being executed, and the 3 bet switch 40b is operated, the count notification will end if the total number of medals stored in the medal count control RWM 522 becomes less than 15,000. If the settlement switch is then operated, and the total number of medals stored in the medal count control RWM 522 becomes 15,000 or greater, the count notification will be executed again.

FIG. 160 is a time chart showing the relationship between the operation of the 3-bet switch 40b and the settlement switch 46, the total number of medals, and the count notification.
Hereinafter, the relationship between the operation of the 3-bet switch 40b and the settlement switch 46, the total number of medals, and the count notification will be described based on FIG.
160, at the timing of "X61", the total number of medals stored in the medal count control RWM 522 is "15,000", the total number of medals displayed on the medal count display unit 121 is "15,000", and the number of bets stored in the main control RWM 512 is "0". In addition, an image constituting a counting notification is being output on the image display device 23, and a sound constituting a counting notification is being output on the speaker 22, and the 3 bet switch 40b, the settlement switch 46, and the counting switch 47 are all in the off state.

Then, when the 3 bet switch 40b is turned on at the timing of "X62" in Figure 160, the main control CPU 510 sends a bet request command including data on the bet request number (number of bets) "3" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "3".
160, when a bet request command including data on the requested bet number (number of bets) "3" is received at timing "X62", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "3" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "14,997" from "15,000".

160, at timing "X62", the medal count control CPU 520 starts subtracting (updating) the display of the medal count display unit 121, and at timing "X63", ends the subtraction (updating) of the display of the medal count display unit 121. At this time, from "X62" to "X63", the medal count control CPU 520 displays the display of the medal count display unit 121 so that it subtracts (decrements) "1" at a time from "15000" to "14997".
In addition, since the time required to subtract "1" from the display of the medal count display unit 121 is "6" ms, the time required to subtract "1" from the display of the medal count display unit 121 from "15000" to "14997" is "18" ms.

Furthermore, at timing "X62" in Figure 160, the sub-control CPU 85 ends the output of the image constituting the count notification on the image display device 23 and the output of the sound constituting the count notification on the speaker 22.
Thus, in Figure 160, at the timing of "X62", it is not the counting switch 47 that is turned on, but rather the 3-bet switch 40b that is turned on.As a result, the total number of medals stored in the medal count control RWM 522 becomes "14,997" (less than "15,000"), and therefore the output of the counting notification from the image display device 23 and speaker 22 is terminated.

Then, when the settlement switch 46 is turned on at the timing of "X67" in Figure 160, the main control CPU 510 sends a settlement request command to the medal count control CPU 520 including data on the settlement request number (number of bets) of "3", and executes processing to set the number of bets stored in the main control RWM 512 to "0".
160, when a settlement request command including data for the settlement request number (number of bets) "3" is received at timing "X67", the medal count control CPU 520 executes settlement processing to add the settlement request number (number of bets) "3" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 changes from "14,997" to "15,000".

160, at timing "X67", the medal count control CPU 520 starts incrementing (updating) the display of the medal count display unit 121, and at timing "X68", ends incrementing (updating) the display of the medal count display unit 121. At this time, from "X67" to "X68", the medal count control CPU 520 displays the display of the medal count display unit 121 so that it increases (increments) by "1" from "14997" to "15000".
In addition, since the time required to add "1" to the display of the medal count display unit 121 is "6" ms, the time required to add "1" to the display of the medal count display unit 121 from "14997" to "15000" is "18" ms.

Furthermore, at timing "X67" in Figure 160, the sub-control CPU 85 resumes output of images constituting the count notification on the image display device 23 and output of sounds constituting the count notification on the speaker 22.
Thus, at the timing of "X67" in Figure 160, medals are not awarded or the loan switch 202 is turned on, but the settlement switch 46 is turned on.As a result, the total number of medals stored in the medal count control RWM 522 becomes "15,000" (more than "15,000"), so the output of the counting notification on the image display device 23 and speaker 22 is resumed.

160, the counting switch 47 is turned on at timing "X72", and then the counting switch 47 is maintained in the on state until timing "X73", at which time the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at timing "X72" to when the counting switch 47 is turned off at timing "X73" is less than "500" ms. In other words, the counting switch 47 is pressed for a short time.
Also, in Figure 160, at timing "X74", the main control board 50 sends a counting notification including data indicating the number of counted gaming media "1" to the rental unit 200.
160, at timing "X74", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "1" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "14,999" from "15,000".

Furthermore, at timing "X74" in Fig. 160, the medal count control CPU 520 subtracts "1" from the display in the medal count display unit 121. As a result, the display in the medal count display unit 121 changes from "15000" to "14999".
Then, at timing "X74" in Figure 160, the sub-control CPU 85 ends the output of the image constituting the count notification on the image display device 23 and the output of the sound constituting the count notification on the speaker 22.
Thus, in Figure 160, at the timing of "X74", the counting switch 47 is pressed for a short time rather than a long time, and as a result, the total number of medals stored in the medal count control RWM 522 becomes "14,999" (less than "15,000"), and the output of the counting notification from the image display device 23 and speaker 22 is terminated.

In the example shown in Figure 160, the counting switch 47 is pressed briefly at the timing "X72" in the figure, but for example, instead of pressing the counting switch 47 briefly at the timing "X72", the 1 bet switch 40a may be turned on at the timing "X74".
In this case, when the 1 bet switch 40a is turned on at the timing of "X74" in Figure 160, the main control CPU 510 sends a bet request command including data for the bet request number (number of bets) "1" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "1".
160, when a bet request command including data of the requested bet number (number of bets) "1" is received at timing "X74", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "1" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "14,999" from "15,000".

Furthermore, at timing "X74" in Fig. 160, the medal count control CPU 520 subtracts "1" from the display in the medal count display unit 121. As a result, the display in the medal count display unit 121 changes from "15000" to "14999".
Furthermore, at timing "X74" in Figure 160, the sub-control CPU 85 ends the output of the image constituting the count notification on the image display device 23 and the output of the sound constituting the count notification on the speaker 22.
In this way, when the 1 bet switch 40a is turned on at the timing of "X74" in Figure 160, the total number of medals stored in the medal count control RWM 522 becomes "14,999" (less than "15,000"), and the output of the counting notification on the image display device 23 and speaker 22 is terminated.

Next, the operation of the counting switch 47 when it is pressed for a short time and when it is pressed for a long time will be described.
When the counting switch 47 is pressed and held (the time from when it is turned on to when it is turned off is 500 ms or more) and the counting process is executed, the sub-control CPU 85 displays that counting is in progress on the image display device 23.
In contrast, when the counting switch 47 is pressed briefly (the time from when it is turned on to when it is turned off is less than 500 ms) and the counting process is executed, the sub-control CPU 85 does not display the counting in progress on the image display device 23.
Here, the "counting in progress display" is a display indicating that counting is in progress. In this embodiment, the sub-control CPU 85 displays an image including the words "counting in progress" on the image display device 23 as the counting in progress display.

As described above, a total count switch can be provided in addition to the count switch 47, which can be operated once (to turn on) to count all medals stored in the medal count control RWM 522. In this case, the sub-control CPU 85 can display the counting in progress on the image display device 23 even when the total count switch is operated.
Furthermore, as described above, if the counting switch 47 is kept on for four seconds or more, it is possible to execute a full counting process that counts all medals stored in the medal count control RWM 522. In this case, the sub-control CPU 85 can display the counting in progress on the image display device 23 even when the full counting process has been executed.

In addition, when the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 outputs a counting sound for a long press from the speaker 22, and when the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 outputs a counting sound for a short press from the speaker 22.
Here, the "counting sound" is a sound that indicates that counting is in progress.
In this embodiment, when the counting switch 47 is pressed and held, the sub-control CPU 85 outputs a relatively long sound, such as a "plodding" sound, as a counting sound for a long press from the speaker 22. The length of the counting sound for a long press is "300" ms from the beginning to the end.

In response to this, when the counting switch 47 is pressed for a short time, the sub-control CPU 85 outputs a relatively short sound such as "pon" as a counting sound for a short press from the speaker 22. The counting sound for a short press has a length of 200 ms from the beginning to the end, which is shorter than the counting sound for a long press (300 ms).
Note that the length of the counting sound when the button is pressed and held, "300" ms, is an example, and the length of the counting sound when the button is pressed and held is not limited to "300" ms, but can be any length greater than "300" ms, and can be set appropriately, for example, to "500" ms or "1" second.
Furthermore, the length of the counting sound when the button is pressed briefly, "200" ms, is an example, and the length of the counting sound when the button is pressed briefly is not limited to "200" ms, but may be any length less than "300" ms, and can be set appropriately, for example, to "100" ms, "150" ms, etc.

In addition, when the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 turns on the push button lamp 88, but disables the operation acceptance of the push button 86, and turns off the push button lamp 88 after the counting switch 47 is turned off.
In contrast, when the counting switch 47 is pressed briefly to execute the counting process, the sub-control CPU 85 does not turn on the push button lamp 88, but keeps it off.

When prompting the user to operate the push button 86, the operation acceptance of the push button 86 is enabled and the push button lamp 88 is lit in a predetermined manner, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 is disabled and the push button lamp 88 is lit in the same manner as when prompting the user to operate the push button 86.
In addition, when prompting the operation of the push button 86, the operation acceptance of the push button 86 may be enabled and the push button lamp 88 may be lit in a predetermined manner, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 may be disabled and the push button lamp 88 may be lit in a manner different from that when prompting the operation of the push button 86.

Specifically, when prompting the operation of the push button 86, the operation acceptance of the push button 86 is enabled and the push button lamp 88 is lit at a predetermined brightness (brightness, luminous intensity, illuminance), and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 is disabled and the push button lamp 88 is lit at a brightness (dark or bright) different from that when prompting the operation of the push button 86.
In addition, when prompting the operation of the push button 86, the operation acceptance of the push button 86 may be enabled and the push button lamp 88 may be lit in a predetermined color, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 may be disabled and the push button lamp 88 may be lit in a color different from that used when prompting the operation of the push button 86.

Furthermore, when prompting the operation of the push button 86, the operation acceptance of the push button 86 may be enabled and the push button lamp 88 may be made to flash in a predetermined manner, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 may be disabled and the push button lamp 88 may be made to flash in the same manner as when prompting the operation of the push button 86.
Furthermore, when prompting the operation of the push button 86, the operation acceptance of the push button 86 may be enabled and the push button lamp 88 may be made to flash in a predetermined manner, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 may be disabled and the push button lamp 88 may be made to flash in a manner different from that when prompting the operation of the push button 86.

In addition, when prompting the user to operate the push button 86, the operation acceptance of the push button 86 may be enabled and the push button lamp 88 may be lit in a predetermined manner, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 may be disabled and the push button lamp 88 may be made to flash in a predetermined manner.
Conversely, when prompting the user to operate the push button 86, the operation acceptance of the push button 86 may be enabled and the push button lamp 88 may be made to flash in a predetermined manner, and when the counting switch 47 is pressed and held down to execute the counting process, the operation acceptance of the push button 86 may be disabled and the push button lamp 88 may be made to light up in a predetermined manner.

In addition, when the counting switch 47 is pressed and held to execute counting processing while game background music is being output from the speaker 22, the sub-control CPU 85 reduces the volume of the game background music to a volume lower than that before the counting processing was executed, and after the counting switch 47 is turned off, returns the volume of the game background music to the volume before the counting processing was executed.
In contrast, when game background music is being output from the speaker 22 and the counting switch 47 is pressed briefly to execute the counting process, the sub-control CPU 85 does not reduce the volume of the game background music, but maintains the volume before the counting process is executed.

As described above, the medal count control CPU 520 transmits a medal count control command to the main control CPU 510 (step S1146 in FIG. 132 ). This medal count control command may include information indicating the on/off state of the count switch 47, information indicating that the counting process has been executed by pressing the counting switch 47 for a long time, information indicating that the counting process has been executed by pressing the counting switch 47 for a short time, etc.
The main control CPU 510 also transmits a main control command to the sub-control CPU 85 (step S1049 in FIG. 127). This main control command may include information indicating whether the counting switch 47 is on or off, information indicating that the counting process has been executed by pressing the counting switch 47 for a long time, information indicating that the counting process has been executed by pressing the counting switch 47 for a short time, etc.

Then, when the sub-control CPU 85 determines based on the received main control command that the counting switch 47 has been pressed and held down and the counting process has been executed, it starts displaying the counting process on the image display device 23, and then when it determines that the counting process has ended, it ends the counting process display on the image display device 23.
Here, the determination of the end of the counting process will be described.
The on/off state of the counting switch 47 is checked, and when it is determined that the counting switch 47 has changed from an on state to an off state, it can be determined that the counting process has ended.
In addition, the number of counted gaming media included in the counting notification is checked, and when it is determined that the number of counted gaming media has changed from "50" to "0", it can be determined that the counting process has ended.

Furthermore, when the counting switch 47 is pressed and held down and the counting switch 47 is turned off, the number of counted game media can be set to "0" at the first counting notification after the counting switch 47 is turned off.
Furthermore, when the counting switch 47 is pressed and held down and the counting switch 47 is turned off, the first counting notification after the counting switch 47 is turned off can set the number of counted gaming media to "50", and the next counting notification can set the number of counted gaming media to "0".

That is, when the counting switch 47 is kept on (pressed and held), a counting notification containing data indicating the number of counted game media of "50" is transmitted every "300" ms, but when the counting switch 47 is turned off, a counting notification containing data indicating the number of counted game media of "0" is transmitted thereafter. When the number of counted game media contained in the counting notification becomes "0" instead of "50", it can be determined that the counting process has ended.
Then, as soon as it is determined that the counting process has ended, the process corresponding to the end of the counting process may be executed, or the process corresponding to the end of the counting process may be executed after a predetermined time has elapsed since it was determined that the counting process has ended.

For example, the sub-control CPU 85 may end the counting display on the image display device 23 immediately upon determining that the counting process has been completed, or may end the counting display on the image display device 23 after a predetermined time has elapsed since determining that the counting process has been completed.
In other words, the sub-control CPU 85 may end the counting display on the image display device 23 as soon as it determines that the counting switch 47 has changed from an on state to an off state, or may end the counting display on the image display device 23 after a predetermined time has elapsed since it determined that the counting switch 47 has changed from an on state to an off state.
In addition, the sub-control CPU 85 may end the counting display on the image display device 23 immediately upon determining that the number of counted gaming media has changed from "50" to "0", or may end the counting display on the image display device 23 after a predetermined time has elapsed since determining that the number of counted gaming media has changed from "50" to "0".

In addition, when the sub-control CPU 85 determines based on the received main control command that the counting switch 47 has been pressed briefly and the counting process has been executed, it outputs a counting sound for a short press from the speaker 22, and when it determines that the counting switch 47 has been pressed for a long time and the counting process has been executed, it outputs a counting sound for a long press from the speaker 22.
In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed, it may start outputting (repeatedly playing) the counting sound (length 300 ms) for when the counting switch 47 is pressed and held down, and then, when it determines that the counting process has ended, it may stop outputting the counting sound for when the counting switch 47 is pressed and held down.

In addition, when the sub-control CPU 85 determines based on the received main control command that the counting switch 47 has been pressed and held down and the counting process has been executed, it turns on the push button lamp 88, but disables the operation of the push button 86, and then turns off the push button lamp 88 when it determines that the counting process has ended.
Furthermore, when the sub-control CPU 85 determines based on the received main control command that the counting switch 47 has been pressed and held down to execute the counting process, it reduces the volume of the game background music to a volume lower than that before the counting process was executed, and thereafter, when it determines that the counting process has ended, it returns the volume of the game background music to the volume before the counting process was executed.
The determination of whether the counting process is complete is as described above.
In addition, when the sub-control CPU 85 determines, based on the received main control command, that the counting switch 47 has been pressed briefly and the counting process has been executed, it does not display the counting in progress on the image display device 23 (does not display), does not turn on the push button lamp 88 (keeps it off), and does not reduce the volume of the game background music (maintains the volume before the counting process was executed).

FIG. 161 is a time chart (1) showing the operation mode when the counting switch 47 is pressed for a short time and when it is pressed for a long time.
Hereinafter, the operation of the counting switch 47 when it is pressed for a short time and when it is pressed for a long time will be described with reference to FIG.
In FIG. 161, at the timing of "X81," the total number of medals stored in the medal count control RWM 522 is "500," and the total number of medals displayed on the medal count display unit 121 is "500." Therefore, no counting notification is being made on the speaker 22 or the image display device 23. In addition, the counting switch 47 is in the OFF state. Therefore, no counting sound is being output from the speaker 22, no counting in progress display is being made on the image display device 23, the push button lamp 88 is turned off, and game background music is being output at a high volume from the speaker 22.

161, the counting switch 47 is turned on at timing "X82", thereafter the counting switch 47 is maintained in the on state until timing "X83", at which time the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at timing "X82" to when the counting switch 47 is turned off at timing "X83" is less than "500" ms. In other words, the counting switch 47 is pressed for a short time.
Also, in Figure 161, at timing "X83", a counting notification including data indicating the number of counted gaming media "1" is sent from the main control board 50 to the rental unit 200.
161, at timing "X83", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "1" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "499" from "500".

Furthermore, at timing "X83" in Fig. 161, the medal count control CPU 520 subtracts "1" from the display in the medal count display unit 121. As a result, the display in the medal count display unit 121 changes from "500" to "499."
Also, in Figure 161, at the timing of "X83", the sub-control CPU 85 outputs a counting sound for short presses from the speaker 22. This notifies the player that the counting switch 47 has been short pressed and the counting process has been executed.

However, in Figure 161, although the counting process is executed at the timing of "X83", the counting is not displayed on the image display device 23 (it is in a non-display state), the push button lamp 88 does not light up (it remains off), and the game background music continues to be output at a high volume from the speaker 22 (the volume is not reduced, and the volume before the counting process is maintained).
Since the counting process by short pressing is completed immediately, the volume of the game background music is not lowered but is maintained at the volume before the counting process by short pressing, thereby preventing the player from feeling uncomfortable.

161, the counting switch 47 is turned on at the timing "X88", and then the counting switch 47 is maintained in the on state until the timing "X93", at which point the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at the timing "X88" until when the counting switch 47 is turned off at the timing "X93" is "800" ms, which is more than "500" ms. In other words, the counting switch 47 is pressed and held.
Also, in Figure 161, at the timing of "X91", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200, and then, at the timing of "X93", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.

Furthermore, in Figure 161, at timing "X91", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "449" from "499". Then, at timing "X93", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "399" from "449".

Furthermore, in FIG. 161, at timing "X91", the medal count control CPU 520 starts decrementing (updating) the display of the medal count display unit 121, and at timing "X95", ends decrementing (updating) the display of the medal count display unit 121. At this time, the medal count control CPU 520 displays the display of the medal count display unit 121 by decrementing "1" from "499" to "449" over "300" ms from "X91" to "X93", and then further displays the display of the medal count display unit 121 by decrementing "1" from "449" to "399" over "300" ms from "X93" to "X95". As a result, the total medal count displayed in the medal count display unit 121 changes from "499" to "399" over "600" ms from "X91" to "X95".

Also, in Figure 161, at timing "X91", the sub-control CPU 85 outputs a counting sound (length "300" ms) for a long press from the speaker 22, and then at timing "X93", it outputs another counting sound (length "300" ms) for a long press from the speaker 22. As a result, the counting sound for a long press is output for 600 ms, from "X91" to "X95", notifying the player that the counting switch 47 has been pressed and the counting process has been executed.

In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed at the timing of "X91" in Figure 161, it may start outputting (repeatedly playing) the counting sound for when the counting switch 47 is pressed and held down, and then, when it determines that the counting switch 47 has been turned off at the timing of "X93", it may end outputting the counting sound for when the counting switch 47 is pressed and held down after a predetermined time has elapsed (at the timing of "X95").
In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed at the timing of "X91" in Figure 161, it may start outputting (repeatedly playing) the counting sound for when the counting switch 47 is pressed and held down, and then, when it determines that the number of counted gaming media has become "0" at the timing of "X95", it may end outputting the counting sound for when the counting switch 47 is pressed and held down.

Also, in Figure 161, at the timing of "X91", the sub-control CPU 85 starts the counting display on the image display device 23, then maintains the counting display on the image display device 23 until the timing of "X95", and ends the counting display on the image display device 23 at the timing of "X95". This allows the player to be informed that the counting switch 47 has been pressed and held and the counting process has been executed.
Furthermore, in Figure 161, at timing "X93", the counting switch 47 is turned off, and then at timing "X95", the counting display on the image display device 23 is ended, so after the counting switch 47 is turned off, the counting display on the image display device 23 is ended.

In the example of Figure 161, the counting display on the image display device 23 is terminated 300 ms after the counting switch 47 is turned off, but the counting display on the image display device 23 may be terminated as soon as the counting switch 47 is turned off.
Also, if it is determined that the number of counted gaming media has reached "0" at the timing of "X95", the counting display on the image display device 23 may be ended.

161, at the timing "X91", the sub-control CPU 85 starts lighting up the push button lamp 88, then keeps the push button lamp 88 lit until the timing "X95", and turns off the push button lamp 88 at the timing "X95". This notifies the player that the counting switch 47 has been pressed and held down and the counting process has been executed.
However, in Figure 161, from "X91" to "X95", the sub-control CPU 85 turns on the push button lamp 88, but disables operation acceptance of the push button 86.

The sub-control CPU 85 normally lights up the push button lamp 88 to prompt the player to operate the push button 86, but during the counting process, the sub-control CPU 85 lights up the push button lamp 88 not to prompt the player to operate the push button 86 but to notify the player that the counting process is being performed. Therefore, during the counting process, although the push button lamp 88 is turned on, the operation of the push button 86 is disabled.
Note that "operation acceptance disabled" is also referred to as "operation acceptance not possible" or "operation acceptance not permitted." When switch operation acceptance is enabled, if a switch operation is detected, a process corresponding to the switch operation is executed. However, when switch operation acceptance is disabled, even if a switch operation is detected, a process corresponding to the switch operation is not executed.

In this way, when the counting switch 47 is pressed and held down to execute the counting process, the push button lamp 88 is turned on, so that the player can be informed in an easy-to-understand manner that the counting switch 47 has been pressed and held down to execute the counting process.
Furthermore, when the push button lamp 88 is turned on, it may be mistakenly thought that the push button 86 has been prompted to be operated, and the push button 86 may be operated. However, since the acceptance of the push button 86 operation is disabled, even if the push button 86 is operated, it is possible to prevent the processing corresponding to the operation of the push button 86 from being executed.

Also, in Figure 161, at timing "X93", the counting switch 47 is turned off, and then at timing "X95", the push button lamp 88 is turned off, so after the counting switch 47 is turned off, the push button lamp 88 is turned off.
In the example of Figure 161, the push button lamp 88 is turned off 300 ms after the counting switch 47 is turned off, but the push button lamp 88 may also be turned off immediately after the counting switch 47 is turned off.
Also, at the timing of "X95", if it is determined that the number of counted gaming media has become "0", the push button lamp 88 may be turned off.

Also, in Figure 161, at the timing of "X91", the sub-control CPU 85 reduces the volume of the game background music output from the speaker 22 (reducing the volume from the volume before the counting process is executed), and then maintains the volume of the game background music at a low volume until the timing of "X95", at which point it returns the volume of the game background music to a high volume (the volume before the counting process is executed).
As described above, in Figure 161, the counting sound for a long press is output over a period of 600 ms from "X91" to "X95." During this time, the volume of the game background music is turned down to make the counting sound for a long press stand out (more noticeable), and the counting sound for a long press can be made to be heard without difficulty, so that the player can be reliably informed that the counting switch 47 has been pressed and the counting process has been executed.

Also, in Figure 161, at timing "X93", the counting switch 47 is turned off, and then at timing "X95", the volume of the game BGM is returned to the volume before the counting process was executed, so after the counting switch 47 is turned off, the volume of the game BGM is returned to the volume before the counting process was executed.
When the counting switch 47 is turned off, the volume of the game BGM is returned to the volume before the counting process is executed, so the player does not have to perform an operation to return the volume of the game BGM to the original volume, and therefore the player can be prevented from feeling bothered.
In the example of Figure 161, the volume of the game background music is returned to the volume before the counting process was executed 300 ms after the counting switch 47 was turned off, but the volume of the game background music may also be returned to the volume before the counting process was executed as soon as the counting switch 47 is turned off.
Also, if it is determined that the number of counted gaming media has become "0" at the timing of "X95", the volume of the gaming background music may be returned to the volume before the counting process was executed.
Furthermore, while the counting sound for long presses is being output, the volume of the game background music may be set to "0" (the game background music may be muted), and when the counting process by long pressing of the counting switch 47 is completed, the game background music may be output again at the volume before the counting process was executed.

FIG. 162 is a time chart (2) showing the operation mode when the counting switch 47 is pressed for a short time and when it is pressed for a long time.
In Fig. 161, the total number of medals is "500" or less, and no count notification is made. In contrast, in Fig. 162, there are cases where the total number of medals is "15,000" or more, and a count notification is made.
Below, based on Figure 162, the operation mode when the counting switch 47 is pressed for a short time and when it is pressed for a long time will be described.

In FIG. 162, at the timing of "X101," the total medal count stored in the medal count control RWM 522 is "15,100," and the total medal count displayed on the medal count display unit 121 is "15,100." Therefore, counting notifications are being issued by the speaker 22 and the image display device 23. In addition, the counting switch 47 is in the OFF state. Therefore, no counting sound is being output from the speaker 22, no counting in progress display is being displayed on the image display device 23, the push button lamp 88 is turned off, and game background music is being output at a high volume from the speaker 22.
162, at the timing of "X101", the counting notification is being made, but the game background music is output at a loud volume. In this way, since the counting notification is being made, the volume of the game background music is not reduced, and even when the counting notification is made, the volume of the game background music before the counting notification is maintained.

162, at timing "X102", the counting switch 47 is turned on, and thereafter the counting switch 47 is maintained in the on state until timing "X107", at which time the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at timing "X102" until when the counting switch 47 is turned off at timing "X107" is "800" ms, which is more than "500" ms. In other words, the counting switch 47 is pressed and held.
Also, in Figure 162, at the timing of "X105", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200, and then at the timing of "X107", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.

Furthermore, in FIG. 162, at timing "X105", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "15,050" from "15,100". Thereafter, at timing "X107", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "15,050" from "15,000".

Furthermore, in Figure 162, at timing "X105", the medal count control CPU 520 starts decrementing (updating) the display of the medal count display unit 121, and at timing "X109", ends decrementing (updating) the display of the medal count display unit 121. At this time, the medal count control CPU 520 displays the display of the medal count display unit 121 so that it decrements by "1" from "15100" to "15050" over "300" ms from "X105" to "X107", and then further displays the display of the medal count display unit 121 so that it decrements by "1" from "15050" to "15000" over "300" ms from "X107" to "X109". As a result, the total medal count displayed in the medal count display unit 121 changes from "15,100" to "15,000" over 600 ms, from "X105" to "X109."

Also, in Figure 162, at timing "X105", the sub-control CPU 85 outputs a counting sound (length "300" ms) for a long press from the speaker 22, and then at timing "X107", it outputs another counting sound (length "300" ms) for a long press from the speaker 22. As a result, the counting sound for a long press is output for 600 ms, from "X105" to "X109", notifying the player that the counting switch 47 has been pressed and the counting process has been executed.

In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed at the timing of "X105" in Figure 162, it starts outputting (repeatedly playing) the counting sound for when the counting switch 47 is pressed and held down, and then, when it determines that the counting switch 47 has been turned off at the timing of "X107", it may end the output of the counting sound for when the counting switch 47 is pressed and held down after a predetermined time has elapsed (at the timing of "X109").
In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed at the timing of "X105" in Figure 162, it may start outputting (repeatedly playing) the counting sound for when the counting switch 47 is pressed and held down, and then, when it determines that the number of counted gaming media has become "0" at the timing of "X107", it may end outputting the counting sound for when the counting switch 47 is pressed and held down.

Also, in Figure 162, at the timing of "X105", the sub-control CPU 85 starts the counting display on the image display device 23, then maintains the counting display on the image display device 23 until the timing of "X109", and ends the counting display on the image display device 23 at the timing of "X109". This allows the player to be informed that the counting switch 47 has been pressed and held and the counting process has been executed.
Furthermore, in Figure 162, at the timing of "X107", the counting switch 47 is turned off, and then at the timing of "X109", the counting display on the image display device 23 is ended, so after the counting switch 47 is turned off, the counting display on the image display device 23 is ended.
In the example of Figure 162, the counting display on the image display device 23 is terminated 300 ms after the counting switch 47 is turned off, but the counting display on the image display device 23 may be terminated as soon as the counting switch 47 is turned off.
Also, if it is determined at the timing of "X109" that the number of counted gaming media has become "0", the counting display on the image display device 23 may be ended.

162, at the timing of "X105", the sub-control CPU 85 starts lighting up the push button lamp 88, then keeps the push button lamp 88 lit until the timing of "X109", and turns off the push button lamp 88 at the timing of "X109". This notifies the player that the counting switch 47 has been pressed and held down and the counting process has been executed.
However, in Figure 162, from "X105" to "X109", the sub-control CPU 85 turns on the push button lamp 88, but disables the operation acceptance of the push button 86.

Also, in Figure 162, at timing "X107", the counting switch 47 is turned off, and then at timing "X109", the push button lamp 88 is turned off, so after the counting switch 47 is turned off, the push button lamp 88 is turned off.
In the example of Figure 162, the push button lamp 88 is turned off 300 ms after the counting switch 47 is turned off, but the push button lamp 88 may also be turned off immediately after the counting switch 47 is turned off.
Also, at the timing of "X109", if it is determined that the number of counted gaming media has become "0", the push button lamp 88 may be turned off.

Also, in Figure 162, at the timing of "X105", the sub-control CPU 85 reduces the volume of the game background music output from the speaker 22 (reducing the volume from the volume before the counting process is executed), and then maintains the volume of the game background music at a low volume until the timing of "X109", and at the timing of "X109", returns the volume of the game background music to a high volume (the volume before the counting process is executed).
As described above, in Figure 162, the counting sound for a long press is output over a period of 600 ms from "X105" to "X109." During this time, the volume of the game background music can be turned down to make the counting sound for a long press stand out, thereby reliably informing the player that the counting switch 47 has been pressed and the counting process has been executed.

Also, in Figure 162, at the timing of "X107", the counting switch 47 is turned off, and then at the timing of "X109", the volume of the game BGM is returned to the volume before the counting process was executed, so after the counting switch 47 is turned off, the volume of the game BGM is returned to the volume before the counting process was executed.
In the example of Figure 162, the volume of the game background music is returned to the volume before the counting process was executed 300 ms after the counting switch 47 was turned off, but the volume of the game background music may also be returned to the volume before the counting process was executed as soon as the counting switch 47 is turned off.
Also, if it is determined at the timing of "X109" that the number of counted gaming media has become "0", the volume of the gaming background music may be returned to the volume before the counting process was executed.

Note that at timing "X109" in Figure 162, a counting notification is being made, but the output of the counting sound ends, so the volume of the game background music is returned to the volume before the counting process was executed. In other words, at "X105" to "X109" in Figure 162, the volume of the game background music is being reduced because the counting sound is being output, not because the counting notification is being made.

Then, in Figure 162, at timing "X114", the counting switch 47 is turned on, and then the counting switch 47 remains on until timing "X115", at which point the counting switch 47 is turned off. Furthermore, the time from when the counting switch 47 is turned on at timing "X114" until when the counting switch 47 is turned off at timing "X115" is less than 500 ms. In other words, the counting switch 47 is pressed for a short time.

Also, in FIG. 162, at the timing of "X115", the main control board 50 sends a counting notification including data indicating the number of counted gaming media "1" to the rental unit 200.
162, at timing "X115", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "1" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "14,999" from "15,000".

Furthermore, at the timing of "X115" in Fig. 162, the medal count control CPU 520 subtracts "1" from the display in the medal count display unit 121. As a result, the display in the medal count display unit 121 changes from "15000" to "14999".
Also, in Figure 162, at the timing of "X115", the total number of medals stored in the medal count control RWM 522 becomes "14,999" (less than "15,000"), so the sub-control CPU 85 ends the output of the counting notification from the speaker 22 and the image display device 23.

Furthermore, at the timing of "X115" in Figure 162, the sub-control CPU 85 outputs a counting sound for short presses from the speaker 22. This notifies the player that the counting switch 47 has been short pressed and the counting process has been executed.
However, in Figure 162, at the timing of "X115", the counting process is executed and the counting sound for a short press is output from the speaker 22, but the counting is not displayed on the image display device 23 (it is in a non-display state), the push button lamp 88 does not light up (it remains off), and the game background music continues to be output from the speaker 22 at a high volume (the volume is not reduced, and the volume before the counting process is maintained).

Next, the operation modes when the counting switch 47 and the lending switch 202 are operated will be described.
When the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 displays a counting in progress message on the image display device 23 .
In contrast, when the lending switch 202 is operated to execute the lending process, the sub-control CPU 85 does not display on the image display device 23 an indication that the item is being lent.
In addition, when the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 outputs a counting sound for a long press from the speaker 22 .
In contrast, when the rental switch 202 is operated and rental processing is executed, the sub-control CPU 85 outputs a rental sound from the speaker 22.

Here, the "rental sound" is a sound that indicates that the item is being rented. In this embodiment, when the rental switch 202 is operated and the rental process is executed, the sub-control CPU 85 outputs a "ping"-like sound as the rental sound from the speaker 22. The length of the rental sound from the beginning to the end is 450 ms.
Note that the length of the rental sound of "450" ms is an example, and the length of the rental sound is not limited to "450" ms, but can be any length of "300" ms or more, and can be set appropriately, for example, to "500" ms or "1" second.

In addition, when the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 turns on the push button lamp 88, but disables the operation acceptance of the push button 86, and turns off the push button lamp 88 after the counting switch 47 is turned off.
In contrast, when the rental switch 202 is operated to execute the rental process, the sub-control CPU 85 does not turn on the push button lamp 88, but keeps it off.

In addition, when game background music is being output from the speaker 22, when the counting switch 47 is pressed and held down to execute counting processing, the sub-control CPU 85 reduces the volume of the game background music to a volume lower than that before the counting processing is executed, and when the counting processing is completed, returns the volume of the game background music to the volume before the counting processing is executed.
On the other hand, when game background music is being output from the speaker 22 and the lending switch 202 is operated to execute the lending process, the sub-control CPU 85 outputs the lending sound from the speaker 22, but does not reduce the volume of the game background music, and maintains the volume before the counting process is executed.
In addition, when game background music is being output from the speaker 22, if the loan switch 22 is operated to execute the loan process and the total number of medals stored in the medal count control RWM 522 becomes "15,000" or more, the sub-control CPU 85 outputs a counting notification on the speaker 22 and the image display device 23, but does not reduce the volume of the game background music, and maintains the volume that was present before the counting process was executed.

As described above, the medal count control CPU 520 sends a medal count control command to the main control CPU 510. In addition to information indicating whether the counting switch 47 is on or off and information indicating that the counting process has been performed by pressing and holding the counting switch 47, this medal count control command can also include information indicating that a loan notification containing data on the number of loaned gaming media "50" has been received, and information indicating that a loan process has been performed that adds the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM 522.

The main control CPU 510 also sends a main control command to the sub-control CPU 85. This main control command can include information indicating whether the counting switch 47 is on or off, information indicating that the counting process was performed by pressing and holding the counting switch 47, information indicating that a loan notification including data on the number of loaned gaming media "50" was received, and information indicating that a loan process was performed to add the number of loaned gaming media "50" to the total number of medals stored in the medal count control RWM 522.

Then, when the sub-control CPU 85 determines, based on the received main control command, that a lending process has been executed to add the number of lending game media "50" to the total number of medals stored in the medal count control RWM 522, it outputs a lending sound from the speaker 22.
In addition, when the sub-control CPU 85 determines, based on the received main control command, that a lending process has been executed in which the number of lending game media "50" is added to the total number of medals stored in the medal count control RWM 522, it does not display on the image display device 23 an indication that the game is being lent, does not turn on the push button lamp 88 (it remains off), and does not reduce the volume of the game background music (it maintains the volume before the counting process was executed).

FIG. 163 is a time chart (1) showing the operation mode when the counting switch 47 and the lending switch 202 are operated.
Hereinafter, the operation modes when the counting switch 47 and the lending switch 202 are operated will be described with reference to FIG.
In FIG. 163, at the timing of "X121," the total number of medals stored in the medal count control RWM 522 is "500," and the total number of medals displayed on the medal count display unit 121 is "500." Therefore, no counting notification is being made by the speaker 22 or the image display device 23. Furthermore, the counting switch 47 is in the OFF state. Therefore, no counting sound is being output from the speaker 22, no counting display is being made on the image display device 23, the push button lamp 88 is in the OFF state, and game background music is being output at a high volume from the speaker 22. Furthermore, the lending switch 202 is in the OFF state. Therefore, no lending sound is being output from the speaker 22.

163, at timing "X122", counting switch 47 is turned on, thereafter counting switch 47 is maintained in the on state until timing "X125", at which time counting switch 47 is turned off. Also, the time from when counting switch 47 is turned on at timing "X122" until when counting switch 47 is turned off at timing "X125" is "550" ms, which is more than "500" ms. In other words, counting switch 47 is pressed and held.
Also, in Figure 163, at the timing of "X125", the main control board 50 sends a counting notification including the data of the number of counted gaming media "50" to the rental unit 200.

163, at timing "X125", the medal count control CPU 520 executes counting processing to subtract the number of counted game media, "50", from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "450" from "500".
163, at the timing of "X125", the medal count control CPU 520 starts decrementing (updating) the display of the medal count display unit 121, and at the timing of "X127", ends the decrementing (updating) of the display of the medal count display unit 121. At this time, the medal count control CPU 520 takes "300" ms from "X125" to "X127" to display the display of the medal count display unit 121 so that it decrements by "1" from "500" to "450".

163, at the timing of "X125", the sub-control CPU 85 outputs a counting sound (length "300" ms) for a long press from the speaker 22. As a result, the counting sound for a long press is output over the "300" ms from "X125" to "X127", thereby informing the player that the counting switch 47 has been pressed and the counting process has been executed.
Furthermore, in Figure 163, at the timing of "X125", the sub-control CPU 85 starts the counting display on the image display device 23, then maintains the counting display on the image display device 23 until the timing of "X127", and ends the counting display on the image display device 23 at the timing of "X127". This allows the player to be informed that the counting switch 47 has been pressed and held and the counting process has been executed.

163, at the timing of "X125", the sub-control CPU 85 starts lighting up the push button lamp 88, then keeps the push button lamp 88 lit until the timing of "X127", and turns off the push button lamp 88 at the timing of "X127". This notifies the player that the counting switch 47 has been pressed and held down and the counting process has been executed.
However, in Figure 163, between "X125" and "X127", the sub-control CPU 85 turns on the push button lamp 88, but disables operation acceptance of the push button 86.

Furthermore, in Figure 163, at the timing of "X125", the sub-control CPU 85 reduces the volume of the game background music output from the speaker 22 (reducing the volume from before the counting process was executed), and then maintains the volume of the game background music at a low volume until the timing of "X127", and at the timing of "X127", returns the volume of the game background music to a high volume (the volume from before the counting process was executed).
In Figure 163, a counting sound for a long press is output between "X125" and "X127", but by turning down the volume of the game background music during that time, the counting sound for a long press can be made more prominent, so that the player can be reliably informed that the counting switch 47 has been pressed and the counting process has been executed.

Then, in Figure 163, at timing "X133", the lending switch 202 is turned on, and then at timing "X134", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
163, at timing "X134", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "500" from "450".

Furthermore, in Figure 163, at timing "X134", the medal count control CPU 520 starts incrementing (updating) the display of the medal count display unit 121, and at timing "X136", ends incrementing (updating) the display of the medal count display unit 121. At this time, the medal count control CPU 520 takes "300" ms to display the display of the medal count display unit 121 by "1" from "450" to "500".

Furthermore, at the timing of "X134" in Figure 163, the sub-control CPU 85 outputs a lending sound (length "450" ms) from the speaker 22. As a result, the lending sound is output over the "450" ms from "X134" to "X137", thereby informing the player that the lending switch 202 has been operated and the lending process has been executed.
However, in Figure 163, at the timing of "X134", the lending process is executed and a lending sound is output from the speaker 22, but no display is made on the image display device 23 to indicate that lending is in progress, the push button lamp 88 does not light up (it remains off), and the game background music continues to be output from the speaker 22 at a high volume (the volume is not reduced, and the volume before the lending process was executed is maintained).
Since the rental switch 202 is usually not operated continuously but only once, the rental process also ends immediately. Therefore, even if the rental switch 202 is operated while the game background music is being output, the rental process ends immediately, and by maintaining the volume of the game background music, the player does not feel uncomfortable and the interest of the player is not lost.

FIG. 164 is a time chart (2) showing the operation mode when the counting switch 47 and the lending switch 202 are operated.
In Fig. 163, the total number of medals is "500" or less, and no count notification is made. In contrast, in Fig. 164, there are cases where the total number of medals is "15,000" or more, and a count notification is made.
Hereinafter, the operation modes when the counting switch 47 and the lending switch 202 are operated will be described with reference to FIG.

In FIG. 164, at the timing of "X141," the total number of medals stored in the medal count control RWM 522 is "15,000," and the total number of medals displayed on the medal count display unit 121 is "15,000." Therefore, counting notifications are being issued by the speaker 22 and the image display device 23. In addition, the counting switch 47 is in the OFF state. Therefore, no counting sound is being output from the speaker 22, no counting in progress display is being displayed on the image display device 23, the push button lamp 88 is turned off, and game background music is being output at a high volume from the speaker 22.
164, at the timing of "X141", the counting notification is being made, but the game background music is output at a high volume. In this way, since the counting notification is being made, the volume of the game background music is not reduced, and even when the counting notification is made, the volume of the game background music before the counting notification is maintained.

164, the counting switch 47 is turned on at the timing "X142", thereafter the counting switch 47 is maintained in the on state until the timing "X145", and at the timing "X145", the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at the timing "X142" until when the counting switch 47 is turned off at the timing "X145" is "550" ms, which is more than "500" ms. In other words, the counting switch 47 is pressed and held.
Also, in FIG. 164, at timing "X145", the main control board 50 sends a counting notification including data on the number of counted gaming media "50" to the rental unit 200.

164, at timing "X145", the medal count control CPU 520 executes counting processing to subtract the number of counted game media, "50", from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "14,950" from "15,000".
164, at the timing of "X145", the medal count control CPU 520 starts decrementing (updating) the display of the medal count display unit 121, and at the timing of "X147", ends the decrementing (updating) of the display of the medal count display unit 121. At this time, the medal count control CPU 520 takes "300" ms from "X145" to "X147" to display the display of the medal count display unit 121 so that it decrements by "1" from "15000" to "14950".

164, at the timing of "X145", the sub-control CPU 85 outputs a counting sound (length "300" ms) for a long press from the speaker 22. As a result, the counting sound for a long press is output over the "300" ms from "X145" to "X147", thereby informing the player that the counting switch 47 has been pressed and the counting process has been executed.
Furthermore, in Figure 164, at the timing of "X145", the sub-control CPU 85 starts the counting display on the image display device 23, then maintains the counting display on the image display device 23 until the timing of "X147", and ends the counting display on the image display device 23 at the timing of "X147". This allows the player to be informed that the counting switch 47 has been pressed and held and the counting process has been executed.

Furthermore, in Figure 164, at the timing of "X145", the sub-control CPU 85 starts lighting up the push button lamp 88, then keeps the push button lamp 88 lit until the timing of "X147", and turns off the push button lamp 88 at the timing of "X147". This notifies the player that the counting switch 47 has been pressed and held down and the counting process has been executed.
However, in Figure 164, between "X145" and "X147", the sub-control CPU 85 turns on the push button lamp 88, but disables operation acceptance of the push button 86.

Also, in Figure 164, at the timing of "X145", the sub-control CPU 85 reduces the volume of the game background music output from the speaker 22 (reducing the volume from the volume before the counting process is executed), and then maintains the volume of the game background music at a low volume until the timing of "X147", and at the timing of "X147", returns the volume of the game background music to a high volume (the volume before the counting process is executed).
As described above, in Figure 164, the counting sound for long presses is output between "X145" and "X147", but by turning down the volume of the game background music during that time, the counting sound for long presses can be made to stand out, so that the player can be reliably informed that the counting switch 47 has been pressed and the counting process has been executed.

Also, in Figure 164, at timing "X145", the sub-control CPU 85 ends the output of the count notification from the speaker 22 and the image display device 23.
Furthermore, in Figure 164, between "X145" and "X154", the sub-control CPU 85 stops output of the count notification from the speaker 22 and the image display device 23.
Then, in Figure 164, at timing "X153", the lending switch 202 is turned on, and then at timing "X154", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
164, at timing "X154", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "15,000" from "14,950".

Furthermore, in Fig. 164, at the timing of "X154", the medal count control CPU 520 starts incrementing (updating) the display of the medal count display unit 121, and at the timing of "X156", ends the incrementing (updating) of the display of the medal count display unit 121. At this time, the medal count control CPU 520 takes "300" ms from "X154" to "X156" to display the display of the medal count display unit 121 by adding (incrementing) "1" at a time from "14950" to "15000".
Furthermore, at the timing of "X154" in Figure 164, the sub-control CPU 85 outputs a lending sound (length "450" ms) from the speaker 22. As a result, the lending sound is output over the "450" ms from "X154" to "X157", thereby informing the player that the lending switch 202 has been operated and the lending process has been executed.

Also, in Figure 164, at timing "X154", the sub-control CPU 85 starts outputting counting notification from the speaker 22 and image display device 23.
However, in Figure 164, at the timing of "X154", the lending process is executed and the speaker 22 and image display device 23 start outputting a counting notification, but the image display device 23 does not display any indication that the device is being lent, the push button lamp 88 does not light up (it remains off), and the game background music continues to be output at a high volume from the speaker 22 (the volume is not reduced, and the volume before the lending process was executed is maintained).
Furthermore, since the game can continue even if the total number of medals stored in the medal count control RWM 522 exceeds "15,000", even if the lending switch 202 is operated and the lending process is executed while the game BGM is being output, and the total number of medals exceeds "15,000" and a counting notification is executed, the volume of the game BGM is maintained so that the player does not feel uncomfortable and the player's interest is not lost.

Next, the operation when the counting switch 47 is pressed for a long time and when the door is detected to be open will be described.
When the counting switch 47 is pressed and held to execute the counting process, the sub-control CPU 85 displays the counting in progress on the image display device 23, outputs the counting sound for when the switch is pressed and held from the speaker 22, and turns on the push button lamp 88, but disables the operation of the push button 86.
In addition, when the front door 16 is opened, the door switch 17 is turned on, and the main control board 50 (main control CPU 510) detects that the front door 16 is open, the sub-control CPU 85 issues a door open notification via the speaker 22 and the image display device 23 and turns on the push button lamp 88, but disables operation of the push button 86.
Thereafter, the front door 16 is closed, the door switch 17 is turned off, and the sub-control CPU 85 keeps the push button lamp 88 lit until a predetermined time (450 ms) has elapsed since the main control board 50 detected the closure of the front door 16, and when the predetermined time has elapsed since the main control board 50 detected the closure of the front door 16, the sub-control CPU 85 turns off the push button lamp 88.

Here, when the main control board 50 (main control CPU 510) detects that the front door 16 is open (referred to as "door open" or "door error", etc.) due to the door switch 17 being turned on, it issues an alert indicating that the front door 16 is open (referred to as "door open alert" or "door error alert", etc.).
Specifically, the main control board 50 displays a code (for example, "dE") indicating that the front door 16 is open on the number of wins display unit 78 as a door open notification.
In addition, when the main control board 50 detects that the front door 16 is open by the door switch 17 being turned on, it sends a command indicating that the front door 16 is open (referred to as a "door open command" or "door error command", etc.) to the sub-control board 80.

Then, when the sub-control board 80 (sub-control CPU 85) receives the door open command, it executes a door open notification on the speaker 22 and the image display device 23. Specifically, as the door open notification, the sub-control board 80 outputs (repeatedly plays) a voice message saying "Door is open" from the speaker 22 and displays the words "Door open" on the image display device 23.
Furthermore, when the sub-control board 80 (sub-control CPU 85) receives a door open command, it turns on the push button lamp 88 but disables operation of the push button 86. This allows players and parlor staff to be notified that the front door 16 has been opened.
Furthermore, when the push button lamp 88 is turned on, it may be mistakenly thought that the push button 86 has been prompted to be operated, and the push button 86 may be operated. However, since the acceptance of the push button 86 operation is disabled, even if the push button 86 is operated, the process corresponding to the operation of the push button 86 is not executed.

In addition, a release switch (not shown) for releasing the door open notification is provided near the locking device on the back side of the front door 16 (the side opposite the side facing the player). When the door key is inserted into the door key insertion slot and turned counterclockwise by approximately 45 degrees, the release switch changes from an OFF state to an ON state. In other words, when the door key is turned by approximately 45 degrees in the opposite direction to when unlocking the front door 16, the release switch changes from an OFF state to an ON state.

As described above, the door lock is released when the door key is inserted into the door key slot and turned 90 degrees clockwise. When the front door 16 is pulled in the unlocked state, the front door 16 rotates around the hinges and opens.
Furthermore, when the front door 16 is closed, the door switch 17 is turned off, but once the door open notification is executed, it is not cancelled simply by closing the front door 16 and turning the door switch 17 off, but continues until the release switch changes from the off state to the on state.

Then, while the door open notification is being executed, the front door 16 is closed to turn the door switch 17 off, and in this state, the door key is turned counterclockwise (the opposite direction to when the front door 16 is unlocked) by about 45 degrees to turn the release switch from the off state to the on state, thereby canceling the door open notification.
In this way, the operation of turning the door key in the opposite direction to that for unlocking the front door 16 is the operation for canceling the door open notification (cancellation operation).
It is also possible to configure the system so that when the front door 16 is closed and the door switch 17 is turned off, the door open notification is cancelled without the need to operate the cancellation switch.

Also, when the door open notification is cancelled, the main control board 50 displays the number of wins before displaying "dE" on the win number display 78.
Furthermore, when the release switch changes from an off state to an on state, the main control board 50 sends a command indicating the release of the door open notification (referred to as an ``alert release command'' or ``error release command'', etc.) to the sub-control board 80.
Then, when the sub-control board 80 receives the notification cancel command, it ends the door open notification on the speaker 22 and the image display device 23.

In addition, when the main control board 50 detects that the front door 16 is closed by the door switch 17 being turned off, it sends a command indicating that the front door 16 is closed (referred to as a "door close command") to the sub-control board 80.
The sub-control board 80 (sub-control CPU 85) then keeps the push button lamp 88 lit until a predetermined time (450 ms) has elapsed since the door close command was received, and turns off the push button lamp 88 once the predetermined time has elapsed since the door close command was received.
In this way, by changing the manner in which the push button lamp 88 is turned off when the counting switch 47 is pressed and held down and when the opening of the front door 16 is detected, it is possible to distinguish whether the counting switch 47 is pressed and held down or the opening of the front door 16 is detected.
In addition, the player can be made aware that the illumination of the push button lamp 88 when the counting switch 47 is pressed and held is not an error notification.

Note that the predetermined time of 450 ms from receiving the door close command until the push button lamp 88 is turned off is an example, and the predetermined time from receiving the door close command until the push button lamp 88 is turned off is not limited to 450 ms, and can be set appropriately, for example, to 500 ms or 1 second.
The sub-control board 80 may also turn off the push button lamp 88 immediately upon receiving a door close command.

FIG. 165 is a time chart showing the operation when the counting switch 47 is pressed and held and when the door is detected to be open.
Below, based on Figure 165, we will explain the operation when the counting switch 47 is pressed and held and when the door is detected to be open.
In Fig. 165, at the timing of "X161", the total medal count stored in the medal count control RWM 522 is "500", and the total medal count displayed on the medal count display unit 121 is "500". In addition, the count switch 47 is in the OFF state. Therefore, no counting sound is being output from the speaker 22, no counting in progress display is being displayed on the image display device 23, and the push button lamp 88 is in the OFF state.

165, at timing "X162", the counting switch 47 is turned on, and thereafter the counting switch 47 is maintained in the on state until timing "X167", at which time the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at timing "X162" until when the counting switch 47 is turned off at timing "X167" is "800" ms, which is more than "500" ms. In other words, the counting switch 47 is pressed and held.
Also, in Figure 165, at the timing of "X165", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200, and then, at the timing of "X167", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.

Furthermore, in Figure 165, at timing "X165", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "450" from "500". Thereafter, at timing "X167", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "400" from "450".

Furthermore, in FIG. 165, at timing "X165", the medal count control CPU 520 starts decrementing (updating) the display of the medal count display unit 121, and at timing "X169", ends decrementing (updating) the display of the medal count display unit 121. At this time, the medal count control CPU 520 displays the display of the medal count display unit 121 by decrementing "1" from "500" to "450" over "300" ms from "X165" to "X167", and then displays the display of the medal count display unit 121 by decrementing "1" from "450" to "400" over a further "300" ms from "X167" to "X169". As a result, the total medal count displayed in the medal count display unit 121 changes from "500" to "400" over "600" ms from "X165" to "X169".

Also, in Figure 165, at timing "X165", the sub-control CPU 85 outputs a counting sound (length "300" ms) for a long press from the speaker 22, and then at timing "X167", it outputs another counting sound (length "300" ms) for a long press from the speaker 22. As a result, the counting sound for a long press is output for 600 ms from "X165" to "X169", notifying the player that the counting switch 47 has been pressed and the counting process has been executed.

In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed at the timing of "X165" in Figure 165, it starts outputting (repeatedly playing) the counting sound for when the counting switch 47 is pressed and held down, and then, when it determines that the counting switch 47 has been turned off at the timing of "X167", it may end the output of the counting sound for when the counting switch 47 is pressed and held down after a predetermined time has elapsed (at the timing of "X169").
In addition, when the sub-control CPU 85 determines that the counting switch 47 has been pressed and held down and the counting process has been executed at the timing of "X165" in Figure 165, it may start outputting (repeatedly playing) the counting sound for when the counting switch 47 is pressed and held down, and then, when it determines that the number of counted gaming media has become "0" at the timing of "X169", it may end outputting the counting sound for when the counting switch 47 is pressed and held down.

Also, in Figure 165, at the timing of "X165", the sub-control CPU 85 starts the counting display on the image display device 23, then maintains the counting display on the image display device 23 until the timing of "X169", and ends the counting display on the image display device 23 at the timing of "X169". This allows the player to be informed that the counting switch 47 has been pressed and held and the counting process has been executed.
In the example of Figure 165, the counting display on the image display device 23 is terminated 300 ms after the counting switch 47 is turned off (at timing "X169"), but the counting display on the image display device 23 may also be terminated as soon as the counting switch 47 is turned off (at timing "X167").
Also, if it is determined that the number of counted gaming media has reached "0" at the timing of "X169", the counting display on the image display device 23 may be ended.

Also, in FIG. 165, at the timing of "X165", the sub-control CPU 85 starts lighting up the push button lamp 88, then keeps the push button lamp 88 lit until the timing of "X169", and then turns off the push button lamp 88 at the timing of "X169". This notifies the player that the counting switch 47 has been pressed and held down and the counting process has been executed. It is also possible to confirm that the push button lamp 88 is lit up.
However, in Figure 165, from "X165" to "X169", the sub-control CPU 85 turns on the push button lamp 88, but disables the operation of the push button 86.

In the example of Figure 165, the push button lamp 88 is turned off 300 ms after the counting switch 47 is turned off (at timing "X169"), but the push button lamp 88 may also be turned off as soon as the counting switch 47 is turned off (at timing "X167").
Also, at the timing of "X169", if it is determined that the number of counted gaming media has become "0", the push button lamp 88 may be turned off.

Then, at the timing of "X171" in Figure 165, the front door 16 is opened, the door switch 17 is turned on, and when the main control CPU 510 detects that the front door 16 has been opened, the sub-control CPU 85 executes a door open notification on the speaker 22 and the image display device 23 and turns on the push button lamp 88.
Thereafter, at timing "X173" in Figure 165, when the front door 16 is closed and the door switch 17 is turned off, the main control CPU 510 detects that the front door 16 has been closed.

Thereafter, the secondary control CPU 85 keeps the push button lamp 88 lit until timing "X176" (450 ms has elapsed since the main control CPU 510 detected the closure of the front door 16), and turns off the push button lamp 88 at timing "X176".
That is, in FIG. 165, the push button lamp 88 starts to light up at the timing "X171", and then remains lit until the timing "X176", at which point the push button lamp 88 is turned off. In this way, by lighting the push button lamp 88 in a manner different from when the counting switch 47 is pressed and held, it is possible to notify the player and parlor staff that the front door 16 has been opened. It is also possible to confirm that the push button lamp 88 is lit.
However, in Figure 165, from "X171" to "X176", the sub-control CPU 85 turns on the push button lamp 88, but disables operation acceptance of the push button 86.

Furthermore, as described above, even if the front door 16 is closed and the door switch 17 is turned off, the door open notification is not cancelled (ended) by that alone, and the door open notification continues until the release switch changes from the off state to the on state.
Then, when the release switch is turned on at the timing of "X177" in Figure 165, the door open notification is released (ended).

Next, the relationship between the counting sound when the counting switch 47 is pressed briefly and the lending sound when the lending switch 202 is operated will be described.
When the counting process is executed by short-pressing the counting switch 47 (the time from when it is turned on to when it is turned off is less than 500 ms), the sub-control CPU 85 outputs a counting sound for short presses from the speaker 22. The counting sound for short presses is a "pop"-like sound, and is 200 ms long from start to finish, which is shorter than the counting sound for long presses (300 ms) and the transmission intervals of count notifications and loan notifications (300 ms).
Note that the length of the counting sound when the button is pressed briefly, "200" ms, is an example, and the length of the counting sound when the button is pressed briefly is not limited to "200" ms, but can be any length less than "300" ms, and can be set appropriately, for example, to "100" ms, "150" ms, etc.
Furthermore, the transmission interval of 300 ms for the counting notification and the lending notification is an example, and the transmission interval for the counting notification and the lending notification can be set as appropriate.

Furthermore, when the rental switch 202 is operated to execute the rental process, the sub-control CPU 85 outputs a rental sound from the speaker 22. The rental sound is a "ping-pong" sound, and is 450 ms long from start to finish, which is longer than the counting sound (300 ms) for a long press and the transmission interval (300 ms) of the counting notification and rental notification.
Note that the length of the rental sound of "450" ms is an example, and the length of the rental sound is not limited to "450" ms, but can be any length of "300" ms or more, and can be set appropriately, for example, to "500" ms or "1" second.

FIG. 166 is a time chart showing the relationship between the counting sound when the counting switch 47 is pressed briefly and the lending sound when the lending switch 202 is operated.
Below, based on Figure 166, we will explain the relationship between the counting sound when the counting switch 47 is pressed briefly and the lending sound when the lending switch 202 is operated.
In FIG. 166, at the timing of "X181", the total medal count stored in the medal count control RWM 522 is "1", and the total medal count displayed on the medal count display unit 121 is "1". In addition, the count switch 47 and the lending switch 202 are both in the OFF state. Therefore, neither the counting sound nor the lending sound is output from the speaker 22.

166, the counting switch 47 is turned on at the timing "X182", thereafter the counting switch 47 is maintained in the on state until the timing "X183", and at the timing "X183" the counting switch 47 is turned off. Also, the time from when the counting switch 47 is turned on at the timing "X182" to when the counting switch 47 is turned off at the timing "X183" is "200" ms, which is less than "500" ms. In other words, the counting switch 47 is short-pressed.
Also, in Figure 166, at the timing of "X183", a counting notification including data indicating the number of counted gaming media "1" is sent from the main control board 50 to the rental unit 200.

166, at timing "X183", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "1" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "0" from "1".
Furthermore, at the timing of "X183" in Fig. 166, the medal count control CPU 520 subtracts "1" from the display in the medal count display unit 121. As a result, the display in the medal count display unit 121 changes from "1" to "0."

166, at the timing of "X183", the sub-control CPU 85 outputs a counting sound for short presses from the speaker 22. As described above, the counting sound for short presses is a sound like "pon" and has a length of 200 ms from start to finish, which is shorter than the counting sound for long presses (300 ms) and the transmission intervals of counting notifications and loan notifications (300 ms).
When the counting switch 47 is pressed briefly to execute counting processing, a counting sound specific to the counting of medals by the short press is output, thereby informing the player that the medals have been counted by the short press.
Furthermore, since the transmission interval for the counting notification is 300 ms, when the counting switch 47 is repeatedly pressed shortly, the counting process can be executed every 300 ms by shortly pressing the counting switch 47. By setting the length from the start to the end of the counting sound for short pressing to 200 ms, which is shorter than the transmission interval for the counting notification, even if the counting switch 47 is repeatedly pressed shortly, the counting sound for short pressing can be output each time the counting switch 47 is shortly pressed, and can be heard by the player.

Then, in Figure 166, at timing "X187", the lending switch 202 is turned on, and then at timing "X188", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
166, at the timing of "X188", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 changes from "0" to "50".

Furthermore, in Figure 166, at timing "X188", the medal count control CPU 520 starts incrementing (updating) the display of the medal count display unit 121, and at timing "X190", ends incrementing (updating) the display of the medal count display unit 121. At this time, the medal count control CPU 520 displays the display of the medal count display unit 121 by adding (incrementing) "1" at a time from "0" to "50" over "300" ms from "X188" to "X190".

Furthermore, in Fig. 166, for 450 ms from "X188" to "X191", the sub-control CPU 85 outputs a lending sound from the speaker 22. As described above, the lending sound is a "ping-pong" sound, and is 450 ms long from start to finish, which is longer than the counting sound (300 ms) for long presses and the transmission interval (300 ms) for counting notifications and lending notifications.
When the lending switch 202 is operated to execute lending processing, a lending sound specific to the lending of medals is outputted, thereby informing the player that the medals have been lent.
Furthermore, although the transmission interval for the rental notice is 300 ms, the rental switch 202 is normally not operated continuously but only once. By setting the length from the beginning to the end of the rental sound to 450 ms, which is longer than the transmission interval for the rental notice, the rental sound can be clearly heard by the player.

Next, the manner in which the rental sound is output when the rental switch 202 is operated repeatedly will be described.
As described above, when the rental switch 202 is operated and the rental process is executed, the sub-control CPU 85 outputs a rental sound from the speaker 22. The length from the beginning to the end of the rental sound is 450 ms, which is longer than the 300 ms transmission interval of the rental notification.
Furthermore, since the interval for sending the rental notification is "300" ms, when the rental switch 202 is operated continuously (repeatedly turned on and off), the rental process can be executed at the shortest interval of "300" ms.

In other words, a rental notification is sent from the rental unit 200 to the main control board 50 at intervals of 300 ms. When the rental switch 202 is repeatedly turned on and off within a short period of time, each rental notification sent at 300 ms intervals contains the data for the number of rental game media "50." As a result, when the rental switch 202 is repeatedly turned on and off within a short period of time, the medal count control CPU 520 can execute rental processing that adds the number of rental game media "50" to the total number of medals stored in the medal count control RWM 522 at intervals of at least 300 ms.

When the rental switch 202 is operated continuously (repeatedly turned on and off) and the rental process is executed at intervals of 300 ms, the sub-control CPU 85 outputs the next rental sound from the beginning before the previous rental sound is output to the end.
As described above, the length of the rental sound from its beginning to its end is 450 ms, so if the rental process is executed at 300 ms intervals, the next rental process will be executed before the first rental sound has been output to its end. In such a case, the sub-control CPU 85 outputs the next rental sound from its beginning before the first rental sound has been output to its end.

Figure 167 is a time chart (1) showing the output mode of the rental sound when the rental switch 202 is operated continuously.
Hereinafter, based on FIG. 167, the output mode of the rental sound when the rental switch 202 is operated repeatedly will be described.
In FIG. 167, at the timing of "X201", the total number of medals stored in the medal count control RWM 522 is "0", and the total number of medals displayed on the medal count display unit 121 is "0". Also, the lending switch 202 is in the OFF state. Therefore, no lending sound is output from the speaker 22.

After that, in FIG. 167, at timing "X202", the lending switch 202 is turned on, and at timing "X203", the lending switch 202 is turned off (the "first" operation is performed). Also, at timing "X204", the lending switch 202 is turned on, and at timing "X205", the lending switch 202 is turned off (the "second" operation is performed). Furthermore, at timing "X206", the lending switch 202 is turned on, and at timing "X207", the lending switch 202 is turned off (the "third" operation is performed). In other words, the operation of turning the lending switch 202 on and off is repeated at intervals of no more than "300" ms (consecutive operations).

In this case, in Figure 167, at timing "X203", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50, and then at timing "X205", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50, and again at timing "X207", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50. In other words, in Figure 167, at timing "X203" to "X207", each lending notification sent at intervals of "300" ms includes data on the number of lending gaming media "50".

167, at timing "X203", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 changes from "0" to "50".
167, at the timing of "X205", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "100" from "50".
167, at timing "X207", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "150" from "100".

Also, in Figure 167, at the timing of "X203", the medal count control CPU 520 starts adding (updating) the display of the medal count display unit 121, and at the timing of "X209", ends adding (updating) the display of the medal count display unit 121.
At this time, the medal count control CPU 520 takes 300 ms to display the display in the medal count display unit 121 from "0" to "50" by incrementing "1" from "X203" to "X205". Next, it takes 300 ms to display the display in the medal count display unit 121 from "50" to "100" by incrementing "1" from "X205" to "X207". After that, it takes 300 ms to display the display in the medal count display unit 121 from "100" to "150" by incrementing "1".
As a result, the total medal count displayed in the medal count display section 121 changes from "0" to "150" over "900" ms, from "X203" to "X209".

Also, in Figure 167, at timing "X203", the sub-control CPU 85 starts outputting the "first" rental sound from the speaker 22. As mentioned above, the length from the beginning to the end of the rental sound is "450" ms, which is longer than the transmission interval of the rental notification ("300" ms). Therefore, at timing "X205" in Figure 167, the next rental process will be executed before the "first" rental sound has been output to its end. Then, at timing "X205" in Figure 167, the sub-control CPU 85 outputs the "second" rental sound from its beginning before the "first" rental sound has been output to its end.

Furthermore, at the timing of "X207" in Fig. 167, the next rental process will be executed before the "second" rental sound has been output to its end.Then, at the timing of "X207" in Fig. 167, the sub-control CPU 85 outputs the "third" rental sound from its beginning before the "second" rental sound has been output to its end.
In addition, in Figure 167, at the timing of "X209", the number of rental gaming media in the rental notification is "0", and the rental process is not executed, so the "third" rental sound is output until the end (timing of "X210" in Figure 167).

In this way, in the example shown in Figure 167, the rental process is executed at the rental notification sending interval, so if the next rental process is executed before one rental sound has been output to its end, the sub-control CPU 85 will not output the one rental sound to its end, but will overwrite and output the next rental sound from the beginning.
This allows the lending sound to be output from the beginning each time the lending process is executed, making it easier for the player to understand the number of times the lending process has been executed (the number of times the lending switch 202 has been operated).

Next, other output modes of the rental sound when the rental switch 202 is operated repeatedly will be described.
Figure 168 is a time chart (2) showing the output mode of the rental sound when the rental switch 202 is operated continuously.
In Figure 167, the rental process is executed at the rental notification transmission interval, so that if the next rental process is executed before one rental sound is output to its end, the first rental sound is not output to its end, but the next rental sound is overwritten and output from the beginning.
In contrast, in Figure 168, the rental process is executed at the rental notification transmission interval, so that if the next rental process is executed before one rental sound has been output to its end, the one rental sound is output to its end, and the next rental sound is output from its beginning based on the execution of the subsequent rental process.

Hereinafter, based on FIG. 168, other output modes of the rental sound when the rental switch 202 is operated continuously will be described.
In FIG. 168, at the timing of "X221", the total number of medals stored in the medal count control RWM 522 is "0", and the total number of medals displayed on the medal count display unit 121 is "0". Also, the lending switch 202 is in the OFF state. Therefore, no lending sound is output from the speaker 22.

After that, in FIG. 168, at timing "X222", the lending switch 202 is turned on, and at timing "X223", the lending switch 202 is turned off (the "first" operation is performed). Also, at timing "X224", the lending switch 202 is turned on, and at timing "X225", the lending switch 202 is turned off (the "second" operation is performed). Furthermore, at timing "X226", the lending switch 202 is turned on, and at timing "X227", the lending switch 202 is turned off (the "third" operation is performed). In other words, the operation of turning the lending switch 202 on and off is repeated at intervals of no more than "300" ms (consecutive operations).

In this case, in Figure 168, at timing "X223", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50, and then at timing "X225", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50, and again at timing "X227", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50. In other words, in Figure 167, from "X223" to "X227", each lending notification sent at intervals of "300" ms includes data on the number of lending gaming media "50".

168, at timing "X223", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 changes from "0" to "50".
168, at the timing of "X225", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "100" from "50".
168, at timing "X227", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "150" from "100".

Also, in Figure 168, at the timing of "X223", the medal count control CPU 520 starts adding (updating) the display of the medal count display unit 121, and at the timing of "X229", ends adding (updating) the display of the medal count display unit 121.
At this time, the medal count control CPU 520 takes 300 ms to display the display in the medal count display unit 121 from 0 to 50, incrementing by 1 from "X223" to "X225". Next, it takes 300 ms to display the display in the medal count display unit 121 from 50 to 100, incrementing by 1 from "X225" to "X227". After that, it takes 300 ms to display the display in the medal count display unit 121 from 100 to 150, incrementing by 1 from "X227" to "X229".
As a result, the total medal count displayed in the medal count display section 121 changes from "0" to "150" over "900" ms, from "X223" to "X229".

Also, in Figure 168, at timing "X223", the sub-control CPU 85 starts outputting the "first" rental sound from the speaker 22. As mentioned above, the length from the beginning to the end of the rental sound is "450" ms, which is longer than the transmission interval of the rental notification ("300" ms). Therefore, at timing "X225" in Figure 168, the next rental process will be executed before the "first" rental sound has been output to its end. Also, at timing "X225" in Figure 168, the next rental process will be executed before the "first" rental sound has been output to its end, but the sub-control CPU 85 outputs the "first" rental sound to its end (timing "X226" in Figure 168).

Thereafter, at timing "X227" in Fig. 168, the lending process is executed based on the "third" operation of the lending switch 202. Then, at timing "X227" in Fig. 168, the sub-control CPU 85 outputs the "second" lending sound from the beginning.
The second lending sound is also output until the end (timing "X230" in FIG. 168).

In this way, in the example shown in Figure 168, the rental process is executed at the rental notification sending interval, so that if the next rental process is executed before one rental sound has been output to its end, the sub-control CPU 85 will output one rental sound to its end and then output the next rental sound from its beginning based on the execution of the subsequent rental process.
This allows the player to hear the entire lending sound from start to finish once it is output, so that if the lending sound contains words, for example, the player can hear the words from start to finish, preventing the words from being cut off midway and becoming incomprehensible.

Next, the relationship between the on/off state of the settlement switch 46 and the validity/invalidity of operation acceptance of the 3-bet switch 40b, the start switch 41, the counting switch 47, and the lending switch 202 will be described.
When the settlement switch 46 is in the on state, the operation acceptance of the 3-bet switch 40b and the start switch 41 is invalid, but the operation acceptance of the counting switch 47 and the lending switch 202 is valid.

Here, the on/off status of the 1 bet switch 40a, 3 bet switch 40b, start switch 41, the three (left/center/right) stop switches 42, and the settlement switch 46 is determined by the main control interrupt processing (Figure 115) by the main control CPU 510.
115, the main control CPU 510 performs input port reading processing. Then, it determines whether the 1 bet switch 40a, 3 bet switch 40b, start switch 41, the "three" (left/center/right) stop switches 42, and the settlement switch 46 have been operated (turned on), and generates data based on the input ports (level data, rising edge data, falling edge data) and stores this in the main control RWM 512.

For example, when the 3-bet switch 40b is operated (turned on), the rising data of the 3-bet switch 40b becomes "1", and the determination in step S994 of FIG. 113 is "Yes".
Also, when the settlement switch 46 is operated (turned on), the rising data of the settlement switch 46 becomes "1", and the determination in step S971 of FIG. 111 is "Yes".

Furthermore, when the start switch 41 is operated (turned on), the rising data of the start switch 41 becomes "1", and the determination in step S938 of FIG. 108 is "Yes".
Furthermore, when the stop switch 42 is operated (turned on), the rising data of the stop switch 42 becomes "1", and the determination in step S941 of FIG. 108 is "Yes".

In the input port read process in step S1045 of Fig. 115, when any switch is in the ON state, even if another switch is in the ON state, the process corresponding to the other switch being in the ON state is not executed. In other words, the operation acceptance of that other switch is invalidated.
Specifically, when the settlement process can be executed by operating the settlement switch 46 and the settlement switch 46 is in the on state, the main control CPU 510 does not execute the process corresponding to the 3 bet switch 40b being turned on, even if the 3 bet switch 40b is turned on.
That is, when the number of medals bet is between "1" and "3", and operation acceptance of the settlement switch 46 is valid, the settlement process can be executed by operating the settlement switch 46. In this state, when the settlement switch 46 is on, operation acceptance of the 3-bet switch 40b is invalidated.

In addition, when the settlement process can be executed by operating the settlement switch 46 and the settlement switch 46 is in the on state, the main control CPU 510 does not execute the process corresponding to the start switch 41 being turned on, even if the start switch 41 is turned on.
That is, when the settlement process can be executed by operating the settlement switch 46 and the settlement switch 46 is in the on state, acceptance of operation of the start switch 41 is invalidated.
In this way, when the settlement process can be executed by operating the settlement switch 46 and the settlement switch 46 is in the on state, acceptance of operations of the 1 bet switch 40a, the 3 bet switch 40b, and the start switch 41 is invalidated. This makes it possible to prevent the game from progressing, and to make the player aware that the state is not normal.

When the number of medals bet is "0", there are no medals to settle in the first place, so settlement processing by operating the settlement switch 46 cannot be executed, and therefore acceptance of operation of the settlement switch 46 may be enabled or disabled.
When the settlement process cannot be executed by operating the settlement switch 46 and the settlement switch 46 is in the on state, the acceptance of the operation of the 1 bet switch 40a and the 3 bet switch 40b may be enabled or disabled.
Also, when the settlement switch 46 is in an on state with its operation acceptance disabled, the operation acceptance of the 1 bet switch 40a and the 3 bet switch 40b may be enabled or disabled.

Furthermore, while at least one reel 31 is spinning, the settlement process cannot be performed by operating the settlement switch 46, and therefore, acceptance of the operation of the settlement switch 46 is disabled.
When at least one reel 31 is spinning, settlement processing cannot be performed by operating the settlement switch 46, and the settlement switch 46 is on, the main control CPU 510 may enable or disable acceptance of operation of the stop switch 42.

For example, when all reels 31 are spinning, the settlement process cannot be performed by operating the settlement switch 46, the settlement switch 46 is on, and the left stop switch 42 is turned on, the main control CPU 510 may enable operation acceptance of the left stop switch 42 to stop the rotation of the left reel 31, or may disable operation acceptance of the left stop switch 42 to not stop the rotation of the left reel 31.
In addition, when all reels 31 are spinning, the settlement process cannot be performed by operating the settlement switch 46, and the settlement switch 46 is in the on state, and the middle stop switch 42 or the right stop switch 42 is turned on, the same occurs as when the left stop switch 42 is turned on.

When a plurality of switches are turned on at the same time, a priority order is determined in advance, and among the plurality of switches turned on, the switch with the highest priority order is made to accept operation valid, and the other switches are made to accept operation invalid.
In this embodiment, of the 1 bet switch 40a, the 3 bet switch 40b, the start switch 41, the three (left/center/right) stop switches 42, and the settlement switch 46, the switch with the highest priority is the settlement switch 46.

When the settlement switch 46 and the start switch 41 are simultaneously turned on, the main control CPU 510 enables operation acceptance of the settlement switch 46 and disables operation acceptance of the start switch 41.
In addition, "the settlement switch 46 and the start switch 41 are turned on at the same time" means that when the input port reading process is performed in one main control interrupt process, both the settlement switch 46 and the start switch 41 are in the off state, and when the input port reading process is performed in the next main control interrupt process, both the settlement switch 46 and the start switch 41 are in the on state.

In addition, when the settlement switch 46 and the 3-bet switch 40b are simultaneously turned on, the main control CPU 510 enables operation acceptance of the settlement switch 46 and disables operation acceptance of the 3-bet switch 40b.
Furthermore, the three (left/center/right) stop switches 42 are, in descending order of priority, the left stop switch 42, the center stop switch 42, and the right stop switch 42. When the left stop switch 42 and the center stop switch 42 are simultaneously turned on, the main control CPU 510 enables operation acceptance of the left stop switch 42 and disables operation acceptance of the center stop switch 42.
The switch with the highest priority is not limited to the settlement switch 46, but can be set as appropriate.

As described above, the on/off status of the 1 bet switch 40a, 3 bet switch 40b, start switch 41, the three (left/center/right) stop switches 42, and settlement switch 46 is determined by main control interrupt processing (Figure 115) by the main control CPU 510, but the on/off status of the counting switch 47 is determined by medal count control interrupt processing (Figure 132) by the medal count control CPU 520.
Specifically, in step S1211 of Fig. 132, the medal count control CPU 520 performs input port check processing. This processing checks the signal of the count switch 47, the VL signal indicating that the main control CPU 510 has started up, the signal of the total medal count clear switch 112, etc.

133 is a flowchart showing the processing related to the counting switch 47 during the input port check processing in step S1211 of FIG.
In this way, the processing related to the counting switch 47 is performed by the medal number control CPU 520, not the main control CPU 510.

Therefore, even if at least one of the 1 bet switch 40a, 3 bet switch 40b, start switch 41, three (left/center/right) stop switches 42, and settlement switch 46 is in the on state, the medal number control CPU 520 enables operation acceptance of the counting switch 47.
In this way, even if the settlement switch 46 etc. is in the on state, by enabling the operation acceptance of the counting switch 47, it is possible to execute the medal counting process and return the medals from the gaming machine 10 to the lending unit 200.

Furthermore, the on/off state of the rental switch 202 is determined by a CPU provided in the rental unit 200 .
Therefore, even if at least one of the 1 bet switch 40a, 3 bet switch 40b, start switch 41, three (left/center/right) stop switches 42, and settlement switch 46 is on, the CPU provided in the lending unit 200 validates the acceptance of operation of the lending switch 202.

Furthermore, when at least one of the 1 bet switch 40a, 3 bet switch 40b, start switch 41, the three (left/center/right) stop switches 42, and settlement switch 46 is in the on state, and a loan notification including data on the number of loaned gaming media of 50 is received, the medal count control CPU 520 executes a loan process that adds the number of loaned gaming media of 50 to the total number of medals stored in the medal count control RWM 522.
In this way, even if the settlement switch 46 etc. is in the on state, by enabling the operation acceptance of the lending switch 202, the medal lending process can be executed, and medals can be loaned from the lending unit 200 to the gaming machine 10.

FIG. 169 is a time chart showing the relationship between the on/off of the settlement switch 46 and the validity/invalidity of operation acceptance of the 3-bet switch 40b, the start switch 41, the counting switch 47, and the lending switch 202.
Hereinafter, the relationship between the on/off state of the settlement switch 46 and the validity/invalidity of operation acceptance of the 3-bet switch 40b, the start switch 41, the counting switch 47, and the lending switch 202 will be described with reference to FIG.

In Figure 169, at the timing of "X241", the total number of medals stored in the medal count control RWM 522 is "50", and the number of bets stored in the main control RWM 512 is "0". Furthermore, the operation acceptance of the 3 bet switch 40b is in an enabled state, and the 3 bet switch 40b is in an off state. Furthermore, the operation acceptance of the start switch 41 is in an enabled state, and the settlement switch 46 is in an off state. Furthermore, the operation acceptance of the lending switch 202 is in an enabled state, and the lending switch 202 is in an off state. Furthermore, the operation acceptance of the counting switch 47 is in an enabled state, and the counting switch 47 is in an off state.

Then, at the timing of "X242" in Figure 169, when the operation acceptance of the 3 bet switch 40b is enabled and the 3 bet switch 40b is turned on, the main control CPU 510 sends a bet request command including data for the bet request number (number of bets) "3" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "3".
169, when a bet request command including data on the requested bet number (number of bets) "3" is received at timing "X242", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "3" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "47" from "50".
In addition, in FIG. 169, the 3-bet switch 40b is in the on state from "X242" to "X243", and during that time, the operation acceptance of the start switch 41 is in the invalid state.

Then, when the settlement switch 46 is turned on at the timing of "X244" in Figure 169, the main control CPU 510 sends a settlement request command including data for the settlement request number (number of bets) of "3" to the medal number control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "0".
169, when a settlement request command including data for the settlement request number (number of bets) "3" is received at timing "X244", the medal count control CPU 520 executes settlement processing to add the settlement request number (number of bets) "3" to the total medal count stored in the medal count control RWM 522 (step S1062 of the medal count main processing in FIG. 130, step S1078 in FIG. 117, and settlement request command reception processing in FIG. 119). As a result, the total medal count stored in the medal count control RWM 522 changes from "47" to "50".

Also, in FIG. 169, the settlement switch 46 is in the on state from "X244" to "X245", and during that time, the operation acceptance of the 3-bet switch 40b and the start switch 41 is in the invalid state.
Thereafter, in FIG. 169, from "X245" to "X247", the settlement switch 46 is in the OFF state, and during that time, the operation acceptance of the 3-bet switch 40b and the start switch 41 is in the valid state.
Also, in FIG. 169, from "X247" onwards, the settlement switch 46 is in the on state, and the operation acceptance of the 3-bet switch 40b and the start switch 41 is in the invalid state.

Also, in FIG. 169, from "X247" onwards, the settlement switch 46 is in the on state, but the operation acceptance of the counting switch 47 is in the valid state.
169, at timing "X250", counting switch 47 is turned on, thereafter counting switch 47 is maintained in the on state until timing "X253", at which time counting switch 47 is turned off. Also, the time from when counting switch 47 is turned on at timing "X250" until when counting switch 47 is turned off at timing "X253" is "550" ms, which is more than "500" ms. In other words, counting switch 47 is pressed and held.

Also, in Figure 169, at timing "X253", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.
169, at timing "X253", the medal count control CPU 520 executes counting processing to subtract the number of counted game media, "50", from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "0" from "50".

Also, in FIG. 169, from "X247" onwards, the settlement switch 46 is in the on state, but the operation acceptance of the lending switch 202 is in the valid state.
Then, in Figure 169, at timing "X255", the lending switch 202 is turned on, and then at timing "X256", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
169, at the timing of "X256", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 changes from "0" to "50".

As described above, when the settlement switch 46 is in the on state, the operation of the lending switch 202 is valid. Therefore, when the settlement switch 46 and the lending switch 202 are turned on at the same time, the operation will be as follows.
When the settlement switch 46 is turned on, the main control CPU 510 sends a settlement request command to the medal count control CPU 520, including data on the settlement request number (number of bets) of "3", and executes processing to set the number of bets stored in the main control RWM 512 to "0". The medal count control CPU 520 then executes settlement processing to add the settlement request number (number of bets) "3" to the total number of medals stored in the medal count control RWM 522 (step S1062 of the medal count main processing in Figure 130, step S1078 in Figure 117, and settlement request command receiving processing in Figure 119).

In addition, when the lending switch 202 is turned on, the lending unit 200 sends a lending notification to the main control board 50 including data on the number of lending game media "50", and the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total number of medals stored in the medal count control RWM 522 (step S805 of the medal count interrupt processing in Figure 132, lending control in Figure 69).
Furthermore, the settlement request command reception process in Figure 119 is executed in the medal count control main process (Figure 130), and the lending control in Figure 69 is executed in the medal count control interrupt process (Figure 132).

Then, as shown in FIG. 130, in step S1061 of the medal count control main processing, medal count control interrupt processing is prohibited, and in step S1064 of the medal count control main processing, medal count control interrupt processing is permitted.
Therefore, when the settlement switch 46 and the lending switch 202 are simultaneously turned on, if the medal count control interruption process is prohibited, the settlement process is executed first, and the lending process is executed after the medal count control interruption process is permitted.
Furthermore, when the settlement switch 46 and the lending switch 202 are turned on simultaneously, if the medal count control interruption process is not prohibited, the lending process is executed first, and the settlement process is executed after the medal count control interruption process is prohibited.

As described above, when the settlement switch 46 is in the on state, the operation of the counting switch 47 is valid. Therefore, when the settlement switch 46 is turned on and the counting switch 47 is pressed briefly, the operation will be as follows.
When the counting switch 47 is pressed briefly, the medal count control CPU 520 executes a counting process to subtract the number of counted game media "1" from the total number of medals stored in the medal count control RWM 522 (step S1212 of the medal count interrupt process in Figure 132, counting control process in Figure 134).

Also, as described above, the settlement request command reception processing in Figure 119 is executed in the medal count control main processing (Figure 130), and the counting control processing in Figure 134 is executed in the medal count control interrupt processing (Figure 132).
Then, as shown in FIG. 130, in step S1061 of the medal count control main processing, medal count control interrupt processing is prohibited, and in step S1064 of the medal count control main processing, medal count control interrupt processing is permitted.

Therefore, if the medal count control interrupt process is prohibited when the settlement switch 46 is turned on and the counting switch 47 is pressed briefly, the settlement process is executed first, and the counting process is executed after the medal count control interrupt process is permitted.
Furthermore, when the settlement switch 46 is turned on and the counting switch 47 is pressed briefly, if the medal count control interrupt process is not prohibited, the counting process is executed first, and the settlement process is executed after the medal count control interrupt process is prohibited.

Next, the screen display mode of the image display device 23 when the count switch 47 is operated, the screen display mode of the image display device 23 when the lending switch 202 is operated, and the screen display mode of the image display device 23 when the 3-bet switch 40b is operated will be described.
When the sub-control CPU 85 determines that the conditions for transitioning to the game standby state have been met, it displays a demo screen (standby screen) corresponding to the game standby state on the image display device 23.

Also, when a demo screen is displayed on the image display device 23 and the 3-bet switch 40b is operated (turned on), the main control CPU 510 sends a bet request command including data for the requested bet number (number of bets) "3" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "3", and the medal count control CPU 520 executes bet processing to subtract the number of bets "3" from the total number of medals stored in the medal count control RWM 522.
Furthermore, when a demo screen is displayed on the image display device 23, if the 1 bet switch 40a or the 3 bet switch 40b is operated (turned on), the sub-control CPU 85 ends the display of the demo screen on the image display device 23 and switches to displaying the game screen.

Furthermore, when a demo screen is displayed on the image display device 23 and the counting switch 47 is pressed and held (the time from when it is turned on to when it is turned off is 500 ms or more), the medal count control CPU 520 executes a counting process to subtract the number of counted game media, 50, from the total number of medals stored in the medal count control RWM 522.
Furthermore, when a demo screen is displayed on the image display device 23 and the counting switch 47 is pressed for a short time or for a long time, the sub-control CPU 85 maintains the display of the demo screen on the image display device 23 .

Here, when the sub-control CPU 85 determines that the conditions for transitioning to the game standby state have been met, it is configured to reduce power consumption and display a demo screen (standby screen) on the image display device 23 to inform the player that the game is in the standby state.
In this embodiment, the condition for transitioning to the game standby state is set to when the timer value measuring the time until transitioning to the game standby state (demo transition waiting time) becomes "0" or when the settlement switch 46 is operated.
The timer value of the demo transition waiting time is stored in a predetermined memory area in the sub-control RWM 83 on the sub-control board 80.
When all the reels 31 have stopped, the main control CPU 510 sends an all-reel stop command to the sub-control CPU 85 indicating that all the reels 31 have stopped.
In addition, when the sub-control CPU 85 receives the all reel stop command, it sets the initial value "60000" in the memory area for the timer value of the demo transition waiting time.

Thereafter, the sub-control CPU 85 subtracts "1" from the timer value of the demo transition waiting time each time it executes interrupt processing ("1" ms).
As a result, when approximately 60 seconds (60,000 x 1 ms = 60 seconds) have passed since the last reel 31 stopped (when the all reels stop command was received), the timer value for the demo transition waiting time becomes 0.
When the timer value of the demo transition waiting time reaches "0", the sub-control CPU 85 reduces power consumption and displays a demo screen on the image display device 23 to inform the player that the game is in a waiting state.

However, when the 1 bet switch 40a or 3 bet switch 40b is operated (turned on), a command indicating this is sent from the main control CPU 510 to the sub-control CPU 85. In this case, the sub-control CPU 85 stops decrementing the timer value for the demo transition waiting time, preventing transition to a game standby state. Therefore, when the 1 bet switch 40a or 3 bet switch 40b is operated (turned on), the sub-control CPU 85 does not display a demo screen on the image display device 23.

Furthermore, when a replay is won, medals are automatically bet, and a command indicating this is sent from the main control CPU 510 to the sub-control CPU 85. In this case, the sub-control CPU 85 also stops the subtraction of the timer value for the demo transition waiting time, preventing the transition to a game standby state. Therefore, even when a replay is won and medals are automatically bet, the sub-control CPU 85 does not display a demo screen on the image display device 23.

Furthermore, when the 1 bet switch 40a or 3 bet switch 40b is operated (turned on) while a demo screen is being displayed on the image display device 23, a command indicating this is sent from the main control CPU 510 to the sub-control CPU 85. In this case, the sub-control CPU 85 ends the display of the demo screen on the image display device 23 and switches to displaying the game screen.

As a result of the above, if 60 seconds have passed since the last reel 31 stopped without the 1 bet switch 40a or 3 bet switch 40b being operated and without an automatic bet of medals being made due to a replay winning, the timer value for the demo transition waiting time becomes 0, and the sub-control CPU 85 displays a demo screen on the image display device 23.
This reduces power consumption and also notifies players and parlor staff that the machine is in a standby state.

In addition, when the settlement switch 46 is operated, the main control CPU 510 sends a settlement command to the sub-control CPU 85 indicating that the settlement switch 46 has been operated.
Then, when the sub-control CPU 85 receives the settlement command, it displays a demo screen on the image display device 23 in the same manner as when the timer value of the demo transition waiting time reaches "0".
This reduces power consumption and also notifies players and parlor staff that the machine is in a standby state.

In addition, when the counting switch 47 is pressed briefly or for a long time, the main control CPU 510 sends a counting command to the sub-control CPU 85 indicating that the counting switch 47 has been pressed briefly or for a long time.
Then, when a demo screen is displayed on the image display device 23 and a counting command is received (when it is determined that the counting switch 47 has been pressed briefly or for a long time), the sub-control CPU 85 maintains the display of the demo screen on the image display device 23.
The counting switch 47 is normally operated when the player wants to stop playing, but when the player wants to stop playing and presses the counting switch 47 for a short time or a long time, the display of the demo screen on the image display device 23 can be maintained.

Figure 170 is a time chart showing the screen display mode of the image display device 23 when the counting switch 47 is operated, the screen display mode of the image display device 23 when the lending switch 202 is operated, and the screen display mode of the image display device 23 when the 3-bet switch 40b is operated.
Below, based on Figure 170, we will explain the screen display mode of the image display device 23 when the counting switch 47 is operated, the screen display mode of the image display device 23 when the lending switch 202 is operated, and the screen display mode of the image display device 23 when the 3 bet switch 40b is operated.

In Figure 170, at the timing of "X261", the total number of medals stored in the medal count control RWM 522 is "50", and the number of bets stored in the main control RWM 512 is "0". Furthermore, the sub-control CPU 85 determines that the conditions for transitioning to a game standby state have been met, and the image display device 23 displays a demo screen (standby screen) and does not display the game screen (is not displayed). Furthermore, the 3-bet switch 40b is in the OFF state, the lending switch 202 is also in the OFF state, and the counting switch 47 is also in the OFF state.

Then, in Figure 170, at timing "X262", the counting switch 47 is turned on, and then the counting switch 47 remains on until timing "X265", at which point the counting switch 47 is turned off. Furthermore, the time from when the counting switch 47 is turned on at timing "X262" until when the counting switch 47 is turned off at timing "X265" is 550 ms, which is more than 500 ms. In other words, the counting switch 47 is pressed and held.

Also, in Figure 170, at timing "X265", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.
170, at timing "X265", the medal count control CPU 520 executes counting processing to subtract the number of counted game media "50" from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "0" from "50".

Furthermore, in Figure 170, although the counting switch 47 is turned on from "X262" to "X265", the sub-control CPU 85 maintains the display of the demo screen on the image display device 23 and does not switch to displaying the game screen.
Then, in Figure 170, at timing "X269", the lending switch 202 is turned on, and then, at timing "X270", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.

170, at timing "X270", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 changes from "0" to "50".
Furthermore, in Figure 170, at the timing of "X270", the lending switch 202 is turned on, but the sub-control CPU 85 maintains the display of the demo screen on the image display device 23 and does not switch to displaying the game screen.

Then, when the 3 bet switch 40b is turned on at the timing of "X275" in Figure 170, the main control CPU 510 sends a bet request command including data on the bet request number (number of bets) "3" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "3".
170, when a bet request command including data on the requested bet number (number of bets) "3" is received at timing "X275", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "3" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "47" from "50".
Furthermore, when the 3-bet switch 40b is turned on at the timing of "X275" in Figure 170, the sub-control CPU 85 determines that the game is not in a waiting state, and ends the display of the demo screen on the image display device 23 and switches to displaying the game screen.

Next, based on Figure 171, the relationship between the counting notification image on the image display device 23 and the recommended press order image on the image display device 23 will be explained.
When the total number of medals stored in the medal count control RWM 522 is equal to or greater than "15,000," a count notification image prompting the player to operate the count switch 47 is displayed on the image display device 23.
In this embodiment, the image "Please press the counting switch" shown in Figure 171 (1) is displayed on the image display device 23 as the "counting notification image".

In addition, in this embodiment, there are recommended and non-recommended pressing orders for the stop switch 42, and when the stop switch 42 is operated in a non-recommended pressing order, a recommended pressing order notification image is displayed on the image display device 23 to prompt the player to operate the stop switch 42 in the recommended pressing order.
In this embodiment, the image "recommended push order notification image" is displayed on the image display device 23 as shown in Figure 171 (2) stating "left push recommended."
The size of the counting notification image is larger than the size of the recommended pressing order notification image.

Specifically, as shown in FIG. 171(1), the width of the counting notification image is set to "W1" and the height of the counting notification image is set to "H1".
Also, as shown in Figure 171 (2), the width of the recommended press order notification image is "W2" and the height of the recommended press order notification image is "H2".
In this embodiment, the relationships are set to "W1>W2" and "H1>H2."

Furthermore, in this embodiment, the counting notification image takes priority over the recommended push order notification image, and when both the recommended push order notification image and the counting notification image are displayed on the image display device 23, the counting notification image is displayed above (on the front layer of) the recommended push order notification image. Therefore, the recommended push order notification image is hidden by the counting notification image and cannot be seen.
By displaying the counting notification image with priority, it is possible to prompt the user to operate the counting switch 47 .
However, the counting notification image makes the recommended push order notification image invisible, but as the counting notification image repeatedly appears and disappears, when the counting notification image becomes invisible, the recommended push order notification image becomes visible.

In this embodiment, there are cases where multiple types of small winning combinations with different numbers of medals awarded are won at the same time, and the following methods can be used to control the stopping of the reel 31 in this case.
As a first priority, when all of the symbols (on the reel 31) that make up the winning symbol combination can be stopped on an active line, the reel 31 is stopped at that position.
Next, when all of the symbols constituting the winning symbol combination cannot be stopped on the effective line (when the first priority cannot be adopted), the reels 31 are controlled to stop according to either "number priority" or "number priority" as the second priority.

In addition, "number of medals priority" means that, among the symbol combinations of the multiple winning roles, the symbol on the reel 31 that constitutes the symbol combination with the greatest number of medals awarded is given priority to stopping (pulling in) on the valid line.
On the other hand, "number priority" means that the symbols on the reel 31 are stopped on the pay line with priority so as to maximize the number of symbol combinations that can be stopped and displayed on the pay line.
In a game where a player wins multiple kinds of small winning combinations with different numbers of medals given, the reel 31 is controlled to stop with priority given to the number of medals when the push order is correct, and the reel 31 is controlled to stop with priority given to the number of medals when the push order is incorrect.
As a result, in a game in which multiple types of small winning combinations with different numbers of medals awarded are won, the pattern combination (type of small winning combination) stopped and displayed on the valid line will differ depending on the order in which the stop switch 42 is pressed, resulting in an advantage/disadvantage in the game result (number of medals awarded).

In addition, in this embodiment, in a game in which multiple types of small winning combinations with different numbers of medals awarded are won, the expected number of medals awarded differs depending on the operation mode of the stop switch 42 (the order in which it is pressed and/or the timing of operation).
In this way, a role in which the expected value of the number of medals awarded differs depending on the operation mode of the stop switch 42 is called a "biased role."
In other words, a biased role is a role in which the winning role differs depending on the operation mode of the stop switch 42, and which has a unilaterally advantageous press order and other press orders (unilaterally disadvantageous press orders), and in a game in which a biased role is won, when the stop switch 42 is operated in a unilaterally advantageous press order, the expected value of the number of medals awarded in that one game (expected value without taking into account the expected value related to the AT) is higher than when the stop switch 42 is operated in a other press order.

A biased role is made up of multiple types of small roles, and winning a biased role corresponds to overlapping wins of these multiple types of small roles. When a biased role is won (when multiple types of small roles are overlapping wins), if the stop switch 42 is operated in a unilaterally advantageous pressing order, the small role with the largest payout number (hereinafter referred to as a "high-value role") may win due to the number-priority control. On the other hand, when a biased role is won, if the stop switch 42 is operated in a pressing order other than the unilaterally advantageous pressing order, the small role with the largest payout number will not win due to the number-priority control, and other small roles (hereinafter referred to as a "low-value role") may win.
When the number-priority control is executed, the higher number will generally be "PB=1" and a prize will be awarded.
In contrast, when quantity priority control is executed,
a) When Yasume wins with "PB=1",
b) There are cases where the cheap winning combination wins with "PB≠1" or where none of the small winning combinations win (missing out on winning combinations).

In addition, the order in which the stop switch 42 is pressed can be either normal pressing (stopping first on the left) or irregular pressing (stopping first on the middle or first on the right), but the "unilaterally advantageous pressing order" in this embodiment corresponds to irregular pressing.
Furthermore, for biased roles, the correct button press order is not evenly allocated to the six possible button press orders. In this embodiment, the correct button press order is not assigned to normal button presses, and the correct button press order is assigned to irregular button presses. When a biased role is won, operating the stop switch 42 with irregular button presses is configured to give one side an advantage. Therefore, when a biased role is won, irregular button presses become one-sidedly advantageous button press orders, and normal button presses become one-sidedly disadvantageous button press orders. Furthermore, "bias" indicates that the advantageous button press order is biased toward irregular button presses.

In addition, in this embodiment, when the expected probability of winning the AT (also referred to as "winning probability,""winningrate,""expected winning value," etc.) when the stop switch 42 is operated by pressing in the normal order is set to "P1," and the expected probability of winning the AT when the stop switch 42 is operated by pressing in an irregular order is set to "P2," the relationship is set to "P1 >P2."
Therefore, in order to increase the chances of winning the AT, it is advantageous for the player to always play by pressing the buttons in order.

In addition, in this embodiment, when a biased role is won, if the stop switch 42 is operated by pressing the buttons in an irregular sequence, the expected number of medals awarded in that game will be higher than when the stop switch 42 is operated by pressing the buttons in the normal sequence.
However, as described above, when the stop switch 42 is operated by pressing the buttons in order, the probability of winning the AT is higher than when the stop switch 42 is operated by pressing the buttons in an irregular order.
In this embodiment, the total (entire game) ball output performance, including balls output in the AT, is higher when pressing in order than when pressing in irregular order.

For this reason, in this embodiment, the order of pressing in order (stopping first on the left) is referred to as the "recommended order of pressing," and the order of pressing in an irregular manner (stopping first on the middle or first on the right) is referred to as the "non-recommended order of pressing."
"Recommended" means that if you play using that button press order, the expected number of medals awarded in total (for the entire game) will be higher than with other button press orders.
However, pressing the buttons in order is merely a "recommended" rule, not an "instruction." In other words, pressing buttons in an irregular order is "not recommended" and not "prohibited."

In this embodiment, when the stop switch 42 is operated in a non-recommended button press order, the sub-control CPU 85 displays a recommended button press order notification image on the image display device 23 to prompt the user to operate the stop switch 42 in the recommended button press order.
Here, the "recommended button press order notification image" is an image that informs the player that pressing buttons in order is the recommended button press order, in other words, that pressing buttons in order is an advantageous button press order for the player.
The display of the recommended button press order notification image is a display to inform the player of the recommended button press order, and is different from a warning display. When the stop switch 42 is operated by pressing the buttons in an irregular order, no penalty will be imposed on the player in the next game or thereafter, and no disadvantage will be inflicted on the player.
However, the probability of winning the AT differs between a game in which the stop switch 42 is operated by pressing the buttons in order and a game in which the stop switch 42 is operated by pressing the buttons in an irregular order.

Therefore, the purpose of displaying the recommended button press order notification image is to inform the player that operating the stop switch 42 in an irregular manner will reduce the expected number of medals awarded in total (for the entire game).
In addition, in this embodiment, the image "Left push recommended" shown in Figure 171 (2) is displayed on the image display device 23 as the "recommended push order notification image."
However, the "recommended button press order notification image" is not limited to the image "Left button press recommended" shown in Figure 171 (2), but may also be, for example, "Left button press is advantageous,""Pressing in order is recommended," or "Pressing in order is advantageous."

In a game in which the stop switch 42 is operated in the recommended pressing order (forward pressing), the sub-control CPU 85 does not display the recommended pressing order notification image on the image display device 23.
In contrast, in a game in which the stop switch 42 is operated in a non-recommended press order (irregular press order), the sub-control CPU 85 displays a recommended press order notification image on the image display device 23 at the time of the first center stop or the first right stop.

Next, the relationship between the 1 bet sound, the 3 bet sound, and the settlement sound will be described.
When a bet process is executed to subtract the bet number "1" from the total number of medals stored in the medal number control RWM 522 based on the operation of the 1 bet switch 40a (turning it on), the sub-control CPU 85 outputs a 1 bet sound from the speaker 22.
In addition, when a bet process is executed to subtract the bet number "3" from the total number of medals stored in the medal number control RWM 522 based on the operation of the 3 bet switch 40b, the sub-control CPU 85 outputs a 3 bet sound, which is different from the 1 bet sound, from the speaker 22.

Furthermore, when the settlement process is executed based on the operation of the settlement switch 46 to add the bet number "1" to the total number of medals stored in the medal count control RWM 522, and when the settlement process is executed based on the operation of the settlement switch 46 to add the bet number "3" to the total number of medals stored in the medal count control RWM 522, the sub-control CPU 85 outputs the same settlement sound from the speaker 22.

Here, the "1 bet sound" is a sound that indicates that the 1 bet switch 40a has been operated (turned on) to bet "1" medal, and that a bet process has been executed to subtract the bet number "1" from the total number of medals stored in the medal number control RWM 522.
In this embodiment, when the 1 bet switch 40a is operated and "1" medal is bet, the sub-control CPU 85 outputs a relatively short sound such as "beep" from the speaker 22 as the 1 bet sound.

In addition, the "3 bet sound" is a sound that indicates that the 3 bet switch 40b has been operated (turned on) to bet "3" medals, and that a bet process has been executed to subtract the bet number "3" from the total number of medals stored in the medal number control RWM 522.
In this embodiment, when the 3-bet switch 40b is operated to bet "3" medals, the sub-control CPU 85 outputs a relatively long sound such as "bub bub bub" from the speaker 22 as the 3-bet sound.

Furthermore, the "settlement sound" is a sound that indicates that the settlement switch 46 has been operated (turned on) to return the bet medals and that the settlement process has been executed to add the number of bet medals to the total number of medals stored in the medal count control RWM 522.
In this embodiment, when the settlement switch 46 is operated when "1" medal has been bet and a settlement process is executed to add the bet number "1" to the total number of medals stored in the medal count control RWM 522, and when the settlement switch 46 is operated when "3" medals have been bet and a settlement process is executed to add the bet number "3" to the total number of medals stored in the medal count control RWM 522, the sub-control CPU 85 outputs the same "prun"-like sound from the speaker 22 as the settlement sound.

Furthermore, by outputting the same settlement sound when settling whether a "1" bet or a "3" bet, it is possible to make it easier for the player to understand that the settlement has been made.
Note that the above-mentioned "beep" sound as the 1 bet sound, the "bubbubu" sound as the 3 bet sound, and the "prun" sound as the settlement sound are all examples, and the settings can be made as appropriate without being limited to these.

FIG. 172 is a time chart showing the relationship between the 1 bet sound, the 3 bet sound, and the settlement sound.
The relationship between the 1 bet sound, the 3 bet sound, and the settlement sound will be described below with reference to FIG.
172, at the timing of "X281", the total number of medals stored in the medal count control RWM 522 is "50", and the number of bets stored in the main control RWM 512 is "0". In addition, the 1 bet switch 40a is in the OFF state, the 3 bet switch 40b is also in the OFF state, and the settlement switch 46 is also in the OFF state.

Then, when the 1 bet switch 40a is turned on at the timing of "X282" in Figure 172, the main control CPU 510 sends a bet request command including data for the bet request number (number of bets) "1" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "1".
172, when a bet request command including data of the requested bet number (number of bets) "1" is received at timing "X282", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "1" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "49" from "50".
Furthermore, when the 1 bet switch 40a is turned on at the timing of "X282" in Figure 172, the sub-control CPU 85 outputs a 1 bet sound (a sound like "beep") from the speaker 22.

Then, when the settlement switch 46 is turned on at the timing of "X285" in Figure 172, the main control CPU 510 sends a settlement request command including data of the settlement request number (number of bets) "1" to the medal number control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "0".
172, when a settlement request command including data for the settlement request number (number of bets) "1" is received at timing "X285", the medal count control CPU 520 executes settlement processing to add the settlement request number (number of bets) "1" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "50" from "49".
Furthermore, when the settlement switch 46 is turned on at the timing of "X285" in Figure 172, the sub-control CPU 85 outputs a settlement sound (a sound like "prun") from the speaker 22.

Then, when the 3 bet switch 40b is turned on at the timing of "X288" in Figure 172, the main control CPU 510 sends a bet request command including data for the bet request number (number of bets) "3" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "3".
172, when a bet request command including data on the requested bet number (number of bets) "3" is received at timing "X288", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "3" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "47" from "50".
Furthermore, when the 3-bet switch 40b is turned on at the timing of "X288" in Figure 172, the sub-control CPU 85 outputs a 3-bet sound (a sound like "bub bub bub") from the speaker 22.

Then, when the settlement switch 46 is turned on at the timing of "X291" in Figure 172, the main control CPU 510 sends a settlement request command including data for the settlement request number (number of bets) "3" to the medal number control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "0".
172, when a settlement request command including data for the settlement request number (number of bets) "3" is received at timing "X291", the medal count control CPU 520 executes settlement processing to add the settlement request number (number of bets) "3" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "50" from "47".
Furthermore, in Figure 172, when the settlement switch 46 is turned on at the timing of "X291", the sub-control CPU 85 outputs the same settlement sound (a sound like "prun") as at the timing of "X285" from the speaker 22.

Next, the display modes of the counting notification image and the menu screen when the 3-bet switch 40b is operated will be described.
FIG. 173 shows a menu screen and a counting notification image.
After the game end check process (step S1247 in FIG. 140) of the main control main process (FIG. 140), if the push button 86 is operated (turned on) before medals for the next game are bet (step S936 in FIG. 140), the sub-control CPU 85 displays the menu screen shown in FIG. 173 (1) on the image display device 23.

In addition, when the total number of medals stored in the medal count control RWM 522 is "15,000" or more, the sub-control CPU 85 displays the count notification image shown in Figure 173 (2) on the image display device 23.
Furthermore, in a situation where the total number of medals stored in the medal count control RWM 522 is "15,000" or more, if the push button 86 is operated after the game end check process of the main control main process and before medals for the next game are bet, the sub-control CPU 85 will display both the menu screen and the counting notification image on the image display device 23, as shown in Fig. 173 (3). In other words, if the push button 86 is operated while the counting notification image is being displayed (during counting notification), the menu screen will be displayed and the display of the counting notification image (counting notification) will continue.

At this time, the counting notification image takes priority over the menu screen, and when both the menu screen and the counting notification image are displayed on the image display device 23, the counting notification image is displayed above the menu screen (on the front layer). As a result, part of the menu screen is hidden by the counting notification image and cannot be seen.
By displaying the counting notification image with priority, it is possible to prompt the user to operate the counting switch 47 .
However, by repeatedly displaying and hiding the counting notification image, when the counting notification image is no longer displayed, the menu screen becomes visible.

Also, when the menu screen is displayed on the image display device 23, if the 1 bet switch 40a is operated (turned on), the sub-control CPU 85 ends the display of the menu screen on the image display device 23.
Similarly, when the menu screen is displayed on the image display device 23, if the 3-bet switch 40b is operated (turned on), the sub-control CPU 85 ends the display of the menu screen on the image display device 23.

In addition, when a counting notification image is displayed on the image display device 23, if the 1 bet switch 40a is operated (turned on) to execute a bet process that subtracts the bet number "1" from the total number of medals stored in the medal count control RWM 522, and the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 will end the display of the counting notification image on the image display device 23.

Similarly, when a counting notification image is displayed on the image display device 23, if the 3 bet switch 40b is operated (turned on) to execute a bet process that subtracts the bet number "3" from the total number of medals stored in the medal count control RWM 522, and the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 will end the display of the counting notification image on the image display device 23.

When both the menu screen and counting notification image are displayed on the image display device 23, if the 1 bet switch 40a is operated (turned on) to execute a bet process that subtracts the bet number "1" from the total number of medals stored in the medal count control RWM 522, and the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 will end the display of the menu screen on the image display device 23 and then end the display of the counting notification image.

Similarly, when both the menu screen and the counting notification image are displayed on the image display device 23, the 3 bet switch 40b is operated (turned on) to execute a bet process that subtracts the bet number "3" from the total number of medals stored in the medal count control RWM 522, and when the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 ends the display of the menu screen on the image display device 23 and then ends the display of the counting notification image.
In this way, by ending the display of the counting notification image after ending the display of the menu screen, the counting notification image can be viewed by the player for as long as possible.

Here, the menu screen shown in FIG. 173(1) will be described.
The menu screen shown in Figure 173(1) displays four options from top to bottom: Model Information, Game History, Volume Change, and Exit. In Figure 173(1), the Volume Change option is surrounded by a thick line, which represents the cursor.
When the sub-control CPU 85 detects operation (ON) of the up switch 87a of the cross key 87 while the menu screen is displayed on the image display device 23, it moves the cursor up. For example, when the sub-control CPU 85 detects operation (ON) of the up switch 87a of the cross key 87 while the cursor is located at the volume change item, it moves the cursor to the game history item.

Furthermore, when the sub-control CPU 85 detects operation (ON) of the down switch 87b of the cross key 87 while the menu screen is displayed on the image display device 23, it moves the cursor downward. For example, when the sub-control CPU 85 detects operation (ON) of the down switch 87b of the cross key 87 while the cursor is positioned at the volume change item, it moves the cursor to the end item.
In this way, when the menu screen is displayed on the image display device 23, the cursor can be moved up or down by operating the up switch 87a or the down switch 87b of the cross key 87, thereby making it possible to select an item displayed on the menu screen. The item on which the cursor is positioned becomes the selected item.

When an item of model information is selected and operation (ON) of the push button 86 is detected, the sub-control CPU 85 displays the model information (not shown) on the image display device 23. In other words, when the push button 86 is operated while an item of model information displayed on the menu screen is selected, the item of model information is confirmed and the model information is displayed on the image display device 23.
Furthermore, when a game history item is selected and the operation (ON) of the push button 86 is detected, the sub-control CPU 85 displays the game history (not shown) on the image display device 23. In other words, when the push button 86 is operated with the game history item displayed on the menu screen selected, the game history item is determined and the game history is displayed on the image display device 23.

Furthermore, when the volume change item is selected and the operation (ON) of the push button 86 is detected, the sub-control CPU 85 displays a volume change image (Fig. 175 (1)) on the image display device 23. In other words, when the push button 86 is operated while the volume change item displayed on the menu screen is selected, the volume change item is confirmed and the volume change image is displayed on the image display device 23.
Furthermore, when the end item is selected and operation (ON) of the push button 86 is detected, the sub-control CPU 85 ends the display of the menu screen on the image display device 23, and displays the screen before the display of the menu screen (for example, a demo screen) on the image display device 23. In other words, when the push button 86 is operated while the end item displayed on the menu screen is selected, the end of the display of the menu screen is determined, and the screen returns to the screen before the menu screen was displayed.

175(1) shows five volume change icons, from left to right: "1" indicating volume 1, "2" indicating volume 2, "3" indicating volume 3, "4" indicating volume 4, and "5" indicating volume 5. In FIG. 175(1), the "3" indicating volume 3 is surrounded by a thick line, which indicates the cursor.
When the operation (ON) of the right direction switch 87c of the cross key 87 is detected while the volume change image is displayed on the image display device 23, the sub-control CPU 85 moves the cursor to the right. For example, when the operation (ON) of the right direction switch 87c of the cross key 87 is detected while the cursor is at the "3" position indicating volume 3, the sub-control CPU 85 moves the cursor to the "4" position indicating volume 4.

Furthermore, when the operation (ON) of the left direction switch 87d of the cross key 87 is detected while the volume change image is displayed on the image display device 23, the sub-control CPU 85 moves the cursor to the left. For example, when the operation (ON) of the left direction switch 87d of the cross key 87 is detected while the cursor is at the "3" position indicating volume 3, the sub-control CPU 85 moves the cursor to the "2" position indicating volume 2.
In this way, when the volume change image is displayed on the image display device 23, the cursor can be moved left or right by operating the right direction switch 87c or the left direction switch 87d of the cross key 87, thereby selecting an item displayed on the volume change image. The item on which the cursor is positioned is the selected item.

When "3" indicating volume 3 is selected, if operation (ON) of the push button 86 is detected, the sub-control CPU 85 sets the volume to 3.
Also, when "5" indicating volume 5 is selected, if operation (ON) of the push button 86 is detected, the sub-control CPU 85 sets the volume to 5.
The same applies when "1" indicating volume 1, "2" indicating volume 2, or "4" indicating volume 4 is selected.

It should be noted that after the game end check process of the main control main process, when the push button 86 is operated (turned on) before medals are bet for the next game, a menu screen is displayed on the image display device 23, but this is not limited to this.
For example, after medals are bet, the push button 86 may be operated before the start switch 41 is operated, and a menu screen may be displayed on the image display device 23 .

Also, for example, after the game end check process of the main control main process, before medals for the next game are bet, or after medals are bet and before the start switch 41 is operated, a menu screen may be displayed on the image display device 23 when the cross key 87 is operated.
Furthermore, the selection items displayed on the menu screen are not limited to the four items of machine information, game history, volume change, and end, but can be set as appropriate.
Furthermore, the selection items displayed on the volume change image are not limited to the five options "1" indicating volume 1 to "5" indicating volume 5, and can be set as appropriate.

Furthermore, on the menu screen, multiple selection items are displayed one above the other, and by operating the up switch 87a or the down switch 87b of the cross key 87, the cursor can be moved up or down to select an item displayed on the menu screen, but this is not limited to this.
For example, a menu screen may be configured so that multiple selection items are displayed side by side, and an item displayed on the menu screen can be selected by operating the right direction switch 87c or the left direction switch 87d of the cross key 87 to move the cursor left or right.

In addition, in the volume change image, numbers (items) indicating multiple volumes are displayed side by side, and by operating the right direction switch 87c or the left direction switch 87d of the cross key 87, it is possible to move the cursor left and right and select a number (item) indicating the volume, but this is not limited to this.
For example, the volume change image may display a plurality of numbers (items) indicating volume levels one above the other, and the number (item) indicating volume level may be selected by operating the up switch 87 a or the down switch 87 b of the cross key 87 to move the cursor up or down.

FIG. 174 is a time chart showing the display mode of the counting notification image and the menu screen when the 3-bet switch 40b is operated.
Hereinafter, the display mode of the counting notification image and the menu screen when the 3-bet switch 40b is operated will be described with reference to FIG.
In FIG. 174, at the timing of "X301", the total number of medals stored in the medal count control RWM 522 is "15,000". Therefore, a counting notification image prompting the operation of the counting switch 47 is displayed on the image display device 23. Furthermore, although the counting notification image is displayed on the image display device 23, the menu screen is not displayed. Furthermore, the number of bets stored in the main control RWM 512 is "0". Furthermore, the 3-bet switch 40b, the cross key 87, the lending switch 202, and the counting switch 47 are all in the OFF state.

Then, in Figure 174, at timing "X302", the counting switch 47 is turned on, and thereafter the counting switch 47 remains on until timing "X305", at which time the counting switch 47 is turned off. Furthermore, the time from when the counting switch 47 is turned on at timing "X302" until when the counting switch 47 is turned off at timing "X305" is "550" ms, which is more than "500" ms. In other words, the counting switch 47 is pressed and held.

Also, in Figure 174, at timing "X305", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.
174, at timing "X305", the medal count control CPU 520 executes counting processing to subtract the number of counted game media, "50", from the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "14,950" from "15,000".
Furthermore, at timing "X305" in Figure 174, the sub-control CPU 85 makes the counting notification image invisible on the image display device 23.

After that, when the push button 86 is operated (turned on) at timing "X307" in Figure 174, the sub-control CPU 85 displays a menu screen on the image display device 23. At this time, the total number of medals stored in the medal count control RWM 522 is "14,950", which is less than "15,000", so the sub-control CPU 85 does not display a count notification image on the image display device 23.

Then, in Figure 174, at timing "X311", the lending switch 202 is turned on, and then at timing "X312", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
174, at the timing of "X312", the medal count control CPU 520 executes lending processing to add the number of lending game media, "50", to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "15,000" from "14,950".

Furthermore, at timing "X312" in Figure 174, the sub-control CPU 85 displays a counting notification image on the image display device 23. At this time, as shown in Figure 173 (3), both the menu screen and the counting notification image are displayed on the image display device 23. As described above, the counting notification image takes priority over the menu screen and is displayed on top of the menu screen, so part of the menu screen is hidden by the counting notification image and cannot be seen. However, by repeatedly displaying and hiding the counting notification image, the menu screen becomes visible when the counting notification image is no longer displayed.

Then, when the 3 bet switch 40b is turned on at the timing of "X314" in Figure 174, the main control CPU 510 sends a bet request command including data for the bet request number (number of bets) "3" to the medal count control CPU 520, and executes processing to set the number of bets stored in the main control RWM 512 to "3".
174, when a bet request command including data on the requested bet number (number of bets) "3" is received at timing "X314", the medal count control CPU 520 executes bet processing to subtract the requested bet number (number of bets) "3" from the total number of medals stored in the medal count control RWM 522. As a result, the total number of medals stored in the medal count control RWM 522 becomes "14997" from "15000".

Furthermore, at the timing of "X314" in Figure 174, while both the menu screen and the counting notification image are displayed on the image display device 23, the 3 bet switch 40b is turned on and a bet process is executed to subtract the bet number "3" from the total number of medals stored in the medal count control RWM 522.When the total number of medals stored in the medal count control RWM 522 becomes "14,997" (less than "15,000"), the sub-control CPU 85 ends (hides) the display of the menu screen on the image display device 23, and then, at the timing of "X315" in Figure 174, ends (hides) the display of the counting notification image.

In this way, by ending the display of the counting notification image after ending the display of the menu screen, the counting notification image can be viewed by the player for as long as possible.
It should be noted that instead of hiding the menu screen immediately when the 3-bet switch 40b is turned on, the display of the menu screen may be gradually dimmed when the 3-bet switch 40b is turned on, and the menu screen may be hidden after a predetermined time (for example, 3 seconds) has elapsed since the 3-bet switch 40b was turned on.

Similarly, when the 3-bet switch 40b is turned on, the display of the counting notification image may be gradually faded, and the counting notification image may be made invisible after a predetermined time (for example, 3 seconds) has elapsed since the display of the counting notification image began to fade.
In this case, the display of the menu screen starts to fade first, and then the display of the counting notification image starts to fade.Then, the menu screen goes out of view first, and then the counting notification image goes out of view.
Alternatively, the menu screen display may begin to fade first, and then the count notification image display may begin to fade, and then the menu screen and the count notification image may disappear simultaneously.

Next, the display modes of the volume change image and the count notification image while the demo screen is displayed will be described.
FIG. 175 shows a volume change image and a count notification image.
As described above, when the volume change item is selected on the menu screen and the push button 86 is operated (turned on), the sub-control CPU 85 displays the volume change image shown in Figure 175 (1) on the image display device 23.

The volume change image is displayed not only when the push button 86 is operated with the volume change item selected on the menu screen, but also on the demo screen.
That is, when the conditions for transitioning to the game standby state are met, the sub-control CPU 85 displays a demo screen on the image display device 23 and also displays a volume change image.
At this time, the volume change image takes priority over the demo screen, and when both the demo screen and the volume change image are displayed on the image display device 23, the volume change image is displayed above the demo screen (on the front layer). As a result, part of the demo screen is hidden by the volume change image and cannot be seen.

Furthermore, as described above, when the total number of medals stored in the medal count control RWM 522 is "15,000" or more, the sub-control CPU 85 displays the count notification image shown in Figure 175 (2) on the image display device 23.
Furthermore, when the total number of medals stored in the medal count control RWM522 is "15,000" or more and the conditions for transitioning to the game standby state are met, the sub-control CPU85 displays a demo screen on the image display device 23, as well as a volume change image and a count notification image.

Similarly, when the conditions for transitioning to the game standby state are met and the total number of medals stored in the medal count control RWM522 becomes "15,000" or more, the sub-control CPU85 displays a demo screen on the image display device 23, as well as a volume change image and a count notification image.
At this time, the volume change image takes priority over the demo screen, and further, the counting notification image takes priority over the volume change image. Therefore, when the demo screen, volume change image, and counting notification image are all displayed on the image display device 23, the volume change image is displayed above the demo screen (the front layer), and further, as shown in Figure 175 (3), the counting notification image is displayed above the volume change image (the front layer). Therefore, part of the demo screen is hidden by the volume change image and counting notification image, and part of the volume change image is hidden by the counting notification image.

By displaying the counting notification image with priority, it is possible to prompt the user to operate the counting switch 47 .
The counting notification image is displayed for "2" seconds, hidden for "1" second, displayed for "2" seconds, hidden for "1" second, and so on, and is displayed and hidden for a cycle of "3" seconds.
Furthermore, the volume change image is displayed for "2" seconds, hidden for "2" seconds, displayed for "2" seconds, hidden for "2" seconds, and so on, and is displayed and hidden for "2" seconds, and so on ...
In this way, the cycle in which the counting notification image is repeatedly displayed and hidden is "3" seconds, which is shorter than the cycle in which the volume change image is repeatedly displayed and hidden, which is "4" seconds.
Furthermore, the cycle of repeating the display and non-display of the counting notification image is shorter than the cycle of repeating the display and non-display of the volume change image, so that the counting notification image can be made more noticeable than the volume change image, and the counting notification image can be made more memorable to the player.

The cycle of repeating the display and non-display of the counting notification image is not limited to the above-mentioned embodiment, and may be a cycle of 2 seconds, such as display for 1 second, non-display for 1 second, display for 1 second, non-display for 1 second, or may be a cycle of 2 seconds, such as display for 1.5 seconds, non-display for 0.5 seconds, display for 1.5 seconds, non-display for 0.5 seconds. In this way, the cycle of repeating the display and non-display of the counting notification image can be set as appropriate.
Furthermore, the cycle of repeating the display and non-display of the volume change image is not limited to the above-mentioned embodiment, and may be a "4" second cycle, such as "display for 2.5" seconds, "non-display for 1.5" seconds, "display for 2.5" seconds, and "non-display for 1.5" seconds, or a "5" second cycle, such as "display for 2" seconds, "non-display for 3" seconds, "display for 2" seconds, and "non-display for 3" seconds. In this way, the cycle of repeating the display and non-display of the volume change image can be set as appropriate.

As described above, when the demo screen is displayed on the image display device 23, if the 1 bet switch 40a is operated (turned on), the sub-control CPU 85 ends the display of the demo screen on the image display device 23 and switches to the display of the game screen. At this time, the display of the volume change image also ends.
Similarly, when the demo screen is displayed on the image display device 23 and the 3-bet switch 40b is operated (turned on), the sub-control CPU 85 ends the display of the demo screen on the image display device 23 and switches to the display of the game screen. At this time, the display of the volume change image also ends.

In addition, when a counting notification image is displayed on the image display device 23, if the 1 bet switch 40a is operated (turned on) to execute a bet process that subtracts the bet number "1" from the total number of medals stored in the medal count control RWM 522, and the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 will end the display of the counting notification image on the image display device 23.

Similarly, when a counting notification image is displayed on the image display device 23, if the 3 bet switch 40b is operated (turned on) to execute a bet process that subtracts the bet number "3" from the total number of medals stored in the medal count control RWM 522, and the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 will end the display of the counting notification image on the image display device 23.

When both the demo screen and the counting notification image are displayed on the image display device 23, if the 1 bet switch 40a is operated (turned on) to execute a bet process that subtracts the bet number "1" from the total number of medals stored in the medal count control RWM 522, causing the total number of medals stored in the medal count control RWM 522 to become less than "15,000", the sub-control CPU 85 will end the display of the demo screen on the image display device 23, switch to the game screen display, and then end the display of the counting notification image.

Similarly, when both the demo screen and the counting notification image are displayed on the image display device 23, the 3 bet switch 40b is operated (turned on) to execute a bet process that subtracts the bet number "3" from the total number of medals stored in the medal count control RWM 522, and when the total number of medals stored in the medal count control RWM 522 becomes less than "15,000", the sub-control CPU 85 ends the display of the demo screen on the image display device 23 and switches to the display of the game screen, and then ends the display of the counting notification image.
In this way, by ending the display of the demo screen and switching to the display of the game screen, the display of the counting notification image is ended, so that the player can view the counting notification image for as long as possible.

FIG. 176 is a time chart showing the display mode of the volume change image and the count notification image while the demo screen is being displayed.
Below, based on Figure 176, we will explain the display mode of the volume change image and count notification image while the demo screen is being displayed.
In FIG. 176, at the timing of "X321", the total number of medals stored in the medal count control RWM 522 is "14,950". Therefore, the count notification image prompting the operation of the count switch 47 is not displayed on the image display device 23 (it is in a non-display state). Also, because the conditions for transitioning to the game standby state are not met, the demo screen is not displayed on the image display device 23 (it is in a non-display state), and the game screen is displayed. Furthermore, both the lending switch 202 and the count switch 47 are in an off state.

After that, when the conditions for transitioning to the game standby state are met at timing "X322" in Figure 176, the sub-control CPU 85 displays a demo screen corresponding to the game standby state on the image display device 23, and also displays a volume change image indicating that the volume can be changed on the image display device 23. Also, in the example shown in Figure 176, on the demo screen, the volume change image is displayed for "2" seconds, then hidden for "2" seconds, then displayed for "2" seconds, then hidden for "2" seconds, and so on, repeating display and hiding in a cycle of "4" seconds.

Then, in Figure 176, at timing "X323", the lending switch 202 is turned on, and then at timing "X324", a lending notification including data on the number of lending gaming media "50" is sent from the lending unit 200 to the main control board 50.
176, at timing "X324", the medal count control CPU 520 executes lending processing to add the number of lending game media "50" to the total medal count stored in the medal count control RWM 522. As a result, the total medal count stored in the medal count control RWM 522 becomes "15,000" from "14,950".

Furthermore, at timing "X324" in Figure 176, the sub-control CPU 85 displays on the image display device 23 a counting notification image that prompts the user to operate the counting switch 47. Also, in the example shown in Figure 176, on the demo screen, the counting notification image is displayed for "2" seconds, hidden for "1" second, and so on, repeatedly displayed and hidden in a cycle of "3" seconds.
Then, from "X324" onward in FIG. 176, the demo screen, the volume change image, and the counting notification image are displayed on the image display device 23. At this time, as described above, the volume change image takes priority over the demo screen, and the counting notification image takes priority over the volume change image. Therefore, when the demo screen, the volume change image, and the counting notification image are all displayed on the image display device 23, the volume change image is displayed on top of the demo screen, and the counting notification image is displayed on top of the volume change image. Therefore, part of the demo screen is hidden by the volume change image and the counting notification image, and part of the volume change image is hidden by the counting notification image.
By displaying the counting notification image with priority, it is possible to prompt the user to operate the counting switch 47 .

However, the counting notification image alternates between displaying and hiding at a cycle of 3 seconds, and the volume change image alternates between displaying and hiding at a cycle of 4 seconds. Therefore, when the counting notification image is hidden, the volume change image becomes visible, and when both the counting notification image and the volume change image are hidden, the demo screen becomes visible.
Furthermore, the cycle of repeating the display and non-display of the counting notification image is shorter than the cycle of repeating the display and non-display of the volume change image, so that the counting notification image can be made more noticeable than the volume change image, making the counting notification image more likely to leave an impression on the player.

Next, a description will be given of how the counting sound changes when a volume change operation is performed while the counting sound is being output.
When the counting switch 47 is pressed and held down to execute the counting process, the sub-control CPU 85 outputs a counting sound for a long press from the speaker 22 .
In addition, the sub-control CPU 85 is capable of accepting a volume change operation while the counting sound is being output.
Then, when a volume change operation is performed while the counting sound is being output, the sub-control CPU 85 makes the volume of the counting sound changeable.

FIG. 177 is a time chart showing the change in the counting sound when a volume change operation is performed while the counting sound is being output.
Hereinafter, based on FIG. 177, a description will be given of how the counting sound changes when a volume change operation is performed while the counting sound is being output.
In FIG. 177, at the timing of "X341", the total number of medals stored in the medal count control RWM 522 is "500", and the total number of medals displayed on the medal count display unit 121 is "500". Also, the count switch 47 is in the OFF state. Therefore, no counting display is being performed on the image display device 23, and no counting sound is being output from the speaker 22.

177, at the timing of "X342", the counting switch 47 is turned on, and thereafter the counting switch 47 is maintained in the on state for "500" ms or more. In other words, the counting switch 47 is pressed and held.
Also, in Figure 177, at each of the times "X347", "X350", "X353", and "X356", a counting notification including data on the number of counted gaming media "50" is sent from the main control board 50 to the rental unit 200.
Furthermore, in Figure 177, at each of the times "X347", "X350", "X353", and "X356", the medal count control CPU 520 executes a counting process to subtract the number of counted game media "50" from the total number of medals stored in the medal count control RWM 522.

As a result, at the timing of "X347" in Figure 177, the total number of medals stored in the medal number control RWM 522 changes from "500" to "450".
Also, in FIG. 177, at the timing of "X350", the total number of medals stored in the medal number control RWM 522 changes from "450" to "400".
Furthermore, in FIG. 177, at the timing of "X353", the total number of medals stored in the medal number control RWM 522 changes from "400" to "350".
Furthermore, in FIG. 177, at the timing of "X356", the total number of medals stored in the medal number control RWM 522 changes from "350" to "300".

Also, in FIG. 177, at the timing of "X347", the medal count control CPU 520 starts decrementing (updating) the display of the medal count display section 121.
Then, the medal count control CPU 520 takes 300 ms to display the medal count display unit 121 from "500" to "450" by subtracting "1" at a time from "X347" to "X350", and then takes 300 ms to display the medal count display unit 121 from "450" to "400" by subtracting "1" at a time from "X350" to "X353".

Furthermore, the medal count control CPU 520 takes 300 ms to display the medal count display unit 121 from "400" to "350" by subtracting "1" at a time from "X353" to "X356", and then takes 300 ms to display the medal count display unit 121 from "350" to "300" by subtracting "1" at a time from "X356" to "X359".
As a result, the total medal count displayed in the medal count display section 121 changes from "500" to "300" over "1200" ms, from "X347" to "X359".

Also, in Figure 177, at timing "X347", the sub-control CPU 85 starts displaying the counting in progress on the image display device 23, and thereafter continues to display the counting in progress until the counting process is completed. This allows the player to be notified that the counting switch 47 has been pressed and held down and the counting process has been executed.

Furthermore, at timing "X347" in Figure 177, the sub-control CPU 85 starts outputting the counting sound for long presses from the speaker 22, and thereafter continues to output the counting sound for long presses until the counting process is completed. This notifies the player that the counting switch 47 has been pressed and the counting process has been executed.

Also, in Figure 177, when the volume setting is changed from volume 5 to volume 4 by operating the cross key 87 and push button 86 at the timing of "X349", the sub-control CPU 85 changes the volume of the counting sound output from the speaker 22 when pressed and held from volume 5 to volume 4.
Furthermore, in Figure 177, when the volume setting is changed from volume 4 to volume 3 by operating the cross key 87 and push button 86 at the timing of "X350", the sub-control CPU 85 changes the volume of the counting sound output from the speaker 22 when pressed and held from volume 4 to volume 3.

Furthermore, in Figure 177, when the volume setting is changed from volume 3 to volume 2 by operating the cross key 87 and push button 86 at the timing of "X351", the sub-control CPU 85 changes the volume of the counting sound output from the speaker 22 when pressed and held from volume 3 to volume 2.
In this way, by operating the cross key 87 and the push button 86 while the counting sound for long presses is being output, the volume of the counting sound for long presses can be lowered (made quieter).
When the volume is lowered by operating the cross key 87 and the push button 86, not only the volume of the counting sound when pressed and held is lowered, but also the volume of, for example, game background music, etc.

Also, in Figure 177, when the volume setting is changed from volume 2 to volume 3 by operating the cross key 87 and push button 86 at the timing of "X353", the sub-control CPU 85 changes the volume of the counting sound output from the speaker 22 when pressed and held from volume 2 to volume 3.
Furthermore, in Figure 177, when the volume setting is changed from volume 3 to volume 4 by operating the cross key 87 and push button 86 at the timing of "X354", the sub-control CPU 85 changes the volume of the counting sound output from the speaker 22 when pressed and held from volume 3 to volume 4.

Furthermore, in Figure 177, when the volume setting is changed from volume 4 to volume 5 by operating the cross key 87 and push button 86 at the timing of "X355", the sub-control CPU 85 changes the volume of the counting sound output from the speaker 22 when pressed and held from volume 4 to volume 5.
In this way, by operating the cross key 87 and the push button 86 while the counting sound for a long press is being output, it is possible to not only lower (make quieter) the volume for a long press, but also to raise (louder) the volume for a long press.
It should be noted that when the volume is increased by operating the cross key 87 and the push button 86, not only the volume of the counting sound when pressed and held is increased, but also the volume of, for example, game background music, etc.

Although the tenth embodiment of the present invention has been described above, the present invention is not limited to the above-described content, and various modifications such as those described below are possible.
(1) In the tenth embodiment, the medal count control CPU 520 transmits information regarding the total medal count to the main control CPU 510, and the main control CPU 510 then transmits information regarding the total medal count to the sub-control CPU 85. In other words, the medal count control CPU 520 indirectly transmits information regarding the total medal count to the sub-control CPU 85 via the main control CPU 510. Then, when the sub-control CPU 85 determines that the total medal count is equal to or greater than the threshold, it outputs a count notification.
However, the present invention is not limited to this, and for example, the medal count control CPU 520 may transmit information regarding the total medal count directly to the sub-control CPU 85 without going through the main control CPU 510. Then, when the sub-control CPU 85 determines that the total medal count is equal to or greater than a threshold value, it may output a count notification.

(2) Whether or not the counting process has ended can be determined as follows.
The on/off state of the counting switch 47 is checked, and when it is determined that the counting switch 47 has changed from an on state to an off state, it can be determined that the counting process has ended.
In addition, the number of counted gaming media included in the counting notification is checked, and when it is determined that the number of counted gaming media has changed from "50" to "0", it can be determined that the counting process has ended.

Furthermore, when the counting switch 47 is pressed and held down and the counting switch 47 is turned off, the number of counted game media can be set to "0" at the first counting notification after the counting switch 47 is turned off.
Furthermore, when the counting switch 47 is pressed and held down and the counting switch 47 is turned off, the first counting notification after the counting switch 47 is turned off can set the number of counted gaming media to "50", and the next counting notification can set the number of counted gaming media to "0".

That is, when the counting switch 47 is kept on (pressed and held), a counting notification containing data indicating the number of counted game media of "50" is transmitted every "300" ms, but when the counting switch 47 is turned off, a counting notification containing data indicating the number of counted game media of "0" is transmitted thereafter. When the number of counted game media contained in the counting notification becomes "0" instead of "50", it can be determined that the counting process has ended.
Then, as soon as it is determined that the counting process has ended, the process corresponding to the end of the counting process may be executed, or the process corresponding to the end of the counting process may be executed after a predetermined time has elapsed since it was determined that the counting process has ended.

For example, the sub-control CPU 85 may end the counting display on the image display device 23 immediately upon determining that the counting process has been completed, or may end the counting display on the image display device 23 after a predetermined time has elapsed since determining that the counting process has been completed.
In other words, the sub-control CPU 85 may end the counting display on the image display device 23 as soon as it determines that the counting switch 47 has changed from an on state to an off state, or may end the counting display on the image display device 23 after a predetermined time has elapsed since it determined that the counting switch 47 has changed from an on state to an off state.
In addition, the sub-control CPU 85 may end the counting display on the image display device 23 immediately upon determining that the number of counted gaming media has changed from "50" to "0", or may end the counting display on the image display device 23 after a predetermined time has elapsed since determining that the number of counted gaming media has changed from "50" to "0".

(3) In the tenth embodiment, the number of lending game media is set to "50," but the number of lending game media is not limited to "50" and can be set appropriately to, for example, "30" or "100."
(4) In the tenth embodiment, the number of game media counted when the counting switch 47 is pressed and held is set to "50." However, the number of game media counted when the counting switch 47 is pressed and held is not limited to "50," and can be set appropriately to, for example, "30" or "100."
(5) In the tenth embodiment, the number of game media counted when the counting switch 47 is pressed briefly is set to “1.” However, the number of game media counted when the counting switch 47 is pressed briefly is not limited to “1” and can be set appropriately, for example, to “3” or “5.”

(6) In the tenth embodiment, the time for determining whether the counting switch 47 is pressed long or short is set to 500 ms. However, the time for determining whether the counting switch 47 is pressed long or short is not limited to 500 ms and can be set appropriately to, for example, 400 ms, 600 ms, etc.
(7) In the tenth embodiment, the threshold value for the total number of medals when a counting notification is issued to prompt the player to operate the counting switch 47 is set to “15,000.” However, the threshold value is not limited to “15,000” and can be set appropriately to, for example, “10,000” or “16,000.”

(8) In the tenth embodiment, the counting notification is output as both an image and sound, but this is not limited to this. For example, only the image of the counting notification may be output on the image display device 23, or only the sound of the counting notification may be output from the speaker 22.
Furthermore, the image constituting the count notification is an image including the text "Please press the count switch," but this is merely an example and can be set as appropriate.
Furthermore, the voice constituting the count notification is a voice including the words "Please press the count switch," but this is merely an example and can be set as appropriate.
Furthermore, the images and sounds that make up the counting notification are set to be 2 seconds long from start to finish, but 2 seconds is an example, and the length from start to finish can be set as appropriate, for example, to 1.5 seconds, 3 seconds, or the like.

(9) In the tenth embodiment, the length of the counting sound when the button is pressed and held is set to 300 ms. However, the length of the counting sound when the button is pressed and held is not limited to 300 ms, and may be any length equal to or longer than 300 ms. For example, the length may be set to 500 ms, 1 second, or the like.
(10) In the tenth embodiment, the length of the counting sound when a button is pressed is set to 200 ms. However, the length of the counting sound when a button is pressed is not limited to 200 ms and may be any length less than 300 ms. For example, the length may be set to 100 ms, 150 ms, or the like.
(11) In the tenth embodiment, the length of the rental sound is set to 450 ms, but the length of the rental sound is not limited to 450 ms and may be any length greater than 300 ms, and can be set appropriately to, for example, 500 ms or 1 second.

(12) In the tenth embodiment, the transmission interval of the counting notification and the lending notification is set to "300" ms, but the transmission interval of the counting notification and the lending notification is not limited to "300" ms and can be set as appropriate.
(13) In the tenth embodiment, the time from receiving the door close command to turning off the push button lamp 88 was set to 450 ms. However, the time from receiving the door close command to turning off the push button lamp 88 is not limited to 450 ms and can be set as appropriate, for example, to 500 ms or 1 second.
Additionally, the push button light 88 may be turned off immediately upon receiving a door close command.
(14) In the tenth embodiment, the 1 bet sound is a "beep" sound, the 3 bet sound is a "bubbubbu" sound, and the settlement sound is a "prun" sound, but these are all examples and can be set as appropriate without being limited to these.

(15) In the tenth embodiment, the counting notification image is displayed for two seconds, hidden for one second, and so on, but this is not limited to this.
The cycle of repeating display and non-display of the counting notification image may be a "2" second cycle, such as "1" second display, "1" second non-display, "1" second display, "1" second non-display, or may be a "2" second cycle, such as "1.5" second display, "0.5" second non-display, "1.5" second display, "0.5" second non-display. In this way, the cycle of repeating display and non-display of the counting notification image can be set appropriately.

(16) In the tenth embodiment, the volume change image is displayed for “2” seconds, hidden for “2” seconds, and then hidden for “2” seconds, and so on, but this is not limited to this.
The cycle of repeating display and non-display of the volume change image may be a "4" second cycle, for example, "display for 2.5" seconds, "non-display for 1.5" seconds ... or a "5" second cycle, for example, "display for 2" seconds, "non-display for 3" seconds, "display for 2" seconds, "non-display for 3" seconds. In this way, the cycle of repeating display and non-display of the volume change image can be set appropriately.

(17) In the tenth embodiment, when the counting switch 47 is pressed and held down to execute the counting process, the speaker 22 outputs the counting sound for the long press, and the volume of the game background music is lowered. After 300 ms has elapsed since the counting switch 47 was turned off, the volume of the game background music is returned to the volume before the counting process was executed. However, the volume of the game background music may be returned to the volume before the counting process was executed immediately after the counting switch 47 is turned off.
Also, when it is determined that the number of counted gaming media has changed from "50" to "0", the volume of the gaming background music may be returned to the volume before the counting process was executed.
Furthermore, while the counting sound for long presses is being output, the volume of the game background music may be set to "0" (the game background music may be muted), and when the counting process by long pressing of the counting switch 47 is completed, the game background music may be output again at the volume before the counting process was executed.

(18) The first to tenth embodiments and the various modifications shown in the first to tenth embodiments are not limited to being implemented alone, but can also be implemented in appropriate combinations.

<Additional Notes>
The inventions (original inventions) described in the original specification etc. of the present application can be exemplified by the following Original Invention 1 to Original Invention 22. However, this does not mean that the inventions described in this specification are limited to Original Invention 1 to Original Invention 22.
1. Original invention 1
In conventional gaming machines, when the total number of gaming media stored in the gaming media number storage means reaches or exceeds a threshold value ("15,000"), a notification is issued to prompt the player to operate a counting switch (for example, JP 2023-064762 A).
However, if the timing of starting the notification prompting the player to operate the counting switch is late, the player will not be informed early that the total number of game media stored in the game media number storage means has reached or exceeded the threshold value.
The problem that the original invention 1 aims to solve is to notify the player at an early stage that the total number of game media stored in the game media number storage means has reached a threshold value or more.

The initial invention 1 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
a game medium number display unit (a medal number display unit 121) that displays the total number of game media stored in the game medium number storage means,
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
The game medium number control means is capable of executing a lending process of adding the number of game media to be lent "N1"("50") to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202),
When the total number of game media stored in the game media number storage means is equal to or greater than "N2"("15,000"), a count notification is made to prompt the user to operate a count switch.
When a game medium lending operation is performed when the total number of game media stored in the game medium number storage means is less than "N2" and equal to or greater than "N2-N1" (when the lending switch 202 is operated at timing "X10" in FIG. 157), a counting notification is started before the display on the game medium number display unit becomes "N2" or greater (at timing "X12" in FIG. 157, the speaker 22 and the image display device 23 start outputting a counting notification, but the total medal count displayed on the medal number display unit 121 is still "14,950", which is less than "15,000").
It is characterized by:

According to the initial invention 1, a count notification is issued to prompt the player to operate the count switch before the display on the gaming medium count display unit reaches "N2" or more, thereby notifying the player early on that the total number of gaming media stored in the gaming medium count storage means has reached "N2" or more.

2. Original invention 2
In conventional gaming machines, when the total number of gaming media stored in the gaming media number storage means reaches or exceeds a threshold value ("15,000"), a notification is issued to prompt the player to operate a counting switch (for example, JP 2023-064762 A).
However, if the timing for ending the notification prompting the operation of the counting switch is late, the player cannot be notified early that the total number of game media stored in the game media number storage means has fallen below the threshold value.
The problem that the original invention 2 aims to solve is to notify the player at an early stage that the total number of game media stored in the game media number storage means has fallen below a threshold value.

The initial invention 2 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
a game medium number display unit (a medal number display unit 121) that displays the total number of game media stored in the game medium number storage means,
The game medium number control means is capable of executing a counting process of subtracting the counted game medium number "N1"("50") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time ("500" ms) (when the counting switch 47 is pressed and held down),
When the total number of game media stored in the game media number storage means is equal to or greater than "N2"("15,000"), a count notification is made to prompt the user to operate a count switch.
When the total number of game media stored in the game media number storage means is equal to or greater than "N2" and less than "N1 + N2," and the time from when the counting switch is turned on to when it is turned off is equal to or greater than a predetermined time and the counting process is executed (when the counting switch 47 is pressed and held from "X27" to "X32" in FIG. 158), the counting notification is terminated before the display in the game media number display unit becomes less than "N2" (at the timing of "X32" in FIG. 158, the output of the counting notification from the speaker 22 and the image display device 23 is terminated, but the total medal count displayed in the medal count display unit 121 is still "15,049," which is greater than "15,000").
It is characterized by:

According to the initial invention 2, the count notification prompting the player to operate the count switch is terminated before the display on the gaming medium number display unit falls below "N2," thereby notifying the player early on that the total number of gaming media stored in the gaming medium number storage means has fallen below "N2."

3. Original invention 3
In conventional gaming machines, when the total number of gaming media stored in the gaming media number storage means reaches or exceeds a threshold value ("15,000"), a notification is issued to prompt the player to operate a counting switch (for example, JP 2023-064762 A).
However, if the timing for ending the notification prompting the operation of the counting switch is late, the player cannot be notified early that the total number of game media stored in the game media number storage means has fallen below the threshold value.
The problem that the original invention 3 aims to solve is to notify the player at an early stage that the total number of game media stored in the game media number storage means has fallen below a threshold value.

The initial invention 3 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
When the total number of game media stored in the game media number storage means is equal to or greater than a threshold value, a count notification is made to prompt the player to operate a count switch;
The counting notification is a notification in which a predetermined image and/or a predetermined sound is repeatedly reproduced for a predetermined length of time from the beginning to the end,
If the total number of game media stored in the game media number storage means falls below a threshold value during the playback of the predetermined image and/or predetermined sound constituting the counting notification, the playback of the predetermined image and/or predetermined sound constituting the counting notification is terminated without reaching its end (in FIG. 159, at the timing of "X55", the image display device 23 is in the middle of playing the image prompting the player to operate the counting switch 47, and the speaker 22 is in the middle of playing the sound prompting the player to operate the counting switch 47, but when the total number of medals stored in the medal count control RWM 522 reaches "14999", the image and sound prompting the player to operate the counting switch 47 are terminated without reaching their end).
It is characterized by:

According to initial invention 3, when the total number of gaming media stored in the gaming media number storage means falls below a threshold, the specified images and/or sounds that make up the counting notification are terminated before being played to their end, thereby allowing the player to be notified early that the total number of gaming media stored in the gaming media number storage means has fallen below the threshold.

4. Original invention 4
In conventional gaming machines, when the total number of gaming media stored in the gaming media number storage means reaches or exceeds a predetermined threshold value ("15,000"), a notification is issued to prompt the player to operate a counting switch (for example, JP 2023-064762 A).
The problem that the original invention 4 aims to solve is to notify the player when the total number of game media stored in the game media number storage means falls below a threshold value, even if the counting switch is not operated.

The initial invention 4 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
a bet switch (3 bet switch 40b) that is operated when betting gaming media;
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
the game medium number control means is capable of executing a bet process of subtracting the bet number "N1"("3") from the total number of game media stored in the game medium number storage means based on the operation of the bet switch;
When the total number of game media stored in the game media number storage means is equal to or greater than "N2"("15,000"), a count notification is made to prompt the user to operate a count switch.
When the total number of gaming media stored in the gaming media number storage means is equal to or greater than "N2" and less than "N1 + N2", the number of gaming media betted is "0", and the counting notification is being executed, if the bet switch is operated, the counting notification will be terminated (in FIG. 160, at the timing of "X61", the total number of medals stored in the medal count control RWM 522 is "15,000", and the counting notification is being output from the speaker 22 and the image display device 23, but thereafter, at the timing of "X62", the 3 bet switch 40b is turned on, and when the total number of medals stored in the medal count control RWM 522 becomes "14,997" (less than "15,000"), the counting notification from the speaker 22 and the image display device 23 will be terminated).
It is characterized by:

According to initial invention 4, when the total number of gaming media stored in the gaming media number storage means falls below a threshold, the counting notification that prompts the player to operate the counting switch is terminated by operating the bet switch, not the counting switch, thereby informing the player that the total number of gaming media stored in the gaming media number storage means has fallen below the threshold.

5. Original invention 5
In conventional gaming machines, when the total number of gaming media stored in the gaming media number storage means reaches or exceeds a predetermined threshold value ("15,000"), a notification is issued to prompt the player to operate a counting switch (for example, JP 2023-064762 A).
The problem that the original invention 5 aims to solve is to notify the player when the total number of game media stored in the game media number storage means falls below a threshold value, even if the counting switch is not operated.
Furthermore, even if no game media are awarded, when the total number of game media stored in the game media number storage means reaches or exceeds a threshold value, the player is notified of this fact.

The initial invention 5 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
a bet switch (3 bet switch 40b) operated when placing a bet on gaming media;
and a settlement switch (46) that is operated when returning the bet game media,
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
the game medium number control means is capable of executing a bet process of subtracting the bet number "N1"("3") from the total number of game media stored in the game medium number storage means based on the operation of the bet switch;
the game medium count control means is capable of executing a settlement process of adding the number of bets to the total number of game media stored in the game medium count storage means based on the operation of the settlement switch;
When the total number of game media stored in the game media number storage means is equal to or greater than "N2"("15,000"), a count notification is made to prompt the player to operate a count switch.
When the total number of game media stored in the game media number storage means is equal to or greater than "N2" and less than "N1 + N2", the number of game media bet is "0", and the counting notification is being executed, if the bet switch is operated, the counting notification is terminated, and if the settlement switch is operated thereafter, the counting notification is executed again (at the timing of "X61" in FIG. 160, the total number of medals stored in the medal count control RWM 522 is "15,000", and the counting notification is output from the speaker 22 and the image display device 23). However, thereafter, at the timing of "X62", when the 3-bet switch 40b is turned on and the total number of medals stored in the medal count control RWM 522 becomes "14,997" (less than "15,000"), the counting notification is stopped on the speaker 22 and the image display device 23. Thereafter, at the timing of "X67", when the settlement switch 46 is turned on and the total number of medals stored in the medal count control RWM 522 becomes "15,000", the counting notification is again output on the speaker 22 and the image display device 23.
It is characterized by:

According to the initial invention 5, when the total number of gaming media stored in the gaming media number storage means falls below a threshold value, the counting notification that prompts the player to operate the counting switch is terminated by operating the bet switch, not the counting switch, so that the player can be notified that the total number of gaming media stored in the gaming media number storage means falls below a threshold value.
Furthermore, when the total number of game media stored in the game media number storage means becomes equal to or greater than a threshold value by operating the settlement switch, rather than game media being provided, a counting notification is executed to prompt the player to operate the counting switch, so that the player can be informed that the total number of game media stored in the game media number storage means becomes equal to or greater than a threshold value.

6. Original invention 6
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, the image display device displays the words "counting in progress" to indicate that counting is taking place, and the speaker outputs a counting sound to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 6 aims to solve is to let the player know in an easy-to-understand manner whether the counting was performed by short pressing of the counting switch or by long pressing of the counting switch.

The initial invention 6 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
The game medium number control means is capable of executing a counting process of subtracting the counted game medium number "N1"("1") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time ("500" ms) (when the counting switch 47 is short-pressed),
the game medium number control means, when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time (when the counting switch 47 is pressed and held), is capable of executing a counting process of subtracting the counted game medium number "N2"(N2>N1)("50") from the total number of game media stored in the game medium number storage means;
When the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time and the counting process is being executed, a counting display indicating that counting is in progress is displayed on the image display device (23) (in FIG. 161, when the counting switch 47 is turned on (long pressed) from "X88" to "X93", the counting display is displayed on the image display device 23). However, when the time from when the counting switch is turned on to when it is turned off is less than the predetermined time and the counting process is being executed, the counting display is not displayed on the image display device (in FIG. 161, when the counting switch 47 is turned on (short pressed) from "X82" to "X83", the counting display is not displayed on the image display device 23).
It is characterized by:

According to the initial invention 6, when the time from when the counting switch is turned on to when it is turned off is longer than a predetermined time (when the counting switch is pressed and held down) and the counting process is executed, a counting display indicating that counting is in progress is displayed on the image display device.
On the other hand, when the time from when the counting switch is turned on to when it is turned off is less than the predetermined time (short press) and the counting process is executed, the counting display indicating that counting is in progress is not displayed on the image display device.
This allows the player to easily know whether the counting process was executed by short pressing of the counting switch or by long pressing of the counting switch.

7. Original invention 7
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, the image display device displays the words "counting in progress" to indicate that counting is taking place, and the speaker outputs a counting sound to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 7 aims to solve is to inform the player in an easy-to-understand manner that the counting switch has been pressed and counted.

The initial invention 7 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
a performance switch (push button 86) that is operated when the performance is to proceed;
and a performance switch lamp (push button lamp 88) that illuminates the operation body of the performance switch;
the game medium number control means, when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time (500 ms) (when the counting switch 47 is pressed and held), is capable of executing a counting process of subtracting a predetermined counted number of game media (50) from the total number of game media stored in the game medium number storage means;
When the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time and the counting process is being executed, the effect switch lamp is lit, but acceptance of operation of the effect switch is disabled, and after the counting switch is turned off, the effect switch lamp is turned off (in FIG. 161, when the counting switch 47 is turned on (pressed and held) from "X88" to "X93", the push button lamp 88 is lit from "X91" to "X95", but acceptance of operation of the push button 86 is disabled during that time, and when the counting switch 47 is turned off at the timing of "X93", the push button lamp 88 is then turned off at the timing of "X95").
It is characterized by:

According to the initial invention 7, when the time from when the counting switch is turned on to when it is turned off is longer than a predetermined time (when the counting switch is pressed and held down) and the counting process is executed, the effect switch lamp is turned on, so that the player can be easily informed that the counting switch has been pressed and held down and the counting process has been executed.
Furthermore, when the effect switch lamp is turned on, it is possible that the effect switch may be mistakenly thought to be prompted to be operated, and the effect switch may be operated; however, since acceptance of the effect switch operation is disabled, even if the effect switch is operated, processing corresponding to the operation of the effect switch will not be executed.

8. Original invention 8
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, the image display device displays the words "counting in progress" to indicate that counting is taking place, and the speaker outputs a counting sound to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 8 aims to solve is to inform the player in an easy-to-understand manner that the counting switch has been pressed and counted.

The initial invention 8 (tenth embodiment) is
a front door (16) attached to the cabinet (15) so as to be able to open and close;
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
a performance switch (push button 86) that is operated when the performance is to proceed;
and a performance switch lamp (push button lamp 88) that illuminates the operation body of the performance switch;
the game medium number control means, when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time (500 ms) (when the counting switch 47 is pressed and held), is capable of executing a counting process of subtracting a predetermined counted number of game media (50) from the total number of game media stored in the game medium number storage means;
When the time from when the counting switch is turned on to when it is turned off is longer than a predetermined time and the counting process is being executed, the effect switch lamp is lit, but acceptance of operation of the effect switch is disabled, and after the counting switch is turned off, the effect switch lamp is turned off (in FIG. 165, when the counting switch 47 is turned on (pressed and held) from "X162" to "X167", the push button lamp 88 is lit from "X165" to "X169", but acceptance of operation of the push button 86 is disabled during that time, and when the counting switch 47 is turned off at the timing of "X167", the push button lamp 88 is then turned off at the timing of "X169").
When the opening of the front door is detected, the effect switch lamp is turned on, but operation acceptance of the effect switch is disabled, and the effect switch lamp remains on until a predetermined time has elapsed since the closing of the front door is detected, and when the predetermined time has elapsed since the closing of the front door is detected, the effect switch lamp is turned off (in FIG. 165, when the opening of the front door 16 is detected at timing "X171", the push button lamp 88 is turned on, but operation acceptance of the push button 86 is disabled, and when the closing of the front door 16 is detected at timing "X173", the push button lamp 88 is then turned off at timing "X176").
It is characterized by:

According to the initial invention 8, when the time from when the counting switch is turned on to when it is turned off is longer than a predetermined time (when the counting switch is pressed and held down) and the counting process is executed, the effect switch lamp is lit, so that the player can be easily informed that the counting switch has been pressed and held down and the counting process has been executed.
In addition, when the opening of the front door is detected, the effect switch lamp is turned on, so that the player and the hall staff can be notified that the front door has been opened.
Furthermore, when the counting switch is pressed and held or when the opening of the front door is detected, if the effect switch lamp is turned on, it may be mistakenly thought that an instruction to operate the effect switch has been prompted, and the effect switch may be operated. However, since acceptance of the effect switch operation is disabled, even if the effect switch is operated, processing corresponding to the operation of the effect switch will not be executed.
Furthermore, by changing the manner in which the effect switch lamp is turned off when the counting switch is pressed and held down and when the opening of the front door is detected, it is possible to distinguish whether the counting switch is pressed and held down or the opening of the front door is detected.
In addition, the player can be made aware that the lighting of the effect switch lamp when the counting switch is pressed and held is not an error notification.

9. Original invention 9
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, a counting sound is output from the speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
However, if the counting switch is pressed and held down to count the game media while background music is being output from the speaker, the counting sound becomes difficult to hear.
The problem that the original invention 9 aims to solve is to make it possible to count the number of gaming media by pressing and holding the counting switch while background music is being output from the speaker without making the counting sound difficult to hear.

The initial invention 9 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means, when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time ("500" ms), is capable of executing a counting process of subtracting a predetermined counted number of game media ("50") from the total number of game media stored in the game medium number storage means;
When a predetermined BGM (game BGM) is being output, if the time from when the counting switch is turned on to when it is turned off is equal to or longer than the predetermined time and the counting process is executed, the volume of the predetermined BGM is made lower than the volume before the counting process is executed, and after the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the counting process is executed (in FIG. 161, when the counting switch 47 is turned on (pressed and held) from "X88" to "X93", the volume of the game BGM is made low from "X91" to "X95", and when the counting switch 47 is turned off at the timing of "X93", the volume of the game BGM is then returned to high at the timing of "X95").
It is characterized by:

According to the initial invention 9, when the counting switch is pressed and held down to execute the counting process while the predetermined background music is being output, the volume of the predetermined background music is made lower than the volume before the counting process is executed, so that the counting sound can be made to stand out and the counting sound can be prevented from becoming difficult to hear.
Thereafter, when the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the execution of the counting process, so that the player does not have to perform an operation to return the volume of the predetermined BGM to the original volume, thereby preventing the player from feeling bothered.

10. Original invention 10
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, a counting sound is output from the speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
However, if the counting switch is pressed and held down to count the game media while background music is being output from the speaker, the counting sound becomes difficult to hear.
The problem that the original invention 10 aims to solve is to make it possible to count game media by pressing and holding the counting switch while background music is being output from the speaker without making the counting sound difficult to hear.

The initial invention 10 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
The game medium number control means is capable of executing a counting process of subtracting the counted game medium number "N1"("1") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time ("500" ms) (when the counting switch 47 is short-pressed),
The game medium number control means is capable of executing a counting process of subtracting the counted game medium number "N2"(N2>N1)("50") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time ("500" ms) (when the counting switch 47 is pressed and held down),
When a predetermined BGM (game BGM) is being output, if the time from when the counting switch is turned on to when it is turned off exceeds a predetermined time (when the counting switch is pressed and held down) and the counting process is executed, the volume of the predetermined BGM is made lower than the volume before the counting process is executed, and after the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the counting process is executed (in FIG. 161, when the counting switch 47 is turned on (pressed and held down) from "X88" to "X93", the volume of the game BGM is made low from "X91" to "X95", and when the counting switch 47 is turned off at the timing of "X93", the volume of the game BGM is then returned to high at the timing of "X95").
When a predetermined background music is being output, if the time from when the counting switch is turned on to when it is turned off (short press) is less than the predetermined time and the counting process is executed, the volume of the predetermined background music is maintained (in FIG. 161, when the counting switch 47 is turned on (short press) from "X82" to "X83", the volume of the game background music is maintained at a high volume without being reduced).
It is characterized by:

According to the initial invention 10, when the counting switch is pressed and held down to execute counting processing while predetermined background music is being output, the volume of the predetermined background music is made smaller than the volume before the counting processing is executed, so that the counting sound can be made prominent and the counting sound can be prevented from becoming difficult to hear.
Thereafter, when the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the execution of the counting process, so that the player does not have to perform an operation to return the volume of the predetermined BGM to the original volume, thereby preventing the player from feeling bothered.
Furthermore, when the counting switch is pressed briefly to execute counting processing while predetermined background music is being output, the counting processing by the short press ends immediately, so by maintaining the volume of the predetermined background music, the player does not feel uncomfortable and the interest of the player is not lost.

11. Original invention 11
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, a counting sound is output from the speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
However, if the counting switch is pressed and held down to count the game media while background music is being output from the speaker, the counting sound becomes difficult to hear.
The problem that the original invention 11 aims to solve is to make it possible to count game media by pressing and holding the counting switch while background music is being output from the speaker without making the counting sound difficult to hear.

The initial invention 11 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means, when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time (500 ms) (when the counting switch 47 is pressed and held), is capable of executing a counting process of subtracting a predetermined counted number of game media (50) from the total number of game media stored in the game medium number storage means;
The game medium number control means is capable of executing a lending process of adding a predetermined number of game media to be lent ("50") to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202),
When a predetermined BGM (game BGM) is being output, if the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time and the counting process is executed, the volume of the predetermined BGM is made lower than the volume before the counting process is executed, and after the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the counting process is executed (in FIG. 163, when the counting switch 47 is turned on (pressed and held) from "X122" to "X125", the volume of the game BGM is made low from "X125" to "X127", and when the counting switch 47 is turned off at the timing of "X125", the volume of the game BGM is then returned to high at the timing of "X127").
When a predetermined background music is being output, and a lending process is executed based on a game medium lending operation, the volume of the predetermined background music is maintained (in FIG. 163, when the lending switch 202 is turned on at timing "X133", a lending process is executed at timing "X134" to add the number of lent game media "50" to the total number of medals in the medal count control RWM 522, but the volume of the game background music is maintained at a high volume without being reduced).
It is characterized by:

According to the initial invention 11, when the counting switch is pressed and held down to execute the counting process while the predetermined background music is being output, the volume of the predetermined background music is made smaller than the volume before the counting process is executed, so that the counting sound can be made to stand out and the counting sound can be prevented from becoming difficult to hear.
Thereafter, when the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the execution of the counting process, so that the player does not have to perform an operation to return the volume of the predetermined BGM to the original volume, thereby preventing the player from feeling bothered.
Furthermore, since the lending operation is usually not performed continuously but only once, the lending process also ends quickly. Therefore, even if the game medium lending operation is performed while the predetermined BGM is being output, the lending process ends quickly, so by maintaining the volume of the predetermined BGM, the player does not feel uncomfortable and the interest of the player is not lost.

12. Original invention 12
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, a counting sound is output from the speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
However, if the counting switch is pressed and held down to count the game media while background music is being output from the speaker, the counting sound becomes difficult to hear.
The problem that the original invention 12 aims to solve is to make it possible to count game media by pressing and holding the counting switch while background music is being output from the speaker without making the counting sound difficult to hear.

The initial invention 12 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means, when the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time (500 ms) (when the counting switch 47 is pressed and held), is capable of executing a counting process of subtracting a predetermined counted number of game media (50) from the total number of game media stored in the game medium number storage means;
The game medium number control means is capable of executing a lending process of adding a predetermined number of game media to be lent ("50") to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202),
When the total number of game media stored in the game media number storage means is equal to or greater than a threshold value ("15,000"), a count notification is made to prompt the user to operate a count switch;
When a predetermined BGM (game BGM) is being output, if the time from when the counting switch is turned on to when it is turned off is equal to or longer than a predetermined time and the counting process is executed, the volume of the predetermined BGM is made lower than the volume before the counting process is executed, and after the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the counting process is executed (in FIG. 164, when the counting switch 47 is turned on (pressed and held) from "X142" to "X145", the volume of the game BGM is made low from "X145" to "X147", and when the counting switch 47 is turned off at the timing of "X145", the volume of the game BGM is then returned to high at the timing of "X147").
When a predetermined background music is being output, a lending process is executed based on a game medium lending operation, and when the total number of game media stored in the game medium number storage means becomes equal to or greater than a threshold value, a counting notification is issued, but the volume of the predetermined background music is maintained (in FIG. 164, when the lending switch 202 is turned on at timing "X153", a lending process is executed at timing "X154" to add the number of lent game media "50" to the total medal count of the medal count control RWM 522, and when the total medal count becomes equal to or greater than "15,000", a counting notification is issued, but the volume of the game background music is maintained at a high volume without being lowered).
It is characterized by:

According to the initial invention 12, when the counting switch is pressed and held down to execute the counting process while the predetermined background music is being output, the volume of the predetermined background music is made lower than the volume before the counting process is executed, so that the counting sound can be made to stand out and the counting sound can be prevented from becoming difficult to hear.
Thereafter, when the counting switch is turned off, the volume of the predetermined BGM is returned to the volume before the execution of the counting process, so that the player does not have to perform an operation to return the volume of the predetermined BGM to the original volume, thereby preventing the player from feeling bothered.
Furthermore, since the game can be continued even if the total number of game media exceeds the threshold value, even if a game media lending operation is performed while the specified background music is being output, and the total number of game media exceeds the threshold value, and a counting notification is executed to prompt the player to operate the counting switch, the volume of the specified background music is maintained so that the player does not feel uncomfortable and does not lose interest.

13. Original invention 13
In conventional gaming machines, when a counting switch is operated and gaming media are counted, a counting sound is output from a speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 13 aims to solve is to output a counting sound for the player to hear each time the counting switch is pressed, even if the counting switch is pressed repeatedly.

The initial invention 13 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
The game medium number control means is capable of executing a counting process of subtracting a predetermined count game medium number ("1") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time ("500" ms) (when the counting switch 47 is short-pressed),
The game medium number control means is capable of executing a lending process of adding a predetermined number of game media to be lent ("50") to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202),
When the counting process is executed within a predetermined time from when the counting switch is turned on to when it is turned off, a counting sound having a length of time "T1" (200 ms) from the start to the end is output (in FIG. 166, when the counting switch 47 is pressed briefly at the timing of "X182", a counting sound for a short press having a length of "200" ms from the start to the end is output at the timing of "X183").
When a lending process is executed based on a game medium lending operation, a lending sound having a length from start to end of time "T2" (450 ms) is output (in FIG. 166, when the lending switch 202 is operated at timing "X187", a lending sound having a length from start to end of 450 ms is output at timing "X188").
The time "T1" is less than a specific time (the transmission interval of counting notifications and lending notifications, which is "300" ms),
The time "T2" is characterized by being equal to or longer than a specific time.

According to the original invention 13, the length from the beginning to the end of the counting sound output when the counting switch is shortly pressed is time "T1", which is less than the specific time. Therefore, even if the counting process is executed by shortly pressing the counting switch every specific time by repeatedly shortly pressing the counting switch, the counting sound when the counting switch is shortly pressed can be output and heard by the player every time the counting switch is shortly pressed.
Furthermore, the length from the beginning to the end of the lending sound is time "T2," which is equal to or longer than the specific time. The lending operation of gaming media is usually not performed continuously, but only once. Therefore, by making the length from the beginning to the end of the lending sound equal to or longer than the specific time, the lending sound can be clearly heard by the player.

14. Original invention 14
In conventional gaming machines, when a counting switch is operated and gaming media are counted, a counting sound is output from a speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 14 aims to solve is to output a counting sound for the player to hear each time the counting switch is pressed, even if the counting switch is pressed repeatedly.

The initial invention 14 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
The game medium number control means is capable of executing a counting process of subtracting a predetermined count game medium number ("1") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time ("500" ms) (when the counting switch 47 is short-pressed),
The game medium number control means is capable of executing a lending process of adding a predetermined number of game media to be lent ("50") to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202),
When the counting process is executed within a predetermined time from when the counting switch is turned on to when it is turned off, a counting sound having a length of time "T1" (200 ms) from the start to the end is output (in FIG. 166, when the counting switch 47 is pressed briefly at the timing of "X182", a counting sound for a short press having a length of "200" ms from the start to the end is output at the timing of "X183").
When a lending process is executed based on a game medium lending operation, a lending sound having a length from start to end of time "T2" (450 ms) is output (in FIG. 166, when the lending switch 202 is operated at timing "X187", a lending sound having a length from start to end of 450 ms is output at timing "X188").
The time "T1" is less than a specific time (the transmission interval of counting notifications and lending notifications, which is "300" ms),
The time “T2” is equal to or greater than a specific time,
When the game medium lending operation is performed continuously, the lending process can be performed at the shortest interval of time "T3"("300" ms),
Time “T3” is a specific time,
When game medium lending operations are performed consecutively and lending processes are performed at time intervals of "T3", the next lending sound is output from the beginning before one lending sound is output to the end (in FIG. 167, output of the "first" lending sound begins at timing "X203", the "second" lending sound is output from the beginning at timing "X205" before output of the "first" lending sound is completed to the end, and the "third" lending sound is output from the beginning at timing "X207" before output of the "second" lending sound is completed to the end).
It is characterized by:

According to the original invention 14, the length from the beginning to the end of the counting sound output when the counting switch is shortly pressed is time "T1", which is less than the specific time. Therefore, even if the counting process is executed by shortly pressing the counting switch every specific time by repeatedly shortly pressing the counting switch, the counting sound when the counting switch is shortly pressed can be output and heard by the player every time the counting switch is shortly pressed.
Furthermore, the length from the beginning to the end of the lending sound is time "T2", which is equal to or longer than the specific time. Therefore, by making the length from the beginning to the end of the lending sound equal to or longer than the specific time, the lending sound can be clearly heard by the player.
However, if the length from the beginning to the end of the rental sound is set to a specific time or more, when a rental operation of a gaming medium is performed at specific time intervals and a rental process is executed, there is a possibility that the next rental process will be executed before one rental sound has been output to its end.
Therefore, in the initial invention 14, if the next lending process is executed before one lending sound has been output to its end, the first lending sound is not output to its end, but the next lending sound is output from its beginning, overwriting it. This allows the lending sound to be output from its beginning each time a lending process is executed, making it easier for the player to understand the number of times the lending process has been executed.

15. Original invention 15
In conventional gaming machines, when a counting switch is operated and gaming media are counted, a counting sound is output from a speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 15 aims to solve is to output a counting sound for the player to hear each time the counting switch is pressed, even if the counting switch is pressed repeatedly.

The initial invention 15 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
The game medium number control means is capable of executing a counting process of subtracting a predetermined count game medium number ("1") from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time ("500" ms) (when the counting switch 47 is short-pressed),
The game medium number control means is capable of executing a lending process of adding a predetermined number of game media to be lent ("50") to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202),
When the counting process is executed within a predetermined time from when the counting switch is turned on to when it is turned off, a counting sound having a length of time "T1" (200 ms) from the start to the end is output (in FIG. 166, when the counting switch 47 is pressed briefly at the timing of "X182", a counting sound for a short press having a length of "200" ms from the start to the end is output at the timing of "X183").
When a lending process is executed based on a game medium lending operation, a lending sound having a length from start to end of time "T2" (450 ms) is output (in FIG. 166, when the lending switch 202 is operated at timing "X187", a lending sound having a length from start to end of 450 ms is output at timing "X188").
The time "T1" is less than a specific time (the transmission interval of counting notifications and lending notifications, which is "300" ms),
The time “T2” is equal to or greater than a specific time,
When the game medium lending operation is performed continuously, the lending process can be performed at the shortest interval of time "T3"("300" ms),
Time “T3” is a specific time,
When game medium lending operations are executed continuously and lending processes are executed at time intervals of "T3", one lending sound is output to its end, and based on the execution of the subsequent lending process, the next lending sound can be output from its beginning (in FIG. 168, at timing "X223", output of the "first" lending sound is started, and this "first" lending sound is output to its end (timing "X226" in FIG. 168). Thereafter, at timing "X227" in FIG. 168, the "second" lending sound is output from its beginning, and this "second" lending sound is output to its end (timing "X230" in FIG. 168).)
It is characterized by:

According to the original invention 15, the length from the beginning to the end of the counting sound output when the counting switch is shortly pressed is the time "T1", which is less than the specific time. Therefore, even if the counting process is executed by short pressing of the counting switch every specific time by repeating short pressing of the counting switch, the counting sound at the time of short pressing can be output and heard by the player every time the counting switch is shortly pressed.
Furthermore, the length from the beginning to the end of the lending sound is time "T2", which is equal to or longer than the specific time. Therefore, by making the length from the beginning to the end of the lending sound equal to or longer than the specific time, the lending sound can be clearly heard by the player.
However, if the length from the beginning to the end of the rental sound is set to a specific time or more, when the rental operation of the game medium is performed at specific time intervals and the rental process is executed, there is a possibility that the next rental process will be executed before one rental sound has been output to its end.
Therefore, in the initial invention 15, if the next rental process is executed before one rental sound has been output to its end, the first rental sound is output to its end, and based on the execution of the subsequent rental process, the next rental sound is output from its beginning. This allows the player to hear the rental sound from its beginning to its end once it has been output, so if the rental sound contains words, for example, the player can hear the words from beginning to end, preventing the words from being cut off midway and becoming incomprehensible.

16. Original invention 16
In a conventional gaming machine, it is known to execute a counting process of subtracting the number of counted gaming media from the total number of gaming media based on the operation of a counting switch (for example, Japanese Patent Application Laid-Open No. 2023-064762).
The problem that the original invention 16 aims to solve is to make it possible to execute counting processing even if other switches are operated.

The initial invention 16 (tenth embodiment) is
a plurality of reels (31);
a start switch (41) that is operated to start the rotation of each reel;
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
Bet switches (1 bet switch 40a, 3 bet switch 40b) that are operated when betting gaming media;
and a settlement switch (46) that is operated when returning the bet game media,
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
the game medium number control means is capable of executing a bet process of subtracting the number of bets from the total number of game media stored in the game medium number storage means based on the operation of the bet switch;
the game medium count control means is capable of executing a settlement process of adding the number of bets to the total number of game media stored in the game medium count storage means based on the operation of the settlement switch;
the game medium number control means is capable of executing a lending process of adding the number of lent game media to the total number of game media stored in the game medium number storage means based on a game medium lending operation (operation of the lending switch 202);
When the settlement switch is on, the acceptance of operations of the bet switch and start switch is invalid, but the acceptance of operations of the counting switch and the lending operation of game media is valid (in FIG. 169, from "X247" onwards, the settlement switch 46 is on, and at this time, the acceptance of operations of the 3 bet switch 40b and start switch 41 is invalid, but the acceptance of operations of the counting switch 47 and lending switch 202 is valid).
It is characterized by:

According to the initial invention 16, when the settlement switch is in the on state, the operation of the bet switch and start switch is disabled, thereby preventing the game from progressing, and thereby making the player aware that the state is not normal.
Furthermore, even if the settlement switch is in the on state, by enabling the operation acceptance of the counting switch, it is possible to execute the counting process and return the game media.
Furthermore, even if the settlement switch is in the on state, by enabling acceptance of the game medium lending operation, the lending process can be executed and the game medium can be made available for lending.

17. Original invention 17
In conventional gaming machines, when the total number of gaming media reaches or exceeds a threshold value, a counting notification is issued on the image display device to prompt the player to operate a counting switch, and when the game transitions to a standby state without the counting switch being operated, a standby screen is displayed on the image display device.However, it is known that the counting notification continues on the image display device even while the standby screen is being displayed, as long as the total number of gaming media does not fall below the threshold value (for example, JP 2023-064762 A).
The problem that the original invention 17 aims to solve is to display an appropriate screen on the image display device according to the type of switch operated while the standby screen is being displayed.

The initial invention 17 (tenth embodiment) is
an image display device (23);
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) operated when paying off game media;
bet switches (1 bet switch 40a, 3 bet switch 40b) that are operated when placing a bet on gaming media;
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
the game medium number control means is capable of executing a bet process of subtracting the number of bets from the total number of game media stored in the game medium number storage means based on the operation of the bet switch;
When it is determined that the game is in a standby state, a standby screen (demo screen) corresponding to the standby state is displayed on the image display device;
When the bet switch is operated while the standby screen is displayed on the image display device, the bet process is enabled and the display of the standby screen on the image display device is terminated (when the 3 bet switch 40b is turned on at the timing of "X275" in FIG. 170, the display of the demo screen on the image display device 23 is terminated and the display is switched to the game screen).
When the counting switch is operated while the standby screen is displayed on the image display device, the counting process can be executed and the standby screen display on the image display device is maintained (in FIG. 170, from "X262" to "X265", the counting switch 47 is turned on, but the demo screen display on the image display device 23 is maintained and the display is not switched to the game screen).
It is characterized by:

According to the initial invention 17, the bet switch is operated when playing a game, so when the bet switch is operated while a standby screen is displayed on the image display device, the display of the standby screen on the image display device is terminated.
In addition, since the counting switch is operated when stopping the game, when a standby screen is displayed on the image display device, if the counting switch is operated, the display of the standby screen on the image display device will be maintained.
As a result, when a standby screen is displayed on the image display device, an appropriate screen can be displayed on the image display device depending on the type of switch that has been operated.

18. Original invention 18
In a conventional gaming machine, when the total number of game media reaches or exceeds a threshold value, a count notification is issued on an image display device to prompt the player to operate a count switch (for example, Japanese Patent Application Laid-Open No. 2023-064762).
The problem that the original invention 18 aims to solve is to display an appropriate screen according to the situation on an image display device.

The initial invention 18 (tenth embodiment) is
a plurality of reels (31);
a stop switch (42) that is operated to stop the rotation of each reel;
an image display device (23);
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
When the total number of game media stored in the game media number storage means is equal to or greater than a threshold value ("15,000"), a counting notification image (FIG. 171(1)) that prompts the user to operate the counting switch can be displayed on the image display device.
The stop switch has a recommended pressing order (forward pressing, left first stop) and a non-recommended pressing order (irregular pressing, center first stop or right first stop),
When the stop switch is operated in a non-recommended pressing order, a recommended pressing order notification image (Fig. 171 (2)) that prompts the user to operate the stop switch in the recommended pressing order can be displayed on the image display device.
The size of the counting notification image is larger than the size of the recommended push order notification image (as shown in FIG. 171(1), when the width of the counting notification image is "W1" and the height of the counting notification image is "H1", and as shown in FIG. 171(2), when the width of the recommended push order notification image is "W2" and the height of the recommended push order notification image is "H2", it is configured to satisfy "W1>W2" and "H1>H2").
It is characterized by:

According to initial invention 18, the size of the counting notification image is larger than the size of the recommended push order notification image, so the counting notification image can be displayed with priority, thereby encouraging the operation of the counting switch.

19. Original invention 19
In conventional gaming machines, it is known that when a bet switch is operated, a bet sound is output from a speaker, and when a settlement switch is operated, a settlement sound is output from a speaker (for example, JP 2023-064762 A).
The problem that the original invention 18 aims to solve is to output an appropriate sound from a speaker according to the operated switch.

The initial invention 19 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
A first bet switch (1 bet switch 40a) that is operated when betting "N1"("1") gaming media;
A second bet switch (3 bet switch 40b) that is operated when betting "N2"(N2>N1)("3") game media;
and a settlement switch (46) that is operated when returning the bet game media,
the game medium number control means is capable of executing a bet process of subtracting the bet number "N1" from the total number of game media stored in the game medium number storage means based on the operation of the first bet switch;
the number-of-game-media control means is capable of executing a bet process of subtracting the bet number "N2" from the total number of game media stored in the number-of-game-media storage means based on the operation of the second bet switch;
the game medium number control means is capable of executing a settlement process of adding the number of bets to the total number of game media stored in the game medium number storage means based on the operation of the settlement switch;
When a bet process is executed to subtract the number of bets "N1" from the total number of game media based on the operation of the first bet switch, a first bet sound is output (when the 1 bet switch 40a is turned on at the timing of "X282" in FIG. 172, a 1 bet sound (such as a "beep") is output from the speaker 22).
When a bet process is executed to subtract the bet number "N2" from the total number of game media based on the operation of the second bet switch, a second bet sound different from the first bet sound is output (in FIG. 172, when the 3-bet switch 40b is turned on at the timing of "X288", a 3-bet sound (such as a "buzz buzz" sound) is output from the speaker 22).
When a settlement process is executed to add the number of bets "N1" to the total number of game media based on the operation of the settlement switch, and when a settlement process is executed to add the number of bets "N2" to the total number of game media based on the operation of the settlement switch, the same settlement sound is output (when the settlement switch 46 is turned on at the timing of "X285" in FIG. 172, a settlement sound (a sound like "plug") is output from the speaker 22. When the settlement switch 46 is turned on at the timing of "X291" in FIG. 172, the same settlement sound (a sound like "plug") as that at the timing of "X285" is output from the speaker 22).
It is characterized by:

According to original invention 19, when an "N1" bet is placed based on the operation of the first bet switch, a first bet sound is output, and when an "N2" bet is placed based on the operation of the second bet switch, a second bet sound different from the first bet sound is output. However, when the settlement switch is operated whether an "N1" bet is placed or an "N2" bet is placed, the same settlement sound is output, making it easier for the player to understand that the settlement has been made.

20. Original invention 20
In a conventional gaming machine, when the total number of game media reaches or exceeds a threshold value, a count notification is issued on an image display device to prompt the player to operate a count switch (for example, Japanese Patent Application Laid-Open No. 2023-064762).
The problem that the original invention 20 aims to solve is to display an appropriate screen according to the situation on an image display device.

The initial invention 20 (tenth embodiment) is
an image display device (23);
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying back game media;
bet switches (1 bet switch 40a, 3 bet switch 40b) that are operated when betting gaming media,
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
the game medium number control means is capable of executing a bet process of subtracting the number of bets from the total number of game media stored in the game medium number storage means based on the operation of the bet switch;
When the total number of game media stored in the game media number storage means is equal to or greater than a threshold value ("15,000"), a counting notification image that prompts the user to operate a counting switch can be displayed on the image display device;
When the counting notification image is displayed on the image display device, if the total number of game media stored in the game media number storage means becomes less than the threshold value due to the execution of a bet process based on the operation of the bet switch, the display of the counting notification image on the image display device is terminated;
A menu screen (FIG. 173(1)) can be displayed on the image display device based on the operation of a predetermined switch (push button 86),
When a menu screen is displayed on the image display device, if the bet switch is operated, the display of the menu screen on the image display device is terminated,
When a menu screen and a counting notification image are displayed on the image display device, if a bet process is executed based on the operation of the bet switch and the total number of gaming media stored in the gaming media number storage means falls below a threshold value, the display of the menu screen on the image display device is terminated and then the display of the counting notification image is terminated (at the timing of "X314" in FIG. 174, with both the menu screen and the counting notification image displayed on the image display device 23, the 3 bet switch 40b is turned on and a bet process is executed to subtract the bet number "3" from the total number of medals, so that when the total number of medals becomes "14,997" (less than "15,000"), the display of the menu screen on the image display device 23 is terminated, and then, at the timing of "X315" in FIG. 174, the display of the counting notification image is terminated).
It is characterized by:

According to the original invention 20, by ending the display of the counting notification image after ending the display of the menu screen, the counting notification image can be viewed by the player for as long as possible.

21. Original invention 21
In a conventional gaming machine, when the total number of game media reaches or exceeds a threshold value, a count notification is issued on an image display device to prompt the player to operate a count switch (for example, Japanese Patent Application Laid-Open No. 2023-064762).
The problem that the original invention 21 aims to solve is to display an appropriate screen according to the situation on an image display device.

The initial invention 21 (tenth embodiment) is
an image display device (23);
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
When the total number of game media stored in the game media number storage means is equal to or greater than a threshold value ("15,000"), a counting notification image (FIG. 175(2)) that prompts the user to operate the counting switch can be displayed on the image display device.
When it is determined that the game is in a standby state, a standby screen (demo screen) corresponding to the standby state is displayed on the image display device;
On the standby screen, a volume change image (FIG. 175(1)) indicating that the volume can be changed can be displayed.
The counting notification image is repeatedly displayed and hidden in a cycle of "T1" (in FIG. 176, the counting notification image is displayed on the image display device 23 at the timing of "X324". The counting notification image is repeatedly displayed and hidden in a cycle of "3" seconds, such as displayed for "2" seconds, hidden for "1" second, displayed for "2" seconds, and hidden for "1" second).
The volume change image is repeatedly displayed and hidden in a cycle of "T2" (in FIG. 176, the volume change image is displayed on the image display device 23 at the timing of "X322". The volume change image is repeatedly displayed and hidden in a cycle of "4" seconds, such as displayed for "2" seconds, hidden for "2" seconds, displayed for "2" seconds, and hidden for "2" seconds).
The period "T1" is characterized by being shorter than the period "T2".

According to initial invention 21, the cycle "T1" of the repeated display and non-display of the counting notification image is shorter than the cycle "T2" of the repeated display and non-display of the volume change image, making the counting notification image more noticeable than the volume change image and making the counting notification image more memorable to the player.

22. Original invention 22
In conventional gaming machines, when the counting switch is pressed and held down and "50" gaming media are counted, a counting sound is output from the speaker to indicate that counting is taking place (for example, JP 2023-064762 A).
The problem that the original invention 22 aims to solve is to output the counting sound from the speaker at an appropriate volume.

The initial invention 22 (tenth embodiment) is
a game media number control means (a medal number control CPU 520, a medal number control means 520) for managing the number of game media (a medal number);
a game medium number storage means (a medal number control RWM 522) capable of storing the total number of game media (total number of medals);
a counting switch (47) that is operated when paying out game media;
the game medium number control means is capable of executing a counting process of subtracting the counted game medium number from the total game medium number stored in the game medium number storage means based on the operation of the counting switch;
When the counting process is executed, a counting sound is output to indicate that the counting process has been executed.
The volume can be changed while the counting sound is being output.
When a volume change operation is performed while the counting sound is being output, the volume of the counting sound can be changed (when the volume is changed from volume 5 to volume 4 by operating the cross key 87 and the push button 86 at the timing of "X349" in FIG. 177, the volume of the counting sound output from the speaker 22 when pressed and held is changed from volume 5 to volume 4).
It is characterized by:

According to original invention 22, when a volume change operation is performed while the counting sound is being output, the volume of the counting sound can be changed, allowing the counting sound to be output at an appropriate volume.

10 Slot machine, gaming machine 11 Power switch 12 Setting key switch 13 Setting switch 14 Reset switch 15 Cabinet 16 Front door 16c Control panel 17 Door switch 18 Display window 21 Performance lamp 22 Speaker 23 Image display device 31 Reel 32 Motor 33 Reel sensor 40a 1 bet switch 40b 3 bet switch 41 Start switch 42 Stop switch 46 Cancel switch, settlement switch 47 Counting switch 50 Main control board (main control means), main control board (main control means)
51 Input port 52 Output port 53 (First main control) RWM
53a bet number storage means 53b award number storage means 54 (first main control) ROM
55 Main CPU, (first main control) CPU
61 Role lottery means 62 Winning flag control means 65 Reel control means 66 Winning determination means 67 Award means 73 Setting value display means 76 Credit number display LED
77 Bet number display unit 78 Acquisition number display LED, awarded number display unit 80 Sub-control board (sub-control means), sub-control board (sub-control means)
80a 1-chip microprocessor 81 Input port 82 Output port 83 (Sub-control) RWM
84 (Sub-control) ROM
85 Sub-CPU, (Sub-control) CPU
86 Push button 87 Cross key 87a Up switch 87b Down switch 87c Right switch 87d Left switch 88 Push button lamp 91 Performance output control means 100 Payout control board (credit number management board), game medium number control board 101 Input port 102 Output port 103 (Second main control) RWM
103a Game media number storage means 104 (second main control) ROM
105 Credit number management CPU, (second main control) CPU
106 Capacitor 107 Capacitor A
108 Capacitor B
111 Credit number management means 112 Total number of game media (total number of medals) clear switch 113 Role ratio monitor 120 Number of game media (number of medals) display board (number of game media display device)
121 Game medium number (medal number) display unit 130 Connection terminal board 150 Power supply board 151 Capacitor 161 Harness A
162 Harness B
163 Harness C
164 Harness D
165 Harness E
166 Harness F
167 Harness G
168 Harness H
190 External centralized terminal board 200 Management device (CR unit), rental unit (dedicated unit)
201: bill insertion slot; 202: lending switch; 203: return switch; 204: number display unit (number of lendable gaming media (number of medals) display unit)
205 Card reader/writer 206 Number of lendable game media (number of medals) storage means 300 Hall computer 400 Management computer 500 One-chip microprocessor 501 Main CPU
502 Main control ROM
503 Main control RWM
504 Game media number control ROM
505 Game media number control RWM
506 ROM outside the usage area
507 RWM outside usage area
510 Main control CPU (main control means)
511 Main control ROM
512 Main control RWM
520 medal count control CPU (medal count control means)
521 Medal count control ROM
522 Medal count control RWM
600 Test firing test machine 601 Interface board 602 Interface board

Claims (1)

a game medium number storage means capable of storing the total number of game media;
a game medium number control means having a game medium number storage means;
A counting switch and
the game medium number control means is capable of executing a counting process of subtracting a specific number of game media from the total number of game media stored in the game medium number storage means when the time from when the counting switch is turned on to when it is turned off is less than a predetermined time;
the game medium number control means is capable of executing a lending process of adding a predetermined number of game media to the total number of game media stored in the game medium number storage means, based on a game medium lending operation being performed in the dedicated unit;
When the time from when the counting switch is turned on to when it is turned off is less than a predetermined time and a counting process for subtracting a specific number of game media is executed, a counting sound having a length of time "T1" from the start to the end can be output;
When a lending process is executed to add a predetermined number of game media based on the fact that a game media lending operation is performed in the dedicated unit, a lending sound having a length of time "T2" from the beginning to the end can be output;
Time "T2" is longer than time "T1",
The time “T2” is equal to or greater than a specific time,
The lending process for adding a predetermined number of game media can be continuously executed at intervals of at least time "T3",
Time “T3” is a specific time,
When the lending process for adding the predetermined number of game media is executed continuously at time intervals of "T3", even if the lending process for adding the predetermined number of game media is executed before the output of one lending sound is completed to the end, the output of the one lending sound that is being output continues and a new lending sound is not output from the beginning, and when the lending process for adding the predetermined number of game media is executed after the output of one lending sound is completed to the end, a new lending sound can be output from the beginning.
A gaming machine characterized by: