MPFiltri ICM, Руководство пользователя

Страница: 17 / 26

Appendix B
Messages 17
Messages
CAN2.0B and J1939
The ICM CAN-bus implementation is designed to be interoperable with J1939 net-
works. This is done by restricting CAN-bus message IDs to those within the pro-
prietary ranges allocated by J1939. Advanced J1939 features have been avoided, so
that customers not using J1939 will also be able to communicate using ``generic’’
CAN-bus frames. For non-J1939 users the only requirement is that their network
should support CAN2.0 (29 bit identifiers).
Broadcast messages use the J1939 PDU2 format. These are transmitted periodi-
cally to communicate the ICM status and the latest test results.
Peer-to-peer messages use the J1939 PDU1 format. These are used to
control the
ICM. These are generally optional; customers may opt to leave the ICM automati-
cally testing and broadcasting results.
J1939 Parameters
Node Address (PDU1) 0x3F (J1939 ``Oil Sensor’’)
Command & Configuration Message PGN 0xEF3F
Broadcast Messages PGNs 0xFFB5 - 0xFFB9
Default Broadcast Interval 1s
Data page 0
Priority 6
PDU format / PDU specific Derived from PGN
Byte Endianness All data is in little-endian byte order
Table I CAN-bus Parameters for J1939 Interoperation
Non-J1939 CAN2.0B Users
• Taken together these imply a generic CAN "base address" of 0x18FFB53F.
• Command and control messages can then be sent to CAN address 0x18EF3F00.