Go to file
a2nr 0f62045260 feat: implement unified odometry interface with nav_msgs/Odometry; add odometry handling and integration tests 2026-03-17 19:59:01 +07:00
docs feat: implement unified odometry interface with nav_msgs/Odometry; add odometry handling and integration tests 2026-03-17 19:59:01 +07:00
src feat: implement unified odometry interface with nav_msgs/Odometry; add odometry handling and integration tests 2026-03-17 19:59:01 +07:00
.gitignore persiapan 2026-03-09 05:01:13 +07:00
DOCUMENTATION.md feat: implement unified odometry interface with nav_msgs/Odometry; add odometry handling and integration tests 2026-03-17 19:59:01 +07:00
pixi.lock feat: port gpio_node to C++ using libgpiod; update package structure and dependencies for native Raspberry Pi support 2026-03-12 10:27:47 +07:00
pixi.toml feat: add AS5600 magnetic encoder node with I2C support; implement message handling and integration tests 2026-03-16 20:08:07 +07:00
readme.md feat: implement unified odometry interface with nav_msgs/Odometry; add odometry handling and integration tests 2026-03-17 19:59:01 +07:00
workspace.json feat: add main program block and async procedure support in Blockly; enhance code generation and execution flow 2026-03-11 16:09:46 +07:00

readme.md

Project Management — AMR ROS2 K4

Project: Blockly ROS2 Robot Controller (Kiwi Wheel AMR) ROS2 Distro: Jazzy Last Updated: 2026-03-16 Current Focus: Task #5 — Unified Odometry Interface

Dokumentasi lengkap dapat dilihat di DOCUMENTATION.md.

Aturan pengggunaan dokumen

bab pada dokumen merepresentasikan alur rencana pengembangan.

Potential Enhancements

bab ini digunakan untuk Feasibility Study

Planned Feature

Backlog. Setelah kita pelajari untuk di kerjakan maka kita pindah ke backlog

Feature Task

penjabaran Pekerjaan yang ready untuk dikerjakan. Task harus dijelaskan apa yang akan dikerjakan dan terdapat definition of done nya Berikut ini adalah template untuk pembuatan task :


## <nomor task> <judul task> : <state: [ ] >
jelaskan permasalah di bab ini
### Definition Of Done
jelaskan apa yang dimaksut untuk menyelesaikan task


Potential Enhancements

this list is short by priority

  • Blockly UI Enhancement: Lets make Human Interface in same view to help me monitoring node that needed. it programaticaly using block is real good, you can take labview interface as refrence. you can separated program as main_program to handle human interface.
  • Feasibility Study to implement Controller: mobile robot need controller to move flawlesly.
  • Launch files: ROS2 launch files to start all nodes with one command includ node in raspberry pi
  • Simulation: Integrate with Gazebo/Isaac Sim for testing Kiwi Wheel kinematics before deploying to hardware
  • Block categories: Future blocks grouped into Robot, Sensors, Navigation categories

Feature Task

3 Enhancement: PCA9685 — 16-Channel PWM Controller (I2C) : [ ]

PCA9685 adalah 16-channel, 12-bit PWM controller via I2C. Motor DC kiwi wheel menggunakan 6 channel (3 motor × 2: PWM + direction), sehingga 10 channel tersedia untuk extensi (servo, LED, dll). Node ini general-purpose — mengontrol channel mana saja via Blockly block dengan parameter address, channel, dan PWM value.

Implementasi

A. Package Structure (C++, ament_cmake)

src/pca9685_node/
├── CMakeLists.txt              # ament_cmake — NO external lib dependency
├── package.xml                 # depend: rclcpp, blockly_interfaces
├── include/pca9685_node/
│   └── pca9685_node.hpp        # Pca9685Node class + I2C helpers
└── src/
    ├── pca9685_node.cpp         # I2C init, write_callback, set_pwm()
    └── main.cpp                 # rclcpp::spin(node)

Hardware interface menggunakan Linux I2C (/dev/i2c-X) via ioctl() — tidak perlu external library, cukup linux/i2c-dev.h (kernel header).

B. ROS2 Interface

New messageblockly_interfaces/msg/PwmWrite.msg:

uint8 address       # I2C address (default 0x40, configurable via solder bridges: 0x400x7F)
uint8 channel       # PWM channel (015)
uint16 value        # Duty cycle (04095, 12-bit resolution)

Topic: /pwm/write (executor → pca9685_node)

ROS2 Parameters (configurable via --ros-args -p):

Parameter Type Default Fungsi
i2c_device string /dev/i2c-1 Linux I2C device path
frequency int 50 PWM frequency Hz (semua channel)

PCA9685 write-only — tidak perlu PwmRead.msg.

