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 SN65HVD230

Block diagram of the SN65HVD230: its function blocks, how they connect and which package pins reach each block.Block diagram of the SN65HVD230: its function blocks, how they connect and which package pins reach each block.
Inside the SN65HVD230
Figure description and sources

The SN65HVD230'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.

Hardware description: docs/hardware.yml

Drawn from:

SN65HVD230: A CAN node

Schematic of the SN65HVD230 a can node: the chip with U2 MCU with CAN controller, C1 capacitor 100 nF, R1 resistor 120 Ω, J1 CAN bus; the MCU wires carry the port hooks Receive(CanFrame&, timeout_us), Send(const CanFrame&).Schematic of the SN65HVD230 a can node: the chip with U2 MCU with CAN controller, C1 capacitor 100 nF, R1 resistor 120 Ω, J1 CAN bus; the MCU wires carry the port hooks Receive(CanFrame&, timeout_us), Send(const CanFrame&).
SN65HVD230: A CAN node
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.

Hardware description: docs/hardware.yml

Drawn from:

SN65HVD230 package, SOIC-8

Outline of the SN65HVD230 in SOIC-8 drawn to scale from above: body 4.9 x 3.9 x 1.75 mm, pitch 1.27 mm, 8 pins.Outline of the SN65HVD230 in SOIC-8 drawn to scale from above: body 4.9 x 3.9 x 1.75 mm, pitch 1.27 mm, 8 pins.
SN65HVD230 package, SOIC-8
Figure description and sources

The SN65HVD230 package seen from the top and, when the height is known, from the side, drawn to scale: 4.9 x 3.9 x 1.75 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 at the stated pitch; the datasheet's land pattern is the reference for a board.

Drawn from: docs/hardware.yml.

Hardware description: docs/hardware.yml

Drawn from:

SN65HVD230 pinout, SOIC-8

Pinout of the SN65HVD230 in SOIC-8, top view: 8 pins, each with its name, its electrical type as a colour and the driver hook that uses it.Pinout of the SN65HVD230 in SOIC-8, top view: 8 pins, each with its name, its electrical type as a colour and the driver hook that uses it.
SN65HVD230 pinout, SOIC-8
Figure description and sources

The SN65HVD230 seen from the top, in its SOIC-8 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.

Hardware description: docs/hardware.yml

Drawn from:

The layers, one of them yours

Layer diagram: your application calls the Client core, which sends CAN frames through the CAN port contract to the port class you write, which drives the CAN controller; the core and the contract are the same on every MCU.Layer diagram: your application calls the Client core, which sends CAN frames through the CAN port contract to the port class you write, which drives the CAN controller; 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 CAN frames (SDO requests, NMT commands, SYNC, PDOs) 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 puts each frame on the bus and hands received frames back. 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/canopen_client.hpp public calls; inc/canopen_client_can_interface.hpp CanInterface; figure module docs/diagrams/figures/driver-layers.py.

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

Drawn from: