A robot access method, device, robot and storage medium

The data access robot is parsed through the user-configured formula files, which solves the problems of complex data processing and fixed format in the existing technology, and realizes the flexibility and speed of robot access.

CN113672559BActive Publication Date: 2024-11-29SIASUN CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202111002759.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-08-30
Publication Date
2024-11-29
Estimated Expiration
2041-08-30

AI Technical Summary

Technical Problem

In the existing robot access methods, users need to process and convert data by themselves, and the operation is complicated; or the data format is fixed, and users cannot dynamically configure and expand.

Method used

Through the user-configured recipe files, obtain and parse recipe parameters, determine the parsed data to access the robot, and achieve flexible data access without the need for fixed lengths and types, reducing user processing and conversion.

Benefits of technology

It realizes the flexibility, convenience and speed of the robot access process, avoiding the complexity of data access and format fixity problems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113672559B_ABST
    Figure CN113672559B_ABST
Patent Text Reader

Abstract

The present invention discloses a robot access method, device, robot and storage medium. The method comprises: obtaining a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; parsing the recipe parameters in the recipe file to determine parsed data of the recipe file; and accessing the robot based on the parsed data. Through the technical solution of the present invention, the robot can be accessed based on the recipe file configured by the user, without fixing the length and type of data access, and without the user having to process and convert data, so that the robot access process is more flexible, convenient and fast.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of robot technology, and in particular to a robot access method, a robot access device, a robot, and a storage medium. Background Art

[0002] At present, there are two main ways for robots on the market to access the outside world: one is to send and receive the user's original data, unpack and convert the original data through the upper-level script function, and then access the outside world; the other is that the robot sends or receives a certain data format package in a fixed data format, and then unpacks the data to access the outside world.

[0003] In the first method, the robot does not provide data unpacking and data conversion, and the user has to process the data at the script language level, which is complex and error-prone. In the second method, although a fixed data format is provided on the robot side for external users to receive or send data, the data format provided is relatively fixed and users cannot perform dynamic configuration and expansion. Summary of the invention

[0004] The embodiments of the present invention provide a robot access method, device, robot and storage medium to enable robot access based on a recipe file configured by a user, without the need to fix the length and type of data access and without the need for data processing and conversion by the user, making the robot access process more flexible, convenient and quick.

[0005] In a first aspect, an embodiment of the present invention provides a robot access method, comprising:

[0006] Obtaining a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user;

[0007] Parsing the recipe parameters in the recipe file to determine parsed data of the recipe file;

[0008] The robot is accessed based on the parsed data.

[0009] Further, the step of obtaining the recipe file input by the user includes:

[0010] Acquire the recipe file input by the user in the external user device through the external interface;

[0011] The recipe file is a file obtained after a user configures recipe parameters in a recipe template file, and the recipe module file is determined based on a protocol of the external interface.

[0012] Further, the parsing of the recipe parameters in the recipe file to determine the parsed data of the recipe file includes:

[0013] Parsing each recipe parameter in the recipe file to determine the configuration data corresponding to each recipe parameter;

[0014] The parsed data of the recipe file is determined according to each of the recipe parameters and the corresponding configuration data.

[0015] Further, if the recipe file is a streaming recipe file, each recipe parameter of the streaming recipe file includes: a data header, a data footer, a first data input item, a first data output item and a first system recipe flag;

[0016] If the recipe file is a frame-type recipe file, each recipe parameter of the frame-type recipe file includes: a second data input item, a second data output item and a second system recipe flag, wherein the second data input item includes: a data identification number.

[0017] Further, according to each of the recipe parameters and the corresponding configuration data, the parsed data of the recipe file is determined, including:

[0018] For a streaming recipe file, determining first parsed data of the recipe file according to configuration data corresponding to the first data input item; determining second parsed data of the recipe file according to configuration data corresponding to the first data output item;

[0019] For a frame-type recipe file, first parsed data of the recipe file is determined according to configuration data corresponding to the second data input item; and second parsed data of the recipe file is determined according to configuration data corresponding to the second data output item.

[0020] Further, accessing the robot based on the parsed data includes:

[0021] If the configuration data corresponding to the system recipe flag is system data, then updating the first target data in the system data area of ​​the robot according to the first parsed data;

[0022] Reading first target data in the system data area of ​​the robot according to the second parsed data, and sending the first target data to the user terminal;

[0023] The system formula identifier includes: a first system formula identifier and a second system formula identifier.

[0024] Further, accessing the robot based on the parsed data further includes:

[0025] If the configuration data corresponding to the system recipe flag is custom data, calling a custom update function according to the first parsed data, and updating the second target data in the custom data area in the robot based on the custom update function;

[0026] calling a custom read function according to the second parsed data, reading second target data in the custom data area in the robot based on the custom read function, and sending the second target data to an external user device;

[0027] The system formula identifier includes: a first system formula identifier and a second system formula identifier.

[0028] In a second aspect, an embodiment of the present invention further provides a robot access device, the device comprising:

[0029] A recipe acquisition module is used to acquire a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user;

[0030] A recipe parsing module, used to parse the recipe parameters in the recipe file to determine parsed data of the recipe file;

[0031] A data access module is used to access the robot based on the parsed data.

[0032] In a third aspect, an embodiment of the present invention further provides a robot, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the robot access method as described in any one of the embodiments of the present invention is implemented.

[0033] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the robot access method as described in any one of the embodiments of the present invention.

[0034] The embodiment of the present invention obtains a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; the recipe parameters in the recipe file are parsed to determine parsed data of the recipe file; and the robot is accessed based on the parsed data. The robot can be accessed based on the recipe file configured by the user, without fixing the length and type of data access, and without the need for the user to process and convert the data, thereby achieving a more flexible, convenient and quick robot access process, and solving the problems in the prior art that the robot side does not provide data unpacking and data conversion, resulting in complicated data access on the user side, or that although the robot side provides a data format, the data format is fixed and the user cannot perform dynamic configuration and expansion. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0036] Figure 1 is a flow chart of a robot access method in Embodiment 1 of the present invention;

[0037] Figure 2 is a flow chart of a robot access method in Embodiment 2 of the present invention;

[0038] Figure 3 is a schematic structural diagram of a robot access system in an embodiment of the present invention;

[0039] Figure 4 is a flow chart of a method for accessing robot system data in an embodiment of the present invention;

[0040] Figure 5 is a flow chart of a method for accessing robot custom data in an embodiment of the present invention;

[0041] Figure 6 It is a schematic diagram of the structure of a robot access device in Embodiment 3 of the present invention;

[0042] Figure 7 It is a schematic diagram of the structure of a robot in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0043] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0044] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0045] Embodiment 1

[0046] Figure 1This is a flow chart of a robot access method provided in Embodiment 1 of the present invention. This embodiment is applicable to the case where the robot is accessed through an external user device. The method can be executed by the robot access device in the embodiment of the present invention. The device can be implemented in software and / or hardware. Figure 1 As shown, the method specifically comprises the following steps:

[0047] S110, obtaining a recipe file input by a user.

[0048] The recipe file may be a general data conversion method provided in the form of a file, and the robot and the external user device implement access processes such as sending and receiving data based on the recipe file. The recipe file in the embodiment of the present invention is obtained by configuring the recipe parameters by the user.

[0049] Exemplarily, a method for obtaining a recipe file input by a user may be: the robot obtains a configured recipe file input by a user through an external interface, or a recipe template file may be provided to the user at the robot's external interface, and a recipe file obtained by the user configuring recipe parameters in the recipe template file is received.

[0050] The robot is accessed based on the recipe file configured by the user. The recipe file can be configured by the user according to the needs. There is no need to fix the length and type of data access, making the robot access process more flexible.

[0051] S120, parsing the recipe parameters in the recipe file to determine parsed data of the recipe file.

[0052] The recipe file is composed of recipe parameters and configuration data corresponding to the recipe parameters. The recipe parameters are parameters included in the recipe file, and the configuration data are data configured by the user for the recipe parameters. The specific contents of the configuration parameters and the configuration data are not limited here.

