# VBCores

**VB Cores** is a system of electronic modules and software examples designed to simplify and accelerate the development of robotic devices. The system is primarily tailored for:

* **Educational institutions** 
* **Startups and research laboratories** .
* **Advanced Developers**: Full access to firmware and schematics for custom robot control.

***

#### **Core of the System: VBCore Microcontroller Module**

The VBCores VB32G4 combines the processing power and rich peripherals of an STM32G474RE microcontroller with an 60V input power supply and FDCAN transceiver, all in a tiny (30.48mm x 38.1mm) form factor suitable for integration into products. It provides an affordable, convenient and flexible way to create electronic hardware in bot h development and production stages. 

Any embedded software developer can use this device with ease thanks to compatibility with Arduino IDE (STM32duino), STM32Cube and all other products compatible with STM32G4 MCUs.

Key features include:

* **Built-in power converter** supporting voltages up to **60V** — connect batteries directly.
* **CAN FD interface** for high-speed communication between robot nodes.
* **Compact design with single-sided mounting** — easily integrates into any board (motor drivers, sensors, etc.).
* **Convenient debugging** : a dedicated programming port accessible even in assembled devices.

The module handles electronics management, allowing developers to focus on robot logic.

***

#### **What’s in the System?**

**Electronics** :

* **VBCore32G4 microcontroller module** .
* **Motor control boards** : for brushed, brushless (BLDC), and stepper motors.
* **Power management boards** : battery monitoring, energy distribution.
* **CAN FD converters** (SPI, Ethernet).
* **Sensors and auxiliary devices** .

**Code examples and libraries** :

* Motor control.
* ROS / ROS2 integration
* Ready-to-use solutions for **Arduino IDE** and **STM32** .

***

#### **Typical Robot Architecture with VB Cores**

1. **Power** :
   * Battery (up to 50 V) → power management board ensures energy distribution and monitoring.
2. **Control** :
   * **Microcomputer** (e.g., Raspberry Pi or x86) for high-level tasks (navigation, AI).
   * **Drivers / sensor boards** for low-level control of motors and sensors.
3. **Communication** :
   * **CAN FD** — for data exchange between modules.
   * **Cyphal protocol** — for reliable communication in distributed systems.

***

#### **Software: Ready-Made Solutions**

**Libraries** :

* **libcxxcanard** — Cyphal protocol implementation ([https://opencyphal.org/ ](https://opencyphal.org/)).
* **cyphal\_ros\_bridge** — ROS/ROS2 integration ([https://github.com/VBCores/cyphal\_ros\_bridge ](https://github.com/VBCores/cyphal_ros_bridge)).
* **VBCoreG4\_arduino\_system** — simplified setup for Arduino IDE ([VBCoreG4\_arduino\_system](https://github.com/VBCores/VBCoreG4_arduino_system)).
* **libvoltbro** — examples for STM32 peripherals ([libvoltbro](https://github.com/VBCores/libvoltbro)).

**Code examples** :

* Motor control, acquire sensor data, communication setup.

***

#### **Advantages**

* **Time-saving** : No need to design basic components — use pre-built modules.
* **Flexibility** : Create devices of any complexity, from educational robots to advanced prototypes.
* **Compatibility** : Supports **CAN FD** , **Cyphal** , and **ROS** standards.
* **Openness** : Schematics, code, and documentation are publicly available.

**VB Cores** eliminates routine tasks, letting you focus on your robot’s unique features.

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://voltbro.gitbook.io/en-vbcores/vbcores.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.