JP5738334B2 - Game machine - Google Patents

Description

  The present invention relates to a gaming machine such as a pachinko gaming machine or a slot gaming machine, and more particularly to a control process of a rendering operation in the gaming machine.

Japanese Patent No. 4613191

  In pachinko machines, slot machines, etc., it is possible to play games by lighting / flashing operations using light emitting parts using LEDs (Light Emitting Diodes), sound output from speakers, and driving of movable objects on the game board. An accompanying presentation is performed, or error notification, guidance display, etc. are performed by lighting / flashing operation of a light emitting unit or sound output by a speaker.

  In the gaming machine, various presentation control and error control are performed in addition to the control of the original game operation. For this reason, the control load of the microcomputer and the necessary memory capacity tend to increase. In view of this, the present invention proposes a technique for performing efficient processing for realizing various effects and reducing the memory capacity as much as possible.

A gaming machine according to the present invention includes a main control unit that controls a game operation in an integrated manner, outputs a control command related to the game operation, and an effect control unit that controls execution of an effect related to the game operation. The production control means has a plurality of production scenario tables in which a plurality of production data defining the operation of the production device are stored in the order of execution and end information is stored at the final position, and based on the control command, The designation information for designating one of the plurality of types of production scenario tables is registered in an empty channel of a work area in which a plurality of channels capable of storing production data are prepared, and the designation information registered in the work area The effect data stored in the effect scenario table corresponding to is sequentially referred to and the process corresponding to the effect data to be processed is executed. Together with the completion information stored in the effect scenario table in response to to be processed, and is configured to delete the specified information from the work area.

In the present invention, when the process reaches the end code line of the main table, the scenario deletion process is immediately performed from the work area. The burden can be reduced.
Moreover, since the scenario channel becomes an empty channel as soon as the processing is completed, unnecessary registration is not continued and it can be used immediately for registration of a new scenario.

  According to the present invention, it is possible to realize the efficiency of the presentation control process and the reduction of the required memory capacity in the gaming machine.

1 is a perspective view of a pachinko gaming machine according to an embodiment of the present invention. It is a front view of the board surface of the pachinko game machine of an embodiment. It is a block diagram of a control configuration of the pachinko gaming machine of the embodiment. 3 is a block diagram of a connection configuration of a driver unit according to the first embodiment. FIG. It is a block diagram of an example of an internal configuration of a driver unit according to the first embodiment. It is a flowchart of the main control main process of an embodiment. It is a flowchart of the main control timer interruption process of an embodiment. It is a flowchart of an effect control main process of the embodiment. It is a flowchart of 1 ms timer interruption processing of effect control of an embodiment. It is a flowchart of the command analysis process in presentation control of an embodiment. It is a flowchart of the command corresponding | compatible process in presentation control of embodiment. It is a flowchart of the scenario registration process in presentation control of an embodiment. It is a flowchart of the scenario deletion process in presentation control of an embodiment. It is a flowchart of the scenario update process in presentation control of an embodiment. It is a flowchart of the subscenario update process in presentation control of an embodiment. It is explanatory drawing of scenario registration information, lamp data registration information, and motor data registration information of embodiment. It is explanatory drawing of the sound data registration information of embodiment. It is explanatory drawing of the main scenario table of embodiment. It is explanatory drawing of the sub scenario table of embodiment. It is a flowchart of the LED drive data update process in presentation control of an embodiment. It is explanatory drawing of the registration information of the lamp data of embodiment. It is explanatory drawing of the address table of the lamp data and mask data of embodiment. It is explanatory drawing of the lamp data table and mask data table of embodiment. It is a flowchart of the registration process of the sound of embodiment. It is a flowchart of the setting process of SE of embodiment. It is a flowchart of the setting process of sound control of an embodiment. It is explanatory drawing about the data structure of the information of the sound control of embodiment. It is explanatory drawing about the conversion process of fade-type sound control information. It is explanatory drawing about the usage example of the information of fade type sound control. It is explanatory drawing about the example of control which mutes a predetermined kind of sound with a secondary volume. It is a flowchart of sound reproduction processing of an embodiment. It is explanatory drawing about the volume control according to error generation. It is a flowchart of the registration process of the motor of an embodiment. It is explanatory drawing of the motor operation | movement table of embodiment. It is explanatory drawing of the origin switch of embodiment. It is a flowchart of the motor operation update process of an embodiment. It is a flowchart of the input update process and switch information creation process of an embodiment. It is a flowchart of the process according to the option of the operation system of an embodiment. It is a flowchart of the process according to the option of the operation system of an embodiment. It is a flowchart of the process according to the option of the operation system of an embodiment. It is a flowchart of the process according to the non-operation type option of an embodiment. It is a flowchart of the process according to the non-operation type option of an embodiment. It is explanatory drawing of the motor output data of embodiment. It is a flowchart of motor output processing of an embodiment. It is explanatory drawing of the motor pushing-in operation | movement of embodiment.

Hereinafter, a pachinko gaming machine will be exemplified as an embodiment of a gaming machine according to the present invention, and will be described in the following order.
<1. Pachinko machine structure>
<2. Control configuration of pachinko gaming machine and driver configuration of embodiment>
<3. Processing of main control unit>
<4. Processing of production control unit>
[4-1: Main processing]
[4-2: 1ms timer interrupt processing]
[4-3: Command analysis processing]
[4-4: Scenario registration / deletion processing]
[4-5: Scenario update processing]
[4-6: LED drive data update process]
[4-7: Sound registration processing]
[4-8: Sound reproduction processing]
[4-9: Motor registration process]
[4-10: Motor operation update processing]
[4-11: Motor output processing]
[4-12: Motor push-in operation]
<5. Summary and Modification>

<1. Pachinko machine structure>

First, with reference to FIG. 1 and FIG. 2, the structure of the pachinko gaming machine 1 as an embodiment of the present invention will be schematically described.
FIG. 1 is a front perspective view showing the appearance of a pachinko gaming machine 1 according to the embodiment, and FIG. 2 is a front view of the game board.
The pachinko gaming machine 1 shown in FIGS. 1 and 2 mainly includes a “frame portion” and a “game board portion”.
The “frame portion” includes a front frame 2, an outer frame 4 , a glass door 5, and an operation panel 7 described below. The “game board part” comprises the game board 3 of FIG. In the following description, “frame part” and “frame side” are a general term for the front frame 2, the outer frame 4 , the glass door 5, and the operation panel 7. “Board” and “board side” indicate the game board 3.

As shown in FIG. 1, the pachinko gaming machine 1 has a frame-shaped front frame 2 attached to the front surface of a wooden outer frame 4 so as to be opened and closed. Although not shown, a game board storage frame is formed on the rear surface of the front frame 2, and the game board 3 shown in FIG. 2 is mounted in the game board storage frame. As a result, the gaming area 3a formed on the surface of the gaming board 3 faces the front side of the gaming machine in FIG.
A glass door 5 supporting transparent glass is provided on the front side of the game area 3a, and the game area 3a is exposed to the player on the front side through the transparent glass.

The glass door 5 is attached to the front frame 2 by a shaft support mechanism 6 so as to be opened and closed. Then, by operating a door lock release key cylinder (not shown) provided at a predetermined position of the glass door 5, the lock state of the glass door 5 with respect to the front frame 2 is released, and the glass door 5 can be opened to the front side. ing. Further, the lock state of the front frame 2 with respect to the outer frame 4 can be released by operating the door lock releasing key cylinder.
On the front side of the glass door 5, decorative lamps 20w are provided in various places as light emitting means on the frame side. The decorative lamp 20w performs, for example, a light emitting operation for effects, a light emitting operation for error notification, and a light emitting operation according to an operation state as a light emitting operation by an LED.

An operation panel 7 is provided below the glass door 5. The operation panel 7 can also be opened and closed with respect to the front frame 2 by a shaft support mechanism (not shown).
The operation panel 7 is provided with an upper tray unit 8, a lower tray unit 9, and a firing operation handle 10.

The upper tray unit 8 is formed with an upper tray 8a for storing game balls to be used as bullets. The lower tray unit 9 is formed with a lower tray 9a that stores game balls that cannot be stored in the upper tray 8a.
The upper tray unit 8 is provided with a ball removal button 16 for removing the game balls stored in the upper tray 8a toward the lower tray 9a. The lower tray unit 9 is provided with a ball pulling lever 17 for pulling out the game balls stored in the lower tray 9a below the gaming machine.
Further, the upper tray unit 8 has a ball lending button 14 for requesting a game ball lending device to a game ball lending device (not shown) and a card for requesting the return of the valuable medium inserted in the game ball lending device. A return button 15 is provided.
Further, the upper tray unit 8 is provided with a patrol switch 11, an effect button 12, and a cross key 13. The patrol light switch 11 and the effect button 12 are push buttons that can be operated by turning on the built-in lamp during a predetermined input reception period and can be changed when the built-in lamp is turned on. Further, the cross key 13 is an operator for the player to perform an operation for an operation or an effect setting according to the effect situation.

The firing operation handle 10 is provided on the right end side of the operation panel 7 and is an operator for operating the launching device 32 shown in FIG.
In addition, speakers 25 that sound production effects are provided on both sides of the upper portion of the front frame 2 and in the vicinity of the firing operation handle 10.

  Next, the configuration of the game board 3 will be described with reference to FIG. The game board 3 is mainly composed of a substantially square wooden plywood or resin board. The game board 3 is provided with a ball guide rail 31 for guiding the launched game ball in a ring shape as a board surface partition member. A substantially circular area surrounded by the ball guide rail 31 is a game area 3a. It has become.

A main liquid crystal display device 32M (LCD: Liquid Crystal Display) is provided at a substantially central portion of the game area 3a, and a sub liquid crystal display device 32S is provided on the right side of the main liquid crystal display device 32M.
In the main liquid crystal display device 32M, under the control of the effect control unit 51, which will be described later, for example, three decorative symbols of left, middle and right are displayed in a variable manner on the background image. Various effect images such as a normal effect, a reach effect, and a super reach effect are also displayed. Similarly, the sub liquid crystal display device 32S performs display according to various effects.

A center decoration 35C is provided in the game area 3a so as to surround the display surfaces of the main liquid crystal display device 32M and the sub liquid crystal display device 32S.
The center decoration 35C not only exhibits a decorative effect due to its design, but also has an action of protecting the display surfaces of the main liquid crystal display device 32M and the sub liquid crystal display device 32S from surrounding game balls. Furthermore, the center decoration 35C also functions as a member that enables the right and left shots of the flow path of the game ball depending on the strength or stroke length of the game ball. That is, the flow path of the game ball launched to the upper part of the game area 3a via the ball guide rail 31 flows down either the left game area 3b or the right game area 3c divided by the center decoration 35C. In the case of so-called left hit, the game ball flows down the left game area 3b, and in the case of right hit, the game ball flows down the right game area 3c.

In addition, a lower left decoration 35L is provided below the left game area 3b to exhibit a decorative effect and define a range as the left game area 3b.
Similarly, a lower right decoration 35R is provided below the right game area 3c, which exhibits a decorative effect and defines a range as the left game area 3b.
In the game area 3a (the left game area 3b and the right game area 3c), nails 49 and windmills 47 are provided at various places to form various flow paths for game balls.
Further, a center stage 35S is provided below the main liquid crystal display device 32M, which exhibits a decorative effect and functions as a play area for a game ball.
Although not shown in the drawing, the center ornament 35C is provided with a movable body accessory that provides a visual effect in an appropriate place.

In the vicinity of the upper right edge of the game area 3a, a symbol display unit 33 is provided by a dot display formed by arranging a plurality of LEDs.
In the symbol display unit 33, a first special symbol display unit, a second special symbol display unit, and a normal symbol display unit are formed by a predetermined dot area, and the first special symbol, the second special symbol, and the normal symbol are displayed. Each variation display operation (variation display operation for setting variation start and variation stop as one set) is performed.
The main liquid crystal display device 32M described above variably displays the decorative symbol by the image in time synchronization with the variable display of the first and second special symbols by the symbol display unit 33.

A winning device having an upper start port 41 (first special symbol start port) is provided below the center ornament 35C, and a lower start port 42a (second special symbol start port) is further provided below that. A variable winning device 42 is provided.
Inside the upper start opening 41 and the lower start opening 42a, detection sensors (upper start opening sensor 71 and lower start opening sensor 72 shown in FIG. 3) for detecting the passage of the game ball are formed.

  The upper starting port 41 is a winning port related to the starting condition of the variable display operation of the first special symbol in the symbol display unit 33, and does not have a starting port opening / closing means (means for opening or expanding the starting port). It is a type winning device.

The normal variation winning device 42 having the lower starting port 42a is configured as a winning rate variation type winning device capable of changing the winning rate of the game ball at the starting port by the starting port opening / closing means. That is, it is a so-called electric tulip type winning device including a pair of left and right movable blades (movable members) 42b that can open or enlarge the lower start port 42a.
The lower start opening 42 a of the normal variation winning device 42 is a winning opening relating to the start condition of the variable display operation of the second special symbol in the symbol display unit 33. The winning rate of the lower start port 42a varies depending on the operating state of the movable blade piece 42b. That is, it is configured such that winning is easy when the movable blade piece 42b is open, and winning is difficult or impossible when the movable blade piece 42b is closed.

In addition, a plurality of general winning ports 43 are provided on the left and right sides of the normal variation winning device 42. A detection sensor (general winning opening sensor 74 shown in FIG. 3) for detecting the passage of the game ball is formed inside each general winning opening 42.
In addition, a normal symbol start port 44 including a gate (specific passage region) through which a game ball can pass is provided on the lower side of the right game region 3c. The normal symbol starting port 44 is a winning port related to a normal symbol variation display operation in the symbol display unit 33, and a sensor (gate sensor 73 shown in FIG. 3) for detecting a passing game ball is formed in the normal symbol starting port 44. Has been.

A first special variable winning device 45 (special electric accessory) is provided along the flow path from the normal symbol starting port 44 to the normal variable winning device 42 in the right game area 3c.
The first special variable winning device 45 is configured to close / open the first big winning opening 45a by a retractable opening door 45b. In addition, a sensor for detecting the passage of the game ball to the first big prize opening 45a (the first big prize port sensor 75 in FIG. 3) is formed inside.
The lower right decoration 35R bulges from the surface of the game board 3 around the first grand prize winning opening 45a, and the upper side of the bulged portion and the upper surface of the open door 45b guide downstream of the right flow path 3c. Forming part. Therefore, when the open door 45b is drawn into the board, the game ball that has reached the downstream guide portion can easily enter the first big prize opening 45.

A second special variable winning device 46 (special electric accessory) is provided below the normal variable winning device 42. The second special variable winning device 46 is configured to close / open the second large winning port 46a on the inside by an open door 46b that is pivotally supported at the lower part and can be opened and closed. In addition, a sensor (second big prize port sensor 76 in FIG. 3) for detecting the passage of the game ball to the second big prize port 46a is formed therein.
The second big prize opening 46a is opened by opening the open door 46b. In this state, the game balls that have flowed down the left game area 3b or the right game area 3c will enter the second big prize opening 50 with a high probability.

As described above, the upper starting port 41, the lower starting port 42a, the normal symbol starting port 44, the first large winning port 45a, the second large winning port 46a, and the general winning port 43 are formed in the game area of the board as winning ports. Has been.
In the pachinko gaming machine 1 according to the present embodiment, when a winning is made to a winning port other than the normal symbol starting port 44 among these winning ports, per winning ball set for each winning port. The number of prize balls is paid out from the game ball payout device 55 (see FIG. 3).
For example, the upper start opening 41 and the lower start opening 42a are set to three, the first big winning opening 45a and the second big winning opening 46a are set to 13, the general winning opening 43 is set to 10 and the like.
Note that the game balls that have not won the prize holes are discharged from the game area 3 a through the out port 48.
Here, “winning” means that the winning opening takes the game ball inside, or the game ball passes through the gate. Actually, when a game ball is detected by a sensor (each winning detection switch) formed for each winning opening, it is treated that a “winning” has occurred in that winning opening. The game ball related to the winning is also referred to as “winning ball”.

On the board as described above, the center ornament 35C, the lower left ornament 35L, the lower right ornament 35R, the center stage 35S, the first special variable winning device 45, the second special variable winning device 46, and a movable object not shown in the figure. Although not shown in detail, decorative lamps 20b are provided as light emitting means on the panel side at various places.
The decorative lamp 20b performs, for example, a light emitting operation for production, a light emitting operation for error notification, and a light emitting operation according to an operation state as a light emitting operation by an LED.

<2. Control configuration of pachinko gaming machine and driver configuration of embodiment>

Next, the configuration of the control system of the pachinko gaming machine 1 according to the present embodiment will be described. FIG. 3 is a schematic block diagram of the internal configuration of the pachinko gaming machine 1.
The pachinko gaming machine 1 according to the present embodiment mainly has a main control board 50, an effect control board 51, a liquid crystal control board 52, a payout control board 53, a launch control board 54, and a power supply board 58 as the boards forming the control configuration. Is provided.

The main control board 50 is equipped with a microcomputer or the like, and performs overall control related to the entire game operation of the pachinko gaming machine 1. In the following description, a component of the main control board 50 including a microcomputer mounted on the main control board 50 is referred to as a “main control unit 50”.
The effect control board 51 is equipped with a microcomputer or the like, and receives an effect control command from the main control unit 50 and performs control for executing various effect operations using image display, light emission, and sound output. Hereinafter, the structure of the effect control board 51 including the microcomputer mounted on the effect control board 51 is referred to as an “effect control unit 51”.

The liquid crystal control board 52 is equipped with a microcomputer, a video processor, etc., and receives display control commands from the effect control unit 51 to control display operations by the main liquid crystal display device 32M and the sub liquid crystal display device 32S.
The main liquid crystal control substrate and the sub liquid crystal control substrate may be provided independently as the liquid crystal control substrate for controlling the display operation by the main liquid crystal display device 32M and the sub liquid crystal display device 32S.
The payout control board 53 performs payout control of prize balls by the game ball payout device 55 connected to the pachinko gaming machine 1.
The launch control board 54 controls the launch operation of the game ball by the launch device 56 provided in the player's pachinko gaming machine 1.
The power supply board 58 performs AC / DC conversion and further DC / DC conversion from an external power supply (for example, AC 24 V), and supplies an operation power supply voltage Vcc to each unit. The power supply path is not shown.

First, the main controller 50 and its peripheral circuits will be described.
The main control unit 50 includes a microprocessor incorporating a CPU 100 (hereinafter referred to as “main control CPU 100”), a ROM 101 (hereinafter referred to as “main control ROM 101”), and a RAM 102 (hereinafter referred to as “main control RAM 102”). A microcomputer is configured.
The main control CPU 100 executes various calculations and control processes according to the progress of the game based on the control program.
The main control ROM 101 stores a game operation control program by the main control CPU 100 and various data necessary for game operation control.
The main control RAM 102 is used as a work area used by the main control CPU 100 for various arithmetic processing, and as a buffer area for various input / output data and processing data.
Although not shown, the main control unit 50 includes an interface circuit with each unit, a random number generation circuit that generates random numbers for lottery related to special symbol variation display, a CTC (Counter Timer Circuit) for various time counting, An interrupt controller circuit for giving an interrupt signal to the control CPU 100 is also provided.

As described above, the main control unit 50 receives each winning means in the game area on the board (upper start port 41, lower start port 42a, normal symbol start port 44, first big win port 45a, second big win port 46a, general It is configured to receive a detection signal of a sensor provided at the winning opening 43).
That is, the detection signals of the upper start opening sensor 71, the lower start opening sensor 72, the gate sensor 73, the general winning opening sensor 74, the first large winning opening sensor 75, and the second large winning opening sensor 76 are sent to the main control unit 50. Supplied.
These sensors (71 to 76) are configured by detection switches that detect a game ball that has entered, but specifically, contactless switches such as photoswitches and proximity switches, and contact points such as microswitches. It can consist of switches.

  The main control unit 50 receives the detection signals of the upper start opening sensor 71, the lower start opening sensor 72, the gate sensor 73, the general winning opening sensor 74, the first large winning opening sensor 75, and the second large winning opening sensor 76. Depending on the process. For example, lottery processing, symbol variation control, prize ball payout control, effect control command transmission control, external data transmission processing, and the like are performed.

The main control unit 50 is connected to a normal electric accessory solenoid 77 that opens and closes the movable wing piece 42b of the lower start port 42, and the main control unit 50 transmits a control signal according to the progress of the game to perform normal electric operation. The driving operation of the accessory solenoid 77 is executed, and the opening / closing operation of the movable blade piece 42b is executed.
Further, the main control unit 50 has a first grand prize opening solenoid 78 that opens and closes the opening door 45b of the first big prize opening 45 and a second big prize that opens and closes the opening door 46b of the second big prize opening 46. A mouth solenoid 79 is connected. The main control unit 50 drives and controls the first big prize opening solenoid 78 or the second big prize opening solenoid 79 in accordance with the so-called jackpot situation, and opens the first big prize opening 45 or the second big prize opening 46. Is executed.

  In addition, a symbol display unit 33 is connected to the main control unit 50, and a control signal is transmitted to the symbol display unit 33 to execute various symbol displays (LED OFF / ON / flashing). Thereby, the display operation in the 1st special symbol display part 80 in the symbol display part 33, the 2nd special symbol display part 81, and the normal symbol display part 82 is performed.

  The main control unit 50 is connected to a frame external terminal board 57. The main control unit 50 can transmit information related to game progress to a hall computer (not shown) via the frame external terminal board 57. The information related to the game progress is information such as jackpot winning information, prize ball number information, symbol variation display execution number information, and the like. The hall computer is a management computer that comprehensively manages pachinko hall gaming machines, and is installed outside the gaming machine.

In addition, a payout control board 53 is connected to the main control unit 50. Connected to the payout control board 53 are a launch control board 54 for controlling the launch device 56 and a game ball payout device 55 for paying out game balls.
The main control unit 50 transmits a payout control command (payout control command for designating the number of prize balls) to the payout control board 53. The payout control board 53 controls the game ball payout device 55 in accordance with the control command to cause the game ball to be paid out.
The payout control board 53 can transmit information (payout state signal) regarding the payout operation state to the main control unit 50. The main controller 50 monitors whether or not the game ball payout device 55 is functioning normally based on this payout state signal. Specifically, it is monitored whether or not a problem such as clogged balls or insufficient payout of prize balls has occurred during the prize ball payout operation.

  The main control unit 50 transmits an effect control command including information related to the special symbol variation display to the effect control unit 51. The transmission of the effect control command from the main control unit 50 to the effect control unit 51 is executed by one-way communication. This is to prevent an unauthorized signal due to an illegal act from the outside from being input to the main control unit 50 via the effect control unit 51.

Next, the production control unit 51 and its peripheral circuits will be described.
The effect control unit 51 includes a microprocessor incorporating a CPU 200 (hereinafter referred to as “effect control CPU 200”), a ROM 201 (hereinafter referred to as “effect control ROM 201”), and a RAM 202 (hereinafter referred to as “effect control RAM 202”). A microcomputer is configured.
The effect control CPU 200 performs arithmetic processing for various effect operations and controls each effect means based on the effect control program and the effect control command received from the main control unit 50. In the case of the pachinko gaming machine 1 according to the present embodiment, the effect means is the main liquid crystal display device 32M, the sub liquid crystal display device 32S, the decorative lamps 20w and 20b, the speaker 59, and a movable object that is not shown.
The effect control ROM 201 stores a control program of the effect operation by the effect control CPU 200 and various data necessary for effect operation control.
The effect control RAM 202 is used as a work area used by the effect control CPU 200 for various arithmetic processes, a table data area, a buffer area for various input / output data and processing data, and the like.
Although illustration is omitted, the production control unit 51 gives an interrupt signal to the interface circuit with each unit, a random number generation circuit for generating random numbers for lottery for production, CTC for various time counting, and the production control CPU 200. It also has an interrupt controller circuit.
The main roles of the effect control unit 51 are to receive an effect control command from the main control unit 50, to select an effect based on the effect control command, and to provide an effect control command to the main liquid crystal display device 32M and the sub liquid crystal display device 32S. , Output sound control by the speaker 25, light emission control of the decorative lamps 20w and 20b (LED), operation control of the movable body accessory, and the like.

  The effect control unit 51 transmits an effect control command to the main liquid crystal display device 32M and the sub liquid crystal display device 32S, and the effect control command is sent to the liquid crystal control substrate 52 via the liquid crystal interface substrate 66.

The liquid crystal control board 52 performs display control of the main liquid crystal display device 32M and the sub liquid crystal display device 32S. Although not shown, the liquid crystal control board 52 includes a VDP (Video Display Processor), an image ROM, a VRAM (Video RAM), a liquid crystal control CPU, a liquid crystal control ROM, and a liquid crystal control RAM.
The VDP performs overall control of video output processing such as image development processing and image drawing.
The image ROM stores image data (effect image data) on which the VDP performs image expansion processing.
The VRAM is an image memory area that temporarily stores image data developed by the VDP.
The liquid crystal control CPU outputs control data necessary for the VDP to perform display control.
The liquid crystal control ROM stores a program describing the display control operation procedure of the liquid crystal control CPU and various data necessary for the display control.
The liquid crystal control RAM functions as a work area and a buffer memory.

  With these configurations, the liquid crystal control board 52 generates various image data based on the effect control command from the effect control board 51, and outputs it to the main liquid crystal display device 32M and the sub liquid crystal display device 32S. As a result, various effect images are displayed on the main liquid crystal display device 32M and the sub liquid crystal display device 32S.

The production control unit 51 controls the light production and the sound production. For this reason, a frame driver unit 61, a panel driver unit 62, and a sound source IC (Integrated Circuit) 59 are connected to the effect control unit 51.
The frame driver unit 61 performs light emission driving for the LEDs of the decorative lamp unit 63 on the frame side. Note that the decorative lamp portion 63 is a general view of the decorative lamp 20w provided on the frame side as shown in FIG.
The panel driver unit 62 performs light emission driving for the LEDs of the decorative lamp unit 64 on the panel side. In addition, the decorative lamp part 64 is a general view of the decorative lamp 20b provided on the panel side as shown in FIG.
The movable body accessory motor 65 generally indicates one or more motors that drive one or more movable body accessories formed on the board side. In the case of the present embodiment, the panel driver unit 62 also drives the motor of the movable body accessory motor unit 65. For example, a stepping motor is used as the motor of the movable body accessory motor unit 65.

In the case of the present embodiment, the frame driver unit 61 is a first-system drive signal output unit, and the panel driver unit 62 is a second-system drive signal output unit. Although details will be described later with reference to FIG. 4, the effect control unit 51 (effect control CPU 200) uses the serial data transmission channels ch <b> 1 and ch <b> 2 and uses the drive data for the first and second systems with the effect drive data as serial data. The output means (the frame driver unit 61 and the panel driver unit 62) is supplied.
In this example, the panel driver unit 62 also drives the motor of the movable body accessory motor unit 65 that drives the movable body accessory formed on the panel side. The driver unit that drives the light emission and the driver unit that drives the motor of the movable body accessory motor unit 65 may be provided separately.

As the movable body accessory motor unit 65, for example, a plurality of motors (for example, stepping motors) are provided corresponding to the plurality of accessories.
Each motor has a specified origin position. The origin position is, for example, a position where an accessory does not normally appear on the board surface of FIG.
Each motor is provided with an origin switch 68 so that it can be confirmed on the side of the effect control board 51 whether or not the motor is at the origin position. For example, a photo interrupter is used. The information of the origin switch 68 is configured to be detected by the effect control CPU 200. Details will be described with reference to FIGS.

Further, the effect control unit 51 controls the sound source IC 59 so that the speaker 25 outputs a desired sound. A sound data ROM 69 is connected to the sound source IC 59, and the sound source IC 59 acquires necessary sound data (sound data of a phrase to be reproduced) from the sound data ROM 69 and outputs a sound signal.
The sound source IC 59 mixes phrases of a plurality of channels (a sound channel aCH described later) to obtain a predetermined number (number of channels) of audio signals. As shown in FIG. 1, in the case of this example, since a plurality of speakers 25 are provided, the number of output channels of the sound source IC 59 can be, for example, two channels of Lch and Rch (stereo output). Through the above mixing, phrases of a plurality of channels instructed to be reproduced from the effect control unit 51 can be reproduced simultaneously.
The sound source IC 59 performs sound control for the phrase instructed as a control target in accordance with the instruction from the effect control unit 51. Specifically, the production control unit 51 gives information related to an instruction to give a sound effect such as a volume change instruction or fade-in reproduction / fade-out reproduction to the sound source IC 59, and the sound source IC 59 is designated as a control target according to the information. Controls playback of the phrase that is played.

The sound source IC 59 used in the present embodiment also has a SUB volume setting function and a pan function (left-right pan and up-down pan).
In this case, the sound source IC 59 requests an instruction to output a sound, at least “phrase number”, “primary volume”, “primary volume transition amount”, “secondary volume”, “number of loops”, “SUB0 volume”, “SUB1”. “Volume”, “Left / Right Pan Pot”, “Left / Right Pan Pot Transition Amount”, “Up / Down Pan Pot”, “Up / Down Pan Pot Transition Amount”. In other words, the sound source IC 59 in this case is provided with a register for each of the sound channels aCH that accepts the input of the indicated value for each of these items.
In the present embodiment, the SUB volume is not used. Accordingly, “0” is set in the registers of the “SUB0 volume” and “SUB1 volume” (see step S1202 in FIG. 32 described later).