[0053] Exemplarily, after acquiring the recipe file, the robot parses the recipe parameters in the recipe file through a recipe parser to determine parsed data of the recipe file, where the parsed data is used to describe the content and format of data access.

[0054] S130: Access the robot based on the parsed data.

[0055] When accessing the robot, this step can determine the sending data format for sending data to the robot according to the configuration data contained in the input item in the parsed data, send data to the robot based on the sending data format, and; determine the acquisition data format for obtaining data from the robot according to the configuration data contained in the output item in the parsed data, obtain data from the robot based on the acquisition data format, and determine the data format for obtaining data from the robot.

[0056] The technical solution of this embodiment is to obtain a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; parse the recipe parameters in the recipe file to determine parsed data of the recipe file; and access the robot based on the parsed data. The robot can be accessed based on the recipe file configured by the user, without fixing the length and type of data access, and without the need for the user to process and convert data, thereby making the robot access process more flexible, convenient and quick.

[0057] Optionally, the step of obtaining a recipe file input by a user includes:

[0058] Acquire the recipe file input by the user in the external user device through the external interface;

[0059] The recipe file is a file obtained after the user configures the recipe parameters in the recipe template file. The recipe template file is used to provide recipe parameters that need to be configured by the user. The recipe module file is determined based on the protocol of the external interface.

[0060] Exemplarily, the external interface connecting the robot to the external user equipment can generally include two categories: one is an interface based on a streaming protocol, such as the Transmission Control Protocol (TCP) and the serial communication protocol (RS-485 or RS-232); the other is an interface based on a frame protocol carrying an identification number, such as the Controller Area Network (CAN). Different types of external interface protocols correspond to different recipe template files. The recipe template file corresponding to the interface based on the streaming protocol can be a streaming recipe template file, and the recipe template file corresponding to the interface based on the frame protocol carrying an identification number can be a frame recipe template file. The recipe parameters contained in different recipe template files may also be different.

[0061] Embodiment 2

[0062] Figure 2 This is a flow chart of a robot access method in Embodiment 2 of the present invention. This embodiment is optimized based on the above embodiment. In this embodiment, the parsing of the recipe parameters in the recipe file to determine the parsed data of the recipe file includes: parsing each recipe parameter in the recipe file to determine the configuration data corresponding to each recipe parameter; determining the parsed data of the recipe file according to each recipe parameter and the corresponding configuration data.

[0063] like Figure 2 As shown, the method of this embodiment specifically includes the following steps:

[0064] S210, obtaining a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user.

[0065] S220, parsing each recipe parameter in the recipe file to determine configuration data corresponding to each recipe parameter.

[0066] Specifically, the recipe files include: streaming recipe files and frame recipe files. Different types of recipe files contain different recipe parameters, and the recipe files are unpacked to obtain configuration data corresponding to the recipe parameters of the recipe files of this type.

[0067] Optionally, if the recipe file is a streaming recipe file, each recipe parameter of the streaming recipe file includes: a data header, a data footer, a first data input item, a first data output item and a first system recipe flag;

[0068] If the recipe file is a frame-type recipe file, each recipe parameter of the frame-type recipe file includes: a second data input item, a second data output item and a second system recipe flag, wherein the second data input item includes: a data identification number.

[0069] Among them, the data input item is used to describe the name of the data input to the robot, the data output item is used to describe the name of the data output by the robot, and each recipe parameter of the streaming recipe file includes: a data header, a data tail, a first data input item, a first data output item, and a first system recipe flag. The data header head and the data tail tail serve as the frame header and frame tail of the streaming recipe file data frame respectively. The first data input item Input and the first data output item Output may include: a data name name and a data type type. The data types include: unsigned eight-bit integer data byte, signed eight-bit integer data char, unsigned sixteen-bit integer data word, signed sixteen-bit integer data short, unsigned thirty-two-bit integer data dword, signed thirty-two-bit integer data int, thirty-two-bit floating point number float, and sixty-four-bit double-precision floating point number double, which can be represented as 0-7 respectively.

[0070] Each recipe parameter of the frame recipe file includes: a second data input item, a second data output item and a second system recipe flag, wherein the second data input item includes: data name name, data type type and data identification number, the data identification number, i.e., data ID, is used as the frame ID of the frame recipe to determine the data to be accessed.

