Bus converter

Abstract

The invention relates to an apparatus for coupling a field bus to a local bus for connection with a data bus user device, comprising a field bus core, which can be connected to a field bus and is adapted to send and receive data via the field bus, a local bus core, which can be connected to a local bus and is adapted to send and receive data in at least one data packet via the local bus, and a data management unit, which is connected to the field bus core and the local bus core, the data management unit being adapted to transfer first symbols from data received via the field bus core into the local bus core in a sequence-dependent manner, so that the first symbols are transmitted to the local bus core in the same order as the symbols are received from the field bus core. Furthermore, the invention relates to a corresponding method for transmitting data.

Description

[0001] This case is a divisional application of the PCT invention patent for "bus converter", which entered the Chinese national phase on November 25, 2019, with national phase application number 201880034583.6 (international application number PCT / EP2018 / 062971, priority data DE102017208824.9, 2017.5.24). Technical Field

[0002] The present invention generally relates to an apparatus for connecting a fieldbus to a local bus, and more particularly to a bus converter for converting data streams from a fieldbus to a local bus. Background Technology

[0003] Devices that connect two bus systems are mainly used in automated equipment.

[0004] Automated equipment is used, in particular, to control factories, buildings, and vehicles. To control automated equipment, multiple sensors and actuators are typically required. These sensors and actuators monitor and control the processes performed by the equipment. Here, the different sensors and actuators of automated equipment are generally referred to as automation instruments.

[0005] These automated instruments can be directly connected to the control unit of automated equipment, or they can first be connected to input and output modules, which are usually called E / A modules. These modules can then be directly connected to the control unit.

[0006] Here, automated instruments can be directly integrated into the E / A module, or they can be connected to the E / A module via cable or wireless means.

[0007] The control unit of automated equipment typically functions using one or more Stored Programmable Controllers (SPSs). These SPSs can be arranged hierarchically or distributed throughout the automated equipment. Different performance levels exist within each SPS, allowing them to handle different controls and adjustments based on their computing and storage capacity. In its simplest form, the SPS has inputs, outputs, an operating system (firmware), and an interface through which a user program is loaded. The user program defines how the outputs are switched based on the inputs. These inputs and outputs can be connected to automated instruments and / or E / A modules, and the logic stored in the user program allows for the monitoring or control of processes performed by the automated equipment. Process monitoring is performed by sensors, and process control is performed by actuators. The control unit, also known as a central control unit or central unit, is responsible for controlling at least the automated instruments or E / A modules connected to it.

[0008] However, the direct connection between automated instruments and at least one control unit, or between an E / A module and at least one control unit, uses parallel wiring. This means a separate line is laid from each automated device or E / A module to the higher-level control unit, which is extremely cumbersome. Ironically, as the level of automation in automated equipment increases, the cost of parallel wiring also increases. This is related to the significant costs associated with planning, installation, commissioning, and maintenance.

[0009] Therefore, bus systems are commonly used in automation technology today, through which automation instruments or E / A modules can be connected to the control unit. These user devices of the bus system are also called bus user devices. Because data is exchanged on the bus system, bus user devices are often also called data bus user devices. To further simplify the connection of individual automation instruments or E / A modules to the bus system, groups of individual automation instruments or E / A modules are now first interconnected with a local bus system via a dedicated local bus, and then at least one user device on this local bus is connected to the bus system, which in turn connects to the control unit. Here, the local bus system may differ from the bus system used to achieve the connection with the control unit.

[0010] A user device that connects to a group of local bus user devices connected to the bus system of the control unit is typically referred to as a local bus host. Alternatively, the term "front end of the local bus system" may be used. Compared to other local bus user devices, the local bus host may contain additional logic, circuitry, or functions necessary for connection to the bus system of the control unit. Furthermore, the local bus host itself may include an SPS (Service Switch). The user device may also have logic and circuitry for conversion between two bus systems. Therefore, the local bus host can also be configured as a gateway or bus converter, ensuring that data in the bus system format is converted to the local bus system format and vice versa. However, in most cases, it is not mandatory that the local bus host is specifically designed to connect the local bus to the upper-level bus.

[0011] The local bus used is primarily coordinated to meet the specific application requirements of automation instruments or E / A modules, or taken into account their unique hardware design. Here, the groups of automation instruments or E / A modules in the local bus system typically form subgroups of automation equipment used to perform specific tasks during processes executed by the automation equipment. The data exchanged on the bus for the process is often referred to as local bus data or process data, as this data includes information for regulating or controlling the processes performed by the automation equipment. This data may in particular include measurement data, control data, status data, and / or other information. Depending on the bus protocol used, additional data (header) may be set before this data or additional data may be appended to these process data (tail).

[0012] This other data may include information about the data itself, or information about internal communications on the local bus. Various types of information are known here, which may be set before or appended to the process data depending on the bus protocol used. Local bus user devices connected to the local bus may also be called data bus user devices because these local bus user devices exchange data on the local bus. Here, data bus user devices control or monitor processes, in particular, by outputting control signals to actuators and / or by receiving measurement signals from sensors, for example. Data bus user devices convert control signals and / or measurement signals into data on the local bus, and vice versa.

[0013] Here, a ring bus is a special form of local bus, as known from US 5, 472, and 347A. In a ring bus, data bus user devices (e.g., automation instruments or E / A modules) are connected to their directly adjacent data bus user devices, and data is forwarded sequentially from one data bus user device to another. Data transmitted on the local bus can also be called local bus data. Therefore, not all data bus user devices transmit data simultaneously, but rather sequentially, where a data bus user device receives data from its upstream data bus user device and forwards it to its downstream data bus user device. Between data reception and forwarding, the data bus user devices can process the received data. When data reaches the last data bus user device in the sequence, data from the last data bus user device returns sequentially to the first data bus user device. Here, the return can be done by all data bus user devices or can be bypassed with the help of bypass routes. Therefore, a ring bus has both downstream and upstream data flows. Data in a ring bus is typically transmitted in the form of data packets passing through all data bus user devices.

[0014] In a ring bus, data packets are forwarded from one data bus user equipment (User Equipment) to another. At any given time, a Data Bus User Equipment always receives only a portion of the data packet from its upstream Data Bus User Equipment. Once the data contained in this portion has been processed by the Data Bus User Equipment, that portion is forwarded to the downstream Data Bus User Equipment, while the upstream Data Bus User Equipment receives new portions of the data packet. In this way, all portions of the data packet pass through all Data Bus User Equipment in sequence.

[0015] In known ring bus systems or other local bus systems, bus converters are used to convert data streams from the control unit into a local bus-compatible format. Here, high-performance controllers are typically used to reorder the data from the control unit in a local bus-compatible format, conforming to the order of data bus user devices on the local bus. This means that the reordered data order corresponds to the order in which the data bus user devices are arranged on the local bus. Due to this reordering, addressing can be eliminated in such bus systems because the data is arranged according to the physical location of the data bus user devices on the local bus. For example, data pointing to a first data bus user device is placed in a first location in a local bus-compatible format, data pointing to a second data bus user device is placed in a second location in a local bus-compatible format, and so on. To perform this conversion, especially the reordering, without significant latency, high-performance, high-clock controllers are mostly used in known systems. However, even with these high-performance controllers, latency can only be minimized to a certain extent. High-performance controllers also have several disadvantages; most require active cooling, have high power consumption, and are expensive.

[0016] Therefore, the object of the present invention is to provide an apparatus and a corresponding method by which data can be converted from a fieldbus to a local bus, and in particular to a ring bus, with almost no delay, and the conversion does not require any complex hardware. Summary of the Invention

