ROBOTIC REPAIR SYSTEM
20240018942 ยท 2024-01-18
Assignee
Inventors
Cpc classification
F03D17/004
MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
F03D17/003
MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
B25J15/0019
PERFORMING OPERATIONS; TRANSPORTING
F03D80/501
MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
B62D57/024
PERFORMING OPERATIONS; TRANSPORTING
F03D80/50
MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
International classification
F03D80/50
MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
B62D57/032
PERFORMING OPERATIONS; TRANSPORTING
B62D57/024
PERFORMING OPERATIONS; TRANSPORTING
B25J11/00
PERFORMING OPERATIONS; TRANSPORTING
Abstract
An integrated robotic repair system for repairing a surface is described. The said system comprising: a base translation system (110), said system comprising a multistage platform; a repair module (150), said module coupled to the translation system (110) to move the module (150) relative to the base translation system (110); an end effector selector system coupled to the repair module, said selector system comprising end effector repair tools (360, 362, 366), each tool (360, 362, 366) configured to undertake a repair task on the surface; and deployable legs (120), said legs (120) coupled to the base translation system (110) and configured to engage and disengage from the surface to allow the system to walk along surface.
Claims
1. An integrated robotic repair system for repairing a surface, said system comprising: a base translation system, said system comprising a multistage platform; a repair module, said module coupled to the translation system to move the module relative to the base translation system; an end effector selector system coupled to the repair module, said selector system comprising end effector repair tools, each tool configured to undertake a repair task on the surface; deployable legs, said legs coupled to the base translation system and configured to engage and disengage from the surface to allow the system to walk along surface.
2. The system of claim 1, wherein the deployable legs comprise attachment means for releasably engaging the repair system to the surface.
3. The system of claim 2, wherein the attachment means comprise suction discs.
4. The system of claim 3, wherein the suction discs comprise a plurality of suctions cups, said cups provided between an inlet sealing block and a contact surface sealing block.
5. The system of claim 4, wherein the suction cups are configured to engage the surface by compressing the inlet sealing block towards the contact surface sealing block.
6. The system of any one of claims 2 to 5, wherein the multistage platform comprises a first translation stage and a second translation stage, wherein the repair module is coupled to the first translation stage and is translatable in a first single axis.
7. The system of claim 6, wherein the first translation stage is coupled to the second translation stage and is translatable in a second single axis perpendicular to the first axis.
8. The system of any one of claims 2 to 7, wherein the deployable legs are hingedly attached to the attachment means.
9. The system of any preceding claim, where the surface may be a flat or curved surface.
10. The system of any preceding claim, wherein the repair module comprises a repair arm, said repair arm extending within the base translation system to present the end effector repair tool on the surface.
11. The system of any preceding claim, wherein the repair arm comprises a rotary tool selection system, said system rotatable to allow the desired end effector repair tool to be presented to the surface.
12. The system of any preceding claim, wherein the end-effector repair tools comprise a cleaning end-effector for performing a cleaning task.
13. The system according to claim 12, wherein the cleaning end-effector comprises: a controllable dispenser for metering cleaning liquid; and a rotary cleaning device driven by a motor.
14. The system of claim 13, wherein the controllable dispenser further comprises: a metering motor for actuating the dispenser, and wherein position information from the motor and metering motor allow control of a release rate of the cleaning liquid to the rotary cleaning device and a rotational speed of the rotary cleaning device according to the cleaning task.
15. The system according to any preceding claim, wherein the end-effector repair tools comprise a sanding end-effector for performing an abrasive task.
16. The system according to claim 15, wherein the sanding end-effector comprises a rotary sanding device driven by a motor.
17. The system according to any preceding claim, wherein the end-effector repair tools comprise a filler deposition end-effector for performing a filling task.
18. The system according to claim 17, wherein then filler deposition end-effector comprises: an active mixer for mixing filler, said active mixer comprising a motor; a nozzle for applying the filler to the blade according to the filling task, wherein the nozzle is a soft slit nozzle that conforms to the curvature of the blade; and a proximity sensor for measuring a deposition thickness of the filler and to interrupt the motor once a desired thickness according to the filling task is reached.
19. The system of any preceding claim, wherein the repair module comprises a series of joints for moving manoeuvring the repair module relative to the base translation system, and wherein the system further comprises a toolbox for storing the plurality of end effector repair tools; and wherein the repair module comprises a tool change mechanism located at a terminal end and configured to retrieve the repair tools from the toolbox and install them onto the module.
20. The system according to claim 19, wherein the toolbox comprises a retractable end-effector tool holder, said holder comprising resiliently biased jaws for holding one of the end-effector repair tools.
21. The system according to any preceding claim, wherein the system further comprises a casing for housing the toolbox, control electronics and any repair tool materials.
22. The system of claims 19 to 21, wherein the repair module comprises a mounting mechanism for installing the robotic repair system to a mobile robotic platform.
23. The system of claims 19 to 22, wherein the mobile robotic platform is an unmanned aerial vehicle or a crawler.
24. The system of claims 19 to 23, wherein the system further comprises a vacuum mounting for mounting the system to a surface.
25. The system of claims 19 to 24, wherein the plurality of joints comprise revolute joints, each revolute joint providing a rotational degree of freedom for the terminal end of the arm.
26. The system of claims 19 to 25, wherein the repair arm comprises a plurality of linkages, and wherein each revolute joint connects two linkages together.
27. The system of claim 26, wherein the repair arm comprises 5 revolute joints.
28. The system according to any of claims 19 to 27, wherein end-effector repair tools comprise a female connector and the tool change mechanism comprises a corresponding male connector for releasably retaining the end-effector repair tools.
29. The system according to claim 28, wherein the male connector is configured to retract to receive the female connector on the end-effector repair tool and is configured to extend to engage the female connector.
30. The system according to any preceding claim, further comprising one or more cameras for wirelessly transmitting visual images of performance of the repair system to a remote user.
31. The system according to any preceding claim, wherein the repair system comprises an imaging camera, and wherein the system comprises an image processing module for examining the surface for defects; and optionally or preferably wherein the system begins a repair task autonomously upon detection of defect.
32. The system according to any preceding claim, wherein the repair system is covered in a flexible protective sleeve; and optionally or preferably wherein the sleeve comprises one or more sleeve sensors configured to detect sheer strain in the sleeve indicative of the repair module being configured in a damaging orientation.
33. The system according to any preceding claim, further comprising a user interface for providing wireless control commands to the repair module by a remote user for transferring the remote user's tacit knowledge of the robotic repair process.
34. The system according to claim 33, further comprising a remote motion imitator for imitating movement of the remote control commands in a model of the repair module.
35. The system according to any preceding claim, wherein movement of the repair module through space is determined using one or more sensors.
36. The system of claim 35 wherein the sensor includes a collision detection sensor for detecting deleterious contact between the repair module and the blade and optionally or preferably wherein the collision detection sensor is an encoder on a motor of the system.
Description
BRIEF DESCRIPTION OF DRAWINGS
[0049] Embodiments will be described, by way of example only, with reference to the drawings, in which
[0050]
[0051]
[0052]
[0053]
[0054]
[0055]
[0056]
[0057]
[0058]
[0059]
[0060]
[0061]
[0062]
[0063]
[0064]
[0065]
[0066]
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
[0076]
[0077]
[0078] It should be noted that the Figures are diagrammatic and not drawn to scale. Relative dimensions and proportions of parts of these Figures have been shown exaggerated or reduced in size, for the sake of clarity and convenience in the drawings. The same reference signs are generally used to refer to corresponding or similar feature in modified and different embodiments.
DETAILED DESCRIPTION OF EMBODIMENTS
[0079]
[0080] Cameras 7, typically Wi-Fi cameras are used to monitor performance of the system and to provide real-time feedback to a remote user of the motion and movement of the repair system. The repair system comprises a repair module, such as a repair arm 8 and a tip 9 having an end-effector tool change mechanism 13 that is configured to retrieve repair tools from the toolbox and to install them onto the terminal end of the arm. Also shown is a stepper motor 10 and a servo-motor 11 that are linked by joints 12.
[0081]
[0082] The casing unit may form a three layer cluster case structured with a top layer 15 that is integrated with the mounting mechanism 5 for arm attachment, a middle layer housing the electronics 16, 17 for communication & control and material supply 24 and dispensing 25 mechanisms, and a base layer which accommodates the end-effector repair tools (toolbox layer). The electronics may be Arduino and/or Raspberry Pi boards or other system on a chip device. The lower layer accommodates retractable clamping end-effector tool holders 19 to hold the end-effector repair tools whilst not in use in the toolbox 14.
[0083] As will be described in further detail below,
[0084]
[0085]
[0086]
[0087]
[0088] A DC gear motor with Encoder (12 V, 300 rpm) is in charge of moving the drum 43 via an integrated 3D-printed gear. The position information provided by the two motor encoders, within a cleaning liquid dispenser module and the cleaning end-effector repair tool, enables controlling the release-rate of the cleaning liquid to the microfiber material as well as the drum rotational speed to carry out an effective cleaning task. The maximum capacity of the cleaning material dispenser is typically 20 ml.
[0089] The position information provided by the two motor encoders, within the cleaning liquid dispenser module 24 and the cleaning end-effector repair tool 24a, enables controlling the release-rate of the cleaning liquid to the microfibre.
[0090]
[0091] According to the material's technical datasheet, the recommended film thickness of this material (a layer of deposition at time) is 2 mm. In order to ensure this, a proximity sensor which comprises of an optical head FU-69U (Keyence Co., Japan) and a fiber-optic sensor FS-N11MN at locations near the terminal end of the arm continuously measure the deposition depth and interrupt the process if the maximum thickness is exceeded.
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098] All the presented process can be done autonomously and the operator acts as a supervisor to take control of the repair arm via the remote motion imitator via the user interface if any problem happens for its autonomous control system.
[0099] The other two sanding (
[0100] Additionally communication with the robotic system may be undertaken using communication software. In the last three decades, increasing attention to safety in human's working environments and need to industrial mass productions are two major reasons for the widespread use of robots and automation systems. However, the initial progress in developing robots were very slow. One of the main reason of the proposed problem was lack of open-source standard programming libraries to be used to sensors reading and actuators controlling which caused to re-write them for each application. The complexity writing the mentioned libraries led to creation of various middleware to simplify the process of robots' software developing and low-level communication complexity. For example, middleware that most widely used to facilitate the process of developing various kinds of robots is Robot Operating System (ROS). In fact, ROS is not an operating system, but it is an open-source middleware which can provide the services like low-level controlling, package management, building environment, message routine and hardware abstraction which simplified the process of robots' software development.
[0101] The fast progress in broadband telecommunication technologies, increases need to wireless controlling, big data collection, processing and analyzing has grown the researchers' attention to use Internet based telecommunication system for robots. In 1995, Taylor and Trevelyan provided a web based control for a robotic arm to manipulate some colored blocks. Burgard and Schulz developed a predictive simulation for visualization to handle teleoperation delay of mobile robots. Goldberg et al. created a web based control system and allowed users to maintain a garden by interacting with the robot over web. Yinong et al. presents a cloud based framework to interact with robots in the area of service-oriented computing. Osentoski et al. proposed the rosbridge and rosjs to enabled users who hasn't familiar with ROS to interact with ROS topics and services using JavaScript. Alexander et al. presents a collection of open-source modules to coverage ROS with modern web and network technologies[ ]. Kubaa et al. developed an asynchronous cloud based communication protocol between the robot and users.
[0102] Despite of the advantages of the aforementioned Internet based telecommunication system, there are weaknesses like need to have access to public IP address to be accessible by Websockets clients in rosbridge or need to have access to cloud based services like ROSLink. Moreover, based on new approaches in multiple robotic systems control, smart resources management and telecommunication security, we need new facilities which can support them.
[0103] There have been done many researches about the Internet based telecommunication systems that can be applied for interacting with robots over the Internet. In the following the most related works to our research and their pros and cons will be described.
[0104] In 2011, Osentoski et al. presented rosbridge and rosjs. As it mentioned in, the main motivations behind rosbridge and rosjs are, to enable novice robot users to interact with a ROS based robot by using Internet browsers and to provide the possibility of develop client applications to communicate with ROS based robots by Web developers who has no knowledge in field of robotics. Rosbridge and rosjs were developed based on JavaScript programming language for web applications. Moreover, they used the version 1.0 of socket and version 2.0 of WebSocket to provide common interfaces for non-web clients. In order to use rosjs we need to create a rosjs object firstly to be able to interact with a ROS based system by using ROS services and topics. The main features of rosbridge and rosjs are ability to publish through a simple publish command, providing an additional abstraction level on top of ROS systems, ability to interact with ROS through TCP/IP or WebSocket connection and provides two methods of security, first, protecting services/topics and key authorization. According to structure of rosbridge, the Websockets server which is ran on the robot need a public IP address then the WebSocket client can have access to it. This issue couldn't be reached in all robots. Developing robot applications by using web browsers advantages includes, the web-browsers are simple to use and people are familiar by using them and because of using web browsers in all of operating systems, then developing web browsers based applications can increase the accessibility of them. In 2012 B. Alexander et al. presented Robot Web Tools (RWT), which allows web applications to interface with various robots that has middleware like ROS. RVVT uses rosbridge for messaging ROS topics in a client-server architecture and interact with users through web browsers. A principal goal of RVVT is to converge robot middleware like ROS with web based technologies to provide the possibility of accessing to cloud robotics for use over public area networks. In 2015, A. Casan et al. developed a Robotic Programming Network (RPN) in the context of a web-enabled ROS system to provide the possibility of remote education and training. In 2017 Koubaa et al. proposed ROSLink as a bridge between ROS and Internet of Things (IoT) to use for cloud robotics. In fact, ROSLink is as a communication protocol that enable the possibility of implementing specifications of client in the robot side, and manifestation of a proxy server which is set on a public IP server machine, like a cloud server. One of the main points about ROSLink is, its ability to define its own communication protocol between ROS and non-ROS users through the cloud. The main advantages of ROSLink cloud-based approach compare to the similar protocols like it can be regarded as, its independency from the robots' ROS master nodes, ability to communication between users and robots through the cloud, and effective management of robots, users and fundamental services. Due to the vast facilities of cloud services provides for their users, interesting in researches about cloud robotics has been increased currently. In 2019, Pereira et al. developed ROSRemote to helps users to work with ROS in a remote master based on a framework that give the possibility to create several applications that may run remotely on it. In 2020, Toffetti et al. presented an Enterprise Cloud Robotics Platform (ECRP), a Platform as a Service (PaaS) solution to build ROS-based cloud robotics applications. In spite of cloud services advantages for using as remote computing service or logged data storage, there are some concerns exist about them like, having continues access to them, privacy and security of storage data, and the support of services providers about their products.
[0105] ROS is an open-source meta-operating software which is created based on a collection of tools, libraries, and conventions that aim to simplify the process of creating complex and robust robot behavior across a wide variety of robotic platforms. ROS provides common interface that allow users to code sharing and reuse. The proposed features of ROS help robotic researchers and developers to concentrate on new innovation instead of spending time to writing the standard programming libraries again.
[0106] Moreover, it provides an abstraction layer to hardware resources and reveal the data obtained from the hardware parts as a labeled data stream which is named Topic.
[0107] ROS uses a peer-to-peer networking topology. The systems that are ROS based include a number of processes called nodes which are communicate with each other by sending messages. The ROSs' messages are simple data structures consist of typed fields. The communication between nodes will be done through ROS Master. The ROS Master main duties is to naming and registration services to rest of the nodes in ROS based system. In a ROS distributed network the master device will be considered as the ROS-core executer.
[0108] The main communication models between ROS nodes are, publish/subscribe and request/reply models. In the first communication model nodes exchanges topics, in this case one or multiple nodes may act as publisher(s) of a specific topic, and multiple nodes may subscribe to that topic, via the ROS Master. In the second ROS based communication model, one node will act as server which provide the service which is defined by using a pair of messages (one for the request and the other for reply) under a certain name, and process the received requests from other nodes as clients.
[0109] ROS is an open-source meta-operating software which is created based on a collection of tools, libraries, and onventions that aim to simplify the process of creating complex and robust robot behavior across a wide variety of robotic platforms. ROS provides common interface that allow users to code sharing and reuse. The proposed features of ROS help robotic researchers and developers to concentrate on new innovation instead of spending time to writing the standard programming libraries again.
[0110] Moreover, it provides an abstraction layer to hardware resources and reveal the data obtained from the hardware parts as a labeled data stream which is named Topic.
[0111] ROS uses a peer-to-peer networking topology. The systems that are ROS based include a number of processes called nodes which are communicate with each other by sending messages. The ROSs' messages are simple data structures consist of typed fields. The communication between nodes will be done through ROS Master. The ROS Master main duties is to naming and registration services to rest of the nodes in ROS based system. In a ROS distributed network the master device will be considered as the ROS-core executer.
[0112] The main communication models between ROS nodes are, publish/subscribe and request/reply models. In the first communication model nodes exchanges topics, in this case one or multiple nodes may act as publisher(s) of a specific topic, and multiple nodes may subscribe to that topic, via the ROS Master. In the second ROS based communication model, one node will act as server which provide the service which is defined by using a pair of messages (one for the request and the other for reply) under a certain name, and process the received requests from other nodes as clients.
TABLE-US-00001 Algorithm 1: Sending command from console to the manipulator 1. Function sent (command): 2. Define: user api_id, api_hash and phone number, 3. Client = TelegramClient(phone, api_id, api_hash) 4. Client_connect 5. If not client_is_user_authoriaed( ) then 6. Client_send_code_request(phone); 7. Client_sign_in(phone, (Enter the code)); 8. Client_start( ); 9. Destination_user_username=insert the client user name; 10. Entity=client_get_entity(robot_user_username); 11. Client)send_message(entity, message=command); 12. Function main( ); 13. If container.txt>0 then 14. Command=read_container.txt( ); 15. Sign_1=command[0] 16. If sign_1==1 then->input command is related to switch button or joints 17. Sent(command[1]); 18. else 19. for (i=2; i<7; i++) do 20. Sent(command[i]); Control a Manipulator
[0113] In order to make a remote connection between the arm and the console, a secure internet-based communication system is designed and implemented.
[0114]
[0115] In the case that the operator push each of the console switch button a number and a sign will be sent to the Telegram application and then the proposed data will be sent to the arm as an executable command.
[0116] In Algorithms 1 and 2, the api id, api hash and the phone number are three parameters used for user identification which can be obtained from the Telegram application, and they are unique. Moreover, as seen in Algorithm 1, the content of the container.txt file will be monitored continuously, and any change in the content is checked against the commands for end-effector switch buttons or the console's imitation tool, which is used to detect the onset of commands array for reading. The output of Algorithm 2 will be saved in container.txt file which is used as the input command to the ROS node used to control the arm.
[0117] The latency of the ROSIC system is calculated; the delay between the time of sending and receiving of the data over 4G mobile internet network is less than three seconds, which is acceptable for this project application.
TABLE-US-00002 Algorithm 2: Receiving command from console and save in container.txt file. 1. Function receive( ); 2. Define: user api_id, api_hash and phone number; 3. Client=TelegramClient(phone, api_id, api_hash)_start( ) 4. Client_start( ) 5. Destination_user_username==insert the user's name; 6. @client_on(events_NewMessage) -> Check the command which are 7. Async def handler(event); received from operator Telegram 8. Chat = await event_get_input_chat( ) 9. UI=chat_user_id 10. If(UI==user_id) then 11. Save even in container.txt 12. Client_run_until_disconnected( )
[0118]
[0119]
[0120]
[0121]
[0122] By utilising this two axis stage, the repair module and the associated end effector tools can be positioned at any point within the stage.
[0123] In order for the robotic system to be moveable to a general location for repair/maintenance, the deployable legs are able to attach and release the turbine surface to allow the system to walk across the surface of the blade and into position.
[0124] In order to attach to the surface the deployable legs are hingedly attached to the attachment means. The attachment means are shown in
[0125] The example shown has 3 suction cups that are retained in the suction cup holder plate through a bayonet fitting about a neck of the suction cups 142. The suction cups 142 comprise a stopper 144 that are secured to the blade surface through a stopper hub 146 and a soft foam layer 148 that is placed on the surface. The foam layer is typically soft EPDM foam that allows conformation to the blade's curved surface.
[0126] Negative pressure may be used to engage and disengage the suction cups. This may include using a vacuum pump or using a compression mechanism for the suction cup as well as a sealing mechanism for the suction cup inlet. The above suction cup compression mechanism can either exploit the weight of the robot or be an active (motorised) compression mechanism.
[0127] From reading the present disclosure, other variations and modifications will be apparent to the skilled person. Such variations and modifications may involve equivalent and other features which are already known, and which may be used instead of, or in addition to, features already described herein.
[0128] Although the appended claims are directed to particular combinations of features, it should be understood that the scope of the disclosure of the present invention also includes any novel feature or any novel combination of features disclosed herein either explicitly or implicitly or any generalisation thereof, whether or not it relates to the same invention as presently claimed in any claim and whether or not it mitigates any or all of the same technical problems as does the present invention.
[0129] Features which are described in the context of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable sub-combination. The applicant hereby gives notice that new claims may be formulated to such features and/or combinations of such features during the prosecution of the present application or of any further application derived therefrom.
[0130] For the sake of completeness it is also stated that the term comprising does not exclude other elements or steps, the term a or an does not exclude a plurality, and reference signs in the claims shall not be construed as limiting the scope of the claims.