[0071] Both the stream recipe file and the frame recipe file include the system recipe flag system, which is used to describe the system data or custom data of the access robot. The system recipe flag is true, which indicates the robot system data; the system recipe flag is false, which indicates non-robot system data, that is, custom data. When the system recipe flag describes the robot system data, the robot will periodically receive and send system data. When the recipe describes user-defined data, the reception and sending of data are determined by the user at the script language layer.

[0072] Exemplarily, the standard format for describing the streaming recipe file in json format may be:

[0073]

[0074]

[0075] The standard format for describing the frame recipe file in json format can be:

[0076] S230: Determine parsed data of the recipe file according to each of the recipe parameters and the corresponding configuration data.

[0077] Specifically, the configuration data corresponding to each recipe parameter in the recipe file is converted into a data access format accessible to the robot, and the parsed data of the robot is determined.

[0078] In a specific example, a streaming recipe file for accessing robot system data may be:

[0079]

[0080] By parsing the above stream recipe file, a parsed data that can access the robot system data can be obtained. The format of the parsed data is that the data header is bytes FF(255), FF(255), the data tail is bytes FF(255), FF(255), the input parsed data is an unsigned 16-bit integer named "__WordInputReg_1", and the data output is a 32-bit floating point number named "__RobotState_1". For example, the parsed data determined by the configuration data corresponding to the data input item as shown in Table 1 is obtained, and the parsed data is mapped to the robot system data "__WordInputReg_1", which is equivalent to using the robot system variable as the access object: __WordInputReg_1 = 0x0008. Due to the configuration shown in Table 2, the output data "__RobotState_1" determined by the configuration data corresponding to the data output item, after the recipe file is parsed, the robot system will periodically send parsed data to the external user device. The parsed data consists of a data header, "__RobotState_1" output data and a data footer, where the __RobotState_1 type is float, occupying 4 bytes, and the output format of the parsed data is determined by the configuration data of the output item.

[0081] Table 1

[0082]

[0083] Table 2

[0084]

[0085] In another specific example, a streaming recipe file for accessing custom data may be:

[0086]

[0087]

[0088] By parsing the above streaming recipe file, a parsed data that can access user-defined data can be obtained. The data header of the parsed data is byte FF (255), the data tail is byte FF (255), the data input is an unsigned 16-bit integer named "value_in", and the data output is a 32-bit floating point number named "value_out". For example, the input data shown in Table 3 can be obtained, and the user-defined function value = recipe_read ("value_in") is called based on the input data, which is mapped to the data value = 0x0008 in the robot's custom data area. Since the user configures a custom output variable, when the user calls the script value = 3.14, recipe_write ("value_out", value), the value variable is processed into the output data shown in Table 4.

[0089] Table 3

[0090]

[0091] Table 4

[0092]

[0093] S240: Access the robot based on the parsed data.

[0094] The technical solution of this embodiment is to obtain a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; parse the recipe parameters in the recipe file to determine parsed data of the recipe file; and access the robot based on the parsed data. The robot can be accessed based on the recipe file configured by the user, without fixing the length and type of data access, and without the need for the user to process and convert data, thereby making the robot access process more flexible, convenient and quick.

[0095] Optionally, determining the parsed data of the recipe file according to each of the recipe parameters and the corresponding configuration data includes:

[0096] For a streaming recipe file, determining first parsed data of the recipe file according to configuration data corresponding to the first data input item; determining second parsed data of the recipe file according to configuration data corresponding to the first data output item;

[0097] For a frame-type recipe file, first parsed data of the recipe file is determined according to configuration data corresponding to the second data input item; and second parsed data of the recipe file is determined according to configuration data corresponding to the second data output item.

[0098] Exemplarily, for a streaming recipe file, the first parsed data of the recipe file is determined based on the data name and data type in the first data input item, so as to facilitate sending data to the robot in the data format of the first parsed data; the second parsed data of the recipe file is determined based on the data name and data type in the first data output item, so as to facilitate obtaining data from the robot in the data format of the second parsed data.

