Internal logistics conveying device
By introducing central data agents and object data sets in the internal logistics conveying device, the route decision made by objects at the local level has been realized, and the reliance on the central PLC in the existing technology and the system complexity of the central PLC have been solved. Sexual and efficiency.
Patent Information
- Application Number
- CN202380045959.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-12-23
- Filing Date
- 2023-06-12
- Publication Date
- 2025-01-21
AI Technical Summary
In existing internal logistics conveying devices, the routing decisions of objects depend on the control of the central PLC, resulting in the need for system complexity and topological programming.
By introducing the central data agent in the conveying device, the object data set contains the destination information of the object, and the sorting controller performs sorting decisions locally. Routing decisions are made by object data sets at the local level.
Reduce the dependence on the central PLC, simplify the system design, avoid programming needs for the topology of the conveyor device, and improve the flexibility and efficiency of the system.
Smart Images

Figure CN119343308A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to an internal logistics conveying device. Background Art
[0002] In a conventional internal logistics conveying device, such as that shown in US 7,996,104 B2, a plurality of conveying zones are provided. A plurality of local zone controllers control the operation of the zones based on an overall control signal provided by a central programmable logic controller (PLC). Thus, the local zone controllers provide start / stop and speed control of the motorized rollers according to messages from the PLC.
[0003] Scanners arranged along the zones provide identification data related to the objects to be transported. These identification data are sent to the PLC via a data connection. The PLC has access to an object database which provides destination data based on the identification of the object. Based on the acquired destination data, the PLC provides operating instructions to the local zone controllers on how to handle the object, i.e. to which exit the object is to be transported. Thus, the routing decisions for the individual objects are made in the PLC and provided to the zone controllers. The zone controllers control the zone actuators based on the provided routing decisions.
[0004] EP 3 222 564 B1 discloses a conveyor operated according to a more decentralized method. Here is an object from a starting position to a target destination. The conveyor includes a plurality of zones into which the conveyor is divided, and the object is conveyed across these zones. Each zone includes a linear conveying zone, which linearly conveys the object; a conveying direction changing zone, which selects the conveying direction of the object to send out the object in the selected conveying direction; a conveying destination storage unit, which is configured to temporarily store conveying destination information; an information receiving unit, which is configured to receive the conveying destination information from the upstream zone; and an information transmission unit, which is configured to transmit the conveying destination information to the downstream zone. The conveyor is configured to transmit the conveying destination information from the upstream zone to the downstream zone as the object moves across the zone. Based on the conveying destination information received from the upstream zone, the routing of the object is locally controlled by the actual zone.
[0005] US2002 / 0045969 A1 discloses an apparatus for sorting material units. A central sorting logic processor, such as a PLC, is provided, which transmits multiple signals to multiple actuators via a network bus. The actuators are directly controlled by the central sorting logic processor.
[0006] EP 2 370 331 B1 discloses a material flow system with multiple multi-directional conveying modules. Each module includes: conveying hardware, in particular motor-driven rollers; and a controller that controls the operation of the hardware and communicates with other modules. These modules can operate completely autonomously without being connected to any central control unit. These modules can be attached to adjacent modules to transfer objects to be conveyed from these modules to adjacent modules at corresponding ports, and vice versa. The ports serve as inlets and outlets for objects to be conveyed. Each port is equipped with a data interface through which adjacent modules can be directly data-connected to each other. There is no bus connection between modules. The module control can easily identify any modifications to the spatial relationship between modules. The topology of the modules and any changes in the topology can be automatically determined.
[0007] US2005 / 065642 A1 discloses a transport system for transporting items to a destination on a predefined transport route. The predefined transport route has a plurality of branch positions. A main controller sets a destination and a transport route associated with the destination for each transported item. Therefore, any local controller controls the branch position based on the transport route provided by the main controller. Summary of the invention
[0008] It is an object of the present invention to provide an improved method of controlling a conveying device.
[0009] The invention is solved by the subject matter of the independent claims; embodiments are the subject matter of the dependent claims and the description.
[0010] According to the present invention, a central data agent is provided that provides object data sets to interested parties. The object data sets pertain to real objects that are conveyed and sorted in a conveyor. The data may include any type of value that supports the operation of a local zone controller.
[0011] In particular, instead of explicit sorting instructions being provided by the PLC, sorting decisions are performed locally in the sorting controller with the aid of data. Simply put, the object knows its destination and tells the sorting controller what this destination is via its object data set. The sorting controller therefore knows which path to take in the local sorting segment and sets the local sorting segment accordingly. Routing decisions are therefore made at a local level based on object data, rather than asking a central PLC for individual routing decisions.
[0012] Generally speaking, in the context of this specification, two types of sensors are distinguished. On the one hand, presence sensors can simply provide information whether there are any objects in the sensor field; presence sensors usually do not provide any data related to the identity of the detected object. On the other hand, scanners can provide identification data, such as barcode or QR code information.
[0013] The term "belongs to" / "belongs to" indicates the relationship between the real transported object and the object dataset in two directions. Thus, the object dataset characterizes and provides detailed information related to the transported object; the transported object is characterized by the belonging object dataset.
[0014] When talking about a data set, it is not necessary that under the term "data set", it always refers to the complete data set. For example, a specific sorting segment may not be interested in certain values of the data set, so the controller can only store a portion of the complete data set, which is also considered a data set.
[0015] Compared to the prior art, the data agent only provides the destination associated with a particular object. Any decision on which route needs to be taken is made by the local zone controller. Therefore, no PLC (e.g., master controller) needs to be programmed with the topology of zones and destinations within the conveyor.
[0016] In general, the term routing conditions should be considered different from the term destination or destination information. The use of destination / destination information indicates a location to which an object must be delivered. A destination does not include any information, i.e., by which route to reach that destination. In contrast, routing conditions may include a single information about the path or direction decisions that need to be taken at various locations. Routing conditions do not include any indication of the destination. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Non-limiting examples of the present invention are described with reference to the accompanying drawings;
[0018] Figure 1 shows an exemplary delivery region used in the present invention;
[0019] Figure 2 Schematically illustrating embodiments of delivery zones with different inlet / outlet configurations;
[0020] Figure 3 The conveying device of the present invention is schematically shown;
[0021] Figure 4 A lookup table containing path conditions is schematically shown;
[0022] Figure 5 Flowchart showing the steps during the transport of objects from a feed station to a destination.
[0023] Figure 6 An exemplary object data set in step S2 is shown;
[0024] Figure 7 Another lookup table used in step S4 is shown;
[0025] Figure 8 An exemplary object data set in step S6 is shown;
[0026] Fig. 9 An exemplary object data set in step S7 is shown;
[0027] Fig.10 An exemplary object data set in step S9 is shown;
[0028] Fig.11 Schematically shows Figure 3 a portion of a conveying device of which is modified with an additional sorting branch;
[0029] Fig.12 Shows support according to Fig.11 The modified lookup table.
[0030] Fig.13 A portion of a conventional conveying device is schematically shown. DETAILED DESCRIPTION
[0031] Figure 1 An exemplary conveying area 2 is shown, which comprises several conveying rollers 3 driven together. For this purpose, one of the conveying rollers 3 is designed as a motor-driven conveying roller 3M. The motor-driven conveying roller 3M is driven in particular by a three-phase motor arranged in the conveying roller 3M. The conveying rollers 3 of the conveying area 2 are connected to each other via one or more transmission connections 4, such as a transmission belt, and are driven together by the motor-driven conveying roller 3M. The object is transported linearly from the inlet I to the outlet O.
[0032] With the aid of the presence sensor 5, the presence of a conveyed object 9 arranged on the conveying area can be determined. The presence sensor 5 does not have to cover the entire conveying area 2; it is sufficient if the presence sensor 5 detects the presence of a conveyed object 9 in a partial area of the conveying area 2. The presence sensor 5 thereby generates a sensor signal S5, which is connected via a signal line (not shown) to the area controller 11 presented further below. The presence detection can also be carried out without an explicit sensor and can be derived from other raw data. For example, there are already methods that can deduce the presence of conveyed material on the conveying area from other data, such as from the trend of the current intensity in the conveying area.
[0033] The conveyor rollers 3 and the presence sensors 5 are attached to a common support frame 8. The conveyor rollers 3 of several conveyor zones 2 can be attached to a common support frame 8.
[0034] The motor-driven conveying rollers 3M are all controlled by at least one or more zone controllers 11. A single zone controller 11 can control the motor-driven conveying rollers of several conveying zones 2. Several such zone controllers 11 are arranged in the conveying device 1 (see below). Figure 3 ), which communicate with each other via bus connection 13.
[0035] The area controller 11 controls the motor-driven conveying rollers 354 so that the continuously approaching conveyed goods 9 do not collide with each other. The control is performed in such a way that there is basically only one conveyed object 9 in each conveying area 2. However, a slight overlap can occur. For example, even if the downstream conveyed material has not completely left the downstream conveying area, the upstream conveyed material may have entered the downstream conveying area from the upstream conveying area. In addition, although it is ensured that the two conveyed goods will not contact and thus damage each other, the sensor signal S5 of the presence sensor 5 is still used as an input variable here.
[0036] Fig.13 A conventional conveying device is shown in which the aforementioned conveying zone 2 is used. A plurality of zone controllers 11 control the operation of the zone 2 based on an overall control signal provided by a PLC 12 .
[0037] Scanners arranged along the zone provide identification data related to the objects to be transported. These identification data are sent to the PLC 12 via the data connection 13. The PLC has access to an object database which provides destination data based on the identification of the object. Based on the acquired data, the PLC 12 provides operating instructions to the local zone controller 11, how to handle the object, i.e. to which exit the object is to be transported.
[0038] In one embodiment, the zone controllers 11 are connected to a common high-level object data agent 10 , in particular via a bus connection 13 , via which the zone controllers 11 are also connected to each other.
[0039] In the following process of the present invention, using Figure 2 The schematic diagram of the conveying area shown here refers to the conveying area. Figure 2 Schematically represents Fig.10 A conveying device is shown, which shows a first inlet I1 and a first outlet O1. No further inlets and outlets are provided. The conveying area can be curved.
[0040] Figure 2 b shows a view of another conveying area 2b with an extended operating range. Figure 2In addition to the conveying area 2a of the first embodiment, the conveying area 2b also has an additional second outlet O2. The object 9 can be selectively conveyed from the first inlet I1 to one of the first outlet O1, O2.
[0041] For example, Figure 2 The conveying area of b can be composed of Figure 1 The conveying area shown is formed, and the conveying area is additionally provided with a conveying area as described in reference EP 3 222 564 B1 Figure 5 The conveying device 20.
[0042] Figure 2 c shows a view of the conveying area 2c with an extended operating range. Figure 2 In addition to the conveying area 2a of a, the conveying area 2b also has an additional second inlet I2. Objects 9 can be conveyed from one of the first and second inlets I1, I1 to the first outlet O1. Such a conveying area is also called a "merge".
[0043] Reference Figure 2 b The conveying device described in claim 1 may also be adapted to provide said additional second inlet I2.
[0044] Figure 2 d shows a view of the conveying area 2d with an extended operating range. Figure 2 In addition to the conveying area 2a of a, the conveying area 2d also has an additional second inlet I2 and an additional second outlet O2, and is Figure 2 b and Figure 2 An example of a combination of embodiments of c.
[0045] like Figure 1 As shown, all conveying zones are controlled by a zone controller 11 , in particular wherein one zone control device may be adapted to control the operation of more than one zone 2 .
[0046] Figure 3 An example of a conveyor device 1 is shown. As described above, the conveyor device 1 comprises a plurality of conveying zones 2. Objects are selectively conveyed from at least one feed station F1, F2 to one of a plurality of destinations D1-D9 via the conveying zones 2. The conveyor device comprises conveying zones 2a-2d of different embodiments provided.
[0047] All functions of the conveying area 2 are controlled by the area controller 11. Due to better visibility, Figure 3 Only a few (not all) zone controllers 11 are shown.
[0048] At least some of the conveying areas 2b, 2d have more than one outlet O1, O2. In the following, such conveying areas having at least two outlets are referred to as sorting areas 2b, 2d.
[0049] The area controller 11 controls the sorting function of the sorting areas 2b and 2d. Here, the area controller 11 provides clear instructions to the sorting areas 2b and 2d, and determines through which of the plurality of outlets O1 and O2 the current conveyed object 9 is conveyed.
[0050] For better illustration and description, Figure 3 Some of the sorting areas are additionally provided with identification, for example see sorting areas B1, B2, B3.
[0051] Figure 4 An exemplary lookup table 16 is shown. The lookup table 16 provides route information about individual sorting areas. In particular, in the lookup table, it is stored which exits of a certain conveying area lead to which destinations within the conveying device.
[0052] In the following, this information, which is independent of the individual objects to be transported, is referred to as "routing conditions". Figure 3 As can be seen in FIG. 1 , an object traveling to a certain destination needs to pass through several sorting areas 2b, 2d. In each sorting area, the object needs to be routed through one of the multiple exits. The routing conditions are stored locally in the zone controller.
[0053] As an example, any object destined for D5 needs to pass through - among others - sorting areas B1 and B2. At sorting area B1, exit O1 will be used; at sorting area B2, exit O2 will be used (see also Figure 2 b), the corresponding exits are marked with solid arrows.
[0054] As another example, any object 9 intended to reach destination D1 needs to pass through sorting area B1, but does not need to pass through sorting area B2. In sorting area B1, exit O2 (see also Figure 2 b).
[0055] Figure 4 The lookup table in reflects the general routing conditions described above. Here, Figure 4 a and Figure 4 b shows two different embodiments of a lookup table, from which it should be apparent that there are many ways to provide routing conditions in such a table.
[0056] Therefore, based on the destination information associated with the object, the zone controller 11 can send a signal to the relevant sorting zone to sort the object to the correct outlet O1, O2.
[0057] Figure 5 A flow chart showing the steps occurring during the transport of objects from a feed station F to a destination D.
[0058] In step S1, the objects to be conveyed are fed into the conveying device, for example at the feeding station 1. The zone controller 11a controlling the operation of the feeding station F1 sends a first message M1 to the object data agent 10 via the bus 13 (see Figure 3 ). In the message M1, the zone controller 11 provides the information that an object has been fed. The message M1 also contains the ID of the feeding station F1 (Feeding ID, see below) and a timestamp of the date and time of the feeding event (Feeding Time, see below).
[0059] In step 2, the object data agent 10 creates a new object data set 14. The object data set 14 includes information about the objects to be conveyed which were recently fed into the feed station F1. Figure 6 An exemplary object dataset 14 created in step S2 is shown.
[0060] The object data set 14 includes the following data values:
[0061] intID: An explicit unique internal identifier used to identify each object transported within the device. The identifier can be a counter that corresponds to the sequential position of all transported objects. The explicit unique internal identifier can be replaced by an implicit internal identifier as described below -
[0062] Feed time (feedInTime): A timestamp indicating the calendar date (here May 24, 2022) and date time (here 16:11:13) when the object was fed into the feed station.
[0063] Feed ID (feedInID): a unique identifier for identifying a feed station (eg, feed station F1) that feeds objects.
[0064] Label ID: A unique label identifier provided as machine-readable information on the object 9 itself. Typically, the label ID is provided on the object as a printed code (e.g., a barcode or a QR code). In an embodiment, the label identifier may not be printed, such as an RFID code provided by an RFID tag attached to the object.
[0065] Destination ID: A unique identifier that identifies the destination to which the object is to be transported in the transport device.
[0066] DestinationTime: A timestamp indicating the calendar date and time at which the object arrives at the destination.
[0067] Weight: The weight of the object to be transported.
[0068] The combination of the value of the feed time and the feed ID already provides an implicit unique internal identification, because only one object can be fed at a time at a single feed station. The combination can be used as an internal identification in all other steps here and within the scope of this specification to replace the explicit internal identification.
[0069] In step 3, the object data agent 10 sends a second message M2 to all the zone controllers 11, including the zone controller 11a of the feed station F1. In the second message M2, the first object that has just entered through the feed station F1 is introduced to all the zone controllers 11. The second message M2 contains information related to Figure 6 A copy of the object dataset for the object shown.
[0070] During steps S2 and S3, most of the data fields are empty (also means: filled with placeholders). During the further processing, the data fields are increasingly filled with data that are important for the further transport processing.
[0071] Now, the object 9 is conveyed from the feed station F1 in the direction of the sorting area B3. Therefore, the first area controller 11a - controlling the feed station F1 which has fed the object - provides the internal identification to the area controller 11b of the subsequent conveying area. The subsequent controller 11b now knows that the object data set of "obj0000001" is associated with the next arriving object.
[0072] The subsequent regional controller 11b needs to perform a routing decision. Therefore, the regional controller 11b analyzes the object data set of "obj0000001", which does not include any values for "destination ID" and "tag ID"; there is no value set for "weight". Therefore, it is currently unknown which object obj0000001 is (from an external perspective) and to which destination D it is to be transported. In addition, the weight is unknown.
[0073] The controller 11b can access Figure 7 The lookup table shown contains the routing conditions for the sorting area B3. Since at least one of the tag ID and the weight value is not available in the relevant object data set 14, the object needs to go through exit O2, which guides the object to the barcode scanner S and the weighing station W. Therefore, in step S4, it is checked whether the predetermined value of the object data set is available, and a sorting decision is made based on the check.
[0074] In step S5, and as a result of the routing decision of step 4, the object is conveyed through the second exit O2 of the sorting area B3 to direct the object to a station S, W where one or more missing data of the object data set value can be acquired.
[0075] Therefore, in step S6 (see Figure 5 ), the scanning station S and the weighing station W provide the missing values of the tag ID and the weight. In step S6, the regional controller 11c of the control station S, W also sends a third message M3 to the object data agent 10, which contains the value tag ID "987654321" and weight "750g" associated with the intID "obj0000001".
[0076] Also in step S6, the object data agent 10 adds the most recently acquired value to the object data set 14, so that the updated object data set includes the following: Figure 8 The updated object data set 14 is sent out by the object data proxy 10 as a new second message M2.
[0077] In principle, the second message M2 can be regarded as a global notification message M2, in which the object data agent 10 sends the updated object data set to multiple regional controllers within the device. Therefore, the second message M2 is broadcast to all regional controllers through the network; regional controllers interested in the information about the object data set can receive the message and can store the relevant data in a local memory for later use during control.
[0078] The second message M2 relating to a specific object data set belonging to a specific object to be transported can be broadcast by the object data proxy 10 in different situations, for example always, when the object data set in the object data proxy is updated at regular intervals and / or upon request of the zone controller 11, etc. Thus, the object data set is sent to the controller in a manner independent of the actual transport operation.
[0079] During scanning, the scanner may also scan the destination information if it is provided at the object itself, for example in print on the object. The destination information may include any explicit destination ID, or may also include implicit information that provides an association with the destination ID.
[0080] In step S7, the destination information, in particular the destination ID, is assigned to the object data set 14. In an embodiment, the device conveyor can access a database 15 that provides associations between destination IDs based on the tag ID. Once the object data agent determines the destination ID, a new second message M2 is sent to all zone controllers 11, which includes the following information: Fig. 9The updated object data set shown in the figure, wherein the updated object data set now also includes the value "D5" as the destination ID. Therefore, all zone controllers are set to know that the objects 9 they belong to need to be transported to the selected destination D5.
[0081] In step S8, the object 9 is conveyed in the direction of the destination so as to approach one of the sorting areas B1, B2. The area controllers 11d, 11e (each of which controls the operation of the sorting areas B1, B2) have previously received the latest updated object data set in the new second message M2. In the case where the relevant object will approach the corresponding sorting area, the corresponding area controllers 11d, 1e can control the sorting operation of the sorting area in such a way that the relevant object is conveyed in the direction of the destination D5 as described above.
[0082] In step 9, the object is finally sorted to the destination D5 in the sorting area B4, which finally leads to the destination D5. In addition, as mentioned before, the controller 11f that controls the sorting area B4 operates with the help of the lookup table. Now, the object is finally delivered to the destination D5.
[0083] When the object 9 is finally delivered to the correct destination through the sorting area B4 , the controller 11 f controls the last sorting area before the destination sends a fourth message M4 to the object data agent 10 .
[0084] The fourth message M4 contains time information indicating the time when the object has been delivered to the correct destination D5. At this time, the object data agent 10 can update the destination time value such as Fig.10 The object dataset 14 shown may be updated, and a new second message M2 including the updated object dataset may be sent.
[0085] At this point, the object data set 14 contains all relevant values in view of the conveying / sorting operation. Therefore, the object data set includes a value that clearly indicates that the sorting operation has been completed, because the main value is set to a value. In particular, a value indicating that the object has been delivered to the destination is set.
[0086] The object data set 14 associated with the delivered object 9 is now no longer associated with the operating components of the several conveying zones. In particular, once the zone conveyor receives the updated second message M2, the object data set belonging to the delivered object can be deleted from the local memory of the operating zone controller in order to clear the memory for a new object data set belonging to the next object to be conveyed.
[0087] Furthermore, it is not required that all sorting controllers 2b, 2d store all transmitted object data sets. Individual sorting controllers may decide whether to store any transmitted object data sets. Next, there is an example where storage may not be required.
[0088] according to Figure 4 b, in sorting section B1, all objects with destinations D1, D2 and D3 must go out of exit O2. All other objects ("else") must go out of exit O1. Since the routing conditions include default conditions 16d for all other destinations, the sorting controller 11d only needs to check whether there are any objects that belong to non-default conditions. Fig. 9 The object data set 14 shown in FIG. 1 indicates that the object is intended to reach the destination D5. Figure 5 b, the destination D5 is covered by the default condition 16d. The sorting controller 11a is adapted to sort unknown objects (for which no object data set is provided) in the same way as objects under the default condition. Therefore, the unknown objects at the sorting section B1 are sorted in the outlet O1 by the sorting controller 11d. Therefore, in order to operate the sorting section B1 correctly, the relevant zone controller 11d controlling the sorting section B1 does not need to store the following information: Fig. 9 The object dataset 14 is shown.
[0089] The situation is different for sorting section B2, see Figure 4 b (right side). Here, destination D5 belongs to the explicit routing condition and not the default condition. Therefore, the sorting controller needs to know the Fig. 9 The objects in the object data set will be sorted to the exit O2. Therefore, Fig. 9 The object dataset 14 is essential for the operation and will be stored in the sorting controller 11f that controls the sorting section B4.
[0090] Fig.11 Shown according to Figure 3 A portion of a conveying device in which an additional destination branch including additional destinations D10 to D12 has been inserted. In order to support the additional destinations, an additional sorting section B5 is also inserted to support sorting operations between destinations D7 to D9 and the newly added destinations D10 to D12.
[0091] The decentralized structure of the conveyor means that only simple database adjustments need to be performed. Figure 4 The lookup table shown is still valid, since the default condition 16d has provided sufficient instructions to support the newly added destinations D10-D12 at sorting segments B1 and B2. Here, the newly added destinations are completely covered by the default condition 16d.
[0092] At this point, you only need to generate Fig.12 A new lookup table 16 or Fig.12 b to configure the added sorting segment B5.
[0093] No adjustments need to be made at the data proxy 12 .
[0094] Reference numerals list
[0095] 1 Conveying device
[0096] 2a…d Conveying area
[0097] 3 Conveyor rollers
[0098] 3M Motorized Roller
[0099] 4 Connectors
[0100] 5 Presence sensor
[0101] 8 Support frame
[0102] 9 Objects being transported
[0103] 10 Object Data Proxy
[0104] 11 Zone Controller
[0105] 12 Central Programmable Logic Controller (PLC)
[0106] 13 Bus connection
[0107] 14 Object Dataset
[0108] 15 Database
[0109] 16 Lookup Table
[0110] I Entrance to the conveying area
[0111] O Exit of conveying area
[0112] D. Destination
[0113] F Feeding Station
[0114] S Scan Station / Scanner
[0115] W Weighing Station
Claims
1. An internal logistics conveying device (1), which is suitable for selectively conveying objects (9) from at least one feeding station (F) to a selected destination (D5) among a plurality of destinations (D1-D12), The conveying device (1) comprises: - a plurality of conveying areas (2), each conveying area (2) being suitable for conveying objects (9) from an inlet (I) of said conveying area (2) to an outlet (O) of said conveying area (2), - a plurality of zone controllers (11) adapted to control the operation of the conveying zones (2); in, The conveying areas (2) are arranged so that the objects (9) can be transferred from an outlet (O) of a preceding conveying area (2) to an inlet (I) of a subsequent conveying area (2); At least one of the conveying areas is a sorting area (2b, 2d) having at least two exits (O1, O2), and the area controller (11) controlling the sorting area (2b, 2d) is a sorting controller (11b, 11d, 11e). wherein each sorting controller (11b, 11d, 11e) is adapted to control the sorting area (2b, 2d) in such a manner that the sorting area (2b, 2d) selectively transports the object from the entrance to a selected one of the at least two exits (O1, O2); Features The internal logistics conveying device (1) comprises - an object data agent (10) connected to each of said zone controllers (11) via a data connection (13); The zone controller (11) is adapted to receive an object data set (14) from the data agent (10) via a data connection (13), The object data set (14) contains information related to the transported object (9), and the zone controller (11) is suitable for controlling the operation of the relevant zone, in particular the sorting operation, based on the object data set (14) provided by the data agent (10).
2. The internal logistics conveying device (1) according to the preceding claim, Features The object data set (14) provided by the object data agent (10) contains destination information (destination ID), the destination information indicating a selected destination (D5) to which the associated object is to be transported, Wherein, the sorting controller (11b, 11d, 11e) is suitable for controlling the sorting area (2b, 2d) based on the provided destination information in such a way that the sorting area (2b, 2d) transports the object to a selected exit, wherein the selected exit leads to the selected destination (D5).
3. An internal logistics conveying device (1) according to any one of the preceding claims, characterized in that The object data set (14) does not contain any routing information indicating which of the plurality of outlets is to be used in a single sorting operation, and / or The sorting controller (11b, 11d, 11e) is adapted to control individual sorting operations using only the destination information (destination ID) from the object data set (14) without using any routing information provided in the data set.
4. An internal logistics conveying device (1) according to any one of the preceding claims, Features The sorting controller (11b, 11d, 11e) accesses routing conditions (16), in particular a lookup table (16), The routing condition (16) includes information about which of the exits leads to which of the destinations.
5. An internal logistics conveying device (1) according to any one of the preceding claims, Features The routing conditions (16) include a default condition (16d) that is valid for non-specified destinations ("rest").
6. An internal logistics conveying device (1) according to any one of the preceding claims, Features The sorting controller (11b, 11d, 11e) is adapted to store the routing condition (16) locally within the sorting controller (11b, 11d, 11e).
7. An internal logistics conveying device (1) according to any one of the preceding claims, Features At least one of the sorting controllers (11a) is adapted to control the sorting operation in the following manner: checking the object dataset (14) associated with a specific object (9) for specific missing values (weight; tag ID); According to the inspection result, the sorting operation of the sorting area is controlled in such a way that the object is guided to the area (S, W) where the missing value (weight; tag ID) can be acquired.
8. An internal logistics conveying device (1) according to any one of the preceding claims, Features The object data set (14) is broadcast by the data agent (10) to a plurality of zone controllers (2) in a non-directional manner independent of the position of the associated object (9).
9. The internal logistics conveying device (1) according to any one of the preceding claims, Features The object data set (14) is broadcast by the data agent (10) to at least one zone controller (2) independently of the actual transport operation involving the associated object (9).
10. The internal logistics conveying device (1) according to any one of the preceding claims, Features - once the data object set has been updated with new values and / or - at regular intervals and / or - Upon request from the Regional Controller, The object data set (14) is broadcasted by the data agent (10) to a plurality of areas.
11. The internal logistics conveying device (1) according to any one of the preceding claims, Features The sorting controller (11b, 11d, 11e) is adapted to store the routing conditions (16) locally within the sorting controller (11b, 11b, 11d, 11e) in a manner that is independent of the actual position of the belonging object.
12. The internal logistics conveying device (1) according to any one of the preceding claims, Features The zone controller (11), in particular the sorting controller (11b, 11d, 11e), is adapted to check, based on the object data set (14), whether it is necessary to store the object data set to support a subsequent sorting process; in particular, to check whether the conveying zone associated with the sorting controller (110b, 11d) is located on a route from the object to the selected destination.
13. The internal material flow conveying device (1) according to the preceding claim, Features If the previous checking step leads to the result that storage of the object data set is not necessary to support operations at the relevant segment, the controller (11) decides - selectively not storing the object data set (14) locally in the sorting controller (11b, 11d) and / or - selectively deleting the object data set locally from the sorting controller (11b, 11d).
14. The internal logistics conveying device (1) according to any one of the preceding claims, Features Apart from the zone controllers, the intralogistics conveying device does not comprise a central programmable logic controller (PLC) particularly adapted to control the sorting operations of the sorting zones.
Citation Information
Patent Citations
Conveyor and method for manufacturing conveyor
EP3222564B1
Event driven multicast material sorting system
US20020045969A1
Transport system, in particular an airport luggage transport system, and a controller for a transport system
US20050065642A1
Driver board control system for modular conveyor with address-based network for inter-conveyer communication
US7996104B2