The output audio signal from the sound source IC 59 is amplified by the amplifier unit 67 and then given to the speaker 25.
In FIG. 3, for convenience of illustration, the number of output channels of the sound source IC 59 is one. However, in reality, the amplifier unit 67 and the speaker 25 are provided with output channels corresponding to, for example, Lch and Rch, respectively, and stereo sound Playback is possible.

  In the above description, the sound source IC 59 is provided separately from the effect control board 51. However, the sound source IC 59 may be provided integrally on the same board as the effect control board 51.

The effect control unit 51 is connected to an operation unit 60 that can be operated by the player, and can receive an operation detection signal from the operation unit 60. The operation unit 60 is the patrol switch 11, the effect button 12, the cross key 13, and the operation detection mechanism described above with reference to FIG.
The effect control unit 51 can perform various effect controls according to the operation detection signal from the operation unit 60.

  The production control unit 51 determines a production pattern by lottery or uniquely from a plurality of types of production patterns prepared in advance based on the production control command sent from the main control unit 50, and performs various productions at necessary timing. Control means. Thereby, the display of the effect image by the main / sub liquid crystal display devices 32M and 32S corresponding to the effect pattern, the sound reproduction from the speaker 25, the lighting and blinking driving of the LEDs in the decoration lamp parts 63 and 64 (decoration lamps 20w and 20b), The operation of the movable body accessory by the motor of the movable body accessory motor unit 65 is realized, and various effect patterns are developed in time series. Thereby, the “production scenario” is realized.

The effect control command defines a function by a 2-byte structure consisting of a 1-byte length mode (MODE) and a 1-byte length event (EVENT).
In order to distinguish between MODE and EVENT, MODE Bit 7 is ON, and EVENT Bit 7 is OFF.
When these pieces of information are transmitted as valid, a strobe signal is output corresponding to each of the mode (MODE) and the event (EVENT). That is, when there is a command to be transmitted, the main control CPU 100 sets and outputs mode (MODE) information for transmitting the command to the effect control unit 51, and the first strobe signal after a predetermined time has elapsed from this setting. Send. Furthermore, event (EVENT) information is set and output after the elapse of a predetermined time from the transmission of the strobe signal, and the second time of the strobe signal is transmitted after the elapse of the predetermined time from this setting.
The strobe signal is controlled by the main control CPU 100 to be in an active state for a predetermined period during which the effect control CPU 200 can reliably receive a command.
The effect control unit 51 (effect control CPU 200) generates an interrupt based on the input of the strobe signal and executes a control program for command reception interrupt processing, and the effect control command is acquired in this interrupt processing. .

Then, the structure of the drive signal output means (the frame driver unit 61 and the panel driver unit 62) of the first system and the second system described above will be described.
FIG. 4 shows the frame driver unit 61 and the board driver unit 62 connected to the effect control unit 51.

In the frame driver unit 61 which is the first-system drive signal output means, n LED drivers 90 are connected in parallel to the serial data output channel ch1 of the effect control CPU 200.
As a signal line of the serial data output channel ch1, a reset signal line for supplying a reset signal RESET, a clock line for supplying a clock signal CLK, a data line for supplying serial data DATA as effect drive data, and an enable signal ENABLE are supplied. An enable signal line is provided. Each of these signal lines is connected so as to supply each signal in parallel to n LED drivers 90 constituting the frame driver unit 61.
In each LED driver 90 of the frame driver unit 61, a device ID used as a slave address by the effect control CPU 200 is set. That is, the identifier of each LED driver 90. For the sake of explanation, the device IDs (slave addresses) of the LED drivers 90 are denoted as w1 to w (n) as illustrated.

In the panel driver unit 62 which is the second-system drive signal output means, m LED drivers 90 are connected in parallel to the serial data output channel ch2 of the effect control CPU 200.
Similarly to channel ch1, the signal line of serial data output channel ch2 is a reset signal line for supplying reset signal RESET, a clock line for supplying clock signal CLK, a data line for supplying serial data DATA as effect drive data, and an enable signal ENABLE. An enable signal line for supplying is provided. Each of these signal lines is connected so as to supply each signal in parallel to m LED drivers 90 constituting the panel driver unit 62.
In each LED driver 90 of the panel driver unit 62, a device ID (identifier of each LED driver 90) used as a slave address by the effect control CPU 200 is set. For the sake of explanation, the device ID (slave address) of each LED driver 90 is represented as b1 to b (m) as shown in the figure.

As each LED driver 90 in the frame driver unit 61 and the panel driver unit 62, for example, “LV5236V (manufactured by Sanyo Semiconductor Co., Ltd.)” which is a 24-channel LED driver can be used, and 24 current output terminals are provided. Therefore, one LED driver 90 can output a maximum of 24 LED drive currents. Specifically, for example, 8 series of R (red) LED drive current outputs, 8 series of G (green) LED drive current outputs, and 8 series of B (blue) LED drive current outputs, and light emission of 8 full-color LEDs. It can be driven. Here, one “series” means one LED connected to one current output terminal, or a group of a plurality of LEDs connected in series or in parallel to one current output terminal. pointing.
The number n of LED drivers 90 in the frame driver unit 61 is determined by the number of LED series arranged on the frame side (the number of series of decorative lamps 20w). Therefore, n may be 1 or may be 2 or more. The frame driver unit 61 has one or a plurality of LED drivers 90.
Further, the number m of LED drivers 90 in the panel driver unit 62 is determined by the number of LED series (the number of series of decorative lamps 20b) arranged on the panel side. Accordingly, m may be 1 or may be 2 or more. The panel driver unit 62 has one or a plurality of LED drivers 90.

FIG. 5A shows a schematic configuration example of a main part of the LED driver 90.
The LED driver 90 includes a serial bus interface 91, an address setting unit 92, a data buffer / PWM controller 93, a D / A converter 94, and drive current source circuits 95-1 to 95-24.
The drive current source circuits 95-1 to 95-24 are current sources that perform the 24 series drive current outputs from the output terminals 96-1 to 96-24, respectively.

The LED driver 90 receives an enable signal ENABLE, a clock signal CLK, and serial data DATA from the effect control CPU 200 with respect to the serial bus interface 91. The serial bus interface 91 takes in the serial data DATA at the timing of the clock signal CLK during the period specified by the enable signal ENABLE. The serial bus interface 91 converts the captured serial data into parallel data and transfers the parallel data to the data buffer / PWM controller 93.
The effect control CPU 200 designates a slave address and transmits LED drive data.
The data buffer / PWM controller 93 performs slave address confirmation for the parallel data transferred from the serial bus interface 91. When it is confirmed that the slave address included in the parallel data matches the own slave address (either w1 to w (n) or b1 to b (m)) set in the address setting unit 92 The LED drive data included in the parallel data is stored as valid data in a designated register.

When the data buffer / PWM controller 93 fetches each series of LED drive data, the data buffer / PWM controller 93 sets the value corresponding to the luminance information (gradation value) indicated by the LED drive data as the 24 series drive control values as D / A. Output to the converter 94.
The D / A converter 94 converts a value corresponding to the luminance information into an analog signal, which is used as a control signal to each of the current source circuits 95-1 to 95-24.

24 series of LEDs 120 are connected to all (or part of) the output terminals 96-1 to 96-24. Although the drawing shows a simplified state in which one LED 120 is connected to one series of output terminals 96, a configuration in which a plurality of LEDs are connected to one series of output terminals 96 (for example, series connection) is also possible. Of course this is possible.
In each series (output terminals 96-1 to 96-24), the power supply voltage Vcc is applied to the series connection of the LED 120 and the resistor R. Current is supplied to each series of LEDs 120 by the current source circuits 95-1 to 95-24 to emit light.
That is, each of the current source circuits 95-1 to 95-24 operates so that a drive current having a current amount corresponding to the signal supplied from the D / A converter 94 flows through the corresponding series of LEDs 120.

Specifically, such LED drive control is described for one series. The data buffer / PWM controller 93 converts the digital data string corresponding to the pulse duty corresponding to the gradation value of the series to the D / A converter 94. The D / A converter 94 converts the digital data string into a pulse signal as an analog signal and supplies the pulse signal to the current source circuit 95 of the series. The output of the current source circuit 95 is controlled by the H / L of the pulse signal, and for example, outputs currents of 0 mA and 5 mA. For example, in such an operation, a driving current having an average current value corresponding to the gradation value flows to the LED 120 as a result.
In this embodiment, the current value is set to, for example, 0 mA and 5 mA by the PWM driving method, and gradation control is performed (integrally) in the time axis direction. Needless to say, the current value may actually be changed according to the gradation. Regardless of duty control or level control, appropriate gradation expression can be realized by setting the average current value per unit time to a level corresponding to the gradation.

In the case of the present embodiment, a part of the LED drivers 90 in the panel driver unit 62 are connected to each motor of the movable body accessory motor portion 65 that drives the movable body accessory. FIG. 5B shows an example in which, for example, the stepping motor 121 is connected to all (or a part) of the output terminals 96-1 to 96-24 of a certain LED driver 90. 5B shows only the portions of the output terminals 96-1 to 96-24, but the internal configuration of the LED driver 90 is the same as that of FIG. 5A.
For example, when the stepping motor 121 is a four-phase driving motor, the output terminals 96-1 to 96-4 are connected so that an excitation current for one stepping motor 121 flows. Similarly, output terminals 96-5 to 96-8, output terminals 96-9 to 96-12, output terminals 96-13 to 96-16, output terminals 96-17 to 96-20, and output terminals 96-21 to 96. -24 are connected so that an exciting current flows through one stepping motor 121. In this case, a maximum of six stepping motors 121 can be driven by one LED driver 90.
The LED driver 90 is a circuit that outputs a current instructed by a given command (serial data) from the output terminals 96-1 to 96-24, and thus a driver for a physically movable body driving device such as a stepping motor or a solenoid. Can also be used. Therefore, some LED drivers 90 are used as drivers for the stepping motor 121 as shown in FIG. 5B. The operation of the movable body accessory is finely set according to the production scenario, and the production control unit 51 controls the driving direction, the driving amount, and the like accordingly. The movable body is operated using the LED driver 90 in the panel driver unit 62. By driving the accessory, the movable object accessory can be controlled by serial data together with each decoration lamp (LED 20b) of the decoration lamp unit 64, and the control processing and configuration can be made efficient.
In one LED driver 90, a method may be adopted in which some output terminals are used for LED driving and other part of the output terminals are used for driving a stepping motor, a solenoid, or the like.

As described above, each LED driver 90 is driven so that each LED 120 emits light with a designated luminance in accordance with the serial data DATA received from the effect control CPU 200. Alternatively, a part of the LED driver 90 drives the stepping motor 121 according to the serial data DATA.
Each of the first and second system drive signal output means (frame driver unit 61, board driver unit 62) includes a plurality of LED drivers 90 each outputting a drive signal to one or a plurality of effect means, The serial data from the effect control unit 51 is transmitted in parallel to each LED driver 90 in one system. Each LED driver 90 acquires effect drive data (serial data) including its own ID (slave address).

<3. Processing of main control unit>

Hereinafter, control processing according to the present embodiment will be described. First, main processing by the main control unit (main control board) 50 will be described here.
FIG. 6 is a flowchart showing main processing of the main control unit 50. The main process starts when the power is turned on without operating the initialization switch (not shown), such as when recovering from a power failure, and when the initialization switch is turned on. May turn on. In any case, when the pachinko gaming machine 1 is powered on, the power board 58 supplies a voltage to each control board. In this case, the main control unit 50 (main control CPU 100) starts the main process shown in FIG.

In the main control side main process, the main control CPU 100 first executes a necessary initial setting process before starting the game operation in step S11. For example, it first sets itself to an interrupt disabled state, sets it to a predetermined interrupt mode (interrupt mode 2), and initializes register values in the CPU including each part of the microcomputer.
Next, in step S12, the main control CPU 100 determines the state (ON, OFF) of a RAM clear signal that is an output signal of a RAM clear switch that is input via an input port (not shown). The RAM clear signal is a signal that determines whether or not to initialize all the areas of the RAM. The RAM clear signal usually has a value corresponding to the ON / OFF state of the initialization switch operated by the store clerk of the pachinko parlor.

When the RAM clear signal is in the ON state, the main control CPU 100 advances the process from step S12 to S16, and performs zero clear of the entire area of the RAM. Therefore, the value of the backup flag set at the time of power-off becomes zero together with other checksum values.
Subsequently, in step S17, the main control CPU 100 transmits a “RAM clear display command” for notifying that the RAM area has been cleared to zero to each control board as an initialization command. In step S18, for example, 30 seconds is stored in the RAM clear notification timer as a time for notifying that the RAM has been cleared.

Next, in step S19, the main control CPU 100 initializes a CTC that outputs an interrupt signal for starting a timer interrupt operation, and sets the CPU to an interrupt enabled state.
Thereafter, as the processing of steps S20, S21, and S22, the interrupt disabled state and the interrupt enabled state are repeated until an interrupt occurs, and various random number update processes are executed during that time. In the various random number update processing in step S21, random numbers used for changing initial values (start values) of various random numbers used for special symbol fluctuation display and normal symbol fluctuation display, and fluctuations used for selection of fluctuation patterns. Update pattern random numbers.
The various random numbers used for the special symbol variation display and the normal symbol variation display are, for example, random numbers related to jackpot lottery circulating through a predetermined numerical range by increment processing (special symbol determination random numbers used for symbol lottery). Or a random number related to a lottery per assistance (a random number for judging per assistance used in winning lottery per assistance). The random numbers used for changing the initial value include an initial value random number for special symbol determination, an initial value random number for auxiliary hit determination, and the like.

The main control RAM 102 has a special symbol determination random number counter initial value generation counter and a special symbol determination random number counter as various random number counters used for symbol lottery related to big hit lottery, auxiliary lottery, or variation pattern lottery. There are provided a counter for generating an initial value per auxiliary sub-counting counter, a random counter for sub-peripheral determining, a random number 1 counter for variation pattern, a random number 2 counter for variation pattern, and the like. These counters serve as random number generation means for generating random numbers in software.
In the various random number update processing in step S21, two initial value generation counters for generating initial values of the special symbol determination random number counter and the auxiliary hit determination random number counter, a variation pattern random number 1 counter, and a variation pattern random number 2 The counter is updated to generate the above various soft random numbers. For example, if the numerical value range that can be taken as the variation pattern random number 1 counter is 0 to 238, a value is acquired from the count value storage area for generating the value of the variation pattern random number 1 in the main control RAM 102, and the acquired value is changed to the acquired value. After adding 1, it is stored in the original count value storage area. At this time, if the result of adding 1 to the acquired value is 239, 0 is stored in the original random number counter storage area. Other initial value generation random number counters are updated in the same manner. The CPU 201 is configured to repeatedly execute various random number update processes except during a timer interrupt process that is executed intermittently.

The above describes the case where it is determined in step S12 that the RAM clear switch is ON. Next, the case where the RAM clear switch is OFF will be described. For example, at the time of recovery from a power failure state, the initialization switch (RAM clear signal) is in an OFF state. In such a case, the main control CPU 100 advances the process from step S12 to S13, and determines the backup flag value. The backup flag is set to the ON state when the power is shut off, and is reset to the OFF state in the first timer interrupt processing after the power is restored.
Therefore, when the power is turned on or when recovering from a power failure, the backup flag should normally be in the ON state. However, the backup flag is reset (OFF) if the predetermined processing is not completed before the power is cut off for some reason. Therefore, when the backup flag is in the OFF state, the main control CPU 100 advances the process from step S13 to S16, and returns the operation of the gaming machine to the initial state.

On the other hand, if the backup flag is in the ON state, the main control CPU 100 advances the process from step S13 to S14, and executes a checksum calculation for calculating a checksum value. Here, the checksum operation is an 8-bit addition operation for the work area of the main control RAM 102.
When the checksum value is calculated, the calculation result is compared with the stored value at the SUM address in the main control RAM 102. This SUM address stores a checksum value obtained by the same checksum calculation when the power is shut off. The stored calculation result is maintained by the backup power source together with other data of the main control RAM 102. Therefore, originally, both should match according to the determination in step S14.
However, there may be a case where the checksum operation cannot be executed when the power is turned off, or even if it can be executed, the data in the work area is damaged after the checksum operation of the main process is executed. In such a case, the determination result in step S14 is inconsistent.
If data corruption is detected due to the discrepancy of the determination results, the main control CPU 100 proceeds from step S14 to step S16, executes RAM clear processing, and returns the operating state of the gaming machine to the initial state.

If the checksum value obtained by the checksum calculation in step S14 matches the stored value at the SUM address, the main control CPU 100 proceeds to step S15, and returns the stack pointer before power-off based on the backup data. A game restoration process necessary for starting a game from the processing state at the time of power-off is executed.
When the game recovery process at step S15 is completed, the process proceeds to the process at step S19, the CTC is initialized and the CPU is set in the interrupt enabled state, and thereafter, the interrupt disabled state and the interrupt enabled state are generated until an interrupt occurs. In the meantime, various random number update processes described above are executed (steps S20 to S22).

  Next, timer interrupt processing of the main control CPU 100 will be described. FIG. 7 shows the timer interrupt process of the main control CPU 100. This main control timer interrupt process is activated by interruption every predetermined time (about 4 ms) from the CTC, and is interrupted and executed during execution of the main process described above.

  When a timer interrupt occurs, the main control CPU 100 saves the contents of the register in the stack area, and then first performs a power supply abnormality check process for monitoring the power supply state from the power supply board 58 in step S51 of FIG. In this power abnormality check process, it is mainly monitored whether the power is normally supplied. Here, for example, when an abnormality such as a power interruption occurs, a backup process is performed in which predetermined game information at the time of power interruption is stored in the RAM so that the game can be restored without any trouble when the power is restored.

  In step S52, the main control CPU 100 performs a timer management process for managing a timer used for gaming operation control. Timer values of various timers (for example, special symbol accessory operation timer) used for game operation control of the pachinko gaming machine 1 are managed (updated) by this processing.

In step S53, the main control CPU 100 performs input management processing. In this input management process, information detected by various sensors provided in the pachinko gaming machine 1 is stored in the winning counter. Here, the detection information by the various sensors includes, for example, an upper start opening sensor 71, a lower start opening sensor 72, a gate sensor (normal pattern start opening sensor) 73, a first large winning opening sensor 75, and a second second winning opening sensor. 76, ON / OFF information (winning detection information) of a switch signal output from a winning detection switch such as the general winning opening sensor 74.
Through the processing in step S53, it is monitored for each interrupt whether or not a winning is detected (winning has occurred) at each winning opening. The “winning counter” is a counter provided corresponding to each winning opening and counting the number of game balls (winning balls) won. In the present embodiment, in a predetermined area of the main control RAM 102, an upper start opening winning counter for the upper starting opening 41, a lower starting opening winning counter for the lower starting opening 42a, a normal symbol starting opening winning counter for the gate 44, A first grand prize winning counter for the first grand prize winning opening 45a, a second big winning prize winning prize counter for the second big winning prize opening 46a, a general winning prize winning counter for the general winning opening 43, and the like are provided. .
Further, in this input management process, it is also monitored whether or not there is an illegal prize based on whether or not the detection information from the prize detection switch has won a prize during a period in which the prize should be allowed. For example, when the first and second big prize opening sensors 75 and 76 detect a game ball even though the big hit game is not being played, the prize detection information is invalidated by invalidating the prize detection information. In order to notify the outside of the fact, a predetermined error process is performed in an error management process in step S55 described later.

  In step S54, the main control CPU 100 performs a timer interrupt random number management process for periodically updating the random numbers related to each variation display. In this periodic random number update process, a special symbol determination random number or auxiliary per-subject determination random number is updated (+1 is added for each interrupt), and a process for changing the start value of the random number counter is performed each time the random number counter makes a round. For example, the value of the special symbol judgment random number counter is updated (added by +1) within a predetermined range, and the special symbol judgment random number counter initial value generation counter value is read each time the special symbol judgment random number counter makes one round. The value of the generation counter is stored in the special symbol determination random number counter. As a result, the start value of the special symbol determination random number counter is changed according to the value of the generation counter, so that the count value of the special symbol determination random number counter is random while the update cycle is constant.

In step S55, the main control CPU 100 performs an error management process for monitoring whether there is an abnormality in the gaming operation state. In this error management process, as abnormalities in the game operation state, these operational abnormalities (errors) occur, for example, by monitoring whether or not a break has occurred between the boards or whether or not there has been an illegal winning. If so, predetermined error processing corresponding to the error is performed.
As the error processing, for example, the progress of a predetermined game operation (for example, a game ball payout operation or a game ball launch operation) is stopped, or an error notification command is transmitted to the effect control unit 51 to generate the effect means. To notify that an error has occurred.

In step S56, the main control CPU 100 performs prize ball management processing. In this prize ball management process, the data stored in the input management process in step S53 is grasped, the above-mentioned prize counter is confirmed, and if there is a prize, a payout control command for designating the number of prize balls is issued. Transmit to the substrate 53.
Upon receiving this payout control command, the payout control board 53 controls the game ball payout device 55 to perform a payout operation for the designated number of prize balls. Thereby, the number of winning balls corresponding to each winning opening is paid out. The number of winning balls corresponding to a winning opening is the predetermined number of winning balls per winning ball set for each winning opening × the number of winning balls corresponding to the value of the winning counter.

  In step S57, the main control CPU 100 performs normal symbol management processing. In this normal symbol management process, a lottery per auxiliary in the normal symbol variation display is performed, and based on the lottery result, the variation pattern of the normal symbol and the stop display mode of the normal symbol are determined, or the blinking is repeated every predetermined time. Create symbol data (data for LED blinking display during normal symbol variation), or create data for stop display (data for LED blinking display during normal symbol stop display) if normal symbol is not varying Or

In step S <b> 58, the main control CPU 100 performs a normal electric accessory management process. In this ordinary electric accessory management process, generation of an excitation signal for solenoid control for the ordinary electric accessory solenoid 77 and its data (solenoid control data) based on the lottery result of the auxiliary symbol lottery in the normal symbol management process in step S57. Set up. Based on the data set here, an excitation signal is output to the ordinary electric utility solenoid 77 in a solenoid management process in step S64 described later, whereby the operation of the movable blade piece 42b is controlled.
In step S59, the main control CPU 100 performs special symbol management processing. In this special symbol management process, the big hit lottery in the special symbol variation display is mainly performed, and based on the lottery result, the variation pattern of the special symbol (look-ahead variation pattern, variation pattern at the start of variation), the special stop symbol, etc. decide.
In step S60, the main control CPU 100 performs a special electric accessory management process. In this special electric utility management process, when the big hit lottery result is “big hit” or “small win”, a setting process necessary to execute and control the hit game corresponding to the win is performed.

In step S61, the main control CPU 100 performs a right-handed notification information management process. In this right-handed notification information management process, for example, a right-handed instruction is given in situations where right-handed is advantageous, such as when the first and second winning holes 45a and 46a are opened or when the movable blade piece 42b is driven. A process for making a “launch position guidance effect (right-handed notification effect)” for performing the notification appears. Specifically, the right-handed instruction is an effect operation instructing the player to aim at the right game area 3c. For example, an image prompting the player to “right-hand” is displayed on the main liquid crystal display device 32M. Or a right-handed message sound is generated from the speaker 25.
When a right-handed notification effect is performed, in this right-handed notification information management process, a “right-handed instruction command” instructing execution of a right-handed notification effect is transmitted to the effect control unit 51 as an effect control command. Then, the production control unit 51 performs execution control of right-handed notification using an image or sound.
In step S62, the main control CPU 100 performs LED management processing. This LED management process is a process of outputting display data for normal symbol display and first and second special symbol displays to the symbol display unit 33. By this processing, normal symbol and special symbol change display and stop display are performed. The normal symbol display data created in the normal symbol management process in step S57 and the special symbol display data created in the special symbol display data update process in the special symbol management process in step S59 are the LED management process. Is output.

In step S63, the main control CPU 100 performs an external terminal management process. In this external terminal management process, the operation state information of the pachinko gaming machine 1 is output to an external device such as a hall computer or an island lamp through the frame external terminal board 57. The operating state information includes that a big hit game has occurred (condition device has been activated), that a small hit game has occurred, that a symbol variation display has been executed (a special symbol variation display game has started or ended) , Information such as winning information (information indicating that the player has won a winning opening or a big winning opening and information on the number of winning balls) is included.
In step S64, the main control CPU 100 performs solenoid management processing. In this solenoid management process, an excitation signal output process for the ordinary electric accessory solenoid 77 based on the solenoid control data created in the ordinary electric accessory management process in step S58, and a special electric accessory management process in step S60. Excitation signal output processing for the first and second big prize opening solenoids 78 and 79 based on the solenoid control data is performed. Thereby, the movable wing piece 42b and the open doors 45b and 46b operate in a predetermined pattern, and the lower start port 42a and the big winning ports 45a and 46b are opened and closed.

After completing the above steps S51 to S64, the main control CPU 100 restores the saved register contents and sets the interrupt permitted state in step S65. As a result, the timer interrupt process is ended, the process returns to the main process on the main control side in FIG. 6 before the interruption, and the main control main process is performed until the next timer interrupt occurs.

<4. Processing of production control unit>
[4-1: Main processing]

Then, the process of the production | presentation control part 51 is demonstrated. As the processing of the effect control unit 51, mainly processing performed every 16 ms on the main loop (hereinafter also referred to as “16 ms processing”) and interrupt processing performed every 1 ms (hereinafter referred to as “1 ms timer interrupt processing”). Say).
First, main processing including 16 ms processing will be described here.
FIG. 8 shows the main process of the effect control unit 51. The effect control unit 51 (effect control CPU 200) starts the main process of FIG. 8 when the gaming machine body is powered on.
In this main process, the effect control CPU 200 first performs a necessary initial setting process before starting the game operation in step S101. For example, as an initial setting process, command reception interrupt setting, movable object starting point return processing, CTC initial setting, timer interrupt permission, initial setting of CPU internal register values including each part of the microcomputer, and the like are performed.

When the initial setting process in step S101 is completed, the processes in steps S102 to S117 are repeated as a process during normal operation.
In other words, in this example, the effect control CPU 200 performs the ID check in step S102 and the random number update in step S117 every loop, and performs the processing of steps S105 to S116 (16 ms processing) every 16 ms.
In the ID check in step S102, the effect control CPU 200 confirms the ID of itself or each connected part set on the system. If an ID abnormality is detected for some reason, system stop processing is performed as step S103.
In normal times when there is no problem with the ID, the effect control CPU 200 performs the processing of step S104 and subsequent steps. That is, the effect control CPU 200 determines whether or not the value of the interrupt counter for determining whether to execute the 16 ms process is greater than “15”. This interrupt counter is a counter that is incremented in step S207 of the 1 ms timer interrupt process described later. Therefore, when the value of the interrupt counter is larger than “15”, it means that the processing timing is 16 ms.

When the value of the interrupt counter is “15” or less, the production control CPU 200 proceeds from step S104 to S117, performs the production soft random number update process, finishes one main process, and again performs the process from step S102. I do.
On the other hand, if the value of the interrupt counter is equal to or greater than “16”, the effect control CPU 200 executes the processes of steps S105 to S116, and then updates the effect soft random number in step S117 to perform one main process. The process from step S102 is performed again.

Thus, every 16 ms counted by the interrupt counter, the effect control CPU 200 performs the 16 ms processing from step S105.
In that case, first, in step S105, the interrupt counter is reset to zero. Thereafter, the counting up to the next 16 ms processing is performed again.

In step S106, the effect control CPU 200 performs error processing. The error processing includes error processing timer processing during a RAM clear error, an accessory error, a right-handed error, etc., scenario registration processing for error notification when various errors occur, error scenario after error notification Clearing processing will be performed.
In particular, in the case of the present embodiment, in step S106, a volume MAX error flag setting process corresponding to a predetermined error detection is also performed. The volume MAX error means an error for which the volume of a sound (error sound) output in response to the occurrence should be set to MAX. When a volume MAX error is detected, that is, when an error sound is to be output by MAX, for example, 0x5A is set as a volume MAX error flag, and when a volume MAX error is not detected, for example, 0x00 is set as a volume MAX error flag. Set.

  Next, in step S107, the effect control CPU 200 performs a demo process. In this demonstration process, processing such as scenario registration and command set for playback sound control, demonstration movie execution, and accessory origin correction are performed. In the customer waiting state or the like, the demonstration movie display is executed by executing the scenario set in the demonstration process.

  In step S108, the effect control CPU 200 performs command analysis processing. In this command analysis process, the effect control CPU 200 monitors whether or not the effect control command supplied from the main control unit 50 is stored in the command reception buffer, and reads out this command if the effect control command is stored. . Then, an effect control process corresponding to the read effect control command is performed. Details will be described later with reference to FIGS.

  In step S109, the effect control CPU 200 performs input detection processing. In this input detection process, an input is detected by operating the operation elements (the patrol switch 11, the effect button 12, and the cross key 13) of the operation unit 60. When an input is detected, a process corresponding to the operation is performed.

  In step S110, effect control CPU200 performs a scenario update process. In this process, the main scenario and subscenario are updated. At that time, lighting pattern registration of the decorative lamp units 64 and 65, registration of sound to be reproduced, registration of motor operation for driving the movable body accessory, and the like are also performed. Details will be described later with reference to FIGS.

