![TR-Electronic encoTRive MD-025-CO-C Series Manual Download Page 151](http://html1.mh-extra.com/html/tr-electronic/encotrive-md-025-co-c-series/encotrive-md-025-co-c-series_manual_1146659151.webp)
CANopen communication
Printed in the Federal Republic of Germany
©
TR-Electronic GmbH 2007, All Rights Reserved
05/16/2007
TR - EMO - BA - DGB - 0013 - 00
Page 151 of 260
4.2.2.1 SDO (Service Data Object)
Objects can be read or written with SDOs. This is a confirmed service. The so-called
SDO Client
specifies in its "Request" the parameter, the access type (read/write) and
the value if applicable. The so-called
SDO Server
executes the write or read access
and answers the request with a "Response". In the case of error, an error code
provides information on the cause of the error. Transmit SDO and receive SDO are
differentiated by their function codes.
encoTRive represents an SDO server and uses the following function codes for SDOs:
Function code
COB-ID
Meaning
11 (1011 bin) 0x580 + Node ID
encoTRive
→
SDO Client
12 (1100 bin) 0x600 + Node ID
SDO Client
→
encoTRive
Table 2: COB-IDs for Service Data Object (SDO)
Example:
Node ID encoTRive: 112 (0x70)
•
A message with COB-ID 0x5F0 (= 0x580+0x70) corresponds to an SDO from
encoTRive to the SDO client.
•
A message with COB-ID 0x670 (=0x600+0x70) corresponds to an SDO from
the SDO Client to the encoTRive.