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 DYNAMIXEL

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

The DYNAMIXEL'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/dynamixel_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

DYNAMIXEL: servo bus on an MCU's UART through a half-duplex stage

Schematic of the DYNAMIXEL servo bus on an mcu's uart through a half-duplex stage: the chip with U2 MCU, U3 Half-duplex stage, C1 capacitor 100 µF; the MCU wires carry the port hooks Write().Schematic of the DYNAMIXEL servo bus on an mcu's uart through a half-duplex stage: the chip with U2 MCU, U3 Half-duplex stage, C1 capacitor 100 µF; the MCU wires carry the port hooks Write().
DYNAMIXEL: servo bus on an MCU's UART through a half-duplex stage
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/dynamixel_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

DYNAMIXEL package, TTL servo

Outline of the DYNAMIXEL in TTL servo drawn to scale from above: body 28.5 x 46.5 x 34.0 mm, pitch 2.5 mm, 3 pins.Outline of the DYNAMIXEL in TTL servo drawn to scale from above: body 28.5 x 46.5 x 34.0 mm, pitch 2.5 mm, 3 pins.
DYNAMIXEL package, TTL servo
Figure description and sources

The DYNAMIXEL package seen from the top and, when the height is known, from the side, drawn to scale: 28.5 x 46.5 x 34.0 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; inc/dynamixel_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

DYNAMIXEL pinout, TTL servo

Pinout of the DYNAMIXEL in TTL servo, top view: 3 pins, each with its name, its electrical type as a colour and the driver hook that uses it.Pinout of the DYNAMIXEL in TTL servo, top view: 3 pins, each with its name, its electrical type as a colour and the driver hook that uses it.
DYNAMIXEL pinout, TTL servo
Figure description and sources

The DYNAMIXEL seen from the top, in its TTL servo 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/dynamixel_uart_interface.hpp.

Hardware description: docs/hardware.yml

Drawn from:

One read on the half-duplex data line

A read on the DYNAMIXEL data line: the controller sends an instruction packet for four bytes, the servo waits its return delay time and answers with a status packet carrying the bytes, an error byte and a CRC-16.A read on the DYNAMIXEL data line: the controller sends an instruction packet for four bytes, the servo waits its return delay time and answers with a status packet carrying the bytes, an error byte and a CRC-16.
One read on the half-duplex data line
Figure description and sources

Participants, left to right: MCU (driver) and Servo 1. The steps run from top to bottom. MCU (driver) sends Read 4 bytes at address 132 (instruction packet) to Servo 1. A note over MCU (driver) and Servo 1 says: Return Delay Time, factory 500 microseconds. Servo 1 returns Status packet with the 4 bytes (error byte, CRC-16) to MCU (driver).

Drawn from: docs/model/data-line-read.seq.yml.

Hardware description: docs/model/data-line-read.seq.yml

Drawn from:

The layers, one of them yours

Layer diagram: your application calls the DYNAMIXEL 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 DYNAMIXEL 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/dynamixel.hpp public calls; inc/dynamixel_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 call through the layers: your code calls ReadRegister({1, X430}, PresentPosition), the core exchanges frames with the chip through your port and returns the result to your code.One call through the layers: your code calls ReadRegister({1, X430}, PresentPosition), the core exchanges frames with the chip through your port and returns the result to your code.
One call through the layers
Figure description and sources

Participants, left to right: Your code, DYNAMIXEL and Your port. The steps run from top to bottom. Your code sends ReadRegister({1, X430}, PresentPosition) to DYNAMIXEL. A note over DYNAMIXEL says: table lookup: address 132, 4 bytes. DYNAMIXEL sends Write(instruction packet) to Your port. Your port returns true (last stop bit sent) to DYNAMIXEL. DYNAMIXEL sends Read(buffer, max, reply_timeout_us) to Your port. Your port returns n bytes to DYNAMIXEL. A note over DYNAMIXEL says: Scan: header, length, instruction, CRC-16. A note over DYNAMIXEL says: error byte, ID, parameter count. DYNAMIXEL returns Result{2048, Ok} 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: