ifm
System Manual
ecomat
mobile
PDM360NG (CR1080, CR1081, CR9042) Target V01
2011-07-28
CAN in the PDM360
CAN units acc. to SAE J1939
210
Example: short message documentation
7680
But even if the aggregate manufacturer only provides a short documentation, the function parameters
can be derived from the identifier. In addition to the ID, the "transmission repetition rate" and the
meaning of the data fields are also always needed.
If the protocol messages are not manufacturer-specific, the standard SAE J1939 or ISO 11992 can
also serve as information source.
Structure of the identifier 0CF00203
16
:
PRIO, reserved, PG
PF + PS
SA / DA
0 C F 0 0 2 0 3
As these values are hexadecimal numbers of which individual bits are sometimes needed, the
numbers must be further broken down:
SA / DA
Source / Destination Address
(hexadecimal)
Source / Destination Address (decimal)
0 3
00
03
0
3
PF
PDU format (PF) (hexadecimal)
PDU format (PF) (decimal)
F 0
0F
00
16
0
PS
PDU specific (PS) (hexadecimal)
PDU specific (PS) (decimal)
0 2
00
02
0
2
PRIO, reserved, PG
PRIO, reserved, PG (binary)
0 C 0000
1100
Out of the 8 bits (0C
16
) only the 5 least significant bits are needed:
Not necessary
Priority
res.
PG
x x x 0
2
1
2
1
2
0
2
0
2
x 03
10
0
10
0
10
Further typical combinations for "PRIO, reserve., PG"
18
16
:
Not necessary
priority
res.
PG
x x x 1
2
1
2
0
2
0
2
0
2
x 6
10
0
10
0
10
1C
16
:
Not necessary
priority
res.
PG
x x x 1
2
1
2
1
2
0
2
0
2
x 7
10
0
10
0
10
