Tell us why you’re using the Boe-Bot and I’ll send you a Gripper 3.0!
While reviewing our product line sales this past weekend, I noticed that the Boe-Bot stood out as a leading product [as it has been for well over over 25 years]. This got me thinking about the it, and why educators continue to use it. The Boe-Bot may be the most popular educational robot kit ever produced if measured in lifecycle and total units put to use. At it’s peak, customers were able to buy this robot at over 5,000 RadioShack stores!
What is the appeal of the Boe-Bot, as newer, flashy options become available almost daily? The success of the Boe-Bot is a result of the simplicity, printed curriculum, and openness of the hardware. I’ll tell you what I think is special about the Boe-Bot, and if you’re an educator and tell us what you like about it below then I’ll send you a Gripper 3.0.
Open Chassis and Accessible Electronics
Nothing is hidden in this hardware. The Boe-Bot’s design is intentionally straightforward, making it an ideal starting point for students who are new to robotics. Its chassis is uncomplicated, and the assembly process is intuitive, requiring only a basic understanding of mechanics and electronics. The electronics are fully exposed and add-ons/customizations are easy to accessorize.
The “Robotics with the Boe-Bot” Curriculum by Andy Lindsay
One of the most significant factors contributing to the Boe-Bot’s longevity in education is Andy Lindsay’s comprehensive printed book that accompanies it. The “Robotics with the Boe-Bot” curriculum is regarded as one of the best instructional resources in educational robotics. This guide takes students step-by-step through the process of building and programming their robot, offering clear explanations and practical examples. The schematics, pictorials, and sample codes are easy to follow. The book is structured to accommodate various learning styles, ensuring that both visual and hands-on learners can grasp the concepts. For educators, this curriculum is a valuable tool that reduces preparation time and ensures that students are learning from a proven, high-quality resource.
Did you notice that the Robotics with the Boe-Bot book is a printed book? It’s a lay-flat spiral bound 400+ page book. The use of a printed book reduces the alt-tab effect of switching applications to read the tutorials, and copy/paste code examples. The book can lay on the table, opened to the page where the student is working, further minimizing the distraction of screen-time and application switching to read online tutorials. Students also need to type their own code when using a printed book.
PBASIC: A “Close to the hardware” Programming Language with the BASIC Stamp
The programming language at the heart of the Boe-Bot is PBASIC, a language designed to be “close to the hardware.” This is partially a result of the BASIC Stamp’s own design limitations, but the benefit is that very little is hidden from the coder. No libraries or include files, and very little abstraction hides behind each PBASIC command. This is also a drawback as programs become more complex. Basically “you get what you program” and the hardware timing loops are don’t hide any engineering behind the scenes. For example, programming the BASIC Stamp requires the student to fully understand servo control. One example would be the following loop, which drives a servo with a 1 ms “pulse” every 20 ms. Run the loop 150 times to drive forward for three seconds (okay, it’s actually a bit less than 150x because the PULSOUT commands take some time too).
Note that the timing loop must be manually maintained in PBASIC:
FOR Counter = 1 to 150 ' three-second forward
PULSOUT 14, 500 ' HIGH signal of 1 ms (500 us x 2) on P14 PULSOUT 15, 1000 ' HIGH signal of 2 ms (1000 us x 2) on P15
PAUSE 20 ' wait 20 ms
NEXT
This seemingly basic, timing-specific requirement forces the student to understand the relationship of time to their coding practices. The loop runs 100 times and the Boe-Bot rolls forward several inches. Any sensor-checking or logic decisions occur in the 20 ms pause, and their timing requirements must also be considered in this loop. Talk to too many sensors and add in some serial communication, and you’ll find out that you’re not spending enough time caretaking this 20ms loop!
By comparison, the Python used in the cyber:bot sets a servo speed in the following way:
# forward_three_seconds from cyberbot import * bot(18).servo_speed(75) # Full speed forward bot(19).servo_speed(-75) sleep(3000) # Wait three seconds bot(18).servo_speed(None) #Stop bot(19).servo_speed(None)
That’s right — it’s “set it and forget it” thanks to the cyber:bot library that supports the servo_speed command. All the student needs to do is state the speed in their Python script once, and the servo timing will be maintained by the micro:bit, thanks to the cyberbot library. This is very helpful, as the use of a library abstracts the timing requirements needed by the servo.
The introductory nature of PBASIC and Python have similar comfort. BASIC might be old, and limiting without libraries, but it’s still easy to read and does the job well. For students, this close connection between code and action is both fascinating and educational, helping them to develop a deeper appreciation for the mechanics of robotics.
Why are you using the Boe-Bot?
I’ve explained why I think it’s popular. The printed book is a complete guide, PBASIC is close to the hardware and easy to code, and the kit simply works really well. And this makes it engaging to students. What educators want the most is to be effective, and student engagement is one of their most important measures.
Tell us why you are using the Boe-Bot! I’ll send your a Gripper 3.0 for your contribution posted below, but pay attention to those servo timing loops once you add this popular accessory!
Ken Gracey
Parallax Inc.