In step S111, the effect control CPU 200 performs sound reproduction processing. The effect control CPU 200 outputs data such as a phrase number and volume to the sound source IC 59 in accordance with the sound data registered for each sound channel in the work based on the scenario data. Thereby, the reproduction output of the sound effect, music / sound, etc. from the speaker 25 is performed.
This sound reproduction process will be described later with reference to FIG.

  In step S112, the effect control CPU 200 performs an accessory error process. Here, a position error determination such as a return of the origin of the movable object is not performed.

  In step S113, the effect control CPU 200 updates the LED drive data. Here, processing for creating LED output data (driving data) is performed based on the lamp data registered as a lamp channel in the workpiece based on the scenario data. Details will be described later with reference to FIG. The LED output data is output to each LED driver 90 at a predetermined timing in the 1 ms timer interrupt process.

In step S114, the effect control CPU 200 performs checksum calculation and storage for the work area of the effect control RAM 202, and in step S115, stores the backup data.
In step S116, the scenario update counter is reset to zero. The scenario update counter is a counter that is incremented by a 1 ms timer interrupt process described later.

The 16 ms processing as described above is performed every 16 ms in the main loop processing of FIG.

[4-2: 1ms timer interrupt processing]

Next, the 1 ms timer interrupt process will be described with reference to FIG. The effect control CPU 200 executes the 1 ms timer interrupt process of FIG. 9 in response to an interrupt request generated every 1 ms by the time count.
In this 1 ms timer interrupt process, first, in step S201, it is determined whether or not a checksum is being calculated according to a test command from the main control CPU 100. If the checksum is not being calculated, the effect control CPU 200 proceeds to the input process in step S202.

The input process in step S202 is a process for every 1 ms for performing input detection by operating the operator together with the input detection process in step S109 of FIG. For example, in this input process, when an edge is detected in the signal waveform of the operation detection signal of the operation element, the input counter is reset, and thereafter, the input counter is counted up during a period in which no edge occurs. In the 1 ms timer interrupt process, input information (H or L of the input signal waveform) is detected, and the input counter is reset or incremented depending on the presence or absence of an edge. In step S109 in the main loop process (16 ms process), when the input counter value is 16 or more and the input information has changed from the previous time, the input change is recognized.
Such input processing (S202) and input detection processing (S109) can prevent erroneous input recognition due to noise chattering. In addition, since an input counter is used and, in this embodiment, for example, a 16-bit counter can be used to count up to 65535 ms (about 65 seconds), so-called long press can be detected.

In step S203, the effect control CPU 200 performs a motor operation update process. In this case, the effect control CPU 200 performs a process of creating motor drive data based on the motor data registered as a motor channel in the work (motor data registration information described in FIG. 16C) based on the scenario data. This is motor drive data output to the LED driver of the panel driver unit 62 in order to drive and control each motor of the movable body accessory motor unit 65. In the present embodiment, the LED drive data is updated every 16 ms in step S113, while the motor data is updated every 1 ms.
The motor operation update process will be described later with reference to FIGS.
In step S204, the effect control CPU 200 outputs motor drive data. As described above, the stepping motor 121 and the like of the movable body accessory motor unit 65 are connected to some LED drivers 90 of the panel driver unit 62. In step S204, serial data as drive data for the stepping motor 121 is output to a predetermined LED driver 90 (the LED driver 90 that drives the stepping motor 121) of the panel driver unit 62.
The motor output process will be described later with reference to FIG.

In step S205, the effect control CPU 200 executes each process according to the value of the interrupt counter. The interrupt counter is reset to zero in step S105 of the 16 ms process described above and incremented in step S207 of the 1 ms timer interrupt process. Therefore, when step S205 is executed in the 1 ms timer interrupt process, the value of the interrupt counter is 0-15.
According to the interrupt counter values 0 to 15, the process of step S205 is defined as case 0 to case 15. For example, in the present embodiment, in case 0, a WDT (watchdog timer) clear signal ON and an initialization process of the LED driver 90 are performed. In cases 1 to 3, the LED driver 90 is initialized. In case 8, the WDT clear signal is turned OFF. In cases 12 to 15, LED drive data is output to the LED driver 90.
The initialization of the LED driver 90 is a process of outputting a default value to a register that is not used in the LED driver 90. This initialization and LED drive data output are performed for a few LED drivers 90 in one 1 ms timer interrupt process.

In step S206, the effect control CPU 200 outputs an effect control command to the liquid crystal control board 52. For example, one command (2 bytes) is transmitted in one 1 ms timer interrupt process. That is, a 2-byte effect control command as a mode and an event is transmitted.
Thereafter, the effect control CPU 200 increments the interrupt counter in step S207, and increments the scenario update counter in step S208. If the value of the scenario update counter is less than 100, the 1 ms timer interrupt process ends.
Since the scenario update counter is reset to zero in step S116 of the 16 ms process as described above, the scenario update counter value does not normally exceed 100. The value of 100 or more is a case where the 16 ms process is not executed due to a calculation abnormality, a process response abnormality or the like, or the progress of a certain process in the 16 ms process is stopped. In such a case, an infinite loop is entered, and the time-up process is performed by WDT.

When it is determined that the checksum is being calculated in step S201 when entering the 1 ms timer interrupt process, the effect control CPU 200 advances the process to step S210 and clears the WDT. In step S211, an effect control command is transmitted to the liquid crystal control board 52. In step S212, the interrupt counter is incremented and the 1 ms timer interrupt process is completed.

[4-3: Command analysis processing]

Next, the command analysis processing performed in step S108 of FIG. 8 as 16 ms processing will be described with reference to FIGS. The effect control CPU 200 monitors whether or not the effect control command supplied from the main control unit 50 is stored in the command reception buffer as the command analysis processing in step S108, and if the effect control command is stored, this command Is read. As this specific process, the processes of steps S301 to S308 in FIG. 10 are performed.

In the effect control unit 51, a command reception buffer that captures the effect control command transmitted from the main control unit 50 is prepared in the effect control RAM 202, for example. In step S301 in FIG. 10, the effect control CPU 200 first checks the read pointer indicating the read address of the command reception buffer and the write pointer indicating the write address.
The light pointer is updated in response to the command reception, and the received effect control command is stored in the address indicated by the light pointer accordingly. The read pointer is updated when reading from the command reception buffer is performed (step S302). Therefore, if the read pointer is not the write pointer, the effect control command that has not been read is stored in the command reception buffer. Therefore, if the read pointer is not the write pointer, the process goes to step S302, and the effect control CPU 200 loads 1-byte command data from the address indicated by the read pointer in the command reception buffer. In this case, the read pointer is incremented for the next reading (loading).

As described above, one presentation control command is formed of two bytes, one byte as a mode and one byte as an event. In step S303, the effect control CPU 200 confirms whether the loaded 1-byte command data is a mode or an event. This confirmation is performed by the value of Bit 7 out of 8 bits (Bit 0 to Bit 7).
If it is the mode, the process proceeds to step S304 as a process for receiving the upper data of the command, and the read command data is saved in the register “command HI byte”. Also, the “command LO byte” register is cleared. Then, the process returns to step S301.
Even if the read pointer is not equal to the write pointer, the effect control command that has not yet been read is stored in the command reception buffer, and thus the process proceeds to step S302, where the effect control CPU 200 uses the read pointer in the command reception buffer. Load 1 byte of command data from the indicated address. In addition, the read pointer is incremented.
If the read command is an event, the process proceeds from step S303 to S305 as processing for receiving lower-order data of the command, and the read command data is saved in the register “command LO byte”.

The command data of the mode and the event is saved in the registers “command HI byte” and “command LO byte”, so that the effect control CPU 200 takes in one command.
Therefore, the effect control CPU 200 performs processing according to the fetched command in step S306. A specific example will be described later with reference to FIG.

  The read pointer = write pointer is when the effect control command that has not yet been captured by the effect control CPU 200 does not exist in the command reception buffer. Therefore, since new acquisition is unnecessary, the process proceeds to step S307. In this case, it is confirmed whether 100 ms has elapsed while waiting for a symbol command. If such a situation does not occur, the command analysis processing of FIG. 10 is finished. On the other hand, if 100 ms has elapsed while waiting for a symbol command, symbol fluctuation processing due to a missing command is performed in step S308.

An example of the command response process in step S306 will be described with reference to FIG.
FIG. 11A shows basic processing as command response processing. In response to the reception of the 2-byte effect control command, the effect control CPU 200 first checks in step S321 of FIG. 11A whether or not it is currently in the test mode. If it is in the test mode, all the production scenarios are cleared, the sound output is stopped, and the LEDs in the decorative lamp units 63 and 64 are turned off in step S322. In step S323, the test mode ends.
These processes are not performed unless in the test mode.
Then, the effect control CPU 200 performs a process for the acquired effect control command as step S330.

  As the effect control command, for example, a special symbol variation pattern designation command, a special symbol designation command, a holding ball subtraction command, a holding ball addition command, an error display designation command, a jackpot start designation command, etc. are variously set. In step S330, the effect control CPU 200 performs a process specified by the program in response to the received command. Here, in FIG. 11B, FIG. 11C, FIG. 11D, and FIG. 11E, specific processing is exemplified by giving four effect control commands.

FIG. 11B shows a process S330a when a variation pattern command is fetched as the command process in step S330.
In this case, the effect control CPU 200 performs a process of setting a symbol command waiting state in step S331. This is because the effect control CPU 200 controls the variation display of the symbols by sequentially receiving the variation pattern command and the symbol commands.
FIG. 11C shows a process S330b when a symbol command is fetched as the command process in step S330.
In this case, the effect control CPU 200 first confirms whether or not the variation pattern command has been received in step S332. If it has not been received, the process ends.
If a variation pattern command has already been received when the symbol command is received, the process proceeds to step S333, and first, scenario registration for the operation of correcting the accessory origin is performed. In step S334, variation start processing is performed. In this variation start process, the scenario setting of the symbol variation operation according to the variation pattern command and symbol command, the presence / absence of execution of the announcement effect that should appear during the variation display, and its type are determined by lottery. Set up. Furthermore, it also transmits commands for liquid crystal display synchronized with them.
After executing this variation start process, the effect control CPU 200 deletes the variation pattern command in step S335.

FIG. 11D shows a process S330c when a power-on command is captured as the command process in step S330.
In this case, the effect control CPU 200 clears the effect control RAM 202 in step S337. For example, the command reception / transmission buffer, the contents of the input information buffer for the operation unit 60, and the checksum storage area are cleared.
Then, in step S338, an error release command is transmitted, in step S339 the accessory error information is cleared, in step S340, the accessory operation is stopped, in step S341, a power-on scenario is registered, and in step S342, the power is transmitted to the liquid crystal control board 52. Perform a set of commands sequentially.

FIG. 11E shows a process S330d when a RAM clear command is fetched as the command process in step S330.
In this case, the effect control CPU 200 clears the effect control RAM 202 in step S343. For example, the command reception / transmission buffer, the contents of the input information buffer for the operation unit 60, and the checksum storage area are cleared.
In step S344, an error cancel command is transmitted, and in step S345, a RAM clear error set and an error notification timer are set. In step S346, information related to the lottery process in the effect control RAM 202 is cleared. In step S347, information related to the scenario is cleared. In step S348, an initial power-on display (RAM clear) command to be transmitted to the liquid crystal control board 52 is set.

[4-4: Scenario registration / deletion processing]

Next, scenario registration / deletion processing will be described. The scenario is data defining various operations to be executed such as production control and error processing. The scenario data to be executed is registered in the work area of the effect control RAM 202 as scenario registration information. The scenario registration information shown in FIG. 16A will be described later. As scenario registration information, 64 scenario channels from 0 to 63 are prepared. Scenarios registered in these 64 scenario channels can be executed simultaneously. Hereinafter, the scenario channel is indicated by “sCH”.
The scenario registration process is a process of registering a scenario having a scenario number requested to be registered in an arbitrary scenario channel sCH in the scenario registration information. In principle, any scenario channel of sCH0 to sCH63 may be used.

  Scenario registration to be described below is called and executed when necessary, for example, in the process of error processing in step S106, demo processing in step S107, command analysis processing in step S108, and the like. For example, step S333 in FIG. 11C and step S341 in FIG. 11D described above are an example of the case where scenario registration is executed.

As the process of FIG. 12, the effect control CPU 200 performs a process of registering a scenario number and a waiting time (delay) value corresponding to a scenario specified on a command or a programgram in a work (scenario registration information).
In step S401, the effect control CPU 200 first checks whether or not the scenario number to be registered this time is normal. If the scenario number is not possible, the process ends without doing anything.

  If the scenario number is appropriate, effect control CPU 200 sets variable B to zero in step S402. The variable B is a variable used for sequentially searching for an empty channel among the scenario channels sCH0 to sCH63. Furthermore, the variable B also serves as a variable for determining whether or not there remains a scenario channel that has not yet been searched (confirmation of whether it is an empty channel).

In step S403, the effect control CPU 200 confirms whether or not the “additional pointer” + B scenario channel is empty. The additional pointer is a pointer set in step S407 described later when scenario registration is performed. At the time of starting the processing of FIG. 12, the value of the additional pointer is a value indicating the scenario channel next to the scenario channel registered last time. Note that the initial value of the additional pointer (the value when the processing in FIG. 12 is performed for the first time from the initial state) is zero.
If the “addition pointer” + B scenario channel is not empty, the effect control CPU 200 increments the variable B in step S404.
If B <64 is not satisfied in step S405, the processing in FIG. This is a case where all scenario channels have been searched but scenario registration is impossible because there are no free channels.
At a time point when all scenario channels have not been searched (confirmation of whether or not they are free channels), B <64 in step S405. In that case, the confirmation process of step S406 is performed, and if the value of “addition pointer” + B is not equal to or greater than the value “64” exceeding the maximum value of the scenario channel sCH, the process returns to step S403.
If the value of “addition pointer” + B is “64” or more, correction processing for the value of the addition pointer is performed in step S407. Specifically, when the value of “addition pointer” + B becomes “64”, a process of subtracting “64” from the value of the addition pointer is performed. Then, the process returns to step S403.

According to the processing in steps S403 to S407, it is sequentially confirmed from the scenario channel next to the previously registered scenario channel whether or not the scenario channel is empty.
That is, the scenario channel sCH that is confirmed every time step S403 is performed sequentially advances one by one due to the increment of the variable B in step S404.
Since variable B is zero-reset in step S402 and incremented in step S404, if B <64 is not satisfied in step S405 (that is, if variable B reaches 64), step S403 has already been performed. This process is performed 64 times. This is a case where all scenario channels sCH0 to sCH63 have been examined, but it is determined that there is no free space. For this reason, the processing of FIG.

Further, since the value of the “addition pointer” is a value indicating the next scenario channel of the scenario channel registered last time, the “addition pointer” + B even when B <64 when all the scenario channels are not yet confirmed. (That is, the number of the scenario channel sCH to be checked next) may be “64” or more. Specifically, the value of “addition pointer” + B is 63 at the time of immediately preceding step S403, and after confirming the scenario channel sCH63, the variable B is incremented in step S404. In this state, the scenario channel sCH64 that does not exist next is designated.
Therefore, this point is confirmed in step S406, and if the value of “addition pointer” + B is “64”, in step S407, correction of the addition pointer is performed to return the scenario channel to be confirmed next to “sCH0”. Do. That is, the value of “addition pointer” + B is set to “0” by setting the value of the addition pointer to −64. Thus, in the next step S403, it is confirmed whether or not the scenario channel sCH0 is empty.

If an empty scenario channel is found in the process of step S403 at a certain time, the presentation control CPU 200 proceeds to step S408, and sets a scenario number and a waiting time (delay) in the empty scenario channel. In addition, the data necessary for other scenario management is cleared to zero.
In step S409, the additional pointer is updated to the value of the registered scenario channel + 1. That is, the value of the scenario channel next to the scenario channel registered this time is stored as an additional pointer so that it can be used for the next registration process. In this embodiment, since the scenario channel is 64 channels sCH0 to sCH63, the maximum value of the additional pointer is 63.

  According to the processing of FIG. 12, at the time of scenario registration, an empty channel is searched from the scenario channel next to the scenario channel that was registered last time. The initial value of the additional pointer is “0”, and is subsequently updated in step S407 according to the registration. In many cases, according to this process, scenario registration is performed using the scenario channel sCH0 in order. . When the scenario is registered, the availability is confirmed from the scenario channel next to the previous registered channel. Therefore, in most cases, an empty channel can be found quickly, and the scenario registration process can be executed efficiently. As a result, the processing burden on the effect control CPU 200 is reduced.

  As a modification of the process, the value of the additional pointer updated in step S407 may be set as the number of the scenario channel that has been registered, and 1 may be substituted for variable B in step S402. In this case, however, it is determined in step S405 whether B ≦ 65.

Next, scenario deletion processing will be described. This is a process for deleting a scenario registered in a certain scenario channel of the work.
FIG. 13A shows processing of the effect control CPU 200 when a certain scenario is deleted from the scenario registration information.
The effect control CPU 200 starts the process of FIG. 13A based on the value of a scenario number to be deleted (a main scenario number (mcNo) described later) designated on the command or the programgram. First, in step S421, the effect control CPU 200 confirms whether or not the scenario number related to the deletion request is normal. If the scenario number is not possible, the process ends without being deleted.

  If the scenario number is appropriate, effect control CPU 200 sets variable B to zero in step S422. The variable B in this case is a variable used for searching for a channel in which the scenario to be deleted is registered among the scenario channels sCH0 to sCH63. Further, the variable B also serves as a variable for determining whether or not there remains a scenario channel that has not yet been searched (confirmation of whether or not a scenario to be deleted is registered).

In step S423, the effect control CPU 200 confirms whether or not the scenario registered in the B area, that is, the scenario channel sCH (B) is the scenario number to be deleted. If the scenario registered in the scenario channel sCH (B) is not the scenario number to be deleted, the variable B is incremented in step S424, and it is confirmed in step S425 that B <64, and the process of step S423 is performed. Do.
According to the processing of steps S423 and F424, the scenario to be deleted is searched in order from the scenario channel sCH0 to the scenario channel sCH63.
If the scenario registered in the scenario channel sCH (B) is the scenario number to be deleted in step S423, the process proceeds to step S426, and the scenario registered in the B area, that is, the scenario channel sCH (B) is deleted. Perform the process.
As described above, the process of deleting the scenario with the requested scenario number from the work (scenario registration information) is performed.
If it is determined in step S425 that B <64 is not satisfied, that is, if the variable B reaches 64, all the scenario channels sCH0 to sCH63 have been searched, but the scenario to be deleted has not been registered. Therefore, the process is finished.

FIG. 13B shows processing for deleting a certain range of scenarios. This process is performed when a deletion scenario is specified by a range.
The effect control CPU 200 first sets a variable B to zero in step S431 when a deletion is designated within a range of a certain scenario number on a command or program. The variable B in this case is a variable used to search for a channel in which a scenario corresponding to the deletion target range is registered among the scenario channels sCH0 to sCH63. Further, the variable B also serves as a variable for determining whether or not there remains a scenario channel that has not yet been searched (confirmation of whether or not a scenario corresponding to the deletion target range is registered).

In step S432, the effect control CPU 200 confirms whether or not the scenario registered in the B area, that is, the scenario channel sCH (B), is a scenario number within the range to be deleted. If the scenario registered in the scenario channel sCH (B) is a scenario number within the range to be deleted, the scenario registered in the scenario channel sCH (B) is deleted in step S433. Then, the process proceeds to step S434.
If the scenario registered in the scenario channel sCH (B) is not a scenario number within the range targeted for deletion, the process proceeds to step S434 without performing step S433.
The effect control CPU 200 increments the variable B in step S434, confirms that B <64 in step S435, and returns to step S432. If the variable B has reached 64, the processing has been completed for all scenario channels sCH0 to sCH63, and the scenario range deletion processing is completed.
As described above, one or more scenarios in the scenario number range are deleted from the work (scenario registration information).

FIG. 13C shows a process for deleting all registered scenarios. For example, it is a process called when a scenario is unavoidably deleted due to circumstances on the system. Do not delete scenarios that are targeted for protection.
When it is requested to delete all scenarios, the effect control CPU 200 first sets the variable B to zero in step S441. The variable B in this case is a variable used for confirming the scenario channel in which the scenario to be protected is registered among the scenario channels sCH0 to sCH63. Furthermore, the variable B also serves as a variable for determining whether or not there remains a scenario channel that has not yet been confirmed (confirmation of whether or not a scenario to be protected is registered).

In step S442, the effect control CPU 200 confirms whether or not the scenario registered in the B region, that is, the scenario channel sCH (B), is a scenario to be protected. If it is a scenario to be protected, it is not deleted. On the other hand, if it is not a scenario to be protected, the scenario registered in the scenario channel sCH (B) is deleted in step S443.
In step S444, the variable B is incremented. If B <64 in step S445, the process returns to step S442. If the variable B has reached 64, the processing has been completed for all the scenario channels sCH0 to sCH63, and thus the scenario all deletion processing ends.
As described above, all scenarios other than the scenario to be protected are deleted from the scenario registered as scenario registration information in the work.

[4-5: Scenario update processing]

Next, the scenario update process performed in step S110 of the 16ms process of the main process will be described. In the scenario update process, the main scenario and the sub-scenario are updated as described with reference to FIGS.

First, the structure of scenario registration information will be described with reference to FIGS. FIG. 16A shows the structure of scenario registration information as a main scenario and a sub-scenario. This scenario registration information is set using the work area of the effect control RAM 202.
As described above, in the present embodiment, the scenario registration information has 64 channels of scenario channels sCH0 to sCH63. Scenarios registered in each scenario channel sCH can be executed simultaneously.

  As shown in the figure, information that can be registered in each scenario channel sCH includes a sub-scenario timer (scTm) used in the sub-scenario update process, a sub-scenario execution line (scIx) indicating an execution line of the sound / motor sub-scenario table, and a lamp sub-scenario. Sub scenario execution line lmp (lmpIx) indicating the execution line of the table, main scenario timer (msTm) used for scenario update processing, main scenario execution line (mcIx) indicating the execution line of the main scenario table, main scenario number (mcNo), There are main scenario option (mcOpt), user option (userFn), waiting time (delay), and checksum (checkSum), which are optional data that can be added to the main scenario.

When the sound output by the speaker 25, the light emission by the decorative lamp units 63 and 64, and the production by the driving of the movable body accessory by the movable body accessory motor unit 65 are started, the standby time (delay) and the main scenario number (scNo) are set. It registers in an empty scenario channel among the scenario channels sCH0 to sCH63.
The waiting time (delay) indicates the time from registration to the scenario channel sCH until the scenario is started. The waiting time (delay) is decremented by 1 every 16 ms processing. When the waiting time (delay) is 0, processing corresponding to the registered data is executed.

FIG. 18 shows an example of scenario numbers 1, 2, and 3 as a part of the main scenario table. As the scenario of each scenario number, the main scenario timer (msTm) value is described as time data in each line (row) of the scenario, and the sub-scenario number (scNo) and option (OPT) can be described. . That is, in the main scenario table, a sub-scenario (and optional in some cases) to be executed is designated as the time by the main scenario timer (msTm). In the last line of the scenario, a scenario data end code D_SEEND or a scenario data loop code D_SELOP is described.
Since the value of the main scenario timer (msTm) is incremented by 1 in the scenario update process performed in the 16 ms process from the start of the main scenario, “1” indicates 16 ms. The scenario table of each scenario number advances to the next line when the time of the main scenario timer (msTm) in a certain line has elapsed. The time data of each line indicates the timing when the line ends.
For example, in the case of scenario number 2, the operation of sub-scenario number 2 is specified as a time of 1500 × 16 ms, the operation of sub-scenario number 20 is specified as the next time of 500 × 16 ms, and the operation is performed as the next time of 2000 × 16 ms. The operation of scenario number 21 is designated. The next line is the scenario data end code D_SEEND. In the case of the scenario data end code D_SEEND, this scenario is deleted from the scenario registration information (work) (see step S617 in FIG. 14 described later).

Next, the structure of the lamp data registration information will be described with reference to FIG. 16B. As the lamp data registration information, a scenario selected from the lamp sub-scenario table, that is, information indicating a rendering operation (lighting pattern) by the decorative lamp units 63 and 64 is registered. This lamp data registration information is also set using the work area of the effect control RAM 202.
In the present embodiment, the ramp data registration information has 16 channels of ramp channels dwCH0 to dwCH15. Priorities are set for each of the ramp channels dwCH0 to dwCH15, and the priority increases in order from the ramp channels dwCH0 to dwCH15. Therefore, the scenario (lamp sub-scenario) registered in the ramp channel dwCH15 is executed with the highest priority. For example, if a scenario is registered in the ramp channels dwCH3 and dwCH10, the scenario registered in the ramp channel dwCH10 is preferentially executed.
The ramp channel dwCH0 is mainly used for a lamp effect associated with BGM (Back Ground Music), the lamp channel dwCH15 is used for an error-related lamp effect, and the lamp channels dwCH1 to dwCH14 are used for a normal effect.

  As shown in the figure, information that can be registered in each lamp channel dwCH includes a registered lighting number (lmpNew) indicating the number of the registered lighting pattern, an execution lighting number (lmpNo) indicating the number of the lighting pattern to be executed, and a lamp sub-scenario. There are an offset indicating an execution line (offset), an execution time (time), and a checksum (checkSum).

  FIG. 19A shows an example of lamp sub-scenario numbers 1, 2, and 3 as a part of the lamp sub-scenario table. For each number of lamp sub-scenarios, time data (time) values are described in each line (row) of the scenario, and lamp channels and lamp numbers indicating various lighting patterns are described. In the last line, a lamp scenario data end code D_LSEND is described.

In this ramp sub-scenario table, the time data (time) of each line indicates the time at which the line is started after the sub-scenario is started.
When the main scenario timer (msTm) and the time data in the table are compared every 16 ms and they match, the lamp number of that line is registered in the lamp data registration information of FIG. 16B. The registered ramp channel dwCH is the channel indicated in the line.
For example, it is assumed that the scenario number 2 shown in FIG. 18 is registered and the sub-scenario number 2 is referred to in a certain scenario channel sCH described above. In the lamp sub-scenario number 2 shown in FIG. 19A, the lamp channel 5 (dwCH5) and the lamp number 5 are described as time data (time) = 0 on the first line. In this case, when the main scenario timer (msTm) = 0, the information on the first line is first registered in the lamp channel dwCH5 of the lamp data registration information in FIG. 16B as the registered lighting number (lmpNew) = 5. The value of the sub-scenario execution line lmp (lmpIx) in the scenario registration information (FIG. 16A) is updated to the value of the next line (second line). This is a registration for performing the lighting pattern operation of the lighting number 5 with a relatively low priority of the lamp channel dwCH5.
For the second line, the same processing is performed when it becomes 500 × 16 ms. That is, the registered lighting number (lmpNew) = 6 (that is, the lighting pattern 6 lighting instruction) is registered in the lamp channel dwCH5 of the lamp data registration information.
If the time data (time) has the same value for two consecutive lines, the processing for each line is started simultaneously.
In the LED drive data update process to be described later, LED drive data is created based on the lamp data registration information updated in this way.

Next, the structure of the motor data registration information will be described with reference to FIG. 16C. As the motor data registration information, information indicating a scenario selected from the sound / motor sub-scenario table (described later in FIG. 19B) is registered. This motor data registration information is also set using the work area of the effect control RAM 202.
In the present embodiment, the motor data registration information is assumed to have eight channels of motor channels mCH0 to mCH7.
Information that can be registered in each motor channel mCH includes execution operation number (no), registration operation number (noNew), operation count (lcnt), excitation counter (tcnt), execution step (step), operation line as shown in the figure. (Offset), parent (migration source) / child (migration destination) attribute (attribute), parent number (retNo), return address (retAddr), loop start point (roopAddr), loop count (roopCnt), error counter (errCnt) ), Current input information (currentSw), software switch information (softSw), and software count (softCnt).

FIG. 19B shows an example of sound / motor subscenario numbers 1 and 2 as part of the sound / motor subscenario table.
As the sound / motor sub-scenario of each number, the time data (time) value (ms) is described in each line (row) of the scenario, and BGM, SE1, SE2, error sound, sound control, motor, solenoid / User option information can be described. In the last line, a scenario data end code D_SEEND is described.
With respect to this sound / motor sub-scenario table, if the value of the sub-scenario timer (scTm) becomes the value of time data (time) described in a certain line in the sound / motor sub-scenario table (initially 0) The information corresponding to the BGM, SE1, SE2, error sound, sound control, motor, solenoid / user option described in the line is registered in the sound data registration information and motor data registration information.
The time data (time) of each line indicates the timing at which the line is started.

In the sound / motor sub-scenario table of FIG. 19B, data relating to the motor is a total of 8 bytes, 4 bytes indicated as “motor 0-3” and 4 bytes indicated as “motor 4-7” in the figure. As information that can correspond to a maximum of 8 motors (each motor 121 in the movable body accessory motor unit 65: see FIGS. 3 and 5), the operation pattern number of the motor is indicated by 1-byte data for each motor. It is configured.
This operation pattern number is set for the motor channel corresponding to the motor number.
A specific process for registering the motor information described in the sound / motor sub-scenario table in the work as motor data registration information will be described later with reference to FIG.

