(a) Notice of significant events that a gaming device generates shall be sent via the interface element to the MCS using an approved communication protocol. Each such event shall be stored in a database that includes the following:

1. (1) date and time that the event occurred; and

2. (2) identity of the gaming device that generated such event; and

   1. (i) a unique number/code that defines such event; or
   2. (ii) a brief text that describes the event in the local language.

(b) Significant events including the following shall be collected from the gaming device and transmitted to the system for storage:

1. (1) power resets or power failure;

2. (2) hand-pay conditions (amount needs to be sent to the system):

   1. (i) gaming device jackpot (an award in excess of the single-win limit of the gaming device);
   2. (ii) cancelled credit hand-pay; and
   3. (iii) progressive jackpot (an award in excess of the single-win limit of the gaming device);
3. (3) door openings (any door that gives access to a critical area on the gaming device). Door switches (discrete inputs to the interface element) are acceptable if their operation does not result in redundant or confusing messaging;

4. (4) bill (item) validator errors (the errors described in subparagraphs (i) and (ii) of this paragraph should be sent as a unique message, if supported by the communication protocol):

   1. (i) stacker full (it is recommended that an explicit “stacker full” error message not be used, because doing so may promote a security issue, but “bill validator malfunction” or the equivalent may not); and
   2. (ii) bill (item) jam;
5. (5) gaming device low RAM battery error;
6. (6) reel spin errors (if applicable with individual reel number identified);

7. (7) printer errors (if printer supported):

   1. (i) printer empty/paper low; and
   2. (ii) printer disconnect/failure.