Interface Examples and Project Structure

Starter projects

Open a starter project using File → Open, save a copy in your test folder, and select the actual device. Templates have no databases, Loggers, simulation, replay, or automatic periodic tasks. Example transmit rows are manual. These are configuration examples, not hardware validation results.

File	Configuration
can-classic.blproj	500 kbit/s classic CAN, manual eight-byte ID 555
can-fd.blproj	500 kbit/s, FD configured at 2 Mbit/s; manual row without BRS
can-monitor.blproj	500 kbit/s listen-only, no transmit rows
lin-master.blproj	19200 master, manual 3C send / 3D request
lin-slave.blproj	19200 slave, empty response table
uart.blproj	UART 115200, manual AA 55 01
uart2can.blproj	UART utility mode 115200
uart2lin.blproj	UART utility mode 19200
python.blproj	REPL 115200 8N1

CAN needs an ACK-capable peer. The LIN master request may time out without a responder; that does not establish that no header was sent.

For a combined CAN + LIN + UART project, add all three, configure bus and UART Loggers separately, verify Started (3/3), test each manually, then enable required cycles.

Stored and external data

Projects contain module parameters, schedules/responses, database paths, logging, simulation configuration, graph signals, user variables, panel layouts and bindings, replays, and layout. They do not embed full Trace history, database contents, log files, or Python editor source.

Transfer external files alongside projects, reselect database/replay paths, and use a locally writable output folder.

AI editing and offline validation

.blproj is JSON and can be edited by AI. Keep the original and validate the edited copy:

beinilink-cli project validate --file .\Demo.blproj --output json
beinilink-cli project validate --file .\Demo.blproj --check-files
beinilink-cli project schema --output json
beinilink-cli help project validate

Validation does not connect to hardware or modify the project. Errors include field locations. Exit 0 means valid (warnings may remain); exit 2 means invalid input. It checks fields, parameter ranges, interface conflicts, schedule slots and payload lengths. --check-files also checks database and replay input files exist. Relative paths use the process working directory, not the project directory.

Inspect the intended configuration in the app after validation. Hardware connectivity, database signal/node availability, output-folder permissions and internal window layout are not proven by this check.