Recently Updated Pages

This page: structure of this subsystem and where to find what. Make sure you understand the emb...

This page: the short, concrete workflow for using STM32CubeMX to configure an STM32 project and g...

This page: each arm_board protobuffer explained. The protobuffers for the arm_board are passed b...

Architecture and ERC tasks ArUco marker During the navigation task, there will be some l...

This page: Complete protobuf message definitions for the sensor_board component. The protobuffers...

Introduction There are some issues with ethernet. Those are described here. The Issues Arp Table ...

General structure The general structure of how the control system is made, tested, and deployed w...

This page: structure of this subsystem components/driving_board folder contains 4 libraries: firm...

Overview The Communications node bridges the gap between raw UDP/protobuf packets and the ROS2 ec...

Introduction This documentation gives some tips on how to debug the Ethernet Driver. Debug Flags ...

Introduction This documentation is about extra functions, that are not necessary to get it runnin...

udp_forwarder_node.cpp This is the main file running the communications logic on Jonny Boi's side...

Defining terms To do kinematics on the robotic arm, it first needs to be modelled in a way to do ...

What is the PBEnvelope? The PBEnvelope is a wrapper message defined in components/common/envelope...

What are Protobuffers? Protocol Buffers (Protobuffers or protobufs) are Google's binary serializa...

Introduction The platformio.pioc file is the central configurationhere file used to define build ...

Work on this subsystem has not started yet

Code Structure Architecture (Summary) Each board’s main.c acts strictly as an orchestrator. It in...

Introduction This Python script processes a custom PlatformIO configuration file (platformio.pioc...

Communication is a subsystem responsible for bridging the two distinct networks present on the ro...