First run

Start the application (build/bin/tinkerbus after wails build). The window has three parts.

• Top bar. The project menu (open, save, close, with undo and redo next to it), a search button (Ctrl+K), a keyboard shortcut help (the ? button), the Allow sending switch once you are connected, and the connection menu on the right.
• Navigation rail on the left, in three groups:
  • Project: Devices & places, Network, Group addresses, Reports, Compare. These need an open project.
  • Library: Catalog.
  • Bus: Diagnostics, Programming.
• Telegram monitor as a drawer at the bottom. Ctrl+J opens and closes it.

The last section you used and the state of the monitor drawer are remembered.

Some things work without a project: bus diagnostics, programming a new device, and the catalog. Devices, group addresses and reports come from a project.

Connect to a gateway

Open the connection menu in the top right.

1. Click Find on local network to run a multicast search, or type the address of a gateway (10.0.0.5 or 10.0.0.5:3671). Multicast discovery does not cross routers. For a gateway on another subnet, enter its address and click Describe, which asks that one gateway about itself.
2. Tick Tunnel over TCP (KNXnet/IP v2) if your gateway supports it and you want TCP instead of UDP.
3. Click Connect. The status shows the interface and the individual address the gateway assigned to you.

If you opened a project that remembers the gateway ETS used, a button offers Use project’s gateway.

The telegram monitor now shows traffic. Watching is passive: nothing is sent.

Sending

Allow sending is off after every connection. Diagnostics and programming need it, and so does reading or writing a group address from the Group addresses section. It switches off again when you disconnect. See safety.

Keyboard shortcuts