Systems and methods for dynamically configuring communication data elements

The system dynamically configures data elements using a data configurator and design tool, addressing the need for flexible data format adaptation across devices without altering software or firmware, enhancing efficiency and compatibility.

DE102013104786B4Active Publication Date: 2024-11-07COGNEX CORP
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
DE102013104786
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2012-05-10
Filing Date
2013-05-08
Publication Date
2024-11-07
Estimated Expiration
2033-05-08

AI Technical Summary

Technical Problem

Existing communication protocols require costly and time-consuming software/firmware changes to accommodate customer-specific data format requests, limiting flexibility and compatibility across devices.

Method used

A system and method for dynamically configuring data elements using a data configurator and design tool that maintains independence from the underlying communication protocol, allowing users to define data formats and content without altering device software or firmware.

Benefits of technology

Enables flexible and efficient data reconfiguration across devices, reducing costs and time associated with custom software changes while maintaining protocol compliance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Device for reconfiguring data transmitted over a production and / or automation network (22), wherein the network (22) uses a communication protocol and the device comprises the following: a processor (32), and a storage medium (40) accessible through the processor (32), wherein the processor (32) is configured to receive data from a second device in the network; a data configurator (76), wherein the data configurator (76) is configured to dynamically reconfigure the data from the second device (62, 82, 84), wherein the data from the second device (62, 82, 84) have the form of a network element defined by the second device (62, 82, 84), and wherein the data configurator (76) is configured to transfer the reconfigured data to at least either the processor (32) or the storage medium (40) in the form of a device element inherent in the device (24); and a mapping entry, wherein the mapping entry is used by the data configurator (76) and defines a unique relationship between the network element and the device element, wherein the figure entry includes a network representation section for data in the network element and a device representation section for data in the device element.
Need to check novelty before this filing date? Find Prior Art

Description

BACKGROUND OF THE INVENTION

[0001] The present invention relates to data elements and in particular to the configuration of communication data elements.

[0002] A communication protocol can be described as a system of digital message formats and rules. The protocol is used to exchange digital messages between devices in a network that are capable of transmitting and / or receiving the specified message format. These messages are sent and received by devices in the network to establish communication and exchange data between them. The communication protocol defines the rules for this message transmission, including the transmission of data elements. Therefore, there are various types of communication protocols designed to transport predefined data elements between two or more devices in the network.A manufacturer or vendor of a device using such a protocol typically configures the device software and / or firmware responsible for the data elements to generate a specified form of data elements so that the vendor's device is able to transmit and receive information in a configuration that is most efficient for the device and within the rules of the communication protocol.

[0003] However, it is possible that some customers with devices on their network that connect to, and thus communicate with, the vendor's device may prefer to use a form of data element that differs from the pre-configured and fixed data elements used by the vendor. Accordingly, the customer may request that the vendor's device support a modified or entirely different data element format to facilitate improved communication efficiency, ensure compatibility with successor devices, or maintain compatibility with competitor devices.To accommodate a customer requesting a change to the pre-configured and fixed data element format of the device vendor, the vendor must, in most cases, make specific modifications to the vendor's device software and / or firmware. Software / firmware modifications are costly, time-consuming, and difficult to manage because they are tailored to the customer's specific request and are rarely transferable for use by other customers. For these reasons, most vendors are reluctant to make such individual modifications for a single customer.

[0004] Areas where communication protocols are commonly used include manufacturing and automation. For example, some well-known protocols used for communication between devices include EtherNet / IP, Profinet, CIP, and ModbusTCP. A manufacturing / automation network can also encompass a wide range of devices, including computers, robots, machines, sensors, and countless other types.

[0005] An example of a field that can use communication protocols for communication and data transmission is machine vision and image processing analytics. In its simplest form, machine vision is commonly used to examine and / or locate an object. For example, in manufacturing applications, image processing analytics can be used to detect defects in a manufactured object by capturing images of the object and using various types of image processing algorithms to analyze the images. For instance, a system for producing electrical components such as resistors can use machine vision to examine the resistors to identify manufacturing defects and ensure that the resistor is properly labeled or color-coded.A large amount of data can be collected and analyzed during the image processing process. Not only do some or all of this data need to be communicated to other devices, but instructions and other application-related data can also be communicated to and from the image processing system.

[0006] Data conversion units and industrial gateway devices are available that allow a user to convert data from one device, which uses a different data format, to another device, which uses a different data format. These systems are primarily available in the field of information processing systems or database systems and mainly serve the purpose of converting data once from one system to another. However, these systems do not address the problem of reconfiguring communicated data elements defined by the device vendor.

[0007] There are other system specifications that are more focused on production and automation applications, such as OLE for Process Control (OPC) and the Common Industrial Protocol (CIP). OPC provides an open standard specification for data communication and data access. The OPC specification allows users to dynamically select which data elements they wish to transmit; however, it does not provide a means to dynamically change the format or value of a data element. Similarly, CIP includes a specification for dynamic arrangements; however, much like OPC, it does not allow data type or value conversion, such as reversing a bit array to an integer or values. Further state of the art is known from US 2012 / 0033850 A1, US 2011 / 0007665 A1 and EP 0 895 196 A1.

[0008] Systems and procedures are needed that enable dynamic configuration of data content and data formats while maintaining independence from the underlying communication protocol. SUMMARY OF THE INVENTION

