Networked cameras configured for camera replacement

Abstract

A camera is provided that has an image sensor for recording image data from a field of vision, a communication interface for connection to at least one further camera in a network, a control and evaluation unit for reading the image data, and a memory in which a parameter set for the operation of the camera is stored, At least one further parameter set for the operation of at least one further camera of the network is stored in the memory here.

Claims

1. A camera, comprising: an image sensor for recording image data from a field of vision; a communication interface for connection to at least one further camera in a network; a control and evaluation unit for reading the image data; and a memory in which a parameter set for the operation of the camera is stored, wherein at least one further parameter set for the operation of the at least one further camera of the network is stored in the memory, wherein a device map including an identification or address of the at least one further camera is stored in the memory, wherein the control and evaluation unit is configured to recognize a camera replacement in the network when the at least one further camera is no longer connected in the network and a new camera is subsequently connected in the network, and wherein the control and evaluation unit is further configured to report itself as a master to the network upon recognizing the camera replacement, the master being responsible for transferring the device map and the at least one further parameter set to the new camera.

2. The camera in accordance with claim 1, wherein a network configuration is stored in the memory.

3. The camera in accordance with claim 1, wherein the device map includes the identification or the address for ones of the camera and the at least one further camera which mutually save a parameter set for one another.

4. The camera in accordance with claim 1, wherein further parameter sets for the operation of at least two further cameras of the network are stored in the memory.

5. The camera in accordance with claim 1, wherein the control and evaluation unit is configured to communicate the network configuration of the no longer connected further camera to the new camera.

6. The camera in accordance with claim 1, wherein the control and evaluation unit is configured to communicate an updated device map to the network including the new camera.

7. The camera in accordance with claim 1, wherein the control and evaluation unit is configured to transfer the further parameter set stored for the previously connected further camera to the new camera.

8. The camera in accordance with claim 1, wherein the control and evaluation unit is configured to initiate a transfer to the memory of the new camera of the further parameter sets of a further camera that were stored in the memory of the no longer connected camera.

9. The camera in accordance with claim 1, wherein a control and evaluation unit of the new camera is configured to recognize that it is in a still unconfigured state and to wait for communication requests of the network and/or to recognize that the network is not the one of the at least one further camera for which a further parameter set has been stored and to wait for communication requests of the network.

10. The camera in accordance with claim 1, wherein the control and evaluation unit is configured to compare a further parameter set stored in the memory with a further camera.

11. The camera in accordance with claim 1, wherein the control and evaluation unit is configured to read codes in the image data.

12. A camera apparatus having a plurality of cameras that are connected in a network, the cameras each comprising an image sensor for recording image data from a field of vision, a communication interface for connection to at least one further camera in a network, a control and evaluation unit for reading the image data, and a memory in which a parameter set for the operation of the camera is stored, wherein at least one further parameter set for the operation of the at least one further camera of the network is stored in the memory, wherein a device map including an identification or address of the at least one further camera is stored in the memory, wherein the control and evaluation unit is configured to recognize a camera replacement in the network when the at least one further camera is no longer connected in the network and a new camera is subsequently connected in the network, and wherein the control and evaluation unit is further configured to report itself as a master to the network upon recognizing the camera replacement, the master being responsible for transferring the device map and the at least one further parameter set to the new camera.

13. The camera apparatus in accordance with claim 12 that is configured as a reading tunnel for reading codes on objects that are conveyed through the reading tunnel.

14. A method for the replacement of a camera in a camera apparatus, comprising the steps of: establishing a camera network including a plurality of cameras, wherein each of the cameras has a device map stored in memory including an identification or address of at least one further camera of the camera network, and wherein each of the cameras has a parameter set for operation of the corresponding one of the cameras stored in the memory, and wherein each of the cameras has a further parameter set for operation of the at least one further camera stored in the memory; upon recognition of replacement of one of the cameras in the camera network with a new camera, one of the cameras reporting itself as a master to the network, the master being responsible for transferring the device map and the further parameter set to the new camera; and transferring the further parameter set of a replaced one of the cameras and the device map to the new camera.

Description

(1) The invention will be explained in more detail in the following also with respect to further features and advantages by way of example with reference to embodiments and to the enclosed drawing. The Figures of the drawing show in:

(2) FIG. 1 a schematic three-dimensional view of a camera apparatus above a conveyor belt with objects to be detected;

(3) FIG. 2 a supplementary sectional representation of individual cameras of the camera apparatus with their fields of view;

(4) FIG. 3 a block diagram of an individual camera;

(5) FIG. 4 a flowchart of an initialization phase of a camera apparatus having a plurality of cameras;