C. Node Behavior — Pca9685Node

  1. Constructor: open i2c_device, configure prescaler berdasarkan frequency param
  2. Subscribe /pwm/write (PwmWrite) — set duty cycle via I2C register write
  3. set_pwm(address, channel, value): select I2C slave address via ioctl(I2C_SLAVE), write 4 bytes ke channel registers
  4. Multi-address support: satu node bisa mengontrol multiple PCA9685 boards (address dikirim per-message, ioctl(I2C_SLAVE) di-set setiap write)
  5. Cleanup: close file descriptor di destructor

PCA9685 register map:

Register Address Fungsi
MODE1 0x00 Sleep/restart, auto-increment
LED0_ON_L 0x06 Channel 0 ON timing (4 registers per channel)
PRE_SCALE 0xFE PWM frequency: prescale = round(25MHz / (4096 × freq)) - 1

D. Handler — blockly_executor/handlers/pwm.py

@handler("pwm_write")
def handle_pwm_write(params, hardware):
    address = int(params["address"], 16)  # hex string → int
    channel = int(params["channel"])
    value = int(params["value"])
    # Dummy: log only. Real: publish PwmWrite to /pwm/write

Lazy-create publisher di hardware.node._pwm_write_pub, sama dengan pola gpio.py.

E. Blockly Block — pwmWrite.js

┌──────────────────────────────────────────────┐
│ PCA9685  addr: [0x40]                        │
│          channel: [0 ▾]    pwm: [■ value]    │
└──────────────────────────────────────────────┘
  • addr: FieldDropdown — common addresses (0x400x47)
  • channel: FieldNumber (015)
  • pwm: ValueInput (04095) — accepts expression blocks, uses String(expr) pattern
  • Category: Robot, Command: pwm_write

F. pixi.toml Changes

  • setup-dep: tambah i2c-tools (optional, untuk debugging i2cdetect)
  • build-pca9685: colcon build --packages-select pca9685_node (depends-on: setup-dep, build-interfaces)
  • pca9685-node: ros2 run pca9685_node pca9685_node

Tidak perlu conda deps baru — Linux I2C headers sudah tersedia di kernel.

G. Penggunaan

# Default — /dev/i2c-1, 50 Hz
pixi run pca9685-node

# Ganti I2C device dan frequency via --ros-args
source install/setup.bash
ros2 run pca9685_node pca9685_node --ros-args -p i2c_device:=/dev/i2c-0 -p frequency:=1000

# Cek I2C bus yang tersedia di Pi
ls /dev/i2c-*           # list semua bus
i2cdetect -y 1          # scan device di bus 1 (perlu i2c-tools)

Catatan: pixi run pca9685-node menggunakan parameter default. Untuk override parameter, jalankan ros2 run langsung (setelah source install/setup.bash) karena pixi task tidak meneruskan --ros-args ke proses inner.

Definition Of Done

  • src/pca9685_node/ berisi CMakeLists.txt, package.xml, include/, src/
  • blockly_interfaces/msg/PwmWrite.msg terdaftar di rosidl_generate_interfaces()
  • pixi run build-interfaces berhasil — PwmWrite.msg ter-generate
  • pixi run build-pca9685 berhasil di Raspberry Pi (native build) tanpa error
  • Node berjalan: pixi run pca9685-node — subscribe /pwm/write
  • Parameter i2c_device, frequency berfungsi via --ros-args -p
  • Handler pwm_write berfungsi di dummy mode (test passes)
  • Blockly block pwmWrite muncul di toolbox, generate valid JS code
  • End-to-end: Blockly block → executor (real) → /pwm/write → pca9685_node → I2C write

4 Enhancement: AS5600 — 12-bit Magnetic Rotary Encoder (I2C) : [ ]

AS5600 adalah 12-bit magnetic rotary position sensor via I2C. Kiwi wheel AMR menggunakan 3 encoder (satu per roda) untuk feedback posisi. AS5600 memiliki fixed I2C address (0x36) — untuk 3 module, setiap encoder menggunakan I2C bus terpisah (e.g., /dev/i2c-1, /dev/i2c-3, /dev/i2c-4). Node ini publisher — membaca angle secara periodik dan publish ke ROS2 topic.

Implementasi

A. Package Structure (C++, ament_cmake)

src/as5600_node/
├── CMakeLists.txt              # ament_cmake — NO external lib dependency
├── package.xml                 # depend: rclcpp, blockly_interfaces
├── include/as5600_node/
│   └── as5600_node.hpp         # As5600Node class + I2C helpers
└── src/
    ├── as5600_node.cpp          # I2C init, timer_callback, read_raw_angle()
    └── main.cpp                 # rclcpp::spin(node)

Hardware interface menggunakan Linux I2C (/dev/i2c-X) via ioctl() — tidak perlu external library, cukup linux/i2c-dev.h (kernel header).

