Pololu Blog » Posts tagged “raspberry pi” »
Posts tagged “raspberry pi” (Page 2)
You are currently viewing a selection of posts from the Pololu Blog. You can also view all the posts.
Popular tags: community projects new products raspberry pi arduino more…
Just Keep Swimming: a goldfish-steered mobile fish tank
 |
During Build18 2017, “an annual engineering festival held by the Electrical and Computer Engineering department at Carnegie Mellon University and run by students”, a team of CMU students presented a goldfish-steered mobile fish tank that allows the goldfish to decide where to drive. The robot is controlled by a Raspberry Pi and uses some Pololu parts listed below. They posted a video of the robot on Facebook, and their project webpage has a description and a parts list.
Related products
A Raspberry Pi robot without a HAT
 |
Using an Arduino shield or Raspberry Pi add-on board is often a quick and convenient way to get started on a robotics project, but for maximum flexibility, nothing beats building your own system from standalone boards. Rud Merriam’s Hackaday article describes the design of his Raspberry Pi-controlled robot, for which he opted to use separate modules instead of daughterboards on the Pi, and mentions some of the trade-offs involved in making that decision.
The robot is built on a Wild Thumper chassis and uses a Maestro USB servo controller and two Simple Motor Controllers to interface the Raspberry Pi with the robot’s motors and actuators. In Rud’s writeup, he explains how he made use of some of the more advanced features of the Maestro and SMCs, like using servo channels for general-purpose I/O and setting up daisy-chained serial communications. Check out the full article for all of the details.
Related products
New product: Raspberry Pi 3 Model B
 |
We are now offering the Raspberry Pi 3 Model B. The Raspberry Pi is a popular credit card-sized computer that can run ARM Linux distributions. As the successor to the Raspberry Pi 2 Model B, the Pi 3 has a more powerful processor and adds wireless connectivity. Here are the specific improvements:
- 1.2 GHz 64-bit quad-core ARMv8 CPU
- 802.11n Wireless LAN
- Bluetooth 4.1
- Bluetooth Low Energy (BLE)
Along with these improvements, the Raspberry Pi 3 maintains compatibility with and the form factor of the previous Pi 2 (and Pi 1 Model B+). With its 0.1″-spaced GPIO header and small size, the Raspberry Pi also works as a programmable controller in a wide variety of robotics and electronics applications. It can also be combined with our A-Star 32U4 Robot Controller LV with Raspberry Pi Bridge to make a great controller for a small robot. We also carry a selection of Raspberry Pi expansion boards.
|
|
This comparison chart can help in selecting the right Raspberry Pi for your project:
 Raspberry Pi Model A+ 512MB |
 Raspberry Pi Model B+ |
 Raspberry Pi 2 Model B |
 Raspberry Pi 3 Model B |
 Raspberry Pi 3 Model B+ |
|
|---|---|---|---|---|---|
| CPU: | BCM2835 | BCM2836 | BCM2837 | BCM2837B0 | |
| CPU cores: | 1 | 4 | |||
| CPU speed: | 700 MHz | 900 MHz | 1.2 GHz | 1.4 GHz | |
| RAM: | 512 MB | 512 MB | 1 GB | ||
| Ethernet: | No | Yes | |||
| WiFi: | No | 2.4 GHz 802.11n | 2.4 GHz 5 GHz 802.11b/g/n/ac | ||
| Bluetooth: | No | 4.1 | 4.2 | ||
| Bluetooth Low Energy: | No | Yes | |||
| HDMI: | Yes | ||||
| Analog video: | Yes1 | ||||
| SD socket: | microSD | ||||
| Onboard regulators: | switching | ||||
| Expansion header pins: | 40 | ||||
| USB ports: | 1 | 4 | |||
| Mounting holes: | 4 | ||||
| Dimensions2: | 2.5″ × 2.2″ × 0.47″ | 3.35″ × 2.2″ × 0.8″ | |||
| Weight3: | 23 g | 42 g | 50 g | ||
1 Audio and analog video provided by a single four-pole 3.5 mm jack. This 3.5 mm jack also has its own dedicated low-noise power supply for improved audio.
2 Length and width measurements are for the PCB only; several of the connectors extend past the edge of the board.
3 Weight does not include microSD cards.
Related products
Building a Raspberry Pi robot with the A-Star 32U4 Robot Controller
In this post I will show you how to build an expandable robot platform based on a Raspberry Pi and an A-Star 32U4 Robot Controller. With this platform, the powerful Raspberry Pi can take care of high-level tasks like motion planning, video processing, and network communication, while the A-Star, which mounts to the Pi’s GPIO header, takes care of actuator control, sensor inputs, and other low-level tasks that the Pi is incapable of. The total cost of the parts I used is about $120. Continued…
New product: A-Star 32U4 Robot Controller SV with Raspberry Pi Bridge
 |