[0009] The present embodiments overcome the disadvantages of the prior art by providing systems and methods for dynamically configuring the content and / or format of data elements transmitted over a network, while maintaining independence from the underlying communication protocol and simultaneously adhering to the protocol rules for data transmission. The communication protocol defines how the data elements are transmitted over the network, while the vendor defines the data content and data format.

[0010] The systems and methods for reconfiguring data transmitted over a network using a communication protocol include a processor and a storage medium. The processor can be operated to receive data from a second device in the network. The systems and methods include a data configurator that can be operated to dynamically reconfigure the data from the second device, wherein the data from the second device has the form of a network element defined by the second device. The data configurator can be operated to forward the reconfigured data to at least either the processor or the storage medium in the form of a device element inherent to the device. The data configurator uses a mapping entry, wherein the mapping entry defines a unique relationship between the network element and the device element.The figure entry includes a network representation section for data in the network element and a device representation section for data in the data element.

[0011] The systems and procedures include a data design tool that provides the user with the means to define the relationship between a network element and one or more device elements. The data design tool generates and stores the configuration information selected by the user, which can be processed by the data configurator at runtime to create the mapping entries.

[0012] As described above, some embodiments include a method for reconfiguring communication data from a first device in a network and for providing the reconfigured data to a second device in the network.The method involves starting a data configurator, which can be operated on the second device; receiving configuration information to reconfigure a selected data element according to a configuration mode; generating a mapping entry for the selected data element; starting the runtime operation of the second device; receiving a transmitted network element, including the selected data element, by the data configurator during runtime; reconfiguring the selected data element from the transmitted network element according to the mapping entry; and forwarding the reconfigured, selected data element to an application on the second device.

[0013] Other embodiments include a method for reconfiguring data elements using a data configurator.The method involves starting a data design tool, wherein the data design tool resides in memory in a first device connected to a network, the first device containing a user interface; selecting a data element for reconfiguration from a second device connected to the network; generating a mapping configuration, the mapping configuration comprising a network representation section and a device representation section; saving the mapping configuration; forwarding the mapping configuration to a third device in the network, the third device containing the data configurator; and dynamically reconfiguring the selected data element from the second device according to the mapping configuration using the data configurator.

[0014] To achieve the objectives described above and those associated with them, embodiments of the invention therefore include the features described in full below. The following description and the accompanying drawings detail certain exemplary aspects of the invention. However, these aspects only reveal some of the possible applications of the fundamental principles of the invention. Further aspects, advantages, and novel features of the invention will become clear from the following detailed description of the invention in conjunction with the examination of the drawings. Brief description of the different drawing views Fig. Figure 1 is a schematic view of a system according to the present embodiments comprising devices in a network, a data design tool and a data configurator set up for restructuring data elements; Fig. 2 is a block diagram view of the data configurator located on a device, the device communicating with another device via a network; Fig. 3 is a block diagram view similar to Fig. 2, apart from the fact that it shows another detail, the data flow; Fig. Figure 4 is a block diagram view of a data mapping configuration mode available for restructuring the data elements, according to the present embodiments; Fig. Figure 5 is a block diagram view of a data type conversion configuration mode available for restructuring the data elements, according to the present embodiments; Fig. Figure 6 is a block diagram view of a logical data manipulation configuration mode available for restructuring the data elements, according to the present embodiments; Fig. 7 and Fig. Figure 8 shows block diagram views of a network element reconfiguration in which a network element is reconfigured into individual device elements according to figure entries and then transferred to a user's device, according to the present embodiments; Fig. Figure 9 is a block diagram view of a network element reconfiguration similar to Fig. 7 and Fig. 8, apart from the fact that the network element is reconfigured into individual device elements according to mapping entries and logic elements and is subsequently transferred to a user's device, according to the present embodiments; Fig. Figure 10 is a block diagram view of an exemplary figure entry, according to the present embodiments; Fig. Figure 11 is a block diagram view of an exemplary mapping from a network element to a device element; Fig. Figure 12 is a block diagram view of an exemplary mapping from a device element to a network element; Fig. Figure 13 is a block diagram view of an image list in the form of a hierarchical tree structure, wherein the tree structure consists of a tree structure with sublists, according to the present embodiments; Fig. 14 is a flowchart of an application procedure associated with the data design tool; and Fig. Figure 15 is a flowchart of an application procedure associated with the data configurator.

[0015] Although various modifications to the invention and alternative embodiments are possible, certain embodiments of the invention have been illustrated by way of example in the drawings and are described in detail herein. It should be noted, however, that the description of certain embodiments contained herein is not intended to limit the invention to the embodiments disclosed herein, but rather to cover all modifications, correspondences, and alternatives that fall within the scope of the invention and its conception, as defined in the accompanying claims. DETAILED DESCRIPTION OF THE INVENTION

[0016] The various aspects of the present invention are described below with reference to the accompanying drawings, where similarly named reference numerals correspond to similar elements in the different views. It should be noted, however, that the drawings and the subsequent detailed description relating to them are not intended to limit the claimed subject matter to the embodiment disclosed herein. Rather, they are intended to cover all modifications, correspondences, and alternatives that fall within the scope of the invention and the claimed subject matter.

