# Boardoza Pulse & Acrome SMD Integration

This section details the communication topology, signal processing flow, and hardware abstraction layers between the Boardoza Pulse S32-S3 master control unit and Acrome SMD Red smart motor drivers.

The system utilizes a distributed control architecture, leveraging the industrial RS485 differential signaling standard to ensure robust data transmission in electrically noisy environments.

### Operation Logic and Signal Flow Diagram

The data flow is structured into three primary phases: Command Generation (Master), Physical Layer Conversion (Gateway), and Actuation (Slave).

#### 1. Master Control Unit (MCU): Boardoza Pulse S32-S3

The Boardoza Pulse acts as the central processing unit (CPU) of the system. It is responsible for trajectory generation, kinematic calculations, and high-level decision-making logic.

* Function: Kinematics solving and command packet generation.
* Interface: UART (Universal Asynchronous Receiver-Transmitter).
* Physical Output: Transmits serial data at TTL logic levels (typically 3.3V) via the J4 Connector.
* Technical Detail: The MCU calculates the target position, velocity, or torque profile and transmits this data via the TX (Transmit) line at a predefined baud rate.

#### 2. Signal Conditioner (Gateway Interface)

This component serves as the physical layer (PHY) bridge. It converts the Single-Ended TTL UART signals from the MCU into Differential RS485 signals suitable for industrial transmission.

* Function: Protocol translation and signal conditioning `(UART TTL ↔ RS485 Differential)`.
* Engineering Rationale: Standard TTL signals are susceptible to attenuation and Electromagnetic Interference (EMI) over long distances. The Gateway encodes the data as a voltage difference between lines A and B. This differential structure utilizes Common Mode Rejection to nullify external noise, ensuring signal integrity over longer cable runs.

#### 3. Smart Actuator (Slave Node): Acrome SMD Red

The Acrome SMD Red is the terminal execution unit. It listens to the RS485 bus, parses incoming data packets, and manages the power stage to drive the motor.

* Function: Packet parsing, address verification, and Power Stage Switching.
* Input Interface: RS485 (Half-Duplex).
* Process: The driver continuously monitors the bus. Upon receiving a valid data packet (verified via Checksum) that matches its unique Node ID, the internal processor interprets the command and applies the necessary PWM signals to the MOSFET bridge to energize the motor coils.

***

<figure><img src="/files/yJmJ6UOXrbXWrI2VuL78" alt=""><figcaption></figcaption></figure>

### Design Justification: Why this Architecture?

From an engineering perspective, this topology is selected based on the following design criteria:

1. Signal Integrity: Motors generate significant inductive noise and switching transients. The differential nature of RS485 provides high immunity against this EMI, preventing data corruption.
2. Scalability: The bus topology allows for a modular design. Multiple drives can be added to the system using a Daisy-chain configuration without altering the core hardware of the controller.
3. Distributed Processing: Computational load is decentralized. The Boardoza Pulse handles the "Motion Planning," while the high-frequency current control loops and PID algorithms are executed locally on the Acrome SMD.


---

# 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://docs.acrome.net/electronics/smd-red/boardoza-pulse-and-acrome-smd-integration.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.