FIG. 17 shows sound data registration information. As the sound data registration information, information indicating a scenario selected from the sound / motor sub-scenario table (described later in FIG. 19B) is registered. This sound data registration information is also set using the work area of the effect control RAM 202.
In the present embodiment, the sound data registration information has 16 channels of sound channels aCH0 to aCH15. Each of the sound channels aCH0 to aCH15 corresponds to each of the input channels (also 16) of the sound source IC 59.
Information that can be registered in each sound channel aCH includes primary volume transition amount (frzVq), primary volume (frzVl), transition amount change (rsv2), volume change (rsv1), phrase change (rsv0) as shown in the figure. , Stereo (frzSt), loop (frzLp), phrase number hi (frzHi), phrase number low (frzLo), and secondary volume (scdVl).

Here, the primary volume is volume information described together with phrase number information of a phrase to be reproduced in scenario data (BGM, SE1, SE2, error described later) instructing the start of reproduction of a certain phrase. .
The secondary volume is volume information that determines the final reproduction volume by multiplying with the primary volume.
The difference between the primary volume and the secondary volume is as follows.
As described above, the primary volume is also described in the scenario data for instructing the start of phrase reproduction, whereas the secondary volume is described in the scenario data for sound control (sound control information) described later.
Further, in the case of the present embodiment, depending on the primary volume, volume control for the phrase being played back is possible by combining with the information of the primary volume transition amount (frzVq). Phrase fade-in playback / fade-out playback is enabled. As will be described later, these fade-in playback / fade-out playback instructions are executed based on scenario data as sound control.
The secondary volume is usually set to a value according to the state of the volume switch provided on the back side of the pachinko gaming machine 1, and the MAX value is used when an error or a desired phrase is to be muted as described later. Different values are set.
The secondary volume change instruction can also be made by scenario data as sound control (this will also be described later).

The primary volume transition amount frzVq is information indicating the time (speed) for changing the primary volume.
The transition amount change rsv2 is information indicating whether or not the primary volume transition amount frzVq is changed, and the volume change rsv1 is information indicating whether or not the primary volume is changed during phrase reproduction. The phrase change rsv0 is information indicating whether or not the phrase number is rewritten. The stereo frzSt is either stereo playback or monaural playback, and the loop frzLp is either infinite loop playback or no loop playback. It becomes information to represent.

  As shown in the figure, the primary volume transition amount, the primary volume, and the data size of the secondary volume are each 1 byte (8 bits). Each information of transition amount change, volume change, phrase change, stereo, and loop is 1 bit. Furthermore, the phrase number hi is 3 bits, and the phrase number low is 1 byte. That is, the phrase number information is composed of 11 bits, so that a maximum of 2048 phrases can be specified.

In this example, in the case of stereo reproduction, two sound channels aCH that are adjacent to each other are used. Specifically, the sound channel aCHn that is an even channel and the sound channel aCHn + 1 that is the next odd channel are used.
In the scenario data instructing stereo playback, information on the phrase number for designating a phrase to be played back in stereo (one phrase number common to Lch and Rch is used as designation information) and stereo playback are designated. Based on the scenario data, the phrase number and stereo playback instruction information are registered in the even sound channel aCHn and the odd sound channel aCHn + 1 in the sound data registration information (described above). Phrase numbers hi, low and stereo frzSt).

In the sound / motor sub-scenario table of FIG. 19B, BGM, SE1, SE2, error sound, and sound control can be described as data related to sound.
SE (SE1 and SE2) in the sound / motor sub-scenario table means sound related to effects other than BGM and error sound. Sounds for so-called notice effects (notice sounds) are classified into this SE.
The distinction between SE1 and SE2 is made according to the appearance frequency of the effect that outputs the sound. For example, in the case of a notice sound, the distinction is made according to the appearance frequency (reliability) of the notice effect using the sound. In the case of this example, SE2 is a sound related to an effect having a lower appearance frequency than SE1.

Each information of BGM, SE1, SE2, and error sound in the sound / motor sub-scenario table includes a phrase number and primary volume information.
The BGM, SE1, SE2, and error sound information described in the sound / motor sub-scenario table are registered in one of the sound channels aCH in the sound data registration information. For each type of BGM, SE1, SE2, and error sound, a sound channel aCH for registering the information content is determined in advance.
Specifically, the BGM information described in the sound / motor sub-scenario table is registered in the sound channel aCH0 (in addition, in the case of stereo, aCH1). Further, information on SE1 is registered in an empty channel among the sound channels aCH2 to aCH9, and information on SE2 is registered in an empty channel among the sound channels aCH10 to aCH14. Further, information on the error sound is registered in the sound channel aCH15.
As described above, in the present embodiment, the correspondence between the type of sound and the sound channel aCH for registering sound-related information about the sound is determined in advance.

The sound control information in the sound / motor sub-scenario table describes information for controlling the phrase being reproduced.
In the case of the present embodiment, the sound control information is composed of 4 bytes, the lower 3 bytes are information for designating a phrase to be controlled, and the upper 1 byte is control information (information indicating the control content of the sound) Has been.

Here, in the present embodiment, the correspondence between the type of sound and the sound channel aCH for registering information about the sound is determined as described above. This is because the phrase as BGM is the sound channel aCH0. (Stereo is aCH0 and aCH1), the phrase SE1 is reproduced on any of the sound channels aCH2 to aCH9, the phrase SE2 is reproduced on any of the sound channels aCH10 to aCH14, and an error sound In other words, it can be said that the phrase is reproduced on the sound channel aCH15.
Therefore, when a predetermined type of sound (BGM / SE1 / SE2 / error sound) is controlled based on the sound control information, the sound control information is registered for the sound channel aCH corresponding to the sound. That's fine.
In view of this point, in the sound control information of the present embodiment, information specifying the sound channel aCH is described as information of the lower 3 bytes, that is, information for specifying the phrase to be controlled. That is, the sound channel aCH (that is, aCH0 (and aCH1) / aCH2 to aCH9 / aCH10 to aCH14 / aCH15 according to the type of BGM / SE1 / SE2 / error sound) in which the sound (phrase) to be controlled is reproduced. Information to be specified is described.

  It should be noted that specific processing for registering each information of BGM, SE1, SE2, error sound, and sound control described in the sound / motor sub-scenario table in the work as sound data registration information is shown in FIGS. It will be described later.

In this embodiment, as described above, the correspondence between the sound type and the sound channel aCH in which information about the sound is registered is determined in advance, so that a certain type of sound is generated. The reproduced sound channel aCH can be uniquely determined. Thus, when a certain type of sound being played is controlled, it is only necessary to register control information for the sound channel aCH associated with that type of sound in the work, and the sound to be controlled is played back. It may be unnecessary to search for the middle sound channel aCH.
Therefore, the control load related to the rendering operation can be reduced as much as the search process is omitted.

Further, as described above, in the present embodiment, the sound control information for controlling the sound being reproduced includes information indicating the content of the control, and information indicating the sound channel aCH corresponding to the sound to be controlled. Information.
As described above, even when the sound control information is information that can designate the sound channel aCH that is the registration destination of the control content information, it is not necessary to search for the sound channel aCH that is reproducing the sound to be controlled. That is, the point that the sound control information has such a configuration also contributes to the omission of the search process, that is, the reduction of the control load related to the rendering operation.

In the sound reproduction process described as step S111 in FIG. 8, reproduction output is performed based on the sound data registration information updated in the scenario update process in FIGS.
In the motor operation update process in step S203 of FIG. 9, motor drive data is created based on the motor data registration information updated in the scenario update process of FIGS.

Scenario update processing executed using each piece of information described so far will be described with reference to FIGS.
In the scenario update process of FIG. 14 executed as step S110 of the 16 ms process of FIG. 8, the effect control CPU 200 performs the processes of steps S600 to S616 for each of the scenario channels sCH0 to sCH63 as the loop process LP1. The scenario channel to be processed each time in the loop processing will be described as “sCHn”.

  The effect control CPU 200 confirms whether or not the main scenario number of the scenario channel sCHn is 0 in step S600. When the main scenario number is 0, the scenario channel sCHn is a channel sCH for which the main scenario has not been registered in the scenario registration process of FIG. 12, and thus information update of the scenario channel sCHn is unnecessary. Therefore, in this case, the processing after step S615 is executed to finish the processing. Specifically, the checksum of the data related to the scenario channel sCHn is calculated and stored in step S615, and the data related to the scenario channel sCHn is backed up and stored in step S616. This completes one process for the scenario channel sCHn.

  On the other hand, if it is determined in step S600 that the main scenario number is not 0, the process proceeds to step S601, and the standby time (delay) of the scenario channel sCHn is confirmed. If the standby time (delay) = 0 is not satisfied, the value of the standby time (delay) is decremented by −1 (decrement) in step S602. And the process of step S615 and S616 is performed and the process of 1 time about scenario channel sCHn is finished.

When it is confirmed in step S601 that the standby time (delay) = 0, the effect control CPU 200 proceeds to step S603, and the main scenario number (mcNo) registered in the scenario channel sCHn and the main scenario execution line ( Specify the address of the main scenario table corresponding to mcIx).
In step S604, it is confirmed whether or not an execution line of a certain main scenario number in the main scenario table indicated by the specified address is a final line in which an end code D_SEEND (see FIG. 18) is described.
If the end code matches the last line in which the end code is described, the processing to be executed in the scenario registered in the scenario channel sCHn has been completed. Therefore, in step S617, the scenario registered in the scenario channel sCHn. Is deleted from the scenario registration information (work).
Note that the scenario registration deletion in this case is a normal deletion corresponding to the end of the scenario. It is added that the scenario deletion described above with reference to FIG. 13 is a process for deleting, for example, an unfinished scenario from the scenario registration information (work) other than the normal deletion.

  After the scenario is deleted in step S617, the process proceeds to step S615.

If it is determined in step S604 that the line in the main scenario table is not an end code, the production control CPU 200 proceeds to step S605, and first sets the option (OPT) of the line in the main scenario option (mcOpt) of the scenario channel sCHn. To do. In step S607, 0 is substituted for the user option (userFn).
In step S608, the sub-scenario specified by the scenario channel sCHn is updated. The sub-scenario update will be described later with reference to FIG.

  If it is determined in step S606 that the scenario number is not 0, the process proceeds to step S609.

In step S609, the effect control CPU 200 increments the main scenario timer (msTm) by +1. In step S610, the value of the main scenario timer (msTm) is compared with the time data of the corresponding line in the main scenario table (see FIG. 18: described in msTm). As described above, since the time data of each line in the main scenario table defines the end timing of the line, the value of the main scenario timer (msTm) is described in the corresponding line in the main scenario table. If it is more than the time data, the process for that line ends and the next line is targeted. Accordingly, if it is determined in step S610 that the value of the main scenario timer (msTm) is equal to or greater than the time data described in the relevant line of the main scenario table, the process proceeds to step S611, and the main scenario execution line (mcIx for the scenario channel sCHn). ) +1. That is, next time, the next line is targeted.
If it is determined in step S610 that the value of the main scenario timer (msTm) is not equal to or greater than the time data described in the relevant line of the main scenario table, the process proceeds to step S615.

After the main scenario execution line (mcIx) of the scenario channel sCHn is incremented by 1 in step S611, it is confirmed in step S612 whether or not the next line is designated as a loop. In scenario number 1 in the main scenario table of FIG. 18, an example is shown in which the last line is the scenario data loop code D_SELOP. Set loop line to mcIx).
If it is determined in step S612 that the next line is not designated as a loop, the process proceeds to step S614 without going through step S613.

In step S614, the effect control CPU 200 performs a clear process according to the end of one line. That is, main scenario timer (msTm), sub-scenario timer (scTm), sub-scenario execution line (scIx), sub-scenario execution line lmp (lmpIx), main scenario option (mcOpt), user option (userFn), standby time (delay) To clear.
Then, the checksum process in step S615 and the backup process in step S616 are performed, and one process for the scenario channel sCHn is completed.
As the scenario update process, the above process is executed for each of the scenario channels sCH0 to sCH63 as the loop process LP1.

The sub-scenario update process performed in step S608 is shown in detail in FIG. 15A.
Based on the main scenario timer (msTm), the scenario channel sCHn, and the sub-scenario number (scNo) described in the main scenario table, the sub-scenario update process of FIG. 15A is performed.

First, in step S621, the effect control CPU 200 confirms whether or not the scenario channel sCHn indicates any of 0 to 63, that is, whether or not it is an appropriate value. If the scenario channel sCHn is 64 or more, the update process is impossible and the process of FIG. 15 ends.
If the scenario channel sCHn is an appropriate value, the effect control CPU 200 identifies the address of the lamp sub scenario table (see FIG. 19A) corresponding to the sub scenario number (scNo) and the sub scenario execution line lmp (lmpIx) in step S622. .

  In step S623, the effect control CPU 200 sets the lamp channel count value to zero. This lamp channel count value is a value managed by the effect control CPU 200 in order to prevent the lighting pattern number from being registered in the lamp data registration information beyond the number (16) of the lamp channels dwCH. It is.

  In step S624, the effect control CPU 200 compares the main scenario timer (msTm) with the time data (time) in the lamp sub-scenario table. The time data (time) in the lamp sub-scenario table indicates the time (ms) at which the line (the line indicated by the sub-scenario execution line lmp (lmpIx)) is started. Therefore, if the time of the main scenario timer (actually, the time of msTm × 16 ms) is equal to or greater than the time data (time), the processing for that line is performed. In that case, in step S625, it is confirmed whether or not the ramp channel count value is normal (within “16” which is the number of ramp channels dwCH). If it is an abnormal value, the process ends. If it is a normal value, it is checked in step S626 if the current line is a line in which the lamp scenario data end code D_LSEND is described.

If it is not the line in which the lamp scenario data end code D_LSEND is described, the effect control CPU 200 acquires the lamp channel and lamp number described in the line in step S627. In step S628, the lighting pattern number is registered.
The lighting pattern number registration process is shown in FIG. 15B. In this case, first, in step S651, the effect control CPU 200 determines whether or not the value of the lamp channel dwCH described in the line is a normal value. If it is not a normal value, the process ends without performing registration.
If it is a normal value, it is determined in step S652 whether or not the ramp number described in the line is a normal value. If it is not a normal value, the process ends without performing registration.
If both the lamp channel dwCH and the lamp number are normal values, the registered lighting number (lmpNew) and the execution lighting number (lmpNo) are set in the area corresponding to the lamp channel dwCH in the lamp data registration information of the work in step S653. To do. That is, the lamp number acquired from the relevant line in the lamp sub-scenario table is set in the registered lighting number (lmpNew), and “0” is set in the execution lighting number (lmpNo).
15B is performed in step S628, the effect control CPU 200 increments the value of the sub-scenario execution line lmp (lmpIx) in step S629, increments the lamp channel count value in step S630, and returns to step S624.

  When the time of the main scenario timer does not reach the time data (time) of the line indicated by the sub-scenario execution line lmp (lmpIx) in step S624, and the lamp scenario data end code D_LSEND is confirmed in step S626 The process of the effect control CPU 200 proceeds to step S631.

In step S631, the sub-scenario number described in the main scenario table and the address of the sound / motor sub-scenario table corresponding to the sub-scenario execution line (scIx) registered in the currently processed scenario channel sCHn are specified. .
In step S632, it is checked whether the value of the sub-scenario timer (scTm) is equal to or greater than the value of the time data (time) in the table. That is, whether or not the value of the sub-scenario timer (scTm) is equal to or greater than the value of the time data (time) of the line indicated by the sub-scenario execution line (sclx) registered in the currently processed scenario channel sCHn. Check.

  In step S632, if the value of the sub-scenario timer (scTm) is not equal to or greater than the value of the time data (time) in the table, the registration process for the information described in the line should not be executed yet, as shown in the figure. Then, the process proceeds to step S640 without registering the sound and the motor, the value of the sub-scenario timer (scTm) is incremented (+1), and the process of FIG. 15A is completed.

On the other hand, if the value of the sub-scenario timer (scTm) is equal to or greater than the value of the time data (time) in the table in step S632, the effect control CPU 200 advances the process to step S633 and stores the corresponding sound / motor sub-scenario number table. Then, it is confirmed whether or not the line indicated by the sub-scenario execution line (scIx) is a line in which the scenario data end code D_SEEND is described. If the scenario data end code D_SEEND is described, the process ends.
If the scenario data end code D_SEEND is not described, the effect control CPU 200 performs sound registration in step S635 and motor registration in step S636. As the registration processing of these steps S635 and S636, the information on the corresponding line of the corresponding sub-scenario number of the sound / motor sub-scenario table as illustrated in FIG. Each of the motor data registration information is registered in the motor channel mCH.
Detailed processing contents of sound registration executed as step S635 will be described later with reference to FIGS. 24 to 28, and detailed processing details of motor registration executed as step S636 will be described later with reference to FIG. .

Subsequently, in step S637, the effect control CPU 200 registers the solenoid / user option information described in the line in the scenario registration information or the like.
In step S638, the value of the next line is set as the value of the sub-scenario execution line (scIx). Further, in step S640, the sub-scenario timer (scTm) is incremented and the process is terminated.

  In step S110 in FIG. 8, the processes in FIGS. 14 and 15 are performed. Through this process, the scenario registration information, lamp data registration information, motor data registration information, and sound data registration information on the workpiece are sequentially updated, and effect control according to the scenario is realized by performing effect control accordingly. The

Particularly in the present embodiment, scenario registration information is set in the first work area (scenario channels sCH0 to sCH63) as effect data for specifying the effect type. Specifically, the main scenario number (mcNo) is set, and the sub-scenario on the main scenario table is specified. Further, in the first work area, a sub-scenario execution line (scIx) indicating an execution line of the sound / motor sub-scenario table and a sub-scenario execution line lmp (lmpIx) indicating an execution line of the lamp sub-scenario table are set. The production type is specified by these.
Further, the operation data of the effect device corresponding to the effect to be executed is set in the second work area. Lamp channels dwCH1 to dwCH15 for setting lamp data registration information, motor channels mCH0 to mCH7 for setting motor data registration information, and sound channels aCH0 to aCH15 for setting sound data registration information are prepared as second work areas.
In other words, in the present embodiment, overall presentation data using various presentation devices is set in the first work area, and operation data is set in the second work area based on the presentation data of the first work area. Will be.
In this case, in order to set various effects, it is preferable to relatively increase the number of effects data (number of scenario registration information) that can be registered in the first work area. For example, I want to increase the number of registered channels for production data. Therefore, 64 channels are prepared as scenario channels sCH0 to sCH63.
On the other hand, since the operation data that defines the operation of the rendering device need only be set in the second work area, the number of registerable operation data may be relatively small. In particular, since the second work area is provided corresponding to each effect device for lamps, motors, and sounds, it is not necessary to unnecessarily increase the number that can be registered for each device. Therefore, as the second work area, the ramp channel is 16 channels (dwCH1 to dwCH15), the motor channel is 8 channels (mCH0 to mCH7), and the sound channel is 16 channels (aCH0 to aCH15). Since it suffices for the operation data for one corresponding production device to be set for each of them, it is possible to cope with a wide variety of production operations even if the number of registered channels is small.
Thus, if the number of channels in the first work area is N (for example, N = 64) and the number of channels in the second work area is M (for example, M = 16 or M = 8), N> M. The storage area is allocated as follows.
This keeps the memory from being consumed by the dark clouds while still allowing a variety of performance operations.

In the present embodiment, the effect control CPU 200 registers effect data (scenario number in the main scenario table) selected based on the effect control command from the main control CPU 100 in the empty channel of the work area (FIG. 11). FIG. 12). As described with reference to FIG. 18, the main scenario table stores one or more designation information (sub-scenario numbers) for designating the operation of the production device to define a series of production operations.
Then, the effect control CPU 200 sequentially executes processing corresponding to the specified information, with one or more specified information stored in the effect data registered as scenario registration information in the work area as a processing target (step in FIG. 14). S603 to S616). Further, in response to the end information (end code (D_SEEND)) stored on the effect data being processed, the effect data (scenario) is deleted from the work area scenario registration information (FIG. 14). Step S617).
In this way, when the process reaches the end code line of the main scenario table, the scenario deletion process is immediately performed from the work area, thereby effectively using the work area, improving the efficiency of the process, and reducing the processing load. Can be planned.
For example, normally, in order to delete a scenario on the scenario registration information, a flag is set for the scenario channel sCH in accordance with the end code, and then the process of deleting the contents of the scenario channel sCH flagged as the scenario deletion process is performed. Do. On the other hand, in the present embodiment, such independent scenario deletion processing is usually performed only in a special case as described with reference to FIG. 13 (for example, when deletion is specifically designated by a command or the like). When the process ends, that is, when the process related to the scenario ends, the process is automatically deleted in step S617. Therefore, the scenario deletion process from the workpiece is efficiently executed. Also, management of the end scenario on the work area (for example, the above flag setting) becomes unnecessary.

Also, since the scenario channel sCH becomes an empty channel as soon as the processing is completed, unnecessary registration is not continued and it can be used immediately for registration of a new scenario. In particular, in this example, the production control CPU 200 registers production data (scenario) selected based on the production control command in an arbitrary empty channel in the work area, as described in FIG. Therefore, opening the scenario channel sCH as soon as possible is also suitable for scenario registration. In other words, when performing various scenario operations and performing various effects, it is preferable that a situation where there is no free space is not generated as much as possible without increasing the number of channels.
As described above, scenario deletion according to the end code facilitates efficient processing and efficient use of memory.

In the present embodiment, the effect control CPU 200 stores a plurality of operation data for specifying the operation of each effect device and information for specifying the execution time (for example, information on each line corresponding to time data (time)). A sub-scenario table, and a plurality of main scenario tables storing information (for example, a sub-scenario number (scNo) and a main scenario timer (msTm)) specifying the sub-scenario table and its execution time are used. Then, the main scenario table is specified based on the effect control command from the main control CPU 100, the sub-scenario table is specified according to the contents of the specified main scenario table, and each effect device is identified according to the contents of the specified sub-scenario table. Control to operate.
That is, a hierarchical structure in which the sub-scenario table is derived from the main scenario table is employed, and as actual individual production devices, light emitting devices (decorative lamp units 63 and 64), sound devices (sound source IC 59), motor devices (movable bodies) The operation of the accessory motor unit 65) is defined by the sub-scenario table. The effect control CPU 200 can perform integrated control of a plurality of effect devices only by specifying the main scenario table, and can easily manage and execute various effect operations using the effect devices. As a result, various effects can be realized while reducing the processing load on the effect control CPU 200.
Also, by having a hierarchical structure, various scenarios can be easily set, for example, by having a large number of main scenario tables with different combinations of sub-scenario tables, and the memory capacity for that can be reduced.

[4-6: LED drive data update process]

The LED drive data update process in step S113 of FIG. 8 will be described.
This process is a process for creating LED drive data with reference to the lamp data table corresponding to the lighting number (registered lighting number (lmpNew), execution lighting number (lmpNo)) registered in the lamp data registration information. . As described above, the lamp number indicating the lighting pattern originally set in the lamp sub-scenario table is set as the lighting number of the lamp data registration information. The lamp number has been described as the number indicating the lighting pattern, but specifically indicates the lamp data number of the lamp data table described in FIG. 23A.

FIG. 20 shows LED drive data update processing.
In step S701, the effect control CPU 200 clears the LED drive data that has been output data until then.
Then, as loop processing LP2, the processing of steps S702 to S720 is performed for each of the lamp channels dwCH0 to dwCH15 of the lamp data registration information. Hereinafter, the lamp channel to be processed will be described as “dwCHn”.

In step S702, the effect control CPU 200 checks whether or not the execution lighting number (lmpNo) and the registered lighting number (lmpNew) in the target lamp channel dwCHn match. Since the lighting pattern number is registered as in step S653 of FIG. 15B, the execution lighting number (lmpNo) and the registered lighting number (lmpNew) do not match at first. If they do not match, the lighting is started, and the value of the registered lighting number (lmpNew) is substituted into the execution lighting number (lmpNo) in step S703. In step S704, the execution line (ofset) is set to 0, and the execution time (time) is set to 0.
If the execution lighting number (lmpNo) matches the registered lighting number (lmpNew), the above steps S703 and S704 have already been performed, and these processes are unnecessary.

Regarding the information registered in a certain lamp channel dwCH, after the registration, the LED drive data to be output to each LED driver 90 is created for each occasion of the LED drive data update process.
FIG. 21A shows a state where registration is performed on the ramp channels dwCH0, dwCH5, and dwCH8 in the ramp data registration information of the workpiece shown in FIG. 16B. The state in this figure is an example of the state at time t0 in FIG. 21B.
That is, the information on the lamp channels dwCH0 and dwCH5 is reflected in the LED output data before time t0. For the lamp channel dwCH0, the execution lighting number (lmpNo) and the registered lighting number (lmpNew) have already been matched, and the execution line (ofset) has advanced to 3 (third line). Also, for the lamp channel dwCH5, the execution lighting number (lmpNo) and the registered lighting number (lmpNew) have already been matched, and the execution line (ofset) has advanced to 2 (second line). At time t0, the lamp channel dwCH8 is immediately after registration, and the execution lighting number (lmpNo) and the registration lighting number (lmpNew) are not matched. Thereafter, the processes in steps S703 and S704 are performed.

As described above, in the present embodiment, priority is set for the ramp channels dwCH0 to dwCH15, and the priority increases in order from the ramp channels dwCH0 to dwCH15. As shown in FIG. 21A, the lamp channel dwCH15 having a high priority is used for error notification. Lamp channels with high priority, such as the lamp channels dwCH12, dwCH13, dwCH14, etc. are used for relatively highly reliable performances such as continuous notices and final notices. The lamp channel with medium priority is used for moving body effects, and the lamp channel with relatively low priority is used for effects with relatively low reliability, such as conversation notices and step-up notices. Channels are used for ramp effects that are synchronized with normal fluctuations, reach, and the like.
Due to such priority setting, when the operations of a plurality of lamp channels dwCH overlap as shown in FIG. 21B, a lighting operation of a lamp channel with a high priority is executed. For example, from time t0, the lighting operation based on the lamp channels dwCH0 and dwCH5 is limited, and the LED output data is generated so that lighting based on dwCH8 is performed. In order not to reflect the information of the lamp channel having a low priority, mask data described later is used.

Subsequently, in step S705 of FIG. 20, the effect control CPU 200 confirms whether or not the value of the execution lighting number (lmpNo) is within a normal range. The normal range is a range where numbers exist as lamp data in the lamp data table shown in FIG. 23A.
If the execution lighting number (lmpNo) is abnormal, the process proceeds to step S719. If the lamp channel dwCHn is an unregistered empty channel, that is, if the execution lighting number (lmpNo) and the registered lighting number (lmpNew) are “0”, the process proceeds to step S719 as an abnormality here.
In step S705, it may be confirmed whether or not the value of the registered lighting number (lmpNew) is within the normal range.

If the execution lighting number (lmpNo) is normal, the process proceeds to step S706. In step S706, the effect control CPU 200 specifies the address of the lamp data table corresponding to the execution lighting number (lmpNo) and execution line (ofset) registered in the lamp channel dwCHn.
In step S707, the execution lighting number (lmpNo) registered in the lamp channel dwCHn and the address of the mask data table are specified.
To specify the address, the effect control CPU 200 refers to a lamp data address table as shown in FIG. In this lamp data address table, the address of the lamp data number for realizing each lighting pattern, for example, entire flashing, right flashing, left flashing, and accessory lighting is shown. The numbers on the left side of FIG. 22 are the lamp numbers shown in the lamp sub-scenario table of FIG. 19A. The stored address is described.
In the address field of mask data, an address where mask data necessary for executing the lighting pattern of the lamp data number is stored is stored. For example, when a lighting pattern of blinking on the right side of the lighting number 5 is performed, a center case mask is required, but an address of mask data for performing the center case mask is described.

FIG. 23A shows lamp data 1 and 2 as part of the lamp data table.
Each line in each number of lamp data describes time data and lighting data as a timer (frame). The timer (frame) defines the time for generating the LED output data based on the lighting data of each line.
The lighting data is described corresponding to each LED driver 90. In FIG. 4, it is assumed that there are n LED drivers 90 in the frame driver unit 61 and m LED drivers 90 in the panel driver unit 62. However, in the following, as an example, four LED drivers 90 are included in the frame driver unit 61. The description will be made on the assumption that there are five LED drivers 90 in 62, that is, nine in total.
In that case, lighting data is described in each line of the lamp data corresponding to each of the nine LED drivers 90, as shown in FIG. 23A. In the figure, the correspondence with each LED driver 90 is indicated by w1 to w4 and b1 to b5 as slave addresses of the LED driver 90.
As the lighting data, 4 bits (0h to Fh) are assigned to one output terminal 96 (one series of LED drive current outputs) of the LED driver 90 described in FIGS. 4 and 5 (“h” is Hexadecimal notation is shown), and the luminance of 16 gradations is designated. As described in FIG. 5, the LED driver 90 has 24 output terminals 96-1 to 96-24. Therefore, one piece of lighting data is information of (4 × 24) bits as “FFFF000055550000AAAAAAAA (h)”. If the lighting data for the LED driver 90 (w1) is “FFFF00000000000000055550000 (h)” as shown in the first line of the lamp data 1 shown in the figure, the output terminals 96-1 to 96-96 of the LED driver 90 (w1). -4 outputs a driving current for emitting the maximum luminance “F”, the output terminals 96-5 to 96-16 and 96-21 to 96-24 are not emitting light (minimum luminance), and the output terminal 96-17. ... 96 to 20 is information for designating output of a drive current having a luminance of “5”.
In the lamp data, such lighting data is set for each of the LED drivers 90 (w1 to w4, b1 to b5), and is set for each line, so that time series. A predetermined light emission pattern that changes is shown. (In the figure, the lighting data is illustrated only in part. The blank portion is not shown, and the lighting data is actually described.)