[0017] The terms "component," "system," and similar terms used here refer to a processor-related entity, whether hardware, a combination of hardware and software, software, or software in execution. For example, a component, without being limited to these embodiments, can be an operation running on a processor, a processor, an object, a program file, an execution thread, a program, and / or a computer. For illustration, both an application running on a computer and the computer itself can be a component. One or more components can reside in a processor and / or execution thread, and a component can be located on a computer and / or distributed between two or more computers or processors.

[0018] The word "exemplary" is used here to express that something serves as an example, case study, or illustration. Each aspect or execution described here as "exemplary" is not necessarily intended to be preferred or advantageous over other aspects or executions.

[0019] Furthermore, the disclosed subject matter can be implemented as a system, method, device, or production article using standard programming and / or process techniques to produce software, firmware, hardware, or any combination thereof, to control a computer- or processor-based device, in order to implement aspects described in detail herein. The term "production article" as used here is intended to encompass a computer program that can be accessed by any computer-readable device, data carrier, or media. For example, computer-readable media, without being limited to these embodiments, can include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips, etc.), optical storage media (e.g., compact discs (CDs), DVDs, etc.), chip cards, and devices with flash memory (e.g., cards, USB drives).Furthermore, it should be noted that a carrier wave can be used to transmit computer-readable electronic data, such as that used for sending and receiving emails or for accessing a network like the internet or a local area network (LAN). It goes without saying that those skilled in the art will recognize many modifications that can be made to these statements without deviating from the scope or inventive concept of the claimed subject matter.

[0020] Embodiments of the invention are described below by means of diagrams to illustrate either the structure or the processing of embodiments used to implement the systems and methods of the present invention. This use of diagrams to present embodiments of the invention should not be interpreted as limiting its scope. The present invention includes both methods and systems for dynamically configuring data elements. The embodiments of the present invention may include a device, such as an automation device, a specialized or general-purpose computer including various types of computer hardware, software, and / or firmware, etc., as discussed in more detail below.

[0021] The various embodiments of the invention are described in connection with an image processing system comprising one of a plurality of devices in a network. In some embodiments, the image processing system includes a data configurator and a data design tool used to dynamically configure the content and format of a device element used by the image processing system, while maintaining independence from the underlying communication protocol rules, although these rules are still adhered to. This is because the features and advantages of the invention are well suited for this purpose. Nevertheless, it should be noted that the various aspects of the invention can be applied in other forms and in other devices capable of utilizing a communication protocol.

[0022] An exemplary image processing system may use image processing software that can be operated to perform various types of image analysis or image processing functions or algorithms when examining a captured image of an object. Any type of camera or other device can be used to capture the images to be analyzed in an image processing application, including digital cameras, line scan cameras, infrared imaging devices, X-ray imaging devices, ultrasound imaging devices, and any other type of device that can be operated to receive, generate, process, or capture an image or sensor data. As is known to those skilled in the art, the image acquisition, image analysis, and / or image processing functions described above involve the generation and transmission of data.

[0023] Fig. Figure 1 shows an exemplary image processing system 20 connected to a network 22, such as a local area network (LAN), a wide area network (WAN), a wireless network, or the Internet, to which the teaching of this invention can be applied. The image processing system 20 can be used, among other things, but not exclusively, in a manufacturing, testing, measurement, automation, and / or control application. It should be noted that the teaching described and claimed herein, although the description refers to an image processing system as an exemplary operational implementation, can expressly be applied to a wide range of devices capable of communicating data elements over a network using a communication protocol.Therefore, the systems and procedures described herein should be understood as broadly applicable to systems or devices of all kinds that require the communication of data elements over a network by means of a communication protocol.

[0024] The image processing system 20 includes an imaging device 24 coupled to a computer system 28. The term "imaging device" as used here is intended to encompass various types of devices that can be operated to capture and / or store an image and that may include in-device processing capabilities. An imaging device can thus also be operated to analyze or process the captured or stored image. Examples of an imaging device include analog and digital cameras with in-device processors and other similar types of devices.

[0025] Thus, it shows Fig. 1 An exemplary image acquisition or image processing system 20, wherein the imaging device 24 may include a processor 32, a storage medium 40, and an image processing application 36 for performing an image processing function. The imaging device 24 may be coupled to the computer 28 by means of a serial bus, a network, wired or wirelessly, or by other means 42.

[0026] The term "processor" as used here can include one or more processors and memory and / or one or more programmable hardware elements. The term "processor" as used here is intended to include any type of processor, CPUs, microcontrollers, or other devices capable of executing software instructions. The term "programmable hardware element" as used here is intended to include various types of programmable hardware, reconfigurable hardware, programmable logic, or field-programmable devices (FPDs), such as one or more FPGAs (field-programmable gate arrays) or one or more PLDs (programmable logic devices), such as one or more SPLDs (simple PLDs) or one or more CPLDs (complex PLDs), or other types of programmable hardware.