B. ROS2 Interface

New messageblockly_interfaces/msg/EncoderRead.msg:

uint8 encoder_id       # Encoder index (0, 1, 2, ...)
float32 angle          # Angle in degrees (0.0-360.0)
uint16 raw_angle       # Raw 12-bit value (0-4095)

Topic: /encoder/state (as5600_node → executor)

ROS2 Parameters (configurable via --ros-args -p):

Parameter Type Default Fungsi
i2c_devices string[] ["/dev/i2c-1"] List of I2C device paths, satu per encoder
publish_rate double 10.0 Publish frequency Hz

C. Node Behavior — As5600Node

  1. Constructor: open setiap I2C bus, set slave address 0x36 via ioctl(I2C_SLAVE), create publisher dan timer
  2. Timer callback: iterate semua I2C fds → read 2-byte RAW_ANGLE register → compute angle = raw * 360.0 / 4096.0 → publish EncoderRead
  3. read_raw_angle(fd): write register address 0x0C, read 2 bytes → ((buf[0] & 0x0F) << 8) | buf[1] (12-bit)
  4. Multi-bus support: satu node mengontrol semua encoder — setiap fd dedicated ke satu bus/encoder
  5. Cleanup: close semua file descriptors di destructor

AS5600 register map:

Register Address Fungsi
RAW_ANGLE 0x0C-0x0D 12-bit raw angle (0-4095)
STATUS 0x0B Magnet detect status
AGC 0x1A Automatic gain control

D. Handler — blockly_executor/handlers/encoder.py

@handler("encoder_read")
def handle_encoder_read(params, hardware):
    encoder_id = int(params["encoder_id"])
    # Dummy: return "0.0". Real: subscribe /encoder/state, return cached angle

Lazy-create subscriber dengan cache {encoder_id: {angle, raw_angle}}, sama dengan pola digital_in di gpio.py.

E. Blockly Block — encoderRead.js

┌──────────────────────────────────────┐
│ Encoder Read  id: [0]                │
└──────────────────────────────────────┘
  • id: FieldNumber (02)
  • Returns: Number (angle 0-360)
  • Category: Robot, Command: encoder_read
  • Output block (can be used in expressions, e.g., set variable to [Encoder Read id: 0])

F. pixi.toml Changes

  • build-as5600: colcon build --packages-select as5600_node (depends-on: setup-dep, build-interfaces)
  • as5600-node: ros2 run as5600_node as5600_node

Tidak perlu conda deps baru — Linux I2C headers sudah tersedia di kernel.

G. Penggunaan

# Default — /dev/i2c-1, 10 Hz, 1 encoder
pixi run as5600-node

# 3 encoder pada bus terpisah, 20 Hz
source install/setup.bash
ros2 run as5600_node as5600_node --ros-args \
  -p i2c_devices:="['/dev/i2c-1', '/dev/i2c-3', '/dev/i2c-4']" \
  -p publish_rate:=20.0

# Raspberry Pi: enable extra I2C buses via config.txt
# dtoverlay=i2c-gpio,bus=3,i2c_gpio_sda=17,i2c_gpio_scl=27
# dtoverlay=i2c-gpio,bus=4,i2c_gpio_sda=22,i2c_gpio_scl=23

Definition Of Done

  • src/as5600_node/ berisi CMakeLists.txt, package.xml, include/, src/
  • blockly_interfaces/msg/EncoderRead.msg terdaftar di rosidl_generate_interfaces()
  • pixi run build-interfaces berhasil — EncoderRead.msg ter-generate
  • pixi run build-as5600 berhasil di Raspberry Pi (native build) tanpa error
  • Node berjalan: pixi run as5600-node — publish /encoder/state
  • Parameter i2c_devices, publish_rate berfungsi via --ros-args -p
  • Handler encoder_read berfungsi di dummy mode (test passes)
  • Blockly block encoderRead muncul di toolbox, generate valid JS code
  • End-to-end: Blockly block → executor (real) → cache /encoder/state → return angle

5 Enhancement: Unified Odometry Interface — nav_msgs/Odometry : [ ]

Interface odometry menggunakan standar ROS2 nav_msgs/Odometry agar kompatibel dengan ekosistem ROS2. Setiap jenis sensor odometry (encoder, IMU, optical) publish ke topic terpisah odometry_<type>/odom menggunakan message type yang sama.

Motivasi: Modularitas — tambah sensor baru cukup buat node yang publish nav_msgs/Odometry ke odometry_<type>/odom. Dari Blockly, user pilih source dan field yang mau dibaca.

Arsitektur:

as5600_node (encoder)     → odometry_encoder/odom  (nav_msgs/Odometry)
future: imu_node          → odometry_imu/odom      (nav_msgs/Odometry)
future: optical_node      → odometry_optical/odom   (nav_msgs/Odometry)