(6) FIG. 5 a representation of data and parameters stored in the cameras after the initialization phase;

(7) FIG. 6 a flowchart for the transfer of parameters on a replacement of a camera, wherein the new camera has been set to works settings;

(8) FIG. 7 a representation of data and parameters stored in the cameras directly after the connection of the new camera;

(9) FIG. 8 a representation of data and parameters stored in the cameras after transfer of a network configuration to the new camera;

(10) FIG. 9 a representation of data and parameters stored in the cameras after transfer of a device map to the new camera;

(11) FIG. 10 a representation of data and parameters stored in the cameras after completion of the transfer of the parameters;

(12) FIG. 11 a flowchart for the transfer of parameters on a replacement of a camera, wherein the new camera has been set to settings from a network in which it had previously been operated; and

(13) FIGS. 12-15 a representation of data and parameters stored in the cameras in accordance with FIGS. 8-11 for the flowchart of FIG. 11.

(14) FIG. 1 shows a schematic three-dimensional view of or a multi-camera system or of a camera apparatus 10 above a conveyor belt 12 having objects 14 to be detected on which codes 16 are attached by way of example, but not necessarily. The conveyor belt 12 is an example for the production of a stream of objects 14 which move relative to the stationary camera apparatus 10. Alternatively, the camera apparatus 10 can also observe a scene without a conveyor belt 12. The camera apparatus 10 comprises a plurality of cameras 18.sub.1 . . . 18.sub.n, where n=4 by way of example in FIG. 1. In addition to the shown cameras 18.sub.1 . . . 18.sub.n in a perspective from above, further cameras can be installed from a different direction, for example laterally, to detect further object sides. The cameras 18.sub.1 . . . 18.sub.n are arranged in a row transversely to the conveyor belt 12, with other arrangements in a differing orientation or as a matrix, for example, also being conceivable.

(15) FIG. 2 additionally shows the arrangement of the cameras 18.sub.1 . . . 18.sub.n and their fields of view 20.sub.1 . . . 20.sub.n above the conveyor belt 12 in a sectional representation, with now a different example with more cameras 18.sub.1 . . . 18.sub.n being selected, and FIG. 3 shows an individual camera 18.sub.j. The cameras 18.sub.1 . . . 18.sub.n each have an image sensor 22 having a plurality of light reception elements arranged to form a pixel row or a pixel matrix as well as an objective 24. A respective control and evaluation unit 26 reads image data and is responsible for camera-related control work and evaluations. The control and evaluation unit 26 has a memory 28 in which parameters, network configurations, and a device map having identities or addresses of further cameras 18.sub.1 . . . 18.sub.n can be stored. Data, in particular parameters for other cameras 18.sub.1 . . . 18.sub.n, are also saved in the memory 28; this will be explained in more detail further below. The cameras 18.sub.1 . . . 18.sub.n are linked to a network via a respective communication point 30, for instance via Ethernet or CAN. The cameras 18.sub.1 . . . 18.sub.n furthermore preferably have an illumination 32 to illuminate their own fields of view 20.sub.1 . . . 20.sub.n on a recording. A higher ranking control 34 can be provided in the network whose work can instead be taken over at least partly by a camera 18.sub.1 . . . 18.sub.n. The cameras 18.sub.1 . . . 18.sub.n are preferably of the same design among one another to reduce system complexity. They can, however, work with different configurations and recording parameters.

(16) In a preferred embodiment, the cameras 18.sub.1 . . . 18.sub.n are configured as code readers in which the control and evaluation unit 26 additionally acts as a decoding unit for reading code information and corresponding pre-processing for localizing and preparing code regions. It is also conceivable to detect streams of objects 14 without codes 16 and accordingly to dispense with the decoding unit itself or its use, for example for an inspection or quality control. In addition, a decoding can also take place downstream outside the cameras 18.sub.1 . . . 18.sub.n on their image data, in particular in the higher ranking control 34.

(17) The conveyor belt 12 is too wide to be detected by an individual camera 18.sub.1 . . . 18.sub.n. The fields of view 20.sub.1 . . . 20.sub.n of the cameras 18.sub.1 . . . 18.sub.n therefore preferably complement one another in the transverse direction of the conveyor belt 12 with a partial mutual overlap. An optional geometry detection sensor 36, for example in the form of a distance measuring laser scanner known per se, is located above the individual cameras 18.sub.1 . . . 18.sub.n with respect to the direction of movement of the conveyor belt 12 to measure the three-dimensional contour of the objects 14 on the conveyor belt 12 in advance, with dimensions, volume, position, and shape resulting therefrom. In addition, the geometry data can be used to trigger the recordings and to focus the cameras 18.sub.1 . . . 18.sub.n.

