Patent Grant
11897132
Network redundancy is the process of adding additional instances of network devices and lines of communication to help ensure network availability and decrease the risk of failure along a critical data path. The underlying premise of network redundancy is to have a backup system in place in the event a point of failure in a network disrupts or bring downs the entire system. Redundancy in communication networks helps to mitigate single points of failure to ensure better network stability and uptime in the face of events that would otherwise take the system offline.
Network stability and redundancy in communication networks can be of importance in robotic contexts. Many robots and robotic systems possess complex and sophisticated on-board electronic and other hardware components (e.g., actuators, motors, sensors, switches, wiring, power-related components, controllers, computers, communication-related components, and others), many of which are configured to interface with one another and that are controlled via a computerized on-board network for the operation of the robot or robotic system. Disruption or failure of this network can be costly, and in some cases can create unsafe operating conditions. For example, in robots or robotic systems (e.g., wearable robotic exoskeletons donned by human beings, humanoid robots, teleoperated robots, unmanned ground robots, and others), network failures in conveying operation signals to controllers, motors and actuators of the robot can leave the robot motionless or operating beyond a range of movement. This is particularly problematic for those robots that interact with humans, or that comprise a human interface (e.g., human users donning an exoskeleton), network failures can result in operation of the robot that is not comfortable, or worse, dangerous or unsafe, for the human being interfacing with the robot. To avoid unnecessary operational downtime, untimely and costly repairs, as well as potentially unsafe operating conditions for humans interfacing with certain types of robots or robotic systems, safeguards centered on network redundancy can help to ensure continued functionality, serviceability, and integrity of an on-board robot network during operation of the robot or robotic system.
An initial overview of the technologies is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technologies more quickly but is not intended to identify key features or essential features of the technologies, nor is it intended to limit the scope of the claimed subject matter.
Technologies are described herein for redundant network communication in a robot or robotic system (referred to herein generally as a robot). A robot can comprise a machine capable of performing a complex series of actions by way of commands or instructions transmitted over a communications network from a central or main controller to one or more local controllers associated with one or more robotic components, the main controller, the local controller(s) and the robotic component(s) being part of the communications network. A robot control system can be used to control the movement of the robot, as well as to control other functioning devices of the robot. This can occur via commands or instructions from mechanical robotic components and program systems that make it possible to control the robot. The robotic components can be controlled in various ways using commands sent over the robot's communication network, including wireless control (e.g., radio control), semi-autonomous control (which can be a mix of fully automatic and wireless control), and fully autonomous control (which can use artificial intelligence). Each robotic component can comprise or otherwise be associated with its own local robotic controller (e.g., component controller) for controlling a part of the robot (e.g., robotic components can include, but are not limited to, actuators, motors, manipulators, end-effectors, and the like). For example, a robotic joint can include a local controller for controlling a robotic component in the form of a motor to effectuate rotation movement of the robotic joint.
A wide variety of robots or robotic systems exist, including, but not limited to, humanoid robots, exoskeleton robots, robotic arms, and other robots and robotic systems, and one fundamental technical problem of robotics is system communication faults that occur due to breaks in communication channels, such as damage to a network cable or a failure of a network device. Indeed, network communication stability remains an inevitable challenge in the world of robotics. The technologies described herein address the technical problem of system communication faults in robotics by providing redundant communication channels between a main robotic controller and robotic components.
In one example configuration, a robot control system can comprise a redundant network communication system comprising two or more network channels used for communications between a main robotic controller and robotic components (e.g., actuators, motors, manipulators, end-effectors, and the like) that have or that are otherwise associated with individual or local controllers that are operable to facilitate control of the robotic components. One of the network channels can be designated as a primary network channel and the other network channel can be a redundant secondary network channel. The main robotic controller can be configured to duplicate an original or originating data signal (e.g., a control signal) and to send the duplicated data signal in parallel over the primary and secondary network channels to one or more of the robotic components, which are in network communication with the main robotic controller.
The first or primary network channel can be configured to facilitate network communication between the main robotic controller and a local controller of a robotic component to facilitate conveying a first data signal from the main robotic controller to the to the local controller for operating the local controller. The second or secondary network channel can be configured to facilitate network communication between the main robotic controller and the local controller to facilitate conveying a second data signal from the main robotic controller to the local controller for operating the local controller. The first data signal and the second data signal can be configured to be redundant data signals that are sent respectively over the first or primary network channel and the second or secondary network channel.
A local controller associated with a robotic component can be configured to compare the data signals received over the primary and secondary network channels to determine signal integrity of the data signals. For example, the local controller can receive a first data signal sent over the primary network channel and a second data signal sent over the secondary network channel. In response to receiving the first and second data signals, the local controller of the robotic component can compare the signal integrity of the first data signal to the signal integrity of the second data signal to determine whether degradation of the first data signal has occurred. In the event that no degradation of the first data signal has occurred, the local controller cancan be configured to process the data signal to obtain a command encoded in the data signal and to cause an associated robotic component perform the command obtained from the second data signal. However, in the event that degradation of the first data signal is detected, then the local controller of the robotic component can be configured to can select the second data signal for processing and perform the command encoded in the second data signal.
In one example, the present disclosure sets forth a system for redundant network communication in a robot. The system can comprise a main robotic controller in network communication with one or more robotic components. The system can further comprise a local controller in network communication with the main robotic controller and a controlled component of the one or more robotic components that is controlled by the local controller to perform a function of the robot. The system can further comprise one or more processors and a memory in network communication with one or more of the main robotic controller and the local controller. The memory can include instructions that, when executed by the processor, cause one or more of the local controller and the main robotic controller to: (1) transfer first and second data signals between the main robotic controller and the local controller via first and second network channels, wherein a command is encoded in the first and second data signals and the first data signal is sent over the first network channel, and the second data signal is sent over the second network channel; (2) compare the first data signal with the second data signal to determine signal integrity of the first and second data signals; (3) determine degradation of the first data signal if the signal integrity of the first data signal is less than the signal integrity of the second data signal; and (4) select the second data signal received over the second network channel for processing if degradation of the first data signal is determined.
In some examples, the memory further includes instructions that, when executed by the processor, cause the local controller or the main robotic controller to: (1) process the second data signal to obtain the command encoded in the second data signal; and (2) cause the robotic component to perform an action based on the command obtained from the second data signal.
In some examples, the instructions, when executed by the processor, can further cause the local controller or the main robotic controller to: (1) compare signal integrity of the first and second data signals; and (2) determine whether a signal integrity of the first data signal is less than a signal integrity of the second data signal.
In some examples, the instructions, when executed by the processor, can further cause the local controller or the main robotic controller to: (1) compare a number of data packets contained in each of the first and second data signals; and (2) determine that a number of data packets contained in the first data signal is less than a number of data packets contained in the second data signal, or determine that a data packet was missed in a case when the main robotic controller or the local controller does not receive the data packet within a prescribed amount of time.
In some examples, the instructions, when executed by the processor, can further cause the local controller or the main robotic controller to log signal integrity metrics for the first and second data signals to allow diagnosis of the degradation of the first data signal.
In some examples, the instructions, when executed by the processor, can further cause the local controller or the main robotic controller to generate a system notification to indicate a problem with the first network channel associated with the degradation of the first data signal.
In some examples, the main robotic controller or the local controller can send the first and second data signals in parallel over the first and second network channels.
In some examples, the instructions, when executed by the processor, can further cause the local controller or the main robotic controller to: (1) transfer a third data signal containing a command sent over a third network channel in parallel with sending of the first and second data signals, and (2) compare the third data signal to the first and second data signals to determine signal integrity degradation of any of the first, second, or third data signals.
In some examples, the first, second, and third network channels each comprise a cable communication channel, a power-line communication channel, or a wireless communication channel.
In another example of the present disclosure a computer implemented method for redundant network communication can include transferring a command between a main robotic controller and a local controller in network communication with the main robotic controller and a controlled component of a robotic component that is controlled by the local controller to perform a function of the robot, wherein a command is encoded in a first and second data signal at the main robotic controller or the local controller, and the first data signal is sent over a first network channel, and the second data signal is sent over a second network channel. The method can further include comparing the first data signal with the second data signal to determine signal integrity associated with the first and second network channels. The method can further include determining if the signal integrity of the first data signal is degraded as compared to the signal integrity the second data signal. The method can further include processing the second data signal received over the second network channel to obtain the command encoded in the second data signal. The method can further include performing an action based on the command obtained from the second data signal.
In some examples of the method, comparing the first and second data signals further comprises comparing a number of data packets received in each of the first and second data signals.
In some examples of the method, comparing the first and second data signals further comprises comparing a signal to noise ratio of the first data signal to a signal to noise ratio of the second data signal.
In some examples, the method further comprises writing signal integrity metrics for the first and second data signals to a system log to allow diagnosis of the degradation of the first data signal.
In some examples, the method further comprises generating a system notification to indicate a problem with the first network channel associated with the degradation of the first data signal and displaying the system notification on a display device to alert a user of a problem with the first network channel associated with the degradation of the first data signal.
In some examples of the method, performing the action based on the command comprises executing instructions to actuate the controlled component of the robotic component.
In some examples, the method can further comprise transferring between the main robotic controller and the local controller a third data signal containing the command sent over a third network channel in parallel with sending of the first and second data signals over the first and second network channels. The method can further comprise comparing the third data signal to the first and second data signals to determine signal integrity degradation of any of the first, second, or third data signals, wherein the first, second, and third network channels each comprise a cable communication channel, a power-line communication channel, or a wireless communication channel.
Another example of the present disclosure can be a non-transitory machine-readable storage medium including instructions embodied thereon, wherein the instructions, when executed by at least one processor, cause a redundant network communications system of a robot to: (1) transfer between a main robotic controller and a local controller associated with a controlled component of robotic component and in network communication with the main robotic controller, first and second data signals sent over primary and secondary network channels, respectively, wherein an original data signal is duplicated at the main robotic controller or local controller to generate the first data signal and the second data signal; (2) compare the first and second data signals to determine signal integrity of the first and second data signals, wherein the first data signal is compared to the second data signal; (3) determine whether the signal integrity of the first data signal is degraded as compared to the signal integrity of the second data signal; and (4) process the second data signal received over the secondary network channel.
In some examples of the non-transitory machine-readable storage medium, the second data signal is processed to obtain a command encoded in the second data signal and to cause the robotic component to perform an action based on the command obtained from the second data signal.
In some examples, the non-transitory machine-readable storage medium can further comprise instructions, that when executed by the at least one processor, cause the redundant network communications system to: (1) compare signal integrity of the first and second data signals; and (3) determine whether a signal integrity of the first data signal is less than a signal integrity of the second data signal.
In some examples, the non-transitory machine-readable storage medium can further comprise instructions, that when executed by the at least one processor, cause the redundant network communications system to: (1) compare a number of data packets contained in each of the first and second data signals; and (2) determine whether a number of data packets contained in the first data signal is less than a number of data packets contained in the second data signal, or determine whether a data packet was missed in a case when the data packet is not received within a prescribed amount of time.
In some examples, the non-transitory machine-readable storage medium can further comprise instructions, that when executed by the at least one processor, cause the redundant network communications system to write signal integrity metrics for the first and second data signals to a system log to allow diagnosis of the degradation of the first data signal.
In some examples, the non-transitory machine-readable storage medium can further comprise instructions, that when executed by the at least one processor, cause the redundant network communications system to generate a system notification to indicate a problem with the primary network channel associated with the degradation of the first data signal.
In some examples, the non-transitory machine-readable storage medium can further comprise instructions, that when executed by the at least one processor, cause the redundant network communications system to: (1) transfer, between the main robotic controller and the local controller, a third data signal generated from the original data signal and sent over a tertiary network channel in parallel with sending of the first and second data signals over the primary and secondary network channels, and (2) compare the third data signal to the first and second data signals to determine signal integrity degradation of any of the first, second, or third data signals, wherein the primary, secondary, and tertiary network channels each comprise a cable communication channel, a power-line communication channel, or a wireless communication channel.
To further describe the present technologies, examples are now provided with reference to the figures.
As shown, the robotic exoskeleton 100 can include a plurality of robotic components, systems and the like (e.g., local controllers and controlled components such as joints or mechanisms that actuate to produce movement or operate functions of the robotic exoskeleton 100) that facilitate movement of the robotic exoskeleton 100 in a plurality of degrees of freedom. For example, as shown, the robotic exoskeleton 100 can include one or more of a shoulder joint 102, an elbow joint 104, a wrist joint 106, a hip joint 108, and a knee joint 110, each of these facilitating movement of the robotic exoskeleton 100 in corresponding degrees of freedom. However, the present technology is not to be limited by the joints, robotic components, systems or the like illustrated in
Each robotic component 204 can further have or otherwise be associated with a controlled component 214. The controlled component 214 can be for driving motion and/or other functions of the robotic component 204. It is to be understood that the controlled component 214 can be any component used for performing or actuating a function or motion of a robot and is not intended to be limited in any way by this disclosure. Indeed, the controlled component (e.g., 214) of any robotic components in the robot 100 can be any functioning device of the robot 100 including, but not limited to, motors, gas or fluid or other actuators, clutches, transmissions, sensors, imaging devices, audio recording or playing devices, light emission devices, electrical filter circuits, sensors, or any other function or device of any kind within a robot that is driven or controlled by a controller. The controlled component 214 can be in network communication with the local controller 206 and the main robotic controller 202. The controlled component 214 can be in network communication with the main robotic controller 202 through a tertiary network channel 212.
The main robotic controller 202 manages commands and data to direct or regulate the movement and function of robotic components 204 included in the robot 100. The main robotic controller 202 sends commands and data to, and receives commands and data from, one or more local controllers 206 associated with one or more robotic components 204 using the primary network channel 208 and the redundant secondary network channel 210 for the purpose and function of facilitating the control and operation of the robotic components 204, as well as for other purposes. In other words, the commands and data from and to the main robotic controller 202 cause the robot, with its robotic components 204, to perform its various intended functions. More specifically, the main robotic controller 202 and the local controllers 206 (i.e., distributed controllers) each can be configured to send and/or receive data (including commands, sensor data, control parameters, and other key information) used to operate the robotic system, including controlling the robotic system and its various components, monitoring the robotic system health and any subsystems health, configuring the robotic system and its subsystems, and so forth. Indeed, directing the movement of the robot is only one of many functions that can be performed by the main controller 202 and the local or distributed controllers 206. Exchange of corruption free data between these signal conditioning, processing and control modules ensures proper and safe operation of the robot and its various systems or subsystems.
The network channels are communication channels. A communication channel refers to a physical transmission medium such as a wire, and software realized communication protocols or to a logical connection over a multiplexed medium, such as a radio channel in telecommunications and computer networking. A communication channel is used to convey an information signal (data signal), for example, a digital bit stream, from a sender (or transmitter) to one or more receivers. A communication channel has a certain capacity for transmitting information, often measured by the communication channel's bandwidth in Hertz (Hz) or a data rate in bits per second.
The primary and secondary network channels 208 and 210, respectively, can comprise a communication medium that provides a path for data transmission between the main robotic controller 202 and a local controller 206, such as the one associated with a robotic component 204. The term “associated with” is intended to cover all of the possible configurations or arrangements in which a local controller 206 is operable to receive/send commands and data from/to the main robotic component 102 for the purposes discussed herein and as understood by those skilled in the art, such as for controlling one or more robotic components, initiating or executing a function or operation of the robot, and/or for any other purpose related to the monitoring and/or operation of the robot. In one aspect, the local controller 206 being associated with a robotic component can mean that a local controller is part of (i.e., an integral component of) the robotic component 204. In another aspect, the local controller being associated with a robotic component can mean that the local controller is not necessarily part of the robotic component 204, but nonetheless in communication with the robotic component 204 for the intended purpose of receiving, sending and processing commands and data, such as to control the robotic component 204, or to perform another function or operation.
The medium of the primary and secondary network channels 208 and 210 can include: network cables (e.g., multiple twisted pair cables, coaxial cable, optical fiber cable, patch cable, power-line cable), wireless network components, free space optical network components, or another suitable medium, or any combination of these. The network channels can support the transfer of information in one direction, either direction alternately, or both directions simultaneously. These two modes of communication (either direction alternately or both direction simultaneously) can be referred to as half duplex and full duplex, respectively.
In the example illustrated in
In instances in which a self-diagnosed communication fault (e.g., a missed data packet) is detected by the local controller or main robotic controller over a network channel (e.g., primary network channel 208), the main robotic controller and/or local controller can then default to send/receive messages over a redundant network channel (e.g., secondary network channel 210 to ensure continued network communication and proper operation of the robot. Alternatively, a communication can be sent in parallel over both the primary network channel 208 and the secondary network channel 210 to ensure that, in the event of a communication fault in the primary network channel 208, the communication can be sent/received by the local controller 206 and/or the main robotic controller 202 via the secondary network channel 210.
Furthermore, the main robotic controller 202 or the local controller 206 can send, in parallel, identical data signals containing a command intended for a robotic component 204 over the primary and secondary network channels 208 and 210. As an example, the main robotic controller 202 or local controller 206 can duplicate a data signal (e.g., an original data signal) containing a command or instruction intended for a robotic component 204 or the main robotic controller 202 to form the first and second data signals, both containing the command or instruction. Thereafter, the main robotic controller 202 can send/receive, in parallel, the first data signal over the primary network channel 208 and the second data signal over the secondary network channel 210 to/from the local controller 206 associated with the robotic component 204. Accordingly, the same command or instruction can be sent/received over both the primary network channel 208 and the secondary network channel 210 by the main robotic controller 202 or the local controller 206 associated with the robotic component 204 at substantially the same time.
In one example configuration, an external source (e.g., a remote control or remote computer) can send commands to the main robotic controller 202, and the main robotic controller 202 can forward the commands to one or more intended local controllers associated with one or more robotic components 204 over both the first and second network channels 208 and 210. In another example configuration, the main robotic controller 202 can be an autonomous system within the robot 100, and the main robotic controller 202 can generate commands intended for one or more robotic components 204 and send the commands to the one or more local controllers over both the first and second network channels 208 and 210. Additionally, the local controllers 206 can likewise send commands to the main robotic controller 202 based on user input. For example, an external source (e.g., a remote control or remote computer) can send commands to the local controllers 206, and the local controllers 206 can forward the commands to the main robotic controller 202 over both the first and second network channels 208 and 210. In another example configuration, the local controllers 206 can autonomous systems within the robot 100, and can generate commands intended for the main robotic controller 202 and send the commands to the main robotic controller 202 over both the first and second network channels 208 and 210.
The tertiary network channel 212 can be provided to facilitate additional redundant network communication back and forth between the main robotic controller 202 and local controllers associated with the robotic component 204. Specifically, the tertiary network channel 212 can be provided to facilitate additional redundant network communication back and forth between the main robotic controller 202 and the controlled component 214. The tertiary network channel 212 can be a power line providing power to the controlled component 214. Additionally or alternatively, the tertiary network channel 212 can provide data communication back and forth between the main robotic controller 202 and the controlled component 214, thereby providing redundant communication and driving of the controlled component 214 in case the local controller 206 fails to provide control and data signals to the controlled component 214 for any reason, such as a failure of primary and secondary network channels 208 and 210.
Using redundant network channels for communication within the robot can lead to advantageous effects that avoid dangerous conditions and system failures. For example, instances in which a self-diagnosed communication fault (e.g., a missed data packet) is detected by the local controller or main robotic controller over a network channel (e.g., primary network channel 208), the main robotic controller or the local controller can then default to send messages over a redundant network channel (e.g., secondary network channel 210 to ensure continued network communication and proper operation of the robot even in the presence of a communication failure by one of the network channels. The self-diagnostic or self-verification features of the local controller used to individually diagnose signal integrity on the first and second network channels can be carried out using error detection algorithms and processes, such as using checksum, parity checks, cyclic redundancy checks.
Alternatively or in addition to the self-diagnostics described above, the local controller 206 or main robotic controller 202 can receive the first and second data signals sent over the primary and secondary network channels 208 and 210, and can compare the first data signal with the second data signal (namely the signal integrity of the first data signal can be compared with the signal integrity of the second data signal) to determine the signal integrity of the first data signal, which can be a health indicator of the primary network channel 208. For example, the signal integrity of the first data signal can be used to determine whether there is degradation in the first data signal that indicates a problem with the primary network channel 208.
Data signal degradation is a degradation or loss in quality, level, or standard of performance of a data signal. In other words, data signal degradation is a reduction or loss of “signal integrity” as used herein. Loss of signal integrity, or signal degradation, can be caused by a break in communication channels, such as damage to a network cable, network congestion, or other physical connectivity issues. Loss or reduction in signal integrity can be a weak or noisy RF signal, presence of RF interference, data packet loss, packet collision, or a failure of a network device. Degradation of a data signal can be identified when the signal integrity of one data signal is less than the signal integrity of the other data signal.
A loss in signal integrity can indicate that the first data signal sent over the primary network channel 208 has degraded during transfer between the main robotic controller 202 and the local controller 206 of the robotic component 204. Likewise, a degradation of the second data signal associated with the secondary network channel 210 can also be detected via comparison of the first and second data signals, in addition to using self-diagnostics, which can indicate that there can be a problem with the secondary network channel 210.
Accordingly, in response to receiving the first and second data signals, the local controller 206 of the robotic component 204 or the main robotic controller 202 can compare the data signals to determine the signal integrity of the data signals, data corruption, errors, a signal to noise ratio of the data signal that is lower than a desired value, as described in more detail below. In the case that the signal integrity of the first data signal, which is associated with the primary network channel 208, is less than the second data signal, which is associated with the secondary network channel 210, then the local controller 206 or main robotic controller 202 can determine that the first data signal is degraded. Degradation usually refers to a reduction in quality of a digital signal, and can be caused by noise, interference, damage to a network cable, a failure of a network device, or other problems that can occur within the communications network of the robot 100.
In response to determining that the first data signal received over the primary network channel 208 is degraded, the local controller 206, as associated with the robotic component 204, or the main robotic controller 202 can ignore or discard the first data signal and select the second data signal received over the secondary network channel 210. The local controller 206 can process the second data signal to obtain a command or instruction intended for the robotic component 204 (e.g., controlled component 214 of the robotic component 204), and execute the command or instruction to cause the robotic component 204 (e.g., via the controlled component 214) to perform an action based on the command or instruction. That is, the local controller 206 of the robotic component 204 can failover to the secondary network channel 210 to receive commands and data to prevent a shutdown of the robot 100 due to network degradation or failure in the primary network channel 208 that results in a communication fault. Thus, network redundancy can be accomplished by monitoring the primary network channel 208 for communication faults and failing over to the secondary network channel 208 when signal degradation in the primary network channel 208 is detected, which can indicate a network failure in the primary network channel 208.
It is to be understood that, although the robotic components 306A-N and 308A-N do not specifically show local controllers and controlled components as shown in
The main robotic controller 301 can provide power and data to the one or more robotic components 306A-N and 308A-N(e.g., the local controllers and/or the controlled components of the robotic components 306A-N and 308A-N) that operate various motions (e.g., degrees of freedom) and/or functions within the robot. The main robotic controller 301 can include a power distribution module 302 in electrical communication with the robotic components to facilitate providing electrical power to the robotic components (e.g., the local controllers and/or the controlled components of the robotic components 306A-N and 308A-N). The main robotic controller 301 can further include a data distribution module 304 to facilitate transferring control signals and other data between the robotic components (e.g., the local controllers and/or the controlled components of the robotic components 306A-N and 308A-N). Any number of robotic components can be used in a robot including right side robotic components 308A through 308N and left side robotic components 306A through 306N. The right side and left side robotic components 306A-308N can correspond to robotic components that facilitate degrees of freedom of movement (e.g., provided by joints) on the right and left side of the robot. However, those skilled in the art will recognize that these can also correspond to torso robotic components, or any robotic component regardless of placement, correspondence, function, and/or orientation.
As illustrated in
System 300 can include a secondary network channel 312 (e.g., second network channel) configured to facilitate network communication between the main robotic controller 301 and the local controllers of the robotic component(s) 306A-308N. The secondary network channel 312 can facilitate transfer of a second data signal between the main robotic controller 301 and the local controllers of robotic components 306A-308N for operating the robotic components. As shown, the secondary network channel 312 can deliver electrical power from the power distribution module 302 to the robotic component(s) 306A-308N. The secondary network channel 312 can comprise a single channel from the main robotic controller 301 that branches off to each robotic component or can comprise a separate channel for each robotic component from the main robotic controller 301. The medium of network channel 312 can include: network cables (e.g., twisted pair cables, coaxial cable, optical fiber cable, patch cable, power-line cable, Ethernet cables).
The secondary network channel 312 can be used to deliver both power and data between the main robotic controller 301 and the robotic components 306A-308N. As electric power needs to be delivered to local controllers and/or controlled components of the robotic components 306A-308N, the power lines between the main robotic controller 301 and the robotic component(s) 306A-308N can be utilized to also transfer data between the main robotic controller 301 and the robotic components 306A-308N. For example, the power distribution module 302 can be electrically connected to the data distribution module 304 via connection 316A to facilitate transfer of power from the power distribution module 302 to the data distribution module 304. Similarly, the data distribution module 304 can be electrically connected to the power distribution module 302 via connection 3168 to facilitate transfer of data signals from the data distribution module 304 to the power distribution module 302. It will be understood by one of skill in the art that connections 316A and 3168 can be combined into a single bi-directional power and communication pathway for conducting electric power and transferring data signals.
From the power distribution module 302, data signals can be tuned at a frequency, configured, and/or encoded to transmit over the secondary network channel 312 in tandem with the transmission of electric power without interfering with the data signals or the electric power transmission. The secondary network channel 312 can comprise one or more of connections 316A and 3168 (e.g., a first connection) that connect the power distribution module 302 to the data distribution module 304 and can be used to deliver a data signal from the data distribution module 304 to the power distribution module 302. The secondary network channel 312 can further comprise secondary network channel 312 connections (e.g., second connections), which can connect the power distribution module 302 and robotic components 306A-308N. Accordingly, secondary network channel 312 can be utilized as a power-line communication channel to deliver power and data to one or more elements (e.g., local controller(s) and/or controlled component(s)) of the robotic component(s) 306A-308N.
Similarly, system 300 can include a tertiary network channel 314 that provides electric power from the power distribution module 302 to one or more additional elements (e.g., controlled components such as motors, actuators, imaging devices, audio devices, sensors, recording devices, or other) of the robotic component(s) 306A-308N and data between one or more local controllers and/or controlled components of the robotic component(s) and the main robotic controller 301. Similar to the secondary network channel 312, the tertiary network channel 314 can deliver electric power from the power distribution module 302 and data from the data distribution module 304, via connection 316B to the power distribution module 302, over the tertiary network channel 314 to the robotic component(s) 306A-308N. From the power distribution module 302, data signals can be tuned at a frequency, configured, and/or encoded to transmit over the tertiary network channel 314 in tandem with the transmission of electric power without interfering with the data signals or the electric power transmission. Accordingly, tertiary network channel 314 can be utilized as a power-line communication channel to deliver power and data to one or more elements (e.g., controlled component(s)) of the robotic component(s) 306A-308N.
Furthermore, each robotic component 306A-308N can comprise a wireless network component (e.g., wireless transmitter, receiver, or transceiver) for facilitating wireless network communication. The data distribution module 304 can also comprise a wireless network component (e.g., wireless transmitter, receiver, or transceiver) for facilitating wireless network communication between the robotic component(s) 306A-308N and the data distribution module. The wireless network components of the robotic component(s) and the data distribution module 304 can make up a wireless network channel for sending data signals between the robotic components and the data distribution module 304. Thus, the wireless network channel can comprise a fourth redundant communication channel for providing data signals to robotic component(s) from the data distribution module 304. The wireless network channel can comprise any wireless communication medium including, electromagnetic waves, light beams through mirrors and/or fiber optics, light transmission, Bluetooth, Wi-Fi, or other methods of wireless data transmission.
Each of the robotic components 306A through 308N of
As shown in
The secondary network channel 312 can be configured to facilitate network communication between the main robotic controller 301 and the local controller 307B to facilitate conveying a second data signal between the main robotic controller 301 and the local controller 307B for operating the local controller 307B or communicating with the main robotic controller 301. The local controller 307B can include a second network interface 322 that connects, pairs, and/or interfaces with the secondary network channel 312 to facilitate the network communication between the local controller 307B and the main robotic controller 301 and to facilitate receiving the second data signal by the local controller 307B in tandem with the electric power for the local controller 307B from the power distribution module 302 of the main robotic controller 301. The second network interface 322 can be any of one or more of a port for receiving an electrical connection, a connector, a plug, a wire, a wireless transmitter and/or receiver, or any element that facilitates any kind of network and/or electrical communication recited herein. The disclosure is not intended to limit the interface in anyway.
The power distribution module 302 can provide electrical power to the local controller 307B of the robotic component 306A. Additionally, as shown, the data distribution module 304 can be electrically connected to the power distribution module 302 so that the data distribution module 304 can be provided with electrical power. Additionally, the secondary network channel 312 can be configured to provide electrical communication from the power distribution module 302 to the local controller 307B to facilitate providing power to the local controller 307B from the power distribution module 302.
The secondary network channel 312 can be in network communication with both the main robotic controller 301 and the local controller 307B through the power distribution module 302 to facilitate transferring the second data signal from the main robot controller 301 over the secondary network channel 312 in tandem with the power provided to the local controller 307B over the second network channel 312 from the power distribution module 302. The secondary network channel 312 can comprise one or more of connections 316A and 3168 (e.g., a first connection) that connects the power distribution module to the data distribution module. The secondary network channel 312 can further comprise the secondary network channel 312 connection (e.g., second connection) that can connect the power distribution module 302 and local controller 307B.
The connection 316A (e.g., first connection) between the data distribution module 304 and the power distribution module 302 can serve to provide the second data signal from the data distribution module 304 to the power distribution module 302. The secondary network channel 312 (e.g., second connection) can be configured to provide electrical communication from the power distribution module 302 to the local controller 307B to facilitate providing power to the local controller 307B from the power distribution module 302. The second data signal can be configured, tuned, and/or encoded by the local controller, the main robotic controller 301, data distribution module 304, or power distribution module 302 to travel along the secondary network channel 312 in tandem with electrical power in order to transfer redundant data signals between the local controller 307B and the main robotic controller 301 without interfering with either the electrical power or the data signals. The local controller 307B can include a decoder for decoding encoded second data signals sent over the secondary network channel 312 to the local controller 307B. Similarly, the main robotic controller 301 can include a decoder for decoding encoded second data signals sent over the secondary network channel 312 to the main robotic controller 301. The first data signal and the second data signal are configured to be redundant data signals that are sent respectively over the primary network channel 310 and the secondary network channel 312. Accordingly, the secondary network channel 312 can be utilized as a power-line communication channel to deliver power and data to one or more elements (e.g., local controller(s)) of the robotic component(s) or the main robotic controller 301. From the power distribution module 302, data signals can be tuned at a frequency, configured, and/or encoded to transmit over the secondary network channel 312 in tandem with the transmission of electric power without interfering with the data signals or the electric power transmission.
As shown, the tertiary network channel 314 can provide electrical power from power distribution module 302 to the controlled component 307A. The tertiary network channel 314 (e.g., main power line) can further be configured to facilitate network communication between the main robotic controller 301 and the local controller 307B to facilitate transferring a third data signal between the main robotic controller 301 and the local controller 307B for operating the local controller 307B or the main robotic controller 301. The local controller 307B can include a third network interface 324 that connects, pairs, and/or interfaces with the third network channel 314 to facilitate the network communication between the local controller 307B and the main robotic controller 301 and to facilitate receiving electrical power by the local controller 307B and transferring the third data signal between the local controller 307B and the main robotic controller 301. The electrical power can be received by the third network interface 324 from the power distribution module 302 of the main robotic controller 301, through the connection 318 and controlled component 307A, thus providing a redundant electrical power channel in addition to the redundant network communication channels for delivering redundant data signals. Furthermore, the third data signal can be received by the third network interface 324 from the data distribution module 304 of the main robotic controller 301 through the power distribution module 302, the controlled component 307A, and the connection 318. The third network interface 324 can be any of one or more of a port for receiving an electrical connection, a connector, a plug, a wire, a wireless transmitter and/or receiver, or any element that facilitates any kind of network and/or electrical communication recited herein for transferring data and/or electrical power. The disclosure is not intended to limit the interface in anyway.
The power distribution module 302 can provide electrical power to the controlled component 307A of the robotic component 306A. The controlled component 307A can be in network communication with the local controller 307B through connection 318. Accordingly, the third data signal can be provided to/from the local controller 307B from/to the data distribution module 304 via the power distribution module 302, the controlled component 307A, and connection 318 to facilitate transferring a third data signal between the main robotic controller 301 and the local controller 307B over the third network channel 314 in tandem with the power provided to the controlled component 307A over the third network channel 314 from the power distribution module 304.
Similar to the second data signal, the third data signal sent over the tertiary network channel 314 can be configured, tuned, and/or encoded by the main robotic controller 301, data distribution module 304, or power distribution module 302 to travel along the tertiary network channel 314 in tandem with electrical power in order to deliver redundant data signals to the local controller 307B without interfering with either the electrical power or the data signals. The local controller 307B can include a decoder for decoding encoded second data signals sent over the secondary network channel 312 to the local controller 307B. Similarly, the main robotic controller 301 can include a decoder for decoding encoded second data signals sent over the secondary network channel 312 to the main robotic controller 301. The first, second, and third data signals can be configured to be redundant data signals sent respectively over the first network channel, the second network channel, and the third network channel.
As disclosed, the robot, in addition to the primary, secondary, and tertiary network channels, can further include an additional wireless network channel facilitating network communication between the main robotic controller 301 and the local controller 307B to facilitate transferring a wireless data signal between the data distribution module 302 of the main robotic controller 301 and the local controller 307B. The local controller 307B can include a wireless network interface 324 that connects, pairs, and/or interfaces with the wireless network channel to facilitate the network communication between the local controller 307B and the main robotic controller 301 and to facilitate the local controller 307B receiving/sending the wireless data signal from/to the data distribution module 304 of the main robotic controller 301. The first network interface 320 can be any known wireless transmitter and/or receiver, or any element that facilitates any kind of wireless network and/or electrical communication recited herein, including wireless communication mediums, electromagnetic waves, light beams through fiber optics or mirrors, light transmission, Bluetooth, Wi-Fi, or other methods of wireless data transmission. The disclosure is not intended to limit the interface in anyway. The first, second, third, and wireless data signals can be configured to be redundant data signals for the local controller or main robotic controller that are sent separately over the primary, secondary, and tertiary network channels and the wireless network channel, respectively.
While
A network system within a robot as described above can have many different configurations and may be implemented in various ways and examples.
Furthermore, it is to be understood that, although the robotic components 508A-N do not specifically show local controllers and controlled components as shown in
As shown, the robot 510A can include the main robotic controller 502, a data distribution module 506, a power distribution module 504, and a plurality of robotic components 508A-N(e.g., actuators, motors, manipulators, end-effectors, and the like). Each robotic component 508A-N can be associated with a local controller and/or a controlled component (e.g., in the same or similar manner as the local controller 206 and controlled component 214 described above in association with
In one example, the cable communication channel 514A can serve as the primary network channel for the robot 510A, and the power-line communication channel 512 can serve as the redundant or backup (i.e., secondary) network channel for the robot 510A. It will be appreciated, however, that in some examples the power-line communication channel 512 can serve as the primary network channel and the cable communication channel 514A can serve as the secondary network channel. A physical transmission medium used for the cable communication channel 514A can include, but is not limited to, multi-twisted pair cables (e.g., Ethernet cable), optical fiber cable, and/or coaxial cable. A physical transmission medium used for the power-line communication channel 512 can include one or more alternating current (AC) power wires or direct current (DC) that supply electrical power to the robotic components 508A-N including the local controllers contained in the robot 510A. The power-line communication channel 512 can facilitate power-line communication (also known as power-line carrier or PLC), which can carry data on a conductor that is also used simultaneously for AC or DC electric power transmission or electric power distribution to the electric components of the robot 510A. The power-line communications channel 512 can operate by adding a modulated carrier signal to the wiring system of the robot 510A.
As illustrated, the main robotic controller 502 for the robot 510A can be in network communication with a data distribution module 506 configured to facilitate network communications between the main robotic controller 502 and the robotic components 508A-N(via a local controller and/or controlled component associated with the robotic components 508A-N), as well as between the main robotic controller 502 and any other local controllers. In response to receiving a communication from the main robotic controller 502, the data distribution module 506 may encode the communication into duplicate data signals and send one of the data signals over the cable communications channel 514A and send the other data signal to a power distribution module 504 configured to send the data signal over the power-line communication channel 512. In one example, the data distribution module 206 may encrypt the duplicate data signals before distributing the data signals to the robotic components 508A-N. Accordingly, an identical communication is transferred in parallel between at least one of the local controllers, such as those associated with the robotic components 508A-N, and the main robotic controller 502 over both the cable communication channel 514A and the power-line communication channel 512.
In response to receiving the data signals sent over the network channels 512 and 514A, a robotic component 508A-N, local controller (e.g., local controller 307B), such as one associated with one of the robotic components 508A-N, compares the data signals to determine the signal integrity of the data signals. In a similar way, the main robotic controller 202 can receive data sent over network channels 212 and 214 from the local controllers associated with robotic components 208A-N and compare the data signals to determine the signal integrity of the data signals. As described earlier in association with
Alternatively, or in addition to the comparison of data signals sent over network channels 212 and 214, the local controllers of robotic components 508A-N and/or the main robotic controller 502 can individual monitor and self diagnose communication statuses of the network channels 212 and 214 without comparing the redundant data signals sent over the network channels 212 and 214.
In the ring topology of
In one example, the wireless communication channel 614 can serve as the primary network channel for the robot 610, and the power-line communication channel 612 can serve as the redundant or backup (i.e., secondary) network channel for the robot 610. However, in other examples, the power-line communication channel 612 can be designated the primary network channel and the wireless communication channel 614 may be designated the secondary network channel.
As in the previous examples, the data distribution module 606 can distribute communications between the main robotic controller 602 and the local controllers, such as those associated with the robotic components 608A-N. In the example illustrated in
At least one of the local controllers or the main robotic controller, such as one or more associated with a respective one of the robotic components 608A-N, can receive the duplicate data signals over the network channels 612/614 and can compare the data signals in order to determine the signal integrity of the data signals. In the case that the one or more local controllers, such as those associated with the robotic components 608A-N, determines that the signal integrity of the data signal sent over the wireless communications channel 614 is degraded, the local controllers or the main robotic controller can ignore or discard the data signal and select the data signal received over the power-line communications channel 612 for processing.
It is to be understood that, although the robotic components 608A-N do not specifically show local controllers and controlled components as shown in
Similar to the preceding examples, a data distribution module 706 can distribute duplicated data signals in parallel between a main robotic controller 402 and the local controllers, such as those respectively associated with a plurality of robotic components 708A-N, using the network channels 712, 714, 716. That is, the data distribution module 706 can duplicate a data signal to create a first, second, and third data signal, and the data distribution module 706 can send the first data signal over the primary communication channel (e.g., the cable communication channel 716), send the second data signal over the secondary network channel (e.g., the wireless communication channel 716), and send the third data signal over the tertiary network channel (e.g., the power-line communication channel 712).
At least one of the local controllers, such as one or more associated with a respective one or more of the robotic components 708A-N, as well as the main robotic controller 702, can receive the duplicate data signals over the network channels 712, 714, 716 and can compare the three data signals to determine the signal integrity of the data signal associated with the primary network channel. In the case that the signal integrity of the data signal sent over the primary network channel is degraded, the one or more local controllers, such as one or more associated with a respective one of the robotic component 708A-N, or the main robotic controller 702 can select the data signal received over the secondary network channel for processing. In the case that the signal integrity of both the data signals sent over the primary and secondary network channels indicates degradation of the data signals, then the data signal sent over the tertiary network channel can be processed and used.
It is to be understood that the power-line communication channel 712 can be omitted from the robot 710A of
Similar to the preceding examples, duplicated data signals can be sent in parallel between a main robotic controller 402 and the local controllers, such as those respectively associated with a plurality of robotic components 708A-N, using the network channels 714 and 716. That is, duplicate data signals can be created by the local controllers or the main robotic controller 702 to create first and second data signal, and can send the first data signal over the primary communication channel (e.g., the cable communication channel 716) and send the second data signal over the secondary network channel (e.g., the wireless communication channel 716).
At least one of the local controllers, such as one or more associated with a respective one or more of the robotic components 708A-N, or the main robotic controller 702 can receive the duplicate data signals over the network channels 714, 716 and can compare the data signals to determine the signal integrity of the data signal associated with the primary network channel. In the case that the signal integrity of the data signal sent over the primary network channel is degraded, the one or more local controllers, such as one or more associated with a respective one of the robotic component 708A-N, or the main robotic controller 702 can select the data signal received over the secondary network channel for processing.
It is to be understood that, although the robotic components 708A-N do not specifically show local controllers and controlled components as shown in
The signal data of the primary, secondary, tertiary, and any other number of network channels (e.g., wireless comms channels 614, 716) can be processed in accordance with a method to determine signal integrity of the data signals of each network channel. For example, with reference to the system 200 shown in
In another example configuration, the local controller 206 can determine signal integrity of the first and second data signals by comparing the signal strengths and signal to noise ratios of the first and second data signals. Signal strength may refer to transmitter power output as received by a receiver, e.g., milliwatts (mW), received signal strength indicator (RSSI), or decibels in relation to a milliwatt (dBm). When a signal strength and signal to noise ratio of the first data signal is less than a signal strength and signal to noise ratio of the second data signal, the local controller 206 or main robotic controller 202 can determine that the first data signal is degraded.
As indicated above, in response to determining that the first data signal received over the primary network channel 208 is degraded, the local controller 206 or main robotic controller 202 can ignore or discard the first data signal and select the second data signal received over the secondary network channel 210. The local controller 206 can process the second data signal to obtain a command or instruction intended for the local controller 206 of the robotic component 204, and execute the command or instruction to cause the local controller 206 of the robotic component 204 to control the controlled component 214 to perform an action based on the command or instruction. If the main robotic controller 202 is receiving the data, the main robotic controller 202 can process the second data signal to obtain a command or instruction intended for the main robotic controller 202 of the robotic component 204, and execute the command or instruction to cause the main robotic controller 202 of the robotic component 204 to perform an action based on the command or instruction. That is, the local controller 206 and the main robotic controller 202 can each failover to the secondary network channel 210 to receive/send commands to prevent a shutdown of the robot 100 due to network degradation or failure in the primary network channel 208 that results in a communication fault. Thus, network redundancy is accomplished by monitoring the primary network channel 208 for communication faults and failing over to the secondary network channel 208 when signal degradation in the primary network channel 208 is detected, which can indicate a network failure in the primary network channel 208
In the case that a communication fault is detected, operation of the robot 100 can continue, a remedial measure can be taken (e.g., the robot can be caused to enter a safe operating mode, and/or an operator of the robot 100 can be notified, or others). For example, basic operations of the robot 100 (e.g., drive control, motion control, balance control, etc.) can be maintained via the redundancy provided by the secondary network channel 210 to allow the robot 100 to be placed in a safe position or operating state (e.g., a non-standing or a self-standing position) or to be safely returned to a service dock or station. In another example, if a communication fault associated with the primary network channel 208 is detected by the local controller 206, such as the one associated with the robotic component 204, the local controller 206 can notify the main robotic controller 202 of the communication fault, and the main robotic controller 202 can switch to a service mode that allows the robot 100 to minimally function and allows the robot 100 to get to a service station, if needed. Similarly, if a communication fault is detected by the main controller 202 the main controller 202 can switch to a service mode that allows the robot 100 to minimally function and allows the robot 100 to get to a service station if needed.
In one example configuration, communications sent over the redundant network communication system can be limited to communications related to basic operations of the robot 100. For example, in order to safeguard the robot 100 from experiencing an abnormal or an unsafe condition, the secondary network channel 210 can be reserved for commands and data associated with basic operations of the robot 100 (e.g., drive control, motion control, balance control, etc.). Non-basic or non-essential commands can be sent over the primary network channel 208. As an example, the main robotic controller 202 can duplicate data signals containing basic or essential commands for basic operation of the robot 100 and send the data signals in parallel over the primary and secondary network channels 208, 210 to the local controller 206. When received over the primary network channel 208, the local controller 206 can identify the data signals as containing basic or essential commands, for example, by inspecting the data packet for a basic or essential command indicator, and compare the data signal with the data signal received over the secondary network channel 210 to determine the signal integrity of the primary network channel 208. In the event that the controller 206 detects a communication fault associated with the primary network channel 208, the controller 206 can failover to the data signal received over the secondary network channel 210 to receive the basic or essential commands, thereby allowing the robot 100 to maintain basic operations and avoid an uncontrolled failure of the robot 100.
In one example, as described in greater detail in association with
Moreover, when a communication fault is detected, the local controller 106 can generate a system notification to indicate that a problem with one or both of the primary and secondary network channels 208, 210 has been detected. The system notification can provide a user with information that allows the user to return the robot 100 to a service location, or perform some other remedial action to avoid damage to the robot 100 and/or injury to the user and/or personnel in the surrounding area of the robot. For example, the system notification can specify the type of failure, robotic component(s) 204 affected by the failure, instructions for correcting the failure and/or bypassing the failure, etc. The system notification can be displayed on a display device of the robot 100 and/or user device, played on an audio output device of the robot 100 and/or user device, sent to a user device (e.g., application notification, SMS message, email, etc.), and the like.
In one example, after detecting a communication fault in the primary network channel 208 and switching to the secondary network channel 210 to transfer communications between the main robotic controller 202 and the local controller 206, the local controller 206 or the main robotic controller 202 can continue to monitor the primary network channel 208 to determine whether the primary network channel 208 recovers from the degradation or failure. For example, the local controller 206 and/or main robotic controller 202 can continue to self-monitor the primary network channel 208 and individually self-diagnose communication faults over the primary network channel 208 using checksum algorithms or other self-diagnostic or self-verification techniques described herein. In the event that the primary network channel 208 recovers from the degradation, the local controller 206 and/or the main robotic controller 202 can revert back to sending data signals over the primary network channel 208 for communicating between the local controller 206 and the main robotic controller 202. In one example, prior to reverting back to the primary network channel 208, the local controller 206 and/or main robotic controller 202 can continue to monitor the signal integrity of the primary network channel 208 for a period of time (e.g., 20 seconds, 60 seconds, 120 seconds, etc.), and then revert back to the primary channel 208 if signal integrity of the primary network channel 208 is maintained for the period of time.
Alternatively, or in addition to the self-diagnostics, in the event that a problem with the primary network channel 208 is temporary (e.g., temporary signal interference), the local controller 206 and/or main robotic controller 202 can continue to compare data signals received over both the network channels 208, 210 so as to detect whether the primary network channel 208 is restored to full performance. In the case that the local controller 206 and/or the main robotic controller 202 detects that the primary network channel 208 has recovered, the local controller 206 and/or the main robotic controller 202 can revert back to the primary network channel 208 for transferring communications between the main robotic controller 202 and the local controller 206. In one example, prior to reverting back to the primary network channel 208, the local controller 206 and/or the main robotic controller 202 can continue to monitor the signal integrity of the primary network channel 208 for a period of time (e.g., 20 seconds, 60 seconds, 120 seconds, etc.), and then revert back to the primary channel 208 if signal integrity of the primary network channel 208 is maintained for the period of time.
As in block 820, the local controller, in one example as associated with the robotic component, can receive the first data signal sent over the first network channel, and receive the second data signal sent over the second network channel (or any other data signals sent over additional network channels). In response to receiving the first and second data signals, the local controller can compare the first data signal with the second data signal to determine signal integrity associated with the first and second network channels, as in block 830. In one example, comparing the first and second data signals can comprise comparing a number of data packets received in each of the first and second data signals. In another example, comparing the first and second data signals can comprise comparing a signal strength and a signal to noise ratio of the first data signal to a signal strength and a signal to noise ratio of the second data signal.
As in block 840, in the case that degradation of the data signal received over the first network channel is not detected, then as in block 850, the first data signal can be processed to obtain the command encoded in the first data signal and the local controller can cause the controlled component of the robotic component to perform the command. However, in the case that degradation of the data signal received over the first network channel is detected, then as in block 860, the local controller can process the second data signal received over the second network channel to obtain the command encoded in the second data signal, and the local controller can cause the controlled component of the robotic component to perform the command. Namely, in either case, performing the command comprises the local controller executing instructions obtained from one of the data signals that actuate the controlled component of the robotic component in some way (or that cause the local controller to initiate another function or operation).
While the method 800 is described from a reference frame of data being created at the main robotic controller and sent to the local controller, it is to be understood that the main robotic controller and local controller support bi-directional communication. Therefore, the method 800 can also be utilized in similar fashion in a situation where data is sent from the local controller to the main robotic controller.
In one example configuration of a redundant network communication system for a robot, a third network channel can be used to provide additional network channel redundancy. For example, the main robotic controller can generate three duplicate data signals and send the third data signal over a third network channel in parallel with the sending of the first and second data signals over the first and second network channels. When received at the local controller, the third data signal can be compared to the first and second data signals to determine signal integrity degradation of any of the first, second, or third data signals. In one example, the first, second, and third network channels can be any combination of cable communication channels, power-line communication channels, and/or wireless communication channels.
Other methods of diagnosing communication faults can be carried out instead of or in addition to method 800.
As in block 920, the local controller (e.g., the second controller), in one example as associated with the robotic component, can receive the data signal sent over the primary network channel. In response to receiving the data signal, the local controller determine signal integrity associated with the primary network channel to see if any data signal degradation has occurred, as in block 930. In one example, the self-diagnostic features of the used to individually diagnose signal integrity on the primary network channel can be carried out using checksum algorithms and processes as error detection mechanisms for determining signal degradation. In other examples, the controller can use various mechanisms such as using Error Correction Code, parity checks, missed data packet detection, time-out mechanisms and algorithms, cyclic redundancy checks. For example, the controller can detect missed data packets over the network channel by observing that the controller does not receive the packet within a prescribed amount of time. These and any other methods known by those of ordinary skill in the art for detecting network channel issues and signal degradation can be used to self-diagnose network channel and signal health in a robotic network.
As in block 940, in the case that degradation of the data signal received over the primary network channel is not detected, the local controller can remain defaulted to receive network data signals over the primary network channel and can further move to the block 810 of the method 800 illustrated in
In block 950, in the case that degradation of the data signal received over the primary network channel is detected, then the local controller can stop receiving and/or considering the data signals received over the primary network channel. In order to obtain the command encoded in the data signal for operation of the controlled component of the robotic component to perform the command, the local controller can instead move to receive data signals sent over a redundant or secondary network channel to ensure reception of data signals by the local controller and proper operation of the robot continues. Namely, in either case, performing the command comprises the local controller executing instructions obtained from one of the data signals that actuate the controlled component of the robotic component in some way (or that cause the local controller to initiate another function or operation).
It is to be understood that individual diagnosing of network channels (e.g., method 900) and comparison diagnosing of network channels (e.g., method 800) can be performed in tandem with each other such that each network channel (e.g., primary, secondary, tertiary, and so on) are individually diagnosed as well as comparatively diagnosed for network communication faults. The comparative diagnosis of method 800 can catch network communication faults that can be missed by the individual diagnosis of method 900. It will be further appreciated that each of methods 800 and 900 can be performed separately from each other. In other words, a user may choose to only individually diagnose network channels as in method 900 without using any method for comparative data signal analysis. In such a case, the method 900 would not move on to method 800 after block 940 but would instead terminate or return to block 910 for continued diagnosis of network channels. Alternatively, a user can choose to only use comparative methods (e.g., method 800) of network channel diagnosis without individually diagnosing statuses of network channels.
While the method 900 is described from a reference frame of data being created at the main robotic controller and sent to the local controller, it is to be understood that the main robotic controller and local controller support bi-directional communication. Therefore, the method 900 can also be utilized in similar fashion in a situation where data is sent from the local controller to the main robotic controller.
In one example configuration of a redundant network communication system for a robot, a third network channel can be used to provide additional network channel redundancy. For example, the main robotic controller can individually diagnose a third network channel (as well as more additional network channels) in parallel with the first and second network channels. In one example, the first, second, and third network channels can be any combination of cable communication channels, power-line communication channels, and/or wireless communication channels.
As in block 1040, in the case that comparison of the data signals indicates signal degradation in the primary network channel, then as in block 1050, a system notification can be generated to indicate to a user that there is a problem with the primary network channel. The system notification can provide a user with information that allows the user to return the robot to a service location or perform some other action to avoid damage to the robot and/or injury to a user. Illustratively, the system notification can specify the type of failure, robotic component(s) affected by the failure, and/or instructions for correcting the failure and/or bypassing the failure, etc. The system notification can be displayed on a display device of the robot and/or user device, played on an audio output device of the robot and/or user device, sent to a user device (e.g., application notification, SMS message, email, etc.), and the like.
While the method 1000 is described from a reference frame of data being received at the local controller, it is to be understood that the main robotic controller and local controller support bi-directional communication. Therefore, the method 900 can also be utilized in similar fashion in a situation where data is received at the main robotic controller.
The memory 1120 can contain modules 1124 that are executable by the processor(s) 1112 and data for the modules 1124. In one example, the memory 1120 can contain a main robotic controller module, a robotic component controller module, data distribution module, power distribution module, and other modules. The modules 1124 can execute the functions described earlier. A data store 1122 can also be located in the memory 1120 for storing data related to the modules 1124 and other applications along with an operating system that is executable by the processor(s) 1112 and/or processors of the modules 1124, which comprise the local controllers, such as those associated with a robotic component.
Other applications can also be stored in the memory 1120 and can be executable by the processor(s) 1112. Components or modules discussed in this description can be implemented in the form of software using high-level programming languages that are compiled, interpreted or executed using a hybrid of the methods.
The computing device 1110 can also have access to I/O (input/output) devices 1114 that are usable by the computing device 1110. In one example, the computing device 1110 can have access to a display 1130 to allow output of system notifications. Networking devices 1116 and similar communication devices can be included in the computing device. The networking devices 1116 can be wired or wireless networking devices that connect to the internet, a LAN, WAN, or other computing network.
The components or modules that are shown as being stored in the memory device 1120 can be executed by the processor(s) 1112. The term “executable” can mean a program file that is in a form that can be executed by a processor 1112. For example, a program in a higher-level language can be compiled into machine code in a format that can be loaded into a random-access portion of the memory device 1120 and executed by the processor 1112, or source code can be loaded by another executable program and interpreted to generate instructions in a random-access portion of the memory to be executed by a processor. The executable program can be stored in any portion or component of the memory device 1120. For example, the memory device 1120 can be random access memory (RAM), read only memory (ROM), flash memory, a solid-state drive, memory card, a hard drive, optical disk, floppy disk, magnetic tape, or any other memory components.
The processor 1112 can represent multiple processors and the memory device 1120 can represent multiple memory units that operate in parallel to the processing circuits. This can provide parallel processing channels for the processes and data in the system. The local communication interface 1118 can be used as a network to facilitate communication between any of the multiple processors and multiple memories. The local communication interface 1118 can use additional systems designed for coordinating communication such as load balancing, bulk data transfer and similar systems.
While the flowcharts presented for this technology can imply a specific order of execution, the order of execution may differ from what is illustrated. For example, the order of two more blocks can be rearranged relative to the order shown. Further, two or more blocks shown in succession can be executed in parallel or with partial parallelization. In some configurations, one or more blocks shown in the flow chart may be omitted or skipped. Any number of counters, state variables, warning semaphores, or messages might be added to the logical flow for purposes of enhanced utility, accounting, performance, measurement, troubleshooting or for similar reasons.
Some of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules can also be implemented in software for execution by various types of processors. An identified module of executable code can, for instance, comprise one or more blocks of computer instructions, which can be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but can comprise disparate instructions stored in different locations which comprise the module and achieve the stated purpose for the module when joined logically together.
Indeed, a module of executable code can be a single instruction, or many instructions and can even be distributed over several different code segments, among different programs and across several memory devices. Similarly, operational data can be identified and illustrated herein within modules and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can be distributed over different locations including over different storage devices. The modules can be passive or active, including agents operable to perform desired functions.
The technology described here can also be stored on a computer readable storage medium that includes volatile and non-volatile, removable and non-removable media implemented with any technology for the storage of information such as computer readable instructions, data structures, program modules, or other data. Computer readable storage media include, but is not limited to, a non-transitory machine-readable storage medium, such as RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other computer storage medium which can be used to store the desired information and described technology.
The devices described herein can also contain communication connections or networking apparatus and networking connections that allow the devices to communicate with other devices. Communication connections are an example of communication media. Communication media typically embodies computer readable instructions, data structures, program modules and other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. A “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example and not limitation, communication media includes wired media such as a wired network or direct-wired connection and wireless media such as acoustic, radio frequency, infrared and other wireless media. The term computer readable media as used herein includes communication media.
Reference was made to the examples illustrated in the drawings and specific language was used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended. Alterations and further modifications of the features illustrated herein and additional applications of the examples as illustrated herein are to be considered within the scope of the description.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more examples. In the preceding description, numerous specific details were provided, such as examples of various configurations to provide a thorough understanding of examples of the described technology. It will be recognized, however, that the technology may be practiced without one or more of the specific details, or with other methods, components, devices, etc. In other instances, well-known structures or operations are not shown or described in detail to avoid obscuring aspects of the technology.
Although the subject matter has been described in language specific to structural features and/or operations, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features and operations described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. Numerous modifications and alternative arrangements may be devised without departing from the spirit and scope of the described technology.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1880138 | Franz | Sep 1932 | A |
| 2850189 | Leroy | Sep 1958 | A |
| 2981198 | Nettel | Apr 1961 | A |
| 3171549 | Orloff | Mar 1965 | A |
| 3280991 | Melton et al. | Oct 1966 | A |
| 3306646 | Flora, Jr. | Feb 1967 | A |
| 3358678 | Kulstar | Dec 1967 | A |
| 3449008 | Colechia | Jun 1969 | A |
| 3449769 | Mizen | Jun 1969 | A |
| 3535711 | Fick | Oct 1970 | A |
| 3759563 | Kitamura | Sep 1973 | A |
| 3858468 | Pasbrig | Jan 1975 | A |
| 4046262 | Vykukal et al. | Sep 1977 | A |
| 4179233 | Bromell et al. | Dec 1979 | A |
| 4200596 | Iiyama et al. | Apr 1980 | A |
| 4251791 | Yanagisawa et al. | Feb 1981 | A |
| 4367891 | Wauer et al. | Jan 1983 | A |
| 4398110 | Flinchbaugh et al. | Aug 1983 | A |
| 4483407 | Iwamoto et al. | Nov 1984 | A |
| 4561686 | Atchley | Dec 1985 | A |
| 4567417 | Francois et al. | Jan 1986 | A |
| 4575297 | Richter | Mar 1986 | A |
| 4591944 | Gravel | May 1986 | A |
| 4598601 | Molaug | Jul 1986 | A |
| 4603896 | Vasseur et al. | Aug 1986 | A |
| 4661032 | Arai | Apr 1987 | A |
| 4666357 | Babbi | May 1987 | A |
| 4723353 | Monforte | Feb 1988 | A |
| 4762455 | Coughlan et al. | Aug 1988 | A |
| 4768143 | Lane et al. | Aug 1988 | A |
| 4821594 | Rosheim et al. | Apr 1989 | A |
| 4834443 | Crowder et al. | May 1989 | A |
| 4853874 | Iwamoto et al. | Aug 1989 | A |
| 4883400 | Kuban et al. | Nov 1989 | A |
| 4884720 | Whigham et al. | Dec 1989 | A |
| 4915437 | Cherry | Apr 1990 | A |
| 4921292 | Harwell et al. | May 1990 | A |
| 4997095 | Jones et al. | Mar 1991 | A |
| 5004391 | Burdea | Apr 1991 | A |
| 5038089 | Szakaly | Aug 1991 | A |
| 5072361 | Davis et al. | Dec 1991 | A |
| 5080682 | Schectman | Jan 1992 | A |
| 5101472 | Repperger | Mar 1992 | A |
| 5105367 | Tsuchihashi et al. | Apr 1992 | A |
| 5117814 | Luttrell et al. | Jun 1992 | A |
| 5144943 | Luttrell et al. | Sep 1992 | A |
| 5172951 | Jacobsen et al. | Dec 1992 | A |
| 5230147 | Asaoka et al. | Jul 1993 | A |
| 5239246 | Kim | Aug 1993 | A |
| 5246216 | Oberst | Sep 1993 | A |
| 5280981 | Schulz | Jan 1994 | A |
| 5282460 | Boldt | Feb 1994 | A |
| 5328224 | Jacobsen et al. | Jul 1994 | A |
| 5336982 | Backes | Aug 1994 | A |
| 5389849 | Asano et al. | Feb 1995 | A |
| 5399951 | Lavallee et al. | Mar 1995 | A |
| 5402690 | Sekiguchi et al. | Apr 1995 | A |
| 5516249 | Brimhall | May 1996 | A |
| 5577417 | Fournier | Nov 1996 | A |
| 5577902 | Todo et al. | Nov 1996 | A |
| 5588688 | Jacobsen et al. | Dec 1996 | A |
| 5664636 | Ikuma et al. | Sep 1997 | A |
| 5704945 | Wagner et al. | Jan 1998 | A |
| 5762390 | Gosselin et al. | Jun 1998 | A |
| 5784542 | Ohm et al. | Jul 1998 | A |
| 5785505 | Price | Jul 1998 | A |
| 5797615 | Murray | Aug 1998 | A |
| 5845540 | Rosheim | Dec 1998 | A |
| 5865770 | Schectman | Feb 1999 | A |
| 5898599 | Massie et al. | Apr 1999 | A |
| 5912658 | Bergamasco et al. | Jun 1999 | A |
| 5949686 | Yoshinada et al. | Sep 1999 | A |
| 5957981 | Gramnas | Sep 1999 | A |
| 5961476 | Betto et al. | Oct 1999 | A |
| 5967580 | Rosheim | Oct 1999 | A |
| 5994864 | Inoue et al. | Nov 1999 | A |
| 6016385 | Yee et al. | Jan 2000 | A |
| 6170162 | Jacobsen et al. | Jan 2001 | B1 |
| 6202013 | Anderson et al. | Mar 2001 | B1 |
| 6272924 | Jansen | Aug 2001 | B1 |
| 6301526 | Kim et al. | Oct 2001 | B1 |
| 6338605 | Halverson et al. | Jan 2002 | B1 |
| 6340065 | Harris | Jan 2002 | B1 |
| 6360166 | Alster | Mar 2002 | B1 |
| 6394731 | Konosu et al. | May 2002 | B1 |
| 6425865 | Salcudean et al. | Jul 2002 | B1 |
| 6430473 | Lee et al. | Aug 2002 | B1 |
| 6435794 | Springer | Aug 2002 | B1 |
| 6507163 | Allen | Jan 2003 | B1 |
| 6508058 | Seaverson | Jan 2003 | B1 |
| 6554342 | Burnett | Apr 2003 | B1 |
| 6641371 | Graziani et al. | Nov 2003 | B2 |
| 6659703 | Kirkley | Dec 2003 | B1 |
| 6659939 | Moll et al. | Dec 2003 | B2 |
| 6663154 | Pancheri | Dec 2003 | B2 |
| 6714839 | Salisbury, Jr. et al. | Mar 2004 | B2 |
| 6740125 | Mosler | May 2004 | B2 |
| 6855170 | Gramnas | Feb 2005 | B2 |
| 6920374 | Takenaka et al. | Jul 2005 | B2 |
| 7168748 | Townsend et al. | Jan 2007 | B2 |
| 7319919 | Takenaka et al. | Jan 2008 | B2 |
| 7337040 | Takenaka et al. | Feb 2008 | B2 |
| 7379789 | Takenaka et al. | May 2008 | B2 |
| 7396057 | Ye et al. | Jul 2008 | B2 |
| 7405531 | Khatib et al. | Jul 2008 | B2 |
| 7409882 | Massimo et al. | Aug 2008 | B2 |
| 7410338 | Schiele et al. | Aug 2008 | B2 |
| 7509905 | Jacobsen et al. | Mar 2009 | B2 |
| 7628766 | Kazerooni et al. | Dec 2009 | B1 |
| 7783384 | Kraft | Aug 2010 | B2 |
| 7862522 | Barclay et al. | Jan 2011 | B1 |
| 7862524 | Carignan et al. | Jan 2011 | B2 |
| 7883546 | Kazerooni et al. | Feb 2011 | B2 |
| 7947004 | Kazerooni et al. | May 2011 | B2 |
| 7965006 | Kang et al. | Jun 2011 | B2 |
| 8024071 | Komatsu et al. | Sep 2011 | B2 |
| 8051764 | Jacobsen et al. | Nov 2011 | B2 |
| 8100451 | Okuda et al. | Jan 2012 | B2 |
| 8112179 | Nakajima | Feb 2012 | B2 |
| 8132835 | Ban et al. | Mar 2012 | B2 |
| 8151401 | Cheyne | Apr 2012 | B2 |
| 8182010 | Lee et al. | May 2012 | B2 |
| 8204626 | Yoshiike et al. | Jun 2012 | B2 |
| 8245728 | Jacobsen et al. | Aug 2012 | B2 |
| 8295975 | Arimatsu et al. | Oct 2012 | B2 |
| 8336420 | Carter et al. | Dec 2012 | B2 |
| 8375982 | Gray, Jr. | Feb 2013 | B2 |
| 8435309 | Gilbert et al. | May 2013 | B2 |
| 8452447 | Nixon | May 2013 | B2 |
| 8473101 | Summer | Jun 2013 | B2 |
| 8511192 | Hirtt et al. | Aug 2013 | B2 |
| 8516918 | Jacobsen et al. | Aug 2013 | B2 |
| 8529582 | Devengenzo et al. | Sep 2013 | B2 |
| 8534728 | Bosscher et al. | Sep 2013 | B1 |
| 8560118 | Greer et al. | Oct 2013 | B2 |
| 8640723 | Jacobsen et al. | Feb 2014 | B2 |
| 8667643 | Simonelli et al. | Mar 2014 | B2 |
| 8672378 | Yamasaki et al. | Mar 2014 | B2 |
| 8747486 | Kawasaki et al. | Jun 2014 | B2 |
| 8794262 | Jacobsen et al. | Aug 2014 | B2 |
| 8821338 | Thorson | Sep 2014 | B2 |
| 8849457 | Jacobsen et al. | Sep 2014 | B2 |
| 8870967 | Herr et al. | Oct 2014 | B2 |
| 8881616 | Dize et al. | Nov 2014 | B2 |
| 8888864 | Iversen et al. | Nov 2014 | B2 |
| 8892258 | Jacobsen et al. | Nov 2014 | B2 |
| 8920517 | Smith et al. | Dec 2014 | B2 |
| 8942846 | Jacobsen et al. | Jan 2015 | B2 |
| 8977388 | Jacobsen et al. | Mar 2015 | B2 |
| 8977398 | Jacobsen et al. | Mar 2015 | B2 |
| 9079305 | Williamson et al. | Jul 2015 | B2 |
| 9205560 | Edsinger et al. | Dec 2015 | B1 |
| 9295604 | Zoss et al. | Mar 2016 | B2 |
| 9314921 | Jacobsen et al. | Apr 2016 | B2 |
| 9329587 | Fudaba et al. | May 2016 | B2 |
| 9333097 | Herr et al. | May 2016 | B2 |
| 9346165 | Metzger et al. | May 2016 | B1 |
| 9446510 | Vu et al. | Sep 2016 | B2 |
| 9526636 | Bedard et al. | Dec 2016 | B2 |
| 9533411 | Jacobsen et al. | Jan 2017 | B2 |
| 9616580 | Smith et al. | Apr 2017 | B2 |
| 9618937 | Blankespoor et al. | Apr 2017 | B1 |
| 9643323 | Nagatsuka et al. | May 2017 | B2 |
| 9727076 | Smith et al. | Aug 2017 | B2 |
| 9789603 | Jacobsen et al. | Oct 2017 | B2 |
| 9862090 | Kennedy et al. | Jan 2018 | B2 |
| 9895812 | Gonzalez et al. | Feb 2018 | B2 |
| 9926025 | Blankespoor et al. | Mar 2018 | B1 |
| 10028844 | Cheng et al. | Jul 2018 | B2 |
| 10071485 | Schiele et al. | Sep 2018 | B2 |
| 10216177 | Gildert et al. | Feb 2019 | B2 |
| 10300969 | Blackespoor et al. | May 2019 | B1 |
| 10406676 | Smith et al. | Sep 2019 | B2 |
| 10512583 | Smith | Dec 2019 | B2 |
| 10518404 | Barnes | Dec 2019 | B2 |
| 10533542 | Smith et al. | Jan 2020 | B2 |
| 10561564 | LaChappelle et al. | Feb 2020 | B2 |
| 10566914 | Fujita et al. | Feb 2020 | B2 |
| 10609896 | Kraaij et al. | Apr 2020 | B2 |
| 10709633 | Kazerooni et al. | Jul 2020 | B2 |
| 10765537 | Smith et al. | Sep 2020 | B2 |
| 10828767 | Smith et al. | Nov 2020 | B2 |
| 11148279 | Mooney et al. | Oct 2021 | B1 |
| 11241801 | Smith et al. | Feb 2022 | B2 |
| 20010033146 | Kato et al. | Oct 2001 | A1 |
| 20010043847 | Kramer | Nov 2001 | A1 |
| 20020075233 | White et al. | Jun 2002 | A1 |
| 20020094919 | Rennex et al. | Jul 2002 | A1 |
| 20030005896 | Jacobsen et al. | Jan 2003 | A1 |
| 20030060808 | Wilk | Mar 2003 | A1 |
| 20030146720 | Riwan et al. | Aug 2003 | A1 |
| 20030152452 | Hodgson | Aug 2003 | A1 |
| 20030223844 | Schiele et al. | Dec 2003 | A1 |
| 20040004362 | Love | Jan 2004 | A1 |
| 20040037681 | Marcotte | Feb 2004 | A1 |
| 20040102723 | Horst | May 2004 | A1 |
| 20040106881 | McBean et al. | Jun 2004 | A1 |
| 20040116836 | Kawai et al. | Jun 2004 | A1 |
| 20040246769 | Ido | Dec 2004 | A1 |
| 20040250644 | Gosselin et al. | Dec 2004 | A1 |
| 20050059908 | Bogert | Mar 2005 | A1 |
| 20050099386 | Kukita | May 2005 | A1 |
| 20050159850 | Melman | Jul 2005 | A1 |
| 20050166413 | Crampton | Aug 2005 | A1 |
| 20050193451 | Quistgaard et al. | Sep 2005 | A1 |
| 20050251110 | Nixon | Nov 2005 | A1 |
| 20060052732 | Shimada et al. | Mar 2006 | A1 |
| 20060064047 | Shimada et al. | Mar 2006 | A1 |
| 20060069449 | Bisbee, III et al. | Mar 2006 | A1 |
| 20060130594 | Ikeuchi | Jun 2006 | A1 |
| 20060149419 | Ogawa et al. | Jul 2006 | A1 |
| 20060184275 | Hosokawa et al. | Aug 2006 | A1 |
| 20060197049 | Hamada et al. | Sep 2006 | A1 |
| 20060245897 | Hariki et al. | Nov 2006 | A1 |
| 20060249315 | Herr et al. | Nov 2006 | A1 |
| 20070054777 | Kawai et al. | Mar 2007 | A1 |
| 20070056592 | Angold et al. | Mar 2007 | A1 |
| 20070105070 | Trawick | May 2007 | A1 |
| 20070123997 | Herr et al. | May 2007 | A1 |
| 20070129653 | Sugar et al. | Jun 2007 | A1 |
| 20080009771 | Perry et al. | Jan 2008 | A1 |
| 20080023974 | Park et al. | Jan 2008 | A1 |
| 20080156363 | Ikeuchi et al. | Jul 2008 | A1 |
| 20080269027 | Chen | Oct 2008 | A1 |
| 20080271942 | Yamashita et al. | Nov 2008 | A1 |
| 20080281468 | Jacobsen et al. | Nov 2008 | A1 |
| 20090036815 | Ido | Feb 2009 | A1 |
| 20090038258 | Pivac et al. | Feb 2009 | A1 |
| 20090039579 | Clifford et al. | Feb 2009 | A1 |
| 20090149993 | Neki et al. | Jun 2009 | A1 |
| 20090199883 | Hiki | Aug 2009 | A1 |
| 20090210093 | Jacobsen et al. | Aug 2009 | A1 |
| 20090294238 | Gilmore | Dec 2009 | A1 |
| 20100050947 | Kortekaas | Mar 2010 | A1 |
| 20100089855 | Kjolseth | Apr 2010 | A1 |
| 20100094185 | Amundson et al. | Apr 2010 | A1 |
| 20100152630 | Matsuoka et al. | Jun 2010 | A1 |
| 20100198402 | Greer et al. | Aug 2010 | A1 |
| 20100234996 | Schreiber et al. | Sep 2010 | A1 |
| 20100241242 | Herr et al. | Sep 2010 | A1 |
| 20100295497 | Takamatsu | Nov 2010 | A1 |
| 20110010012 | Murayama et al. | Jan 2011 | A1 |
| 20110015786 | Kawai | Jan 2011 | A1 |
| 20110040216 | Herr et al. | Feb 2011 | A1 |
| 20110046781 | Summer | Feb 2011 | A1 |
| 20110066088 | Little et al. | Mar 2011 | A1 |
| 20110071677 | Stillman | Mar 2011 | A1 |
| 20110214524 | Jacobsen et al. | Sep 2011 | A1 |
| 20110219899 | Dize et al. | Sep 2011 | A1 |
| 20110264230 | Herr et al. | Oct 2011 | A1 |
| 20120000891 | Nakanishi et al. | Jan 2012 | A1 |
| 20120060322 | Simonelli et al. | Mar 2012 | A1 |
| 20120065902 | Nakajima | Mar 2012 | A1 |
| 20120073930 | Lansberry et al. | Mar 2012 | A1 |
| 20120137667 | Jacobsen et al. | Jun 2012 | A1 |
| 20120179075 | Perry et al. | Jul 2012 | A1 |
| 20120191245 | Fudaba et al. | Jul 2012 | A1 |
| 20120216671 | Gammon | Aug 2012 | A1 |
| 20120237319 | Jacobsen et al. | Sep 2012 | A1 |
| 20120259429 | Han et al. | Oct 2012 | A1 |
| 20120277901 | Jacobsen et al. | Nov 2012 | A1 |
| 20120277911 | Jacobsen et al. | Nov 2012 | A1 |
| 20120277915 | Jacobsen et al. | Nov 2012 | A1 |
| 20120328395 | Jacobsen et al. | Dec 2012 | A1 |
| 20130011220 | Jacobsen et al. | Jan 2013 | A1 |
| 20130013108 | Jacobsen et al. | Jan 2013 | A1 |
| 20130023803 | Hsu et al. | Jan 2013 | A1 |
| 20130033050 | Matsuoka et al. | Feb 2013 | A1 |
| 20130057001 | Tsai | Mar 2013 | A1 |
| 20130090580 | Hong et al. | Apr 2013 | A1 |
| 20130106127 | Lipson et al. | May 2013 | A1 |
| 20130106128 | Yamasaki et al. | May 2013 | A1 |
| 20130192406 | Godowski | Aug 2013 | A1 |
| 20130226048 | Unluhisarcikili et al. | Aug 2013 | A1 |
| 20130253385 | Goffer et al. | Sep 2013 | A1 |
| 20130296746 | Herr et al. | Nov 2013 | A1 |
| 20130302129 | Smith et al. | Nov 2013 | A1 |
| 20130306430 | Laffranchi et al. | Nov 2013 | A1 |
| 20130331744 | Kamon | Dec 2013 | A1 |
| 20130333368 | Durfee et al. | Dec 2013 | A1 |
| 20140067124 | Williamson et al. | Mar 2014 | A1 |
| 20140088728 | Herr | Mar 2014 | A1 |
| 20140100492 | Nagasaka | Apr 2014 | A1 |
| 20140190289 | Zhu | Jul 2014 | A1 |
| 20140195052 | Tsusaka et al. | Jul 2014 | A1 |
| 20150073595 | Fudaba et al. | Mar 2015 | A1 |
| 20150073596 | Fudaba et al. | Mar 2015 | A1 |
| 20150173929 | Kazerooni et al. | Jun 2015 | A1 |
| 20150209214 | Herr et al. | Jul 2015 | A1 |
| 20150217457 | Lipson et al. | Aug 2015 | A1 |
| 20150272749 | Amend, Jr. et al. | Oct 2015 | A1 |
| 20150278263 | Bowles et al. | Oct 2015 | A1 |
| 20150289995 | Wilkinson et al. | Oct 2015 | A1 |
| 20150321340 | Smith | Nov 2015 | A1 |
| 20150321342 | Smith et al. | Nov 2015 | A1 |
| 20160003268 | Shevchenko et al. | Jan 2016 | A1 |
| 20160114482 | Lessing et al. | Apr 2016 | A1 |
| 20160153508 | Battlogg | Jun 2016 | A1 |
| 20160279788 | Kanaoka et al. | Sep 2016 | A1 |
| 20160279793 | Sisbot | Sep 2016 | A1 |
| 20160331556 | Wijesundara et al. | Nov 2016 | A1 |
| 20160331572 | Popovic et al. | Nov 2016 | A1 |
| 20160332302 | Bingham et al. | Nov 2016 | A1 |
| 20160332305 | Gonzalez et al. | Nov 2016 | A1 |
| 20160332312 | Song et al. | Nov 2016 | A1 |
| 20170050310 | Kanaoka | Feb 2017 | A1 |
| 20170119132 | Pruess et al. | May 2017 | A1 |
| 20170326737 | Martin et al. | Nov 2017 | A1 |
| 20180126548 | Sugito et al. | May 2018 | A1 |
| 20180133905 | Smith et al. | May 2018 | A1 |
| 20180133906 | Smith et al. | May 2018 | A1 |
| 20180193172 | Smith et al. | Jul 2018 | A1 |
| 20180193999 | Jacobsen et al. | Jul 2018 | A1 |
| 20180194000 | Smith et al. | Jul 2018 | A1 |
| 20180221237 | Swift et al. | Aug 2018 | A1 |
| 20180290309 | Becker et al. | Oct 2018 | A1 |
| 20180298976 | Battlogg | Oct 2018 | A1 |
| 20190022853 | Kim et al. | Jan 2019 | A1 |
| 20190105777 | Dalley et al. | Apr 2019 | A1 |
| 20190138423 | Agerstam et al. | May 2019 | A1 |
| 20190176320 | Smith et al. | Jun 2019 | A1 |
| 20190184576 | Smith et al. | Jun 2019 | A1 |
| 20200001450 | Smith et al. | Jan 2020 | A1 |
| 20200164523 | Hallock et al. | May 2020 | A1 |
| 20200281803 | Teng et al. | Sep 2020 | A1 |
| 20200312109 | Shionozaki | Oct 2020 | A1 |
| 20200346009 | Murray et al. | Nov 2020 | A1 |
| 20200368094 | Yoshimi et al. | Nov 2020 | A1 |
| 20200405417 | Shelton, IV et al. | Dec 2020 | A1 |
| 20210023693 | Berger et al. | Jan 2021 | A1 |
| 20210039269 | Son | Feb 2021 | A1 |
| 20210059780 | Sutherland et al. | Mar 2021 | A1 |
| 20210369536 | Mooney et al. | Dec 2021 | A1 |
| 20210378903 | Mooney et al. | Dec 2021 | A1 |
| 20230023083 | Shelton, IV | Jan 2023 | A1 |
| 20230165649 | Fitzsimons et al. | Jun 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 101214653 | Jul 2008 | CN |
| 101823517 | Sep 2010 | CN |
| 101486191 | Nov 2012 | CN |
| 103610524 | Mar 2014 | CN |
| 203495949 | Mar 2014 | CN |
| 103802907 | May 2014 | CN |
| 203752160 | Aug 2014 | CN |
| 104843484 | Aug 2015 | CN |
| 105411813 | Mar 2016 | CN |
| 205250544 | May 2016 | CN |
| 105818143 | Aug 2016 | CN |
| 105856190 | Aug 2016 | CN |
| 107471203 | Dec 2017 | CN |
| 108081303 | May 2018 | CN |
| 111267992 | Jun 2020 | CN |
| 111616914 | Sep 2020 | CN |
| 102004029513 | Sep 2005 | DE |
| 102010029088 | Nov 2011 | DE |
| 202013009698 | Nov 2013 | DE |
| 102016201540 | Aug 2017 | DE |
| 202018104980 | Sep 2018 | DE |
| 0039578 | Nov 1981 | EP |
| 0616275 | Sep 1998 | EP |
| 1037264 | Sep 2000 | EP |
| 1258324 | Nov 2002 | EP |
| 1442846 | Aug 2004 | EP |
| 1721593 | Nov 2006 | EP |
| 2198810 | Jun 2010 | EP |
| 2548543 | Jan 2015 | EP |
| 2942162 | Nov 2015 | EP |
| 2168548 | Oct 2016 | EP |
| 2651220 | Mar 1991 | FR |
| 686237 | Jan 1953 | GB |
| 2278041 | Nov 1994 | GB |
| S34-015764 | Oct 1959 | JP |
| S36-005228 | May 1961 | JP |
| S44-000603 | Jan 1969 | JP |
| S50-009803 | Jan 1975 | JP |
| S50-006043 | Mar 1975 | JP |
| S52-013252 | Feb 1977 | JP |
| S52-134985 | Nov 1977 | JP |
| S56-140510 | Nov 1981 | JP |
| S58-113586 | Jul 1983 | JP |
| S58-45724 | Oct 1983 | JP |
| S60-177883 | Nov 1985 | JP |
| S62-193784 | Aug 1987 | JP |
| S62-200600 | Sep 1987 | JP |
| H01-295772 | Nov 1989 | JP |
| H02-51083 | Apr 1990 | JP |
| H03-85398 | Aug 1991 | JP |
| H04-44296 | Apr 1992 | JP |
| H05-004177 | Jan 1993 | JP |
| H05-023989 | Feb 1993 | JP |
| H06-213266 | Aug 1994 | JP |
| H06-315879 | Nov 1994 | JP |
| H07-001366 | Jan 1995 | JP |
| H07-5129 | Feb 1995 | JP |
| H07-060679 | Mar 1995 | JP |
| H07-112377 | May 1995 | JP |
| H07-031291 | Jun 1995 | JP |
| H07-246578 | Sep 1995 | JP |
| H08-126984 | May 1996 | JP |
| H09-11176 | Jan 1997 | JP |
| H1156931 | Mar 1999 | JP |
| H11-130279 | May 1999 | JP |
| 2002-161547 | Jun 2002 | JP |
| 2003-103480 | Apr 2003 | JP |
| 2003-146575 | May 2003 | JP |
| 2003-194104 | Jul 2003 | JP |
| 2004-041279 | Feb 2004 | JP |
| 2004-105261 | Apr 2004 | JP |
| 2004-195576 | Jul 2004 | JP |
| 2005-118938 | May 2005 | JP |
| 2005-237504 | Sep 2005 | JP |
| 2005-334999 | Dec 2005 | JP |
| 2006-007337 | Jan 2006 | JP |
| 2006-016916 | Jan 2006 | JP |
| 2006-028953 | Feb 2006 | JP |
| 2006-051558 | Feb 2006 | JP |
| 2006-167223 | Jun 2006 | JP |
| 3909770 | Apr 2007 | JP |
| 2007-130234 | May 2007 | JP |
| 2007-252514 | Oct 2007 | JP |
| 2007-307216 | Nov 2007 | JP |
| 2008-143449 | Jun 2008 | JP |
| 2009-023828 | Feb 2009 | JP |
| 2009-167673 | Jul 2009 | JP |
| 2009-178253 | Aug 2009 | JP |
| 2009-219650 | Oct 2009 | JP |
| 2009-240488 | Oct 2009 | JP |
| 2009-268839 | Nov 2009 | JP |
| 2010-098130 | Apr 2010 | JP |
| 2010-110381 | May 2010 | JP |
| 2010-110465 | May 2010 | JP |
| 2010-142351 | Jul 2010 | JP |
| 2010-263761 | Nov 2010 | JP |
| 2011-067941 | Apr 2011 | JP |
| 2011-156171 | Aug 2011 | JP |
| 2011-193899 | Oct 2011 | JP |
| 2011-230260 | Nov 2011 | JP |
| 2012-501739 | Jan 2012 | JP |
| 2012-125279 | Jul 2012 | JP |
| 2012-176476 | Sep 2012 | JP |
| 2013-022091 | Feb 2013 | JP |
| 2013-090693 | May 2013 | JP |
| 2013-123786 | Jun 2013 | JP |
| 2013-142445 | Jul 2013 | JP |
| 5267730 | Aug 2013 | JP |
| 2013-208293 | Oct 2013 | JP |
| 2013-220496 | Oct 2013 | JP |
| 2013-248699 | Dec 2013 | JP |
| 2014-054273 | Mar 2014 | JP |
| 2014-073199 | Apr 2014 | JP |
| 2014-073222 | Apr 2014 | JP |
| 2014-200853 | Oct 2014 | JP |
| 2015-112649 | Jun 2015 | JP |
| 2015-212010 | Nov 2015 | JP |
| 2015-214019 | Dec 2015 | JP |
| 2016-539017 | Dec 2016 | JP |
| 2018-167375 | Nov 2018 | JP |
| 2020-037164 | Mar 2020 | JP |
| 6748374 | Sep 2020 | JP |
| 2005-0037754 | Apr 2005 | KR |
| 2007-0057209 | Jun 2007 | KR |
| 2010-0112670 | Oct 2010 | KR |
| 2012-0105194 | Sep 2012 | KR |
| 10-1219795 | Jan 2013 | KR |
| 2013-0001409 | Jan 2013 | KR |
| 2013-0045777 | May 2013 | KR |
| 2018-0128731 | Dec 2018 | KR |
| 2019-0108386 | Sep 2019 | KR |
| 515372 | Jul 2001 | SE |
| WO 9429605 | Dec 1994 | WO |
| WO 2003002309 | Jan 2003 | WO |
| WO 2003081762 | Oct 2003 | WO |
| WO 2007144629 | Dec 2007 | WO |
| WO 2009143377 | Nov 2009 | WO |
| WO 2010025409 | Mar 2010 | WO |
| WO 2010027968 | Mar 2010 | WO |
| WO 2012042471 | Apr 2012 | WO |
| WO 2016049622 | Mar 2016 | WO |
| WO 2017148499 | Sep 2017 | WO |
| WO 2017159504 | Sep 2017 | WO |
| WO 2018118004 | Jun 2018 | WO |
| WO 2018211869 | Nov 2018 | WO |
| WO 2018215705 | Nov 2018 | WO |
| WO 2019060791 | Mar 2019 | WO |
| WO 2020175949 | Sep 2020 | WO |
| Entry |
|---|
| Aghili et al., Sensing the torque in a robot's joints, www.memagazine.org/backissues/september98/features/torque/torque.html, 1998, pp. 1-9, The American Society of Mechanical Engineers. |
| Albu-Schaffer et al., A Unified Passivity Based Control Framework for Position, Torque and Impedance Control of Flexible Joint Robots, Institute of Robotics and Mechatronics, 2007, vol. 26, 17 pages, Germany. |
| Aliens (Movie), Starring Sigourney Weaver, Directed by James Cameron, Written by James Cameron, David Giler, Walter Hill, Dan O'Bannon, and Ronald Shuset, Released 1985 by Twentieth Century Fox, Scenes at Playtime 88:26:31-00:26:59 & 00:27:40-00:28:05 & 02:08:25-02:10:39 Non-Patent Literature documentation; Aliens(1986)—IMDb; downloaded Sep. 27, 2014; 4 pages; http://www.imdb.com/title/tt10090605/. |
| Amikabir University of Technology, Manipulator Dynamics (Power Point), Computer Engineering and Information Technology Department, to the best of applicant's knowledge article was available before the application filing date, 44 pages. |
| Bao et al., A unified modeling and control design for precision transmission system with friction and backlash, Advances in Mechanical Engineering, 2016, vol. 8(5), 11 pages. |
| Barras, Stabilization of a Biped Robot with its arms—A Practical Approach, http://biorob.epfl.ch/files/content/sites/biorob/filed/users/170220/public/Report.pdf; May 2010, 33 pages, EPFL Biorobotics Laboratory (BioRob), Switzerland. |
| Bauman, Utah Firm Markets on Big Gorilla of an Arm, Deseret News; Jan. 27, 1993, 2 pages, Deseret News Publishing Company, Salt Lake City, Utah. |
| Claeyssen et al., Magnetostrictive actuators compared to piezoelectric actuators, Proceedings of SPIE—The International Society for Optical Engineering 4763, Mar. 2003, 6 pages. |
| David et al., Study of an External Passive Shock-absorbing Mechanism for Walking Robots, 8th IEEE International Conference on Humanoid Robots, Dec. 1-3, 2008, pp. 435-440, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Desai et al., Robust Swing Leg Placement under Leg Disturbances, 2012 IEEE International Conference on Robotics and Biomimetics, Dec. 11-14, 2012, pp. 265-270, China. |
| Digital World Tokyo, Giant Robot Grabbing Hands Grab All They Can, www.digitalworldtokyo.com/index.php/digital_tokyo/articles/giant_robot_grabbing_hands_grab_all_they_can/, Jul. 17, 2007, 3 pages. |
| Elliott et al., The Biomechanics and Energetics of Human Running using an Elastic Knee Exoskeleton, Jun. 2013, 7 pages, IEEE International Conference on Rehabilitation Robotics, Seattle, Washington. |
| Elliott et al., Design of a Clutch-Spring Knee Exoskeleton for Running, Journal of Medical Devices, Sep. 2014, 11 pages, vol. 8, The American Society of Mechanical Engineers, New York City, New York. |
| Endo et al., A quasi-passive model of human leg function in level-ground walking, 2006 IEEE/RSJ International Conference on Intelligent Robots and Systems, Oct. 9-15, 2006, pp. 4935-4939, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Filippeschi et al., Survey of Motion Tracking Methods on Inertial Sensors: A Focus on Upper Limb Human Motion, www.mdpi.com/journal/sensors, 2017, 40 pages, Sensors, Switzerland. |
| Gauthier et al., Magnetic Shape Memory Alloy and Actuator Design, Conference: 5th International Workshop on Microfactories (IWMF'06), Oct. 2006, 5 pages, Besançon, France. |
| Grabowski et al., Exoskeletons for Running and Hopping Augmentation, Journal of Applied Physiology, http://biomech.media.mit.edu/portfolio_page/load-bearing-exoskeleton-for-augmentation-of-human-running/, 2009, 4 pages, vol. 107, No. 3, American Physiological Society, United States. |
| Hauser et al., JammJoint: A Variable Stiffness Device Based on Granular Jamming for Wearable Joint Support, IEEE Robotics and Automation Letters, Apr. 2017, 7 pages, vol. 2, Issue 2, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Huber et al., The selection of mechanical actuators based on performance indices, Oct. 8, 1997, pp. 2185-2205, vol. 453 Issue 1965, The Royal Society, London. |
| Hunter et al., Fast Reversible NiTi Fibers For Use In Microrobotics, Proceedings. IEEE Micro Electro Mechanical Systems, Jan. 30-Feb. 2, 1991, pp. 166-170, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Industrial Magnetics, Inc., PowerLift® Magnets; www.magnetics.com/product.asp?ProductID=1; as accessed Nov. 6, 2012, 2 pages; Boyne City, Michigan. |
| Jacobsen et al., Design of the Utah/M.I.T. Dextrous Hand, IEEE International Conference on Robotics and Automation, 1986, pp. 1520-1532, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Jacobsen et al., Development of the Utah Artificial Arm, IEEE Transactions on Biomedical Engineering, Apr. 1982, pp. 249-269, vol. BME-29, No. 4, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Jacobsen et al., Research Robots for Application in AI, Teleoperation and Entertainment, Proceedings of the International Fluid Power Exposition and Technical Conference, Mar. 24-24, 1992, pp. 1-19, Chicago, Illinois. |
| Jacobsen et al., Research Robots for Applications in Artificial Intelligence, Teleoperation and Entertainment; The International Journal of Robotics Research; Apr.-May 2004, pp. 319-330, vol. 23, No. 4-5, Sage Publications, Thousand Oaks, California. |
| Jacobsen, Science, Robotics, and Superheroes, Presented at Department of Science University of Utah Science at Breakfast, Mar. 17, 2010, 16 pages. |
| Jafari et al., A Novel Actuator with Adjustable Stiffness (AwAS), Oct. 18-22, 2010, 6 pages, IEEE/RSJ International Conference on Intelligent Robots and Systems, Taiwan. |
| Jansen et al., Exoskeleton for Soldier Enhancement Systems Feasibility Study, Sep. 2000, 44 pages, Oak Ridge National Laboratory, Oak Ridge, Tennessee. |
| Kaslin et al., Towards a Passive Adaptive Planar Foot with Ground Orientation and Contact Force Sensing for Legged Robots, IEEE International Conference on Intelligent Robots and Systems, Oct. 1-5, 2018, pp. 2707-2714, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Kazerooni, Berkeley Lower Extremity Exoskeleton (BLEEX), to the best of applicant's knowledge article was available before the application filing date, 3 pages, University of California, Berkeley, Berkeley, California. |
| Kim, Development of a small 6-axis force/moment sensor for robot's fingers, Measurement Science and Technology, Sep. 30, 2004, 2 pages, Issue 11, Institute of Physics and IOP Publishing Limited. |
| Kim et al, A Force Reflected Exoskeleton-Type Masterarm for Human-Robot Interaction, IEEE Transactions on Systems, Man and Cybertentics—Part A: Systems and Humans, Mar. 2005, pp. 198-212, vol. 35, No. 2, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Kulick, An Unpowered Exoskeleton Springs Into Action: Researchers Increase Walking Efficiency, http://www.cmu.edu/me/news/archive/2015/collins-clutch.html, Apr. 1, 2015, 2 pages, Carnegie Mellon University Mechanical Engineering, Pittsburgh, Pennsylvania. |
| Laliberte et al., Underactuation in Space Robotic Hands, Proceeding of the 6th International Symposium on Artificial Intelligence and Robotics & Automation in Space, Jun. 18-22, 2001, 8 pages, Canadian Space Agency, Canada. |
| Liu et al., Cat-inspired Mechanical Design of Self-Adaptive Toes for a Legged Robot, IEEE International Conference on Intelligent Robots and Systems, Oct. 9-14, 2016, pp. 2425-2430, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Liu et al., Concept and Design of a Lightweight Biped Robot for Walking on Rough Terrain, IEEE International Conference on Robotics and Biomimetics, 2017, 6 pages, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Magnetic Base, www.ask.com/wiki/magnetic base; page last updated Sep. 12, 2012, 2 pages, retrieved from www.ask.com/wiki/magnetic_base. |
| Miao et al., Mechanical Design of Hybrid Leg Exoskeleton to Augment Load-Carrying for Walking, International Journal of Advanced Robotic Systems, Mar. 28, 2013, 11 pages, vol. 10, Intech open science open minds, Europe. |
| Mirfakhrai et al., Polymer artificial muscles, materialstoday, Apr. 2007, pp. 30-38, vol. 10 No. 4, Elsevier, Netherlands. |
| Mombaur et al., HEiKA-EXO: Optimization-based development and control of an exoskeleton for medical applications, http://typo.iwr.uni-heidelberg.de/groups/orb/research/heika-exo/, Optimization in Robotics & Biomechanics, Oct. 20, 2014, 3 pages, Germany. |
| Moosavian et al., Dynamics Modeling and Tip-Over Stability of Suspended Wheeled Mobile Robots with Multiple Arms, 2007 IEEE/RSJ International Conference on Intelligent Robots and Systems, Oct. 29-Nov. 2, 2007; pp. 1210-1215, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Newport Corporation, Heavy-Duty Magnetic Base, 300 lb (1334 N) Holding Force, ¼-20 Thread, http://search.newport.com/?q=*&x2=sku&q2=200, as accessed Apr. 23, 2011, 1 page, Irvine, CA. |
| Oak Ridge National Laboratory, Foot Force-Torque Sensor Novel Sensor for Measuring Forces and Torques at the Foot, www.ornl.gov, to the best of applicant's knowledge article was available before the application filing date, 1 page, Oak Ridge National Laboratory, Oak Ridge, Tennessee. |
| Omega, Load Cell Designs, www.omega.com/literature/transactions/volume3/load3.html, Nov. 1, 2005, 3 pages. |
| Ostling, Wearable Robots, Technology Review, Jul./Aug. 2004, pp. 70-73, Elizabeth Bramson-Boudreau, Cambridge, Massachusetts. |
| Ott et al., Admittance Control using a Base Force/Torque Sensor, Department of Mechano-Informatics, 2009, 6 pages, University of Tokyo, Japan. |
| Pan, Improved Design of a Three-degree of Freedom Hip Exoskeleton Based on Biomimetic Parallel Structure, Jul. 2011, 132 pages, University of Ontario Institute of Technology, Canada. |
| Pelrine et al., Electrostriction of polymer dielectrics with compliant electrodes as a means of actuation, Sensors and Actuators A: Physical, Jan. 1998, pp. 77-85, vol. 64 Issue 1, Elsevier, Netherlands. |
| Pelrine et al., High-field deformation of elastomeric dielectrics for actuators, Materials Science and Engineering, Nov. 28, 2000, pp. 89-100, vol. 11 Issue 2, Elsevier, Netherlands. |
| Pelrine et al., Dielectric Elastomer Artificial Muscle Actuators: Toward Biomimetic Motion, Proceedings of SPIE—The International Society for Optical Engineering, Jul. 2002, pp. 126-137, vol. 4695, SPIE, Bellingham, WA. |
| Pin, Wearable Robotics Presented to New Horizons in Science Briefing, Oct. 2003, 34 pages, Knoxville, Tennessee. |
| Pratt et al., The RoboKnee: An Exoskeleton for Enhancing Strength and Endurance During Walking, International Conference on Robotics & Automation, Apr. 2004, 6 pages, IEEE, New Orleans, LA. |
| Robotics Research Group, Degrees of Freedom, www.robotics.utexas.edu/rrg/learn_more/low_ed/dof/, Oct. 25, 2006, 2 pages, University of Texas. |
| Roetenberg et al., Xsens MVN: Full 6DOF Human Motion Tracking Using Miniature Inertial Sensors, XSENS—Inertial Motion Capture, Jan. 2009, 9 pages, XSENS Technologies. |
| Rouse et al., Clutchable Series—Elastic Actuator: Design of a Robotic Knee Prosthesis for Minimum Energy Consumption, 2013 IEEE 13th International Conference on Rehabilitation Robotics (ICORR), Jun. 24-26, 2013, 6 pages, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Schuler et al., Dextrous Robot Arm, In Proceedings of the 8th ESA Workshop on Advanced Space Technologies for Robotic and Automation ‘ASTRA 2004’ ESTEC, Nov. 2-4, 2004, 8 pages, Noordwijk, The Netherlands. |
| Searchmap Blog, Scientists Develop Mechanical Spring-Loaded Leg Brace to Improve Walking, http://www.searchmap.en/blog/scientists-develop-mechanical-spring-loaded-leg-brace-to-improve-walking/, Apr. 1, 2015, 5 pages, Searchmap Blog. |
| Seppala, These exoskeleton heels could help stroke victims walk again, https://www.engadger.com/2015/04/02/feet-exoskeletons/, Apr. 2, 2015, Engadget, San Francisco, California. |
| Shamaei et al., Estimation of Quasi-Stiffness of the Human Knee in the Stance Phase of Walking, Mar. 22, 2013, 10 pages, vol. 8 Issue 3, PLOS One, San Francisco, California. |
| Siddharth et al., Design and Analysis of a 1-DOF Walking Mechanism, http://siddharthswaminathan.in/files/WalkingMechanism.pdf , Nov. 2012, 7 pages, India. |
| Smith et al., Integrated thin-film piezoelectric traveling wave ultrasonic motors, Sensors and Actuators A: Physical, Dec. 2012, pp. 305-311, vol. 188, Elsevier, Netherlands. |
| Song et al, Kinematics Analysis and Implementation of a Motion-Following Task for a Humanoid Slave Robot Controlled by an Exoskeleton Master Robot, International Journal of Control, Automation and Systems, Dec. 2007, pp. 681-690, vol. 5, No. 6, Korean Institute of Electrical Engineers, South Korea. |
| Suitx, Phoenix Medical Exoskeleton, https://www.suitx.com/phoenix-medical-exoskeleton, 3 pages, to the best of the applicant's knowledge article was available before the application filing date, US Bionics, Inc., Berkeley, California. |
| Suleiman, Engineering an affordable exoskeleton, Phys.org, https://phys.org/news/2014-06-exoskeleton.html, Jun. 12, 2014, 5 pages, Science X Network. |
| Szczesna et al., Inertial Motion Capture Costume Design Study, 2017, 21 pages, Sensors, Switzerland. |
| Tmsuk, Rescue Robot “T-53” release Control Technologies to Control the Synchronous Operation of the Arm, http://robot.watch.impress.co.jp/cda/news/2007/07/18/564.html, as accessed Sep. 1, 2011 5 pages, Robot Watch website. |
| Ueda et al., Large Effective-Strain Piezoelectric Actuators Using Nested Cellular Architecture With Exponential Strain Amplification Mechanisms, IEEE/ASME Transactions on Mechatronics, Oct. 2010, pp. 770-782, vol. 15 Issue 5, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Vanderborght et al., Variable impedance actuators: A review, Robotics and Autonomous Systems, Dec. 2013, 14 pages, vol. 61, Issue 12, Elsevier, Netherlands. |
| Walsh, Biomimetic Design of an Under-Actuated Leg Exoskeleton For Load-Carrying Augmentation, Massachusetts Institute of Technology, Feb. 2006, 97 pages, Massachusetts. |
| Walsh et al., A Quasi-Passive Leg Exoskeleton for Load-Carrying Augmentation, International Journal of Humanoid Robotics, Mar. 8, 2007, 20 pages, vol. 4, No. 3, World Scientific Publishing Company. |
| Wang et al., A highly-underactuated robotic hand with force and joint angle sensors, 2011 IEEE/RSJ International Conference on Intelligent Robots and Systems, Sep. 25-30, 2011, 6 pages, Institute of Electrical and Electronics Engineers, Piscataway, New Jersey. |
| Yeates, Utah-built robot safeguards the workplace, http://www.ksl.com?nid=148&sid=17654421&autostart=y; Oct. 13, 2011, 3 pages, KSL Broadcasting, Salt Lake City, Utah. |
| Yip et al., High-Performance Robotic Muscles from Conductive Nylon Sewing Thread, 2015 IEEE International Conference on Robotics and Automation (ICRA), May 26-30, 2015, 6 pages, Seattle, Washington. |
| Zubrycki et al., Novel haptic glove-based interface using jamming principle, Proceedings of the 10th International Workshop on Robot Motion and Control, Jul. 6-8, 2015, 6 pages, IEEE, Poland. |