[0017] The device according to the invention, also referred to as a bus converter or gateway, has a first unit that can be connected to a fieldbus and is adapted to send and receive data via the fieldbus. The fieldbus can be any bus that can be used in automated equipment and can be used to establish a connection with a control unit (e.g., SPS). Connections to the control unit can also be established via multiple different fieldbuses; even if the connection between the first unit and the control unit according to the invention consists of multiple different fieldbuses, the entire connection should be understood as a fieldbus connection. According to the invention, the first unit is adapted to connect to the fieldbus. For this purpose, the first unit can have an interface designed for the fieldbus. This interface can establish a connection with the fieldbus via wired or wireless means. Data streams can be received by the fieldbus and output to the fieldbus via the interface of the first unit or via the first unit itself. Due to its connectivity with the fieldbus, the first unit can also be referred to as a fieldbus core (FBC). The FBC can be constructed as a separate arithmetic logic unit, a computing core, or an arithmetic circuit designed as digital logic, particularly at least as part of a semiconductor chip. FBCs can be implemented in application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable circuits (PLDs) or discrete gate or transistor logic.

[0018] Furthermore, the apparatus according to the invention also includes a second unit that can be connected to a local bus, particularly a ring bus, and this second unit is adapted to send and receive data via the local bus in the form of at least one data packet. The data packet can also be called a telegram. The data packet has, for example, a header, a payload, and advantageously a checksum. The data packet is advantageously a communication data packet or a process data packet.

[0019] The communication data packets do not contain process data. Advantageously, the communication data packets contain data, particularly data for programming and / or control and / or monitoring and / or identification of at least one data bus user equipment. Advantageously, the communication data packets have an address assigned to at least one data bus user equipment. Preferably, the data bus user equipment is set to an evaluation address.

[0020] A process data packet contains process data sent and / or received by a data bus user device on the local bus. Advantageously, the process data packet does not have an address for sending process data to or from a data bus user device on the local bus. In the process data packet, the process data is arranged, for example, such that the data bus user device can identify the process data associated with the corresponding data bus user device based on the corresponding position of the process data in the process data packet, for example, within one or more bits in an associated contiguous data block (1 byte). Advantageously, the process data packet has an identifier (IDE) that is assigned to the type of the data packet, that is, assigned to the process data packet, and can be identified by the data bus user device. The process data may be referred to as local bus data.

[0021] The protocols used on the fieldbus and the local bus may be different, so without conversion, fieldbus-compatible formats cannot be sent to the local bus, and vice versa.

[0022] According to the present invention, the second unit is adapted to be connected to a local bus. For this purpose, the second unit may have an interface designed for the local bus. This interface can establish a connection with the local bus via wired or wireless means. Data packets can be sent to the local bus via the interface of the second unit or via the second unit itself, and data packets can be received by the local bus. Due to the connectivity of the second unit to the local bus, it can also be referred to as the Local Bus Core (LBC). The LBC can be constructed as a separate arithmetic logic unit, a computational core, or an arithmetic circuit designed as digital logic, particularly at least as part of a semiconductor chip. The LBC can be implemented in an ASIC, FPGA, or other PLD or discrete gate or transistor logic.

[0023] The apparatus according to the invention also includes a data management unit connected to the first and second units. The data management unit may also be referred to as a management unit (MU), and depending on its orientation, it may be called a fieldbus management unit (FMU) or a local bus management unit (LMU). The connection can advantageously be a parallel bus between the units, for example configured as a 32-bit parallel bus. The data management unit is adapted to transmit a first symbol from the data received by the first unit (FBC) to the second unit (LBC) in a sequence-dependent manner. In this case, sequence-dependent means that the symbols are transmitted to the second unit according to the order in which they are received from the first unit. Therefore, the order depends on the incoming symbols. For example, symbols received via the fieldbus can be transmitted sequentially to the second unit. Here, for example, the order of the symbols received via the fieldbus is not changed or is not significantly changed; that is, the symbols are also transmitted to the second unit in the order they are received on the fieldbus. It can also be said that since the order of the symbols is maintained, no reordering occurs. It can also be said that the symbols are transmitted one-to-one. Here, the transmitted symbols may be process data received from the control unit via the fieldbus in a fieldbus-compatible format. Here, the fieldbus-compatible format can have process data as well as other data preceding, appended to, or superimposed on the process data. This other data is, for example, bus-specific, while the process data is bus-neutral. In most cases, in the case of a fieldbus-compatible format, other data precedes the process data; this data may be called the header and is typically used for addressing and control. Additional data that can be appended to the process data for error detection may also be present. The process data is a component of the useful data portion (payload) of the fieldbus-compatible format. The process data is designed to elicit control, regulation, or other responses from the data bus user equipment on the local bus. For example, a fieldbus telegram can be received via the fieldbus, in which the process data is contained as symbols with a fixed number of bits, and wherein the symbols are arranged in a first order within the fieldbus telegram. The data management unit can here be adapted to transmit the symbols from the fieldbus telegram to the LBC in a second order. Preferably, the first and second orders of the symbols are consistent here.

[0024] The data management unit (FBC) can be adapted to transmit only process data. This means that the FBC or the first unit can already be adapted to select process data from fieldbus-compatible formats or fieldbus telegraphs. The FBC can be constructed as a separate arithmetic logic unit, a computational core, or an arithmetic circuit designed as digital logic, particularly at least as part of a semiconductor chip. The FBC can be implemented in an ASIC, FPGA, or other PLD or discrete gate or transistor logic. The FBC, LBC, and data management unit can also be implemented together in an ASIC, FPGA, PLD, or discrete gate or transistor logic. In particular, after transmission, the process data can be selectively modified by the local bus master using an manipulation unit. For this purpose, the local bus master advantageously has instructions that cause changes to the process data.

[0025] After the first symbol is transmitted to the LBC and a data packet carrying the transmitted symbol is generated, this data packet can be sent to the local bus in, for example, 8-bit (i.e., 1 byte) portions, and individual portions of this data packet can continuously pass through the data bus user equipment on the local bus. That is, at any given time, a data bus user equipment always receives only a portion of the data packet from its upstream data bus user equipment. Once the process data contained in this portion has been processed by the data bus user equipment, this portion is forwarded to the downstream data bus user equipment, while the upstream data bus user equipment receives new portions of the data packet. Here, the LBC and the local bus data bus user equipment can be clock-synchronized, so that when the LBC sends a new portion of the data packet to the local bus, the corresponding data bus user equipment also sends the current portion of the data packet to its downstream data bus user equipment. Here, the last data bus user equipment on the local bus can again send its current portion back to the LBC through all data bus user equipment or via a bypass route. Here, the LBC can be synchronized to the clock of the fieldbus, i.e., synchronized to the clock in the fieldbus telegraph received from the fieldbus on the FBC. Here, before the first symbol has been fully received by the FBC, the LBC can be adapted to output the start of the data packet already on the local bus.

[0026] Using the apparatus according to the invention, accelerated conversion from a data stream on the fieldbus to the local bus and vice versa can be achieved through the sequence-dependent transmission of process data. Here, the conversion of all necessary process data of the local bus user equipment is bus-neutral and performed with minimal delay and jitter. Since the conversion depends on the order but is always the same, it is advantageous that the data bus user equipment understands the order used, which may differ from the order of the data bus user equipment's physical location on the local bus. This understanding of the order enables the programming of the data bus user equipment so that it can retrieve the process data directed to it from data packets without reordering the process data. Here, the programming of the data bus user equipment can be performed, for example, via communication data packets sent by a second unit before the data packets carrying the process data.