FIG. 23B shows mask data 1 to 5 as examples of the mask data table. Each mask data includes a mask for driving the decorative lamp 20w on the frame side, a mask for driving the decorative lamp 20b on the board side, an entire mask, a mask for the center case, Necessary mask patterns are stored for masking and the like.
The mask data 1 to 5 are data indicating that the output terminals 96-5 to 96-24 of the LED drivers 90 (w1 to w4 and b1 to b5) are turned off by “0h” and no mask by “Fh”, respectively. It is said that.
For example, in the mask data 1, the LED driver 90 (w1 to w4) in the frame driver unit 61 is “0000... 00 (h)” and the output terminals 96-5 to 96-24 are turned off. Is set for the LED drivers 90 (b1 to b5) of the panel driver unit 62, and "FFFF... FF (h)" and no output masks are set for the output terminals 96-5 to 96-24. ing. That is, the data specifies that only the decorative lamp 20w on the frame side is masked. (Note that the mask data 4 and 5 are not shown with data values)

In steps S706 and S707 in FIG. 20, an address corresponding to the lamp channel dwCHn being processed is specified in the lamp data table and the mask data table.
Subsequently, in step S708, the effect control CPU 200 obtains a timer (frame) of the corresponding line (the line indicated by the execution line (offset) of the current target lamp channel dwCHn) in the lamp data table, and substitutes it for the variable Dtime. .

  In step S709, the effect control CPU 200 develops the corresponding lighting data and mask data specified in steps S706 and S707, and generates LED drive data. Although this process will be described later, the lighting data and mask data for the lamp channel dwCHn currently being processed are reflected in the LED drive data to be output.

In step S710, the execution time (time), which is information of the ramp channel dwCHn, is incremented by one.
In step S711, the variable Dtime is compared with the execution time (time). The timer (frame) of the currently executing line is assigned to the variable Dtime. The execution time (time) is incremented by 1 in step S710 for each LED drive data update process (every 16 ms). Therefore, if Dtime ≦ time, the current line end timing is reached. If Dtime ≦ time is not satisfied, it is determined that the end of the current line has not yet been reached, and the process proceeds from step S711 to S719. If Dtime ≦ time, the process proceeds from step S711 to S712 as the end of the current line.
The effect control CPU 200 resets the execution time (time) to 0 in step S712. In step S713, the execution line (offset) value is incremented by one. In other words, the next line is targeted.
In step S714, the effect control CPU 200 specifies the address of the lamp data table corresponding line corresponding to the execution line (offset). In steps S715 and S717, it is confirmed whether an end code (D_DTEND) or a loop code (LMP_LP) is described in the line.
If the end code (D_DTEND) is described, the registered lighting number of the lamp channel dwCHn is updated to 0 in step S716. In other words, it indicates that the processing corresponding to the registration of the lamp channel dwCH is completed on the work.
If the loop code (LMP_LP) has been described, the value of the execution line (offset) is updated to the loop destination address in step S718.

In step S719, the effect control CPU 200 calculates the checksum of the LED drive data at the time of the lamp channel dwCHn. In step S720, the backup data is saved.
This completes the LED data update for one lamp channel dwCHn. As the loop processing LP2, the above processing is sequentially performed up to the ramp channels dwCH0 to dwCH15.

The LED output data is updated in each lamp channel dwCHn in step S709, and this is the following process.
The output data buffer that generates the LED drive data by expanding the lighting data and the mask data corresponds to each of the LED drivers 90 (w1 to w4, b1 to b5), similarly to the lamp data table and the mask data table. Prepared. For example, an information area of (4 × 24) bits corresponding to one LED driver 90 is provided for each of, for example, nine LED drivers 90 (w1 to w4, b1 to b5). In this case, the output data buffer is a 9 × (4 × 24) bit buffer area.

For such an output data buffer, in step S709, a process of developing the mask data with AND (logical product) and developing the lighting data with OR (logical sum) is performed. This is sequentially performed in step S709 for each of the lamp channels dwCH0 to dwCH15 by loop processing (LP2).
For example, at the time point t0 shown in FIG. 21, the output data buffer is AND-expanded with the mask data of the lamp data 2 (see FIG. 22: no mask), and the lighting data of the third line of the lamp data 2 is OR-expanded. After the state, the mask data of the lamp data 5 (see FIG. 22: center case mask) is AND expanded, and the lighting data of the second line of the lamp data 5 is OR expanded.
As described above, in the mask data, 0h (= 0000) is extinguished and Fh (= 1111) is no mask. Therefore, expanding the mask data with AND means that the bit to be extinguished (masked) is set to “0” in the output data buffer value up to that point, and the bits not masked are not changed.
Further, when the lighting data is expanded OR, the lighting data of the lamp channel dwCH being processed is reflected in the output data buffer after masking.
By sequentially performing this process for the lamp channels dwCH0 to dwCH15, the LED drive data that is prioritized for the higher-numbered lamp channels is formed on the output data buffer.

  The LED drive data generated by the LED data update process as described above is actually sent to each LED driver in step S205 (in the above cases 12 to 15) of the 1 ms timer interrupt process described with reference to FIG. In this way, a lamp effect operation according to the scenario data is realized.

In the present embodiment, in the LED data update process described above, the effect control CPU 200 registers and lights the designated value (lamp number) of the effect operation information (lighting pattern) to be executed in the lamp channel dwCH of the lamp data registration information. The number is managed as a number (lmpNew), and the designated value (ramp number) of the performance operation information being executed is managed as the execution lighting number (lmpNo).
By doing in this way, the lighting pattern to be executed and the lighting pattern being executed (during the LED drive data update process in steps S706 to S718) on each lamp channel dwCH of the lamp data registration information can be easily performed. Can be managed and distinguished.

In the case of this example, specifically, a process of registering the designated value (lamp number) of the rendering operation information selected based on the control command as the registered lighting number (lmpNew) is performed in step S653 of FIG. 15B. Then, at the start of execution of the process according to the presentation operation information (lighting pattern) registered in the lamp data registration information as the registered lighting number (lmpNew), the execution lighting number (lmpNo) is set in steps S702 to S704 in FIG. By substituting the value of the registered lighting number (lmpNew), the lamp number of the lighting pattern being executed is managed as the execution lighting number (lmpNo).
By such processing, the registered lighting number (lmpNew) and the execution lighting number (lmpNo) on the workpiece can be easily processed, and the processing load of the production control CPU 200 can be reduced. In step S705, the processing is branched with reference to the execution lighting number (lmpNew), and redundant processing can be avoided.
If the registered lighting number (lmpNew) and the execution lighting number (lmpNo) do not match in step S702, a process of substituting the value of the registered lighting number (lmpNew) for the execution lighting number (lmpNo) in step S703 is adopted. By doing so, the execution lighting number (lmpNo) can be updated without referring to information other than the lamp data registration information, which is also effective in reducing the processing burden.
In this way, the processing load of the effect control CPU 200 is reduced.

[4-7: Sound registration processing]

Next, the sound registration process executed as step S635 in FIG. 15 will be described.
This sound registration processing is processing for registering information corresponding to the description content (subscenario data) of the sound / motor sub-scenario table illustrated in FIG. 19B in the sound channel aCH of the sound data registration information of FIG.

FIG. 24 shows a sound registration process.
First, the effect control CPU 200 determines in step S800 whether sound data exists in the sound / motor sub-scenario table. That is, it is determined whether any information of BGM / SE1 / SE2 / error sound / sound control exists as description information of the corresponding line of the sub-scenario number in the sound / motor sub-scenario table.
If these sound data do not exist, the process ends.

On the other hand, if any of these sound data exists, the effect control CPU 200 determines whether or not it is BGM in step S801. If the sound data is BGM, the effect control CPU 200 sets the sound data of the sound / motor sub-scenario table to the sound channel aCH0 in step S802. That is, the BGM information described in the corresponding line of the sub-scenario number in the sound / motor sub-scenario table is registered in the sound channel aCH0 as the sound channel aCH associated with the BGM in the sound data registration information.
As described above, when the sound data is BGM, SE1, SE2, and error sound, the description content (that is, scenario data) includes at least the phrase number of the phrase to be reproduced, information on the primary volume, and loop reproduction. And information regarding the presence / absence of stereo playback are included, and thus these pieces of information are registered in the sound data registration information.
Note that BGM, SE1, and SE2 can be played back in stereo, and in that case, the instruction is given by the information of BGM, SE1, and SE2 in the sound / motor sub-scenario table. For example, when BGM is reproduced in stereo, not only the sound channel aCH0 but also the sound channel aCH1 is used. In this case, among the sound channels aCH0 and aCH1, the phrase number described in the BGM information is registered as the phrase number (frzHi, frzLo) in the even channel sound channel aCH0, and stereo (frzSt) information is registered. “1” is described. When loop playback is performed, “1” is described as loop (frzLp) information.

  If BGM sound data is set in step S802, or if the sound data is not BGM in step S801, the effect control CPU 200 determines whether or not the sound data is an error sound in step S803. In this case, the sound data of the sound / motor sub-scenario table is set to the sound channel aCH15 in step S804. That is, information corresponding to the description content of the sub-scenario data is registered in the sound channel aCH15 as the sound channel aCH corresponding to the error sound.

When the sound data of the error sound is set in step S804, or when the sound data is not an error sound in step S803, the effect control CPU 200 determines whether the sound data is SE1 in step S805, and is SE1. In this case, the SE1 setting process is performed in step S806.
If the SE1 setting process is executed in step S806, or if the sound data is not SE1 in step S805, the effect control CPU 200 determines in step S807 whether the sound data is SE2 and is SE2. In this case, the SE2 setting process is performed in step S808.
Further, when the SE2 setting process is executed in step S808, or when the sound data is not SE2 in step S807, the effect control CPU 200 determines whether or not the sound data is sound control in step S809. If there is, sound control setting processing is performed in step S810.
When the sound control setting process is executed in step S810, or when the sound data is not sound control in step S805, the effect control CPU 200 ends the process shown in FIG.

  The contents of the SE1 setting process, SE2 setting process, and sound control setting process executed in steps S806, S808, and S810, respectively, will be described individually.

First, the contents of the SE1 setting process and SE2 setting process executed in steps S806 and S808, respectively, will be described with reference to FIG.
The contents of the SE1 setting process and SE2 setting process are the same except that the sound channel aCH (corresponding sound channel aCH) to be registered for the sound data is different. And

First, the effect control CPU 200 acquires the reproduction state of the corresponding sound channel aCH in step S901. As described above, in the present embodiment, the correspondence of the sound channel aCH to be registered is determined for each sound type. In the case of SE1, the sound channels aCH2 to aCH9 are set, and in the case of SE2, the sound channels aCH10 to aCH14 are set. Are the corresponding sound channels aCH.
Therefore, the process of step S901 is a process of acquiring the playback state of the sound channels aCH2 to aCH9 when executed as the SE1 setting process (S806), and the sound channel when executed as the SE2 setting process (S808). This is a process of acquiring the playback state of aCH10 to aCH14.
Acquisition of the reproduction state of each sound channel aCH, that is, acquisition of information on whether or not a phrase is being reproduced, is performed by acquiring the value of a reproduction state information storage register provided for each sound channel aCH in the sound source IC 59. .

Next, in step S902, the effect control CPU 200 sets the set sound channel aCH as the start sound channel aCH. Here, the set sound channel aCH means a sound channel aCH that is a target of sound data registration. The start sound channel aCH means the sound channel aCH having the smallest channel number among the corresponding sound channels aCH, and corresponds to aCH2 in the case of SE1 and aCH10 in the case of SE2.
In step S902, the set sound channel aCH is set as the start sound channel aCH in order to search for an empty channel in order from the start sound channel aCH and register SE sound data by the processing in steps S903 to S911.

In step S903, the effect control CPU 200 determines whether or not the set sound channel aCH is being reproduced. If the set sound channel aCH is being reproduced, the set sound channel aCH is incremented by 1 in step S908, and whether or not the set sound channel aCH is larger than the end channel is determined in step S909. The end channel means the sound channel aCH having the largest channel number among the corresponding sound channels aCH. Therefore, in the case of SE1, whether or not it is larger than the sound channel aCH9, and in the case of SE2, larger than the sound channel aCH14. Whether or not each is determined.
If the set sound channel aCH is larger than the end channel, the corresponding sound channel aCH is empty, and the process ends.
On the other hand, if the set sound channel aCH is not larger than the end channel, the process returns to step S903 (that is, it is determined whether or not the next sound channel aCH is being reproduced).

If it is determined in step S903 that the set sound channel aCH is not being reproduced, the effect control CPU 200 proceeds to step S904 and determines whether there is no sound data in the work of the set sound channel aCH.
If there is sound data in the set sound channel aCH, that is, if the set sound channel aCH is not empty, the effect control CPU 200 proceeds to step S908. In other words, this searches for the next empty channel in the corresponding sound channel aCH.

  On the other hand, if there is no sound data in the set sound channel aCH, that is, it is determined that the set sound channel aCH is empty, the effect control CPU 200 proceeds to step S905 and determines whether or not there is a stereo request. That is, with reference to information indicating whether or not stereo playback is included in the SE information of the table, it is determined whether or not the SE information is accompanied by a request for stereo playback. As described above, in the scenario data for requesting stereo reproduction, individual phrase numbers of Lch and Rch are not described, but one common phrase number is described.

If there is a stereo request, the effect control CPU 200 proceeds to step S906 and determines whether or not the set sound channel aCH is an even channel. If the set sound channel aCH is not an even channel, the effect control CPU 200 proceeds to step S908 and increments the set sound channel aCH by one. That is, an empty channel is searched after the next sound channel aCH.
As described above, in this example, the stereo reproduction uses the even-numbered sound channel aCHn and the next odd-numbered sound channel aCHn + 1. For this reason, continuous even / odd empty channels are searched according to scenario data requiring stereo reproduction. Therefore, if the set sound channel aCH is not an even channel in step S906, an empty channel is searched after the next sound channel aCH.
If the set sound channel aCH is an even channel in step S906, the effect control CPU 200 proceeds to step S907 and determines whether or not the next sound channel aCH of the set sound channel aCH is also an empty channel (even if it is not being played). Or not).
If the sound channel aCH next to the set sound channel aCH is not an empty channel, the process proceeds to step S908. That is, the next empty channel in the corresponding sound channel aCH is searched.
If the sound channel aCH next to the set sound channel aCH is an empty channel, the continuous even-numbered sound channel aCHn and the next odd-numbered sound channel aCHn + 1 can be used. In step S911, the sound data in the table is set in the work area corresponding to the set sound channel aCH, and the process ends. In the present embodiment, the sound data is set only to the even-numbered sound channel aCHn among the even-numbered and odd-numbered sound channels (aCHn, aCHn + 1).

When it is determined in step S905 that there is no stereo request, that is, in the case of a monaural request, the effect control CPU 200 proceeds to step S910 and confirms whether or not the current set sound channel aCH is an even channel. If it is an even channel, the process proceeds to step S911, the sound data of the table is set in the work area corresponding to the set sound channel aCH, and the process is terminated.
However, in the case of an odd channel, there is a possibility that it is an odd channel of the two sound channels (aCHn, aCHn + 1) used in stereo as described above. Since sound data is not set for the odd-numbered channels used in stereo, it is determined in step S904 that the channel is an empty channel, so it is necessary to confirm the sound channel for stereo use.
If it is determined in step S910 that the channel is not an even channel, the process proceeds to step S912 to check whether the previous even channel is being played back in monaural.
If the previous even channel is being reproduced in stereo, the current set sound channel aCH cannot be used, and the process advances to step S908.
If the previous even channel is being played back in monaural, the process advances to step S911 to set the sound data in the table in the work area corresponding to the set sound channel aCH, and the process ends.

Through the above SE setting process, the sound data of SE1 or SE2 described in the sub-scenario table is registered in an empty channel among the corresponding sound channels aCH in the sound data registration information.
Further, when the information of SE1 or SE2 requests stereo playback of a phrase, this corresponds to the case where the sound source IC 59 requests to use an even channel and the next odd channel for stereo playback. Sound data can be registered in the even channel by using the even channel and the next odd channel in the corresponding sound channel aCH. In other words, this makes it possible to perform appropriate information registration according to the specifications of the sound source IC 59.

Next, the sound control setting process executed as step S810 of FIG. 24 will be described with reference to FIGS.
FIG. 26 shows the sound control setting process in step S810.
First, the effect control CPU 200 confirms the value of the upper 1 byte of the sound control information in step S1001.

FIG. 27 shows an example of the data structure of sound control information.
In the case of the present embodiment, the sound control information is composed of 4 bytes, information (control type information) for describing the sound control content is described in the upper 1 byte, and the sound control target is described in the lower 3 bytes. Information for designating the sound channel aCH (information to be controlled) is described.
Depending on the control type information of the upper 1 byte, fade-in reproduction, fade-out reproduction, and secondary volume change instruction can be made.

As shown in the figure, as the control type information represented by the upper 1 byte, 0x20 to 0x70 are fade-type information, and 0x80 or more is secondary volume change instruction information.
Specifically, as for the fade system information from 0x20 to 0x70, 0x25 (SFO1M) is "fade-out slow mute", 0x35 (SFO2M) is "fade-out normal mute", 0x45 (SFO3M) is "fade-out mute", 0x20 (SFO1) is “fading out slowly”, 0x30 (SFO2) is “fading out normal”, 0x40 (SFO3) is “fading out quickly”, 0x50 (SFI1) is “fading in slowly”, 0x60 (SFI2) “Fade in normal” and 0x70 (SFI3) means “Fade in fast”.
Here, “slow”, “normal”, and “fast” mean the volume transition speed (speed) in the fade control. The difference between “mute” and “sound volume” for fade-out is whether or not the volume after transition is “0”.

  As the change instruction information of the secondary volume of 0x80 or higher, 0x80 (SVO8), 0x81 (SVO0), 0x82 (SVO2), and 0x83 (SVO4) are secondary volumes = 0x80 (MAX) and 0x00 (0), respectively. , 0x20, 0x40. Then, 0x90 (SVO8E) represents the secondary volume of all sound channels aCH (aCH0 to aCH14) other than the error = 0x80, and 0x91 (SVO0E) represents the secondary volume of all sound channels aCH other than the error = 0x00. .

  The lower 3 bytes of the sound control information are 0x110000 (BG_T) for sound channel aCH0 (BGM), 0x220,000 (YK1_T) for sound channels aCH2 to aCH9 (SE1), and 0x330000 (YK2_T) for sound channels aCH10 to aCH14 (SE2). ), 0x440000 (YKA_T) represents the sound channel aCH2 to aCH14 (SE1 + SE2 = all SEs), and 0x00 ---- (other) represents the sound channel aCH reproducing the phrase indicated by “----”.

  In step S1001 of FIG. 26, the production control CPU 200 confirms the value of the upper 1 byte of the sound control information having the above data structure, and the value of the upper 1 byte is less than 80h (0x80), 80h or more and less than 90h. , 90h or more is confirmed. This is equivalent to confirming whether the control type is a fade type, a simple secondary volume change instruction, or a secondary volume change instruction with designation of all sound channels aCH other than errors.

In the case of 80h or more and less than 90h, the effect control CPU 200 sets the secondary volume of the sound channel aCH indicated by the lower 3 bytes of the sound / motor sub-scenario table (sound control information) to the volume value indicated by the upper 1 byte in step S1002. To finish the process.
If it is 90h or more, the effect control CPU 200 sets the secondary volume of the sound channels aCH0 to aCH14 to the volume value indicated by the upper 1 byte in step S1003 and ends the process.

  On the other hand, if the upper 1 byte is less than 80h, the effect control CPU 200 performs the process of converting to control data corresponding to the value of the upper 1 byte in step S1004, and then in step S1005 the sound / motor sub-scenario table ( The converted control data is set in the work area corresponding to the sound channel aCH indicated by the lower 3 bytes of the sound control information), and the process ends.

  Here, the fade-type control information whose upper 1 byte is less than 80h is information for identifying only the difference in the control type such as “fade out slowly mute” or “fade in quickly”. Therefore, the information of the control type of the upper 1 byte is converted into information that allows the sound source IC 59 to execute the corresponding operation in step S1004.

FIG. 28A shows the contents of the conversion process in step S1004 of FIG.
First, the effect control CPU 200 acquires a 2-byte value corresponding to the higher-order 1-byte value from the conversion table in step S1101. In step S1102, a 2-byte value is acquired based on the lower 3 bytes.
In step S1103, the 2-byte values acquired in steps S1101 and S1102 are concatenated.

FIG. 28B is an explanatory diagram of the acquisition process of steps S1101 and S1102 described above.
First, in the acquisition process of step S1101, a conversion table storing the corresponding value (2 bytes) for each value (0x25 to 0x70) of the upper 2 bytes of the fade system is used as shown in the figure. The effect control CPU 200 refers to the conversion table and acquires a 2-byte value corresponding to the higher-order 1-byte value.
In the acquisition process in step S1102, the control target is other than SE1 and SE2 (that is, other than aCH2 to aCH14: other than the warning sound) and SE1 and SE2 based on the value of the lower 3 bytes of the sound control. , 2 byte values as shown in the figure are acquired. That is, it is 0xD000 in cases other than SE1 and SE2, and 0xC000 in cases of SE1 and SE2.
As will be described later, the acquisition value differs depending on whether the control target is either SE1 or SE2 or not, because the fade control is set to monaural only for SE1 and SE2. Because.
The 2-byte values thus obtained are concatenated in step S1103 to obtain 4-byte control data.

FIG. 28C illustrates the correspondence between the sound control fade system information and the control data obtained by the conversion processing of FIG. 28A according to the information content (value).
Here, in this embodiment, the control data of a total of 4 bytes obtained by the conversion process of FIG. 28A is set (registered) as it is in the sound data registration information. In this sense, in the figure, the control data obtained by the conversion process of FIG. 28A is indicated as “data to be set in the sound data registration information”.
According to FIG. 28C, for information about the fade sound control, for example, the upper 1 byte = SFO1M (fading out slowly mute) and the lower 3 bytes = BG_T, the control data of “0x2000D000” is obtained by the above conversion process. It turns out that it is converted. Also, for example, the sound control information in which the upper 1 byte = SFO3M (fading out quickly mute) and the lower 3 bytes = YK1_T is converted into control data “0xFF00C000”.

Referring to FIG. 17, in the sound data registration information, the first byte is “primary volume transition amount”, the second byte is “primary volume”, the third byte is “transition amount change”, “volume change”, and “phrase change”. “Stereo” “Loop” (1 bit each so far) and “Phrase number hi” (3 bits), and the fourth byte is “Phrase number low”.
As described above, in the present embodiment, the converted control data is set as it is in the sound data registration information, so, for example, according to the control data (0x2000D000) of the sound control information of SFO1M + BG_T described above, the registered content of the sound data registration information is ,
“Primary volume transition amount” = “0x20”
“Primary volume” = “0x00”
“Transition amount change” = “1”
"Volume change" = "1"
“Phrase change” = “0”
"Stereo" = "1"
"Loop" = "0"
“Phrase number hi” = “000”
“Phrase number low” = “0x00”
It becomes.
For example, according to the control data (0xFF00C000) of the sound control information of SFO3M + YK1_T described above, the registration content of the sound data registration information is
“Primary volume transition amount” = “0xFF”
“Primary volume” = “0x00”
“Transition amount change” = “1”
"Volume change" = "1"
“Phrase change” = “0”
"Stereo" = "0"
"Loop" = "0"
“Phrase number hi” = “000”
“Phrase number low” = “0x00”
It becomes.

  When the control target is other than SE1 or SE2 as in the former example, “1” (stereo) is set to “stereo”, and the control target is SE1 (same for SE2) as in the latter example. In this case, “0” (monaural) is set in “stereo”. As understood from this point, monaural designation for the above-described SE fade control is realized.

As described above, in the present embodiment, for fade type sound control information, information indicating only the difference in fade control is described as the control type information, and this is converted by the above conversion processing. Thus, the data is converted into data that can be registered in the sound data registration information (that is, data required for the sound source IC 59 to execute the fade control).
Here, fade control such as “slow mute fade out” and “fast fade in” can be realized by preparing sub-scenario data that gradually changes the volume over time. Will hold sub-scenario data for each hour, which requires more memory capacity. On the other hand, according to the present embodiment that performs the conversion processing as described above, the sub-scenario data may simply describe information representing only the difference in fade control such as “fade out slowly mute” and “fade in fast”. The number of sub-scenario data required for a kind of fade control can be reduced to one, and as a result, the memory capacity for holding the sub-scenario data can be reduced.

Further, if the conversion process as described above is performed, even if the specification of the sound source IC 59 is changed, it can be handled only by changing the contents of the conversion table shown in FIG. 28B. There is no need to rewrite or rewrite the program. Therefore, it is possible to flexibly cope with a change in the specification of the sound source IC 59 and to reduce a work load for dealing with a change in the specification of the sound source IC 59.
Also, when a specific volume transition amount or the like is changed as a fade-in / out, it is only necessary to change the contents of the conversion table shown in FIG. 28B. Similarly, the sub-scenario data is rewritten or the program is rewritten. It is possible to reduce the work burden associated with the change.

Here, referring to FIG. 29, an example of use of fade-type sound control information will be described.
In the example of FIG. 29, as sub-scenario data of sound / motor sub-scenario number 001 in the sound / motor sub-scenario table, BGM is faded in the form of “fading out quickly, small sound” (SFO3 + BG_T) at time = 0. , Start playback of SE1 phrase 0001 at volume 0x80 at time = 0, start stereo playback of phrase 0002 at SE1 at volume 0x80 at time = 2000, and “fade in slowly” BGM at time = 5000 ( The case where information to be faded in the form of (SFI1 + BG_T) is described.
As also shown in the figure, the phrase end timing is the time when the sound data as the phrase ends.

The scenario update process, the sub-scenario update process, and the sound data registration process described with reference to FIGS. 14, 15, and 24 to 28 are executed, so that first, the sound control information described in the time = 0 line ( Control data corresponding to SFO3 + BG_T) and SE1 information (0x00806001) described in the time = 0 line are set in the sound data registration information. For confirmation, according to the processing shown in FIGS. 14, 15, and 24, the data described in the same time = 0 line is set at once for the sound data registration information. (It is set at a time in the “sound registration process (S635)” of FIG. 15).
By the sound reproduction process (S111) in the main process of FIG. 8, the information set in the sound data registration information is sequentially output to the sound source IC 59, and the sound output according to the sub-scenario data is realized. As a result, BGM fade-out and phrase 0001 reproduction as shown in the lower part of the figure are realized.

In response to time = 2000, SE2 information (0x00807002) described in the line of time = 2000 is registered in the sound data registration information, and this registration information is stored in the sound source IC 59 in the sound reproduction process in step S111. Are sequentially output, the reproduction of the phrase 0002 is started from time = 2000 as shown in the lower part of the figure.
Further, when time 5000 is reached, control data corresponding to the sound control information (SFI1 + BG_T) described in the line of the time = 5000 is registered in the sound data registration information, and this registration information is stored in step S111. By sequentially outputting to the sound source IC 59 in the reproduction process, BGM fade-in at time = 5000 as shown in the figure is realized.

Here, depending on the information of the sound control, as described with reference to FIG. 27, it is also possible to give an instruction to change the secondary volume of the phrase reproduced on the designated sound channel aCH.
An example of volume control based on a secondary volume change instruction will be described with reference to FIG.
FIG. 30 is an explanatory diagram of a control example in which a predetermined type of sound is muted by the secondary volume. Specifically, when a scenario for reproducing the phrase 0010 of SE1 is registered during BGM reproduction, An example in which BGM is muted by the next volume is shown.
In this example, there are two lines of time = 0 in the sub-scenario table, and “SVO0 + BG_T” (see FIG. 27) is described as sound control information in one line of time = 0. The other time = 0 line describes “0x0080700A” (stereo reproduction of phrase 0010 with primary volume 0x80) as SE1 information.
When there are two lines having the same time as described above, the description information of these lines is sequentially converted into the sound data registration information by the processing shown in FIGS. 14, 15, and 24. Will be registered. In response to these pieces of registration information, mute by the secondary volume of BGM as shown in the figure and playback of the phrase 0010 as SE1 are started corresponding to time = 0.
In the example of this figure, “SVO8 + BG_T” (secondary volume = 0x80) is described as the sound control information in the line of time = 5000, and as a result, the BGM mute state is canceled after time = 5000 as shown in the figure. Is done.

  As described above, according to the present embodiment in which the secondary volume of the designated sound channel aCH can be changed by the sound control information, when a certain type of sound is being reproduced, the priority is high later. When another sound is to be reproduced, it is possible to easily reproduce and output a high priority sound without giving an instruction to stop the reproduction of the sound being reproduced. Therefore, sound priority control can be easily realized.

Here, the priority control for BGM and other sounds has been exemplified above, but in this embodiment, the sounds as SE are classified into SE1 and SE2, that is, SE1 and SE2 are separated into separate sounds. Therefore, for these SE1 and SE2, sound priority control can be realized by controlling the secondary volume based on sound control information.
As described above, the classification of SE1 and SE2 is classified according to the appearance frequency of the effect. Therefore, in the case where the sound of SE1 having a lower appearance frequency (higher reliability) is to be reproduced later while the sound of SE1 having a higher appearance frequency (that is, low reliability) is being reproduced, FIG. By controlling the secondary volume based on the sound control information as in the example, SE1 being reproduced can be muted, and SE2 can be preferentially output.

In addition, since the volume control can be performed not only by the primary volume but also by the secondary volume, the mute control as shown in FIG. 30 can be appropriately realized.
Here, when the BGM mute control as shown in FIG. 30 is to be realized using only the primary volume, for example, by performing fade-out with the transition speed as fast as possible based on the sound control information, during playback. It is conceivable to silence the BGM.
However, as described above, the primary volume is a volume value that is set in the sound source IC 59 together with the phrase number when the reproduction of the phrase is started. For this reason, even if the sound is silenced by the primary volume using the sound control information as described above, the timing (X) in FIG. If the start of BGM playback is newly instructed by another scenario at the previous timing), the BGM volume is set to a required volume other than 0x00 at the time of the “X”, and the BGM is emitted. End up.
On the other hand, according to the present embodiment in which the volume control by the secondary volume is also possible, as described with reference to FIG. 30, once the secondary volume of the BGM is controlled to 0x00 by the sound control information, Even if a new BGM playback is started before the sound control for returning the secondary volume is performed and the primary volume is set to a volume other than 0x00, the output volume can be maintained at 0x00. . Thereby, the sound volume control as shown in FIG. 30 can be appropriately realized.

