This instruction only contains additional information about the programming of D-20-9/D-21-9 CANopen
pressure transmitter. For the standard information please refer to operating instructions No. 2059064.
2011h Maximum allowed Pressure18
2020h Min. Value Storage20
2021h Max. Value Storage20
2080h Uncompensated AD-Value20
2090h Process Value as Integer21
2100h User Device Name21
2201h Last Calibration Date Year22
2202h Last Calibration Date Month22
2203h Last Calibration Date Day22
2207h Date of Production Year23
2208h Date of Production Month23
2209h Date of Production Day23
2320h Configure Node-ID24
2321h Configure Bit Timing24
2330h Auto-Operational26
7122h AI Input Scaling 2 FV28
6123h AI Input Scaling 2 PV29
6124h AI Input Offset29
6125h AI Autozero30
6130h AI Input PV30
6131h AI Physical Unit PV31
6132h AI Decimal Digits32
6148h AI Span Start32
6149h AI Span End33
61A0h AI Filter Type34
61A1h AI Filter Constant34
6. Calibration35
Input Scaling35
Input Offset37
Input Autozero37
7. Filter38
8. Emergency Object (EMCY)39
9. Network Management Objects40
Module Control Services40
The structure of the synchronous and asynchronous PDO is identical.
The identifier of the PDO can be set via object 1800h.
Factory-set: 180h + NID
Byte 0 to byte 3 contains the currently configured process value.
The default settings are configured to object 2090h subindex 0 (process value as integer).
The coding corresponds to DS301, chapter 9.1.4.5 “Signed Integer”
The user can switch the mapping to object 6130h subindex 1 (process value as float).
Then the coding corresponds to DS301, chapter 9.1.4.6 “Floating Point Numbers”
For further information about the data types see description below.
Data Types
Signed Integer
Byte0Byte1Byte2Byte3
Integer32b7..b0b15..b8b23..b16b31..b
The data is represented as bit sequence of length 32.
24
The bit sequence b = b0 .. b31 is assigned the value
INTEGER32(b) = b30*2
30
+ … + b1*21 + b0*20 if b31=0
and, performing two’s complement arithmetic,
INTEGER32(b) = - INTEGER32(^b)-1 if b31=1
Floating Point Numbers
Byte0Byte1Byte2Byte3
Real32b7..b0b15..b8b23..b16b31..b
24
The data type REAL32 is represented as bit sequence of length 32.
The encoding of values follows the IEEE 754-1985 Standard for single precision floating-point.
The bit sequence b = b0 .. b31 is assigned the value
REAL32(b ) = (-1)S * 2
E-127
* (1+F)
Here
S = b31 is the sign.
E = b30*27 + …+ b23*20; 0 < E < 255; is the un-biased exponent.
-23
F = 2
*(b22*222 + …+ b1*21 + b0*20) is the fractional part of the number.
- the device has to be in the PRE-OPERATIONAL mode
- deactivate currently mapped object by writing 0 to object 1A00h subindex 0
- mapping is deactivated, PDO does not supply any data; DLC = 0
- Write desired object to subindex 1 of object 1A00h (INTEGER32: 2090 00 20h / REAL32: 6130 01 20)
- Finally the mapping has to be reactivated by writing 1 to object 1A00h subindex 0
The physical unit of the process value can be configured via object 6131h “Physical Unit Process Value”
The decimal digits can be changed via object 6132h “AI Decimal Digits”
PDO Transmission Types (Object 1800h, subindex 2)
Synchronous Transmission:
A transmission type of n (1 … 240) means that the message is transmitted with every n-th SYNC object.
Asynchronous Transmission:
A transmission type of 254 means that the message will be send after the event timer elapses. The event
timer can be configured via object 1800h subindex 5.
With Service Data Objects the access to entries of a device’s object dictionary is provided.
Read Object
Master sends
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
Transmitter answers
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
580h
+
Node-ID
8
8
CS =
40h
CS =
42h
LSBMSB
Index
LSBMSBLSBMSB
Index
Sub-
Index
Sub-
Index
00h00h00h00h
Data
Write Object
Master sends
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
Transmitter answers
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
580h
+
Node-ID
8
8
CS =
22h
CS =
60h
LSBMSBLSBMSB
Index
LSBMSB
Index
Sub-
Index
Sub-
Index
Data
00h00h00h00h
Abort SDO Transfer
If an error occurred while reading or writing an object, the transmitter answers:
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
8
CS =
80h
LSBMSBLSBMSB
Index
Sub-
Index
Abort Code
Abort Codes
0504 0001hClient/server command specifier not valid or unknown
0601 0001hAttempt to read a write only object
0601 0002hAttempt to write a read only object
0602 0000hObject does not exist in the object dictionary
0606 0000hAccess failed due to an hardware error
0609 0011hSub-index does not exist
0609 0030hValue range of parameter exceeded
0800 0020hData cannot be transferred or stored to the application
This object describes the type of device and its functionality. It is composed of a 16-bit field which describes
the device profile that is used and a second 16-bit field which gives additional information about optional
functionality of the device. The additional information parameter specifies the implemented function blocks.
Entry description
Accessro
PDO MappingNo
Data TypeUNSIGNED 32
Default Value0002 0194h
Data
MSBLSB
Additional InformationDevice Profile Number
0002h0194h
Device Profile 404
Analogue Input Block
1001h Error Register
Object description
This object is an error register for the device. The device maps internal errors in this byte. It is a part of an
emergency object.
Entry description
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value00h
The objects at index 100Ch and 100Dh include the guard time in milliseconds and the life time factor. The life
time factor multiplied with the guard time gives the life time for the Life Guarding Protocol. It is 0 if not used.
Entry description
Accessrw*
PDO MappingNo
Data TypeUNSIGNED 16
Default Value0
* Write access to this object is only allowed, if object 1017h producer heartbeat time is 0.
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Data
MSBLSB
00h00hGuard Time in ms
100Dh Life Time Factor
Object description
The life time factor multiplied with the guard time gives the life time for the node guarding protocol. It is 0 if not
used.
Entry description
Accessrw*
PDO MappingNo
Data TypeUNSIGNED 8
Default Value0
* Write access to this object is only allowed, if object 1017h producer heartbeat time is 0.
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
This object supports the saving of parameters in non volatile memory. By read access the device provides
information about its saving capabilities.
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
Sub-Index01h
Namesave all parameters
Accessrw
PDO MappingNo
Data TypeUNSIGNED 32
Default Value01h
In order to avoid storage of parameters by mistake, storage is only executed when the signature "save" is
written to Subindex 1.
Data
MSBLSB
65h
"e"
76h
"v"
61h
"a"
73h
"s"
"save"
On reception of the correct signature in sub-index 1 the device stores the parameter and then confirms the
SDO transmission (initiate download response). If the storing failed, the device responds with an Abort SDO
Transfer (abort code: 0606 0000h). If a wrong signature is written, the device refuses to store and responds
with Abort SDO Transfer (abort code: 0800 002xh).
On read access to Sub-Index 1 the device provides information about its storage functionality with the
following format:
Data
MSBLSB
00h00h00h01h
Device does not save parameters
autonomously
Device saves parameters on command
The Storage affects the following objects:
100Ch Guard Time6114hAI ADC Sample Rate
100Dh Life Time Factor6121hAI Input Scaling 1 PV
1017h Producer Heartbeat Time6123hAI Input Scaling 2 PV
1800h Transmit PDO Communication Parameters6124hInput Offset
1A00h Transmit PDO Mapping Parameter6131hAI Physical Unit PV
2010h Minimum Allowed Pressure6132hDecimal Digits
2011h Maximum Allowed Pressure61A1h AI Filter Constant
2330h Auto-Operational
With this object the default values of parameters according to the communication and device profile are
restored. By read access the device provides information about its capabilities to restore these values.
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
Sub-Index01h
Namerestore all default parameters
Accessrw
PDO MappingNo
Data TypeUNSIGNED 32
Default Value01h
In order to avoid the restoring of default parameters by mistake, restoring is only executed when the signature
"load" is written to sub-index 1.
Data
MSBLSB
64h
"d"
61h
"a"
6Fh
"o"
6Ch
"l"
"load"
On reception of the correct signature in sub-index 1 the device restores the default parameters and then
confirms the SDO transmission (initiate download response). If the restoring failed, the device responds with
an Abort SDO Transfer (abort code: 0606 0000h). If a wrong signature is written, the device refuses to restore
the defaults and responds with an Abort SDO Transfer (abort code: 0800 002xh).
The default values are set valid after the device is reset (reset node or power cycled)
On read access to sub-index 1 the device provides information about its default parameter restoring capability
with the following format:
Data
MSBLSB
00h00h00h01h
Device restores parameters
The Storage affects the following objects:
100Ch Guard Time6114hAI ADC Sample Rate
100Dh Life Time Factor6121hAI Input Scaling 1 PV
1017h Producer Heartbeat Time6123hAI Input Scaling 2 PV
1800h Transmit PDO Communication Parameters6124hInput Offset
1A00h Transmit PDO Mapping Parameter6131hAI Physical Unit PV
2010h Minimum A llowed Pressure6132hDecimal Digits
2011h Maximum Allowed Pressure61A1h AI Filter Constant
2330h Auto-Operational
The producer heartbeat time defines the cycle time of the heartbeat in milliseconds. The producer heartbeat
time is 0 if it is not used.
Entry description
Accessrw*
PDO MappingNo
Data TypeUNSIGNED 16
Default Value0
* Write access to this object is only allowed, if object 100Ch Guard Time and 100Dh Life Time Factor are 0.
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
This object contains general information about the device. The Vendor ID (sub-index 1h) contains a unique
value allocated to each manufacturer (WIKA: 47h). The manufacturer-specific Product code (sub-index 2h)
identifies a specific device version (Product label: P#). The manufacturer-specific Revision number (sub-index
3h) consists of a major revision number and a minor revision number. The major revision number identifies a
specific CANopen behaviour. If the CANopen functionality is expanded, the major revision has to be
incremented. The minor revision number identifies different versions with the same CANopen behaviour. The
manufacturer-specific Serial number (sub-index 4h) identifies a specific device (Product label: S#).
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value04h
Sub-Index01h
NameVendor ID
Accessro
PDO MappingNo
Data TypeUNSIGNED 32
Default Value00 00 00 47h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
This object contains the mapping for the PDO the device is able to transmit.
The subindex 0h contains the number of valid entries within the mapping record. This number of entries is also
the number of the application variables which shall be transmitted with the corresponding PDO.
The subindex 1h contains the information about the mapped application variable. This entry describes the
PDO contents by their index, sub-index and length. All three values are hexadecimal coded. The length entry
contains the length of the object in bit (20h).
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value04h
Sub-Index01h
Name1st. Mapped Application Object
Accessrw
PDO MappingNo
Data TypeUNSIGNED 32
Default Value2090 00 20 h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
This object defines the minimum allowed pressure. If pressure (field value) exceeds this limit an emergency
message is sent.
Entry description
Accessrw
PDO MappingNo
Data TypeUNSIGNED 16
Default Value0000h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory setting via object 1011h Restore Default Parameters.
If the minimum allowed pressure is set to 0, no emergency message will be send if pressure exceeds the limit.
Data
MSBLSB
00h00hMin. allowed pressure
2011h Maximum allowed Pressure
Object description
This object defines the maximum allowed pressure. If pressure (field value) exceeds this limit an emergency
message is sent.
Entry description
Accessrw
PDO MappingNo
Data TypeUNSIGNED 16
Default ValueFFFFh
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
If the maximum allowed pressure is set to 0xFFFF, no emergency message will be send if pressure exceeds
the limit.
This object defines the Node-ID of the device. The user can configure the Node-ID via this object or LSS
(layer setting services)
Entry description
Accessrw
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
Data Range01h ... 7Fh
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Data
MSBLSB
00h00h00hNode-ID
2321h Configure Bit Timing
Object description
This object defines the bitrate of the device. The user can configure the bitrate via this object or LSS (layer
setting services)
Entry description
Accessrw
PDO MappingNo
Data TypeUNSIGNED 8
Default Value03h
Data Range00h ... 07h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Data
MSBLSB
00h00h00h
Table
index
CiA bit timing table:
BaudrateTable Index
1000 kbit/s0
800 kbit/s1
500 kbit/s2
250 kbit/s3
Through this object the user can set the device to enter the OPERATIONAL-Mode automatically after boot up.
Entry description
Accessrw
PDO MappingNo
Data TypeUNSIGNED 8
Default Value00h
Data Range00h ... 01h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
7122h AI Input Scaling 2 FV
Object description
This object defines the field value of the second calibration point for the analogue input channel. It is scaled in
physical unit of field value.
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
6124h AI Input Offset
Object description
This object defines the additional offset value for the analogue input channel. It is scaled in physical unit of
process value.
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
Writing a signature value of „zero“ to this object causes a modification of the AI Input Offset in such a way that
the actual AI Input PV becomes zero. This cycle is performed for one time.
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
This object represents the result of the input scaling block and gives the measured quantity scaled in the
physical unit of process values (e.g. bar, Pa,...).
Entry description
Sub-Index00h
Namenumber of entries
Accessro
PDO MappingNo
Data TypeUNSIGNED 8
Default Value01h
- 7122h AI Input Scaling 2 FV
The calibration is carried out via objects 6121h and 6123h. The objects 7120h and 7122h are read only.
The device is recalibrated by addressing 2 measuring points and sending the respective set value to the
device. The device offsets the set value specified against the actual pressure value. The 2 measuring points
ideally correspond to lower limit of range and upper limit of range which however might not be possible in each
case (e.g. -1 .. x bar).
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Example 1:
Pressure Range: -1 … 2.5 bar (=> -100,000 … 250,000 Pa output value)
Calibration Point 1:
Pressure applied (reference value): -0.9 bar
The user writes the value that the device is supposed to indicate under the pressure currently applied to object
6121h subindex 1 (AI_Input_Scaling_1_PV), i.e. in this example -90,000 Pa (=> FF FE A0 70 h)
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
8
CS =
22h
The pressure transmitter confirms the successful service by:
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
580h
+
Node-ID
8
CS =
60h
21h61h70hA0hFEhFFh
Index 6121h
21h61h
Index 6121h
01h
Subindex
01h
Subindex
desired value (as integer32)
00h00h00h00h
Calibration Point 2:
Pressure applied (reference value): 2.5 bar
The user writes the value that the device is supposed to indicate under the pressure currently applied to object
6123h subindex 1 (AI_Input_Scaling_2_PV), i.e. in this example 250,000 Pa (=> 00 03 D0 90 h)
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
8
CS =
22h
23h61h90hD0h03h00h
Index 6121h
01h
Subindex
desired value (as integer32)
The pressure transmitter confirms the successful service by:
6124h AI_Input_Offset
For manual offset correction the detected offset is sent to the device, e.g. the device (pressure range 10 bar /
1,000,000 Pa) indicates 0.01 bar / 10,000 Pa at ambient pressure.
The user writes the determined offset to object 6124h subindex 1 (AI_Input_Offset_1),
i.e. in this example 10,000 Pa (=> 00 00 27 10 h)
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
8
CS =
22h
24h61h10h27h00h00h
Index 6124h
01h
Subindex
desired value (as integer32)
The pressure transmitter confirms the successful service by:
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
580h
+
Node-ID
8
CS =
60h
24h61h
Index 6124h
01h
Subindex
00h00h00h00h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Input Autozero
6125h AI_Input_Autozero
The zero (pressure = 0) is changed to the actual pressure.
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
600h
+
Node-ID
8
CS =
22h
25h61h7Ah65h72h6F
Index 6125h
01h
Subindex
“zero” (ASCII)
The pressure transmitter confirms the successful service by:
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
580h
+
Node-ID
8
CS =
60h
25h61h
Index 6125h
01h
Subindex
00h00h00h00h
Changed parameters are not automatically stored, but they have to be stored via object 1010h Store
Parameters.
Furthermore the device can be reset to the factory settings via object 1011h Restore Default Parameters.
Through Module Control Services, the NMT master controls the state of the NMT slaves. The state attribute is
one of the values {STOPPED, PRE-OPERATIONAL, OPERATIONAL and INITIALISING}. The Module Control
Services can be performed with a certain node or with all nodes simultaneously. The NMT master controls its
own NMT state machine via local services, which are implementation dependent.
Module Control Protocol
NMT Master request
IDDLCByte0Byte1
00h2CS
CS: NMT command specifier
NMT services are unconfirmed.
Start Remote Node
Through this service the NMT Master sets the state of the selected NMT Slaves to "OPERATIONAL".
CS = 01h
Stop Remote Node
Through this service the NMT Master sets the state of the selected NMT Slaves to "STOPPED". This service
is unconfirmed.
CS = 02h
Through this service the NMT Master sets the state of the selected NMT Slaves to "PREOPERATIONAL".
This service is unconfirmed.
CS = 80h
Reset Node
Through this service the NMT Master initiates a "RESET APPLICATION" of the selected NMT Slaves from
any state. This service is unconfirmed.
CS = 81h
Reset Communication
Through this service the parameters of the communication profile area are set to their power-on values. After
this the state "INITIALISATION" is finished and the device executes the write boot-up object service and
enters the state PRE-OPERATIONAL.
CS = 82h
Through Error control services the NMT detects failures in a CAN-based Network. Local errors in a node lead
to a change of state (PREOPERATIONAL). Error Control services are achieved principally through periodically
transmitting of messages by a device. There exist two possibilities to perform Error Control.
The guarding is achieved through transmitting guarding requests (Node guarding protocol) by the NMT
Master. If a NMT Slave has not responded within a defined span of time (node life time) or if the NMT Slave’s
communication status has changed, the NMT Master informs its NMT Master Application about that event. If
Life guarding (NMT slave guarded NMT master) is supported, the slave uses the guard time and lifetime factor
from its Object Dictionary to determine the node life time. If the NMT Slave is not guarded within its life time,
the NMT Slave informs its local Application about that event. If guard time and life time factor are 0 (default
values), the NMT Slave does not guard the NMT Master. Guarding starts for the slave when the first remotetransmit-request for its guarding identifier is received. This may be during the boot-up phase or later.
The heartbeat mechanism for a device is established through cyclically transmitting a message by a heartbeat
producer. One or more devices in the network are aware of this heartbeat message. If the heartbeat cycle fails
for the heartbeat producer the local application on the heartbeat consumer will be informed about that event.
Heartbeat Protocol
The Heartbeat Protocol defines an Error Control Service without need for remote frames. A Heartbeat
Producer transmits a Heartbeat message cyclically. One or more Heartbeat Consumer receive the indication.
The relationship between producer and consumer is configurable via the object dictionary. The Heartbeat
Consumer guards the reception of the Heartbeat within the Heartbeat Consumer Time. If the Heartbeat is not
received within the Heartbeat Consumer Time a Heartbeat Event will be generated.
r: reserved (always 0)
s: the state of the Heartbeat producer
0: BOOTUP
4: STOPPED
5: OPERATIONAL
127: PRE-OPERATIONAL
If the Heartbeat Producer Time is configured on a device the Heartbeat Protocol begins immediately. If a
device starts with a value for the Heartbeat Producer Time unequal to 0 the Heartbeat Protocol starts on the
state transition from INITIALISING to PRE-OPERATIONAL. In this case the Bootup Message is regarded as
first heartbeat message. It is not allowed for one device to use both error control mechanisms Guarding
Protocol and Heartbeat Protocol at the same time. If the heartbeat producer time is unequal 0 the heartbeat
protocol is used.
This protocol is used to detect remote errors in the network. Each NMT Slave uses one remote COB for the
Node Guarding Protocol. This protocol implements the provider initiated Error Control services.
s: the state of the NMT Slave
4: STOPPED
5: OPERATIONAL
127: PRE-OPERATIONAL
t: toggle bit. The value of this bit must alternate between two consecutive responses from the NMT Slave. The
value of the toggle-bit of the first response after the Guarding Protocol becomes active, is 0. The Toggle Bit in
the guarding protocol is only reset to 0 when reset_communication is passed (no other change of state resets
the toggle bit). If a response is received with the same value of the toggle-bit as in the preceding response
then the new response is handled as if it was not received.
The NMT Master polls each NMT Slave at regular time intervals. This time-interval is called the guard time
and may be different for each NMT Slave. The response of the NMT Slave contains the state of that NMT
Slave. The node life time is given by the guard time multiplied by the life time factor. The node life time can be
different for each NMT Slave. If the NMT Slave has not been polled during its life time, a remote node error is
indicated through the 'Life Guarding Event' service.
A remote node error is indicated through the 'Node guarding event' service if:
− The remote transmit request is not confirmed within the node life time
− The reported NMT slave state does not match the expected state
If it has been indicated that a remote error has occurred and the errors in the guarding protocol have
disappeared, it will be indicated that the remote error has been resolved through the 'Node Guarding Event'
and 'Life Guarding Event' services.
For the guard time and the life time factor there are default values specified at the appropriate Object
Dictionary entries.
Through this service, the NMT slave indicates that a local state transition occurred from the state
INITIALISING to the state PRE-OPERATIONAL. The protocol uses the same identifier as the error control
protocols.
LSS offers the possibility to change the settings of
• Node-ID
• Bit timing parameters of the physical layer (baud rate)
of a CANopen Slave.
LSS Address
An LSS Slave is identified by an LSS Address. This LSS Address consists of
• vendor-id,
• product-code,
• revision-number and
• serial-number.
These parameters are identical to the Identity-Object 1018h of the object dictionary.
Switch Mode Services
The slave accepts the LSS services only in STOPPED mode (see 9. Network Management Objects).
To configure a slave via LSS the device has to be the LSS-mode CONFIGURATION.
There are two ways to do this:
• Switch Mode Global switches all LSS Slaves between configuration and operation mode(used for configuration of the bit timing).
• Switch Mode Selective switches exactly one LSS Slave between configuration and operation mode
(used for configuration of the node-id)
Configuration Services
Configure Node-ID
By means of this service the LSS Master configures the NMT-address parameter of a LSS Slave.
This service allows only one LSS Slave in configuration mode. The remote result parameter confirms
the success or failure of the service.
Configure Bit Timing Parameters
By means of the Configure Bit Timing Parameters service the LSS Master sets the new bit timing on a
LSS Slave.
By means of the table_selector the bit timing parameter table to be used is specified. In the bit timing
parameter table the bit timing parameters for different baud rates are specified. With table_selector
value ´0´ the standard CiA bit timing parameter table is referenced. The table_index selects the entry
(baud rate) in the selected table (value ‘0’ refers to the highest baud rate).
This service has to be followed by an Activate Bit Timing Parameters service to activate the configured
parameters. After execution of the Configure Bit Timing Parameters service the node may not execute
any remote LSS services except the services Configure Bit Timing Parameters, Activate Bit Timing
Parameters and Switch Mode.
The remote result parameter confirms the success or failure of the service.
Activate Bit Timing Parameters
By means of the Activate Bit Timing Parameters service the LSS Master activates the bit timing as
defined by the Configure Bit Timing Parameters service.
The switch_delay parameter specifies the length of two delay periods of equal length, which are
necessary to avoid operating the bus with differing bit timing parameters. Each node performs the
actual switch of the bit timing parameters ´switch_delay´ milliseconds after the reception of the
command. After performing the switch, a node does not transmit any messages before the second
time ´switch_delay´ has passed.
LSS Protocol Descriptions
A protocol description specifies the sequence of COB's and their format that are exchanged between
the LSS Master and LSS Slave(s) for a particular LSS service. Requesting Messages (from LSS
Master) using COB-ID 2021. Response Messages (from LSS Slave) using COB-ID 2020.
LSS uses command specifiers to identify the commands.
SWITCH MODE PROTOCOLS
Switch Mode Global
LSS-Master sends
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
7E5h8
CS =
04h
modereserved
cs:LSS command specifier
04 for Switch Mode Global
mode:The LSS mode to switch to:
0: switches to operation mode
1: switches to configuration mode
vendor-id: Vendor name part of the LSS address, with respect to index 1018h, subindex 1
product-code:Product name part of the LSS address, with respect to index 1018h, subindex 2
revision-number:Revision part of the LSS address, with respect to index 1018h, subindex 3
serial-number:Serial number part of the LSS address, with respect to index 1018h, subindex 4
table_selector: selects which bit timing parameters table has to be used
0: standard CiA bit timing table
1..255: reserved
table_index : selects the entry (bit timing parameters) in the standard CiA bit timings table
error_code:
0: protocol successfully completed
1: bit timing not supported
2..255: reserved
Activate Bit Timing Parameters Protocol
LSS-Master sends
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
7E5h8
LSS-Slave answers
IDDLCByte0Byte1Byte2Byte3Byte4Byte5Byte6Byte7
7E4h8
CS =
15h
CS =
13h
Switch delay
LSBMSB
error
code
Reserved
reserved
cs:LSS command specifier
15h for Activate Bit Timing Parameters
switch_delay:
The duration of the two periods of time to wait until the bit timing parameters switch is done (first
period) and before transmitting any CAN message with the new bit timing parameters after performing
the switch (second period). The time unit of switch delay is 1 ms.
ISO 11898 Controller area network (CAN)
CiA Draft Standard 301 Version 4.02 - CANopen Application Layer and Communication Profile
CiA Draft Standard 404 Version 1.2 – CANopen Device Profile Measuring Devices and Closed-Loop
Controllers
CiA Draft Recommendation Proposal 303-1 Version 1.1.1 – CANopen Cabling and Connector Pin Assignment
CiA Draft Standard 102 Version 2.0 - CAN Physical Layer for Industrial Applications
CiA Draft Standard Proposal 305 Version 1.1.1 – CANopen Layer Setting Services and Protocol (LSS)
12. Definitions and abbreviations
CANController Area Network
CiACAN in Automation international users and manufacturers group e.V.
COBCommunication Object (CAN Message). A unit of transportation in a CAN network. Data must be
sent across a CAN
COB-IDCOB-Identifier. Identifies a COB uniquely in a network. The identifier determines the priority of that
COB in the MAC
CSCommand Specifier
EDSElectronic Data Sheet
ISOInternational Standardisation Organisation
DLCData Length Code of a CAN message
IDIdentifier
LSBLeast Significant Bit
LSSLayer Setting Services. One of the service elements of the CA N Application Layer in the CAN
Reference Model.
MACMedium Access Control. One of the sub-layers of the Data Link Layer in the CAN Reference Model
that controls
MSBMost Significant Bit
NMTNetwork Management. One of the service elements of the CAN Application Layer in the CAN
Reference Model.
Node-ID The Node-ID of the NMT Slave has to be assigned uniquely (1 .. 127).
OSIOpen Systems Interconnection
PDOProcess Data Object
RORead Only
RWRead/Write
SDOService Data Object
SYNCSynchronisation Object
WOWrite Only
network inside a COB. A COB can contain at most 8 bytes of data.
sub-layer too
It serves to configure parameters of each layer in the CAN Reference Model.
who gets access to the medium to send a message.
It performs initialisation, configuration and error handling in a CAN network.
13. History
Version 1: 10.02.2004
Version 2: 29.09.2004
- added description for Layer setting services (LSS)