[0027] The computer 28 or other computing device is shown coupled to the imaging device 24. The computer 28 is shown with a processor 38 and user interface components, such as, though not required, a mouse 44, a keyboard 46, and a screen 50. Other types of computing devices and interfaces may also be used, such as a personal digital assistant (PDA), a laptop, a human-machine interface, or a tablet computer in various embodiments. In some embodiments, the imaging device 24 may be permanently coupled to the computer 28, particularly if the computer performs one or more data configuration and / or image processing functions. Alternatively, the processor 32 in the imaging device 24 typically allows the device 24 to operate independently without being permanently coupled to a computer 28.In this embodiment, the computer 28 can be coupled to and / or communicate with the imaging device 24 and the associated image processing application 36, for example, for device setup, testing, and runtime analysis. The computer 28 can also be operated with the imaging device 24 to analyze, measure, or control other devices or processes. In other embodiments, the computer 28 can be omitted; that is, the imaging device 24 can be operated completely independently of the computer.

[0028] The computer 28 can include the processor 38 for executing computer programs and a storage medium 54 on which computer programs can be stored. In one embodiment, another storage medium 58 can be located on a second computer 62, which is connected via the network 22 to the imaging device 24 or to the computer 28. In this case, the second computer 62 can be operated to provide program instructions and / or data to the imaging device 24 or the computer 28 for execution via the network 22.

[0029] With further reference to Fig. 1. The imaging device 24 can also include a storage medium 40 on which computer programs, e.g., text-based or graphical programs, can be stored. In other embodiments, configuration information can be stored which can be used to configure a programmable hardware element, such as an FPGA, present in the imaging device 24 or the computer 28, to perform, among other things, a measurement, control, automation, or analysis function.

[0030] The term "storage medium" as used here includes non-volatile storage media, such as magnetic recording media or hard drives, optical storage media, or flash memory; volatile storage media, such as computer system memory, e.g., main memory (RAM) such as DRAM, SRAM, EDO RAM, RAMBUS RAM, DR RAM, etc.; or installation media, such as software media, e.g., CD-ROMs or floppy disks, on which computer programs can be stored and / or data communications can be temporarily stored. The term "storage medium" can also include other types of storage or combinations thereof.

[0031] In the exemplary image processing system 20 shown, a conveyor system 70 can be used to move a large number of objects 72. These objects, in turn, pass through a field of view (FOV) of the imaging device 24, so that their time-of-flight images can be captured and examined, e.g., for manufacturing defects and / or other relevant features during an inspection process. Therefore, the imaging device 24 can capture one or more images of an inspected object 72.

[0032] In some embodiments, a data configurator 76 can be located in and / or operate within the imaging device 24. The data configurator 76 can also be part of the image processing application 36 and can be accessible via the computer 28. In other embodiments, the data configurator 76 can be located in and / or operate within the computer 28, or it can include components that are located in and / or operate within both the imaging device 24 and the computer 28.

[0033] In some embodiments, a data design tool 78 may be located in and / or operate within the computer 28. In other embodiments, the data design tool 78 may be part of the image processing application 36 and may be located in and / or operate within the imaging device 24 and may be accessible via the computer 28. In other embodiments, the data design tool 78 may include components that are located in and / or operate within both the imaging device 24 and the computer 28. The data design tool 78 may be operated to provide the user with the means to define the relationship between a network element and one or more device elements. The data design tool 78 may generate and store the configuration information selected by the user, which may be processed at runtime by the data configurator 76 to generate an imaging entry (discussed below).

[0034] In the described embodiment, the data design tool 78 can be an offline tool that a user employs to enter and save some or all of the configuration information used by the data configurator to reconfigure data. In some embodiments, the data design tool 78 can be used for design and / or setup, and the data configurator can be an online tool, i.e., a runtime tool.

[0035] The embodiments of the data configurator 76 and the data design tool 78 described herein provide a customizable restructuring of data, including the ability to configure the division, content and value of the communicated data, without any modification of the software and / or firmware of the transmitting or receiving device.Essentially, by using the data design tool 78 to define the relationship between a network element and one or more device elements, the data configurator 76 is able to use the defined relationship to map data that is externally visible in the network 22 (described as a network element) to the data content and data format inherent to a vendor's device (described as a device element), and vice versa. The user is no longer restricted to the vendor's pre-programmed data format. The user can now define their own preferred data format and continue to work with the vendor's device without the vendor having to create custom software and / or firmware.

[0036] The network element being reconfigured need not be based on communication protocol rules, i.e., EtherNet / IP or Profinet rules, but rather consists of one or more predefined device elements that are statically located within a defined structure and transmit and / or receive data over a network. The device element is defined by the device vendor.

[0037] The communication protocol defines how network elements are transmitted across the network, but the device vendor defines the data content and format. Therefore, to remain independent of the protocol, the device elements are defined in a protocol-independent manner. Mapping device elements to network elements may depend on the communication protocol, but the data elements themselves are generally not protocol-based, as they are not part of the protocol.

[0038] The data design tool 78 can include and / or interact with a user interface mechanism 80, such as a graphical user interface, or a keyboard 46 and a screen 50, to allow a user to generate commands for the data configurator 76 regarding which data should be restructured and how, without the need for one-off firmware changes to be implemented in response to individual customer requests. Therefore, the user is able to provide configuration information to the data configurator 76 to generate one or more mapping entries and / or logic elements, which are discussed in more detail below, that are used to restructure data according to their specific requirements. The data configurator 76 then performs the data manipulation at runtime.

