METHOD FOR TRANSMITTING DATA VIA A CANOPEN BUS

• US 20130080585A1
• Filed: 03/29/2011
• Published: 03/28/2013
• Est. Priority Date: 03/31/2010
• Status: Active Grant

• Current Assignee: Schneider Electric Automation GmbH (Schneider Electric SE)
• Original Assignee: Schneider Electric Automation GmbH (Schneider Electric SE)
• Inventors: Schaffner, Heinz, Hampikian, Pascal
• Granted Patent: US 9,667,699 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

The invention relates to a method for transmitting data between a first automation appliance, and at least one second automation appliance, via a CANopen bus using a service data object as an SDO service, wherein an SDO client implemented in the first automation appliance is used to send a download or upload request to an SDO server implemented in the at least one second automation appliance, wherein the data are encapsulated in a CANopen frame by an application implemented in the first automation appliance or the at least one second automation appliance wherein the CANopen frame with the encapsulated data is transmitted or sent by means of an SDO service into or out of a data tunnel object defined in an object directory of the SDO server, and wherein the encapsulated data are decapsulated by the application implemented in the first or the at least one second automation appliance.

Claims

1. Method for transmitting data between a first automation device (50, 12, 14, 18), such as a user PC or a central control device, and at least one second automation device (24, 40), such as a field device, via a CANopen bus (20, 22) using a service data object as a SDO service, wherein an SDO client implemented in the first automation device (50, 12, 14, 18) is used to send a download or upload request to a SDO server implemented in the at least one second automation device (24, 40), wherein the data are encapsulated in a CANopen frame by an application (54, 84) implemented in the first automation device (50, 12, 14, 18) or the at least one second automation device (24, 40), wherein the CANopen frame with the encapsulated data is transmitted or sent by means of a SDO service into or out of a data tunnel object (80, 86) defined in an object dictionary (76) of the SDO server (82), and wherein the encapsulated data are decapsulated by the application (84) implemented in the first or the at least one second automation device (24, 40),

characterized in that

the method is used to configure and/or parameterize via the CANopen bus (20, 22) the at least one second automation device (24-40) that includes a MODBUS server, in that the data in the form of configuration and/or parameterization data are generated in the form of a MODBUS frame and encapsulated in said CANopen frame, and in that the CANopen frame is loaded by way of an SDO download in the data tunnel object (80, 86) of the SDO server of the at least one second automation device (24) and decapsulated.

2. Method according to claim 1,

characterized in that

a data transmission is carried out from the first automation device (50) to the at least one second automation device (24) by way of a SDO download to the data tunnel object (80) of the object dictionary (76), initiated by the application (54) implemented in the first automation device (50).

4. Method according to claim 1,

characterized in that

a preset SDO server channel is used for data transmission, wherein a second SDO server channel is used in the event of high data volume.

5. Method claim 1,

characterized in that

a single data tunnel object (80) is sufficient for simplex or half-duplex data transmission.

6. claim 1,

characterized in that

for a full-duplex data transmission at least two data tunnel objects (80, 86) in the object dictionary (76) of the SDO server are used.

7. Method according to claim 1,

characterized in that

the application (54) implemented in the first automation device (50) comprises a field device tool and at least one device type manager with which the parameterization and configuration data are generated in the form of MODBUS frames.

8. Method according to claim 1,

characterized in that

during a transmission of data from the at least one second automation device (24) to the first automation device (50) a protocol-specific part of the device type manager (DTM) implemented in the first automation device (50) must regularly query the at least one second automation device (24) with the application (84), whereby a CANopen communication DTM implemented in the application (84) executes the SDO upload request.

9. Method according to claim 1,

characterized in that

the data tunnel object (80, 86) is of the domain type.

10. Method according to claim 1,

characterized in that

the CANopen frame with the encapsulated MODBUS frame is sent via a routing functionality implemented in the first automation device (50) to the at least second automation device (24) with the appropriate address.

11. Method according to claim 1,

characterized in that

encapsulated data are transmitted in the form of parameter and/or configuration data and control programs.

12. Method according to claim 1,

characterized in that

the data transmission is carried out sequentially for each of the second automation devices (24-40) and/or is carried out when one of the second automation devices (24-40) is attached to the CANopen bus (20, 22).

3. Method according to claim,

characterized in that,

a data transmission is carried out from the at least one second automation device (24) to the first automation device (50) by way of a SDO upload from the data tunnel object (80), initiated by the application (54) implemented in the first automation device (50), wherein the application (54) addresses cyclically the application (84) implemented in the at least one second automation device (24).