main_pc [Wonder Controlz]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Main PC ======

The Main PC is the central computer of every Wonder Controlz installation. It hosts Node-RED (game logic), software products like [[products:er-audio|er-audio]], and serves as the single point of management for the entire room.

===== Role in the System =====

  * Runs **Node-RED** — all game logic, automation, and the [[game_master_panel|Game Master Panel]]
  * Runs **software products** — [[products:er-audio|er-audio]], [[products:er-chat|er-chat]], and others
  * Communicates with **I/O modules** over CAN bus (er-01-rev-a, er-rfid)
  * Communicates with **lighting and video** devices over Ethernet/LAN
  * Connects to the **VPN** for remote service access

Following the [[architecture#zero_field_logic|Zero Field Logic]] principle, the Main PC is the only device in the room that contains game logic. All other devices are passive — they execute commands and report events.

===== Hardware =====

We use **BeeLink mini-PCs** — compact, fanless (or near-silent), energy-efficient computers that fit easily behind scenography or in a technical cabinet.

^ Parameter ^ Value ^
| Form factor | Compact mini-PC |
| Operating system | Linux (Debian 12) |
| Connectivity | Ethernet (LAN), USB ports for CAN adapter and audio interfaces |
| Power | Low power consumption, 12V or 19V DC input |

The BeeLink platform is chosen for its reliability, availability, and ease of replacement. If a Main PC fails, a new unit can be configured and deployed quickly — the game logic is stored as a Node-RED flow export and can be restored in minutes.

===== Software Stack =====

  * **Node-RED** — visual programming environment, game logic, [[game_master_panel|Game Master Panel]]
  * **[[products:er-audio|er-audio]]** — multi-channel audio (optional, can also run on a separate machine)
  * **Wonder Controlz Node-RED nodes** — [[products:node-red-nodes|custom palette]] for controlling all ecosystem products
  * **CAN interface** — connects to the CAN bus for I/O module communication