[0039] For example, the vendor of the device, in this exemplary embodiment the vendor of the image processing system 20, defines one or more device elements in advance for the imaging device 24. A device element can comprise any number of data forms and / or types. For example, a device element can be a device command, a device event, and / or device values. In one example, a value (usually a single bit) can be used to indicate the occurrence of an event. In another example, the current speed of a motor can be considered value data.

[0040] When using it, a user will connect from one of the others connected to a hub 86 in the network 22 (see Fig. 1) Devices 62, 82 and / or 84 are now able to instruct the data configurator 76 to restructure data from the user's device 82 so that the data is ultimately in the form of the vendor's predefined device elements. For example, the user's device 82 generates data that can then be transmitted via network 22 to the imaging device, i.e., the vendor's device 24, where the data configurator 76 is able to restructure the data from the user's device so that it is in the form of the vendor's predefined device elements.

[0041] The data configurator 76 can be instructed to restructure data in a variety of ways. In an exemplary embodiment, the data configurator can utilize any combination of three different configuration modes capable of restructuring data, although further modes are included within the scope of the invention. The exemplary configuration modes include data mapping 88, data type conversion 90, and logical data manipulation 92. Each mode is described in more detail below.

[0042] With reference to Fig. 3. A network element 98 is generated by a user's device 82 and then forwarded to the communication protocol 100 for transmission to the vendor's device 24 in the network 22. The network element 98 is received by the communication protocol 104 in the vendor's device 24. Protocol 104 then forwards the network element to the data configurator 76. The data configurator 76 now restructures the network element into one or more device elements using one of the configuration modes described below and forwards the device elements to the image processing application 36 in the vendor's device 24, for example, to be billed by the image processing application 36.It must be noted that the data configurator 76 is also able to receive device elements from the image processing application 36 in the vendor's device, restructure the device elements into a network element, and forward the network element to the communication protocol 104 so that the protocol can transmit the restructured data via the network 22 to the user's device 82.

[0043] In the following examples, a network element is a structure made up of individual data elements, as depicted in network 22. Referring to Fig. Section 4 now shows a simplified representation of a data mapping as a restructuring of a network element 98 into a device element 102. In this example, both the network element 98 and the device element 102 have the form of a known data structure, but this is not a requirement, since Fig. 5 and Fig. 6 individual device elements that do not have the form of a data structure.

[0044] Network element 98 is represented by five individual data elements 94. The data elements 94 can be restructured during the communication process. Using the data configurator 76 for data mapping, part or all of the content of network element 98 can be restructured, i.e., mapped, into / onto device element 102. As can be seen in device element 102, the structure of the transmitted individual data elements 94 has been restructured in device element 102, and the number of transmitted individual data elements 94 has been reduced from five to three individual data elements 96.

[0045] Likewise and as in Fig. As shown in Figure 5, a data type conversion refers to the conversion of conventional data types. Fig. Figure 5 shows a network element 106 that contains five individual data elements 110. Each of these five individual data elements 110 can be recognizably transformed within the communication process. Fig. Figure 5 shows an example of data transformation using the data configurator 76, in which part or all of the content of the transmitted network element 106 can be restructured, i.e., transformed, into a plurality of device elements 114, 116, 118, wherein selected individual data elements 110 were transformed into the individual device elements 114, 116, 118. The individual data elements 110 were converted from 32-bit integer values ​​to 16-bit integer values, and the number of transmitted individual data elements 110 was reduced from five data elements to three device elements 114, 116, 118.

[0046] With reference to Fig. 6. Logical data manipulation now refers to changing a data value based on some kind of logical (AND, OR, exclusive OR, NOT, etc.) and / or arithmetic operators. Fig. Figure 6 shows a network element 122 that contains five individual data elements 126. Each of these five individual data elements 126 can be transparently manipulated during the communication process. Fig. Figure 6 shows an example of data manipulation using the data configurator 76, where part or all of the content of the transmitted network element 122 can be restructured, i.e., manipulated, into a multitude of device elements 130, 134. As can be seen with device elements 130, 134, the transmitted individual data elements 126 were manipulated using both logical and arithmetic operators (although both are certainly not required). Furthermore, the number of transmitted individual data elements 126 was reduced from five individual data elements to two device elements 130, 134.

[0047] As is evident, logical data manipulation (or any other configuration mode) also performs data type conversion in addition to logical and / or arithmetic operators. For example, a bit field can be converted to an integer field and vice versa. Furthermore, each configuration mode can be executed individually or in any combination.

[0048] Both the mapping and the logical functionality, as described above, can be used independently of the type and operation of the communication protocol. Therefore, this would not be tied to a specific type of connection or communication medium.

[0049] To enable the Data Configurator 76 to restructure data as described above, the Data Configurator 76 dynamically generates a single mapping entry 140. Information for generating the mapping entry 140 can be provided by the Data Design Tool 78. Each mapping entry 140 defines the unique relationship between selected data in a uniquely identified network element and an associated, uniquely identified device element. At runtime, the Data Configurator 76 uses the generated mapping entry 140 to restructure the user's transmitted network element. The protocol receives the network element and forwards it to the Data Configurator 76 for restructuring.

[0050] Before the underlying communication protocol starts and becomes operational, the vendor's device 24 typically performs an initialization action. Mapping entry 140 can be dynamically generated during this initialization action. It should be noted that the data configurator 76 is also capable of restructuring data from the vendor's device 24 so that the data can be transferred to the user's device 82 via network 22. Mapping entry 140 can generally be generated in such a way that various mapping entries can be configured without requiring any modifications to the device software and / or firmware.