[0099] For a frame-type recipe file, the first parsed data of the recipe file is determined according to the data identification number, data name and number type in the second data input item, so as to facilitate sending data to the robot in the data format of the first parsed data; the second parsed data of the recipe file is determined according to the data identification number, data name and number type in the second data output item, so as to facilitate obtaining data from the robot in the data format of the second parsed data.

[0100] Optionally, accessing the robot based on the parsed data includes:

[0101] If the configuration data corresponding to the system recipe flag is system data, then updating the first target data in the system data area of ​​the robot according to the first parsed data;

[0102] Reading first target data in the system data area of ​​the robot according to the second parsed data, and sending the first target data to the user terminal;

[0103] The system formula identifier includes: a first system formula identifier and a second system formula identifier.

[0104] Exemplarily, if the system recipe flag is system data, the first target data is determined to be data in the robot system data area, the first parsed data is determined to be mapped to the first target data in the robot system data area, and the first target data is updated according to the first parsed data to achieve periodic data transmission to the robot system. The first target data in the robot system data area is read according to the second parsed data, and the first target data is sent to the user terminal to achieve data acquisition from the robot system.

[0105] Optionally, accessing the robot based on the parsed data further includes:

[0106] If the configuration data corresponding to the system recipe flag is custom data, calling a custom update function according to the first parsed data, and updating the second target data in the custom data area in the robot based on the custom update function;

[0107] calling a custom read function according to the second parsed data, reading second target data in the custom data area in the robot based on the custom read function, and sending the second target data to an external user device;

[0108] The system formula identifier includes: a first system formula identifier and a second system formula identifier.

[0109] Exemplarily, if the configuration data corresponding to the system recipe flag is custom data, the second target data is determined to be the data in the robot's custom data area; since the user-defined data is not controlled by the system, the sending and receiving requires the user to call a function trigger, and the custom update function is called according to the first parsed data, and the second target data in the custom data area in the robot is updated based on the custom update function to send data to the robot's system data area. The custom read function is called according to the second parsed data, and the second target data in the custom data area in the robot is read based on the custom read function, and the second target data is sent to the external user device to obtain data from the robot's system data area.

[0110] Exemplarily, the robot access method provided by the embodiment of the present invention can be performed by Figure 3 The robot access system shown is executed, and the system includes: an external user device, a robot external interface, and a data access device. The data access device includes a recipe parsing module for parsing each recipe parameter in the recipe file. The external user device is connected to the robot external interface, and the robot external interface may include: a TCP interface, a 485 interface, a 232 interface or a CAN bus interface; the recipe file corresponding to the external interface protocol input by the user is obtained through the external interface, and the recipe parsing module at the end of the data access device parses each recipe parameter in the recipe file to determine the configuration data corresponding to each recipe parameter; the target data of the robot is determined according to each recipe parameter and the corresponding configuration data. If the recipe parameter system recipe mark is system data, the target data is the system data of the robot; if the recipe parameter system recipe mark is custom data, the target data is the user-defined data in the robot. The data access device will send the target data read from the robot system data area or the user-defined data area to the external user device through the robot external interface. Figure 4 As shown in the figure, when the recipe file is configured with system data, the process of accessing the robot system data from the external interface is as follows: the user configures the recipe file in the external device interface, sends the recipe file to the data access device through the robot external interface connected to the external user device, and parses each recipe parameter in the recipe file through the recipe parsing module in the data access device, determines the recipe parameter mapping to the target data in the robot system data area, and sends the target data to the external user device through the robot's external interface. Figure 5As shown, when the recipe file is configured with custom data, the process of accessing the robot system data from the external interface is: the user configures the recipe file on the external device interface, sends the recipe file to the data access device through the robot external interface connected to the external user device, parses each recipe parameter in the recipe file through the recipe parsing module in the data access device to determine the target data, calls the custom function corresponding to the target data to read the target data in the robot data area, and sends the target data to the external user device through the robot's external interface.

[0111] Embodiment 3

