This page (revision-50) was last changed on 2021-03-29 07:49 by Murray Altheim

This page was created on 2020-07-06 05:48 by Murray Altheim

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
50 2021-03-29 07:49 14 KB Murray Altheim to previous
49 2021-03-29 07:48 15 KB Murray Altheim to previous | to last
48 2021-03-29 07:10 17 KB Murray Altheim to previous | to last
47 2021-03-29 07:08 17 KB Murray Altheim to previous | to last
46 2021-03-29 07:07 17 KB Murray Altheim to previous | to last
45 2020-07-21 09:23 17 KB Murray Altheim to previous | to last
44 2020-07-21 09:20 17 KB Murray Altheim to previous | to last
43 2020-07-15 10:23 17 KB Murray Altheim to previous | to last
42 2020-07-13 10:43 16 KB Murray Altheim to previous | to last
41 2020-07-13 09:40 16 KB Murray Altheim to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 29 changed one line
Certainly, which of the many robotic microcomputer/microcontroller platforms (Raspberry Pi, Arduino, micro:bit, etc.), which of the various programming environments (graphical, Python, MicroPython, C++, assembly language), and then which robot to choose has much to do with one's requirements, whether to purchase a ready-made robot, a kit, or design-your-own from either an existing system or truly on your own. And whether to purchase something that grows with one's experience or is limited to the specifics of the chosen robot. I won't mention "age level" since it's pretty clear that a 10 year old and a 70 year old may share the same level of previous experience, interest, and ingenuity.
Which of the many robotic [microcomputer/microcontroller|microcontroller] platforms ([Raspberry Pi], [Arduino], [micro:bit|microbit], etc.), which of the various programming environments (graphical, [Python], MicroPython, C++, assembly language), and then which specific robot to choose has as much to do with one's requirements as which robot is most appealing to the eye. There's also the question as to whether to purchase a ready-made robot, a kit, or design-your-own from either an existing system or a bespoke robot from available parts (truly "on your own"). And also whether to purchase something that grows with one's experience or is limited to the specifics of the chosen robot. I don't consider "age level" really much of a factor since it's pretty clear that a 10 year old and a 70 year old may share the same level of previous experience, interest, and ingenuity. But having the flexibility of multiple programming environments is a factor in any robot's favour.
At line 31 changed one line
For a "club robot", i.e., something that a group of people can cooperatively work together, share ideas and designs, something that has a wide range of programming opportunities, and something that is very well-documented and used by a ''huge'' number of people, well, the __BBC micro:bit__ platform is hard to beat. The micro:bit can be used as a learning tool outside of robotic applications, and because of its edge connector needn't be soldered or permanently connected to a robot.
The [mini-Zumo robots|Zumo Robot] are appealing if competition within a group is a requirement. These are generally Arduino-based, so they'd be programmed in C++. But they're pretty limited beyond line following and knocking each other out of the ring.
At line 33 changed one line
Among the many micro:bit based robots the "votes" were based on durability, expandability, features-to-cost, and finally, aesthetics. While appearance may be considered important to children, my guess is that it's the parents that believe that cuteness counts. It probably does for the first ten minutes. After the cuteness wears off a child probably wants a robot that is something they can learn and be intrigued by, one with a bit of depth. A Lego kit that can only be built one way is less than a set of Lego blocks that continues to spur the imagination.
For a "club robot", i.e., something that a group of people can cooperatively work on together, sharing ideas and designs, something that has a wide range of programming opportunities, and something that is very well-documented and used by a ''huge'' number of people, well, the __BBC micro:bit__ platform is hard to beat. The micro:bit can be used as a learning tool outside of robotic applications, and because of its edge connector needn't be soldered or permanently connected to a robot.
At line 35 changed one line
With that said, our first choice is the __Waveshare Alphabot__, as it has a lot of features for the money, and is probably the most durable of the micro:bit robots listed below. The DFRobot __micro:Maqueen Plus__ or __micro:Maqueen Lite__ are likewise great choices. The Plus has a lot of expansion capabilities, even an AI "smart" camera that can be trained to recognise objects and colours.
Among the many micro:bit based robots the major factors were: durability, expandability, features-vs-cost, and lastly, aesthetics. While appearance may be considered important to children, my guess is that it's the ''parents'' who believe that cuteness counts. It probably does for the first ten minutes. After the cuteness wears off a child probably wants a robot that is something they can learn with and be intrigued by, one with a bit of depth. A Lego kit that can only be built one way is less interesting over the long haul than a set of Lego blocks that can continue to spur the imagination over many years.
At line 37 added 2 lines
With that said, our first choice for a micro:bit robot is the __Waveshare Alphabot__, as it has a lot of features for the money, and is probably the most durable of the micro:bit robots listed below. The DFRobot __micro:Maqueen Plus__ or __micro:Maqueen Lite__ are likewise great choices. The Plus has a lot of expansion capabilities, even an AI "smart" camera that can be trained to recognise objects and colours.