[0051] The Fig. Figures 7 to 9 show a more detailed representation of the restructuring of network elements 98, 106 and 122, as described in the respective sections. Fig. 4-6 shown. With reference to Fig. Figure 7 represents network element 98 as a structure of data received by the communication protocol in the vendor's device 24. Each network element in the network is assigned a unique identifier, e.g., from 1 to 1+n. A mapping entry is generated for each individual data element in network element 98 that requires reconfiguration. Any number of mapping entries can be generated, with three mapping entries 140, 142, and 144 being shown. The plurality of mapping entries 140, 142, and 144 are shown to form an exemplary mapping list 148. The mapping list 148 can contain any number of mapping entries. As described above, each figure entry 140, 142, 144 defines the relationship between selected data 141, 143, 145 in the network element 98 and the associated device element 102 in the device 24 of the seller.A device element can be a real data element in the seller's device or a virtual data element, such as a logic element as described below.

[0052] During runtime, the data configurator 76 uses one or more of the mapping entries 140, 142, 144 from the mapping list 148 to manipulate the transmitted network element. For example, the transmitted network element 98 can be manipulated such that mapping entry 140 manipulates the data 141 so that it can be forwarded to the device element 102 in the vendor's device 24. Similarly, mapping entry 142 manipulates the data 143 so that it can be forwarded to the device element 102, and mapping entry 144 manipulates the data 145 so that it can be forwarded to the device element 102.

[0053] Fig. Figure 8 shows a more detailed representation of how in Fig. Figure 5 shows the restructuring of network element 106. Network element 106 represents a structure of data, as can be seen in network 22. Again, each network element in the network is assigned a unique identifier. A mapping entry is generated for each individual data element in network element 106 that requires reconfiguration. Any number of mapping entries can be generated, with three mapping entries 140, 142, and 144 being shown. The multitude of mapping entries 140, 142, and 144 are shown to form an example mapping list 148. The mapping list 148 can contain any number of mapping entries. As described above, each figure entry 140, 142, 144 defines the relationship between selected data 141, 143, 145 in the network element 106 and the associated device elements 114, 116, 118 in the vendor's device 24.

[0054] During runtime, the data configurator 76 uses one or more of the mapping entries 140, 142, 144 from the mapping list 148 to manipulate the transmitted network element. For example, the transmitted network element 106 can be manipulated so that mapping entry 140 manipulates the data 141 so that it can be forwarded to the device element 114 in the vendor's device 24. Similarly, mapping entry 142 manipulates the data 143 so that it can be forwarded to the device element 116, and mapping entry 144 manipulates the data 145 so that it can be forwarded to the device element 118.

[0055] Fig. Figure 9 shows a more detailed representation of how in Fig. Figure 6 shows the restructuring of network element 122. As discussed previously, data configurator 76 also allows the logical manipulation of data. For example, data configurator 76 allows a user to combine a variety of data elements into a new data element or to change the value of one data element based on the value of another.

[0056] Network element 122 represents a data structure, as can be seen in network 22. Each network element in the network is assigned a unique identifier. A mapping entry is generated for each data element in network element 122 that requires reconfiguration. Any number of mapping entries can be generated, with four mapping entries 140, 142, 144, and 150 being shown. The multitude of mapping entries 140, 142, 144, and 150 are shown to form an example mapping list 148. Mapping list 148 can contain any number of mapping entries.

[0057] Furthermore, one or more logic elements 172, 174 can be dynamically generated and are shown in addition to the figure list 148. Logic elements 172, 174 can contain any number of logical operations, one AND operation being shown in logic element 172 and two MULT operations being shown in logic element 174. The logic elements are generated generically, allowing a wide variety of logical operations to be configured without requiring any changes to the software or firmware. As described above, each figure entry 140, 142, 144, 150, together with logic elements 172, 174, defines the relationship between selected data 141, 143, 145, 147 in network element 122 and the associated device elements 130, 134 in the vendor's device 24.

[0058] During runtime, the data configurator 76 uses the generated logic elements 172 and 174 together with the mapping entries 140, 142, 144, and 150 to manipulate the transmitted network element 122. For example, the transmitted network element 122 can be manipulated so that the mapping entry 140 and the logic element 172 manipulate the data 141 so that it can be forwarded to the device element 130 in the vendor's device 24. Similarly, the mapping entries 142, 144, and 150 and the logic element 174 manipulate the data 143, 145, and 147 so that it can be forwarded to the device element 134 in the vendor's device 24.

[0059] Fig. Figure 9 also shows that a figure entry 140 can provide for the division of larger data elements 143, 145, 147 into smaller sub-elements 134, or vice versa, of small data elements 141 into larger aggregated data elements 130.