[0112] Figure 6 This is a schematic diagram of the structure of a robot access device provided in Embodiment 3 of the present invention. This embodiment is applicable to the case where a robot is accessed through an external user device. The device can be implemented in software and / or hardware. The device can be integrated in any device that provides the function of robot access, such as Figure 6 As shown, the access device of the robot specifically includes: a recipe acquisition module 310 , a recipe parsing module 320 and a data access module 330 .

[0113] The recipe acquisition module 310 is used to acquire a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user;

[0114] A recipe parsing module 320, for parsing the recipe parameters in the recipe file to determine parsed data of the recipe file;

[0115] The data access module 330 is used to access the robot based on the parsed data.

[0116] Optionally, the recipe acquisition module 310 is specifically used to:

[0117] Acquire the recipe file input by the user in the external user device through the external interface;

[0118] The recipe file is a file obtained after a user configures recipe parameters in a recipe template file, and the recipe module file is determined based on a protocol of the external interface.

[0119] Optionally, the recipe parsing module 320 includes:

[0120] A parsing unit, used to parse each recipe parameter in the recipe file to determine the configuration data corresponding to each recipe parameter;

[0121] The determination unit is used to determine the parsed data of the recipe file according to each of the recipe parameters and the corresponding configuration data.

[0122] Optionally, if the recipe file is a streaming recipe file, each recipe parameter of the streaming recipe file includes: a data header, a data footer, a first data input item, a first data output item and a first system recipe flag;

[0123] If the recipe file is a frame-type recipe file, each recipe parameter of the frame-type recipe file includes: a second data input item, a second data output item and a second system recipe flag, wherein the second data input item includes: a data identification number.

[0124] Optionally, the determining unit is specifically configured to:

[0125] For a streaming recipe file, determining first parsed data of the recipe file according to configuration data corresponding to the first data input item; determining second parsed data of the recipe file according to configuration data corresponding to the first data output item;

[0126] For a frame-type recipe file, first parsed data of the recipe file is determined according to configuration data corresponding to the second data input item; and second parsed data of the recipe file is determined according to configuration data corresponding to the second data output item.

[0127] Optionally, the data access module 330 is specifically used to:

[0128] If the configuration data corresponding to the system recipe flag is system data, then updating the first target data in the system data area of ​​the robot according to the first parsed data;

[0129] Reading first target data in the system data area of ​​the robot according to the second parsed data, and sending the first target data to the user terminal;

[0130] The system formula identifier includes: a first system formula identifier and a second system formula identifier.

[0131] Optionally, the data access module 330 is further used to:

[0132] If the configuration data corresponding to the system recipe flag is custom data, calling a custom update function according to the first parsed data, and updating the second target data in the custom data area in the robot based on the custom update function;

[0133] calling a custom read function according to the second parsed data, reading second target data in the custom data area in the robot based on the custom read function, and sending the second target data to an external user device;

[0134] The system formula identifier includes: a first system formula identifier and a second system formula identifier.

[0135] The above-mentioned product can execute the robot access method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0136] Embodiment 4

[0137] Figure 7 This is a schematic diagram of the structure of a robot in Embodiment 4 of the present invention. Figure 7 A block diagram of an exemplary robot 12 suitable for use in implementing embodiments of the present invention is shown. Figure 7 The robot 12 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0138] like Figure 7 As shown, the robot 12 is embodied in the form of a general purpose computing device. The components of the robot 12 may include, but are not limited to: one or more processors or processor 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processor 16).

[0139] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0140] The robot 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the robot 12, including volatile and non-volatile media, removable and non-removable media.

[0141] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The robot 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 7 not shown, usually called a "hard drive"). Although Figure 7Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0142] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0143] The robot 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), and may also communicate with one or more devices that enable a user to access the robot 12, and / or any device that enables the robot 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. In addition, in the robot 12 of this embodiment, the display 24 is not present as an independent entity, but is embedded in the mirror surface. When the display surface of the display 24 is not displayed, the display surface of the display 24 is visually integrated with the mirror surface. In addition, the robot 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the robot 12 via a bus 18. It should be understood that although not shown in the figures, other hardware and / or software modules can be used in conjunction with the robot 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0144] The processor 16 executes various functional applications and data processing by running the program stored in the system memory 28, for example, implementing the robot access method provided in the embodiment of the present invention: obtaining a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; parsing the recipe parameters in the recipe file to determine the parsed data of the recipe file; and accessing the robot based on the parsed data.