[0027] In a preferred embodiment of the apparatus according to the invention, the data management unit is adapted to prepend and / or append and / or insert additional symbols into the first symbol. Here, it is conceivable that the other symbols are empty symbols, for example, when the local bus does not allow any gaps in the symbols, or when the LBC expects a certain number of symbols, but that number does not correspond to the number of the first symbols; these other symbols are used to account for integrity on the local bus. Here, the data management unit may also be adapted to insert additional symbols into the first symbol. The data management unit may also be adapted to remove unnecessary symbols from the first symbol.

[0028] In another preferred embodiment of the device according to the invention, the data management unit caches the first symbols. For example, the data management unit may cache the transmitted symbols in memory so that these symbols can be provided to the controller for evaluation.

[0029] Here, the controller is configured to transmit data not only between the FBC and LBC. By means of a buffer, transmitted symbols can be checked, for example, even without interruption of the data flow. Furthermore, the buffer also enables the delta adjustment of symbols to be performed before transmission on the local bus and after reception from the local bus. To buffer the transmitted symbols, the device according to the invention can have at least one volatile or non-volatile memory, such as pseudo-static dynamic random access memory. However, those skilled in the art will know that any other device for storing data for buffering can be used. Here, the device itself does not necessarily have to be part of the device, but can be externally held by the device or an additional module. The device, and especially the data management unit, only needs to access the device.

[0030] In another preferred embodiment of the apparatus according to the invention, the LBC is adapted to generate a data packet including a first symbol and transmit the data packet on a local bus. Here, the data packet can be transmitted symbol by symbol on the local bus. Here, the LBC can perform all necessary protocol-specific adaptations to transmit the data packet on the local bus. The LBC is also adapted to receive data packets from the local bus, wherein the received data packet may include a second symbol different from the first symbol. The LBC is also adapted to manipulate the first and / or second symbols. This manipulation can be performed bit by bit and can be used to adapt the first and second symbols according to the corresponding transmission direction.

[0031] In another preferred embodiment of the device according to the invention, the data management unit is used as a master unit. Here, the data management unit has a first master interface connected to the slave interface of the FBC, and a second master interface connected to the slave interface of the LBC. That is, the data management unit controls the transmission process of the first symbol between the FBC and the LBC by requesting a symbol from the FBC via the first master interface and transmitting the requested symbol to the LBC via the second master interface. Here, the data management unit has a first data transmission unit DTU0, wherein the DTU0 is adapted to read the first symbol from the buffer of the FBC via the first master interface based on a first instruction, and to write the first symbol into the buffer of the LBC via the second master interface. Here, the DTU0 is also adapted to send the validity of the first symbol written via the second master interface to the LBC. Here, validity is indicated, for example, by control signals, tags, flags, or other codes. The first symbol is sent from the LBC to the local bus only when validity is indicated. If validity is not determined, the last valid first symbol received can be retransmitted and sent, for example. Alternatively, in this case, a default symbol or an empty symbol that does not cause any or defined control, regulation, etc., to the data bus user equipment can also be sent. This prevents the erroneous transmission of the first symbol on the local bus, which could lead to incorrect control, regulation, etc., of the data bus user equipment or associated actuators. The data management unit may also include a second data transmission unit (DTU1), adapted to read the second symbol from the LBC's buffer via a second master interface based on a second instruction, and write the second symbol into the FBC's buffer via a first master interface. Therefore, DTU0 is adapted to transmit symbols from the fieldbus towards the local bus, while DTU1 is adapted to transmit symbols from the local bus towards the fieldbus. DTUs 0 and 1 are preferably implemented independently in hardware, thus separating the transmission directions. This hardware separation allows for parallel processing in both transmission directions, ensuring simultaneous transmission in both directions. DTU1 may also be adapted to write a portion of the second symbol into the FBC's buffer only when the LBC verifies the validity of the second symbol. This has the advantage that the time for sending the second symbol to the control unit via the fieldbus can be delayed until the validity of the second symbol has been checked. This is because the FBC only sends the second symbol from the buffer via the fieldbus when the second symbol is complete, for example, only when the buffer has reached a certain fill level (i.e., the fieldbus telegraph is complete). Furthermore, the data management unit can also be adapted to transmit the second symbol based on the LBC's control signal. The second symbol is transmitted only when this control signal is present.

[0032] The first data transfer unit DTU0 and the second data transfer unit DTU1 can also be referred to as copy units. Here, DTU0 copies process data selected from the data stream received via the fieldbus to the buffer of the LBC. DTU1 copies process data selected from the data stream received via the local bus to the buffer of the FBC. Then, the FBC and LBC send their buffer contents to the fieldbus or the local bus, respectively. Here, the FBC and LBC are not bus-neutral because they package the corresponding buffer contents into a fieldbus-compatible or local bus-compatible format. This means that the FBC and LBC are suitable for the corresponding bus system. Therefore, these units can be designed to be interchangeable, and thus these units can be changed according to the bus system used. However, the copy units are bus-neutral because they only copy process data, and no other bus-specific information is considered here. However, the copy units copy the first and second process data in a specific order. This means that the copy units copy the process data in the order in which the process data is received from the data stream. For example, this means that the first process data is also copied to the LBC in the order it is received via the fieldbus. In reverse order, this means that the second process data is copied to the FBC in the order it is received via the local bus. In other words, process data is copied between the FBC and LBC via a copying unit without changing their order.

[0033] In another preferred embodiment of the device according to the invention, the device further includes a computing unit for controlling the FBC and / or the data management unit and / or the LBC, and for evaluating first and second symbols. The computing unit may be a microcontroller connected to the FBC, LBC, and / or data management unit via a parallel bus. For example, the bus may be a 32-bit parallel bus. The computing unit may be adapted to program and modify the instructions that allow the FBC, LBC, and / or data management unit to operate according to instructions. Furthermore, the computing unit may be adapted to receive, read, and evaluate data via a fieldbus or from a local bus of the data management unit. Additionally, the computing unit may be adapted to read and evaluate the first symbol cached by the data management unit, i.e., cached process data. Moreover, the computing unit may be adapted to control the LBC, particularly writing control data for manipulating process data into the LBC.

[0034] In another preferred embodiment of the apparatus according to the invention, the first unit is adapted to check the validity of data received via the fieldbus. The first unit may also be adapted to signal the validity of data received. The second unit may be adapted to check the validity of data received via the local bus. The second unit may also be adapted to signal the validity of data received. For example, data can only be transmitted after the validity is confirmed by signaling. The validity of the data stream can be based on CRC check, for example. Here, two units or only one unit may be adapted to check the corresponding validity. If the validity of the transmitted or received data is not signaled by the corresponding other unit, the first and second units may be adapted not to output data to the fieldbus or the local bus. It is possible that the fieldbus connected to the first unit needs to continuously transmit data, i.e., transmit data without time interruption. In this case, when the validity of the previous data is not given, the data that is last confirmed as valid by the first unit can be transmitted on the fieldbus.

[0035] In another preferred embodiment of the device according to the invention, the device further includes a clock setter and / or a timer for generating internal timing and / or for handing over to data bus user equipment on the local bus. Furthermore, the device according to the invention may include a synchronization unit for synchronizing the clock setter and / or timer with the clock of the fieldbus. For example, the synchronization unit may be adapted to detect transitions in the data stream received from the fieldbus and may use these transitions to adjust the clock frequency of the internal clock signal, and set a defined phase of the internal clock signal to the detected transition. Therefore, the timer of the device according to the invention may, for example, be synchronized with a timing unit used by the control unit. This timing may also transmit the device according to the invention to data bus user equipment on the local bus. This timing can be used during the transmission of data packets on the local bus.

