Skip to content

Figures

Every figure on this site is drawn by a Python module from facts extracted from the code, so it is rebuilt, not redrawn, when the code changes. CI runs kokeb-docs figures --check and fails when a committed figure no longer matches the code. Each figure below lists the files it is drawn from.

Inside the BASIS 2 (B and BC series)

Block diagram of the BASIS 2 (B and BC series): its function blocks, how they connect and which package pins reach each block.Block diagram of the BASIS 2 (B and BC series): its function blocks, how they connect and which package pins reach each block.
Inside the BASIS 2 (B and BC series)
Figure description and sources

The BASIS 2 (B and BC series)'s function blocks inside its outline. Arrows between blocks carry signals or data in the direction they point (both ways where they have two heads). The package pins stand on the left and right edges with their numbers, each wired to the block it reaches.

Drawn from: docs/hardware.yml; inc/alicat_basis2_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

BASIS 2 (B and BC series): RS-232 point to point

Schematic of the BASIS 2 (B and BC series) rs-232 point to point: the chip with U2 MCU, U3 RS-232 level shifter, C1 capacitor 100 nF, J1 12 to 24 V supply; the MCU wires carry the port hooks Read(), Write().Schematic of the BASIS 2 (B and BC series) rs-232 point to point: the chip with U2 MCU, U3 RS-232 level shifter, C1 capacitor 100 nF, J1 12 to 24 V supply; the MCU wires carry the port hooks Read(), Write().
BASIS 2 (B and BC series): RS-232 point to point
Figure description and sources

A schematic. The MCU is on the left, each of its pins level with the chip pin it connects to; above each wire is the hook of the driver's port that drives or reads it. Supply pins point up to their supply and decoupling, ground pins down. Pins on the right carry the loads and the pins tied to a supply or ground; a cross marks a pin left open. A dot is a junction; wires that cross without a dot are not connected.

Drawn from: docs/hardware.yml; inc/alicat_basis2_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

BASIS 2 (B and BC series): RS-485 multidrop line

Schematic of the BASIS 2 (B and BC series) rs-485 multidrop line: the chip with U2 MCU, U3 RS-485 transceiver, J1 12 to 24 V supply, C1 capacitor 100 nF; the MCU wires carry the port hooks Read(), Write().Schematic of the BASIS 2 (B and BC series) rs-485 multidrop line: the chip with U2 MCU, U3 RS-485 transceiver, J1 12 to 24 V supply, C1 capacitor 100 nF; the MCU wires carry the port hooks Read(), Write().
BASIS 2 (B and BC series): RS-485 multidrop line
Figure description and sources

A schematic. The MCU is on the left, each of its pins level with the chip pin it connects to; above each wire is the hook of the driver's port that drives or reads it. Supply pins point up to their supply and decoupling, ground pins down. Pins on the right carry the loads and the pins tied to a supply or ground; a cross marks a pin left open. A dot is a junction; wires that cross without a dot are not connected.

Drawn from: docs/hardware.yml; inc/alicat_basis2_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

BASIS 2 (B and BC series) package, JST GH 6-pin connector

Outline of the BASIS 2 (B and BC series) in JST GH 6-pin connector drawn to scale from above: body 68.6 x 22.2 x 39.4 mm, 6 pins.Outline of the BASIS 2 (B and BC series) in JST GH 6-pin connector drawn to scale from above: body 68.6 x 22.2 x 39.4 mm, 6 pins.
BASIS 2 (B and BC series) package, JST GH 6-pin connector
Figure description and sources

The BASIS 2 (B and BC series) package seen from the top and, when the height is known, from the side, drawn to scale: 68.6 x 22.2 x 39.4 mm. The arrows carry the datasheet's dimensions, the dot marks pin 1 and the pads are numbered counter-clockwise from it, coloured by the pin's electrical type (legend below). Pads sit centred on each side, evenly spaced; the datasheet's land pattern is the reference for a board.

Drawn from: docs/hardware.yml; inc/alicat_basis2_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

BASIS 2 (B and BC series) pinout, JST GH 6-pin connector

Pinout of the BASIS 2 (B and BC series) in JST GH 6-pin connector, top view: 6 pins, each with its name, its electrical type as a colour and the driver hook that uses it.Pinout of the BASIS 2 (B and BC series) in JST GH 6-pin connector, top view: 6 pins, each with its name, its electrical type as a colour and the driver hook that uses it.
BASIS 2 (B and BC series) pinout, JST GH 6-pin connector
Figure description and sources

The BASIS 2 (B and BC series) seen from the top, in its JST GH 6-pin connector package. Pin 1 is marked by the dot; the numbers run counter-clockwise from it. Each pad is coloured by the pin's electrical type (legend below). Next to it is the pin's name and, in mono, the hook of the driver's port that drives or reads it; a pin without a hook is not used by the driver.

Drawn from: docs/hardware.yml; inc/alicat_basis2_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

The layers, one of them yours

Layer diagram: your application calls the Basis2 core, which sends register reads and writes through the UART port contract to the port class you write, which drives the chip; the core and the contract are the same on every MCU.Layer diagram: your application calls the Basis2 core, which sends register reads and writes through the UART port contract to the port class you write, which drives the chip; the core and the contract are the same on every MCU.
The layers, one of them yours
Figure description and sources

Top to bottom, each arrow is a call. Your application calls one object, whose public calls are listed from the umbrella header in inc/. The core turns each call into register reads and writes and hands them to the port contract (the CRTP base in inc/*_interface.hpp), which forwards them, at compile time, to the hooks of the port class you write; your port moves the bytes on the bus. The notes on the right say which layers stay the same on every MCU and which one you write. A library without a port contract has only the first two layers.

Drawn from: inc/alicat_basis2.hpp public calls; inc/alicat_basis2_uart_interface.hpp UartInterface; figure module docs/diagrams/figures/driver-layers.py.

Figure module: docs/diagrams/figures/driver-layers.py

Drawn from:

One call through the layers

One ReadFlow call: the device class builds the request, the bus layer waits for silence, writes it through your port and reads until a carriage return, and the reply is checked and decoded into a flow value.One ReadFlow call: the device class builds the request, the bus layer waits for silence, writes it through your port and reads until a carriage return, and the reply is checked and decoded into a flow value.
One call through the layers
Figure description and sources

Participants, left to right: Your code, Basis2, Bus and Your port. The steps run from top to bottom. Your code sends ReadFlow() to Basis2. Basis2 does ascii::Make(Poll) builds and checks the bytes itself. Basis2 sends Execute(request, timing) to Bus. A note over Bus says: wait t3.5 of silence. Bus sends FlushInput(), Write("A\r") to Your port. A note over Bus and Your port says: Repeat until a CR or the deadline. Bus sends Read(buffer) to Your port. A note over Bus and Your port says: End of the repeated steps. Your port returns "A +012.30 +024.8 ... Air\r" to Bus. Bus returns Reply to Basis2. A note over Basis2 says: strict grammar, unit ID, range. Basis2 returns Result of Decimal to Your code.

Drawn from: docs/model/one-call-through-the-layers.seq.yml.

Hardware description: docs/model/one-call-through-the-layers.seq.yml

Drawn from: