1.1Mechanical fixture sets the cycle
A contoured guide sets the tool path while adjustable stops set the stroke endpoints. A foot switch energizes a pneumatic valve through a relay, and an end-of-stroke switch triggers the return stroke.
Generated automatically. Not reviewed by a person. Not legal advice or an opinion.
Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.
A contoured guide sets the tool path while adjustable stops set the stroke endpoints. A foot switch energizes a pneumatic valve through a relay, and an end-of-stroke switch triggers the return stroke.
The operator measures fixture spacing and overhead clearance, weighs the workpiece, and enters the required reach, maximum tool height, and payload into a job form. The dispatcher uses the entered values directly to match the job to a station.
Each station has two permanently mounted arms sized for the fixture and workpiece family. The job record addresses the station directly, and hardwired fixture switches gate the start signal for the installed arms.
The robots run the programmed cycle with a dummy workpiece that matches the production mass and center of gravity. Fixture gauges and drive current sensors record actual clearance and current, and the controller releases production when the readings meet the acceptance limits.
The technician reads joint current and fixture clearance values and uses a printed setup table to choose a wrist spacer or counterbalance setting. After the adjustment, the technician repeats the cycle and checks the readings against the acceptance limits.
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
A greenhouse controller reads tray dimensions, loaded mass, bench height, and aisle width from a work order and a facility map. It selects mobile manipulators using their payload and reach ratings, then compares predicted tray tilt with the spill limit for the assigned route. When the predicted tilt exceeds that limit, it commands an automatic tool changer to fit a tray cradle. It loads the cradle dimensions and acceleration limits into the selected robots and dispatches the transfers.
A mixed-integer linear programming solver replaces the fleet controller's robot selection logic. Binary variables assign robots to jobs, while constraints enforce reach, payload rating, tool compatibility, and availability. After selection, an inverse kinematics routine checks the assigned waypoints for low joint travel margins and determines base offsets for the affected robots. The controller commands the bases to move to the calculated offsets, updates their coordinate frames from docking measurements, and starts the jobs.
A controller assigns transport jobs at 12 workstations to a fleet of eight mobile manipulators on a 30-second planning cycle. It uses scheduled pickup times, tray masses, route lengths, and robot battery readings to estimate the charge remaining after each assigned trip. If a trip projects a charge below 20 percent, the controller issues a battery exchange command and directs the assigned robot to an automated exchange dock. After the dock reports that the replacement pack is seated, the controller updates the robot's charge and dispatches the job.
A controller selects a mobile manipulator to carry a tote through a passage with 620 millimeters of overhead clearance and requires a 40-millimeter vertical clearance margin. It combines the robot's lift position with the tote height to predict whether the loaded profile exceeds 580 millimeters. If the profile exceeds that height, the controller commands the robot to retract its lift within its 180-millimeter stroke and checks the resulting height from the lift encoder. It then loads the measured profile into the route controller, sets a passage speed of 0.25 meters per second, and starts the transfer.
A conveyor controller sends part identifiers, encoder counts, and belt speed to a robot fleet controller. The fleet controller selects an arm using its reach and cycle time, then compares the available suction force with the force required to lift and accelerate the identified part. When the suction margin falls below the configured minimum, the controller commands the arm to exchange its suction tool for a parallel-jaw gripper at a tool rack. It loads the gripper offsets, synchronizes the arm with the conveyor encoder, and commands the arm to pick the moving part.
A controller derives the torque and dwell schedule from a repetitive task and selects robots using their payload ratings, reach, and drive ratings. It initializes a thermal model with each assigned drive's temperature and estimates the peak winding temperature over the scheduled cycles using logged motor current and enclosure temperature. If the forecast exceeds a configured threshold, the controller calculates lower joint acceleration limits and writes them to the affected drives. It regenerates the motion timing under those limits and starts the revised cycle after the drives confirm the settings.
A fleet computer polls each robot controller over a wired network for rated payload, joint travel limits, and the installed tool identifier. Each controller returns the values with a robot identifier and timestamp.
A modification command identifies a replacement wrist module and its rack position. The computer moves the arm to the rack, actuates the coupler, and verifies the lock switch and module identifier before releasing the arm.
After a wrist module exchange, each robot touches a fixed calibration sphere from three approach directions with a probe of known geometry. The computer computes the tool center offset and stores it in the active tool frame along with the module mass and center of gravity.
The controller transforms fixture waypoints into each robot's base frame and applies the stored tool offsets when generating joint trajectories. One arm seats the workpiece, and a fixture position switch triggers the second arm to close the retaining clamp.
Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.
A device in a robot enabling the robot to cooperatively work with other robot in a robot network, comprising: a communication module, configured to acquire information of a team task; a task analysis module, configured to determine, based on the acquired information of the team task, each robot in a robot team in the robot network, wherein the robot team comprises at least one cooperating robot; a leader robot determining module, configured to determine a leader robot in theA · US 2019/0283255 A1 · claim 14
Step 108a: generating control instructions respectively for one or more robots in the robot team based on the information of the state of the present robot, the information of the state of the each other robot, and the information of the team task, wherein the control instructions are configured to respectively control the one or more robots in the robot team to work cooperatively so as to complete the team task;A · US 2019/0283255 A1 · ¶ 77
In this case, instead of the general common sense based robotic ontology, a specific fact file for the current context needs to be accessed. Robot specific knowledge will get populated at the start by manual entry and the outer world of the robot is generated as a semantic map out of continuous observations.B · US 2024/0402725 A1 · ¶ 49
When the object is in the current view state, the system 100 queries the ontology (herein after interchangeably used as ontology graph) to see a match between the robot capability, target object property and the task type extracted from user instruction.B · US 2024/0402725 A1 · ¶ 27
In Step 108a, the leader robot generates control instructions configured to allow the robots in the robot team to work cooperatively to complete the team task based on the information of the team task and the information of the state of all the robots in the robot team.A · US 2019/0283255 A1 · ¶ 109
If the task is feasible, the robot will look up the task execution list to see which of the sub-task needs to be done, and in what sequence, and involving what entities. The list of task actions and its mapping to actual robotic movements is stored in an Action Recipe module, that acts as a wrapper on top of the actual physical world actuation of a robot.B · US 2024/0402725 A1 · ¶ 27
If so, the any one robot generates and sends control instructions that respectively enable one or more robots in the robot team to cooperatively complete the team task; otherwise, it receives and executes a control instruction from the leader robot.A · US 2019/0283255 A1 · abstract
As an example, the high level action ‘go forward’ will be mapped to moving the robot motor wheels forward by some pre-set distance or instructed distance estimate. Final stage is execution by robot motors in hand (wheels in case of navigation) till goal state as per user instruction is reached.B · US 2024/0402725 A1 · ¶ 27
An empty cell means only that no passage was reproduced there.
With the increasingly refined division of labor among robots, different robots are configured to specialize in processing different tasks respectively, and therefore, the cooperation among a plurality of robots has become more and more important.A · US 2019/0283255 A1 · ¶ 3
Embodiments of the present disclosure provide a robot cooperation method and device, a robot, a computer program product, and a robot system, mainly to improve the control flexibility for robot cooperation.A · US 2019/0283255 A1 · ¶ 5
Existing robotic task execution systems do not provide solutions to check whether task instruction provided by the user is executable or not in an uncertain environment.B · US 2024/0402725 A1 · ¶ 5
The input medium can also be speech or gestures converted to text by a processing unit.B · US 2024/0402725 A1 · ¶ 8
patent.fyi, US 2026/0355953 A1, claim 1, first published 2026-11-19T17:33:15-05:00, https://patent.fyi/US20260355953/, SHA-256 d8b7a794ec19733039ed967e1a791536e8f333a774ee126480c852b34c76203f