Our A-Star 32U4 Robot Controller SV with Raspberry Pi Bridge is now available, joining the LV version we released six months ago.
Similar to its lower-voltage sibling, the Robot Controller SV is a general-purpose robot controller that includes dual motor drivers and other useful peripherals like pushbuttons and a buzzer. It also has the same level shifters and power circuit that allow it to easily power and communicate with a Raspberry Pi when mounted as an auxiliary controller. Like our other A-Star controllers, the A-Star Robot Controller SV built around an ATmega32U4 microcontroller and ships preloaded with an Arduino-compatible USB bootloader.
This SV version of the A-Star Robot Controller uses an efficient step-down switching regulator, enabling it to operate (and optionally supply power to an attached Raspberry Pi) with input voltages from 5.5 V to 36 V. Compared to the LV version, the Robot Controller SV can also supply substantially more current across its wide operating voltage range:
 |
We’ve been working on some (long-awaited) I²C software to allow the A-Star to be used as a slave controller with a Raspberry Pi master, as well as an example project that shows how to build a robot with this setup. They’re nearly ready, so watch for them on the blog in the coming weeks. But don’t forget that the A-Star board can also be used by itself as a capable robot controller, as my recent sumo robot demonstrates.
To facilitate both of these uses, the A-Star 32U4 Robot Controller SV is available either assembled for use as a Raspberry Pi add-on or in a more barebones configuration that is suitable for customized assembly or standalone use. See those product pages and the user’s guide for more information about the robot controller.
Related products
New products: Raspberry Pi Model A+ and Raspberry Pi 2 Model B
We now have three "Pi"s! …No, I’m not talking about our 3pi robot.
 |
In addition to the Raspberry Pi Model B+ we’ve been carrying, we now offer the smaller Raspberry Pi Model A+ and the more powerful Raspberry Pi 2 Model B as well. Check out their product pages for details about each version and how they compare to each other.
|
|
 |
Raspberry Pi Model B+. |
|---|
As with the B+, the A+ and 2 B are compatible with our Raspberry Pi expansion boards, including our A-Star 32U4 Robot Controller with Raspberry Pi Bridge and our MC33926 and DRV8835 motor driver add-ons.
 |
Related products
Pi Wars 2015
There is a nice recap on the Raspberry Pi blog of the Pi Wars 2015 competition that was held last weekend on December 5th, 2015. It is a robotics competition held in Cambridge, UK that focuses on robots controlled by a Raspberry Pi. I noticed a lot of Pololu parts on the robots in the videos. Just a few examples are wheels and tracks, motors, and reflectance sensors. I didn’t see any A-Star 32U4 robot controllers in the videos, but I think that would make a great controller for a robot in the next competition because it can be used as a Raspberry Pi expansion board!
You can check out the Pi Wars 2015 post for more details.
Raspberry Pi Solar Tracker
Jay Doscher posted on his blog at Polyideas.com about his 2-axis solar tracker designed to provide the optimal amount of power output with a portable setup. In the build, Jay uses a Raspberry Pi A+ topped with our Dual MC33926 Motor Driver for Raspberry Pi to control the motion of the system, which is accomplished using a Concentric 4″ linear actuator with feedback. In lieu of a GPS unit, the tracker uses hard-coded longitude and latitude coordinates with Pysolar, an open-source Python library, to calculate the sun’s predicted position. The system keeps the solar panel pointed at the calculated position with the help of a Razor IMU from SparkFun. The video above is time lapse footage of a mechanical test of the system that shows the unit tracking the sun (although it is indoors).
 |