(18) FIG. 4 shows a flowchart for an initialization phase of the camera apparatus. Only those steps among the large number of conceivable or required steps of an initial putting into operation are discussed here that are related to a mutual parameter saving and return parameter transfer.

(19) The network is configured in a step S1, with every form of an automatic, manual, or semiautomatic configuration being possible. The cameras 18.sub.1 . . . 18.sub.n are initially set to works settings, but have a unique serial number or another individual feature that could alternatively also be negotiated. The initialization can, for example, be coordinated by a master among the cameras 18.sub.1 . . . 18.sub.n or by the higher ranking control 34. A device recognition takes place first. A distinguishable network address such as an IP address or a CAN node ID is then assigned to the recognized devices. The cameras 18.sub.1 . . . 18.sub.n are thus able to communicate with one another over the network.

(20) A device map is generated and distributed in a step S2. The device map, for example, includes the serial numbers, IP addresses, and node IDs of the connected cameras 18.sub.1 . . . 18.sub.n. It is sufficient for the mutual saving and transferring back of parameter sets for the device map of every camera 18.sub.1 . . . 18.sub.n to include a further camera 18.sub.1 . . . 18.sub.n, but better two or more cameras 18.sub.1 . . . 18.sub.n, as a precaution for protection from a failure. The device maps can be thinned out accordingly before or after the distribution.

(21) The parameter sets of the individual cameras 18.sub.1 . . . 18.sub.n are mutually communicated and stored in the respective memory 28 in a step S3. This is also called parameter cloning. Which cameras 18.sub.1 . . . 18.sub.n they respectively are is preferably decided with reference to the device maps. The device maps are therefore not necessarily complete representations of the camera apparatus 10, but only a section of the parameter cloning. There is thus at least a simple redundancy by storing a parameter set in a respective camera 18.sub.1 . . . 18.sub.n itself and in its at least one partner, preferably double redundancy with two partners up to maximum security when each camera 18.sub.1 . . . 18.sub.n stores the parameter sets for every other camera 18.sub.1 . . . 18.sub.n.

(22) An exemplary result of the initialization phase is shown in FIG. 5. In order not to show too much information, only three cameras 18.sub.1 . . . 18.sub.n are shown without thereby actually restricting their number. The cameras 18.sub.1 . . . 18.sub.n will from here on frequently in a simplifying manner be called first, second, and third cameras, without reference numerals, in accordance with the column position in the table shown without these names having any special or even restrictive technical significance. The data naturally do not have to be written to the memory 28 in this form; FIG. 5 is one arbitrary representation of many. The respective serial numbers, that were already stored ex works, are in the first line. It must be remembered that a different unique feature such as a MAC address would equally be usable. The second line and third line show the network configuration by way of example with an IP address or a node ID that have been numbered consecutively for reasons of clarity. The fourth line includes the respective device map; the cameras are accordingly aware of one another, i.e. the first camera knows the second and third cameras and so forth. The respective saved parameter sets for the two other cameras are shown in the same manner in the fifth line. In addition, and not shown here, each camera holds its own parameter set in memory. The parameter sets are preferably associated via at least one of the features serial number, IP address, node ID. This facilitates the identification of a replacement device.

(23) FIG. 6 shows a flowchart for a replacement of a camera 18.sub.1 . . . 18.sub.n of the camera apparatus 10. A particularly advantageous automatic configuration is achieved with these steps, but each step that is not explicitly marked as indispensable is to be considered optional. FIGS. 7 to 10 illustrate intermediate results. A device exchange is very considerably simplified thanks to the automatic parameter cloning for which FIG. 6 shows an embodiment.

(24) A defect is discovered or there is another reason for a replacement in a step S11. The new camera 18.sub.1 . . . 18.sub.n is installed instead of the old camera 18.sub.1 . . . 18.sub.n, is connected to its connections for supply and network connection, and is then switched on. The new camera 18.sub.1 . . . 18.sub.n automatically receives the configurations and parameters stored in the network on booting and is immediately ready for use. This will now be described in detail.

(25) In this embodiment, the new camera 18.sub.1 . . . 18.sub.n is initially set to works settings. It accordingly determines in a step S12 that it does not have a valid network configuration and remains silent. However, it transmits a general message with its identity to indicate its new connection.

(26) FIG. 7 shows the stored information at this time in a representation similar to FIG. 5. New information or information particularly relevant to the explanation is printed in bold in each case. The previous serial numbers, network configurations, device maps, and saved parameter sets are furthermore stored in the first and second cameras. However, in part this relates to the old third camera that is no longer connected. Only its serial number and an initial setting for the IP address and node ID not valid in the network are stored in the third camera.

