Selection and control of motion data

Abstract

A motion system comprising a controller, a media source, a motion device, a display, and a software program. The media source, motion device, and display are all in communication with the controller. The software program runs on the controller and generates an interface comprising a play list and a play button. The play list contains a list of script items, where each script item contains motion data for operating the motion device to perform a desired movement sequence. The play button causes the software program to transfer a selected script item from the play list to the motion device to cause the motion device to perform the desired movement sequence.

Description

FIELD OF THE INVENTION

[0002] The present invention relates to motion control systems and methods and, more specifically, to systems and methods for selecting and controlling motion data that is then transmitted to a motion control device to cause the motion control device to move in a desired manner.

BACKGROUND OF THE INVENTION

[0003] The purpose of a motion control device is to move an object in a desired manner. The basic components of a motion control device are a controller and a mechanical system. The mechanical system translates signals generated by the controller into movement of an object.

[0004] While the mechanical system commonly comprises a drive and an electrical motor, a number of other systems, such as hydraulic or vibrational systems, can be used to cause movement of an object based on a control signal. Additionally, it is possible for a motion control device to comprise a plurality of drives and motors to allow multi-axis control of the movement of the object.

[0005] The present invention is of particular importance in the context of a mechanical system such as a toy including at least one drive and electrical motor having a rotating shaft that, when rotated, causes movement of the toy, and that application will be described in detail herein. But the principles of the present invention are generally applicable to any mechanical system that generates movement based on a control signal. The scope of the present invention should thus be determined based on the claims appended hereto and not the following detailed description.

[0006] In a mechanical system comprising a controller, a drive, and an electrical motor, the motor is physically connected to the object to be moved such that rotation of the motor shaft is translated into movement of the object. The drive is an electronic power amplifier adapted to provide power to a motor to rotate the motor shaft in a controlled manner. Based on control commands, the controller controls the drive in a predictable manner such that the object is moved in the desired manner.

[0007] These basic components are normally placed into a larger system to accomplish a specific task. For example, one controller may operate in conjunction with several drives and motors in a multi-axis system for moving a tool along a predetermined path relative to a workpiece. In industry, the basic components described above are often used in conjunction with a host computer or programmable logic controller (PLC). The host computer or PLC allows the use of a high-level programming language to generate control commands that are passed to the controller. Software tools running on the host computer are designed to simplify the task of programming the controller, but the use of such software tools is beyond the ability of average consumers without a background in computer programming.

[0008] Another example of a larger system incorporating motion components is a doll having sensors and motors configured to cause the doll to mimic human behaviors such as dancing, blinking, clapping, and the like. Such dolls are pre-programmed at the factory to move in response to stimulus such as sound, internal timers, heat, light, and touch. Programming such dolls requires knowledge of hardware dependent low-level programming languages and is also beyond the abilities of an average consumer.

PRIOR ART

[0009] The Applicant is aware of programmable toys such as the Mindstorms® robotics system produced by The LEGO Group. Such systems simplify the process of programming motion systems such that children can design and build simple robots, but provide the user with only rudimentary control over the selection and control of motion data for operating the robot.

SUMMARY OF THE INVENTION

[0010] The present invention is a motion system comprising a controller, a media source, a motion device, a display, and a software program. The media source, motion device, and display are all in communication with the controller. The software program runs on the controller and generates an interface comprising a play list and a play button. The play list contains a list of script items, where each script item contains motion data for operating the motion device to perform a desired movement sequence. The play button causes the software program to transfer a selected script item from the play list to the motion device to cause the motion device to perform the desired movement sequence.

DESCRIPTION OF THE DRAWING

[0011] FIG. 1 is a block diagram of a motion system incorporating a control system constructed in accordance with, and embodying, the principles of the present invention;

[0012] FIG. 2 depicts a first embodiment of a user interface that may be used by the control system depicted in FIG. 1;

[0013] FIG. 3 depicts a second embodiment of a user interface that may be used by the control system depicted in FIG. 1;

[0014] FIG. 4 depicts a third embodiment of a user interface that may be used by the control system depicted in FIG. 1;

[0015] FIG. 5 depicts a fourth embodiment of a user interface that may be used by the control system depicted in FIG. 1;

[0016] FIG. 6 depicts a fifth embodiment of a user interface that may be used by the control system depicted in FIG. 1;