[0145] Embodiment 5

[0146] Embodiment 5 of the present invention provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the method for accessing a robot as provided in all the embodiments of the invention of this application is implemented: obtaining a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; parsing the recipe parameters in the recipe file to determine parsed data of the recipe file; and accessing the robot based on the parsed data.

[0147] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0148] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0149] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0150] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0151] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A robot access method, characterized in that: include: Obtaining a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; Parsing the recipe parameters in the recipe file to determine parsed data of the recipe file; accessing the robot based on the parsed data; The accessing the robot based on the parsed data comprises: If the configuration data corresponding to the system recipe flag is system data, then updating the first target data in the system data area of ​​the robot according to the first parsed data; Reading first target data in the system data area of ​​the robot according to the second parsed data, and sending the first target data to the user terminal; Among them, the system recipe flag includes: a first system recipe flag and a second system recipe flag; the first parsed data is determined according to the configuration data corresponding to the data input item of the recipe parameter, and the second parsed data is determined according to the configuration data corresponding to the data output item in the recipe parameter.

2. The method according to claim 1, characterized in that The step of obtaining the recipe file input by the user comprises: Acquire the recipe file input by the user in the external user device through the external interface; The recipe file is a file obtained after a user configures recipe parameters in a recipe template file, and the recipe template file is determined based on a protocol of the external interface.

3. The method according to claim 1, characterized in that The step of parsing the recipe parameters in the recipe file to determine parsed data of the recipe file includes: Parsing each recipe parameter in the recipe file to determine the configuration data corresponding to each recipe parameter; The parsed data of the recipe file is determined according to each of the recipe parameters and the corresponding configuration data.

4. The method according to claim 3, characterized in that: If the recipe file is a streaming recipe file, each recipe parameter of the streaming recipe file includes: a data header, a data footer, a first data input item, a first data output item and a first system recipe flag; If the recipe file is a frame-type recipe file, each recipe parameter of the frame-type recipe file includes: a second data input item, a second data output item and a second system recipe flag, wherein the second data input item includes: a data identification number.

5. The method according to claim 4, characterized in that Determining the parsed data of the recipe file according to each of the recipe parameters and the corresponding configuration data includes: For the streaming recipe file, determining first parsed data of the recipe file according to the configuration data corresponding to the first data input item; determining second parsed data of the recipe file according to the configuration data corresponding to the first data output item; For the frame-type recipe file, the first parsed data of the recipe file is determined according to the configuration data corresponding to the second data input item; and the second parsed data of the recipe file is determined according to the configuration data corresponding to the second data output item.

6. The method according to claim 5, characterized in that Accessing the robot based on the parsed data further includes: If the configuration data corresponding to the system recipe flag is custom data, calling a custom update function according to the first parsed data, and updating the second target data in the custom data area in the robot based on the custom update function; calling a custom read function according to the second parsed data, reading second target data in the custom data area in the robot based on the custom read function, and sending the second target data to an external user device; Wherein, the system recipe mark includes: a first system recipe mark and a second system recipe mark.

7. A robot access device, characterized in that: include: A recipe acquisition module is used to acquire a recipe file input by a user, wherein the recipe file is obtained by configuring recipe parameters by the user; A recipe parsing module, used to parse the recipe parameters in the recipe file to determine parsed data of the recipe file; A data access module, for accessing the robot based on the parsed data; The data access module is specifically used for: If the configuration data corresponding to the system recipe flag is system data, then updating the first target data in the system data area of ​​the robot according to the first parsed data; Reading first target data in the system data area of ​​the robot according to the second parsed data, and sending the first target data to the user terminal; Among them, the system recipe flag includes: a first system recipe flag and a second system recipe flag; the first parsed data is determined according to the configuration data corresponding to the data input item of the recipe parameter, and the second parsed data is determined according to the configuration data corresponding to the data output item in the recipe parameter.

8. A robot comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Citation Information

Patent Citations

  • Robot and simple configuration method based on robot common platform

    CN108445840A