> For the complete documentation index, see [llms.txt](https://docs.veerobot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veerobot.com/ros-robots/beetle-bot-plus.md). # BeetleBot Plus BeetleBot Plus, indoor ROS 2 lab robot. Drive, map, and mission from day one. Built and supported in India. BeetleBot Plus is an indoor four-wheel skid-steer robot for teaching labs, student projects, and research that needs to **work on day one**. Power it on, open a browser or **VEEPanel**, and you are driving, mapping, and running missions, with **ROS 2 Jazzy** already on the robot when you are ready to write your own nodes. {% hint style="success" %} **Designed, built, and supported in India.** You talk to the team that ships the hardware and the software, not a distant reseller chain. Labs that want a serious platform without the price of a heavy research UGV start here. {% endhint %}
BeetleBot Plus

BeetleBot Plus

{% hint style="warning" %} Keep clear of the wheels. Start in a large indoor space. Do not leave the robot unattended while armed. {% endhint %} ## Who it is for * **Teaching labs** that need mapping, navigation, and teleop that students can run the same week the crate arrives * **Student and faculty R\&D** that need a rigid payload deck and a real ROS 2 stack, not a toy that dies at the first custom package * **Demos and open days** that must look professional without a laptop tethered to every robot ## One robot, three ways to work {% tabs %} {% tab title="Operate (no code required)" %} From the **operator app** at `http://:8080` (browser or optional Android **VEEPanel**): * First power-on: if the OLED shows **`19.9.12.1`**, join the robot **`BeetleBot-…`** Wi‑Fi and open that address to save lab Wi‑Fi ([Connect](/veestack/veestack/connect.md#first-connection-robot-wi-fi)) * Live map, RGB camera, battery, and health on one dashboard * Drive with the on-screen stick or the kit gamepad. **ARM** when ready; **E-STOP** when you must * Build a **site map**, fix small map artifacts with **Edit**, save **named places**, send **Go** (or **voice go-to** on VEEPanel) * Run **multi-point missions** with the mission editor * On-robot **Help** and a live “Not working” checklist Full operate path: [VEEStack Operate](/veestack/veestack.md) · hands-on: [Tutorials](/tutorials/beetlebot-plus.md) {% endtab %} {% tab title="Develop (ROS 2 on board)" %} When students open a terminal: * **ROS 2 Jazzy** already installed. SSH as `veerobot@` * Native Nav2 / mapping stack the dashboard already uses * **Foxglove** (port 8765) and **RViz** on a laptop when you want denser views * Live **OpenAPI** at `:8080/docs`, allowlisted publish, and **webhooks** * Your packages live in `~/user_ws` beside the product workspace. Do not rebuild the product stack for class Start: [For developers](/ros-robots/beetle-bot-plus/for-developers.md) · [Laptop ROS and RViz](/ros-robots/beetle-bot-plus/for-developers/laptop-ros.md) {% endtab %} {% tab title="Research (go further)" %} Same robot, your experiment: * Add sensors or a small payload on the deck (rated **2.5 kg** nominal) * Optional **depth camera** and **Jetson Orin Nano** compute * Bags, custom nodes, perception and controller work on a platform that already localizes and drives You keep the operator path for demos; you keep ROS for the paper. {% endtab %} {% endtabs %} ## Why labs choose BeetleBot Plus | You get | Why it matters | | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | | **Ready to operate** | Map, places, missions, and safety controls ship configured. Not a weekend of glue code before the first lab | | **Open where it counts** | Full ROS 2 on the Pi: SSH, topics, Foxglove, RViz, HTTP. When the course needs code, the door is open | | **Built & supported in India** | Hardware and software from one Bengaluru team. Faster answers, no import lottery for every spare or question | | **Serious platform, accessible price** | Production-minded indoor UGV for institutions that need capability without the budget of a large research chassis | No fighting scorecards. One clear offer: **a complete indoor ROS robot your lab can own, teach on, and trust.** ## What arrives with the robot
BeetleBot Plus box contents

Typical kit: robot, wireless gamepad, and charger. Hard case is optional; confirm your packing list.

{% columns %} {% column %} **Every shipment** * BeetleBot, with the battery already fitted * Wireless gamepad, batteries, and USB receiver (usually already plugged into the computer) * Battery charger * One-page printed sheet (Wi-Fi name, robot address, login) Standard packing is a cardboard carton with foam supports. {% endcolumn %} {% column %} **If ordered** * Android tablet with VEEPanel * Depth camera * Rugged hard case (transit case), **optional**; not every order includes one Confirm the packing list against the box before you discard packaging. Missing items: with your order number. {% endcolumn %} {% endcolumns %} ## What’s on the robot | | | | ----------- | --------------------------------------------------------------- | | Computer | Raspberry Pi 5 8 GB (standard) · Jetson Orin Nano 8 GB (option) | | Operator UI | `http://:8080` · optional VEEPanel tablet | | LiDAR | RPLidar C1 (2D, 360°) | | Camera | RGB fitted and licensed · depth optional | | Drive | Four-wheel skid-steer · kit gamepad | | Battery | 3S Li-ion installed · Standard or Extended pack | | Software | VEEStack operator app + ROS 2 Jazzy + navigation | ## First session (about one hour) 1. Power on (rear switch, red ring). Wait for the OLED to show an IP. 2. Join the same Wi-Fi as the sheet. Open `http://:8080` or VEEPanel. 3. Sign in → wait for live telemetry → hold the shield **3 s** to **ARM** → drive. 4. Map your room when you leave the factory floor, then use **places** and **missions** for every later lab. Step-by-step: [Getting started](/ros-robots/beetle-bot-plus/getting-started.md) · full courses: [Tutorials](/tutorials/beetlebot-plus.md). ## Specifications | | | | ------------------------ | ---------------------------------------------------------------------------------------------------------- | | External size (L×W×H) | 375 × 350 × 272 mm | | Ground clearance | 40 mm | | Weight | about 5.85 kg | | Drive | 4-wheel skid-steer · DC gear motors | | Payload | **2.5 kg** nominal (about 4.0 kg structural deck limit) | | Speed | min about 0.1 m/s · normal about 0.8 m/s · turbo max 1 m/s | | Climb (no extra payload) | up to about 35° | | LiDAR | RPLidar C1, \~10 Hz, \~8–10 m typical indoors | | Camera | RGB always fitted · depth optional | | Battery | 3S4P Li-ion · **Standard** 8.8 Ah or **Extended** 12.0 Ah @ 12.6 V full | | Run time (typical) | Idle \~4.4–6.0 h · half speed \~2.8–3.8 h · full speed \~1.6–2.1 h (by pack) | | Charger | 220 V kit charger · **2 A** (standard) or **3 A** (extended) · 2.1 mm rear jack | | Charge time (full) | \~5.5–6.0 h (2 A) · \~5.0–5.5 h (3 A) | | Rear panel | Power (red LED ring), Pi reset, Ethernet, charge jack, 0.91" OLED | | Operator UI | Port 8080 | | Foxglove | Port 8765 (enable in Settings → Plugins) | | SSH | `veerobot@` | | ROS | ROS 2 Jazzy on the robot · [Laptop ROS and RViz](/ros-robots/beetle-bot-plus/for-developers/laptop-ros.md) | | Environment | Operate 5–45 °C · store −5–60 °C · indoor lab (IP40 class) | ## In this manual * [**Tutorials**](/tutorials/beetlebot-plus.md), numbered courses (start here for labs) * [Hardware](/ros-robots/beetle-bot-plus/hardware.md), exterior, top plate, wheels, sensors, gamepad * [Getting started](/ros-robots/beetle-bot-plus/getting-started.md), power, connect, ARM, first drive * [Battery](/ros-robots/beetle-bot-plus/charge-and-battery.md) * [Maps and missions](/ros-robots/beetle-bot-plus/maps-and-missions.md), mapping, places, voice, edit, missions * [Foxglove](/ros-robots/beetle-bot-plus/foxglove.md) * [For developers](/ros-robots/beetle-bot-plus/for-developers.md), ROS 2, RViz, HTTP API, webhooks * [Laptop ROS and RViz](/ros-robots/beetle-bot-plus/for-developers/laptop-ros.md) * [ROS 2](/ros-robots/beetle-bot-plus/for-developers/ros2.md) * [Map from the terminal](/ros-robots/beetle-bot-plus/for-developers/map-from-terminal.md) * [HTTP API and webhooks](/ros-robots/beetle-bot-plus/for-developers/http-and-webhooks.md) * [Troubleshooting](/ros-robots/beetle-bot-plus/not-working.md) ## Talk to us Want a quote, a classroom pack, or a live demo walkthrough? We are the same team that builds the robot. **Sales:** · **Support:** Siliris Technologies Pvt. Ltd. · Bengaluru · [veerobot.com](https://veerobot.com) · [siliris.com](https://siliris.com)