[0017] FIG. 7 depicts a first embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0018] FIG. 8 depicts a second embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0019] FIG. 9 depicts a third embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0020] FIG. 10 depicts a fourth embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0021] FIG. 11 depicts a fifth embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0022] FIG. 12 depicts a sixth embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0023] FIG. 13 depicts a seventh embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0024] FIG. 14 depicts an eighth embodiment of an interface layout that may be used by the control system depicted in FIG. 1;

[0025] FIG. 15 depicts a ninth embodiment of an interface layout that may be used by the control system depicted in FIG. 1; and

[0026] FIG. 16 depicts a tenth embodiment of an interface layout that may be used by the control system depicted in FIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Referring initially to FIG. 1, depicted therein is a motion system 20 implementing the principles of the present invention. The motion system 20 comprises a control system 22, a motion device 24, and a media source 26 of motion data for operating the motion device 24. The control system 22 comprises a controller 30 and a display 32.

[0028] The controller 30 receives motion data from the media source 26 and transfers this motion data to the motion device 24. The controller 30 further generates a user interface on the display 32 for allowing the user to select motion data and control the transfer of motion data to the motion device 24.

[0029] The controller 30 is any general purpose or dedicated controller capable of running a software program that performs the functions recited below. Typically, the controller 30 will be a general purpose computing platform, hand-held device, cell-phone, or the like separate from the motion device 24 or a microcontroller integrated within the motion device 24.

[0030] The display 32 may be housed separately from the controller 30 or may be integrated with the controller 30. As such, the display 32 may also be housed within the motion device 24 or separate therefrom.

[0031] The controller 30, motion device 24, and media source 26 are all connected such that motion data can be transmitted therebetween. The connection between these components 30, 24, and 26 can be permanent, such as when these components are all contained within one housing, or these components 30, 24, and 26 can be disconnected in many implementations. The controller 30 and display 32 can also be disconnected from each other in some implementations, but will often be permanently connected.

[0032] One common implementation of the present invention would be to connect the control system 22 to the media source 26 over a network such as the internet. In this case, the controller 30 will typically run a browser that allows motion data to be downloaded from a motion data server functioning as the media source 26. The controller 30 will typically be a personal computer or hand-held computing device such as a Game Boy or Palm Pilot that is connected to the motion device 24 using a link cable or the like. The motion device 24 will typically be a toy such as a doll or robot but can be any programmable motion device that operates under control of motion data.

[0033] The media source 26 will typically contain a library of scripts that organize the motion data into desired motion sequences. The scripts are identified by names that uniquely identify the scripts; the names will often be associated with the desired motion sequence. The operator of the control system 22 select and download a desired motion sequence or number of desired motion sequences by selecting the name or names of these motion sequences. The motion system 20 may incorporate a system for generating and distributing motion commands over a distributed network such as is described in copending U.S. Patent Application Serial No. XX/XXX,XXX (Serial No. not yet assigned; Attorney Matter No. P213577) filed on Feb. 21, 2001, and commonly assigned with the present application; the contents of the application filed on Feb. 21, 2001, are incorporated herein by reference.

[0034] The motion data contained in the scripts may comprise one or more control commands that are specific to a given type or brand of motion device. Alternatively, the motion data may be hardware independent instructions that are converted at the controller 30 into control commands specific the particular motion device or devices to which the controller 30 is connected. The system 20 may incorporate a control command generating system such as that described in U.S. Pat. No. 5,691,897 owned by the Assignee of the present invention into one or both of the media source 26 and/or controller 30 to allow the use of hardware independent application programs that define the motion sequences. The contents of the '897 patent are incorporated herein by reference.

[0035] At least one motion script is stored locally at the controller 30, and typically a number of scripts are stored locally at the controller 30. The characteristics of the particular controller 30 will determine the number of scripts that may be stored locally.

[0036] As generally discussed above, the logic employed by the present invention will typically be embodied as a software program running on the controller 30. The software program generates a user interface that allows the user to select a script to operate on the motion device 24 and to control how the script runs on the motion device 24.

[0037] A number of exemplary user interfaces generated by the controller 30 will now be discussed with reference to FIGS. 2-5.