[0036] In a preferred embodiment of the device according to the invention, the fieldbus is one of the following groups: ARCNET, AS-Interface, BACNet, BITBUS, ControlNet, Profibus / Profinet, EtherCAT, Ethernet / IP, Interbus, AS-Interface, CIP protocol, CANopen, CC-Link, Modbus, Modbus / TCP, P-NET, Lonworks, SERCOS, BACnet, Bitbus, Measurement Bus, Powerlink, DeviceNet, RTPS, DALI, EIB, FAIS bus, FIB bus, FlexRAY, HART, KNX, LCN, LIN, LON, P-Net, T-Bus, VARAN. However, it is also possible for the fieldbus to use other bus protocols. The protocol used by the fieldbus must only allow for a clear distinction between process data and non-process data, i.e., other data contained in the data stream. For this purpose, for example, the protocol must clearly define the location of the predetermined process data and the location of the non-process data within the data stream. Alternatively or additionally, if process data is not always found in the same location within the data stream, the protocol must allow the location of the process data to be determined based on other information within the data stream. Determining the location of process data within the data stream is necessary so that process data can be selected from the data stream.

[0037] In a preferred embodiment of the device according to the invention, the first unit is designed as a first logic circuit, and the second unit is designed as a second logic circuit. Here, the first and second logic units are adapted to operate independently of each other. This means that the two logic circuits can simultaneously perform different operational operations. This is achieved through separate hardware implementations of the first and second logic circuits.

[0038] In another preferred embodiment of the apparatus according to the invention, the first unit is adapted to receive a serial data stream from a fieldbus and output a serial data stream on the fieldbus. The second unit is adapted to output the serial data stream to a local bus and receive a serial data stream from the local bus. The first and second units are preferably adapted to convert the serial data stream into a parallel data stream. Preferably, the first and second units are connected to a data management unit via their respective parallel buses. These parallel buses can be designed as 32-bit parallel buses. This means that within the apparatus according to the invention, symbols of the various data streams are forwarded in parallel. Each parallel bus can also be a segment of a single parallel bus.

[0039] The aforementioned objective is also achieved by a method for transmitting data between a fieldbus and a local bus, particularly a ring bus, wherein at least one data bus user equipment is connected to the local bus. The method according to the invention includes receiving data via the fieldbus at a first unit, wherein the received data includes a first symbol, sequentially related transmission of the first symbol to a second unit, and transmitting data packets on the local bus from the second unit including the first symbol. Attached Figure Description

[0040] The invention will now be explained in more detail with reference to the accompanying drawings and embodiments. Further details, features, and advantages of the subject matter of the invention will be obtained from the described embodiments. Illustrations:

[0041] Figure 1 It is a schematic block diagram of an exemplary automation device having a storage programmable control unit, a fieldbus, an embodiment of the device according to the present invention, and an exemplary ring bus;

[0042] Figure 2 This is a schematic block diagram of an embodiment of the device according to the present invention;

[0043] Figure 3a This is a schematic block diagram of an exemplary embodiment of the device according to the invention, wherein a first symbol is transmitted from the fieldbus to the ring bus; and

[0044] Figure 3b This is a schematic block diagram of an embodiment of the device according to the present invention, wherein a second symbol is transmitted from the ring bus to the fieldbus. Detailed Implementation

[0045] Figure 1 A schematic block diagram of an automated device is shown. Those skilled in the art will understand that the automated device shown is merely an example, and all elements, modules, components, user equipment, and units belonging to the automated device can be configured differently but can still fulfill the basic functions described herein.

[0046] Figure 1The illustrated automated equipment has a higher-level control unit 1, which can be implemented, for example, through a stored programmable controller (SPS). Such an SPS 1 is primarily used to control and regulate the processes performed by the automated equipment. However, the SPS 1 in modern automated equipment also undertakes broader functions, such as visualization, alarming, and recording all process-related data, thus acting as a human-machine interface. SPS 1s exist at different performance levels, possessing varying resources (computing capacity, memory capacity, number and type of inputs and outputs, and interfaces) that enable the SPS 1 to control and regulate the processes of the automated equipment. SPS 1s typically have a modular construction and consist of individual components, each performing a different task. Generally, an SPS 1 includes a central computing architecture group (with one or more main processors and storage modules) and multiple architecture groups with inputs and outputs.

[0047] The modular construction of an SPS 1 can be easily expanded by adding structural groups. Here, the choice of which structural groups must be integrated into the SPS 1 depends on the complexity of the process and the structure of the automation equipment. In today's automation equipment, the SPS 1 is no longer typically a standalone system, but rather connected to the internet or intranet via a corresponding interface (not shown here).

[0048] This means that SPS 1 is part of a network through which or from which it can obtain information, instructions, programs, etc. For example, SPS 1 can obtain information about the materials provided by the process through a connection to a computer located on an intranet or the Internet, thus allowing for optimal control of the process, for example, by understanding the quantity or properties of the materials. It is also conceivable that SPS 1 is controlled by user access from an intranet or the Internet. Therefore, for example, a user can access SPS 1 with the help of a computer (also called a host computer) and inspect, modify, or correct its user programming. Thus, SPS 1 can be accessed from one or more remote control stations or control centers. If needed, the host computer can have visualization devices for representing the process sequence.

[0049] To control the processes of automated equipment, SPS1 is connected to the automated instruments. To maintain low wiring costs, a bus system is used for these connections. Figure 1 In the illustrated embodiment, SPS 1 is connected to the local bus host 3 of the lower-level local bus system via a higher-level bus 2, which in this illustrated embodiment can be a fieldbus. However, the higher-level bus 2 can be connected not only to the local bus host 3 of the local bus as in the illustrated embodiment, but also to any other user equipment (not shown) designed to communicate with SPS 1.

[0050] In the embodiment shown here, the upper-level bus 2 is connected to the local bus host 3. For this purpose, the local bus host 3 has a first interface 4, which is designed to allow connection to the upper-level bus 2. For this purpose, the interface 4 may have a receiving portion, for example, in the form of a socket, while the upper-level bus 2 may have a plug that can be received by the socket. Here, the plug and socket may be, for example, a modular plug and a modular socket, i.e., each cable core of the upper-level bus 2 is electrically or optically connected to a connection portion in a modular socket. However, those skilled in the art also know how to design other feasible solutions for the interface 4, so that the local bus host 3 can be electrically or optically connected to the upper-level bus 2. Those skilled in the art are familiar with screw-on connections, rotational connections, snap-fit ​​connections, or plug connections, by means of which electrical or optical connections can be established. Here, in most cases, the male plug is received by a female mating part. This receiving typically not only establishes an electrical or optical connection but also ensures that the two parts are mechanically coupled and can only be disengaged by applying a certain force. However, it is also conceivable to fix the upper-level bus 2 to the interface 4.

[0051] In the embodiment shown here, the local bus host 3 has another second interface for connecting the local bus host 3 to the local bus. Data bus user equipments 7a, 7b, ..., 7n are connected to the local bus or form a local bus. The local bus is advantageously configured such that data packets sent by the local bus host 3 pass through all data bus user equipments 7a, 7b, ..., 7n connected to the local bus and are sent back to the local bus host 3. Here, data bus user equipments 7a, 7b, ..., 7n always receive only a portion of the data packets from their upstream data bus user equipments 7a, 7b, ..., 7n.

[0052] After a period of time, during which data bus user equipment 7a, 7b, ..., 7n can process the data contained in this portion, and then forward this portion to downstream data bus user equipment 7a, 7b, ..., 7n, while simultaneously receiving new portions of the data packet by upstream data bus user equipment 7a, 7b, ..., 7n. In this way, all portions of the data packet pass sequentially through all data bus user equipment 7a, 7b, ..., 7n. Advantageously, the local bus is designed as a ring structure. Such a local bus can also be called a ring bus 6. Alternatively, the local bus can be formed in a chain or star configuration, or in a combination or hybrid of the aforementioned configurations. Here, the transmission and reception of data packets are accomplished through the second interface of the local bus host 3. In the embodiment shown here, the second interface is divided into a first portion 5a and a second portion 5b. The first portion 5a of the second interface establishes a downlink connection in the ring bus 6, and the second portion 5b of the second interface establishes an uplink connection in the ring bus 6.

