AI playbooks
A playbook is a step-by-step diagnosis written for an AI agent: which values to read on the device, in which order, how to interpret them and which documentation page explains each one. It is how siliXcon itself diagnoses a symptom, written down so your agent follows the same path instead of guessing.
Your agent gets the playbooks through emGUI: when it is connected to emGUI's MCP server, it can list the playbooks that match the connected device and read them. emGUI fetches them from this site when they are needed, so your agent follows the current version. The playbooks read the device. Anything that changes it - a parameter, or on a motor controller restarting the motor driver to check its sensor - is proposed to you first, and emGUI allows it only at the permission level you set.
Playbooks exist per device family and application. A new device starts with the getting started playbook: it connects the device, identifies it and hands over to its setup. The general method applies to every siliXcon device - motor controller, BMS or display - and comes first; a playbook for the device's family and application, when there is one, takes over from it. On a motor controller, an application's playbook follows the application up to the command it sends the motor; from there the motor driver playbook takes over, the same for every controller.
The same pages are readable here, so you can see what your agent is following.
How to diagnose a siliXcon device over MCP
Getting started: connect a new siliXcon device and set it up
Motor identification: set a controller up for its motor
LYNX: the motor does not run or does not react to the throttle
LYNX: set up the throttle, the speed and the maps
OPHION: set up the potentiometer range
ECHO: drive the motor over CAN
IGNIS: set up a starter-generator
CAPRA: set up a BMS for its battery
FALCON: first settings, the throttle input, then motor identification
Motor driver: the motor does not turn, runs badly, or the driver reports an error
Motor controller: does not switch on, is not found, or reports undervoltage
Is it really faulty? Checks before returning a device
New playbooks are added when a support case shows a pattern worth repeating: one symptom per page, linking to the documentation rather than repeating it. If your problem is not covered, send us a diagnostic report with a description of the symptom.