[0038] A first exemplary user interface depicted at 50 in FIG. 2 comprises a play list 52 listing a plurality of play script items 54a-c from which the user can select. The exemplary interface 50 further comprises a play button 56, a stop button 58, and, optionally, a current play indicator 60. In this first exemplary interface 50, the play list 52 is loaded by opening a file, or downloading the play-list from a network (or Internet) site. Once loaded, selecting the Play button 56 runs all items 54 in the play list 52. Selecting the Stop button 58 causes the play session to stop (thus stopping all motion and/or motion programs from running) and returns the current play position to the beginning of the list 52.

[0039] The play list 52 is typically implemented using a software element such as a List box, List view, List control, Tree view, or custom list type. The play list 52 may appear on a main window or in a dialog that is displayed after the user selects a button or menu item. The Play List 52 contains and identifies, in the form of a list of the play script items 54, all motion content that will actually play on the target motion device 54.

[0040] The play button 56 is typically implemented using a software element such as a Menu item, button, graphic with hot spot, or other hyper-link type jump. The Play button 56 is selected using voice, touch, keyboard, or other input device. Selecting the Play button 56 causes the controller 30 to cause the motion device 24 to begin running the script or scripts listed as play script items 54 in the Play List 52. Because the script(s) contains or package motion data or instructions, running the script(s) causes the target motion device 24 to move in the motion sequence associated with the script item(s) 54 in the play list 52. In the exemplary interface 50, the script item 54a at the start of the Play List is first run, after which any other play script items 54 in the play list are run in sequence.

[0041] The current play indicator 60 is a visible, audible, tactile, or other indication identifying which of the play script items 54 in the play list 52 is currently running; in the exemplary interface 50, the current play indicator 60 is implemented by highlighting the background of the script item 54 currently being played.

[0042] The stop button 58 is also typically implemented using a software element such as a Menu item, button, graphic with hot spot, or other hyper-link type jump and may be selected in the same manner as the play button 56. Selecting the Stop button 58 causes the controller 30 to stop running the script item 54 currently playing, thereby stopping all motion on the target device 24. The position of the current play indicator 60 position is typically moved to the first script item 44 in the Play List 52 after the stop button 58 is selected.

[0043] Referring now to FIG. 3, depicted therein is yet another user interface 50a that may be generated by the software running on the controller 30. Like the user interface 50 described above, the user interface 50a comprises a play list 52 listing a plurality of play script items 54a-c, a play button 56, a stop button 58, and, optionally, a current play indicator 60. These interface components 52, 54, 56, 58, and 60 were discussed above with reference to the user interface 50 and will be described again below only to the extent necessary for a complete understanding of the interface 50a.