[0060] With reference to Fig. Figure 10 shows an example mapping entry 140. As described above, mapping entry 140 defines the unique mapping between the transmitted representation of data 141, for example, from network element 98, and the representation of a device element, for example, device element 102 in the vendor's device 24. The mapping entry includes a network representation section 176, a device representation section 178, and an option section 180. A single data element 141 represented in mapping entry 140 includes various data fields, including, for example, identifier (ID), offset, size, and type, for both network representation section 176 and device representation section 178.Element ID defines a unique element identification character, Element Offset defines an offset value in the network element 98, Element Size defines a size of the individual data element 141 in the network element 98, and Element Type defines one of the well-known, conventional data types, such as bit, unsigned byte, signed long, etc., and a special link type that provides a mapping link for hierarchical mappings (see . Fig. 14 and the discussion below). Various details can also be identified as option variables in option section 180, including, but not limited to, data flow direction, input / output, dummy data placeholders (do not map), and data reversal.

[0061] For example, it shows Fig. 11 a network representation and a device representation as defined by a mapping entry 140 in the mapping from a network element 182 to a device element 184. In this example, an array of four unsigned bits 186 from bit offset thirty-two 188 of the network element 182 is mapped to an unsigned byte 190 at bit offset eight 192 of the device element 184. Fig. Figure 12 shows an additional illustration example in which the entire device element 194, consisting of an unsigned integer value 196 with sixteen bits of bit offset zero, is mapped to the entire network element 198, consisting of a signed integer value 199 with thirty-two bits at bit offset zero.

[0062] As noted above, a list of figures can be structured, for example, as a hierarchical tree structure, a flat list, or a combination of both. The flat list configuration is a simple, straightforward list of figure entries, such as the one in Fig. 7. List of illustrations shown 148. With reference to Fig. 13. A hierarchical tree structure consists of a tree structure with sublists. The example hierarchical tree structure 200 consists of a flat list 204 with roots that organize an input sublist 208 and an output sublist 212 into separate tree branches. This type of configuration can be used to speed up processing by eliminating the requirement to search for each mapping entry in a single flat list. The form of the hierarchical tree structure is more complex, but it allows data to be structured into logical groups. Such groups can be defined for any application purpose, such as increasing processing speed.

[0063] The Fig. 14 and Fig. Figure 15 shows embodiments of methods for using the data configurator 76 and the data design tool 78 to manipulate data. The illustrated methods can be used, among other things, with any of the computer systems or devices shown in the preceding figures. In various embodiments, some of the illustrated method elements can be executed simultaneously, in a different order than shown, or can be omitted. Additional method elements can also be executed if desired.

[0064] With reference to Fig. Figure 14 describes a procedure in which a user uses the data design tool 78 to generate commands for the data configurator 76 to prepare it for data conversion. A first step is to start the data design tool 78 as shown in Operation Block 220. The user can start the data design tool 78 using the computer 28 or, optionally, directly via an interface in the vendor's device 24. As discussed earlier, the data design tool 78 can reside in the storage medium 40 in the device 24 and / or in the storage medium 54 in the computer 28, and can accordingly be executed by the processor 32 in the device 24 and / or the processor 38 in the computer 28. Using the interface 80 shown on screen 50, the user can, for example, select data elements 141, 143, and / or 145, as shown in Operation Block 222.The selection process can optionally include providing data information for the network representation section 176, the device representation section 178, and the options section 180. The selected data elements are arranged to generate the configuration information for the data configurator 76, preparing it to perform data conversion using one or more mapping configurations, as shown in operation block 224. The user can also optionally generate one or more logical configurations 172. Either the data design tool 78 and / or the data configurator 76 can then generate a mapping list 148 containing the arranged mapping configurations. The user can then save the mapping list, the mapping configurations, and / or the logical configurations, as shown in operation block 226.All figure lists 148, figure configurations and / or logical configurations can be forwarded to the data configurator, as shown in operation block 228.

[0065] With reference to Fig.Figure 15 describes a procedure that outlines the steps performed by the data configurator 76. As shown in Operation Block 240, the data configurator 76 can be started using the data design tool 78. The data configurator 76 can then receive the mapping list 148, the mapping configuration, and / or the logical configuration information to reconfigure the selected data elements according to one of the available configuration modes, as shown in Operation Block 242. The mapping configurations and / or logical configurations can optionally include providing data information for the network mapping section 176, the device mapping section 178, and the options section 180. Based on the configuration information, a mapping entry 140 and / or a logic element 172 can be generated for each data element, as shown in Operation Block 244.Either the data design tool 78 and / or the data configurator 76 can generate the mapping entry 140 and / or a logic element 172 for each data element. The device runtime operation can then be started, as shown in operation block 246. During runtime, as shown in operation block 248, the data configurator 76 receives the transmitted network element 98 from the communication protocol 104, and in operation block 250, the data configurator 76 reconfigures the selected data elements from the network element according to the mapping entries and / or the logic elements. The manipulated data is forwarded in operation block 252 to the image processing application 36 in the vendor's device 24 to be received by the vendor's device in one or more device elements that were reconfigured from the transmitted network element.

[0066] Although the present invention has been described with reference to preferred embodiments, those skilled in the art will recognize that changes in form and details can be made without departing from the inventive concept and scope of the invention. For example, embodiments of the invention are not limited to the image processing systems and associated electronics described herein, but can be operated with numerous other devices capable of transmitting and / or receiving data in a network.

[0067] The specific embodiments disclosed above are merely examples, as the invention can be modified and applied in various, yet equivalent, ways, which those skilled in the art who benefit from the teaching disclosed herein will recognize. Furthermore, there are to be no restrictions on the design or execution details presented here other than those described in the claims below. Therefore, it is obvious that the specific embodiments disclosed above can be modified or altered, and all such modifications fall within the scope and inventive concept of the invention. Accordingly, the protection sought here corresponds to the claims below.