[0053] Ring bus 6 (The data transmission direction of the ring bus is indicated by an arrow) Figure 1 (As shown in the embodiment) The embodiment shown here includes data bus user devices 7a, 7b, ..., 7n. In the embodiment shown here, these data bus user devices 7a, 7b, ..., 7n each have an interface 8 for receiving data from upstream or preceding data bus user devices 7a, 7b, ..., 7n. In the case of data bus user device 7a, the data bus user device receives data from the upstream local bus host 3 via interface 8. Furthermore, in the embodiment shown here, data bus user devices 7a, 7b, ..., 7n each have an interface 9 for forwarding data to downstream or subsequent data bus user devices 7a, 7b, ..., 7n. In the case of data bus user device 7a, this data bus user device sends data to downstream data bus user device 7b via interface 9. Here, interfaces 8 and 9 are used to propagate data in the downlink direction (i.e., away from the local bus host 3) of the ring bus 6. In addition, in this embodiment, data bus user devices 7a, 7b, ..., 7n also have interfaces 10 and 11 for propagating data in the uplink direction of the ring bus 6, i.e., to the local bus host 3. In the case of data bus user equipment 7a, interface 10 is designed to receive data from downstream or subsequent data bus user equipment 7b, and interface 11 is designed to forward data to upstream or previous data bus user equipment, in this case, local bus host 3. Therefore, it can also be said that interfaces 9 and 11 are transmitting interfaces, while interfaces 8 and 10 are receiving interfaces.

[0054] In the embodiment shown here, the connection between the interface and the SPS 1 or data bus user equipment 7a, 7b, ..., 7n is achieved via cables or circuit boards using direct or indirect contact via electrical contacts. Alternatively, a single connection can be established wirelessly, with the interface providing the necessary conversion for the wireless standard used.

[0055] Even in the embodiments shown here, the local bus host 3 and the individual data bus user devices 7a, 7b, ..., 7n are shown separately from each other, and the local bus host 3 is therefore also distributed with the data bus user devices 7a, 7b, ..., 7n, as those skilled in the art will know.

[0056] Data bus user devices 7a, 7b, ..., 7n and the local bus host 3, which also represents the data bus user devices of the ring bus 6, can also be directly connected to each other. Here, for example, a contact of one data bus user device can be embedded into a corresponding receptacle or receptacle of a directly adjacent data bus user device to establish an electrical connection between the data bus user devices, thereby enabling data transmission in both the uplink and downlink directions. For example, data bus user devices 7a, 7b, ..., 7n may have receptacles on the side facing away from the host and contacts on the side facing the host. If the data bus user devices 7a, 7b, ..., 7n are then arranged in rows accordingly, the contacts of one data bus user device 7a, 7b, ..., 7n are embedded into the receptacles of another data bus user device 7a, 7b, ..., 7n, respectively, and an electrical connection can be established. The local bus host 3 then has corresponding contacts on its side, which are embedded into the receptacle of the first data bus user device 7a to establish an electrical connection between interfaces 5a and 8 or interfaces 5b and 11. However, those skilled in the art also know of other possibilities, such as pressure contacts, fork contacts, or two data bus user devices 7a, 7b, ..., 7n arranged directly adjacent to each other, which may form an electrical or optical connection.

[0057] In cases where data bus user devices 7a, 7b, ..., 7n and local bus host 3 are directly connected to each other, they may also have mechanical receptacles or mechanical fastening devices through which individual data bus user devices 7a, 7b, ..., 7n and local bus host 3 can be connected to each other. In this case, for example, data bus user devices 7a, 7b, ..., 7n may have a protrusion on one side and an undercut on the other side. If the data bus user devices 7a, 7b, ..., 7n are subsequently arranged in a row, one protrusion is embedded into the undercut of another data bus user device 7a, 7b, ..., 7n, thereby creating mechanical coupling. For simple row arrangement of data bus user devices 7a, 7b, ..., 7n, they may also be arranged on a common receptacle, such as a mounting rail. For fixation on the mounting rail, data bus user devices 7a, 7b, ..., 7n may have corresponding fastening devices. Alternatively or additionally, the data bus user equipment 7a, 7b, ..., 7n may also have, for example, a releasably connected fastening device, by which the data bus user equipment 7a, 7b, ..., 7n can be secured to a mounting rail or another receiving portion. For this purpose, the releasably connected fastening devices can be interchanged, and a corresponding fastening device for a desired receiving portion can be connected to the data bus user equipment 7a, 7b, ..., 7n so that they can be secured to the desired receiving portion.

[0058] In addition, Figure 1 In the illustrated embodiment, the data bus user equipment 7a, 7b, ..., 7n further includes a processing unit 12. This processing unit 12 may be an arithmetic logic unit or another type of computing device that can process data. Preferably, the processing unit 12 is an integrated component of the data bus user equipment 7a, 7b, ..., 7n to ensure particularly fast and time-synchronized data processing.

[0059] Processing unit 12 can also be referred to as the entire circuitry of the data bus user equipment. That is, processing unit 12 receives data via inputs 8 and 10 and outputs data at outputs 9 and 11. Furthermore, processing unit 12 can receive or output data from inputs and outputs 13 and 14. Additionally, processing unit 12 can access the memory (not shown here) of data bus user equipment 7a, 7b, ..., 7n, which stores, for example, data, process data, or instruction lists.

[0060] Processing unit 12 can be configured to process received data and output data. Data to be processed can be received from upstream data bus user equipment or from input 13 of data bus user equipment 7a, 7b, ..., 7n. Here, input 13 of data bus user equipment 7a, 7b, ..., 7n can be connected to sensor 15, which sends, for example, measurement data, status data, etc. The processed data can be output to downstream data bus user equipment or output 14 of data bus user equipment 7a, 7b, ..., 7n. Here, output 14 of data bus user equipment 7a, 7b, ..., 7n can be connected to actuator 16, which performs specific actions, for example, by means of data directed to it. If data processing is also performed in the upstream direction, data can also be received by downstream data bus user equipment 7a, 7b, ..., 7n, and the processed data can be sent to upstream data bus user equipment 7a, 7b, 7n.

[0061] For simplicity, in the embodiment shown here, data bus user devices 7a, 7b, ..., 7n are shown as having only one input 13 and one output 14, and only data bus user device 7b is connected to sensor 15 and actuator 16. However, it is known to those skilled in the art that data bus user devices 7a, 7b, ..., 7n may have multiple inputs and outputs 13 and 14, and may be connected to multiple different sensors 15 and actuators 16. Here, sensor 15 is characterized in that sensor 15 receives data or signals and transmits data or signals to data bus user devices 7a, 7b, ..., 7n, while actuator 16 receives data or signals from data bus user devices 7a, 7b, ..., 7n and performs actions based on these data or signals.

[0062] Alternatively, interfaces 8, 9, 10, and 11 can be integrated into the module unit, and data bus user devices 7a, 7b, ..., 7n can be inserted into this module unit. The module unit can also be referred to as the basic element of the ring bus 6. Here, the ring bus infrastructure is constructed from module units, and the data bus user devices 7a, 7b, ..., 7n are interchangeable; therefore, the ring bus 6 can be constructed using any of the data bus user devices 7a, 7b, ..., 7n. The module units also ensure that even if data bus user devices 7a, 7b, ..., 7n are removed, communication between the remaining data buses 7a, 7b, ..., 7n will not be interrupted due to communication occurring on the remaining module units.

