US 7,031,798 B2Grant
Event management systems and methods for the distribution of motion control commands
Issue Date:2006-04-18
•16 Claims
•7 Drawing Sheets
Abstract
A motion control system for controlling a target device to perform a desired motion operation. The motion control system comprises at least one motion event provider, a motion event manager, and a motion control component. The motion event provider is configured to generate at least one event token upon the occurrence of at least one predetermined event. The event token is associated with at least one motion command. The motion event manager receives the at least one event token. The motion control component is adapted to transmit to the target device a control command based on the at least one motion command associated with the event token received by the motion event manager.
Metadata
Assignee
- Roy-G-Biv Corporation
Inventors
- David W. Brown
- Skylar Stein
Application Information
Application Number:US 10/074,577
Filing Date:2002-02-11
Priority Date:2001-02-09
Art Unit:2125
Classifications
IPC:
G06F19/00
Patent Drawings (7 sheets)
Description
Related Applications
[0001] This application claims priority of U.S. Provisional Application Ser. No. 60/267,645 filed Feb. 9, 2001.
Technical Field
[0002] The present invention relates to motion control systems and, more specifically, to an event management system optimized for the processing and distribution of motion control commands for a motion control device.
Background of the Invention
[0003] Electromechanical systems are used in numerous environments to translate electrical signals in mechanical movement. As examples, factory automation systems, toys, appliances, and the like all may use one or more electromechanical transducers that move in response to electrical control signals.
[0004] Typically, an application programmer familiar with a specific environment creates an application program defining a desired sequence of movements. U.S. Pat. Nos. 5,691,897, 5,867,385, and 6,209,037 to Brown et al. disclose systems and methods for generating, processing, and/or distributing control commands to one or more motion control devices based on such an application program.
[0005] The present invention may be embodied as a part of an overall motion control system as described in the Brown et al. patents and will be described herein in that context. However, as described below, the principles of the present invention may have broader application to other motion control systems and methods, and the scope of the present invention should be determined by the claims appended hereto and not the following detailed description.
Summary of the Invention
[0006] A motion control system for controlling a target device to perform a desired motion operation. The motion control system comprises at least one motion event provider, a motion event manager, and a motion control component. The motion event provider is configured to generate at least one event token upon the occurrence of at least one predetermined event The event token is associated with at least one motion command. The motion event manager receives the at least one event token. The motion event manager uses the motion control component to transmit to the target device a control command based on the at least one motion command associated with the event token received by the motion event manager.
Description of the Drawing
[0007] FIG. 1 is a module interaction map depicting a motion control system incorporating an event management system of the present invention;
[0008] FIG. 2 is a scenario map depicting the startup and initialization of the system of FIG. 1 ;
[0009] FIG. 3 is a scenario map depicting the process of injecting a motion event provider DLL into the address space of a target application;
[0010] FIG. 4 is a scenario map depicting the process of configuring motion events provided by each of one or more motion event providers 132;
[0011] FIG. 5 is a scenario map depicting the process of handling a motion event;
[0012] FIG. 6 is a scenario map depicting how a user may obtain new motion media and motion event providers 132 from the motion web site 136;
[0013] FIG. 7 is a scenario map depicting shut down of the system of FIG. 1 ; and
[0014] FIG. 8 is a scenario map depicting the mapping of text to motion events.
Detailed Description of the Invention
[0015] Referring initially to FIG. 1 , depicted therein is a motion control system 120 constructed in accordance with, and embodying, the principles of the present invention. The motion control system 120 is an event-based system used to control, configure, and query one or more motion based devices or machines such as indicated by reference character 122 in the drawing. The motion based devices or machines 122 will be referred to herein as the target device.
[0016] In the following discussion, the components or objects that form the motion control system 120 and the basic operation of the system 120 will first be described. After that will follow a discussion of the interaction between those objects and several detailed scenarios of typical actions of this system 120 .
[0017] Referring initially to FIG. 1 of the drawing, it can be seen that the motion control system 120 comprises the motion based machine or device 122, a motion event manager 130, one or more motion event provider objects 132, a motion event interface 134, a motion web site 136, and a media creation tool 138.
[0018] The system 120 is adapted to be run on a general purpose computer platform comprising computer hardware and an operating system 140. The exemplary operating system 140 is a Windows variant and comprises a registry 142.
[0019] The web site 136 and media creation tool 138 provide access to one or more motion media files 144. The motion media files 144 contain what will be referred to herein as motion media.
[0020] The term “motion media” includes motion scripts, motion application programs, and/or individual motion instructions capable of causing the target device 122 to perform a desired motion operation comprising a discrete movement or sequence of movements.
[0021] The motion media comprises what will be referred to as motion commands. The term “motion commands” will be used herein to refer to both control commands and media commands associated with a desired motion operation. The term “control commands” as used herein refers to device-specific commands that may be directly run by a target device to obtain a desired motion operation. The term “media commands” used herein refers to machine independent instructions that generically define a desired motion operation. Normally, media commands are converted into control commands before the target device executes the desired motion operation corresponding to a particular media command or set of media commands. The term “application program” will be used to refer to a set of control and/or media commands associated with a sequence of discrete movements.
[0022] The motion event manager 130 comprises a motion control component 150 and an event handling component 152. The motion event interface 134 further comprises a event provider configuration control 154 and a media view control 156.
[0023] The motion control system 120 operates basically as follows. The motion event providers 132 generate what will be referred to as event tokens based on the occurrence of a predetermined event. The event token is associated with the predetermined event in advance and thus identifies the predetermined event. The event token may also contain additional information such as the source of the predetermined event, parameters associated with the predetermined event, and the like.
[0024] The event tokens are sent to the motion event manager 130. The motion event providers 132 and motion event manager 130 run in separate processes and could perhaps run on separate physical machines connected over a network. The motion event providers 132 and motion event manager 130 thus use the system for the inter-process communication provided by the operating system to transmit the event tokens from the event providers 132 to the motion event manager 130.
[0025] The motion event manager 130 notifies the motion control component 150 when the event token is received and the identity of the event token. The action taken by the motion control component 150 upon receipt of an event token depends upon the nature of the event token. The received event token may contain or identify a particular control command, and the motion control component 150 can simply pass that control command to the target device 122. The received event token may contain or identify a particular media command, in which case the motion control component 150 may be required to convert the media command into a control command capable of being run by the target device 122. Another event token may start, stop, or otherwise control a separate application program run by the motion control component 150.
[0026] In the exemplary system 120, the association of motion media with event tokens is preferably made by the motion event manager 130. This association is typically represented by a table, spreadsheet, or other data storage means capable of defining relationships between event tokens and motion media. Upon receipt of each event token, the motion event manager 130 will identify the motion media previously associated with the received token and send the identified motion media to the motion control component 150 for control of the target device 122.
[0027] With the foregoing understanding of the basic operation of the system 120, the details of this exemplary motion control system 120 will now be described.
[0028] The motion event manager 130 handles the creation of each event provider 132 installed on the system by creating in-proc providers or injecting other providers into their target processes. The event manager 130 also catches events fired from each provider 132 and initiates the appropriate motion request for each event. In the exemplary system 120, the event manager 130 is the only object that communicates directly with the motion control component 150, as will be described in further detail below. The exemplary event manager 130 is accessible by double clicking its icon in the Windows System Tray in a conventional manner.
[0029] The purpose of the event handling component 152 is to handle the inter-process communications between the motion event manager 130 and the motion event providers 132. The exemplary event handling component 152 is or may be a conventional software object referred to as a message pump.
[0030] The motion event provider objects 132 are individually designed to monitor user configurable events from a given source. The exemplary system 120 employs two types of motion event providers 132: simple in-proc servers 132a,b hosted by the motion event manager 130 and specialty DLLs 132c,d that are injected into a target process to monitor event cases. Each motion event provider object 132 also contains an event configuration control 154 that, as will be described below, allows a user to configure all events supported by the motion event provider objects 132. The motion event provider objects 132 notify the motion event manager 130 of each event caught by the objects 132.
[0031] The motion event manager 130 and motion control component 150 operate together to allow interaction between the motion event providers 132 and the target device 122.
[0032] The motion control component 150 may be or incorporate parts of a software system as disclosed, for example, in U.S. Pat. Nos. 5,691,897 and 5,867,385. The systems disclosed in the '897 and '385 patents are capable of generating device-specific control commands based on hardware independent media commands written to a predetermined application programming interface.
[0033] As an alternative, the motion control component 150 may act as a conduit that passes device-specific control commands and query responses between the motion event providers 132 and the target device 122. A motion control component implemented in this manner would not convert between hardware independent media commands and device specific control commands.
[0034] A preferred implementation of the motion control component 152 would be to be for the component 152 to function in both a translation mode and in a pass-through mode. In the translation mode, the component 152 converts media commands into control commands. In the pass-through mode, the component 152 simply passes control commands from the motion event providers 132 to the target devices 122. In either mode, query responses are returned from the target devices 122 to the event provider 132 in an appropriate format.
[0035] The motion event configuration interface 134 is preferably a visual interface displayed on a screen to allow a user to configure all motion event providers 132 installed on the system 120. The exemplary interface 134 also provides access to the motion web site 136 where new motion media and motion event providers 132 may be downloaded and installed.
[0036] As will be described in more detail below, the configuration options allowed by the interface 134 include the ability to enable/disable event providers 132 and map motion media to particular events supported by each provider 132. The interface 134 also provides access to the motion web site 136, allowing for new motion media and motion event providers 132 to be downloaded and installed onto the current system.
[0037] Each motion event provider 132 contains a visual configuration control 158 that allows the user to configure the events supported by each provider 132. The exemplary configuration controls 158 use the media view control object 156 to gain access to the available motion media in the motion media file 144 that can be mapped to each available event.
[0038] These controls may also be configured to allow the user to add new, customized events to the motion event providers 132. The dynamic events can be defined using parameters such as text (usernames, messages, email, etc.), date/time, or any other parameter particular to an event providers event source.
[0039] The media view control object 156 provides access to all installed motion media scripts as represented by the motion media file 144. Preferably, the media view control object 156 displays a conventional browse/select dialog to allow identification and selection of the available motion media. This object 156 is used by the event provider configuration controls 158 and allows the configuration controls 158 to remain independent of the motion media format.
[0040] The media creation tool application 138 allows the user to customize and/or create motion media. This application 138 preferably implements a graphical, easier to use, front-end user interface design.
[0041] The motion web site 136 provides a location for the user to download new motion media as well as new and/or updated motion event providers 132. The motion media is preferably stored in a single meta file. New motion media downloaded from the motion web site 136 will be added to this meta file.
[0042] The present invention is preferably embodied using the Windows registry; typically, a component category is created for each of the motion event providers 132, allowing the motion event manager 130 to enumerate all providers 132 installed on the system. Primary event sources 132 are user actions (in any active application supported via a motion event provider) and operating system tasks.
[0043] With the foregoing understanding of the modules that form the exemplary system 120, various scenarios in which these modules typically interact will now be described.
[0044] Referring now to FIG. 2 , depicted therein is the scenario describing the startup process of the motion event manager 130 of the system 120. Each of the steps of this startup process will now be described with reference to FIG. 2 .
[0045] The motion event manager 130 process 130 begins on system startup. The motion event manager 130 process 130 next queries the MOTION_EVENT_PROVIDER component category in the Windows Registry to enumerate all motion event providers 132 installed on the system.
[0046] Third, the registry entry of each of the event providers 132 contains startup information indicating if the particular event provider is either a standard in-proc provider or a specialty provider that is injected into a target process to monitor event conditions.
[0047] Fourth, the motion event manger 130 creates a new instance of each provider 132. If the event provider 132 is a specialty provider that is injected into a target application process, the event manger 130 will read the target-process information from the provider's registry entry, find the target process, and perform the DLL-injection. If the target process is not active, the motion event manager 130 will continually monitor the creation of new applications, and perform the injection when/if the requested application is launched.
[0048] Fifth, once the event providers 132 are created, the motion event manager 130 will send the appropriate initialization information to each provider 132, including callback information to allow the event providers 132 to post event messages back to the event manager 130.
[0049] Finally, the event provider 132 reads initialize message data and establish the necessary event syncs to monitor the events. The initialize message data includes a registry key identifying the location of the event configurations and preferences as last set by the motion event configuration interface 134 or the default installed set.
[0050] Referring now to FIG. 3 , depicted therein is the DLL injection scenario map. This scenario describes the process of injecting a motion event provider DLL into the address space of a target application.
[0051] As shown in FIG. 3 , the first step of this process is for the motion event manager 130 to determine which process into which the motion event provider 132 must be injected based on the registry entry of the provider 132.
[0052] Once the target process has been identified, the next step is for the event manager 130 to install a Windows message hook in the target process. This causes the event provider DLL to be loaded into the target address space of the target process. The event provider DLL has now been loaded into the required process, and will now wait for the “initialize” message from the motion event provider 132.
[0053] Referring now to FIG. 4 , depicted therein is the motion event configuration scenario map. This scenario map describes the process of configuring motion events of each of the motion event providers 132.
[0054] First, the user launches the motion event configuration interface 134 from system tray interface of the motion event manager 130.
[0055] Each event provider object 132 supports a custom visual control 154 that can be used to edit the object's supported events. The event configuration interface 134 creates and hosts these visual controls 154 for the user.
[0056] Next, when the event provider configuration control 154 is created and initialized, it will receive the location in the Windows Registry 142 of its persisted event data, which will be loaded into the control 154.
[0057] Next, the user will select an event provider 132 to configure. Individual events may be mapped to motion actions, and particular events (as well as the entire event provider itself) may be deactivated if desired. As noted above, these event configuration controls 154 may also provide the means to add additional, customized events based on input user parameters (custom text strings, buddy chat names, email messages, etc).
[0058] When the user selects an event to configure, the event provider configuration control 154 will defer to the media view control object 156. The media view control object 156 displays all available motion media via a dialog box, allowing the user to make a selection.
[0059] Finally, once the user makes a motion media selection, the media view control object 156 returns data back to the event provider configuration control object 154 (including human-readable description text of the event for display as well as a data token which can later be used to identify media selection). The configuration control object 154 then persists this information to the Windows Registry 142.
[0060] Referring now to FIG. 5 , depicted therein is a motion event scenario map. This scenario describes the process of handling a motion event.
[0061] The scenario depicted in FIG. 5 begins whenever an event occurs. The occurrence of an event may be caused from a user action, operating system event, or an event situation monitored in a third-party application.
[0062] The event provider 132 then fires a event token associated with this event to the event manager 130. The event token has previously been stored in the registry during the event configuration process. If the provider 132 requires queried data to be returned, the provider 132 will also pass the necessary callback data to the event manager 130.
[0063] The event manager 130 next receives the event and passes the requested media information to the motion control component 150. The motion control component 150 then executes the specified motion media on the target motion device 122.
[0064] Finally, if a query action was requested, the motion control component 150 will return the appropriate data. The motion event manger 130 will send the data through the specified event provider callback mechanism.
[0065] Depicted in FIG. 6 is a motion web site scenario map. The scenario of FIG. 6 describes how a user may obtain new motion media and motion event providers 132 from the motion web site 136.
[0066] This process may be started when users visit the motion web site 136 to browse currently available motion event providers 132 and new motion media. In FIG. 6 , the reference character 144a is used to represent a motion media file stored locally by the system 120, while the reference character 144 represents a motion media file stored at a remote location.
[0067] Next, the user selects the desired provider/media download option, and the new software is installed into the motion event manager 130 including the motion control component 150.
[0068] The next time the motion event configuration interface 134 is launched, the user will be able to configure the new event provider 132 or motion media in the local motion media file 144a.
[0069] Alternatively, users may download new event providers 132 and motion media directly from within the motion event Configuration dialog interface. This configuration dialog will provide the following options to the user: Download new Motion Media and/or Download/install new motion event providers 132. The user or the motion event manager 130 may also check for new versions of currently installed motion media and/or event providers 132.
[0070] Next, the user selects the desired provide/media download or update option, and the configuration dialog interface object 134 automatically downloads and installs the new software from the media web site 136.
[0071] Finally, once the new software is installed the configuration dialog 134 will automatically update to provide access to the new components and/or media.
[0072] Referring now to FIG. 7 , depicted therein is the system shutdown scenario map. This scenario describes the process of shutting down the exemplary event manager module 130 associated with the motion control component 150.
[0073] Upon operating system shutdown, the motion event manager 130 will prepare to terminate.
[0074] The event manager 130 next posts a shutdown message to each event provider 132 currently being managed by the manager 130. Specialty event providers 132 that have been injected into external processes may have already finished if the target process has been shutdown. In this case those event providers 132 would have already notified the event manager 130 that they are no longer available.
[0075] Each event provider 132 performs any required shutdown tasks.
[0076] Upon finishing any shutdown tasks, each provider 132 will notify the event manager 132 that the provider 132 is now finished.
[0077] Once the event manager 130 receives notifications that each of the event providers 132 managed thereby have been shutdown, the event manager 130 itself is now finished.
[0078] Referring now to FIG. 8 , depicted therein is a scenario map illustrating the mapping of text to motion events. This scenario generally describes the mapping of text based event situations to motion.
[0079] The first step of this process is for a text based event situation to occur. This text could be one or more of the following: (a) a particular sub-string in an Instant Message or the entire message string itself; (b) an Instant Message sent from a target screen or ‘buddy’ name; (c) a text string converted from a speech-to-text engine installed on the user's machine; and/or (d) an email message meeting previously configured criteria (Sent From, Subject, message content, etc). In the case of an event created using a peer-to-peer networked application such as Instant Messenger-type process, text is entered at a remote source application and sent as a text message to a receiving application.
[0080] The motion event provider 132 monitoring the specific text based event catches the event, and performs any pre-processing of the text required to identify the particular event. In the peer-to-peer application described above, a DLL functioning as the event provider 132 is injected into the receiving application; the DLL event provider 132 intercepts the message received by the receiving application and treats the received message as an event.
[0081] Once an event has been identified, the event provider 132 will lookup the corresponding motion event token as previously configured. As generally described above, the motion event tokens are pre-loaded upon initialization. In the peer-to-peer example described above, the DLL functioning as the event provider 132 sends the text message as part of the event token to the event manager 130 using a process-to-process communication system as generally described above.
[0082] After the event token containing the text message is sent to the motion event manager 130, the event manager 130 determines the type of event represented by the received token.
[0083] If the event manager 130 determines that the received event token corresponds to a text event, the event manager 130 next parses the text parameter from the event token. The motion event manager 130 looks up the motion media associated with the event type and event text parameter. The appropriate motion media is then sent to the motion control component 150 for execution on the target motion device 122 as described above with reference to FIG. 5 .
[0084] The process described above with reference to FIG. 8 can also occur in the reverse. In particular, the event manager 130 uses the motion control component 150 to continually query the target device 122 for state information. When the state information meets certain parameters, the control component 150 causes the event manager to ‘create’ a new event (such as a text event) and send it to an event provider 132.
[0085] The event provider 132 in turn then causes the receiving application to sent a message to a remote peer-to-peer application; again, the receiving and remote peer-to-peer applications may be Instant Messenger compatible applications.
[0086] An example of the use of the present system to verify motion status would be for the event manager 130 to continually or periodically query the target device 122 through the motion control component 150 for status parameters that indicate a fault condition. Once a fault condition occurs, the event manager 130 builds a text message that describes the fault and then sends the text message to a remote application, such as an Instant Messenger user, using process-to-process communication system and the peer-to-peer networked application.
[0087] The following Table A describes the interface specifications for components of the exemplary motion control system 120 described above using the exemplary motion control component 150.
[0088]
| TABLE A | ||
|---|---|---|
| compon- | ||
| ent | interface | method(s)/description |
| motion | IXMCEventProviderMgt | EnumerateProviders used by |
| event | configuration dialog object to get | |
| manager | a list of all installed motion event | |
| 30 | providers 132 | |
| EnableProvider( ) used to | ||
| enable/disable given event | ||
| providers. will be called from the | ||
| configuration dialog object | ||
| IXMCEventScheme | GetSchemes( ) used by | |
| configuration dialog object to get | ||
| current list of schemes on the | ||
| system | ||
| AddScheme( ) - used by | ||
| configuration dialog object to add | ||
| a new scheme | ||
| RemoveScheme( ) - used by | ||
| configuration dialog object to | ||
| remove a given scheme | ||
| RenameScheme( ) - used by | ||
| configuration dialog object to | ||
| rename a given scheme | ||
| Event | IXMCEventConfig | Initialize( ) - called by the |
| configura- | configuration dialog object which | |
| tion | hosts this control, used to pass | |
| controls | required init data, such as 1) | |
| 158 | current registry location where | |
| event configuration data may be | ||
| loaded/persisted, 2) interface to | ||
| the media view control 156, | ||
| etc . . . | ||
| Media | IXMCMediaViewCtrl | method: SelectMedia( ) - called |
| View | by each event configuration | |
| Control | control. This method will display | |
| 156 | a dialog to visualize all motion | |
| media available on the system | ||
| and return a tokenized data | ||
| param that can later identify the | ||
| media item selected | ||
[0089] In the following discussion, the details of a number of the exemplary components of the system 120 will now be described.
[0090] The Windows Registry 142 is used to persist event management with motion control configuration data.
[0091] Data associated with the motion event providers 132 is persisted to the Windows Registry 142 primarily to accommodate event provider DLLs that need to be injected into a target process, an environment where those DLLs may not be able to rely on standard COM storage alternatives.
[0092] At runtime, when the motion event manager 130 initializes an event provider, the provider will receive a location in the registry where it should read its previously configured event data.
[0093] At design time, when hosted within the motion event configuration interface 134, the event configuration controls 156 of the event providers 132 receive the registry location, and will persist configuration changes to that location.
[0094] Event providers will persist both standard (hard coded) and custom events to their registry storage location. Associated with each event will be the configured motion event token data, which the provider will use when firing event notifications back to the motion event manager 130.
[0095] The motion event manager 130 manages all registry locations for the event provider objects.
[0096] The event manager provides a mechanism to support different event schemes. This allows configurations unique for several different users, situations, or motion devices. When a new scheme is selected via the motion event configuration interface 134, the event manager 130 will pass the new scheme registry location to each event provider object 132, allowing access to the new scheme data. Each scheme will be located in a unique sub key under the primary event manager registry location.
[0097] The user interface components 154 and 156 of the system 120 may be implemented in many different forms. The motion event configuration control 154 is used to configure all motion event providers 132 installed on the system, as well as to provide access to the motion web site 136 where new motion media and motion providers may be downloaded and installed. The interface of the media creation tool 138 is a preferably graphical representation of the motion device or system, where simple drag-drop, click, and record operations will facilitate the creating and modification of motion media.
[0098] The system 120 is designed to be easily extendible via new motion event provider and motion media components. The system 120 is also capable of supporting any number of additional event sources with the addition of new motion event providers 132 by registering these new providers with the system 120. These event providers 132 can link to virtually any event source to a target system 122.
[0099] The motion media formats can be modified and extended without requiring changes to any event provider objects. For example, a XMCMediaCtrl object proxies the raw motion media format to the event providers. Accordingly, once the XMCMediaCtrl component is updated to handle any new media formats, the event providers 132 may, by design, make use of the changes.
[0100] Instead of triggering entire motion programs as described above with reference to FIG. 6 , a motion program or media set may be streamed to the device 122 through the system 120. Whether or not and how the media plays may be controlled by captured events. For example, a media player may fire events based on different musical notes or tones. When such events are received, one media stream may be selected over another, thus causing the motion device 122 to perform different actions. This may also occur with the standard motion programs described above.
[0101] Very large motion programs may be downloaded in partial form and then either downloaded in full over time or as certain specified events occur in the system.
[0102] Similar to streaming media support, single motion operations may also be supported in which a specified event causes a single motion operation to take place immediately. One example of this would be an event that causes movement of one axis in the clockwise direction.
[0103] The present invention may be embodied in forms other than those described above. The scope of the present invention should thus be determined with reference to the following claims and not the foregoing exemplary detailed description.
Claims
We claim:
1. A motion control system for controlling a selected target device from a group of supported target devices to perform a desired motion operation from a set of supported motion operations that can be performed by the supported target devices, comprising:
a motion event configuration interface for associating source dependent events with source independent event tokens, where
each event token is associated with at least one hardware independent motion command, and
each hardware independent motion command is associated with at least one of the desired motion operations;
at least one motion event provider configured to generate at least one event token upon the occurrence of at least one event;
a motion event manager for receiving the at least one event token generated by the at least one motion event provider; and
a motion control component adapted to
generate device-specific control commands for the selected target device based on the at least one hardware independent motion command associated with the at least one event token received by the motion event manager, and
transmit the device-specific control commands to the selected target device to cause the selected target device to perform the desired motion operation.
2. A motion control system as recited in claim 1, in which the motion event configuration interface further comprises an event provider configuration control for identifying the at least one event associated with each event token.
3. A motion control system as recited in claim 1, in which the motion event configuration interface further comprises a media view control for associating event tokens with hardware independent motion commands.
4. A motion control system as recited in claim 1, in which:
the hardware independent motion command is a media command; and
the motion control component generates at least one device-specific control command based on the media command.
5. A motion control system as recited in claim 1, in which:
the hardware independent motion command associated with the event token corresponds to at least one of a media command and a device-specific control command; and
the motion control component further operates in a pass-through mode in which the motion control device transmits at least one device-specific control command defined by the event token to the selected target device.
6. A motion control system as recited in claim 1, in which the motion event configuration interface further comprises:
an event provider configuration control for identifying the at least one predetermined event associated with each event token; and
a media view control for associating event tokens with hardware independent motion commands.
7. A motion control system as recited in claim 1, in which:
the event token further comprises a text message; and
the motion event manager further parses the event token to extract the text message, where the text message identifies the hardware independent motion command associated with the event token.
8. A motion control system as recited in claim 1, in which the at least one event is the receipt of a message by a receiving application of a peer-to-peer communications system.
9. A motion control system as recited in claim 1, in which:
the motion control component determines a status of the selected target device; and
the motion event manager queries the motion control component to determine the status of the selected target device and sends to the at least one motion event provider a status message based on the status of the selected target device.
10. A motion control system as recited in claim 1, in which the motion event manager stores associations between at least some of the event tokens and at least some of the hardware independent motion commands and sends to the motion control component the hardware independent motion command associated with at least some of the event tokens received by the motion event manager.
11. A motion control system as recited in claim 1, further comprising a system registry, where associations of source dependent events and source independent event tokens are persisted in the system registry.
12. A motion control system as recited in claim 1, in which the event provider configuration control allows configuration of associations of source dependent events and source independent event tokens.
13. A motion control system as recited in claim 1, in which the event provider configuration control allows parameters associated with associations of source dependent events and source independent event tokens to be altered.
14. A motion control system as recited in claim 1, in which each source dependent event is associated with an event provider, and the event provider configuration control allows selection of at least one event provider.
15. A motion control system for controlling a selected target device from a group of supported target devices to perform a desired motion operation from a set of supported motion operations that can be performed by the supported target devices, comprising:
at least one event provider for generating at least one event associated with the desired motion operation;
a motion event configuration interface for associating events with event tokens where the motion event configuration interface allows selection of the at least one event provider;
at least one motion event provider configured to generate at least one event token upon the occurrence of at least one event; and
a motion event manager for receiving the at least one event token generated by the at least one motion event provider; and
a motion control component adapted to
generate device-specific control commands for the selected target device based on the at least one event token received by the motion event manager, and
transmit the device-specific control commands to the selected target device to cause the selected target device to perform the desired motion operation.
16. A motion control system for controlling a selected target device from a group of supported target devices to perform a desired motion operation from a set of supported motion operations that can be performed by the supported target devices, comprising:
at least one event provider, where each event provider generates at least one event and each event is associated with an event token;
a motion event configuration interface for selecting at least one event provider;
at least one motion event provider configured to generate at least one event token upon the occurrence of at least one event; and
a motion event manager for receiving the at least one event token generated by the at least one motion event provider; and
a motion control component adapted to
generate device-specific control commands for the selected target device based on the at least one event token received by the motion event manager, and
transmit the device-specific control commands to the selected target device to cause the selected target device to perform the desired motion operation.
Patent Citations (201)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4159417(A) | 1979-06-01 | Rubincam | Applicant |
| US4199814(A) | 1980-04-01 | Rapp et al. | Applicant |
| US4418381(A) | 1983-11-01 | Molusis et al. | Applicant |
| US4531182(A) | 1985-07-01 | Hyatt | Applicant |
| US4688195(A) | 1987-08-01 | Thompson et al. | Applicant |
| US4713808(A) | 1987-12-01 | Gaskill et al. | Applicant |
| US4767334(A) | 1988-08-01 | Thorne et al. | Applicant |
| US4769771(A) | 1988-09-01 | Lippmann et al. | Applicant |
| US4782444(A) | 1988-11-01 | Munshi et al. | Applicant |
| US4800521(A) | 1989-01-01 | Carter et al. | Examiner |
| US4809335(A) | 1989-02-01 | Rumsey | Applicant |
| US4815011(A) | 1989-03-01 | Mizuno et al. | Applicant |
| US4840602(A) | 1989-06-01 | Rose | Applicant |
| US4846693(A) | 1989-07-01 | Baer | Applicant |
| US4855725(A) | 1989-08-01 | Fernandez | Applicant |
| US4857030(A) | 1989-08-01 | Rose | Applicant |
| US4887966(A) | 1989-12-01 | Gellerman | Applicant |
| US4897835(A) | 1990-01-01 | Gaskill et al. | Applicant |
| US4912650(A) | 1990-03-01 | Tanaka et al. | Applicant |
| US4923428(A) | 1990-05-01 | Curran | Applicant |
| US4937737(A) | 1990-06-01 | Schwane et al. | Applicant |
| US4987537(A) | 1991-01-01 | Kawata | Applicant |
| US5005135(A) | 1991-04-01 | Morser et al. | Applicant |
| US5020021(A) | 1991-05-01 | Kaji et al. | Applicant |
| US5095445(A) | 1992-03-01 | Sekiguchi | Applicant |
| US5120065(A) | 1992-06-01 | Driscoll et al. | Applicant |
| US5126932(A) | 1992-06-01 | Wolfson et al. | Applicant |
| US5168441(A) | 1992-12-01 | Onarheim et al. | Applicant |
| US5175684(A) | 1992-12-01 | Chong | Applicant |
| US5175817(A) | 1992-12-01 | Adams et al. | Applicant |
| US5175856(A) | 1992-12-01 | Van Dyke et al. | Applicant |
| US5245703(A) | 1993-09-01 | Hubert | Applicant |
| US5247650(A) | 1993-09-01 | Judd et al. | Applicant |
| US5377258(A) | 1994-12-01 | Bro | Applicant |
| US5390304(A) | 1995-02-01 | Leach et al. | Applicant |
| US5390330(A) | 1995-02-01 | Talati | Applicant |
| US5392207(A) | 1995-02-01 | Wilson et al. | Applicant |
| US5402518(A) | 1995-03-01 | Lowery | Applicant |
| US5412757(A) | 1995-05-01 | Endo | Applicant |
| US5438529(A) | 1995-08-01 | Rosenberg et al. | Applicant |
| US5450079(A) | 1995-09-01 | Dunaway | Applicant |
| US5453933(A) | 1995-09-01 | Wright et al. | Applicant |
| US5465215(A) | 1995-11-01 | Strickland et al. | Applicant |
| US5491813(A) | 1996-02-01 | Bondy et al. | Applicant |
| US5493281(A) | 1996-02-01 | Owens | Applicant |
| US5511147(A) | 1996-04-01 | Abdel-Malek | Applicant |
| US5541838(A) | 1996-07-01 | Koyama et al. | Applicant |
| US5576727(A) | 1996-11-01 | Rosenberg et al. | Applicant |
| US5596994(A) | 1997-01-01 | Bro | Applicant |
| US5600373(A) | 1997-02-01 | Chui et al. | Applicant |
| US5604843(A) | 1997-02-01 | Shaw et al. | Applicant |
| US5607336(A) | 1997-03-01 | Lebensfeld et al. | Applicant |
| US5608894(A) | 1997-03-01 | Kawakami et al. | Applicant |
| US5617528(A) | 1997-04-01 | Stechmann et al. | Applicant |
| US5623582(A) | 1997-04-01 | Rosenberg | Applicant |
| US5625821(A) | 1997-04-01 | Record et al. | Examiner |
| US5636994(A) | 1997-06-01 | Tong | Applicant |
| US5652866(A) | 1997-07-01 | Aldred et al. | Applicant |
| US5655945(A) | 1997-08-01 | Jani | Applicant |
| US5666161(A) | 1997-09-01 | Kohiyama et al. | Applicant |
| US5670992(A) | 1997-09-01 | Yasuhara et al. | Applicant |
| US5691897(A) | 1997-11-01 | Brown et al. | Applicant |
| US5691898(A) | 1997-11-01 | Rosenberg et al. | Applicant |
| US5701140(A) | 1997-12-01 | Rosenberg et al. | Applicant |
| US5707289(A) | 1998-01-01 | Watanabe et al. | Applicant |
| US5724074(A) | 1998-03-01 | Chainani et al. | Applicant |
| US5733131(A) | 1998-03-01 | Park | Applicant |
| US5734373(A) | 1998-03-01 | Rosenberg et al. | Applicant |
| US5737523(A) | 1998-04-01 | Callaghan et al. | Applicant |
| US5739811(A) | 1998-04-01 | Rosenberg et al. | Applicant |
| US5746602(A) | 1998-05-01 | Kikinis | Applicant |
| US5752880(A) | 1998-05-01 | Gabai et al. | Applicant |
| US5754855(A) | 1998-05-01 | Miller et al. | Examiner |
| US5764155(A) | 1998-06-01 | Kertesz et al. | Applicant |
| US5790178(A) | 1998-08-01 | Shibata et al. | Applicant |
| US5800268(A) | 1998-09-01 | Molnick | Applicant |
| US5801946(A) | 1998-09-01 | Nissen et al. | Applicant |
| US5805785(A) | 1998-09-01 | Dias et al. | Examiner |
| US5818537(A) | 1998-10-01 | Enokida et al. | Applicant |
| US5821920(A) | 1998-10-01 | Rosenberg et al. | Applicant |
| US5821987(A) | 1998-10-01 | Larson | Applicant |
| US5822207(A) | 1998-10-01 | Hazama et al. | Applicant |
| US5825308(A) | 1998-10-01 | Rosenberg | Applicant |
| US5828575(A) | 1998-10-01 | Sakai | Applicant |
| US5846132(A) | 1998-12-01 | Junkin | Applicant |
| US5848415(A) | 1998-12-01 | Guck | Applicant |
| US5852441(A) | 1998-12-01 | Nakajima et al. | Applicant |
| US5855483(A) | 1999-01-01 | Collins et al. | Applicant |
| US5867385(A) | 1999-02-01 | Brown et al. | Applicant |
| US5873765(A) | 1999-02-01 | Rifkin et al. | Applicant |
| US5889670(A) | 1999-03-01 | Schuler et al. | Applicant |
| US5889672(A) | 1999-03-01 | Schuler et al. | Applicant |
| US5890963(A) | 1999-04-01 | Yen | Applicant |
| US5907704(A) | 1999-05-01 | Gudmundson et al. | Applicant |
| US5907831(A) | 1999-05-01 | Lotvin et al. | Applicant |
| US5914876(A) | 1999-06-01 | Hirai | Applicant |
| US5920476(A) | 1999-07-01 | Hennessey et al. | Applicant |
| US5924013(A) | 1999-07-01 | Guido et al. | Applicant |
| US5956484(A) | 1999-09-01 | Rosenberg et al. | Applicant |
| US5959613(A) | 1999-09-01 | Rosenberg et al. | Applicant |
| US5960085(A) | 1999-09-01 | De La Huerga | Applicant |
| US5977951(A) | 1999-11-01 | Danieli et al. | Applicant |
| US6012961(A) | 2000-01-01 | Sharpe et al. | Applicant |
| US6020876(A) | 2000-02-01 | Rosenberg et al. | Applicant |
| US6028593(A) | 2000-02-01 | Rosenberg et al. | Applicant |
| US6031973(A) | 2000-02-01 | Gomi et al. | Examiner |
| US6038603(A) | 2000-03-01 | Joseph | Applicant |
| US6046727(A) | 2000-04-01 | Rosenberg et al. | Applicant |
| US6057828(A) | 2000-05-01 | Rosenberg et al. | Applicant |
| US6061004(A) | 2000-05-01 | Rosenberg | Applicant |
| US6070010(A) | 2000-05-01 | Keenleyside et al. | Applicant |
| US6078308(A) | 2000-06-01 | Rosenberg et al. | Applicant |
| US6078968(A) | 2000-06-01 | Lo et al. | Applicant |
| US6083104(A) | 2000-07-01 | Choi | Applicant |
| US6090156(A) | 2000-07-01 | MacLeod | Applicant |
| US6100874(A) | 2000-08-01 | Schena et al. | Applicant |
| US6101425(A) | 2000-08-01 | Govindaraj et al. | Applicant |
| US6101530(A) | 2000-08-01 | Rosenberg et al. | Applicant |
| US6104158(A) | 2000-08-01 | Jacobus et al. | Applicant |
| US6125385(A) | 2000-09-01 | Wies et al. | Applicant |
| US6128006(A) | 2000-10-01 | Rosenberg et al. | Applicant |
| US6131097(A) | 2000-10-01 | Peurach et al. | Applicant |
| US6139177(A) | 2000-10-01 | Venkatraman et al. | Applicant |
| US6144895(A) | 2000-11-01 | Govindaraj et al. | Applicant |
| US6147647(A) | 2000-11-01 | Tassoudji et al. | Applicant |
| US6161126(A) | 2000-12-01 | Wies et al. | Applicant |
| US6166723(A) | 2000-12-01 | Schena et al. | Applicant |
| US6169540(B1) | 2001-01-01 | Rosenberg et al. | Applicant |
| US6173316(B1) | 2001-01-01 | De Boor et al. | Applicant |
| US6191774(B1) | 2001-02-01 | Schena et al. | Applicant |
| US6195592(B1) | 2001-02-01 | Schuler et al. | Applicant |
| US6209037(B1) | 2001-03-01 | Brown et al. | Applicant |
| US6216173(B1) | 2001-04-01 | Jones et al. | Applicant |
| US6219032(B1) | 2001-04-01 | Rosenberg et al. | Applicant |
| US6219033(B1) | 2001-04-01 | Rosenberg et al. | Applicant |
| US6232891(B1) | 2001-05-01 | Rosenberg | Applicant |
| US6233545(B1) | 2001-05-01 | Datig | Applicant |
| US6243078(B1) | 2001-06-01 | Rosenberg | Applicant |
| US6246390(B1) | 2001-06-01 | Rosenberg | Applicant |
| US6252579(B1) | 2001-06-01 | Rosenberg et al. | Applicant |
| US6252853(B1) | 2001-06-01 | Ohno | Applicant |
| US6259382(B1) | 2001-06-01 | Rosenberg | Applicant |
| US6271833(B1) | 2001-08-01 | Rosenberg et al. | Applicant |
| US6278439(B1) | 2001-08-01 | Rosenberg et al. | Applicant |
| US6285351(B1) | 2001-09-01 | Chang et al. | Applicant |
| US6288705(B1) | 2001-09-01 | Rosenberg et al. | Applicant |
| US6290565(B1) | 2001-09-01 | Galyean III et al. | Applicant |
| US6292170(B1) | 2001-09-01 | Chang et al. | Applicant |
| US6292174(B1) | 2001-09-01 | Mallett et al. | Applicant |
| US6292712(B1) | 2001-09-01 | Bullen | Applicant |
| US6292714(B1) | 2001-09-01 | Okabayashi | Applicant |
| US6295530(B1) | 2001-09-01 | Ritchie et al. | Applicant |
| US6300936(B1) | 2001-10-01 | Braun et al. | Applicant |
| US6300937(B1) | 2001-10-01 | Rosenberg | Applicant |
| US6301634(B1) | 2001-10-01 | Gomi et al. | Examiner |
| US6304091(B1) | 2001-10-01 | Shahoian et al. | Applicant |
| US6309275(B1) | 2001-10-01 | Fong et al. | Applicant |
| US6310605(B1) | 2001-10-01 | Rosenberg et al. | Applicant |
| US6317116(B1) | 2001-11-01 | Rosenberg et al. | Applicant |
| US6317871(B1) | 2001-11-01 | Andrews et al. | Applicant |
| US6343349(B1) | 2002-01-01 | Braun et al. | Applicant |
| US6400996(B1) | 2002-06-01 | Hoffberg et al. | Applicant |
| US6425118(B1) | 2002-07-01 | Molloy et al. | Applicant |
| US6442451(B1) | 2002-08-01 | Lapham | Examiner |
| US6288716(B1) | 2002-09-01 | Humpleman | Applicant |
| US6463404(B1) | 2002-10-01 | Appleby | Applicant |
| US6497606(B1) | 2002-12-01 | Fong et al. | Applicant |
| US6519594(B1) | 2003-02-01 | Li | Applicant |
| US6523171(B1) | 2003-02-01 | Dupuy et al. | Applicant |
| US6528963(B1) | 2003-03-01 | Hong | Applicant |
| US6546436(B1) | 2003-04-01 | Fainmesser et al. | Applicant |
| US6571141(B1) | 2003-05-01 | Brown | Applicant |
| US6652378(B1) | 2003-11-01 | Cannon et al. | Applicant |
| US6658627(B1) | 2003-12-01 | Gallup et al. | Applicant |
| US6662361(B1) | 2003-12-01 | Jackson | Applicant |
| US6665688(B1) | 2003-12-01 | Callahan et al. | Applicant |
| US6678713(B1) | 2004-01-01 | Mason et al. | Examiner |
| US6778949(B1) | 2004-08-01 | Duan et al. | Applicant |
| US2001/0020944(A1) | 2001-09-01 | Brown et al. | Applicant |
| US2001/0029443(A1) | 2001-10-01 | Miyahira | Applicant |
| US2001/0032268(A1) | 2001-10-01 | Brown et al. | Applicant |
| US2001/0037492(A1) | 2001-11-01 | Holzmann | Applicant |
| US2002/0165708(A1) | 2002-11-01 | Kumhyr | Applicant |
| US2002/0177453(A1) | 2002-11-01 | Chen et al. | Applicant |
| US2003/0033150(A1) | 2003-02-01 | Balan et al. | Applicant |
| US2003/0061023(A1) | 2003-03-01 | Menezes et al. | Applicant |
| US2003/0069998(A1) | 2003-04-01 | Brown et al. | Applicant |
| US2004/0025150(A1) | 2004-02-01 | Heishi et al. | Applicant |
| EP442676(A2) | 1991-08-01 | Applicant | |
| EP281427(B1) | 1992-08-01 | Applicant | |
| EP508912(A1) | 1992-10-01 | Applicant | |
| EP583908(A2) | 1994-02-01 | Applicant | |
| EP821522(A2) | 1998-01-01 | Applicant | |
| EP275826(A1) | 1998-07-01 | Applicant | |
| GB2224896(A) | 1991-12-01 | Applicant | |
| JP59228473(A) | 1983-06-01 | Applicant | |
| JP8161335(A) | 1996-06-01 | Applicant | |
| JP2000020114(A) | 2000-01-01 | Applicant | |
| WO92/11731(A2) | 1992-07-01 | Applicant | |
| WO93/08654(A1) | 1993-04-01 | Applicant | |
| WO95/07504(A1) | 1995-03-01 | Applicant |
Non-Patent Literature (92)
- Sue Chen, Jonathon Lin; “Computer Numerical Control: Essentials in Programming and Networking”; Part 5, Chapter 27; pp. 824-848, No Date.Applicant
- Pritschow et al.; “Open System Controllers: Challenge for the Future of the Machine Tool Industry”; pub. Jan. 15, 1993; pp. 449-452.Applicant
- William E. Ford; “What Is an Open Architecture Robot Controller” pub. Aug. 16, 1994; pp. 27-32.Applicant
- Marcos et al.; “A New Solution for Integrating Control Devices Involved in Computer-Integrated Manufacturing”; pub. Sep. 2, 1996; pp. 485-490.Applicant
- Chu and Wang; “Development of a Practical SFC System for CNC Machine Shop”; pub. 1994; pp. 362-367.Applicant
- MICROSOFT; “The Microsoft Object Technology Strategy”; pub. Mar. 1994; pp. 1-33.Applicant
- MICROSOFT; “Open Systems: Technology, Leadership, and Collaboration”; pub. Mar. 1994; pp. 1-15.Applicant
- MICROSOFT; Microsoft OLE Today and Tomorrow: Technology Overview; pub. Dec. 1993; pp. 1-9.Applicant
- MICROSOFT; “Object Linking and Embedding 2.0 Backgrounder”; pub. Sep. 1993; pp. 1-15.Applicant
- Robert Anderson; “SMART: A Modular Architecture for Robotics and Teleoperation”; pub. 1993; pp. 416-421.Applicant
- Proctor et al.; “Validation of Standard Interfaces from a Machine Control”; pub. 1996; pp. 659-664.Applicant
- Altintas et al.; “Design and Analysis of a Modular CNC System”; pub. Mar. 4, 1990; pp. 305-316.Applicant
- Wright et al.; “Open Architecture Manufacturing: The Impact of Open-System Computers on Self-sustaining Machinery and the Machine Tool Industry”; pp. 41-47, No Date.Applicant
- Protoctor et al.; “Open Architecture Controllers”; pub. Jun. 1997; pp. 60-64.Applicant
- Lutz et al.; “OSACA-The Vendor-Neutral Control Architecture”; pub. Dec. 1997; pp. 247-256.Applicant
- Morales et al.; “A Generalised Software Control System for Industrial Robots”; pub. 1998; pp. 411-416.Applicant
- Feng et al.; “Distributed Control of a Multiple-Tethered Mobile Robot System for Highway Maintenance and Construction”; pub Nov. 1997; pp. 383-392.Applicant
- Fedrowitz; “IRL-Based Expansion of the Commonly Used High-Level Language C for Robot Programming:” pub. Oct. 1995; 5 pages.Applicant
- Szabo et al.; “Validation Results of Specifications for Motion Control Interoperability”; pub. 1997; pp. 166-167.Applicant
- Chang et al.; “Development and Implementation of an Application Programming Interface for PC/DSP-based Motion Control System”; pub. 1998; pp. 94-105.Applicant
- Erol et al.; “Open System Architecture Modular Tool Kit for Motion and Machine Control”; pub. Sep. 2000; pp. 281-291.Applicant
- Mizukawa et al.; “OriN: Open Robot Interface for the Network: A Proposed Standard”; pub. May 2000; pp. 344-350.Applicant
- Michaloski et al.; “A Framework for Component-base CNC Machines” pub. Nov. 1998; pp. 132-143.Applicant
- Bouzouia et al.; “A Three-layer Workcell Control Architecture Design”; pub. May 1998; pp. 1185-1191.Applicant
- Morales et al.; “GENERIS: The EC-JRC Generalized Software Control System for Industrial Robots”; pub. 1999; pp. 26-33.Applicant
- Muir et al.; “Mechatronic Objects for Real-time Control Software Development”; pub. Nov. 1998; pp. 251-265.Applicant
- Cho et al.; “A Compact/Open Network-based Controller Incorporating Modular Software Architecture for a Humanoid Robot”; pub. 1999; pp. 341-355.Applicant
- Ge et al.; “A One-stop Solution in Robotic Control System Design”; pub. Sep. 2000; pp. 42-55.Applicant
- McGraw et al.; “A Friendly Command, Control, and Information System for Astronomy”; pub. 1996; pp. 356-367.Applicant
- Jackman; “Robotic Control Using Sequential Function Charts”; pub. 1996; pp. 120-128.Applicant
- Mizukawa et al.; “De-facto Standard API for Open and Networked Industrial Robots”; pub. Oct. 1999; pp. 455-462.Applicant
- Leu et al.; “A Telemanufacturing Workcell over the Internet”; pub. Nov. 1998; pp. 230-237.Applicant
- Natale et al.; “Robust Hybrid Force/Position Control with Experiments on an Industrial Robot”; pub. Sep. 19, 1999; pp. 956-961.Applicant
- Nilsson et al.; “Integrated Architecture for Industrial Robot Programming and Control”; pub. Dec. 31, 1999; pp. 205-226.Applicant
- Valera et al.; “Interactive Online Evaluation of Robot Motion Control”; pub. Aug. 22, 1999; pp. 1039-1043.Applicant
- “NEMI Low-cost Controller Project”; pub. Dec. 1996; total pages 392.Applicant
- Sperling; “Designing Applications for an OSACA Control”; pub. Nov. 16, 1997; 5 pages.Applicant
- Lutz et al.; “OSACA: The Vendor-neutral Control Architecture”; pub. 1997; 10 pages.Applicant
- Sperling et al.; “Enabling Open Control Systems: An Introduction to the OSACA System Platform”; pub. May 1996; pp. 1-8.Applicant
- “Requirements of Open Modular Architecture Controllers for Applications in the Automotive Industry”; pub. Dec. 13, 1994; pp. 1-13.Applicant
- Open, Modular Architecture Controls at GM Powertrain; pub. May 14, 1996; pp. 1-33.Applicant
- Proctor et al.; “Validation of Standard Interfaces for Machine Control”; pub. Dec. 6, 2000; pp. 1-7.Applicant
- “Technologies Enabling Agile Manufacturing (TEAM) Intelligent Closed Loop Processing”; pub. Jan. 11, 1996; 30 pages.Applicant
- Bradley Bargen and Peter Donnely; Inside Direct X—In Depth Techniques for Developing High-Performance Multimedia Applications; 1988; Chps. 1, 18-20, 22-27; Microsoft Press; U.S.Applicant
- Peter Kovach; Inside Direct3D—The Definitive Guide for Real-Time 3D Power and Performance for Microsoft Windows; 2000; Chps. 1, 7, 15; Microsoft Press; U.S.Applicant
- M. Farsi and M. Barbosa; CANopen Implementation—Applications to Industrial Network; 2000; Research Studies Press Ltd.; England and U.S.Applicant
- Wolfhard Lawrenz; CAN System Engineering—From Theory to Practical Applications; 1997; Springer-Verlag New York, Inc.; U.S.Applicant
- Allen-Bradley; “CNCnet Software Library”; Oct., 1992; Publication 8000-6.1.1; U.S.Applicant
- Robert Bosch GmbH; “CAN Specification”; Sep., 1991; Version 2.0.Applicant
- SISCO, Inc.; “Overview and Introduction to the Manufacturing Message Specification (MMS)”; 1994-1995; Revision 2; Systems Integration Specialists Company, Inc.; Sterling Heights, Michigan, U.S.Applicant
- ISO-9506-1 “Industrial Automation Systems—Manufacturing Message Specification—Part 1: Service definition”; Aug., 2000; pp. i-22; ISO/IEC; Switzerland.Applicant
- ISO-9506-2 “Industrial Automation Systems—Manufacturing Message Specification—Part 2: Protocol specification”; Aug. 2000; pp. i.-6; ISO/IEC; Switzerland.Applicant
- SISCO Inc.; “MMS-EASE”; Jan. 1996; Systems Integration Specialists Company, Inc.; Sterling Heights, Michigan, U.S.Applicant
- ANSI/EIA-484-A “Electrical and Mechanical Interface Characteristics and Line Control Protocol Using Communication Control Characters for Serial Data Link Between a Direct Numerical Control System and Numerical Control Equipment Employing Asynchronous Full Duplex Transmission”; Jun., 1995; Electronic Industries Association; U.S.Applicant
- ISO/IEC 7498-1 “Information Technology—Open Systems Interconnection-Basic Reference Model: The Basic Model”; Nov. 1994; U.S.Applicant
- ISO/IEC 7498-3 “Information Technology—Open Systems Interconnection-Basic Reference Model: Naming and Addressing”; Apr. 1997; U.S.Applicant
- Todd J. Schuett; “The Benefits and Data Bottlenecks of High Speed Milling”; Aug., 1995; conference paper presented at Southeastern Michigan Chapter American Mold Builders Association; Creative Technology Corporation; U.S.Applicant
- Todd J. Schuett; “The Ultimate DNC; Direct CNC Networking (DCN)”; Modern Machine Shop; Jan., 1996; Creative Technology Corporation; U.S.Applicant
- Todd J. Schuett; “Advanced Controls for High Speed Milling”; conference paper presented at the SME “High Speed Machining” conference; May 7-8, 1996; Creative Technology Corporation; U.S.Applicant
- Leitao, Machado & Lopes; “A Manufacturing Cell Integration Solution”; paper developed at CCP as a part of the ESPRIT 5629 Project; Oct., 1995.Applicant
- Mitsubishi Electric; Mitsubishi Electric Advance: Programmable Logic Controllers Edition; Sep., 1996; vol. 76; Mitsubishi Electric Corporation; Tokyo.Applicant
- Farsi, M.; “Flexible and Reliable Robotics Cells in Factory Automation”; 1993; pp. 520-525.Applicant
- Chu & Wang; “Development of a Practical SFC System for CNC Machine Shop”; International Conference on Data and Knowledge Systems for Manufacturing and Engineering; May 1994; pp. 362-367, vol. 1; pp. xx+745, vol. 2.; Chinese Univ.; Hong Kong.Applicant
- Farsi, M.; “Device Communication for Flexible Manufacturing:-A New Concept”; 1994; pp. 328-334.Applicant
- Farsi, M.; “A Production Cell Communication Model in Factory Automation Using the Controller Area Network”; 1995; pp. 90-95.Applicant
- Farsi, M. “CANopen: The Open Communications Solution”; 1996;pp. 112-116.Applicant
- Katayama et al.; “A Motion Control System with Event-driven Motion-module Switching Mechanism for Robotic Manipulators”; IEEE International Workshop on Robot and Human Communication; Jul., 1993; pp. 320-325; U.S.Applicant
- Matsui et al.; “An Event-Driven Architecture for Controlling Behaviors of the Office Conversant Mobile Robot, Jijo-2”; Proceedings of the 1997 IEEE International Conference on Robotics and Automation; Apr. 1997; pp. 3367-3372; U.S.Applicant
- Microsoft Corporation; “How to Write and Use ActiveX Controls for Microsoft Windows CE 3.0”; Windows CE 3.0 Technical Articles; Jun., 2000; pp. 1-5.Applicant
- Microsoft Corporation; “Notes on Implementing an OLE Control Container”; ActiveX Controls Technical Articles; Sep. 21, 1994; pp. 1-47.Applicant
- Microsoft Corporation; “What OLE Is Really About”; OLE (General) Technical Articles; Jul., 1996; pp. 1-33.Applicant
- Microsoft Corporation; “Categorizing by Component Capabilities”; Platform SDK: COM; Nov., 2001; pp. 1-23.Applicant
- Microsoft Corporation; “Dynamic Data Exchange”; Windows 3.1 SDK Guide to Programming; 1992, 1993; Chapter 22; 21 pages.Applicant
- Microsoft Corporation; “Dynamic Data Exchange Management Library”; Win32 SDK: Prog. Ref. vol. 2; 1992, 1993; Chapter 77; 26 pages.Applicant
- Microsoft Corporation; “Network Dynamic Data Exchange”; Windows for Workgroups 3.1 Resource Kit; 1992, 1993; Chapter 11; 19 pages.Applicant
- WOSA Backgrounder: Delivering Enterprise Services to the Windows-based Desktop, Jul. 1993, Microsoft Development Library; pp. 1-19.Applicant
- WOSA Inside Windows 95; pp. 348-351, no date.Applicant
- Software Products for Industrial Automation, ICONICS; 6 pages, no date.Applicant
- WEB 3.0 Product Brochure, Trihedral Engineering Ltd. (1994); 6 pages.Applicant
- The Complete, Computer-Based Automation Tool (IGSS) Seven Technologies A/S; 6 pages no date.Applicant
- Oregon Micro Systems Product Guide: pp. 1-20, no date.Applicant
- AIMAX-WIN Product Brochure, TA Engineering Co., Inc.; 8 pages, no date.Applicant
- XANALOG Model NL-SIM Product Brochure, XANALOG, 4 pages, no date.Applicant
- ExperTune PID Tuning Software, Gerry Engineering Software; 6 pages, no date.Applicant
- PMAC Product Catalog, p. 43, no date.Applicant
- Paragon TNT Product Brochure, Intec Controls Corp.; 6 pages, no date.Applicant
- Aerotech Motion Control Product Guide; pp. 233-234, no date.Applicant
- OpenBatch Product Brief, PID, Inc.; 6 pages, no date.Applicant
- PC/DSP-Series Motion Controller C Programming Guide; pp. 1-54, no date.Applicant
- FLX Product Brochure, Intellution (1994); 6 pages.Applicant
- Precision Motion Controls Product Guide; p. 17, no date.Applicant
- Compumotor Digiplan (1993-94) Catalog pp. 10-11.Applicant