The present application is a U.S. National Stage under 35 USC 371 filing of International Application Number PCT/US2010/002084, entitled “MODULAR ROBOTICS” filed on Jul. 23, 2010, which is a Nonprovisional Application of U.S. Provisional Application Ser. No. 61/343,400, entitled “HERMAPHRODITIC MAGNETIC ELECTRIC CONNECTOR” filed on Apr. 28, 2010, and a Nonprovisional Application of U.S. Provisional Application Ser. No. 61/288,169, entitled “MODULAR ROBOTS” filed on Jul. 24, 2009, which are all incorporated herein by reference.
The present invention is related generally to the learning of science, technology, engineering, and mathematics, and in particular to a robotics construction kit.
Systems exist for children to construct and program robots but no robotics construction toys use the same modular blocks paradigm or enable children to build robots without programming. Existing systems for constructing robots are centralized, with one computer that controls robot operation. None of these products embody a distributed computing model and none allow the modular construction of robots by beginners. The few toys that contain more than one node of computation are passive entertainment products.
The present invention is a decentralized modular system for constructing and programming robots comprising concurrent communicating microcontrollers. The present invention is a robotics construction kit that serves as a platform for children to engage in problem-solving and innovative thinking in science, technology, engineering, and mathematics. By designing and building robotics constructions from an apparently simple set of blocks that encapsulate the kinetic, electronic, and software elements of robots, children and others can encounter, explore, and experiment with basic principles of science and computation. Unlike existing robotics construction kits for education, the present invention embodies computation in almost every element, which affords understanding systems of distributed computation, rather than systems of top-down control.
The invention is further illustrated by the following drawings in which:
As used herein in the specification and claims, including as used in the examples and unless otherwise expressly specified, all numbers may be read as if prefaced by the word “about”, even if the term does not expressly appear. Also, any numerical range recited herein is intended to include all subranges subsumed therein.
The present invention can be any size. For illustration purposes only, blocks 2 can be 40 mm plastic cube-shaped blocks that snap together with magnetic 23 and electric connectors 24, 25, 26 (
Every block 2 contains a microcontroller and supporting electronics. The microcontroller in each block runs a program in firmware, which provides the default behavior of the blocks. All blocks initially run the same firmware program. In alternative embodiments of the present invention, users may replace the initial firmware using a reprogramming interface described below.
There are four categories of blocks: Sensors, Operators, Actuators, and Utilities. Different colors of plastic indicate the block categories. Sensor blocks sense signals from the environment (including light, sound, touch, motion and distance from objects) and pass signals to connected neighboring blocks. Operator blocks apply functions to those signals including arithmetic functions that compute a number from two or more numbers, such as sum, maximum, minimum, inverse and threshold. Actuator blocks convert signals they receive into various types of action. For example, a motorized tread block (
Now turning to
In one embodiment of embedded electronic device 4 one or more printed circuit boards 4A can be configured to be adjacent to an inner surface 12 of side 6. In the case where there is more than one printed circuit board, solder joints 18 electrically couple three individual circuit boards 4A, 4B, 4C, as shown in
Each block 2 contains a core set of identical embedded electronic device 4 on one or more printed circuit boards: a microcontroller, programming header, shift register, and power management circuitry. In addition, some blocks contain additional electronics and mechanics specific to their functions. For example, the motorized tread block (see
Each sensor block and each actuator block has a special face that houses its sensor or actuator. These special faces may or may not contain hermaphroditic connectors to attach to other blocks. For example, the special spinning face 45 of the rotation actuator block 47 (see
Now turning to
Now turning to
Now turning to
Now turning to
Now turning to
Now turning to
Now turning to
Now turning to
The embedded electronic device 4 inside each block 2 includes a printed circuit board 33 having a motherboard 4A, a daughterboard 4B, and wing boards 4C (see
An electrical connector 20 can also use magnetic force to from an integral electrical and structural connector to hold parts together physically as well as electrically to connect pairs of blocks 2.
The connector 20 shown here is four-way rotationally symmetric. It could easily be modified to support a different number of rotations, such as two or six (or more). The connector 20 shown herein supports three electrical contacts, in this case for conducting a power signal, a ground signal, and a data signal, but it could be easily modified for more or fewer contacts.
The connector 20 has a front, or outer surface 11, which contacts another connector when it is connected, and a back, or interior side, which contacts a circuit board.
Embedded magnets 23 on each face or side 6 of block 2 and concentric rings 25, 26 and a center spring pin 24 connect the blocks 2 electrically. The magnets 23 on one block 2 and outer rings 26 on the other block 2 hold each pair of blocks 2 together physically by magnetic force.
When a pair of connectors 20 are held together physically by the magnets 23, and exerts an axial force that compresses the rings 25, 26, which holds the rings 25, 26 firmly against the circuit board 33 behind them. This force also holds the outer rings 26 and spring pins 24 in contact with one another on the outer surface 11 of side 6. The outer rings 26 can be made of any magnetic material, such as stamped steel.
The rings 25, 26 connect electrically using metal spring clips to contact circuit boards 33 mounted on the inner surface 12 of each side 6.
On the back, or interior side, or inner surface 12 of the connector 20, a printed circuit board 33 makes electrical contact with the spring pin 24 and the sprung wings 27, 29 of inner and outer rings 25, 26, respectively.
Each block in a construction possesses a dynamic one-byte value that determines how it operates with regards to software, block data values and behaviors. These values originate in sensor blocks, travel through the construction from block to neighboring block and are consumed by actuator blocks. Thus, sensors are data sources and actuators are data sinks. Operator blocks change data values that pass through them, according to their pre-programmed functions. Utility blocks (except for blocker blocks) simply pass data unchanged.
A Sensor block computes its value from environmental input. A light sensor block, for example, computes a value of 5 in a dark room and over 200 outside on a sunny day. For example, a touch sensor has a resting value of zero and 255 when it contacts another object.
Each Actuator block derives its value from data it receives from its neighbors. The Actuator block's action depends on this value. For example, a tread block drives along a surface with a speed proportional to its value. A Rotation block with a value of zero remains still, but with a value of 127 it rotates its active face at half speed.
The default firmware computes the Actuator block's value as the weighted average of the values it receives from all sources. Values originating closer to the block are weighted higher than values originating further away. The formula is as follows:
V=Sum (V1/D1+V2/D2+. . . Vn/Dn)/n
where n is the total number of packets in the Action block's data store, V1, . . . n are the sensor values in arrived data packets, and D1, . . . n are the distances (hop-counts) for these data packets, respectively.
An Operator block computes its value as a function of the values it receives from its neighbors. The value of a Sum block, for example, is the arithmetic sum of its neighbors' values. The value of a Maximum block is the largest of its neighbors' values.
A simple example illustrates the flow of data values and resulting behaviors.
The robot (shown in
Programs running in the blocks exchange data through the electrical connections on the block faces. They form a network that communicates data from sensor blocks to actuator blocks.
Blocks operate asynchronously, transferring data pairwise with no central clock. Each sensor block's value derives from its embedded sensor. Every other block's value is computed as a function of the number of steps from every sensor data source in the construction, with closer sensors having a greater influence than sensor that are farther away. Two sensor blocks at either end of a chain of blocks, for example, create a gradient of values along the blocks between them.
Each data transfer between a pair of blocks is done as a packet. Packets originate at sensor blocks, which produce the data values from their sensor readings. Packets are consumed by actuator blocks, which use the data values to determine the actuator's physical behavior.
Each packet contains the unique ID of the originating sensor block, a time stamp that indicates when the packet was created, a hop-count, and a data value. Each time a packet moves from one block to another, its hop-count is incremented by one. The hop-count therefore describes the distance the packet has traveled through the network from its sensor block source.
A propagation algorithm in the firmware program running in each block manages the flow of packets through the block. On arrival of an incoming packet from a neighboring block, the propagation algorithm compares the incoming packet's originating sensor block ID with other packets in its store. If any packets in its store have the same ID as the arriving packet, it compares the time stamps of the two packets. If the arriving packet is older than the packet in its store, it ignores the arriving packet. If the packet in its store is older, it deletes the packet in its store and adds the incoming packet to its store.
Each block constantly tries to establish a data connection with each of its neighbors, successively. Whenever a connection between two blocks is established, each connected block adds to its data store the contents of its neighbor's data store, eliminating the oldest packets originating from the same sensor, as described above.
The reprogramming system enables users to change a firmware program that runs in any unit of a distributed modular robot shown in
A distributed modular robot is a collection, also called ensemble, of individual units also called modules, each comprising a microcontroller and additional electronics and mechanical components, and the having the ability to communicate with other units, some but not necessarily all of which include a sensor, such as a light, sound, or distance sensor, or an actuator such as a motor, speaker, or LED.
The overall behavior of a distributed modular robot is produced by local interactions among its units: A distributed modular robot has no single controlling unit. Therefore to program and reprogram the robot's behavior, a user must enter controlling code, called firmware, into individual units.
The reprogramming system described herein enables a user to compose and compile a program on a computer or mobile device, also called the programming platform, and load the resulting compiled firmware code into some or all of the robot's units. This enables a user to change the physical behavior of individual units and hence the behavior of the distributed modular robot.
Other embodiments of the present invention allowed the user to otherwise replace the unit's source code by (i) entering a new source code in an editor on the computer or mobile device, or (ii) editing previously entered source code selected from a database.
The wireless communication unit reports, to the editor and compiler, the currently connected units' identities and connections of the modular robot to the reprogramming environment. The programming editor and compiler displays this to the user, for example as a graph in which nodes represent units 36 and edges represent connections 30 between units (
The programming platform, using the target unit's unique ID as an index, retrieves source code from a database stored on a server and displayed in a text-editing area 43 on the PC or mobile device screen 31. The user enters new source code in the text-editing area, compiles it, and downloads it into a unit.
Upon the user's request, which is indicated for example by the user pressing a button in the editor and compiler's screen interface, the editor and compiler posts the new source code to the database stored on the server, stamped with the current date and time.
The database contains source code for the firmware that is currently running on the unit, as well as previous versions of the firmware. The user can revert to a previous version of the firmware by selecting it in a menu; the editor and compiler displays the source code for this previous version in a text-editing area and the user can compile and download the program into the unit. Other embodiments of the present invention provide the capability of entering a new source code in an editor on the computer or mobile device or editing previously entered source code selected from a database.
In addition to posting the new source code to the database, when the user requests it, the editor and compiler compiles the user's program. If the code compiles without error, the editor and compiler sends the code to the wireless communication unit, which routes it to the designated target unit in the modular robot. The wireless communication unit waits for acknowledgement from the target unit that it has been successfully reprogrammed. When it receives this acknowledgement, the wireless communication unit conveys it to the programming editor and compiler, which in turn conveys it to the user. If the wireless communication unit receives no acknowledgement within a set time, the wireless communication unit conveys this information to the editor and compiler, which conveys to the user that reprogramming has failed.
The user's compiled program is copied from the wireless communication unit through the network of units in the modular robot to its designated target unit.
When a unit in the modular robot receives a reprogramming packet that is targeted for another unit, it passes the packet to all the units it is connected to.
When a neighbor unit 42 in the modular robot receives a reprogramming packet that is targeted for another unit (target unit 40) that is directly connected to it, neighbor unit 42 passes the reprogramming packet to the target unit 40 and prepares to reprogram the target unit 40.
When the target unit 40 receives a reprogramming packet addressed to it, it restarts its microcontroller in reprogramming mode, also called bootloader mode, which begins to execute the bootloader program that is stored in its memory. When the target unit 40 restarts, it signals to its neighbor unit 42 that it is ready and waits for reprogramming by its neighbor unit 42.
The neighbor unit 42 waits until it receives a ready message from the target unit 40 and then reprograms the microcontroller of the target unit 40 using the bootloader program that resides on the microcontroller. The neighbor unit 42 sends the target unit 40 a reprogram message. The target unit 40 resets itself and starts its bootloader program when it receives the reprogram message. The bootloader program sets the target unit 40 to receive a new application program from the neighbor unit 42. The target unit 40 signals to the neighbor unit 42 when the reprogramming sequence is complete, and the target unit 40 passes an acknowledgement packet, also called ready packet, back to the wireless communication unit. Both target and neighbor units then return to their ordinary modes of operation.
While the disclosure has been described in detail and with reference to specific embodiments thereof, it will be apparent to one skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the embodiments. Thus, it is intended that the present disclosure cover the modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalents.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2010/002084 | 7/23/2010 | WO | 00 | 1/24/2012 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2011/011084 | 1/27/2011 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3640018 | Light | Feb 1972 | A |
3768178 | Glassman | Oct 1973 | A |
4183173 | Ogawa | Jan 1980 | A |
4334221 | Rosenhagen | Jun 1982 | A |
4990099 | Marin | Feb 1991 | A |
5172534 | Milner et al. | Dec 1992 | A |
5746638 | Shiraishi | May 1998 | A |
6062937 | Kikuchi | May 2000 | A |
6206745 | Gabai et al. | Mar 2001 | B1 |
6443796 | Shackelford | Sep 2002 | B1 |
6454624 | Duff et al. | Sep 2002 | B1 |
6505087 | Lucas et al. | Jan 2003 | B1 |
6575802 | Yim et al. | Jun 2003 | B2 |
6585553 | Fetridge et al. | Jul 2003 | B1 |
6605914 | Yim et al. | Aug 2003 | B2 |
6626727 | Balanchi | Sep 2003 | B2 |
6733360 | Dooley et al. | May 2004 | B2 |
6795318 | Haas et al. | Sep 2004 | B2 |
6893316 | Maxwell et al. | May 2005 | B2 |
6902461 | Munch et al. | Jun 2005 | B1 |
6939192 | Munch et al. | Sep 2005 | B1 |
7066778 | Kretzschmar | Jun 2006 | B2 |
7316567 | Hsieh | Jan 2008 | B2 |
7322873 | Rosen et al. | Jan 2008 | B2 |
7444205 | Desmond | Oct 2008 | B2 |
7507136 | Patton | Mar 2009 | B2 |
8079890 | Seligman | Dec 2011 | B2 |
20050234592 | McGee et al. | Oct 2005 | A1 |
20060095893 | Vahid et al. | May 2006 | A1 |
20060100739 | Raffle et al. | May 2006 | A1 |
20060136180 | Hansen et al. | Jun 2006 | A1 |
20070262984 | Pruss | Nov 2007 | A1 |
20090273560 | Kalanithi | Nov 2009 | A1 |
20100001923 | Zilber | Jan 2010 | A1 |
20100216548 | Ellis | Aug 2010 | A1 |
Entry |
---|
Bordignon (Robotics & Automation, 2009. ICRA '09, IEEE International Conference on : A Virtual Machine-base Approach for Fast and Flexible Reprogramming of Modular Robots (pp. 4273-4280). |
Bordignon (Robotics and Automation, 2009/ ICRA 2009/ IEEE International Conference: A Virtual Machine-Based Approach for Fast and Flexible Reprogramming of Modular Robots (pp. 4273-4280). |
Schweikardt, E. et al, roBlocks: A Robotic Construction Kit for Mathematics and Science Education, URL: http://code.arc.cmu.edu/lab/upload/sp151-schweikardt.0.pdf, Nov. 4, 2006, pp. 1-4, Banff, Alberta Canada. |
Schweikardt, E. et al, Learning About Complexity with Modular Robots, Digital Games and Intelligent Toys Based Education, 2008 Second IEEE Int'l Conference ON, IEEE, Piscataway, NJ, USA, Nov. 17, 2008, pp. 116-123. |
Schweikardt, E. et al, A Brief Survey of Distributed Computational Toys, Digital Game and Intelligent Toy Enhanced Learning, 2007, The First IEEE Int'l Workshop ON, IEEE, PI, Mar. 1, 2007, pp. 57-64. |
International Search Report and Written Opinion for International Application No. PCT/US2010/002084 dated Sep. 27, 2010. |
International Preliminary Report on Patentability for International Application No. PCT/US2010/002084 dated Feb. 2, 2012. |
Number | Date | Country | |
---|---|---|---|
20120122059 A1 | May 2012 | US |
Number | Date | Country | |
---|---|---|---|
61228169 | Jul 2009 | US | |
61343400 | Apr 2010 | US |