[0063] Since the data bus user equipment 7a, 7b, ..., 7n shown in this embodiment are often referred to as E / A modules due to their inputs and outputs 13, 14, which can be connected to the sensor 15 or actuator 16. Even though in the exemplary embodiment shown here, the data bus user equipment 7a, 7b, ..., 7n are shown to be spatially separated from the sensor 15 or actuator 16, the sensor 15 or actuator 16 can also be integrated into the E / A module.

[0064] The ring bus 6 shown in the embodiment illustrated herein is based on cyclic frame communication.

[0065] Here, a cyclic frame can be defined, for example, as a recurring (cyclic) preferably equidistant time interval in which data can be transmitted on the ring bus 6. The cyclic frame has, for example, at least one start identifier (SOC) and a time range for data transmission. Here, multiple start identifiers (SOCs) of consecutive cyclic frames are advantageously spaced equidistant from each other in time. The time range is set for transmitting data that can be transmitted in packet form within the cyclic frame. The start identifier (SOC) and the data packets are transmitted via the ring bus 6 and pass through all data bus user devices 7a, 7b, ..., 7n. Advantageously, the cyclic frame is initialized by the local bus master 3 in the ring bus 6. The start identifier (SOC) is independent, i.e., it can be transmitted as an independent symbol or advantageously included in a start data packet (SOC packet).

[0066] Within the time frame of the cyclic frame, no, one, or more data packets are transmitted. Advantageously, idle data (dormant data) is inserted into the cyclic frame, particularly adjacent to at least one data packet. Advantageously, the transmission of data packets and / or idle data causes an uninterrupted signal on the ring bus 6. This signal allows data bus user devices 7a, 7b, ..., 7n to synchronize with this signal. Advantageously, the cyclic frame also has a tail. The tail has a variable length and follows the time frame used for data transmission preferably until the next start identifier (SOC) of the next cyclic frame. Advantageously, the tail contains idle data. Each data packet is sent by the local bus host 3 in the downlink direction to the first data bus user device 7a on the ring bus 6. The first data bus user device receives the first portion of the data packet through interface 8. This portion of the data packet is also referred to below as a block or a unit. The data bus user device 7a then processes this portion and forwards it through interface 9 to the next data bus user device 7b, preferably the first data bus user device 7a, which simultaneously receives the second portion of the data packet, and so on. Here, the size of a portion of the data packet, i.e., the subdivision of the data packet, depends on the capacity of the data bus user devices 7a, 7b, ..., 7n, for example, a fixed number of bits, such as 8 bits of the data packet being able to exist simultaneously at the data bus user devices 7a, 7b, ..., 7n for processing.

[0067] Accordingly, data packets are transmitted, for example, in 8-bit portions or symbols, cell-by-cell, block-by-block, or portion-by-part. A portion of the data packet processed by the last data bus user equipment (data bus user equipment 7n in the exemplary embodiment shown here) then travels uphill through the ring bus 6, so that the portion is transmitted upwards again from the last data bus user equipment 7n toward the local bus host 3 through all data bus user equipment 7a, 7b, ..., 7n. For this purpose, the last data bus user equipment 7n has a switchable bridge connecting interface 9 to interface 10, or a switchable bridge (not shown here) connected to the last data bus user equipment 7n, which takes over the function of transmitting portions of the data packet from interface 9 to interface 10. Alternatively, interface 10 of data bus user equipment 7n can also be directly connected to interface 5b of the local bus host 3 by means of a bypass path not shown here.

[0068] As shown in the exemplary embodiment illustrated here, in the uplink direction, a unit of one or more data packets can be looped back to the local bus host 3 by a single data bus user equipment 7a, 7b, ..., 7n without any further processing. However, it is also conceivable to process the units of the data packets again in the uplink direction, so that the data packets can be processed twice, once in the downlink direction towards the last data bus user equipment 7n and once in the uplink direction towards the local bus host 3. For example, in the uplink direction, processing can be performed by signal refreshing and / or phase shifting.

[0069] When processing data packets in the downlink direction (i.e., away from the local bus host 3) or the uplink direction (i.e., towards the local bus host 3), processing is accomplished via an instruction list, which includes a set of instructions that can be executed by the processing unit 12 of the data bus user devices 7a, 7b, ..., 7n. The instruction list itself can be sent from the local bus host 3 to individual data bus user devices 7a, 7b, ..., 7n during the initialization phase, or advantageously during ongoing communication, thus enabling programming of the data bus user devices 7a, 7b, ..., 7n without interrupting communication.

[0070] The instruction list index can be used to determine which instruction list is being transmitted to data bus user devices 7a, 7b, ..., 7n. This instruction list index informs the data bus user devices which stored instruction list to use. Therefore, by assigning the instruction list index to an instruction list and vice versa, the instruction list to be used can be identified with the help of the instruction list index. For this purpose, the instruction list index preferably has a value assigned to the instruction list, for example, indicating a specific instruction list or its storage location. This value itself can be a storage address where the instruction list is stored or where at least the first instruction of the instruction list is stored. Alternatively or additionally, the value can also indicate the storage area where the corresponding instruction list is stored. In the above case, direct allocation can also be used. The value of the instruction list index can be, for example, but can also be used as input to a lookup table (LUT). Here, the value of the instruction list index is the input value of the lookup table. The output value of the lookup table can be the storage address of the first instruction in the relevant instruction list, or an identifier for the instruction list. The translation table can be stored in software and hardware technologies, for example, in logical form, and specifies the explicit conversion from input values ​​to output values, where the output values ​​indicate the list of instructions to be used. Here, what depends on the translation table is how the association is established between the instruction list index and the instruction list. Using the translation table can also be described as indirect allocation. However, in both direct and indirect allocation, the instruction list used by the data bus user equipment can be explicitly identified by the instruction list index, i.e., it can be found. The instruction list index can be inserted into the data packet before the process data to be processed, so that data bus user equipment 7a, 7b, ..., 7n can use the corresponding instruction list according to the order of the process data in the data packet. Here, the instruction list contains instructions that apply to the order of the process data in the data packet. For example, the instruction list for process data not directed to data bus user equipment 7a, 7b, ..., 7n may have a "SKIP" instruction, i.e., instructing data bus user equipment 7a, 7b, ..., 7n to skip the corresponding portion of the data packet, while the instruction list for process data directed to data bus user equipment 7a, 7b, ..., 7n may have corresponding instructions for processing the process data. This allows the processing of process data to be separated from the actual location of the process data in the data packet, because the data bus user equipment adapts to the order of the process data in the data packet by means of the instruction list.

[0071] To facilitate the conversion between the upper-level bus 2, also known as the fieldbus, and the ring bus 6, the embodiment shown here uses a local bus master 3. Figure 2 The device responsible for the conversion in the local bus host 3 is shown.

[0072] Figure 2 A block diagram illustrating an exemplary embodiment of the device according to the invention arranged in a local bus host 3 is shown. The local bus host 3 is connected to a fieldbus 2 via an interface 4 and to a ring bus 6 via an interface 5. Accordingly, interface 4 may also be referred to as a fieldbus interface, and interface 5 may be referred to as a local bus interface. Here, in order to process the data streams received or to be transmitted through these interfaces, processing units may be connected to interfaces 4 and 5. Here, a first unit 17 (also referred to as a fieldbus core (FBC)) may be connected to fieldbus interface 4, and a second unit 19, also referred to as a local bus core (LBC), may be connected to local bus interface 5.

[0073] FBC 17 and LBC 19 are connected to data management unit 18 via a parallel bus. The parallel bus can be a 32-bit parallel bus, and computing units such as microcontrollers, μC, or processors can also be connected to the parallel bus. The parallel bus can control FBC 17, data management unit 18, and LBC 19.

