Creative Commons images are CC BY 2.0

Description: This buzzer is an add-on for your RedBot that gives your robot the ability to make awesome beep-boop noises or alerts when something interesting (or terrible) happens. The buzzer works by making use of two I/O pins on a controller board to create different noises based on the different frequency of I/O toggling. If you are using this buzzer on a RedBot, simply plug it in to one of the many 3-pin I/O ports and get your robot to make some noise.

The buzzer has a 3-pin header which connects directly to the RedBot Mainboard or via male to female jumper wires. Use the included RedBot library to detect sound alarms and make some noise.

Check out the entire RedBot family of products!

Dimensions: 1.0" x 0.52" (25.33 x 13.37 mm)


Recommended Products

Customer Comments

  • Why does the description say: “The buzzer works by making use of two I/O pins on a controller board”?

    Should say one I/O pin. + PWR and GND of course

  • No sound clip or youtube video of what this thing actually sounds like?

  • Quicksilver, I think that Digikey sells the buzzer unit by itself. Search for their part #102-1265-1-ND.

    Under $3

  • It would be really cool if you could sell this buzzer by itself, I feel like a tool ordering a single component off of DigiKey sometimes…

  • Can some one provide a snippet of Arduino code or point me to some example Arduino code for operating this RedBot buzzer? I’ve looked through the Redbot library and tutorials, but I can’t seem to find anything on how to get this to work.

  • For those of you who purchased a RedBot and are thinking of upgrading it with some of the new gadgets for it like the Wheel Encoder, they changed the “standard” layout of the line-follower sensors. The old setup for the (left, center, right) sensors was (A2, A3, A6) and it changed to (A7, A6, A3), probably because they were running out of digital pins and they wanted to move one of the line-following sensors to A7 which is analog-only. This is not a big deal as long as you realize the issue exists.

    Making your bot match whatever version of the library and demo code you have is easy - just move some wires if needed. Marking the library match however your bot is wired is also easy: find the 3 lines in a header file or code:

    RedBotSensor lSen = RedBotSensor(NN);
    RedBotSensor cSen = RedBotSensor(NN);
    RedBotSensor rSen = RedBotSensor(NN);

    where NN represents 3 different numbers, and change them to match your setup wiring, if needed. These are normally the only references to the pin numbers.

    With the new gadgets, RedBot is using all available pins (which doesn’t rule out adding a port expander on the I2C bus):

    Left Motor: D2, D4, D5 Right Motor: D7, D8, D6 Line Sensors (l, c, r): A7, A6, A3 Wheel Encoders (l, r): A2/D16, D3 Bumper Sensors (l, r): D10 D11 Serial port: D0, D1 XBEE serial port: A0/D14, A1/D15 Accelerometer: A4/D18, A5/D19, although I2C can handle a practically unlimited number of devices on the bus. Buzzer: D9 User LED: D13 User Button: D12 on newer mainboards. D12 is brought out at the ICSP header so adding a button isn’t hard.

    The old setup sometimes used up to 4 unspecified “servo” devices on PWM pins D3, D9, D10, and D11. If you want that now, you’ll need to choose what devices you want to connect.

Customer Reviews

No reviews yet.