(27) The absence of the old camera and the addition of the third camera is noticed in a step S13. The second camera is here by way of example the one that first recognizes the replacement. It communicates this to the other cameras, in particular by broadcast, and makes itself the cloning master in a step S14. It thus takes over a temporary master function for the communication in the further procedure in accordance with FIG. 6.

(28) In a step S15, the second camera acting as the cloning master communicates a valid network configuration to the new third camera. This is preferably the still stored network configuration of the predecessor whose position the third camera now takes over. Alternatively, a new network configuration could also be assigned and communicated to all. The third camera thus becomes a participant in the network and can communicate with the other cameras without interference.

(29) FIG. 8 illustrates the information now stored in the cameras. With respect to FIG. 7, the default values for the IP address and the value node ID for the third camera are now overwritten with a valid network configuration. The second camera is shown dark from now on to illustrate its function as a cloning master. The tables would, however, not look different if, for example, the first camera acts as the cloning master.

(30) In a step S16, the second camera acting as the cloning master determines current device maps with the new third camera and transfers these device maps to the other cameras. It is conceivable that the device map is tailored by the cloning master and/or in the receiving cameras because every camera is not necessarily responsible for the parameters of every other camera, but optionally makes a relevant selection.

(31) FIG. 9 illustrates the result of this step S16. The old camera is replaced with the new third camera in the device maps of the first camera and of the second camera. The third camera now stores a device map having the two other cameras.

(32) A first part of the actual parameter cloning then follows in a step S17. The third camera takes over the parameters stored for the old, replaced camera from the cloning master or from another camera responsible therefor. The third camera can thus replace the old camera without another parameterization or configuration. This functionally corresponds to the conventional step of inserting and reading the SD card of the old camera in the new camera.

(33) The parameter cloning is completed by a second part in a step S18. The third camera receives the parameter set of the cameras registered to its device map, that is of the first camera and of the second camera, and saves them in its own memory 28. The third camera could thus now take over the role of the cloning master or at least of the outsourced parameter memory on a future replacement of the first or second cameras.

(34) FIG. 10 shows the finally stored information. The third camera now has parameter sets for the two other cameras. Conversely, the first and second cameras continue to store the parameter set for the third camera. This parameter set is initially identical with that of the old device; 3 {2005 0003}=3 {2006 0128} therefore applies in the last line of the table. If, however, the third camera should be directly reconfigured, the first and second cameras thus hold the new parameter set of the third camera in future and no longer the obsolete parameter set of the replaced old device.

(35) FIG. 11 shows a flowchart for an alternative embodiment and FIGS. 12 to 15 illustrate intermediate results, analog to FIGS. 7 to 10. Unlike the embodiment described with reference to FIGS. 6 to 10, the new camera, again the third camera, is now not a device at works settings, but was already used in another network.

(36) A network configuration, device map, and saving of parameter sets for further cameras are therefore, unlike in step 11 of FIG. 6, already stored in the third camera in step 21. This is shown in FIG. 12, where values have already been entered everywhere in the last column that are, however, not valid in the new network, with the exception of the serial number.

(37) There is now the challenge in a step S22 that the third camera initially does not know that it is now connected in a new network. It must be prevented that it disseminates its invalid stored parameter sets and interferes in the network communication. The third camera recognizes this situation in that none of the cameras entered in its device map can be reached. The third camera therefore remains silent and waits until a new network configuration, a new device map, and new parameter sets are transferred to it.

(38) In another respect, this step is a further reason, in addition to the increased redundancy and safety, why every camera should preferably mutually save parameter sets with two further cameras. In the case of a device exchange, the only partner of the replaced device remaining in the network would namely otherwise erroneously assume that it is a completely new network because none of the cameras registered in its device map replies and that could result in inconsistent states.

(39) The further steps S23 to S28 then no longer differ from the steps S13 to S18 of FIG. 6. The invalid old device map for the third camera is still shown in FIG. 13 and the parameter sets of the partners of the earlier network are still shown in FIGS. 13 and 14. They are successively overwritten. The invalid information could alternatively also be deleted as soon as the third camera has determined in step S22 that it is in a new network. FIGS. 13 to 15 would thus look exactly as FIGS. 8 to 10 except for the different serial number of the third camera.

(40) Alternatively to the flowchart of FIG. 11, the new camera can first be set to works settings and then the flowchart of FIG. 6 can be used. This is, however, possibly a little awkward because the service engineer cannot easily address the new camera in isolation to trigger the reset. It is additionally unfavorable to require a manual intervention of the service engineer at all because this could be forgotten and thus represents an additional error source.