METHOD FOR ACCESSING A NUMBER OF SLAVE DEVICES WITH REGISTERS BY A MASTER DEVICE OVER A NETWORK

Abstract

A computer, such as a programmable logic controller (PLC), implemented method for accessing a number of slave devices having a number of registers by a master device on a network includes the steps of: providing a generic driver software in the master device for accessing slave devices on the network; reading by the master device description files, describing the slave devices on the network; and using the description files for converting data read from and written to the generic driver when accessing the slave devices on the network.

Claims

1: A computer, such as a programmable logic controller (PLC), implemented method for accessing a number of slave devices having a number of registers by a master device on a network, the method comprising: providing a generic driver as software in the master device for accessing the slave devices on the network; reading by the master device description files, describing the slave devices on the network; and using the description files for converting data read from and written to the generic driver when accessing the slave devices on the network.

2: The computer implemented method according to claim 1, wherein the data exchanged between the generic driver and the slave devices has a uniform structure.

3: The computer implemented method according to claim 1, wherein the description files describe the functions of the registers for a slave device.

4: The computer implemented method according to claim 1, wherein the master device comprises a software layer with variables and wherein the description files are used to map the variables to the data read from and written to the generic driver.

5: The computer implemented method according to claim 1, wherein the network to which the master device and the slave devices are connected comprises a controller area network (CAN).

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The present invention will be described in even greater detail below based on the exemplary figures. The invention is not limited to the exemplary embodiments. Other features and advantages of various embodiments of the present invention will become apparent by reading the following detailed description with reference to the attached drawings which illustrate the following:

[0010] FIG. 1 shows a schematic diagram of an embodiment of the computer implemented method according to the invention.

[0011] FIG. 2 shows a schematic data diagram for the embodiment of FIG. 1.

DETAILED DESCRIPTION

[0012] This object is achieved with a computer implemented method for accessing a number of slave devices having a number of registers by a master device on a network, which method comprises the steps of: [0013] providing a generic driver software in the master device for accessing slave devices on the network; [0014] reading by the master device description files, describing the slave devices on the network; [0015] using the description files for converting data read from and written to the generic driver when accessing the slave devices on the network.

[0016] With the invention any slave device on the network is accessed by the generic driver in the same way. This allows one to have a single description or electronic data sheet on how any slave device on the network is to be accessed. Only after the generic driver has accessed a specific slave device to read some data and this data is sent further by the generic driver, the data is converted based on an description file. The same applies, when data is to be written to a slave device. In such a case, the data is first converted based on the description file and only after the conversion sent to the generic driver, which then accesses the slave device to write the converted data.

[0017] Since with the method according to the invention, a single generic driver is used to access all the slaves, the software does not need to be rewritten when changes are made to the topology of the network. Only a description file needs to be changed or added, but as these are read by the master device, the software of the master device does not require to be rewritten and recompiled.

[0018] In a preferred embodiment of the computer implemented method according to the invention, the data exchanged between the generic driver and the slave devices has a uniform structure. So, between the generic driver and the slave devices, there is no difference in the structure of the data being written to or read from the slave devices.

[0019] In yet another embodiment of the computer implemented method according to the invention, the description files describe the functions of the registers for a slave device.

[0020] For example, with a first type of slave device, the first register will contain the voltage value and a second register will contain the current value. A second type of slave device will contain the voltage value in a sixth register and the current value in a seventh register.

[0021] The description files will describe on which network address which type of slave device is present and also describe for all the data received from the generic driver, which part correspond to which particular value.

[0022] In a further preferred embodiment of the computer implemented method according to the invention the master device comprises a software layer with variables and the description files are used to map the variables to the data read from and written to the generic driver.

[0023] Preferably, the network to which the master device and the slave devices are connected, is a controller area network (CAN).

[0024] FIG. 1 shows a network 1 to which a number of slave devices 2 are connected as well as a master device 3. The master device 3 has a generic driver 4 which accesses the slave devices 2 on the network 1. The generic driver 4 is connected to a converter 5, which reads data from the generic driver 4 and writes data to the generic driver 4.

[0025] The converter 5 uses description files stored in a database 6 to be able to convert data read from the generic driver 4 and send it further to a next process 7 or to convert data received from the next process 7 and after conversion send it to the generic driver 4, such that it can be written in a generic way to one of the slave devices 2.

[0026] FIG. 2 shows a schematic data diagram for the embodiment of FIG. 1. Data 10 read from a slave 2 on the network by the generic driver 4 contains rows of data divided into a main index, a sub-index and the value present in the register, identified by main index and sub-index, of the specific slave 2. This data 10 would be meaningless in its current form for the next process 7 meaningless and has to be converted first by the converter 5.

[0027] Based on the address from where the data 10 is read, one of the description files 11, 12 is selected and used to convert the data 10. Each description file describes which parameter is present on which location within the data 10. This results in converted data 13, which can be further used by the next process 7. For example, the description file 11 defines that the value for parameter p2 can be found on index 2, sub-index 1. In the present example this results in a value of 0 for parameter p2 using the data 10.

[0028] While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description are to be considered illustrative or exemplary and not restrictive. It will be understood that changes and modifications may be made by those of ordinary skill within the scope of the following claims. In particular, the present invention covers further embodiments with any combination of features from different embodiments described above and below. Additionally, statements made herein characterizing the invention refer to an embodiment of the invention and not necessarily all embodiments.

[0029] The terms used in the claims should be construed to have the broadest reasonable interpretation consistent with the foregoing description. For example, the use of the article “a” or “the” in introducing an element should not be interpreted as being exclusive of a plurality of elements. Likewise, the recitation of “or” should be interpreted as being inclusive, such that the recitation of “A or B” is not exclusive of “A and B,” unless it is clear from the context or the foregoing description that only one of A and B is intended. Further, the recitation of “at least one of A, B and C” should be interpreted as one or more of a group of elements consisting of A, B and C, and should not be interpreted as requiring at least one of each of the listed elements A, B and C, regardless of whether A, B and C are related as categories or otherwise. Moreover, the recitation of “A, B and/or C” or “at least one of A, B or C” should be interpreted as including any singular entity from the listed elements, e.g., A, any subset from the listed elements, e.g., A and B, or the entire list of elements A, B and C.