[0044] The interface 50a is more full-featured than the interface 50 and uses both the Selection List 62 and the Play List 52. Using the Add, Add All, Remove and Remove All buttons the user can easily move items from the Selection List over to the Play List or remove items from the Play List to create the selections of content items that are to be run. Using the content play controls, the user is able to control how the content is run by the player. Selecting Play causes the content to start playing (i.e. the end device begins moving as specified by the instructions (or data) making up the content. Selecting Stop halts any content that is currently running. And FRev, Rev, Fwd, FFwd are used to change the position where content is played.

[0045] The user interface 50a further comprises a selection list 62 that contains a plurality of selection script items 64a-f. The selection script items 64 are a superset of script items from which the play script items 54 may be selected.

[0046] Play script items 54 are added to and removed from the play list 52 using one of a plurality of content edit controls 65 comprising an add button 66, a remove button 68, an add all button 70, and/or a remove all button 72. These buttons 66-72 are typically implemented using a software element such as a Menu item, button, graphic with hot spot, or other hyper-link type jump and selected using a voice, touch, keyboard, or other input device.

[0047] Selecting the Add button 66 causes a selected selection item 64 in the Selection List 62 to be copied into the Play List 52. The selected item 64 in the selection list 62 may be chosen using voice, touch, keyboard, or other input device and is typically identified by a selection indicator 74 that is or may be similar to the play indicator 60. One or more selection items 64 may be selected and the selection indicator 74 will indicate if a plurality of items 64 have been chosen.

[0048] Selecting the Remove button 68 causes the selected item in the Play List 52 to be removed from the Play List 52. Selecting the Add All button 70 causes all items in the Selection List 62 to be copied into the Play List 52. Selecting the Remove All button 72 causes all items in the Play List 52 to be removed.

[0049] The interface 50b further comprises a plurality of content play controls 75 comprising a Frev button 76, a Rev button 78, a Fwd button 80, and a FFwd button 82. These buttons 76-82 are also typically implemented using a software element such as a Menu item, button, graphic with hot spot, or other hyper-link type jump and selected using a voice, touch, keyboard, or other input device. The content play controls 75 control the transfer of motion data from the controller 30 to the target motion device 24 and thus allows the user more complete control of the desired movement of the motion device 24.

[0050] Selecting the FRev button 76 moves the current play position in the reverse direction at a fast pace through the content embodied in the play script item 54 identified by the current play indicator 60. When the end of the identified script item 54 is reached, further selection of the FRev 76 button will cause the current play indicator 60 to move to the next script item 54 in the play list 52. Depending upon the capabilities of the motion device 24, the motion device 24 may move at a higher rate of speed when the FRev button 76 is selected or may simply skip or pass over a portion of the motion data contained in the play script item 54 currently being played.

[0051] Selecting the Rev button 78 moves the current play position in the reverse direction at a slow pace or in a single step where each instruction (or data element) in the play script item 54 currently being played is stepped in the reverse direction. Selecting the Fwd button 80 moves the current play position in the forward direction at a slow pace or in a single step where each instruction (or data element) in the play script item 54 currently being played is stepped in the reverse direction. Selecting the FFwd button 82 causes an action similar to the selection of the FRev button 76 but in the forward direction.

[0052] Referring now to FIG. 4, depicted therein is yet another user interface 50b that may be generated by the software running on the controller 30. Like the user interfaces 50 and 50a described above, the user interface 50b comprises a play list 52 listing a plurality of play script items 54a-c, a play button 56, a stop button 58, and, optionally, a current play indicator 60. Like the interface 50a described above, the interface 50b comprises content edit controls 65 comprising buttons 66-72 and content play controls 75 comprising buttons 76-82. These interface components 52-82 were discussed above with reference to the user interfaces 50 and 50a and will be described again below only to the extent necessary for a complete understanding of the interface 50b.

[0053] Like the interface 50a, the interface 50b uses both the Selection and Player Lists. In addition, the Add, Add All, Remove and Remove All controls are used as well. Two new controls, used for editing the play list, are added to this layout: the Move Up and Move Down controls. The Move Up control moves the currently selected item in the play list to the previous position in the list, whereas the Move Down control moves the currently selected item to the next position in the play list. These controls allow the user to more precisely set-up their play lists before running them on the target device. In addition to the Play, Stop, FRev, Rev, Fwd and FFwd controls used to play the content, six new controls have been added to this layout. The Rec, Pause, To Start, To End, Rand. And Cont. buttons are new to this layout. Selecting the Rec button causes the player to direct the target to start recording each move and/or other move related data (such as axis position, velocity, acceleration, etc.) Selecting the Pause button causes any currently running content to stop running yet remember the current play position. Selecting Play after selecting Pause causes the player to start playing at the play position where it was last stopped. To Start and To End move the current play position to either the start or end of all items in the content list respectively. Selecting Rand directs the player to randomly select items from the Play List to run on the target device. Selecting Cont causes the player to continuously run through the Play List. Once the last item in the list completes, the first item starts running and this process repeats until continuous mode is turned off. If both Cont and Rand are selected the player continuously selects at random each item from the play lists and plays each. When running with Rand selected and Cont not selected, each item is randomly selected from the Play List and played until all items in the list have played.

[0054] The content edit controls 65 of the exemplary interface 50b further comprise a Move Up button 84 and a Move Down button 86 that may be implemented and selected in a manner similar to any of the other buttons comprising the interface 50b. Selecting the Move Up button 84 causes the current item 54 selected in the Play List 52 to move up one position in the list 52. Selecting the Move Down button 86 causes the current item 54 selected in the Play List 52 to move down one position in the list 52.

[0055] The content play controls 75 of the exemplary interface 50b further comprise a Rec button 88, a Pause button 90, a To Start button 92, a To End button 94, a Rand. button 96, and a Cont. button 98. Selecting the Rec button 88 causes the controller 30 to begin recording content from the target device 24 by recording motion instructions and/or data into a script that can then be replayed at a later time.

[0056] Selecting the Pause button causes the controller 30 to stop running content and store the current position in the script (or stream). Subsequent selection of the Play button 56 will continue running the content at the stored position in the script.

[0057] Selecting the To Start button 92 moves the current play position to the start of the first item 54 in the Play List 52. Selecting the To End button 94 moves the current play position to the end of the last item 54 in the Play List 52.

[0058] Selecting the Rand. button 96 causes the controller 30 to enter a random selection mode. When running in the random selection mode, play script items 54 are selected at random from the Play List 52 and played until all of the items 54 have been played.

[0059] Selecting the Cont. button 98 causes the controller 30 to enter a continuous run mode. When running in continuous run mode and the last item 54 in the Play List 52 is played, the current play position is reset to the beginning of the Play List 52 and all content in the list 52 is run again. This process repeats until continuous mode is turned off. If random mode is enabled when the Cont. button 98 is selected, play script items 54 are continuously selected at random and run until continuous mode is turned off.

[0060] Referring now to FIG. 5, depicted therein is yet another exemplary interface 50c that is similar to the interface 50b described above but the control buttons have been rearranged in a different configuration that may be preferable under some circumstances.

[0061] Referring now to FIG. 6, depicted therein is yet another exemplary interface 50d that is similar to the interface 50b described above but further comprises several new controls 100, 102, and 104 at the bottom thereof. These controls 100, 102, and 104 comprise sliders 106, 108, and 110 that are used to change attributes associated with the content that is run from the Play List 52. Velocity controls are provided to alter the velocity of a specific axis of motion or even all axes at the same time.

[0062] Instead of using single controls for each axis, a single master velocity control may also be used to control the velocity on all axes at the same thus speeding up or slowing down the current item being played from the play list. Another way of achieving the same ends is with the use of a velocity lock control 112. When selected all velocity controls move in sync with one another regardless of which one the user moves.

[0063] Below the velocity controls are the status controls 114, 116, and 118 that display useful information for each axis of motion. For example, status controls may be used to graphically depicte the current velocity, acceleration, deceleration, position, or any other motion related property occurring on each axis.

[0064] Referring now to FIGS. 7-16, somewhat schematically depicted therein are interface layouts 120, 122, 124, 126, 128, 130, 132, 134, 136, and 138. Each of these layouts 120-138 comprises a selection list 62, a play list 52, play list edit controls 65, and content play controls 75 as described above. The exact content and format of these lists 62 and 52 and controls 65 and 75 may vary from implementation to implementation.

[0065] The layout 120 of FIG. 7 corresponds to the layouts of the interface 50a described above.

[0066] The layout 122 of FIG. 8 arranges the Play List Controls 65 on top.

[0067] The layout 124 of FIG. 9 arranges the play list controls 65 to the right and the content play controls on top.

[0068] The layout 126 of FIG. 10 arranges the Play Controls 75 on Top and the Edit Controls to the left.

[0069] The layout 128 of FIG. 11 arranges the Play Controls 75 on Top and the Edit Controls 65 to the Left, with the positions of the Play List 52 and Selection Lists 62 reversed.

[0070] The layout 130 of FIG. 12 arranges the play controls 75 on top, the play list 52 at left, and the selection list 62 at right.

[0071] The layout 132 of FIG. 13 arranges the Play Controls 75 on the bottom, the Play List 52 on the left, and the Selection List 62 on the right.

[0072] The layout 134 of FIG. 14 arranges the Play Controls 75 on the bottom, the Edit Controls 65 on Left, the Play List 52 next, and the Selection List 62 on the right.

[0073] The layout 136 of FIG. 15 arranges the Play Controls 75 on the bottom, the Edit Controls 65 on the left, the Selection List 62 next, and the Play List 52 on the right.

[0074] The layout 138 of FIG. 16 arranges the Play Controls 75 on the bottom, the Selection List 62 on the left, then the Play List 52, and the Edit Controls 65 on the right.

[0075] These examples have been provided to show that as long as the controls provided all support a common functionality their general layout does not change the overall player's functionality other than making the application more or less intuitive (and or easier) to use. Certain of these layouts may be preferred, however, depending on a particular set of circumstances.

Claims

1. A motion system comprising: a controller; a media source in communication with the controller; a motion device in communication with the controller; a display in communication with the controller; and a software program running on the controller for generating an interface comprising a play list containing a list of script items, where each script item contains motion data for operating the motion device to perform a desired movement sequence, and a play button for causing the software program to transfer a selected script item from the play list to the motion device to cause the motion device to perform the desired movement sequence.