![background image](http://html1.mh-extra.com/html/ifm/pdm360ng-series/pdm360ng-series_system-manual_3875026208.webp)
ifm
System Manual
ecomat
mobile
PDM360NG (CR1080, CR1081, CR9042) Target V01
2011-07-28
CAN in the PDM360
CAN units acc. to SAE J1939
208
The following information and tools should be available to develop programs for functions to
SAE J1939:
List of the data to be used by the aggregates
Overview list of the aggregate manufacturer with all relevant data
CAN monitor with 29-bit support
If required, the standard SAE J1939
Identifier acc. to SAE J1939
7675
For the data exchange with SAE J1939 the 29 bit identifiers are determinant. This identifier is pictured
schematically as follows:
A
S
O
F
Identifier 11 bits
S
R
R
I
D
E
Identifier 18 bits
R
T
R
S
O
F
Priority R
D
P
PDU format (PF)
6+2 bits
S
R
R
I
D
E
still PF
PDU specific (PS)
destination address
group extern or proprietary
Source address
R
T
R
B
1 3 2 1 1 1 8 7 6 5 4 3 1 1 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 1
C
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
D
- 28 27 26 25 24 23 22 21 20 19 18 - - 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 -
Legend:
A = CAN extended message format
B = J1939 message format
C = J1939 message bit position
D = CAN 29 bit ID position
SOF =
S
tart
o
f
f
rame
SRR =
S
ubstitute
r
emote
r
equest
IDE =
Id
entifier
e
xtension flag
RTR =
R
emote
t
ransmission
r
equest
PDU =
P
rotocol
D
ata
U
nit
PGN =
P
arameter
G
roup
N
umber = PDU format (PF) + PDU source (PS)
(
CAN-ID
(
→
))
To do so, the 3 essentially communication methods with SAE J1939 are to be respected:
destination specific communication with PDU1 (PDU format 0...239)
broadcast communication with PDU2 (PDU format 240...255)
proprietary communication with PDU1 or PDU2