In the picture above, you can see the Raspberry Pi and dual MC33926 driver board on the left and the IMU on the right. The Dual MC33926 Driver for Raspberry Pi fits on top of the Raspberry Pi mainboard, eliminating a lot of wiring and making it easy to use while also leaving the setup looking clean and organized. Additionally, the Dual MC33926 Driver for Raspberry Pi provides a set of three through-holes where an appropriate voltage regulator can be conveniently connected, allowing the motor supply to also power the Raspberry Pi. You can see one of our D24V10F5 switching step-down regulators mounted on top of the dual MC33926 driver board to serve this purpose in the picture above as well.
 |
This project was also a 2015 Hackaday Prize entry and made it to the quarterfinals!
For more information about this project, see Jay’s blog post, which has additional photos and details including a parts list and links to his code.
Related products
New product: A-Star 32U4 Robot Controller with Raspberry Pi Bridge
 |
I am excited to announce our new A-Star 32U4 Robot Controller LV with Raspberry Pi Bridge, a general-purpose robot controller based on Atmel’s ATmega32U4 microcontroller.
This new robot controller is the latest model in our A-Star line of Arduino-compatible USB microcontroller boards. We started with the A-Star 32U4 Micro and have been gradually expanding the line, adding peripherals and various form-factor and voltage options, with the goal of eventually replacing our older Orangutan robot controllers. The Zumo 32U4 was a major step in that direction, since its controller board is essentially an A-Star 32U4 plus extra peripherals for motor control and sensing. But while the Zumo 32U4 is a complete robot kit, this board is for people who want to design their own robot.
The A-Star 32U4 Robot Controller LV includes most of the features of the A-Star 32U4 Prime LV, including an Arduino-compatible USB bootloader, an efficient step-up/step-down regulator, and handy peripherals like the buzzer and buttons, and it expands on the A-Star line by adding a pair of Texas Instruments DRV8838 1.8 A motor drivers, the same motor drivers as on the Zumo. All of the AVR’s GPIO lines are broken out, and we have included handy power and ground rails so you can easily connect lots of things like servos and sensors:
 |
This board is well-suited for small robots that would have otherwise used an Orangutan controller like the SV-328 or SVP-1284. While we did not include an LCD like on the Orangutans, you can get far better display, monitoring, or data logging by making use of the Raspberry Pi connection, which I will talk about next.
Using the robot controller with a Raspberry Pi
The Raspberry Pi is a great board for an embedded project that needs serious computational power or connectivity. We have released a couple of Raspberry Pi motor driver boards over the past year, which give you a way to get started exploring robotics with your Raspberry Pi. But robotics projects tend to use a lot of analog sensors, timing-sensitive devices like servos, and other peripherals that are not compatible with the limited I/O capabilities of the Raspberry Pi. These types of things are what microcontrollers are designed for, so you can do a lot more if you pair your Raspberry Pi with a complete microcontroller board.
That’s why instead of using the standard Arduino form factor like the Prime, we built the A-Star 32U4 Robot Controller LV to double as a Raspberry Pi HAT:
 |
A-Star 32U4 Robot Controller LV with Raspberry Pi Bridge on a Raspberry Pi Model B+. |
|---|
The Robot Controller fits on top of a Raspberry Pi A+/B+/2, powers the Pi, and connects to it as an I²C slave device, giving you a bidirectional channel of communication between the two processors. We have broken out all of the GPIO of the Raspberry Pi, and there are a few general-purpose level-shifters included on the board to help you experiment with other communications protocols or interface other hardware to your system. We even include the EEPROM required by the HAT specification, though we have not found it to be particularly useful – we ship it blank and unlocked for you to experiment with.
For more information about the A-Star 32U4 Robot Controller LV, or to order, see the product page. You can also check out our open-source A-Star 32U4 Arduino library, which provides easy access to the main features of the Robot Controller, including its motor drivers; we will be adding examples showing I²C communication with the Raspberry Pi soon.
Related products
New product: Pololu Dual MC33926 Motor Driver for Raspberry Pi
 |