[4-8: Sound reproduction processing]

Next, the sound reproduction process executed as step S111 in FIG. 8 will be described.
As described above, the sound reproduction process is a process for causing the sound source IC 59 to perform sound output based on information set in the work as sound data registration information.

FIG. 31 is an explanatory diagram of sound reproduction processing.
First, the effect control CPU 200 performs steps S1200 to S1220 for each of the sound channels aCH0 to aCH15 of the sound data registration information as the loop process LP3. Hereinafter, the sound channel aCH to be processed will be described as “aCHn”.

In step S1200, the effect control CPU 200 confirms the volume MAX error flag. Note that the volume MAX error flag is a flag set in the error processing (see FIG. 8) in the previous step S106. As described above, 0x5A indicates that a volume MAX error is occurring, and 0x00 is occurring. It represents that it is not.
If the volume MAX error flag is 0x5A, the process proceeds to step S1221, and the secondary volume of the work is rewritten to sound channel aCH0-14 (other than error sound) = 0x00, sound channel aCH15 (error sound) = 0x80, and step S1201 is performed. move on.
On the other hand, if the volume MAX error flag is 0x00, the process proceeds to step S1201 without rewriting the secondary volume of the work in step S1221.

In step S1201, the effect control CPU 200 outputs the value of the secondary volume to the target sound channel aCHn. That is, the value of the secondary volume set in the sound channel aCH of the sound data registration information is output to the secondary volume register for the sound channel aCHn in the sound source IC 59.
As described above, the value of the secondary volume is normally set in the all sound channel aCH of the sound data registration information as a value corresponding to the state of the volume switch. Alternatively, as a scenario, when the sound control information for instructing the change of the secondary volume of a certain sound channel aCH is described, the value of the secondary volume described in the sound control information is the sound data. It is set to the sound channel aCH indicated by the sound control information in the registration information. If the volume MAX error is occurring, “0” is set for the sound channel aCH0 to 14 and the MAX value is set for the sound channel aCH15 by the process of step S1221.

  Next, the effect control CPU 200 outputs the value “0x00” to the SUB volumes 0 and 1 in step S1202. That is, the value “0x00” is output to each register of “SUB volume 0” and “SUB volume 1” of the sound channel aCHn. As described above, the SUB volume is not used in this embodiment.

  In step S1203, the effect control CPU 200 determines whether there is sound data (sound data other than the secondary volume) in the work sound channel aCHn. If there is no sound data, the process for the sound channel aCHn ends.

On the other hand, if there is sound data, the process proceeds to step S1204 to determine whether or not it is a replacement request.
In this embodiment, a phrase replacement request can be made using the value of the upper 2 bytes (“primary volume transition amount” and “primary volume”) of the sound data registration information shown in FIG. ing. Specifically, if the upper 2 bytes of the sound data registration information is a predetermined value (for example, “0x5A5A” in this example), it is interpreted as a phrase replacement request.
In step S1204, it is determined whether or not it is a phrase replacement request by determining whether or not the upper 2 bytes of the data set in the sound channel aCHn is a predetermined value “0x5A5A”.

If it is a replacement request, the effect control CPU 200 rewrites the phrase number in step S1205, and proceeds to step S1206. Specifically, the phrase number is rewritten in step S1205 on the work corresponding to the sound channel aCH, the phrase number hi (frzHi), the phrase number low (frzLo), the primary volume (frzVl), and the phrase change (rsv0). ), Stereo (frzSt), etc. are set.
On the other hand, if it is not a replacement request, the process proceeds to step S1206 without going through step S1205.

In step S1206, the effect control CPU 200 determines whether there is a transition amount change request or a volume change request. That is, it is determined whether or not “1” is set in either the transition amount change rsv2 or the volume change rsv1 of the sound channel aCHn.
Here, the value of the transition amount change rsv2 in the sound data registration information is set to “1” when the sound registration process (S635) is executed based on the fade-type sound control information, and other than the fade-type information. In other words, “0” is set when the sound registration process is executed based on the sound control information (ie, secondary volume change instruction), BGM, SE1, SE2, and error sound information. .
On the other hand, the volume change rsv1 (whether or not to change the primary volume) is not limited to the case where the sound registration process is executed based on the fade sound control information, and the BGM, SE1, SE2, error sound information, “1” is set when the sound registration processing is executed based on the information of the fade-type sound control. Then, “0” is set when the sound registration process is executed based on the sound control information other than the fade system.
As understood from these points, not only when sound data based on fade-type sound control information is registered, but also when sound data based on BGM, SE1, SE2, and error sound information is registered. Even in the case where there is, the primary volume transition amount and the information of the primary volume are output to the sound source IC 59 by the subsequent steps S1209 or S1211.

If there is a transition amount change request or a volume change request, the effect control CPU 200 proceeds to step S1207 and determines whether or not the sound channel aCHn is stereo reproduction, that is, whether or not the value of the stereo frzSt is “1”. To do.
If the sound channel aCHn is not stereo playback, the process proceeds to step S1209 to output the primary volume transition amount and the primary volume to the sound channel aCHn of the sound source IC 59, and further output the panpot to the sound channel aCHn of the sound source IC 59 in step S1210. And go to step S1213.
Here, as the output of the pan pot, the value is output to each register of “left / right pan pot”, “left / right pan pot transition amount”, “up / down pan pot”, and “up / down pan pot transition amount” for the sound channel aCHn in the sound source IC 59. To do. For example, in the case of monaural playback, in step S1210, the left and right panpot registers are 0x40 (left and right equal volume), the left and right panpot transition amount registers are 0x00 (unused), the upper and lower panpot registers are 0x40 (upper and lower equal volumes), 0x00 (unused) is output to the pan pot transition amount register.

On the other hand, if the sound channel aCHn is stereo reproduction, the process proceeds to step S1208 to determine whether or not the sound channel aCHn is an even number.
If the sound channel aCHn is an even number, the process proceeds to step S1211, and the primary volume transition amount and the primary volume are output to the sound channel aCHn and the sound channel aCHn + 1. And proceeds to step S1213.

In this embodiment, the “left and right panpot” registers of the even-numbered sound channel aCHn and the next odd-numbered sound channel aCHn + 1 are used for the stereo reproduction instruction. Specifically, the sound source IC 59 in this case is a “left and right panpot” of the even sound channel aCHn (corresponding to the Lch side of stereo reproduction) and the next odd sound channel aCHn + 1 (corresponding to the Rch side of stereo reproduction). By setting predetermined values in the registers, the sound channel aCHn and the sound channel aCHn + 1 are configured to recognize that they are stereo reproduction. More specifically, in the sound source IC 59 in this case, “0x81” is set in the “left and right panpot” register of the even sound channel aCHn, and the “left and right panpot” register of the next odd sound channel aCHn + 1 is set. Is set to “0x82”, it is configured to recognize that the sound channel aCHn and the sound channel aCHn + 1 are in stereo reproduction.
In response to this, in step S1212, as a panpot output process for the sound channel aCHn and the sound channel aCHn + 1, “0x81” is set in the “left and right panpot” register of the sound channel aCHn, and “left and right panning of the sound channel aCHn + 1”. “0x82” is output to the “pot” register. For example, in the case of stereo reproduction, 0x81 and 0x82 (stereo) are assigned to the left and right panpot registers for the sound channels aCHn and aCHn + 1, 0x00 (unused) to the left and right panpot transition amount registers, and 0x40 ( 0x00 (unused) is output to each upper and lower panpot transition amount register.

If the sound channel aCHn is not an even channel in step S1208, the process proceeds to step S1220, the sound data of the work sound channel aCHn is cleared, and the process for the sound channel aCHn is ended.
That is, when the sound channel aCHn is stereo reproduction and is an odd channel, the phrase number is not registered in the sound channel aCHn, so the phrase number for the sound channel aCHn is output to the sound source IC 59. Instead, the registered sound data of the sound channel aCHn is cleared. Note that the primary volume transition amount and the primary volume have already been output in S1211, which is processing for the even number aCHn.
The sound source IC 59 in this case specifies the phrase data of Lch and Rch to be reproduced based on the phrase number set in the processing for the even numbered sound channel aCHn.

  If there is no transition amount change request or volume change request in the previous step S1206, the presentation control CPU 200 proceeds to step S1213 without passing through the processing of steps S1207 to S1212.

In step S1213, the effect control CPU 200 determines whether or not there is a phrase change request, that is, whether or not the value of the phrase change rsv0 is “1”.
If there is no phrase change request, the sound data of the sound channel aCHn is cleared in step S1220, and the process for the sound channel aCHn is ended. That is, when there is no phrase change request, the phrase number set in the work sound channel aCHn is not output to the sound source IC 59 (S1215).

On the other hand, if there is a phrase change request, it is determined in step S1214 whether or not the sound channel aCHn is a stereo reproduction and an odd channel. If the sound channel aCHn is a stereo reproduction and an odd channel, the sound data of the sound channel aCHn is cleared in step S1220, and the process for the sound channel aCHn is ended.
That is, when the sound channel aCHn is stereo reproduction and is an odd channel, the phrase number is not registered in the sound channel aCHn, and therefore the phrase number is not output to the sound source IC 59. The sound source IC 59 is for specifying the phrase data by the phrase number set in the processing for the even numbered sound channel aCHn.

  If it is determined in step S1214 that the sound channel aCHn is not a stereo playback and odd channel, the process proceeds to step S1215 to output a phrase number to the sound channel aCHn. That is, information on the phrase number composed of the phrase number hi and the phrase number low registered in the work sound channel aCHn is output to the blaze number register for the sound channel aCHn of the sound source IC 59.

  In the next step S1216, the effect control CPU 200 determines whether or not there is a loop request, that is, whether or not the value of the loop frzLp is “1”. If there is a loop request, the loop count 0xFF (infinite loop) is output to the sound channel aCHn of the sound source IC 59 in step S1217 and the process proceeds to step S1219. If there is no loop request, the loop count 0x00 is set to the sound channel aCHn of the sound source IC 59 in step S1218. (No loop) is output and the process proceeds to step S1219.

In step S1219, the effect control CPU 200 issues a playback output instruction for the sound channel aCHn. That is, a reproduction instruction based on the data set in the sound channel aCHn is given to the sound source IC 59.
Next, the effect control CPU 200 clears the sound data of the work sound channel aCHn in step S1220, and ends the process for the sound channel aCHn.

The effect control CPU 200 sequentially performs the processes of steps S1201 to S1220 described above from the sound channels aCH0 to aCH15 by the loop process LP3. Thereby, the sound reproduction process of step S111 is completed.
By such sound reproduction processing, sound output based on information registered in the sound data registration information is executed, and sound production according to the scenario is realized.

  Here, as described above, in the present embodiment, a stereo reproduction instruction is given to the sound source IC 59 by setting a predetermined value in the “left and right panpot” registers of the even-numbered and next odd-numbered sound channels aCH. However, this makes it possible to properly instruct stereo reproduction / monaural reproduction without providing the sound source IC 59 with a register for instructing stereo reproduction / monaural reproduction. That is, the number of registers of the sound source IC 59 can be reduced. At the same time, since the stereo reproduction / monaural reproduction instruction to the sound source IC 59 can be realized by the output process of the pan pot, it is not necessary to separately perform the stereo reproduction / monaural reproduction instruction process, and the processing load is reduced accordingly.

  By the way, in the sound reproduction process of FIG. 31, the volume MAX error flag is confirmed each time in step S1200, and if the volume MAX error is occurring, the secondary volume of the work is rewritten in step S1221. Will be described with reference to FIG.

FIG. 32 is an explanatory diagram of volume control according to the occurrence of an error.
FIG. 32A shows the state of occurrence of the volume MAX error, and the period from the time point t1 to t2 is the occurrence period of the volume MAX error as shown in the figure.
32B to 32E show cases in which phrases are played back in different playback periods, and in the case of FIG. 32B as shown in the figure, the phrase playback period is from time point t0 (time point before time point t1) to time point tn (time point). In the case of FIG. 32C, the phrase playback period is from the time point tn to the time point t3 (time point after the time point t2), and in the case of FIG. 32D, the phrase playback period is from the time point t0 to the time point t3. In the case of 32E, the phrase reproduction period is the time point tn1 to the time point tn2 (the time point between the time points t1 and tn2 between the time points t1 and tn2). In addition, the phrase said here shall mean phrases other than an error sound.
32B to 32E, it is assumed that sound control information for controlling the secondary volume of the phrase is also described as a scenario. The figure also shows the state of the secondary volume (“secondary volume state” in the figure). Note that “0x **” means a value of the secondary volume that is larger than “0x00” and smaller than “0x80”.
As described above, the value of the work secondary volume is normally set according to the state of the volume switch. In the example of this figure, it is assumed that the value corresponding to the state of the volume switch is “0x80”.

In the case of FIG. 32B, in response to the fact that the sound control information for controlling the secondary volume to “0x **” is registered in the work at the timing corresponding to the time point t0, the secondary volume of the phrase corresponds to the time point t0. The timing is lowered from “0x80” to “0x **”. If the volume MAX error does not occur, the secondary volume of the phrase is maintained at “0x **” after time t0.
However, in this case, in response to the occurrence of the volume MAX error at time t1, the secondary volume is forcibly lowered to “0x00” at the timing corresponding to time t1 as shown in the figure. This is because the value of the secondary volume other than the work sound channel aCH15 is rewritten to “0x00” in step S1221 of FIG. 31 in accordance with the occurrence of the volume MAX error.
If a volume MAX error is occurring, the rewriting process in step S1221 is performed every 16 ms. Therefore, even after time t1, the secondary volume of the work (sound channel aCH other than error sound) is set to “0x00” each time, and this is output to the sound source IC 59, so that the secondary volume is maintained at “0x00”. The
At this time, at the time tn when the reproduction of the phrase ends, the effect control CPU 200 sets a value corresponding to the state of the volume switch as the value of the secondary volume of the sound channel aCH (work) corresponding to the phrase. . Therefore, there is a concern that the mute state of the sound channel aCH is canceled at time tn. However, even in this case, the volume rewriting process in step S1221 is executed in the sound reproduction process shown in FIG. 31, that is, the value of the secondary volume of the work is just before the output of the secondary volume to the sound source IC 59. By rewriting, “0x00” can be instructed to the sound source IC 59 as the secondary volume. This reliably prevents the phrase from being emitted by setting a value greater than “0x00” as the secondary volume during the volume MAX error occurrence period.

Subsequently, in the case of FIG. 32C, the reproduction of the phrase is started at time tn after time t1 when the error occurs. In this case, the value of the secondary volume of the work is “0x80” corresponding to the volume switch state in the period up to the time t1, but in the period after the time t1, the work is performed by the process in step S1221 according to the occurrence of the error. The value of the secondary volume is rewritten to “0x00”.
Here, although not reflected in the figure, in this case, since the sound control information for controlling the secondary volume of the phrase is described as a scenario, at the time tn when the reproduction of the phrase is started, the phrase in the work The value of the secondary volume of the sound channel aCH corresponding to is set to the value indicated by the sound control information. However, in this case as well, by executing the rewriting process in step S1221 in the sound reproduction process, the value of the secondary volume that is finally output to the sound source IC 59 can be set to “0x00”. It is reliably prevented that the next volume is set to a value larger than “0x00” and the phrase is emitted.
In the case of FIG. 32C, the phrase reproduction period is also after time t2, but at time t2, the value of the secondary volume of the work is a value corresponding to the volume switch state (in this case, “0x80”). Set to At time t2, the rewriting process in step S1221 is not executed after time t2 in response to the volume MAX error flag changing to “0x00”. From these points, after time t2, “0x80” is output to the sound source IC 59, and as a result, the phrase is properly emitted after the error is resolved.

In the case of FIG. 32D, the reproduction of the phrase is started at time t0, and the secondary volume of the phrase is controlled from “0x80” to “0x **” based on the sound control information.
Also in this case, in the period t1 to t2 which is an error occurrence period, the value of the secondary volume of the work is rewritten to “0x00” every time by the process of step S1221, and thus the phrase is muted during the error occurrence period.
At time t2, the value of the secondary volume of the work is set to a value (“0x80”) corresponding to the state of the volume switch, and the volume MAX error flag changes to “0x00”. Thus, the phrase is properly emitted after time t2 when the error is resolved.

In the case of FIG. 32E, the value of the secondary volume of the work is “0x80” in the period up to the time point t1, but in the period after the time point t1 according to the occurrence of the error, the work 2 is processed by the process in step S1221. The value of the next volume is “0x00”.
In the case of FIG. 32E, the reproduction of the phrase is started at the time tn1 after the time t1, but even if the value of the secondary volume indicated by the sound control information is set to the work at the time tn1, The value of the secondary volume of the work is rewritten to “0x00” by the process of step S1221, so that the phrase is not emitted. When the phrase playback period ends at time tn2, the value of the work secondary volume is rewritten to a value corresponding to the volume switch. However, the value of the work secondary volume is changed to “ Since “0x00” is rewritten, the phrase is not emitted during the period from the time point tn2 to the time point t2.
Also in this case, at time t2, the value of the secondary volume of the work becomes a value (“0x80”) corresponding to the state of the volume switch, and the volume MAX error flag changes to “0x00” and the time t2 and thereafter. Since the rewriting process in step S1221 is not executed, the secondary volume returns to “0x80” after time t2 when the error is resolved.

In this way, the volume MAX error flag is confirmed each time in the sound reproduction processing of FIG. 31 (S1200), and if the volume MAX error is occurring, the work secondary volume is rewritten (step S1221). The sound other than the error sound can be reliably silenced during the occurrence of the volume MAX error.

[4-9: Motor registration process]

Next, a motor registration process executed as step S636 in FIG. 15 will be described.
This motor registration process is a process of registering information corresponding to the description contents (subscenario data) of the sound / motor subscenario table illustrated in FIG. 19B in the motor channel mCH of the motor data registration information (work) of FIG. 16B. It becomes.

FIG. 33A shows a motor registration process.
In this example, eight channels of motor channels mCH0 to mCH7 are prepared as motor data registration information, and a maximum of eight motors can be driven and controlled. That is, as the movable body accessory motor unit 65 shown in FIG. 3, a maximum of eight stepping motors 121 shown in FIG. 5B can be used.
MT (n) in FIG. 33A is a motor number corresponding to each of up to eight motors (n = 0 to 7). The motor numbers MT0 to MT7 assigned to the individual stepping motors 121 also correspond to the motor channels mCH0 to mCH7. Also, the total 8 bytes of “Motor 0-3” and “Motor 4-7” in the sound / motor sub-scenario table of FIG. 19B are 1 byte each, and the operation of each motor of motor numbers MT0-MT7. This indicates the pattern number. There are 255 types of operation pattern numbers from 1 to 255.
Hereinafter, the stepping motor 121 having the motor number MT (n) is referred to as “motor MT (n)”.

In the motor data registration process of FIG. 33A, the processes of steps S1501 to S1502 are performed corresponding to each motor of the motor numbers MT0 to MT7 as the loop process LP4.
In step S1501, the effect control CPU 200 confirms whether data about the motor MT (n) is described in the sound / motor sub-scenario table. Since the process of step S636 in FIG. 15 is performed in step S608 of the scenario update process in FIG. 14, step S1501 is a 1-byte “/” in the sound / motor sub-scenario table indicated by the currently referenced scenario channel sCHn. This is a process for confirming the contents of “motor n”.
If the content of “motor n” is “0”, that is, there is no description, the process proceeds to the next motor.
If the content of “motor n” is not “0” and some information, that is, an operation pattern number for motor MT (n) is described, motor operation pattern registration processing is performed in step S1502.
The above operation is repeated for the motors MT0 to MT7.

The motor operation pattern registration process in step S1502 is shown in FIG. 33B.
In step S1510, the effect control CPU 200 confirms whether or not the motor number MT (n) that is currently processed is normal. If the number is not normal for some reason, or if it is an unused motor number, the processing in step S1502 is terminated. For example, in a pachinko machine equipped with only six stepping motors 121, when the motor numbers MT6 and MT7 are not used, processing corresponding to the motor numbers MT6 and MT7 is not performed.

If the motor number is normal (valid), the effect control CPU 200 confirms in step S1511 whether or not the operation pattern number described in the sound / motor sub-scenario table is normal.
The operation pattern number corresponds to a table number stored in the non-volatile memory area of the effect control ROM 201 or the effect control RAM 202 as a motor operation table. FIG. 34 shows an example of a motor operation table. The contents of each motor operation table will be described later. FIG. 34A shows the motor operation table 1 showing the operation pattern of the motor for the initial operation, and FIG. 34B shows the motor operation pattern for the retry operation. Operation table 71, FIG. 34C shows a motor operation table 72 showing a motor operation pattern for reciprocating operation, and FIG. 34D shows a motor for performing an operation of “appearance → swing 10 times → return”. The motor operation table x which showed the operation pattern is illustrated.
For example, as described above, table data with table numbers 1, 2,... 71, 72,... X .. are prepared as motor operation tables. A series of operation patterns are defined by a plurality of entries (control items). In the sound / motor sub-scenario table, such a motor operation table is indicated as an operation pattern number as “motor n”.
Therefore, in step S1511, it is confirmed whether or not the designated operation pattern number is a number prepared as a motor operation table.
If the number is not prepared, the processing as step S1502 is finished as it is. If the operation pattern number is normal, that is, if it corresponds to the number of the prepared motor operation table, the process proceeds to step S1512.

  In step S1512, the effect control CPU 200 confirms whether or not the motor MT (n) that is the current registration processing target is in an error state. If there is an error, the processing as step S1502 is terminated. If there is no error, the process proceeds to step F1513.

In step S1513, the effect control CPU 200 sets the operation pattern number (the number of the motor operation table) described in the sound / motor sub-scenario table in the motor registration information (work). That is, in the motor registration information of FIG. 16C, the execution operation number (no) and the registration operation number (noNew) are set in the motor channel mCHn corresponding to the motor MT (n) that is the current registration process target.
In this case, the operation pattern number (the number of the motor operation table) described in the sound / motor sub-scenario table is written in the registered operation number (noNew). The execution operation number (no) is updated to the operation pattern number when it is actually executed. At this time, “0” is set.

As shown in FIGS. 33A and 33B, the motor registration process in step S636 in FIG. 15 is performed.
That is, the motor operation table number is registered in each motor channel mCH of the motor data registration information (work) according to the contents of the sound / motor sub-scenario table.

Here, the motor operation table will be described.
As illustrated in FIGS. 34A to 34D, the motor operation table is a table in which one row (one control item) is composed of three contents of an option (OPT), a speed (SPEED), and a step (STEP). It has become. Option (OPT) indicates a control type, speed (SPEED), and step (STEP) indicates an instruction value for the control content indicated by the control type.
With this structure, one row (one control item) is used as information defining one control process, and a series of operation patterns are designated in principle in such a manner that each row is processed sequentially.

As an option (OPT) indicating a control type, in this example, various operation types are defined as an operation system option indicating a control content of a motor operation and a non-operation system option indicating a control content not accompanied by a motor operation. .
In the case of the operation system option, the speed (SPEED) is an instruction value indicating the motor driving speed, and the step (STEP) is an instruction value indicating the motor operation range (the number of steps of the stepping motor).
On the other hand, in the case of a non-operating option, the speed (SPEED) is an instruction value that designates the next process, such as the next line to be moved (the number of progressing lines), the link destination, and the number of loops. Step (STEP) is not usually used.
As described above, the speed (SPEED), which is an instruction value, is shared between the operation system option and the non-operation system option, but the meaning of the instruction content is different.

  Note that the motor data registration information execution step (step) in FIG. 16C is different from the step (STEP) in the motor operation table. The execution step (step) is a variable updated in the process of FIG. 36 described later, and the step (STEP) of the motor operation table is information for specifying the number of drive steps of the motor operation.

The operating system options are as follows. The “origin SW” is an origin switch 68 for detecting the position of the movable body accessory operated by each motor.
cw_all ・ ・ ・ Forward rotation: Operates when origin SW is on / off
cw_on ・ ・ ・ Forward rotation: Stop when origin SW is on, Operation when origin SW is off
cw_off ・ ・ ・ Forward rotation operation: Operation when origin SW is on, stop when origin SW is off
ccw_all ・ ・ ・ Reverse operation: Operates when origin SW is on / off
ccw_on ・ ・ ・ Reverse operation: Stop when origin SW is on, Operation when origin SW is off
ccw_off ・ ・ ・ Reverse operation: Operation when origin SW is on, stop when origin SW is off
stop ・ ・ ・ Stop operation (no excitation)
keep ・ ・ ・ Stop operation (excitation)
cw_on2 ・ ・ ・ Forward rotation: Stop when origin SW is on, Operation when origin SW is off
cw_off2 ・ ・ ・ Forward rotation: Operation when origin SW is on, stop when origin SW is off
ccw_on2 ・ ・ ・ Reverse operation: Stop when origin SW is on, Operation when origin SW is off
ccw_off2 ・ ・ ・ Reverse operation: Operation when origin SW is on, stop when origin SW is off
cw_btn ・ ・ ・ Forward operation: Operation when the button is pressed, Stop when not pressed
ccw_btn ・ ・ ・ Reverse operation: Operation when the button is pressed, Stop when not pressed

Non-operational options include the following.
sys_ck1 ... Origin SW off: Move to the next line, Origin SW on: Move the specified number of lines (SPEED value)
sys_ck2 ... Origin SW off: Moves the specified number of lines (SPEED value), Origin SW on: Moves to the next line
sys_ck3: Origin SW off: Move to the next line, Origin SW on: Move the specified number of lines (SPEED value)
sys_ck4: Origin SW off: Moves the specified number of lines (SPEED value), Origin SW on: Moves to the next line
roop_s ・ ・ ・ Loop start point: Loop count = SPEED value
roop_e ・ ・ ・ Loop end point
link ... Link command: The link destination is the motor operation table with the number indicated in the SPEED value.
err_cnt: Error counter + 1
sys_err ・ ・ ・ No error command
sys_erc ・ ・ ・ There is an error command
nor_end ・ ・ ・ Normal end: No origin check
chk_end ・ ・ ・ End of check: Origin check is performed.

Since these options (OPT) are related to the operation of the origin switch 68, the configuration of the origin switch 68 will be described with reference to FIG.
35A and 35B schematically show the origin switch 68 provided on one movable body. Each movable body mounted in the pachinko gaming machine 1 of this example is provided with such an origin switch 68.
As shown in FIG. 35A, a shielding plate 81 is formed on a part of the rotating body 80 attached to the motor. A photo interrupter 82 in which the light emitting element D1 and the light receiving element PD are arranged to face each other as shown in FIG. 35B is used, and the shielding plate 81 can be positioned in the gap between the light emitting element D1 and the light receiving element PD. When the movable body accessory driven by the motor is within the range (within the origin) of the origin position, the shielding plate 81 is positioned in the gap between the light emitting element D1 and the light receiving element PD as shown in FIG. 35B, and the light emitting element D1. However, when the rotating body 80 is in a rotational position that is out of the origin, the shielding plate 81 is detached, and the light from the light emitting element D1 is received by the light receiving element PD.

FIG. 35C shows a circuit configuration of the origin switch 68. The light emitting element D1 (for example, a light emitting diode) emits light when a light emission driving current is supplied from the power supply Vcc line via the resistor R1.
The light receiving element PD (for example, a phototransistor) conducts in response to light reception. Therefore, a current through the resistor R2 is supplied from the power supply Vcc line when receiving light, and the collector voltage decreases. However, when light is not received, the collector voltage increases. As a result, the origin switch signal SWg extracted from the collector end is a signal that is at the H level when the motor is within the origin as shown in FIG.
In the processing based on each option (OPT) described above, it is determined whether the motor is within the origin or outside the origin based on the origin switch signal SWg, and predetermined processing is performed. Note that the origin switch ON / OFF determination used in the processing of each option (OPT) uses switch information (described later in FIG. 37) generated from this origin switch signal SWg in the actual control operation.

Returning to FIG. 34, an example of an operation pattern based on the motor operation table will be described.
In the motor operation table 1 of FIG. 34A, an operation pattern as an initial operation process is defined. This operation pattern is as follows.
In sys_ck1 (system check 1) on the first line, it is checked whether it is within the origin.
If it is within the origin, it shifts to a link (link command) of “7” destination specified by the speed (SPEED: the number of progressing lines in this case).
If it is outside the origin, the process proceeds to the second line, which is the next line. The second line is moved toward the origin by ccw_on (reverse operation). Here, by “6” designated by the speed (SPEED), one-step driving is performed “8” times indicated by the step (STEP) at 6 count intervals of the operation count (lcnt) (see FIG. 16C). Since the operation count (lcnt) is updated every 1 ms, the operation in the second row is that the stepping motor is driven to return to the origin by 8 steps at a speed of 1 step in 6 ms. Become.
Therefore, in the case of the operation system option, the time required for processing one line is SPEED × STEP × 1 ms.

  Next, it is moved toward the origin by ccw_on (reverse operation) in the third line. In the operation on the third row, the stepping motor is driven at a speed of one step every 3 ms by a number of steps twice the total number of steps. That is, the operation of returning to the origin is performed at a higher speed than the second line. Since ccw_on is stopped when the origin switch is turned on, the process on the third line ends when it is within the origin.

Since it should have returned to the origin by the above processing of the second line and the third line, it is checked whether or not it is within the origin by sys_ck1 (system check 1) on the fourth line.
If it is within the origin, the process shifts to ccw_all (reverse operation) on the sixth line of the “2” destination specified by the speed (SPEED: the number of progressing lines in this case).
If it is outside the origin, the process proceeds to the link (link command) on the fifth line, which is the next line. In the link (link command) on the fifth line, the motor operation table 71 (FIG. 34B) is designated, so the retry operation of the motor operation table 71 is executed. When the retry operation of the motor operation table 71 is normally completed (nor_end), the link (link command) on the fifth line is completed, and the process proceeds to the next sixth line.

In the sixth line, as the ccw_all (reverse operation), the stepping motor is driven to return toward the origin by 58 steps at a speed of 1 step (high speed) every 3 ms.
Further, in the next seventh line, similarly, as ccw_all (reverse operation), the stepping motor is driven to return toward the origin by 8 steps at a speed of 1 step (low speed) in 6 ms.
The sixth and seventh lines are further pushed in after confirming that they are within the origin, and this push-in action is performed in two stages from high speed to low speed.

When the origin is confirmed in the first line, or after the 6th and 7th lines are pushed in, the process proceeds to the link (link command) on the 8th line, and the speed (SPEED: link destination in this case) ) To move to the motor operation table 72 (FIG. 34C) designated by ().
In the motor operation table 72, an operation pattern as a reciprocal operation is defined. When this is normally completed (nor_end), the link (link command) on the eighth line of the motor operation table 1 is completed, and the next nine lines Go to the eyes. The ninth line is nor_end (normal end), and the initial operation process as the motor operation table 1 is ended here.