[0074] Data management unit 18 is adapted to transmit first symbols from FBC 17 to LBC 19 in a sequence-dependent manner, such as in an invariant order, so that the first symbols can be sent to ring bus 6 via local bus interface 5 in the form of being included in at least one data packet. Here, the first symbols may be process data received via fieldbus 2 via interface 4 on FBC 17. LBC 19 may be adapted to generate consecutive local bus-compatible data packets to transmit process data on local bus 6 and insert process data received from data management unit 18 into the corresponding data packets. Here, the order of process data can be maintained, that is, the process data in the data packets on the local bus has the same order as the order in which the process data is received via fieldbus interface 4 on FBC 17. In other words, fieldbus telegrams from fieldbus 2, which have process data in the form of first symbols, are received on FBC 17 via fieldbus interface 4. These first symbols have a fixed number of bits, such as 8 bits, i.e., 1 byte. These first symbols are arranged in a first order in the fieldbus telegram. Data management unit 18 is adapted to copy process data from FBC 17 to LBC 19. LBC 19 is adapted to generate data packets for local bus 6, wherein the first symbol of the process data is included in the data packet in a second order, and wherein the first order and the second order of the symbols are coordinated. Data bus user devices 7a, 7b, ..., 7n are configured to evaluate the process data in the data packet via an instruction list and an instruction list index. For this purpose, for example, an instruction list index is set before the process data in the data packet. Conversely, data management unit 18 is adapted to transmit the second symbol from LBC 19 in a sequence-dependent manner, for example, to be transmitted unchanged to FBC 17, so that the second symbol can be sent to fieldbus 2 via fieldbus interface 4. Here, the second symbol is received from local bus 6 on LBC 19 via local bus interface 5. If local bus 6 is a ring bus, local bus interface 5 is divided into two parts, namely parts 5a and 5b, wherein data is sent to local bus 6 in the downlink direction via part 5a, and received by local bus 6 in the uplink direction via part 5b.

[0075] In the embodiment shown here, the data management unit 18 also has first and second master interfaces 18a and 18b. Here, the first master interface 18a is connected to the slave interface 17a of the FBC 17. That is, the data management unit 18 and the FBC 17 are in a master-slave relationship, in which case control begins from the data management unit 18. Therefore, the data management unit 18 reads data from or writes data to the FBC 17 at times specified by the data management unit 18. The second master interface 18b of the data management unit 18 is connected to the slave interface 19a of the LBC 19. Moreover, the data management unit 18 and the LBC 19 are in a master-slave relationship. That is, the data management unit 18 controls the data transmission between the FBC 17 and the LBC 19, particularly in both directions.

[0076] Furthermore, in the embodiment shown here, the data management unit 18 and LBC 19 are connected via another line 25, through which validity information related to the transmitted symbols can be exchanged between the data management unit 18 and LBC 19. This validity information can then be used to delay the transmission of the first and second symbols on the fieldbus 2 or the local bus 6.

[0077] Advantageously, the connection between units is designed as a bus. Here, the bus can advantageously be a 32-bit parallel bus. Alternatively, the connection can be any other connection that allows the aforementioned data transfer between the units.

[0078] Figure 3a A schematic block diagram of an embodiment of the device according to the invention, implemented in a local bus host 3 of a ring bus 6, is shown. In the embodiment shown here, a first interface 4 of the local bus host 3 receives a fieldbus message 20 from a fieldbus 2. For example, the fieldbus message 20 contains 10 bytes, indicated by boxes, each box representing 1 byte, or 8 bits. The four black boxes, representing only 4 bytes, contain first process data 21. The other 6 bytes of the fieldbus message 20 are information corresponding to the bus protocol used on the fieldbus 2. However, these other 6 bytes do not carry the process data 21 necessary for control or regulation; this additional information is only bus-specific information, such as addressing information, checksum information, etc. The first process data 21 is also identified here as [1], [2], [3], and [4], indicating their order. The first process data 21 is selected from the fieldbus message 20 by an FBC 17 and stored, for example, in a buffer not shown here. This option allows FBC 17 to transmit process data 21 only in the buffer, ignoring other bytes of fieldbus telegram 20.

[0079] In the embodiment shown here, the data management unit 18 has a first data transmission unit 22 that reads process data 21 from a buffer of the FBC 17 via master-slave interface connections 17a, 18a, and then writes the process data 21 into a buffer (not shown) of the LBC 19 via master-slave interface connections 18b, 19a. That is, the first data transmission unit 22 copies the process data 21 from the FBC 17 to the LBC 19. Here, the copying can be performed according to instructions, and the first data transmission unit 22 can be adapted to prepend and / or append other data to the process data 21 and / or insert other data between the process data 21. Alternatively or additionally, the LBC 19 can be adapted to prepend and / or append other data to the process data 21 and / or insert other data between the process data 21 and / or modify the process data 21. For example, the other data can be used by the LBC 19 to convert the process data 21 into a local bus compatible format, such as a data packet that can be sent to the local bus 6. In the embodiment shown here, symbols are prepended to process data 21, and additional symbols are appended to generate data packets 24 carrying process data 21. Those skilled in the art will understand that even if only one symbol is prepended and appended to process data 21, any number of symbols can be prepended and / or appended, and this depends solely on the data packet format used on local bus 6. The first data transmission unit 22 may be further adapted to notify LBC 19 of the validity of process data 21 after it has been copied to LBC 19. Here, validity can be conveyed via connection 25. LBC 19 can only transmit this process data downlink to local bus 6 via local bus interface 5a if the copied process data 21 is valid. The validity of process data 21 is determined here, for example, by CRC or a valid bit.

[0080] It will be apparent to those skilled in the art that portions of data packet 24 generated by LBC 19 can be sent to local bus 6 even before a validity indication. Specifically, as Figure 1 As shown, if portions of data packet 24 continuously pass through data bus user equipment 7a, 7b, ..., 7n, that is, at any given time, only a portion of data packet 24 is sent by local bus host 3, and that portion is then forwarded by a single data bus user equipment 7a, 7b, ..., 7n. In this case, even before validity indication, LBC 19 can send the portion of data packet 24 containing process data or other information to local bus 6. Therefore, in the embodiment shown here, LBC 19 can already send the attached symbols as the first portion of data packet 24 to local bus 6.

[0081] Therefore, the first data transmission unit 22 copies the process data 21 from the fieldbus 2 to the local bus 6. Here, the order of the process data 21 is maintained during this copying process [1], [2], [3], [4], that is, the order of the process data 21 is the same in the data packets 24 of the fieldbus telegram 20 and the local bus 6. Here, the process data 21 is copied neutrally to the bus, that is, no bus-specific information is used to receive the process data 21. Therefore, in the embodiment shown here, the first two symbols and the additional four symbols of the fieldbus telegram 20 are not copied.

