Example Directory

Bundled files use public teaching data, with connections configured through local Bench. This table lists companion materials and preparation.

Tutorial	Included material	Runtime preparation
01	Sample bus health report	Checks on the current computer
02	VehicleStatus DBC	Correct wiring, known/discovered parameters, and natural traffic
03	Requirements and result samples	Project source materials, cases, and test runner
04	Flashing plan, transfer report, four-byte HEX	Offline HEX dry-run; full flashing needs project code and ECU configuration
05	HTML, CSS, JavaScript, startup guide	Open listen-only channel and DBC signal plan
06	BMCLI simulation manifest	Isolated CAN bench and scenario runner
07	Channel mapping and criteria	Input logs, replay script, DUT, and independent observation
08	LDF	LIN master/slave bench with suitable power
09	A2L and debugging plan	Matching XCP target and runner
10	EDS and acceptance plan	Matching CANopen node and runner
11	EdgeX Profile and device list	Modbus slave matching register definitions
12	Dual-CAN gateway project and DBCs	Offline validation; two independent CAN networks for runtime
13	Python adapter, smoke check, offline tests	BMCLI; smoke/unit tests do not access the bus

flash-plan.yaml, requirements.yaml, debug-plan.yaml, and similar files are design inputs for the surrounding application. AI builds reading, execution, and judgment logic around them, gradually producing project-specific automation.

Download companion examples (ZIP) · Return to the series contents