Significant events
Compiled text through Nov 15, 2021
Register checked through Jul 29, 2026
Later Register activity found — review the notice before relying on the compiled text.
Dates and status
- Compiling agency
- Executive Department
- Text status
- Source receipt
- Compiled text through
- Nov 15, 2021
- Register checked through
- July 29, 2026/Vol. XLVIII, Issue 30 (2026-07-29)
- Activity status
- Later Register activity found — review the notice before relying on the compiled text.
- Latest notice
- TAF-46-21-00009-P · Proposed rule · Nov 17, 2021
- Source snapshot
- Jun 6, 2026
(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)date and time that the event occurred; and
(2)identity of the gaming device that generated such event; and
(i)a unique number/code that defines such event; or
(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)power resets or power failure;
(2)hand-pay conditions (amount needs to be sent to the system):
(i)gaming device jackpot (an award in excess of the single-win limit of the gaming device);
(ii)cancelled credit hand-pay; and
(iii)progressive jackpot (an award in excess of the single-win limit of the gaming device);
(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)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):
(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
(ii)bill (item) jam;
(5)gaming device low RAM battery error;
(6)reel spin errors (if applicable with individual reel number identified);
(7)printer errors (if printer supported):
(i)printer empty/paper low; and
(ii)printer disconnect/failure.