[0082] Figure 3b A schematic block diagram of an embodiment of the device according to the invention, implemented in a local bus host 3 of a ring bus 6, is shown. In the embodiment shown here, the second interface 5b of the local bus host 3 receives a data packet 26. The data packet 26 contains, for example, 6 bytes, represented by boxes, each box representing 1 byte, i.e., 8 bits. The four black boxes, representing only 4 bytes, contain second process data 27. The other 2 bytes of the data packet 26 are information corresponding to the bus protocol used on the local bus 6. The second process data 27 is also identified here as [1'], [2'], [3'], and [4'], indicating their order. Here, the second process data 27 may be based on the first process data 21 (e.g., Figure 3a (As shown), and can be represented after process data 21 passes through (i.e., process data processing) local bus 6. Process data 27 is selected from data packet 26 by LBC 19 and stored, for example, in a buffer not shown here. This selection may be such that LBC 19 only transmits process data 27 in the buffer, while ignoring the other bytes of data packet 26.

[0083] In the embodiment shown here, the data management unit 18 has a second data transmission unit 23. This first data transmission unit reads process data 27 from the buffer of the LBC 19 via master-slave interface connections 18b and 19a, and then writes the process data 27 into the buffer of the FBC 17 via master-slave interface connections 17a and 18a. That is, the second data transmission unit 23 copies the process data 27 from the LBC 19 to the FBC 17. Here, the copying can be performed according to instructions, and the second data transmission unit 23 can be adapted to prepend and / or append other data to the process data 27 and / or insert it between the process data 27 and / or modify the process data. Alternatively or additionally, the FBC 17 can be adapted to prepend and / or append other data to the process data 27 and / or insert it between the process data 27. For example, the FBC 17 can use other data to convert the process data 27 into a fieldbus-compatible format, such as fieldbus telegraph 28 of fieldbus 2. In the embodiment shown here, process data 27 is preceded by two symbols and appended with four symbols to generate a fieldbus message 28 carrying process data 27. Those skilled in the art will know that even if a particular number of symbols are prepended and appended to process data 27, the number of symbols can be arbitrary, depending only on the fieldbus message format used on fieldbus 2. The second data transmission unit 23 can also be adapted to copy only a portion of process data 27 to FBC 17 and only copy the remaining process data 27 via connection 25 upon receiving a validity indication from LBC 19. As a result, the second data transmission unit 23 can control the timing of sending fieldbus message 28 via FBC 17, since the fieldbus message is always sent directly when fieldbus message 28 is completely filled with process data 27. If this is not the case, fieldbus message 28 is not sent. This allows control between the second data transmission unit 23 and FBC 17 without requiring another connection. Here, the validity of process data 27 is determined by means of CRC.

[0084] The components of the device according to the invention, described in the described embodiments as independent units, modules, or interfaces, can be implemented as independent hardware or integrated on the same semiconductor chip, and their functions can be implemented by hardware logic gates. For example, the units, modules, or interfaces can be implemented on an FPGA / ASIC.

[0085] Appendix Label Sheet

[0086] 1. Storage Programmable Controller (SPS)

[0087] 2. Upper bus

[0088] 3 Local Bus Host

[0089] 4 First Interface

[0090] 5a, b Second Interface

[0091] 6 ring bus

[0092] 7a, b, n data bus user equipment

[0093] 8 First Downlink Data Interface

[0094] 9 Second Downlink Data Interface

[0095] 10 First uplink data interface

[0096] n Second uplink data interface

[0097] 12 processing units

[0098] 13, 14 Inputs / Outputs

[0099] 15 Sensors

[0100] 16 Actuators

[0101] 17. Unit 1 (Fieldbus Core, FBC)

[0102] 17a First Unit Slave Interface

[0103] 18 Data Management Units

[0104] The first and second main interfaces of the 18a and b data management units

[0105] 19. Second Unit (Local Bus Core, LBC)

[0106] 19a Second Unit Slave Interface

[0107] 20 Fieldbus Messages Received

[0108] 21 First Process Data

[0109] 22 First Data Transmission Unit (DTU0)

[0110] 23 Second Data Transmission Unit (DTU1)

[0111] 24 data packets (downlink direction)

[0112] 25 Connection with validity indicators

[0113] 26 data packets (uplink)

[0114] 27 Second Process Data

[0115] 28 Fieldbus telegrams sent

Claims

1. An apparatus for coupling a fieldbus to a local bus for connection to a data bus user equipment, the apparatus comprising: The fieldbus core is capable of connecting to the fieldbus and is suitable for sending and receiving data via the fieldbus. A local bus core that can be connected to a local bus and is adapted to send and receive data in at least one data packet via the local bus; as well as A data management unit, connected to a fieldbus core and a local bus core, is adapted to transmit first symbols of data received via the fieldbus core to the local bus core in a sequence-dependent manner, such that the first symbols are transmitted to the local bus core in the same order as the order in which these symbols are received from the fieldbus core.

2. The apparatus according to claim 1, wherein, The data management unit is adapted to place an additional symbol before and / or append it to the first symbol.

3. The apparatus according to claim 1, wherein, The data management unit is suitable for caching the first symbol.

4. The apparatus according to claim 1, wherein, The local bus core is adapted to generate local bus-compatible data packets including a first symbol, and to transmit local bus-compatible data packets on the local bus.

5. The apparatus according to claim 1, wherein, The local bus core is adapted to receive local bus-compatible data packets from the local bus, wherein the local bus-compatible data packets contain a second symbol.

6. The apparatus according to claim 1, wherein, The local bus core is also adapted to manipulate the first symbol.

7. The apparatus according to claim 4, wherein, The cycle time of the cyclic frame of a local bus-compatible data packet is adapted to the cycle time of the fieldbus.

8. The apparatus according to claim 1, wherein, The data management unit has a first master interface that connects to the slave interface of the fieldbus core, and / or wherein, The data management unit has a second master interface that connects to the slave interface of the local bus core.

9. The apparatus according to claim 8, wherein, The data management unit has a first data transmission unit, and wherein, The first data transmission unit is adapted to read the first symbol from the buffer of the fieldbus core via the first main interface based on the first instruction and to write the first symbol into the buffer of the local bus core via the second main interface.

10. The apparatus according to claim 9, wherein, When the validity of the received first symbol is given, the data management unit is adapted to send the received first symbol to the local bus core via the second main interface through the first data transmission unit.

11. The apparatus according to claim 1, wherein, The data management unit has a second data transmission unit. The second data transmission unit is adapted to read the second symbol from the buffer of the local bus core via the second main interface based on the second instruction, and write the second symbol into the buffer of the fieldbus core via the first main interface.

12. The apparatus according to claim 11, wherein, When the validity of the second symbol is given, the data management unit is adapted to write the second symbol into the buffer of the fieldbus core via the first main interface using the second data transmission unit.

13. The apparatus according to claim 1, wherein, The fieldbus core is adapted to check the validity of data packets received via the fieldbus, and the local bus core is adapted to check the validity of local bus-compatible data packets received via the local bus.

14. The apparatus according to claim 1, wherein, The fieldbus core is suitable for serially sending and receiving data via fieldbus; The local bus core is suitable for serially sending and receiving data via the local bus; The data management unit is connected to the fieldbus core via a parallel bus; and The data management unit is connected to the local bus core via a parallel bus.

15. The apparatus according to claim 1, in, The fieldbus core is configured as the first logic circuit for communicating with the fieldbus; The local bus core is configured as a second logic circuit for communicating with the local bus; and The first logic circuit and the second logic circuit are adapted to perform independent operations.

16. The apparatus of claim 1, wherein the local bus core is adapted to generate and transmit local bus-compatible data packets including a first symbol on the local bus.

17. The apparatus according to claim 1, wherein, The symbols include process data.

18. The apparatus according to claim 1, wherein, Fieldbus is a bus at a higher level than local bus.

19. A method for transferring data between a fieldbus and a local bus, wherein a data bus user equipment is connected to the local bus, the method comprising: Data is received via fieldbus on the first unit, wherein the received data includes a first symbol; The first symbol is transmitted to the second unit in a sequential manner, such that the first symbol is transmitted to the second unit in the same order as the symbols were received from the first unit.

20. An apparatus for coupling a fieldbus to a local bus for connection to a data bus user equipment, the apparatus comprising: The fieldbus core is capable of connecting to the fieldbus and is suitable for sending and receiving data via the fieldbus. A local bus core that can be connected to a local bus and is adapted to send and receive data in at least one data packet via the local bus; as well as The data management unit is connected to the fieldbus core and the local bus core.

Images