Satuan: Mengikuti REP-103 kecuali jarak menggunakan centimeter (cm) karena rentang pergerakan robot kecil. Angular menggunakan radian.

Blocker: Implementasi sensor baru (IMU, optical) menunggu desain mekanik final.

Implementasi

A. Standard Interface — nav_msgs/Odometry

Tidak menggunakan custom message. nav_msgs/Odometry sudah tersedia di RoboStack (ros-jazzy-desktop dan ros-jazzy-ros-base). Message fields yang digunakan:

  • pose.pose.position.x/y — posisi robot (cm)
  • pose.pose.orientation — quaternion dari heading (2D: z=sin(θ/2), w=cos(θ/2))
  • twist.twist.linear.x/y — kecepatan robot (cm/s)
  • twist.twist.angular.z — kecepatan angular (rad/s)
  • header.frame_id = "odom", child_frame_id = "base_link"

B. AS5600 Node — Kiwi Wheel Kinematics (backward compatible)

as5600_node menghitung robot-level odometry langsung dari 3 encoder menggunakan kiwi wheel forward kinematics, lalu publish ke dua topic:

  • /encoder/state (EncoderRead) — legacy per-wheel angle, backward compat
  • odometry_encoder/odom (nav_msgs/Odometry) — robot-level pose + twist

Kiwi Wheel Forward Kinematics (3 roda @ 120°):

Constraint: ωᵢ = (1/r)(-vx·sin(αᵢ) + vy·cos(αᵢ) + L·ωz)

Forward kinematics (3 roda → robot velocity):
vx  = (r/n) · Σ(-ωᵢ·sin(αᵢ))     [cm/s]
vy  = (r/n) · Σ( ωᵢ·cos(αᵢ))     [cm/s]
ωz  = r/(n·L) · Σ(ωᵢ)            [rad/s]

Pose integration (Euler):
x  += (vx·cos(θ) - vy·sin(θ))·dt   [cm]
y  += (vx·sin(θ) + vy·cos(θ))·dt   [cm]
θ  += ωz·dt                         [rad]

Parameter kiwi wheel (configurable via --ros-args -p):

Parameter Type Default Keterangan
wheel_radius double 5.0 Radius roda (cm) — HARUS di-tune
wheel_distance double 15.0 Jarak center-to-wheel (cm) — HARUS di-tune
wheel_angles double[] [0, 2π/3, 4π/3] Sudut posisi roda (rad)

C. Handler — odometry.py

@handler("odometry_read")
def handle_odometry_read(params, hardware):
    source = params.get("source", "encoder")  # "encoder" | "imu" | "optical"
    field = params["field"]                     # "x" | "y" | "heading" | "vx" | "vy" | "omega_z"

Lazy-create subscriber per source ke odometry_<source>/odom. Cache robot-level fields dengan quaternion → yaw conversion.

D. Blockly Block — odometryRead.js

┌───────────────────────────────────────────────────────────┐
│ Odometry Read  source: [Encoder ▾]  field: [X (cm) ▾]    │
└───────────────────────────────────────────────────────────┘
  • source: FieldDropdownEncoder (extensible: IMU, Optical)
  • field: FieldDropdownX (cm), Y (cm), Heading (rad), Vel X (cm/s), Vel Y (cm/s), Angular Vel (rad/s)
  • Returns: Number, Category: Robot, Command: odometry_read

E. Backward Compatibility

  • EncoderRead.msg, encoder.py, encoderRead.js tetap ada dan berfungsi
  • Existing test test_block_encoder.py tetap pass
  • Saved workspace yang pakai encoderRead block tetap bisa di-load

F. Future Phases (blocked on mekanik)

  • Sensor nodes baru (imu_node, optical_node) publish nav_msgs/Odometry ke odometry_<type>/odom
  • Update odometryRead.js dropdown source untuk sensor baru
  • Handler odometry.py auto-subscribe ke topic baru via _SOURCE_TOPICS dict

Definition Of Done

  • Interface menggunakan nav_msgs/Odometry (bukan custom message)
  • as5600_node publish ke odometry_encoder/odom dengan kiwi wheel kinematics
  • Parameter wheel_radius, wheel_distance, wheel_angles configurable
  • pixi run build-as5600 berhasil — as5600_node compile dengan nav_msgs dependency
  • Handler odometry_read berfungsi di dummy mode (test passes)
  • Blockly block odometryRead dengan source + field dropdowns
  • End-to-end: Blockly → executor (real) → cache odometry_encoder/odom → return value
  • Backward compat: encoderRead block dan encoder_read handler tetap berfungsi
  • Integration test test_block_odometry.py passes di dummy mode