Here, the initial operation process as the motor operation table 1 has been described. However, each motor operation table specifies a necessary operation for each row as in this example, and the number of rows to be skipped according to circumstances, the link destination The operation pattern is defined as a structure in which the motor operation table number, the number of loops, etc. can be specified.
Although the description is omitted, the motor operation tables of FIGS. 34B, 34C, and 34D and many other motor operation tables not shown are also based on the option (OPT), speed (SPEED), and step (STEP) in each row. The operation is specified and a series of operation patterns is defined.

[4-10: Motor operation update processing]

In order to execute the operation of each row of the above motor operation table, the contents of each motor channel mCH are updated as needed on the workpiece motor data registration information (FIG. 16C). Specifically, the motor operation update process is performed in step S203 of the 1 ms timer interrupt process in FIG. The motor operation update process in step S203 will be described with reference to FIGS.
In the following explanation, the data described in the option (OPT) of the motor operation table is “D_OPT”, the data described in the speed (SPEED) is “D_SPEED”, and the data described in the step (STEP) is “ D_STEP ”.

As the motor operation update process of FIG. 36, the effect control CPU 200 repeats the processes of steps S1601 to S1623 for each of the motors MT (n) (n = 0 to 7) as the loop process LP5.
As described above, since the motors MT0 to MT7 correspond to the motor channels mCH0 to mCH7 of the motor data registration information, the loop process LP5 is a process performed for each of the motor channels mCH0 to mCH7. Hereinafter, the motor channel to be processed at that time will be described as “mCHn”.

In step S1601, the effect control CPU 200 confirms whether or not the execution operation number (no) and the registered operation number (noNew) in the target motor channel mCHn match.
At the time when the motor operation pattern is first registered in the motor channel mCHn, as described in step S1513 in FIG. 33, the operation pattern number is substituted into the registration operation number (noNew), but the execution operation number (no) = 0. That is, after registration, the execution operation number (no) and the registration operation number (noNew) do not match until processing of the motor channel mCHn is started.
If they do not coincide with each other, the operation is started. In step S1602, the excitation output data corresponding to the motor channel mCHn is cleared, and in step S1603, the value of the registered operation number (noNew) is substituted into the execution operation number (no).
In step S1604, the production control CPU 200 performs an operation count (lcnt), an operation line (ofset), an execution step (step), a loop start point (roopAddr), a loop count (roopCnt), and a parent number (retNo) for the motor channel mCHn. The return address (retAddr) and error counter (errCnt) are set to 0, respectively. Further, the value of “5A” indicating the parent is set in the attribute of the parent (migration source) / child (migration destination).
If the execution operation number (no) and the registered operation number (noNew) match in step S1601, the processing in steps S1602 to S1603 has already been performed in the past, so these processes are unnecessary. is there.

Subsequently, in step S1605, the effect control CPU 200 confirms whether or not the motor MT (n) currently being processed is in an error state. If there is an error, the excitation output data corresponding to the motor channel mCHn is cleared in step S1606. The excitation output data will be described later with reference to FIGS. 43 and 44, and is motor drive data output to the LED driver 90 to which the stepping motor 121 is connected.
The excitation output data is set in the excitation output data buffer as 4-byte data for each motor channel mCH, and is transmitted to the LED driver 90 by serial data transmission. In step S1606, the processing is to clear the 4-byte data corresponding to the motor channel mCHn on the excitation output data buffer.

  If it is determined in step S1605 that the state is not an error state, in step S1607, the effect control CPU 200 confirms whether or not the value of the execution operation number (no) is within the normal range. The normal range is a range of numbers that are valid (exist) as motor operation table numbers. The registration operation number (noNew) and the execution operation number (no) are “0” when not registered, and any one of the motor operation table 1 to the final number is substituted in the motor registration described above. Therefore, when the value is “0” or a value exceeding the final number, it is abnormal. This is a state where an unknown motor operation table is designated or the motor channel mCHn is unregistered (empty channel). In step S1607, it may be determined whether the registration operation number (noNew) is within the normal range.

If the value of the execution operation number (no) is abnormal, the process proceeds to step S1620.
In step S1602, the effect control CPU 200 clears the excitation output data corresponding to the motor channel mCHn. In step S1621, the execution operation number (no) and the registered operation number (noNew) are set to “0”. Then, input update processing is performed in step S1622, and switch information creation processing is performed in step S1623. The input update process and the switch information creation process will be described in the description of steps S1613 and S1614 (FIG. 37).

If the value of the execution operation number (no) is normal, the effect control CPU 200 proceeds to step S1608, and obtains the motor operation table data corresponding to the motor MT (n), the execution operation number (no), and the operation line (ofset). get.
That is, data “D_OPT”, “D_SPEED”, and “D_STEP” in the row indicated by the operation line (ofset) in the motor operation table indicated by the execution operation number (no) are acquired. First, since the operation line (ofset) is set to 0 in step S1604, data “D_OPT”, “D_SPEED”, and “D_STEP” in the first row of the designated motor operation table are acquired. For example, if the execution operation number (no) is set to 72, “cw_off”, “6”, and “8” in the first row of the motor operation table 72 in FIG. 34C are acquired as “D_OPT”, “D_SPEED”, and “D_STEP”. become.

In step S1608, the effect control CPU 200 determines whether the data “D_OPT” is data of an operation system option or data of a non-operation system option, and branches the process.
If it is non-operating system option data, in step S1619, processing corresponding to the non-operating system option (described later) is performed.
If it is operation system option data, the processing of steps S1610 to S1618 is performed.

If it is the data of the motion system option, first in step S1610, the effect control CPU 200 confirms whether or not it is the update timing of the excitation output data. This is determined by comparing the value of the operation count (lcnt) with the value of “D_SPEED”.
As described above, in the case of the operation system option, the value of “D_SPEED” indicates an interval of one-step driving of the stepping motor. If “D_SPEED” = 6, one-step driving is performed once every six times. The operation count (lcnt) is a value that is first set to “0” in step S1604 and then incremented in step S1616, which will be described later, that is, incremented by 1 for each 1 ms timer interrupt process.
Therefore, when the operation count (lcnt) = “D_SPEED” −1, the excitation output data update timing is reached.

If the excitation output data update timing has not been reached, the process proceeds to step S1616, the operation count (lcnt) is incremented, the processing of the current motor channel mCHn is terminated, and the processing of the next motor channel mCH is started as loop processing LP5.
If it is the update timing of the excitation output data, the effect control CPU 200 proceeds to step S1611 and increments the execution step (step) by 1 on the motor data registration information. The execution step (step) is a variable for counting whether or not the number of steps indicated by “D_STEP” acquired from the motor operation table has been reached.
Next, in step S1612, the effect control CPU 200 performs processing (described later) according to the operation system option indicated by “D_OPT”.

Subsequently, the effect control CPU 200 performs input update processing in step S1613 and switch information creation processing in step S1614 as processing relating to the origin switch.
These processes are shown in FIG.
FIG. 37A shows the input update process. In step S1631, the effect control CPU 200 first checks whether the input information matches the origin switch signal SWg.
The origin switch signal SWg is a signal obtained from the origin switch 68 as described with reference to FIG. 35C. The input information is information acquired by the effect control CPU 200 in synchronization with the switch count interval.
FIG. 37C shows a signal waveform. The switch count is a variable that is updated at an interval T. The interval T is “D_SPEED” × 1 ms during motor operation and 1 ms when the motor is stopped.

The reason why the input information does not match the origin switch signal SWg in step S1631 is when an edge occurs in the origin switch signal SWg within the interval T.
When an edge occurs, that is, when the origin switch signal SWg changes, the effect control CPU 200 substitutes the value of the origin switch signal SWg for input information in step S1632. In step S1633, the switch count = 0.
On the other hand, when the input information matches the origin switch signal SWg in step S1631, it is after the latest change in the origin switch signal SWg has already been reflected in the input information. In this case, if the switch count is not FFh in step S1634, the switch count is incremented by 1 in step S1635. If switch count = FFh, the switch count is not updated. Therefore, the value of the switch count takes a value from 00h to FFh.

Thus, if the input update process of step S1613 is performed as the process of FIG. 37A, the production control CPU 200 subsequently performs the process of FIG. 37B as the switch information creation process of step S1614.
First, in step S1641, it is confirmed whether or not the input information matches the switch information. The switch information is information that the effect control CPU 200 actually confirms as information on the origin switch 68.
If the input information matches the switch information, the input information is already reflected in the switch information and no particular processing is performed.
If the input information does not match the switch information, it is checked in step S1642 if the switch count exceeds the update timing. If it has exceeded, the switch information is updated in step S1643. That is, the value of input information is substituted into switch information.

The update timing here is a value set to prevent chattering, and in FIG. 37C, an example of update timing = “3” is used. Therefore, the switch information is updated when the switch count = 4.
In other words, in this case, when the information is maintained four times continuously after the input information changes, it is considered that the origin switch has changed. By such processing, chattering generated by the origin switch 68 prevents the information (= switch information) indicating whether or not the origin is confirmed by the effect control CPU 200 from becoming unstable, and makes accurate origin determination. To be able to do that.
The processes in steps S1622 and S1623 in FIG. 36 are the same as above.

After performing the above processing in steps S1613 and S1614 in FIG. 36, the effect control CPU 200 confirms in step S1615 whether or not the specified number of times of motor driving has been performed. That is, the value of “D_STEP” is compared with the execution step.
Unless “D_STEP” ≦ the execution step (step), the motor drive operation specified in the current row of the motor operation table has not yet been completed, so the process proceeds to step S1616 and the operation count (lcnt) is set. Increment, finish processing of the current motor channel mCHn, and proceed to processing of the next motor channel mCH as loop processing LP5.
If “D_STEP” ≦ execution step (step), the motor drive operation specified in the current row is complete, so the process proceeds to step S1617, where operation count (lcnt) = 0, execution step (step). In step S1618, the operation line (ofset) is incremented by 1 to perform processing for the next line.
The above is performed for each motor channel mCHn.

  As processing corresponding to the operation system option in step S1612, processing corresponding to main ones described in “D_OPT” will be described with reference to FIGS. This will be described with reference to FIG.

FIG. 38A shows a case where “D_OPT” = cw_all (forward rotation operation).
The effect control CPU 200 sets excitation output data corresponding to the excitation counter (tcnt) in step S1651. In step S1652, the value of the excitation counter (tcnt) in the motor data registration information (FIG. 16C) is incremented by one.
This cw_all is optional data that performs forward rotation regardless of whether the origin switch is on or off. Therefore, the excitation output data is set in the excitation output data buffer without performing the origin determination.

Here, the excitation data table and the excitation output data buffer will be described with reference to FIG.
FIG. 43A shows an example of an excitation data table.
The excitation data table is a table in which 4 bytes of excitation data are arranged. In the 4 bytes, 4 bits from the MSB side are information corresponding to the motors MT0, MT1,. For each motor, excitation data is arranged in the corresponding byte according to the excitation counter values 0, 1, 2, and 3.
For example, regarding the motor MT0, the excitation counter values 0, 1, 2, and 3 correspond to 4-byte values of “0x60000000”, “0x50000000”, “0x90000000”, and “0xA0000000”.
For the motor MT0, 4 bits on the MSB side of these 4 bytes function as excitation output data. That is, “6h”, “5h”, “9h”, and “Ah”.
“6h” = 0110, “5h” = 0101, “9h” = 1001, “Ah” = 1010, and the values of 0110, 0101, 1001, 1010 themselves become excitation drive signals for the four-phase drive stepping motor. .
That is, when the stepping motor 121 as the motor MT0 is rotated in the forward direction, the corresponding LED driver 90 is assigned 0110 (6h) → 0101 (5h) → 1001 (9h) → 1010 (Ah) → 0110 (6h) → 0101 ( Excitation output data may be transmitted in the order of 5h).
When the stepping motor 121 is rotated in the reverse direction, the LED driver 90 is in reverse order 1010 (Ah) → 1001 (9h) → 0101 (5h) → 0110 (6h) → 1010 (Ah) → 1001 (9h Excitation output data may be transmitted in the order of

For the motor MT1, the next 4 bits as viewed from the MSB side function as excitation output data, and “6h”, “5h”, “9h”, and “Ah” are set in the same manner.
For the motor MT2, the next 4 bits function as excitation output data, and “6h”, “5h”, “9h”, and “Ah” are similarly set.
Hereinafter, “6h”, “5h”, “9h”, and “Ah” are similarly set in the corresponding four bits of the motors MT3, MT4, and MT5.
In this example, the motors MT6 and MT7 are not used, and all information corresponding to the motors MT6 and MT7 is “0x00000000”. However, if used, the corresponding 4 bits are also used for the motor MT6. .

A value corresponding to the excitation counter value is extracted from such an excitation data table and set in the excitation output data buffer.
An excitation output data buffer is schematically shown in FIG. 43B.
The excitation output data buffer is secured as an area of 4 bytes (32 bits), for example, and is assigned so that excitation output data is stored in units of 4 bits for each motor.
For example, the excitation output data dMT1 of the motor MT1 is used for bits 0 to 3, the excitation output data dMT0 of the motor MT0 is used for bits 4 to 7, the excitation output data dMT3 of the motor MT3 is used for bits 8 to 11, and the motor is used for bits 12 to 15. Excitation output data dMT2 of MT2, excitation output data dMT5 of motor MT5 in bits 16-19, excitation output data dMT4 of motor MT4 in bits 20-23, excitation output data dMT7 of motor MT7 in bits 24-27 28 to 31 store excitation output data dMT6 of the motor MT6, respectively.

In the 4-byte output data buffer, data obtained by logically summing all 4-byte values extracted with reference to the excitation data table is actually set for each of the motors MT0 to MT7.
For example, in step S1651 of FIG. 38A described above, it is assumed that the motor MT0 (motor channel mCH0) is processed and the excitation counter (tcnt) = 0, and “0x60000000” is extracted from the excitation data table of FIG. 43A. At this time, it is assumed that “0x00900000” is extracted from the excitation data table, assuming that the excitation counter (tcnt) = 2 for the motor MT2 (motor channel mCH2). It is assumed that the excitation output data is cleared for all of the other motors MT1, MT3 to MT7 (for example, clearing is performed in steps S1602 and S1606 in FIG. 36 or in step S1732 in FIG. 41D described later). That is, the excitation output data of the motors MT1, MT3 to MT7 is “0x00000000”.
These are logically summed, and 4-bit excitation output data dMT0 to dMT7 are set in the excitation output data buffer as shown in FIG. 43C. The excitation output data dMT0 of the motor MT0 is arranged in bits 4 to 7. In these bits 4 to 7, "0x60000000", "0x00000000", "0x00900000", "0x00000000" ... "0x00000000" on each MSB side Since a 4-bit logical sum is set, “0110” as “6h” is eventually set. Further, the excitation output data dMT2 of the motor MT2 is arranged in the bits 12 to 15, and in these bits 4 to 7, “1001” as “9h” is set. The others are “0000”.

  Excitation output data stored in such an excitation output data buffer is output to the LED driver 90. As described in FIG. 5A, if six stepping motors 121 are connected to one LED driver 90, the excitation output data buffer of the LED driver 90 (for example, the LED driver 90 at the slave address b4) is connected. The excitation output data dMT0 to dMT5 of bits 0 to 23 are output as drive data corresponding to the output terminals 96-1 to 96-24 of the LED driver 90.

Returning to FIG. 38, the description of the processing according to the operation system option will be continued.
FIG. 38B shows a case where “D_OPT” = cw_on (forward rotation operation).
In this case, the effect control CPU 200 confirms the origin switch in step S1651. That is, “0” and “1” of the switch information described in FIG. 37 are confirmed.
If switch information = 0 (outside the origin), excitation output data corresponding to the excitation counter (tcnt) is set in step S1656 (the data is set in the excitation output data buffer). In step S1657, the value of the excitation counter (tcnt) in the motor data registration information (FIG. 16C) is incremented by one.
If switch information = 1 (within the origin), in step S1658, the operation count (lcnt) = 0 and the execution step (step) = 0. In step S1659, the operation line (ofset) is incremented by 1 to perform processing for the next row. In this case, as indicated by “M” in the figure, the process returns to step S1608 in FIG. 36 to perform processing for the next row.
38B corresponding to this cw_on, control is performed such that when the motor is within the origin, the motor is stopped, and when the motor is outside the origin, the forward rotation is performed.

FIG. 38C shows a case where “D_OPT” = cw_off (forward rotation operation).
In this case, the effect control CPU 200 confirms the origin switch (switch information) in step S1661.
If switch information = 1 (within the origin), excitation output data corresponding to the excitation counter (tcnt) is set in step S1664 (the data is set in the excitation output data buffer). In step S1665, the value of the excitation counter (tcnt) is incremented by one.
If the switch information = 0 (outside the origin), in step S1662, the operation count (lcnt) = 0 and the execution step (step) = 0. In step S1663, the operation line (ofset) is incremented by 1, and the process returns to step S1608 in FIG. 36 to perform processing for the next row.
38C corresponding to this cw_off, control is performed such that the motor is stopped when the motor is out of the origin, and the forward rotation is performed when the motor is within the origin.

FIG. 39A shows a case where “D_OPT” = ccw_all (reverse operation).
In step S1667, the effect control CPU 200 sets excitation output data corresponding to the complement of the excitation counter (tcnt) as data to be set in the excitation output data buffer. That is, when the excitation counter (tcnt) = 0, the excitation counter of the excitation data table = 3 data, and when the excitation counter (tcnt) = 1, the excitation counter of the excitation data table = 2 data, the excitation counter (tcnt) = 2. In this case, the data of the excitation counter = 1 in the excitation data table is extracted, and when the excitation counter (tcnt) = 3, the data of the excitation counter = 0 in the excitation data table is extracted.
In step S1668, the value of the excitation counter (tcnt) is incremented by one.
This ccw_all is optional data that performs reverse operation regardless of whether the origin switch is on or off. For this reason, the excitation output data corresponding to the complement of the excitation counter (tcnt) is set in the excitation output data buffer without particularly determining the origin.

FIG. 39B shows a case where “D_OPT” = ccw_on (reverse operation).
In this case, the effect control CPU 200 confirms the origin switch (switch information) in step S1671.
If switch information = 0 (outside the origin), in step S1672, the data is set in the excitation output data buffer corresponding to the complement of the excitation counter (tcnt). In step S1673, the value of the excitation counter (tcnt) is incremented by one.
If the switch information = 1 (within the origin), in step S1674, the operation count (lcnt) = 0 and the execution step (step) = 0. In step S1675, the operation line (ofset) is incremented by 1 to perform processing for the next row, and the processing returns to step S1608 in FIG. 36 to perform processing for the next row.
39B corresponding to ccw_on, control is performed such that when the motor is within the origin, the motor is stopped, and when the motor is outside the origin, the reverse operation is performed.

FIG. 39C shows a case where “D_OPT” = ccw_off (reverse operation).
In this case, the effect control CPU 200 confirms the origin switch (switch information) in step S1676.
If switch information = 1 (within the origin), excitation output data corresponding to the complement of the excitation counter (tcnt) is set as data to be set in the excitation output data buffer in step S1679. In step S1680, the value of the excitation counter (tcnt) is incremented by one.
If the switch information = 0 (outside the origin), the operation count (lcnt) = 0 is set and the execution step (step) = 0 is set in step S1677. In step S1678, the operation line (ofset) is incremented by 1, and the process returns to step S1608 in FIG. 36 to perform processing for the next row.
39C corresponding to this ccw_off, control is performed such that when the motor is outside the origin, the motor is stopped, and when it is within the origin, the reverse operation is performed.

FIG. 40A shows a case where “D_OPT” = cw_btn (forward rotation operation).
In this case, the effect control CPU 200 confirms in step S1681 whether or not the prescribed step operation for the row has been completed. If the operation has been completed, the operation count (lcnt) = 0 is set in step S1682, and the execution step (step) = 0 is set. In step S1683, the operation line (ofset) is incremented by 1, and the process returns to step S1608 in FIG. 36 to perform processing for the next row.
If it has not been operated, it is checked in step S1684 whether or not the button of the operation unit 60 is being pressed. If the button is being pressed, the excitation output data corresponding to the excitation counter (tcnt) is set as data to be set in the excitation output data buffer in step S1585. In step S1686, the value of the excitation counter (tcnt) is incremented by one.
40A corresponding to this cw_btn, control is performed such that the forward rotation operation is performed when the button is pressed, and the stop state is performed when the button is not pressed.

FIG. 40B shows a case where “D_OPT” = ccw_btn (reverse operation).
In this case, the effect control CPU 200 confirms in step S1691 whether or not the prescribed step operation for the row has been completed. If the operation has been completed, the operation count (lcnt) = 0 in step S1692 and the execution step (step) = 0. In step S1693, the operation line (ofset) is incremented by 1, and the process returns to step S1608 in FIG. 36 to perform processing for the next row.
If it has not been operated, it is checked in step S1694 whether or not the button of the operation unit 60 is being pressed. If the button is being pressed, excitation output data corresponding to the complement of the excitation counter (tcnt) is set as data to be set in the excitation output data buffer in step S1695. In step S1696, the value of the excitation counter (tcnt) is incremented by one.
40B corresponding to this ccw_btn, control is performed so that a reverse operation is performed when the button is pressed and a stop state is set when the button is not pressed.

  By processing according to the above operating system options, various motor operations such as normal rotation and reverse rotation of the motor, normal rotation or reverse rotation according to the origin switch state, and normal rotation or reverse rotation according to the button operation Can be specified by table.

  Subsequently, processing corresponding to main ones described in “D_OPT” will be described with reference to FIGS. 41 to 42 as processing corresponding to the non-operation option in step S1619 in FIG.

FIG. 41A shows a case where “D_OPT” = roop_s (loop start point).
In step S1701, the effect control CPU 200 refers to the attribute of the motor data registration information and confirms whether or not the motor operation table currently being executed is a parent.
In the case of the parent, in step S1702, the line of the operation line (ofset) +1 is substituted as the loop start point. That is, the line next to the line “D_OPT” = roop_s is set as a loop start point. In step S1703, the value of “D_SPEED” is set as the number of loops. In step S1704, the operation line (ofset) is incremented by 1, and the process returns to step S1608 in FIG. 36 to perform processing from the next line. In this case, the process from the next line to the loop end line is repeated by the number of loops.
If the parent is not the parent in step S1701, the loop is not set, and the operation line (ofset) is incremented by 1 in step S1704, and the process returns to step S1608 in FIG.

FIG. 41B shows a case where “D_OPT” = roop_e (loop end point).
In step S1711, the effect control CPU 200 refers to the attribute of the motor data registration information and confirms whether or not the motor operation table currently being executed is a parent.
In the case of the parent, in step S1712, it is confirmed whether or not the loop count = 0. Since the value of “D_SPEED” is set in step S1730 of FIG. 41A and is set to −1 in the next step S1713, the number of loops = 0 means that the number of loops indicated by “D_SPEED” has ended. Means.
If the loop count is not 0, the value of the loop count is decremented by -1 in step S1713, and it is confirmed again in step S1714 whether the loop count is 0 or not. If the number of loops is not 0, the value of the loop start point (see step S1702 in FIG. 41A) is substituted into the operation line (ofset) in step S1716. That is, in order to continue the loop process, the process returns to the loop start line. Then, the process returns to step S1608 in FIG. 36 to perform processing from the loop start line.
If it is not the parent in step S1711, if the loop count = 0 in step S1712, or if the loop count = 0 in step S1714, the operation line (ofset) is incremented by 1 in step S1715 and the process returns to step S1608 in FIG. That is, the processing is performed from the line following the loop end point line.

  By performing the processes in FIGS. 41A and 41B according to roop_s (loop start point) and roop_e (loop end point), it is possible to specify a loop in the motor operation table. In other words, by designating a loop in the motor operation table and performing operation control in accordance with the loop specification, an efficient motor operation table that does not unnecessarily increase the number of rows can be set, leading to a reduction in memory capacity.

FIG. 41C shows a case where “D_OPT” = link (link command).
In step S1721, the effect control CPU 200 refers to the attribute of the motor data registration information to check whether or not the motor operation table currently being executed is a parent.
In the case of the parent, in step S1722, the value of the execution operation number (no) is written in the parent number (retNo) of the current motor channel mCHn of the motor data registration information. In step S1723, the value of the operation line (ofset) +1 is written to the return address (retAddr).
In step S 1724, the value “D_SPEED” is written in the execution operation number (no) and the registered operation number (noNew). This is because in the case of link (link command), “D_SPEED” indicates the number of the motor operation table at the link destination.
In step S 1725, the operation line (ofset) = 0 is set, and in step S 1726, the attribute is set to “0” indicating a child (link destination), and the process returns to step S 1608 in FIG. As a result, processing from the first line of the linked motor operation table is performed.
If it is determined in step S1721 that the child is a child, the process returns to step S1608 in FIG. 36 without doing anything.

FIG. 41D shows a case where “D_OPT” = nor_end (normal end).
In step S1731, the effect control CPU 200 refers to the attribute of the motor data registration information and confirms whether the motor operation table currently being executed is a parent.
In the case of the parent, the excitation output data is cleared in step S1731, and the data relating to the motor operation is cleared in step S1733, specifically, the data relating to the motor operation other than the excitation count (tcnt) in the motor channel mCHn. The data relating to the motor operation refers to 12 types of data from the execution operation number (no) to the error counter (errCnt) in FIG. 16C.
On the other hand, in the case of a child, processing for returning to the parent motor operation table is performed. That is, the effect control CPU 200 writes the value of the parent number (retNo) in the execution operation number (no) and the registered operation number (noNew) in step S1734. In step S1735, the return address (retAddr) value is written to the operation line (ofset). In step S1736, the attribute is set to “5A” indicating the parent. In step S1737, the parent number (retNo) and the return address (retAddr) are cleared, and the process returns to step S1608 in FIG.
Thus, processing is performed from the row of the motor operation table that is the link source in FIG. 41C (the row next to the “D_OPT” = link row written in the return address (retAddr) in step S1723).

If nor_end (normal end) is designated by the processing of FIG. 41D described above, control of the operation pattern of the current motor operation table is normally completed thereby. Along with this, the work is cleared, and thereafter, the motor channel mCHn becomes a newly registerable empty channel.
41C and 41D, it is possible to set the link of the motor operation table from parent to child and return to the parent motor operation table at the end of the child motor operation table.
In the case of the parent (link source) as shown in FIG. 41C, first, the parent number (retNo) and the return address (retAddr) are set in the motor channel mCHn for returning from the link destination, and then the motor operation of the link destination is performed. The table is set as an execution operation number (no) and a registration operation number (noNew), and processing corresponding to each row of the motor operation table at the link destination is executed. In the motor operation table of the child at the link destination, the process returns to the line next to the line “D_OPT” = link of the parent motor operation table from the nor_end (normal end) line by the processing of steps S1734 to S1737.
Thus, a plurality of motor operation tables can be linked, and the prepared motor operation tables can be used efficiently. In other words, an efficient motor operation table that does not unnecessarily increase the number of rows can be set, leading to a reduction in memory capacity.

FIG. 42A shows a case where “D_OPT” = chk_end (end of check).
The effect control CPU 200 confirms the origin switch (switch information) in step S1741, and if switch information = 0 (outside the origin), the motor MT (n) is error-set in step S1742.
In step S1743, excitation output data for the motor channel mCHn is cleared, and in step S1744, data related to motor operation other than the excitation count (tcnt) is cleared in the motor channel mCHn. Then, the process proceeds to “C” in FIG. 36 (end of the process in the loop LP5).
By this chk_end (end of check) process, the operation pattern is ended with confirmation of being within the origin.

FIG. 42B shows a case where “D_OPT” = err_cnt (error counter + 1).
The effect control CPU 200 increments the error counter (errCnt) of the motor MT (n) by 1 in step S1751.
In step S1752, the value of the error counter is confirmed. If it exceeds 2, error setting of the motor MT (n) is performed in step S1753.
In step S1754, the excitation output data for the motor channel mCHn is cleared. In step S1755, data related to motor operation other than the excitation count (tcnt) is cleared in the motor channel mCHn. Then, the process proceeds to “C” in FIG. 36 (end of the process in the loop LP5).
By this err_cnt (error counter + 1) process, a motor error is set according to the value of the error counter.

FIG. 42C shows a case where “D_OPT” = sys_err (no error command).
The effect control CPU 200 performs error setting of the motor MT (n) in step S1761.
In step S1762, the excitation output data for the motor channel mCHn is cleared. In step S1763, data relating to the motor operation of the motor channel mCHn (12 types of data from the execution operation number (no) to the error counter (errCnt)). clear. Then, the process proceeds to “C” in FIG. 36 (end of the process in the loop LP5).
FIG. 42D shows a case where “D_OPT” = sys_erc (with error command).
The effect control CPU 200 performs error setting of the motor MT (n) in step S1771.
In step S1772, an error command indicating an error in the motor MT (n) is set. In step S1773, the excitation output data for the motor channel mCHn is cleared, and in step S1774, the motor operation data for the motor channel mCHn (12 types of data from the execution operation number (no) to the error counter (errCnt)) is cleared. To do. Then, the process proceeds to “C” in FIG. 36 (end of the process in the loop LP5).
By specifying sys_err and sys_erc in FIGS. 42C and 42D, an error setting that specifies the presence or absence of an error command becomes possible.

FIG. 42E shows a case where “D_OPT” = sys_ck1 (migration according to the origin switch).
The effect control CPU 200 confirms the origin switch (switch information) in step S1781.
If the switch information = 0 (outside the origin), the operation line (ofset) is incremented by 1 in step S1782.
If switch information = 1 (within the origin), the value of (ofset + D_SPEED) is written to the operation line (ofset) in step S1783.
This sys_ck1 process advances the processing line to the next line when it is outside the current origin, and advances the processing line by the number of lines specified by “D_SPEED” when it is within the current origin. As a result, processing corresponding to the inside and outside of the origin of the motor can be defined for each motor operation table. This also contributes to the realization of an efficient motor operation table with a small capacity.

FIG. 42F shows a case where “D_OPT” = sys_ck2 (transfer according to the origin switch).
The effect control CPU 200 confirms the origin switch (switch information) in step S1791.
If switch information = 1 (within the origin), the operation line (ofset) is incremented by 1 in step S1793.
If switch information = 0 (outside the origin), the value of (ofset + D_SPEED) is written to the operation line (ofset) in step S1792.
By this sys_ck2, the processing line is advanced to the next line when it is currently within the origin, and the processing line is advanced by the number of lines designated by “D_SPEED” when it is outside the current origin. As a result, processing corresponding to the inside and outside of the origin of the motor can be defined for each motor operation table. This also contributes to the realization of an efficient motor operation table with a small capacity.

The processing according to the operation system option and the non-operation system option has been described so far, but the pachinko gaming machine 1 according to the present embodiment generates a special game state advantageous to the player due to the lottery process such as a big hit. It is a game machine to let you. The movable body is provided with the above-mentioned possible body accessory as a movable body for notifying that the transition to the special gaming state or the possibility of transition is high, and each motor of the movable body accessory motor unit 65 is movable. Motor). And the effect control part 51 (effect control CPU200) is provided as a control means to drive a motor. Then, the effect control CPU 200 performs motor control based on the motor operation table described with reference to FIG.
That is, as described above, the motor operation table includes the control items of the operation system processing information (operation system option) indicating the control contents with motor driving and the non-operation system processing information (non-operation) indicating the control contents without motor driving. A plurality of control items (contents of each line) are stored in the order of execution. The production control CPU 200 refers to the motor operation table in which a series of motor operation patterns are indicated by a plurality of control items as described above, and executes processing according to the operation system option or the non-operation system option indicated in each control item. By doing so, motor operation control is performed.
The control items of the motor operation table are operation type data (OPT) for identifying whether the option is an operation system option or a non-operation system option, and operation content data (SPEED) for specifying a specific operation content related to the operation type. , STEP).
In the control items of the operation system option, the rotation direction and rotation amount of the motor are defined by “D-OPT” and “STEP”.
In addition, the non-operating option control items include information specifying the next control item to be executed without following the order specified in the motor operation table as information specifying the next processing to be executed. . For example, link, roop_s, roop_e, sys_ck1 to sys_ck4, and the like.
In addition, in the control items of the non-operation system option, for example, information for determining the position detection switch (origin switch 68) of the movable body accessory such as sys_ck1 to sys_ck4 and changing the subsequent operation according to the determination result. It is prescribed.

