
LEMCOM CANopen®
– User manual
Detailed
description of CANopen objects
COVAL
– LMCOP-EN-A-1155UM0068
34/49
12.14
2017h – Communication fault counter (local bus)
The number of communication faults on the local bus (master/secondary CAN bus) can be accessed
using the following SDO command:
Client (master)
server (LEMCOM)
CAN-ID
(600h+ID)
620h
Command
40h
Object L
17h
Object H
20h
Subindex
Module no.+1
Byte 0
00h
Byte 1
00h
Byte 2
00h
Byte 3
00h
The subindex is used to define the module to query (from 1 to 16):
- Subindex = 0x01
request for counter value on master module (address #0)
-
…
- Subindex = 0x10
request for counter value on secondary module at address #15
The reply is as follows:
Server (LEMCOM)
Client (master)
CAN-ID
(580h+ID)
5A0h
Command
43h
Object L
17h
Object H
20h
Subindex
Module no.+1
Byte 0
00h
Byte 1
00h
Byte 2
00h
Byte 3
00h
The number of faults is provided in hexadecimal format by the following:
Byte 3
– Byte 2 – Byte 1 – Byte 0
12.15
2018h – Communication fault counter (client bus)
The number of communication faults on the client CAN bus (CANopen communication between the
PLC and the LEMCOM master module) can be accessed using the following SDO command:
Client (master)
server (LEMCOM)
CAN-ID
(600h+ID)
620h
Command
40h
Object L
18h
Object H
20h
Subindex
Module no.+1
Byte 0
00h
Byte 1
00h
Byte 2
00h
Byte 3
00h
The subindex is used to define the module to query (from 1 to 16):
- Subindex = 0x01
request for counter value on master module (address #0)
-
…
- Subindex = 0x10
request for counter value on secondary module at address #15
The reply is as follows:
Server (LEMCOM)
Client (master)
CAN-ID
(580h+ID)
5A0h
Command
43h
Object L
18h
Object H
20h
Subindex
Module no.+1
Byte 0
00h
Byte 1
00h
Byte 2
00h
Byte 3
00h
The number of faults is provided in hexadecimal format by the following:
Byte 3
– Byte 2 – Byte 1 – Byte 0