Claims

[1] Device for reconfiguring data transmitted over a production and / or automation network (22), wherein the network (22) uses a communication protocol and the device comprises: a processor (32), and a storage medium (40) accessible by the processor (32), wherein the processor (32) is configured to receive data from a second device in the network; a data configurator (76), wherein the data configurator (76) is configured to dynamically reconfigure the data from the second device (62, 82, 84), wherein the data from the second device (62, 82, 84) is in the form of a network element defined by the second device (62, 82, 84), and wherein the data configurator (76) is configured to transmit the reconfigured data to at least one of the processor (32) and the storage medium (40) in the form of a device element inherent in the device (24); and a mapping entry, the mapping entry being used by the data configurator (76) and defining a unique relationship between the network element and the device element, wherein the mapping entry includes a network representation portion for data in the network element and a device representation portion for data in the device element. [2] The apparatus of claim 1, further comprising a data design tool (78), wherein the data design tool (78) is configured to generate configuration information for the mapping entry including the network representation portion and the device representation portion. [3] The apparatus of claim 1 or 2, wherein the data configurator (76) dynamically reconfigures the data from the second device using at least one of a data mapping configuration mode, a data type conversion configuration mode, and a logical data manipulation configuration mode. [4] Apparatus according to any one of claims 1 to 3, wherein the mapping entry includes an options section. [5] The device according to any one of claims 1 to 4, wherein the network representation section and the device representation section each include at least one of an ID data field, an offset data field, a size data field, and a type data field. [6] Device according to one of claims 1 to 5, wherein the data configurator (76) is stored in the storage medium (40). [7] Apparatus according to any one of claims 1 to 6, wherein the apparatus (24) comprises an imaging device. [8] The device of any one of claims 1 to 7, wherein the processor (32) is configured to generate device data for communicating with the second device (62, 82, 84) in the network (22). [9] The device of claim 8, wherein the data configurator (76) is further configured to dynamically reconfigure the device data into a network element defined by the device, the device data being in the form of a vendor-predefined data element, and wherein the data configurator (76) is configured to forward the network element to the communication protocol for transmission to the second device (62, 82, 84). [10] Apparatus according to any one of claims 1 to 9, wherein a plurality of mapping entries are structured in a mapping list. [11] The apparatus of claim 10, wherein the mapping list comprises a hierarchical tree structure, wherein the hierarchical tree structure comprises a flat tree structure and a tree structure with sublists. [12] A method for reconfiguring communication data from a first device in a network (22) and providing the reconfigured data to a second device (62, 82, 84) in the network (22), the method comprising: Starting a data configurator (76), wherein the data configurator (76) is operated on the second device (62, 82, 84); Receiving configuration information for reconfiguring a selected data item according to a configuration mode; Creating a mapping entry for the selected data element; Starting a runtime operation of the second device (62, 82, 84); Receiving a transmitted network element including the selected data element by the data configurator (76) during runtime; Reconfiguring the selected data element from the transmitted network element according to the mapping entry; and Forwarding the reconfigured, selected data item to an application on the second device (62, 82, 84). [13] The method of claim 12, further comprising generating a logic element and reconfiguring the selected data element from the transmitted network element according to the mapping entry and the logic element. [14] The method of claim 12 or 13, further comprising receiving the reconfigured selected data item by the application on the second device (62, 82, 84) in a device element that was reconfigured from the transmitted network element. [15] The method of claim 14, wherein creating the mapping entry includes defining a unique relationship between the network element and the device element, the mapping entry including a network representation portion for data in the network element and a device representation portion for data in the data element. [16] The method of claim 15, wherein the network representation section and the device representation section each include at least one of an ID data field, an offset data field, a size data field, and a type data field. [17] A method for reconfiguring data elements using a data configurator, the method comprising: Starting a data design tool (78), the data design tool (78) being located in a memory in a first device coupled to a network (22); selecting a data item for reconfiguration from a second device coupled to the network (22); Creating a mapping configuration, the mapping configuration including a network mapping portion and a device mapping portion; storing the mapping configuration; forwarding the mapping configuration to a third device in the network, the third device including the data configurator (76); and dynamically reconfiguring the selected data element from the second device (62, 82, 84) according to the mapping configuration by means of the data configurator (76). [18] The method of claim 17, wherein dynamically reconfiguring the selected data element includes using at least one of a data mapping configuration mode, a data type conversion configuration mode, and a logical data manipulation configuration mode. [19] The method of claim 17 or 18, wherein the mapping configuration defines a unique relationship between a network element and a device element. [20] The method of any one of claims 17 to 19, wherein selecting the data item includes providing data information to the network representation portion and the device representation portion. [21] The method of any one of claims 17 to 20, further comprising using a user interface on the first device (24) to select the data item to reconfigure.

Citation Information

Patent Citations

  • Pattern data generator, pattern data generating method, and its medium

    EP0895196A1

  • Design and control systems, commissioning tools, configuration adapters and method for wireless and wired networks design, installation and automatic formation

    US20110007665A1

  • Methods and systems for optical asset recognition and location tracking

    US20120033850A1