Adding peripherals to a board¶

A fifteen-second procedure: open the board, right-click to add a chip to a bus, and it is in the project. The recording uses the inoCORE32-TM board and adds a TCA9555 expander and an ADS1115 converter to I²C.

What each component does, its parameters and how it is wired is on its own page in the peripheral catalogue.

What happens in the clip¶

Time	What you are looking at
0:00	A project open on the inoCORE32-TM board. The tree shows only the interfaces the board actually has — CAN, RS485, Ethernet, I²C. It has no display, so there is no display node. The green dot beside CAN is live status read from the panel.
0:02	Clicking the board node opens its page. The module card — ESP32-PICO-V3-02, IP101GRI Ethernet, 8 free pins — and the pin assignment from the `boards/` catalogue.
0:05	Right-clicking I²C offers the chips for that bus. TCA9555 and ADS1115. POWERSTEP01 is an SPI part, so it is not offered — the list is filtered by the bus the chip belongs on.
0:06	TCA9555 appears in the tree and its page opens. The expander's pin table: every pin can be bound to a tag.
0:09	The same for the ADS1115. Four analogue inputs, address 0x48.
0:13	Back on the board page. Both peripherals are listed with their addresses, and the pin table has gained the pins they use.

Pins are never configured at run time

A peripheral added in the editor is compile-time configuration: it goes into the package and the panel reads it at start-up. The pin assignment does not change while running. That is a deliberate decision, and it protects against a badly deployed project switching a pin that has something else hanging on it.

How this clip was made

The editor itself is recorded, not the screen: input is injected straight into the user interface before the frame is drawn. It is therefore deterministic — the same script always produces the same recording, which makes the clip a regression test of the procedure as well as a video. The commands live in the product repository under docs/video/.