Technical Report of Auriga's 1:10 Scale Autonomous Vehicle Robot
Organizations: Team Auriga, Faculty of Electrical Engineering, Shahid Beheshti University, Tehran, Iran
Abstract
This report presents the design and implementation of Auriga Robotics' 1:10 scale autonomous vehicle, developed at Shahid Beheshti University's Robotics and Intelligent Automation Laboratory. The platform integrates a custom mechanical chassis, a distributed embedded system based on ESP32 microcontrollers, and a Jetson Orin NX module for high-level perception and control. The embedded layer manages sensor interfacing, real-time data acquisition, and actuator control, while the Jetson handles environment perception through deep-learning--based lane, sign, and traffic light detection, as well as decision-making and trajectory control. System communication is achieved via structured UART links, ensuring synchronized operation between perception and control subsystems. The vehicle's software stack incorporates ROS, modular firmware design, and multiple control algorithms---Stanley, PID, and Pure Pursuit---to achieve stable autonomous navigation in structured driving scenarios. The overall system demonstrates robust performance and reliability in urban-like environments, serving as a modular research platform for future autonomous driving studies.
Figures & tables
| Dimension | Value (cm) |
|---|---|
| Wheelbase (front axle to rear axle) | |
| Vehicle width | |
| Overall length (front bumper to rear bumper) | |
| Height |
| Unit | Processor | Primary Function |
|---|---|---|
| Jetson Orin NX | ARM Cortex-A78AE + GPU | Perception and control logic |
| CONTROL ESP32 | Xtensa LX6 Dual-Core | Intermediary communication layer, actuator interfacing |
| ZERO ESP32 | Xtensa LX6 Dual-Core | Sensor acquisition, low-level actuation |
| MCU | Task | Core | Prio. | Function / period |
|---|---|---|---|---|
| ZERO | Sensor read and transmit | 0 | 10 | Reads all sensor data, builds and sends packet p1 . |
| ZERO | Instruction receiver | 0 | 10 | Parses p3 (motor command, ToF bitmask); 1-tick polling |
| ZERO | ToF reader | 1 | 13 | Sweeps the 12 ToF sensors every 41 ms; pushes results to a queue |
| ZERO | Button monitor | 1 | 15 | Debounces the motor cut-off button (ISR-flagged) (this task was not included in Fig. 4 but is implemented). |
| CONTROL | ZERO Jetson forwarder | 0 | 10 | Receives p1 from ZERO, checks its integrity and forwards it to Jetson |
| CONTROL | NeoPixel handler | 1 | 10 | Applies the light mode; 5-tick polling, 500 ms blink toggle |
| Parameter | Meaning | Value |
|---|---|---|
| heading process noise | ||
| residual-bias random-walk noise | ||
| magnetometer heading noise | ( ) | |
| field-deviation scale in Eq. 29 | ||
| before first update | initial heading variance | |
| initial residual-bias variance |
| Packet | Direction | Length | Wire time | Fields |
|---|---|---|---|---|
| p1 | ZERO CONTROL Jetson | 85 B | 7.4 ms/hop | 12 ToF distances (mm), compass bearing (0.1 ∘ ), encoder count, speed, motor-enable flag, time elapsed, checksum |
| p2 | Jetson CONTROL | 25 B | 2.2 ms | steering command (0–255), buzzer, motor command ( 1023), light mode, ToF bitmask, checksum |
| p3 | CONTROL ZERO | 18 B | 1.6 ms | motor command, ToF bitmask, checksum |
| Node | Inputs | Primary Function / Outputs |
|---|---|---|
| Camera | Intel RealSense D455 | Captures synchronized RGB and depth frames at and writes them to shared memory. Publishes a startup-ready parameter after the first valid frame. |
| Sign | Shared memory frames | Performs traffic sign detection. Publishes sign_topic (sign type and distance) and cross_input to trigger crosswalk processing. |
| Network | Shared memory RGB frame | Runs lane segmentation model and writes a tensor to shared memory. |
| Postprocess | Network output + RGB frame | Extracts lane offset and heading angle, published on line_topic . |
| Crosswalk | RGB frame + cross_input | Computes crosswalk angle and position, and receives the intersection parameter from Control. |
| Control | Perception topics + uart_topic | Computes steering, throttle, and mode, publishing serial data to the Listener. |
| Block Name | Type | Input Res. | Out Ch. | Engineering Rationale |
|---|---|---|---|---|
| Stem | Conv2D + PReLU | 64 | Aggressive downsampling to reduce memory footprint. | |
| HG-Block 1 | Standard Hourglass | 128 | Initial coarse feature extraction. | |
| HG-Block 2 | Standard Hourglass | 128 | Refinement of features with skip connections. | |
| HG-Block 3 | Dilated Hourglass | 128 | Custom: Uses dilation rates (2, 4) to expand receptive field for sharp turns. | |
| Heads | Conv 1x1 | 7 | Projects features into: 1x Confidence, 2x Offsets, 4x Embeddings. |
| Case | Condition | Action |
|---|---|---|
| 1 | Path assumed locally straight: advance the last known sign distance directly, commanded by the encoder. | |
| 2 | and | Curve detected, but the arcsine relation of Case 3 is outside its valid domain ( ); fall back to the same straight-line action as Case 1. |
| 3 | and | Curve detected and the sign lies within the estimated turn radius: use the arc-length correction of Eqs. 70 – 71 instead of the raw distance . |
| Version | Core Approach | Key Strengths | Key Limitations |
|---|---|---|---|
| Ver. 1 | Open-loop, hardcoded actuation triggered at a fixed 10 cm distance from the sign (e.g., advance 30 cm, then turn until a preset heading change is sensed by the compass). | Minimal development time. | Only IMU feedback; almost entirely dependent on a fixed approach geometry. |
| Ver. 2 | Added intersection-approach angle. A PID loop first corrects heading error, then the same hardcoded turning actions as Ver. 1 are executed. | Introduces road-relative feedback. Simpler algorithm; fewer tuneable parameters. | High perception noise from a low-quality, poorly mounted camera; the vision data was only reliable in a narrow crosswalk viewing position, so the feedback loop had to re-sample it 2–3 times. Failed when the vehicle approached skewed toward the right edge of the road. Could not handle intersections on curved roads. Two-lane validation was added but was not accurate enough to enable feedback after the crosswalk or inside the intersection. |
| Ver. 3 | Generalized further: road curvature ( ) was introduced to estimate the distance the vehicle must travel through a bend to reach the sign, with turn direction (CW/CCW) taken from perception. | Broader applicability across road geometries. | More parameters to tune and longer development time than earlier versions. Increased generality reduced reliability: at plain, straight intersections the algorithm could still unnecessarily factor in crosswalk angle and curvature, causing failures over part of the intersection design space. |
| Ver. 4 | Adopted the vehicle’s bicycle-model kinematics to reach the target lane more reliably and directly, motivated by a reduced maximum steering angle that had been increasing the distance travelled in the opposing lane. Repositioning between an initial and target pose is solved as a three-segment steering maneuver (section 5.2 ), with the required encoder (CMPS) travel computed for each segment. The same model-based CMPS estimation is used to judge how far the vehicle must travel through a curve to reach a set distance from the sign, replacing noisy curvature-based perception. A dedicated feedback behavior biases the vehicle slightly left to counteract drift toward the right edge; once the vehicle reaches the crosswalk at a shallow, safe angle with no risk of edge proximity, the three-segment maneuver is executed using the measured crosswalk-approach angle. | More reliable: grounded in the actual vehicle kinematic model rather than hardcoded actions. More accurate sign approach in sharp intersection turns, by relying on the vehicle model and CMPS changes instead of noisy curvature perception. | Highly sensitive to the mechanical design, steering calibration (section 5.5 ) and measurement accuracy (section 3 – 5 ); imprecise geometry directly degrades the open-loop maneuver. Tends to look mechanically stiff, and a reverse segment is less visually natural — a potential drawback for real-world user acceptance. |
| Control | Commanded | Combined | Combined | Combined | Mean | T- | P- | Significant |
|---|---|---|---|---|---|---|---|---|
| Input | Angle ( ∘ ) | Mean ( ∘ ) | StdDev ( ∘ ) | Var ( ∘ ) | Diff. ( ∘ ) | Statistic | Value | ( ) |
| 0 | 2.204 | 4.857 | 0.8904 | No | ||||
| 25 | 1.068 | 1.140 | 0.0231 | Yes | ||||
| 50 | 1.013 | 1.027 | 0.2577 | No | ||||
| 75 | 1.374 | 1.887 | 0.1051 | No | ||||
| 90 | 1.888 | 3.565 | 0.3494 | No |
| Right wheel | Left wheel | |||||||
|---|---|---|---|---|---|---|---|---|
| ( ∘ ) | Model (cm) | Meas. (cm) | (cm) | ( ∘ ) | Model (cm) | Meas. (cm) | (cm) | |
| 0 | −44.09 | 35.50 | 36.7 | −1.20 | −38.30 | 32.49 | 30.0 | +2.49 |
| 25 | −35.77 | 31.43 | 36.7 | −5.27 | −30.85 | 29.70 | 29.5 | +0.20 |
| 50 | −27.46 | 28.74 | 29.3 | −0.56 | −23.41 | 27.79 | 27.5 | +0.29 |
| 75 | −19.14 | 26.99 | 28.7 | −1.71 | −15.97 | 26.52 | 26.3 | +0.22 |
| 90 | −14.15 | 26.30 | 27.2 | −0.90 | −11.50 | 26.02 | 25.8 | +0.22 |
| Statistic | Right wheel | Left wheel | Pooled |
|---|---|---|---|
| Sample size | 13 | 13 | 26 |
| Mean residual (cm) | −0.05 | −0.09 | −0.07 |
| Std. deviation (cm) | 2.18 | 1.13 | 1.70 |
| Std. error of mean (cm) | 0.60 | 0.31 | 0.33 |
| 95% CI of mean (cm) | [−1.36, 1.27] | [−0.77, 0.59] | [−0.75, 0.62] |
| -test vs. zero, -value | 0.941 | 0.776 | 0.839 |
| (°) | (°) | Required (°) | Measured (°) | Ackermann (%) | ||
|---|---|---|---|---|---|---|
| 0 | ||||||
| 25 | ||||||
| 50 | ||||||
| 75 | ||||||
| 190 | ||||||
| 215 |
| Wheel | Extreme angle (deg) | Setpoint | (cm) |
|---|---|---|---|
| Right | |||
| Right | |||
| Left | |||
| Left |
Autonomous Driving
Autonomous driving develops vehicles that perceive road scenes, predict interactions, and plan and control safe movement with limited or no human input.
See all 570 papers