Table of Contents
Advertisement
CAN in the ecomatmobile controller
Example of a short message documentation:
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
PRIO, reserv., PG
0
C
As these values are hexadecimal numbers of which individual bits are sometimes needed, the
numbers must be further broken down:
SA / DA
0
3
PF
F
0
PS
0
2
PRIO, reserv., PG
0
C
Out of the 8 bits (0C
16
Not required
x
x
Further typical combinations for "PG, reserv., PG"
18
:
16
Not required
x
x
1C
:
16
Not required
x
x
ifm
System Manual
ecomatmobile
:
16
F
Source / destination address (hexadecimal)
00
PDU format (PF) (hexadecimal)
0F
PDU specific (PS) (hexadecimal)
00
PRIO, reserv., PG (binary)
0000
) only the 5 least significant bits are needed:
x
x
x
SmartController (CR2500) V05
PF + PS
0
0
03
00
02
1100
Priority
0
1
2
2
03
10
Priority
1
1
2
2
6
10
Priority
1
1
2
2
7
10
Use of the CAN interfaces to SAE J1939
SA / DA
2
0
Source / destination address (decimal)
0
PDU format (PF) (decimal)
16
PDU specific (PS) (decimal)
0
Res.
1
0
2
2
0
10
Res.
0
0
2
2
0
10
Res.
1
0
2
2
0
10
3
3
0
2
PG
0
2
0
10
PG
0
2
0
10
PG
0
2
0
10
147
Hide quick links:
Advertisement
Table of Contents