In the motor operation table, the operation option and the non-operation option are described in a mixed manner as control items constituting a series of motor operation patterns, so that the presentation control CPU 200 simply refers to the motor operation table. Thus, it is only necessary to perform the process instructed in each line, and the process in which the operating system and the non-operating system are mixed is simplified, and the processing load is reduced.
Moreover, precise and diverse operation patterns can be defined in the motor operation table by mixing operating and non-operating options.
Non-operating options include information specifying the next process to be executed, information for jumping to the link destination without following the order specified in the motor operation table, and line progress (for other control items). Etc.), each row of the motor operation table and other motor operation tables can be used effectively, and precise and diverse operation patterns can be specified without increasing the capacity of the entire motor operation table. it can.
In addition, the non-operating system option specifies the information to change the subsequent operation based on the judgment result of the origin switch 68, so that the control operation according to the situation of the motor (movable body accessory) can be specified. Motor operation can be executed.
In addition, the motor operation table is provided with an instruction value shared between the operation system option and the non-operation system option, such as the above-described speed (SPEED), and the effect control CPU 200 has the operation system option and the non-operation system option. Processing is performed by determining the content of the instruction value (D_SPEED) according to each control content. Sharing the instruction value in this way is also effective in reducing the data amount of the motor operation table.
That is, according to the motor control method using the motor operation table of this example, various motor operation effects can be achieved while reducing the processing load of the effect control CPU 200 and effectively using the memory area.
Note that such a motor control system using the motor operation table is suitable not only for the pachinko gaming machine 1 of the embodiment but also for the movable body control of other gaming machines, for example, the reel control of the slot gaming machine. It is.

In the present embodiment, in the motor operation update process of FIG. 36, the effect control CPU 200 specifies the designated value (operation pattern number) of the effect operation information (motor operation table) to be executed in the motor channel mCH of the motor data registration information. Is registered as the registered operation number (noNew), and the designated value (operation pattern number) of the effect operation information being executed is managed as the execution operation number (no).
In this way, the motor operation table scheduled to be executed and the motor operation table being executed (during the processing of steps S1680 to S1618) can be easily managed and processed on each motor channel mCH of the motor data registration information. Can be distinguished.

In the case of this example, specifically, a process of registering the designated value (motion pattern number) of the rendering motion information selected based on the control command as the registered motion number (noNew) is performed in step S1513 in FIG. 33B. Then, at the start of the execution of the process according to the presentation operation information (operation pattern number) registered in the motor data registration information as the registered operation number (noNew), the execution operation number (no) is executed in the processing of steps S1602 to S1604 in FIG. By substituting the value of the registered operation number (noNew) into, the operation pattern number of the motor operation table being executed is managed as the execution operation number (no).
By such processing, the registration operation number (noNew) and execution operation number (no) on the workpiece can be easily processed, and the processing load of the rendering control CPU 200 can be reduced. The table can be clearly managed, and in step S1607, the processing is branched with reference to the execution operation number (no), and redundant processing can be avoided.
If the registration operation number (noNew) and the execution operation number (no) do not match in step S1601, a process of substituting the value of the registration operation number (noNew) for the execution operation number (no) in step S1603 is adopted. By doing so, the execution operation number (no) can be updated without referring to information other than the motor data registration information, which is also effective in reducing the processing burden.
In this way, the processing load of the effect control CPU 200 is reduced.

[4-11: Motor output processing]

Next, the motor output process performed in step S204 of the 1 ms timer interrupt process in FIG. 9 will be described with reference to FIG.
Here, as in the example shown in FIG. 43, six stepping motors 121 of motors MT0 to MT5 are mounted, and the motors MT6 and MT7 are unused. The motor MT0 to MT5 will be described as being connected to one LED driver 90 as shown in FIG. 5B.

The motor output process of FIG. 44 is a process of outputting excitation output data dMT0 to dMT5 to the LED driver 90 to which the motors MT0 to MT5 are connected.
The effect control CPU 200 performs steps S1801 to S1808 for the number of LED drivers 90 to which the stepping motor 121 is connected as the loop process LP6. Assuming that one LED driver 90 is used to drive the six stepping motors 12 as described above, the number of loops is one.

Here, the register structure of the LED driver 90 will be described. 5A is a register provided in the data buffer / PWM controller 93 of FIG. 5A.
As registers, 8-bit register spaces each having register addresses 00h to 2Ch are prepared. Among these, register addresses 00h to 14h are used for driving the stepping motor 121.
The register addresses 15h to 2Ch are registers in which LED lighting data (gradation values) corresponding to the output terminals 96-1 to 96-24 are written, respectively, and may not be used in the case of motor driving.
Data is written in the registers at register addresses 00h to 14h as follows.

00h: PWM cycle setting data is set in 3 bits out of 8 bits, and master / slave setting data is set in 1 bit.
01h: Setting data of fade-in speed per gradation is set by 3 bits out of 8 bits and fade-out speed is set by 3 bits.
02h: Red LED current value data is set in 5 bits of 8 bits.
03h: Current value data of the green LED is set in 5 bits out of 8 bits.
04h: Current value data of blue LED is set in 5 bits out of 8 bits.
05h: Six bits out of eight bits set ON / OFF setting data of output terminals 96-1 to 96-6.
06h: Six bits out of eight bits set ON / OFF setting data of output terminals 96-7 to 96-12.
07h: Six bits out of eight bits set ON / OFF setting data of output terminals 96-13 to 96-18.
08h: Six bits out of eight bits set ON / OFF setting data of output terminals 96-19 to 96-24. The registers at the register addresses 05h to 08h serve as on / off setting units for the output terminals 96-1 to 96-24.
09h to 0Eh: For each of the four output terminals, any one of “PWM output priority”, “fade output priority”, and “forced on / off output priority” is selected and set for each of the four output terminals. The six registers from 09h to 0Eh correspond to the 24 output terminals 96-1 to 96-24.
0Fh to 11h: Three registers (24 bits in total) are set to enable / disable the fade function of 24 output terminals 96-1 to 96-24.
12h to 14h: Three registers (24 bits in total) are used to forcibly turn on / off the 24 output terminals 96-1 to 96-24.

  When the LED driver 90 is used for motor driving, data is written to the register addresses 00h to 14h in steps S1801 to S1808 as follows.

When serial data is transmitted to an LED driver 90 in the process of FIG. 44, the effect control CPU 200 turns on an enable signal (ENABLE) corresponding to the LED driver 90 in step S1801. In step S1802, the slave address of the target LED driver 90 is output.
Further, the effect control CPU 200 outputs a data setting start register address in step S1803. In this case, since data is written to the register addresses “00h” to “14h”, the data setting start register address = 00h.
On the LED driver 90 side, the transmitted data is sequentially stored in successive register addresses from the register indicated by the data setting start register address.

In step S1804, the effect control CPU 200 sequentially transmits data corresponding to the register addresses “00h” to “14h”.
First, in step S1804, data transfer to register addresses 00h to 11h is performed.
In this case, the data to be transferred is as follows. Note that “0x” and “h” are separately used to distinguish between the register address value and the data value to be transferred.
00h: 0x00: Initial setting of PWM cycle 01h: 0x00: No fade-in / fade-out slope 02h: 0x1F: Initial setting of red LED current value 03h: 0x1F: Initial setting of green LED current value 04h: 0x1F ... Initial setting of blue LED current value 05h: 0x77 ... ON setting of output terminals 96-1 to 96-6 06h: 0x77 ... ON setting of output terminals 96-7 to 96-12 07h : 0x77 ... ON setting of output terminals 96-13 to 96-18 08h: 0x77 ... ON setting of output terminals 96-19 to 96-24 09h: 0xAA ... Forced on / off setting priority 0Ah: 0xAA ... priority on / off setting priority 0Bh: 0xAA ... forcible on / off setting priority 0Ch: 0xAA ... forcible on / off setting First 0Dh: 0xAA ... Forced on / off setting priority 0Eh: 0xAA ... Forced on / off setting priority 0Fh: 0x00 ... Fade function disabled 10h: 0x00 ... Fade function disabled 11h: 0x00 ... Fade Disabled

Such data transfer is data to register addresses 09h to 0Fh, giving priority to the forced on / off setting for the output terminals 96-1 to 96-24 of the LED driver 90, and data to register addresses 05h to 08h. The output terminals 96-1 to 96-24 are turned on.
After making such settings, the effect control CPU 200 transfers the excitation output data dMT0 to dMT5 described with reference to FIG. 43C.
That is, in step S1805, 8 bits of excitation output data dMT0 and dMT1 of the motors MT0 and MT1 are transferred to the register address 12h.
In step S1806, 8 bits of excitation output data dMT2 and dMT3 of the motors MT2 and MT3 are transferred to the register address 13h.
In step S1807, 8 bits of excitation output data dMT4 and dMT5 of the motors MT4 and MT5 are transferred to the register address 14h.

When the above is completed, the enable signal (ENABLE) is turned off in step S1808, and the serial data transfer to one LED driver 90 is finished.
Depending on such motor output processing, the forced on / off setting priority is given to the output terminals 96-1 to 96-24 of the LED driver 90, and the register addresses 12h to 14h for the forced on / off setting are set. Excitation output data dMT0 to dMT5 are set. Excitation output data dMT0 to dMT5 are each 4-bit data as described with reference to FIG. 43. The 4-bit "0" is information for forcibly turning off and "1" is for instructing forcible on. Is a signal for driving the four output terminals described in FIG. 5B.

For example, it is assumed that the output terminals 96-1 to 96-4 are connected to the stepping motor 121 as the motor MT0, and the output terminals 96-5 to 96-8 are connected to the stepping motor 121 as the motor MT1. Assuming that the excitation output data dMT0 = 0110 (6h) and the excitation output data dMT1 = 0000, the excitation output data dMT0 = 0110 is transferred in step S1805, and “01100000” is set in the register address 12h.
In this case, the output terminals 96-2 and 96-3 are forcibly turned on by “0110”, and the excitation drive current is caused to flow to the stepping motor 121.

When the stepping motor 121 is rotated in the forward direction, the excitation output data is given to the LED driver 90 as described above: 0110 (6h) → 0101 (5h) → 1001 (9h) → 1010 (Ah). When the excitation output data dMT0 = 0101 is transferred, the output terminals 96-2 and 96-4 are forcibly turned on, and the excitation drive current is supplied to the stepping motor 121.
That is, 4-bit excitation output data for one motor is directly used as a drive control signal for the four-phase stepping motor, and the excitation output data is given in the above order, whereby the four-phase excitation drive for the stepping motor 121 is realized.

  As described above, in the present embodiment, the LED driver 90 causes the terminal to which the stepping motor 121 is connected to be set to give priority to the forced on / off setting, and then the 4-bit excitation output data dMT (n ) Is given as it is as a control signal for four-phase excitation drive. As a result, the effect control CPU 200 has a small transmission data generation processing load on the LED driver 90, and a simple control process. In addition, the drive control is only required to transmit the excitation output data of 4 bits per motor after forcibly turning on / off each register of the LED driver 90, the transmission data amount is small, and the transmission processing load is small. The necessary transmission data buffer area can also be reduced.

Further, in the processing of the effect control CPU 200 of the present example described above, the light emission operation of the decorative lamp unit 63 that should be executed based on the control command from the main control CPU 100, the sound output operation by the sound source IC 59, and the movable body accessory A registration process for registering operation information about the motor operation by the motor unit 65 in a predetermined memory area (for example, the work area in FIGS. 16 and 17) as necessary is executed for each first period as a 16 ms process (FIG. 8 step S110, FIG. 14, FIG. 15).
On the other hand, output data generation processing and output processing corresponding to the registration of the operation information about the motor operation are executed every second period as a 1 ms timer interruption process shorter than the first period (see FIG. 9 steps S203, F204, FIG. 36, FIG. 44).
Regarding the motor operation, by controlling the operation as finely as possible in a short period of time, it is possible to perform a smooth movement and precise operation of the accessory, and to improve the effect. However, if the registration of the operation information of the motor data registration information to the motor channel mCH is also performed by the 1 ms timer interrupt process, the processing load increases. Therefore, the registration process is performed in a 16 ms process, thereby reducing the processing load on the effect control CPU 200. This also enables processing to be performed simultaneously with the operation information registration to the work (lamp channel dwCH, sound channel aCH) for the sound output operation and the light emission operation, thereby improving the processing efficiency.
Further, the output data generation process corresponding to the registration of the operation information regarding the light emission operation and the sound output operation is executed every 16 ms process (first period) (steps S113, F111 in FIG. 8, FIG. 20, FIG. 31). For these, it is assumed that there is no need for processing at such a short interval as the motor, so that the processing load is not increased unnecessarily by setting every first period.
8 and 9, the 16 ms processing of FIG. 8 is performed when the interrupt counter is counted up to 16 in the 1 ms timer interrupt processing. That is, the process in the first period here is a process executed when the interrupt process in the second period is performed a predetermined number of times. By having the first and second periods in such a relationship, management of each processing period does not have to be performed individually, which also contributes to reducing the processing load of the effect control CPU 200.

[4-12: Motor push-in operation]

Here, the control of the motor pushing operation will be described.
Each motor operation table illustrated in FIGS. 34A, 34C, and 34D stipulates that the motor is pushed in within the origin.
For example, in the motor operation table 1 of FIG. 34A, the stepping motor is driven to return toward the origin by 58 steps at a speed of 1 step per 3 ms (high speed) as ccw_all (reverse operation) on the 6th row. Further, on the seventh line, similarly as ccw_all (reverse operation), the stepping motor is driven to return toward the origin by 8 steps at a speed of 1 step (low speed) in 6 ms. The sixth and seventh lines are further pushed into the origin after confirming that they are within the origin, and this push-in action is performed in two stages from high speed to low speed.
The same applies to the 11th and 12th lines of the motor operation table 72 of FIG. 34C, and the same applies to the 11th and 12th lines of the motor operation table x of FIG. 34C.

For each stepping motor 121, a stopper is provided mechanically within the origin range as a limit position for the movement of the accessory. However, the above pushing operation surely pushes the accessory to the stopper position, and the position (the accessory) (Posture) is determined.
By executing such a push-in operation, the reference position of the accessory within the origin can be precisely defined, and the designed operation can be stably executed with the set number of motor steps during the operation. In particular, the pushing operation is performed in two stages from high speed to low speed, so that effects such as reduction of the gear load in the motor and stabilization of the final stop position on the assumption of rebounding can be obtained.

Each motor operation table in FIG. 34 is an example, but various controls can be considered for actually pushing the origin, and Examples 1 to 4 are shown in FIG.
Each figure of FIG. 45 shows the operation when the horizontal axis is time and the accessory returns to the origin. In each figure, the time point ton is the timing when the origin switch signal SWg (actually the switch information of FIG. 37C as viewed from the effect control CPU 200) is turned on, and the time point tsp is the stopper arrival timing. The stopper arrival timing is a time point when the stepping motor 121 is driven by the motor step number x after the time point ton. That is, the movable body accessory is structured to reach the stopper position by driving the x motor step from the time point when it is detected that the movable body accessory has reached the origin range.
Note that the origin switch 68 outputs the origin switch signal SWg for detecting that the accessory as a movable body is located in the origin range including the stopper position with the configuration described in FIG.

  Example 1 is an example in which the motor is driven toward the origin at a high speed and then pushed toward the stopper position at a low speed when the origin switch is turned on (within the origin). For example, the motor rotation of the number of motor steps exceeding the required number of motor steps x of the stepping motor 121 from the origin switch-on position to the stopper position is executed at a low speed. For example, the stopper position is reached at time tsp, but it is driven at a low speed after that, so even if there is a bounce of the accessory when it reaches the stopper, or there are errors in the number of steps in the design and mechanism, it will be useful. An object can be pressed against the stopper. In addition, when the stopper is reached, it is driven at a low speed, so that the burden and impact on the motor mechanism can be reduced.

  In example 2, after the motor is driven at high speed toward the origin, when the origin switch is turned on (within the origin), the required motor step number x of the stepping motor 121 from the origin switch on position to the stopper position is exceeded. The motor rotation of the number of motor steps is executed as it is at high speed. In this example, after the motor step number is driven, the predetermined motor step number is driven at a lower speed. In this case, the stopper position is reached at the time point tsp, but the high speed driving and the low speed driving are still executed thereafter, so that the rebound of the accessory when reaching the stopper, the number of design steps and the error in the mechanism, etc. Even if it exists, it can be set as the state which pressed the accessory against the stopper reliably. Ultimately, it is easy to stabilize the final accessory position by pressing it against the stopper at a low speed.

In Example 3, after driving the motor at high speed toward the origin, when the origin switch is turned on (within the origin), the number of required motor steps x of the stepping motor 121 from the origin switch on position to the stopper position is exceeded. The motor rotation with a small number of motor steps is executed at high speed as it is. Then, after the motor step number is driven, driving is performed at a low speed at a predetermined motor step number exceeding the stopper reach. The total number of motor steps exceeds the required number of motor steps x.
In this case, the stopper position is reached at time tsp, but when the stopper is reached, it is driven at a low speed, so that the burden and impact applied to the motor mechanism can be reduced. After that, the low-speed driving is still performed, so that the accessory can be surely pressed against the stopper even if the accessory rebounds when it reaches the stopper or there is a design error. Particularly in this case, the stopper reaches the stopper at a low speed, and the rebound is reduced because the pushing is performed, and the final accessory position is easily stabilized by pushing.

In Example 4, after driving the motor at high speed toward the origin, when the origin switch is turned on (within the origin), the motor of the required number of motor steps x of the stepping motor 121 from the origin switch on position to the stopper position The rotation is executed as it is at high speed. In this example, after the motor step number is driven, the predetermined number of motor steps is driven at a low speed. The total number of motor steps exceeds the required number of motor steps x.
In this case, the stopper position is reached at the time point tsp, but after that, by switching to low speed driving and executing the pushing, even if there is a bouncing of the accessory when reaching the stopper or a design error, it is ensured. It is possible to make a state in which the accessory is pressed against the stopper. Further, since the final push-in is slow, it is easy to stabilize the final accessory position.

In any of the above examples, the effect control CPU 200 moves the movable accessory to the stopper position at the first speed (high speed) when moving the movable accessory to the stopper position on the mechanism and stops it. Then, the first motor drive control for driving the movable body accessory is performed at a second speed (low speed) in the direction toward the stopper position.
Thereby, the movable body accessory can be slowed down and stopped at the stopper position, and reliable position control by the above-described pushing is realized.
In Examples 2 to 4, high-speed and low-speed motor drive control is performed after the origin switch on timing. Further, in all of Examples 1 to 4 in FIG. 45, the total number of motor steps of the first motor driving control and the second motor driving control is the driving amount from the state where the motor enters the origin range until the stopper position is reached. Pushing is performed so as to perform motor drive control with a drive amount (motor step number x + α) exceeding (necessary motor step number x).
By doing so, the stop position of the accessory within the origin can be stabilized even if there is a rebound or the like. In particular, when the upper part is the origin, the rebound due to its own weight will increase even if it reaches the stopper position, but it will eventually stop by pushing at the second speed as in the above example. The position can be stabilized.
In addition, although the example which performs a motor drive speed in two steps was shown here, you may make it into three steps or more. In any case, it is preferable to perform low-speed drive control in the final stage of push-in control.

<5. Summary and Modification>

By the processing of the effect control CPU 200 described above, various effect operations can be efficiently realized while reducing the control load. In addition, the memory capacity required for effect control can be reduced.

Note that the present invention is not limited to the examples given in the embodiment, and various modifications and application examples are conceivable.
For example, in the above description, an example in which the present invention is applied to a ball game machine such as the pachinko gaming machine 1 has been shown, but the present invention can also be suitably applied to a revolving game machine (so-called slot machine). Is. That is, the various effect controls described above by the effect control CPU 200 can be suitably applied to the light emission effect, the sound effect, and the movable object effect in the slot machine.
In the movable body accessory motor unit 65, the stepping motor 121 has been described as the motor for driving the movable body. However, other drive mechanisms such as a solenoid may be used. Even when a solenoid is used, solenoid control can be performed in the same manner as the motor control described above. For example, solenoid registration is performed following motor registration in step S636 of FIG. In step S203 (FIG. 9) of the 1 ms timer interrupt process, the solenoid operation update process is performed following the process of FIG. 36, and the process of setting the excitation output data based on the data of the solenoid operation table is performed. Excitation output data may be transmitted to the solenoid driver.
In the embodiment, the example in which the LED driver 90 is used as the motor driver has been described. Of course, this is an example. Needless to say, a dedicated motor driver may be used to drive each motor.

DESCRIPTION OF SYMBOLS 1 Pachinko machine 2 Front frame 3 Game board 3a Game area 4 Outer frame 5 Glass door 6 Axle support mechanism 7 Operation panel 8 Upper tray unit 9 Lower tray unit 10 Launching operation handle 11 Patrite switch 12 Direction button 13 Cross key 14 Ball rental Button 15 Card return button 20w, 20b Decorative lamp 25 Speaker 31 Sphere guide rail 32M Main liquid crystal display device 32S Sub liquid crystal display device 33 Symbol display section 41 Upper start opening 42 Ordinary variable winning device 42a Lower start opening 43 General winning opening 44 Gate 45 First special variable winning device 46 Second special variable winning device 50 Main control board 50
51 Production control board 51
52 Liquid Crystal Control Board 53 Dispensing Control Board 54 Launch Control Board 58 Power Supply Board 59 Sound Source IC
60 Operation unit 61 Frame driver unit 62 Panel driver unit 63, 64 Decoration lamp unit 65 Movable body accessory motor unit 67 Amplifier unit 200 Production control CPU
201 Production control ROM
202 Production control RAM

Claims (1)

Main control means for overall control of game operations and outputting control commands related to game operations;
Production control means for controlling the execution of the production related to the game operation,
The production control means includes
A plurality of production data that defines the operation of the production device are stored in the order of execution, and there are a plurality of types of production scenario tables in which end information is stored at the final position,
Based on the control command, registering designation information for designating any one of the plurality of types of production scenario tables in an empty channel in a work area where a plurality of channels capable of storing production data are prepared,
The effect data stored in the effect scenario table corresponding to the specified information registered in the work area is sequentially referred to, and the process corresponding to the effect data to be processed is executed and stored in the effect scenario table. wherein the termination information in response to to be processed, a game machine that is configured to delete the specified information from the working area.

Images