The Pololu Dual MC33926 Motor Driver for Raspberry Pi is our latest offering designed to help you build a robot around the powerful and versatile Raspberry Pi single-board computer. It features a pair of Freescale MC33926 motor drivers, each capable of supplying a motor with up to 3 A continuous (5 A peak) at voltages from 5 V to 28 V. This makes it a good choice for driving bigger things like our 25D and 37D motors and even linear actuators.
 |
Driving motors with a #2756 dual motor driver on a on a Raspberry Pi Model B+ or Pi 2 Model B. A step-down regulator provides 5 V to the Raspberry Pi. |
|---|
We particularly like using the MC33926 because of its robustness: it can withstand voltage transients up to 40 V, and it has a current regulation feature that actively limits the output current to a safe amount. Furthermore, the driver automatically lowers the current limit as its temperature increases, allowing it to gracefully reduce the motor current instead of abruptly shutting down.
This add-on board is a step up from the relatively minimal, lower-power DRV8835 motor driver expansion we released last year, but it is just as easy to use. Our Python library helps you quickly get your motors running with the board’s default pin mappings, which use logic gates to enable drive/brake operation of the MC33926 drivers with only two control pins per motor.
Additional inputs and outputs on the MC33926 drivers are exposed for advanced users who want to make use of other configurations and control methods, and a small prototyping area on the side of the board provides a convenient space for adding custom circuits. As with the DRV8835 board, you can optionally connect a voltage regulator (not included) to power the Raspberry Pi from the motor power supply.
The motor driver board is available in two versions:
- a partial kit, with connectors included but not soldered in
- fully assembled, with the female header and terminal blocks soldered to the board
|
|
If you’re familiar with other Raspberry Pi add-on boards, you might find it unusual that we are not calling this board a “motor driver HAT”. In fact, it meets most of the requirements needed to qualify as a Raspberry Pi HAT (Hardware Attached on Top): it matches the HAT mechanical specification, and it even includes the recommended ideal diode circuit, allowing the optional regulator and the Raspberry Pi’s usual USB Micro-B power supply to be safely connected at the same time.
The reason the board does not qualify as a HAT is the absence of an ID EEPROM. Such a component is intended to allow the Raspberry Pi to identify a HAT board and configure itself to work with that board. We spent some time looking into how an ID EEPROM might help make this motor driver expansion better or easier to use, and we made provision for adding one in the design of the PCB, but eventually we concluded that it seems to offer no substantial value for this kind of board. (We’ve even seen some similar HATs from other manufacturers that ship with a completely blank EEPROM!)
Automatic configuration might be useful for making the Raspberry Pi automatically load a Linux device driver for an I²C or SPI add-on, but since this motor driver expansion is controlled with direct manipulation of GPIO pins, the responsible program or library can easily set up the pins itself before it begins driving and reading them. Other use cases, like enabling the Raspberry Pi to detect whether the HAT is connected and potentially distinguish between different versions of the HAT, would require much more complex support software to take advantage of while being of questionable benefit.
As a result, we’ve decided to omit the ID EEPROM from the board, even if that means it doesn’t meet the full HAT specification and shouldn’t be called a HAT. The EEPROM format specification still appears to be preliminary and subject to change, so it’s possible that future Raspberry Pi updates will make the EEPROM more useful; if so, we will likely reconsider the decision not to populate the EEPROM chip. However, if you think we’ve missed an argument for including an ID EEPROM now or have any other thoughts on its value, we’d be interested to hear your observations.
Related products
Home | Forum | Blog | Support | Ordering Information | Wish Lists | Distributors | BIG Order Form | About | Contact
© 2001–2023 Pololu Corporation
